Signaling for sub-band full duplex operation

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive configuration information identifying a scheduling request (SR) resource configuration, where the SR resource configuration includes: a physical uplink control channel (PUCCH) resource configured in a non-subband full duplex (SBFD) slot and an SBFD slot, or a first PUCCH resource configured in an SBFD slot and a second PUCCH resource configured in a non-SBFD slot. The UE can transmit a SR message in an SBFD slot or a non-SBFD slot using the SR resource configuration. Numerous other aspects are described.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication, and more particularly to techniques, apparatus and methods for signaling for subband full-duplex operation. Background Technology

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

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

[0004] Some aspects described herein relate to a method for wireless communication performed by a User Equipment (UE). The method may include receiving configuration information for an Identifier Scheduling Request (SR) resource configuration, wherein the SR resource configuration includes: Physical Uplink Control Channel (PUCCH) resources configured in non-subband full-duplex (non-SBFD) time slots and SBFD time slots, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. The method may include using the SR resource configuration to transmit SR messages in the SBFD time slot or the non-SBFD time slot.

[0005] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include transmitting configuration information identifying an SR resource configuration, wherein the SR resource configuration includes: PUCCH resources configured in a non-SBFD time slot and an SBFD time slot, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. The method may include using the SR resource configuration to receive SR messages in the SBFD time slot or the non-SBFD time slot.

[0006] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive configuration information identifying SR resource configurations, wherein the SR resource configurations include: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. When executed by one or more processors of the UE, the set of instructions enables the UE to transmit SR messages using the SR resource configurations in the SBFD time slot or the non-SBFD time slot.

[0007] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to send configuration information identifying an SR resource configuration, wherein the SR resource configuration includes: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. When executed by one or more processors of the network node, the set of instructions enables the network node to receive SR messages in the SBFD time slot or the non-SBFD time slot using the SR resource configuration.

[0008] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive configuration information identifying SR resource configurations, wherein the SR resource configurations include: PUCCH resources configured in non-SBFD time slots and SBFD time slots, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. The one or more processors may be configured to use the SR resource configurations to transmit SR messages in the SBFD time slot or the non-SBFD time slot.

[0009] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit configuration information identifying an SR resource configuration, wherein the SR resource configuration includes: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. The one or more processors may be configured to use the SR resource configuration to receive SR messages in the SBFD time slot or the non-SBFD time slot.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving configuration information identifying an SR resource configuration, wherein the SR resource configuration includes: PUCCH resources configured in a non-SBFD time slot and an SBFD time slot, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. The apparatus may include components for transmitting SR messages using the SR resource configuration in the SBFD time slot or the non-SBFD time slot.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting configuration information identifying an SR resource configuration, wherein the SR resource configuration includes: PUCCH resources configured in a non-SBFD time slot and an SBFD time slot, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot. The apparatus may include components for receiving SR messages in the SBFD time slot or the non-SBFD time slot using the SR resource configuration.

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

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

[0014] While aspects and implementations have been described herein by way of example, those skilled in the art will understand that additional specific implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, various implementations and / or devices can be produced via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to a use case or application, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the implementations protected and described by the claims. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with different sizes, shapes, and constructions. Attached Figure Description

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

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

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

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

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

[0020] Figure 5 This is a diagram illustrating examples of physical channels and reference signals in a wireless network according to this disclosure.

[0021] Figures 6A to 6C This is a diagram illustrating an example of signaling associated with subband full-duplex operation according to this disclosure.

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

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

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

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

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

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

[0028] Some communication systems allow uplink and downlink communication to occur within the same set of resources. For example, a frequency band can be divided into a set of subbands, and one or more subbands within a subband can be used for both uplink and downlink communication. Such subbands may be referred to as "subband full-duplex" or "SBFD" resources. In some scenarios, some subbands can be assigned for SBFD operations, and other subbands can be assigned for non-SBFD operations. In non-SBFD operations, a subband can be assigned as either an uplink subband or a downlink subband, but the two cannot be assigned concurrently.

[0029] A scheduling request (SR) is a physical layer message that a user equipment (UE) can send to a network node to request the network node to send uplink permission. Uplink permission may include permission for resources used by the UE to send Physical Uplink Shared Channel (PUCCH) communication. The UE can use the allocated Physical Uplink Control Channel (PUCCH) resources to send the SR. Each logical channel of the communication system may have a single associated SR configuration. The UE may have a Media Access Control (MAC) entity that uses a set of SR configurations for a different set of use cases. Each SR configuration may be associated with an SR disable timer, a maximum SR transmission value, or mapped PUCCH resources, etc., and is described in more detail herein. In SBFD slots, uplink resources can be configured in the uplink band of the SBFD slot. However, in scenarios where SBFD slots are configured, the network node may not have a signaling format or a set of messages for configuring PUCCH resources used for SR transmission.

