System information (SI) request via a subband full-duplex (SBFD) random access channel (RACK) occasion

Abstract

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for requesting system information. One aspect provides a method for wireless communications at a user equipment (UE). The method includes receiving at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; and transmitting a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot.

Description

SYSTEM INFORMATION (SI) REQUEST VIA A SUBBAND FULL-DUPLEX (SBFD) RANDOM ACCESS CHANNEL (RACH) OCCASION CROSS-REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims priority to U.S. Patent Application No. 18 / 922,121, filed October 21, 2024, which is hereby incorporated by reference herein.Field of the Disclosure

[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for requesting system information.Description of Related Art

[0003] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.

[0004] Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists a need for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.SUMMARY

[0005] One aspect provides a method for wireless communications at a user equipment (UE). The method includes receiving at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; and transmitting a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot.

[0006] Another aspect provides a method for wireless communications at a network entity. The method includes transmitting at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; and receiving a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot.

[0007] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and / or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed (e.g., directly, indirectly, after pre-processing, without pre-processing) by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and / or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.

[0008] The following description and the appended figures set forth certain features for purposes of illustration.BRIEF DESCRIPTION OF DRAWINGS

[0009] The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.

[0010] FIG. 1 depicts an example wireless communications network.

[0011] FIG. 2 depicts an example disaggregated base station architecture.

[0012] FIG. 3 depicts aspects of an example base station and an example user equipment.

[0013] FIGS. 4A, 4B, 4C, and 4D depict various example aspects of data structures for a wireless communications network.

[0014] FIGs. 5A, 5B, and 5C depict various examples of full duplex (FD) time / frequency resource configurations.

[0015] FIGs. 6A, 6B, and 6C depict various examples of full duplex configurations.

[0016] FIGs. 7A and 7B depict an example of inter-UE cross link interference (CLI).

[0017] FIG. 8 depicts an example of an FD base station performing simultaneous transmission and reception.

[0018] FIGs. 9A and 9B depict example uplink and downlink subbands for subband FD (SBFD) operations.

[0019] FIG. 10 depicts a call flow diagram illustrating a 4-step random access channel (RACH) procedure.

[0020] FIG. 11 depicts a call flow diagram illustrating techniques for requesting system information (SI).

[0021] FIG. 12 illustrates an SI request configuration information element (IE).

[0022] FIG. 13 illustrating SI scheduling information.

[0023] FIG. 14 illustrates example SI scheduling information that may include scheduling information for subband full-duplex (SBFD)-aware user equipments (UEs), in accordance with certain aspects of the present disclosure.

[0024] FIG. 15 illustrates example SI scheduling information that may include SI request resources for SBFD-aware UEs, in accordance with certain aspects of the present disclosure.

[0025] FIG. 16 illustrates example SI scheduling information that may include scheduling information and SI request resources for SBFD-aware UEs, in accordance with certain aspects of the present disclosure.

[0026] FIG. 17 is a diagram illustrating example techniques for preamble partitioning between time-divisions duplex (TDD) UEs, in accordance with certain aspects of the present disclosure.

[0027] FIG. 18 depicts a method for wireless communications.

[0028] FIG. 19 depicts a method for wireless communications.

[0029] FIG. 20 depicts aspects of an example communications device.

[0030] FIG. 21 depicts aspects of an example communications device.DETAILED DESCRIPTION

[0031] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for requesting system information. In some cases, a random access channel (RACH) occasion (RO) may fall in a subband full-duplex (SBFD) slot. In some cases, a UE that is SBFD-aware may request system information (SI). Some aspects are directed towards techniques towards an SBFD-aware UE requesting SI when ROs fall in SBFD and half-duplex (HD) slots. The BS may broadcast a first SIB (e.g., SIB1), but other SIB information may be requested by the UE transmitting a preamble via a certain RO in either an SBFD or HD slot.Introduction to Wireless Communications Networks

[0032] The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.

[0033] FIG. 1 depicts an example of a wireless communications network 100, in which aspects described herein may be implemented.

[0034] Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communications device and / or a communications function performed by a communications device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network as well as various devices associated with and interacting with a network may be considered networkentities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102), and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.

[0035] In the depicted example, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.

[0036] FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA), satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (loT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0037] BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0038] BSs 102 may generally include: a NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and / or others. Each of BSs 102 may providecommunications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of a macro cell). A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area), a pico cell (covering relatively smaller geographic area, such as a sports stadium), a femto cell (relatively smaller geographic area (e.g., a home)), and / or other types of cells.

[0039] While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a base station may be disaggregated, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a base station includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location. In some aspects, a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (0-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated base station architecture.

[0040] Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., an SI interface). BSs 102 configured for 5G (e.g., 5GNR or Next Generation RAN (NG-RAN)) may interface with 5GC 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface), which may be wired or wireless.

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

[0042] The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz), and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL).

[0043] Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182’. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182”. UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182”. BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182’. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receivedirections for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.

[0044] Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0045] Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0046] EPC 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) Gateway 172, such as in the depicted example. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, MME 162 provides bearer and connection management.

[0047] Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services.

[0048] BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and / or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

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

[0050] AMF 192 is a control node that processes signaling between UEs 104 and 5GC 190. AMF 192 provides, for example, quality of service (QoS) flow and session management.

[0051] Internet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0052] In various aspects, a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0053] FIG. 2 depicts an example disaggregated base station 200 architecture. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or aNon-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both). A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an Fl interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.

