Logical channel and scheduling request configuration for full duplex mode and half duplex mode

Abstract

Aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive a configuration message indicating a scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE. The UE can transmit a scheduling request using the at least one resource associated with the half-duplex mode or the at least one resource associated with the full-duplex mode. Additionally or alternatively, the configuration message can indicate a logical channel mapped to a corresponding scheduling request configuration associated with the half-duplex mode of the UE, a corresponding scheduling request configuration associated with the full-duplex mode of the UE, or a combination thereof. Accordingly, the UE can transmit the scheduling request using the logical channel. Numerous other aspects are described.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication, and to techniques and apparatus for configuring logical channels and scheduling requests for full-duplex and half-duplex modes. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include multiple base stations (BSs) capable of supporting communication for multiple user equipments (UEs). UEs can communicate with the BS via downlinks and uplinks. A "downlink" (or forward link) refers to the communication link from the BS to the UE, and an "uplink" (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0004] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, or even global level. NR, also known as 5G, is a set of enhancements to the LTE mobile standard released by 3GPP. NR aims to better support mobile broadband internet access by: improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, better integrating with other open standards, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. The open standard uses Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM)) on the uplink (UL). With the continued growth in demand for mobile broadband access, further improvements to LTE, NR, and other radio access technologies remain highly valuable. Summary of the Invention

[0005] In some aspects, a user equipment (UE) for wireless communication includes: a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: receive from a base station a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and send a scheduling request to the base station using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0006] In some aspects, a base station for wireless communication includes: a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: send a configuration message to a UE indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and receive a scheduling request from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0007] In some aspects, a UE for wireless communication includes: a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: receive from a base station a configuration message indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the UE, a corresponding scheduling request configuration associated with a full-duplex mode of the UE, or a combination thereof; and send a scheduling request to the base station using the logical channel.

[0008] In some aspects, a base station for wireless communication includes: a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: send a configuration message to a UE indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the UE, a corresponding scheduling request configuration associated with a full-duplex mode of the UE, or a combination thereof; and receive scheduling requests from the UE using the logical channel.

[0009] In some aspects, a wireless communication method performed by a UE includes: receiving from a base station a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and sending a scheduling request to the base station using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0010] In some aspects, a method of wireless communication performed by a base station includes: sending a configuration message to a UE indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and receiving a scheduling request from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0011] In some aspects, the wireless communication method performed by the UE includes: receiving from a base station a configuration message indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof; and sending a scheduling request to the base station using the logical channel.

[0012] In some aspects, the wireless communication method performed by the base station includes: sending a configuration message to the UE indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof; and receiving a scheduling request from the UE using the logical channel.

[0013] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of the UE, cause the UE to: receive from a base station a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and send a scheduling request to the base station using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0014] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: send a configuration message to a UE indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and receive a scheduling request from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0015] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of the UE, cause the UE to: receive from a base station a configuration message indicating a logical channel configuration that maps the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof; and send a scheduling request to the base station using the logical channel.

[0016] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to: send a configuration message to the UE indicating a logical channel configuration that maps the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof; and receive a scheduling request from the UE using the logical channel.

[0017] In some aspects, an apparatus for wireless communication includes: a component for receiving from a base station a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the apparatus and at least one resource associated with a full-duplex mode of the apparatus; and a component for sending a scheduling request to the base station using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0018] In some aspects, the apparatus for wireless communication includes: a component for sending a configuration message to a UE indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and a component for receiving a scheduling request from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

[0019] In some aspects, an apparatus for wireless communication includes: a component for receiving from a base station a configuration message indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the apparatus, a corresponding scheduling request configuration associated with a full-duplex mode of the apparatus, or a combination thereof; and a component for sending a scheduling request to the base station using the logical channel.

[0020] In some aspects, the apparatus for wireless communication includes: a component for sending a configuration message to a UE indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the UE, a corresponding scheduling request configuration associated with a full-duplex mode of the UE, or a combination thereof; and a component for receiving a scheduling request from the UE using the logical channel.

[0021] The terms generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems, which are basically described herein with reference to the accompanying drawings and description and are illustrated by the accompanying drawings and description.

[0022] The features and technical advantages of the examples according to this disclosure have been outlined rather broadly above to facilitate a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifications or the design of other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and operation, and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and is not intended to define limitations of the claims.

[0023] While aspects have been described in this disclosure by way of example, those skilled in the art will understand that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / procurement equipment, medical devices, or AI-enabled devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices combining the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers). The aspects described herein are intended to be implemented in devices, components, systems, distributed arrangements, or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0024] To gain a more detailed understanding of the foregoing features of this disclosure, reference can be made to various aspects for a more specific description of the above brief overview, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should therefore not be considered as limiting its scope, as the description may acknowledge other equally valid aspects. The same reference numerals in different drawings may denote the same or similar elements.

[0025] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0026] Figure 2 This is a diagram illustrating an example of a base station communicating with a UE in a wireless network according to this disclosure.

[0027] Figure 3A , Figure 3B and Figure 3C This is a diagram illustrating an example of full-duplex communication according to this disclosure.

[0028] Figure 4 This is a diagram illustrating an example of configuring scheduling requests for full-duplex and half-duplex modes according to this disclosure.

[0029] Figure 5 This is a diagram illustrating examples of using logical channels for full-duplex and half-duplex modes according to this disclosure.

[0030] Figure 6 This is a diagram illustrating an example of a scheduling request process associated with full-duplex and half-duplex modes according to this disclosure.

[0031] Figure 7 , Figure 8 , Figure 9 and Figure 10 This is a diagram illustrating an example process associated with configuring logical channels and scheduling requests for full-duplex and half-duplex modes according to this disclosure.

[0032] Figure 11 and Figure 12 This is a block diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0033] The various aspects of this disclosure will be described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Based on the guidance herein, those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of the disclosure herein, which may be implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover an apparatus or method that is practiced using a structure, function, or structure and function other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0034] Several aspects of a telecommunications system will now be described with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints of the overall system.

[0035] It should be noted that although the terms commonly associated with 5G or NR radio access technology (RAT) may be used to describe the aspects herein, the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0036] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. Among other examples, the wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network. The wireless network 100 may include multiple base stations 110 (shown as BS110a, BS110b, BS110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, Transmit / Receive Point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0037] A Base Station (BS) can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs subscribed to the service. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs subscribed to the service. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access for UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macrocell can be referred to as a macro BS. A BS for a picocell can be referred to as a pico BS. A BS for a femtocell can be referred to as a femtocell BS or a home BS. Figure 1 In the example shown, BS110a can be a macro BS of macro cell 102a, BS110b can be a pico BS of pico cell 102b, and BS110c can be a femto BS of femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB”, “base station”, “NR BS”, “gNB”, “TRP”, “AP”, “Node B”, “5G NB”, and “cell” are used interchangeably in this document.

[0038] In some respects, the cell is not necessarily stationary, and the geographical area of ​​the cell can move depending on the location of the mobile BS. In some respects, the BS can interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network, through various types of backhaul interfaces such as direct physical connections or virtual networks.

[0039] The wireless network 100 may also include relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or a UE) and transmitting data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, the relay BS110d can communicate with the macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, repeater, etc.

[0040] Wireless network 100 can be a heterogeneous network, including different types of base stations (BSs), such as macro BSs, pico BSs, femto BSs, and relay BSs. These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 watts to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0041] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0042] UEs 120 (e.g., 120a, 120b, 120c) may be distributed across the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be 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 or equipment, a biosensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0043] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. For example, MTC UEs and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with base stations, another device (e.g., remote devices), or some other entity. For example, a wireless node can provide connectivity to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components and / or memory components. In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0044] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0045] In some respects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0046] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1) from 410 MHz to 7.125 GHz, and / or can communicate using an operating band with a second frequency range (FR2) from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency (IF) frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, FR2 is often referred to as the "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise stated, it should be understood that the terms "sub-6GHz" and the like (if used herein) can broadly refer to frequencies less than 6GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125GHz). Similarly, unless otherwise stated, it should be understood that the terms "millimeter wave" and the like (if used herein) can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25GHz). It is anticipated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0047] As mentioned above, Figure 1This is provided as an example. Other examples may be provided related to... Figure 1 The descriptions are different.

[0048] Figure 2 This is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein, generally, T ≥ 1 and R ≥ 1.

[0049] At base station 110, transmitting processor 220 can receive data from one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQI) received from the UE, process (e.g., encode and modulate) the data of each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). If applicable, the transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can also process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from modulators 232a to 232t can be transmitted via antennas 234a to 234t, respectively.

[0050] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 can also process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or Channel Quality Indicator (CQI). In some respects, one or more components of the UE 120 may be included in the housing 284.

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

[0052] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, antenna groups, antenna element groups, and / or antenna arrays, or may be included in one or more antenna panels, antenna groups, antenna element groups, and / or antenna arrays. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include coplanar antenna element groups and / or non-coplanar antenna element groups. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element groups, and / or antenna arrays may include antenna elements coupled to one or more transmitting and / or receiving components (such as...) Figure 2 One or more antenna elements (one or more components).

[0053] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can also generate reference symbols for one or more reference signals. If applicable, the symbols from the transmitting processor 264 can be pre-encoded by the TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM, etc.), and transmitted to base station 110. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 254) of UE 120 can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. Processors (e.g., controller / processor 280) and memory 282 may be used with the transceiver to perform aspects of any of the methods described herein (e.g., references...). Figures 4 to 10 ).

[0054] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 if applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some aspects, modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TXMIMO processor 230. The processor (e.g., controller / processor 240) and memory 242 may be used with the transceiver to perform aspects of any of the methods described herein (e.g., references...). Figures 4 to 10 ).

[0055] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component may perform one or more techniques associated with configuring logical channels and scheduling requests for full-duplex and half-duplex modes, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can execute or direct, for example Figure 7 Process 700 Figure 8 The process 800 Figure 9 The process 900 Figure 10 The operation of process 1000 and / or other processes described herein. Memory 242 and 282 may store data and program code of base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, transformation, and / or interpretation), one or more processors, UE 120, and / or base station 110 may be caused to perform or direct, for example... Figure 7 Process 700 Figure 8 The process 800 Figure 9 The process 900 Figure 10 The operation of process 1000 and / or other processes described herein. In some aspects, the execution instructions may include run instructions, conversion instructions, compilation instructions, and / or interpretation instructions, etc.