[0030] Some aspects described herein can provide signaling for SBFD operation. For example, a network node can configure the UE using SR resource configurations that include PUCCH resources configured in both non-SBFD and SBFD time slots. For example, a network node can send configuration information conveying the SR resource configuration including PUCCH resources configured in both non-SBFD and SBFD time slots. Additionally or alternatively, a network node can configure the UE using separate SR configurations (and associated mappings from logical channels to SR configurations) for both SBFD and non-SBFD time slots. For example, a network node can send configuration information conveying a first SR resource configuration with PUCCH resources in SBFD time slots and a second SR resource configuration with PUCCH resources in non-SBFD time slots.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by configuring SBFD resources and / or non-SBFD resources, the described techniques can be used to transmit SR communications in a communication system that includes both SBFD and non-SBFD resources. By providing signaling for configuring one or more SR configurations, the described techniques can be used to improve performance by allowing both SBFD and non-SBFD time slots.

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

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

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

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

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

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

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

[0039] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations conforming to O-RAN Alliance standards), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

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

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

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

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

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

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

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

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

[0048] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, or may be included in the following: access terminal, another terminal, mobile station, or subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

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

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

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

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

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

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

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

[0056] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive configuration information identifying scheduling request (SR) resource configurations, wherein the SR resource configurations include: physical uplink control channel (PUCCH) resources configured in non-subband full-duplex (non-SBFD) time slots and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot; and transmitting SR messages in SBFD time slots or non-SBFD time slots using the SR resource configurations. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send configuration information identifying SR resource configurations, wherein the SR resource configurations include: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot; and receive SR messages in SBFD or non-SBFD time slots using the SR resource configurations. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] In some aspects, UE 120 includes components for receiving configuration information identifying SR resource configurations, wherein the SR resource configurations include: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot; and / or components for transmitting SR messages in SBFD or non-SBFD time slots using the SR resource configurations. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0089] In some aspects, network node 110 includes components for transmitting configuration information identifying SR resource configurations, wherein the SR resource configuration includes: PUCCH resources configured in non-SBFD time slots and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot; and / or components for receiving SR messages in SBFD time slots or non-SBFD time slots using the SR resource configuration. Components enabling the network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

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

[0091] Figure 4 These are illustrations of examples 400, 405, and 410 of full-duplex communication in a wireless network according to this disclosure. "Full-duplex communication" in a wireless network refers to simultaneous bidirectional communication between devices in the wireless network. For example, a UE operating in full-duplex mode can transmit uplink communication and receive downlink communication at the same frequency (e.g., in the same time slot or the same symbol). "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., downlink communication only or uplink communication only) between devices at a given time (e.g., in a given time slot or a given symbol). When a network node operates in full-duplex mode, the UE may be aware that the network node is operating in full-duplex mode (in which case, the UE may be a UE aware of sub-band full-duplex (SBFD)) or may not be aware that the network node is operating in full-duplex mode.

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

[0093] like Figure 4As further illustrated, Example 410 shows an example of SBFD communication, which may also be referred to as "Subband Frequency Division Duplex (SBFDD)" or "Flexible Duplex." In SBFD, network nodes can transmit (on the downlink) and receive (on the uplink) in overlapping portions of frequency bands, and can transmit across the entire frequency band (on the downlink). Guard bands may exist to limit or reduce leakage power between adjacent frequencies. In some examples, network nodes can operate across the entire frequency band that serves as the downlink band and configure a portion of that band as an uplink band (e.g., partially overlapping with the downlink band). Network nodes can support both transmission and reception in the overlapping portions of the frequency bands and can perform interference cancellation when transmission and reception occur simultaneously.

[0094] As indicated above, Figure 4 This is provided as an example. Other examples may be provided relative to... Figure 4 The examples described are different.

[0095] Figure 5 This is a diagram illustrating example 500 of physical channels and reference signals in a wireless network according to this disclosure. For example... Figure 5 As shown, the downlink channel and downlink reference signal can carry information from network node 110 to UE 120, and the uplink channel and uplink reference signal can carry information from UE 120 to network node 110.

[0096] As shown in the figure, downlink channels may include a Physical Downlink Control Channel (PDCCH) carrying downlink control information (DCI), a Physical Downlink Shared Channel (PDSCH) carrying downlink data, or a Physical Broadcast Channel (PBCH) carrying system information, etc. In some examples, PDSCH communication may be scheduled by PDCCH communication. Further as shown in the figure, uplink channels may include a Physical Uplink Control Channel (PUCCH) carrying uplink control information (UCI), a Physical Uplink Shared Channel (PUSCH) carrying uplink data, or a Physical Random Access Channel (PRACH) for initial network access, etc. In some examples, UE 120 may send acknowledgment (ACK) or negative acknowledgment (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0097] As further shown in the figure, downlink reference signals may include synchronization signal blocks (SSBs), channel state information (CSI) reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), or phase tracking reference signals (PTRS), etc. As also shown in the figure, uplink reference signals may include sounding reference signals (SRS), DMRS, or PTRS, etc.

[0098] The SSB can carry information for initial network acquisition and synchronization, such as the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH, and PBCH DMRS. The SSB is sometimes referred to as the synchronization signal / PBCH (SS / PBCH) block. In some examples, network node 110 can transmit multiple SSBs on multiple corresponding beams, and the SSBs can be used for beam selection.

