Techniques for improving scheduling request transmission in wireless communications

Abstract

Aspects described herein relate to transmitting a scheduling request (SR) for an uplink grant based at least in part on the presence of data in a buffer, wherein the SR is scheduled for transmission according to SR periodicity; and aborting at least a next SR scheduled for transmission according to the SR periodicity based at least in part on a drop timer corresponding to the buffer overtime and / or the buffer being null.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 743,104, filed on May 12, 2022, entitled “TECHNIQUES FOR IMPROVING SCHEDULING REQUEST TRANSMISSION IN WIRELESS COMMUNICATIONS,” which is assigned to the assignee of the present invention and is incorporated herein by reference in its entirety. Background Art Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to sending scheduling requests (SRs).

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems 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, and single-carrier frequency division multiple access (SC-FDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. For example, the fifth generation (5G) wireless communication technology, which may be referred to as 5G New Radio (5G NR), is designed to expand and support diverse usage scenarios and applications for current mobile network generations. On the one hand, 5G communication technology may include: enhanced mobile broadband addressing people-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communications (URLLC) with certain specifications for latency and reliability; and massive machine-type communications that may allow very large numbers of connected devices and the transmission of relatively small amounts of non-delay-sensitive information.

[0006] In some wireless communication technologies, such as 5G NR, a device, including a user equipment (UE), may send an SR to a network node to request scheduling of resources for sending data to the network node. In the event that an initial SR transmission is not received or fails at the network node, the UE may initiate an SR procedure to send multiple SRs to the network node over a period of time. In 5G NR, the SR procedure may include parameters such as an SR periodicity defining the periodicity for sending the SR, an SR inhibit timer defining a time period after sending an SR during which another SR may not be sent, or a maximum send count defining the maximum number of SRs that may be sent as part of the SR procedure. Summary of the invention

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0008] According to one aspect, a wireless communication method is provided, the method comprising: sending a scheduling request (SR) for an uplink grant based at least in part on the presence of data in a buffer, wherein the SR is scheduled for transmission according to an SR periodicity; and aborting at least a next SR scheduled for transmission according to the SR periodicity based at least in part on the expiration of a discard timer corresponding to the buffer.

[0009] In another example, a device for wireless communication is provided, the device comprising a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of the methods described herein. On the other hand, a device for wireless communication is provided, the device comprising a component for performing the operations of the methods described herein. On the other hand, a computer-readable medium is provided, the computer-readable medium comprising code that can be executed by one or more processors to perform the operations of the methods described herein.

[0010] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate rather than limit the disclosed aspects, wherein like numerals represent like elements, and in which:

[0012] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is illustrated;

[0013] Figure 2 is a diagram illustrating an example of a decomposed base station architecture according to various aspects of the present disclosure;

[0014] Figure 3 is a block diagram illustrating an example of a user equipment (UE) according to various aspects of the present disclosure;

[0015] Figure 4 is a flow chart illustrating an example of a method for aborting one or more scheduling request (SR) transmissions according to various aspects described herein;

[0016] Figure 5 An example of a timeline for suspending SR transmission according to various aspects of the present disclosure is illustrated;

[0017] Figure 6 An example of a specific process for suspending SR transmission according to various aspects of the present disclosure is illustrated;

[0018] Figure 7 An example of a specific process for suspending SR transmission without releasing uplink resources according to various aspects of the present disclosure is illustrated; and

[0019] Figure 8 is a block diagram illustrating an example of a multiple-input multiple-output (MIMO) communication system including a base station and UEs according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0020] Various aspects are now described with reference to the accompanying drawings. In the following description, for the purpose of explanation, in order to provide a thorough understanding of one or more aspects, numerous specific details are described. However, it is apparent that such aspects can be practiced without these specific details.

[0021] The features described overall relate to improving the SR procedure to avoid sending an SR when the device has no data to send. For example, it may be the case that a device sending an SR in an SR procedure may time out data from a buffer before receiving an uplink (UL) grant, at which point the device may not use the UL grant if the UL grant is eventually received. For example, when a medium access control (MAC) buffer is empty, the device may obtain an uplink packet from an upper layer for sending to a network node. The device may start a discard timer (e.g., a DiscardTimer configured by the network) for the packet. In order to obtain an uplink (UL) grant, the device may send an SR. In some cases, such as a cell edge scenario or when the network provides an UL grant with a delay, the device may attempt to send multiple SRs in an SR procedure. The device may perform an SR procedure by sending multiple SR requests based on the SR periodicity, SR-ProhibitTimer, and / or dsr-TransMax count of the SR procedure. If the network has configured a lower DiscardTimer for the device to discard data from the buffer, then that Discard Timer may time out and the buffer become empty before an UL Grant is received from the network as it is the only pending data available in the buffer.