[0056] In some respects, UEs (e.g., UE 120, UE 302 and / or in Figure 3) Figure 11 The apparatus 1100 may include a means for receiving signals from a base station (e.g., base station 110, base station 304 of FIG3 and / or...). Figure 12The apparatus 1200) includes a component that receives a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and / or a component for sending a scheduling request to the base station using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode. For example, components for the UE to perform the operations described herein may include one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282. In some aspects, the UE may also include a component for sending a random access preamble to the base station at least in part based on a determination of a counter limit satisfaction after sending the scheduling request. Alternatively, the UE may include a component for sending a random access preamble to the base station at least in part based on a determination of a first counter limit satisfaction or a determination of a second counter limit satisfaction after sending the scheduling request.

[0057] In some aspects, base stations (e.g., base station 110, base station 304 of Figure 3 and / or Figure 12 The apparatus 1200 may include a means for sending signals to a UE (e.g., UE 120, UE 302 of FIG. 3 and / or Figure 11 The apparatus 1100) includes a component that transmits a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and / or a component for receiving a scheduling request from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode. For example, components for the base station to perform the operations described herein may include one or more of a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, the base station may also include a component for receiving a random access preamble from the UE, at least in part based on a counter limit satisfaction, after receiving a scheduling request. Alternatively, the base station may include a component for receiving a random access preamble from the UE, at least in part based on a first counter limit satisfaction or a second counter limit satisfaction, after receiving a scheduling request.

[0058] In some aspects, UEs (e.g., UE 120, UE 302 of Figure 3 and / or Figure 11 The apparatus 1100 may include a means for receiving signals from a base station (e.g., base station 110, base station 304 of FIG3 and / or...). Figure 12The apparatus 1200) includes a component that receives a configuration message indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode; and / or a component for sending a scheduling request to the base station using the logical channel. For example, components for the UE to perform the operations described herein may include one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0059] In some aspects, base stations (e.g., base station 110, base station 304 of Figure 3 and / or Figure 12 The apparatus 1200 may include a means for sending signals to a UE (e.g., UE 120, UE 302 of FIG. 3 and / or Figure 11 The apparatus 1100 includes a component that transmits a configuration message indicating a logical channel configuration, which maps a logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the UE, a corresponding scheduling request configuration associated with a full-duplex mode of the UE, or a combination thereof; and / or a component for receiving scheduling requests from the UE using the logical channel. For example, components for the base station to perform the operations described herein may include one or more of the following: a transmit processor 220, a TX MIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

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

[0061] As mentioned above, Figure 2 This is provided as an example. Other examples may be provided related to... Figure 2 The descriptions are different.

[0062] Figures 3A to 3C These are schematic diagrams illustrating examples 300, 310, and 320 of full-duplex communication. (See diagram for example.) Figures 3A to 3C As shown, Examples 300, 310, and 320 include one or more UEs 302 communicating with one or more base stations 304, TRPs 304, and / or similar devices in a wireless network supporting full-duplex communication. However, it should be understood that... Figures 3A to 3C The devices shown are provided as examples only, and the wireless network can support full-duplex communication between other devices (e.g., between mobile terminal nodes and control nodes, between child nodes and parent nodes in an Integrated Access Backhaul (IAB) network, between scheduled nodes and scheduling nodes, etc.).

[0063] like Figure 3A As shown, Example 300 includes a UE 302 communicating with two base stations (e.g., TRPs) 304-1 and 304-2. Figure 3A As shown, UE 302 can send one or more uplink transmissions to base station 304-1 and can simultaneously receive one or more downlink transmissions from base station 304-2. Therefore, in Figure 3A In Example 300, full-duplex communication is enabled for UE 302, which may operate as a full-duplex node, but not for base stations 304-1 and 304-2, which may operate as half-duplex nodes. For example, UE 302 may have at least two antenna panels (each antenna panel including one or more antenna elements) such that at least one antenna panel can be used to transmit uplink transmissions while at least one other antenna panel receives downlink transmissions.

[0064] Additional or alternative land, such as Figure 3B As shown, Example 310 includes two UEs communicating with base station 304, namely UE1 302-1 and UE2 302-2. In this case, base station 304 can send one or more downlink transmissions to UE1 302-1 and can simultaneously receive one or more uplink transmissions from UE2 302-2. Therefore, in Figure 3B In Example 310, full-duplex communication is enabled for base station 304, which can operate as a full-duplex node, but not for UE1 302-1 and UE2 302-2, which can operate as half-duplex nodes. For example, base station 304 may have at least two antenna panels (each antenna panel including one or more antenna elements) such that at least one antenna panel can be used to transmit downlink transmissions while at least one other antenna panel receives uplink transmissions.

[0065] Additional or alternative land, such as Figure 3C As shown, Example 320 includes a UE 302 communicating with a base station 304. In this configuration, base station 304 can transmit and UE 302 can receive one or more downlink transmissions, while UE 302 transmits and base station 304 receives one or more uplink transmissions. Therefore, in Figure 3CIn Example 320 shown, full-duplex communication is enabled for both UE 302 and base station 304, with each of UE 302 and base station 304 operating as a full-duplex node.

[0066] Full-duplex communication can provide reduced latency by allowing full-duplex nodes to send or receive downlink signals in uplink-only time slots or downlink-only time slots. Furthermore, full-duplex communication can improve the spectral efficiency or throughput of each cell or UE by simultaneously allocating time and frequency resources for both uplink and downlink communication, thus achieving more efficient resource utilization.

[0067] Full-duplex communication can be in-band (also known as "IBFD"), whereby base station 304 is configured with downlink and uplink resources that at least partially overlap in time and / or frequency. Alternatively, full-duplex communication can be sub-band (also known as "flexible duplex"), whereby base station 304 is configured with downlink and uplink resources that overlap in time but use different frequencies. In some aspects, base station 304 may also configure a guard band comprising one or more frequencies between the downlink and uplink resources.

[0068] Frequency division multiplexing (FDM) (e.g., for subband full-duplex) is typically used in paired spectrum bands (e.g., bands n1, n2, n3, n5, and / or other low-frequency bands). By using paired bands, base station 304 can configure one of the two paired bands for downlink and the other of the two paired bands for uplink. In unpaired spectrum bands (e.g., bands n40, n41, n50, and / or other higher-frequency bands), time division multiplexing is typically used. Subband full-duplex allows base station 304 to use FDM in unpaired spectrum bands. For example, base station 304 can configure a first portion of frequencies included in one or more unpaired spectrum bands for downlink and a second portion of frequencies included in one or more unpaired spectrum bands for uplink.

[0069] When a UE has data to send to a base station, the UE will send a scheduling request (also known as "SR") to the base station (e.g., on the Physical Uplink Control Channel (PUCCH) and / or another uplink channel). Therefore, the base station can grant authorization for one or more resources that the UE can use to send data, at least in part, based on the scheduling request. When the UE sends a scheduling request to the base station, the UE can send a scheduling request associated with full-duplex or half-duplex mode (e.g., as combined above). Figures 3A to 3C(As described herein). For example, a UE may send a scheduling request in full-duplex or half-duplex mode, and / or request data to be sent according to half-duplex or full-duplex mode. However, base stations typically cannot distinguish between these modes. For example, higher layers of the UE (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or another layer) may select a logical channel for sending the scheduling request. As used herein, a "logical channel" may refer to a channel between the RLC layer and the MAC layer that facilitates downlink communication from the base station to the UE and uplink communication from the UE to the base station. A logical channel may reside in the control plane and carry control information, or it may reside in the user plane and carry data. Furthermore, lower layers of the UE (e.g., the physical layer and / or another layer) may select at least one resource for sending the scheduling request, at least in part, based on a mapping between the logical channel and a scheduling request configuration that includes at least one resource. Neither the logical channel nor the scheduling request configuration indicates a full-duplex or half-duplex mode. Therefore, base stations cannot distinguish between scheduling requests associated with full-duplex and scheduling requests associated with half-duplex.

[0070] Because the base station cannot distinguish between full-duplex and half-duplex scheduling requests, it can grant one or more resources (such as frequency bands), leading to high self-interference between the UE's antenna panels. This degrades the communication quality and / or reliability between the UE and the base station, and can increase latency and waste processing resources if the base station has to retransmit downlink data due to high self-interference. Alternatively, the base station can grant one or more resources configured for full-duplex downlink, requiring the UE to transmit data in half-duplex mode. This reduces throughput between the UE and the base station and increases latency because the UE cannot operate in full-duplex mode while transmitting data.

[0071] Some of the techniques and apparatus described herein can allow a base station (e.g., base station 110 and / or base station 304) to instruct a scheduling request configuration that includes at least one resource associated with a half-duplex mode of a UE (e.g., UE 120 and / or UE 302) and at least one resource associated with a full-duplex mode of UE 120. Therefore, base station 110 can distinguish between a scheduling request sent for a half-duplex mode and a scheduling request sent for a full-duplex mode. Thus, base station 110 can grant authorization for one or more resources to UE 120 to transmit data, which reduces self-interference at UE 120 and is not configured for downlink in full-duplex mode. This increases the communication quality and / or reliability between UE 120 and base station 110, saves processing resources by reducing the chance of the base station having to retransmit downlink data due to self-interference, and increases throughput and reduces latency between UE 120 and base station 110 because UE 120 can operate in full-duplex mode when transmitting data.

[0072] Additionally or alternatively, some of the techniques and apparatus described herein can allow a base station (e.g., base station 110 and / or base station 304) to instruct a logical channel configuration that maps logical channels to a corresponding scheduling request configuration associated with a half-duplex mode of a UE (e.g., UE 120 and / or UE 302), a corresponding scheduling request configuration associated with a full-duplex mode of UE 120, or a combination thereof. Thus, base station 110 can distinguish between a transmitted scheduling request associated with a half-duplex mode and a transmitted scheduling request associated with a full-duplex mode. As described above, this increases the communication quality and / or reliability between UE 120 and base station 110, saves processing resources by reducing the chance of the base station having to retransmit downlink data due to self-interference, and increases throughput while reducing latency between UE 120 and base station 110, since UE 120 can operate in full-duplex mode when transmitting data associated with the scheduling request.

[0073] As mentioned above, Figures 3A to 3C Provided as one or more examples. Other examples may be provided in relation to... Figures 3A to 3C The descriptions are different.

[0074] Figure 4 This is a diagram illustrating example 400 associated with configuring scheduling requests for full-duplex and half-duplex modes according to this disclosure. Figure 4 As shown, Example 400 may include a base station 110 and a UE 120 communicating with each other. For example, base station 110 and UE 120 may be included in a wireless network, such as... Figure 1 Wireless network 100.

[0075] As shown with reference to reference numeral 405 in the accompanying drawings, base station 110 can transmit, and UE 120 can receive, a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with half-duplex mode of UE 120 and at least one resource associated with full-duplex mode of UE 120. For example, the configuration message may include a radio resource control (RRC) message, a MAC control element (MAC-CE), downlink control information (DCI), or a combination thereof.

[0076] In some aspects, the scheduling request configuration may include the ScheduledRequestConfig data structure as defined in 3GPP specifications and / or another standard. Although the following description refers to the ScheduledRequestConfig data structure, it also applies to other similar data structures. At least one resource associated with full-duplex mode may be defined using one or more variables. For example, at least one resource may include one or more frequencies (and / or other portions of the frequency domain) associated with the sr-PUCCH-ResourceIndex variable included in the ScheduledRequestConfig data structure as defined in 3GPP specifications and / or another standard. Additionally or alternatively, at least one resource may include a subframe (and / or other portions of the time domain) associated with the sr-ConfigIndex variable included in the ScheduledRequestConfig data structure as defined in 3GPP specifications and / or another standard. Although the following description refers to the sr-PUCCH-ResourceIndex and sr-ConfigIndex variables, it also applies to other similar variables defining at least one resource. At least one resource associated with half-duplex mode may be defined similarly.

[0077] As shown in conjunction with reference to reference numeral 410, UE 120 can select at least one resource to use when sending a scheduling request. In some aspects, the half-duplex mode can be associated with a first bandwidth portion (BWP), which is different from the second BWP associated with the full-duplex mode. Therefore, when sending a scheduling request associated with the half-duplex mode, UE 120 can select at least one resource within the first BWP, and when sending a scheduling request associated with the full-duplex mode, it can select at least one resource within the second BWP. As used herein, "bandwidth portion" or "BWP" can refer to a contiguous set of physical resource blocks (PRBs), where each PRB comprises a set of frequencies corresponding to one or more subcarriers.

[0078] As an alternative, half-duplex mode can at least partially share a BWP with full-duplex mode. Therefore, at least one resource associated with half-duplex mode and at least one resource associated with full-duplex mode can be included in at least one BWP shared by both half-duplex and full-duplex modes.

[0079] In some aspects, the scheduling request configuration may include one or more PUCCH resources for half-duplex mode and one or more other PUCCH resources for full-duplex mode. Therefore, at least one resource associated with half-duplex mode may include one or more first PUCCH resources, and at least one resource associated with full-duplex mode may include one or more second PUCCH resources separate from the one or more first PUCCH resources. For example, the ScheduledRequestConfig data structure may include sr-PUCCH-ResourceIndex variables and / or sr-ConfigIndex variables defining one or more first PUCCH resources (e.g., they may be referred to as HD-sr-PUCCH-ResourceIndex and / or HD-sr-ConfigIndex, respectively). Similarly, the ScheduledRequestConfig data structure may include sr-PUCCH-ResourceIndex variables and / or sr-ConfigIndex variables defining one or more second PUCCH resources (e.g., they may be referred to as FD-sr-PUCCH-ResourceIndex and / or FD-sr-ConfigIndex, respectively).

[0080] Additionally or alternatively, the scheduling request configuration may include one or more PUCCH resources common to both half-duplex and full-duplex modes. Therefore, at least one resource associated with half-duplex mode and at least one resource associated with full-duplex mode may include one or more PUCCH resources common to both half-duplex and full-duplex modes. For example, the SchedulingRequestConfig data structure may include sr-PUCCH-ResourceIndex variables and / or sr-ConfigIndex variables defining one or more first PUCCH resources (e.g., they may be referred to as common-sr-PUCCH-ResourceIndex and / or common-sr-ConfigIndex, respectively).

[0081] In any of the aspects described above, the scheduling request configuration may also include a first timer associated with half-duplex mode and a second timer associated with full-duplex mode. For example, as combined below Figure 6As described, the ScheduledRequestConfig data structure may include a first sr-ProhibitTimer variable (e.g., it may be referred to as HD-sr-ProhibitTimer) defining a first timer. Similarly, the ScheduledRequestConfig data structure may include a second sr-ProhibitTimer variable (e.g., it may be referred to as FD-sr-ProhibitTimer) defining a second timer. Alternatively, the schedule request configuration may include timers common to both half-duplex and full-duplex modes. For example, as combined with the following... Figure 6 As described, the ScheduleRequestConfig data structure may include a first sr-ProhibitTimer variable that defines the timer (e.g., it may be called common-sr-ProhibitTimer).

[0082] In any of the aspects described above, the scheduling request configuration may also include counter limits (e.g., thresholds) common to both half-duplex and full-duplex modes. For example, as combined with the following Figure 6 As described, the ScheduledRequestConfig data structure may include a first sr-TransMax variable (e.g., it may be called common-sr-TransMax) that defines the counter limit. Alternatively, the schedule request configuration may also include a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode. For example, as combined below... Figure 6 As described, the ScheduledRequestConfig data structure may include a first sr-TransMax variable (e.g., which may be referred to as HD-sr-TransMax) defining a first timer. Similarly, the ScheduledRequestConfig data structure may include a second sr-TransMax variable (e.g., which may be referred to as FD-sr-TransMax) defining a second timer.

[0083] As shown in conjunction with reference numeral 415, UE 120 may use at least one resource associated with half-duplex mode or at least one resource associated with full-duplex mode to transmit a scheduling request, and base station 110 may use at least one resource associated with half-duplex mode or at least one resource associated with full-duplex mode to receive a scheduling request. For example, UE 120 may use at least one resource selected as described above in conjunction with reference numeral 410. In some aspects, UE 120 may use the following combination of... Figure 6The described process is at least a part of determining to send a scheduling request.

[0084] In some respects, after sending a scheduling request, based at least in part on the determination that a counter limit (e.g., common to both half-duplex and full-duplex modes) is satisfied, UE 120 can send a random access preamble, and base station 110 can receive the random access preamble. For example, in the following combination... Figure 6 As described, UE 120 can release the PUCCH configuration associated with the scheduling request (as well as the Probe Reference Signal (SRS) configuration, Semi-Persistent Channel State Information (SP-CSI) configuration, Semi-Persistent State (SPS) configuration, and / or Configuration Grant (CG)) based at least in part on the satisfaction of thresholds defined by sr-TransMax. Furthermore, UE 120 can initiate a Random Access Channel (RACH) procedure with base station 110.

[0085] As an alternative, after sending the scheduling request, UE 120 may send a random access preamble, and base station 110 may receive the random access preamble, at least in part based on a determination that a first counter limit (e.g., associated with half-duplex mode) or a determination that a second counter limit (e.g., associated with full-duplex mode) is satisfied. For example, in combination with the following Figure 6 As described, when a scheduling request is transmitted in half-duplex mode, UE 120 can release the PUCCH configuration (and SRS configuration, SP-CSI configuration, SPS configuration, and / or CG) associated with the scheduling request, at least in part, based on the thresholds defined by HD-sr-TransMax. Furthermore, UE 120 can initiate a RACH procedure with base station 110. Similarly, as described below... Figure 6 As described, when a scheduling request is sent in full-duplex mode, UE 120 can release the PUCCH configuration (as well as SRS configuration, SP-CSI configuration, SPS configuration, and / or CG) associated with the scheduling request, at least in part, based on the thresholds defined by FD-sr-TransMax. Furthermore, UE 120 can initiate a RACH procedure with base station 110.

[0086] As shown in conjunction with reference numeral 420, base station 110 can determine at least one resource used in uplink granting. For example, as described above in conjunction with reference numeral 410, half-duplex mode can be associated with a first frequency band BWP different from the second BWP associated with full-duplex mode, allowing base station 110 to distinguish between scheduling requests associated with full-duplex mode and scheduling requests associated with half-duplex mode. Therefore, base station 110 can determine at least one resource based at least in part on whether the scheduling request is associated with full-duplex mode or half-duplex mode. For example, base station 110 can select at least one resource for half-duplex mode, which would otherwise be reserved for downlink in full-duplex mode. Additionally or alternatively, base station 110 can select at least one resource for full-duplex mode that causes less self-interference at UE 120 (e.g., based at least in part on reports from UE 120, which are based at least in part on one or more interference measurements performed by UE 120).

[0087] Additionally or alternatively, and as described above in conjunction with reference numeral 410, the scheduling request configuration may include one or more PUCCH resources for half-duplex mode and one or more other PUCCH resources for full-duplex mode, such that base station 110 can distinguish between scheduling requests associated with full-duplex mode and scheduling requests associated with half-duplex mode. Therefore, as described above, base station 110 can determine at least one resource based at least in part on whether the scheduling request is associated with full-duplex mode or half-duplex mode.

[0088] As an alternative, and as described above in conjunction with reference numeral 410, the scheduling request configuration may include one or more PUCCH resources for half-duplex mode and one or more other PUCCH resources for full-duplex mode. Therefore, base station 110 can determine at least one resource such that it can be used in either full-duplex or half-duplex mode. In some aspects, base station 110 can still distinguish between scheduling requests associated with full-duplex mode and scheduling requests associated with half-duplex mode, at least in part, based on the logical channel associated with the scheduling request (e.g., as described below in conjunction with reference numeral 410). Figure 5 (As described above). Therefore, as described above, base station 110 can determine at least one resource based at least in part on whether the scheduling request is associated with full-duplex mode or half-duplex mode.

[0089] As shown in conjunction with reference numeral 425, base station 110 can send uplink grants, and UE 120 can receive uplink grants. For example, uplink grants can include DCI, MAC-CE, or a combination thereof. Therefore, UE 120 can send data to base station 110 at least in part based on uplink grants. Additionally, UE 120 can send data in full-duplex or half-duplex mode at least in part based on whether the scheduling request is associated with full-duplex or half-duplex mode.

[0090] By using, such as combination Figure 4 According to the described technique, base station 110 can instruct a scheduling request configuration, which includes at least one resource associated with half-duplex mode of UE 120 and at least one resource associated with full-duplex mode of UE 120. Therefore, base station 110 can distinguish between a scheduling request sent for half-duplex mode and a scheduling request sent for full-duplex mode. Thus, base station 110 can grant UE 120 authorization for one or more resources to transmit data, which reduces self-interference at UE 120 and is not configured for downlink in full-duplex mode. This increases the communication quality and / or reliability between UE 120 and base station 110, saves processing resources by reducing the chance of the base station having to retransmit downlink data due to self-interference, and increases throughput while reducing latency between UE 120 and base station 110 because UE 120 can operate in full-duplex mode when transmitting data.

[0091] As mentioned above, Figure 4 This is provided as an example. Other examples may be provided related to... Figure 4 The descriptions are different.

[0092] Figure 5 This is a diagram illustrating example 500 associated with using a logical channel for full-duplex and half-duplex modes according to this disclosure. Figure 5 As shown, Example 500 may include a base station 110 and a UE 120 communicating with each other. For example, base station 110 and UE 120 may be included in a wireless network, such as... Figure 1 Wireless network 100.

[0093] As shown with reference to reference numeral 505 in the accompanying drawings, base station 110 can send, and UE 120 can receive, a configuration message indicating a logical channel configuration that maps logical channels to a corresponding scheduling request configuration associated with half-duplex mode of UE 120, a corresponding scheduling request configuration associated with full-duplex mode of UE 120, or a combination thereof. For example, the configuration message may include an RRC message, MAC-CE, DCI, or a combination thereof.

[0094] In some aspects, logical channel configuration may include the LogicalChannelConfig data structure as defined in 3GPP specifications and / or another standard. Although the following description refers to the LogicalChannelConfig data structure, it also applies to other similar data structures. A logical channel can be defined using one or more variables. For example, a logical channel may have a priority associated with a priority integer, a bit rate associated with a prioritizedBitRate variable, a bucket size associated with a bucketSizeDuration variable, and / or a subcarrier spacing (SCS) associated with an allowedSCS-List variable, as defined in 3GPP specifications and / or another standard, included in the LogicalChannelConfig data structure. Although the following description refers to the priority, prioritizedBitRate, bucketSizeDuration, and / or allowedSCS-List variables, it also applies to other similar data variables used to define a logical channel.

[0095] Additionally, the LogicalChannelConfig data structure can indicate a mapping to the corresponding scheduling request configuration. For example, the LogicalChannelConfig data structure may include a schedulingRequestID identifier, which maps to a ScheduleRequestConfig data structure that defines the corresponding scheduling request configuration (e.g., as combined above). Figure 4 The corresponding identifiers included in the description.

[0096] In some respects, each logical channel can be mapped to a scheduling request configuration. As described above... Figure 4 As described, the scheduling request configuration may include one or more PUCCH resources for half-duplex mode and one or more other PUCCH resources for full-duplex mode. Additionally or alternatively, as combined above... Figure 4As described, the scheduling request configuration may include one or more PUCCH resources common to both half-duplex and full-duplex modes. In some aspects, the logical channel configuration may also include indicators that exclude the logical channel from use in either half-duplex or full-duplex modes. For example, the LogicalChannelConfig data structure may include an allowedDuplexMode variable (e.g., as defined in 3GPP specifications and / or another standard) indicating whether the logical channel can be used in full-duplex and / or half-duplex modes. Additionally or alternatively, the logical channel configuration may implicitly exclude the logical channel from use in full-duplex mode by not mapping the logical channel to scheduling request configurations that are associated with and / or include one or more PUCCH resources associated with full-duplex mode. Similarly, the logical channel configuration may implicitly exclude the logical channel from use in half-duplex mode by scheduling request configurations that are not mapped to scheduling request configurations that are associated with and / or include one or more PUCCH resources associated with half-duplex mode. Therefore, in some respects, base station 110 can exclude logical channels associated with Ultra Reliable Low Latency Communication (URLLC) service, Enhanced Mobile Broadband (eMBB) service and / or another service from full-duplex or half-duplex modes.

[0097] Alternatively, each logical channel can be mapped to two or more scheduling request configurations. For example, the LogicalChannelConfig data structure may include multiple schedulingRequestID identifiers that map to corresponding identifiers included in the ScheduleRequestConfig data structure. In some aspects, the two or more scheduling request configurations may include at least one scheduling request configuration associated with full-duplex mode (e.g., indicated by the FD-schedulingRequestID identifier) ​​and at least one scheduling request configuration associated with half-duplex mode (e.g., indicated by the HD-schedulingRequestID identifier). In some aspects, the logical channel configuration may explicitly exclude the logical channel from use in half-duplex or full-duplex mode (e.g., using the allowedDuplexMode variable as described above). Additionally or alternatively, the logical channel configuration may implicitly exclude the logical channel from use in full-duplex mode by including null values ​​in the FD-schedulingRequestID identifier and / or by not mapping the logical channel to a scheduling request configuration associated with full-duplex mode and / or including one or more PUCCH resources associated with full-duplex mode. Similarly, by including a null value in the HD-schedulingRequestID identifier and / or by not mapping logical channels to scheduling request configurations associated with half-duplex mode and / or including one or more PUCCH resources associated with half-duplex mode, logical channel configuration can implicitly exclude logical channels from use in half-duplex mode. Therefore, in some aspects, base station 110 can exclude logical channels associated with URLLC service, eMBB service, and / or another service from full-duplex mode or half-duplex mode.

[0098] In any of the aspects described above, each logical channel may be associated with either a half-duplex mode or a full-duplex mode. For example, the LogicalChannelConfig data structure may include a duplexMode variable (e.g., as defined in 3GPP specifications and / or another standard) indicating whether a logical channel is associated with a full-duplex or half-duplex mode.

[0099] As shown in conjunction with reference to reference numeral 510 in the accompanying drawings, UE 120 can select the logical channel to use when sending a scheduling request. In some aspects, and as described above, a half-duplex mode can be associated with one or more first logical channels, which are different from one or more second logical channels associated with a full-duplex mode. Therefore, when sending a scheduling request associated with a half-duplex mode, UE 120 can select from one or more first logical channels, and when sending a scheduling request associated with a full-duplex mode, it can select from one or more second logical channels.

[0100] As an alternative, and as described above, the logical channel may not be separated between half-duplex and full-duplex modes. Therefore, when a selected logical channel is associated with multiple scheduling request configurations, UE 120 can select among the multiple scheduling request configurations at least in part based on whether the scheduling request will be associated with half-duplex or full-duplex mode. Additionally or alternatively, when a scheduling request configuration associated with the selected logical channel (or selected from the multiple scheduling request configurations associated with the selected logical channel) includes at least one resource associated with half-duplex mode (different from at least one resource associated with full-duplex mode), UE 120 can select among the resources included in the scheduling request configuration at least in part based on whether the scheduling request will be associated with half-duplex or full-duplex mode.

[0101] As shown with reference to reference numeral 515, UE 120 can use a logical channel to send scheduling requests, and base station 110 can use a logical channel to receive scheduling requests. For example, UE 120 can use the logical channel selected as described above with reference to reference numeral 510. In some aspects, UE 120 can use the following combined with... Figure 6 The described process is at least a part of determining to send a scheduling request.

[0102] In some respects, after sending a scheduling request, based at least in part on the determination that a counter limit (e.g., common to both half-duplex and full-duplex modes, or associated with the same mode as the scheduling request) is satisfied, UE 120 may send a random access preamble, and base station 110 may receive the random access preamble. For example, in the following combination... Figure 6 As described, UE 120 can release the PUCCH configuration (as well as SRS configuration, SP-CSI configuration, SPS configuration, and / or CG) associated with the scheduling request, at least in part, based on the thresholds defined by sr-TransMax. Furthermore, UE 120 can initiate a RACH procedure with base station 110.

[0103] As shown in conjunction with reference numeral 520, base station 110 can determine at least one resource used in uplink granting. For example, as described above in conjunction with reference numeral 505, a half-duplex mode can be associated with one or more first logical channels, which are different from one or more second logical channels associated with a full-duplex mode, such that base station 110 can distinguish between scheduling requests associated with a full-duplex mode and scheduling requests associated with a half-duplex mode. Therefore, base station 110 can determine at least one resource based at least in part on whether the scheduling request is associated with a full-duplex mode or a half-duplex mode. For example, base station 110 can select at least one resource for half-duplex mode, which would otherwise be reserved for downlink in full-duplex mode. Additionally or alternatively, base station 110 can select at least one resource for full-duplex mode that causes less self-interference at UE 120 (e.g., based at least in part on reports from UE 120, which are based at least in part on one or more interference measurements performed by UE 120).

[0104] As an alternative, and as described above in conjunction with reference numeral 505, the logical channel may not be indicated as associated with full-duplex or half-duplex mode. Therefore, base station 110 can determine at least one resource such that it can be used in either full-duplex or half-duplex mode. In some aspects, base station 110 can still distinguish between scheduling requests associated with full-duplex mode and those associated with half-duplex mode, at least in part, based on one or more PUCCH resources used to transmit the scheduling request (e.g., as described above in conjunction with reference numeral 505). Figure 6 (As described above). For example, a logical channel may be associated with one or more first scheduling request configurations, which are associated with a half-duplex mode, and the first scheduling request configurations differ from one or more second scheduling request configurations associated with a full-duplex mode, such that base station 110 can distinguish between scheduling requests associated with a full-duplex mode and scheduling requests associated with a half-duplex mode. Additionally or alternatively, a logical channel may be associated with a scheduling request configuration that includes one or more first PUCCH resources associated with a half-duplex mode, and the one or more first PUCCH resources differ from one or more second PUCCH resources associated with a full-duplex mode, such that base station 110 can distinguish between scheduling requests associated with a full-duplex mode and scheduling requests associated with a half-duplex mode. Therefore, as described above, base station 110 can determine at least one resource at least partially based on whether the scheduling request is associated with a full-duplex mode or a half-duplex mode.

[0105] As shown with reference to reference numeral 525 in the accompanying drawings, base station 110 can send uplink grants, and UE 120 can receive uplink grants. For example, uplink grants can include DCI, MAC-CE, or a combination thereof. Therefore, UE 120 can send data to base station 110 at least in part based on uplink grants. Additionally, UE 120 can send data in full-duplex or half-duplex mode at least in part based on whether the scheduling request is associated with full-duplex or half-duplex mode.

[0106] By using combination Figure 5 According to the described technology, base station 110 can instruct a logical channel configuration that maps logical channels to a corresponding scheduling request configuration associated with half-duplex mode of UE 120, a corresponding scheduling request configuration associated with full-duplex mode of UE 120, or a combination thereof. Therefore, base station 110 can distinguish between a transmitted scheduling request associated with half-duplex mode and a transmitted scheduling request associated with full-duplex mode.

[0107] As mentioned above, Figure 5 This is provided as an example. Other examples may be provided related to... Figure 5 The descriptions are different.

[0108] Figure 6 This is a diagram illustrating Example 600 associated with a scheduling request process for full-duplex and half-duplex modes according to this disclosure. The UE 120 sends a scheduling request (e.g., as described above in conjunction with...). Figure 4 and / or Figure 5 Prior to the description, the UE (e.g., UE 120) could use Example 600.

[0109] As shown in conjunction with reference numeral 605, before sending a scheduling request, UE 120 can determine whether a previous scheduling request is currently pending. In some aspects, UE 120 can only check pending scheduling requests associated with the same mode as the scheduling request. For example, when attempting to send a scheduling request associated with a half-duplex mode, UE 120 can check pending half-duplex mode scheduling requests. Similarly, when attempting to send a scheduling request associated with a full-duplex mode, UE 120 can check pending full-duplex mode scheduling requests.

[0110] As shown in conjunction with reference numeral 610, UE 120 can prevent the sending of scheduling requests when the scheduling request is pending. Therefore, when the determination described above in conjunction with reference numeral 605 returns '1' or true, UE 120 can prevent the sending of scheduling requests.

[0111] As shown in conjunction with reference numeral 615, when no scheduling request is pending (e.g., the determination described above in conjunction with reference numeral 605 returns "0" or false), UE 120 may start a counter for the scheduling request. For example, UE 120 may initialize the SR_COUNTER variable to 0 as defined in 3GPP specifications and / or another standard. In some aspects, when the scheduling request is associated with full-duplex mode, UE 120 may initialize a first variable (e.g., FD_SR_COUNTER) that differs from the second variable (e.g., HD_SR_COUNTER) used when the scheduling request is associated with half-duplex mode.

[0112] As shown in conjunction with reference numeral 620, UE 120 can determine whether at least one resource (e.g., a PUCCH resource) has been configured for the scheduling request. In some aspects, UE 120 can check only the resources associated with the same mode as the scheduling request. For example, when attempting to send a scheduling request associated with a half-duplex mode, UE 120 can check the resources associated with the half-duplex mode. Similarly, when attempting to send a scheduling request associated with a full-duplex mode, UE 120 can check the resources associated with the full-duplex mode.

[0113] As shown in conjunction with reference numeral 625, when no resources are configured for the scheduling request, UE 120 can initiate a RACH procedure (e.g., by sending a random access preamble). Therefore, when the determination described above in conjunction with reference numeral 620 returns '0' or false, UE 120 can send a random access preamble. In some aspects, UE 120 can use the same mode associated with the scheduling request to initiate the RACH procedure. For example, when the scheduling request is associated with full-duplex mode, UE 120 can send the random access preamble in full-duplex mode, and when the scheduling request is associated with half-duplex mode, UE 120 can send the random access preamble in half-duplex mode.

[0114] As shown in conjunction with reference numeral 630, when at least one resource is configured (e.g., the determination described above in conjunction with reference numeral 620 returns '1' or true), UE 120 may check whether a timer associated with the scheduling request is running. For example, UE 120 may check whether sr-ProhibitTimer, as defined in 3GPP specifications and / or another standard, is running. In some aspects, when the scheduling request is associated with full-duplex mode, UE 120 may check a first timer (e.g., FD-sr-ProhibitTimer) that differs from a second timer (e.g., HD-sr-ProhibitTimer) used when the scheduling request is associated with half-duplex mode.

[0115] While the timer is running, UE 120 can prevent the transmission of scheduling requests. Therefore, when the determination described above in conjunction with reference to reference numeral 630 returns '1' or true, UE 120 can prevent the transmission of scheduling requests.

[0116] As shown in conjunction with reference numeral 635, when the timer is not running (e.g., the determination described above in conjunction with reference numeral 630 returns "0" or false), UE 120 may check whether a counter limit (e.g., a threshold) associated with the scheduling request is satisfied. For example, UE 120 may check whether SR_COUNTER satisfies the sr-TransMax threshold as defined in 3GPP specifications and / or another standard. In some aspects, when the scheduling request is associated with full-duplex mode, UE 120 may check a first counter limit (e.g., whether FD_SR_COUNTER satisfies FD-sr-TransMax), which differs from the second counter limit used when the scheduling request is associated with half-duplex mode (e.g., whether HD_SR_COUNTER satisfies HD-sr-TransMax).

[0117] As shown in conjunction with reference numeral 640, when the counter limit is satisfied (e.g., the determination described above in conjunction with reference numeral 635 returns '1' or true), UE 120 can release the PUCCH configuration (and SRS configuration, SP-CSI configuration, SPS configuration, and / or CG) associated with the scheduling request. Furthermore, UE 120 can initiate a RACH procedure (e.g., by sending a random access preamble). In some aspects, UE 120 can initiate a RACH procedure using the same mode associated with the scheduling request. For example, when the scheduling request is associated with full-duplex mode, UE 120 can send the random access preamble in full-duplex mode, and when the scheduling request is associated with half-duplex mode, UE 120 can send the random access preamble in half-duplex mode.

[0118] As shown in conjunction with reference numeral 645, when the counter limit is not met (e.g., the determination described above in conjunction with reference numeral 635 returns '0' or false), UE 120 may send a scheduling request. Additionally, UE 120 may increment the counter associated with the scheduling request. For example, when the scheduling request is associated with full-duplex mode, UE 120 may increment a first counter (e.g., FD_SR_COUNTER), which is different from the second counter (e.g., HD_SR_COUNTER) used when the scheduling request is associated with half-duplex mode. Additionally, UE 120 may start a timer associated with the scheduling request, such that the timer is now running. For example, when the scheduling request is associated with full-duplex mode, UE 120 may start a first timer (e.g., FD-sr-ProhibitTimer), which is different from the second timer (e.g., HD-sr-ProhibitTimer) used when the scheduling request is associated with half-duplex mode. Therefore, when the corresponding timer has expired and the corresponding counter limit has not been met, UE 120 may retransmit the scheduling request.

[0119] As mentioned above, Figure 6 This is provided as an example. Other examples may be provided related to... Figure 6 The descriptions are different.

[0120] Figure 7 This is a diagram illustrating an example process 700 performed by a UE, etc., according to this disclosure. Example process 700 is a UE (e.g., UE 120 and / or...). Figure 11 An example of the device 1100 performing operations associated with configuring full-duplex and half-duplex modes for scheduling requests.

[0121] like Figure 7 As shown, in some aspects, process 700 may include data from a base station (e.g., base station 110 and / or...). Figure 12 The device 1200 receives a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode (block 710). For example, as described above, the UE (e.g., using...) Figure 11 The receiving component 1102 shown can receive a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode.

[0122] like Figure 7Further, in some aspects, process 700 may include sending a scheduling request to the base station using at least one resource associated with a half-duplex mode or at least one resource associated with a full-duplex mode (block 720). For example, as described above, the UE (e.g., using...) Figure 11 The transmitting component 1104 shown can use at least one resource associated with half-duplex mode or at least one resource associated with full-duplex mode to transmit scheduling requests.

[0123] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or one or more other processes described elsewhere herein.

[0124] In the first aspect, at least one resource associated with the half-duplex mode and at least one resource associated with the full-duplex mode are included in at least one BWP shared by the half-duplex mode and the full-duplex mode.

[0125] In the second aspect, either alone or in combination with the first aspect, at least one resource associated with the half-duplex mode includes one or more first PUCCH resources, and at least one resource associated with the full-duplex mode includes one or more second PUCCH resources separate from the one or more first PUCCH resources.

[0126] In the third aspect, either alone or in combination with one or more of the first and second aspects, the scheduling request configuration includes one or more PUCCH resources common to both half-duplex and full-duplex modes.

[0127] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the scheduling request configuration also includes a first timer associated with half-duplex mode and a second timer associated with full-duplex mode.

[0128] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the scheduling request is based at least in part on the determination that the first timer has not run (e.g., using...). Figure 11 The determination component 1108 shown or the second timer is not running is sent.

[0129] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the scheduling request configuration also includes a counter limit common to both half-duplex and full-duplex modes.

[0130] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the scheduling request is sent at least in part based on the determination that the counter limit is not satisfied (e.g., using determination component 1108).

[0131] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 700 further includes sending (e.g., using the sending component 1104) a random access preamble to the base station, at least in part based on the determination of counter limit satisfaction (e.g., using the determination component 1108), after sending the scheduling request.

[0132] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the scheduling request configuration also includes a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode.

[0133] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the scheduling request is sent at least in part based on the determination that the first counter limit is not met (e.g., using determination component 1108) or the determination that the second counter limit is not met (e.g., using determination component 1108).

[0134] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the scheduling request configuration also includes timers common to both half-duplex and full-duplex modes.

[0135] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the scheduling request is sent at least in part based on the determination that the timer is not running (e.g., using determination component 1108).

[0136] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 700 further includes transmitting (e.g., using transmission component 1104) a random access preamble to the base station based at least in part on the determination of a first counter limit satisfaction (e.g., using determination component 1108) or the determination of a second counter limit satisfaction (e.g., using determination component 1108).

[0137] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include more than Figure 7 The boxes shown may contain more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes of process 700 may be executed in parallel.

[0138] Figure 8 This is a diagram illustrating an example process 800 performed by a base station, for example, according to this disclosure. Example process 800 is a base station (e.g., base station 110 and / or...). Figure 12 An example of the device 1200 performing operations associated with configuring scheduling requests for full-duplex and half-duplex modes.

[0139] like Figure 8As shown, in some aspects, process 800 may include sending data to the UE (e.g., UE 120 and / or...). Figure 11 The device 1100 sends a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode (block 810). For example, as described above, the base station (e.g., using...) Figure 12 The transmitting component 1204 shown can transmit a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode.

[0140] like Figure 8 As further shown, in some aspects, process 800 may include receiving a scheduling request from the UE using at least one resource associated with a half-duplex mode or at least one resource associated with a full-duplex mode (block 820). For example, as described above, the base station (e.g., using...) Figure 12 The receiving component 1202 shown can use at least one resource associated with half-duplex mode or at least one resource associated with full-duplex mode to receive scheduling requests.

[0141] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or one or more other processes described elsewhere herein.

[0142] In the first aspect, at least one resource associated with the half-duplex mode and at least one resource associated with the full-duplex mode are included in at least one BWP shared by the half-duplex mode and the full-duplex mode.

[0143] In the second aspect, either alone or in combination with the first aspect, at least one resource associated with the half-duplex mode includes one or more first PUCCH resources, and at least one resource associated with the full-duplex mode includes one or more second PUCCH resources separate from the one or more first PUCCH resources.

[0144] In the third aspect, either alone or in combination with one or more of the first and second aspects, the scheduling request configuration includes one or more PUCCH resources common to both half-duplex and full-duplex modes.

[0145] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the scheduling request configuration also includes a first timer associated with half-duplex mode and a second timer associated with full-duplex mode.

[0146] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the scheduling request is received at least in part based on the fact that the first timer is not running or the second timer is not running.

[0147] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the scheduling request configuration also includes a counter limit common to both half-duplex and full-duplex modes.

[0148] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the scheduling request is received at least in part based on the non-satisfaction of the counter limit.

[0149] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 800 further includes receiving, at least in part, a random access preamble from the UE (e.g., using receiving component 1202) based on a counter limit after receiving a scheduling request.

[0150] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the scheduling request configuration also includes a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode.

[0151] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the scheduling request is received at least in part based on the non-satisfaction of the first counter limit or the non-satisfaction of the second counter limit.

[0152] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the scheduling request configuration also includes timers common to both half-duplex and full-duplex modes.

[0153] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the scheduling request is received at least in part based on the timer not running.

[0154] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 800 further includes receiving, at least in part, a random access preamble from the UE based on a first counter limit satisfaction or a second counter limit satisfaction after receiving a scheduling request (e.g., using receiving component 1202).

[0155] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include more than Figure 8 The boxes shown may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes of process 800 may be executed in parallel.

[0156] Figure 9 This is a diagram illustrating an example process 900 performed by a UE or the like according to this disclosure. Example process 900 is a UE (e.g., UE 120 and / or...). Figure 11 An example of the device 1100 performing operations associated with using the logical channel for full-duplex and half-duplex modes.

[0157] like Figure 9 As shown, in some aspects, process 900 may include data from a base station (e.g., base station 110 and / or...). Figure 12 The apparatus 1200 receives a configuration message indicating a logical channel configuration, which maps logical channels to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof (block 910). For example, as described above, the UE (e.g., using...) Figure 11 The receiving component 1102 shown can receive a configuration message indicating a logical channel configuration, which maps a logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof.

[0158] like Figure 9 As further shown, in some aspects, process 900 may include sending a scheduling request to the base station using a logical channel (block 920). For example, as described above, the UE (e.g., using...) Figure 11 The transmitting component 1104 shown can use a logical channel to send scheduling requests.

[0159] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or one or more other processes described elsewhere herein.

[0160] In some aspects, logical channel configuration also includes indicators for excluding logical channels from use in half-duplex or full-duplex modes.

[0161] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include more than Figure 9 The boxes shown may contain more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes of process 900 may be executed in parallel.

[0162] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, by a base station according to this disclosure. Example process 1000 is a base station (e.g., base station 110 and / or...). Figure 12An example of the device 1200 performing operations associated with using the logical channel for full-duplex and half-duplex modes.

[0163] like Figure 10 As shown, in some aspects, process 1000 may include sending data to the UE (e.g., UE 120 and / or...). Figure 11 The apparatus 1100 sends a configuration message indicating a logical channel configuration, which maps logical channels to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof (block 1010). For example, as described above, the base station (e.g., using...) Figure 12 The transmitting component 1204 shown can transmit a configuration message indicating a logical channel configuration, which maps a logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof.

[0164] like Figure 10 As further shown, in some aspects, process 1000 may include receiving a scheduling request from the UE using a logical channel (block 1020). For example, as described above, the base station (e.g., using...) Figure 12 The receiving component 1202 shown can use a logical channel to receive scheduling requests.

[0165] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or one or more other processes described elsewhere herein.

[0166] In some aspects, logical channel configuration also includes indicators for excluding logical channels from use in half-duplex or full-duplex modes.

[0167] although Figure 10 An example box of process 1000 is shown, but in some respects, process 1000 may include more than Figure 10 The boxes shown may include more boxes, fewer boxes, different boxes, or boxes arranged differently. Additionally or alternatively, two or more boxes of process 1000 may be executed in parallel.

[0168] Figure 11This is a block diagram of an example device 1100 for wireless communication. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 can use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, in other examples, device 1100 may include a determining component 1108.

[0169] In some respects, device 1100 can be configured to perform the functions described herein. Figures 4 to 6 One or more operations described herein. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 7 The process 700 Figure 9 The process 900 or a combination thereof. In some respects, Figure 11 The illustrated device 1100 and / or one or more components may include the above combinations. Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 11 One or more components shown can be combined as described above. Figure 2 Implemented in one or more of the described components. Additionally or alternatively, one or more of the components in this group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0170] Receiver 1102 may receive communications from device 1106, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 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), and may provide the processed signals to one or more other components of device 1106. In some aspects, receiver 1102 may include combinations of the above. Figure 2 The described UE includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0171] Transmitting component 1104 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1106. In some aspects, one or more other components of device 1106 can generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1106. In some aspects, transmitting component 1104 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signals to device 1106. In some aspects, transmitting component 1104 can include combinations of the above. Figure 2 The described UE includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in a transceiver.

