Random access channel occasions configured on sub-band full duplex symbols

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive: a sub-band full duplex (SBFD) time configuration configuring one or more SBFD symbols on one or more downlink or flexible symbols; a SBFD frequency configuration configuring one or more downlink sub-bands in the one or more SBFD symbols and configuring one or more uplink sub-bands in the one or more SBFD symbols; and a random access channel (RACH) configuration configuring one or more RACH occasions (ROs) in the one or more SBFD symbols. The UE can transmit a RACH message on an uplink sub-band of the one or more uplink sub-bands on a valid RO of the one or more ROs, the valid RO being associated with a subset of a set of SBFD-aware UEs or one or more RACH trigger events. Numerous other aspects are described.

Description

Cross-references to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 609,492, filed March 19, 2024, entitled “RANDOM ACCESS CHANNELOCCASIONS CONFIGURED ON SUB-BAND FULL DUPLEX SYMBOLS”, assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus, and methods for timing random access channels configured on sub-band full-duplex symbols. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0005] Some aspects described herein relate to an apparatus for wireless communication. The apparatus 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 individually or collectively to: receive SBFD timing configurations for configuring one or more sub-band full-duplex (SBFD) symbols on one or more downlink or flexible symbols. The one or more processors may be configured individually or collectively to: receive SBFD frequency configurations for configuring one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols. The one or more processors may be configured individually or collectively to: receive RACH configurations for configuring one or more random access channel (RACH) timings (ROs) in one or more SBFD symbols. The one or more processors may be configured individually or collectively to: transmit RACH messages on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of an SBFD-aware user equipment (UE) set or one or more RACH triggering events.

[0006] Some aspects described herein relate to an apparatus for wireless communication. The apparatus 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 individually or jointly configured to: transmit SBFD timing configurations configuring one or more SBFD symbols on one or more downlink or flexible symbols. The one or more processors may be individually or jointly configured to: transmit SBFD frequency configurations configuring one or more downlink subbands in one or more SBFD symbols and one or more uplink subbands in one or more SBFD symbols. The one or more processors may be individually or jointly configured to: transmit RACH configurations configuring one or more ROs in one or more SBFD symbols. The one or more processors may be individually or jointly configured to: receive RACH messages on an active RO in one or more ROs in an uplink subband of one or more uplink subbands, the active RO being associated with a subset of an SBFD-aware UE set or one or more RACH triggering events.

[0007] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include: receiving an SBFD time configuration that configures one or more SBFD symbols on one or more downlink or flexible symbols. The method may include: receiving an SBFD frequency configuration that configures one or more downlink subbands and one or more uplink subbands on one or more SBFD symbols. The method may include: receiving a RACH configuration that configures one or more ROs on one or more SBFD symbols. The method may include: transmitting a RACH message on an active RO on one or more ROs in an uplink subband of one or more uplink subbands, the active RO being associated with a subset of an SBFD-aware UE set or one or more RACH-triggered events.

[0008] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include: transmitting SBFD time configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols. The method may include: transmitting SBFD frequency configurations that configure one or more downlink subbands and one or more uplink subbands on one or more SBFD symbols. The method may include: transmitting RACH configurations that configure one or more ROs on one or more SBFD symbols. The method may include: receiving RACH messages on active ROs on one or more uplink subbands within one or more uplink subbands, the active ROs being associated with a subset of an SBFD-aware UE set or one or more RACH-triggered events.

[0009] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for: receiving an SBFD time configuration that configures one or more SBFD symbols on one or more downlink or flexible symbols. The apparatus may include components for: receiving an SBFD frequency configuration that configures one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols. The apparatus may include components for: receiving a RACH configuration that configures one or more ROs in one or more SBFD symbols. The apparatus may include components for: transmitting a RACH message on an active RO in one or more ROs on an uplink subband in one or more uplink subbands, the active RO being associated with a subset of an SBFD-aware UE set or one or more RACH triggering events.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting SBFD time configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols. The apparatus may include components for transmitting SBFD frequency configurations that configure one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols. The apparatus may include components for transmitting RACH configurations that configure one or more ROs in one or more SBFD symbols. The apparatus may include components for receiving RACH messages on an active RO in one or more uplink subbands, the active RO being associated with a subset of an SBFD-aware UE set or one or more RACH triggering events.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to: receive an SBFD timing configuration configuring one or more SBFD symbols on one or more downlink or flexible symbols. When executed by one or more processors of the UE, the set of instructions enables the UE to: receive an SBFD frequency configuration configuring one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols. When executed by one or more processors of the UE, the set of instructions enables the UE to: receive a RACH configuration configuring one or more ROs in one or more SBFD symbols. When executed by one or more processors of the UE, the set of instructions enables the UE to: transmit a RACH message on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to: transmit an SBFD timing configuration configuring one or more SBFD symbols on one or more downlink or flexible symbols. When executed by one or more processors of the network node, the set of instructions enables the network node to: transmit an SBFD frequency configuration configuring one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols. When executed by one or more processors of the network node, the set of instructions enables the network node to: transmit a RACH configuration configuring one or more ROs in one or more SBFD symbols. When executed by one or more processors of the network node, the set of instructions enables the network node to: receive RACH messages on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events.

[0013] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0014] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0015] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved through this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

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

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

[0018] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0019] Figure 4 This is a diagram illustrating an example of full-duplex communication in a wireless network according to the present disclosure.

[0020] Figure 5 This is a diagram illustrating an example of full-duplex operation associated with a network node according to this disclosure.

[0021] Figure 6 This is a diagram illustrating an example of subband full-duplex (SBFD) operation associated with a network node according to this disclosure.

[0022] Figure 7 This is a diagram illustrating an example of a two-step random access procedure according to this disclosure.

[0023] Figure 8 This is a diagram illustrating an example of a four-step random access procedure according to this disclosure.

[0024] Figure 9 This is a diagram illustrating an example of random access associated with an SBFD symbol according to this disclosure.

[0025] Figure 10 This is a diagram illustrating an example of an instance associated with a random access channel timing (RO) configured on an SBFD symbol according to this disclosure.

[0026] Figure 11 This is a diagram illustrating an example of a valid and invalid RO configured on an SBFD symbol according to this disclosure.

[0027] Figure 12 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0028] Figure 13 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0029] Figure 14 This is a diagram of an example device for wireless communication according to the present disclosure.

[0030] Figure 15 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0031] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0032] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0033] Random access procedures, such as the Random Access Channel (RACH) procedure, enable User Equipment (UE) to establish a network connection with a network node. The RACH procedure can be prompted by a RACH triggering event. As part of the random access procedure, the UE may transmit uplink communication during a RACH timing (RO). In some examples, the RO may be configured in a Subband Full-Duplex (SBFD) symbol, in which the network node can simultaneously receive uplink communication and transmit downlink communication on different frequency resources. However, allowing any SBFD-aware UE (e.g., a UE capable of transmitting uplink communication on an uplink subband in one or more SBFD symbols) to use a RO configured in an SBFD symbol in response to any RACH triggering event can result in excessively high collision probabilities and latency, such as those associated with random access procedures.

[0034] Various aspects typically involve the eligibility of a UE to use a Remotely Operated (RO) configured on an SBFD symbol. For example, some implementations may restrict the use of an RO configured on an SBFD symbol to a subset of SBFD-aware UEs (e.g., an RO configured on an SBFD symbol may only be valid for a subset of SBFD-aware UEs). In some aspects, the subset of SBFD-aware UEs allowed to use an RO may be based on, for example, the SBFD-aware UE's subscription type, whether the SBFD-aware UE is a cell-edge SBFD-aware UE, whether the SBFD-aware UE is associated with a certain RACH type, or a RACH triggering event.

[0035] Some aspects involve more specifically controlling which ROs in the ROs are valid for a subset of SBFD-aware UEs or for one or more RACH-triggered events. In some aspects, a UE can send RACH messages on an RO in the uplink subband, and a network node can receive RACH messages on an RO in the uplink subband, which are valid for a subset of the SBFD-aware UE set or for one or more RACH-triggered events.

[0036] In some respects, a subset of the SBFD-aware UE set can be associated with cell-edge UEs. For example, an RO configured in an SBFD symbol may be valid for cell-edge SBFD-aware UEs but invalid for cell-center SBFD-aware UEs.

