BR112017014904B1 - METHOD AND APPARATUS FOR MANAGING ULTRA LOW LATENCY COMMUNICATIONS OVER A PLURALITY OF COMPONENT CARRIERS AND COMPUTER READABLE MEMORY - Google Patents

Abstract

Several aspects described here pertain to managing ultra-low latency (ULL) communications over a plurality of component (CC) carriers. An arrangement for aggregating a set of CCs may be received, wherein the set of CCs includes at least one primary cell and one secondary cell. Based on the received configuration, at least the primary cell can be communicated for legacy communication, wherein legacy communications are based on a first transmission time interval (TTI) having a first duration. Based on the received configuration, the primary cell and the secondary cell can be communicated for ULL communications, wherein the ULL communications are based on a second TTI having a second duration that is less than the first duration.

Description

Cross Reference to Related Orders

[0001] This application claims the benefit of US provisional order no. 62/102,303 entitled “TECHNIQUES FOR MANAGING WIRELESS COMMUNICATIONS OVER MULTIPLE CARRIERS” filed on January 12, 2015 and US patent application no. 14/962,871, entitled “TECHNIQUES FOR MANAGING WIRELESS COMMUNICATIONS OVER MULTIPLE CARRIERS”, filed on December 8, 2015, which are expressly incorporated by reference into the present invention in full.

BACKGROUND

[0002] Aspects in general related to communication systems and more particularly to the management of wireless communications through multiple carriers are described here.

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (eg, 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 (OFDMA), 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 a common protocol that allows different wireless devices to communicate on a city, national, regional and even global level. An example of a telecommunication standard is Long Term Evolution (LTE). LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard enacted by the Third Generation Society Project (3GPP). It is designed to support better mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA on the downlink (DL), SC-FDMA on the uplink (UL) and multiple input multiple output (MIMO) antenna technology. However, as the demand for mobile broadband access continues to increase, there is a need for further improvements in LTE technology. Preferably, these enhancements should be applicable to other multi-access technologies and to telecommunication standards that employ these technologies.

[0005] In wireless communication systems employing legacy LTE, a plurality of UEs served by a specific eNodeB can be resources programmed to communicate with the eNodeB through one or more channels using transmission time intervals (TTI) of the order of a 1 millisecond subframe. As UE capabilities and bandwidth demand increase, lower latency in communications may be desirable.

summary

[0006] The following presents a simplified summary of one or more aspects to provide a basic understanding of those aspects. This summary is not an extensive overview of all Aspects considered, and is not intended to identify key or critical elements of all Aspects or to delineate the scope of all or any Aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] According to an example, a method of managing ultra-low latency (ULL) communications over a plurality of component (CC) carriers is provided. The method includes receiving a configuration for aggregating a set of CCs, where the set of CCs includes at least one primary cell and one secondary cell. The method also includes communicating, based on the received configuration, with at least the primary cell for legacy communications, wherein legacy communications are based on a first transmission time interval (TTI) having a first duration, and communicating, with based on the received configuration, with at least one of the primary cell or secondary cell for ULL communications, wherein the ULL communications are based on a second TTI having a second duration that is less than the first duration.

[0008] In other aspects, an apparatus for managing ULL communications through a plurality of CCS is provided. The apparatus includes at least one processor, and memory communicatively coupled to the at least one processor. At least one processor is configured to receive a configuration for aggregating a set of CCs, wherein the set of CCs includes at least one primary cell and one secondary cell. The at least one processor is also configured to communicate, based on the received configuration, with at least the primary cell for legacy communications, wherein the legacy communications are based on a first TTI having a first duration and communicate, based on the configuration received, with at least one between primary cell or secondary cell for UL communications, wherein ULL communications are based on a second TTI having a second duration that is less than the first duration.

[0009] In another example, an apparatus for managing ULL communications across a plurality of CCs is provided. The apparatus includes means for receiving an arrangement for aggregating a set of CCs, wherein the set of CCs includes at least one primary cell and one secondary cell. The apparatus also includes means for communicating, based on the received configuration, with at least the primary cell for legacy communications, wherein legacy communications are based on a first TTI having a first duration, and means for communicating, based on the received configuration with at least one of the primary cell or secondary cell for ULL communications, wherein the ULL communications are based on a second TTI having a second duration that is less than the first duration.

[00010] In other aspects, a computer-readable storage medium including computer-executable code for managing ULL communications across a plurality of CCs is provided. The code includes code to receive a configuration for aggregating a set of CCs where the set of CCs includes at least one primary cell and one secondary cell. The code also includes code for communicating, based on the received configuration, with at least the primary cell for legacy communications, where legacy communications are based on a first TTI having a first duration, and code for communicating, based on the received configuration with at least one of the primary cell or secondary cell for ULL communications, wherein the ULL communications are based on a second TTI having a second duration that is less than the first duration.

[00011] For the realization of the above and related purposes, one or more aspects comprise the characteristics fully described below and particularly indicated in the claims. The following description and accompanying drawings set out in detail certain illustrative features of one or more aspects. These features are indicative, however, of just a few of the many ways in which the principles of various aspects can be employed, and this description is intended to include all of these aspects and their equivalents.

Brief description of the drawings

[00012] To facilitate a more complete understanding of aspects described herein, reference is now made to the attached drawings, in which similar elements are referenced with similar numerals. These drawings are not to be construed as limiting the present disclosure, but are intended to be illustrative only.

[00013] Figure 1 shows a block diagram conceptually illustrating an example of a telecommunications system, according to aspects described here.

[00014] Figure 2 is a diagram illustrating an example of an access network.

[00015] Figure 3 is a diagram illustrating an example of a developed Node B and user equipment in an access network.

[00016] Figure 4 is a diagram illustrating example timelines for uplink bandwidth allocation.

[00017] Fig. 5 is a diagram illustrating an example system for managing ultra-low latency (ULL) communications over a plurality of component (CC) carriers in accordance with aspects described herein.

[00018] Fig. 6 is a flowchart of an example method of communication using a ULL and/or a legacy communication technology via a plurality of CCs in accordance with aspects described herein.

[00019] Fig. 7 is a flowchart of an example method of configuring communications using a ULL and/or a legacy communication technology across a plurality of CCs in accordance with aspects described herein.

