Resource blocks in uplink band of sub-band full duplex symbols

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive downlink control information (DCI) that schedules a downlink message for initial access communication and indicates a common physical uplink control channel (PUCCH) resource for feedback for the downlink message. The UE may obtain one or more resource subband physical block (PRB) offsets for transmitting the feedback in an uplink subband of a subband full duplex symbol associated with the common PUCCH resource. The UE may transmit the feedback in a first PRB for a first frequency hopping in the uplink subband and in a second PRB for a second frequency hopping in the uplink subband based at least in part on the one or more subband PRB offsets. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 384,081, entitled "RESOURCE BLOCKS IN UPLINK BAND OF SUBBAND FULL DUPLEX SLOT", filed on November 16, 2022, and U.S. Non - Provisional Patent Application No. 18 / 347,187, entitled "RESOURCE BLOCKS IN UPLINK BAND OF SUBBAND FULL DUPLEX SYMBOL", filed on July 5, 2023. These two applications are hereby incorporated by reference in their entirety. Field of the Disclosure

[0003] Aspects of the present disclosure generally relate to wireless communication and, more particularly, to techniques and apparatus for resource blocks in an uplink band using sub - band full - duplex symbols. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques that are capable of supporting communication with multiple users by sharing available system resources, such as bandwidth or transmit power. Examples of such multiple access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, Time Division - Synchronous Code Division Multiple Access (TD - SCDMA) systems, and Long Term Evolution (LTE). LTE / Advanced LTE is an enhanced collection of the Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the 3rd Generation Partnership Project (3GPP).

[0005] The above multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, or global level. New Radio (NR) (which may be referred to as 5G) is an enhanced set of LTE mobile standards promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technology, and carrier aggregation to improve spectral efficiency, reduce costs, improve services, utilize new spectrums, and better integrate with other open standards. With the continuous increase in the demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies are still useful. SUMMARY OF THE INVENTION

[0006] Some aspects described herein relate to a method of wireless communication performed by a User Equipment (UE). The method may include receiving Downlink Control Information (DCI) that schedules a downlink message for initial access communication and indicates a Physical Uplink Control Channel (PUCCH) resource for feedback for the downlink message. The method may include obtaining one or more Subband Physical Resource Block (PRB) offsets for transmitting feedback in an uplink subband of a Subband Full Duplex (SBFD) symbol (or time slot) associated with the common PUCCH resource. The method may include transmitting feedback in a first PRB for a first frequency hop in the uplink subband and in a second PRB for a second frequency hop in the uplink subband, at least in part based on the one or more subband PRB offsets.

[0007] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include transmitting DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The method may include receiving feedback in a first PRB for a first frequency hop in an uplink subband of an SBFD symbol (or time slot) associated with the common PUCCH resource and in a second PRB for a second frequency hop in the uplink subband.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The method may include selecting a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of an SBFD symbol (or slot). The method may include transmitting feedback in the selected PUCCH resource.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The method may include selecting a set of PUCCH resources at least in part based on a slot type. The method may include selecting a PUCCH resource at least in part based on an index within the set of PUCCH resources. The method may include transmitting feedback in a first PRB of a first frequency hop for an SBFD symbol associated with the selected PUCCH resource in an uplink subband and in a second PRB of a second frequency hop in the uplink subband.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or jointly, to cause the UE to receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The one or more processors may be configured, individually or jointly, to cause the UE to obtain one or more subband PRB offsets for transmitting feedback in an uplink subband of an SBFD symbol associated with the common PUCCH resource. The one or more processors may be configured, individually or jointly, to cause the UE to transmit feedback in a first PRB of a first frequency hop for an uplink subband and in a second PRB of a second frequency hop in the uplink subband at least in part based on the one or more subband PRB offsets.

[0011] Some aspects described herein relate to a network entity for wireless communication. The network entity may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or jointly, to cause the network entity to transmit DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The one or more processors may be configured, individually or jointly, to cause the network entity to receive feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband.

[0012] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or jointly, to cause the UE to receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The one or more processors may be configured, individually or jointly, to cause the UE to select a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of an SBFD symbol. The one or more processors may be configured, individually or jointly, to cause the UE to transmit feedback in the selected PUCCH resource.

[0013] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or jointly, to cause the UE to receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The one or more processors may be configured, individually or jointly, to cause the UE to select a set of PUCCH resources at least in part based on a slot type. The one or more processors may be configured, individually or jointly, to cause the UE to select a PUCCH resource at least in part based on an index within the set of PUCCH resources. The one or more processors may be configured, individually or jointly, to cause the UE to transmit feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The instruction set, when executed by one or more processors of the UE, may cause the UE to obtain one or more subband PRB offsets for transmitting feedback in an uplink subband of an SBFD symbol associated with the common PUCCH resource. The instruction set, when executed by one or more processors of the UE, may cause the UE to transmit feedback in a first PRB for a first frequency hop in the uplink subband and in a second PRB for a second frequency hop in the uplink subband, at least in part based on the one or more subband PRB offsets.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to transmit DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive feedback in a first PRB for a first frequency hop in an uplink subband of an SBFD symbol associated with the common PUCCH resource and in a second PRB for a second frequency hop in the uplink subband.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. One or more instructions, when executed by one or more processors of the UE, may cause the UE to receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The instruction set, when executed by the one or more processors, may cause the UE to select a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of an SBFD symbol. The instruction set, when executed by the one or more processors, may cause the UE to transmit feedback in the selected PUCCH resource.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the UE to receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The instruction set, when executed by the one or more processors, may cause the UE to select a PUCCH resource set at least in part based on a slot type. The instruction set, when executed by the one or more processors, may cause the UE to select a PUCCH resource at least in part based on an index within the PUCCH resource set. The instruction set, when executed by the one or more processors, may cause the UE to transmit feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The apparatus may include means for obtaining one or more subband PRB offsets for transmitting feedback in an uplink subband for an SBFD symbol associated with the common PUCCH resource. The apparatus may include means for transmitting feedback in a first PRB of a first frequency hop in the uplink subband and in a second PRB of a second frequency hop in the uplink subband at least in part based on the one or more subband PRB offsets.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The apparatus may include means for receiving feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The apparatus may include means for selecting a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband for an SBFD symbol. The apparatus may include means for transmitting feedback in the selected PUCCH resource.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The apparatus may include components for selecting a PUCCH resource set based at least in part on a slot type. The apparatus may include components for selecting a PUCCH resource based at least in part on an index within the PUCCH resource set. The apparatus may include components for transmitting feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband.

[0022] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, UE, base station, network entity, wireless communication device, or processing system that are fully described with reference to the drawings and the specification and illustrated as in the drawings and the specification.

[0023] The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the drawings, the characteristics (both its organization and operation methods) of the concepts disclosed herein and the associated advantages will be better understood. Each of the drawings provided is for the purpose of illustration and description and not as a definition of the limits of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] To enable a more detailed understanding of the above features of the present disclosure, a more specific description of the foregoing briefly summarized may be obtained by reference to the aspects, some of which are illustrated in the drawings. It should be noted, however, that the drawings illustrate only some typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0025] Figure 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure.

[0026] Figure 2 is a diagram illustrating an example base station communicating with a user equipment (UE) in a wireless network in accordance with the present disclosure.

[0027] Figure 3Is a diagram illustrating an example disaggregated base station architecture according to the present disclosure.

[0028] Figure 4 Is a diagram illustrating an example of full-duplex communication according to the present disclosure.

[0029] Figure 5 Is a diagram illustrating an example of a time slot pattern having sub-band full-duplex (SBFD) time slots according to the present disclosure.

[0030] Figure 6 Is a diagram illustrating an example of communication in an uplink sub-band of an SBFD symbol according to the present disclosure.

[0031] Figure 6 Is a diagram illustrating an example of physical resource blocks (PRBs) in an uplink (UL) sub-band according to the present disclosure.

[0032] Figure 7 Is a diagram illustrating an example of a PRB offset used with a UL sub-band according to the present disclosure.

[0033] Figure 8 Is a diagram illustrating an example of a PRB offset used with a UL sub-band according to the present disclosure.

[0034] Figure 9 Is a diagram illustrating an example of a PRB offset used with a UL sub-band according to the present disclosure.

[0035] Figure 10 Is a diagram illustrating an example of a PRB offset used with a UL sub-band according to the present disclosure.

[0036] Figure 11 Is a diagram illustrating an example of a PRB offset used with a UL sub-band according to the present disclosure.