[0099] CSI-RS can carry information for downlink channel estimation (e.g., downlink CSI acquisition), which can be used for scheduling, link adaptation, or beam management, etc. Network node 110 can configure a set of CSI-RS for UE 120, and UE 120 can measure the configured set of CSI-RS. Based at least in part on these measurements, UE 120 can perform channel estimation and can report channel estimation parameters to network node 110 (e.g., in a CSI report), such as Channel Quality Indicator (CQI), Pre-decoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), Rank Indicator (RI), or Reference Signal Received Power (RSRP), etc. Network node 110 can use CSI reports to select transmission parameters for downlink communication to UE 120, such as the number of transmission layers (e.g., rank), pre-decoding matrix (e.g., pre-decoder), modulation and decoding scheme (MCS), or refinement of downlink beams (e.g., using beam refinement or beam management procedures), etc.

[0100] The DMRS can carry information used to estimate the radio channel for demodulating the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of the DMRS can be specific to the physical channel it is used to estimate. The DMRS is UE-specific, can be beamformed, can be confined to scheduled resources (e.g., not transmitted over broadband), and can be transmitted only when necessary. As shown, the DMRS is used for both downlink and uplink communication.

[0101] PTRS can carry information for compensating oscillator phase noise. Typically, phase noise increases with the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter-wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communication (e.g., on PDSCH) and uplink communication (e.g., on PUSCH).

[0102] The PRS may carry information for improving the Observed Time Difference of Arrival (OTDOA) positioning performance of the UE 120 by performing timing or ranging measurements based on signals transmitted by network node 110. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped diagonally with frequency and time offsets to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). Generally, the PRS may be designed to improve the detectability of the UE 120, which may need to detect downlink signals from multiple neighboring network nodes to perform OTDOA-based positioning. Therefore, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells) and may report the Reference Signal Time Difference (RSTD) based on the OTDOA measurements associated with the PRS received from the multiple cells. In some examples, network node 110 may then calculate the positioning of the UE 120 based on the RSTD measurements reported by the UE 120.

[0103] The SRS can carry information for uplink channel estimation, which can be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. Network node 110 can configure one or more SRS resource sets for UE 120, and UE 120 can transmit SRS on the configured SRS resource sets. The SRS resource sets can have configurable uses, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. Network node 110 can measure the SRS, perform channel estimation at least in part based on these measurements, and use the SRS measurements to configure communication with UE 120.

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

[0105] A scheduling request (SR) is a physical layer message that a UE can send to a network node to request the network node to send uplink permission. Uplink permission may include permission for resources used by the UE to send PUSCH communication. The UE can use the allocated PUSCH resources to send the SR. Each logical channel of the communication system may have a single associated SR configuration. The UE may have a Media Access Control (MAC) entity that uses a set of SR configurations for a set of different use cases. Each SR configuration may be associated with an SR disable timer, a maximum SR transmission value, or mapped PUSCH resources, etc., and is described in more detail herein. In SBFD slots, uplink resources can be configured in the uplink band of the SBFD slot. However, in scenarios where SBFD slots are configured, the network node may not have a signaling format or a set of messages for configuring PUSCH resources for SR transmission.

[0106] Some aspects described herein can provide signaling for SBFD operation. For example, a network node can configure the UE using SR resource configurations that include PUCCH resources configured in both non-SBFD and SBFD time slots. For example, a network node can send configuration information conveying the SR resource configuration including PUCCH resources configured in both non-SBFD and SBFD time slots. Additionally or alternatively, a network node can configure the UE using separate SR configurations (and associated mappings from logical channels to SR configurations) for both SBFD and non-SBFD time slots. For example, a network node can send configuration information conveying a first SR resource configuration with PUCCH resources in SBFD time slots and a second SR resource configuration with PUCCH resources in non-SBFD time slots.

[0107] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by configuring SBFD resources and / or non-SBFD resources, the described techniques can be used to transmit SR communications in a communication system that includes both SBFD and non-SBFD resources. By providing signaling for configuring one or more SR configurations, the described techniques can be used to improve performance by allowing both SBFD and non-SBFD time slots.

[0108] Figures 6A to 6C This is a diagram illustrating example 600 associated with signaling used for SBFD operation according to this disclosure. For example... Figure 6A As shown, Example 600 includes communication between network node 110 and UE 120.

[0109] like Figure 6AFurthermore, as shown by reference numeral 610, UE 120 can receive configuration information from network node 110. For example, UE 120 can receive information identifying SR resource configurations. In this case, UE 120 can receive an information element (IE) including a list of SR resource configurations, which identifies one or more SR resource identifiers, one or more SR identifiers, or one or more PUCCH resource identifiers, etc.