[0054] Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controllerproviding instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0055] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP)), control plane functionality (e.g., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.

[0056] The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rdGeneration Partnership Project (3GPP). In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.

[0057] Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, controlled by a DU 230, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fastFourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 240 can be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0058] The SMO Framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For nonvirtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an 01 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an 01 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.

[0059] The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy -based guidance of applications / features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface)connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.

[0060] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 225, the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from nonnetwork data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0061] FIG. 3 depicts aspects of an example BS 102 and a UE 104.

[0062] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which may be configured to implement various functions described herein related to wireless communications.

[0063] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively 352), transceivers 354a-r (collectively 354), which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360). UE 104 includes controller / processor 380, which may be configured to implement various functions described herein related to wireless communications.

[0064] In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller / processor 340. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group commonPDCCH (GC PDCCH), and / or others. The data may be for the physical downlink shared channel (PDSCH), in some examples.

[0065] Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).

[0066] Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.

[0067] In order to receive the downlink transmission, UE 104 includes antennas 352a- 352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0068] MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0069] In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel(PUCCH)) from the controller / processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0070] At BS 102, the uplink signals from UE 104 may be received by antennas 334a-t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller / processor 340.

[0071] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0072] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

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

[0074] In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.

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

[0076] FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.

[0077] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5GNR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.

[0078] Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and / or in the time domain with SC-FDM.

[0079] A wireless communications frame structure may be frequency division duplex (FDD), in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for either DL or UL. Wireless communications frame structures may also be time division duplex (TDD), in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.

[0080] In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL / UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling). In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format.Subframes may also include mini-slots, which generally have fewer symbols than an entire slot. Other wireless communications technologies may have a different frame structure and / or different channels.

[0081] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerol ogies (p) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots, respectively, per subframe. For slot configuration 1, different numerol ogies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology p, there are 14 symbols / slot and 2p slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2^ X 15 kHz, where p is the numerology 0 to 6. As such, the numerology p = 0 has a subcarrier spacing of 15 kHz and the numerology p = 6 has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGS.4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology p = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps.

[0082] As depicted in FIGS. 4 A, 4B, 4C, and 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0084] FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, nine RE groups (REGs), each REG including, for example, four consecutive REs in an OFDM symbol.

[0085] A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe / symbol timing and a physical layer identity.

[0086] A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.

[0087] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and / or paging messages.

[0088] As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS). The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0089] FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.Overview of Full Duplex Communication

[0090] As noted above, a full-duplex (FD) device is capable of simultaneous bidirectional communications. In contrast, half-duplex (HD) devices are only capable of communications in one direction (transmit or receive) at one time.

[0091] Examples of FD communication modes include in-band FD (IBFD) and subband FD. As illustrated in FIGs. 5A and 5B, with IBFD, a device may transmit and receive on the same time and frequency resources. In this case, the downlink (DL) 502 and uplink (UL) 504 shares the same IBFD time and frequency resources which may fully overlap (FIG. 5A) or partially overlap (FIG. 5B).

[0092] As shown in FIG. 5C, with SBFD (also referred to a flexible duplexing), a device may transmit and receive at the same time, but using different frequency resources. In this case, the DL resource may be separated from the UL resource, in frequency domain, by a guard band 506.

[0093] Interference to a UE and / or a network entity (e.g., a base station such as a gNB or node of a disaggregated base station) operating in FD mode may come in the form of CLI from neighboring nodes, as well as self-interference (SI). FIG. 5A, FIG. 5B, FIG.5C, and FIG. 5D illustrate example interference scenarios for various FD communication use cases.

[0094] As illustrated in FIG. 6A, a first scenario is when FD is enabled for a gNB (e.g., with non-overlapping UL / DL subbands) but disabled for each connected UE (which in turn may be enabled for half-duplex (HD) communication), a gNB communicates using FD capabilities. In this case, CLI between UEs, SI from the FD gNB, and CLI between the gNB and neighboring gNBs interferes with FD communication.

[0095] As illustrated in FIG. 6B, a second scenario is when FD is enabled for both a gNB and a FD UE / customer premise equipment (CPE) connected to the gNB, the gNB communicates with the FD UE using FD capabilities. If the gNB is connected to an HD UE alongside the FD UE, the gNB communicates with the HD UE. In this case, CLI between UEs, SI from the gNB and the FD UE, and CLI between the FD gNB and neighboring gNBs interferes with FD communication.

[0096] As illustrated in FIG. 6C, a third scenario is when FD is enabled for two gNBs (e.g., in a multiple TRP scenario) and enabled at one UE / CPE connected to the two gNBs. In this case, the two gNBs may communicate with the FD UE using FD capabilities. If one of the two gNBs is connected to an HD UE alongside the FD UE, the one gNB communicates with both the HD UE and the FD UE. In this case, CLI between UEs, SI from the FD UE, and CLI between the two gNBs may interfere with FD communication.

[0097] FIG. 7A also illustrates various forms of interference for FD communications. As illustrated, if a UE 104 is operating in HD mode and a gNB 102 is operating in FD (mode) SBFD / IBFD, sources of interference at the UE include inter-cell interference from other gNBs, intra-cell CLI from UEs in the same cell, and inter-cell CLI from UEs in adjacent cells. Additionally, there may be self-interference for full-duplex UEs, particularly in SBFD slots that include both uplink subbands 754 and downlink subbands 752, as shown in FIG. 7B.