[0037] Figure 12 Is a diagram of an example associated with using a PRB offset for a UL sub-band according to the present disclosure.

[0038] Figure 13 Is a diagram of an example associated with using a PRB offset for a UL sub-band according to the present disclosure.

[0039] Figure 14 Is a diagram of an example associated with using a UL sub-band according to the present disclosure.

[0040] Figure 15 Is a diagram illustrating an example process, such as performed by a UE, according to the present disclosure.

[0041] Figure 16 Is a diagram illustrating an example process, such as performed by a network entity, according to the present disclosure.

[0042] Figure 17 is a diagram illustrating an example process performed, for example, by a UE in accordance with the present disclosure.

[0043] Figure 18 is a diagram illustrating an example process performed, for example, by a UE in accordance with the present disclosure.

[0044] Figure 19 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure.

[0045] Figure 20 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure. Detailed Description

[0046] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. 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 present disclosure is intended to cover such apparatus or methods practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the various aspects of the present disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0047] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements") in the accompanying drawings. These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0048] Figure 1FIG. is a diagram illustrating an example of a wireless network in accordance with the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, and so on. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE120b, UE 120c, UE 120d, and UE 120e), or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographical area. In the Third Generation Partnership Project (3GPP), the term “cell” may refer to the coverage area of the base station 110 or the base station subsystem serving the coverage area, depending on the context in which the term is used.

[0049] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access by UEs 120 having a service subscription. A pico cell may cover a relatively small geographical area and may allow unrestricted access by UEs 120 having a service subscription. A femto cell may cover a relatively small geographical area (e.g., a home) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station.

[0050] The wireless network 100 may be a heterogeneous network including different types of base stations 110 such as macro base stations, pico base stations, femto base stations, or relay base stations. These different types of base stations 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 watt to 2 watts). In Figure 1In the example shown, BS110a may be a macro base station for macro cell 102a, BS110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102c. A base station may support one or more (e.g., three) cells. Network controller 130 may be coupled to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110. Network controller 130 may communicate with base stations 110 via a backhaul communication link. Base stations 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

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

[0052] In some examples, a cell may not necessarily be stationary, and the geographical area of a cell may move according to the location of a moving base station 110 (e.g., a mobile base station). In some examples, base stations 110 may be interconnected with each other or with one or more other base stations 110 or network nodes (not shown) in wireless network 100 using any suitable transport network via various types of backhaul interfaces such as a direct physical connection or a virtual network.

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

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

[0055] Some UEs 120 can be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. An MTC UE or eMTC UE can include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag, which can communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 can be considered Internet of Things (IoT) devices, or can be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 can be considered customer premises equipment. A UE 120 can be included inside an enclosure that houses components of the UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component can be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) can be operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0056] Generally, any amount of wireless network 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. The RAT can also be referred to as a radio technology or an air interface. The frequency can also be referred to as a carrier or a frequency channel. In a given geographical area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network can be deployed.

[0057] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., communicate with each other without using the base station 110 as an intermediate medium). For example, UE 120 can use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., can include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol) or a mesh network to communicate. In such examples, UE 120 can perform scheduling operations, resource selection operations, or other operations described elsewhere herein as performed by the base station 110.

[0058] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Similar naming issues sometimes occur in connection with FR2. Although different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band, FR2 is generally (interchangeably) referred to as the "millimeter wave" band in various documents and articles.

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

[0060] Considering the above examples, unless specifically stated otherwise, it should be understood that when used herein, the term "below 6 GHz" can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless specifically stated otherwise, it should be understood that when used herein, the term "millimeter wave" can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-1, or FR5, or can be within the EHF band. Frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) are considered modifiable, and the techniques described herein apply to those modified frequency ranges.

[0061] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive downlink control information (DCI) that schedules a downlink message for initial access communication and indicates a physical uplink control channel (PUCCH) resource for feedback for the downlink message. The communication manager 140 may obtain one or more subband physical resource block (PRB) offsets for transmitting feedback in an uplink subband of a subband full-duplex (SBFD) symbol associated with the common PUCCH resource. The communication manager 140 may transmit feedback in a first PRB for a first frequency hop in the uplink subband and in a second PRB for a second frequency hop in the uplink subband, at least in part based on the one or more subband PRB offsets.

[0062] In some aspects, communication manager 140 may receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. Communication manager 140 may select a PUCCH resource from a data structure including multiple PUCCH resources for transmission in an uplink subband of an SBFD symbol. Communication manager 140 may transmit feedback in the selected PUCCH resource.

[0063] In some aspects, communication manager 140 may receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. Communication manager 140 may select a set of PUCCH resources at least in part based on a slot type. Communication manager 140 may select a PUCCH resource at least in part based on an index within the set of PUCCH resources. Communication manager 140 may transmit feedback in a first PRB of a first frequency hop in an uplink subband of an SBFD symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

[0064] In some aspects, a network entity (e.g., base station 110) may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may transmit DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. Communication manager 150 may receive feedback in a first PRB of a first frequency hop in an uplink subband of an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0065] As indicated above, Figure 1 is provided as an example. Other examples may be different from the example described with respect to Figure 1 described.

[0066] Figure 2 is a diagram illustrating an example base station 110 that communicates with a UE 120 in a wireless network. Base station 110 may correspond to Figure 1 the base station 110 of. Similarly, UE 120 may correspond to Figure 1UE 120. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

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

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

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

[0070] One or more antennas (e.g., antennas 234a through 234t or antennas 252a through 252r) may include or may be included within one or more of the following: one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. The antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (within a single housing or multiple housings), a coplanar set of antenna elements, a non-coplanar set of antenna elements, or one or more antenna elements coupled to one or more transmit or receive components (such as Figure 2 one or more components) of

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

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

[0073] The controller / processor of a network entity (e.g., the controller / processor 240 of the base station 110), the controller / processor 280 of the UE 120, or Figure 2Any other component of may perform one or more techniques associated with a PRB offset for an uplink subband of an SBFD symbol, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, or Figure 2 any other component of may perform or direct, for example Figure 15 process 1500 of Figure 16 process 1600 of Figure 17 process 1700 of Figure 18 process 1800 of or the operation of other processes as described herein. The memories 242 and 282 may store data and program code for the base station 110 and the UE 120, respectively. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code or program code) for wireless communication. For example, when the one or more instructions are executed by one or more processors of the base station 110 or the UE 120 (e.g., executed directly, or after compilation, conversion, or interpretation), the one or more processors, the UE 120, or the base station 110 may be caused to perform or direct, for example Figure 15 process 1500 of Figure 16 process 1600 of Figure 17 process 1700 of Figure 18 process 1800 of or the operation of other processes as described herein. In some examples, executing the instructions may include running the instructions, converting the instructions, compiling the instructions, or interpreting the instructions, and so on.

[0074] In some aspects, a UE (e.g., UE 120) includes: means for receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message; means for obtaining one or more subband PRB offsets for transmitting feedback in an uplink subband of an SBFD symbol associated with the common PUCCH resource; and / or means for transmitting feedback in a first PRB for a first frequency hop in the uplink subband and in a second PRB for a second frequency hop in the uplink subband based at least in part on the one or more subband PRB offsets. The means for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0075] In some aspects, the UE includes: components for receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message; components for selecting a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of an SBFD symbol; and / or components for transmitting feedback in the selected PUCCH resource.

