Requests for conservative scheduling periods

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send a conservative scheduling request (CSR) medium access control control element (MAC-CE) during a random access channel (RACH) procedure to request a conservative scheduling period, the conservative scheduling period associated with a certain duration. The UE may transmit an uplink transmission during the conservative scheduling period that is established for the duration based at least in part on the CSR MAC-CE. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to wireless communication and techniques and apparatus for conserving requests for scheduling periods. Background Art

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

[0003] A wireless network may include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., sidelink (SL), Wireless Local Area Network (WLAN) link, and / or Wireless Personal Area Network (WPAN) link, etc.).

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

[0005] In some specific embodiments, an apparatus for wireless communication at a user equipment (UE) includes: a memory; and one or more processors coupled to the memory and configured to: send a conservative scheduling request (CSR) medium access control control element (MAC-CE) during a random access channel (RACH) procedure to request a conservative scheduling period associated with a certain duration; and send an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0006] In some specific embodiments, an apparatus for wireless communication at a network node includes: a memory; and one or more processors coupled to the memory and configured to: receive a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and receive an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0007] In some specific embodiments, a wireless communication method performed by a UE includes: sending a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and sending an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0008] In some specific embodiments, a wireless communication method performed by a network node includes: receiving a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and receiving an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0009] In some specific embodiments, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: send a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and send an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0010] In some specific embodiments, a non-transitory computer-readable medium storing instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: receive a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and receive an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0011] In some specific embodiments, an apparatus for wireless communication includes means for: transmitting a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and means for: transmitting an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0012] In some specific embodiments, an apparatus for wireless communication includes means for: receiving a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and means for: receiving an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0013] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and the specification and illustrated in the accompanying drawings and the specification.

[0014] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein in terms of both their organization and method of operation, as well as the associated advantages, will be better understood when considered in conjunction with the following description taken in connection with the accompanying drawings. Each of the accompanying drawings provided is for the purpose of illustration and description and is not to be construed as a definition of the limits of the claims.

[0015] While aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such 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 packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] To obtain a more particular description of the above-described features of the present disclosure, reference may be made to aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the description may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

[0018] Figure 2 is a diagram illustrating an example of a network node communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of restricted uplink transmission quality according to the present disclosure.

[0021] Figure 5 is a diagram illustrating another example of restricted uplink transmission quality according to the present disclosure.

[0022] Figures 6 to 8Is a diagram illustrating an example associated with a request for a conservative scheduling period according to the present disclosure.

[0023] Figures 9 to 10 Is a diagram of an example process associated with a request for a conservative scheduling period according to the present disclosure.

[0024] Figures 11 to 12 Is a diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Description

[0025] Various aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such an apparatus or method practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

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

[0027] Although terms that are generally associated with 5G or new radio (NR) radio access technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0028] Figure 1FIG. is an illustration of an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, and so on. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, network nodes 110b, network nodes 110c, and network nodes 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, UEs 120b, UEs 120c, UEs 120d, and UEs 120e), and / or other entities. The network nodes 110 are network nodes that communicate with the UEs 120. As shown, the network nodes 110 may include one or more network nodes. For example, the network nodes 110 may be aggregated network nodes, which means that the aggregated network nodes are configured to utilize a radio protocol stack physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network nodes 110 may be disaggregated network nodes (sometimes referred to as disaggregated base stations), which means that the network nodes 110 are configured to utilize a protocol stack physically or logically distributed between two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0029] In some examples, the network nodes 110 are or include network nodes (such as RUs) that communicate with the UEs 120 via radio access links. In some examples, the network nodes 110 are or include network nodes (such as DUs) that communicate with other network nodes 110 via fronthaul links or midhaul links. In some examples, the network nodes 110 are or include network nodes (such as CUs) that communicate with other network nodes 110 via midhaul links or communicate with the core network via a backhaul link. In some examples, the network nodes 110 (such as aggregated network nodes 110 or disaggregated network nodes 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network nodes 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, transmit receive points (TRPs), DUs, RUs, CUs, mobility elements of the network, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, the network nodes 110 may be interconnected with each other or interconnected to one or more other network nodes 110 in the wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0030] In some examples, network node 110 may provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographical area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographical area and may allow unrestricted access by UEs 120 with a service subscription. A femto cell may cover a relatively small geographical area (e.g., a home) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macro cell may be referred to as a macro network node. The network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. In Figure 1 the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographical area of a cell may move according to the location of a moving network node 110 (e.g., a mobile network node).

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

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

[0033] Wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watt to 2 watts).

[0034] The network controller 130 may be coupled to or communicate with a set of network nodes 110, and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a fronthaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other, or indirectly via a wireless fronthaul communication link or a wired fronthaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

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

[0036] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. The MTC UE and / or eMTC UE may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices, and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

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

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

[0041] Considering the above examples, unless otherwise specifically stated, it should be understood that if terms such as "below 6 GHz" are used herein, such terms can broadly represent frequencies that can be below 6 GHz, can be within FR1, or can include intermediate band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if terms such as "millimeter wave" are used herein, such terms can broadly represent frequencies that can include intermediate band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein apply to those modified frequency ranges.

[0042] In some aspects, a UE (e.g., UE 120) can include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 can send a conservative scheduling request (CSR) medium access control control element (MAC-CE) during a random access channel (RACH) procedure to request a conservative scheduling period associated with a certain duration; and send an uplink transmission during the conservative scheduling period, which is established for the duration at least in part based on the CSR MAC-CE. Additionally or alternatively, the communication manager 140 can perform one or more other operations described herein.

[0043] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and receive an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0044] As indicated above, Figure 1 is provided as an example. Other examples may differ from the example Figure 1 described.

[0045] Figure 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

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

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

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

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

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

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