[0172] In some aspects, receiving component 1102 can receive from device 1106 a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with half-duplex mode of device 1100 and at least one resource associated with full-duplex mode of device 1100. Therefore, transmitting component 1104 can send a scheduling request to device 1106 using either the at least one resource associated with half-duplex mode or the at least one resource associated with full-duplex mode.

[0173] In some aspects, the scheduling request configuration may include a first timer associated with half-duplex mode and a second timer associated with full-duplex mode. Therefore, determining component 1108 can determine whether the first timer is not running or the second timer is not running. In some aspects, determining component 1108 may include a combination of the above. Figure 2 The described UE includes a transmit MIMO processor, a transmit processor, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof. Therefore, the transmit component 1104 can transmit a scheduling request at least in part based on a determination that a first timer has not run or a determination that a second timer has not run.

[0174] Alternatively, the scheduling request configuration may include a timer common to both half-duplex and full-duplex modes. Therefore, the determining component 1108 can determine that the timer is not running. Thus, the sending component 1104 can send the scheduling request at least in part based on the determination that the timer is not running.

[0175] Additionally or alternatively, the scheduling request configuration may include a counter limit common to both half-duplex and full-duplex modes. Therefore, determining component 1108 can determine that the counter limit is not met. Therefore, transmitting component 1104 can transmit the scheduling request at least in part based on the determination that the counter limit is not met. In some aspects, determining component 1108 can determine that the counter limit is met. Therefore, transmitting component 1104 can transmit a random access preamble to device 1106 after transmitting the scheduling request, at least in part based on the determination that the counter limit is met.