[0037] In some respects, a valid RO can be associated with one or more RACH triggering events. For example, an RO can be valid for an SBFD-aware UE that initiates a RACH procedure in response to one or more RACH triggering events, and an RO can be invalid for an SBFD-aware UE that initiates a RACH procedure in response to other RACH triggering events. For example, an SBFD-aware UE can use an RO only in response to certain RACH triggering events.

[0038] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, associating a valid RO with a subset of the SBFD-aware UE set or one or more RACH-triggered events allows the described techniques to limit the number of valid ROs for that SBFD-aware UE or RACH-triggered events. Therefore, the probability of collisions with valid ROs can be increased (e.g., reduced), and shorter latency in the random access procedure can be achieved.

[0039] Associating a subset of the SBFD-aware UE set with cell-edge UEs can improve RACH coverage and capacity for cell-edge UEs. For example, limiting effective ROs to cell-edge UEs prevents cell-center UEs from interfering with cell-edge UEs attempting to use effective ROs. In this way, cell-edge UEs can be prioritized over cell-center UEs, as cell-edge UEs typically have worse RACH coverage and capacity than cell-center UEs. Associating a subset of the SBFD-aware UE set with cell-center UEs can improve RACH coverage and capacity for cell-center UEs. For example, limiting effective ROs to cell-center UEs prevents cell-edge UEs from interfering with cell-center UEs attempting to use effective ROs.

[0040] A valid Return of Interest (RO) is associated with one or more RACH triggering events, allowing certain RACH triggering events to take precedence over others for the purpose of using the valid RO. For example, a RACH triggering event with strict delay requirements (e.g., and not a RACH triggering event with flexible delay requirements) can be associated with a valid RO, thereby reducing the RACH collision probability of the RACH triggering event with strict delay requirements.

[0041] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables different wireless communication devices to communicate at the city, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution program released by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0042] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0043] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0044] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless communication networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0045] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may be referred to as: NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in the radio access network (RAN).

[0047] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0048] Alternatively, and also as shown, network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 may use protocol stacks that are physically distributed and / or logically distributed across two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple individually deployable units.

[0049] Network nodes 110 of wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some examples, DUs may also host one or more low-PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or low-PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0050] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0051] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0052] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0053] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0054] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0055] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0056] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0057] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), 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 smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0058] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0059] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among a plurality of antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0060] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0061] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. Category 1 UEs 120 facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to Category 2 UEs 120. Category 2 UEs 120 may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. Category 3 UEs 120 may possess intermediate-level complexity and / or capabilities (e.g., capabilities between Category 1 and Category 2 UEs 120). Category 3 UEs 120 may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0062] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can send and receive sidelink communication using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0063] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0064] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0065] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive SBFD time configurations configuring one or more SBFD symbols on one or more downlink or flexible symbols; receive SBFD frequency configurations configuring one or more downlink subbands and one or more uplink subbands on one or more SBFD symbols; receive RACH configurations configuring one or more ROs on one or more SBFD symbols; and transmit RACH messages on active ROs of one or more ROs on the uplink subbands of one or more uplink subbands, the active ROs being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0066] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send SBFD time configurations configuring one or more SBFD symbols on one or more downlink or flexible symbols; send SBFD frequency configurations configuring one or more downlink subbands and one or more uplink subbands on one or more SBFD symbols; send RACH configurations configuring one or more ROs on one or more SBFD symbols; and receive RACH messages on active ROs of one or more ROs on an uplink subband of one or more uplink subbands, the active ROs being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0067] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0068] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0069] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0070] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0071] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0072] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0073] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0074] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0075] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0076] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0077] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0078] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0079] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0080] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (such as a data pipeline, data queue, and / or application executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0081] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0082] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0083] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0084] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0085] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0086] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0087] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0088] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0089] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360) (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0090] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0091] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. 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 RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0092] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0093] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

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

[0095] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0096] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with the RO configured on the SBFD symbol or perform one or more operations associated with the RO configured on the SBFD symbol, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with the RO configured on the SBFD symbol or perform one or more operations associated with the RO configured on the SBFD symbol. Figure 2 Any other component, CU 310, DU 330, or RU 340 that can execute or boot, for example Figure 12 Process 1200 Figure 13The operation of process 1300 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 12 Process 1200 Figure 13 The process 1300 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0097] In some aspects, UE 120 includes components for: receiving SBFD timing configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols; components for: receiving SBFD frequency configurations that configure one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols; components for: receiving RACH configurations that configure one or more ROs in one or more SBFD symbols; and / or components for: transmitting RACH messages on active ROs in one or more uplink subbands, where the active ROs are associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0098] In some aspects, network node 110 includes components for: transmitting SBFD time configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols; components for: transmitting SBFD frequency configurations that configure one or more downlink subbands and one or more uplink subbands in one or more SBFD symbols; components for: transmitting RACH configurations that configure one or more ROs in one or more SBFD symbols; and / or components for: receiving RACH messages on an active RO in one or more uplink subbands, the active RO being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. Components for network node 110 to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0099] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0100] Figure 4 These are illustrations of examples 400, 405, and 410 of full-duplex communication in a wireless network according to this disclosure. "Full-duplex communication" in a wireless network refers to simultaneous bidirectional communication between devices in the wireless network. For example, a UE operating in full-duplex mode can simultaneously (e.g., in the same time slot or the same symbol) transmit uplink communication and receive downlink communication. "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., downlink communication only or uplink communication only) between devices at a given time (e.g., in a given time slot or a given symbol).

[0101] like Figure 4 As shown, Examples 400 and 405 illustrate examples of in-band full-duplex (IBFD) communication. In IBDF, the UE can send uplink communication to and receive downlink communication from the base station on the same time and frequency resources. As shown in Example 400, in the first example of IBDF, the time and frequency resources used for uplink communication can completely overlap with those used for downlink communication. As shown in Example 405, in the second example of IBDF, the time and frequency resources used for uplink communication can partially overlap with those used for downlink communication.

[0102] like Figure 4 Further illustrated, Example 410 shows an example of SBFD communication, which may also be referred to as "Subband Frequency Division Duplex (SBFDD)" or "Flexible Duplex." In SBFD, a UE can simultaneously send uplink communication to and receive downlink communication from a base station on different frequency resources. For example, different frequency resources could be subbands of a band such as a TDD band. In this case, the frequency resources used for downlink communication can be separated from the frequency resources used for uplink communication in the frequency domain by guard bands. Some aspects described herein relate to the UE's eligibility to use ROs configured on SBFD symbols.

[0103] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0104] Figure 5 These are illustrations of examples 500 and 510 associated with full-duplex operation at network node 110 according to this disclosure. In examples 500 and 510, SBFD operation occurs at the network node, while half-duplex operation occurs at one or more UEs 120.

[0105] In Example 500, network nodes (e.g., network node 110) may include those associated with a corresponding beam and located at a distance from it. d The system includes a transmit port (“Tx”) 520 and a receive port (“Rx”) 530. As indicated by reference numeral 540, self-interference may occur when the transmitted signal leaks into the receive port 530. As indicated by reference numeral 550, clutter effects may occur when objects in the surrounding environment (e.g., buildings) reflect the transmitted signal back to the receive port.

[0106] In Example 510, network node 110 can communicate with first UE 120(1) via first port 560(1) and with second UE 120(2) via second port 560(2) using a corresponding beam. As shown by reference numeral 570, network node 110 in half-duplex mode can use downlink MU-MIMO technology to send downlink signals to UE 120(1) and 120(2) in the same time slot. As shown by reference numeral 580, network node 110 in half-duplex mode can use uplink MU-MIMO technology to receive uplink signals from UE 120(1) and 120(2) in the same time slot.

[0107] As shown by reference numeral 590, in full-duplex mode, network node 110 can use downlink MU-MIMO technology to send downlink signals to UE 120(1) in the same time slot, and can use uplink MU-MIMO technology to receive uplink signals from UE 120(2). Network node 110 in full-duplex mode may suffer from self-interference and / or clutter. For example, as shown by reference numeral 595, self-interference may occur when downlink signals sent from the first port 560(1) leak into the second port 560(2).

[0108] Despite self-interference and clutter effects, SBFD offers many potential advantages, some of which will be discussed below. Figure 6 This will be discussed. Some aspects described in this article relate to the UE's eligibility to use the RO configured on the SBFD symbol.