[0110] In some aspects, UE 120 may receive information identifying SR resource configurations, which include PUCCH resources configured in non-SBFD time slots and PUCCH resources configured in SBFD time slots. In this case, the SR resource configuration is associated with PUCCH resources of the configured type and may include a scheduling request identifier, a PUCCH resource identifier (for non-SBFD time slots), and a PUCCH resource identifier for SBFD (for SBFD time slots). In some aspects, the SR resource configuration may be associated with a configured SR identifier space. In some aspects, a configured mapping may exist between logical channels and SR configurations. For example, network node 110 may configure, and UE 120 may apply, a single mapping from logical channels to SR configurations across PUCCH resources in non-SBFD and SBFD time slots. Therefore, UE 120 may transmit SRs on PUCCH resources configured in non-SBFD or SBFD time slots according to the SR configuration. In some aspects, network node 110 may configure SR resource configurations associated with PUCCH resources configured in non-SBFD time slots. In this scenario, network node 110 can also utilize the PUCCH resources in the SBFD time slot to configure SR resource configuration.

[0111] As an example, such as Figure 6B As shown, the resource configuration may include a first PUCCH resource 650 for SR identifier 1 and a second PUCCH resource 652 for SR identifier 2. For example... Figure 6B Furthermore, as shown by reference numeral 654, both the first PUCCH resource 650 and the second PUCCH resource 652 are scheduled in SBFD slots assigned for both the downlink (D) and uplink (U). Similarly, as shown by reference numeral 656, both the first PUCCH resource 650 and the second PUCCH resource 652 are scheduled in non-SBFD slots assigned only for the uplink.

[0112] In some respects, UE 120 may receive information identifying different SR configurations for different time slots. For example, UE 120 may receive a first SR configuration for a non-SBFD time slot and a second SR configuration for an SBFD time slot. In this case, network node 110 may configure a separate set of SR configurations for SBFD time slots and may configure different mappings from logical channels to SR configurations. In other words, when network node 110 wants to use a non-SBFD time slot for a first service and an SBFD time slot for a second service, network node 110 may configure different SR configurations for different time slot types to suit different services. As an example, network node 110 may configure Ultra Reliable Low Latency Communication (URLLC) (e.g., to achieve low latency) on both SBFD and non-SBFD time slots, configure Enhanced Multimedia Broadband (eMBB) on non-SBFD time slots, and configure traffic offloading on SBFD time slots. Therefore, network node 110 may allocate PUCCH resources within both SBFD and non-SBFD time slots to suit the resource utilization assigned to the corresponding service. In some respects, network node 110 can be configured, and UE 120 can use, logical channel mapping. For example, a single logical channel can be mapped to a single SR configuration associated with a non-SBFD timeslot, and in some examples, another SR configuration associated with an SBFD timeslot may be included. In this case, network node 110 can configure a logical channel to be associated with only one SR configuration that is specific to the SBFD timeslot.

[0113] As an example, such as Figure 6C As shown, the resource configuration may include a first PUCCH resource 660 for SR identifier 1 and a second PUCCH resource 662 for SR identifier 2. For example... Figure 6C Furthermore, as shown by reference numeral 664, only the first PUCCH resource 660 is scheduled in the SBFD slots assigned for both the downlink (D) and uplink (U). In contrast, as shown by reference numeral 666, only the second PUCCH resource 662 is scheduled in non-SBFD slots assigned only for the uplink.

[0114] In some respects, UE 120 may receive information identifying SR configurations via specific types of messages. For example, network node 110 may send Radio Resource Control (RRC) signaling identifying one or more SR configurations. In some respects, UE 120 may receive SR configuration activation signaling. For example, when UE 120 receives multiple SR configurations via RRC signaling, UE 120 may (e.g., via another RRC signaling message, a Media Access Control (MAC) Control Element (CE) signal, or a Layer 1 signal) receive activation signaling associated with selecting an SR configuration from among the multiple SR configurations.

[0115] In some respects, UE 120 can be configured using dedicated SR resources. For example, network node 110 can configure SR resources in the SBFD time slot for specific use cases, such as for beam fault recovery (BFR) transmission, listen-before-tell (LBT) transmission, or for position measurement gap (PosMG) request transmission. In this case, when UE 120 triggers SR transmission and transmits the SR on the dedicated SR resource, network node 110 can receive explicit information (or implicitly inferred information) identifying the purpose of the SR. Based on the received SR, network node 110 can provide the corresponding uplink permission to UE 120. In some respects, network node 110 can configure dedicated SR resources for UE 120 by using SR identifier extensions or by identifying additional PUCCH resources in the SBFD time slot associated with the configured SR identifier.