[0076] In some aspects, the UE includes: components for receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message; components for selecting a set of PUCCH resources at least partially based on a slot type; components for selecting a PUCCH resource at least partially based on an index within the set of PUCCH resources; and / or components for transmitting feedback in a first PRB of a first frequency hop in an uplink subband of an SBFD symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband. Components for the UE to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0077] In some aspects, a network entity (e.g., base station 110) includes: components for transmitting DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message; and / or components for receiving feedback in a first PRB of a first frequency hop in an uplink subband of an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband. In some aspects, components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0078] The deployment of a communication system, such as a 5G NR system, can be arranged with various components or constituent parts in various ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in an aggregated or disaggregated architecture. For example, a base station (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a disaggregated base station.

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

[0080] Base station type operations or network designs can consider the aggregation characteristics of base station functionality. For example, a disaggregated base station can be utilized in an IAB network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed individually. A disaggregated base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can achieve flexibility in network design. The individual units of a disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

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

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

[0083] As indicated above, Figure 2 Is provided as an example. Other examples may be different from the examples described with respect to Figure 2 Described examples.

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

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

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

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

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

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

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

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

[0092] As indicated above, Figure 3 is provided as an example. Other examples may be different from the examples described with respect to Figure 3 those described.

[0093] Figure 4 is a diagram illustrating an example of full-duplex communication 400 in accordance with the present disclosure. In some cases, a wireless communication device (such as a UE or a network entity) may support full-duplex operation. Full-duplex operation may include a wireless communication device transmitting and receiving almost simultaneously.

[0094] The UE may operate in an in-band full-duplex (FD) mode. In the in-band full-duplex mode, the UE may transmit and receive on the same time and frequency resources. The uplink and the downlink may share the same time and frequency resources. For example, in the first full-duplex communication 402, the time and frequency resources for the uplink may completely overlap with the time and frequency resources for the downlink. As another example, in the second full-duplex communication 404, the time and frequency resources for the uplink may partially overlap with the time and frequency resources for the downlink.

[0095] Full-duplex operation may include the SBFD mode. The SBFD mode may also be referred to as the sub-band frequency division duplex mode or the flexible duplex mode. The SBFD communication 406 shows that a wireless communication device can transmit and receive simultaneously (in the same SBFD time slot), but the wireless communication device can transmit and receive on different frequency domain resources. For example, a network entity can operate in the SBFD mode. The network entity can schedule a first UE to receive downlink communication in an SBFD time slot. The network entity can schedule a second UE to transmit uplink communication in the same SBFD time slot. However, the uplink communication may cause interference to the first UE that is receiving downlink communication. To solve this problem, the downlink time / frequency resources in the SBFD time slot can be separated from the uplink time / frequency resources in the SBFD time slot by a gap (e.g., in time or frequency), which can be used to reduce self-interference and improve latency and uplink coverage. The gap can be a frequency offset or a frequency gap (guard band) between the downlink time / frequency resources and the uplink time / frequency resources in the same SBFD time slot.

[0096] In some cases, the time slot mode may include a combination of downlink time slots, uplink time slots, or SBFD time slots.

[0097] As indicated above, Figure 4 is provided as an example. Other examples may be different from the examples described with respect to Figure 4 which are described.

[0098] Figure 5 is a diagram illustrating an example 500 of a time slot mode with an SBFD time slot according to the present disclosure.

[0099] A UE can use the configured time slot mode to transmit or receive communication. The configured time slot mode can include a combination of downlink time slots, uplink time slots, or SBFD time slots within a bandwidth part (BWP) for uplink (UL) and downlink (DL). Example 500 shows an SBFD time slot (SBFD symbols in the SBFD time slot), which can be used for operations in the radio resource control (RRC) connected state, where the UE maintains a connection established using RRC signaling. The time and frequency positions of the sub-bands for SBFD operation may not be known to the UE. In some examples, the UE can be an SBFD-aware UE, where the time and frequency positions of the sub-bands for SBFD operation are known to the SBFD-aware UE.

[0100] As indicated above, Figure 5 is provided as an example. Other examples may be different from the examples described with respect to Figure 5 which are described.

[0101] Figure 6FIG. 600 is an illustration example of communication in an uplink subband of an SBFD time slot according to the present disclosure.

[0102] A UE may transmit communication in an uplink resource, such as an uplink subband in an uplink time slot or an SBFD time slot. For example, the UE may receive downlink control information in a physical downlink control channel (PDCCH) communication, where DCI (e.g., DCI format 1_0) schedules physical downlink shared channel (PDSCH) communication (e.g., Msg4). The UE may transmit feedback for the PDSCH communication, such as a hybrid automatic repeat request (HARQ) acknowledgement (ACK) or negative acknowledgement (NACK). The UE may transmit the feedback in a PUCCH resource. The PUCCH resource may be a cell-specific PUCCH resource. The UE may extract cell-specific configuration (e.g., PUCCH-ConfigCommon) from a system information block (SIB) such as SIB1. There are 16 PUCCH resources, and the UE may determine the PUCCH resource with an index where N CCE is the number of command control elements (CCEs) in a control resource set (CORESET) received by the PDCCH using the DCI format, n CCE,0 is the index of the first CCE for PDCCH reception, and Δ PRI is the physical resource indicator (PRI) value (e.g., 3 bits) of the PUCCH resource indicator field of the DCI format. For example, index 0 may indicate PUCCH format 0, the first symbol at symbol 12, the number of symbols 2, the PRB offset 0, the initial channel state (CS) index set {0,3}, and the PRB allocation 8, while index 10 may indicate PUCCH format 1, the first symbol at symbol 4, the number of symbols 10, the PRB offset 4, the initial CS index set {0,3,6,9}, and the PRB allocation 4.

[0103] The PUCCH resource may involve frequency hopping. For example, for in-slot frequency hopping, where the first communication in a time slot (e.g., the first half of the symbols) is in the first PRB within the UL BWP of a component carrier (CC), and the second communication in the time slot (e.g., the second half of the symbols) is in the second PRB within the UL BWP, where the second PRB is at a different frequency from the first PRB (frequency hopping).

[0104] As indicated above, Figure 5 is provided as an example. Other examples may be different from the examples described with respect to Figure 5

[0105] Figure 6 ​FIG. 600 is an illustration of an example of PRBs in a UL subband according to the present disclosure.

[0106] A network entity and a UE (SBFD-aware UE) configured to use SBFD time slots may utilize an uplink subband for PUCCH transmission carrying feedback during initial access in an initial UL BWP. The feedback may include ACK / NACK (A / N) feedback for a downlink (DL) message (e.g., Msg4). The UE may apply frequency hopping for PUCCH transmission before receiving any dedicated UE configuration (except in the case of shared spectrum or unlicensed spectrum where the UE is configured with an interleaved mode). As shown in example 600, the UE may transmit feedback (the first half) in the first PRB 602 of the UL time slot and hop frequencies to transmit feedback (the second half) in the second PRB 604. PRB 602 and PRB 604 are within the full BWP and may be considered the first BWP PRB and the second BWP PRB, respectively. PRB 602 may be considered RB 0, and PRB 604 may be the highest RB.

[0107] However, a problem arises when PUCCH is triggered for an uplink subband in an SBFD time slot. For example, SBFD time slot 606 may include a UL subband 608 between DL subbands. The PRBs 602 and 604 used for frequency hopping are not within the frequency band (RBs) of the UL subband 608. That is, PRB 602 is not among the PRBs (e.g., PRB 610) within UL subband 608, and PRB 604 is not within the PRBs (e.g., PRB 612) within UL subband 608. As a result, the feedback may fail to be transmitted in the PUCCH resources, which may degrade communication and waste power, processing resources, and signaling resources.

[0108] As indicated above, Figure 6 is provided as an example. Other examples may be different from the example described with respect to Figure 6 FIG. 700 is an illustration of an example of PRB offset used with a UL subband according to the present disclosure.

[0109] Figure 7 is provided as an example. Other examples may be different from the example described with respect to

[0110] In accordance with various aspects described herein, a UE may be configured with a PRB offset (PRB sub-band offset) for use with sub-bands in an SBFD time slot. One or more PRB offsets may be used in conjunction with frequency hopping within a time slot. Example 700 illustrates an SBFD time slot 702 with a UL sub-band 704. PRB 706 and PRB 708 are within the BWP but outside the UL sub-band 704, or outside the frequency range (RB) of the UL sub-band 704. Example 700 illustrates that the UE may be configured to use a PRB offset 710 with PRB 708 to transmit feedback in PRB 712 (PRB 708 minus PRB offset 710). Similarly, the UE may be configured to use a PRB offset 714 with PRB 706 to transmit feedback in PRB 716 (PRB 706 plus PRB offset 714). Example 700 illustrates symmetric operation of the PRB offset for the UL sub-band 704, where PRB offset 710 and PRB offset 714 are the same.

[0111] Example 700 illustrates formulas for determining PRBs, such as for PRB 706, PRB 708, PRB 712, and PRB 716 within a time slot for PUCCH transmission. PRB offset 710 and / or PRB offset 714 may be expressed as If 0, the UE may determine the lowest PRB index for PUCCH transmission in the first hop (for PRB 716) as and determine the lowest PRB index for PUCCH transmission in the second hop (for PRB 716) as If 1, the UE may determine the lowest PRB index for PUCCH transmission in the first hop (for PRB 716) as and determine the lowest PRB index for PUCCH transmission in the second hop (for PRB 712) as Note that the UE may not apply the value for PUCCH transmission in the UL time slot and each PUCCH resource (including the PRBs for PUCCH transmission) may be configured with a specific (e.g., different) value for the PRB offset.

[0112] In some aspects, the PRB offset may be explicitly configured, such as via broadcast configuration or via uplink sub-band configuration. In some aspects, the UE may implicitly determine the PRB offset. For example, the PRB offset may represent the first RB in the UL sub-band relative to common RB 0. As another example, the PRB offset may represent the first RB in the UL sub-band relative to the first RB of the initial UL BWP.

[0113] By using the configured PRB offset used with the UL sub - band in the SBFD time slot, the UE can successfully send feedback in the PUCCH. This can improve communication and save power, processing resources, and signaling resources.

[0114] As indicated above, Figure 7 is provided as an example. Other examples may be different from the example Figure 7 described.

[0115] Figure 8 is a diagram illustrating Example 800 of a PRB offset used with a UL sub - band according to the present disclosure.

[0116] In some aspects, the UE may be configured with different PRB offsets. Example 800 shows two SBFD - specific PRB offsets for transmission in PUCCH resources within a UL sub - band PRB offset 802 is less than PRB offset 804. This can be applicable to scenarios where the UL sub - band is not centered at the middle of a time slot (e.g., configured at the side). Symmetry (mirroring) will not apply within the UL sub - band. If then the UE can determine the lowest PRB index for PUCCH transmission in the first hop (for PRB 716) as and the lowest PRB index for PUCCH transmission in the second hop (for PRB 712) as If then the UE can determine the lowest PRB index for PUCCH transmission in the first hop (for PRB 716) as and the lowest PRB index for PUCCH transmission in the second hop (for PRB 712) as Note that the UE may not apply the value for PUCCH transmission in the UL time slot and each PUCCH resource may be configured (or determined) with a specific (e.g., different) value for the PRB offset.

[0117] In some aspects, the PRB offset can be explicitly configured via broadcast configuration or via UL sub - band configuration. In some aspects, the UE can implicitly determine the PRB offset. For example, the PRB offset 804 for PRB 716 can be determined relative to the common RB 0. As another example, the PRB offset 804 for PRB 716 can be determined in UL sub - band 704 relative to PRB 706 of the initial UL BWP. The PRB offset 802 can be determined in UL sub - band 704 relative to the common RB 0. The PRB offset 802 for PRB 712 can also be determined relative to PRB 706 or PRB 708 of the initial UL BWP.

[0118] As indicated above, Figure 8 is provided as an example. Other examples may be different from the examples described with respect to Figure 8 the examples described.

[0119] Figure 9 is a diagram illustrating Example 900 of a PRB offset used with a UL sub - band in accordance with the present disclosure.

[0120] In some aspects, the PRBs within a UL sub - band can be based at least in part on a single PRB offset 902 and the size 904 of the UL sub - band. This can involve a mirror frequency hopping with respect to the UL sub - band. For example, for a first frequency hop, the UE can use the PRB offset 902 to map to the first PRB (PRB 716) in UL sub - band 704. The UE can use a mirror RB offset for a second frequency hop, which is based at least in part on the PRB offset 902 and the UL sub - band size 904. This can include using the PRB offset 902 for PRB716, using the PRB offset 902 plus the UL sub - band size 904 for PRB 712, or using PRB 716 plus the UL sub - band size 904.

[0121] As indicated above, Figure 9 is provided as an example. Other examples may be different from the examples described with respect to Figure 9 the examples described.

[0122] Figure 10 is a diagram illustrating Example 1000 of a PRB offset used with a UL sub - band in accordance with the present disclosure.

[0123] In some aspects, the UE may use an SBFD - specific RB offset that is mapped to the middle of UL sub - band 704. For example, the PRB offset 902 may be from PRB 706 to the center of UL sub - band 704. PRB 716 and PRB 712 may be mirror images of each other across the center of UL sub - band 704. For example, PRB 716 may be the PRB offset 902 of PRB 706 minus a part (e.g., half) of the UL sub - band size 904, and PRB 712 may be that part of the UL sub - band size 904 plus the PRB offset 902.

[0124] As indicated above, Figure 10 is provided as an example. Other examples may be different from the examples described with respect to Figure 10 the examples described.

[0125] Figure 11 is a diagram of Example 1100 illustrating a PRB offset used with a UL sub - band in accordance with the present disclosure.

[0126] Example 1100 shows another use of an SBFD - specific PRB offset configured to be used with a UL sub - band. Instead of (as shown in Example 1000) for PRB 712, PRB 712 is at least partially based on

[0127] As indicated above, Figure 11 is provided as an example. Other examples may be different from the examples described with respect to Figure 11 the examples described.

[0128] Figure 12 is a diagram 1200 of an example associated with using a PRB offset for a UL sub - band in accordance with the present disclosure. As Figure 12 shown, the network entity 1210 (e.g., base station 110) may communicate with the UE 1220 (e.g., UE 120). In some aspects, the network entity 1210 and the UE 1220 may be part of a wireless network (e.g., wireless network 100).

[0129] As shown by reference numeral 1225, network entity 1210 may send DCI that schedules a downlink message (e.g., PDSCH communication) for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. As shown by reference numeral 1230, UE 1220 may obtain one or more subband PRB offsets for sending feedback in a UL subband for an SBFD time slot (for one or more SBFD symbols in the SBFD time slot). UE 1220 may obtain one or more subband PRB offsets by receiving an indication of the one or more subband PRB offsets or by implicitly determining the one or more subband PRB offsets.

[0130] UE 1220 may send feedback in a first PRB for a first frequency hop in a UL subband and in a second PRB for a second frequency hop in an uplink subband at least partially based on the one or more subband PRB offsets. As shown by reference numeral 1235, UE 1220 may send feedback (e.g., the first half) in the first PRB for the first frequency hop. As shown by reference numeral 1240, UE 1220 may send feedback (e.g., the second half) in the second PRB for the second frequency hop.

[0131] As indicated above, Figure 12 is provided as an example. Other examples may be different from the examples described with respect to Figure 12 which are different from the examples described with respect to

[0132] Figure 13 is a diagram 1300 of an example associated with using a PRB offset for a UL subband in accordance with the present disclosure.

[0133] In some aspects, network entity 1210 may expand the number of PUCCH resources from 16 resources to 32 resources. The additional 16 PUCCH resources may be used for PUCCH transmission in a UL subband. Network entity 1210 may configure UE 1220 with a PRB offset mapped to a PRB in the UL subband. This enables an optimized configuration (e.g., PUCCH format, number of RBs, length) for PUCCH in the UL subband.

[0134] For example, UE 1220 may determine an index (i.e., 5 bits) of a PUCCH resource index at least partially based on: 3 bits based on Δ PRI (value of the PUCCH resource indicator field of the DCI format 3 bits), 1 bit based on the CCE index, and / or 1 bit based on the target time slot for PUCCH transmission. The PUCCH may be at least partially based on a time slot type, such as 1 (legacy) or 2 for SBFD, where n CCE,0ranges from 0 to (N CCE -1), and Δ PRI ranges from 0 to 7. Resource r PUCCH can be where SlotType–1 can be 0 or 16, can be 0 or 1, 2, and Δ PRI can be 0, 2, 4, 6, 8, 10, 12, or 14.

[0135] Example 1300 provides an example of using PUCCH resources with an extended amount for UL sub-bands. As shown by reference numeral 1325, network entity 1210 may send DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. As shown by reference numeral 1330, UE 1220 may select a PUCCH resource from a data structure including multiple PUCCH resources for transmission in the UL sub-band of the SBFD symbol. As shown by reference numeral 1335, UE 1220 may send feedback in the selected PUCCH resource, which is selected from the PUCCH resources for the UL sub-band.

[0136] By selecting from PUCCH resources specific to the UL sub-band in the SBFD time slot, the UE can successfully send feedback in the PUCCH. This can improve communication and save power, processing resources, and signaling resources.

[0137] As indicated above, Figure 13 is provided as an example. Other examples may be different from the examples described with respect to Figure 13

[0138] Figure 14 is a diagram 1400 of an example associated with using UL sub-bands according to the present disclosure.

[0139] Instead of extending the number of PUCCH resources to 32 resources, an additional 16 resources may be configured with an SBFD-specific common PUCCH resource set. There may be a first set of 16 PUCCH resources and a second set of 16 PUCCH resources. For example, n CCE,0 can be in the range of 0 to (N CCE -1), Δ PRI can be in the range of 0 to 7, and can be 0, 1, or 2. In some aspects, Δ PRI can be 0, 2, 4, 6, 8, 10, 12, or 14.

[0140] ​Using SBFD-specific PUCCH resource sets enables frequency hopping with PRB offsets and PRB allocations dedicated to SBFD. This can enable different power control configurations (e.g., for p0).

[0141] As shown by reference numeral 1425, network entity 1210 can send DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for that downlink message. As shown by reference numeral 1430, UE 1220 can select a PUCCH resource set at least in part based on the slot type. As shown by reference numeral 1435, UE 1220 can select a PUCCH resource at least in part based on an index within the PUCCH resource set.

[0142] UE 1220 can send feedback in a first PRB for a first frequency hop in a UL subband and in a second PRB for a second frequency hop in an uplink subband at least in part based on one or more subband PRB offsets. As shown by reference numeral 1440, UE 1220 can send feedback (e.g., the first half) in a first PRB for a first frequency hop. As shown by reference numeral 1445, UE 1220 can send feedback (e.g., the second half) in a second PRB for a second frequency hop.

[0143] As indicated above, Figure 14 is provided as an example. Other examples may be different from the example described with respect to Figure 14 .

[0144] Figure 15 is a diagram illustrating an example process 1500 performed by a UE, for example, in accordance with the present disclosure. Example process 1500 is an example where a UE (e.g., UE 120, UE 1220) performs operations associated with transmitting in a PRB in an uplink band of an SBFD symbol.

[0145] As Figure 15 shown, in some aspects, process 1500 can include receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for that downlink message (block 1510). For example, a UE (e.g., using Figure 19 the communication manager 1908 and / or the receiving component 1902 depicted) can receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for that downlink message, as described above in connection with Figures 4 to 14 .

[0146] As Figure 15As further shown, in some aspects, process 1500 may include obtaining one or more subband PRB offsets for transmitting feedback in an uplink subband of an SBFD symbol associated with a common PUCCH resource (block 1520). For example, a UE (e.g., using Figure 19 the depicted communication manager 1908, source component 1910, and / or receiving component 1902) may obtain one or more subband PRB offsets for transmitting feedback in an uplink subband of an SBFD symbol associated with a common PUCCH resource, as described above in connection with Figures 4 to 14 that which is described.

[0147] As Figure 15 further shown, in some aspects, process 1500 may include transmitting feedback in a first PRB for a first frequency hop in an uplink subband and in a second PRB for a second frequency hop in the uplink subband, at least in part based on one or more subband PRB offsets (block 1530). For example, a UE (e.g., using Figure 19 the depicted communication manager 1908 and / or transmitting component 1904) may transmit feedback in a first PRB for a first frequency hop in an uplink subband and in a second PRB for a second frequency hop in the uplink subband, at least in part based on one or more subband PRB offsets, as described above in connection with Figures 4 to 14 that which is described.

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

[0149] In a first aspect, obtaining one or more subband PRB offsets includes receiving an indication of the one or more subband PRB offsets.

[0150] In a second aspect, alone or in combination with the first aspect, the indication is included in a broadcast configuration or an uplink subband configuration.

[0151] In a third aspect, alone or in combination with one or more of the first and second aspects, obtaining one or more subband PRB offsets includes determining the one or more subband PRB offsets, at least in part based on a common RB zero or an RB of an initial uplink bandwidth part.

[0152] In a fourth aspect, alone or in combination with one or more of the first through third aspects, obtaining one or more subband PRB offsets includes obtaining the one or more subband PRB offsets specified in stored configuration information.

[0153] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more subband PRB offsets include a subband PRB offset, and the first PRB is a subband PRB offset from a first BWP PRB outside an uplink subband, and the second PRB is a subband PRB offset from a second BWP PRB outside an uplink subband.

[0154] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more subband PRB offsets include a first subband PRB offset and a second subband PRB offset, and the first PRB is a first subband PRB offset from a first BWP PRB outside the uplink subband, and the second PRB is a second subband PRB offset from a second BWP PRB outside the uplink subband.

[0155] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the one or more subband PRB offsets include a subband PRB offset, and the first PRB is a subband PRB offset from a first BWP PRB outside an uplink subband, and the second PRB is based at least in part on the size of the uplink subband plus the first PRB.

[0156] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the one or more subband PRB offsets include a subband PRB offset from a first BWP PRB outside the uplink subband to the center of the uplink subband, wherein the first PRB is at least partially based on the center of the uplink subband minus a portion of the size of the uplink subband, and the second PRB is at least partially based on a portion of the size of the uplink subband plus the center of the uplink subband.

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

[0158] Figure 16 1 is a diagram illustrating an example process 1600 performed, for example, by a network entity according to the present disclosure. Example process 1600 is an example in which a network entity (e.g., base station 110, network entity 1210) performs operations associated with receiving in a PRB in an uplink frequency band of a SBFD symbol.

[0159] like Figure 16As shown, in some aspects, process 1600 may include transmitting DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message (block 1610). For example, a network entity (e.g., using Figure 20 the depicted communication manager 2008 and / or transmission component 2004) may transmit DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message, as described above in connection with Figures 4 to 14 the description.

[0160] As Figure 16 further shown, in some aspects, process 1600 may include receiving feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband (block 1620). For example, a network entity (e.g., using Figure 20 the depicted communication manager 2008 and / or receiving component 2002) may receive feedback in a first PRB of a first frequency hop in an uplink subband for an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband, as described above in connection with Figures 4 to 14 the description.

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

[0162] In a first aspect, process 1600 includes transmitting an indication of one or more subband PRB offsets associated with locating the first PRB and the second PRB.

[0163] In a second aspect, either alone or in combination with the first aspect, the first PRB is a subband PRB offset from a first BWP PRB outside the uplink subband, and the second PRB is a subband PRB offset from a second BWP PRB outside the uplink subband.

[0164] In a third aspect, either alone or in combination with one or more of the first and second aspects, the first PRB is a first subband PRB offset from a first BWP PRB outside the uplink subband, and the second PRB is a second subband PRB offset from a second BWP PRB outside the uplink subband.

[0165] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first PRB is a subband PRB offset from a first BWP PRB outside an uplink subband, and the second PRB is based at least in part on the size of the uplink subband plus the first PRB.

[0166] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first PRB is based at least in part on the center of the uplink subband minus a portion of the size of the uplink subband, and the second PRB is based at least in part on a portion of the size of the uplink subband plus the center of the uplink subband.

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

[0168] Figure 17 is a diagram illustrating an example process 1700 performed, for example, by a UE in accordance with the present disclosure. Example process 1700 is an example of a UE (eg, UE 120, UE 1220) performing operations associated with transmitting in a PRB in an uplink frequency band of a SBFD symbol.

[0169] like Figure 17 As shown, in some aspects, process 1700 may include receiving a DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message (block 1710). For example, a UE (e.g., using Figure 19 The depicted communication manager 1908 and / or receiving component 1902) may receive a DCI that schedules a downlink message for an initial access communication and indicates a common PUCCH resource for feedback for the downlink message, as described above in conjunction with Figures 4 to 14 as described.

[0170] like Figure 17 As further shown, in some aspects, process 1700 may include selecting a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of a SBFD symbol (block 1720). Figure 19 The depicted communication manager 1908 and / or selection component 1912) may select a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of a SBFD symbol, as described above in conjunction with Figures 4 to 14as described.

