METHODS AND APPARATUSES FOR A USER EQUIPMENT (UE) BASED CHANNEL STATE INFORMATION (CSI) REPORTING REQUEST

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Application No. 16/573,523, filed September 17, 2019, which claims priority to U.S. Provisional Patent Application No. 62/732,919 filed September 18, 2018 both assigned to the assignee hereof. The disclosures of the prior Applications are considered part of and are incorporated by reference in this Patent Application.

Field of the Disclosure

[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for user equipment (UE) based channel state information (CSI) reporting request.

Description of Related Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.

[0004] In some examples, a wireless multiple-access communication system may include a number of base stations (BSs), which are each capable of simultaneously supporting communication for multiple communication devices, otherwise known as user equipments (UEs). In an LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation, a new radio (NR), or 5G network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., which may be referred to as a base station, 5G NB, next generation NodeB (gNB or gNodeB), TRP, etc.). A base station or distributed unit may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a EGE to a base station or distributed unit).

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. New Radio (NR) (e.g., 5G) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP. It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL). To these ends, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0006] However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in NR and LTE technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

[0007] The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled“Detailed Description” one will understand how the features of this disclosure provide advantages that include improved communications between access points and stations in a wireless network. [0008] Certain aspects provide a method for wireless communications in a network by a user equipment (UE). The method generally includes detecting a condition indicative of a change in channel conditions, sending an indication to a network entity to initiate channel state information (CSI) reporting by the UE, based on the detection, monitoring for a downlink transmission from the network entity to trigger CSI reporting, monitoring for CSI reference signals (CSI-RS) from the network entity, and sending a CSI report based on the CSI-RS.

[0009] Certain aspects provide a method for wireless communications in a network by a user equipment (UE). The method generally includes receiving a request, from a user equipment (UE), to initiate channel state information (CSI) reporting by the UE, sending a downlink transmission, in response to the request, to trigger CSI reporting by the UE, transmitting CSI reference signals (CSI-RS), and receiving, from the UE, a CSI report based on the CSI-RS.

[0010] Aspects of the present disclosure also provide apparatus, methods, processing systems, and computer readable mediums for performing the operations described above.

[0011] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the appended drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.

[0013] FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in accordance with certain aspects of the present disclosure. [0014] FIG. 2 is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN), in accordance with certain aspects of the present disclosure.

[0015] FIG. 3 is a diagram illustrating an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.

[0016] FIG. 4 is a block diagram conceptually illustrating a design of an example base station (BS) and user equipment (UE), in accordance with certain aspects of the present disclosure.

[0017] FIG. 5 is a diagram showing examples for implementing a communication protocol stack, in accordance with certain aspects of the present disclosure.

[0018] FIG. 6 illustrates an example of a frame format for a new radio (NR) system, in accordance with certain aspects of the present disclosure.

[0019] FIG. 7 illustrates an example timeline for CSI reporting, in accordance with certain aspects of the present disclosure.

[0020] FIG. 8 illustrates example operations for wireless communications by a user equipment, in accordance with certain aspects of the present disclosure.

[0021] FIG. 9 illustrates example operations for wireless communications by a network entity, in accordance with certain aspects of the present disclosure.

[0022] FIG. 10 illustrates an example flow diagram for a UE based CSI reporting request, in accordance with aspects of the present disclosure.

[0023] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation.

DETAILED DESCRIPTION

[0024] Certain aspects of the present disclosure provide techniques for a UE-based CSI reporting request. In some cases, upon detecting a condition indicative of a change in channel conditions, a UE sends a request for CSI reporting. Such UE-based CSI reporting request may lead to more timely CSI reports which may help a base station (gNB) with scheduling, which may help increase throughout and spectral efficiency. [0025] The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the 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 a claim. The word“exemplary” is used herein to mean“serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0026] The techniques described herein may be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms“network” and“system” are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as NR (e.g. 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash- OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).

