Uplink control resource allocation for dynamic time division duplex systems
By generating and transmitting uplink bandwidth allocation maps for multiple transmission window lengths in the LTE system, the problem of low allocation efficiency of uplink control resource allocation in traditional systems is solved, dynamic bandwidth allocation is realized, and system efficiency is improved.
Patent Information
- Application Number
- CN202011307799.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2015-10-02
- Filing Date
- 2015-10-05
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2035-10-05
AI Technical Summary
In the adoption of traditional LTE wireless communication systems, the allocation efficiency of uplink control resources is low, especially when the length of the dynamic transmission window is unknown, resulting in inefficiency of the system.
The uplink bandwidth allocation map is generated and transmitted through a network entity, which defines the bandwidth allocation for each UE for a plurality of transmission window lengths, and the UE querys the stored mapping after receiving the transmission window length to determine the bandwidth allocation, implementing the Dynamic bandwidth allocation.
It improves the allocation efficiency of uplink control resources, reduces inefficiency, and enhances the overall performance of the system.
Smart Images

Figure CN112492690B_ABST
Abstract
Description
[0001] This application is a divisional application of Chinese invention patent application 201580060065.8 (PCT / US2015 / 054063) with a filing date of October 5, 2015 and entitled “Uplink Control Resource Allocation for Dynamic Time Division Duplex Systems”. Technical Field
[0002] The present disclosure generally relates to communication systems, and more particularly to a method and apparatus for allocating uplink control resources in a wireless communication system. Background Art
[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical 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). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0004] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate in cities, countries, regions, and even global levels. An example of an emerging telecommunication standard is Long Term Evolution (LTE). LTE is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA on downlink (DL), using SC-FDMA on uplink (UL) and using multiple input multiple output (MIMO) antenna technology. However, as the demand for mobile broadband access continues to grow, there is a need for further improvement in LTE technology. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that adopt these technologies.
[0005] In a wireless communication system using conventional LTE, multiple UEs served by a particular network entity (e.g., an eNodeB) may receive control information from the eNodeB on a shared physical downlink control channel (PDCCH). The control information included in the PDCCH may include one or more uplink resource grants for the UE to transmit uplink data in a future LTE uplink transmission window. However, when the UE is to transmit control information in the uplink, it is often inefficient for the network entity to transmit dynamic grants for each uplink control information transmission. In addition, pre-allocating fixed resources (in time and frequency) without knowing the length of the dynamic uplink transmission window also leads to system inefficiencies.
[0006] As such, improvements in uplink control resource allocation are needed to alleviate these current inefficiencies. Summary of the invention
[0007] A brief summary of one or more aspects is given below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its only purpose is to give some concepts of one or more aspects in a simplified form as a prelude to a more detailed description given later.
[0008]
[0011] In accordance with one or more aspects and corresponding disclosure thereof, various techniques are described in conjunction with example methods and apparatus for managing user equipment communications in a wireless communication system.
[0009] For example, the present disclosure provides an example method for managing uplink scheduling of one or more UEs served by a network entity in a wireless communication system. The example method may include generating an uplink bandwidth allocation map by the network entity, the uplink bandwidth allocation map defining an uplink bandwidth allocation for at least one UE in the one or more UEs for at least one uplink transmission window length in a plurality of uplink transmission window lengths. In addition, the example method may include transmitting the uplink bandwidth allocation map to at least one UE in the one or more UEs.
[0010] In a further aspect, the present disclosure provides an example apparatus for managing uplink scheduling of one or more UEs served by a network entity in a wireless communication 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, the instructions may be executed by the processor to: generate an uplink bandwidth allocation map by the network entity, 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 transmit the uplink bandwidth allocation map to at least one of the one or more UEs.
[0011] In addition, the present disclosure provides a further example apparatus for managing uplink scheduling of one or more UEs served by a network entity in a wireless communication system. In one aspect, the example apparatus may include means for generating an uplink bandwidth allocation map by the network entity, the uplink bandwidth allocation map defining an uplink bandwidth allocation for at least one of the one or more UEs for at least one uplink transmission window length in a plurality of uplink transmission window lengths. In addition, the example 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 present disclosure provides a non-transitory computer-readable medium storing computer-executable code for managing uplink scheduling of one or more UEs served by a network entity in wireless communication. The code may include instructions executable to: generate, by the network entity, an uplink bandwidth allocation map, the uplink bandwidth allocation map defining an uplink bandwidth allocation for at least one UE among the one or more UEs for at least one uplink transmission window length in a plurality of uplink transmission window lengths; and transmit the uplink bandwidth allocation map to at least one UE among the one or more UEs.
[0013] In addition, the present disclosure describes a wireless communication method that can be performed by a UE. The example method may include receiving an uplink bandwidth allocation map from a network entity, and the uplink bandwidth allocation map defines an uplink bandwidth allocation for the UE for at least one uplink transmission window length in a plurality of uplink transmission window lengths. The method may further include storing the uplink bandwidth allocation map in a memory. In addition, the method may include receiving an uplink transmission window length from an uplink transmission window from the network entity after receiving the uplink bandwidth allocation map. In addition, the method may include querying the uplink bandwidth allocation map in the 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 window length based on the uplink bandwidth allocation.
[0014] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the appended claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 shows a block diagram conceptually illustrating an example of a telecommunications system according to an aspect of the present disclosure;
[0016] Figure 2 is a diagram illustrating an example of an access network.
[0017] Figure 3 is a diagram illustrating an example of a DL frame structure in LTE.
[0018] Figure 4 is a diagram illustrating an example of a UL frame structure in LTE.
[0019] Figure 5 is a diagram illustrating an example of a radio protocol architecture for a user plane and a control plane.
[0020] Figure 6 is a diagram illustrating an example of an evolved NodeB and user equipment in an access network.
[0021] Fig. 7A is a diagram illustrating an example uplink bandwidth allocation map for uplink bandwidth allocation according to the present disclosure.
[0022] Figure 7B is a diagram illustrating an example uplink bandwidth allocation map for uplink bandwidth allocation according to the present disclosure.
[0023] Figure 8 is a diagram illustrating uplink scheduling components configured to implement aspects of the present disclosure.
[0024] Fig. 9 is a flow chart of an uplink bandwidth allocation method.
[0025] Fig.10 is a conceptual data flow diagram illustrating the flow of data between different modules / devices / 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 uplink management components configured to implement aspects of the present disclosure.
[0028] Fig.13 is a flow chart of an uplink bandwidth management method.
[0029] Fig.14 is a conceptual data flow diagram illustrating the flow of data between different modules / devices / 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 set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid diluting such concepts.
[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0033] As an example, an element, or any part of an element, or any combination of elements can be implemented with a "processing system" including 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, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.
[0034] Accordingly, in one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD) and floppy disk, wherein the disc often reproduces data magnetically, and the disc reproduces data optically with a laser. The above combination should also be included in the scope of computer-readable media.
[0035] The present disclosure provides example methods and equipment for managing resource allocation for uplink control transmission. For example, in one aspect of the present disclosure, a UE may be assigned variable bandwidth resources via an uplink bandwidth allocation map (also referred to herein as a "mapping"), which is a function of the uplink transmission window length specified by a serving network entity. In other words, based on the specified window length, the specific uplink bandwidth allocation for the UE may vary for each uplink transmission window. In one aspect, this window length may vary over time. In other words, the window length may include one or more symbols, which may be aggregated over time to form a transmission time interval (TTI) of variable size.
[0036] In addition, the network entity may generate an uplink bandwidth allocation map on a semi-static basis and transmit the uplink bandwidth allocation map to each UE associated therewith or a subset of these UEs that may be scheduled for uplink transmission. In other words, the network entity may transmit the map on a periodic basis (wherein the periodicity of the map transmission is not as frequent as per window (e.g., once every 100 ms)) rather than transmitting the map for each uplink transmission window. In addition, the most recently received map may be stored in the UE memory.
[0037] In addition, before each transmission window, the UE may receive a transmission window length corresponding to each transmission window from the network entity. The UE may then query a mapping stored in the UE memory to match the received transmission window length with a specific uplink bandwidth allocation for the transmission window. In this way, uplink bandwidth may be allocated based solely on the transmission window length received on a per-transmission window basis by the UE cross-referencing the received transmission window length with a stored uplink bandwidth allocation mapping, which may be updated by the network entity on a semi-static basis, transmitted to the UE, and stored in the UE memory.
[0038] First refer to Figure 1, illustrates an example of a wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 includes a plurality of access points (e.g., base stations, eNBs, or WLAN access points) 105, a plurality of user equipments (UEs) 115, and a core network 130. The access points 105 may include an uplink scheduling component 602 configured to control uplink bandwidth allocation for one or more UEs by generating an uplink bandwidth allocation map on a semi-static basis and transmitting it to the one or more UEs. Similarly, one or more UEs 115 may include an uplink management component 661 configured to periodically receive an uplink bandwidth allocation map and refer to the map in each uplink transmission window to determine uplink bandwidth allocation based on the received uplink transmission window length. Some access points 105 may communicate with the UEs 115 under the control of a base station controller (not shown), which in various examples may be part of the core network 130 or some access points 105 (e.g., base stations or eNBs). The access point 105 may communicate control information and / or user data with the core network 130 via the backhaul link 132. In some examples, the access point 105 may communicate with each other directly or indirectly on the backhaul link 134, which may be a wired or wireless communication link. The wireless communication system 100 may support operations on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals on these multiple carriers at the same time. For example, each communication link 125 may be a multi-carrier signal modulated according to the various radio technologies described above. Each modulated signal may be sent on a different carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, data, etc.
[0039] In some examples, at least a portion of the wireless communication system 100 may be configured to operate on multiple layers, wherein one or more UEs 115 and one or more access points 105 may be configured to support transmissions on a layer with reduced latency relative to another layer. In some examples, a hybrid UE 115-a may communicate with the access point 105-a on both a first layer supporting first layer transmissions having a first symbol type and a second layer supporting second layer transmissions having a second symbol type. For example, the access point 105-a may transmit symbols of the second symbol type time division duplexed with symbols of the first symbol type.
[0040] In some examples, hybrid UE 115-a may confirm receipt of a transmission by, for example, providing an ACK / NACK for the transmission via a HARQ scheme. In some examples, an acknowledgment of a transmission in a first stratum from hybrid UE 115-a may be provided a predefined number of symbols after the symbol (or group of symbols) in which the transmission was received. In an example, when operating in a second stratum, hybrid UE 115-a may confirm reception in the same symbol (or group of symbols) as the symbol (or group of symbols) in which the transmission was received. The time required to transmit an ACK / NACK and receive a retransmission may be referred to as a round trip time (RTT), and thus symbols of the second symbol type may have a second RTT that is shorter than the RTT of symbols of the first symbol type.
[0041] In other examples, the second layer UE 115-b may communicate with the access point 105-b only on the second layer. Thus, the hybrid UE 115-a and the second layer UE 115-b may belong to the second type of UE 115 that can communicate on the second layer, while the traditional UE 115 may belong to the first type of UE 115 that can communicate only on the first layer. The access point 105-b and the UE 115-b may communicate on the second layer by transmitting symbols 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 time-division multiplexed with symbols of the second symbol type on the first layer. In the case where the access point 105-b transmits symbols of the first symbol type, the second layer UE 115-b may ignore such symbols of the first symbol type. Thus, the second layer UE 115-b may confirm the reception of the transmission in the same symbol (or symbol group) as the symbol (or symbol group) in which the transmission is received. Thus, the second tier UE 115-b may operate with reduced latency compared to UE 115 operating on the first tier.
[0042] The access point 105 may communicate wirelessly with the UE 115 via one or more access point antennas. Each access point 105 site may provide communication coverage for a respective coverage area 110. In some examples, the access point 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 B node, an evolved B node, a home B node, a home evolved B node, or some other suitable term. The coverage area 110 of the base station may be divided into sectors (not shown) that constitute only a portion of the coverage area. The wireless communication system 100 may include different types of access points 105 (e.g., macro base stations, micro base stations, and / or pico base stations). The access point 105 may also utilize different radio technologies, such as cellular and / or WLAN radio access technologies. The access point 105 may be associated with the same or different access networks or operator deployments. The coverage areas of different access points 105 (including coverage areas of the same or different types of access points 105, coverage areas utilizing the same or different radio technologies, and / or coverage areas belonging to the same or different access networks) may overlap.
[0043] In LTE / LTE-A network communication systems, the term evolved Node B (eNodeB or eNB) may be generally used to describe access point 105. Wireless communication system 100 may be a heterogeneous LTE / LTE-A network, in which different types of access points provide coverage for various geographic regions. For example, each access point 105 may provide communication coverage for macro cells, micro cells, femto cells, and / or other types of cells. Small cells (such as micro cells, femto cells, and / or other types of cells) may include low power nodes or LPNs. Macro cells generally cover a relatively large geographic area (e.g., an area with a radius of several kilometers) and may allow unrestricted access by UE 115 with a service subscription to a network provider. A small cell will generally cover a relatively small geographic area and may allow, for example, unrestricted access by UEs 115 that have a service subscription with a network provider, and may provide restricted access by UEs 115 associated with the small cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in the residence, and the like) in addition to unrestricted access. An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells.
[0044] The core network 130 may communicate with an eNB or other access point 105 via a backhaul 132 (e.g., an S1 interface, etc.). The access points 105 may also communicate with each other, directly or indirectly, for example, via a backhaul link 134 (e.g., an X2 interface, etc.) and / or via a backhaul link 132 (e.g., through the core network 130). The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, each access point 105 may have similar frame timing, and transmissions from different access points 105 may be approximately aligned in time. For asynchronous operation, each access point 105 may have different frame timing, and transmissions from different access points 105 may not be aligned in time. In addition, transmissions in the first and second strata may be synchronized or asynchronous between the access points 105. The techniques described herein may be used for synchronous or asynchronous operation.
[0045] UE 115 is dispersed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile.UE 115 may also be referred to 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, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or other appropriate terms by those skilled in the art. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wearable item (such as a watch or glasses), a wireless local loop (WLL) station, etc. UE 115 may be able to communicate with a macro eNodeB, a small cell eNodeB, a relay, and the like. UE 115 may also be able to communicate through different access networks (such as cellular or other WWAN access networks, or WLAN access networks).
[0046] The communication link 125 shown in the wireless communication system 100 may include an uplink (UL) transmission from the UE 115 to the access point 105, and / or a downlink (DL) transmission from the access point 105 to the UE 115. Downlink transmissions may also be referred to as forward link transmissions, and uplink transmissions may also be referred to as reverse link transmissions. The communication link 125 may carry transmissions of each layer, and in some examples, these transmissions may be multiplexed in the communication link 125. The UE 115 may be configured to communicate cooperatively with multiple access points 105 through, for example, multiple input multiple output (MIMO), carrier aggregation (CA), coordinated multi-point (CoMP), or other schemes. MIMO technology uses multiple antennas on the access point 105 and / or multiple antennas on the UE 115 to transmit multiple data streams. Carrier aggregation may utilize two or more component carriers on the same or different serving cells for data transmission. CoMP may include techniques for coordinating transmission and reception by several access points 105 to improve the overall transmission quality of the UE 115 and increase network and spectrum utilization.
[0047] As mentioned, in some examples, the access point 105 and the UE 115 may utilize carrier aggregation to transmit on multiple carriers. In some examples, the access point 105 and the UE 115 may concurrently use two or more separate carriers in a frame in the first layer to transmit one or more symbols each having a first symbol type. Each carrier may have a bandwidth of, for example, 20 MHz, but other bandwidths may be utilized. In some examples, the hybrid UE 115-a and / or the second layer UE 115-b may receive and / or transmit one or more symbols in the second layer using a single carrier having a bandwidth greater than the bandwidth of one or more of the separate carriers. For example, if four separate 20 MHz carriers are used in the carrier aggregation scheme in the first layer, a single 80 MHz carrier may be used in the second layer. The 80 MHz carrier may occupy a portion of the radio frequency spectrum that at least partially overlaps with the radio frequency spectrum used by one or more of the four 20 MHz carriers. In some examples, scalable bandwidth for the second tier type may be a combination technique for providing a shorter RTT (such as the RTT described above) to provide further enhanced data rates.
[0048] Each of the different operating modes that the wireless communication system 100 may employ may operate according to frequency division duplex (FDD) or time division duplex (TDD). In some examples, different strata may operate according to different TDD or FDD modes. For example, a first stratum may operate according to FDD, while a second stratum may operate according to TDD. In some examples, OFDMA communication signals may be used in the communication link 125 for LTE downlink transmissions in each stratum, while single carrier frequency division multiple access (SC-FDMA) communication signals may be used in the communication link 125 for LTE uplink transmissions in each stratum. Additional details regarding the implementation of strata in a system such as the wireless communication system 100 and other features and functions related to communications in such a system are provided below with reference to subsequent figures.
[0049] Figure 2 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 a cellular region 210 that overlaps with one or more cells 202. The lower power class eNBs 208 may be femtocells (e.g., home eNBs (HeNBs)), picocells, microcells, or remote radio heads (RRHs). Macro eNBs 204 are each assigned to a respective cell 202 and are configured to provide access points to an evolved packet core for all UEs 206 in the cell 202. In one aspect, the eNB 204 may include an uplink scheduling component 602 that is configured to control uplink bandwidth allocation for one or more UEs by generating an uplink bandwidth allocation map on a semi-static basis and transmitting it to the one or more UEs. Similarly, one or more UEs 206 may include an uplink management component 661 configured to periodically receive an uplink bandwidth allocation map and reference the map in each uplink transmission window to determine the uplink bandwidth allocation based on the received uplink transmission window length. In this example of the access network 200, there is no centralized controller, but a centralized controller may be used in an alternative configuration. The eNB 204 is responsible for all radio-related functions, including radio bearer control, admission control, mobility control, scheduling, security, and connectivity with the serving gateway 116.
[0050] The modulation and multiple access scheme adopted by access network 200 can vary depending on the specific telecommunication standard being deployed. In LTE applications, OFDM is used on DL and SC-FDMA is used on UL to support both frequency division duplex (FDD) and time division duplex (TDD). As those skilled in the art will easily appreciate from the following detailed description, the various concepts given herein are well suited for LTE applications. However, these concepts can be easily extended to other telecommunication standards that adopt other modulation and multiple access technologies. As an example, these concepts can be extended to Evolution Data Optimization (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards as a part of the CDMA 2000 family of standards promulgated by the Third Generation Partnership Project 2 (3GPP2), and CDMA is used to provide broadband Internet access to mobile stations. These concepts can also be extended to Universal Terrestrial Radio Access (UTRA) using Wideband CDMA (W-CDMA) and other CDMA variants (such as TD-SCDMA); Global System for Mobile Communications (GSM) using TDMA; and Evolved UTRA (E-UTRA) using OFDMA, IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA, E-UTRA, UMTS, LTE, and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and multiple access technology used will depend on the specific application and the overall design constraints imposed on the system.
[0051] The eNB 204 may have multiple antennas that support MIMO technology. The use of MIMO technology enables the eNB 204 to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to transmit different data streams simultaneously on the same frequency. These data streams can be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the total system capacity. This is achieved by spatially precoding each data stream (i.e., applying amplitude and phase scaling) and then transmitting each spatially precoded stream on the DL through multiple transmit antennas. The spatially precoded data streams arrive at (these) UEs 206 with different spatial signatures, and these different spatial signatures enable each UE 206 to recover one or more data streams intended for the UE 206. On the UL, each UE 206 transmits a spatially precoded data stream, which enables the eNB 204 to identify the source of each spatially precoded 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 the transmit energy in one or more directions. This can be achieved by spatially precoding the data for transmission over multiple antennas. To achieve good coverage at the cell edge, single-stream beamforming transmission can be used in conjunction with transmit diversity.
[0053] In the following detailed description, various aspects of the access network will be described with reference to a MIMO system that supports OFDM on the DL. OFDM is a spread spectrum technique that modulates data onto several subcarriers within an OFDM symbol. These subcarriers are separated by precise frequencies. This separation provides "orthogonality" that enables a receiver to recover data from these subcarriers. In the time domain, a guard interval (e.g., a cyclic prefix) may be added to each OFDM symbol to combat inter-OFDM symbol interference. SC-FDMA in the form of a DFT-spread OFDM signal may be used in the UL to compensate for high peak-to-average power ratio (PAPR).
[0054] Figure 3 300 is a diagram illustrating an example of a DL frame structure in LTE, which in some examples may be utilized in conjunction with the downlink frame structure provided by the present disclosure. A frame (10 ms) may be divided into 10 equally sized subframes. Each subframe may include 2 consecutive time slots. A resource grid may be used to represent the 2 time slots, each of which includes a resource element block. The resource grid is divided into a plurality of resource elements. In LTE, a resource element block may include 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 the case of an extended cyclic prefix, a resource element block may include 6 consecutive OFDM symbols in the time domain and have 72 resource elements. Some resource elements, such as indicated as R 302, 304, include DL reference signals (DL-RS). DL-RS includes RS (CRS) (sometimes also called common RS) 302 that is specific to a cell and RS (UE-RS) 304 that is specific to a UE. UE-RS 304 is transmitted only on the resource element block to which the corresponding PDSCH is mapped. The number of bits carried by each resource element depends on the modulation scheme. Therefore, the more resource element blocks a UE receives and the higher the modulation scheme, the higher the data rate of the UE.
[0055] Figure 44 is a diagram illustrating an example of a UL frame structure in LTE. The available resource element blocks of the UL may be divided into a data segment and a control segment. The control segment may be formed at two edges of the system bandwidth and may have a configurable size. The resource element blocks in the control segment may be assigned to UEs for transmitting control information, and in one aspect, may be assigned based on an uplink bandwidth allocation map semi-statically transmitted to the UE. The data segment may include all resource element blocks not included in the control segment. The UL frame structure results in the data segment including contiguous subcarriers, which may allow a single UE to be assigned all contiguous subcarriers in the data segment.
[0056] The UE may be assigned resource element blocks 410a, 410b in the control section to transmit control information to the eNB (e.g., according to an uplink bandwidth allocation map), which may vary based on a received transmission window length. The UE may also be assigned resource element blocks 420a, 420b in the data section for transmitting data to the eNB. The UE may transmit control information in a physical UL control channel (PUCCH) on the assigned resource element blocks in the control section. The UE may transmit only data or both data and control information in a physical UL shared channel (PUSCH) on the assigned resource element blocks in the data section. UL transmissions may span multiple symbols or groups of symbols and may hop across frequencies.
[0057] A set of resource element blocks may be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430. PRACH 430 carries a random sequence and cannot carry any UL data / signaling. Each random access preamble occupies a bandwidth corresponding to 6 consecutive resource element blocks. The starting frequency is specified by the network. That is, the transmission of the random access preamble is restricted to certain time-frequency resources. There is no frequency hopping for PRACH. A PRACH attempt may be carried in a single symbol or in a sequence containing several adjacent symbols, and in some examples, a UE may only make a single PRACH attempt in a specified time period (such as but not limited to each frame).
[0058] Figure 5 5 is a diagram illustrating an example of a radio protocol architecture for the user plane and control plane in LTE. The radio protocol architecture for the UE and eNB is shown as having three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions. The L1 layer will be referred to herein as the physical layer 506. Layer 2 (L2 layer) 508 is above the physical layer 506 and is responsible for the link between the UE and the eNB above the physical layer 506.
[0059] In the user plane, the L2 layer 508 includes a medium access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packet data convergence protocol (PDCP) 514 sublayer, which terminate at the eNB on the network side. Although not shown, the UE may have several upper layers above the L2 layer 508, including a network layer (e.g., an IP layer) terminated at the PDN gateway 118 on the network side, and an application layer terminated at the other end of the connection (e.g., a remote UE, a 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 upper layer data packets to reduce radio transmission overhead, provides security by encrypting data packets, and provides support for UE switching 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 channels and transport channels. The MAC sublayer 510 is also responsible for allocating various radio resources (e.g., resource element blocks) in a cellular cell between UEs. The MAC sublayer 510 is also responsible for HARQ operations.
[0061] In the control plane, the radio protocol architecture for the UE and the eNB is basically the same for the physical layer 506 and the L2 layer 508, except that there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) sublayer 516 in layer 3 (L3 layer). The RRC sublayer 516 is responsible for obtaining radio resources (ie, radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.
[0062] Figure 6 6 is a block diagram of an eNB 610 and a UE 650 in communication in an access network. In the DL, upper layer packets from the core network are provided to the controller / processor 675. The controller / processor 675 implements the functionality of the L2 layer. In the DL, the controller / processor 675 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical channels and transport channels, and radio resource allocation 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 transmit (TX) processor 616 implements various signal processing functions for the L1 layer (i.e., the physical layer). These signal processing functions include coding and interleaving to facilitate forward error correction (FEC) at the UE 650 and mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). Subsequently, the coded and modulated symbols are split into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. The channel estimate from the channel estimator 674 can be used to determine the coding and modulation scheme and for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by the UE 650. Each spatial stream is then provided to a different antenna 620 via a separate transmitter 618TX. Each transmitter 618TX modulates an RF carrier with a respective spatial stream for transmission. In addition, the eNB 610 may include an uplink scheduling component 602 configured to control uplink bandwidth allocation for one or more UEs by generating an uplink bandwidth allocation map on a semi-static basis and transmitting it to the one or more UEs.
[0064] At the UE 650, each receiver 654RX receives a signal through its respective antenna 652. Each receiver 654RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 656. The RX processor 656 implements various signal processing functions of the L1 layer. The RX processor 656 performs spatial processing on the information to recover any spatial stream destined for the UE 650. If there are multiple spatial streams destined for the UE 650, they can be combined into a single OFDM symbol stream by the RX processor 656. The RX processor 656 then transforms the OFDM symbol stream 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 symbol on each subcarrier, as well as the reference signal, is recovered and demodulated by determining the signal constellation point most likely transmitted by the eNB 610. These soft decisions can be based on the channel estimate calculated by the channel estimator 658. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the eNB 610. These data and control signals are then provided to the controller / processor 659.
[0065] The controller / processor 659 implements the L2 layer. The controller / processor may be associated with a memory 660 storing program codes and data. The memory 660 may be referred to as a computer-readable medium. In the UL, the controller / processor 659 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover upper layer packets from the core network. These upper layer packets are then provided to a data sink 662, which represents all protocol layers above the L2 layer. Various control signals may also be provided to the data sink 662 for L3 processing. The controller / processor 659 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations. In addition, the UE 650 may include an uplink management component 661, which is configured to periodically receive an uplink bandwidth allocation map and refer to the map in each uplink transmission window to determine the uplink bandwidth allocation based on the received uplink transmission window length.
[0066] In the UL, a data source 667 is used to provide upper 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 conjunction with DL transmissions by the eNB 610, the controller / processor 659 implements the L2 layers for the user plane and control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical channels and transport channels based on radio resource allocations 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 signal or feedback transmitted by the eNB 610 may be used by a TX processor 668 to select the appropriate coding and modulation scheme, and to facilitate spatial processing. The spatial streams generated by the TX processor 668 are provided to different antennas 652 via separate transmitters 654TX. Each transmitter 654TX modulates an RF carrier with a respective spatial stream for transmission.
[0068] UL transmissions are processed at the eNB 610 in a manner similar to that described in conjunction with the receiver functionality at the UE 650. Each receiver 618RX receives a signal through its respective antenna 620. Each receiver 618RX recovers information modulated onto an RF carrier and provides the information to a RX processor 670. The RX processor 670 may implement the L1 layer.
[0069] The controller / processor 675 implements the L2 layer. The controller / processor 675 may be associated with a memory 676 that stores program codes and data. The memory 676 may be referred to as a computer-readable medium. In the UL, the controller / processor 675 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover upper layer packets from the UE 650. The upper layer packets from the controller / processor 675 may be provided to the core network. The controller / processor 675 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0070] Fig. 7A and 7B Non-limiting examples of uplink bandwidth allocations 700A and 700B for two separate uplink transmission windows having unique transmission window lengths 714 and 720, respectively, are illustrated. 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., not as frequently as per transmission window). On the one hand, based on the corresponding transmission window length, the uplink bandwidth allocations 700A and 700B include bandwidth allocations that vary from UE to UE for uplink channels. In other words, each uplink bandwidth allocation map may include bandwidth allocations for each UE (or subset) of a plurality of UEs served by a network entity for each transmission window length in a plurality of transmission window lengths. In some examples, the uplink bandwidth allocation map transmitted to the separated UEs may include unique bandwidth allocations for a given UL window length so that the uplink bandwidth allocation map transmitted to the first UE may be different from the uplink bandwidth allocation map transmitted to the second UE. Thus, for the same window length, the UL window length to UE uplink bandwidth allocation information included in the uplink bandwidth allocation map transmitted to each UE may potentially be different from one or more other UEs, thereby allowing for unequal bandwidth allocations if desired. In one aspect, each transmission window length may include a unique number of symbols, which may be aggregated to form multiple transmission window lengths, each of which may have a unique TTI. For example, in Fig. 7A In FIG. 1 , the uplink bandwidth allocation for a transmission window with a transmission window length of 714 is given. Similarly, Figure 7B An uplink bandwidth allocation for a transmission window having a transmission window length 720 that is shorter than the transmission window length 714 is depicted.
[0071] According to one aspect of the present disclosure, a transmission window length (e.g., 714 or 720) may be transmitted on a per-transmission window basis (i.e., more frequently than the uplink bandwidth allocation map transmission periodicity), and each UE may be informed of the transmission window length for a subsequent (e.g., next) transmission window. Based on this transmission window length, the UE may look up its uplink bandwidth allocation corresponding to the transmission window length in the most recently received uplink bandwidth allocation map. Subsequently, during the next transmission window, the UE may transmit control data on the uplink using the resources indicated in the corresponding uplink bandwidth allocation. In one aspect, such control information may include, but is not limited to, an acknowledgment (ACK) message, a negative acknowledgment (NACK) message, a channel quality information (CQI), or any other control information.
[0072] like Fig. 7A As shown, uplink bandwidth corresponding to a shared uplink channel (e.g., a physical uplink control channel (PUCCH)) may be allocated between uplink data allocations and uplink control information allocations. For example, other UL data 704 and 712 may correspond to uplink data transmission allocations that may be allocated based on explicit uplink grants carried on a physical downlink control channel (PDCCH). In addition, uplink bandwidth allocation 700A includes control bandwidth allocations for three UEs that depend on a transmission window length 714. These allocations include UE 1 control bandwidth allocation 706, UE 2 control bandwidth allocation 708, and UE 3 control bandwidth allocation 710. As shown in FIG. Fig. 7A As illustrated in , each of these UE-specific and transmission window length-dependent control bandwidth allocations is mapped to a unique bandwidth range, resource element, or resource element group within the uplink bandwidth 702. In other words, based solely on the transmission window length 714, UE 1, UE 2, and UE 3 are able to query the uplink bandwidth allocation map to determine their unique bandwidth allocations.
[0073] In addition, based on Fig. 7A Bandwidth allocation and Figure 7B As can be clearly seen from the comparison of the bandwidth allocations of , when the transmission window length received from the network entity changes, the unique bandwidth allocation for each UE may also change. For example, if each UE served by the network entity receives a transmission window length of 720 (e.g., Fig. 7A714). If, after a transmission window of UE 1, UE 2, and UE 3 have been received, UE 1, UE 2, and UE 3 may again query the uplink bandwidth allocation map to find a unique bandwidth allocation for each UE corresponding to a transmission window length 720 having a shorter duration relative to the transmission window length 714. As illustrated in uplink bandwidth allocation 700B, UE 1 may determine that its uplink control bandwidth allocation corresponds to UE 1 control bandwidth allocation 715, UE 2 may determine that its uplink control bandwidth allocation corresponds to UE 2 control bandwidth allocation 716, and UE 3 may determine that there is no uplink bandwidth allocation for this particular transmission window. In addition, similar to uplink bandwidth allocation 700A, uplink bandwidth allocation 700B may include bandwidth 718 granted to other UL data (e.g., in a previous PDCCH allocation).
[0074] In an additional respect, although Fig. 7A and 7B UE-specific uplink bandwidth allocations are contiguous (i.e., each UE has a single contiguous bandwidth allocation), but any UE may have multiple non-contiguous bandwidth allocations (i.e., multiple non-contiguous bandwidth ranges) in a transmission window. For example, the network entity may allocate multiple bandwidth regions to UE 1, and the multiple bandwidth regions may be separated by allocations to other UEs (e.g., data grants or other uplink control bandwidth allocations). In some examples, the bandwidth allocation of a UE may take the form of an interleaved resource block structure that spans a wide bandwidth occupying one resource block in a set of N resource blocks.
[0075] In addition, a single time-frequency resource of the uplink bandwidth may be allocated to multiple UEs for uplink control transmission in a single transmission window. In order to facilitate this example aspect, code division multiplexing (CDM) may be utilized. In other words, each UE may be assigned a specific code so that these mutually orthogonal codes that vary from UE to UE may be used to code-division multiplex the uplink transmission of the time-frequency resource allocation. In addition, OFDM numerology may be advantageous for code division multiplexing in this manner in time (e.g., splitting the time window between multiple UEs), in frequency (e.g., splitting the bandwidth allocation between multiple UEs), or both. In addition, in the case where the uplink transmission window is relatively long in duration and / or the uplink channels are coherent in time, CDM in time may be preferred to CDM in frequency. Alternatively, in the case where the uplink transmission window is relatively short in time and / or the uplink channels are coherent in frequency, CDM in frequency may be preferred to CDM in time.
[0076] In an additional aspect, the determination as to whether to utilize code division multiplexing can be based on operating conditions, design numerology, etc. For example, where a particular network entity is serving a relatively large number of UEs that must transmit control data, the network entity can determine to utilize code division multiplexing. Rules relating to the use of code division multiplexing (e.g., whether to use CDM, which codes to assign to which UEs, etc.) can be generated and communicated to the UEs via an uplink bandwidth allocation map.
[0077] Figure 8 The uplink scheduling component 602 (see Figure 6 ), which may be implemented by a network entity (e.g., an eNodeB) for allocating uplink bandwidth resources (e.g., on a semi-static basis), such as to reduce control overhead in an LTE system. An uplink scheduling component 602 may include an uplink bandwidth allocation map generation component 802, which may be configured to generate an uplink bandwidth allocation map, which may define an uplink bandwidth allocation 806 for at least one of one or more UEs for each of a plurality of uplink transmission window lengths. In addition, the uplink bandwidth allocation map generation component 802 may periodically generate the uplink bandwidth allocation map as defined by a periodic time period 804 (e.g., a generation frequency). In one aspect, the periodic time period 804 may be longer than a single transmission window length so that uplink bandwidth allocations for multiple transmission windows are governed by the map. In other words, the periodic time period 804 may define a semi-static timing for generating (and subsequently transmitting by a transmitting component 814) an uplink bandwidth allocation map. For example, in some examples, the periodic time period may be approximately 100 ms, although this is not a limiting example time period.
[0078] In addition, uplink scheduling component 602 may include transmission window length selection component 808, which may be configured to select the uplink transmission window length of each uplink transmission window. In some examples, the uplink transmission window length may be selected based at least in part on the number of one or more UEs associated with or served by the network entity. Alternatively or additionally, the uplink transmission window length may be selected based at least in part on the UE uplink load 810 corresponding to the one or more UEs (which may be periodically signaled by the UE to notify the network entity or may be determined by the network entity (e.g., based on the recent downlink traffic volume requiring corresponding ACK or NACK)). When the transmission window length is selected, the transmission component 814 may transmit the selected transmission window length (e.g., via RRC signaling message) to the UE during each transmission window (e.g., on the basis of each transmission window).
[0079] Additionally, the selected uplink transmission window length can be transmitted to at least one of the plurality of UEs by transmitting component 814 prior to an uplink transmission window whose length is selected by the transmission window length selection component. For example, transmitting component 814 can transmit the selected transmission window length to each UE during a previous transmission or reception window to enable each UE to query an uplink bandwidth allocation map stored in its memory to determine its unique uplink bandwidth allocation based on the selected transmission window length.
[0080] In addition, the uplink scheduling component 602 may include a code generation component 812, which may be configured to determine that multiple UEs in the one or more UEs are to share bandwidth according to an uplink bandwidth allocation map. Based on such determination, the code generation component 812 may generate a unique code (e.g., a CDM code) for each of the multiple UEs in the one or more UEs. In this way, the code generation component 812 enables code division multiplexing of uplink transmissions performed by at least one UE in the multiple UEs that can share time-frequency resource allocation. In addition, the transmission component 814 may be configured to transmit the unique code (e.g., in a self-reliant signaling message or as part of an uplink bandwidth allocation map) to at least one UE in the multiple UEs.
[0081] Fig. 9 An example method 900 of the present disclosure is illustrated, which may be performed by a network entity (eg, an eNodeB) or a component of a network entity (such as, but not limited to, Figure 6 and Figure 8 For example, in one aspect, at block 902, method 900 may include generating, by a network entity, an uplink bandwidth allocation map. In one aspect, the uplink bandwidth allocation map may define, for each uplink transmission window length in a plurality of uplink transmission window lengths, uplink bandwidth allocations for each UE of one or more UEs served by the network entity. 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. Thus, a first uplink bandwidth allocation map transmitted to a first UE may include different uplink bandwidth allocations for individual uplink transmission window lengths relative to a second uplink bandwidth allocation map transmitted to a second UE. In one aspect, block 902 may be performed by Figure 8 The uplink bandwidth allocation map generation component 802 is executed.
[0082] Additionally, method 900 may include transmitting the uplink bandwidth allocation map to at least one of the one or more UEs at block 904. In one aspect, block 904 may be performed by Figure 8The transmission component 814 of the embodiment is executed. In addition, the generation and transmission of the uplink bandwidth allocation map at blocks 902 and 904 can occur periodically according to a periodic time period (which can be greater than the transmission window length).
[0083] Additionally, at block 906, in an optional aspect (as illustrated by the dashed line of the block), method 900 may include selecting an uplink transmission window length for the uplink transmission window. In one aspect, block 906 may be performed by Figure 8 The transmission window length selection component 808 of the network entity is executed. In addition, the uplink transmission window length can be selected based at least in part on the UE uplink load corresponding to the one or more UEs and / or the number of the one or more UEs associated with or served by the network entity.
[0084] In an additional optional aspect, method 900 may include, at block 908, transmitting the uplink transmission window length to at least one UE of the plurality of UEs prior to the uplink transmission window. Similar to block 904, block 908 may be performed by Figure 8 The transmission component 814 of the embodiment of the present invention is executed. In addition, blocks 906 and 908 can be performed for each uplink transmission window.
[0085] In addition, despite Fig. 9 , but method 900 may include one or more alternative or additional features. For example, method 900 may include determining that multiple UEs of the one or more UEs are to share bandwidth according to the uplink bandwidth allocation map. In addition, method 900 may include generating a unique code for each of the multiple UEs of the one or more UEs to enable code division multiplexing of uplink transmissions performed by at least one of the multiple UEs of the one or more UEs. Similarly, method 900 may include transmitting the unique code to at least one of the multiple UEs of the one or more UEs.
[0086] Fig.10 1000 is a conceptual data flow diagram illustrating the data flow between different modules / devices / components in an exemplary apparatus 1002. The apparatus 1002 may be an eNodeB, which may include but is not limited to Figure 1 Access point 105, Figure 2 macro eNB 204 or lower power class eNB 208, or Figure 6 eNB 610, any of which may include an uplink scheduling component 602 (e.g., see Figure 8 The device 1002 includes a receiving component 1004 configured to receive uplink data 1010 (eg, uplink data sent to the device 1002 by a UE 1008, which may include but is not limited to Figure 1 UE 115 Figure 2 UE 206, or Figure 6 UE 650). Uplink data 1010 may include, but is not limited to, one or more control signals transmitted by UE 1008. Additionally, in some examples, receiving component 1004 may be Fig.11 transceiver 1110 or antenna 1120 .
[0087] In some examples, receiving component 1004 can communicate to uplink scheduling component 602 (eg, see Figure 6 ) forwards the received control information 1012, the uplink scheduling component 602 can be configured to generate an uplink bandwidth allocation map and select an uplink transmission window length for one or more UEs, including UE 1008. The uplink scheduling component 602 can forward the uplink bandwidth allocation map and / or the uplink transmission window length 1014 to the transmission component 1006 of the equipment 1002.
[0088] In one aspect, a transmission component 1006 (which may correspond to Figure 8 The transmission component 814 or Fig.11 The transceiver 1110 or antenna 1120 of the wireless communication network 100 is configured to transmit downlink data 1016 (which may include an uplink bandwidth allocation map and / or an uplink transmission window length) to one or more UEs (which may include UE 1008).
[0089] Equipment 1002 may include performing the aforementioned Fig. 9 900 in the flowchart of the method 900. Fig. 9 Each step in the method 900 may be performed by a specific component and the apparatus 1002 may include one or more of those components. Each component may be one or more hardware components specifically configured to implement the method 900 and its processes / algorithms, implemented by a processor configured to execute the processes / algorithms, stored in a computer-readable medium for implementation by a processor, or some combination thereof.
[0090] Fig.11 1100 is a diagram illustrating an example of a hardware implementation for an apparatus 1002' employing a processing system 1114. Fig.10 The device 1002, the device 1002' and / or the processing system 1114 may be a network entity (e.g., Figure 1 Access point 105, Figure 2 macro eNB 204 or lower power class eNB 208, Figure 6 eNB 610, or Fig.10The processing system 1114 may be implemented using a bus architecture generally represented by bus 1124. Depending on the specific application and overall design constraints of the processing system 1114, bus 1124 may include any number of interconnecting buses and bridges. Bus 1124 may include one or more processors and / or hardware modules (including processor 1104, uplink scheduling component 602 (e.g., see Figure 8 ), and various circuits represented by computer readable media 1106 are linked together. Bus 1124 may also link various other circuits (such as timing sources, 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 over a transmission medium. In addition, the transceiver 1110 may be configured to transmit at least an uplink bandwidth allocation map and / or a transmission window length to one or more UEs and may potentially include Fig.10 The transmission component 1006 and / or Figure 1 The 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 device. 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 an uplink scheduling component 602 (e.g., see Figure 8 )as well as Figure 8 The processing system 1114 may be a component of the eNB 610 and may include the memory 676 and / or include at least one of the TX processor 616, the RX processor 670, and the controller / processor 675.
[0092] In one configuration, an apparatus 1002' for wireless communication includes: a device for generating an uplink bandwidth allocation map by a network entity, the uplink bandwidth allocation map defining an uplink bandwidth allocation for at least one UE among the one or more UEs for each uplink transmission window length in a plurality of uplink transmission window lengths; a device for transmitting the uplink bandwidth allocation map to at least one UE among the one or more UEs; a device for selecting an uplink transmission window length of an uplink transmission window; and a device for transmitting the uplink transmission window length to at least one UE among the multiple UEs before the uplink transmission window.
[0093] The aforementioned means may be one or more of the aforementioned modules in the processing system 1114 of the apparatus 1002 and / or the apparatus 1002' configured to perform the functions recited by the aforementioned means. As previously described, the processing system 1114 may include the TX processor 616, the RX processor 670, and the controller / processor 675. Thus, 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 functions recited by the aforementioned means.
[0094] Fig.12 It includes an uplink management component 661 (see Figure 6 ) is a block diagram of multiple subcomponents of a UE, which can be implemented by a UE to manage uplink control transmissions according to an uplink bandwidth allocation map and a transmission window length received from a network entity. In one aspect, the uplink management component 661 may include a receiving component 1202, which may be configured to receive an uplink bandwidth allocation map 1206 from a network entity. In one aspect, the uplink bandwidth allocation map 1206 may define an uplink bandwidth allocation for the UE for each uplink transmission window length in a plurality of uplink transmission window lengths. In addition, the receiving component 1202 may be configured to receive an uplink transmission window length (which may include a window at a subsequent time relative to the time when the uplink transmission window length is received) from the network entity after receiving the uplink bandwidth allocation map 1206. In addition, in the case where CDM is to be utilized, the receiving component 1202 may receive a uniqueness code for CDM implementation from the network entity during the uplink transmission window.
[0095] Additionally, uplink management component 661 can include memory 1204, which can be configured to store uplink bandwidth allocation map 1206 received by receiving component 1202. In one aspect, memory 1204 can store uplink bandwidth allocation map 1206 until a new uplink bandwidth allocation map is received, at which point the new uplink bandwidth allocation map can replace the currently stored uplink bandwidth allocation map.
[0096] In addition, the uplink management component 661 can include an uplink bandwidth allocation map query component 1208, which can be configured to query the uplink bandwidth allocation map 1206 in the memory 1204 to determine the uplink bandwidth allocation corresponding to the received uplink transmission window length 1210. In addition, the uplink management component 661 can include a transmission component 1212, which can 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.
[0097] Fig.13 An example method 1300 of the present disclosure is illustrated, which may be performed by a UE or a component of a UE such as, but not limited to, Figure 6 and Fig.12 For example, in one aspect, at block 1302, method 1300 may include receiving an uplink bandwidth allocation map from a network entity. In one aspect, the uplink bandwidth allocation map may define an uplink bandwidth allocation for the UE for each uplink transmission window length in a plurality of uplink transmission window lengths. In one aspect, block 1302 may be performed by Fig.12 The receiving component 1202 executes.
[0098] Additionally, method 1300 may include storing, at block 1304, Fig.12 In addition, the method 1300 may include, at block 1306, receiving an uplink transmission window length of an uplink transmission window from the network entity after receiving the uplink bandwidth allocation map. In one aspect, block 1306 may be performed by Fig.12 The receiving component 1202 executes.
[0099] Additionally, at block 1308, method 1300 may include querying the uplink bandwidth allocation map in the memory to determine an uplink bandwidth allocation corresponding to the received uplink transmission window length. In one aspect, block 1308 may be performed by Fig.12The uplink bandwidth allocation mapping query component 1208 is executed. In addition, the method 1300 may include transmitting a control signal during the window length based on the uplink bandwidth allocation at block 1310. In one aspect, the control signal may be an ACK, a NACK, a CQI, a burst interference indicator, or any other control signal known to a person of ordinary skill in the art. In addition, block 1310 may be performed by Fig.12 The transmission component 1212 executes.
[0100] In addition, despite Fig.13 Although not explicitly shown in FIG. 1 , method 1300 may include one or more alternative or additional features. For example, method 1300 may include receiving a unique code from the network entity for use in a CDM context. In addition, in one aspect, block 1310 may include using the code to transmit a control signal to achieve a CDM implementation of shared time-frequency allocation.
[0101] Fig.14 1400 is a conceptual data flow diagram illustrating the data flow between different modules / devices / components in an exemplary apparatus 1402. In some examples, the apparatus 1402 may be a UE (e.g., Figure 1 UE115, Figure 2 UE 206, or Figure 6 UE 650). The equipment includes a receiving component 1404, which is configured to receive data 1410 (e.g., data sent by a network entity 1408 (which may include one or more eNodeBs in the present disclosure) to the equipment 1402). In some examples, the receiving component 1404 may correspond to Fig.12 The receiving component 1202 or Fig.15 The transceiver 1510 or antenna 1520 of FIG. 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 communicate to the uplink management component 661 (e.g., see FIG. 1410 ). Fig.12 ) forwarding data 1412, the uplink management component 661 may be configured to utilize the data 1412 to perform Fig.13 For example, the uplink management component 661 can be configured to store an uplink bandwidth allocation map in a memory and query the uplink bandwidth allocation map in the memory to determine an uplink bandwidth allocation corresponding to the received uplink transmission window length. In addition, the uplink management component 661 can send data / message 1414 (e.g., data / message associated with one or more control signals 1416) to the transmission component 1406.
[0102] Additionally, the equipment 1402 may include a transmission component 1406 (which may correspond to Fig.12 The transmission component 1212 or Fig.15 A transceiver 1510 or antenna 1520) configured to transmit one or more control signals 1406 to a network entity 1408 using an uplink bandwidth allocation that is a function of a transmission window length.
[0103] The equipment may include performing the aforementioned Fig.13 The flowchart contains additional modules for each step of the algorithm. Fig.13 Each step in the aforementioned flow chart of can be performed by a module and the equipment may include one or more modules in those modules. Each module can be one or more hardware components specially configured to implement the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or a combination thereof.
[0104] Fig.15 1500 is a diagram illustrating an example of a hardware implementation for an apparatus 1402' employing a processing system 1514. Fig.14 The equipment 1402, the equipment 1402' and / or the processing system 1514 may be a UE (eg, Figure 1 UE 115 Figure 2 UE206, or Figure 6 UE 650). Processing system 1514 may be implemented with a bus architecture generally represented by bus 1524. Bus 1524 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of processing system 1514. Bus 1524 may include one or more processors and / or hardware modules (including processor 1504, uplink management component 661 (see, for example, FIG. 14 ), and uplink management component 662 (see, for example, FIG. 14 ). Fig.12 ), and various circuits represented by computer readable media 1506 are linked together. Bus 1524 may also link various other circuits (such as timing sources, peripherals, voltage regulators, and power management circuits), which are well known in the art and therefore will not be described further.
[0105] 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. In addition, the transceiver 1510 may be configured to transmit at least control signals to one or more network entities and may potentially include Fig.12The 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 device. The computer-readable medium 1506 may also be used to store data that is manipulated by the processor 1504 when executing the software. The processing system further includes an uplink management component 661 (e.g., see Fig.12 ) . These modules / components may be software modules running in the processor 1504, software modules residing / stored in 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 the memory 660 and / or include at least one of the TX processor 668, the RX processor 656, and the controller / processor 659.
[0106] In one configuration, an apparatus 1402' for wireless communication includes: a device for receiving an uplink bandwidth allocation map from a network entity, the uplink bandwidth allocation map defining an uplink bandwidth allocation for the UE for each uplink transmission window length of a plurality of uplink transmission window lengths; a device for storing the uplink bandwidth allocation map in a memory; a device for receiving an uplink transmission window length of an uplink transmission window from the network entity after receiving the uplink bandwidth allocation map; a device for querying the uplink bandwidth allocation map in the memory to determine an uplink bandwidth allocation corresponding to the received uplink transmission window length; and a device for transmitting a control signal during the window length based on the uplink bandwidth allocation.
[0107] The aforementioned means may be one or more of the aforementioned modules in the processing system 1514 of the equipment 1402 and / or the equipment 1402' configured to perform the functions recited by the aforementioned means. As previously described, the processing system 1514 may include the TX processor 668, the RX processor 656, and the controller / processor 659. Thus, 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 functions recited by the aforementioned means.
[0108] It should be understood that the specific order or hierarchy of the steps in the disclosed processes is an illustration of an exemplary approach. It should be understood that the specific order or hierarchy of the steps in these processes can be rearranged based on design preferences. In addition, some steps can be combined or omitted. The attached method claims present the elements of the various steps in an exemplary order and are not meant to be limited to the specific order or hierarchy given.
[0109] 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 universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the claims in language, wherein the singular reference to the element is not intended to mean "there is and only one", but "one or more", unless otherwise specifically stated. Unless otherwise specifically stated, the term "some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structurally and functionally equivalent schemes currently or hereafter known to those of ordinary skill in the art, and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be contributed to the public, regardless of whether such disclosure is explicitly stated in the claims. No claim element should be interpreted as a device plus function, unless the element is explicitly stated using the phrase "device for...".
Claims
1. A method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network entity, an indication of an uplink control channel transmission window of a plurality of uplink control channel transmission windows defined by the network entity for the UE, wherein each uplink control channel transmission window of the plurality of uplink control channel transmission windows corresponds to an uplink control bandwidth allocation for an uplink control channel during the uplink control channel transmission window in which one or more UEs served by the network entity, including the UE, communicate uplink control information; as well as Control signals are transmitted to the network entity on the uplink control channel during the uplink control channel transmission window according to the uplink control bandwidth allocation based on the indication of the uplink control channel transmission window.
2. The method of claim 1, further comprising: receiving, from the network entity, an uplink control channel bandwidth allocation map, the uplink control channel bandwidth allocation map defining the uplink control bandwidth allocation for each of the plurality of uplink control channel transmission windows defined for the UE based at least in part on a corresponding uplink control channel transmission window length; as well as The uplink control bandwidth allocation corresponding to the uplink control channel transmission window is determined based on the uplink control channel bandwidth allocation map.
3. The method of claim 1, wherein the plurality of uplink control channel transmission windows are semi-statically allocated.
4. The method of claim 1, wherein the uplink control bandwidth allocation is one of: a contiguous bandwidth allocation, or an allocation of multiple non-contiguous bandwidth ranges.
5. The method of claim 1, wherein each of the plurality of uplink control channel transmission windows has a window length of one or more symbols.
6. The method of claim 5, wherein the uplink control bandwidth allocation comprises a bandwidth range, a number of resource elements, or a number of resource element groups.
7. The method of claim 5, wherein the uplink control bandwidth allocation comprises resource elements or resource element groups within the one or more symbols.
8. The method of claim 1 , wherein transmitting the control signal comprises: Transmit an acknowledgement (ACK / NACK) message or a channel quality information (CQI) message.
9. The method of claim 1, wherein transmissions by the UE during at least one of the multiple uplink control channel transmission windows are combined with transmissions of other UEs served by the network entity using code division multiplexing.
10. The method of claim 9, wherein the code division multiplexing comprises time domain code division multiplexing.
11. The method of claim 9, further comprising: A code for the code division multiplexing is received from the network entity.
12. The method of claim 1, wherein different values of the indication are associated with different uplink control channel transmission windows among the plurality of uplink control channel transmission windows.
13. The method of claim 1, wherein the uplink control bandwidth allocation comprises resource elements or resource element groups.
14. The method of claim 1, wherein the plurality of uplink control channel transmission windows are separate from an uplink data channel.
15. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as a processor coupled to the memory and configured to: receiving, from a network entity, an indication of an uplink control channel transmission window of a plurality of uplink control channel transmission windows defined by the network entity for the UE, wherein each uplink control channel transmission window of the plurality of uplink control channel transmission windows corresponds to an uplink control bandwidth allocation for an uplink control channel during the uplink control channel transmission window in which one or more UEs served by the network entity, including the UE, communicate uplink control information; as well as Control signals are transmitted to the network entity on the uplink control channel during the uplink control channel transmission window according to the uplink control bandwidth allocation based on the indication of the uplink control channel transmission window.
16. The apparatus of claim 15, wherein the processor is further configured to: receiving, from the network entity, an uplink control channel bandwidth allocation map, the uplink control channel bandwidth allocation map defining the uplink control bandwidth allocation for each of the plurality of uplink control channel transmission windows defined for the UE based at least in part on a corresponding uplink control channel transmission window length; and The uplink control channel bandwidth allocation map is queried to determine the uplink control bandwidth allocation corresponding to the uplink control channel transmission window length.
17. The apparatus of claim 16, wherein the plurality of uplink control channel transmission windows are semi-statically allocated.
18. The apparatus of claim 15, wherein the uplink control bandwidth allocation is at least one of: a contiguous bandwidth allocation, or an allocation of multiple non-contiguous bandwidth ranges.
19. The apparatus of claim 15, wherein each of the plurality of uplink control channel transmission windows has a window length of one or more symbols.
20. The apparatus of claim 15, wherein the processor configured to transmit the control signal is further configured to transmit an acknowledgement (ACK / NACK) message or a channel quality information (CQI) message.
21. An apparatus for wireless communication at a user equipment (UE), comprising: means for receiving, from a network entity, an indication of an uplink control channel transmission window of a plurality of uplink control channel transmission windows defined by the network entity for the UE, wherein each uplink control channel transmission window of the plurality of uplink control channel transmission windows corresponds to an uplink control bandwidth allocation for an uplink control channel during the uplink control channel transmission window in which one or more UEs served by the network entity, including the UE, communicate uplink control information; as well as means for transmitting a control signal to the network entity on the uplink control channel during the uplink control channel transmission window in accordance with the uplink control bandwidth allocation based on the indication of the uplink control channel transmission window.
22. The apparatus of claim 21, further comprising: means for receiving an uplink control channel bandwidth allocation map from the network entity, the uplink control channel bandwidth allocation map defining the uplink control bandwidth allocation for each of the plurality of uplink control channel transmission windows defined for the UE based at least in part on a corresponding uplink control channel transmission window length; as well as Means for querying the uplink control channel bandwidth allocation map to determine the uplink control bandwidth allocation corresponding to the uplink control channel transmission window.
23. The apparatus of claim 22, wherein the plurality of uplink control channel transmission windows are semi-statically allocated.
24. The apparatus of claim 21, wherein the uplink control bandwidth allocation is at least one of: a contiguous bandwidth allocation, or an allocation of multiple non-contiguous bandwidth ranges.
25. The apparatus of claim 21, wherein each of the plurality of uplink control channel transmission windows has a window length of one or more symbols.
26. The apparatus of claim 21, wherein the means for transmitting the control signal is configured to transmit an acknowledgement (ACK / NACK) message or a channel quality information (CQI) message.
27. A non-transitory computer-readable medium storing computer-executable code for wireless communication at a user equipment (UE), comprising: code for receiving, from a network entity, an indication of an uplink control channel transmission window of a plurality of uplink control channel transmission windows defined by the network entity for the UE, wherein each uplink control channel transmission window of the plurality of uplink control channel transmission windows corresponds to an uplink control bandwidth allocation for an uplink control channel during the uplink control channel transmission window in which one or more UEs served by the network entity communicate uplink control information; as well as Code for transmitting a control signal to the network entity on the uplink control channel during the uplink control channel transmission window according to the uplink control bandwidth allocation based on the indication of the uplink control channel transmission window.
28. The non-transitory computer readable medium of claim 27, further comprising: code for receiving, from the network entity, an uplink control channel bandwidth allocation map that defines the uplink control bandwidth allocation for each of the plurality of uplink control channel transmission windows defined for the UE based at least in part on a corresponding uplink control channel transmission window length; as well as Code for querying the uplink control channel bandwidth allocation map to determine the uplink control bandwidth allocation corresponding to the uplink control channel transmission window.
29. The non-transitory computer readable medium of claim 28, wherein the plurality of uplink control channel transmission windows are semi-statically allocated.
30. The non-transitory computer-readable medium of claim 27, wherein the uplink control bandwidth allocation is at least one of: a contiguous bandwidth allocation, or an allocation of multiple non-contiguous bandwidth ranges.
31. The non-transitory computer-readable medium of claim 28, wherein each uplink control channel transmission window of the plurality of uplink control channel transmission windows has a symbol length of one or more symbols.
32. The non-transitory computer-readable medium of claim 28, wherein the code for transmitting comprises: A code used to transmit an acknowledgment (ACK / NACK) message or a channel quality information (CQI) message.