[0109] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0110] Figure 6 This is a diagram illustrating example 600 associated with an SBFD operation at network node 110 according to this disclosure.

[0111] As shown, network node 110 can operate in SBFD mode to simultaneously transmit downlink signal 610 (“DL”) from UE 120(1) and receive uplink signal 620 (“UL”) to UE 120(2) on a subband basis in the same time slot. For example, network node 110 can communicate with UE 120(1) and 120(2) in SBFD mode using a TDD carrier, or the communication can be based on in-band carrier aggregation. As indicated by reference numeral 630, two downlink subbands and one uplink subband can be configured for operation in SBFD mode. Additionally or alternatively, as indicated by reference numeral 640, one downlink subband and one uplink subband can be configured for operation in SBFD mode.

[0112] SBFD can improve uplink duty cycle, which may result in reduced latency and increased uplink coverage. For example, SBFD can achieve latency savings by enabling network node 110 to transmit uplink signals in uplink subbands configured in downlink-only slots or flexible slots, and / or enabling network node 110 to receive downlink signals in downlink subbands within uplink-only slots. Additionally or alternatively, SBFD can improve system capacity, resource utilization, and / or spectrum efficiency, and robustly enable flexible and dynamic uplink or downlink resource adaptation based on uplink or downlink traffic. Some aspects described herein relate to the UE's eligibility to use ROs configured on SBFD symbols.

[0113] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0114] Full-duplex evolution can be supported for NR TDD in unpaired spectrum. In some examples, full-duplex evolution may involve full-duplex enhancement at network node 110 and half-duplex operation at UE 120, without limiting the associated frequency range. In some examples, subband non-overlapping full-duplex can be enhanced on dynamic or flexible TDD. For example, inter-gNB cross-link interference (CLI) and inter-UE cross-link interference (CLI) can be handled (e.g., intra-subband CLI and inter-subband CLI in the case of subband non-overlapping full-duplex). Subband non-overlapping full-duplex operation can coexist with legacy operation in the same channel (e.g., within the same channel) and adjacent channels. Coexistence with adjacent channels in legacy operation, self-interference, inter-subband CLI at network node 110, inter-carrier CLI at network node 110, inter-subband CLI at UE 120 and / or inter-carrier CLI at UE 120 may affect RF requirements such as antenna, RF and / or algorithm design (e.g., antenna isolation, TX intermodulation suppression in RX components, filtering or digital interference suppression, etc.).

[0115] Figure 7 This is a diagram illustrating Example 700 of a two-step random access procedure according to this disclosure. For example... Figure 7 As shown, network node 110 and UE 120 can communicate with each other to perform a two-step random access procedure.

[0116] As shown by reference numeral 705, network node 110 may send one or more synchronization signal blocks (SSBs) and random access configuration information, and UE 120 may receive one or more synchronization signal blocks (SSBs) and random access configuration information. In some aspects, the random access configuration information may be sent and / or indicated by system information (e.g., one or more system information blocks (SIBs)) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in RRC messages and / or PDCCH command messages that trigger the RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in a two-step random access procedure, such as one or more parameters for sending a random access message (RAM) and / or receiving a random access response (RAR) to the RAM.

[0117] As shown by reference numeral 710, UE 120 may transmit a RAM preamble, and network node 110 may receive the RAM preamble. As shown by reference numeral 715, UE 120 may transmit a RAM payload, and network node 110 may receive the RAM payload. As illustrated, as part of the initial (or first) step of a two-step random access procedure, UE 120 may transmit the RAM preamble and RAM payload to network node 110. In some aspects, the RAM may be referred to as message A, msgA, first message, or initial message in the two-step random access procedure. Furthermore, in some aspects, the RAM preamble may be referred to as message A preamble, msgA preamble, preamble, or PRACH preamble, and the RAM payload may be referred to as message A payload, msgA payload, or payload. In some aspects, the RAM may include some or all of the contents of message 1 (msg1) and message 3 (msg3) in the four-step random access procedure described in more detail below. For example, the RAM preamble may include some or all of the contents of message 1 (e.g., PRACH preamble), and the RAM payload may include some or all of the contents of message 3 (e.g., UE identifier, UCI and / or PUSCH transmission).

[0118] As shown by reference numeral 720, network node 110 can receive the RAM preamble sent by UE 120. If network node 110 successfully receives and decodes the RAM preamble, network node 110 can then receive and decode the RAM payload.

[0119] As shown by reference numeral 725, network node 110 may send a RAR (sometimes referred to as a RAR message). As illustrated, network node 110 may send a RAR message as part of the second step of a two-step random access procedure. In some aspects, the RAR message may be referred to as message B, msgB, or the second message in the two-step random access procedure. The RAR message may include some or all of the contents of message 2 (msg2) and message 4 (msg4) in the four-step random access procedure. For example, the RAR message may include the detected PRACH preamble identifier, the detected UE identifier, timing advance value, and / or contention resolution information.

[0120] As indicated by reference numeral 730, as part of the second step of the two-step random access procedure, network node 110 may send PDCCH communication for RAR. This PDCCH communication may schedule PDSCH communication including RAR. For example, the PDCCH communication may indicate resource allocation for PDSCH communication (e.g., in DCI).

[0121] As shown by reference numeral 735, as part of the second step of the two-step random access procedure, network node 110 may send PDSCH communication for the RAR, as scheduled by PDCCH communication. The RAR may be included in the MAC Protocol Data Unit (PDU) of the PDSCH communication. As shown by reference numeral 740, if UE 120 successfully receives the RAR, UE 120 may send a Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK).

[0122] Some aspects described herein control whether UE 120 can send communications in conjunction with Example 700 in the RO configured on the SBFD symbol.

[0123] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0124] Figure 8 This is a diagram illustrating an example of a four-step random access procedure according to this disclosure. For example... Figure 8 As shown, network node 110 and UE 120 can communicate with each other to perform a four-step random access procedure.

[0125] As shown by reference numeral 805, network node 110 may send one or more SSBs and random access configuration information, and UE 120 may receive one or more SSBs and random access configuration information. In some aspects, the random access configuration information may be sent in system information (e.g., one or more SIBs) and / or indicated by the system information and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or PDCCH command message that triggers the RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in the random access procedure, such as one or more parameters for sending RAM and / or one or more parameters for receiving RAR.

[0126] As shown by reference numeral 810 in the attached figure, UE 120 may transmit RAM, which may include a preamble (sometimes referred to as a random access preamble, PRACH preamble, or RAM preamble). A message including the preamble may be referred to as Message 1, msg1, MSG1, First Message, or Initial Message in the four-step random access process. The random access message may include a random access preamble identifier.

[0127] As indicated by reference numeral 815, network node 110 may send a RAR as a response to the preamble. The message including the RAR may be referred to as message 2, msg2, MSG2, or the second message in the four-step random access procedure. In some aspects, the RAR may indicate the detected random access preamble identifier (e.g., received from UE 120 in msg1). Additionally or alternatively, the RAR may indicate the resource allocation to be used by UE 120 to send message 3 (msg3).

[0128] In some respects, as part of the second step of the four-step random access procedure, network node 110 may send PDCCH communication for the RAR. This PDCCH communication may schedule PDSCH communication that includes the RAR. For example, the PDCCH communication may indicate resource allocation for the PDSCH communication. Also as part of the second step of the four-step random access procedure, network node 110 may send PDSCH communication for the RAR, as scheduled by the PDCCH communication. The RAR may be included in the MACPDU of the PDSCH communication.

[0129] As indicated by reference numeral 820, UE 120 may send an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or the third message of the four-step random access procedure. In some aspects, the RRC connection request may include the UE identifier, UCI, and / or PUSCH communication (e.g., the RRC connection request).

[0130] As shown by reference numeral 825, network node 110 may send an RRC connection establishment message. The RRC connection establishment message may be referred to as message 4, msg4, MSG4, or the fourth message in the four-step random access procedure. In some aspects, the RRC connection establishment message may include the detected UE identifier, timing advance value, and / or contention resolution information. As shown by reference numeral 830, if UE 120 successfully receives the RRC connection establishment message, UE 120 may send a HARQ ACK.

[0131] Some aspects described herein control whether UE 120 can send communications in conjunction with Example 800 in the RO configured on the SBFD symbol.