[0027] New Radio (NR) is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE- Advanced (LTE- A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named“3rd Generation Partnership Project” (3GPP). cdma2000 and UMB are described in documents from an organization named“3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.

[0028] New radio (NR) access (e.g., 5G technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe.

Example Wireless Communications System

[0029] FIG. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be performed. For example, the network 100 may include a UE 120 and BS 110 configured to perform operations shown in FIGs. 8 and 9, respectively, for supporting UE-based CSI reporting requests.

[0030] As illustrated in FIG. 1, the wireless network 100 may include a number of base stations (BSs) 110 and other network entities. A BS may be a station that communicates with user equipments (EEs). Each BS 110 may provide communication coverage for a particular geographic area. In 3 GPP, the term“cell” can refer to a coverage area of a Node B (NB) and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term“cell” and next generation NodeB (gNB), new radio base station (NR BS), 5G NB, access point (AP), or transmission reception point (TRP) may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in wireless communication network 100 through various types of backhaul interfaces, such as a direct physical connection, a wireless connection, a virtual network, or the like using any suitable transport network.

[0031] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0032] A base station (BS) may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by ETEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, the BSs l lOa, l lOb and l lOc may be macro BSs for the macro cells l02a, l02b and l02c, respectively. The BS l lOx may be a pico BS for a pico cell l02x. The BSs 1 lOy and 1 lOz may be femto BSs for the femto cells l02y and l02z, respectively. A BS may support one or multiple (e.g., three) cells.

[0033] Wireless communication network 100 may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. In the example shown in FIG. 1, a relay station l lOr may communicate with the BS l lOa and a UE l20r in order to facilitate communication between the BS l lOa and the UE l20r. A relay station may also be referred to as a relay BS, a relay, etc. [0034] Wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100. For example, macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt).

[0035] Wireless communication network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0036] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with one another (e.g., directly or indirectly) via wireless or wireline backhaul.

[0037] The UEs 120 (e.g., l20x, l20y, etc.) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, 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, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some EEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC EEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a BS, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0038] Certain wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a“resource block” (RB)) may be 12 subcarriers (or 180 kHz). Consequently, the nominal Fast Fourier Transfer (FFT) size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.

[0039] While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR. NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per LIE. Multi-layer transmissions with up to 2 streams per LIE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells.

[0040] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that may function as a scheduling entity. In some examples, a UE may function as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may communicate directly with one another in addition to communicating with a scheduling entity.

[0041] In FIG. 1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. A finely dashed line with double arrows indicates interfering transmissions between a UE and a BS.

[0042] FIG. 2 illustrates an example logical architecture of a distributed Radio Access Network (RAN) 200, which may be implemented in the wireless communication network 100 illustrated in FIG. 1. A 5G access node 206 may include an access node controller (ANC) 202. ANC 202 may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the Next Generation Core Network (NG-CN) 204 may terminate at ANC 202. The backhaul interface to neighboring next generation access Nodes (NG-ANs) 210 may terminate at ANC 202. ANC 202 may include one or more transmission reception points (TRPs) 208 (e.g., cells, BSs, gNBs, etc.).

[0043] The TRPs 208 may be a distributed unit (DU). TRPs 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, TRPs 208 may be connected to more than one ANC. TRPs 208 may each include one or more antenna ports. TRPs 208 may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

[0044] The logical architecture of distributed RAN 200 may support fronthauling solutions across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). [0045] The logical architecture of distributed RAN 200 may share features and/or components with LTE. For example, next generation access node (NG-AN) 210 may support dual connectivity with NR and may share a common fronthaul for LTE and NR.

[0046] The logical architecture of distributed RAN 200 may enable cooperation between and among TRPs 208, for example, within a TRP and/or across TRPs via ANC 202. An inter- TRP interface may not be used.

[0047] Logical functions may be dynamically distributed in the logical architecture of distributed RAN 200. As will be described in more detail with reference to FIG. 5, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

[0048] FIG. 3 illustrates an example physical architecture of a distributed Radio Access Network (RAN) 300, according to aspects of the present disclosure. A centralized core network unit (C-CU) 302 may host core network functions. C-CU 302 may be centrally deployed. C-CU 302 functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity.

