BR112017009562B1 - ALLOCATION OF UPLINK CONTROL RESOURCES FOR DYNAMIC TIME DIVISION DUPLEXING SYSTEMS - Google Patents

Abstract

ALLOCATION OF UPLINK CONTROL RESOURCES FOR DYNAMIC TIME DIVISION DUPLEXING SYSTEMS. Methods and apparatus for managing uplink scheduling for one or more user equipment served by a network entity in a wireless communications system are presented. In this case, an example method is presented that includes generating, by the network entity, an uplink bandwidth allocation map, uplink bandwidth allocation map defining an uplink bandwidth allocation to at least one of the or more user equipments for at least one of a plurality of uplink transmission window lengths. Furthermore, the exemplary method may include transmitting the uplink bandwidth allocation map to at least one of the one or more user equipments.

Description

CROSS REFERENCE TO RELATED ORDER

[0001] This Patent Application claims priority to Provisional Application No.62/077,112 entitled "ALLOCATION OF UPLINK CONTROL RESOURCES FOR DYNAMIC TIME DIVISION DUPLEXING SYSTEMS", filed on November 7, 2014 and Patent Application US No. 14/874,160, entitled "ALLOCATION OF UPLINK CONTROL RESOURCES FOR DYNAMIC TIME DIVISION DUPLEXING SYSTEMS" and filed on October 2, 2015, which are expressly incorporated herein by reference in their entirety.

FUNDAMENTALS

[0002] The present disclosure relates generally to communication systems and, more particularly, to methods and apparatus for allocating uplink control resources in a wireless communications system.

[0003] Wireless communications systems are widely developed to provide various telecommunications services such as telephony, video, data, messaging and broadcasting. Typical wireless communications systems may utilize multiple access technologies capable of supporting communication with multiple users sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access systems (OFDMA), single carrier frequency division multiple access systems (SC-FDMA) and time division synchronous code division multiple access systems (TD-SCDMA).

[0004] These multiple access technologies have been adopted into various telecommunications standards to provide a common protocol that allows different wireless devices to communicate at the city, national, regional, and even global level. An example of an emerging telecommunications standard is LTE (Long Term Evolution). LTE is a set of improvements to the UMTS (Universal Mobile Telecommunications System) mobile standard promulgated by 3GPP (Third Generation Partnership Project). It is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, using new spectrum and better integrating with other open standards using OFDMA on the downlink (DL downlink), SC-FDMA on the uplink (UL uplink), and multiple input and multiple output (MIMO) technology. However, as demand for mobile broadband access continues to increase, there is a need for further improvements in LTE technology. Preferably, these improvements should be applicable to other multi-access technologies and telecommunications standards that employ these technologies.

[0005] In wireless communications systems employing legacy LTE, a plurality of UEs served by a particular network entity (e.g., eNodeB) may receive control information from the eNodeB via a PDCCH (Physical Downlink Control Channel). ) shared. The control information included in the PDCCH may include one or more uplink resource grants for UE transmission of uplink data in a future LTE uplink transmission window. When control information must be transmitted by the UE on the uplink, however, it is often inefficient for the network entity to transmit dynamic grants for each uplink control information transmission. Furthermore, pre-allocation of fixed resources (in time and frequency) without knowing a dynamic uplink transmission window length also leads to system inefficiencies.

[0006] As such, improvements in uplink control resource allocation are needed to mitigate these current inefficiencies.

SUMMARY

[0007] The following is a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all aspects covered and is not intended to identify key or critical elements of all aspects nor to delineate 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 the more detailed description that is presented later.

[0008] In accordance with one or more aspects and their corresponding disclosure, various techniques are described in connection with exemplary methods and apparatus for managing user equipment communications in a wireless communications system.

[0009] For example, the present disclosure presents an exemplary method of managing uplink scheduling for one or more UEs served by a network entity in a wireless communications system. This example method may include generating, by the network entity, an uplink bandwidth allocation map, defining an uplink bandwidth allocation for at least one of the or more UEs for at least one of a plurality of uplink transmission window lengths. Furthermore, the exemplary method may include transmitting the uplink bandwidth allocation map to at least one of the one or more UEs.

[0010] In a further aspect, the disclosure presents an exemplary apparatus for managing uplink scheduling for one or more UEs served by a network entity in a wireless communications system. The example apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. In one aspect, instructions may be executable by the processor to generate, by the network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map defining an uplink bandwidth allocation. uplink to at least one or more UEs for at least one of a plurality of uplink transmission window lengths transmit the uplink bandwidth allocation map to at least one of the one or more UEs.

[0011] Additionally, the disclosure presents another example of apparatus for managing uplink scheduling for one or more UEs served by a network entity in a wireless communications system. In one aspect, the example apparatus may include means for generating, by the network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map defining an uplink bandwidth allocation. uplink to at least one of the or more UEs for at least one of a plurality of uplink transmission window lengths. Furthermore, the exemplary apparatus may include means for transmitting the uplink bandwidth allocation map to at least one of the one or more UEs.

[0012] In a further aspect, the disclosure features a non-transitory computer-readable medium that stores computer-executable code for managing uplink scheduling for one or more UEs served by a network entity in a wireless communication. The code may include executable instructions for generating, by the network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map defining an uplink bandwidth allocation for at least one of the one or more UEs for at least one of a plurality of uplink transmission window lengths and to transmit the uplink bandwidth allocation map to at least one of the one or more UEs.

[0013] Furthermore, the present description describes a method for wireless communication that can be carried out by a UE. The example method may include receiving, from a network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map defining an uplink bandwidth allocation. uplink to the UE for at least one of a plurality of uplink transmission window lengths. The method may further include storing the uplink bandwidth allocation map in a memory. Furthermore, the method may include receiving, from the network entity and after receiving the uplink bandwidth allocation map, an uplink transmission window length from an uplink transmission window. . Additionally, the method may include querying the uplink bandwidth allocation map in memory to determine the uplink bandwidth allocation corresponding to the received uplink transmission window length. The method may further include transmitting a control signal during the length of the window based on the uplink bandwidth allocation.

[0014] To achieve the aforementioned and related purposes, the one or more aspects are constituted by the characteristics described in detail here and described in particular in the claims. The following description and the accompanying drawings illustrate in detail certain illustrative features of the one or more aspects. These features are indicative, however, of only some of the various ways in which the principles of various aspects may be employed, and this description is intended to include all of these aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG. 1 illustrates a block diagram conceptually illustrating an example of a telecommunications system, in accordance with an aspect of the present disclosure.

[0016] FIG. 2 is a diagram illustrating an example of an access network.

[0017] FIG. 3 is a diagram illustrating an example of a DL framework structure in LTE.

[0018] FIG. 4 is a diagram illustrating an example of a UL fabric structure in LTE.

[0019] FIG. 5 is a diagram illustrating an example of a radio protocol architecture for user and control planes.

[0020] FIG. 6 is a diagram illustrating an example of an evolved Node B and user equipment in an access network.

[0021] FIG. 7A is a diagram illustrating an example uplink bandwidth allocation map for uplink bandwidth allocation in accordance with the present disclosure.

[0022] FIG. 7B is a diagram illustrating an example uplink bandwidth allocation map for uplink bandwidth allocation in accordance with the present disclosure.

[0023] FIG. 8 is a diagram illustrating an uplink programming component configured to implement aspects of the present disclosure.

[0024] FIG. 9 is a flowchart of an uplink bandwidth allocation method.

[0025] FIG. 10 is a conceptual data flow diagram illustrating the flow of data between different modules/media/components in an exemplary apparatus.

[0026] FIG. 11 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0027] FIG. 12 is a diagram illustrating an uplink management component configured to implement aspects of the present disclosure.

[0028] FIG. 13 is a flowchart of an uplink bandwidth management method.

[0029] FIG. 14 is a conceptual data flow diagram illustrating the flow of data between different modules/media/components in an exemplary apparatus.