DETAILED DESCRIPTION

[00020] The detailed description set forth below with respect to the attached drawings is intended as a description of various configurations and does not present represent the only configurations in which the concepts described herein can be put into practice. The detailed description includes specific details for the purpose of providing a complete understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts can be put into practice without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[00021] Various aspects of telecommunication systems will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed description and illustrated in the attached drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design limitations imposed on the overall system.

[00022] As an example, an element, or any portion of an element or any combination of elements can be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other hardware. configured to perform the various functionalities described by this disclosure. One or more processors in the processing system can run software. Software will be interpreted broadly to mean instructions, sets of instructions, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

[00024] Various aspects related to the allocation of traffic data resources in wireless communications are described here. For example, an ultra-low latency (ULL) wireless technology can be defined as based on a shorter transmission time interval (TTI) than an existing legacy wireless technology. In a specific example, in long-term evolution (LTE) which is based on a TTI of 1 millisecond (ms) 1 subframe), LTE ULL can be defined as based on a TTI having a duration of less than one subframe (e.g., one symbol, two symbols, a subframe partition, etc.). In this regard, a lower latency in communication is achieved by the more frequent, shorter TTI. It is possible, in some configurations, that the UE could be configured to communicate over a first component carrier (CC) using legacy LTE and LTE ULL resources, while also configured to communicate over a second CC using legacy LTE resources. legacy and no LTE ULL features or LTE ULL feature and no legacy LTE features (eg in uplink and/or downlink communications). The UE can enable and disable LTE ULL over the second CC based on legacy LTE features, or vice versa (eg use LTE ULL features to enable/disable legacy LTE features). The UE can therefore determine a latency to enable/disable communications through the second CC based on whether legacy LTE or LTE ULL is enabled through the second CC. Furthermore, the LTE ULL communications via the second CC may correspond to carrying at least one of the uplink and/or downlink communications.

[00025] With reference first to figure 1, a diagram illustrates an example of a wireless communication system 100, in accordance with aspects described herein. The wireless communication system 100 includes a plurality of access points (e.g., base stations, eNBs, or WLAN access points) 105, a number of user equipment (UEs) 115, and a core network 130. access protocols 105 may include a scheduling component 302 configured to enable/disable one or more CCs or allocate resources for communication using ULL or legacy communications to one or more UEs 115, as further described herein. Similarly, one or more of the UEs 115 may include a communication component 361 configured to receive information related to the activation/deactivation of a CC and/or resources for communicating using ULL or legacy communications with the access points 105. access points 105 may communicate with UEs 115 under the control of a base station controller (not shown), which may form part of the core network 130 or certain access points 105 (e.g., base stations or eNBs) in various examples. Access points 105 may communicate control information and/or user data with core network 130 via back links 132. In examples, access points 105 may directly or indirectly communicate with each other via back links 134, which can be wired or wireless communication links. Wireless communication system 100 can support operation on multiple carriers (waveform signals of different frequencies). Multicarrier transmitters can transmit modulated signals simultaneously on multiple carriers. For example, each of the communication links 125 may be a multicarrier signal modulated in accordance with the various radio technologies described above. Each modulated signal can be sent on a different carrier and can carry control information (e.g., reference signals, control channels, etc.), overhead information, data, etc. For example, multiple carriers can be multiple cells (e.g., one primary cell and one or more secondary cells, or a set of primary cells with sets of one or more corresponding secondary cells, as described below).

[00026] In some examples, at least a portion of the wireless communication system 100 can be configured to operate in multiple hierarchical layers in which one or more of the UEs 115 and one or more of the access points 105 can be configured to support transmissions in a hierarchical layer that has a reduced latency relative to another hierarchical layer. In some examples, a hybrid UE 115-a can communicate with access point 105-a both in a hierarchical first layer that supports first layer transmissions using a first TTI (also referred to herein as "legacy communications") as a second layer hierarchical that supports second layer transmissions using a second TTI, which may be shorter than the first TTI (also referred to here as “ULL communications”).

[00027] In other examples, a second layer UE 115-b can communicate with the access point 105-b in the hierarchical second layer only. In this way, hybrid UEs 115-a second layer UE 115-b can belong to a second class of UEs 115 that can communicate in the hierarchical second layer, while legacy UEs 115 can belong to a first class of UEs 115 that can communicate in the hierarchical layer. first hierarchical layer only. Access point 105-b and UE 115-b can communicate in the second hierarchical layer through transmissions of subframes of the second subframe type. The access point 105-b can transmit communications related to the first or second hierarchical layer only or it can transmit communications to both the first and second hierarchical layers. Where an access point 105-b supports both the first and second hierarchical layers, the communication component 361 may be configured to prioritize communications received from the access point 105-b that pertain to the first and second hierarchical layers, such as described here.

[00028] Access points 105 can communicate wirelessly with UEs 115 through one or more access point antennas. Each of the access point locations 105 may provide communication coverage for a respective coverage area 110. In some examples, access points 105 may be mentioned as a base transceiver station, a radio base station, a radio transceiver , a basic service set (BSS), an extended service set (ESS), a NodeB, eNodeB, home NodeB, a home eNodeB, or some other suitable terminology. The coverage area 110 for a base station can be divided into sectors making up only a portion of the coverage area (not shown). The wireless communication system 100 may include access points 105 of different types (e.g. macro, micro and/or pico base stations). Access points 105 may also utilize different radio technologies, such as cellular and/or WLAN radio access technologies (RAT). Access points 105 may be associated with the same or different access networks or operator deployments. The coverage areas of different access points 105, including the coverage areas of the same or different types of access points 105, using the same or different radio technologies, and/or belonging to the same or different access networks, may overlap .

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

[00030] The core network 130 can communicate with the eNBs or other access points 105 via a return link 132 (eg, Sl interface, etc.). Access points 105 may also communicate with each other, for example, directly or indirectly via backlinks 134 (e.g. interface X2, etc.) and/or backlinks 132 (e.g. via core network 130 ). Wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, access points 105 can have similar frame timing, and transmissions from different access points 105 can be approximately time-aligned. For asynchronous operation, access points 105 may have different frame timing, and transmissions from different access points 105 may not be time-aligned. Furthermore, transmissions in the first hierarchical layer and second hierarchical layer may or may not be synchronized between access points 105. The techniques described here can be used for synchronous or asynchronous operations.