[0049] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU 304 may host core network functions locally. The C-RU 304 may have distributed deployment. The C-RU 304 may be close to the network edge.

[0050] A DU 306 may host one or more TRPs (Edge Node (EN), an Edge Unit (EU), a Radio Head (RH), a Smart Radio Head (SRH), or the like). The DU may be located at edges of the network with radio frequency (RF) functionality.

[0051] FIG. 4 illustrates example components of BS 110 and UE 120 (as depicted in FIG. 1), which may be used to implement aspects of the present disclosure. For example, antennas 452, processors 466, 458, 464, and/or controller/processor 480 of the UE 120 and/or antennas 434 may be configured to perform operations 800 of FIG. 8, while processors 420, 430, 438, and/or controller/processor 440 of the BS 110 may be used to perform operations 900 of FIG. 9.

[0052] At the BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, e.g., for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a through 432t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 432a through 432t may be transmitted via the antennas 434a through 434t, respectively.

[0053] At the TIE 120, the antennas 452a through 452r may receive the downlink signals from the base station 110 and may provide received signals to the demodulators (DEMODs) in transceivers 454a through 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480.

[0054] On the uplink, at UE 120, a transmit processor 464 may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source 462 and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor 480. The transmit processor 464 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators in transceivers 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signals from the UE 120 may be received by the antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120. The receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.

[0055] The controllers/processors 440 and 480 may direct the operation at the base station 110 and the UE 120, respectively. The processor 440 and/or other processors and modules at the BS 110 may perform or direct the execution of processes for the techniques described herein. The memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.

[0056] FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure. The illustrated communications protocol stacks may be implemented by devices operating in a wireless communication system, such as a 5G system (e.g., a system that supports uplink-based mobility). Diagram 500 illustrates a communications protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer 530. In various examples, the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.

[0057] A first option 505-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC 202 in FIG. 2) and distributed network access device (e.g., DU 208 in FIG. 2). In the first option 505-a, an RRC layer 510 and a PDCP layer 515 may be implemented by the central unit, and an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU. In various examples the CU and the DU may be collocated or non-collocated. The first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment.

[0058] A second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device. In the second option, RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530 may each be implemented by the AN. The second option 505-b may be useful in, for example, a femto cell deployment.

[0059] Regardless of whether a network access device implements part or all of a protocol stack, a UE may implement an entire protocol stack as shown in 505-c (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).

[0060] In LTE, the basic transmission time interval (TTI) or packet duration is the 1 ms subframe. In NR, a subframe is still 1 ms, but the basic TTI is referred to as a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16, ... slots) depending on the subcarrier spacing. The NR RB is 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15 KHz and other subcarrier spacing may be defined with respect to the base subcarrier spacing, for example, 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0061] FIG. 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. Each subframe may include a variable number of slots depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols) depending on the subcarrier spacing. The symbol periods in each slot may be assigned indices. A mini-slot, which may be referred to as a sub-slot structure, refers to a transmit time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols).

[0062] Each symbol in a slot may indicate a link direction (e.g., DL, EIL, or flexible) for data transmission and the link direction for each subframe may be dynamically switched. The link directions may be based on the slot format. Each slot may include DL/EIL data as well as DL/EIL control information. [0063] In NR, a synchronization signal (SS) block is transmitted. The SS block includes a PSS, a SSS, and a two symbol PBCH. The SS block can be transmitted in a fixed slot location, such as the symbols 0-3 as shown in FIG. 6. The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SS blocks may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes. The SS block may be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmW. The up to sixty-four transmissions of the SS block are referred to as the SS burst set.

[0064] In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

[0065] A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated set of resources for transmitting a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.

Example UE based CSI reporting request

[0066] Channel state information (CSI) reporting generally refers to a mechanism where a UE measures downlink reference signals (CSI-RS) transmitted by a base station and reports an indication of a status of the channel. At least one of the following components is typically measured and provided for each CSI report: CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), and RI (Rank Indicator). Exactly what combination of components is provided and when depends on the situation and network configuration.