[0052] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other component of may perform one or more techniques associated with a request for a conservative scheduling period, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other component of may execute or direct, for example Figure 9 process 900 of, Figure 10 process 1000 of, and / or the operation of other processes as described herein. The memories 242 and 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, the memories 242 and / or 282 may include non-transitory computer-readable media storing one or more instructions for wireless communication (e.g., code and / or program code). For example, when the one or more instructions are executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or after compilation, transformation, and / or interpretation), the one or more processors, UE 120, and / or network node 110 may be caused to execute or direct, for example Figure 9 process 900 of, Figure 10 process 1000 of, and / or the operation of other processes as described herein. In some examples, executing the instructions may include running the instructions, transforming the instructions, compiling the instructions, and / or interpreting the instructions, etc.

[0053] In some aspects, a UE (e.g., UE 120) includes components for: sending a CSR MAC-CE during a RACH procedure to request a conservative scheduling period associated with a certain duration; and / or components for: sending an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration based at least in part on the CSR MAC-CE. The components for a UE to perform the operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0054] In some aspects, the network node includes components for: receiving a CSRMAC-CE during a RACH procedure to request a conservative scheduling period, the conservative scheduling period being associated with a certain duration; and / or for: receiving an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least partially based on the CSRMAC-CE. The components for the network node to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

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

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

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

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

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

[0060] Figure 3 FIG. is an illustration of an example split base station architecture 300 in accordance with the present disclosure. The split base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more split control units (such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each DU among the DUs 330 may communicate with one or more RUs 340 via a respective fronthaul link. Each RU among the RUs 340 may communicate with one or more UEs 120 via a respective radio frequency (RF) access link. In some embodiments, a UE 120 may be served simultaneously by multiple RUs 340.

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

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

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

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

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

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

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

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

[0069] When the UE is in the RRC connected mode, uplink transmission may be critical for the UE. When operating in the RRC connected mode, the UE may attempt to perform critical uplink transmissions. The uplink transmission can be a control plane message transmission or a data plane transmission.

[0070] However, the uplink transmission of the UE may be affected by multiple factors, such as poor channel conditions, Tx power margin, and / or UE Tx device state. When the UE has a temporary limited uplink transmission capability change (such as lack of sufficient Tx power or Tx link imbalance / shortage to support dual-layer (2L) physical uplink shared channel (PUSCH) transmission or relatively large resource block (RB) size transmission), the UE may not be able to notify the network node of this temporary limited uplink transmission capability change. Inefficient or poor PUSCH transmissions performed by the UE may prevent the network node from learning about the UE's temporary limited uplink transmission capability change. As a result, the network node may not receive critical messages from the UE, such as RRC measurement reports, UE assistance information (UAI) messages, Internet protocol (IP) multimedia subsystem (IMS) signaling, and / or power headroom report (PHR) MAC-CE. Such critical messages may be intended to assist the UE in such a situation but may not be successfully delivered by the UE to the network node.

[0071] UAI may allow a UE to notify a network node of a desired connected mode discontinuous reception (CDRX) configuration, a desired bandwidth, a desired number of carriers, a desired maximum number of layers, and / or a desired RRC state transition. The UE may send the UAI to the network node based at least in part on an RRC reconfiguration received from the network node. The UE may trigger the UAI for different purposes, such as for power benefits. The UAI may also be triggered when the UE experiences a temporary capability degradation due to low battery power, thermal limitations, a temporary performance degradation on some Tx / Rx chains, or resource sharing limitations between two subscriptions in a multi-subscriber identity module (SIM) (MSIM) UE.

[0072] In a first example where uplink transmission quality may be limited, the UE may be in an uplink power limited region, or the UE may have poor quality on a Tx chain. The Tx chain may be one of multiple Tx chains associated with the UE. The UE may be unable to perform a correct transmission for a spatial multiplexing dual layer (SMDL) (e.g., 2L) uplink grant, or the UE may be unable to perform a correct transmission for a single layer, relatively large RB size grant, which may be due to the uplink transmission quality being limited. As a result, the network node may not correctly receive a measurement report, and a UE radio link failure (RLF) may occur due to not receiving a handover command in a timely manner. Alternatively, the UE may desire to trigger the UAI to notify the network node of a preferred MIMO layer, bandwidth, or component carrier, but the UE may be unable to correctly send a UAI message to the network node.

[0073] Figure 4 is a diagram illustrating example 400 of limited uplink transmission quality according to the present disclosure. As Figure 4 shown, example 400 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network, such as wireless network 100.

[0074] As indicated by reference numeral 402, the UE may send a measurement report, which may not be successfully received by the network node. As indicated by reference numeral 404, the UE may send a PUSCH transmission to the network node, and as indicated by reference numeral 406, the network node may send a negative acknowledgment (NACK) in response to the PUSCH transmission. As indicated by reference numeral 408, the UE may send a PUSCH transmission to the network node, and as indicated by reference numeral 410, the network node may send a NACK in response to the PUSCH transmission. As indicated by reference numeral 412, the UE may send a PUSCH transmission to the network node, and as indicated by reference numeral 414, the network node may send a NACK in response to the PUSCH transmission. The multiple PUSCH transmissions and the corresponding NACK transmissions may be at least partially based on the uplink transmission quality of the UE being limited. As indicated by reference numeral 416, the UE may experience RLF. As indicated by reference numeral 418, the network node may fail to successfully receive the measurement report from the UE. As indicated by reference numeral 420, the network node may send a handover command, but due to the RLF, the UE may not be able to receive the handover command. In other words, the network node may not send the handover command in time before the UE experiences RLF.

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

[0076] In a second example where the uplink transmission quality may be limited, due to hardware or RF limitations, the MSIM UE may have temporary limitations on the supported Tx or receive (Rx) chains. The MSIM UE may expect to send a UAI message to indicate a preferred configuration, but due to consistent 2L uplink grants, the MSIM device may not be able to correctly send the UAI message.

[0077] Figure 5 is a diagram illustrating Example 500 of limited uplink transmission quality in accordance with the present disclosure. As Figure 5 shown, Example 500 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0078] As indicated by reference numeral 502, the UE may send a UAI, which may not be successfully received by the network node initially. As indicated by reference numeral 504, the UE may send a PUSCH transmission to the network node, and as indicated by reference numeral 506, the network node may send a NACK in response to the PUSCH transmission. As indicated by reference numeral 508, the UE may send a PUSCH transmission to the network node, and as indicated by reference numeral 510, the network node may send a NACK in response to the PUSCH transmission. As indicated by reference numeral 512, the UE may send a PUSCH transmission to the network node, and as indicated by reference numeral 514, the network node may send a NACK in response to the PUSCH transmission. The multiple PUSCH transmissions and the corresponding NACK transmissions may be at least partially based on the uplink transmission quality of the UE being restricted. As indicated by reference numeral 516, the network node may fail to receive the UAI from the UE. As indicated by reference numeral 518, the network node may successfully receive the UAI after a delay.

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