[0022] Typically, in 5G NR (e.g., according to the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.331), when a user equipment (UE) starts to send an SR, the SR can be canceled only after an UL grant is received or after the number of SR transmissions reaches a dsr-TransMax count without receiving an UL grant. In this regard, the UE may continue to send SRs even after the MAC buffer becomes empty until an UL grant is received or the dsr-TransMax count is reached. When the dsr-TransMax count is reached, the UE may release the physical uplink control channel (PUCCH) resources on which the SR was sent and trigger a random access channel (RACH) procedure to establish a connection with the network node or another network node. A specific example of such a configuration may include an SR configuration in which the SR periodicity is 80 milliseconds (ms), the sr-ProhibitTimer is 3, the sr-TransMax is 64, and the packet data convergence protocol (PDCP) discard timer is 300 ms. In this example, the total time to complete the maximum number of SR attempts may be 15.3 seconds, but the data for transmission may time out after 300 ms of not receiving a UL grant. In the examples described herein, the process or procedure for terminating SR transmission may be accelerated if the MAC buffer becomes empty to avoid wasting time or resources for additional SR transmissions when a UL grant is no longer needed.

[0023] This additional SR transmission may have some negative effects, which can be improved by the concepts described in this article. For example, for a multiple subscriber identity module (MSIM) device, if the problem is occurring on a non-default data subscription (nDDS), the nDDS may keep the transceiver resource manager (TRM) for a longer duration. Since the nDDS connected mode discontinuous reception (CDRX) sleep can help provide TRM for the default data subscription (DDS), this may affect user performance in DDS. In another example, for a device with high power consumption, continuing to send SR after the MAC buffer becomes empty may result in periodic SR transmission, which may affect CDRX sleep. Therefore, the device may not enter full CDRX sleep, and the SR transmission and / or RACH may consume a lot of power. In another example, for a device fill transmission, once the MAC buffer becomes empty, even if the device also receives some UL grants, the device may only transmit the MAC fill with buffer status report (BSR) as 0 to the network, and therefore the device may not correctly utilize the UL grant. As described herein, terminating SR transmission (or the entire SR procedure) when there is no data to send can prevent or otherwise mitigate the negative effects of such situations. This can also improve device efficiency, power consumption, etc., which can improve the user experience in wireless communications using such devices and / or networks.

[0024] The following will refer to Figures 1 to 8 The described features are presented in more detail.

[0025] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but not limited to: a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or a computer. By way of example, both an application running on a computing device and a computing device can be a component. One or more components may exist in a process and / or a thread of execution, and a component may be located in a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components may communicate by means of local and / or remote processes, such as according to signals having one or more data packets (such as data from a component as follows: the component interacts with another component in a local system, a distributed system, and / or interacts with other systems across a network such as the Internet).

[0026] The technology described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" can often be used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 version 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA20001xEV-DO, High Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM TM Etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents of an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents of an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio frequency spectrum bands. However, the following description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in most of the following descriptions, but these techniques can also be applied beyond LTE / LTE-A applications (e.g., to fifth generation (5G) new radio (NR) networks or other next generation communication systems).

[0027] The following description provides examples, but does not limit the scope, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of the present disclosure. Various procedures or components may be omitted, replaced or added to each example as appropriate. For example, the method described may be performed in a different order than described, and various steps may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in other examples.

[0028] Various aspects or features will be presented with respect to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these methods may also be used.

[0029] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). The macro cell may include a base station. The small cell may include a femto cell, a pico cell, and a micro cell. In an example, the base station 102 may also include a gNB 180, as further described herein. In one example, according to various aspects described herein, some nodes of the wireless communication system may have a modem 340 and a UE communication component 342, which is used to suspend SR transmission when the UE has no data to transmit. Although the UE 104 is shown as having a modem 340 and a UE communication component 342, this is an illustrative example, and substantially any node or any type of node may include a modem 340 and a UE communication component 342 for providing the corresponding functions described herein.

[0030] The base station 102 configured for 4G LTE (which may be collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a backhaul link 132 (e.g., using an S1 interface). The base station 102 configured for 5G NR (which may be collectively referred to as the Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a backhaul link 184. The base station 102 may perform one or more of the following functions, among other functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC 160 or 5GC 190) over backhaul link 134 (e.g., using an X2 interface). Backhaul link 134 may be wired or wireless.

[0031] Base station 102 can communicate wirelessly with one or more UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group (which may be referred to as a closed subscriber group (CSG)). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth per carrier allocated in carrier aggregation for up to Yx MHz (e.g., corresponding to x component carriers) in total for transmission in the DL and / or UL direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0032] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0033] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0034] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0035] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz with a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW can extend down to a frequency of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have extremely high path loss and short distances. The mmW base station 180 can use beamforming 182 with the UE 104 to compensate for the extremely high path loss and short distance. The base station 102 mentioned in this article can include gNB 180.

[0036] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0037] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196. AMF 192 may be a control node that handles signaling between UE 104 and 5GC 190. In general, AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be transmitted through UPF 195. UPF 195 may provide UE IP address allocation and other functions for one or more UEs. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0038] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or 5GC 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). IoT UEs may include machine type communication (MTC) / enhanced MTC (eMTC, also referred to as Category (CAT)-M or Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0039] In one example, in a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment (such as a base station (BS) or one or more units (or one or more components) that perform base station functionality) may be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP), or a cell, etc.), including the base station 102 described above and further herein, may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0040] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0041] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0042] In one example, UE 104 can communicate with base station 102 via a DRB and can receive resources (e.g., PUCCH resources) for sending an SR to base station 102. When UE 104 has data in a buffer for sending to base station 102, UE communication component 342 can send an SR to base station 102 to request uplink resources (e.g., a UL grant indicating uplink resources (such as physical uplink shared channel (PUSCH) resources)). When base station 102 correctly receives the SR, base station 102 can send the UL grant to UE 104. However, in some examples, base station 102 may not correctly receive the SR or may be unable to send the UL grant to UE 104. Therefore, UE communication component 342 can send the SR as part of an SR procedure that defines periodic transmission of SRs for a maximum number of attempts.