[0030] FIG. 15 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

[0031] The detailed description presented below in connection with the accompanying drawings is intended to be a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a complete understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0032] Various aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0033] By way of example, an element, or any portion of an element, or any combination of elements can be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, closed logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system may execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether they are referred to as software, firmware, middleware, microcode, hardware description language or others.

[0034] Consequently, in one or more aspects, the described functions can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, functions may be stored or encoded as one or more instructions or code in a computer-readable medium. Computer readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to transport or store desired program code in the form of instructions or data structures and which can be accessed by a computer. Disc and floppy disk as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD) and floppy disk where discs reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above must also be included in the scope of computer-readable media.

[0035] The present disclosure presents examples of methods and apparatus for managing resource allocation for uplink control transmissions. For example, in one aspect of the present disclosure, the UEs may be assigned, via an uplink bandwidth allocation map (also referred to herein as a "map"), a variable bandwidth resource that is a function of an uplink transmission window length specified by a serving network entity. In other words, a specific uplink bandwidth allocation for a UE may vary for each uplink transmission window based on the specified window length. In one aspect, this window length may vary over time. In other words, the window length may include one or more symbols that may be aggregated to form variable-length transmission time slots (TTIs) over time.

[0036] Additionally, the network entity may generate and transmit the uplink bandwidth allocation map to each of its associated UEs, or to a subset of the UEs that may be scheduled with uplink transmissions, in a semi-static base. In other words, instead of transmitting the map for each uplink transmission window, the network entity can transmit the map on a periodic basis, where the periodicity of map transmission is less frequent than each window (e.g. once every 100 ms). Furthermore, a more recently received map may be stored in a UE memory.

[0037] Furthermore, before each transmission window, the UE may receive, from the network entity, a transmission window length corresponding to each transmission window. The UE may then query the map stored in the UE's memory to match the length of the received transmission window with a specific uplink bandwidth allocation for the transmission window. As such, uplink bandwidth can be allocated based solely on a received transmission window length on a transmission window basis by the UE by cross-referencing the received transmission window length with the bandwidth allocation map. uplink stored, transmitted to the UE, and stored in the UE's memory on a semi-static basis.

[0038] Referring first to FIG. 1, a diagram illustrates an example of a wireless communications system 100 in accordance with an aspect of the present disclosure. The wireless communications system 100 includes a plurality of access points (e.g., base stations, eNBs, or WLAN access points) 105, a number of user equipment (UE) 115, and a core network 130. The access points 105 may include an uplink programming component 602 configured to control the uplink bandwidth allocation of one or more UEs by generating and transmitting an uplink bandwidth allocation map to the one or more UEs on a semi-static. Similarly, one or more UEs 115 may include an uplink management component 661 configured to periodically receive the uplink bandwidth allocation map and reference the map for each uplink transmission window to determine the allocation of uplink bandwidth based on a received uplink transmission window length. Some of the access points 105 may communicate with the UEs 115 under the control of a base station controller (not shown), which may be part of the core network 130 or the main access points 105 (e.g., base stations or eNBs) in several examples. The access points 105 may communicate control information and/or user data with the core network 130 via backlinks 132. In examples, the access points 105 may communicate, directly or indirectly, with each other via backlink connections 134, which may be wired or wireless communication links. The wireless communications system 100 may support operation on multiple carriers (waveform signals of different frequencies). Multi-carrier transmitters can transmit modulated signals simultaneously on multiple carriers. For example, each communication link 125 may be a multicarrier signal modulated in accordance with the various radio technologies described above. Each modulated signal can be sent over a different carrier and can carry control information (e.g. reference signals, control channels, etc.), overload information, data, etc.

[0039] In some examples, at least a portion of the wireless communications system 100 may be configured to operate in multiple hierarchical layers in which one or more of the UEs 115 and one or more of the access points 105 may be configured to support transmissions in a hierarchical layer that has a reduced latency relative to another hierarchical layer. In some examples, a hybrid UE 115-a may communicate with the access point 105-a in a first hierarchical layer that supports first layer transmissions with a first symbol type and a second hierarchical layer that supports second layer transmissions with a second type of symbol. For example, access point 105-a may transmit symbols of the second symbol type that are time-division duplexed with symbols of the first symbol type.

[0040] In some examples, the hybrid UE 115-a may acknowledge reception of a transmission by providing ACK/NACK to the transmission through, for example, a HARQ scheme. Acknowledgments from the hybrid UE 115-a for transmissions in the first hierarchical layer may be provided, in some examples, after a predefined number of symbols following the symbol (or group of symbols) in which the transmission was received. The hybrid UE 115-a, when operated in the second hierarchical layer, may, in examples, acknowledge receipt on the same symbol (or group of symbols) as the symbol (or group of symbols) on which the transmission was received. The time required to transmit an ACK/NACK and receive a retransmission can be referred to as round trip time (RTT), and so symbols of the second symbol type can have a second RTT that is shorter than an RTT for symbols of the first symbol type.

[0041] In other examples, a second layer UE 115-b may communicate with access point 105-b in the second hierarchical layer only. In this way, the hybrid UE 115-a and the second-layer UE 115-b may belong to a second class of UEs 115 that can communicate in the second hierarchical layer, while the legacy UEs 115 may belong to a first class of UEs 115 that Only the first hierarchical layer can communicate. The access point 105-b and the UE 115-b may communicate in the second hierarchical layer via symbol transmissions of the second symbol type. The access point 105-b may exclusively transmit symbols of the second symbol type or may transmit one or more symbols of the first symbol type in the first hierarchical layer that are time division multiplexed with symbols of the second symbol type. The second layer UE 115-b, in case the access point 105-b transmits symbols of the first symbol type, may ignore such symbols of the first symbol type. Thus, the second layer UE 115-b may acknowledge reception of transmissions on the same symbol (or group of symbols) as the symbol (or group of symbols) on which the transmissions are received. In this way, the second layer UE 115-b can operate with reduced latency compared to UEs 115 operating in the first hierarchical layer.

[0042] The access points 105 may communicate wirelessly with the UE 15 through one or more access point antennas. Each of the local access points 105 may provide communications coverage for a respective coverage area 110. In some examples, the access points 105 may be referred to as a base transceiver station, a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, an eNode, a Home Node, or some other suitable terminology. The coverage area 110 for a base station can be divided into sectors that constitute only a portion of the coverage area (not shown). The wireless communications system 100 may include access points 105 of different types (e.g., macro, micro, and/or pico base stations). Access points 105 may also utilize different radio technologies, such as cellular radio access technologies and/or WLAN. The access points 105 may be associated with the same or different access networks or operator implementations. The coverage areas of different access points 105, including the coverage areas of the same or different types of access points 105, using the same or different radio technologies, and/or belonging to the same or different access networks, may overlap yourself.

[0043] In LTE/LTE-A network communication systems, the terms evolved Node B (eNodeB or eNB) may generally be used to describe access points 105. The wireless communications system 100 may be an LTE heterogeneous network /LTE-A in which different types of access points provide coverage for various geographic regions. For example, each access point 105 may provide communications coverage for a macro cell, a pico cell, a femto cell, and/or other cell types. Small cells such as pico cells, femto cells and/or other cell types may include low power nodes or LPNs. A macrocell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider. A small cell would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs 115 with service subscriptions with the network provider, for example, and in addition to unrestricted access, may also provide restricted access by UEs 115 that have a association with the small cell (e.g., UEs in a closed subscriber group (CSG), UEs for home users, and the like). An eNB for a macrocell can be referred to as a macro eNB. An eNB for a small cell can be referred to as a small cell eNB. An eNB may support one or several (e.g., two, three, four, and the like) cells.