[0067] There are three basic types of CSI reporting configurations: periodic, semi- persistent, and aperiodic. A gNB may configure a UE for periodic CSI reporting via RRC signaling (for example, to report CQI every 5ms). Periodic CSI reporting is typically carried on a Short PUCCH or long PUCCH. Semi-persistent CSI (SP-CSI) reporting may also be configured via RRC signaling and is typically carried on long PUCCH or PUSCH. Resources (and MCS) for SP-CSI on PUSCH are typically allocated semi -persistently using downlink control information (DCI) signaling. Periodic and semi-persistent CSI reporting typically supports the following periodicities (5, 10, 20, 40, 80, 160, 320} slots. Aperiodic CSI reporting is triggered by a gNB, for example, via a DL grant or UL grant with a bit to signal channel state reporting. Aperiodic CSI reporting is typically carried on PUSCH and may be multiplexed with uplink data.

[0068] One potential problem with periodic CSI reporting is that, for many periods, the reported information may not change (or may change insignificantly). For example, the channel between a gNB and a stationary UE may not change significantly and reporting the same value(s) repeatedly is an inefficient use of resources due to increased overhead for the reporting and periodic CSI-RS transmission.

[0069] In order to reduce this overhead for NR CSI-RS, a-periodical CSI-RS (and/or periodical CSI-RS with very long periodicity) is typically configured. Unfortunately, this may result in CSI-RS reporting that is not timely as the channel conditions may change significantly between CSI reports. This untimely reporting may impact the gNB’s ability to adapt scheduling to changing channel conditions, thus reducing NR throughput and spectrum efficiency.

[0070] FIG. 7 illustrates an example timeline for conventional (network based) aperiodic CSI (A-CSI) reporting. As illustrated, a gNB may trigger aperiodic CSI reporting via a PDCCH transmission (e.g., a DL or UL grant with DCI triggering the CSI reporting). In the figure, the parameter X generally refers to a time gap (in terms of X slots) between A-CSI-RS triggering via the PDCCH DCI and A-CSI-RS transmission. In other words, X slots after sending the trigger, the gNB may transmit CSI-RS.

[0071] In the figure, the parameter Y generally refers to a time gap (in terms of Y slots) between A-CSI-RS triggering via the PDCCH DCI and A-CSI reporting carried in uplink control information (UCI) from the UE. In other words, Y slots after sending the trigger, the UE may send the CSI report (as UCI). One or both of the set of values (X, Y) may be configured via RRC signaling from the network and/or may be indicated by DCI.

[0072] A gNB typically makes a CSI request in DCI based on the limited information available at the gNB. This limited information may include, for example, monitoring PDSCH NACKs in a given period of time, signal to interference plus noise (SINR) measurements for UL sounding reference signals (SRS), timing adjustments, and the like, depending on a particular implementation. Using this limited information, a gNB may send a CSI request even in cases where the reported values may not change for several reports.

[0073] As described above, while a shorter period would result in more current CSI reporting, it also results in more overhead. On the other hand, greater periods result in less overhead, but also less timely CSI reporting, which may affect gNB scheduling.

[0074] Aspects of the present disclosure, however, provide for a UE based CSI reporting request. As will be described below, such a request may take advantage of information available at the UE that may not be available at the gNB. [0075] FIG. 8 illustrates example operations 800 for wireless communications in a network by a user equipment, for example, to request CSI reporting in accordance with aspects of the present disclosure.

[0076] The UE may include one or more components as illustrated in FIG. 4 which may be configured to perform the operations described herein. For example, the antenna 452, demodulator/modulator 454, controller/processor 480, and/or memory 482 as illustrated in FIG. 4 may perform operations 800.