[0043] However, in some examples, the UE communication component 342 can time out the data to be sent before receiving the UL grant from the base station 102. In this example, the UE communication component 342 can terminate the SR transmission in the SR procedure based on detecting that there is no more data in the buffer to be sent to the base station 102. In another example, after multiple terminations or suspensions of SR transmissions, the UE communication component 342 can release the SR resources used to send the SR and / or can perform a RACH procedure to receive an UL grant from the base station 102 or another base station 102 (or more generally through the network) or synchronize uplink communications with the base station 102 or another base station 102 (e.g., in time), establish / reestablish a connection with the base station 102 or another base station 102, etc.

[0044] Figure 2 A diagram illustrating an example of a disaggregated base station 200 architecture is shown. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0045] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals or both to one or more of the other units via a wireless transmission medium.

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

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

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

[0049] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0050] The non-RT RIC 215 may be configured to include logic functions that 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 of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or communicate with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

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

[0052] Now turn to Figures 3 to 8 , various aspects are described with reference to one or more components and one or more methods that can perform the actions or operations described herein, where aspects in dashed lines may be optional. Figures 4 to 7 The operations described in the description are presented in a particular order and / or as being performed by example components, but it should be understood that the order of these actions and the components performing the actions may vary depending on the specific implementation. In addition, it should be understood that the following actions, functions, and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0053] refer to Figure 3 , an example of a specific implementation of the UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 312, memory 316, and transceiver 302 that communicate via one or more buses 344, which may operate in conjunction with the modem 340 and / or UE communication component 342 to abort SR transmission of an SR procedure (or abort the SR procedure) when the UE has no data to transmit, as described herein.

[0054] In one aspect, the one or more processors 312 may include the modem 340 and / or may be part of the modem 340 using one or more modem processors. Thus, various functions associated with the UE communication component 342 may be included in the modem 340 and / or the processor 312, and in one aspect, may be performed by a single processor, while in other aspects, different ones of these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 312 may include a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or any one or any combination of transceiver processors associated with the transceiver 302. In other aspects, some of the features of the one or more processors 312 and / or the modem 340 associated with the UE communication component 342 may be performed by the transceiver 302.

[0055] In addition, the memory 316 may be configured to store local versions of the data and / or applications 375 used herein, or one or more of the UE communication components 342 and / or its subcomponents executed by the at least one processor 312. The memory 316 may include any type of computer-readable medium that can be used by a computer or at least one processor 312, such as random access memory (RAM), read-only memory (ROM), tape, disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when the UE 104 is operating at least one processor 312 to execute one or more of the UE communication components 342 and / or its subcomponents, the memory 316 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes and / or data associated therewith that define the UE communication components 342 and / or its subcomponents.

[0056] The transceiver 302 may include at least one receiver 306 and at least one transmitter 308. The receiver 306 may include hardware and / or software executable by a processor for receiving data, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 306 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 306 may receive signals transmitted by at least one base station 102 or a SL transmitting UE. Additionally, the receiver 306 may process such received signals and may also obtain measurements of these signals, such as but not limited to Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 308 may include hardware and / or software executable by a processor for transmitting data, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 308 may include, but are not limited to, an RF transmitter.

[0057] In addition, in an aspect, the UE 104 may include an RF front end 388 that may operate in communication with one or more antennas 365 and the transceiver 302 for receiving and sending radio transmissions, such as receiving wireless communications sent by at least one base station 102 or SL-transmitting UE, sending wireless communications to at least one base station 102 or SL-receiving UE, etc. The RF front end 388 may be connected to the one or more antennas 365 and may include one or more low noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for sending and receiving RF signals.

[0058] In one aspect, the LNA 390 can amplify the received signal at a desired output level. In one aspect, each LNA 390 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 388 can use one or more switches 392 to select a particular LNA 390 and its specified gain value based on the desired gain value for a particular application.

[0059] In addition, for example, the RF front end 388 can use one or more PAs 398 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 398 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 388 can use one or more switches 392 to select a particular PA 398 and its specified gain value based on a desired gain value for a particular application.

[0060] In addition, for example, the RF front end 388 can use one or more filters 396 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, the output from the corresponding PA 398 can be filtered using a corresponding filter 396 to produce an output signal for transmission. In one aspect, each filter 396 can be connected to a specific LNA 390 and / or PA 398. In one aspect, the RF front end 388 can use one or more switches 392 to select a transmit path or a receive path using a specified filter 396, LNA 390, and / or PA 398 based on a configuration as specified by the transceiver 302 and / or the processor 312.