[0080] In various aspects of the techniques and apparatuses described herein, the UE may send a CSR MAC-CE during a RACH procedure to request a conservative scheduling period. The conservative scheduling period may be associated with a certain duration. The conservative scheduling period may be associated with the UE's substantially uplink transmission capability as compared to a non-conservative scheduling period. The conservative scheduling period may be associated with fewer scheduling grants as compared to the scheduling grants associated with a non-conservative scheduling period. The network node may establish a conservative scheduling period for the duration at least partially based on the CSR MAC-CE. The UE may send an uplink transmission to the network node during the conservative scheduling period. The uplink transmission may be associated with a single carrier and a single layer (e.g., only a single carrier and only a single layer) according to the UE's substantially uplink transmission capability. The uplink transmission may be associated with a measurement report or a UAI message.

[0081] In some aspects, the uplink resynchronization mechanism may be at least partially based on the UE's substantially uplink transmission capabilities. When the UE has an inefficient Tx state to maintain the RRC connection, the uplink resynchronization mechanism may provide a robust and reliable uplink transmission. The uplink resynchronization mechanism may provide a basic transmission mode while requiring reduced UE capabilities, which may help protect critical signaling or data transmissions from the UE, such as mobility-related messages, UAI messages, buffer status report messages, and / or PHR MAC-CEs. When the uplink transmission quality is limited, the uplink resynchronization mechanism may be useful for MSIM UEs and single-SIM (SSIM) UEs and can enable reliable and robust uplink transmissions.

[0082] Figure 6 is a diagram illustrating example 600 associated with a request for a conservative scheduling period according to the present disclosure. As Figure 6 shown, example 600 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0083] In some aspects, the uplink resynchronization mechanism may be at least partially based on the four-step RACH procedure. The uplink resynchronization mechanism may be associated with the UE's substantially uplink transmission capabilities. The network node may receive a newly defined MAC-CE, such as a CSR MAC-CE, during the four-step RACH procedure. The network node may use minimum requirements scheduling for the UE for a certain duration, which may allow the UE to send critical uplink messages that are more likely to be successfully received by the network node. In other words, when the network node receives a CSR MAC-CE from the UE (which may notify the network node of the UE's conservative scheduling request), the network node may establish a conservative scheduling period for a certain duration. During the conservative scheduling period, reliable Tx / Rx communication may occur between the UE and the network node. For example, during the conservative scheduling period, the UE may send critical messages, such as measurement reports or UAI messages, in the uplink direction. The network node may perform conservative scheduling during the conservative scheduling period at least partially based on the minimum required Tx / Rx capabilities that allow the UE to send critical messages / data during that duration, which may allow the UE to become synchronized with the network node.

[0084] As shown by reference numeral 602, the UE may detect the need for conservative scheduling for Tx / Rx communication. The UE may detect the need for conservative scheduling at least in part based on the UE having an uplink transmission but having an inefficient uplink transmission. In other words, the triggering condition may be when the UE has an uplink transmission, but the UE detects an inefficient uplink transmission, which may be determined by the UE at least in part based on the UE implementation (e.g., a grant that exceeds the immediate Tx capability). When the uplink transmission quality of the UE is limited, the UE may detect the need for conservative scheduling for Tx / Rx communication, which may occur when the UE is in an uplink power limited region or when the Tx chain of the UE is associated with a poor quality, and this may cause the UE to be unable to perform a transmission for a 2L uplink grant or for a single-layer, relatively large RB size grant. In some aspects, the four-step RACH procedure may be at least in part based on the detection of a triggering condition, where the triggering condition may be at least in part based on an uplink scheduling grant that exceeds the UE transmission capability. For example, the uplink scheduling grant may schedule an uplink transmission associated with two layers, or an uplink transmission associated with a grant of a relatively large RB size, which uplink transmissions may not be achievable by the UE due to the limited uplink transmission quality of the UE.

[0085] In some aspects, at least in part based on a triggering condition (which may occur when the UE has an uplink transmission but detects an inefficient uplink transmission), the UE may follow a scheduling request (SR) failure procedure to trigger an uplink data arrival at the RACH (e.g., a four-step contention-based RACH procedure). In other words, the UE may initiate the four-step RACH procedure at least in part based on satisfying the triggering condition. The UE may notify the RRC layer to release the physical uplink control channel (PUCCH) for multiple serving cells (e.g., all serving cells). The UE may notify the RRC layer to release the sounding reference signal (SRS) for multiple serving cells. The UE may clear any configured downlink assignments and uplink grants. The UE may clear any PUSCH resources for semi-persistent channel state information (CSI) reporting. The UE may initiate a random access procedure on a special cell (SpCell) and cancel any pending SRs (e.g., all pending SRs).

