Physical random access channel configuration for 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 physical random access channel (PRACH) configuration for a random access procedure in a sub-band full duplex (SBFD) symbol. The UE can transmit signaling according to the random access procedure based at least in part on the PRACH configuration. Numerous other aspects are described.

Description

Cross-reference of related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 440,587, filed February 13, 2024, entitled “PHYSICAL RANDOM ACCESSCHANNEL CONFIGURATIONS FOR FULL DUPLEX SYMBOLS”, which is 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 configuring a Physical Random Access Channel (PRACH) for 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. 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

[0004] Full-duplex operation can involve subband full-duplex (SBFD) operation, where transmission and reception can occur simultaneously but on different frequency resources. Downlink resources can be separated from uplink resources in the frequency domain. Downlink and uplink resources can be associated with the same time but different frequencies. In SBFD operation, frequency overlap between downlink and uplink may not occur. One or more Physical Random Access Channel (PRACH) configurations can be defined in an SBFD network. In the first approach, a single PRACH configuration can be defined for all duplex type time slots. In the second approach, a separate PRACH configuration can be defined for each duplex type.

[0005] When two PRACH configurations are provided, a traditional PRACH configuration and an SBFD PRACH configuration can be offered to an SBFD-aware user equipment (UE) (e.g., a separate PRACH configuration dedicated to an SBFD-aware UE). However, it may not be defined whether the traditional PRACH configuration and the SBFD PRACH configuration are separate configurations with completely separate parameters or some common parameters; it may not be defined whether the SBFD PRACH configuration is suitable for various use cases; and when a UE-specific SBFD PRACH configuration is not provided for use cases such as beam fault recovery (BFR), it may not be defined whether the UE should use the cell-common traditional configuration or the cell-common SBFD configuration. In these cases, the UE may not be able to support SBFD PRACH configurations for various use cases, which may degrade the overall performance of the UE.

[0006] Different tables can be defined for PRACH configuration based on duplex and frequency range. According to these tables, the Random Access Channel (RACH) timing (RO) can occur only in certain subframes of a frame, where these subframes can be associated with uplink symbols. Subframes used for PRACH can be configured to target uplink slots in Time Division Duplex (TDD) mode, which may disallow the use of ROs in SBFD symbols (e.g., downlink symbols derived from SBFD). The restriction that ROs can only occur in certain subframes of a frame may prevent the use of ROs in SBFD symbols, potentially degrading overall system performance.

[0007] Various aspects as a whole relate to PRACH configuration for full-duplex time slots. Some aspects more specifically relate to SBFD-specific PRACH configuration for SBFD in unpaired spectrum. In some examples, a UE may send capability signaling to a network node indicating that it is an SBFD-aware UE. The UE may receive from the network node PRACH configuration for random access procedures in SBFD symbols. This PRACH configuration may be an SBFD-specific PRACH configuration. In other words, this PRACH configuration may be a full-duplex time slot. This SBFD-specific PRACH configuration may be based at least in part on: a TDD frequency range 1 / 2 (FR1 / 2) table, which includes one or more PRACH configurations to allow one or more subframe configurations specific to SBFD; a table for SBFD, which is separate from the TDD FR1 / 2 table and the Frequency Division Duplex (FDD) FR1 / 2 table; or the FDD FR1 / 2 table. The PRACH configuration can be a separate PRACH configuration dedicated to the SBFD-aware UE and separate from the traditional PRACH configuration. This separate PRACH configuration can be at least partially based on a separate common PRACH configuration compared to the traditional PRACH. This separate PRACH configuration can be at least partially based on a common PRACH configuration with a modified structure to support more than one value for one or more parameters. This separate PRACH configuration can be at least partially based on a single common PRACH configuration having an independent Synchronization Signal Block (SSB) to RO mapping for ROs falling within the SBFD time slot. The UE can send signaling to the network node according to the random access procedure based at least partially on this PRACH configuration.

[0008] 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, the described techniques allow the UE to utilize ROs in SBFD symbols by modifying the PRACH configuration table in the specification. In addition to subframe 4 or subframe 9, the UE may also be able to use ROs occurring in other subframes of the frame, such as subframe 3 or subframe 7. The ability to utilize ROs in SBFD symbols can improve overall UE performance in terms of reducing random access latency and lowering the probability of PRACH collisions with other UEs. Furthermore, the UE may be able to distinguish between two different PRACH configurations, one of which may be a conventional PRACH configuration, and the other may be an SBFD-specific PRACH configuration provided for an SBFD-aware UE. The UE's ability to utilize this SBFD-specific PRACH configuration, which may differ from the conventional PRACH configuration, allows the UE to perform PRACH operations during SBFD operation, which can improve overall UE performance.

[0009] In some specific implementations, an apparatus for wireless communication at a UE includes: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the UE to: receive a PRACH configuration for a random access procedure in an SBFD symbol; and transmit signaling according to the random access procedure based at least in part on the PRACH configuration.

[0010] In some specific implementations, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: transmit a PRACH configuration for a random access procedure in an SBFD symbol; and receive signaling according to the random access procedure based at least in part on the PRACH configuration.

[0011] In some specific implementations, a method of wireless communication performed by a UE includes: receiving a PRACH configuration for a random access procedure in an SBFD symbol; and transmitting signaling according to the random access procedure based at least in part on the PRACH configuration.

[0012] In some specific implementations, a method of wireless communication performed by a network node includes: transmitting a PRACH configuration for a random access procedure in an SBFD symbol; and receiving signaling according to the random access procedure based at least in part on the PRACH configuration.

[0013] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a PRACH configuration for a random access procedure in an SBFD symbol; and transmit signaling according to the random access procedure, at least in part based on the PRACH configuration.

[0014] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit a PRACH configuration for a random access procedure in an SBFD symbol; and receive signaling according to the random access procedure, at least in part based on the PRACH configuration.

[0015] In some specific implementations, an apparatus for wireless communication includes: a component for receiving a PRACH configuration for a random access procedure in an SBFD symbol; and a component for transmitting signaling according to the random access procedure based at least in part on the PRACH configuration.

[0016] In some specific implementations, an apparatus for wireless communication includes: a component for transmitting a PRACH configuration for a random access procedure in an SBFD symbol; and a component for receiving signaling according to the random access procedure based at least in part on the PRACH configuration.

[0017] 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.

[0018] 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

[0019] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by 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.

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

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

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

[0023] Figure 4 This is a diagram illustrating an example of random access associated with a subband full-duplex (SBFD) symbol according to this disclosure.

[0024] Figure 5 This is a diagram illustrating an example of a mapping associated with a Synchronization Signal Block (SSB) Random Access Channel (RACH) Timing (RO) according to this disclosure.

[0025] Figure 6 This is a diagram illustrating an example of an SSB-RO mapping associated with this disclosure.

[0026] Figure 7 This is a diagram illustrating an example of a configuration associated with the Public Physical Random Access Channel (PRACH) according to this disclosure.

[0027] Figures 8 to 15 This is a diagram illustrating an example of a PRACH configuration associated with full-duplex symbols according to this disclosure.

[0028] Figures 16 to 17 This is a diagram illustrating an example procedure associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0029] Figures 18 to 19 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0030] 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 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 practiced 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.

[0031] 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 boxes, 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0032] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced 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).

[0033] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 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. These 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.

[0034] 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).

[0035] 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 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.

[0036] 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, the 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.

[0037] 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 also be referred to as an 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 a radio access network (RAN).

[0038] 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 radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio 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 the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0039] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among 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 units that can be deployed independently.

[0040] Network nodes 110 of the 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 functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, PRACH extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower 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.

[0041] 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.

[0042] 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)). A 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).

[0043] 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).

[0044] 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.

[0045] 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). UE 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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 multiple 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.

[0051] 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 collectively referred to 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).

[0052] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, as well as legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category 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.

[0053] 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 use 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 to send and receive sidelink communication. 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.

[0054] 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), in which 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., in 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.

[0055] 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).

[0056] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a Physical Random Access Channel (PRACH) configuration for a random access procedure in a subband full-duplex (SBFD) symbol; and transmit signaling according to the random access procedure based at least in part on the PRACH configuration. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a PRACH configuration for a random access procedure in an SBFD symbol; and receive signaling according to the random access procedure, at least in part based on the PRACH configuration. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0058] 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.

[0059] Figure 2 This is a diagram illustrating an example network node 110 communicating with an example UE 120 in a wireless network according to the present disclosure.

