Skip to main content

LTE-Advanced

LTE-Advanced should be real broadband wireless networks that provide equal or greater peak data rates than those for wired networks, i.e., FTTH (Fiber To The Home), while maintaining equivalent QoS. Smooth introduction of LTE-Advanced should be possible on top of LTE system.

High-level requirements
•Reduced network cost (cost per bit)
•Better service provisioning
•Compatibility with 3GPP systems

Spectrum


WRC 07 identified the following new bands for use by IMT/IMT-Advanced:

450−470 MHz band,
698−862 MHz band,
790−862 MHz band,
2.3−2.4 GHz band, and
3.4−3.6 GHz band.

Not all of these bands are available on a worldwide basis. These bands are in addition to the bands currently specified in 3GPP. Specification for C-band should not be restricted to 3.4 – 3.6 GHz, but cover 3.4 to 3.8 and even 3.4 to 4.2 GHz as these will likely become available in some countries.

Channel Bandwidth

Channel bandwidths up to 100 MHz to be specified
However, for many operators consecutive allocation of 100 MHz unlikely
optimised performance needed for smaller bandwidths of e.g. 50 MHz low cost/complexity (i.e. not fully flexible) resource aggregation to be considered

Interworking with legacy 3GPP RAT

Full low complexity (for NW and terminal) interworking with 3GPP RAT, so operator de facto has flexibility on technology to deploy, when and where. The networks of most operators will be a combination of multiple 3GPP RAT for many years to come.
Network Sharing: Support for at least all currently specified Network Sharing features, also to facilitate cost-efficient roll out of LTE-Advanced, including, but not limited to, rural area coverage.

Working Methods

As LTE-Advanced should be an evolution of LTE, it is essential that it is specified as part of the 36-series of specifications.
It is also essential work is performed to a large degree by the experts that developed LTE, and thus work ideally should be performed in existing Working Groups.
LTE-Advanced will likely constitute the next significant development step for LTE, but (smaller) stand-alone enhancements and additions to LTE should be possible, and progressed in parallel.
Some of these smaller enhancements, as well as the “corrections” to LTE Release 8 could/should be captured in Rel.9, where SAE considerations will lead to relatively short Release completion time-frame.

Popular posts from this blog

Test New ALFA-AWUS036H v.2 (1.000mW) VS ALFA-AWUS036H v.1 (500mW)

- Recently emerged the New ALFA-AWUS036H v.2 (1.000mW), and these are the tests. TEST WITH NETSTUMBLER 1) usb da 100mW chipset railink 2) usb da 200mW chipset railink rt73 3) intel 2200 b/g con connettore esterno rp-sma 4) Alfa-AWUS036H 500mW 5) New Alfa-AWUS036H V2 da 1.000mW

ALFA-­AWUS036H & ALFA-­AWUS050NH INSTALLING/UPDATING DRIVERS RTL8187, r8187, RT2800usb on UBUNTU

NOTE: For surfing Internet with ALFA-AWUS050NH on Ubuntu Jaunty with rt2870sta driver, you must use the Kernel "2.6.28-11-generic #42-Ubuntu", without change or updates the drivers modules. NOTE: The tutorial is not related to Ubuntu karmic. Driver RTL8187/Stacks-­mac80211 (ref. ALFA-­AWUS036h) ­- These drivers, for surfing Internet, are more stable than r8187, and fully compatible with Network-Manager 0.7 installed by default on Ubuntu 9.04. Network-Manager 0.7 installed by default on Ubuntu 9.04. ­- Supports all encryption without problems. (OPEN, WEP and WPA/WPA2) ­- With Compat-Wireless, the "injection" working, but for support “Fragmentation attack” (opt. -5) you need to install one patch. - The RX sensitivity and packets injection is less, related to drivers r8187. Driver r8187/Stacks-ieee80211 (ref. ALFA-AWUS036h) - This driver is recommended for use with the Suite of Aircrack-ng, but not particularly suitable for Internet connections, as less stable and disc...

Packetforge-ng

The purpose of packetforge-ng is to create encrypted packets that can subsequently be used for injection. You may create various types of packets such as arp requests, UDP, ICMP and custom packets. The most common use is to create ARP requests for subsequent injection. To create an encrypted packet, you must have a PRGA (pseudo random genration algorithm) file. This is used to encrypt the packet you create. This is typically obtained from aireplay-ng chopchop or fragmentation attacks.