[0171] As Figure 17 further shown in, in some aspects, process 1700 may include transmitting feedback in a selected PUCCH resource (block 1730). For example, a UE (e.g., using Figure 19 the depicted communication manager 1908 and / or transmission component 1904) may transmit feedback in the selected PUCCH resource, as described above in connection with Figures 4 to 14 as described.

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

[0173] In a first aspect, the PUCCH resource is associated with a first PRB offset and a second PRB offset, and the first PRB of the first frequency hop is the first PRB offset from the first BWP PRB outside the uplink subband, and the second PRB of the second frequency hop is the second PRB offset from the second BWP PRB outside the uplink subband.

[0174] In a second aspect, alone or in combination with the first aspect, selecting the PUCCH resource includes selecting a PUCCH resource index based at least in part on the slot type.

[0175] In a third aspect, alone or in combination with one or more of the first and second aspects, selecting the PUCCH resource includes selecting a PUCCH resource index based at least in part on the PUCCH resource indicator field in the DCI.

[0176] In a fourth aspect, alone or in combination with one or more of the first to third aspects, selecting the PUCCH resource includes selecting a PUCCH resource index based at least in part on the control channel element index.

[0177] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the data structure includes more than 16 PUCCH resource indexes.

[0178] Although Figure 17 example blocks of process 1700 are shown, in some aspects, process 1700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to those depicted. Additionally or alternatively, two or more blocks of process 1700 may be executed in parallel. Figure 17