[00031] The UEs 115 are dispersed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile. A UE 115 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a telephone set, a user agent, a mobile client, a client or some other suitable terminology. A UE 115 can be a cell 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 watch or glasses, a wireless local loop station (WLL) or similar. A UE 115 may be able to communicate with macro eNodeBs, small cell eNodeBs, relays, and the like. A UE 115 may also be able to communicate across different access networks, such as cellular or other WWAN access networks, or WLAN access networks.

[00032] The communication links 125 shown in the wireless communication system 100 may include uplink transmissions (UL) from a UE 115 to an access point 105 and/or downlink transmissions (DL) from an access point access 105 to a UE 115. Downlink transmissions may also be called forward link transmissions while uplink transmissions may also be called reverse link transmissions. The communication links 125 can carry transmissions from each hierarchical layer which, in some examples, can be multiplexed into the communication links 125. The UEs 115 can be configured to collaboratively communicate with multiple access points 105 via, for example, Multiple Input Multiple Output (MIMO), Carrier Aggregation (CA), Coordinated Multipoint (CoMP), Multiple Connectivity, or other schemes. MIMO techniques use multiple antennas at access points 105 and/or multiple antennas at UEs 115 to transmit multiple streams of data.

[00033] For example, carrier aggregation can utilize two or more component carriers in a cell in equal or different service for data transmission. CoMP can include techniques for coordinating transmission and reception by a number of access points 105 to improve overall transmission quality for UEs 115 as well as increase spectrum and network utilization. In multiple connectivity, for example, UE 115 may be configured with at least one primary cell (PCell) configured to support uplink and downlink communications between UE 115 and an access point 105. It should be recognized that there may be one PCell for each of one or more communication links 125 between a SeW 115 and a given access point 105. In addition, each of the communication links 125 may have one or more secondary cells (SCell) that may support uplink and/or downlink communications as well. In some examples, PCell can be used to communicate at least one control channel, and SCell can be used to communicate one data channel. UE 115 may have multiple PCell links with multiple access points and/or multiple SCell links with multiple access points. In any case, in a multi-carrier configuration, UE 115 may establish CCs with each PCell and/or SCell.

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

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

[00036] Figure 2 is a diagram illustrating an example of an access network 200 in an LTE or ULL LTE network architecture. In this example, the access network 200 is divided into a number of cellular regions (cells) 202. One or more small cell eNBs 208 may be provided which may be of a lower power class and may have cellular regions 210 that overlap with one or more of the cells 202. The small cell eNBs 208 may be or may provide a femto cell (e.g., home eNB (HeNB)), pico cell, micro cell, or remote radio head (RRH). The macro eNBs 204 are individually assigned to a respective cell 202 and are configured to provide an access point to the core network 130 for all UEs 206 in cells 202. In one aspect, eNBs 204 (or small cell eNBs 208) may include programming component 302 configured to enable/disable one or more CCs or allocate resources for communication using ULL or legacy communications to one or more UEs 206, as further described herein. Similarly, one or more UEs 206 may include a communication component 361 configured to receive information related to activation/deactivation of a CC and/or resources for communicating using ULL or legacy communications with eNBs 204 and/or 208. centralized controller in this example of an access network 200, however a centralized controller can be used in alternative configurations. The eNBs 204 are responsible for all radio-related functions including radio bearer control, admission control, mobility control, scheduling, security, and connectivity with one or more components of the core network 130.

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

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

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

[00040] In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system that supports OFDM in DL. OFDM is a spread spectrum technique that modulates data across a number of subcarriers in an OFDM symbol. The subcarriers are separated into precise frequencies. The spacing provides "orthogonality" that allows a receiver to retrieve data from the subcarriers. In the time domain, a guard interval (eg, cyclic prefix) can be added to each OFDM symbol to combat OFDM inter-symbol interference. The UL can use SC-FDMA in the form of a spread-DFT OFDM signal to compensate for high peak to medium power ratio (PAPR).

[00041] Figure 3 is a block diagram of an eNB 310 in communication with a UE 350 in an access network. In DL, the upper layer packets from the core network are provided to a controller/processor 375. The controller/processor 375 implements the functionality of the L2 layer. In the DL, controller/processor 375 provides header compression, encryption, packet segmentation and reordering, multiplexing between transport and logical channels, and radio resource allocations to the UR 350 based on various priority metrics. Controller/processor 375 is also responsible for HARQ operations, retransmission of lost packets, and signaling to UE 350.

[00042] Transmission (TX) processor 316 implements various signal processing functions for L1 layer (i.e. physical layer). Signal processing functions include encoding and interleaving to facilitate forward error correction (FEC) at UE 350 and mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), keying Quadrature Phase Shift Keying (QPSK), M Phase Shift Keying (M-PSK), M Quadrature Amplitude Modulation (M-QAM)). The encoded and modulated symbols are then divided into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g. pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by UE 350. Each spatial stream is then provided to a different antenna 320 via a separate transmitter 318TX. Each 318TX transmitter modulates an RF carrier with a respective spatial stream for transmission. Furthermore, eNB 310 may include scheduling component 302 configured to enable/disable one or more CCs or allocate resources for communication using ULL or legacy communications to one or more UEs 350, as further described herein. Although programming component 302 is shown coupled to controller/processor 375, it should be recognized that programming component 302 may also be coupled to other processors (e.g., RX processor 370, TX processor 316, etc.) and/or implemented by one or more processors 316, 370, 375 to perform actions described herein.

[00043] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX retrieves modulated information about an RF carrier and provides the information to the receiving (RX) processor 356. The RX processor 356 implements various L1 layer signal processing functions. Processor RX 356 performs spatial processing on the information to retrieve any spatial streams destined for UE 350. If multiple spatial streams are destined for UE 350, they may be combined by processor RX 356 into a single stream of OFDM symbols. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The decisions soft are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 310 on the physical channel. The data and control signals are then provided to the 359 controller/processor.