[0086] As shown by reference numeral 604, the UE may send a random access message (RAM), which may include a preamble (sometimes referred to as a random access preamble, PRACH preamble, or RAM preamble). The RAM including the preamble may be referred to as message 1, Msg1, MSG1, the first message, or the initial message in the four-step RACH procedure. The RAM may include a random access preamble identifier.

[0087] As shown by reference numeral 606, a network node may send a random access response (RAR) to a UE. The RAR may be referred to as message 2, Msg2, MSG2, or the second message in a four-step RACH procedure. In some aspects, the RAR may indicate a detected random access preamble identifier (e.g., received from the UE in Msg1). Additionally or alternatively, the RAR may indicate a resource allocation to be used by the UE to send message 3 (Msg3).

[0088] In some aspects, the network node may send a physical downlink control channel (PDCCH) communication for the RAR. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. Additionally, as part of the second step of a four-step RACH procedure, the network node may send the PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in a MAC protocol data unit (PDU) of the PDSCH communication.

[0089] As shown by reference numeral 608, the UE may send a PUSCH transmission indicating an RRC connection request message. The RRC connection request message may be referred to as message 3, Msg3, MSG3, or the third message in a four-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier and / or uplink control information (UCI).

[0090] In some aspects, the UE may send a CSR MAC-CE, a buffer status report (BSR), and / or a PHR to the network node during a RACH procedure. The CSR MAC-CE, BSR, and / or PHR may be associated with the PUSCH transmission. In some aspects, the CSR MAC-CE may be used to notify the network node of a UE conservative scheduling request, where the UE conservative scheduling request may be at least partially based on the UE detecting a need for conservative scheduling for Tx / Rx communication. The UE may send the CSR MAC-CE, BSR, and / or PHR during a RACH procedure to request a conservative scheduling period from the network node. In some aspects, the UE may send the CSR MAC-CE in Msg3 of a four-step RACH procedure. Additionally, the UE may send the BSR and PHR in Msg3 to notify the network node of the required grant and the current power headroom level.

[0091] In some aspects, the CSR MAC-CE may be associated with a reserved logical channel identifier (LCID) (e.g., LCID 44). For example, the CSR MAC-CE may be identified by a MAC sub-header with LCID = "44", and the CSR MAC-CE may have a fixed size of zero bits. In other words, the LCID value associated with the UE's conservative scheduling request may be associated with the code point / index "44". The CSR MAC-CE may be defined as a sub-header-only MAC-CE, which may avoid the failure of constructing the conservative scheduling request MAC-CE packet due to the lack of sufficient Msg3 grants. Alternatively, the CSR MAC-CE may use one octet (e.g., 8 bits) to carry additional information. In some aspects, the BSR may indicate to the network node information about the amount of data available for transmission in the UE's uplink buffer. The BSR may indicate the need for conservative scheduling for Tx / Rx communication. In some aspects, the PHR may indicate to the network node information about the headroom between the current UE Tx power (e.g., estimated power) and the nominal power. The PHR may indicate the need for conservative scheduling for Tx / Rx communication.

[0092] As shown by reference numeral 610, the network node may send a PDSCH transmission to the UE, and the PDSCH transmission may indicate an RRC connection establishment message. The RRC connection establishment message may be referred to as Message 4, Msg4, MSG4, or the fourth message of the four-step RACH procedure. In some aspects, the RRC connection establishment message may include the detected UE identifier, the timing advance value, and / or the contention resolution information.

[0093] As shown by reference numeral 612, the network node may establish a conservative scheduling period for the duration, which may enable reliable Tx / Rx communication between the UE and the network node, even when the UE has detected an inefficient uplink transmission (e.g., due to limited uplink transmission quality). The conservative scheduling period may only require the UE to have the most basic uplink transmission capabilities. The network node may perform conservative scheduling during the conservative scheduling period at least partially based on the minimum required Tx / Rx capabilities that allow the UE to send critical messages / data during the duration, which may allow the UE to become synchronized with the network node. The network node may establish a conservative scheduling period for the duration at least partially based on the CSR MAC-CE, BSR, and / or PHR received from the UE via Msg3. During the conservative scheduling period, compared with the time before the conservative scheduling period, the network node may schedule fewer Tx and Rx communications for the UE, which may allow the UE to use the existing Tx capabilities for sending UE critical messages / data transmissions. After the duration, the network node may stop implementing the conservative scheduling period and may return to the normal scheduling period of the UE.

[0094] In some aspects, the UE may send an uplink transmission during a conservative scheduling period, where the conservative scheduling period may be established by the network node at least in part based on the CSR MAC-CE for the duration. The CSR MAC-CE may be identified by a MAC sub-header with an LCID set to a defined code point or index. The conservative scheduling period may be associated with the UE's substantially uplink transmission capabilities relative to a non-conservative scheduling period. The conservative scheduling period may be associated with fewer scheduling grants relative to the scheduling grants associated with the non-conservative scheduling period. The uplink transmission may be associated with a measurement report or a UAI message. The conservative scheduling period may transition to a non-conservative scheduling period at least in part based on the expiration of the duration. The duration may be a number of time slots, and the duration may be at least in part based on the maximum of the calculated grant size and the minimum scheduling time slot.