[0179] Figure 18 ​FIG. is an illustration of an example process 1800 performed, for example, by a UE in accordance with the present disclosure. Example process 1800 is an example in which a UE (e.g., UE 120, UE 1220) performs operations associated with transmitting in a PRB in an uplink band of an SBFD symbol.

[0180] As Figure 18 shown, in some aspects, process 1800 may include receiving DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message (block 1810). For example, a UE (e.g., using Figure 19 the depicted communication manager 1908 and / or receiving component 1902) may receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message, as described above in connection with Figures 4 to 14 described.

[0181] As Figure 18 further shown, in some aspects, process 1800 may include selecting a PUCCH resource set at least in part based on a slot type (block 1820). For example, a UE (e.g., using Figure 19 the depicted communication manager 1908 and / or selecting component 1912) may select a PUCCH resource set at least in part based on a slot type, as described above in connection with Figures 4 to 14 described.

[0182] As Figure 18 further shown, in some aspects, process 1800 may include selecting a PUCCH resource at least in part based on an index within the PUCCH resource set (block 1830). For example, a UE (e.g., using Figure 19 the depicted communication manager 1908 and / or selecting component 1912) may select a PUCCH resource at least in part based on an index within the PUCCH resource set, as described above in connection with Figures 4 to 14 described.