[0061] Thus, the transceiver 302 can be configured to transmit and receive wireless signals through one or more antennas 365 via the RF front end 388. In one aspect, the transceiver can be tuned to operate at a specified frequency so that the UE 104 can communicate with, for example, one or more base stations 102 or one or more cells associated with one or more base stations 102, one or more other UEs in SL communication, etc. In one aspect, for example, the modem 340 can configure the transceiver 302 to operate at a specified frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by the modem 340.

[0062] In one aspect, the modem 340 may be a multi-band multi-mode modem that processes digital data and communicates with the transceiver 302 so that the digital data is transmitted and received using the transceiver 302. In one aspect, the modem 340 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, the modem 340 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 340 may control one or more components (e.g., RF front end 388, transceiver 302) of the UE 104 to enable the sending and / or receiving of signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with the UE 104 as provided by the network during cell selection and / or cell reselection.

[0063] In one aspect, the memory 316 may include a buffer 385 that may store data for transmission to the base station. For example, the buffer 385 may be a buffer at the PDCP layer that stores data for providing to a lower layer (e.g., a MAC layer or a physical layer) for data unit generation and transmission to the base station. In one aspect, the UE communication component 342 may optionally include an SR component 352 for performing an SR procedure to send one or more SRs to the base station to request an UL grant, and / or a buffer management component 354 for managing a buffer of the UE 104 (e.g., the buffer 385) that may store data for transmission to the base station, as further described herein.

[0064] In one aspect, processor 312 may correspond to combining Figure 8 Similarly, the memory 316 may correspond to one or more processors in conjunction with the UE described in the embodiment of the present invention. Figure 8 The memory described by the UE in.

[0065] Figure 4 A flowchart illustrating an example of a method 400 for suspending SR transmission or procedure according to various aspects described herein. In one example, UE 104 may use Figure 1 and Figure 3 One or more of the components described in the method 400 may be used to perform the functions described in the method 400.

[0066] In the method 400, at block 402, an SR for an UL grant may be sent based at least in part on the presence of data in a buffer. In one aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may send an SR for an UL grant based at least in part on the presence of data in a buffer. For example, the SR component 352 may detect the presence of data in a buffer, such as the buffer 385. As described, for example, the buffer 385 may store data generated at the PDCP layer for transmission to a base station, although other buffers may also be used in conjunction with the various aspects described herein. The data stored in the buffer 385 may be generated by an application (e.g., the application 375) executing on the UE 104, and the data may include communications for transmission to the base station. The SR component 352 may detect or be notified of the presence of data, and the SR component 352 may accordingly send an SR to the base station to request an UL grant for UL resources on which the data from the buffer 385 is to be transmitted.

[0067] In one example, as part of initiating an SR procedure, the SR component 352 may send an SR based on the presence of data in the buffer. For example, the SR procedure may include multiple possible SR transmissions defined by one or more parameters of the SR procedure. The SR component 352 may send an initial SR and / or one or more additional SRs based on the SR procedure parameters until a UL grant is received from the base station. As described, for example, the SR parameters may include an SR periodicity for sending the SR, and in the event that the SR component 352 does not receive a UL grant, the SR component may continue to send the SR at a time based on the SR periodicity. In another example, the SR parameters may include a prohibition timer (defined as SR-ProhibitTimer in 5G NR), which may define a time from the last SR transmission before the UE 104 is allowed to send the next SR transmission, and if necessary, the SR component 352 may send multiple SRs based on compliance with the prohibition timer. In another example, the SR parameters may include a maximum SR transmission count for the SR procedure (defined as dsr-TransMax in 5G NR), and if necessary, the SR component 352 may send multiple SRs until the maximum SR transmission count is reached.

[0068] In the method 400, at block 404, at least the next SR scheduled for transmission according to the SR periodicity may be aborted based at least in part on the expiration of a discard timer corresponding to the buffer. In one aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may abort at least the next SR scheduled for transmission according to the SR periodicity based at least in part on the expiration of a discard timer corresponding to the buffer (and / or also based at least in part on the buffer being empty or becoming empty). For example, the buffer management component 354 may maintain a discard timer for the data in the buffer 385. In an example, the buffer management component 354 may start the discard timer based on data being stored in the buffer 385 (e.g., based on detecting an event that data is stored in the buffer 385). If the data is transmitted, the buffer management component 354 may release the data from the buffer 385 and terminate the discard timer. However, if the discard timer expires and the data is not transmitted, the buffer management component 354 may release the data from the buffer. At this point, if a UL grant has not been received and the SR procedure continues, any UL grant received from the base station as a result of the SR transmission may not be used by the UE 104 since there is no more data to send.

[0069] Thus, based on the discard timer expiring, the SR component 352 can abort at least the next SR transmission in the SR procedure. For example, the SR component 352 can refrain from transmitting at least the next SR to the base station 102. In another example, the SR component 352 can terminate the SR procedure entirely, which can be implemented by aborting each remaining SR transmission in the SR procedure (e.g., multiple remaining SR transmissions in the SR procedure) until a maximum transmission count is reached, canceling a process managing the SR procedure, releasing PUCCH resources used to transmit the SR, or otherwise performing a RACH procedure to reestablish a connection, etc. In an example, the SR component 352 can detect that the discard timer has expired based at least in part on receiving an indication of the discard timer expiration from the buffer management component 354 or other component or layer that manages the discard timer. In another example, the SR component 352 can detect an event in which data is released from the buffer 385.