[0077] Operations 800 begin, at 802, by detecting a condition indicative of a change in channel conditions. At 804, the UE sends an indication (e.g., a request) to a network entity to initiate channel state information (CSI) reporting by the UE, based on the detection. At 806, the UE monitors (after sending the indication) for a downlink transmission from the network entity to trigger CSI reporting. At 808, the UE monitors for CSI reference signals (CSI-RS) from the network entity. At 810, the UE sends a CSI report based on the CSI-RS.

[0078] FIG. 9 illustrates example operations 900 for wireless communications in a network by a network entity, for example, a gNB to configure a UE performing operations 800 described above, for CSI reporting.

[0079] The network entity may include one or more components as illustrated in FIG. 4 which may be configured to perform the operations described herein. For example, the antenna 452, demodulator/modulator 454, controller/processor 480, and/or memory 482 as illustrated in FIG. 4 may perform operations 900.

[0080] Operations 900 begin, at 902, by receiving an indication (e.g., a request), from a UE, to initiate channel state information (CSI) reporting by the UE. At 904, the network entity sends a downlink transmission, after receiving the indication, to trigger CSI reporting by the UE. At 906, the network entity transmits CSI reference signals (CSI-RS). At 908, the network entity receives, from the UE, a CSI report based on the CSI-RS.

[0081] In this manner, a UE may send a request for CSI reporting when a condition indicating a change in channel conditions has occurred and a new CSI report may be beneficial (e.g., to aid in gNB scheduling).

[0082] One example of such a condition is the UE detecting a mismatch between the last spectrum efficiency (SE) reported by the UE and an SE indicated for a gNB scheduled transmission. In some cases, the UE may determine that a difference between an SE last reported by the EE and the SE for a gNB scheduled transmission is greater than a threshold value and indicate (e.g., via an actual request or some other type of indication) that the EE would like to trigger CSI reporting to report a more current SE value to the gNB. It should be noted that the EE may request CSI reporting regardless of whether the difference in SE is due to an increase or decrease in SE from the gNB scheduled transmission to the last reported SE value.

[0083] As another example, the EE may request CSI reporting when a measured downlink signal to interference plus noise (SINR) at a current time is different than that for a previous CSI reporting. For example, if the difference is above threshold value, the EE may send a CSI Reporting request. The indication/request may be sent, for example, in a new medium access control (MAC) control element CE or new scheduling request SR type (or via some other type of signaling mechanism).

[0084] After receiving an indication that the EE is requesting CSI reporting from the EE, the gNB may or may not trigger a CSI-RS reporting in a following DCI, with CSI-RS transmission. In other words, the gNB may not necessarily trigger CSI-RS reporting after receiving an indication. If the gNB does trigger a CSI reporting, the EE may measure CSI and send CSI report on a scheduled PEiSCH.

[0085] FIG. 10 illustrates a flow diagram that demonstrates operation of a EE based CSI reporting request, in accordance with aspects of the present disclosure. The example assumes the EE applies the condition described above, where the EE requests CSI reporting if a difference between an SE last reported by the EE and an SE indicated by the gNB for a scheduled transmission exceeds a threshold value.

[0086] As illustrated, the gNB sends (and EE receives) a DL grant, at 1002. At 1004, the EE determines if the difference between the gNB scheduled SE and the SE last measured/reported by the EE is greater than or equal to a threshold value. If the difference in SE is not greater than the threshold value, no CSI reporting is requested, as represented at 1006.

[0087] If the difference in SE is greater than or equal to the threshold value, the EE may send a request for CSI reporting, at 1008. The EE then monitors for a PDCCH (e.g., a grant with DCI) triggering the CSI reporting, at 1010. [0088] In some cases, DCI triggering the CSI reporting may be conveyed via a PDCCH that does not schedule a PUSCH (e.g., a standalone PDCCH for the purpose of triggering CSI reporting). In other cases, DCI triggering the CSI reporting may be conveyed in a PDCCH scheduling a PUSCH (e.g., depending of if the UE has indicated it has data to send).