[0132] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0133] Figure 9 This is a diagram illustrating an example of random access associated with an SBFD symbol according to this disclosure.

[0134] As shown, downlink symbol 910 is configured using downlink subband 920 (“DL SB”) and uplink subband 930 (“UL SB”). For example, an SBFD symbol may be configured on downlink symbol 910. As further shown, downlink symbol 940 and uplink symbol 950 may be configured without utilizing downlink and uplink subbands. One or more UEs 120 (e.g., SBFD-aware UEs) may perform transmission, reception, and / or measurement in SBFD symbols and / or non-SBFD symbols.

[0135] Multiple ROs 960 can be configured on uplink subband 930 and / or uplink symbol 950. An "RO" can refer to a set of resources (e.g., frequency resources and / or time resources) on which the UE 120 can transmit communications associated with a random access procedure. In some examples, ROs 960 can be clustered into sets (e.g., three-in-one sets) instead of being evenly spaced in time as shown in Example 900. In some examples, two or more ROs 960 can be configured simultaneously at different frequencies. For example, frequency division multiplexing (FDM) can be used to multiplex two, four, or eight ROs.

[0136] In some examples, SBFD operation can occur at network node 110 within a TDD carrier. SBFD operation can support random access (e.g., a two-step or four-step random access procedure) in an SBFD symbol for UE 120 (e.g., an SBFD-aware UE) in RRC connected mode, RRC idle mode, and / or RRC inactive mode. For example, a random access procedure can be triggered when UE 120 is in RRC connected mode due to handover, beam failure, or RACH of a PDCCH command (e.g., uplink timing update). At least for TDD-UL-DL- ConfigCommon The parameters are configured for PRACH and msg3 transmission in downlink symbols, and random access is allowed in SBFD symbols.

[0137] PRACH and msg3 transmissions in the uplink subband of an SBFD symbol may result in UE to UE CLI; however, allowing SBFD-aware UE random access within an SBFD symbol offers several advantages. In some examples, allowing random access within an SBFD symbol can reduce random access latency, such as latency during the random access procedure, initial access procedure, or handover. In some examples, allowing random access within an SBFD symbol can enable additional ROs within uplink subband 930, thereby reducing RACH (e.g., PRACH) collision probability, increasing RACH capacity, and reducing contention-based collision probability while enabling more UEs 120 to access the network. In some examples, allowing random access within an SBFD symbol can improve or enhance uplink coverage of PRACH and msg3. For example, UE 120 can use uplink subband 930 in consecutive SBFD slots to enable PRACH or msg1 repetition and / or msg3 repetition. Some aspects described herein control whether UE 120 can transmit RACH communication in ROs configured on an SBFD symbol.

[0138] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0139] SBFD operation can support random access by UEs in at least RRC connected mode within an SBFD symbol. For example, RACH (e.g., connected mode RACH) can be enabled in an SBFD symbol. Therefore, an RO can be configured in an SBFD symbol that is configured on a downlink symbol or a flexible symbol (e.g., a legacy downlink symbol or a flexible symbol). However, allowing any SBFD-aware UE to use an RO configured in an SBFD symbol in response to any RACH triggering event could result in excessively high collision probabilities and latency, such as those associated with random access procedures.

[0140] Figure 10 This is a diagram illustrating an example 1000 associated with an RO configured on an SBFD symbol according to this disclosure. For example... Figure 10 As shown, network node 110 and UE 120 can communicate with each other. In some examples, UE 120 may be an SBFD-aware UE configured to operate in half-duplex mode, and network node 110 may operate in full-duplex mode.

[0141] As indicated by reference numeral 1010, network node 110 may transmit, and UE 120 may receive, an SBFD time configuration that configures one or more SBFD symbols on one or more downlink or flexible symbols. For example, the SBFD time configuration may indicate which symbol or slot is an SBFD symbol or SBFD slot on a legacy downlink or flexible symbol or slot. In some examples, in cases involving non-overlapping full-duplex subband operation at network node 110 within a TDD carrier, the SBFD time configuration may be a semi-static indication of the time position of the SBFD subband for a UE in RRC connectivity mode. In some examples, in cases involving non-overlapping full-duplex subband operation at network node 110 within a TDD carrier, the SBFD time configuration may be an indication of the time position of the SBFD subband in the SIB.

[0142] As indicated by reference numeral 1020, network node 110 may transmit, and UE 120 may receive, an SBFD frequency configuration that configures one or more downlink subbands in one or more SBFD symbols and one or more uplink subbands in one or more SBFD symbols. For example, the SBFD frequency configuration may indicate the frequency positions of the downlink and / or uplink subbands of all SBFD symbols or SBFD time slots configured by the SBFD time configuration. In some examples, in the case of non-overlapping full-duplex operation of subbands at network node 110 within a TDD carrier, the SBFD frequency configuration may be a semi-static indication of the frequency domain position of the SBFD subbands for a UE in RRC connectivity mode. In some examples, in the case of non-overlapping full-duplex operation of subbands at network node 110 within a TDD carrier, the SBFD frequency configuration may be an indication of the frequency domain position of the SBFD subbands in the SIB.

[0143] As indicated by reference numeral 1030, network node 110 can transmit and UE 120 can receive a RACH configuration that configures one or more ROs in one or more SBFD symbols. In some examples, the RACH configuration may also configure ROs on uplink symbols. In some examples, the RACH configuration may configure ROs only on SBFD symbols. In such examples, network node 110 can transmit and UE 120 can receive one or more other RACH configurations that configure ROs on uplink symbols.

[0144] As shown by reference numeral 1040, UE 120 may transmit RACH messages on one or more uplink subbands, on one or more valid ROs, and network node 110 may receive RACH messages on one or more uplink subbands, on one or more valid ROs, where a valid RO is associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. In some examples, one or more ROs may be one or more connection-mode ROs (e.g., ROs configured for use by UEs in connection mode). A UE's "valid RO" may be an RO on which the UE is eligible to transmit RACH messages. If a UE is not eligible to transmit RACH messages on an RO, then the RO may be "invalid" for the UE. In this example, the valid RO is valid for UE 120, therefore UE 120 is eligible to use the RO to transmit RACH messages.

[0145] RACH messages can be any suitable communication associated with random access, such as those combined above. Figure 6 or Figure 7The uplink messages discussed. RACH messages can be part of a contention-free random access (CFRA) RACH procedure, a contention-based random access (CBRA) RACH procedure, a connection mode RACH procedure, an initial access RACH procedure, a four-step RACH procedure, and / or a two-step RACH procedure, etc.

[0146] In some respects, a valid RO can be associated with a subset of the SBFD-aware UE set. A valid RO can be associated with a subset of the SBFD-aware UE set because a valid RO can be valid for that subset of the SBFD-aware UE set (e.g., and invalid for other UEs in the SBFD-aware UE set). For example, only a subset of the SBFD-aware UE set can use one or more ROs configured in one or more SBFD symbols, rather than using one or more ROs configured in one or more SBFD symbols on behalf of the entire SBFD-aware UE set (e.g., any SBFD-aware UE).

[0147] In some respects, a subset of the SBFD-aware UE set can be associated with a subscription type. This is because all SBFD-aware UEs in the subset can have a subscription type. For example, telecommunications standards specifications may define rules that only SBFD-aware UEs with a subscription type can use one or more ROs configured in one or more SBFD symbols, or they may define rules that group SBFD-aware UEs by subscription type for the purpose of determining a subset of SBFD-aware UEs. For example, one or more ROs configured in one or more SBFD symbols may be valid for SBFD-aware UEs with a first subscription type and invalid for SBFD-aware UEs with a second subscription type. Examples of subscription types may include UE subscriptions, data plans, or subscription operators.

[0148] In some respects, a subset of the SBFD-aware UE set can be associated with cell-edge UEs. A subset of the SBFD-aware UE set can be associated with cell-edge UEs because all SBFD-aware UEs in the subset can be cell-edge UEs. For example, telecommunications standards specifications may define rules that only cell-edge SBFD-aware UEs can use one or more ROs configured in one or more SBFD symbols. An SBFD-aware UE can be considered "cell-edge" if at least in part based on the RSRP (e.g., as measured at the SBFD-aware UE) of the SSB mapped to the RO not meeting (e.g., less than) an RSRP threshold. For example, one or more ROs configured in one or more SBFD symbols may be valid for cell-edge SBFD-aware UEs and invalid for other SBFD-aware UEs (e.g., cell-center SBFD-aware UEs).