[0116] In some aspects, the UE 120 can be configured with an SR counter ( sr-Transmax ) and / or SR timer ( sr- ProhibitTimer For example, UE 120 may receive SR configuration associated with the configuration of an SR counter and / or an SR disable timer. In some aspects, UE 120 may configure the SR counter and SR disable timer for SR transmissions in both non-SBFD and SBFD time slots. In this case, when an SR transmission is triggered, UE 120 may increment the SR transmission counter on the PUCCH resources in both the non-SBFD and SBFD time slots. Additionally or alternatively, UE 120 may configure the SR counter and / or SR disable timer in conjunction with logical channels.

[0117] Therefore, UE 120 can be configured using a logical channel with a single SR configuration and PUCCH resources on both SBFD and non-SBFD time slots, and the SR counter and SR disable timer can be associated with and communicated by the single SR configuration. Alternatively, UE 120 can be configured using a logical channel with one or two SR configurations, each configuring PUCCH resources on a single type of time slot (e.g., SBFD or non-SBFD), and the SR counter and SR disable timer are communicated in each SR configuration. Alternatively, UE 120 can be configured using a logical channel with one or two SR configurations, each configuring PUCCH resources on a single type of time slot, and the SR counter and SR disable timer can share the SR configuration of the single logical channel.

[0118] like Figure 6AFurthermore, as shown by reference numeral 620, UE 120 may send SR communication to network node 110. For example, UE 120 may send SR communication in a PUCCH resource associated with an SR configuration configured by network node 110 for UE 120. Based on the receipt of SR communication by network node 110, network node 110 may send uplink permission to UE 120 to provide resources for subsequent communication.

[0119] In some aspects, UE 120 can select an SR configuration for an SBFD time slot from multiple SR configurations configured for UE 120 on a single logical channel. For example, UE 120 can select an SR configuration based on one or more selection rules. In one example, the selection rule may include UE 120 being configured to use an SR resource configured in all SR configurations associated with a single logical channel. In another example, the selection rule may include UE 120 being configured to select the earliest PUCCH resource mapped to an SR resource in the time domain, and in some aspects, it may be configured to use a PUCCH resource in SRs configured in the same time slot type. In another example, UE 120 can determine the SR resource from the SR configuration for a non-SBFD time slot or for an SBFD time slot (e.g., regardless of the time slot order). In another example, UE 120 may be configured such that if a separate SR configuration is configured for an SBFD time slot (e.g., via RRC signaling), UE 120 (e.g., via RRC signaling, MAC CE signaling, or Layer 1 signaling) receives a subsequent network indication to activate one or more SR configurations for the logical channel.

[0120] In some respects, UE 120 can handle failures associated with SR, such as Figure 6AAnd further illustrated by reference numeral 630 in the accompanying drawings. For example, UE 120 may increment the SR counter for a specific time slot type (e.g., non-SBFD or SBFD) based on SR transmission in a specific time slot type. In other words, when UE 120 attempts to transmit an SR in an SBFD time slot, UE 120 may increment the SR counter for the SBFD time slot, and when UE 120 attempts to transmit an SR in a non-SBFD time slot, the UE may increment a different SR counter for the non-SBFD time slot. In this case, when the SR counter meets a configured threshold (e.g., the counter increments to a specific value), UE 120 may send an indication to release the PUCCH. For example, UE 120 may notify the RRC entity to release the configuration of PUCCH resources, release the probe reference signal (SRS) configured on a specific time slot type (e.g., the SR counter meets a threshold), clear the PUSCH resources of the semi-persistent (SP) channel state information (CSI) reference signal, and clear any resources configured for semi-persistent scheduling (SPS) or configuration-granted (CG) transmission on a specific time slot type.

[0121] Additionally or alternatively, when UE 120 detects an SR failure based on an SR counter shared between non-SBFD time slot SR transmissions and SBFD time slot SR transmissions, UE 120 may instruct the RRC entity to release the PUCCH, release the SRS configured on all serving cells, clear the PUSCH resources for SP-CSI, and clear any SPS or CG transmissions for all serving cells. Alternatively, UE 120 may instruct the RRC to release the PUCCH, release the SRS configured for a single time slot type (e.g., based on the configuration used to select which time slot type), clear the PUSCH resources for SP-CSI, and clear any SPS or CG transmissions configured for a single time slot type. In this case, UE 120 may select a single time slot type (e.g., based on a configuration such as UE 120 releasing physical (PHY) resources configured in the SBFD time slot before the non-SBFD time slot). Additionally or alternatively, a single time slot type may be selected based on a received indication (e.g., from network node 110) or a configured default value.

[0122] Based on the detection of an SR failure, UE 120 may initiate a Random Access Channel (RACH) procedure on a special cell (SpCell) (e.g., which may include a primary cell (PCCell) and a primary-secondary cell (PSCell)) and cancel one or more pending or queued SR transmissions. In some aspects, UE 120 may use selected RACH resources to perform the RACH procedure. For example, when an SR counter is configured within an SR configuration for a specific time slot type, UE 120 may select RACH resources configured for that specific time slot type. Alternatively, UE 120 may be configured to select RACH resources configured in either time slot type, such as RACH resources in the earliest RACH timing (RO) of the time slot type. Additionally or alternatively, when an SR counter is configured in an SR configuration for two time slot types, UE 120 may select RACH resources in either time slot type. In this scenario, UE 120 may select a RACH resource in any slot type based on the earliest (e.g., first available) RO or a received network indication (e.g., received from a network node via RRC, Downlink Control Information (DCI), or MAC CE signaling). Alternatively, UE 120 may select a RACH resource based on a priority factor. For example, for an SBFD-aware UE, a RACH resource configured in an SBFD slot may have a higher selection priority than a RACH resource configured in a non-SBFD slot. Alternatively, UE 120 may select a dedicated physical RACH (PRACH) resource configured for SBFD as the first resource for indication, and may select an RO in any slot as the second resource for subsequent indication.

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

[0124] Figure 7 This is a diagram illustrating an example process 700 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 700 is an example in which a device or UE (e.g., UE 120) performs operations associated with signaling for SBFD operation.

[0125] like Figure 7 As shown, in some aspects, process 700 may include receiving configuration information identifying SR resource configuration (block 710). For example, the UE (e.g., using...) Figure 9The depicted receiving component 902 and / or communication manager 906 can receive configuration information identifying SR resource configurations, as described above. In some aspects, the SR resource configuration includes: PUCCH resources configured in non-SBFD time slots and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot, as described above.

[0126] like Figure 7 Further, as shown, in some aspects, process 700 may include sending SR messages in SBFD or non-SBFD time slots using SR resource configuration (box 720). For example, the UE (e.g., using...) Figure 9 The transmitting component 904 and / or the communication manager 906 described above can be configured to transmit SR messages in SBFD or non-SBFD time slots using SR resources.

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

[0128] In a first aspect, the SR resource configuration includes a first configuration and a second configuration, the first configuration being associated with a first SR identifier including a first PUCCH resource, and the second configuration being associated with a second SR identifier including a second PUCCH resource.

[0129] In the second aspect, either alone or in combination with the first aspect, a mapping of logical channels to SR configurations is applied across PUCCH resources in non-SBFD and SBFD time slots.

[0130] In the third aspect, either alone or in combination with one or more of the first and second aspects, a single logical channel is mapped to a first PUCCH resource associated with a non-SBFD time slot and to a second PUCCH resource associated with an SBFD time slot.

[0131] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the SR resource configuration is based at least in part on one or more selection criteria relating to the following: logical channel mapping, the occurrence of the earliest PUCCH resource mapped to the SR resource, the slot type, UE configuration, or received indications.

[0132] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the SR counter or SR disable timer is applicable to SR transmission in both non-SBFD time slots and SBFD time slots.

[0133] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the configuration information indicates the configuration of the SR counter or SR disable timer for the logical channel.

[0134] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the SR counter increments across non-SBFD time slots and SBFD time slots.

[0135] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 700 includes detecting an SR failure associated with the SR transmission counter, triggering a set of SR failure actions, and initiating a random access channel procedure.

[0136] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the random access channel resources used in the random access channel procedure are configured based on the SR transmission counter and associated with the duplex type.

[0137] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, sending an SR message includes sending an SR message on a dedicated SR resource, and process 700 includes receiving uplink permission based on the transmission of the SR message on the dedicated SR resource.

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

[0139] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 800 is an example in which a device or network node (e.g., network node 110) performs operations associated with signaling for SBFD operations.

[0140] like Figure 8 As shown, in some aspects, process 800 may include sending configuration information identifying the SR resource configuration (box 810). For example, a network node (e.g., using...) Figure 10 The transmitting component 1004 and / or the communication manager 1006 depicted may transmit configuration information identifying SR resource configurations, as described above. In some aspects, the SR resource configuration includes: PUCCH resources configured in non-SBFD time slots and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot.

[0141] like Figure 8 As further shown, in some aspects, process 800 may include receiving SR messages in SBFD or non-SBFD time slots using SR resource configuration (box 820). For example, network nodes (e.g., using...) Figure 10 The described receiving component 1002 and / or communication manager 1006 can be configured to receive SR messages in SBFD or non-SBFD time slots using SR resources, as described above.

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

[0143] In a first aspect, the SR resource configuration includes a first configuration and a second configuration, the first configuration being associated with a first SR identifier including a first PUCCH resource, and the second configuration being associated with a second SR identifier including a second PUCCH resource.

[0144] In the second aspect, either alone or in combination with the first aspect, a mapping of logical channels to SR configurations is applied across PUCCH resources in non-SBFD and SBFD time slots.

[0145] In the third aspect, either alone or in combination with one or more of the first and second aspects, a single logical channel is mapped to a first PUCCH resource associated with a non-SBFD time slot and to a second PUCCH resource associated with an SBFD time slot.

[0146] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the SR resource configuration is used for SBFD slots in conjunction with at least one of the following: logical channel mapping, the occurrence of the earliest PUCCH resource mapped to the SR resource, slot type, UE configuration, or received indication.

[0147] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the SR counter or SR disable timer is applicable to SR transmission in both non-SBFD time slots and SBFD time slots.

[0148] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the configuration information indicates the configuration of the SR counter or SR disable timer for the logical channel.

[0149] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the SR counter increments across non-SBFD time slots and SBFD time slots.

[0150] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 800 includes detecting an SR failure associated with the SR transmission counter, triggering a set of SR failure actions, and initiating a random access channel procedure.

[0151] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the random access channel resources used in the random access channel procedure are configured based on the SR transmission counter and associated with the duplex type.

[0152] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, receiving an SR message includes receiving an SR message on a dedicated SR resource, and process 800 includes sending uplink permission based on the reception of the SR message on the dedicated SR resource.

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

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

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

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

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

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

[0159] The receiving component 902 can receive configuration information identifying SR resource configurations, wherein the SR resource configurations include: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot. The transmitting component 904 can use the SR resource configurations to transmit SR messages in either an SBFD or non-SBFD time slot. The communication manager 906 can detect SR failures associated with the SR transmission counter. The communication manager 906 can trigger a set of SR failure actions. The communication manager 906 can initiate a random access channel procedure.

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

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

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

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

[0164] Transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1008. In some aspects, one or more other components of device 1000 may generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1008. In some aspects, transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1008. In some aspects, transmitting component 1004 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1004 may co-located with the receive component 1002 in one or more transceivers.

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

[0166] The transmitting component 1004 can transmit configuration information identifying SR resource configurations, wherein the SR resource configurations include: PUCCH resources configured in both non-SBFD and SBFD time slots, or a first PUCCH resource configured in an SBFD time slot and a second PUCCH resource configured in a non-SBFD time slot. The receiving component 1002 can use the SR resource configurations to receive SR messages in either an SBFD or non-SBFD time slot. The communication manager 1006 can detect SR failures associated with the SR transmission counter. The communication manager 1006 can trigger a set of SR failure actions. The communication manager 1006 can initiate a random access channel procedure.

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

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

[0169] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: receiving configuration information of an identifier scheduling request (SR) resource configuration, wherein the SR resource configuration includes: physical uplink control channel (PUCCH) resources configured in a non-subband full-duplex (SBFD) time slot and a SBFD time slot, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot; and transmitting an SR message in the SBFD time slot or the non-SBFD time slot using the SR resource configuration.

[0170] Aspect 2: According to the method of aspect 1, the SR resource configuration includes a first configuration and a second configuration, the first configuration being associated with a first SR identifier including the first PUCCH resource, and the second configuration being associated with a second SR identifier including the second PUCCH resource.

[0171] Aspect 3: The method according to any one of Aspects 1 to 2, wherein a mapping of logical channels to SR configurations is applied across the non-SBFD time slots and the PUCCH resources in the SBFD time slots.

[0172] Aspect 4: The method according to any one of Aspects 1 to 3, wherein a single logical channel is mapped to a first PUCCH resource associated with the non-SBFD time slot and to a second PUCCH resource associated with the SBFD time slot.

[0173] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the SR resource configuration is selected for the SBFD slot based at least in part on one or more selection criteria relating to: logical channel mapping, the occurrence of the earliest PUCCH resource mapped to the SR resource, slot type, UE configuration, or received indication.

[0174] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the SR counter or SR disable timer is applicable to the SR transmission in the non-SBFD time slot and the SBFD time slot.

[0175] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the configuration information indicates the configuration of an SR counter or SR disable timer for a logical channel.

[0176] Aspect 8: According to the method of aspect 7, wherein the SR counter increments across non-SBFD time slots and SBFD time slots.

[0177] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: detecting an SR failure associated with an SR transmission counter; triggering a set of SR failure actions; and initiating a random access channel procedure.

[0178] Aspect 10: According to the method of aspect 9, the random access channel resources used for the random access channel procedure are based on the configuration of the SR transmission counter and associated with the duplex type.

[0179] Aspect 11: The method according to any one of Aspects 1 to 10, wherein sending the SR message includes sending the SR message on a dedicated SR resource, and wherein the method further includes receiving uplink permission based on the sending of the SR message on the dedicated SR resource.

[0180] Aspect 12: A method for wireless communication performed by a network node, the method comprising: sending configuration information for an identifier scheduling request (SR) resource configuration, wherein the SR resource configuration includes: physical uplink control channel (PUCCH) resources configured in a non-subband full-duplex (SBFD) time slot and a SBFD time slot, or a first PUCCH resource configured in the SBFD time slot and a second PUCCH resource configured in the non-SBFD time slot; and receiving SR messages in the SBFD time slot or the non-SBFD time slot using the SR resource configuration.

[0181] Aspect 13: According to the method of aspect 12, the SR resource configuration includes a first configuration and a second configuration, the first configuration being associated with a first SR identifier including the first PUCCH resource, and the second configuration being associated with a second SR identifier including the second PUCCH resource.

[0182] Aspect 14: The method according to any one of Aspects 12 to 13, wherein a mapping of logical channels to SR configurations is applied across the non-SBFD time slots and the PUCCH resources in the SBFD time slots.

[0183] Aspect 15: The method according to any one of Aspects 12 to 14, wherein a single logical channel is mapped to a first PUCCH resource associated with the non-SBFD time slot and to a second PUCCH resource associated with the SBFD time slot.

[0184] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the SR resource configuration is used for the SBFD slot in combination with at least one of the following: logical channel mapping, the occurrence of the earliest PUCCH resource mapped to the SR resource, slot type, UE configuration, or received indication.

[0185] Aspect 17: The method according to any one of Aspects 12 to 16, wherein the SR counter or SR disable timer is adapted for SR transmission in the non-SBFD time slot and the SBFD time slot.

[0186] Aspect 18: The method according to any one of Aspects 12 to 17, wherein the configuration information indicates the configuration of an SR counter or SR disable timer for a logical channel.

[0187] Aspect 19: The method according to aspect 18, wherein the SR counter increments across non-SBFD time slots and SBFD time slots.

[0188] Aspect 20: The method according to any one of Aspects 12 to 19, the method further comprising: detecting an SR failure associated with an SR transmission counter; triggering a set of SR failure actions; and initiating a random access channel procedure.

[0189] Aspect 21: According to the method of aspect 20, the random access channel resources used for the random access channel procedure are based on the configuration of the SR transmission counter and associated with the duplex type.

[0190] Aspect 22: The method according to any one of Aspects 12 to 21, wherein receiving the SR message includes receiving the SR message on a dedicated SR resource, and wherein the method further includes sending uplink grant based on the reception of the SR message on the dedicated SR resource.

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

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

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

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

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

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

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

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

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

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

[0201] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

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

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

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the UE to: Receive configuration information for the identifier scheduling request (SR) resource configuration, wherein the SR resource configuration includes: Physical uplink control channel (PUCCH) resources configured in non-subband full-duplex (non-SBFD) time slots and SBFD time slots, or The first PUCCH resource configured in the SBFD time slot and the second PUCCH resource configured in the non-SBFD time slot; and The SR resource configuration is used to send SR messages in the SBFD time slot or the non-SBFD time slot.

2. The UE of claim 1, wherein the SR resource configuration includes a first configuration and a second configuration, the first configuration being associated with a first SR identifier including the first PUCCH resource, and the second configuration being associated with a second SR identifier including the second PUCCH resource.

3. The UE of claim 1, wherein a mapping of logical channels to SR configurations is applied across the PUCCH resources in the non-SBFD time slot and the SBFD time slot.

4. The UE of claim 1, wherein a single logical channel is mapped to a first PUCCH resource associated with the non-SBFD time slot and to a second PUCCH resource associated with the SBFD time slot.

5. The UE of claim 1, wherein the SR resource configuration is selected for the SBFD slot based at least in part on one or more selection criteria relating to: Logical channel mapping, The earliest PUCCH resource mapped to SR resources appeared. Time slot type, UE configuration, or The instructions received.

6. The UE according to claim 1, wherein the SR counter or SR disable timer is applicable to SR transmission in the non-SBFD time slot and the SBFD time slot.

7. The UE of claim 1, wherein the configuration information indicates the configuration of an SR counter or SR disable timer for a logical channel.

8. The UE of claim 7, wherein the SR counter increments across non-SBFD time slots and SBFD time slots.

9. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: Detecting SR failures associated with the SR transmission counter; and Trigger a set of SR failure actions; and Initiate the random access channel procedure.

10. The UE of claim 9, wherein the random access channel resources for the random access channel procedure are based on the configuration of the SR transmission counter and associated with the duplex type.

11. The UE of claim 1, wherein, in order for the UE to send the SR message, the one or more processors are configured to cause the UE to send the SR message on dedicated SR resources, and The one or more processors are further configured to enable the UE to receive uplink permission based on the transmission of the SR message on the dedicated SR resource.

12. A network node for wireless communication, the network node comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the network node to: Send configuration information for the identifier scheduling request (SR) resource configuration, wherein the SR resource configuration includes: Physical uplink control channel (PUCCH) resources configured in non-subband full-duplex (non-SBFD) time slots and SBFD time slots, or The first PUCCH resource configured in the SBFD time slot and the second PUCCH resource configured in the non-SBFD time slot; and The SR resource configuration is used to receive SR messages in the SBFD time slot or the non-SBFD time slot.

13. The network node of claim 12, wherein the SR resource configuration includes a first configuration and a second configuration, the first configuration being associated with a first SR identifier including the first PUCCH resource, and the second configuration being associated with a second SR identifier including the second PUCCH resource.

14. The network node of claim 12, wherein a mapping of logical channels to SR configurations is applied across the PUCCH resources in the non-SBFD time slots and the SBFD time slots.

15. The network node of claim 12, wherein a single logical channel is mapped to a first PUCCH resource associated with the non-SBFD time slot and to a second PUCCH resource associated with the SBFD time slot.

16. The network node of claim 12, wherein the SR resource configuration is used for the SBFD time slot in combination with at least one of the following: Logical channel mapping, The earliest PUCCH resource mapped to SR resources appeared. Time slot type, UE configuration, or The instructions received.

17. The network node of claim 12, wherein the SR counter or SR disable timer is adapted for SR transmission in the non-SBFD time slot and the SBFD time slot.

18. The network node of claim 12, wherein the configuration information indicates the configuration of an SR counter or SR disable timer for a logical channel.

19. The network node of claim 12, wherein, in order for the network node to receive the SR message, the one or more processors are configured to cause the network node to receive the SR message on a dedicated SR resource, and The one or more processors are further configured to cause the network node to send uplink grants based on the receipt of the SR message on the dedicated SR resource.

20. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive configuration information for the identifier scheduling request (SR) resource configuration, wherein the SR resource configuration includes: Physical uplink control channel (PUCCH) resources configured in non-subband full-duplex (non-SBFD) time slots and SBFD time slots, or The first PUCCH resource configured in the SBFD time slot and the second PUCCH resource configured in the non-SBFD time slot; and The SR resource configuration is used to send SR messages in the SBFD time slot or the non-SBFD time slot.

Images