[0098] As noted above, an FD enabled device is capable of bi-directional network data transmissions at the same time. FIG. 8 illustrates an example of an FD enabled base station (an FD gNB) performing simultaneous transmission and reception on a same slot. As shown, the FD gNB may simultaneously perform a downlink transmission and receive an uplink transmission. As illustrated, the downlink transmission may be intended for a first UE, and the uplink transmission may be received from a second UE. In some cases, the downlink transmission and uplink transmission may both be associated with the same UE (e.g., if the UE is an FD UE). The simultaneous transmission and reception in a same slot may cause interference, as illustrated.

[0099] FIGs. 9A and 9B depict example uplink (UL) and downlink (DL) subbands for SBFD operations.

[0100] As illustrated in FIG. 9A, for example, UL and DL subbands 900 may be allocated for SBFD operations within a carrier bandwidth (BW). As illustrated, for example, an UL subband allocation (e.g., and / or a DL subband allocation) may span NRB resource blocks (RBs). As noted above, and as illustrated, UL subbands and DL subbands may be separated by guard bands.

[0101] As illustrated in FIG. 9B, a time division duplexing (TDD) pattern 950 may indicate a semi-static configuration of subband time locations for SBFD operation. In such cases, frequency locations of DL subband(s) may be explicitly configured withguardband(s), if any, implicitly derived as RBs which are not within UL subband or DL subband(s). In other cases, a number of RBs for guardband(s), if any, is explicitly configured. In such cases, DL subband(s) may be implicitly derived as RBs which are not within UL subband or guardband(s).Example RACH Procedures

[0102] A random-access channel (RACH) is so named because it refers to a wireless channel (medium) that may be shared by multiple UEs and used by the UEs to (randomly) access the network for communications. For example, the RACH may be used for call setup and to access the network for data transmissions. In some cases, RACH may be used for initial access to a network when the UE switches from a radio resource control (RRC) connected idle mode to active mode, or when handing over in RRC connected mode. Moreover, RACH may be used for downlink (DL) and / or uplink (UL) data arrival when the UE is in RRC idle or RRC inactive modes, and when reestablishing a connection with the network.

[0103] FIG. 10 is a timing (or "call-flow") diagram 1000 illustrating an example four-step RACH procedure, in accordance with certain aspects of the present disclosure. A first message (MSG1) may be sent from the UE to a network entity (e.g., a BS such as a gNB) on the physical random access channel (PRACH). In this case, MSG1 may only include a RACH preamble. The network entity may respond with a random access response (RAR) message (MSG2) which may include the identifier (ID) of the RACH preamble, a timing advance (TA), an uplink grant, cell radio network temporary identifier (C-RNTI), and a back off indicator. MSG2 may include a PDCCH communication including control information for a following communication on the PDSCH, as illustrated. In response to MSG2, MSG3 is transmitted from the UE to the network entity on the PUSCH. MSG3 may include one or more of a RRC connection request, a tracking area update request, a system information request, a positioning fix or positioning signal request, or a scheduling request. The network entity then responds with MSG 4 which may include a contention resolution message.

[0104] In some cases, to speed access, a two-step RACH procedure may be supported. As the name implies, the two-step RACH procedure may effectively "collapse" the four messages of the four-step RACH procedure into two messages.Aspects Related to Requesting System Information

[0105] For non-overlapping subband full duplex (SBFD) operations at a base station within a time-division duplexing (TDD) carrier, a semi-static indication of time location of SBFD subbands may be specified to UEs in radio resource control (RRC) connected (RRC CONNECTED) mode. The time location of SBFD subbands in system information block (SIB) may be indicated. In some aspects, a semi-static indication of the frequency domain location of SBFD subbands may be specified to UEs in RRC CONNECTED mode. In some cases, the frequency domain location of SBFD subbands may be indicated in a SIB. In some cases, a random access channel (RACH) occasion (RO) falls in an SBFD slot (e.g., a slot dedicted to communications using SFBD). The BS may broadcast a first SIB (e.g., SIB1), but other SIB information may be requested by a UE transmitting a preamble in a certain RO which may fall within a half-duplex (HD) slot (e.g., a slot dedicated to communications using HD or TDD) or an SBFD slot.

[0106] FIG. 11 is a timing diagram 1100 illustrating example techniques for requesting system information (SI). As shown, a network entity (e.g., a base station) may send system information such as SIB1. The system information may include scheduling information that allows a UE to determine resources for requesting other system information. For example, as described in more detail herein, the system information may include scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information.

[0107] In some cases, for random access operations of SBFD-aware UEs in RRC CONNECTED state, one single RACH configuration may be used. The ROs within an uplink (UL) subband in SBFD symbols may be valid for an SBFD-aware UE (e.g., and invalid for legacy UEs). In some cases, for random access operation for SBFD-aware UEs in RRC CONNECTED state, two separate RACH configurations may be used, including one legacy RACH configuration and one additional RACH configuration. The ROs within the UL subband in SBFD symbols configured by the additional RACH configuration may be valid for an SBFD-aware UE.

[0108] FIG. 12 illustrates an SI request configuration information element (IE) 1200. An SI request may be performed using a contention-free random access (CFRA) procedure. The network may configure a UE with dedicated random access (RA) resources for SI request purposes in an SI request configuration (SI-RequestConfig) IEthat the BS may broadcast within SIB 1. A first message (Msgl) of the RACH procedure may be used to indicate the requested SI as described with respect to FIG. 11.