[0149] In some respects, a subset of the SBFD-aware UE set can be associated with cell-center UEs. A subset of the SBFD-aware UE set can be associated with cell-center UEs because all SBFD-aware UEs in the subset can be cell-center UEs. For example, telecommunications standards specifications may define rules that only cell-center SBFD-aware UEs can use one or more ROs configured in one or more SBFD symbols. An SBFD-aware UE can be considered "cell-center" based at least in part on the RSRP (e.g., as measured at the SBFD-aware UE) of the SSB mapped to the RO satisfying (e.g., exceeding) an RSRP threshold. For example, one or more ROs configured in one or more SBFD symbols may be valid for cell-center SBFD-aware UEs and invalid for other SBFD-aware UEs (e.g., cell-edge SBFD-aware UEs).

[0150] In some respects, a valid RO can be associated with one or more RACH triggering events. A valid RO can be associated with one or more RACH triggering events because a valid RO can be valid for an SBFD-aware UE that initiates a RACH procedure in response to one or more RACH triggering events (e.g., and invalid for an SBFD-aware UE that initiates a RACH procedure in response to other RACH triggering events). For example, an SBFD-aware UE can use one or more ROs configured in one or more SBFD symbols only in response to certain RACH triggering events (e.g., one or more RACH triggering events), rather than an SBFD-aware UE using one or more ROs configured in one or more SBFD symbols in response to any RACH triggering event. For example, an SBFD-aware UE that initiates a RACH procedure in response to one or more RACH triggering events may be eligible to use one or more ROs to send RACH messages (e.g., and an SBFD-aware UE that does not initiate a RACH procedure in response to one or more RACH triggering events may not be eligible to use one or more ROs to send RACH messages).

[0151] In some examples, telecommunications standard specifications may define that an SBFD-aware UE may use rules for one or more ROs configured in one or more SBFD symbols only in response to one or more RACH triggering events. One or more RACH triggering events may include one or more of the following: initial access from RRC idle mode; RRC connection re-establishment procedure; handover; beam fault recovery (BFR); RRC connection recovery procedure from RRC inactive mode; downlink out-of-sync; uplink out-of-sync; explicit RRC request during synchronization reconfiguration; time alignment establishment for secondary timing advance group (TAG); scheduling request (SR) failure; request for system information; and / or similar situations. In some examples, any of the listed RACH triggering events may be based on CBRA. Additionally or alternatively, the following RACH triggering events may be based on CFRA: handover, BFR, downlink out-of-sync, explicit RRC request during synchronization reconfiguration, time alignment establishment for secondary TAG, and / or request for system information.

[0152] In some respects, one or more RACH trigger events can be associated with a percentage of ROs configured in the SBFD symbol. One or more RACH trigger events can be associated with a percentage of ROs configured in the SBFD symbol because the percentage of ROs configured in the SBFD symbol can be used by the SBFD-aware UE in response to one or more RACH trigger events. For example, for one or more RACH trigger events, network node 110 can configure the SBFD-aware UE to use the percentage of ROs configured in the SBFD symbol. N % of RO (e.g., for BFR-based RACH procedures, RACH procedures based on system information requests, RACH procedures based on handover, and / or RACH procedures based on PDCCH commands, etc.). N It can be any suitable number between 0 and 100 (inclusive).

[0153] In some respects, multiple RACH triggering events, including one or more RACH triggering events, can be associated with multiple percentages of RO configured in the SBFD symbol. Multiple RACH triggering events can be associated with multiple percentages because the corresponding percentages of RO configured in the SBFD symbol can be used by the SBFD-aware UE in response to the corresponding sets of multiple RACH triggering events. For example, for each set of multiple RACH triggering events, network node 110 can configure the SBFD-aware UE to use the RO configured in the SBFD symbol. N % of RO, of which N The events triggered by multiple RACH events can be the same or different across different sets.

[0154] In some respects, the percentage of ROs configured in the SBFD symbol can be predefined (e.g., in or according to a telecommunications standard specification). In some examples, a telecommunications standard specification may define rules for all ROs configured in the SBFD symbol that an SBFD-aware UE performing a BFR-based RACH procedure can use (e.g., for a BFR-based RACH procedure, ...). N =100). In some examples, telecommunications standard specifications may define that an SBFD-aware UE performing a RACH procedure based on a system information request can use each configured in the SBFD symbol. M The rule of one RO among ROs.

[0155] In some respects, one or more RACH trigger events may be associated with a mode of RO configured in an SBFD symbol. One or more RACH trigger events may be associated with a mode of RO configured in an SBFD symbol because an SBFD-aware UE may respond to one or more RACH trigger events to use the RO in the RO mode. For example, the RO mode may cover all ROs, every even RO, every odd RO, every fourth RO, every RO in the first half of a system frame, and / or every RO in the second half of a system frame, etc. In some examples, network node 110 may configure the RO mode for the corresponding RACH trigger event (e.g., for a BFR-based RACH procedure, a system information request-based RACH procedure, a handover-based RACH procedure, and / or a PDCCH command-based RACH procedure, etc.).

[0156] In some aspects, the RACH configuration may include a RACH mask configuration that indicates which valid ROs are associated with one or more RACH triggering events. A valid RO can be associated with one or more RACH triggering events because the SBFD-aware UE can use a valid RO in response to one or more RACH triggering events. In some examples, the RACH configuration may be or may include a RACH mask configuration that indicates which ROs are available for a given RACH triggering event. For example, the RACH mask configuration may be an index corresponding to an allowed RO mask pattern that covers valid ROs. For example, the RACH mask configuration may correspond to a given RACH triggering event. For example, multiple RACH mask configurations may correspond to corresponding RACH triggering events.

[0157] In some respects, network node 110 may send, and UE 120 may receive, an indication of a dedicated mode that indicates a valid Remote Access Registry (RO) associated with one or more RACH triggering events. For example, network node 110 may signal a dedicated mode to indicate which ROs can be used for a given RACH triggering event. For example, a dedicated mode may correspond to a given RACH triggering event. For example, multiple dedicated modes may correspond to corresponding RACH triggering events.

[0158] In some respects, a RACH configuration can be one of multiple RACH configurations that correspond to a specific subset of the SBFD-aware UE set or a RACH triggering event. For example, network node 110 can configure multiple RACH configurations and activate one or more of these configurations for a specific subset of the SBFD-aware UE set or a RACH triggering event.

[0159] In some aspects, the RACH configuration includes multiple fields that correspond to a corresponding subset of the SBFD-aware UE set or a RACH triggering event. For example, the RACH configuration may include multiple mask fields, mode fields, and / or other RACH configuration fields, and network node 110 may use, reuse, configure, or reconfigure the RACH configuration fields for a corresponding subset of the SBFD-aware UE set or a RACH triggering event. For example, network node 110 may activate one or more RACH configuration fields for a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

[0160] Associating a valid RO with a subset of the SBFD-aware UE set or one or more RACH-triggered events can limit the number of ROs that are valid for it with respect to SBFD-aware UEs or RACH-triggered events. Therefore, the probability of collisions with valid ROs can be increased (e.g., reduced), and shorter latency in the random access procedure can be achieved.

[0161] Associating a subset of the SBFD-aware UE set with cell-edge UEs can improve RACH coverage and capacity for cell-edge UEs. For example, limiting effective ROs to cell-edge UEs can prevent cell-center UEs from interfering with cell-edge UEs attempting to use effective ROs. In this way, cell-edge UEs can be prioritized over cell-center UEs, since cell-edge UEs typically have worse RACH coverage and capacity than cell-center UEs.

[0162] Associating a subset of the SBFD-aware UE set with cell-centric UEs can improve RACH coverage and capacity for cell-centric UEs. For example, limiting effective ROs to cell-centric UEs prevents cell-edge UEs from interfering with cell-centric UEs attempting to use effective ROs. In this way, cell-centric UEs can be prioritized over cell-edge UEs because cell-centric UEs can typically initiate RACH procedures more frequently than cell-edge UEs. For example, cell-centric UEs may initiate RACH procedures more frequently than cell-edge UEs because cell-centric UEs may cause fewer CLIs than cell-edge UEs (e.g., because cell-centric UEs relatively closer to network node 110 can use lower uplink transmit power than cell-edge UEs).