[0183] As Figure 18 further shown, in some aspects, process 1800 may include transmitting feedback in a first PRB of a first frequency hop in an uplink subband of a subband full-duplex symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband (block 1840). For example, a UE (e.g., using Figure 19The depicted communication manager 1908 and / or transmission component 1904) may transmit feedback in a first PRB of a first frequency hop in an uplink subband for a subband full-duplex symbol associated with a selected PUCCH resource and in a second PRB for a second frequency hop in the uplink subband, as described above in connection with Figures 4 to 14 as described.

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

[0185] In a first aspect, a PUCCH resource is associated with a first PRB offset and a second PRB offset, and the first PRB is a first PRB offset from a first BWP PRB outside the uplink subband, and the second PRB is a second PRB subband offset from a second BWP PRB outside the uplink subband.

[0186] In a second aspect, alone or in combination with the first aspect, a PUCCH resource set is specific to an SBFD time slot, and selecting a PUCCH resource set includes selecting the PUCCH resource set based at least in part on the SBFD time slot type.

[0187] Although Figure 18 illustrates example blocks of process 1800, in some aspects, process 1800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to those depicted. Additionally or alternatively, two or more blocks of process 1800 may be executed in parallel. Figure 18 is a diagram of an example apparatus 1900 for wireless communication in accordance with the present disclosure. Apparatus 1900 may be a UE (e.g., UE 120, UE 1220), or a UE may include apparatus 1900. In some aspects, apparatus 1900 includes a receiving component 1902 and a transmission component 1904, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1900 may communicate with another apparatus 1906 (such as a UE, a base station, or another wireless communication device) using receiving component 1902 and transmission component 1904. As further shown, apparatus 1900 may include a communication manager 1908. Communication manager 1908 may control and / or otherwise manage one or more operations of receiving component 1902 and / or transmission component 1904. In some aspects, communication manager 1908 may include in connection with

[0188] Figure 19 Figure 2 ​One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 1908 can be or be similar to Figure 1 and Figure 2 the depicted communication manager 140. For example, in some aspects, the communication manager 1908 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1908 can include a receiving component 1902 and / or a transmitting component 1904. The communication manager 1908 can include a parameter component 1910 and / or a selection component 1912, etc.

[0189] In some aspects, the device 1900 can be configured to perform one or more operations described herein in connection with Figures 1 to 14 . Additionally or alternatively, the device 1900 can be configured to perform one or more processes described herein, such as Figure 15 process 1500 of Figure 17 process 1700 of Figure 18 process 1800 of Figure 19 or combinations thereof. In some aspects, Figure 2 the depicted device 1900 and / or one or more components can include one or more components of the UE described in connection with Figure 19 . Additionally or alternatively, Figure 2 one or more of the depicted components can be implemented within one or more components described in connection with

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

[0191] The transmitting component 1904 can send communications to the device 1906, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1900 can generate communications and can provide the generated communications to the transmitting component 1904 for transmission to the device 1906. In some aspects, the transmitting component 1904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications, and can send the processed signals to the device 1906. In some aspects, the transmitting component 1904 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 In some aspects, the transmitting component 1904 can be co-located with the receiving component 1902 in a transceiver.

[0192] In some aspects, the receiving component 1902 can receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The source component 1910 and / or the receiving component 1902 can obtain one or more subband PRB offsets for transmitting feedback in an uplink subband of an SBFD symbol associated with the common PUCCH resource. The transmitting component 1904 can transmit feedback at least partially based on the one or more subband PRB offsets in a first PRB for a first frequency hop in the uplink subband and in a second PRB for a second frequency hop in the uplink subband.

[0193] In some aspects, the receiving component 1902 can receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The selection component 1912 can select a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of an SBFD symbol. The transmitting component 1904 can transmit feedback in the selected PUCCH resource.

[0194] In some aspects, the receiving component 1902 can receive DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The selection component 1912 can select a set of PUCCH resources at least partially based on the slot type. The selection component 1912 can select a PUCCH resource at least partially based on an index within the set of PUCCH resources. The transmitting component 1904 can transmit feedback in a first PRB for a first frequency hop in an uplink subband of an SBFD symbol associated with the selected PUCCH resource and in a second PRB for a second frequency hop in the uplink subband.

[0195] Figure 19 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 19 the components shown. Additionally, Figure 19 two or more of the components shown may be implemented within a single component, or Figure 19 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 19 a set of the (one or more) components shown may perform one or more functions described as being performed by Figure 19 another set of the components shown.

[0196] Figure 20 is a diagram of an example apparatus 2000 for wireless communication in accordance with the present disclosure. Apparatus 2000 may be a network entity, or a network entity may include apparatus 2000. In some aspects, apparatus 2000 includes a receiving component 2002 and a transmitting component 2004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 2000 may communicate with another apparatus 2006 (such as a UE, a base station, or another wireless communication device) using receiving component 2002 and transmitting component 2004. As further shown, apparatus 2000 may include a communication manager 2008. Communication manager 2008 may control and / or otherwise manage one or more operations of receiving component 2002 and / or transmitting component 2004. In some aspects, communication manager 2008 may include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entity described in conjunction with Figure 2 Communication manager 2008 may be or be similar to Figure 1 and Figure 2 the communication manager 150 depicted. For example, in some aspects, communication manager 2008 may be configured to perform one or more of the functions described as being performed by communication manager 150. In some aspects, communication manager 2008 may include receiving component 2002 and / or transmitting component 2004. Communication manager 2008 may include a resource component 2010, and so on.

[0197] In some aspects, apparatus 2000 may be configured to perform one or more operations described herein in connection with FIG. 200. Additionally or alternatively, apparatus 2000 may be configured to perform one or more of the processes described herein, such as Figure 16 process 1600. In some aspects, apparatus 2000 and / or Figure 20 one or more of the components shown may include those described in conjunction with Figure 2One or more components of the described network entity. Additionally or alternatively, Figure 20 One or more of the illustrated components may be implemented in conjunction with Figure 2 One or more of the described components. Additionally or alternatively, one or more components in a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0198] The receiving component 2002 may receive communications from the device 2006, such as reference signals, control information, data communications, or combinations thereof. The receiving component 2002 may provide the received communications to one or more other components of the device 2000. In some aspects, the receiving component 2002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signal to the one or more other components of the device 2000. In some aspects, the receiving component 2002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the described network entity in conjunction with Figure 2 Described.

[0199] The transmitting component 2004 may transmit communications to the device 2006, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 2000 may generate the communications and may provide the generated communications to the transmitting component 2004 for transmission to the device 2006. In some aspects, the transmitting component 2004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signal to the device 2006. In some aspects, the transmitting component 2004 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the described network entity in conjunction with Figure 2 Described. In some aspects, the transmitting component 2004 may be co-located with the receiving component 2002 in a transceiver.

[0200] In some aspects, the transmitting component 2004 may transmit DCI that schedules a downlink message for initial access communication and indicates a common PUCCH resource for feedback for the downlink message. The resource component 2010 may determine the common PUCCH resource. The receiving component 2002 may receive feedback in a first PRB of a first frequency hop in an uplink subband of an SBFD symbol associated with the common PUCCH resource and in a second PRB of a second frequency hop in the uplink subband. The transmitting component 2004 may transmit an indication of one or more subband PRB offsets associated with locating the first PRB and the second PRB.