[0089] As noted above, a difference in SE above a threshold is just one example of a condition that may indicate a change in channel condition. Another example condition is a DL SINR measured at the UE. If the DL SINR is sufficiently different than a DL SINR for a previous (e.g., most recent) CSI reporting (e.g., if the difference is above a threshold), the UE may send a request for CSI reporting.

[0090] Another example condition that may trigger the UE to send a request for CSI reporting involves DL path loss changes compared with previous (e.g., recent) CSI reporting. As another example condition involves a change in UL SRS TX power (e.g., at above the threshold) based on a comparison with recently CSI reporting. Other examples include conditions involving a change in a number of layers or a change in rank.

Example Embodiments

[0091] Embodiment 1 : A method for wireless communications by a user equipment (UE), comprising detecting a condition indicative of a change in channel conditions, sending an indication to a network entity to initiate channel state information (CSI) reporting by the UE, based on the detection, monitoring for a downlink transmission from the network entity to trigger CSI reporting, monitoring for CSI reference signals (CSI-RS) from the network entity, and sending a CSI report based on the CSI-RS.

[0092] Embodiment 2: The method of Embodiment 1, wherein the condition relates to at least one of spectrum efficiency (SE), a change in downlink signal to interference plus noise ratio (SINR) relative to a previous CSI reporting, a change in downlink path loss (DL) since a relative CSI reporting, or a change in uplink transmission power for a sounding reference signal (SRS).

[0093] Embodiment 3 : The method of any of Embodiments 1-2, wherein the condition relates to a difference between a spectrum efficiency (SE) scheduled by the network entity and an SE last reported by the UE. [0094] Embodiment 4: The method of Embodiment 3, wherein the UE sends the indication if the difference is greater than or below a threshold value.

[0095] Embodiment 5: The method of Embodiment 4, wherein the threshold value is determined by the TIE, EIE-specific and signaled by the network, or cell-specific.

[0096] Embodiment 6: The method of any of Embodiments 4-5, further comprising receiving a downlink grant and measuring the SE difference based on the downlink grant.

[0097] Embodiment 7: The method of any of Embodiments 1-6, wherein the indication is sent via a medium access control (MAC) control element (CE).

[0098] Embodiment 8: The method of any of Embodiments 1-7, wherein the indication is sent via a scheduling request (SR) for CSI reporting.

[0099] Embodiment 9: The method of any of Embodiments 1-8, wherein the downlink transmission to trigger the CSI reporting comprises a downlink control information (DCI).

[0100] Embodiment 10: The method of Embodiment 9, wherein the DCI is conveyed via: a physical downlink control channel (PDCCH) that does not schedule a physical uplink shared channel (PETSCE1) or a PDCCH scheduling a PETSCH.

[0101] Embodiment 11 : The method of Embodiment 10, wherein the CSI report is sent via the PETCCH or the scheduled PUSCH.

[0102] Embodiment 12: A method for wireless communications by a network entity, comprising receiving an indication, from a user equipment (UE), to initiate channel state information (CSI) reporting by the EE, sending a downlink transmission, after receiving the indication, to trigger CSI reporting by the UE, transmitting CSI reference signals (CSI-RS), and receiving, from the UE, a CSI report based on the CSI-RS.

[0103] Embodiment 13 : The method of Embodiment 12, wherein the indication is received via a medium access control (MAC) control element (CE).

[0104] Embodiment 14: The method of any of Embodiments 12-13, wherein the indication is received via a scheduling request (SR) for CSI Reporting.

[0105] Embodiment 15: The method of any of Embodiments 12-14, wherein the downlink transmission to trigger the CSI reporting comprises a downlink control information (DCI). [0106] Embodiment 16: The method of Embodiment 15, wherein the DCI is conveyed via a physical downlink control channel (PDCCH) that does not schedule a physical uplink shared channel (PETSCE1) or a PDCCH scheduling a PETSCH.

[0107] Embodiment 17: The method of Embodiment 16, wherein the CSI report is sent via the scheduled PUSCH.