[0044] The core network 130 may communicate with the eNBs or other access points 105 via a backlink 132 (e.g., S1 interface, etc.). The access points 105 may also communicate with each other, e.g., directly or indirectly through backlinks 134 (e.g., X2 interface, etc.) and/or through backlinks 132 (e.g., through of the core network 130). The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, access points 105 may have similar frame timing, and transmissions from different access points 105 may be approximately aligned in time. For asynchronous operation, access points 105 may have different frame timing, and transmissions from different access points 105 may not be aligned in time. Furthermore, transmissions in the first hierarchical layer and the second hierarchical layer may or may not be synchronized between access points 105. The techniques described herein can be used for synchronous or asynchronous operations.

[0045] The UEs 115 are dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile. A UE 115 may also be referred to by those skilled in the art as 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, remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a user agent, a mobile client, a client or any other suitable terminology. A UE 115 may be a cellular telephone, a personal digital assistant (PDA), a wireless modem, a wireless communications device, a portable device, a tablet computer, a portable computer, a cordless telephone, an article that can be used as a watch or glasses, a wireless local loop station (WLL), or similar. A UE 115 may be capable of communicating with macro eNodes, small cell eNodes, relays, and the like. A UE 115 may also be capable of communicating over different access networks, such as cellular networks or other WWAN access networks, or WLAN access networks.

[0046] The communication links 125 illustrated in the wireless communications system 100 may include uplink (UL) transmissions from a UE 115 to an access point 105, and/or downlink (DL) transmissions from a point of access 105 to a UE 115. Downlink transmissions may also be called forward link transmissions, while uplink transmissions may also be called reverse link transmissions. Communication links 125 may carry transmissions from each hierarchical layer which, in some examples, may be multiplexed across communication links 125. UEs 115 may be configured to communicate collaboratively with multiple access points 105 via, for example, MIMO (Multiple Input Multiple Output), carrier aggregation (CA), Coordinated Multi-Point (CoMP) or other schemes. MIMO techniques utilize multiple antennas on access points 105 and/or multiple antennas on UEs 115 to transmit multiple data streams. Carrier aggregation can use two or more component carriers in the same service cell or to a different service cell for data transmission. The CoMP may include techniques for coordinating transmission and reception by a number of access points 105 to improve the overall transmission quality for UEs 115 as well as to increase network and spectrum utilization.

[0047] As mentioned, in some examples, access points 105 and UE 115 may use carrier aggregation to transmit on multiple carriers. In some examples, access points 105 and UEs 115 may simultaneously transmit in a first hierarchical layer, within a frame, one or more symbols each having a first symbol type using two or more separate carriers. Each carrier may have a bandwidth of, for example, 20 MHz, although other bandwidths may be used. The hybrid UE 115-a and/or the second layer UE 115-b may, in certain examples, receive and/or transmit one or more symbols in a second hierarchical layer using a single carrier that has a bandwidth greater than a bandwidth of one or more of the separate carriers. For example, if four separate 20 MHz carriers are used in a carrier aggregation scheme in the first hierarchical layer, a single 80 MHz carrier may be used in the second hierarchical layer. The 80 MHz carrier may occupy a portion of the radio frequency spectrum that overlaps, at least partially, the radio frequency spectrum used by one or more of the four 20 MHz carriers. In some examples, the scalable bandwidth for the second type of Hierarchical layer may have combined techniques to provide shorter RTTs, as described above, to provide even improved data rates.

[0048] Each of the different modes of operation that may be utilized by the wireless communications system 100 may operate in accordance with frequency division duplexing (FDD) or time division duplexing (TDD). In some examples, different hierarchical layers may operate according to different TDD or FDD modes. For example, a first hierarchical layer can work according to FDD while a second hierarchical layer can work according to TDD. In some examples, OFDMA communications signals may be used on the communications links 125 for LTE downlink transmissions for each hierarchical layer, while single frequency division multiple access (SC-FDMA) communications signals may be used on the communication links 125 for uplink LTE transmissions at each hierarchical layer. Additional details regarding the implementation of hierarchical layers in a system such as wireless communications system 100, as well as other features and functions related to communications in such systems, are provided below with reference to the following figures.

[0049] FIG. 2 is a diagram illustrating an example of an access network 200 in an LTE network architecture. In this example, the access network 200 is divided into a number of cellular regions (cells) 202. One or more lower power class eNBs 208 may have cellular regions 210 that overlap with one or more of the cells 202. The Lower power eNB 208 may be a femto cell (e.g., home eNB (HeNB)), pico cell, micro cell, or remote radio header (RRH). The eNB macros 204 are each assigned to a respective cell 202 and are configured to provide an evolved packet core access point for all UEs 206 in cells 202. In one aspect, the eNBs 204 may include a scheduling component 602 uplink bandwidth configured to control the uplink bandwidth allocation of one or more UEs by generating and transmitting an uplink bandwidth allocation map to the one or more UEs on a semi-static basis. Similarly, one or more UEs 206 may include an uplink management component 661 configured to periodically receive the uplink bandwidth allocation map and reference the map each uplink transmission window to determine the allocation. of uplink bandwidth based on a received uplink transmission window length. There is no centralized controller in this example of an access network 200, but a centralized controller may be used in alternative configurations. The eNBs 204 are responsible for all radio-related functions, including radio carrier control, admission control, mobility control, scheduling, security, and connectivity to the service gateway 116.

[0050] The modulation and multiple access scheme used by access network 200 may vary depending on the particular telecommunications standard being implemented. In LTE applications, OFDM is used in the DL and SC-FDMA is used in the UL to support frequency division duplexing (FDD) and time division duplexing (TDD). As those skilled in the art will readily appreciate from the detailed description below, the various concepts presented here are well suited for LTE applications. However, these concepts can be quickly extended to other telecommunications standards that employ other modulation and multiple access techniques. As an example, these concepts can be extended to EV-DO (Evolution-Data Optimized) or UMB (Ultra Mobile Broadband). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project (3GPP2) as part of the CDMA2000 family of standards and employ CDMA to provide broadband Internet access to mobile stations. These concepts can also be extended to Universal Terrestrial Radio Access (UTRA), employing Wideband CDMA (W-CDMA) and other CDMA variants such as TD-SCDMA; Global System for Mobile Communications (GSM) that employs TDMA; Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20 and Flash-OFDM that employ OFDMA. UTRA, E-UTRA, UMTS, LTE and GSM are described in organization documents 3 GPP. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.

[0051] The eNBs 204 may have multiple antennas supporting MIMO technology. The use of MIMO technology allows eNBs 204 to explore the spatial domain to support spatial multiplexing, beamforming, and transmission diversity. Spatial multiplexing can be used to transmit different data streams simultaneously on the same frequency. Data streams may be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the overall system capacity. This is achieved by spatially pre-coding each data stream (i.e., applying a scale of one amplitude and one phase) and then transmitting each spatially pre-coded stream through multiple transmit antennas in the DL. The spatially pre-coded data streams arrive at the UE(s) 206 with different spatial signatures, which allows each of the UE(s) 206 to retrieve one or more data streams destined for that UE 206. In the UL , each UE 206 transmits a spatially pre-coded data stream, which allows the eNB 204 to identify the source of each spatially pre-coded data stream.

[0052] Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming can be used to focus transmission energy in one or more directions. This can be achieved by spatially encoding data for transmission across multiple antennas. To achieve good coverage at the cell edges, single-stream beamforming transmission can be used in combination with transmission diversity.

[0053] In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system that supports OFDM in the DL. OFDM is a spread spectrum technique that modulates data over a number of subcarriers within an OFDM symbol. The subcarriers are spaced at precise frequencies. The spacing provides "orthogonality" that allows a receiver to recover data from the subcarriers. In the time domain, a guard interval (e.g., cyclic prefix) can be added to each OFDM symbol to combat interference between OFDM symbols. The UL can utilize SC-FDMA in the form of a DFT spread OFDM signal to compensate for the high peak power average ratio (PAPR).