[0095] In some aspects, when the network node receives the CSR MAC-CE, the network node may implement a conservative scheduling period by scheduling Rx / Tx communication in a conservative manner for a specific duration of N time slots, which may increase the likelihood that the network node successfully receives critical uplink messages from the UE. When the BSR and / or PHR are received separately together with the CSR MAC-CE, the network node may follow the BSR and / or PHR received from the UE. Otherwise, the network node may follow the default BSR and the default PHR (e.g., default five-bit buffer size BSR_c = 15, and PHR_c = POWER_HEADROOM_15). During conservative scheduling, PUSCH transmission may be associated with a single carrier and a single layer (e.g., only a single carrier and only a single layer), where the transport block (TB) size is calculated at least in part based on the PHR MAC-CE in Msg3. During the conservative scheduling period, PDSCH transmission may be associated with a single-carrier and single-layer PDSCH scheduling (e.g., only a single carrier and only a single layer PDSCH scheduling) using a relatively low MCS such as 16 quadrature amplitude modulation (QAM) or quadrature phase shift keying (QPSK). The conservative scheduling period may be associated with a conservative scheduling duration of N time slots, which may be at least in part based on the maximum of the grant size calculated based on the Msg3 BSR or TB size per time slot and the minimum scheduling time slot.

[0096] In some aspects, the UE may use a two-step RACH procedure to send the CSR MAC-CE, BSR, and / or PHR to notify the network node of the UE's conservative scheduling request. For example, the UE may send the CSR MAC-CE, BSR, and / or PHR during MsgA of the two-step RACH procedure.

[0097] As indicated above, Figure 6Provided as an example. Other examples may be different from the example described with respect to Figure 6 the example described.

[0098] Figure 7 is a diagram illustrating example 700 associated with a request for a conservative scheduling period according to the present disclosure. As Figure 7 shown, example 700 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0099] As Figure 7 shown, the UE may send Msg3 to the network node. Msg3 may indicate an LCID sub-header that may be associated with a CSR MAC-CE. Msg3 may indicate a BSR payload and a corresponding LCID sub-header. Msg3 may indicate a PHR payload and a corresponding LCID sub-header. The network node may receive Msg3 from the UE. The network node may initiate a conservative scheduling period for a certain duration based at least in part on the CSR MAC-CE, BSR payload, and / or PHR payload associated with Msg3.

[0100] As indicated above, Figure 7 Provided as an example. Other examples may be different from the example described with respect to Figure 7 the example described.

[0101] Figure 8 is a diagram illustrating example 800 associated with a request for a conservative scheduling period according to the present disclosure.

[0102] As Figure 8 shown, the network node may initially schedule Tx / Rx communication using PDSCH grants and PUSCH grants, respectively. After a period of time, the network node may receive a CSR MAC-CE from the UE, after which the network node may implement a conservative scheduling period of N time slots. During this conservative scheduling period, the network node may use fewer PDSCH grants and PUSCH grants to schedule Tx / Rx communication compared to before receiving the CSR MAC-CE from the UE. When the N time slots end and the conservative scheduling period is no longer implemented, the network node may return to scheduling Tx / Rx communication using PDSCH grants and PUSCH grants, respectively.

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

[0104] Figure 9FIG. 0 is an illustration of an example process 900 that may be performed by a UE, for example, in accordance with the present disclosure. Example process 900 is an example of operations performed by a UE (e.g., UE 120) associated with a request for a conservative scheduling period.

[0105] As Figure 9 shown, in some aspects, process 900 may include sending a CSR MAC-CE during a RACH process to request a conservative scheduling period associated with a certain duration (block 910). For example, a UE (e.g., using the sending component 1104 and / or communication manager 1106 depicted in Figure 11 ) may send a CSR MAC-CE during a RACH process to request a conservative scheduling period associated with a certain duration, as described above.

[0106] As Figure 9 further shown, in some aspects, process 900 may include sending an uplink transmission during the conservative scheduling period established for the duration, at least in part, based on the CSR MAC-CE (block 920). For example, a UE (e.g., using the sending component 1104 and / or communication manager 1106 depicted in Figure 11 ) may send an uplink transmission during the conservative scheduling period established for the duration, at least in part, based on the CSR MAC-CE, as described above.

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

[0108] In a first aspect, the conservative scheduling period is associated with the UE's substantially uplink transmission capability relative to a non-conservative scheduling period.

[0109] In a second aspect, alone or in combination with the first aspect, the RACH process is a four-step RACH process, and the CSR MAC-CE is indicated in Msg3 of the four-step RACH process.

[0110] In a third aspect, alone or in combination with one or more of the first and second aspects, the uplink transmission is associated with a measurement report or a UAI message.

[0111] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the CSR MAC-CE is identified by a MAC subheader having an LCID set to a defined codepoint or index, and the CSR MAC-CE includes a one-octet payload for indicating additional information.

[0112] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the RACH procedure is at least partially based on the detection of a triggering condition, and the triggering condition is at least partially based on an uplink scheduling grant that exceeds the UE's transmission capabilities.

[0113] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, procedure 900 includes transmitting one or more of a BSR or a PHR together with a CSR MAC-CE, wherein the conservative scheduling period is established at least partially based on one or more of the BSR or the PHR.

[0114] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the conservative scheduling period transitions to a non-conservative scheduling period at least partially based on the expiration of the duration.

[0115] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the conservative scheduling period is associated with fewer scheduling grants as compared to the scheduling grants associated with the non-conservative scheduling period.

[0116] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the uplink transmission is associated with only a single carrier and only a single layer.

[0117] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the downlink transmission that occurs during the conservative scheduling period is associated with only a single carrier and only a single layer.

[0118] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the duration is a certain number of time slots, and the duration is at least partially based on the maximum of the calculated grant size and the minimum scheduling time slot.

[0119] Although Figure 9 illustrates example blocks of procedure 900, in some aspects, procedure 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner as compared to those depicted in Figure 9 . Additionally or alternatively, two or more of the blocks of procedure 900 may be executed in parallel.

[0120] Figure 10 is a diagram illustrating an example procedure 1000 performed, for example, by a network node in accordance with the present disclosure. Example procedure 1000 is an example where a network node (e.g., network node 110) performs operations associated with a request for a conservative scheduling period.