[0163] A valid Returning Root (RO) is associated with one or more RACH triggering events, allowing certain RACH triggering events to take precedence over others for the purpose of using the valid RO. For example, a RACH triggering event with strict latency requirements (e.g., and not a RACH triggering event with flexible latency requirements) can be associated with a valid RO, thereby reducing the RACH collision probability of the RACH triggering event with strict latency requirements. For example, an SBFD-aware UE may use one or more ROs (e.g., valid ROs) configured in one or more SBFD symbols for BFR-based RACH procedures (e.g., RACH procedures in response to BFRs) because BFR-based RACH procedures may require short latency; additionally or alternatively, an SBFD-aware UE may not use one or more ROs configured in one or more SBFD symbols for RACH procedures based on system information requests (e.g., RACH procedures in response to requests for system information).

[0164] In some respects, RACH configuration (including multiple fields corresponding to a corresponding subset of the SBFD-aware UE set or RACH triggering events) can reduce overhead by enabling the use of a single RACH configuration.

[0165] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0166] Figure 11 This is a diagram illustrating an example of a valid and invalid RO configured on an SBFD symbol according to this disclosure.

[0167] As shown, downlink symbol 1110 is configured using downlink subband 1120 (“DL SB”) and uplink subband 1130 (“UL SB”). For example, an SBFD symbol can be configured on downlink symbol 1110. As further shown, downlink symbol 1140 and uplink symbol 1150 may be configured without using downlink and uplink subbands.

[0168] Multiple ROs 1160 can be configured on uplink subband 1130 and / or uplink symbol 1150. In some examples, ROs 1160 can be clustered into sets (e.g., three-in-one sets) instead of being evenly spaced in time as shown in Example 1100. In some examples, two or more ROs of ROs 1160 can be configured simultaneously at different frequencies. For example, FDM can be used to multiplex two, four, or eight ROs.

[0169] As indicated by reference numeral 1170, RO 1160 configured on uplink subband 1130 may be valid for a subset of the SBFD-aware UE set, or for SBFD-aware UEs that initiate a RACH procedure in response to one or more RACH trigger events. As indicated by reference numeral 1180, RO 1160 configured on uplink subband 1130 may be invalid for: non-SBFD-aware UEs, SBFD-aware UEs not in a subset of the SBFD-aware UE set, and / or SBFD-aware UEs that do not initiate a RACH procedure in response to one or more RACH trigger events. As further indicated by reference numerals 1170 and 1180, RO 1160 configured on uplink symbol 1150 may be valid for both SBFD-aware UEs and non-SBFD-aware UEs.

[0170] In some examples, RO 1160 configured on uplink subband 1130 may be valid for a subset of the SBFD-aware UE set, and may be invalid for non-SBFD-aware UEs and / or SBFD-aware UEs not in a subset of the SBFD-aware UE set. In some examples, RO 1160 configured on uplink subband 1130 may be valid for SBFD-aware UEs with a first subscription type, and may be invalid for SBFD-aware UEs with a second subscription type. In some examples, RO 1160 configured on uplink subband 1130 may be valid for cell-edge SBFD-aware UEs, and may be invalid for cell-center SBFD-aware UEs. In some examples, RO 1160 configured on uplink subband 1130 may be valid for cell-center SBFD-aware UEs, while RO 1160 configured on uplink subband 1130 may be invalid for cell-edge SBFD-aware UEs. In some examples, RO 1160 configured on uplink subband 1130 may be valid for SBFD-aware UEs that initiate a RACH procedure in response to a first RACH trigger event, while RO 1160 configured on uplink subband 1130 may be invalid for SBFD-aware UEs that do not initiate a RACH procedure in response to one or more RACH trigger events.

[0171] As indicated above, Figure 11 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 11 The examples described are different.

[0172] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1200 is an example in which a device or UE (e.g., UE 120) performs an operation associated with an RO configured on an SBFD symbol.

[0173] like Figure 12 As shown, in some aspects, process 1200 may include: receiving SBFD timing configuration (block 1210) for configuring one or more SBFD symbols on one or more downlink or flexible symbols. For example, the UE (e.g., using...) Figure 14The depicted receiving component 1402 and / or communication manager 1406 can receive SBFD timing configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols, as described above. In some aspects, the UE can receive SBFD timing configurations as described in conjunction with reference to reference numeral 1010 (…). Figure 10 ).

[0174] like Figure 12 Further shown, in some aspects, process 1200 may include: receiving an SBFD frequency configuration that configures one or more downlink subbands in one or more SBFD symbols and one or more uplink subbands in one or more SBFD symbols (block 1220). For example, the UE (e.g., using...) Figure 14 The depicted receiving component 1402 and / or communication manager 1406 can receive SBFD frequency configurations that configure one or more downlink subbands in one or more SBFD symbols and one or more uplink subbands in one or more SBFD symbols, as described above. In some aspects, the UE can receive SBFD frequency configurations as described in conjunction with reference to reference numeral 1020 (…). Figure 10 ).

[0175] like Figure 12 As further shown, in some aspects, process 1200 may include: receiving a RACH configuration (block 1230) that configures one or more ROs in one or more SBFD symbols. For example, the UE (e.g., using...) Figure 14 The depicted receiving component 1402 and / or communication manager 1406 can receive RACH configurations that configure one or more ROs in one or more SBFD symbols, as described above. In some aspects, the UE can receive RACH configurations as described in conjunction with reference numeral 1030 (…). Figure 10 ).

[0176] like Figure 12 Further, as shown, in some aspects, process 1200 may include: transmitting a RACH message on an active RO (Remote Optical Root) of one or more ROs in an uplink subband of one or more uplink subbands, the active RO being associated with a subset of the SBFD-aware UE set or one or more RACH-triggered events (box 1240). For example, a UE (e.g., using...) Figure 14 The depicted transmitting component 1404 and / or communication manager 1406 can transmit RACH messages on one or more uplink subbands, on one or more active ROs, where the active RO is associated with a subset of the SBFD-aware UE set or one or more RACH triggering events, as described above. In some aspects, the UE can transmit RACH messages as described in conjunction with reference to reference numeral 1040. Figure 10 ).

[0177] Process 1200 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 in this document.

[0178] In the first aspect, the effective RO is associated with a subset of the SBFD-perceived UE set (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0179] In the second aspect, either alone or in combination with the first aspect, a subset of the SBFD-aware UE set is associated with the subscription type (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0180] In the third aspect, either alone or in combination with one or more of the first and second aspects, a subset of the SBFD-sensing UE set is associated with cell-edge UEs (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0181] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, a subset of the SBFD-sensing UE set is associated with the cell center UE (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0182] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, a valid RO is associated with one or more RACH triggering events (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0183] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, one or more RACH triggering events are associated with a percentage of RO configured in the SBFD symbol (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0184] In the seventh aspect, individually or in combination with one or more of the first to sixth aspects, multiple RACH triggering events, including one or more RACH triggering events, are associated with multiple percentages of RO configured in the SBFD symbol, and the percentages of RO configured in the SBFD symbol are predefined (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0185] In the eighth aspect, individually or in combination with one or more of the first to seventh aspects, one or more RACH triggering events are associated with a mode of RO configured in the SBFD symbol (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0186] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the RACH configuration includes a RACH mask configuration that indicates that a valid RO is associated with one or more RACH triggering events (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0187] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1200 includes: receiving an indication of a dedicated mode that indicates a valid RO is associated with one or more RACH triggering events (e.g., as in combination with...). Figure 10 and Figure 11 (As described).

[0188] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the RACH configuration is one of a plurality of RACH configurations corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0189] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the RACH configuration includes multiple fields that correspond to a corresponding subset of the SBFD-aware UE set or a RACH triggering event (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0190] although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 1200 may be executed in parallel.

[0191] Figure 13 This is a diagram illustrating an example process 1300 performed, for example, at a network node or a device of a network node, according to this disclosure. Example process 1300 is an example in which a device or network node (e.g., network node 110) performs operations associated with an RO configured on an SBFD symbol.

[0192] like Figure 13 As shown, in some aspects, process 1300 may include: sending SBFD time configuration (box 1310) for configuring one or more SBFD symbols on one or more downlink or flexible symbols. For example, network nodes (e.g., using...) Figure 15 The depicted transmitting component 1504 and / or communication manager 1506 can transmit SBFD time configurations for configuring one or more SBFD symbols on one or more downlink or flexible symbols, as described above. In some aspects, network nodes can transmit SBFD time configurations as described in conjunction with reference numeral 1010 (…). Figure 10 ).