[0054] FIG. 3 is a diagram 300 illustrating an example of a DL frame structure in LTE, which, in some examples, may be used in conjunction with the downlink frame structure provided by the present disclosure. One frame (10 ms) can be divided into 10 sub-frames of equal size. Each subframe can include two consecutive time slots. A feature grid can be used to represent two time slots, each time slot including a feature element block. The resource grid is divided into several resource elements. In LTE, a resource element block can contain 12 consecutive subcarriers in the frequency domain, and for a normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain, or 84 resource elements. For an extended cyclic prefix, a resource element block can contain 6 consecutive OFDM symbols in the time domain and has 72 resource elements. Some of the feature elements, as indicated as R 302, 304, include DL reference signals (DL-RS). DLRS includes cell-specific RS (CRS) (also sometimes called common RS) 302 and UE-specific RS (UE-RS) 304. UE-RS 304 are transmitted only in the blocks of resource elements over which the corresponding PDSCH is mapped. The number of bits carried by each resource element depends on the modulation scheme. Thus, the more blocks of resource elements the UE receives and the larger the modulation scheme, the higher the data rate for the UE.

[0055] FIG. 4 is a diagram 400 illustrating an example of a UL frame structure in LTE. The resource element blocks available to the UL can be partitioned into a data section and a control section. The control section may be formed at both edges of the system bandwidth and may have a configurable size. Blocks of resource elements in the control section may be assigned to UEs for transmission of control information and, in one aspect, may be assigned based on an uplink bandwidth allocation map that is transmitted semi-statically. to UEs. The data section can include all resource element blocks not included in the control section. The UL frame structure results in the data section including contiguous subcarriers, which can allow a single UE to be assigned to all contiguous subcarriers in the data section.

[0056] A UE may be assigned blocks of resource elements 410a, 410b, which may vary based on a received transmission window length, in the control section to transmit control information to an eNB, e.g., in accordance with an uplink bandwidth allocation map. The UE may also be assigned blocks of resource elements 420a, 420b in the data section to transmit data to the eNB. The UE may transmit control information on a physical UL control channel (PUCCH) in the resource element blocks assigned in the control section. The UE may transmit data only or data and control information on a physical UL shared channel (PUSCH) in the resource element blocks assigned in the data section. A UL transmission can span multiple symbols or groups of symbols and can hop across frequency.

[0057] A set of resource element blocks may be used to perform initial system access and achieve UL synchronization on a physical random access channel (PRACH) 430. The PRACH 430 carries a random sequence and cannot carry any UL data/signaling. Each random access preamble occupies a bandwidth corresponding to six consecutive blocks of resource elements. The starting frequency is specified by the network. That is, transmission of the random access preamble is restricted to certain time and frequency resources. There is no frequency hopping for PRACH. The PRACH attempt may be performed on a single symbol or a sequence of a few contiguous symbols, and in some examples, a UE may make only a single PRACH attempt in a specified period of time (such as, but not limited to, per frame ).

[0058] FIG. 5 is a diagram 500 illustrating an example of a radio protocol architecture for user and control planes in LTE. The radio protocol architecture for the UE and eNB is shown with three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements several physical layer signal processing functions . The L1 layer will be referred to herein as the physical layer 506. The layer 2 (L2 layer) 508 is above the physical layer 506 and is responsible for the connection between the UE and eNB over the physical layer 506.

[0059] In the user plane, the L2 layer 508 includes a media access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packet data convergence protocol sublayer 514 (PDCP), which are terminated in the eNB on the network side. Although not illustrated, the UE may have several upper layers above the L2 layer 508 including a network layer (e.g., IP layer) that is terminated at the PDN gateway 118 on the network side and an application layer that is terminated at the other end. connection (e.g. distant UE, server, etc.).

[0060] The PDCP sublayer 514 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 514 also provides header compression for higher layer data packets to reduce radio transmission overhead, encryption security of the data packets, and handover support for UE between eNBs. The RLC sublayer 512 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ). The MAC sublayer 510 provides multiplexing between logical and transport channels. The MAC sublayer 510 is also responsible for allocating the various radio resources (e.g., blocks of resource elements) in a cell among the UEs. The MAC 510 sublayer is also responsible for HARQ operations.