[0060] like Figure 2 As 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.

[0061] 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.

[0062] 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 processors in the first set and the processors in the second set 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 combined... 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.

[0063] 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) according to 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)).

[0064] 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., T A 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).

[0065] 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.

[0066] 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.

[0067] 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 to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0068] 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 one or more 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.

[0069] 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 perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0070] UE 120 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set 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.

[0071] 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 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0072] 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.

[0073] 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 symbol streams (e.g., U A set of output symbol streams is provided to a set of modems 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.

[0074] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or U Uplink 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., transmissions made 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).

[0075] 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), a set of coplanar antenna elements, a set 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.

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

[0077] 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.

[0078] 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 speaking, 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).

[0079] 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.

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

[0081] 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.

[0082] Each of the components of the decomposed 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.

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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).

[0087] Network node 110, network node 110's controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340 or Figure 1 , Figure 2 or Figure 3 Any other component may implement one or more technologies or perform one or more operations associated with the PRACH configuration for full-duplex symbols, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 16 Process 1600 Figure 17 The operation of process 1700 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 16 Process 1600 Figure 17The process 1700 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.

[0088] In some aspects, the UE (e.g., UE 120) includes: components for receiving PRACH configuration for a random access procedure in an SBFD symbol; and / or components for transmitting signaling according to the random access procedure, at least in part based on the PRACH configuration. Components enabling the UE to perform the operations described herein may include one or more of, for example, a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0089] In some aspects, a network node (e.g., network node 110) includes: components for transmitting a PRACH configuration for a random access procedure in an SBFD symbol; and / or components for receiving signaling according to the random access procedure, at least in part based on the PRACH configuration. Components enabling the network node to perform the operations described herein may include, for example, one or more of a communications manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0090] 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.

[0091] Full-duplex operation can involve SBFD (or flexible duplex) operation, where transmission and reception can occur simultaneously but on different frequency resources. Downlink resources can be separated from uplink resources in the frequency domain. Downlink and uplink resources can be associated with the same time but different frequencies. In SBFD operation, frequency overlap between the downlink and uplink may not occur.

[0092] SBFD operation can increase the uplink duty cycle, which can reduce latency (e.g., downlink signals can be received in uplink-only slots, resulting in latency savings) and improve uplink coverage. SBFD operation can improve system capability, resource utilization, and / or spectral efficiency. SBFD operation can robustly achieve flexible and dynamic uplink / downlink resource adaptation based on uplink / downlink traffic.