[0108] Embodiment 18: An apparatus for wireless communications by a user equipment (UE), comprising means for detecting a condition indicative of a change in channel conditions, means for sending an indication to a network entity to initiate channel state information (CSI) reporting by the UE, based on the detection, monitoring for a downlink transmission from the network entity to trigger CSI reporting, means for monitoring for CSI reference signals (CSI-RS) from the network entity, and means for sending a CSI report based on the CSI-RS.

[0109] Embodiment 19: The apparatus of Embodiment 18, wherein the condition relates to at least one of spectrum efficiency (SE), a change in downlink signal to interference plus noise ratio (SINR) relative to a previous CSI reporting, a change in downlink path loss (DL) since a relative CSI reporting, or a change in uplink transmission power for a sounding reference signal (SRS).

[0110] Embodiment 20: The apparatus of any of Embodiments 18-19, wherein the condition relates to a difference between a spectrum efficiency (SE) scheduled by the network entity and an SE last reported by the UE.

[0111] Embodiment 21 : The apparatus of Embodiment 20, wherein the UE sends the indication if the difference is greater than or below a threshold value.

[0112] Embodiment 22: The apparatus of Embodiment 21, wherein the threshold value is: determined by the UE, UE-specific and signaled by the network, or cell-specific.

[0113] Embodiment 23 : The apparatus of any of Embodiments 21-22, further comprising means for receiving a downlink grant and means for measuring the SE difference based on the downlink grant.

[0114] Embodiment 24: The apparatus of any of Embodiments 18-23, wherein the indication is sent via a medium access control (MAC) control element (CE).

[0115] Embodiment 25: The apparatus of any of Embodiments 18-24, wherein the indication is sent via a scheduling request (SR) for CSI reporting. [0116] Embodiment 26: The apparatus of any of Embodiments 18-25, wherein the downlink transmission to trigger the CSI reporting comprises a downlink control information (DCI).

[0117] Embodiment 27: The apparatus of Embodiment 26, wherein the DCI is conveyed via a physical downlink control channel (PDCCH) that does not schedule a physical uplink shared channel (PETSCE1) or a PDCCH scheduling a PETSCH.

[0118] Embodiment 28: The apparatus of Embodiment 27, wherein the CSI report is sent via the PETCCH or the scheduled PUSCH.

[0119] Embodiment 29: An apparatus for wireless communications by a network entity, comprising means for receiving an indication, from a user equipment (UE), to initiate channel state information (CSI) reporting by the UE, means for sending a downlink transmission, after receiving the indication, to trigger CSI reporting by the UE, means for transmitting CSI reference signals (CSI-RS), and means for receiving, from the UE, a CSI report based on the CSI-RS.

[0120] Embodiment 30: The apparatus of Embodiment 29, wherein the downlink transmission to trigger the CSI reporting comprises a downlink control information (DCI).

[0121] The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

[0122] As used herein, a phrase referring to“at least one of’ a list of items refers to any combination of those items, including single members. As an 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 multiples 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).

[0123] As used herein, the term“determining” encompasses a wide variety of actions. For example,“determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also,“determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

[0124] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean“one and only one” unless specifically so stated, but rather“one or more.” Unless specifically stated otherwise, the term“some” refers to one or more. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase“means for” or, in the case of a method claim, the element is recited using the phrase“step for.”

[0125] The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. For example, various operations shown in FIGs. 8, 9 and 10 may be performed by various processors shown in FIG. 4. More particularly, operations 800 of FIGs 8 may be performed by one or more of processors 466, 458, 464, and/or controller/processor 480 of the UE 120, while operations 900 of FIG. 9 may be performed by processors 420, 460, 438, and/or controller/processor 440 of the BS 110 shown in FIG. 4

[0126] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general- purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., 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.

[0127] If implemented in hardware, an example hardware configuration may comprise a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, among other things, to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal 120 (see FIG. 1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. The processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.

[0128] If implemented in software, the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the machine- readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable media may be embodied in a computer-program product.

[0129] A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that software module.

[0130] Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media may comprise transitory computer- readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.

[0131] Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.

[0132] Further, it should be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

[0133] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.