[0121] As Figure 10As shown, in some aspects, process 1000 may include receiving a CSR MAC-CE during a RACH process to request a conservative scheduling period associated with a certain duration (block 1010). For example, a network node (e.g., using Figure 12 the receiving component 1202 and / or the communication manager 1206 depicted in

[0122] As Figure 10 further shown, in some aspects, process 1000 may include receiving an uplink transmission during the conservative scheduling period established for the duration at least in part based on the CSR MAC-CE (block 1020). For example, a network node (e.g., using Figure 12 the receiving component 1202 and / or the communication manager 1206 depicted in

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

[0124] In a first aspect, relative to a non-conservative scheduling period, the conservative scheduling period is associated with the UE's substantially uplink transmission capability.

[0125] In a second aspect, either alone or in combination with the first aspect, the RACH process is a four-step RACH process, and the CSR MAC-CE is indicated in Msg3 of the four-step RACH process.

[0126] In a third aspect, either alone or in combination with one or more of the first and second aspects, the uplink transmission is associated with a measurement report or a UAI message.

[0127] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the CSR MAC-CE is identified by a MAC sub-header with an LCID set to a defined code point or index, and the CSR MAC-CE includes a one-octet payload for indicating additional information.

[0128] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the RACH process is at least partially based on the detection of a triggering condition, and the triggering condition is at least partially based on an uplink scheduling grant that exceeds the UE's transmission capability.

[0129] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1000 includes receiving one or more of a BSR or a PHR together with a CSR MAC-CE, wherein the conservative scheduling period is established at least in part based on one or more of the BSR or the PHR.

[0130] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the conservative scheduling period transitions to a non-conservative scheduling period at least in part based on the expiration of the duration.

[0131] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the conservative scheduling period is associated with fewer scheduling grants as compared to the scheduling grants associated with the non-conservative scheduling period.

[0132] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the uplink transmission is associated with only a single carrier and only a single layer.

[0133] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the downlink transmission that occurs during the conservative scheduling period is associated with only a single carrier and only a single layer.

[0134] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the duration is a certain number of time slots, and the duration is at least in part based on the maximum of the calculated grant size and the minimum scheduling time slot.

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

[0136] Figure 11 is a diagram of an example apparatus 1100 for wireless communication in accordance with the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1106 is combined with Figure 1The described communication manager 140. As shown, the apparatus 1100 may communicate with another apparatus 1108 (such as a UE or a network node (such as a CU, DU, RU, or base station)) using the receiving component 1102 and the transmitting component 1104.

[0137] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with Figures 6 to 8 the description. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 9 process 900. In some aspects, Figure 11 the apparatus 1100 and / or one or more components shown may include one or more components of the UE described in connection with Figure 2 the description. Additionally or alternatively, Figure 11 one or more components shown may be implemented within one or more components described in connection with Figure 2 the description. Additionally or alternatively, one or more components in a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a part of a component) may be implemented as instructions or code that is stored in a non-transitory computer-readable medium and is executable by a controller or a processor to perform the functions or operations of the component.

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

[0139] The transmitting component 1104 may transmit communications to the apparatus 1108, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the apparatus 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the apparatus 1108. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications, and may transmit the processed signals to the apparatus 1108. In some aspects, the transmitting component 1104 may include one or more components of the UE described in connection with Figure 2One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, transmit component 1104 may be co-located with receive component 1102 in a transceiver.

[0140] Communication manager 1106 may support the operation of receive component 1102 and / or transmit component 1104. For example, communication manager 1106 may receive information associated with configuring the reception of communications by receive component 1102 and / or the transmission of communications by transmit component 1104. Additionally or alternatively, communication manager 1106 may generate control information and / or provide control information to receive component 1102 and / or transmit component 1104 to control the reception and / or transmission of communications.

[0141] Transmit component 1104 may send a CSR MAC-CE during a RACH procedure to request a conservative scheduling period, which is associated with a certain duration. Transmit component 1104 may send an uplink transmission during the conservative scheduling period, which is established for the duration at least in part based on the CSR MAC-CE. Transmit component 1104 may send one or more of a BSR or a PHR together with the CSR MAC-CE, where the conservative scheduling period is established at least in part based on one or more of the BSR or the PHR.

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

[0143] Figure 12 is a diagram of an example apparatus 1200 for wireless communication in accordance with the present disclosure. Apparatus 1200 may be a network node, or a network node may include apparatus 1200. In some aspects, apparatus 1200 includes a receive component 1202, a transmit component 1204, and / or a communication manager 1206, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is combined with Figure 1The described communication manager 150. As shown, device 1200 may communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU, or base station)) using a receiving component 1202 and a transmitting component 1204.

[0144] In some aspects, device 1200 may be configured to perform one or more operations described herein in connection with Figures 6 to 8 Additional or alternatively, device 1200 may be configured to perform one or more processes described herein, such as Figure 10 process 1000. In some aspects, Figure 12 Device 1200 and / or one or more components shown may include one or more components of a network node described in connection with Figure 2 Additional or alternatively, Figure 12 One or more components shown may be implemented within one or more components described in connection with Figure 2 Additional or alternatively, one or more components in a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a part of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and are executable by a controller or a processor to perform the functions or operations of the component.

[0145] Receiving component 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiving component 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to one or more other components of device 1200. In some aspects, receiving component 1202 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of a network node described in connection with Figure 2 In some aspects, receiving component 1202 and / or transmitting component 1204 may include a network interface or may be included in a network interface. The network interface may be configured to obtain and / or output signals for device 1200 via one or more communication links (such as a backhaul link, a midhaul link, and / or a fronthaul link).

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

[0147] The communication manager 1206 may support the operations of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the reception of communications by the receiving component 1202 and / or the transmission of communications by the transmitting component 1204. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the reception and / or transmission of communications.