[0093] Random access can be associated with SBFD symbols. When random access is allowed in SBFD symbols used for SBFD-aware UEs, random access latency can be reduced, PRACH collision probability can be decreased, and / or PRACH and Message 3 (Msg3) coverage can be improved. PRACH coverage can be improved by using long PRACH sequences or PRACH repetition. PRACH and Msg3 transmission in the uplink subband of SBFD symbols may cause UE-to-UE cross-link interference (CLI). At least for TDD uplink-downlink common configurations (... TDD-UL-DL-ConfigCommon In the SBFD symbol, PRACH and Msg3 transmissions are configured as downlink symbols, and random access is permitted.

[0094] Random access in SBFD symbols can enhance uplink coverage. UEs can utilize uplink subbands in consecutive SBFD slots to implement message 1 (Msg1) and Msg3 repetition and frequency hopping, which enhances uplink coverage for initial access. Random access in SBFD symbols can improve PRACH capacity. Additional PRACH timing can be implemented within uplink subbands, which improves PRACH capacity and reduces contention-based collision probability, while enabling more UEs to access the network. Random access in SBFD symbols can reduce random access latency. Latency during the random access procedure, initial access, and / or handover can be reduced, especially for Layer 1 (L1) / Layer 2 (L2) (L1 / L2) mobility.

[0095] Figure 4 This is an illustration of example 400 associated with random access in an SBFD symbol according to this disclosure.

[0096] like Figure 4 As shown, the first symbol / time slot 402 can be a downlink symbol / time slot. The first symbol / time slot 402 can be associated with a Synchronization Symbol Block (SSB), a Control Resource Set (CORESET), and a System Information Block (SIB). The second symbol / time slot 404 can be an SBFD symbol / time slot, where the SBFD symbol / time slot can include both downlink and uplink resources. The second symbol / time slot 404 can include one or more PRACH Opportunities (ROs). The third symbol / time slot 406 can be an SBFD symbol / time slot. The third symbol / time slot 406 can include PUSCH resources. The fourth symbol / time slot 408 can be an SBFD symbol / time slot. The fourth symbol / time slot 408 can include PUCCH resources. One or more ROs, PUSCH resources, and PUCCH resources can be specific to an uplink subband. The fifth symbol / time slot 410 can be an uplink symbol / time slot. The fifth symbol / time slot 410 can be associated with an uplink subband.

[0097] 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.

[0098] For subband non-overlapping full-duplex operations (e.g., SBFD operations) at network nodes within a TDD carrier, a semi-static indication of the time position of the SBFD subband for a UE in RRC connectivity mode can be defined (e.g., indication of the time position of the SBFD subband in the SIB is not excluded), a semi-static indication of the frequency domain position of the SBFD subband for a UE in RRC connectivity mode can be defined (e.g., indication of the frequency domain position of the SBFD subband in the SIB is not excluded), an SBFD operation to support random access by a UE in RRC connectivity mode in an SBFD symbol can be defined, and / or an SBFD operation to support random access by a UE in RRC idle / inactive mode can be defined.

[0099] One or more PRACH configurations can be defined in an SBFD network. In the first approach, a single PRACH configuration can be defined for all duplex type slots. For SBFD-aware UEs, validity rules can be defined in SBFD slots configured in downlink symbols by TDD uplink / downlink. A PRACH configuration can be associated with a single configuration, which translates to less system information and / or overhead. A single PRACH configuration can lead to SSB-RO mapping ambiguity between traditional UEs and SBFD-aware UEs. Furthermore, PRACH frequency resources can lead to resource fragmentation in uplink slots when the uplink subband is in the middle of a slot. In the second approach, separate PRACH configurations can be defined for each duplex type (TDD and SBFD). In addition to the traditional PRACH configuration, another separate PRACH configuration can be dedicated to SBFD-aware UEs. Separate PRACH configurations can create independent PRACH configurations (e.g., without SSB-RO mapping ambiguity), and each PRACH configuration can have its own parameters. A separate PRACH configuration can create additional configuration / overhead, and validity rules may need to be defined differently for a separate PRACH configuration dedicated to SBFD-aware UEs.

[0100] Figure 5 This is a diagram illustrating example 500 associated with SSB-RO mapping according to this disclosure.

[0101] As shown by reference numeral 502, for a single PRACH configuration, a legacy UE SSB-RO mapping and an SBFD-aware UE SSB-RO mapping can be defined. Some ROs may be invalid for both legacy and SBFD-aware UEs, while some ROs may be invalid for legacy UEs but valid for SBFD-aware UEs. The legacy UE SSB-RO mapping and the SBFD-aware UE SSB-RO mapping may be inconsistent with each other, which may be at least in part based on the fact that some ROs are invalid for legacy UEs but valid for SBFD-aware UEs. As shown by reference numeral 504, the SBFD-aware UE SSB-RO mapping can be updated, which resolves the consistency issue with the legacy UE SSB-RO mapping. However, some ROs may still be invalid for both legacy and SBFD-aware UEs, and / or valid only for SBFD-aware UEs.

[0102] 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.

[0103] Figure 6 This is a diagram illustrating example 600 associated with SSB-RO mapping according to this disclosure.

[0104] like Figure 6 As shown, for the SBFD-specific PRACH configuration, the traditional RO and the SBFD-specific RO can be defined separately, which may not lead to ambiguity in the SSB-RO mapping.

[0105] 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.

[0106] Figure 7 This is a diagram illustrating example 700 associated with a public PRACH configuration according to this disclosure.

[0107] like Figure 7 As shown, the common PRACH configuration can be indicated in SIB type 1 (SIB1). PRACH-ConfigCommon The public PRACH configuration can be used for initial access and other random access scenarios, such as BFR when no UE-specific BFR configuration is available. The public PRACH configuration may include one or more parameters associated with the total number of preambles, the association between SSBs and ROs, and the general PRACH configuration, which may indicate information about the time-domain allocation and periodicity of ROs.

[0108] 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.

[0109] PRACH configuration can indicate various types of information. For example, PRACH configuration can indicate the public BWP uplink configuration ( BWP-UplinkCommon ), Community public PRACH configuration ( PRACH-ConfigCommon ), random access parameters plus general PRACH configuration ( PRACH-ConfigGeneric BWP uplink dedicated ( BWP-UplinkDedicated Configuration, beam fault recovery configuration BeamFailureRecoveryConfig BFR PRACH configuration ( PRACH-configBFR System information request configuration () SI_RequestConfig ), PRACH timing system information ( PRACH-OccasionSI PRACH configuration system information ( PRACH-ConfigSI ), with synchronous reconfiguration ( ReconfigurationWithSync ), Dedicated PRACH configuration ( PRACH-ConfigDedicated General PRACH configuration ( PRACH-ConfigGeneric The UE can use the PRACH command (DCI 1_0) and / or the PDCCH command. For contention-based random access (CBRA), the UE can use the PRACH configuration from SIB1. For contention-free random access (CFRA), the UE can use the beam fault recovery configuration. CFRA can be used when the network node configures dedicated PRACH resources for system information requests for the UE, or CBRA can be used in other ways. The PDCCH command can trigger CFRA, and the UE can obtain CFRA parameters (e.g., preamble index) from the target field in the DCI payload. The UE can apply CBRA when all random access preamble indexes provided in the PDCCH command are zero.

[0110] When two PRACH configurations are provided, a traditional PRACH configuration and an additional SBFD PRACH configuration can be offered to an SBFD-aware UE (e.g., a separate PRACH configuration dedicated to the SBFD-aware UE). However, it may not be defined whether the traditional PRACH configuration and the SBFD PRACH configuration are separate configurations with completely separate parameters or some common parameters. It may not be defined whether the SBFD PRACH configuration is suitable for various use cases (e.g., random access triggered events). Furthermore, when no UE-specific SBFD PRACH configuration is provided for use cases such as BFR, it may not be defined whether the UE should use the cell-common traditional PRACH configuration or the cell-common SBFD configuration. In these cases, the UE may not be able to support SBFD PRACH configurations for various use cases (e.g., random access triggered events such as BFR, mobility, or SI requests), which may degrade the overall performance of the UE.

[0111] Different tables can be defined for PRACH configuration based on duplex (e.g., TDD or FDD) and frequency range (e.g., FR1 and FR2). These different tables may include a first table associated with TDD-FR1, a second table associated with FDD-FR1, and a third table associated with TDD-FR2. For example, the tables may indicate the PRACH configuration index, preamble format, subframe number, start symbol, number of PRACH slots within a subframe, number of time-domain PRACH events within a PRACH slot, and / or the PRACH duration value.

[0112] For example, in long sequence format 1 in the FR1 TDD band and in DDDSUDSUU mode (where D is a downlink symbol, S is a flexible symbol, and U is an uplink symbol) in FR1 30kHz subcarrier spacing (SCS), a 20ms RO periodicity can be determined using PRACH configuration indices 3 to 6 (e.g., 20ms PRACH timing periodicity). RO may occur only in the fourth or ninth subframe of a frame, where the fourth and ninth subframes may be associated with uplink symbols. Subframes used for PRACH may be configured to target uplink slots in TDD mode, which may not allow the use of RO in SBFD symbols (e.g., downlink symbols coordinated in SBFD, such as DDDXXXXU). The limitation that RO may only occur in certain subframes of a frame may prevent the use of RO in SBFD symbols, potentially degrading overall system performance.

[0113] In various aspects of the technologies and apparatus described herein, the UE can send capability signaling to a network node indicating that the UE is an SBFD-aware UE. The UE can receive from the network node a PRACH configuration for random access procedures in SBFD symbols. This PRACH configuration can be an SBFD-specific PRACH configuration. In other words, the PRACH configuration can be a full-duplex time slot. The SBFD-specific PRACH configuration can be based at least in part on: a TDD Frequency Range 1 / 2 (FR1 / 2) table, which includes one or more PRACH configurations to allow one or more subframe configurations specific to SBFD; a table for SBFD, which is separate from the TDD FR1 / 2 table and the FDD FR1 / 2 table; or an FDD FR1 / 2 table. The PRACH configuration can be a separate PRACH configuration dedicated to the SBFD-aware UE and separate from the conventional PRACH configuration. The PRACH configuration can be a cell-common configuration or a UE-specific configuration. A separate PRACH configuration may be at least partially based on a separate cell-common (or cell-specific) PRACH configuration compared to a traditional cell-common PRACH. A separate PRACH configuration may be at least partially based on a cell-common PRACH configuration with a modified structure to support more than one value for one or more parameters. A separate PRACH configuration may be at least partially based on a single public PRACH configuration having an independent SSB-to-RO mapping for ROs falling within an SBFD slot. The UE may send signaling to the network node according to the random access procedure based at least partially on this PRACH configuration.

[0114] In some respects, by modifying the PRACH configuration table in the specification, the UE can utilize ROs in SBFD symbols. In addition to subframe 4 or subframe 9, the UE can also use ROs occurring in other subframes of the frame, such as subframe 3 or subframe 7. The ability to utilize ROs in SBFD symbols improves overall UE performance. Furthermore, the UE can distinguish between two different PRACH configurations: one can be a conventional PRACH configuration, while the other can be an SBFD-specific PRACH configuration provided for SBFD-aware UEs. The UE's ability to utilize this SBFD-specific PRACH configuration, which can differ from the conventional PRACH configuration, allows the UE to perform PRACH operations during SBFD operation, further improving overall UE performance.

[0115] Figure 8 This is a diagram illustrating an example 800 associated with a PRACH configuration for full-duplex symbols according to this disclosure. (See diagram for example...) Figure 8As shown, Example 800 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0116] As shown by reference numeral 802 in the attached figure, the UE can send capability signaling to the network node indicating that the UE is an SBFD-aware UE. In other words, the UE can send an SBFD-aware UE signaling capability to the network node, which indicates that the UE can support the PRACH configuration for random access procedures in SBFD symbols. The UE can send the capability signaling via RRC signaling.

[0117] As shown by reference numeral 804, the UE can receive PRACH configuration for random access procedures in an SBFD symbol from the network node. This PRACH configuration can be an SBFD-specific PRACH configuration. The UE can receive the PRACH configuration via RRC signaling, in which case the PRACH configuration can be at least partially based on capability signaling. Alternatively, the UE can receive the PRACH configuration via SIB (e.g., via broadcast), in which case the UE may not send capability signaling to the network node.

[0118] In some respects, SBFD-specific PRACH configurations may be at least partially based on a TDD FR1 / 2 random access table, which includes one or more PRACH configurations to allow specific configurations of one or more subframes within an SBFD symbol. SBFD-specific PRACH configurations may be at least partially based on a random access table for SBFD that is separate from both the TDD FR1 / 2 and FDD FR1 / 2 random access tables. SBFD-specific PRACH configurations may be at least partially based on the FDD FR1 / 2 random access table.

[0119] In some respects, as part of the SBFD-specific PRACH configuration, the PRACH configuration can be specific to the SBFD in the unpaired spectrum. In a first option, the TDD-FR1 / FR2 PRACH tables can be utilized, and additional PRACH configurations (e.g., extra rows) can be added to allow for other subframe configurations. For example, a new PRACH configuration can be added to allow RO to occur at subframe 3 or subframe 7 of the frame. In a second option, in addition to TDD and FDD for each frequency range (e.g., FR1, FR2, etc.), new tables (e.g., SBFD-FR1 and SBFD-FR2 tables) can be defined for SBFD duplex. In a third option, FDD tables (e.g., FFD-FR1 or FDD-FR2) can be reused.

[0120] In some respects, the PRACH configuration can be a separate cell-specific PRACH configuration dedicated to SBFD-aware UEs and separate from traditional cell-specific PRACH configurations (e.g., such as...). Figure 9 (As shown). Individual PRACH configurations may be at least partially based on a single-cell common PRACH configuration compared to a conventional cell common PRACH configuration. Individual PRACH configurations may be at least partially based on a single-cell common PRACH configuration with a modified structure to support more than one value for one or more parameters, and the single-cell common PRACH configuration may include more than one general PRACH configuration parameter. Individual PRACH configurations may be at least partially based on a single-cell common PRACH configuration with an independent SSB-to-RO mapping for ROs falling within SBFD time slots. Furthermore, power control parameters for PRACHs in SBFD symbols may override power control parameters in conventional PRACH configurations.

[0121] In some respects, the PRACH configuration can be an SBFD-specific PRACH configuration for SBFD operation in the TDD band, where the RO within the SBFD downlink symbol or SBFD flexible symbol may be valid, and the RO within the uplink slot may be invalid (e.g., as...). Figures 10 to 11 (As shown). RO in the TDD flexible symbol may be valid. RO in the TDD uplink symbol may be valid. RO in both the uplink symbol and the flexible symbol may be valid.

[0122] In some respects, the UE can identify a conventional RO that overlaps with the SBFD RO in time, wherein the conventional RO can be associated with the temporal domain pattern of the conventional UE, and the SBFD RO can be associated with the temporal domain pattern of the SBFD-aware UE (e.g., as...). Figure 13 (As shown in the diagram). A conventional RO or SBFD RO can be considered a valid timing at least partially based on overlap. In some aspects, the UE can identify a conventional RO that overlaps with an SBFD RO in time rather than frequency, wherein the conventional RO can be associated with the time-domain pattern of the conventional UE, and the SBFD RO can be associated with the time-domain pattern of the SBFD-aware UE, and both the conventional RO and the SBFD RO can be considered valid RACH timings; the UE can avoid discarding the conventional RO and the SBFD RO at least partially based on overlap. The UE can discard the conventional RO or the SBFD RO at least partially based on overlap. The UE can apply a frequency offset to the SBFD RO. Furthermore, the SBFD RO or the SBFD time slot converted from the flexible time slot may be invalid.

[0123] In some aspects, the UE may receive from a network node a single PRACH configuration comprising a set of RACH opportunities (ROs) from both SBFD and non-SBFD symbols. The single PRACH configuration may indicate a BFR PRACH configuration, a system information request RACH configuration, and / or a UE-specific PRACH configuration. In some aspects, the UE may receive from a network node a first PRACH configuration comprising a set of RACH opportunities from TDD symbols used for legacy random access operations and a second PRACH configuration comprising a set of ROs from SBFD symbols used for SBFD random access operations. Each of the first and second PRACH configurations may indicate a common RACH configuration, a BFR RACH configuration, a system information RACH configuration, and / or a UE-specific RACH configuration.

[0124] As shown by reference numeral 806 in the attached figure, the UE can send signaling to the network node according to the random access procedure, at least in part, based on the PRACH configuration. The UE can use one or more parameters in the PRACH configuration to perform the random access procedure with the network node.

[0125] 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.

[0126] Figure 9 This is an illustration of example 900 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0127] Network nodes can send separate PRACH configurations for SBFD-aware UEs. As shown by reference numeral 902, a separate PRACH configuration can be a separate cell-wide PRACH configuration, such as the SBFD-wide PRACH configuration (e.g., ...). SBFD- PRACH-ConfigCommon or PRACH-ConfigCommon-r19 ). SBFD public PRACH configurations may have features such as those included in traditional cell public PRACH configurations (e.g., PRACH-ConfigCommon This refers to all parameters in the PRACH configuration that may have potentially different values. Validation rules may differ between individual PRACH configurations. For example, by... SBFD-PRACH-ConfigCommon The defined RO may only be valid within the SBFD slot. As indicated by reference numeral 904 in the attached figure, a separate PRACH configuration can be used. PRACH- ConfigCommon This refers to new structures with potentially more than one value for each or some of the parameters. Individual PRACH configurations can be new information elements (IEs) because traditional UEs may not be able to decode such new configurations. In some cases, individual PRACH configurations may include more than one general PRACH configuration (…). PRACH-ConfigGeneric) parameters, such as PRACH- ConfigGeneric and SBFD-PRACH-ConfigGeneric As shown by reference numeral 906 in the attached figure, a single PRACH configuration can be a single SSB-to-RO mapping with independent timing for falling into an SBFD slot. PRACH-ConfigGeneric SBFD-aware UEs can be scheduled using power control parameters for PRACH in the SBFD symbol, which override the power control in the common PRACH configuration.

[0128] In some respects, a separate PRACH configuration can be signaled to the SBFD-aware UE via an RRC message after an RRC connection is established, enabling random access for the RRC-connected UE in an SBFD symbol. Alternatively, a separate PRACH configuration can be signaled to the SBFD-aware UE via a SIB1 or SIBx message to additionally enable random access for RRC-idle / inactive UEs in an SBFD symbol.

[0129] 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.

[0130] In some respects, PRACH can be used to configure indexes ( prach-ConfigurationIndex The time resources of a RO are defined by a PRACH configuration index, which indicates the time resources of the selected RO (e.g., subframe number, number of PRACH slots per subframe, number of ROs per slot, and / or PRACH duration in symbols). Because the periodicity of ROs may not align with the periodicity of SBFD symbols, some ROs may not occur in SBFD symbols but may occur in non-SBFD symbols (e.g., uplink symbols or flexible symbols without uplink subbands). SBFD ROs occurring in non-SBFD symbols can be valid or invalid ROs.

[0131] In some respects, validity rules can be defined for SBFD-specific PRACH configurations, including SBFD-specific PRACH timing. For SBFD operations in TDD bands, the PRACH timing of the SBFD-specific PRACH configuration may be valid. In a first option, the PRACH timing of the SBFD-specific PRACH configuration may be valid only within SBFD downlink symbols and SBFD flexible symbols (e.g., as...). Figure 10(As shown). PRACH timings in non-SBFD symbols (e.g., uplink slots or flexible / downlink slots without uplink subbands) may not be valid PRACH timings. In the second option, PRACH timings in TDD flexible symbols may be valid, except that PRACH timings configured with SBFD-specific PRACH are valid within SBFD downlink and SBFD flexible symbols. In the third option, PRACH timings in TDD uplink symbols may be valid, except that PRACH timings configured with SBFD-specific PRACH are valid within SBFD downlink and SBFD flexible symbols. In the fourth option, PRACH timings in both uplink and flexible symbols may be valid, except that PRACH timings configured with SBFD-specific PRACH are valid within SBFD downlink and SBFD flexible symbols (e.g., as shown). Figure 11 (As shown).

[0132] Figure 10 This is a diagram illustrating an example 1000 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0133] like Figure 10 As shown, ROs may only be valid within SBFD symbols. The XXXSUXXXUU format may be at least partially based on the DDDSUDDSUU slot format (in which all DL symbols are SBFD symbols). The PRACH configuration may be at least partially based on a long PRACH sequence (e.g., format 0 with a 1ms sequence). ROs may occur in subframes 0, 4, 5, and 9 of a frame used for SBFD-specific PRACH configurations. Subframe 0, which can be associated with an SBFD symbol, may be associated with the first RO 1002 (RO #0). Subframe 4, which can be associated with an uplink symbol, may be associated with an invalid RO. Subframe 5, which can be associated with an SBFD symbol, may be associated with the second RO 1004 (RO #1). Subframe 9, which can be associated with an uplink symbol, may be associated with an invalid RO. Therefore, ROs in uplink symbols / slots can be invalid ROs.

[0134] 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.

[0135] Figure 11 This is an illustration of example 1100 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0136] like Figure 11As shown, ROs may be valid in both SBFD symbols and uplink symbols. The XXXSUXXXUU format may be at least partially based on the DDDSUDDSUU slot format (in which all DL symbols are SBFD symbols). The PRACH configuration may be at least partially based on a long PRACH sequence (e.g., format 0 with a 1ms sequence). ROs may occur in subframes 0, 4, 5, and 9 of a frame used for SBFD-specific PRACH configurations. Subframe 0, which can be associated with an SBFD symbol, may be associated with the first RO 1102 (RO #0). Subframe 4, which can be associated with an uplink symbol, may be associated with the second RO 1104 (RO #1). Subframe 5, which can be associated with an SBFD symbol, may be associated with the third RO 1106 (RO #2). Subframe 9, which can be associated with an uplink symbol, may be associated with the fourth RO 1108 (RO #3).

[0137] 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.

[0138] Figure 12 This is an illustration of Example 1200 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0139] like Figure 12 As shown, a time-domain mode for a traditional UE 1202 can be defined. Time-domain mode 1202 can be associated with downlink time slots, flexible time slots, and uplink time slots. A time-domain mode for an SBFD-aware UE 1204 can be defined. Time-domain mode 1204 can be associated with downlink time slots, SBFD time slots, flexible time slots, and uplink time slots. When an RO falls within a downlink time slot, the RO may be invalid for a traditional UE, but it may be valid for an SBFD-aware UE. Valid ROs for SBFD-aware UEs that are invalid for traditional UEs can be independently mapped to an SSB according to the traditional mapping.

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

[0141] Figure 13 This is an illustration of Example 1300 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0142] In some respects, traditional ROs may overlap with SBFD-aware ROs. Rules can be defined for SBFD-aware UEs. When a traditional RO overlaps with an SBFD RO in time (or within a specific duration), any PRACH in the PRACH can be discarded or one of the ROs can be considered an invalid RO, which can be at least partially based on specifications or signaled in system information. When a traditional RO overlaps with an SBFD RO in time but is separated from it in the frequency domain, the SBFD-dedicated RO can be considered valid, and no RO can be discarded. Otherwise, one of the ROs can be discarded, or a frequency offset can be applied to the SBFD RO. SBFD-aware UEs can check the validity of traditional ROs and then check the validity of SBFD-aware ROs. In some cases, overlap can be avoided by invalidating all ROs in the flexible time slot converted to SBFD time slots, leaving only the downlink time slots converted to SBFD time slots. In some respects, SBFD ROs in flexible time slots or SBFD time slots converted from flexible time slots may be invalid.

[0143] like Figure 13 As shown, overlap can occur between conventional RO 1304 and SBFD RO 1308. The time-domain mode of conventional UE 1302 can be associated with conventional RO 1304. The time-domain mode of SBFD-aware UE 1306 can be associated with SBFD RO 1308. Conventional RO 1304 occurring within the downlink timeslot of the time-domain mode of conventional UE 1302 may be invalid. SBFD RO 1308 occurring within the downlink timeslot of the time-domain mode of SBFD-aware UE 1306 may be invalid. Conventional RO 1304 occurring within the flexible timeslot of the time-domain mode of conventional UE 1302 may not overlap with SBFD RO 1308 occurring within the flexible timeslot of the time-domain mode of SBFD-aware UE 1306. Conventional RO 1304 occurring in the uplink timeslot of the time-domain mode of conventional UE 1302 may overlap temporally with SBFD RO 1308 occurring in the uplink timeslot of the time-domain mode of SBFD-aware UE 1306, but such ROs may not overlap in frequency and therefore may not be dropped.

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

[0145] In some respects, multiple PRACH configurations can be signaled to the UE for different random access triggered events (e.g., BFR, handover, or system information request). This can be achieved using... PRACH-ConfigCommon , PRACH-ConfigBFR , PRACH- ConfigSI and / or PRACH-ConfigDedicated One or two configuration sets are used to configure / instruct the UE, one configuration set for traditional operation and another configuration set for SBFD-aware RO. When not configured... PRACH-ConfigBFR At that time, the UE can use PRACH-ConfigCommon .

[0146] Figure 14 This is an illustration of Example 1400 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0147] As shown by reference numeral 1402 in the attached figure, when the UE has two PRACH ConfigCommon Configuration (e.g., PRACH- ConfigCommon and SBFD-PRACH-ConfigCommon (or PRACH-ConfigCommon-r19 And it is only available for traditional UEs. PRACH-ConfigBFR , PRACH-ConfigSI and / or PRACH-ConfigDedicated At this time, the UE can use only the traditional UE-specific configuration. PRACH-ConfigBFR , PRACH-ConfigSI and / or PRACH-ConfigDedicated As shown by reference numeral 1404 in the attached figure, when the UE has two ConfigCommon Configuration (e.g., PRACH-ConfigCommon and SBFD- PRACH-ConfigCommon And only traditional services are available. PRACH-ConfigBFR , PRACH-ConfigSI and / or PRACH- ConfigDedicated At this time, the UE can use the provided legacy configuration and SBFD. ConfigCommon Configuration.

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

[0149] Figure 15 This is an illustration of Example 1500 associated with a PRACH configuration for full-duplex symbols according to this disclosure.

[0150] As shown by reference numeral 1502 in the attached figure, when the UE has two ConfigCommon Configuration (e.g., PRACH- ConfigCommon and SBFD-PRACH-ConfigCommon (or PRACH-ConfigCommon-r19 And no PRACH-ConfigBFR , PRACH-ConfigSI and / or PRACH-ConfigDedicated At that time, the UE can only use the traditional ConfigCommonConfigurations are used for BFR, system information, and / or dedicated configurations. As shown by reference numeral 1504 in the attached figure, when the UE has two... ConfigCommon Configuration (e.g., PRACH-ConfigCommon and SBFD-PRACH-ConfigCommon (or PRACH- ConfigCommon-r19 And no PRACH-ConfigBFR , PRACH-ConfigSI and / or PRACH- ConfigDedicated At that time, the UE can use traditional ConfigCommon Configuration and SBFD ConfigCommon Both configurations are used for BFR, system information, and / or dedicated configurations.

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

[0152] Figure 16 This is a diagram illustrating an example process 1600 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1600 is an example of an operation performed by a device or UE (e.g., UE 120) associated with PRACH configuration for full-duplex symbols.

[0153] like Figure 16 As shown, in some aspects, procedure 1600 may include receiving PRACH configuration (block 1610) for a random access procedure in an SBFD symbol. For example, the UE (e.g., using...) Figure 18 The receiving component 1802 and / or communication manager 1806 depicted herein can receive PRACH configurations for random access procedures in SBFD symbols, as described above.

[0154] like Figure 16 As further shown, in some aspects, process 1600 may include: sending signaling according to a random access procedure, at least in part based on a PRACH configuration (box 1620). For example, the UE (e.g., using...) Figure 18 The transmitting component 1804 and / or the communication manager 1806 described herein may transmit signaling according to a random access procedure, at least in part, based on a PRACH configuration, as described above.

[0155] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0156] In a first aspect, process 1600 includes: transmitting capability signaling indicating that the UE is an SBFD-aware UE, wherein the PRACH configuration is received at least in part based on the capability signaling.

[0157] In the second aspect, either alone or in combination with the first aspect, the PRACH configuration is an SBFD-specific PRACH configuration, and the SBFD-specific PRACH configuration is based at least in part on: a TDD FR1 / 2 random access table, which includes one or more PRACH configurations to allow one or more subframe configurations specific to the SBFD symbol; a random access table for SBFD, which is separate from the TDD FR1 / 2 random access table and the FDD FR1 / 2 random access table; or an FDD FR1 / 2 random access table.

[0158] In the third aspect, either alone or in combination with one or more of the first and second aspects, the PRACH configuration is a separate cell-specific PRACH configuration dedicated to SBFD-aware UEs and separate from the traditional cell-specific PRACH configuration, and the separate PRACH configuration is based at least in part on: a separate cell-common PRACH configuration compared to the traditional PRACH configuration; a single cell-common PRACH configuration having a modified structure to support more than one value for one or more parameters, and the cell-common PRACH configuration includes more than one general PRACH configuration parameter; or a single cell-common PRACH configuration having an independent SSB-to-RO mapping for ROs falling within the SBFD time slot, wherein the power control parameters for PRACH in the SBFD symbol override the power control parameters in the traditional PRACH configuration.

[0159] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1600 includes receiving PRACH configuration via RRC signaling or via a System Information Block (SIB).

[0160] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the PRACH configuration is an SBFD-specific PRACH configuration for SBFD operation in the TDD band, where the RO within the SBFD downlink symbol or SBFD flexible symbol is valid and the RO within the uplink time slot is invalid.

[0161] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the RO in the TDD flexible symbol is valid, the RO in the TDD uplink symbol is valid, or the RO in the uplink symbol and the flexible symbol is valid.

[0162] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1600 includes: identifying a conventional RO that overlaps with the SBFD RO in time, wherein the conventional RO is associated with a temporal pattern of a conventional UE and the SBFD RO is associated with a temporal pattern of an SBFD-aware UE, and the conventional RO or the SBFD RO is considered to be a valid timing at least in part based on the overlap.

[0163] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1600 includes: identifying a conventional RO that overlaps with the SBFD RO in time rather than in frequency, wherein the conventional RO is associated with a time-domain mode of a conventional UE and the SBFD RO is associated with a time-domain mode of an SBFD-aware UE, and both the conventional RO and the SBFD RO are considered to be valid RACH timings; and avoiding dropping the conventional RO and the SBFD RO, dropping the conventional RO or the SBFD RO, or applying a frequency offset to the SBFD RO, at least in part based on the overlap.

[0164] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the SBFD RO or the SBFD slot converted from the flexible slot is invalid.

[0165] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1600 includes: receiving a single PRACH configuration comprising a set of RACH timings (ROs) in both SBFD symbols and non-SBFD symbols, wherein the single PRACH configuration indicates one or more of the following: beam fault recovery (BFR) RACH configuration, system information request RACH configuration, or UE-specific PRACH configuration; or receiving a first PRACH configuration comprising a set of RACH timings in TDD symbols for legacy random access operations and a second PRACH configuration comprising a set of ROs in SBFD symbols for SBFD random access operations, wherein each of the first PRACH configuration and the second PRACH configuration indicates one or more of the following: public RACH configuration, BFR RACH configuration, system information RACH configuration, or UE-specific RACH configuration.

[0166] although Figure 16 An example box of process 1600 is shown, but in some respects, process 1600 may include... Figure 16 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 1600 may be executed in parallel.

[0167] Figure 17 This is a diagram illustrating an example process 1700 performed, for example, at a network node or a device of a network node according to the present disclosure. Example process 1700 is an example in which a device or network node (e.g., network node 110) performs operations associated with PRACH configuration for full-duplex symbols.

[0168] like Figure 17 As shown, in some aspects, process 1700 may include sending PRACH configuration (box 1710) for a random access procedure in an SBFD symbol. For example, a network node (e.g., using...) Figure 19 The transmitting component 1904 and / or the communication manager 1906 depicted can transmit PRACH configurations for random access procedures in SBFD symbols, as described above.

[0169] like Figure 17 As further shown, in some aspects, process 1700 may include: receiving signaling according to a random access procedure, at least in part based on a PRACH configuration (box 1720). For example, a network node (e.g., using...) Figure 19 The described receiving component 1902 and / or communication manager 1906 can receive signaling according to a random access procedure, at least in part, based on a PRACH configuration, as described above.

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

[0171] In a first aspect, process 1700 includes: receiving capability signaling indicating that the UE is an SBFD-aware UE, wherein the PRACH configuration is transmitted at least in part based on the capability signaling.

[0172] In the second aspect, either alone or in combination with the first aspect, the PRACH configuration is an SBFD-specific PRACH configuration, and the SBFD-specific PRACH configuration is based at least in part on: a TDD FR1 / 2 random access table, which includes one or more PRACH configurations to allow one or more subframe configurations specific to the SBFD symbol; a random access table for SBFD, which is separate from the TDD FR1 / 2 random access table and the FDD FR1 / 2 random access table; or an FDD FR1 / 2 random access table.

[0173] In the third aspect, either alone or in combination with one or more of the first and second aspects, the PRACH configuration is a separate cell-specific PRACH configuration dedicated to SBFD-aware UEs and separate from the traditional cell-specific PRACH configuration, and the separate PRACH configuration is based at least in part on: a separate cell-common PRACH configuration compared to the traditional PRACH configuration; a single cell-common PRACH configuration having a modified structure to support more than one value for one or more parameters, and the cell-common PRACH configuration includes more than one general PRACH configuration parameter; or a single cell-common PRACH configuration having an independent SSB-to-RO mapping for ROs falling within the SBFD time slot, wherein the power control parameters for PRACH in the SBFD symbol override the power control parameters in the traditional PRACH configuration.

[0174] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1700 includes sending PRACH configuration via RRC signaling or via SIB.

[0175] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the PRACH configuration is an SBFD-specific PRACH configuration for SBFD operation in the TDD band, where the RO within the SBFD downlink symbol or SBFD flexible symbol is valid and the RO within the uplink time slot is invalid.

[0176] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the RO in the TDD flexible symbol is valid, the RO in the TDD uplink symbol is valid, or the RO in the uplink symbol and the flexible symbol is valid.

[0177] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1700 includes: transmitting a single PRACH configuration comprising a set of RACH timings (ROs) in both SBFD symbols and non-SBFD symbols, wherein the single PRACH configuration indicates one or more of the following: a beam fault recovery (BFR) RACH configuration, a system information request RACH configuration, or a UE-specific PRACH configuration; or transmitting a first PRACH configuration comprising a set of RACH timings in TDD symbols for legacy random access operations and a second PRACH configuration comprising a set of ROs in SBFD symbols for SBFD random access operations, wherein each of the first PRACH configuration and the second PRACH configuration indicates one or more of the following: a public RACH configuration, a BFR RACH configuration, a system information RACH configuration, or a UE-specific RACH configuration.

[0178] although Figure 17 An example box of process 1700 is shown, but in some respects, process 1700 may include... Figure 17 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 1700 may be executed in parallel.

[0179] Figure 18 This is a diagram of an example device 1800 for wireless communication according to the present disclosure. Device 1800 may be a UE, or a UE may include device 1800. In some aspects, device 1800 includes a receiving component 1802, a transmitting component 1804, and / or a communication manager 1806, which can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1806 is combined with... Figure 1 The described communication manager 140. As shown, device 1800 can use receiving component 1802 and transmitting component 1804 to communicate with another device 1808 (such as UE or network node (such as CU, DU, RU or base station)).

[0180] In some respects, device 1800 can be configured to perform the functions described herein. Figures 8 to 15 One or more operations described herein. Additionally or alternatively, the apparatus 1800 may be configured to perform one or more processes described herein (such as...). Figure 16 The process 1600) or a combination thereof. In some respects, Figure 18 The illustrated device 1800 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 18One 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.

[0181] Receiver 1802 may receive communications from device 1808, such as reference signals, control information, data communications, or combinations thereof. Receiver 1802 may provide the received communications to one or more other components of device 1800. In some aspects, receiver 1802 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 1800. In some aspects, receiver 1802 may include combinations of... Figure 2 The 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.

[0182] Transmitting component 1804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1808. In some aspects, one or more other components of device 1800 may generate communications and provide the generated communications to transmitting component 1804 for transmission to device 1808. In some aspects, transmitting component 1804 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 1808. In some aspects, transmitting component 1804 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 1804 may co-located with the receive component 1802 in one or more transceivers.

[0183] The communication manager 1806 may support the operation of the receiving component 1802 and / or the transmitting component 1804. For example, the communication manager 1806 may receive information associated with configuring the reception of communications by the receiving component 1802 and / or the transmission of communications by the transmitting component 1804. Additionally or alternatively, the communication manager 1806 may generate control information and / or provide such control information to the receiving component 1802 and / or the transmitting component 1804 to control the reception and / or transmission of communications.

[0184] The receiving component 1802 can receive the PRACH configuration for the random access procedure in an SBFD symbol. The transmitting component 1804 can transmit signaling according to the random access procedure, at least in part, based on the PRACH configuration.

[0185] Transmitting component 1804 can transmit capability signaling indicating that the UE is an SBFD-aware UE, wherein the PRACH configuration is received at least in part based on the capability signaling. Communication manager 1806 can identify a legacy RO that overlaps with an SBFD RO in time, wherein the legacy RO is associated with the time-domain mode of a legacy UE, and the SBFD RO is associated with the time-domain mode of an SBFD-aware UE. Communication manager 1806 can discard a legacy RO or an SBFD RO at least in part based on the overlap. Communication manager 1806 can identify a legacy RO that overlaps with an SBFD RO in time but not in frequency, wherein the legacy RO is associated with the time-domain mode of a legacy UE, and the SBFD RO is associated with the time-domain mode of an SBFD-aware UE.

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

[0187] Figure 19This is a diagram of an example device 1900 for wireless communication according to the present disclosure. Device 1900 may be a network node, or a network node may include device 1900. In some aspects, device 1900 includes a receiving component 1902, a transmitting component 1904, and / or a communication manager 1906, which can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1906 is combined with... Figure 1 The described communication manager 150. As shown, device 1900 can use receiving component 1902 and transmitting component 1904 to communicate with another device 1908 (such as UE or network node (such as CU, DU, RU or base station)).

[0188] In some respects, device 1900 can be configured to perform the functions described herein. Figures 8 to 15 One or more operations described herein. Additionally or alternatively, the apparatus 1900 may be configured to perform one or more processes described herein (such as...). Figure 17 The process 1700) or a combination thereof. In some respects, Figure 19 The illustrated device 1900 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 19 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.

[0189] Receiver 1902 may receive communications from device 1908, such as reference signals, control information, data communications, or combinations thereof. Receiver 1902 may provide the received communications to one or more other components of device 1900. In some aspects, receiver 1902 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 1900. In some aspects, receiver 1902 may include combinations of... Figure 2The described network node may include 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 1902 and / or transmitter component 1904 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1900 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0190] Transmitting component 1904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1908. In some aspects, one or more other components of device 1900 may generate communications and provide the generated communications to transmitting component 1904 for transmission to device 1908. In some aspects, transmitting component 1904 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 1908. In some aspects, transmitting component 1904 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 1904 may co-located with the receive component 1902 in one or more transceivers.

[0191] The communication manager 1906 may support the operation of the receiving component 1902 and / or the transmitting component 1904. For example, the communication manager 1906 may receive information associated with configuring the reception of communications by the receiving component 1902 and / or the transmission of communications by the transmitting component 1904. Additionally or alternatively, the communication manager 1906 may generate control information and / or provide such control information to the receiving component 1902 and / or the transmitting component 1904 to control the reception and / or transmission of communications.

[0192] Transmitting component 1904 can transmit PRACH configuration for random access procedures in SBFD symbols. Receiving component 1902 can receive signaling according to the random access procedures, at least in part, based on the PRACH configuration.

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

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

[0195] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a physical random access channel (PRACH) configuration for a random access procedure in a subband full-duplex (SBFD) symbol; and transmitting signaling according to the random access procedure based at least in part on the PRACH configuration.

[0196] Aspect 2: According to the method of aspect 1, the method further includes: sending capability signaling indicating that the UE is an SBFD-aware UE, wherein the PRACH configuration is received at least in part based on the capability signaling.

[0197] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the PRACH configuration is an SBFD-specific PRACH configuration, and the SBFD-specific PRACH configuration is based at least in part on: a Time Division Duplex (TDD) Frequency Range ½ (FR1 / 2) random access table, the TDD Frequency Range ½ (FR1 / 2) random access table including one or more PRACH configurations to allow one or more subframe configurations specific to SBFD; a random access table for SBFD, the random access table for SBFD being separate from the TDD FR1 / 2 random access table and the Frequency Division Duplex (FDD) FR1 / 2 random access table; or the FDD FR1 / 2 random access table.

[0198] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the PRACH configuration is a separate cell-specific PRACH configuration dedicated to SBFD-aware UEs and separate from conventional cell-specific PRACH configurations, and the separate PRACH configuration is based at least in part on: a separate cell-common PRACH configuration compared to conventional PRACH configurations; a single cell-common PRACH configuration having a modified structure to support more than one value for one or more parameters, and the single cell-common PRACH configuration including more than one general PRACH configuration parameter; or a single cell-common PRACH configuration having an independent synchronization signal block (SSB) to RO mapping for PRACH timing (RO) falling within SBFD time slots, wherein the power control parameters for PRACH in SBFD symbols cover the power control parameters in conventional PRACH configurations.

[0199] Aspect 5: The method according to any one of Aspects 1 to 4, wherein receiving the PRACH configuration comprises receiving the PRACH configuration via Radio Resource Control (RRC) signaling or via System Information Block (SIB).

[0200] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the PRACH configuration is an SBFD-specific PRACH configuration for SBFD operation in a time division duplex (TDD) band, wherein the random access channel (RACH) timing (RO) within the SBFD downlink symbol or the SBFD flexible symbol is valid, and the RO within the uplink timeslot is invalid.

[0201] Aspect 7: According to the method described in aspect 6, wherein: the RO in the TDD flexible symbol is valid, the RO in the TDD uplink symbol is valid, or the RO in the uplink symbol and the flexible symbol is valid.

[0202] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: identifying a conventional RO that overlaps temporally with an SBFD random access channel (RACH) timing (RO), wherein the conventional RO is associated with a temporal pattern of a conventional UE, and the SBFD RO is associated with a temporal pattern of an SBFD-aware UE, and the conventional RO or the SBFD RO is considered a valid timing at least in part based on the overlap.

[0203] Aspect 9: The method according to any one of Aspects 1 to 8, further comprising: identifying a conventional RO that overlaps with an SBFD random access channel (RACH) timing (RO) in time rather than in frequency, wherein the conventional RO is associated with a time-domain mode of a conventional UE and the SBFD RO is associated with a time-domain mode of an SBFD-aware UE, and both the conventional RO and the SBFD RO are considered valid RACH timings; and avoiding dropping the conventional RO and the SBFD RO, dropping the conventional RO or the SBFD RO, or applying a frequency offset to the SBFD RO, at least in part based on the overlap.

[0204] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the SBFD random access channel (RACH) timing (RO) or the SBFD time slot converted from the flexible time slot is invalid.

[0205] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: receiving a single PRACH configuration including a set of RACH timings (ROs) in both SBFD symbols and non-SBFD symbols, wherein the single PRACH configuration indicates one or more of the following: a beam fault recovery (BFR) RACH configuration, a system information request RACH configuration, or a UE-specific PRACH configuration; or receiving a first PRACH configuration including a set of RACH timings in TDD symbols for legacy random access operations and a second PRACH configuration including a set of ROs in SBFD symbols for SBFD random access operations, wherein each of the first PRACH configuration and the second PRACH configuration indicates one or more of the following: a public RACH configuration, a BFR RACH configuration, a system information RACH configuration, or a UE-specific RACH configuration.

[0206] Aspect 12: A method of wireless communication performed by a network node, the method comprising: transmitting a Physical Random Access Channel (PRACH) configuration for a random access procedure in a subband full-duplex (SBFD) symbol; and receiving signaling according to the random access procedure based at least in part on the PRACH configuration.

[0207] Aspect 13: The method according to aspect 12, the method further comprising: receiving capability signaling indicating that a user equipment (UE) is an SBFD-aware UE, wherein the PRACH configuration is transmitted at least in part based on the capability signaling.

[0208] Aspect 14: The method according to any one of Aspects 12 to 13, wherein the PRACH configuration is an SBFD-specific PRACH configuration, and the SBFD-specific PRACH configuration is based at least in part on: a Time Division Duplex (TDD) Frequency Range ½ (FR1 / 2) random access table, the TDD Frequency Range ½ (FR1 / 2) random access table including one or more PRACH configurations to allow one or more subframe configurations specific to SBFD; a random access table for SBFD, the random access table for SBFD being separate from the TDD FR1 / 2 random access table and the Frequency Division Duplex (FDD) FR1 / 2 random access table; or the FDD FR1 / 2 random access table.

[0209] Aspect 15: The method according to any one of Aspects 12 to 14, wherein the PRACH configuration is a separate cell-specific PRACH configuration dedicated to SBFD-aware UEs and separate from conventional cell-specific PRACH configurations, and the separate PRACH configuration is based at least in part on: a separate cell-common PRACH configuration compared to conventional PRACH configurations; a single cell-common PRACH configuration having a modified structure to support more than one value for one or more parameters, and the single cell-common PRACH configuration including more than one general PRACH configuration parameter; or a single cell-common PRACH configuration having an independent synchronization signal block (SSB) to RO mapping for PRACH timing (RO) falling within an SBFD time slot, wherein the power control parameters for PRACH in SBFD symbols override the power control parameters in conventional PRACH configurations.

[0210] Aspect 16: The method according to any one of Aspects 12 to 15, wherein transmitting the PRACH configuration comprises transmitting the PRACH configuration via Radio Resource Control (RRC) signaling or via System Information Block (SIB).

[0211] Aspect 17: The method according to any one of Aspects 12 to 16, wherein the PRACH configuration is an SBFD-specific PRACH configuration for SBFD operation in a time division duplex (TDD) band, wherein the random access channel (RACH) timing (RO) within the SBFD downlink symbol or the SBFD flexible symbol is valid, and the RO within the uplink timeslot is invalid.

[0212] Aspect 18: The method according to aspect 17, wherein: the RO in the TDD flexible symbol is valid, the RO in the TDD uplink symbol is valid, or the RO in the uplink symbol and the flexible symbol is valid.

[0213] Aspect 19: The method according to any one of Aspects 12 to 18, the method further comprising: transmitting a single PRACH configuration including a set of RACH timings (ROs) in both SBFD symbols and non-SBFD symbols, wherein the single PRACH configuration indicates one or more of the following: a beam fault recovery (BFR) RACH configuration, a system information request RACH configuration, or a UE-specific PRACH configuration; or transmitting a first PRACH configuration including a set of RACH timings in TDD symbols for legacy random access operations and a second PRACH configuration including a set of ROs in SBFD symbols for SBFD random access operations, wherein each of the first PRACH configuration and the second PRACH configuration indicates one or more of the following: a public RACH configuration, a BFR RACH configuration, a system information RACH configuration, or a UE-specific RACH configuration.

[0214] Aspect 20: 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 11.

[0215] Aspect 21: 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 11.

[0216] Aspect 22: 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 11.

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

[0218] Aspect 24: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, 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 11.

[0219] Aspect 25: A device for wireless communication, the device including a processing system comprising 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 11.

[0220] Aspect 26: 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 11.

[0221] 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 12 to 19.

[0222] 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 12 to 19.

[0223] 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 12 to 19.

[0224] 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 12 to 19.

[0225] 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 that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 12 to 19.

[0226] Aspect 32: A device for wireless communication, the device including a processing system comprising 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 12 to 19.

[0227] 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 12 to 19.

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

[0229] 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.

[0230] 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.

[0231] As used in this article, the phrase “at least one of” in a list of items refers to any combination of those 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).

[0232] 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 used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are used interchangeably 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”.

[0233] 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 at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the UE to: Receive the Physical Random Access Channel (PRACH) configuration for the random access procedure in sub-band full-duplex (SBFD) symbols; and Signaling is sent according to the random access procedure, at least in part based on the PRACH configuration.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Send capability signaling indicating that the UE is an SBFD-aware UE, wherein the PRACH configuration is received at least in part based on the capability signaling.

3. The apparatus of claim 1, wherein the PRACH configuration is an SBFD-specific PRACH configuration, and the SBFD-specific PRACH configuration is based at least in part on: A Time Division Duplex (TDD) Frequency Range ½ (FR1 / 2) Random Access Table, comprising one or more PRACH configurations to allow specific subframe configurations within an SBFD symbol. The random access table used for SBFD is separate from the TDD FR1 / 2 random access table and the Frequency Division Duplex (FDD) FR1 / 2 random access table, or The FDD FR1 / 2 random access table.

4. The apparatus of claim 1, wherein the PRACH configuration is a separate cell-specific PRACH configuration dedicated to SBFD-aware UEs and separate from traditional cell-specific PRACH configurations, and the separate PRACH configuration is based at least in part on: Compared to traditional community public PRACH configurations, separate community public PRACH configurations... A single-cell public PRACH configuration, the single-cell public PRACH configuration having a modified structure to support more than one value for one or more parameters, and the single-cell public PRACH configuration including more than one general PRACH configuration parameter, or A single-cell public PRACH configuration, wherein the single-cell public PRACH configuration has an independent synchronization signal block (SSB) to RO mapping for PRACH timings (ROs) falling within the SBFD time slot. The power control parameters used for PRACH in the SBFD symbol override the power control parameters in the conventional PRACH configuration.

5. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: The PRACH configuration is received via Radio Resource Control (RRC) signaling or via System Information Block (SIB).

6. The apparatus of claim 1, wherein the PRACH configuration is an SBFD-specific PRACH configuration for SBFD operation in a time division duplex (TDD) band, wherein the random access channel (RACH) timing (RO) within the SBFD downlink symbol or the SBFD flexible symbol is active, and the RO within the uplink timeslot is inactive.

7. The apparatus according to claim 6, wherein: RO is valid in the flexible notation of TDD. The RO in the TDD uplink symbol is valid, or RO is valid in both the uplink symbol and the flexible symbol.

8. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: A conventional RO is identified that overlaps with an SBFD random access channel (RACH) timing (RO) in time, wherein the conventional RO is associated with a time-domain mode of a conventional UE and the SBFD RO is associated with a time-domain mode of an SBFD-aware UE, and the conventional RO or the SBFD RO is considered a valid timing at least in part based on the overlap.

9. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Identify the conventional RO that overlaps with the SBFD Random Access Channel (RACH) timing (RO) in time rather than frequency, wherein the conventional RO is associated with the time-domain mode of the conventional UE, and the SBFD RO is associated with the time-domain mode of the SBFD-aware UE, and both the conventional RO and the SBFD RO are considered valid RACH timings; and The traditional RO and the SBFD RO are avoided at least in part based on the overlap, the traditional RO or the SBFD RO is discarded at least in part based on the overlap, or a frequency offset is applied to the SBFD RO.

10. The apparatus of claim 1, wherein the SBFD random access channel (RACH) timing (RO) or the SBFD time slot converted from the flexible time slot is invalid.

11. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: Receive a single PRACH configuration that includes a set of Random Access Channel (RACH) opportunities (RO) from both SBFD symbols and non-SBFD symbols, wherein the single PRACH configuration indicates one or more of the following: Beam Failure Recovery (BFR) RACH configuration, System Information Request RACH configuration, or UE-specific PRACH configuration; or Receive a first PRACH configuration including a set of RACH timings in TDD symbols for conventional random access operations and a second PRACH configuration including a set of ROs in SBFD symbols for SBFD random access operations, wherein each of the first PRACH configuration and the second PRACH configuration indicates one or more of the following: a public RACH configuration, a BFR RACH configuration, a system information RACH configuration, or a private RACH configuration.

12. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Transmit the Physical Random Access Channel (PRACH) configuration for the random access procedure in sub-band full-duplex (SBFD) symbols; and Signaling is received according to the random access procedure, at least in part based on the PRACH configuration.

13. The apparatus of claim 12, wherein the one or more processors are further configured to cause the network node to: The received indication user equipment (UE) is SBFD-aware UE capability signaling, wherein the PRACH configuration is transmitted at least in part based on the capability signaling.

14. The apparatus of claim 12, wherein the PRACH configuration is an SBFD-specific PRACH configuration, and the SBFD-specific PRACH configuration is based at least in part on: A Time Division Duplex (TDD) Frequency Range 1 / 2 (FR1 / 2) random access table, which includes one or more PRACH configurations to allow specific configurations of one or more subframes within an SBFD symbol. The random access table used for SBFD is separate from the TDD FR1 / 2 random access table and the Frequency Division Duplex (FDD) FR1 / 2 random access table, or The FDD FR1 / 2 random access table.

15. The apparatus of claim 12, wherein the PRACH configuration is a separate cell-specific PRACH configuration dedicated to SBFD-aware user equipment (UE) and separate from traditional cell-specific PRACH configurations, and the separate PRACH configuration is based at least in part on: Compared to traditional community public PRACH configurations, separate community public PRACH configurations... A single-cell public PRACH configuration, the single-cell public PRACH configuration having a modified structure to support more than one value for one or more parameters, and the single-cell public PRACH configuration including more than one general PRACH configuration parameter, or A single-cell public PRACH configuration, wherein the single-cell public PRACH configuration has an independent synchronization signal block (SSB) to RO mapping for PRACH timings (ROs) falling within the SBFD time slot. The power control parameters used for PRACH in the SBFD symbol override the power control parameters in the conventional PRACH configuration.

16. The apparatus of claim 12, wherein the one or more processors are further configured to cause the network node to: The PRACH configuration is transmitted via Radio Resource Control (RRC) signaling or via System Information Block (SIB).

17. The apparatus of claim 12, wherein the PRACH configuration is an SBFD-specific PRACH configuration for SBFD operation in a time-division duplex (TDD) band, wherein the random access channel (RACH) timing (RO) within the SBFD downlink symbol or the SBFD flexible symbol is active, and the RO within the uplink timeslot is inactive.

18. The apparatus according to claim 17, wherein: RO is valid in the flexible notation of TDD. The RO in the TDD uplink symbol is valid, or RO is valid in both the uplink symbol and the flexible symbol.

19. The apparatus of claim 12, wherein the one or more processors are further configured to cause the network node to: Transmit a single PRACH configuration that includes a set of Random Access Channel (RACH) opportunities (ROs) from both SBFD and non-SBFD symbols, wherein the single PRACH configuration indicates one or more of the following: Beam Failure Recovery (BFR) RACH configuration, System Information Request RACH configuration, or UE-specific PRACH configuration; or Transmit a first PRACH configuration comprising a set of RACH timings in TDD symbols for conventional random access operations and a second PRACH configuration comprising a set of ROs in SBFD symbols for SBFD random access operations, wherein each of the first PRACH configuration and the second PRACH configuration indicates one or more of the following: a public RACH configuration, a BFR RACH configuration, a system information RACH configuration, or a private RACH configuration.

20. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive the Physical Random Access Channel (PRACH) configuration for the random access procedure in sub-band full-duplex (SBFD) symbols; as well as Signaling is sent according to the random access procedure, at least in part based on the PRACH configuration.

Images