[0201] Figure 20 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to those shown. Additionally, Figure 20 two or more of the components shown may be implemented within a single component, or Figure 20 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 20 a set of the (one or more) components shown may perform one or more functions described as being performed by another set of components shown. Figure 20 Figure 20

[0202]

[0203] An overview of some aspects of the present disclosure is provided below:

[0203] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving downlink control information (DCI) that schedules a downlink message for initial access communication and indicates a common physical uplink control channel (PUCCH) resource for feedback for the downlink message; obtaining one or more subband physical resource block (PRB) offsets for transmitting the feedback in an uplink subband of a subband full-duplex (SBFD) symbol associated with the common PUCCH resource; and transmitting the feedback in a first PRB of a first frequency hop in the uplink subband and in a second PRB of a second frequency hop in the uplink subband at least in part based on the one or more subband PRB offsets.

[0204] Aspect 2: The method according to aspect 1, wherein obtaining one or more subband PRB offsets comprises receiving an indication of the one or more subband PRB offsets.

[0205] Aspect 3: The method according to any one of aspects 1 to 2, wherein the indication is included in a broadcast configuration or an uplink subband configuration.

[0206] Aspect 4: The method according to any one of Aspects 1 to 3, wherein obtaining the one or more subband PRB offsets includes determining the one or more subband PRB offsets at least in part based on RBs of a common RB zero or an initial uplink bandwidth part.

[0207] Aspect 5: The method according to any one of Aspects 1 to 4, wherein obtaining the one or more subband PRB offsets includes obtaining the one or more subband PRB offsets specified in the stored configuration information.

[0208] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the one or more subband PRB offsets include a subband PRB offset, and wherein the first PRB is the subband PRB offset with respect to a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is the subband PRB offset with respect to a second BWP PRB outside the uplink subband.

[0209] Aspect 7: The method according to any one of Aspects 1 to 5, wherein the one or more subband PRB offsets include a first subband PRB offset and a second subband PRB offset, and wherein the first PRB is the first subband PRB offset with respect to a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is the second subband PRB offset with respect to a second BWP PRB outside the uplink subband.

[0210] Aspect 8: The method according to any one of Aspects 1 to 5, wherein the one or more subband PRB offsets include a subband PRB offset, and wherein the first PRB is the subband PRB offset with respect to a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is at least in part based on the size of the uplink subband plus the first PRB.

[0211] Aspect 9: The method according to any one of Aspects 1 to 5, wherein the one or more subband PRB offsets include a subband PRB offset from a first bandwidth part (BWP) PRB outside the uplink subband to the center of the uplink subband, wherein the first PRB is at least in part based on the center of the uplink subband minus a part of the size of the uplink subband, and wherein the second PRB is at least in part based on the part of the size of the uplink subband plus the center of the uplink subband.

[0212] Aspect 10: A method for wireless communication performed by a network entity, comprising: transmitting downlink control information (DCI), the downlink control information (DCI) scheduling a downlink message for initial access communication and indicating a physical uplink control channel (PUCCH) resource for feedback for the downlink message; and receiving the feedback in a first physical resource block (PRB) of a first frequency hopping in an uplink subband for a subband full-duplex (SBFD) symbol associated with the common PUCCH resource and in a second PRB of a second frequency hopping in the uplink subband.

[0213] Aspect 11: The method according to aspect 10, further comprising: transmitting an indication of one or more subband PRB offsets associated with locating the first PRB and the second PRB.

[0214] Aspect 12: The method according to any one of aspects 10 to 11, wherein the first PRB is a subband PRB offset from a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is the subband PRB offset from a second BWP PRB outside the uplink subband.

[0215] Aspect 13: The method according to any one of aspects 10 to 11, wherein the first PRB is the first subband PRB offset from a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is the second subband PRB offset from a second BWP PRB outside the uplink subband.

[0216] Aspect 14: The method according to any one of aspects 10 to 11, wherein the first PRB is a subband PRB offset from a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is at least partially based on the size of the uplink subband plus the first PRB.

[0217] Aspect 15: The method according to any one of aspects 10 to 11, wherein the first PRB is at least partially based on the center of the uplink subband minus a part of the size of the uplink subband, and wherein the second PRB is at least partially based on the part of the size of the uplink subband plus the center of the uplink subband.

[0218] Aspect 16: The method according to any one of Aspects 10 to 15 further includes: selecting a Physical Uplink Control Channel (PUCCH) resource associated with a first Physical Resource Block (PRB) offset and a second PRB offset, and wherein the first PRB of the first frequency hop is the first PRB offset from a first Bandwidth Part (BWP) PRB outside the uplink subband, and the second PRB of the second frequency hop is the second PRB offset from a second BWP PRB outside the uplink subband.

[0219] Aspect 17: The method according to Aspect 16, wherein selecting the PUCCH resource includes selecting a PUCCH resource index at least partially based on the slot type.

[0220] Aspect 18: The method according to Aspect 16, wherein selecting the PUCCH resource includes selecting a PUCCH resource index at least partially based on a PUCCH resource indicator field in Downlink Control Information (DCI).

[0221] Aspect 19: The method according to Aspect 16, wherein selecting the PUCCH resource includes selecting a PUCCH resource index at least partially based on a Control Channel Element index.

[0222] Aspect 20: The method according to Aspect 16, wherein selecting the PUCCH resource includes selecting the PUCCH resource from a data structure including more than 16 PUCCH resource indexes.

[0223] Aspect 21: The method according to Aspect 16, wherein selecting the PUCCH resource includes selecting the PUCCH resource from a set of PUCCH resources, wherein the set of PUCCH resources is specific to a Subband Full Duplex (SBFD) slot, and wherein the one or more processors are configured individually or jointly to cause the UE to select the set of PUCCH resources at least partially based on the SBFD slot type.

[0224] Aspect 22: A method of wireless communication performed by a User Equipment (UE) includes: receiving Downlink Control Information (DCI) that schedules a downlink message for initial access communication and indicates a Physical Uplink Control Channel (PUCCH) resource for feedback for the downlink message; selecting a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of a Subband Full Duplex (SBFD) symbol; and transmitting the feedback on the selected PUCCH resource.

[0225] Aspect 23: The method according to aspect 22, wherein the PUCCH resource is associated with a first physical resource block (PRB) offset and a second PRB offset, and wherein the first PRB of the first frequency hopping is the first PRB offset from the first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB of the second frequency hopping is the second PRB offset from the second BWP PRB outside the uplink subband.

[0226] Aspect 24: The method according to any one of aspects 22 to 23, wherein selecting the PUCCH resource includes selecting a PUCCH resource index based at least in part on the slot type.

[0227] Aspect 25: The method according to any one of aspects 22 to 24, wherein selecting the PUCCH resource includes selecting a PUCCH resource index based at least in part on a PUCCH resource indicator field in DCI.

[0228] Aspect 26: The method according to any one of aspects 22 to 25, wherein selecting the PUCCH resource includes selecting a PUCCH resource index based at least in part on a control channel element index.

[0229] Aspect 27: The method according to any one of aspects 22 to 26, wherein the data structure includes more than 16 PUCCH resource indexes.

[0230] Aspect 28: A method of wireless communication performed by a user equipment (UE), comprising: receiving downlink control information (DCI), the downlink control information (DCI) scheduling a downlink message for initial access communication and indicating a physical uplink control channel (PUCCH) resource for feedback for the downlink message; selecting a set of PUCCH resources based at least in part on the slot type; selecting a PUCCH resource based at least in part on an index within the set of PUCCH resources; and transmitting the feedback in a first physical resource block (PRB) of a first frequency hopping in an uplink subband for a subband full-duplex symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hopping in the uplink subband.

[0231] Aspect 29: The method according to aspect 28, wherein the PUCCH resource is associated with a first PRB offset and a second PRB offset, and wherein the first PRB is the first PRB offset from the first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is the second PRB subband offset from the second BWP PRB outside the uplink subband.

[0232] Aspect 30: The method according to any one of aspects 28 to 29, wherein the PUCCH resource set is specific to a sub-band full-duplex (SBFD) time slot, and wherein selecting the PUCCH resource set includes selecting the PUCCH resource set at least in part based on the SBFD time slot type.

[0233] Aspect 31: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform the method according to one or more of aspects 1 to 30.

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

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

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

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

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