[0193] like Figure 13 Further shown, in some aspects, process 1300 may include: sending an SBFD frequency configuration that configures one or more downlink subbands in one or more SBFD symbols and one or more uplink subbands in one or more SBFD symbols (box 1320). For example, a network node (e.g., using...) Figure 15 The depicted transmitting component 1504 and / or communication manager 1506 can transmit SBFD frequency configurations, as described above, configuring one or more downlink subbands in one or more SBFD symbols and one or more uplink subbands in one or more SBFD symbols. In some aspects, the network node can transmit as shown in reference numeral 1020 (…). Figure 10 The SBFD frequency configuration described in the document.

[0194] like Figure 13 Further shown, in some aspects, process 1300 may include: sending a RACH configuration (box 1330) that configures one or more ROs in one or more SBFD symbols. For example, network nodes (e.g., using...) Figure 15 The depicted transmitting component 1504 and / or communication manager 1506 can transmit RACH configurations with one or more ROs configured in one or more SBFD symbols, as described above. In some aspects, network nodes can transmit RACH configurations as described in conjunction with reference numeral 1030 (…). Figure 10 ).

[0195] like Figure 13 Further, in some aspects, process 1300 may include: receiving a RACH message on an active RO (Remote Optical Root) of one or more ROs in an uplink subband of one or more uplink subbands, the active RO being associated with a subset of the SBFD-aware UE set or one or more RACH-triggered events (box 1340). For example, a network node (e.g., using...) Figure 15The depicted receiving component 1502 and / or communication manager 1506 can receive RACH messages on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events, as described above. In some aspects, the network node can receive RACH messages as described in conjunction with reference to reference numeral 1040 (…). Figure 10 ).

[0196] Process 1300 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 in this document.

[0197] In the first aspect, the effective RO is associated with a subset of the SBFD-perceived UE set (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0198] In the second aspect, either alone or in combination with the first aspect, a subset of the SBFD-aware UE set is associated with the subscription type (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0199] In the third aspect, either alone or in combination with one or more of the first and second aspects, a subset of the SBFD-sensing UE set is associated with cell-edge UEs (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0200] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, a subset of the SBFD-sensing UE set is associated with the cell center UE (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0201] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, a valid RO is associated with one or more RACH triggering events (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0202] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, one or more RACH triggering events are associated with a percentage of RO configured in the SBFD symbol (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0203] In the seventh aspect, individually or in combination with one or more of the first to sixth aspects, multiple RACH triggering events, including one or more RACH triggering events, are associated with multiple percentages of RO configured in the SBFD symbol, and the percentages of RO configured in the SBFD symbol are predefined (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0204] In the eighth aspect, individually or in combination with one or more of the first to seventh aspects, one or more RACH triggering events are associated with a mode of RO configured in the SBFD symbol (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0205] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the RACH configuration includes a RACH mask configuration that indicates that a valid RO is associated with one or more RACH triggering events (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0206] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1300 includes: sending an indication of a dedicated mode that indicates that a valid RO is associated with one or more RACH triggering events (e.g., as in combination with...). Figure 10 and Figure 11 (As described).

[0207] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the RACH configuration is one of a plurality of RACH configurations corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0208] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the RACH configuration includes multiple fields that correspond to a corresponding subset of the SBFD-aware UE set or a RACH triggering event (e.g., as in combination). Figure 10 and Figure 11 (As described).

[0209] although Figure 13 An example box of process 1300 is shown, but in some respects, process 1300 may include... Figure 13The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 1300 may be executed in parallel.

[0210] Figure 14 This is a diagram of an example device 1400 for wireless communication according to the present disclosure. Device 1400 may be a UE, or a UE may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and / or a communication manager 1406 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is combined with... Figure 1 The described communication manager 140. As shown, device 1400 can communicate with another device 1408 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1402 and transmitting component 1404.

[0211] In some respects, device 1400 can be configured to perform the functions described herein. Figure 10 and Figure 11 The one or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 12 The process is 1200. In some respects, Figure 14 The illustrated device 1400 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 14 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

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

[0213] Transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1408. In some aspects, one or more other components of device 1400 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1408. In some aspects, transmitting component 1404 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 device 1408. In some aspects, transmitting component 1404 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1404 may co-located with the receive component 1402 in one or more transceivers.

[0214] The communication manager 1406 may support the operation of the receiving component 1402 and / or the transmitting component 1404. For example, the communication manager 1406 may receive information associated with configuring the reception of communications by the receiving component 1402 and / or the transmission of communications by the transmitting component 1404. Additionally or alternatively, the communication manager 1406 may generate control information and / or provide control information to the receiving component 1402 and / or the transmitting component 1404 to control the reception and / or transmission of communications.

[0215] The receiving component 1402 can receive SBFD time configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols. The receiving component 1402 can receive SBFD frequency configurations that configure one or more downlink subbands and one or more uplink subbands on one or more SBFD symbols. The receiving component 1402 can receive RACH configurations that configure one or more ROs on one or more SBFD symbols. The transmitting component 1404 can transmit RACH messages on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. In some aspects, the receiving component 1402 can receive an indication of a dedicated mode that indicates that a valid RO is associated with one or more RACH triggering events.

[0216] Figure 14 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 14 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The executable description of the collection of (one or more) components shown is composed of Figure 14 Another set of components shown performs one or more functions.

[0217] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a network node, or a network node may include device 1500. In some aspects, device 1500 includes a receiving component 1502, a transmitting component 1504, and / or a communication manager 1506 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1506 is combined with... Figure 1 The described communication manager 150. As shown, device 1500 can communicate with another device 1508 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1502 and transmitting component 1504.

[0218] In some respects, device 1500 can be configured to perform the functions described herein. Figure 10 and Figure 11 The described one or more operations. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 13 The process is 1300. In some respects, Figure 15 The illustrated device 1500 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 15 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0219] Receiver 1502 may receive communications from device 1508, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiver 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1500. In some aspects, receiver 1502 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1502 and / or transmitter component 1504 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1500 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0220] Transmitting component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1508. In some aspects, one or more other components of device 1500 may generate communications and provide the generated communications to transmitting component 1504 for transmission to device 1508. In some aspects, transmitting component 1504 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 device 1508. In some aspects, transmitting component 1504 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1504 may co-located with the receive component 1502 in one or more transceivers.

[0221] The communication manager 1506 may support the operation of the receiving component 1502 and / or the transmitting component 1504. For example, the communication manager 1506 may receive information associated with configuring the reception of communications by the receiving component 1502 and / or the transmission of communications by the transmitting component 1504. Additionally or alternatively, the communication manager 1506 may generate control information and / or provide control information to the receiving component 1502 and / or the transmitting component 1504 to control the reception and / or transmission of communications.

[0222] Transmitting component 1504 can transmit SBFD time configurations that configure one or more SBFD symbols on one or more downlink or flexible symbols. Transmitting component 1504 can transmit SBFD frequency configurations that configure one or more downlink subbands and one or more uplink subbands on one or more SBFD symbols. Transmitting component 1504 can transmit RACH configurations that configure one or more ROs on one or more SBFD symbols. Receiving component 1502 can receive RACH messages on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of the SBFD-aware UE set or one or more RACH triggering events. In some aspects, transmitting component 1504 can transmit an indication of a dedicated mode that indicates that a valid RO is associated with one or more RACH triggering events.

[0223] Figure 15 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 15 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The executable description of the collection of (one or more) components shown is composed of Figure 15 Another set of components shown performs one or more functions.

[0224] The following provides an overview of some aspects of this disclosure:

[0225] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving an SBFD time configuration configuring one or more SBFD symbols on one or more downlink or flexible symbols; receiving an SBFD frequency configuration configuring one or more downlink subbands and one or more uplink subbands on the one or more SBFD symbols; receiving a RACH configuration configuring one or more ROs on the one or more SBFD symbols; and transmitting a RACH message on an active RO among the one or more ROs on the uplink subband of the one or more uplink subbands, the active RO being associated with a subset of an SBFD-aware UE set or one or more RACH triggering events.

[0226] Aspect 2: According to the method of aspect 1, wherein the effective RO is associated with the subset of the SBFD-aware UE set.