[0070] In the method 400, optionally at block 406, an SR abort count may be incremented based at least in part on a discard timer expiration corresponding to the buffer. In an aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may increment at least the next SR scheduled for transmission according to the SR periodicity based at least in part on a discard timer expiration corresponding to the buffer. For example, the SR component 352 may manage the abort count in the memory 316 and may set the abort count to zero prior to the SR procedure. Each time the SR component 352 aborts an SR transmission in the SR procedure, the SR component 352 may increment the abort count.

[0071] In the method 400, optionally at block 408, it may be determined whether the SR abort count has reached a threshold and / or the buffer is empty. In one aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may determine whether the SR abort count has reached a threshold and / or the buffer is empty. If so, then optionally at block 410, the SR resources may be released. In one aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may release the SR resources if the SR abort count has reached a threshold and / or the buffer is empty. For example, the SR component 352 may release the PUCCH resources on which the SR is sent. In an example, the SR component 352 may release the PUCCH resources at the physical layer by no longer using the PUCCH resources.

[0072] At block 408, if the SR abort count does not reach a threshold and / or the buffer is not empty, then optionally at block 412, a RACH procedure may be triggered on the SR resources. In one aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may trigger a RACH procedure on the SR resources if the SR abort count does not reach a threshold and / or the buffer is not empty. For example, the SR component 352 may send a RACH preamble on the associated resources to request to reestablish a connection with the base station 102 or cell. In the event that the RACH procedure is successful, optionally at block 414, the SR abort count may be reset. In one aspect, the SR component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may reset the SR abort count (e.g., to zero) if the RACH procedure is successful. In this regard, for example, when data arrives at the buffer 385, the SR component 352 may restart the SR procedure.

[0073] Figure 5An example of a timeline 500 for suspending SR transmission according to various aspects described herein is illustrated. In the timeline 500, the UE 104 can communicate with the network 502. The UE 104 can include a PDCP / MAC layer 504 and a layer 1 (ML1) 506, which can be or include a physical layer. At 508, the network 502 can have pre-configured SR resources with the ML1 506, which can include a PUCCH on which the SR is transmitted. At 510, the network 502 can have pre-configured a DRB with a discard timer (with the PDCP 504), and the buffer can be currently empty. At 512, the PDCP / MAC 504 can receive an uplink packet from an upper layer (e.g., an application), and can start a PDCP discard timer. At 514, based on receiving the uplink packet, the PDCP / MAC 504 can transmit a data indication to the ML1 506, and the ML1 506 can start an SR procedure at 516 accordingly. As part of the SR procedure, ML1 506 may send a first SR transmission 518 to the network 502 to request an UL grant for sending the packet. At 520, ML1 506 may detect that an UL grant has not been received from the network 502 (e.g., within a threshold time period). Therefore, as part of the SR procedure, ML1 506 may send a second SR transmission 522 to the network 502 (e.g., based on the SR periodicity) to again request an UL grant for sending the packet. At 524, ML1 506 may detect that an UL grant has not been received from the network 502 (e.g., within a threshold time period). At 526, before the next SR is to be sent, the discard timer may time out at the PDCP / MAC 504 and the buffer may be flushed. At 528, the PDCP / MAC 504 may transmit an empty buffer indication to ML1 506. At 530 , based on receiving the empty buffer indication, ML1 506 may abort SR sending and / or set a SR counter (eg, SR abort count) to zero.

[0074] Figure 6A non-limiting example of a specific process 600 for aborting SR transmission according to various aspects described herein is illustrated. In an example, the process 600 may be performed by the UE 104 or one or more components thereof (such as the SR component 352, the buffer management component 354, etc.), as described above. At 602, a DRB with a PDCP discard timer may be established (e.g., using the base station 102), the lower layer buffer may be empty, and the SR_abort_count may be set to zero. At 604, the lower layer buffer may receive X bytes, where X may be a positive integer. As described, the X bytes may correspond to a packet to be sent to the base station. At 606, it may be determined whether valid SR resources are available. If not, a RACH may be triggered at 608. At 606, if there are valid SR resources available, at 610, an SR may be triggered. This may include triggering an SR procedure and / or SR transmission of an SR procedure. At 612, it may be determined whether an UL grant is received in response to the SR. If so, the SR sending (and / or SR procedure) may be aborted and SR_abort_count may be set to zero.

[0075] At 612, if the UL grant is not received, at 616, it may be determined whether the abort timer has expired and whether the lower layer buffer is equal to zero (e.g., empty). If so, the SR transmission (and / or SR procedure) may be aborted. Further, at 620, it may be determined whether the SR_abort_count is equal to a threshold. If so, at 622, PUCCH resources for SR may be released and SR_abort_count may be set to zero. At 616, if the abort timer has not expired or the lower layer buffer is not empty, at 624, it may be determined whether the SR transmission count is equal to a maximum SR transmission count (sr-TransMax) defined for the SR procedure. If so, at 626, the SR transmission may be aborted and the PUCCH resources may be released, and a RACH may be triggered at 608. At 626, if the SR transmission count is not equal to the maximum SR transmission count, at 628, the SR procedure may continue.