[0176] Alternatively, the scheduling request configuration may include a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode. Therefore, the determining component 1108 may determine that either the first counter limit or the second counter limit is not satisfied. Therefore, the transmitting component 1104 may transmit the scheduling request at least in part based on the determination that either the first or second counter limit is not satisfied. In some aspects, the determining component 1108 may determine that either the first or second counter limit is satisfied. Therefore, the transmitting component 1104 may, after transmitting the scheduling request, transmit a random access preamble to the device 1106 at least in part based on the determination that either the first or second counter limit is satisfied.

[0177] In some respects, the configuration message may additionally or alternatively indicate a logical channel configuration that maps a logical channel to a corresponding scheduling request configuration associated with the half-duplex mode of device 1100, a corresponding scheduling request configuration associated with the full-duplex mode of device 1100, or a combination thereof. Therefore, the transmitting component 1104 can use the logical channel to send a scheduling request to device 1106.

[0178] Figure 11 The number and arrangement of components shown are provided as an example. In reality, there may be more... Figure 11 This shows more components, fewer components, different components, or components arranged differently. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The set (one or more) components shown can perform actions described by Figure 11 The other set of components shown performs one or more functions.

[0179] Figure 12This is a block diagram of an example device 1200 for wireless communication. Device 1200 may be a base station, or a base station may include device 1200. In some aspects, device 1200 includes a receiving component 1202 and a transmitting component 1204, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1200 can use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1206 (such as a UE, a base station, or another wireless communication device). As further shown, in other examples, device 1200 may include an encoding component 1208.