[0227] Aspect 3: According to the method of aspect 2, the subset of the SBFD-aware UE set is associated with a subscription type.

[0228] Aspect 4: According to the method of aspect 2, the subset of the SBFD-aware UE set is associated with cell edge UEs.

[0229] Aspect 5: According to the method of aspect 2, wherein the subset of the SBFD-aware UE set is associated with a cell center UE.

[0230] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the effective RO is associated with the one or more RACH triggering events.

[0231] Aspect 7: According to the method of aspect 6, wherein the one or more RACH triggering events are associated with a percentage of RO configured in the SBFD symbol.

[0232] Aspect 8: The method according to aspect 7 includes multiple RACH trigger events of the one or more RACH trigger events associated with multiple percentages of the RO configured in the SBFD symbol, and wherein the percentages of the RO configured in the SBFD symbol are predefined.

[0233] Aspect 9: According to the method of aspect 6, wherein the one or more RACH triggering events are associated with the mode of the RO configured in the SBFD symbol.

[0234] Aspect 10: The method according to aspect 6, wherein the RACH configuration includes a RACH mask configuration indicating that the valid RO is associated with the one or more RACH triggering events.

[0235] Aspect 11: The method according to aspect 6, the method further comprising: receiving an indication of a dedicated mode, the dedicated mode indicating that the valid RO is associated with the one or more RACH triggering events.

[0236] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the RACH configuration is one of a plurality of RACH configurations, the plurality of RACH configurations corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

[0237] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the RACH configuration includes a plurality of fields corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

[0238] Aspect 14: A method for wireless communication performed by a network node, the method comprising: transmitting an SBFD time configuration configuring one or more SBFD symbols on one or more downlink or flexible symbols; transmitting an SBFD frequency configuration configuring one or more downlink subbands and one or more uplink subbands on the one or more SBFD symbols; transmitting a RACH configuration configuring one or more ROs on the one or more SBFD symbols; and receiving a RACH message on an active RO among the one or more ROs on an uplink subband of the one or more uplink subbands, the active RO being associated with a subset of an SBFD-aware UE set or one or more RACH triggering events.

[0239] Aspect 15: According to the method of aspect 14, wherein the effective RO is associated with the subset of the SBFD-aware UE set.

[0240] Aspect 16: According to the method of aspect 15, the subset of the SBFD-aware UE set is associated with a subscription type.

[0241] Aspect 17: According to the method of aspect 15, the subset of the SBFD-aware UE set is associated with cell edge UEs.

[0242] Aspect 18: According to the method of aspect 15, the subset of the SBFD-aware UE set is associated with a cell center UE.

[0243] Aspect 19: The method according to any one of Aspects 14 to 18, wherein the effective RO is associated with the one or more RACH triggering events.

[0244] Aspect 20: The method according to aspect 19, wherein the one or more RACH triggering events are associated with a percentage of RO configured in the SBFD symbol.

[0245] Aspect 21: The method according to aspect 20 includes multiple RACH triggering events of the one or more RACH triggering events associated with multiple percentages of the RO configured in the SBFD symbol, and wherein the percentages of the RO configured in the SBFD symbol are predefined.

[0246] Aspect 22: According to the method of aspect 19, wherein the one or more RACH triggering events are associated with the mode of the RO configured in the SBFD symbol.

[0247] Aspect 23: The method according to aspect 19, wherein the RACH configuration includes a RACH mask configuration indicating that the valid RO is associated with the one or more RACH triggering events.

[0248] Aspect 24: The method according to aspect 19, the method further comprising: sending an indication of a dedicated mode, the dedicated mode indicating that the valid RO is associated with the one or more RACH triggering events.

[0249] Aspect 25: The method according to any one of Aspects 14 to 24, wherein the RACH configuration is one of a plurality of RACH configurations corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

[0250] Aspect 26: The method according to any one of Aspects 14 to 25, wherein the RACH configuration includes a plurality of fields corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

[0251] Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 26.

[0252] Aspect 28: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 26.

[0253] Aspect 29: 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 26.

[0254] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 26.

[0255] Aspect 31: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 26.

[0256] Aspect 32: A device for wireless communication, the device comprising: a processing system including one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 26.

[0257] Aspect 33: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 26.

[0258] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0259] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0260] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0261] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (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).

[0262] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0263] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication, the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to: Receive SBFD time configuration for configuring one or more sub-band full-duplex (SBFD) symbols on one or more downlink or flexible symbols; Receive an SBFD frequency configuration that configures one or more downlink subbands in the one or more SBFD symbols and one or more uplink subbands in the one or more SBFD symbols; Receive RACH configurations for configuring one or more random access channel (RACH) timings (RO) in the one or more SBFD symbols; as well as On one or more uplink subbands, a RACH message is sent on a valid RO among one or more ROs, the valid RO being associated with a subset of the SBFD-aware user equipment (UE) set or one or more RACH triggering events.

2. The apparatus of claim 1, wherein the effective RO is associated with the subset of the SBFD-aware UE set.

3. The apparatus of claim 2, wherein the subset of the SBFD-aware UE set is associated with a subscription type.

4. The apparatus of claim 2, wherein the subset of the SBFD-aware UE set is associated with a cell edge UE.

5. The apparatus of claim 2, wherein the subset of the SBFD-aware UE set is associated with a cell center UE.

6. The apparatus of claim 1, wherein the effective RO is associated with the one or more RACH trigger events.

7. The apparatus of claim 6, wherein the one or more RACH trigger events are associated with a percentage of ROs configured in the SBFD symbol.

8. The apparatus of claim 7, wherein a plurality of RACH trigger events of the one or more RACH trigger events are associated with a plurality of percentages of the RO configured in the SBFD symbol, and wherein the percentages of the RO configured in the SBFD symbol are predefined.

9. The apparatus of claim 6, wherein the one or more RACH triggering events are associated with a mode of the RO configured in the SBFD symbol.

10. The apparatus of claim 6, wherein the RACH configuration includes a RACH mask configuration indicating that the valid RO is associated with the one or more RACH triggering events.

11. The apparatus of claim 6, wherein the one or more processors are further configured to: Receive an indication of a dedicated mode, which indicates that the valid RO is associated with one or more RACH trigger events.

12. The apparatus of claim 1, wherein the RACH configuration is one of a plurality of RACH configurations, the plurality of RACH configurations corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

13. The apparatus of claim 1, wherein the RACH configuration includes a plurality of fields corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

14. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive SBFD time configuration for configuring one or more sub-band full-duplex (SBFD) symbols on one or more downlink or flexible symbols; Receive an SBFD frequency configuration that configures one or more downlink subbands in the one or more SBFD symbols and one or more uplink subbands in the one or more SBFD symbols; Receive RACH configurations for configuring one or more random access channel (RACH) timings (RO) in the one or more SBFD symbols; as well as On one or more uplink subbands, a RACH message is sent on a valid RO among one or more ROs, the valid RO being associated with a subset of the SBFD-aware UE set or one or more RACH trigger events.

15. The method of claim 14, wherein the effective RO is associated with the subset of the SBFD-aware UE set.

16. The method of claim 14, wherein the valid RO is associated with the one or more RACH triggering events.

17. The method of claim 14, wherein the RACH configuration includes a plurality of fields corresponding to a corresponding subset of the SBFD-aware UE set or a RACH triggering event.

18. An apparatus for wireless communication, the apparatus comprising: The component is used for the following actions: receiving SBFD time configurations for configuring one or more sub-band full-duplex (SBFD) symbols on one or more downlink or flexible symbols; A component for the following operation: receiving an SBFD frequency configuration that configures one or more downlink subbands in the one or more SBFD symbols and configures one or more uplink subbands in the one or more SBFD symbols; The component is used to perform the following actions: receive RACH configurations for configuring one or more random access channel (RACH) timings (RO) in the one or more SBFD symbols; and The component is used to transmit a RACH message on an uplink subband in one or more uplink subbands, on a valid RO in one or more ROs, the valid RO being associated with a subset of the SBFD-aware user equipment (UE) set or one or more RACH triggering events.

19. The apparatus of claim 18, wherein the effective RO is associated with the subset of the SBFD-aware UE set.

20. The apparatus of claim 18, wherein the effective RO is associated with the one or more RACH trigger events.

Images