[0076] The following are used according to this article and Figure 6 An example of pseudo code that illustrates the various aspects of the process described in:

[0077] Step 1: SR_abort_count = 0. The threshold value may be a configurable value.

[0078] Step 2: After getting the data in the buffer,

[0079]

[0080] Step 3:

[0081]

[0082] Figure 7 A non-limiting example of a specific process 700 for aborting SR transmission without releasing PUCCH resources in accordance with various aspects described herein is illustrated. In an example, process 700 can be performed by UE 104 or one or more components thereof (such as SR component 352, buffer management component 354, etc.), as described above. In addition, process 700 can include actions of process 600, including 602, 604, 606, 608, 610, 612, 614, 616, 618, 620, 622, 624, and 626. At 626, if the SR transmission count is not equal to the maximum SR transmission count, then at 702, it can be determined whether the SR_abort_count is greater than zero and less than a threshold. If not, then at 704, the SR procedure can be continued. If the SR_abort_count is greater than zero and less than a threshold, then at 706, a RACH can be triggered but the PUCCH resources are not released. This may allow the UE to request a RACH on the resources at each scheduled SR transmission until the maximum number of SR transmissions is reached. At 708, it may be determined whether the RACH was successful, and if so, at 710, the SR_abort_count may be set to zero.

[0083] Since multiple SR transmission failures may be due to time misalignment, performing RACH can help synchronize uplink communications. The following is used according to this article and Figure 7 An example of pseudo code that illustrates the various aspects of the process described in:

[0084] Step 1: SR_abort_count = 0. The threshold value may be a configurable value.

[0085] Step 2: After getting the data in the buffer,

[0086]

[0087] Step 3:

[0088]

[0089]

[0090] Once a buffer (e.g., buffer 385, which may be a buffer at the MAC layer or PDCP layer) becomes empty, the aspects described herein may help gracefully handle SR transmissions. Since these aspects may help avoid unwanted SRs, they may help save more power by avoiding SR and RACH transmissions. Additionally, in some examples, these aspects may help the UE enter CDRX sleep, which may help DDS subscriptions obtain resources from nDDS subscriptions. As described, through the aspects described herein, both power and performance may be improved.

[0091] Figure 8 1 is a block diagram of a MIMO communication system 800 including a base station 102 and a UE 104. The MIMO communication system 800 may be exemplified with reference to Figure 1 The wireless communication access network 100 is described in detail. The base station 102 may be a reference Figure 1 Examples of various aspects of the base station 102 described. The base station 102 may be equipped with antenna 834 and antenna 835, and the UE 104 may be equipped with antenna 852 and antenna 853. In the MIMO communication system 800, the base station 102 may be able to transmit data over multiple communication links simultaneously. Each communication link may be referred to as a "layer", and the "rank" of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system in which the base station 102 sends two "layers", the rank of the communication link between the base station 102 and the UE 104 is two.

[0092] At the base station 102, a transmit (Tx) processor 820 may receive data from a data source. The transmit processor 820 may process the data. The transmit processor 820 may also generate a control symbol or a reference symbol. The transmit MIMO processor 830 may perform spatial processing (e.g., pre-coding) on ​​the data symbol, the control symbol, or the reference symbol (if applicable), and may provide an output symbol stream to the transmit modulator / demodulator 832 and 833. Each modulator / demodulator 832 to 833 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 832 to 833 may further process the output sample stream (e.g., convert the output sample stream to analog, amplify, filter, and up-convert) to obtain a DL signal. In one example, the DL signals from the modulator / demodulator 832 and 833 may be transmitted via antenna 834 and antenna 835, respectively.

[0093] UE 104 may be a reference Figure 1 to Figure 2Examples of various aspects of the UE 104 described. At the UE 104, the UE antenna 852 and the antenna 853 can receive the DL signal from the base station 102, and can provide the received signal to the modulator / demodulator 854 and 855, respectively. Each modulator / demodulator 854 to 855 can condition the corresponding received signal (e.g., filter, amplify, downconvert, and digitize the corresponding received signal) to obtain input samples. Each modulator / demodulator 854 to 855 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 856 can obtain the received symbols from the modulator / demodulator 854 and 855, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive (Rx) processor 858 may process (eg, demodulate, deinterleave, and decode) the detected symbols to provide decoded data for the UE 104 to a data output and to provide decoded control information to a processor 880 or memory 882 .

[0094] In some cases, processor 880 may execute stored instructions to instantiate UE communication component 342 (see, e.g., Figure 1 and Figure 2 ).

[0095] On the uplink (UL), at the UE 104, a transmit processor 864 may receive and process data from a data source. The transmit processor 864 may also generate reference symbols for reference signals. The symbols from the transmit processor 864 may be pre-decoded by a transmit MIMO processor 866 (if applicable), further processed by modulators / demodulators 854 and 855 (e.g., for SC-FDMA, etc.), and transmitted to the base station 102 according to the communication parameters received from the base station 102. At the base station 102, the UL signal from the UE 104 may be received by antennas 834 and 835, processed by modulators / demodulators 832 and 833, detected by a MIMO detector 836 (if applicable), and further processed by a receive processor 838. The receive processor 838 may provide decoded data to a data output and to the processor 840 or memory 842.