[0148] The receiving component 1202 may receive a CSR MAC-CE during a RACH procedure to request a conservative scheduling period, which is associated with a certain duration. The receiving component 1202 may receive an uplink transmission during the conservative scheduling period, which is established for the duration at least partially based on the CSR MAC-CE. The receiving component 1202 may receive one or more of a BSR or a PHR together with the CSR MAC-CE, where the conservative scheduling period is established at least partially based on one or more of the BSR or the PHR.

[0149] Figure 12 The number and arrangement of the illustrated components are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to those illustrated. Additionally, Figure 12 two or more of the illustrated components may be implemented within a single component, or Figure 12 a single illustrated component may be implemented as multiple distributed components. Additionally or alternatively, Figure 12 a set of the illustrated (one or more) components may perform one or more functions described as being performed by another set of components illustrated by Figure 12 In some aspects, the transmitting component 1204 may be co-located with the receiving component 1202 in a transceiver. Figure 12 another set of the illustrated components.

[0150] The following provides an overview of some aspects of the present disclosure:

[0151] Aspect 1: A wireless communication method performed by a user equipment (UE), the method comprising: sending a conservative scheduling request (CSR) medium access control control element (MAC-CE) during a random access channel (RACH) procedure to request a conservative scheduling period, the conservative scheduling period being associated with a certain duration; and sending an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

[0152] Aspect 2: The method according to aspect 1, wherein the conservative scheduling period is associated with the UE's substantially uplink transmission capability relative to a non-conservative scheduling period.

[0153] Aspect 3: The method according to any one of aspects 1 to 2, wherein the RACH procedure is a four-step RACH procedure, and wherein the CSR MAC-CE is indicated in message 3 (Msg3) of the four-step RACH procedure.

[0154] Aspect 4: The method according to any one of aspects 1 to 3, wherein the uplink transmission is associated with a measurement report or a UE assistance information (UAI) message.

[0155] Aspect 5: The method according to any one of aspects 1 to 4, wherein the CSR MAC-CE is identified by a medium access control (MAC) sub-header having a logical channel identifier (LCID) set to a defined code point or index, and wherein the CSR MAC-CE includes a payload of one octet for indicating additional information.

[0156] Aspect 6: The method according to any one of aspects 1 to 5, wherein the RACH procedure is at least in part based on the detection of a triggering condition, and wherein the triggering condition is at least in part based on an uplink scheduling grant that exceeds the UE's transmission capability.

[0157] Aspect 7: The method according to any one of aspects 1 to 6, the method further comprising: sending one or more of a buffer status report (BSR) or a power headroom report (PHR) together with the CSR MAC-CE, wherein the conservative scheduling period is established at least in part based on one or more of the BSR or the PHR.

[0158] Aspect 8: The method according to any one of aspects 1 to 7, wherein the conservative scheduling period transitions to a non-conservative scheduling period at least in part based on the expiration of the duration.

[0159] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the conservative scheduling period is associated with fewer scheduling grants as compared to the scheduling grants associated with the non-conservative scheduling period.

[0160] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the uplink transmission is associated with only a single carrier and only a single layer.

[0161] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the downlink transmission occurring during the conservative scheduling period is associated with only a single carrier and only a single layer.

[0162] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the duration is a certain number of time slots, and wherein the duration is at least partially based on the maximum of the calculated grant size and the minimum scheduling time slot.

[0163] Aspect 13: A wireless communication method performed by a network node, the method comprising: receiving a conservative scheduling request (CSR) media access control control element (MAC-CE) during a random access channel (RACH) procedure to request a conservative scheduling period, the conservative scheduling period being associated with a certain duration; and receiving an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least partially based on the CSR MAC-CE.

[0164] Aspect 14: The method according to Aspect 13, the method further comprising: receiving one or more of a buffer status report (BSR) or a power headroom report (PHR) together with the CSR MAC-CE, wherein the conservative scheduling period is established at least partially based on one or more of the BSR or the PHR.

[0165] Aspect 15: The method according to any one of Aspects 13 to 14, wherein: the conservative scheduling period is associated with substantially uplink transmission capabilities as compared to the non-conservative scheduling period; the conservative scheduling period transitions to the non-conservative scheduling period at least partially based on the expiration of the duration; and the conservative scheduling period is associated with fewer scheduling grants as compared to the scheduling grants associated with the non-conservative scheduling period.

[0166] Aspect 16: An apparatus for wireless communication at a device, the apparatus 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 the method according to one or more of Aspects 1 to 12.

[0167] Aspect 17: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of Aspects 1 to 12.

[0168] Aspect 18: A device for wireless communication, the device comprising at least one component for performing the method according to one or more of Aspects 1 to 12.

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

[0170] Aspect 20: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 1 to 12.

[0171] Aspect 21: A device for wireless communication at a device, the device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform the method according to one or more of Aspects 13 to 15.

[0172] Aspect 22: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of Aspects 13 to 15.

[0173] Aspect 23: A device for wireless communication, the device comprising at least one component for performing the method according to one or more of Aspects 13 to 15.

[0174] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of Aspects 13 to 15.

[0175] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 13 to 15.

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a memory; and one or more processors coupled to the memory and configured to: send a Conservative Scheduling Request (CSR) Medium Access Control Control Element (MAC-CE) during a Random Access Channel (RACH) procedure to request a conservative scheduling period associated with a certain duration; and send an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

2. The apparatus according to claim 1, wherein the conservative scheduling period is associated with the UE's substantially uplink transmission capability as compared to a non-conservative scheduling period.

3. The apparatus according to claim 1, wherein the RACH procedure is a four-step RACH procedure, and wherein the CSR MAC-CE is indicated in Message 3 (Msg3) of the four-step RACH procedure.