[0180] In some respects, device 1200 can be configured to perform the functions described herein. Figures 4 to 5 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process 800 Figure 10 The process 1000 or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include the above combination. Figure 2 One or more components of the described base station. Additionally or alternatively, Figure 12 One or more components shown can be combined as described above. Figure 2 Implemented in one or more of the described components. Additionally or alternatively, one or more of the components in this group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0181] Receiver 1202 may receive communications from device 1206, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 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), and may provide the processed signals to one or more other components of device 1206. In some aspects, receiver 1202 may include combinations of the above. Figure 2 The described base station includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0182] Transmitting component 1204 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1206. In some aspects, one or more other components of device 1206 can generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1206. In some aspects, transmitting component 1204 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signals to device 1206. In some aspects, transmitting component 1204 can include combinations of the above. Figure 2 The described base station includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in a transceiver.

[0183] The transmitting component 1204 can send a configuration message indicating a scheduling request configuration to the device 1206. The scheduling request configuration includes at least one resource associated with the half-duplex mode of the device 1206 and at least one resource associated with the full-duplex mode of the device 1206. Therefore, the receiving component 1202 can receive the scheduling request from the device 1206 using either the at least one resource associated with the half-duplex mode or the at least one resource associated with the full-duplex mode.

[0184] In some aspects, the scheduling request configuration may include a first timer associated with half-duplex mode and a second timer associated with full-duplex mode. Therefore, the encoding component 1208 may encode the first and second timers into the configuration message. In some aspects, the encoding component 1208 may include a combination of the above. Figure 2 The described base station includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. Therefore, when the first timer is not running or the second timer is not running, the receiving component 1202 can receive a scheduling request.