[0096] The components of the UE 104 may be implemented individually or collectively using one or more ASICs, wherein the one or more ASICs are adapted to perform some or all of the applicable functions in hardware. Each of the modules indicated may be a means for performing one or more functions related to the operation of the MIMO communication system 800. Similarly, the components of the base station 102 may be implemented individually or collectively using one or more application specific integrated circuits (ASICs), which are adapted to perform some or all of the applicable functions in hardware. Each of the components indicated may be a means for performing one or more functions related to the operation of the MIMO communication system 800.

[0097] The following aspects are merely illustrative, and aspects thereof may be combined with aspects of other embodiments or teachings described herein without limitation.

[0098] Aspect 1 is a method for wireless communication, the method comprising: sending an SR for an uplink grant based at least in part on the presence of data in a buffer, wherein the SR is scheduled for transmission according to an SR periodicity; and aborting at least the next SR scheduled for transmission according to the SR periodicity based at least in part on the expiration of a discard timer corresponding to the buffer.

[0099] In aspect 2, the method of aspect 1 includes wherein aborting at least the next SR is further based at least in part on detecting that the buffer is empty after expiration of the discard timer.

[0100] In aspect 3, the method according to any one of aspects 1 or 2 includes wherein at least the next SR is included in an SR procedure of multiple SRs scheduled according to the SR periodicity, and the remaining SRs in the multiple SRs are aborted at least in part based on detecting that the buffer is empty after the discard timer expires.

[0101] In aspect 4, the method according to any one of aspects 1 to 3 includes incrementing a SR abort count based at least in part on the discard timer expiring, and releasing SR resources if the SR abort count reaches a threshold.

[0102] In aspect 5, the method according to aspect 4 includes resetting the SR abort count based on releasing the SR resources.

[0103] In aspect 6, the method according to any one of aspects 1 to 5 includes wherein the next SR is within the maximum SR send count.

[0104] In aspect 7, the method according to any one of aspects 1 to 6 includes incrementing an SR abort count based at least in part on the expiration of the discard timer, and triggering a random access channel (RACH) process without releasing SR resources when the SR abort count is greater than zero and does not reach a threshold.

[0105] In aspect 8, the method according to aspect 7 includes further triggering the RACH procedure without releasing the SR resources if the SR abort count has been incremented and the buffer is not empty.

[0106] In aspect 9, the method according to any one of aspects 7 or 8 includes resetting the SR abort count if the RACH procedure is successful.

[0107] Aspect 10 is a device for wireless communication, the device comprising: a transceiver; a memory configured to store instructions; and one or more processors, the one or more processors being communicatively coupled to the memory and the transceiver, wherein the one or more processors are configured to perform one or more of the methods described in any one of Aspects 1 to 9.

[0108] Aspect 11 is an apparatus for wireless communication, the apparatus comprising means for performing one or more of the methods according to any one of aspects 1 to 9.

[0109] Aspect 12 is a computer-readable medium comprising code executable by one or more processors for wireless communication, the code comprising code for performing one or more of the methods according to any one of aspects 1 to 9.

[0110] The above specific embodiments described above in conjunction with the accompanying drawings describe examples and do not represent the only examples that can be implemented or fall within the scope of the claims. The term "example" used in this specification means "used as an example, instance, or illustration", rather than "preferred" or "advantageous over other examples". The specific embodiments include specific details for providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0111] Information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer executable codes or instructions stored on a computer-readable medium, or any combination thereof.

[0112] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a specially programmed device, such as, but not limited to, a processor for performing the functions described herein, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. Although the specially programmed processor may be a microprocessor, in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0113] The functions described herein may be implemented in hardware, firmware, software executed by a processor, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable medium or sent through it. Other examples and specific implementations fall within the scope and essence of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using hardware, firmware, hard wiring, software executed by a specially programmed processor, or a combination of any of these items. The features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, as used herein, including in the claims, the "or" used in the list of items starting with "at least one of" indicates a dispersed list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0114] Computer readable medium includes both computer storage medium and communication medium, and this communication medium includes any medium that promotes computer program to be transferred from one place to another place.Storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, computer readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, magnetic disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and any other medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connector is appropriately referred to as computer readable medium.For example, if software is to send from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer readable media.

[0115] The previous description of the present disclosure is provided to enable those skilled in the art to implement or use the present disclosure. It will be apparent to those of ordinary skill in the art that various modifications to the present disclosure will be apparent, and the general principles defined herein may be applied to other variations without departing from the essence or scope of the present disclosure. In addition, although the elements of the described aspects and / or embodiments are described or claimed in the singular, the plural form is contemplated unless explicitly stated to be limited to the singular. Additionally, unless otherwise stated, all or part of any aspect and / or embodiment may be used together with all or part of any other aspect and / or embodiment. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication, the device comprising: Transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: transmitting a scheduling request (SR) for an uplink grant based at least in part on the presence of data in the buffer, wherein the SR is scheduled for transmission according to a SR periodicity; and At least a next SR scheduled for transmission according to the SR periodicity is aborted based at least in part on expiration of a discard timer corresponding to the buffer.