[00044] The 359 controller/processor implements the L2 layer. The controller/processor may be associated with a memory 360 which stores program codes and data. Memory 360 can be referred to as a computer readable medium. In the UL, the 359 controller/processor provides demultiplexing between logical and transport channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packets are then provided to a data store 362, which represents all protocol layers above the L2 layer. Various control signals may also be provided to data warehouse 362 for L3 processing. The 359 controller/processor is also responsible for error detection using an acknowledgment (ACK) and/or negative acknowledgment (NACK) protocol to support HARQ operations. Furthermore, the UE 350 may include a communication component 361 configured to receive information related to the activation/deactivation of a CC and/or resources for communicating using ULL or legacy communications with the eNB 310. Although the communication component 361 is shown as coupled to controller/processor 359, it should be recognized that communication component 361 may also be coupled to other processors (e.g., RX processor 356, TX processor 368, etc.) and/or implemented by one or more processors 356, 359, 368 to perform actions described here.

[00045] In the UL, a data source 367 is used to deliver upper layer packets to the controller/processor 359. Data source 367 represents all protocol layers above the L2 layer. Similar to the functionality described with respect to DL transmission by the eNB 310, the controller/processor 359 implements the L2 layer for the user plane and the control plane by providing header compression, scrambling, packet segmentation and reordering, and cross-channel multiplexing. transport and logical based on radio resource allocations by the eNB 310. The controller/processor 359 is also responsible for HARQ operations, retransmission of lost packets, and signaling for the eNB 310.

[00046] Channel estimates derived by a channel estimator 358 from a reference or feedback signal transmitted by the eNB 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, and facilitate spatial processing. The spatial streams generated by the TX processor 368 are fed to different antenna 352 via separate transmitters 354TX. Each 354TX transmitter modulates an RF carrier with a respective spatial stream for transmission.

[00047] The UL transmission is processed in the eNB 310 in a similar manner to that described with respect to the receiver function in the UE 350. Each 318RX receiver receives a signal through its respective antenna 320. Each 318RX receiver retrieves modulated information about an RF carrier and provides information to an RX processor 370. Processor 370 may implement L1 layer.

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

[00049] Figure 4 is a diagram illustrating non-limiting examples of ULL timelines 400, 403, with time extending from left to right in the figure, for managing ULL communications in a wireless communication system. In this example, timelines 400, 402 include ULL frames of symbol duration in each symbol of a subframe. Timelines 400, 402 show both symbols representing a TTI for ULL physical downlink shared control channel (uPDCCH) and/or ULL physical downlink shared channel (uPDSCH) and symbols representing a TTI including ULL physical downlink shared control channel (Upucch) and/or ULL physical uplink shared channel (uPUSCH). In timelines 400, 14 symbols are shown in a given subframe (eg, for normal CP), and in timelines 402, 12 symbols are shown in a given subframe (eg, for extended CP). In any case, lower latency is achieved in ULL by using token-based TTIs. It should be recognized, in other examples, that a TTI can be two or more symbols, a partition of a subframe (where a subframe includes two partitions), etc. Also, the HARQ processing response time can be 3 symbols (or 4 symbols, 3 dual symbols, 3 partitions, etc.) In the example shown, uPDCCH/uPDSCH is sent on symbol 0, and HARQ is processed and is sent on symbol 0. symbol 4, etc. in the subframe.

[00050] With reference to figures 5-7, aspects are shown with reference to one or more components and one or more methods that can perform the actions or functions described here. In one aspect, the term "component" as used herein can be one of the parts that make up a system, it can be hardware or software or some combination thereof, and it can be broken down into other components. Although the operations described below in figures 6 and 7 are presented in a specific order and/or as being performed by an example component, it should be understood that the ordering of actions and the components that perform the actions may vary, depending on the implementation. Furthermore, it should be understood that the following actions or functions may be performed by a specially programmed processor, a processor running specially programmed software or computer readable media, or by any other combination of a hardware component and/or a software component capable of performing the actions or functions described.

[00051] Figure 5 illustrates an example system 500 for allocating resources for ULL and legacy wireless communication. The system 500 includes a UE 502 that communicates with an eNB 504 to access a wireless network, examples of which are described in figures 1-3 (e.g. access points 105, eNB 204, 208, eNB 310, UEs 115, 206 , 350, etc.) above. In one aspect, eNB 504 and UE 502 may communicate across a plurality of CCs 508, 509 (and/or additional CCs) using carrier aggregation. For each CC 508, 509, for example, eNB 504 and UE 502 may have established one or more downlink channels over which to communicate downlink signals, which may be transmitted by eNB 504 (for example, through transceiver 556) and received by UE 502 (e.g., via transceiver 605) to communicate control messages and/or data (e.g., in signaling) from eNB 504 to UE 502 via configured communication facilities. Furthermore, for example, eNB 504 and UE 502 may have established one or more uplink channels over which to communicate via uplink signals for each CC 508, 509, which may be transmitted by UE 502 (e.g., via transceiver 506) and received by eNB 504 (e.g., via transceiver 556) to communicate control messages and/or data (e.g., in signaling) from UE 502 to eNB 504 via configured communication facilities. In another example, UE 502 can communicate with eNB 504 through one CC 508 and another eNB (or another cell provided by eNB 504) through another CC 509, can communicate with both eNBs (or cells) through multiple CCs, etc., although not shown in this figure. Furthermore, for example, the UE 502 and/or eNB 504 may configure a CC 508 as a CC PCell and one or more other CCs 509 as a CC SCell in carrier aggregation and/or multiple connectivity. Furthermore, in one example, each CC 508 and/or 509 can be a set of CCs including a separate uplink CC and downlink CC.