[0109] The SI request period (si-RequestPeriod) may indicate a periodicity of the SI request configuration in a number of association periods. As used herein, an association period generally refers to a time period in which all synchronization signal blocks (SSBs) are mapped to RACH occasions. The random access associated period index may be the index of the association period in the si-RequestPeriod in which the UE can send the SI request for SI message(s) corresponding to SI request resources (SI-RequestResources). The SI request may be transmitted using a preamble indicated by a random access (RA) preamble start index (ra-PreambleStartlndex) and via RACH occasions indicated by an RA SSB Occasion Mask Index (ra-ssb-OccasionMasklndex). For example, if N SSBs (e.g., N being a positive integer) are associated with a RACH occasion, for the ithSSB (i=0, ... , N-l) the preamble with the preamble index = ra-PremableStartlndex + i may be used for the SI request. For N less than 1, the preamble with preamble index = ra-PreambleStartlndex is used for the SI request.

[0110] With higher layer parameters, the UE may have a RACH configuration that determines the RACH occasions used for a system information request (Si-request). However, the UE may not be allowed to use all of the RACH occasions for an Si-request. The UE may be limited to a given periodicity in terms of association period. Moreover, multiple SI request resources may be defined and mapped to different system information (e.g., different types of system information to be requested). A given SI request resource may be defined by a preamble per SSB index, an association period index, and a mask index. In some cases, the same legacy configuration may be used for SBFD-aware UEs, but the ROs that fall in downlink (DL)-SBFD slots may be valid for the SBFD-aware UE. In some cases, another configuration may be defined just for the SBFD aware UE in addition to the legacy configuration.[OHl] With the network enabling SI requests over SBFD slots, an SBFD-aware UE may request SI with lower latency than SI requests from a legacy UE. The UE may send the request in the first available RO, which can be an SBFD-RO, and the network response may be faster and the UE acknowledgment (ACK) / negative ACK (NACK) may be faster. By enabling SI requests over SBFD slots, the network may be able to determine whether the UE requesting SI is an SBFD-aware UE or not so that the network can transmit a physical downlink shared channel (PDSCH) carrying the system information in SBFDslots taking into account the enhancements associated with the SBFD-aware UE, improving scheduling efficiency as well as increasing network energy saving. Requests for new system information may be isolated in these ROs, which will make natural resources available for special types of system information requests. For example, the SBFD-aware UE may request legacy SI over legacy ROs and newly defined system information over SBFD ROs. In some cases, the requested new system information may be SIB1 of a network energy saving (NES) cell.

[0112] FIG. 13 illustrates example SI scheduling information 1300 (e.g., labeled “SI-Schedulinglnfo”) that may be transmitted in a system information block (e.g., SIB1). As shown, the Sl-Schedulinglnfo may include a scheduling information list (e.g., labeled “schedulinglnfoList”) that may include a list of scheduling information (labeled “Schedulinginfo”). The Sl-Schedulinglnfo may also include an SI request configuration (labeled “si-RequestConfig”) that may include a list of SI request resources (labeled “si-RequestResources”). The si-RequestResources may include a list of request resources each labeled “SI-RequestResource.” Each of the Schedulinginfo may be mapped to an SI-RequestResource. For example, the Schedulinginfo may indicate a type of SI to be requested, and the SI-RequestResource may indicate the resource (e.g., RACH occasion and preamble) to be used to request the type of SI. For example, each SI-RequestResource may include a preamble start index (labeled “Preamblestartindex”), an association period index (labeled “AssociationPeriodlndex”), and an occasion mask index (labeled “OccasionMasklndex”). The preamble start index may indicate the starting index of random access preamble(s) to be used for an SI request. The association period index indicates the association period to be used. The occasion mask index indicates the RO(s) associated with an SSB in which a UE may transmit a random access preamble for the SI request.

[0113] In some aspects, system information requests in an SBFD network may be performed using only legacy half-duplex (HD) ROs (e.g., also referred to as time-division duplexing (TDD) ROs), which may be ROs that are in HD slots. Sometimes, an SBFD-aware UE may use either the legacy HD ROs or the SBFD ROs (e.g., an RO that falls within an SBFD slot). For example, an SBFD-aware UE may select the first available RO to request system information, whether the RO is in a TDD or SBFS slot. An SBFD-aware UE may be restricted to transmit in the SBFD or TDD RO based on an indication by the network via a radio resource control (RRC) parameter. That is, a parameter maybe included in the SI-RequestResource of the SIB to indicate whether an SBFD-aware UE should use an SFBD RO or TDD RO to request SI. In this manner, the network may be able to determine the type of the UE requesting system information.

[0114] FIG. 14 illustrates example SI scheduling information 700 that may include scheduling information for SBFD-aware UEs, in accordance with certain aspects of the present disclosure. That is, another list of SchedulinglnfoList (labeled “schedulinglnfoList SFBD) may be included in SIB for the ROs falling in the SBFD slots. When the UE uses a corresponding SI-RequestResource, the UE may either use the legacy RO in the HD slot when the requested information is the corresponding one in SchedulinglnfoList, or use the SBFD RO in the SBFD slot when the requested information is the corresponding one in schedulinglnfoList SBFD. That is, the Schedulinginfo may correspond to resources that may include an HD RO and an SBFD RO. The UE may use the HD RO if requesting the SI type that is in the SchedulinglnfoList or use the SBFD RO if requesting the SI type that is in the schedulinglnfoList SBFD.