[0061] In the control plane, the radio protocol architecture for the UE and eNB is substantially the same for the physical layer 506 and for the L2 layer 508 with the exception that there is no header compression function for the control plane. control. The control plane also includes a radio resource control (RRC) sublayer 516 at Layer 3 (L3 layer). The RRC sublayer 516 is responsible for obtaining radio resources (i.e., radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.

[0062] FIG. 6 is a block diagram of an eNB 610 communicating with a UE 650 in an access network. In DL, upper layer packets from the core network are provided to a controller/processor 675. The controller/processor 675 implements the L2 layer functionality. In the DL, the controller/processor 675 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE 650 based on various priority metrics. The controller/processor 675 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 650.

[0063] The transmission processor (TX) 616 implements various signal processing functions for the L1 layer (i.e., physical layer). Signal processing functions include coding and interleaving to facilitate forward error correction (FEC) in the UE 650 and mapping to constellations of signals based on various modulation schemes (e.g., binary phase shift keying (BPSK) , M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols are then split into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g. pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a channel physical that carries a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 674 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or a channel condition response transmitted by the UE 650. Each spatial stream is then provided to a different antenna 620 via a separate transmitter 618TX. Each 618TX transmitter modulates an RF carrier with a respective spatial stream for transmission. Additionally, the eNB 610 may include an uplink scheduling component 602 configured to control the uplink bandwidth allocation of one or more UEs by generating and transmitting an uplink bandwidth allocation map to one or more UEs on a semi-static basis.

[0064] In UE 650, each receiver 654RX receives a signal through its respective antenna 652. Each receiver 654RX retrieves modulated information about an RF carrier and provides the information to the receive processor (RX) 656. The RX processor 656 implements several L1 layer signal processing functions. The RX processor 656 performs spatial processing on the information to recover any spatial streams destined for the UE 650. If multiple spatial streams are destined for the UE 650, they may be combined by the RX processor 656 into a single OFDM symbol stream. The RX 656 processor then converts the stream of OFDM symbols from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal constitutes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 610. These soft decisions may be based on channel estimates calculated by the channel estimator 658. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 610 on the physical channel. Data and control signals are then supplied to the 659 controller/processor.

[0065] Controller/processor 659 implements the L2 layer. The controller/processor may be associated with a memory 660 that stores program codes and data. Memory 660 may be referred to as a computer-readable medium. In UL, the controller/processor 659 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover higher layer packets from the core network. The higher layer packets are then provided to a data receiver 662, which represents all protocol layers above the L2 layer. Various control signals may also be provided to data collector 662 for L3 processing. The 659 controller/processor is also responsible for error detection using an acknowledgment (ACK) and/or negative acknowledgment (NACK) protocol to support HARQ operations. Additionally, the UE 650 may include an uplink management component 661 configured to periodically receive the uplink bandwidth allocation map and reference the map for each uplink transmission window to determine the bandwidth allocation. uplink bandwidth based on a received uplink transmission window length.

[0066] In the UL, a data source 667 is used to provide higher layer packets to the controller/processor 659. The data source 667 represents all protocol layers above the L2 layer. Similar to the functionality described in connection with DL transmission by eNB 610, controller/processor 659 implements the L2 layer for the user plane and control plane providing header compression, encryption, packet segmentation and reordering, and multiplexing between logical data. and transport channels based on the allocation of radio resources by the eNB 610. The controller/processor 659 is also responsible for HARQ operations, retransmission of lost packets and signaling to the eNB 610.

[0067] Channel estimates derived by a channel estimator 658 from a reference or feedback signal transmitted by the eNB 610 may be used by the TX processor 668 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 668 are provided to the different antenna 652 through separate transmitters 654TX. Each 654TX transmitter modulates an RF carrier with a respective spatial stream for transmission.

[0068] The UL transmission is processed in the eNB 610 in a manner similar to that described in connection with the receiver function in the UE 650. Each receiver 618RX receives a signal through its respective antenna 620. Each receiver 618RX recovers modulated information on a carrier of RF and provides the information to an RX 670 processor. The RX 670 processor can implement the L1 layer.

[0069] Controller/processor 675 implements the L2 layer. The controller/processor 675 may be associated with a memory 676 that stores program codes and data. Memory 676 may be referred to as a computer-readable medium. In the UL, the controller/processor 675 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer packets from the UE 650. The packets upper layer controller/processor 675 may be provided to the core network. The 675 controller/processor is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[0070] FIGS. 7A and 7B illustrate non-limiting examples of uplink bandwidth allocations 700A and 700B, respectively, for two separate uplink transmission windows having single transmission window lengths 714 and 720, respectively. These uplink bandwidth allocations 700A and 700B may be included in an uplink bandwidth allocation map, which may be generated and transmitted to one or more UEs periodically and on a semi-static basis (e.g. , less frequently than any transmission window). In one aspect, uplink bandwidth allocations 700A and 700B contain UE-specific bandwidth allocation for an uplink channel based on a respective transmission window length. In other words, each uplink bandwidth allocation map may include bandwidth allocations for each of (or a subset of) a plurality of UEs served by the network entity for each of a plurality of window lengths. transmission. In some examples, uplink bandwidth allocation maps transmitted to separate UEs may contain unique bandwidth allocations for certain UL window lengths such that an uplink bandwidth allocation map transmitted to a first UE may be different from an uplink bandwidth allocation map transmitted to a second UE. As such, the UL-to-UE window uplink bandwidth allocation information that is included in the uplink bandwidth allocation map transmitted to each UE can potentially be different from one or more UEs for the same length window, allowing for uneven bandwidth distribution if necessary. In one aspect, each of these transmission window lengths may include a unique number of symbols that may be aggregated to form the plurality of transmission window lengths, which may each have a unique TTI. For example, in FIG. 7A, an uplink bandwidth allocation for a transmission window having a transmission window length 714 is shown. Similarly, FIG. 7B illustrates an uplink bandwidth allocation for a transmission window that has a transmission window length 720, which is shorter than the transmission window length 714.

[0071] According to one aspect of the present disclosure, a transmission window length (e.g., 714 or 720) may be transmitted on a transmission window basis (i.e., more frequently than the transmission frequency of the map uplink bandwidth allocation) and may inform each UE of the transmission window length of a subsequent transmission window (e.g., an upcoming one). Based on this transmission window length, a UE may look up its uplink bandwidth allocation corresponding to the transmission window length in a most recently received uplink bandwidth allocation map, which may be stored in a UE memory. Then, during the next transmission window, the UE may utilize the resources indicated in the corresponding uplink bandwidth allocation to transmit control data on the uplink. In one aspect, such control information may include, but is not limited to, acknowledgment messages (ACK), negative acknowledgment messages (NACK), channel quality information (CQI), or any other control information.

[0072] As illustrated in FIG. 7A, an uplink bandwidth corresponding to a shared uplink channel (e.g., a physical uplink control channel (PUCCH)) may be allocated between uplink data allocations and control information allocations. uplink. For example, other UL data 704 and 712 may correspond to uplink data transmission allocations that may be assigned based on an explicit uplink grant supported on a physical downlink control channel (PDCCH). Additionally, the uplink bandwidth allocation 700A includes control bandwidth allocations for three UEs that are dependent on the length 714 of the transmission window. These allocations include UE control bandwidth allocation 1 706, UE control bandwidth allocation 2 708, and UE control bandwidth allocation 3 710. As illustrated in FIG. 7A, each of these specific UE-dependent and transmission window length-dependent control bandwidth allocations are mapped to the single bandwidth range, resource elements, or groups of resource elements within the bandwidth. uplink bandwidth 702. In other words, based on transmission window length 714 alone, a UE 1, UE 2, and UE 3 are able to query the uplink bandwidth allocation map to determine their uplink bandwidth allocations. unique bandwidth.

[0073] Furthermore, as is evident based on a comparison of the bandwidth assignments of FIG. 7A and those of FIG. 7B, when the received transmission window length of the network entity changes, so can single bandwidth allocation for each UE. For example, if transmission window length 720 is received by each of the UEs served by the network entity (e.g., subsequent to the transmission window of FIG. 7A), UE 1, UE 2 and UE 3 may again query the uplink bandwidth allocation to look for the unique bandwidth allocations of each UE corresponding to the length 720 of the transmission window, which has a shorter duration relative to the length 714 of the transmission window. As illustrated in uplink bandwidth allocation 700B, UE 1 may determine that its uplink control bandwidth allocation matches the control bandwidth allocation of UE 1 715, UE 2 may determine that its uplink control bandwidth allocation corresponds to the control bandwidth allocation of UE2 716 and UE3 may determine that there is no uplink bandwidth allocation for this particular transmission window. Furthermore, like the uplink bandwidth allocation 700A, the uplink bandwidth allocation 700B may include bandwidth granted to other UL data 718, for example, in a previous PDCCH allocation.

[0074] In a further aspect, although the UE-specific uplink bandwidth allocations of FIGS. 7A and 7B are contiguous (i.e., each UE has a single contiguous bandwidth allocation), any UE may have multiple discontinuous bandwidth allocations (i.e., a plurality of discontinuous bandwidth slots) in a window transmission. For example, a network entity may allocate a plurality of bandwidth regions to UE 1, and the plurality of bandwidth regions may be separated by allocations (e.g., data grants or other bandwidth allocations of uplink control) to other UEs. In some examples, the UE's bandwidth allocation may take an interlocking resource block structure that spans a wide bandwidth occupying one resource block in a set of N resource blocks.

[0075] Additionally, a single uplink bandwidth time frequency resource may be assigned to multiple UEs for uplink control transmission in a single transmission window. To facilitate this aspect of the example, code division multiplexing (CDM) can be used. In other words, each UE can be assigned a particular code so that uplink transmissions of time-frequency resource allocation can be code division multiplexed using UE-specific codes that are orthogonal to each other. Additionally, OFDM numerology may favor code division multiplexing in this way over time (e.g., splitting the time window among multiple UEs), over frequency (e.g., splitting the bandwidth allocation among multiple UEs) or both. Furthermore, when an uplink transmission window has a relatively long duration and/or the uplink channel is time coherent, time CDM may be preferred over frequency CDM. Alternatively, when the uplink transmission window is relatively short in time and/or the uplink channel is frequency coherent, frequency CDM may be preferred over time CDM.

[0076] In a further aspect, a determination of whether to utilize code division multiplexing may be based on operating conditions, design numerology, or the like. For example, when a particular network entity is serving a relatively large number of UEs that must transmit control data, the network entity may determine that code division multiplexing should be used. Rules regarding the use of code division multiplexing (e.g., whether CDM should be used, which codes are assigned to which UEs, and the like) can be generated and transmitted to the UEs via a network bandwidth allocation map. uplink.

[0077] FIG. 8 is a block diagram containing a plurality of subcomponents of an uplink scheduling component 602 (see FIG. 6), which may be implemented by a network entity (e.g., an eNodeB) to allocate bandwidth resources. uplink (e.g. on a static basis), for example to reduce control overhead in an LTE system. The uplink scheduling component 602 may include an uplink bandwidth allocation map generating component 802, which may be configured to generate an uplink bandwidth allocation map that may define uplink bandwidth allocations. uplink bandwidth 806 for at least one or more UEs for each of a plurality of uplink transmission window lengths. Additionally, the uplink bandwidth allocation map generation component 802 may generate an uplink bandwidth allocation map periodically as defined by a periodicity time period 804 (e.g., a frequency of generation). In one aspect, the periodicity time period 804 may be longer than a single transmission window length, such that uplink bandwidth allocations for a plurality of transmission windows are governed by the map. In other words, the periodicity time period 804 may define the semi-static timing of the generation (and subsequent transmission by the transmission component 814) of uplink bandwidth allocation maps. In some examples, for example, the periodicity time period may be about 100 ms, although this is not a limiting example time period.

[0078] Additionally, the uplink scheduling component 602 may include a transmission window length selection component 808, which may be configured to select an uplink transmission window length for each transmission window of uplink. In some examples, the length of the uplink transmission window may be selected based, at least in part, on a number of one or more UEs associated with or served by the network entity. Alternatively or additionally, the length of the uplink transmission window may be selected based, at least in part, on an uplink load of UE 810 corresponding to one or more UEs (which may be signaled to the network entity periodically by the UE or may be determined by the network entity, for example, based on an amount of recent downlink traffic that requires a corresponding ACK or NACK). When the transmission window length is selected, the transmission component 814 may transmit the selected transmission window length to the UEs, for example, via an RRC signaling message during each transmission window (e.g., on a transmission window).

[0079] Furthermore, the selected uplink transmission window length may be transmitted by the transmission component 814 to at least one of the plurality of UEs prior to the uplink transmission window whose length is selected by the uplink selection component. transmission window length. For example, the transmit component 814 may transmit the selected transmit window length to each of the UEs during a preceding transmit or receive window such that each UE is able to query the network bandwidth allocation map. uplink stored in its memory to determine its unique allocation of uplink bandwidth based on the length of the selected transmission window.

[0080] Additionally, the uplink scheduling component 602 may include a code generation component 812, which may be configured to determine that a plurality of one or more UEs should share a bandwidth in accordance with the bandwidth map. uplink bandwidth allocation. Based on such a determination, the code generation component 812 may generate a unique code (e.g., CDM code) for each of the plurality of one or more UEs. As such, the code generation component 812 enables code division multiplexing of uplink transmissions by at least one of the plurality of UEs that may share an allocation of time-frequency resources. Additionally, the transmission component 814 may be configured to transmit the unique code to at least one of the plurality of UEs, for example, in a stand-alone signaling message or as part of an uplink bandwidth allocation map. .

[0081] FIG. 9 illustrates an example method 900 of the present disclosure, which may be performed by a network entity (e.g., an eNodeB) or a component of the network entity, such as, but not limited to, the uplink scheduling component 602 of the FIG. 6 and FIG. 8. For example, in one aspect, in block 902, method 900 may include generating, by the network entity, an uplink bandwidth allocation map. In one aspect, the uplink bandwidth allocation map may define an uplink bandwidth allocation for each of one or more UEs served by the network entity for each of a plurality of uplink window lengths. uplink transmission. In some examples, each uplink bandwidth allocation map may be unique to a UE or a subset of one or more UEs served by the network entity. As such, a first uplink bandwidth allocation map transmitted to a first UE may contain different uplink bandwidth allocations for the individual uplink transmission window lengths relative to a second uplink bandwidth allocation map. uplink bandwidth transmitted to a second UE. In one aspect, block 902 may be realized by the uplink bandwidth allocation map generating component 802 of FIG. 8.

[0082] Additionally, method 900 may include, in block 904, transmitting the uplink bandwidth allocation map to at least one of the one or more UEs. In one aspect, block 904 may be realized by transmission component 814 of FIG. 8. Furthermore, the generation and transmission of the uplink bandwidth allocation map in blocks 902 and 904 may occur periodically and according to a periodicity time period (which may be greater than a window length transmission).

[0083] Additionally, in block 906, in an optional aspect (as illustrated by the block's dotted lines), method 900 may include selecting an uplink transmission window length for an uplink transmission window. In one aspect, block 906 may be realized by the transmission window length selection component 808 of FIG. 8. Additionally, the length of the uplink transmission window may be selected based, at least in part, on a UE uplink load corresponding to one or more UEs and/or a number of one or more UEs associated with or served by the network entity.

[0084] In a further optional aspect, method 900 may include, in block 908, transmitting the length of the uplink transmission window to at least one of the plurality of UEs prior to the uplink transmission window. Like block 904, block 908 can be realized by transmission component 814 of FIG. 8. Additionally, blocks 906 and 908 may be performed for each uplink transmission window.

[0085] Furthermore, although not explicitly illustrated in FIG. 9, method 900 may include one or more alternative or additional features. For example, method 900 may include determining that a plurality of one or more UEs are to share a bandwidth in accordance with the uplink bandwidth allocation map. Furthermore, method 900 may include generating a unique code for each of the plurality of one or more UEs to enable code division multiplexing of uplink transmissions by at least one of the plurality of one or more UEs. . Likewise, method 900 may include transmitting the unique code to at least one of the plurality of one or more UEs.

[0086] FIG. 10 is a conceptual data flow diagram 1000 illustrating the flow of data between different modules/media/components in an exemplary apparatus 1002. The apparatus 1002 may be an eNodeB, which may include, but is not limited to, the access point 105 of FIG. 1, macro eNB 204 or lower power class eNB 208 of FIG. 2 or eNB 610 of FIG. 6, any of which may include uplink programming component 602 (see, e.g., Figure 8). Apparatus 1002 includes a receiving component 1004 that is configured to receive uplink data 1010 (e.g., sent to apparatus 1002 by a UE 1008, which may include, but is not limited to, UE 115 of FIG. 1 , UE 206 of FIG. 2, or UE 650 of FIG. 6). The uplink data 1010 may include, but is not limited to, one or more control signals transmitted by the UE 1008. Additionally, in some examples, the receiving component 1004 may be the transceiver 1110 or the antenna 1120 of FIG. 11.

[0087] In some cases, the receiving component 1004 may forward the received control information 1012 to the uplink scheduling component 602 (see, for example, Figure 6), which may be configured to generate an allocation map of uplink bandwidth and select an uplink transmission window length for one or more UEs (including UE 1008). The uplink scheduling component 602 may forward the uplink bandwidth allocation map and/or the uplink transmission window length 1014 to a transmission component 1006 of the apparatus 1002.

[0088] In one aspect, the transmission component 1006 (which may correspond to the transmitter component 814 of Figure 8 or transceiver 1110 or antenna 1120 of Figure 11) that is configured to transmit downlink data 1016 (which may include the allocation of uplink bandwidth and/or the length of the uplink transmission window) for one or more UEs, which may include the UE 1008.

[0089] Apparatus 1002 may include additional modules that perform each of the steps of method 900 in the aforementioned flow diagram of FIG. 9. As such, each step in the above-mentioned method 900 of FIG. 9 may be realized by a particular component and the apparatus 1002 may include one or more such components. The components may be one or more hardware components specifically configured to execute the stated method 900 and its processes/algorithm, implemented by a processor configured to execute the stated processes/algorithms, stored on a computer-readable medium for implementation by a processor , or some combination of these.

[0090] FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1002' that employs a processing system 1114. Like the apparatus 1002 of FIG. 10, the apparatus 1002' and/or the processing system 1114 may be a network entity (e.g., the access point 105 of FIG. 1, the macro eNB 204, or the lower power class eNB 208 of FIG. 2, the eNB 610 of Fig. 6 or apparatus 1002 of Fig. 10). The processing system 1114 may be implemented with a bus architecture, generally represented by bus 1124. The bus 1124 may include any number of bus bars and interconnect bridges depending on the specific application of the processing system 1114 and overall design constraints. . Bus 1124 connects together various circuits including one or more processors and/or hardware modules, represented by processor 1104, uplink scheduling component 602 (see, for example, Fig. 8), and computer-readable media. 1106. Bus 1124 can also connect various other circuits, such as timing supplies, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0091] The processing system 1114 may be coupled to a transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides a means for communicating with various other devices via a transmission medium. Furthermore, transceiver 1110 may be configured to transmit at least one uplink bandwidth allocation map and/or transmission window length to one or more UEs and may potentially include the transmission component 1006 of FIG. 10 and/or the transmission component 814 of FIG. 8. Processing system 1114 includes a processor 1104 coupled to a computer-readable medium 1106. The processor 1104 is responsible for general processing, including executing software stored on the computer-readable medium 1106. The software, when executed by the processor 1104 , causes the processing system 1114 to perform the various functions described above for any particular apparatus. The computer-readable medium 1106 may also be used to store data that is manipulated by the processor 1104 when executing the software. The processing system 1114 may further include the uplink scheduling component 602 (see, for example, FIG. 8) and one or more of its subcomponents described in FIG. 8. The modules/components may be software modules running on the processor 1104, resident/stored on the computer-readable medium 1106, one or more hardware modules coupled to the processor 1104, or some combination thereof. The processing system 1114 may be a component of the eNB 610 and may include memory 676 and/or at least one of the TX processor 616, the RX processor 670, and the controller/processor 675.

[0092] In one embodiment, the apparatus 1002' for wireless communication includes means for generating, by the network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map defining a allocating uplink bandwidth to at least one or more UEs for each of a plurality of uplink transmission window lengths; means for transmitting the uplink bandwidth allocation map to at least one of the one or more UEs; means for selecting an uplink transmission window length for an uplink transmission window; and means for transmitting the length of the uplink transmission window to at least one of the plurality of UEs prior to the uplink transmission window.

[0093] The aforementioned means may be one or more of the aforementioned modules of the apparatus 1002 and/or the processing system 1114 of the apparatus 1002' configured to perform the aforementioned functions by the aforementioned means. As described above, the processing system 1114 may include the TX processor 616, the RX processor 670, and the controller/processor 675. As such, in one configuration, the aforementioned means may be the TX processor 616, the RX processor 670, and the controller/processor 675 configured to perform the aforementioned functions by the aforementioned means.

[0094] FIG. 12 is a block diagram containing a plurality of subcomponents of an uplink management component 661 (see FIG. 6), which may be implemented by a UE to manage uplink control transmission in accordance with an allocation map. of uplink bandwidth and a transmission window length received from a network entity. In one aspect, the uplink management component 661 may include a receive component 1202, which may be configured to receive, from a network entity, an uplink bandwidth allocation map 1206. In In one aspect, the uplink bandwidth allocation map 1206 may define an uplink bandwidth allocation for the UE for each of a plurality of uplink transmission window lengths. Additionally, the receiving component 1202 may be configured to receive, from the network entity and after receiving the uplink bandwidth allocation map 1206, an uplink transmission window length for a uplink transmission, which may include a window at a time subsequent to the length of the uplink transmission window being received. Furthermore, when CDM must be used, the receiving component 1202 may receive, from the network entity, a unique code for implementing CDM during an uplink transmission window.

[0095] Additionally, the uplink management component 661 may include a memory 1204, which may be configured to store the uplink bandwidth allocation map 1206 received by the receive component 1202. In one aspect, memory 1204 may store the uplink bandwidth allocation map 1206 until a new uplink bandwidth allocation map is received, at which time the new uplink bandwidth allocation map may be replace a currently stored uplink bandwidth allocation map.

[0096] Additionally, the uplink management component 661 may include an uplink bandwidth allocation map query component 1208, which may be configured to query the uplink bandwidth allocation map 1206 in memory 1204 to determine the uplink bandwidth allocation corresponding to the received uplink transmission window length 1210. Additionally, the uplink management component 661 may include a transmission component 1212, which may be configured to transmit a control signal during the uplink transmission window length 1210 based on the uplink bandwidth allocation returned from the uplink bandwidth allocation map 1206.

[0098] FIG. 13 illustrates an example method 1300 of the present disclosure, which may be performed by a UE or a component of the UE, such as, but not limited to, the uplink management component 661 of FIG. 6 and FIG. 12. For example, in one aspect, in block 1302, method 1300 may include receiving, from a network entity, an uplink bandwidth allocation map. In one aspect, the uplink bandwidth allocation map may define an uplink bandwidth allocation for the UE for each of a plurality of uplink transmission window lengths. In one aspect, block 1302 may be realized by the receiving component 1202 of FIG. 12.

[0098] Additionally, method 1300 may include, in block 1304, storing the uplink bandwidth allocation map in a memory (e.g., memory 1204 of FIG. 12). Additionally, method 1300 may include, in block 1306, receiving, from the network entity and after receiving the uplink bandwidth allocation map, an uplink transmission window length for a uplink transmission. In one aspect, block 1306 may be realized by receiving component 1202 of FIG. 12.

[0099] Additionally, in block 1308, method 1300 may include querying the uplink bandwidth allocation map in memory to determine the uplink bandwidth allocation corresponding to the link transmission window length ascending received. In one aspect, block 1308 may be performed by the uplink bandwidth allocation map query component 1208 of FIG. 12. Additionally, method 1300 may include, in block 1310, transmitting a control signal during the length of the window based on the uplink bandwidth allocation. In one aspect, the control signal may be an ACK, NACK, CQI, a burst interference indicator, or any other control signal known to one skilled in the art. Furthermore, block 1310 may be realized by transmission component 1212 of FIG. 12.

[00100] Furthermore, although not explicitly illustrated in FIG. 13, method 1300 may include one or more alternative or additional features. For example, method 1300 may include receiving, from the network entity, a unique code for use in CDM scenarios. Furthermore, in one aspect, block 1310 may include transmitting the control signal using code to perform CDM implementation in a shared frequency and time allocation.

[00101] FIG. 14 is a conceptual data flow diagram 1400 illustrating the flow of data between different modules/media/components in an exemplary apparatus 1402. In some examples, the apparatus 1402 may be a UE (e.g., UE 115 of FIG. 1, UE 206 of FIG. 2, or UE 650 of FIG. 6). The apparatus includes a receiving component 1404 that is configured to receive data 1410 (e.g., sent to the apparatus 1402 by the network entity 1408, which may include one or more eNodes of the present description). In some examples, the receiver component 1404 may correspond to the receiver component 1202 of FIG. 12 or transceiver 1510 or antennas 1520 of FIG. 15. Additionally, data 1410 may include, but is not limited to, an uplink bandwidth allocation map and/or an uplink transmission window length as described herein. The receiving component 1404 may be configured to forward the data 1412 to an uplink management component 661 (see, e.g., FIG. 12), which may be configured to utilize the data 1412 to perform aspects of the method 1300 of FIG. 13. For example, the uplink management component 661 may be configured to store an uplink bandwidth allocation map in a memory and query the uplink bandwidth allocation map in memory to determine the uplink bandwidth allocation corresponding to a received uplink transmission window length. Additionally, the uplink management component 661 may send data/messages 1414 (e.g., associated with one or more control signals 1416) to the transmission component 1406.

[00102] Additionally, the apparatus 1402 may include a transmission component 1406 (which may correspond to the transmission component 1212 of Figure 12 or the transceiver 1510 or antennas 1520 of Figure 15) that is configured to transmit one or more control signals 1416 to network entity 1408 using an uplink bandwidth allocation that is a function of the length of the transmission window.

[00103] The apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow diagram of FIG. 13. As such, each step in the above-mentioned flowchart of FIG. 13 can be realized by a module and the apparatus can include one or more such modules. Modules may be one or more hardware components specifically configured to execute the stated processes/algorithms, implemented by a processor configured to execute the stated processes/algorithms, stored on a computer-readable medium for implementation by a processor, or some combination thereof. same.

[00104] FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1402' that employs a processing system 1514. Like the apparatus 1402 of FIG. 14, the apparatus 1402' and/or the processing system 1514 may be a UE (e.g., UE 115 of Figure 1, UE 206 of Figure 2, or UE 650 of Figure 6). The processing system 1514 may be implemented with a bus architecture, generally represented by bus 1524. The bus 1524 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1514 and overall design constraints. The bus 1524 links together various circuits including one or more processors and/or hardware modules, represented by the processor 1504, the uplink management component 661 (see, for example, Fig. 12), and the computer-readable medium. 1506. Bus 1524 can also connect various other circuits, such as timing supplies, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[00105] The processing system 1514 may be coupled to a transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1520. The transceiver 1510 provides a means for communicating with various other devices over a transmission medium. Furthermore, the transceiver 1510 may be configured to transmit at least control signals to one or more network entities and may potentially include the transmission component 1212 of FIG. 12. Processing system 1514 includes a processor 1504 coupled to a computer-readable medium 1506. The processor 1504 is responsible for general processing, including executing software stored on the computer-readable medium 1506. The software, when executed by the processor 1504 , causes the processing system 1514 to perform the various functions described above for any particular apparatus. The computer-readable medium 1506 may also be used to store data that is manipulated by the processor 1504 during software execution. The processing system further includes at least one uplink management component 661 (see, for example, Fig. 12). The modules/components may be software modules running on the processor 1504, resident/stored on the computer-readable medium 1506, one or more hardware modules coupled to the processor 1504, or some combination thereof. The processing system 1514 may be a component of the UE 650 and may include memory 660 and/or at least one of the TX processor 668, the RX processor 656, and the controller/processor 659.

[00106] In one configuration, the apparatus 1402' for wireless communication includes means for receiving, from a network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map uplink defining an uplink bandwidth allocation for the UE for each of a plurality of uplink transmission window lengths; means for storing the uplink bandwidth allocation map in a memory; means for receiving, from the network entity and after receiving the uplink bandwidth allocation map, an uplink transmission window length for an uplink transmission window; means for querying the uplink bandwidth allocation map in memory to determine the uplink bandwidth allocation corresponding to the received uplink transmission window length; and means for transmitting a control signal during the length of the window based on the uplink bandwidth allocation.

[00107] The aforementioned means may be one or more of the aforementioned modules of the apparatus 1402 and/or the processing system 1514 of the apparatus 1402' configured to perform the aforementioned functions by the aforementioned means. As described above, the processing system 1514 may include the TX processor 668, the RX processor 656, and the controller/processor 659. As such, in one configuration, the aforementioned means may be the TX processor 668, the RX processor 656, and the controller/processor 659 configured to perform the aforementioned functions by the aforementioned means.

[00108] It is understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes can be rearranged. Additionally, some steps can be combined or omitted. Tracking method claims present elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[00109] The foregoing description is provided to enable anyone skilled in the art to practice the various aspects described herein. Various modifications of these aspects will be readily apparent to those skilled in the art and the generic principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects presented herein, but are to be granted the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" specifically so declared, but rather "one or more". Unless otherwise indicated, the term "some" refers to one or more. All structural and functional equivalents to elements of the various aspects described throughout this description that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly mentioned in the claims. No claim element should be construed as a function of means plus unless the element is expressly recited using the phrase "means for."

Claims (15)

1. Method for managing uplink control channel scheduling for one or more UEs (115) served by a network entity (105) in a wireless communications system (100), characterized by the fact that it comprises: selecting a uplink control channel transmission window length (714, 720) from a plurality of uplink control channel transmission window lengths (714, 720) to an uplink control channel transmission window length (714, 720) uplink, wherein an uplink control channel bandwidth allocation for at least one of the one or more UEs (115) for the uplink control channel transmission window length (714, 720) is configured for and transmitted to the at least one of the one or more UEs (115) and specifies a variable bandwidth resource that is a function of the uplink transmission window length; and allowing uplink control channel bandwidth allocation corresponding to the uplink control channel transmission window length (714, 720) to the at least one of the one or more UEs (115) when transmitting the length of uplink control channel transmission window (714, 720) for the at least one of the one or more UEs (115) before the uplink control channel transmission window. 2. Method according to claim 1, characterized by the fact that it further comprises: generating, by the network entity (105), an uplink control channel bandwidth allocation map, the uplink control channel bandwidth defining an uplink control channel bandwidth allocation for the at least one of the or more UEs (115) for at least one of the plurality of channel transmission window lengths uplink control (714, 720); and transmitting the uplink control channel bandwidth allocation map to at least one of the one or more UEs (115). 3. Method according to claim 2, characterized by the fact that generation and transmission occur periodically and according to a periodic period of time. 4. The method of claim 1, wherein the length of the uplink control channel transmission window (714, 720) is selected based, at least in part, on a number of the one or more UEs (115) associated with the network entity (105). 5. The method of claim 1, wherein the uplink control channel transmission window length (714, 720) is selected based, at least in part, on an uplink load of UE (115) corresponding to the one or more UEs (115). 6. The method of claim 2, further comprising: determining that a plurality of the one or more UEs (115) are to share a bandwidth in accordance with the channel bandwidth allocation map uplink control; generating a unique code for at least one of the plurality of the one or more UEs (115) to enable code division multiplexing of uplink transmissions by at least one of the plurality of the one or more UEs (115); and transmitting the unique code to at least one of the plurality of the one or more UEs (115). 7. The method of claim 2, wherein the uplink control channel bandwidth allocation is a contiguous bandwidth allocation; or wherein the uplink control channel bandwidth allocation comprises an allocation of a plurality of discontinuous bandwidth slots. 8. Apparatus for managing uplink control channel scheduling for one or more UEs (115) served by a network entity (105) in a wireless communications system (100), characterized in that it comprises: means for selecting an uplink control channel transmission window length (714, 720) from a plurality of uplink control channel transmission window lengths (714, 720) for an uplink control channel transmission window length (714, 720) uplink control, wherein an uplink control channel bandwidth allocation to at least one of the one or more UEs (115) for the uplink control channel transmission window length (714, 720 ) is configured for and transmitted to the at least one of the one or more UEs (115) and specifies a variable bandwidth resource that is a function of the uplink transmission window length; and means for allowing uplink control channel bandwidth allocation corresponding to the uplink control channel transmission window length (714, 720) to the at least one of the one or more UEs (115) when transmitting the length of the uplink control channel transmission window (714, 720) for the at least one of the one or more UEs (115) before the uplink control channel transmission window. 9. The apparatus of claim 8, further comprising: means for generating, by the network entity (105), an uplink control channel bandwidth allocation map, the uplink control channel bandwidth allocation defining an uplink control channel bandwidth allocation for at least one of the or more UEs (115) for at least one of the plurality of uplink control channel bandwidth allocations for at least one of the uplink control channel (714, 720); and means for transmitting the uplink control channel bandwidth allocation map to at least one of the one or more UEs (115). 10. The apparatus of claim 9, wherein the means for generating generate the uplink control channel bandwidth allocation map and the means for transmitting transmit the bandwidth allocation map uplink control channel periodically and according to a periodicity time period. 11. The apparatus of claim 8, wherein the length of the uplink control channel transmission window (714, 720) is selected by the means for selecting based, at least in part, on a number of the one or more UEs (115) associated with the network entity (105). 12. The apparatus of claim 8, wherein the length of the uplink control channel transmission window (714, 720) is selected by the means for selecting based, at least in part, on a UE uplink load (115) corresponding to the one or more UEs (115). 13. The apparatus of claim 9, further comprising: means for determining that a plurality of one or more UEs (115) are to share a bandwidth in accordance with the bandwidth allocation map uplink control channel; means for generating a code unique to at least one of the plurality of the one or more UEs (115) to enable code division multiplexing of uplink transmissions by at least one of the plurality of the one or more UEs (115); and means for transmitting the unique code to at least one of the plurality of the one or more UEs (115). 14. The apparatus of claim 9, wherein the uplink control channel bandwidth allocation is a contiguous bandwidth allocation; or wherein the uplink control channel bandwidth allocation comprises an allocation of a plurality of discontinuous bandwidth slots. 15. Computer-readable memory comprising instructions stored therein for managing uplink control channel scheduling for one or more UEs (115) served by a network entity (105) in a wireless communications system (100), the instructions being executable by a computer to perform the steps of the method as defined in any one of claims 1 to 7.