2. The apparatus of claim 1, wherein the one or more processors are configured to abort at least the next SR based further at least in part on detecting that the buffer is empty after the discard timer expires.

3. The apparatus of claim 1 , wherein at least the next SR is included in an SR procedure of a plurality of SRs scheduled according to the SR periodicity, and wherein the one or more processors are further configured to abort remaining SRs of the plurality of SRs based at least in part on detecting that the buffer is empty after the discard timer expires.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to: incrementing a SR abort count based at least in part on the discard timer expiring; and When the SR suspension count reaches a threshold, the SR resource is released. 5 . The apparatus of claim 4 , wherein the one or more processors are further configured to reset the SR abort count based on releasing the SR resources. The apparatus of claim 1 , wherein the next SR is within a maximum SR send count.

7. The apparatus of claim 1, wherein the one or more processors are further configured to: incrementing a SR abort count based at least in part on the discard timer expiring; and In case the SR abort count is greater than zero and does not reach a threshold, a random access channel (RACH) procedure is triggered without releasing SR resources.

8. The apparatus of claim 7, wherein the one or more processors are configured to further trigger the RACH procedure without releasing the SR resources if the SR abort count has been incremented and the buffer is not empty.

9. The apparatus of claim 7, wherein the one or more processors are further configured to reset the SR abort count if the RACH procedure is successful.

10. A method for wireless communication, the method comprising: transmitting a scheduling request (SR) for an uplink grant based at least in part on the presence of data in the buffer, wherein the SR is scheduled for transmission according to a SR periodicity; as well as At least a next SR scheduled for transmission according to the SR periodicity is aborted based at least in part on expiration of a discard timer corresponding to the buffer.

11. The method of claim 10, wherein aborting at least the next SR is further based at least in part on detecting that the buffer is empty after the discard timer expires.

12. The method of claim 10, wherein at least the next SR is included in an SR procedure of a plurality of SRs scheduled according to the SR periodicity, and the method further comprises aborting remaining SRs of the plurality of SRs based at least in part on detecting that the buffer is empty after the discard timer expires.

13. The method according to claim 10, further comprising: incrementing a SR abort count based at least in part on expiration of the discard timer; as well as When the SR suspension count reaches a threshold, the SR resource is released.

14. The method of claim 13, further comprising resetting the SR abort count based on releasing the SR resources.

15. The method of claim 10, wherein the next SR is within a maximum SR send count.

16. The method according to claim 10, further comprising: incrementing a SR abort count based at least in part on expiration of the discard timer; as well as In case the SR abort count is greater than zero and does not reach a threshold, a random access channel (RACH) procedure is triggered without releasing SR resources.

17. The method of claim 16, wherein in a case where the SR abort count has been incremented and the buffer is not empty, further triggering the RACH procedure without releasing the SR resources.

18. The method of claim 16, further comprising resetting the SR abort count if the RACH procedure is successful.

19. An apparatus for wireless communication, the apparatus comprising: means for transmitting a scheduling request (SR) for an uplink grant based at least in part on the presence of data in the buffer, wherein the SR is scheduled for transmission according to a SR periodicity; and Means for aborting at least a next SR scheduled for transmission according to the SR periodicity based at least in part on expiration of a discard timer corresponding to the buffer.

20. The apparatus of claim 19, wherein the means for aborting at least the next SR is further based at least in part on detecting that the buffer is empty after the discard timer expires.

21. The apparatus of claim 19, wherein at least the next SR is included in an SR procedure of a plurality of SRs scheduled according to the SR periodicity, and the apparatus further comprises means for aborting remaining SRs of the plurality of SRs based at least in part on detecting that the buffer is empty after the discard timer expires.

22. The apparatus according to claim 19, further comprising: means for incrementing a SR abort count based at least in part on expiration of the discard timer; and means for releasing SR resources if the SR abort count reaches a threshold.

23. The apparatus of claim 22, further comprising means for resetting the SR abort count based on releasing the SR resources.

24. The apparatus of claim 19, wherein the next SR is within a maximum SR send count.

25. A computer-readable medium comprising code executable by one or more processors for wireless communication, the code comprising code for: transmitting a scheduling request (SR) for an uplink grant based at least in part on the presence of data in the buffer, wherein the SR is scheduled for transmission according to a SR periodicity; and At least a next SR scheduled for transmission according to the SR periodicity is aborted based at least in part on expiration of a discard timer corresponding to the buffer.

26. The computer-readable medium of claim 25, wherein the code for aborting at least the next SR is further based at least in part on detecting that the buffer is empty after the discard timer expires.

27. The computer-readable medium of claim 25, wherein at least the next SR is included in an SR procedure of a plurality of SRs scheduled according to the SR periodicity, and the computer-readable medium further comprises code for aborting remaining SRs of the plurality of SRs based at least in part on detecting that the buffer is empty after the discard timer expires.

28. The computer-readable medium of claim 25, further comprising: code for incrementing a SR abort count based at least in part on an expiration of the discard timer; and Code for releasing SR resources if the SR abort count reaches a threshold.

29. The computer-readable medium of claim 28, further comprising code for resetting the SR abort count based on releasing the SR resources.

30. The computer-readable medium of claim 25, wherein the next SR is within a maximum SR send count.

Images