[0115] FIG. 15 illustrates example SI scheduling information 1500 that may include SI request resources for SBFD-aware UEs, in accordance with certain aspects of the present disclosure. As shown, another list of si-RequestResources (e.g., labeled “si requestResources SBFD) may be defined such that the UE determines the SI request resources in HD slots per the si-RequestResources and determines the SI request resources in SBFD slots per the si-RequestResources_SBFD. A mapping may be defined between the SLrequestresources and the SchedulinglnfoList. In other words, a UE may request SI indicated in the Schedulinginfo using either the resources in HD slots indicated in the si-RequestResources or the resources in SFBD slots indicated in the si requestResources SBFD.

[0116] FIG. 16 illustrates example SI scheduling information 1600 that may include scheduling information and SI request resources for SBFD-aware UEs, in accordance with certain aspects of the present disclosure. That is, another list of si-RequestResources (e.g., labeled “si-RequestResources_SBFD) may be defined such that the UE determines the SI request resources in HD slots from si-RequestResources and determines the SI request resources in SBFD slots from si-RequestResources_SBFD. A mapping may be defined between the SBFD SLrequestresources (e.g., from si-RequestResources_SBFD) and the SchedulinglnfoList (e.g., from the schedulinglnfoList SBFD), and a mapping may be defined between the non-SBFD (e.g., legacy) SLrequestresources (e.g., from si-RequestResources) and the schedulinglnfoList (e.g., from the schedulinglnfoList). In some cases, the Schedulinginfo for the SBFD-aware UEs may duplicate the Schedulinginfo for the non- SBFD-aware UEs.

[0117] FIG. 17 is a diagram 1700 illustrating example techniques for preamble partitioning between TDD UEs (e.g., HD UEs, also referred to as non- SBFD-aware UEs) and SBFD-aware UEs, in accordance with certain aspects of the present disclosure. The preamble index for a cell is an integer that identifies each of the multiple preambles available in a cell. For example, when more than one SSB is mapped to the same RO and the SBFD-aware UE can use the TDD RO, the preamble index of the full-duplex aware UE (e.g., SBFD-aware UE) may be calculated according to the following equation:Preamble index = Preamblestartindex + i + n where n is an RRC configured parameter and i is the SSB block index. For example, as shown, if multiple SSBs (labeled “SSBO”, “SSB1”, “SSB2”, and “SSB3”) are associated with the same RO, an HD UE may use a preamble (e.g., preamble sequence) associated with the indicated preamble start index to indicate SSBO so that the network can respond with the beam associated with SSBO. The HD UE may use a preamble (e.g., preamble sequence) associated with the indicated preamble start index +1 to indicate SSB1 so that the network can respond with the beam associated with SSB1, and so on. In some aspects, the preambles may be partitioned between HD UEs and SBFD-aware UEs. For example, assuming there are four SSBs associated with the RO (e.g., n is equal to 4) the HD UEs may use preamble start index to preamble start index + 3 and SBFD-aware UEs may use the preamble start index + 4 to preamble start index + 7, allowing the network to identify whether a UE is an HD UE or a SBFD-aware UE.Example Operations

[0118] FIG. 18 shows an example of a method 1800 of wireless communications at a user equipment (UE), such as a UE 104 of FIGS. 1 and 3.

[0119] Method 1800 begins at step 1805 with receiving at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot. In some cases, theoperations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 20.

[0120] Method 1800 then proceeds to step 1810 with transmitting a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 20.

[0121] In some aspects, the message is transmitted via the first RO or the second RO that is available first in time.

[0122] In some aspects, the at least one indication of the request resources includes an indication of whether the UE is to use the first RO or the second RO to request the system information.

[0123] In some aspects, the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot.

[0124] In some aspects, the at least one indication of the request resources includes a first information element indicating a first resource to be used to request the system information via the first RO and a second information element indicating a second resource to be used to request the system information via the second RO.

[0125] In some aspects, the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot; and the at least one indication of the request resources includes a third information element indicating a first resource to be used to request the first type of the system information via the first RO and a fourth information element indicating a second resource to be used to request the second type of the system information via the second RO.

[0126] In some aspects, the first type of the system information is the same as the second type of the system information.

[0127] In some aspects, the at least one indication of the request resources includes at least one of: a preamble start index indicating a preamble to be used for requesting thesystem information; an association period to be used for requesting the system information; or an occasion mask index indicating a subset of ROs that can be used for requesting the system information, wherein the ROs are associated with a synchronization signal block (SSB).

[0128] In some aspects, the message requesting the system information is transmitted using a subset of preamble indices dedicated for the UE capable of using the first RO in the SBFD slot to request the system information.

[0129] In one aspect, method 1800, or any aspect related to it, may be performed by an apparatus, such as communications device 2000 of FIG. 20, which includes various components operable, configured, or adapted to perform the method 1800. Communications device 2000 is described below in further detail.

[0130] Note that FIG. 18 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0131] FIG. 19 shows an example of a method 1900 of wireless communications at a network entity, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

[0132] Method 1900 begins at step 1905 with transmitting at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot. In some cases, the operations of this step refer to, or may be performed by, circuitry for transmitting and / or code for transmitting as described with reference to FIG. 21.