[0185] As an alternative, the scheduling request configuration may include timers common to both half-duplex and full-duplex modes. Therefore, encoding component 1208 can encode the timers into the configuration message. Thus, receiving component 1202 can receive scheduling requests when the timers are not running.

[0186] Additionally or alternatively, the scheduling request configuration may include a counter limit common to both half-duplex and full-duplex modes. Therefore, encoding component 1208 can encode the counter limit into the configuration message. Thus, receiving component 1202 can receive the scheduling request when the counter limit is not met. In some aspects, receiving component 1202 can receive a random access preamble from device 1206 after receiving the scheduling request, at least in part based on the satisfaction of the counter limit.

[0187] Alternatively, the scheduling request configuration may include a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode. Therefore, encoding component 1208 can encode the first and second counter limits into the configuration message. Thus, receiving component 1202 can receive the scheduling request when either the first or second counter limit is not satisfied. In some aspects, receiving component 1202 can receive a random access preamble from device 1206 after receiving the scheduling request, at least in part based on whether the first or second counter limit is satisfied.

[0188] In some aspects, the configuration message may additionally or alternatively indicate a logical channel configuration that maps the logical channel to a corresponding scheduling request configuration associated with the half-duplex mode of device 1206, a corresponding scheduling request configuration associated with the full-duplex mode of device 1206, or a combination thereof. Therefore, receiving component 1202 can use the logical channel to receive scheduling requests from device 1206.