4. The apparatus according to claim 1, wherein the uplink transmission is associated with a measurement report or a UE Assistance Information (UAI) message.

5. The apparatus according to claim 1, wherein the CSR MAC-CE is identified by a Medium Access Control (MAC) sub-header having a logical channel identifier (LCID) set to a defined code point or index, and wherein the CSR MAC-CE includes a payload of one octet for indicating additional information.

6. The apparatus according to claim 1, wherein the RACH procedure is at least in part based on the detection of a trigger condition, and wherein the trigger condition is at least in part based on an uplink scheduling grant that exceeds the UE's transmission capability.

7. The apparatus according to claim 1, wherein the one or more processors are further configured to: send one or more of a Buffer Status Report (BSR) or a Power Headroom Report (PHR) together with the CSR MAC-CE, wherein the conservative scheduling period is established at least in part based on one or more of the BSR or the PHR.

8. The apparatus according to claim 1, wherein the conservative scheduling period transitions to a non-conservative scheduling period at least in part based on the expiration of the duration.

9. The apparatus according to claim 1, wherein the conservative scheduling period is associated with fewer scheduling grants as compared to a scheduling grant associated with a non-conservative scheduling period.

10. The apparatus according to claim 1, wherein the uplink transmission is associated with only a single carrier and only a single layer.

11. The apparatus according to claim 1, wherein a downlink transmission occurring during the conservative scheduling period is associated with only a single carrier and only a single layer.

12. The apparatus according to claim 1, wherein the duration is a certain number of time slots, and wherein the duration is at least in part based on the maximum of a calculated grant size and a minimum scheduling time slot.

13. An apparatus for wireless communication at a network node, the apparatus comprising: a memory; and one or more processors, the one or more processors coupled to the memory and configured to: receive a Conservative Scheduling Request (CSR) Medium Access Control Control Element (MAC-CE) during a Random Access Channel (RACH) procedure to request a conservative scheduling period, the conservative scheduling period being associated with a certain duration; and receive an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

14. The apparatus according to claim 13, wherein the one or more processors are further configured to: receive one or more of a Buffer Status Report (BSR) or a Power Headroom Report (PHR) together with the CSR MAC-CE, wherein the conservative scheduling period is established at least in part based on one or more of the BSR or the PHR.

15. The apparatus according to claim 13, wherein: the conservative scheduling period is associated with a substantially uplink transmission capability as compared to a non-conservative scheduling period; the conservative scheduling period transitions to a non-conservative scheduling period at least in part based on expiration of the duration; and the conservative scheduling period is associated with fewer scheduling grants as compared to scheduling grants associated with the non-conservative scheduling period.

16. A wireless communication method performed by a User Equipment (UE), the method comprising: transmit a Conservative Scheduling Request (CSR) Medium Access Control Control Element (MAC-CE) during a Random Access Channel (RACH) procedure to request a conservative scheduling period, the conservative scheduling period being associated with a certain duration; and transmit an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least in part based on the CSR MAC-CE.

17. The method according to claim 16, wherein the conservative scheduling period is associated with a substantially uplink transmission capability of the UE as compared to a non-conservative scheduling period.

18. The method according to claim 16, wherein the RACH procedure is a four-step RACH procedure, and wherein the CSR MAC-CE is indicated in Message 3 (Msg3) of the four-step RACH procedure.

19. The method according to claim 16, wherein the uplink transmission is associated with a measurement report or a UE Assistance Information (UAI) message.

20. The method according to claim 16, wherein the CSR MAC-CE is identified by a Medium Access Control (MAC) sub-header having a logical channel identifier (LCID) set to a defined code point or index, and wherein the CSR MAC-CE includes a payload of one octet for indicating additional information.

21. The method according to claim 16, wherein the RACH procedure is at least partially based on the detection of a triggering condition, and wherein the triggering condition is at least partially based on an uplink scheduling grant that exceeds the UE transmission capability.

22. The method according to claim 16, the method further comprising: Transmitting one or more of a buffer status report (BSR) or a power headroom report (PHR) together with the CSR MAC-CE, wherein the conservative scheduling period is at least partially established based on one or more of the BSR or the PHR.

23. The method according to claim 16, wherein the conservative scheduling period transitions to a non-conservative scheduling period at least partially based on the expiration of the duration.

24. The method according to claim 16, wherein the conservative scheduling period is associated with fewer scheduling grants as compared to the scheduling grants associated with a non-conservative scheduling period.

25. The method according to claim 16, wherein the uplink transmission is associated with only a single carrier and only a single layer.

26. The method according to claim 16, wherein the downlink transmission occurring during the conservative scheduling period is associated with only a single carrier and only a single layer.

27. The method according to claim 16, wherein the duration is a certain number of time slots, and wherein the duration is at least partially based on the maximum value of the calculated grant size and the minimum scheduling time slot.

28. A wireless communication method performed by a network node, the method comprising: Receiving a conservative scheduling request (CSR) medium access control control element (MAC-CE) during a random access channel (RACH) procedure to request a conservative scheduling period, the conservative scheduling period being associated with a certain duration; and Receiving an uplink transmission during the conservative scheduling period, the conservative scheduling period being established for the duration at least partially based on the CSR MAC-CE.

29. The method according to claim 28, the method further comprising: Receiving one or more of a buffer status report (BSR) or a power headroom report (PHR) together with the CSR MAC-CE, wherein the conservative scheduling period is at least partially established based on one or more of the BSR or the PHR.

30. The method according to claim 28, wherein: The conservative scheduling period is associated with a substantially uplink transmission capability as compared to a non-conservative scheduling period; The conservative scheduling period transitions to a non-conservative scheduling period at least partially based on the expiration of the duration; and The conservative scheduling period is associated with fewer scheduling grants as compared to the scheduling grants associated with the non-conservative scheduling period.

Images