[0133] Method 1900 then proceeds to step 1910 with receiving a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot. In some cases, the operations of this step refer to, or may be performed by, circuitry for receiving and / or code for receiving as described with reference to FIG. 21.

[0134] In some aspects, the message is received via the first RO or the second RO that is available first in time.

[0135] In some aspects, the at least one indication of the request resources includes an indication of whether a user equipment (UE) is to use the first RO or the second RO to request the system information.

[0136] In some aspects, the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot.

[0137] In some aspects, the at least one indication of the request resources includes a first information element indicating a first resource to be used to request the system information via the first RO and a second information element indicating a second resource to be used to request the system information via the second RO.

[0138] In some aspects, the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information indicating a second type of the system information to be requested by the first RO in the HD slot; and the at least one indication of the request resources includes a third information element indicating a first resource to be used to request the first type of the system information via the first RO and a fourth information element indicating a second resource to be used to request the second type of the system information via the second RO.

[0139] In some aspects, the first type of the system information is the same as the second type of the system information.

[0140] In some aspects, the at least one indication of the request resources includes at least one of: a preamble start index indicating a preamble to be used for requesting the system information; an association period to be used for requesting the system information; or an occasion mask index indicating a subset of ROs that can be used for requesting the system information, the ROs being associated with a synchronization signal block (SSB).

[0141] In some aspects, the message requesting the system information is transmitted using a subset of preamble indices dedicated for a user equipment (UE) capable of using the first RO in the SBFD slot to request the system information.

[0142] In one aspect, method 1900, or any aspect related to it, may be performed by an apparatus, such as communications device 2100 of FIG. 21, which includes various components operable, configured, or adapted to perform the method 1900. Communications device 2100 is described below in further detail.

[0143] Note that FIG. 19 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Communications Device(s)

[0144] FIG. 20 depicts aspects of an example communications device 2000. In some aspects, communications device 2000 is a user equipment, such as UE 104 described above with respect to FIGS. 1 and 3.

[0145] The communications device 2000 includes a processing system 2005 coupled to the transceiver 2045 (e.g., a transmitter and / or a receiver). The transceiver 2045 is configured to transmit and receive signals for the communications device 2000 via the antenna 2050, such as the various signals as described herein. The processing system 2005 may be configured to perform processing functions for the communications device 2000, including processing signals received and / or to be transmitted by the communications device 2000.

[0146] The processing system 2005 includes one or more processors 2010. In various aspects, the one or more processors 2010 may be representative of one or more of receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to FIG. 3. The one or more processors 2010 are coupled to a computer-readable medium / memory 2025 via a bus 2040. In certain aspects, the computer-readable medium / memory 2025 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 2010, cause the one or more processors 2010 to perform the method 1800 described with respect to FIG. 18, or any aspect related to it. Note that reference to a processor performing a function of communications device 2000 may include one or more processors 2010 performing that function of communications device 2000.

[0147] In the depicted example, computer-readable medium / memory 2025 stores code (e.g., executable instructions), such as code for receiving 2030 and code fortransmitting 2035. Processing of the code for receiving 2030 and code for transmitting 2035 may cause the communications device 2000 to perform the method 1800 described with respect to FIG. 18, or any aspect related to it.

[0148] The one or more processors 2010 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 2025, including circuitry such as circuitry for receiving 2015 and circuitry for transmitting 2020. Processing with circuitry for receiving 2015 and circuitry for transmitting 2020 may cause the communications device 2000 to perform the method 1800 described with respect to FIG. 18, or any aspect related to it.

[0149] Various components of the communications device 2000 may provide means for performing the method 1800 described with respect to FIG. 18, or any aspect related to it. For example, means for transmitting, sending or outputting for transmission may include transceivers 354 and / or antenna(s) 352 of the UE 104 illustrated in FIG. 3 and / or the transceiver 2045 and the antenna 2050 of the communications device 2000 in FIG.20. Means for receiving or obtaining may include transceivers 354 and / or antenna(s) 352 of the UE 104 illustrated in FIG. 3 and / or the transceiver 2045 and the antenna 2050 of the communications device 2000 in FIG. 20.

[0150] FIG. 21 depicts aspects of an example communications device 2100. In some aspects, communications device 2100 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.

[0151] The communications device 2100 includes a processing system 2105 coupled to the transceiver 2145 (e.g., a transmitter and / or a receiver) and / or a network interface 2155. The transceiver 2145 is configured to transmit and receive signals for the communications device 2100 via the antenna 2150, such as the various signals as described herein. The network interface 2155 is configured to obtain and send signals for the communications device 2100 via communication link(s), such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The processing system 2105 may be configured to perform processing functions for the communications device 2100, including processing signals received and / or to be transmitted by the communications device 2100.

[0152] The processing system 2105 includes one or more processors 2110. In various aspects, one or more processors 2110 may be representative of one or more of receiveprocessor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors 2110 are coupled to a computer-readable medium / memory 2125 via a bus 2140. In certain aspects, the computer-readable medium / memory 2125 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 2110, cause the one or more processors 2110 to perform the method 1900 described with respect to FIG. 19, or any aspect related to it. Note that reference to a processor of communications device 2100 performing a function may include one or more processors 2110 of communications device 2100 performing that function.

[0153] In the depicted example, the computer-readable medium / memory 2125 stores code (e.g., executable instructions), such as code for transmitting 2130 and code for receiving 2135. Processing of the code for transmitting 2130 and code for receiving 2135 may cause the communications device 2100 to perform the method 1900 described with respect to FIG. 19, or any aspect related to it.