[0189] Figure 12 The number and arrangement of components shown are provided as an example. In reality, there may be more... Figure 12 This shows more components, fewer components, different components, or components arranged differently. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The set (one or more) components shown can perform actions described by Figure 12 The other set of components shown performs one or more functions.

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

[0191] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving from a base station a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and sending a scheduling request to the base station using the at least one resource associated with the half-duplex mode or the at least one resource associated with the full-duplex mode.

[0192] Aspect 2: According to the method of aspect 1, wherein at least one resource associated with the half-duplex mode and at least one resource associated with the full-duplex mode are included in at least one bandwidth portion shared by the half-duplex mode and the full-duplex mode.

[0193] Aspect 3: According to the method of any one of Aspects 1 to 2, wherein at least one resource associated with the half-duplex mode includes one or more first physical uplink control channel (PUCCH) resources, and at least one resource associated with the full-duplex mode includes one or more second PUCCH resources separate from one or more first PUCCH resources.

[0194] Aspect 4: According to the method of any one of Aspects 1 to 3, wherein the scheduling request configuration includes one or more Physical Uplink Control Channel (PUCCH) resources shared by both half-duplex and full-duplex modes.

[0195] Aspect 5: According to the method of any one of Aspects 1 to 4, wherein the scheduling request configuration further includes a first timer associated with half-duplex mode and a second timer associated with full-duplex mode.

[0196] Aspect 6: According to the method of aspect 5, the scheduling request is sent at least in part based on the determination that the first timer has not run or the determination that the second timer has not run.

[0197] Aspect 7: According to the method of any one of Aspects 1 to 6, wherein the scheduling request configuration also includes a counter limit common to both half-duplex and full-duplex modes.

[0198] Aspect 8: According to the method of aspect 7, the scheduling request is sent at least in part based on the determination that the counter limit is not satisfied.

[0199] Aspect 9: The method according to any one of Aspects 7 to 8 further includes: sending a random access preamble to the base station at least in part based on the determination of the counter limit satisfaction after sending the scheduling request.

[0200] Aspect 10: According to the method of any one of Aspects 1 to 6, wherein the scheduling request configuration further includes a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode.

[0201] Aspect 11: According to the method of aspect 10, the scheduling request is sent at least in part based on the determination that the first counter limit is not satisfied or the determination that the second counter limit is not satisfied.

[0202] Aspect 12: According to the method of any one of Aspects 10 to 11, wherein the scheduling request configuration also includes a timer common to both half-duplex and full-duplex modes.

[0203] Aspect 13: According to the method of aspect 12, the scheduling request is sent at least in part based on the determination that the timer is not running.

[0204] Aspect 14: The method according to any one of aspects 10 to 13 further includes: sending a random access preamble to the base station at least in part based on the determination of the satisfaction of the first counter limit or the determination of the satisfaction of the second counter limit after sending the scheduling request.

[0205] Aspect 15: According to the method of any one of Aspects 1 to 14, wherein the configuration message further indicates a logical channel configuration that maps a logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof, wherein the scheduling request is sent using the logical channel.

[0206] Aspect 16: According to the method of aspect 15, the logical channel configuration further includes an indicator for excluding the logical channel from use in half-duplex or full-duplex mode.

[0207] Aspect 17: A method of wireless communication performed by a base station, comprising: sending to a user equipment (UE) a configuration message indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with a half-duplex mode of the UE and at least one resource associated with a full-duplex mode of the UE; and receiving a scheduling request from the UE using the at least one resource associated with the half-duplex mode or the at least one resource associated with the full-duplex mode.

[0208] Aspect 18: According to the method of aspect 17, at least one resource associated with the half-duplex mode and at least one resource associated with the full-duplex mode are included in at least one bandwidth portion shared by the half-duplex mode and the full-duplex mode.

[0209] Aspect 19: The method according to any one of aspects 17 to 18, wherein at least one resource associated with the half-duplex mode includes one or more first physical uplink control channel (PUCCH) resources, and at least one resource associated with the full-duplex mode includes one or more second PUCCH resources separate from one or more first PUCCH resources.

[0210] Aspect 20: According to the method of any one of Aspects 17 to 19, wherein the scheduling request configuration includes one or more Physical Uplink Control Channel (PUCCH) resources shared by both half-duplex and full-duplex modes.

[0211] Aspect 21: According to the method of any one of Aspects 17 to 20, wherein the scheduling request configuration further includes a first timer associated with half-duplex mode and a second timer associated with full-duplex mode.

[0212] Aspect 22: According to the method of aspect 21, the scheduling request is received at least in part based on the fact that the first timer is not running or the second timer is not running.

[0213] Aspect 23: According to the method of any one of Aspects 17 to 22, wherein the scheduling request configuration also includes a counter limit common to both half-duplex and full-duplex modes.

[0214] Aspect 24: According to the method of aspect 23, the scheduling request is received at least in part based on the fact that the counter limit is not satisfied.

[0215] Aspect 25: According to the method of any one of aspects 23 to 24, the method further includes: receiving a random access preamble from the UE at least in part based on the satisfaction of a counter limit after receiving a scheduling request.

[0216] Aspect 26: According to the method of any one of Aspects 17 to 22, wherein the scheduling request configuration further includes a first counter limit associated with half-duplex mode and a second counter limit associated with full-duplex mode.

[0217] Aspect 27: According to the method of aspect 26, the scheduling request is received at least in part based on the failure of a first counter limit or a second counter limit.

[0218] Aspect 28: According to the method of any one of Aspects 26 to 27, wherein the scheduling request configuration also includes a timer shared by half-duplex mode and full-duplex mode.

[0219] Aspect 29: According to the method of aspect 28, the scheduling request is received at least in part based on the timer not running.

[0220] Aspect 30: According to the method of any one of aspects 26 to 29, the method further includes: receiving a random access preamble from the UE at least in part based on the satisfaction of a first counter limit or a second counter limit after receiving a scheduling request.

[0221] Aspect 31: According to the method of any one of Aspects 17 to 30, wherein the configuration message further indicates a logical channel configuration that maps a logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof, wherein the scheduling request is received using the logical channel.

[0222] Aspect 32: According to the method of aspect 31, the logical channel configuration further includes an indicator for excluding the logical channel from use in half-duplex mode or full-duplex mode.

[0223] Aspect 33: A method of wireless communication performed by a user equipment (UE), comprising: receiving from a base station a configuration message indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the UE, a corresponding scheduling request configuration associated with a full-duplex mode of the UE, or a combination thereof; and sending a scheduling request to the base station using the logical channel.

[0224] Aspect 34: According to the method of aspect 33, the logical channel configuration further includes an indicator for excluding the logical channel from use in half-duplex or full-duplex mode.

[0225] Aspect 35: A method of wireless communication performed by a base station, comprising: sending a configuration message to a user equipment (UE) indicating a logical channel configuration, the logical channel configuration mapping the logical channel to a corresponding scheduling request configuration associated with a half-duplex mode of the UE, a corresponding scheduling request configuration associated with a full-duplex mode of the UE, or a combination thereof; and receiving a scheduling request from the UE using the logical channel.