[00052] In one aspect, the UE 502 may include one or more processors 503 and/or a memory 505 that may be communicatively coupled, for example, via one or more buses 507, and may operate in combination with or otherwise implementing a communication component 361 for receiving resource grants from the eNB 504 and communicating over the resources, which may be based on a ULL timeline (e.g., a timeline having a TTI that is less than a subframe in duration, such as timelines 400, 402 in Figure 4), a legacy timeline (e.g., a timeline with a subframe TTI of 1ms), etc. For example, the various operations relating to the communication component 361 may be implemented or otherwise performed by one or more processors 503 and, in one aspect, may be performed by a single processor, while in other aspects, operations other than operations may be performed by a combination of two or more different processors. For example, in one aspect, one or more processors 503 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or an application-specific integrated circuit (ASIC), or a transmit processor, receive processor, or a transceiver processor associated with transceiver 506. Also, for example, memory 505 may be non-transient computer-readable media that includes, but is not limited to, random access memory ( RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), a optical disk (e.g. compact disc (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g. card, stick, key drive), a registry, a removable disk, and any other suitable media for storing computer-readable software and/or code or instructions that can be accessed and read by a computer or one or more processors 503. Additionally, memory 505 or computer-readable storage media may be resident in a or more processors 503, external to one or more processors 503, distributed across multiple entities including one or more processors 503, etc.

[00053] In particular, one or more processors 503 and/or memory 505 can perform actions or operations defined by the communication component 361 or its subcomponents. For example, one or more processors 503 and/or memory 505 can perform actions or operations defined by a configuration receiving component 510 to obtain a configuration to communicate through a plurality of CCs with one or more cells (e.g., with a or more 504 eNBs) using carrier aggregation, multiple connectivity, etc. In one aspect, for example, configuration receiving component 510 may include hardware (e.g., one or more processor modules from one or more processors 503) and/or computer-readable code or instructions stored in memory 505 and executable by at least one of one or more processors 503 for performing the specially configured configuration receive operations described herein. Also, for example, one or more processors 503 and/or memory 505 can perform actions or operations defined by an optional communication enable/disable component 512 to enable and/or disable legacy and/or ULL communications with eNB 504. In one aspect, for example, the communication enable/disable component 512 may include hardware (e.g., one or more processor modules of one or more processors 503) and/or computer-readable code or instructions stored in memory 505 and executable by at least one of one or more processors 503 to perform the specially configured enable/disable operations described herein. Also, for example, one or more processors 503 and/or memory 505 can perform actions or operations defined by an optional latency determination component 514 to determine a latency to enable/disable communication. In one aspect, for example, the latency determination component 514 may include hardware (e.g., one or more processor modules from one or more processors 503) and/or computer-readable code or instructions stored in memory 505 and executable by at least one of one or more processors 503 for performing the specially configured latency determination operations described herein.

[00054] Similarly, in one aspect, the eNB 504 can include one or more processors 553 and/or a memory 555 that can be communicatively coupled, for example, via one or more buses 557, and can operate in combination with or from another way to implement a scheduling component 302 to generate the resource grants for UEs 502 and/or other UEs according to resources, which may be based on a ULL timeline (e.g., a timeline having a TTI that is less than a subframe in duration, like timelines 400, 402 in Figure 4), a legacy timeline (e.g., a timeline with a subframe TTI of 1ms), etc. For example, the various functions related to programming component 302 may be implemented or otherwise performed by one or more processors 553 and, in one aspect, may be performed by a single processor, while in other aspects, functions other than functions may be performed by a combination of two or more different processors, as described above. It should be recognized, in one example, that one or more processors 553 and/or memory 555 may be configured as described in examples above with respect to one or more processors 503 and/or memory 505 of UE 502.

[00055] In one example, one or more processors 553 and/or memory 555 can perform actions or operations defined by programming component 302 or its subcomponents. For example, one or more processors 553 and/or memory 555 may perform actions or operations defined by a configuration component 520 to configure legacy and/or ULL communications for UE 502 through at least one CC, where UE 502 may another mode can be configured across multiple CCs with eNB 504 or other eNBs/cells in carrier aggregation or multiple connectivity. In one aspect, for example, configuration component 520 may include hardware (e.g., one or more processor modules from one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable for at least one of one or more processors 553 to perform the specially configured communication setup operations described herein. Further, for example, one or more processors 553 and/or memory 555 can perform actions or operations defined by an optional communication enable/disable component 522 to enable/disable legacy and/or ULL communications with the UE 502 via at least one CC. In one aspect, for example, the communication enable/disable component 522 may include hardware (e.g., one or more processor modules of one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable by at least one of one or more processors 553 to perform the specially configured enable/disable operations described herein.

[00056] It should be recognized that transceivers 506, 556 can be configured to transmit and receive signals wirelessly through one or more antennas, an RF front end, one or more transmitters, and one or more receivers. In one aspect, transceivers 506, 556 can be tuned to operate on specified frequencies so that UE 502 and/or eNB 504 can communicate on a certain frequency. In one aspect, one or more processors 503 can configure transceiver 506 and/or one or more processors 553 can configure transceiver 556 to operate at a specified power level and frequency based on a configuration, a communication protocol, etc. , to communicate uplink signals and/or signal eNB 504 for downlink via related uplink or downlink communication channels through one or more CCs.

[00057] In one aspect, transceivers 506, 556 can operate in multiple bands (e.g., using a multiband-multimode modem, not shown) in order to process digital data sent and received using transceivers 506, 556. In one aspect, transceivers 506, 556 may be multiband and configured to support multiple frequency bands for a specific communication protocol. In one aspect, transceivers 506, 556 can be configured to support multiple operating networks and communication protocols. Thus, for example, transceivers 506, 556 can enable transmission and/or reception of signals based on a specified modem configuration.

[00058] Figure 6 illustrates an example method 600 for managing (eg, by a UE 502) legacy and/or ULL communications with one or more cells. In block 602, UE 502 may receive a configuration to aggregate a set of CCs. In such an aspect, the set of CCs may include at least one primary cell CC and one secondary cell CC. In one aspect, configuration receiving component 510 (FIG. 5), for example, in combination with processor(s) 503, memory 505, and/or transceiver 506, can receive configuration to aggregate a set of CCs. In such an aspect, the set of CCs may include at least one primary cell CC and one secondary cell CC. In one example, configuration receiving component 510 may receive configuration for the set of CCs from eNB 504 and/or may receive configuration for one or a subset of the set of CCs configured for UE 502 from eNB 504 . The configuration can specify a frequency band for the CCs, cell information assigned to the CCs, a communication technology for the CCs (for example, legacy and/or ULL), features over which to communicate using the CCs, and/or similar. In one example, configuration receiving component 510 may receive configuration from eNB 504, which may specify use of legacy communications and/or ULL through the CC where legacy communications and/or ULL may refer to a or more uplink or downlink communications through the CC. In one example, the configuration may refer to one CC PCell and one or more CCs SCell in carrier aggregation (e.g. with 504 eNB cells and/or other eNBs) and/or multiple connectivity (e.g. with multiple CCs PCell and corresponding SCell CC(s). In one example, the PCell CC may include a common search space through which UE 502 may search for resource grants in the PCell CC and/or one or more SCell CCs.

[00059] In block 604, UE 502 may communicate, based on the received configuration, with at least the primary cell for legacy communications. In one aspect, the communication component 361, for example, in combination with the processor(s) 503, memory 505, and/or transceiver 506, can communicate, based on the received configuration, with at least the primary cell for legacy communications. As described, legacy communications can be based on a first TTI of a first duration that is greater than a second duration of a second TTI upon which ULL communications are based. In one example, communication component 361 may communicate with eNB 504 over a primary cell CC (e.g., CC 508). As described, for example, the configuration can specify one or more parameters related to communication through the primary cell (For example, frequency band, cell information, communication technology, facilities for uplink/downlink control and/or data communications, etc.). Thus, the communication component 361 can use one or more parameters to communicate with the eNB 504 using the primary cell (e.g., through CC 508) using at least legacy communications (e.g., legacy LTE). In one example, UE 502 may receive the configuration via primary cell communications with eNB 504 (e.g., via CC 508).

[00060] In block 606, the UE 502 may communicate, based on the received configuration, with at least one of the primary cell or secondary cell for ULL communications. In one aspect, the communication component 361, for example, in combination with the processor(s) 503, memory 505, and/or transceiver 506, can communicate, based on the received configuration, with at least one of the cell primary or secondary cell for ULL communications. This may include communication with eNB 504 via a primary cell CC and secondary cell CC (e.g. CCs 508, 509 respectively), and/or may include communication with eNB 504 via a primary cell CC and another eNB not shown) that supplies one of the cells through a secondary cell DC. As described, for example, the configuration can specify one or more parameters relating to communication across primary and secondary cells (e.g., frequency band, cell information, communication technology, facilities for uplink/downlink control communications and/or data, etc.). Thereby the communication component 361 can use one or more parameters to communicate with the eNB 504 using the primary cell (e.g. via CC 508) and/or the secondary cell (e.g. via CC 509) using at least ULL communications (eg LTE ULL). For example, LTE ULL communications can be based on a TTI that has durations of 1 symbol, 2 symbols, 1 partition, etc., where legacy LTE can be based on a TTI that has durations of 1 subframe. Accordingly, communication component 361 can separately manage legacy and/or ULL communications across a plurality of CCs.

[00061] In one example, the communication component 361 can communicate via the primary cell (and/or a second primary cell carrying PUCCH/uPUCCH, referred to here as a pScell), using legacy LTE and ULL (which may include monitoring in regarding communications through the primary cell CC 508 using legacy LTE and ULL) while communicating with the secondary cell using at least LTE ULL (which may include monitoring regarding communication through the secondary cell CC 509 using at least LTE ULL) . In another example, the communication component 361 may communicate through the secondary cell using legacy LTE (which may include monitoring against communication through the secondary cell CC 509 using at least legacy LTE). Thus, for example, the communication component 361 can communicate with a PCell and an SCell (e.g., of eNB 504 and/or one or more other eNBs) or related CC PCell or CC SCell, based on one or more of the following communication type settings: (1) PCell using a legacy technology and SCell using a ULL (and legacy) technology; (2) PCell using a legacy technology and SCell using a ULL (and legacy) technology, or (3) PCell using a ULL (and legacy) technology and SCell using a ULL (and legacy) technology. additional configurations are possible for more than 2 CCs and/or in multiple connectivity. In one example, although the communication component 361 can monitor, based on the received configuration, legacy LTE through SCell for communication, the SCell can provide ULL communications to other UEs through other CCs. Similarly, although the communication component 361 can monitor, based on the received configuration, LTE ULL through SCell for communications, SCell can provide legacy communications to other UEs through other CCs.

[00062] In addition, the communication type configuration can be based in part on subframe configurations across the CCs (for example, since different CCs can have different uplink/downlink subframe configurations/or different frame structures such as FDD or TDD). Furthermore, in one example, the communication component 361 may communicate with the PCell and/or SCell using a legacy technology in an uplink portion of a CC 508, 509 and a ULL (and legacy) technology in a downlink portion of the CC 508, 509 and/or vice versa.

[00063] In one example, at block 608, UE 502 may optionally receive an enable command to enable legacy communications with the primary cell or secondary cell and/or a disable command to disable ULL communications with the primary or secondary cell. the secondary cell. In one aspect, the communication enable/disable component 512, for example, in combination with processor(s) 503, memory 505, and/or transceiver 506, may receive the enable command to enable legacy communications with the primary cell or the secondary cell and/or a disable command to disable ULL communications with the primary cell or the secondary cell (e.g., from eNB 504, as further described herein). For example, the communication component 361 may receive the activation command and/or the deactivation command on legacy resources and/or ULL through the primary cell (e.g. primary cell CC 508), secondary cell (e.g. Secondary Cell CC 509) and/or other CCs. In one example, communication enable/disable component 512 may request legacy and/or ULL communications enable/disable in the secondary cell from eNB 504. Communication enable/disable component 512 may therefore enable legacy communications and/or disable ULL communications through the 509 secondary cell CC (eg, through a corresponding uplink and/or downlink CC). This may include refraining from monitoring of ULL communications (e.g., in the TTI of ULL communications) through secondary cell CC 509, refraining from transmitting ULL communications through secondary cell CC 509, etc. In this regard, latency to establish legacy communications using ULL communications over the CC can be less than establishing the CC entirely in the secondary cell.

[00064] Furthermore, in an example, where ULL communications are disabled, the communication enable/disable component 512 may receive a command to enable ULL communications through secondary cell CC 509 from eNB 504 or another related eNB to the 509 secondary cell CC (and/or a command to disable legacy communication in the secondary cell). Communication enable/disable component 512 may therefore enable ULL communications and/or disable legacy communications at secondary cell CC 509 based on the command(s). In this regard, latency to establish ULL communications using legacy communications over the CC can be less than establishing the CC entirely in the secondary cell. Furthermore, the on/off commands in any case may apply to downlink communications (e.g. via a downlink CC portion of secondary cell CC 509), uplink communications (e.g. via a CC portion secondary cell DC uplink 509), both, etc.

[00065] As described, for example, ULL or legacy communications can be enabled and/or disabled for one of the downlink or uplink communications, or for both downlink and uplink communications in the secondary cell. When ULL or legacy communications are enabled and/or disabled for downlink or uplink, legacy or ULL configuration can also be subframe dependent (e.g., legacy-only communications enabled in some subframes while legacy and ULL are enabled in other subframes depending on whether subframes are configured for downlink and/or uplink communications).

[00066] In block 610, the UE 502 can optionally determine a latency to enable legacy communications with the primary cell or the secondary cell (e.g., through the corresponding CC 509) or disable the ULL communications with the primary cell or the secondary cell. secondary cell. In one aspect, the latency determining component 514, for example, in combination with the processor(s) 503 and/or memory 505, can determine the latency to enable legacy communications with the primary cell or the secondary cell or disable ULL communications with either the primary cell or the secondary cell. For example, where UE 502 is not communicating with the secondary cell, the latency determination component 514 may determine a longer latency to activate legacy communications than where UE 502 is communicating with the secondary cell before activating legacy communication. In another example, where the UR 502 is not communicating with the secondary cell after disabling ULL communications, the latency determination component 514 may determine a longer latency to disable legacy communications than where the UE 502 continues to communicate with the secondary cell (for example, using legacy communications) after disabling ULL communications. It should be recognized that latencies can be similarly determined for reactivating ULL communications and/or deactivating legacy communications.

[00067] In yet another example, the latency determination component 514 may determine the latency to enable or disable legacy or ULL communications in the secondary cell (e.g., via the corresponding CC 509) based on whether the enable or disablement is for legacy communications (eg based on the first TTI) or communications and ULL (eg based on the second TTI). For example, where the enable/disable command is for ULL communications, the latency determination component 514 may determine a shorter latency than when the enable/disable command is for legacy communications. In another example, the latency determination component 514 can determine the latency based on whether the UE 502 communicates with the secondary cell using at least one TTI before and after activation and/or deactivation. In any case, the communication component 361 may utilize latency in determining when (e.g., at what TTI) to communicate (e.g., transmit and/or receive) via enabled features and/or refrain from communicating via disabled features. .

[00068] Fig. 7 illustrates an example method 700 for communicating (e.g., by an eNB 504) with a UE using legacy communications and/or ULL. At block 702, the eNB can configure a UE to communicate via at least one CC out of a plurality of CCs configured for the UE. In one aspect, configuration component 520 (FIG. 5) for example, in combination with processor(s) 553, memory 555 and/or transceiver 556, can configure UE 502 to communicate over at least one CC of a plurality of CCs configured for UE 502. For example, configuration component 520 may specify information to communicate with a primary cell via CC 508 and/or with a secondary cell (e.g., associated with eNB 504 or another eNB ) via CC 509 in carrier aggregation and/or in multiple connectivity. As described, for example, the information may include frequency band, cell information, communication technology, facilities for control communications and/or uplink/downlink data, or other parameters.

[00069] In block 704, the eNB 504 can communicate with the UE through at least one CC using ULL communications. In one aspect, the programming component 302, for example, in combination with the processor(s) 553, memory 555, and/or transceiver 556, can communicate with the UE 502 via at least one CC 508 and/or or 509 using ULL communications as described above (eg based on a ULL timeline). This may be based at least in part on the configuration sent to UE 502.

[00070] In block 706, the eNB 504 can activate legacy communications with the UE through at least one CCC. In one aspect, the communication enable/disable component 522, for example, in combination with the processor(s) 553, memory 555, and/or transceiver 556, can enable legacy communications with the UE 502 via at least one CC 508, 509. For example, on enabling legacy communications in block 706, the eNB 504 may optionally, in block 708, send a command to the UE to enable legacy communications. In one aspect, the communication enable/disable component 522, in combination with the processor(s) 553, memory 555 and/or transceiver 556, can send the command to the UE 502 to enable legacy communications. For example, enable/disable communication component 522 may transmit the command to UE 502 using ULL communications therewith (e.g., via CC 508 and/or 509).

[00071] In block 710, the eNB 504 may optionally disable ULL communications with the UE through at least one CC based on legacy communications enablement. In one aspect, the communication enable/disable component 522, for example, in combination with processor(s) 553, memory 555, and/or transceiver 556, can disable ULL communications with UE 502 via at least one CC 508, 509 based on enabling legacy communications. For example, on disabling ULL communications in block 710, the eNB 504 may optionally, in block 712, send a command to the UE to disable ULL communications. In one aspect, the communication enable/disable component 522, for example, in combination with the processor(s) 553, memory 555, and/or transceiver 556, can transmit the command to the UE 502 using communications ULL or legacy (for example, through CC 508 and/or 509). It should be recognized that eNB 504 can maintain ULL communications with other UEs by disabling ULL communications with UE 502.

[00072] Furthermore, the communication enable/disable component 522 may similarly enable ULL and/or disable legacy communications in the secondary cell for UR 502 as well, which may include sending related commands to UE 502. In any case, in an example, communication enable/disable component 522 may determine to enable/disable ULL and/or legacy communications based on a request from UE 502, based on a buffer status report from UE 502, etc. For example, where eNB 504 receives a buffer status report from UE 502 indicating a buffer status below a threshold capacity where ULL communications are active, communication enable/disable component 522 may disable ULL communications and/or enable legacy communications through secondary cell CC 509 to UE 502 (for example, and/or may disable secondary cell CC 509 entirely). Similarly, for example, where the eNB 504 receives a buffer status report from the UE 502 indicating that a buffer status gets a threshold capability where legacy communications are active, the communication enable/disable component 522 may enable communications ULL and/or disable legacy communications via secondary cell CC 509 to UE 502. Further, in one example, communication enable/disable component 522 may enable/disable legacy and/or ULL communications based on a type of traffic to be communicated through the secondary cell CC 509 (eg, enable ULL communications for media traffic, enable legacy communications for traffic having lower bandwidth requirements, etc.).

[00073] Therefore, the eNB 504 can configure ULL and/or legacy communications over a given CC 508, 509 with UR 502 in carrier aggregation. It should be recognized that one CC (eg primary cell CC 508) may utilize ULL and legacy communications while another CC (eg secondary cell CC 509) may utilize ULL or legacy communications. The eNB 504 can therefore enable and/or disable ULL or legacy communications as described herein. It should also be recognized that a CC can be configured ULL only for one direction (eg ULL downlink) while relying on a different DD for ULL of a different direction (eg ULL uplink). For example, a CC that a UE monitors for a common search space, e.g., the primary cell CC 508, a second primary CC (pScell) that can carry control channels, etc., can be limited so that ULL must be configured for both links (downlink and uplink) if configured. It should also be recognized that the primary cell CC configured for legacy communication can be limited to the same as the primary cell CC for ULL communication. Alternatively, the primary cell CC for legacy communication and the primary cell CC for ULL communication can be separately managed and configured, as described here. As an example, a UE can be configured with 3 CCs: CC1, CC2 and CC3. CC1 can be configured as the primary cell CC for legacy communication, while CC2 can be configured as the primary cell CC for ULL communication. CC3 can be configured as a secondary cell DC. Thus, in an example as described here, the communication enable/disable component 512 may receive instructions over CC1 to enable/disable ULL communications over CC2, and/or vice versa. In any case, as described, one or more eNBs may provide the configuration for the UE (eg, as described with respect to block 602 and/or 702 above).

[00074] In addition, cross-carrier programming can be enabled for ULL communication. That is, a ULL control channel can be transmitted across one CC (e.g. primary cell CC 508 through eNB 504) to schedule ULL communication (downlink or uplink) on a different CC (e.g. cell CC secondary 509). It is also possible that ULL communication (downlink or uplink) can be programmed to a CC over a control channel associated with legacy communication on the CC or another CC (for example, by eNB 504). Similarly, it is also possible that a legacy communication (downlink or uplink) can be programmed by a control channel associated with the ULL communication.

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

[00076] The foregoing description is provided to enable anyone skilled in the art to put into practice the various aspects described herein. Various modifications in these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown here, but the full scope compatible with the language claims must be agreed, where reference to a singular element is not intended to mean "one and only one" unless specifically so. mentioned, but instead “one or more”. Unless specifically mentioned otherwise, the term “some” refers to one or more. All structural and functional equivalents for elements of the various aspects described herein that are known or hereafter become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly cited in the claims. No claim element should be construed as a means plus function unless the element is expressly mentioned using the phrase “means to.”

Claims (11)

1. Method (600) of managing ultra-low latency, ULL, communications over a plurality of component carriers, CC, the method comprising: receiving (602) an arrangement for aggregating a set of CCs, wherein the set of CCs includes at least one primary cell and one secondary cell; communicating (604) based on the received configuration, with at least the primary cell for legacy communications, wherein the legacy communications are based on a first transmission time slot, TTI, having a first duration; and communicating (606), based on the received configuration, with at least one of the primary cell and secondary cell for ULL communications, wherein the ULL communications are based on a second TTI having a second duration that is less than the first duration, characterized in that the method is specifically adapted to receive (608) a disable command to disable ULL communications with the at least one of the primary cell or the secondary cell; and receiving (608) an activation command to activate legacy communications with the secondary cell, along with disabling ULL communications with the secondary cell. 2. Method according to claim 1, characterized in that it further comprises: communicating, based on the received configuration, with the secondary cell for legacy communications. 3. Method according to claim 1, characterized in that receiving further comprises: receiving an activation command for the primary cell to activate legacy communications with the primary cell. 4. Method according to claim 1, characterized in that it further comprises determining a latency to enable or disable ULL or legacy communications with at least one of the primary cell or secondary cell, where the latency is a function of at least least one of: whether activation or deactivation is for communications based on the first TTI or second TTI, or whether the UE communicates with a cell using at least one TTI before and after activation or deactivation. 5. Method according to claim 4, characterized in that determining the latency comprises at least one of: determining a first latency when the UE is not communicating with the cell using legacy communications or ULL communications prior to activation , or determine a second latency when the UE is communicating with the cell using either legacy communications or ULL communications before activation, where the second latency is less than the first latency. 6. Method according to claim 4, characterized in that determining the latency comprises at least one of: determining a first latency when the UE is not communicating with the cell using legacy communications or ULL communications after deactivation ; or determining a second latency when the UE is communicating with the cell using legacy intercom communications or post-disable ULL communications, where the second latency is less than the first latency. 7. Method according to claim 1, characterized in that communicating with the at least one of the primary cell or the secondary cell for ULL communications comprises communicating with the at least one of the primary cell or the secondary cell using the ULL communications for downlink communications and uplink communications. 8. Method according to claim 1, characterized in that communicating with the at least one of the primary cell or secondary cell for ULL communications comprises communicating with the at least one of the primary cell or secondary cell using communications ULL for downlink communication or uplink communication. 9. Method according to claim 1, characterized in that the second TTI comprises at least one of a symbol, two symbols or a partition. 10. Apparatus (500) for managing ultra-low latency, ULL, communications over a plurality of component carriers, CC, the apparatus comprising: means for receiving a setup for aggregating a set of CCs, wherein the set of CCs includes at least one primary cell and one secondary cell; means for communicating, based on the received configuration, with at least the primary cell for legacy communications, wherein the legacy communications are based on a first transmission time slot, TTI, having a first duration; and means for communicating, based on the received configuration, with at least one of the primary cell and secondary cell for ULL communications, wherein the ULL communications are based on a second TTI having a second duration that is less than the first duration, characterized by the fact further comprising: means specifically adapted to receive (608) a disable command to disable ULL communications with the at least one of the primary cell or the secondary cell; and means specifically adapted to receive (608) an activation command to activate legacy communications with the secondary cell, along with deactivating ULL communications with the secondary cell. 11. Computer-readable memory (360), characterized in that it comprises computer-executable code that, when executed by a computer, causes the computer to perform the method as defined in any one of claims 1 to 9.