[0154] The one or more processors 2110 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 2125, including circuitry such as circuitry for transmitting 2115 and circuitry for receiving 2120. Processing with circuitry for transmitting 2115 and circuitry for receiving 2120 may cause the communications device 2100 to perform the method 1900 described with respect to FIG. 19, or any aspect related to it.

[0155] Various components of the communications device 2100 may provide means for performing the method 1900 described with respect to FIG. 19, or any aspect related to it. Means for transmitting, sending or outputting for transmission may include transceivers 332 and / or antenna(s) 334 of the BS 102 illustrated in FIG. 3 and / or the transceiver 2145 and the antenna 2150 of the communications device 2100 in FIG. 21. Means for receiving or obtaining may include transceivers 332 and / or antenna(s) 334 of the BS 102 illustrated in FIG. 3 and / or the transceiver 2145 and the antenna 2150 of the communications device 2100 in FIG. 21.Example Clauses

[0156] Implementation examples are described in the following numbered clauses:

[0157] Clause 1 : A method for wireless communications at a user equipment (UE), comprising: receiving at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; and transmitting a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot.

[0158] Clause 2: The method of Clause 1, wherein the message is transmitted via the first RO or the second RO that is available first in time.

[0159] Clause 3: The method of any one of Clauses 1-2, wherein the at least one indication of the request resources includes an indication of whether the UE is to use the first RO or the second RO to request the system information.

[0160] Clause 4: The method of any one of Clauses 1-3, wherein the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot.

[0161] Clause 5: The method of any one of Clauses 1-4, wherein the at least one indication of the request resources includes a first information element indicating a first resource to be used to request the system information via the first RO and a second information element indicating a second resource to be used to request the system information via the second RO.

[0162] Clause 6: The method of any one of Clauses 1-5, wherein: the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot; and the at least one indication of the request resources includes a third information element indicating a first resource to be used to request the first type of the system information via the first RO and a fourth information element indicating a second resource to be used to request the second type of the system information via the second RO.

[0163] Clause 7: The method of Clause 6, wherein the first type of the system information is the same as the second type of the system information.

[0164] Clause 8: The method of any one of Clauses 1-7, wherein the at least one indication of the request resources includes at least one of: a preamble start index indicating a preamble to be used for requesting the system information; an association period to be used for requesting the system information; or an occasion mask index indicating a subset of ROs that can be used for requesting the system information, wherein the ROs are associated with a synchronization signal block (SSB).

[0165] Clause 9: The method of any one of Clauses 1-8, wherein the message requesting the system information is transmitted using a subset of preamble indices dedicated for the UE capable of using the first RO in the SBFD slot to request the system information.

[0166] Clause 10: A method for wireless communications at a network entity, comprising: transmitting at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; and receiving a message requesting the system information via the RO in the SBFD slot or the RO in the HD slot.

[0167] Clause 11 : The method of Clause 10, wherein the message is received via the first RO or the second RO that is available first in time.

[0168] Clause 12: The method of any one of Clauses 10-11, wherein the at least one indication of the request resources includes an indication of whether a user equipment (UE) is to use the first RO or the second RO to request the system information.

[0169] Clause 13: The method of any one of Clauses 10-12, wherein the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot.

[0170] Clause 14: The method of any one of Clauses 10-13, wherein the at least one indication of the request resources includes a first information element indicating a firstresource to be used to request the system information via the first RO and a second information element indicating a second resource to be used to request the system information via the second RO.

[0171] Clause 15: The method of any one of Clauses 10-14, wherein: the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information indicating a second type of the system information to be requested by the first RO in the HD slot; and the at least one indication of the request resources includes a third information element indicating a first resource to be used to request the first type of the system information via the first RO and a fourth information element indicating a second resource to be used to request the second type of the system information via the second RO.

[0172] Clause 16: The method of Clause 15, wherein the first type of the system information is the same as the second type of the system information.

[0173] Clause 17: The method of any one of Clauses 10-16, wherein the at least one indication of the request resources includes at least one of: a preamble start index indicating a preamble to be used for requesting the system information; an association period to be used for requesting the system information; or an occasion mask index indicating a subset of ROs that can be used for requesting the system information, the ROs being associated with a synchronization signal block (SSB).

[0174] Clause 18: The method of any one of Clauses 10-17, wherein the message requesting the system information is transmitted using a subset of preamble indices dedicated for a user equipment (UE) capable of using the first RO in the SBFD slot to request the system information.

[0175] Clause 19: An apparatus, comprising: at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method in accordance with any combination of Clauses 1-18.

[0176] Clause 20: An apparatus, comprising means for performing a method in accordance with any combination of Clauses 1-18.

[0177] Clause 21: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of an apparatus, cause the apparatus to perform a method in accordance with any combination of Clauses 1-18.

[0178] Clause 22: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any combination of Clauses 1-18.Additional Considerations

[0179] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0180] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a graphics processing unit (GPU), a neural processing unit (NPU), a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, theprocessor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0181] As used herein, “a processor,” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance of the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory,” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and / or instructions, multiple memories configured to collectively store data and / or instructions.