[0226] Aspect 36: According to the method of aspect 35, the logical channel configuration further includes an indicator for excluding the logical channel from use in half-duplex or full-duplex mode.

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

[0228] Aspect 38: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 1 to 16.

[0229] Aspect 39: An apparatus for wireless communication, comprising at least one component for performing the methods of one or more aspects of aspects 1 to 16.

[0230] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more of aspects 1 to 16.

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

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

[0233] Aspect 43: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 17 to 32.

[0234] Aspect 44: An apparatus for wireless communication, comprising at least one component for performing the methods of one or more aspects of aspects 17 to 32.

[0235] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more aspects of aspects 17 to 32.

[0236] Aspect 46: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the methods of one or more aspects of aspects 17 to 32.

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

[0238] Aspect 48: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 33 to 34.

[0239] Aspect 49: An apparatus for wireless communication, comprising at least one component for performing the methods of one or more aspects of aspects 33 to 34.

[0240] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more aspects of aspects 33 to 34.

[0241] Aspect 51: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the methods of one or more aspects of aspects 33 to 34.

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

[0243] Aspect 53: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 35 to 36.

[0244] Aspect 54: An apparatus for wireless communication, comprising at least one component for performing the methods of one or more aspects of aspects 35 to 36.

[0245] Aspect 55: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform methods of one or more aspects of aspects 35 to 36.

[0246] Aspect 56: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions, which, when executed by one or more processors of a device, cause the device to perform the methods of one or more aspects of aspects 35 to 36.

[0247] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit these aspects to the precise forms disclosed. Modifications and variations may be made based on the foregoing disclosure, or from practice in these aspects.

[0248] As used herein, the term "component" is intended to be interpreted broadly as hardware, and / or a combination of hardware and software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, application programs, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, flows, and / or functions, and other examples, whether referring to software, firmware, middleware, microcode, hardware description languages, or others. As used herein, a processor is implemented in hardware, and / or a combination of hardware and software. It is evident that the systems and / or methods described herein can be implemented in various forms of hardware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, while this document describes the operation and behavior of systems and / or methods without reference to specific software code, it should be understood that software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0249] As used in this article, depending on the context, satisfying the threshold can refer to a value that is 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.

[0250] Even if a particular combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the aspects. In fact, many of these features can be combined in ways not specifically stated in the claims and / or not disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the aspects includes combinations of each dependent claim with each other claim in the claim set. As used herein, the phrase “at least one” referring to the list of items means any combination of those items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or other orders of a, b, and c).

[0251] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, “described” is intended to include one or more items associated with “described” and may be used interchangeably with “described one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” If referring to only one item, the phrase “only one” or similar language is used. Furthermore, as used herein, the term “having” or similar terms are intended to be open-ended terms. Further, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, unless explicitly stated otherwise, as used herein, the term “or” is inclusive in a series of uses and may be used interchangeably with “and / or” (e.g., if used in conjunction with “any” or “only one”).

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory, including instructions; and One or more processors are configured to execute the instructions to cause the UE to: Receive a configuration message from a network entity indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode; as well as A scheduling request is sent to the network entity using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

2. The UE according to claim 1, wherein, The at least one resource associated with the half-duplex mode and the at least one resource associated with the full-duplex mode are included in at least one bandwidth portion shared by the half-duplex mode and the full-duplex mode.

3. The UE according to claim 1, wherein, The at least one resource associated with the half-duplex mode includes one or more first physical uplink control channel (PUCCH) resources, and the at least one resource associated with the full-duplex mode includes one or more second PUCCH resources separate from the one or more first PUCCH resources.

4. The UE according to claim 1, wherein, The scheduling request configuration includes one or more Physical Uplink Control Channel (PUCCH) resources shared by the half-duplex mode and the full-duplex mode.

5. The UE according to claim 1, wherein, The scheduling request configuration also includes a first timer associated with the half-duplex mode and a second timer associated with the full-duplex mode.

6. The UE according to claim 5, wherein, The scheduling request is sent at least in part based on a determination that the first timer is not running or a determination that the second timer is not running.

7. The UE according to claim 5, wherein, The scheduling request configuration also includes a counter limit common to both the half-duplex mode and the full-duplex mode.

8. The UE according to claim 7, wherein, The scheduling request is sent at least in part based on the determination that the counter limit is not met.

9. The UE according to claim 7, wherein, The one or more processors are further configured to execute the instructions to cause the UE to: After sending the scheduling request, a random access preamble is sent to the network entity, at least in part based on the determination that the counter limit is satisfied.

10. The UE according to claim 1, wherein, The scheduling request configuration also includes a first counter limit associated with the half-duplex mode and a second counter limit associated with the full-duplex mode.

11. The UE according to claim 10, wherein, The scheduling request is sent at least in part based on the determination that the first counter limit is not met or the second counter limit is not met.

12. The UE according to claim 10, wherein, The scheduling request configuration also includes a timer common to both the half-duplex mode and the full-duplex mode.

13. The UE according to claim 12, wherein, The scheduling request is sent at least in part based on the determination that the timer is not running.

14. The UE according to claim 10, wherein, The one or more processors are further configured to execute the instructions to cause the UE to: After sending the scheduling request, a random access preamble is sent to the network entity at least in part based on the determination that the first counter limit is satisfied or the second counter limit is satisfied.

15. A network entity for wireless communication, comprising: Memory, including instructions; and One or more processors are configured to execute the instructions to cause the network entity to: Send a configuration message indicating a scheduling request configuration to a user equipment (UE), the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode; as well as The scheduling request is received from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

16. The network entity according to claim 15, wherein, The at least one resource associated with the half-duplex mode includes one or more first physical uplink control channel (PUCCH) resources, and the at least one resource associated with the full-duplex mode includes one or more second PUCCH resources separate from the one or more first PUCCH resources.

17. The network entity according to claim 15, wherein, The scheduling request configuration also includes a first timer associated with the half-duplex mode and a second timer associated with the full-duplex mode.

18. The network entity according to claim 17, wherein, The scheduling request is received at least in part based on the first timer not running or the second timer not running.

19. The network entity according to claim 17, wherein, The scheduling request configuration also includes a counter limit common to both the half-duplex mode and the full-duplex mode.

20. The network entity according to claim 19, wherein, The scheduling request is received at least in part based on the fact that the counter limit is not met.

21. The network entity according to claim 19, wherein, The one or more processors are also configured to execute the instructions to cause the network entity to: After receiving the scheduling request, the UE receives a random access preamble based at least in part on the satisfaction of the counter limit.

22. The network entity according to claim 17, wherein, The scheduling request configuration also includes a first counter limit associated with the half-duplex mode and a second counter limit associated with the full-duplex mode.

23. The network entity according to claim 22, wherein, The scheduling request is received at least in part based on the first counter limit not being met or the second counter limit not being met.

24. The network entity according to claim 22, wherein, The scheduling request configuration also includes a timer common to both the half-duplex mode and the full-duplex mode.

25. The network entity according to claim 24, wherein, The scheduling request is received at least in part based on the fact that the timer is not running.

26. The network entity according to claim 22, wherein, The one or more processors are also configured to execute the instructions to cause the network entity to: After receiving the scheduling request, a random access preamble is received from the UE at least in part based on either the satisfaction of the first counter limit or the satisfaction of the second counter limit.

27. A user equipment (UE) for wireless communication, comprising: Memory, including instructions; and One or more processors are configured to execute the instructions to cause the UE to: Receive a configuration message from a network entity indicating a logical channel configuration, wherein the logical channel configuration maps a logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof. as well as The scheduling request is sent to the network entity using the logical channel.

28. The UE according to claim 27, wherein, The logical channel configuration also includes an indicator for excluding the logical channel from use in the half-duplex mode or the full-duplex mode.

29. A network entity for wireless communication, comprising: Memory, including instructions; and One or more processors are configured to execute the instructions to cause the network entity to: Send a configuration message to the user equipment (UE) indicating a logical channel configuration, wherein the logical channel configuration maps the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof. as well as The scheduling request is received from the UE using the logical channel.

30. The network entity according to claim 29, wherein, The logical channel configuration also includes an indicator for excluding the logical channel from use in the half-duplex mode or the full-duplex mode.

31. A method for wireless communication performed by a user equipment (UE), comprising: Receive a configuration message from a network entity indicating a scheduling request configuration, the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode; as well as A scheduling request is sent to the network entity using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

32. A method for wireless communication performed by a network entity, comprising: Send a configuration message indicating a scheduling request configuration to a user equipment (UE), the scheduling request configuration including at least one resource associated with the UE's half-duplex mode and at least one resource associated with the UE's full-duplex mode; as well as The scheduling request is received from the UE using at least one resource associated with the half-duplex mode or at least one resource associated with the full-duplex mode.

33. A method for wireless communication performed by a user equipment (UE), comprising: Receive a configuration message from a network entity indicating a logical channel configuration, wherein the logical channel configuration maps a logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof. as well as The scheduling request is sent to the network entity using the logical channel.

34. A method for wireless communication performed by a network entity, comprising: Send a configuration message to the user equipment (UE) indicating a logical channel configuration, wherein the logical channel configuration maps the logical channel to a corresponding scheduling request configuration associated with the UE's half-duplex mode, a corresponding scheduling request configuration associated with the UE's full-duplex mode, or a combination thereof. as well as The scheduling request is received from the UE using the logical channel.

35. An apparatus for wireless communication performed by a user equipment (UE), comprising components for performing the method according to claim 31 or 33.

36. An apparatus for wireless communication performed by a network entity, comprising components for performing the method according to claim 32 or 34.

37. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a user equipment (UE) to cause the processors to perform the method according to claim 31 or 33.

38. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a network entity to cause the processors to perform the method according to claim 32 or 34.

39. A computer program product comprising computer-readable instructions that, when executed by a processor, cause the processor to perform the method according to claim 31 or 33.

40. A computer program product comprising computer-readable instructions that, when executed by a processor, cause the processor to perform the method according to claim 32 or 34.

Images