[0239] As used herein, the term "component" is intended to be broadly construed as either hardware or a combination of hardware and software. "Software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented with either hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specific control hardware or software code used to implement these systems or methods does not limit the aspects. Accordingly, the operations and behaviors of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods at least in part based on the description herein.

[0240] As used herein, depending on the context, "meeting a threshold" may mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0241] Although specific combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of the aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of each aspect includes each dependent claim in combination with every other claim in the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items (which includes a single member). By way of 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 multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0242] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Additionally, as used herein, the article "a" is intended to include one or more items and may be used interchangeably with "one or more." Further, as used herein, the article "the" is intended to include one or more items referred to in connection with the article "the" and may be used interchangeably with "one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." If only one item is intended to be referred to, the phrase "only one" or similar language will be used. Additionally, as used herein, the terms "has," "owns," "possesses," and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "at least partially based on" unless otherwise explicitly stated. Additionally, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless otherwise explicitly stated (e.g., if used in conjunction with "either" or "only one").

Claims

1. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and the one or more processors being configured, individually or jointly, to cause the UE to: receive downlink control information (DCI), the downlink control information (DCI) scheduling a downlink message for initial access communication and indicating a common physical uplink control channel (PUCCH) resource for feedback for the downlink message; obtain one or more subband physical resource block (PRB) offsets for transmitting the feedback in an uplink subband of a subband full-duplex (SBFD) symbol associated with the common PUCCH resource; and transmit the feedback in a first PRB for a first frequency hop in the uplink subband and in a second PRB for a second frequency hop in the uplink subband, at least in part based on the one or more subband PRB offsets.

2. The UE according to claim 1, wherein, in order to obtain the one or more sub-band PRB offsets, the one or more processors are configured, individually or jointly, to cause the UE to receive an indication of the one or more sub-band PRB offsets.

3. The UE according to claim 1, wherein the indication is included in a broadcast configuration or an uplink sub-band configuration.

4. The UE according to claim 1, wherein, in order to obtain the one or more sub-band PRB offsets, the one or more processors are configured, individually or jointly, to cause the UE to determine the one or more sub-band PRB offsets based at least in part on a common RB zero or an RB of an initial uplink bandwidth part.

5. The UE according to claim 1, wherein, in order to obtain the one or more sub-band PRB offsets, the one or more processors are configured, individually or jointly, to cause the UE to obtain the one or more sub-band PRB offsets specified in the stored configuration information.

6. The UE according to claim 1, wherein the one or more sub-band PRB offsets include a sub-band PRB offset, and wherein the first PRB is the sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band, and the second PRB is the sub-band PRB offset from a second BWP PRB outside the uplink sub-band.

7. The UE according to claim 1, wherein the one or more sub-band PRB offsets include a first sub-band PRB offset and a second sub-band PRB offset, and wherein the first PRB is the first sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band, and the second PRB is the second sub-band PRB offset from a second BWP PRB outside the uplink sub-band.

8. The UE according to claim 1, wherein the one or more sub-band PRB offsets include a sub-band PRB offset, and wherein the first PRB is the sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band, and the second PRB is at least partially based on the size of the uplink sub-band plus the first PRB.

9. The UE according to claim 1, wherein the one or more sub-band PRB offsets include a sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band to the center of the uplink sub-band, wherein the first PRB is at least partially based on the center of the uplink sub-band minus a portion of the size of the uplink sub-band, and wherein the second PRB is at least partially based on the portion of the size of the uplink sub-band plus the center of the uplink sub-band.

10. The UE according to claim 9, wherein the one or more processors are configured, individually or jointly, to cause the UE to transmit an indication of one or more sub-band PRB offsets associated with locating the first PRB and the second PRB.

11. A network entity for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and the one or more processors being configured, individually or jointly, to cause the network entity to: transmit downlink control information (DCI), the downlink control information (DCI) scheduling a downlink message for initial access communication and indicating a common physical uplink control channel (PUCCH) resource for feedback for the downlink message; and receive the feedback in a first physical resource block (PRB) for a first frequency hop in an uplink subband of a subband full-duplex (SBFD) symbol associated with the common PUCCH resource and in a second PRB for a second frequency hop in the uplink subband.

12. The network entity according to claim 11, wherein the first PRB is a sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band, and the second PRB is a sub-band PRB offset from a second BWP PRB outside the uplink sub-band.

13. The network entity according to claim 11, wherein the first PRB is a first sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band, and the second PRB is a second sub-band PRB offset from a second BWP PRB outside the uplink sub-band.

14. The network entity according to claim 11, wherein the first PRB is a sub-band PRB offset from a first bandwidth part (BWP) PRB outside the uplink sub-band, and the second PRB is at least partially based on the size of the uplink sub-band plus the first PRB.

15. The network entity according to claim 11, wherein the first physical resource block (PRB) is at least partially based on the center of the uplink subband minus a portion of the size of the uplink subband, and wherein the second PRB is at least partially based on the portion of the size of the uplink subband plus the center of the uplink subband.

16. The network entity according to claim 15, wherein the one or more processors are configured, individually or jointly, to cause the network entity to select a physical uplink control channel (PUCCH) resource associated with a first PRB offset and a second PRB offset, and wherein the first PRB of the first frequency hopping is the first PRB offset from a first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB of the second frequency hopping is the second PRB offset from a second BWP PRB outside the uplink subband.

17. The network entity according to claim 16, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the network entity to select a PUCCH resource index at least partially based on the slot type.

18. The network entity according to claim 16, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the network entity to select a PUCCH resource index at least partially based on the PUCCH resource indicator field in the downlink control information (DCI).

19. The network entity according to claim 16, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the network entity to select a PUCCH resource index at least partially based on the control channel element index.

20. The network entity according to claim 16, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the network entity to select the PUCCH resource from a data structure including more than 16 PUCCH resource indexes.

21. The network entity according to claim 16, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the network entity to select the PUCCH resource from a set of PUCCH resources, wherein the set of PUCCH resources is specific to a subband full duplex (SBFD) slot, and wherein the one or more processors are configured, individually or jointly, to cause the network entity to select the set of PUCCH resources at least partially based on the SBFD slot type.

22. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and the one or more processors being configured, individually or jointly, to cause the UE to: receive downlink control information (DCI), the downlink control information (DCI) scheduling a downlink message for initial access communication and indicating a common physical uplink control channel (PUCCH) resource for feedback for the downlink message; select a PUCCH resource from a data structure including a plurality of PUCCH resources for transmission in an uplink subband of a subband full-duplex (SBFD) symbol; and transmit the feedback in the PUCCH resource.

23. The UE according to claim 22, wherein the PUCCH resource is associated with a first physical resource block (PRB) offset and a second PRB offset, and wherein the first PRB of the first frequency hopping is the first PRB offset from the first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB of the second frequency hopping is the second PRB offset from the second BWP PRB outside the uplink subband.

24. The UE according to claim 22, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the UE to select a PUCCH resource index at least partially based on the slot type.

25. The UE according to claim 22, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the UE to select a PUCCH resource index at least partially based on the PUCCH resource indicator field in the DCI.

26. The UE according to claim 22, wherein, in order to select the PUCCH resource, the one or more processors are configured, individually or jointly, to cause the UE to select a PUCCH resource index at least partially based on the control channel element index.

27. The UE according to claim 22, wherein the data structure includes more than 16 PUCCH resource indexes.

28. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and the one or more processors being configured, individually or jointly, to cause the UE to: receive downlink control information (DCI), the downlink control information (DCI) scheduling a downlink message for initial access communication and indicating a common physical uplink control channel (PUCCH) resource for feedback for the downlink message; select a set of PUCCH resources, at least in part based on a slot type; Select a PUCCH resource based at least in part on an index within the PUCCH resource set; and Transmit the feedback in a first physical resource block (PRB) of a first frequency hop in an uplink subband of a subband full-duplex symbol associated with the selected PUCCH resource and in a second PRB of a second frequency hop in the uplink subband.

29. The UE according to claim 28, wherein the PUCCH resource is associated with a first PRB offset and a second PRB offset, and wherein the first PRB is the first PRB offset from the first bandwidth part (BWP) PRB outside the uplink subband, and the second PRB is the second PRB subband offset from the second BWP PRB outside the uplink subband.

30. The UE according to claim 28, wherein the PUCCH resource set is specific to a subband full duplex (SBFD) time slot, and wherein, in order to select the PUCCH resource set, the one or more processors are configured, individually or jointly, to cause the UE to select the PUCCH resource set based at least in part on the SBFD time slot type.

Images