[0182] In some cases, rather than actually transmitting a signal, an apparatus (e.g., a wireless node or device) may have an interface to output the signal for transmission. For example, a processor may output a signal, via a bus interface, to a radio frequency (RF) front end for transmission. Accordingly, a means for outputting may include such an interface as an alternative (or in addition) to a transmitter or transceiver. Similarly, rather than actually receiving a signal, an apparatus (e.g., a wireless node or device) may have an interface to obtain a signal from another device. For example, a processor may obtain (or receive) a signal, via a bus interface, from an RF front end for reception. Accordingly, a means for obtaining may include such an interface as an alternative (or in addition) to a receiver or transceiver.

[0183] While the present disclosure may describe certain operations as being performed by one type of wireless node, the same or similar operations may also be performed by another type of wireless node. For example, operations performed by a user equipment (UE) may also (or instead) be performed by a network entity (e.g., a base station or unit of a disaggregated base station). Similarly, operations performed by a network entity may also (or instead) be performed by a UE.

[0184] Further, while the present disclosure may describe certain types of communications between different types of wireless nodes (e.g., between a network entityand a UE), the same or similar types of communications may occur between same types of wireless nodes (e.g., between network entities or between UEs, in a peer-to-peer scenario). Further, communications may occur in reverse order than described.

[0185] Means for receiving, means for communicating, means for transmitting, and means for determining may comprise one or more processors, such as one or more of the processors described above with reference to FIG. 18, FIG. 19, and FIG. 20.

[0186] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples 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).

[0187] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

[0188] The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component(s) and / or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0189] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for”. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

WHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a user equipment (UE), comprising:at least one memory comprising computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to:receive at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; andtransmit a message requesting the system information via the first RO in the SBFD slot or the second RO in the HD slot.

2. The apparatus of claim 1, wherein the one or more processors are configured to execute the computer-executable instructions and cause the apparatus to transmit the message via the first RO or the second RO that is available first in time.

3. The apparatus of claim 1, wherein the at least one indication of the request resources includes an indication of whether the UE is to use the first RO or the second RO to request the system information.

4. The apparatus of claim 1, wherein the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot.

5. The apparatus of claim 1, wherein the at least one indication of the request resources includes a first information element indicating a first resource to be used to request the system information via the first RO and a second information element indicating a second resource to be used to request the system information via the second RO.

6. The apparatus of claim 1, wherein:the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot; andthe at least one indication of the request resources includes a third information element indicating a first resource to be used to request the first type of the system information via the first RO and a fourth information element indicating a second resource to be used to request the second type of the system information via the second RO.

7. The apparatus of claim 6, wherein the first type of the system information is the same as the second type of the system information.

8. The apparatus of claim 1, wherein the at least one indication of the request resources includes at least one of:a preamble start index indicating a preamble to be used for requesting the system information;an association period to be used for requesting the system information; or an occasion mask index indicating a subset of ROs that can be used for requesting the system information, wherein the ROs are associated with a synchronization signal block (SSB).

9. The apparatus of claim 1, wherein the one or more processors are configured to execute the computer-executable instructions and cause the apparatus to transmit the message requesting the system information using a subset of preamble indices dedicated for the UE capable of using the first RO in the SBFD slot to request the system information.

10. An apparatus for wireless communication at a network entity, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions and cause the apparatus to:transmit at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least a first random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; andreceive a message requesting the system information via the first RO in the SBFD slot or the second RO in the HD slot.

11. The apparatus of claim 10, wherein the one or more processors are configured to execute the computer-executable instructions and cause the apparatus to receive the message via the first RO or the second RO that is available first in time.

12. The apparatus of claim 10, wherein the at least one indication of the request resources includes an indication of whether a user equipment (UE) is to use the first RO or the second RO to request the system information.

13. The apparatus of claim 10, wherein the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information element indicating a second type of the system information to be requested by the first RO in the HD slot.

14. The apparatus of claim 10, wherein the at least one indication of the request resources includes a first information element indicating a first resource to be used to request the system information via the first RO and a second information element indicating a second resource to be used to request the system information via the second RO.

15. The apparatus of claim 10, wherein:the at least one indication of the scheduling information comprises a first information element indicating a first type of the system information to be requested by the first RO in the SBFD slot and a second information indicating a second type of the system information to be requested by the first RO in the HD slot; andthe at least one indication of the request resources includes a third information element indicating a first resource to be used to request the first type of the system information via the first RO and a fourth information element indicating a second resource to be used to request the second type of the system information via the second RO.

16. The apparatus of claim 15, wherein the first type of the system information is the same as the second type of the system information.

17. The apparatus of claim 10, wherein the at least one indication of the request resources includes at least one of:a preamble start index indicating a preamble to be used for requesting the system information;an association period to be used for requesting the system information; or an occasion mask index indicating a subset of ROs that can be used for requesting the system information, the ROs being associated with a synchronization signal block (SSB).

18. The apparatus of claim 10, wherein the message requesting the system information is transmitted using a subset of preamble indices dedicated for a user equipment (UE) capable of using the first RO in the SBFD slot to request the system information.

19. A method for wireless communications at a user equipment (UE), comprising:receiving at least one indication of scheduling information indicating system information to be requested and at least one indication of request resources to be used for requesting the system information, wherein the request resources include at least afirst random access channel (RACH) occasion (RO) in an SBFD slot and a second RO in a half-duplex (HD) slot; andtransmitting a message requesting the system information via the first RO in the SBFD slot or the second RO in the HD slot.

20. The method of claim 19, wherein the message is transmitted via the first RO or the second RO that is available first in time.

Images