Sie sind auf Seite 1von 62

LTE Overview

Course Objectives:
Understand the development of mobile communications, and Long Term Evolution (LTE) position and network architecture. Understand the protocol architecture and basic technologies of EUTRAN. Understand key LTE technologies.

Contents

1 Overview.......................................................................................................................................................1 1.1 Background............................................................................................................................................1 1.1.1 1.1.2 Mobile Communications Evolution........................................................................................1 Comparison Among WCDMA, TD-SCDMA, and CDMA2000...........................................2

1.1.3 WCDMA Evolution...............................................................................................................2 1.1.4 TD-SCDMA Evolution..........................................................................................................3 1.1.5 1.2 CDMA200 Evolution.............................................................................................................4

LTE Overview and Standards Development..........................................................................................5

2 LTE Indexes and Requirements..................................................................................................................5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 Frequency Band Division......................................................................................................................6 Peak Data Rate......................................................................................................................................6 Control Plane Delay..............................................................................................................................7 User Plane Delay...................................................................................................................................7 User Throughput....................................................................................................................................7 Spectrum Efficiency...............................................................................................................................8 Mobility.................................................................................................................................................8 Coverage................................................................................................................................................9 Spectrum Flexibility..............................................................................................................................9 Coexistence and Interoperability with Existing 3GPP Systems..........................................................9 Reducing CAPEX and OPEX...........................................................................................................10

3 LTE Architecture........................................................................................................................................11 3.1 System Architecture.............................................................................................................................11

3.2

Radio Protocol Architecture................................................................................................................15 3.2.1 3.2.2 Control Plane Protocol Architecture....................................................................................15 User Plane Protocol Architecture.........................................................................................16

3.3

S1 Interface and X2 Interface..............................................................................................................16 3.3.1 3.3.2 S1 Interface..........................................................................................................................17 X2 Interface.........................................................................................................................21

4 Physical Layer............................................................................................................................................21 4.1 4.2 4.3 Frame Structure...................................................................................................................................21 Physical Resources..............................................................................................................................21 Physical Channels................................................................................................................................23

4.4 Transport Channels..............................................................................................................................25 4.5 4.6 4.7 4.8 Mapping Between Transport Channels and Physical Channels...........................................................27 Physical Signals...................................................................................................................................27 Physical Layer Model..........................................................................................................................28 Physical Layer Procedures..................................................................................................................31 4.8.1 4.8.2 4.8.3 Synchronization Procedures.................................................................................................31 Power Control......................................................................................................................31 Random Access Procedures.................................................................................................32

5 Layer 2........................................................................................................................................................32 5.1 MAC Sublayer.....................................................................................................................................33 5.1.1 5.1.2 5.1.3 5.2 MAC Functions....................................................................................................................33 Logical Channels.................................................................................................................34 Mapping Between Logical Channels and Transport Channels.............................................35

RLC Sublayer......................................................................................................................................36 5.2.1 5.2.2 RLC Functions.....................................................................................................................36 PDU Structure......................................................................................................................37

5.3

PDCP Sublayer....................................................................................................................................37 5.3.1 5.3.2 PDCP Functions...................................................................................................................37 PDU Structure......................................................................................................................38

6 RRC.............................................................................................................................................................38 6.1 6.2 6.3 6.4 RRC Functions....................................................................................................................................38 RRC State............................................................................................................................................39 NAS State and the Relationship With the RRC state..........................................................................40 RRC Procedure....................................................................................................................................41 6.4.1 6.4.2 System Information..............................................................................................................41 Connection Control..............................................................................................................42

7 Core LTE Technologies..............................................................................................................................43 7.1 7.2 7.3 7.4 7.5 Duplex Mode.......................................................................................................................................43 Multi-access Mode..............................................................................................................................43 Multi-antenna Technologies.................................................................................................................44 Link Adaptation...................................................................................................................................45 HARQ and ARQ.................................................................................................................................45 7.5.1 HARQ..................................................................................................................................45

7.5.2 ARQ.....................................................................................................................................46 7.5.3 HARQ/ARQ Interactions.....................................................................................................47

8 Abbreviations .............................................................................................................................................48 9 References ..................................................................................................................................................50

1 Overview

Knowledge points Mobile communications development WCDMA evolution TD-SCDMA evolution CDMA2000 evolution

1.1 Background
1.1.1 Mobile Communications Evolution
The development history from 2G and 3G to 3.9 G is the development history from lowspeed voice services to high-speed multimedia services of mobile communications. 3GPP has been progressively perfecting LTE R8 standard: 1. 2. 3. LTE R8 RAN1 was frozen in December 2008. LTE R8 RAN2, RAN3, and RAN4 were frozen in December 2008.. LTE R8 standard was complete by March 2009, implementing basic LTE functions at the first commercial use of LTE systems. Figure 1 shows the development and evolution of wireless communication technologies.

Development and evolution of wireless communication technologies

1.1.2 Comparison Among WCDMA, TD-SCDMA, and CDMA2000

Comparison among WCDMA, TD-SCDMA, and CDMA2000 Standard Inheritance basis Synchronous mode Chip rate System bandwidth Core network Voice coding mode WCDMA GSM Asynchronous 3.84 Mcps 5 MHz GSM MAP AMR CDMA2000 Narrowband CDMA Synchronous 1.2288 Mcps 1.25 MHz ANSI-41 QCELP, EVRC, and VMR-WB TD-SCDMA GSM Synchronous 1.28 Mcps 1.6 MHz GSM MAP AMR

1.1.3 WCDMA Evolution


Figure 2 shows the WCDMA technology roadmap.

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

WCDMA technology roadmap

1.1.4 TD-SCDMA Evolution


ZTE wireless network equipment supports smooth evolution of recent TD evolution software. TD evolution can be divided into two stages: standard stage of CDMA technologies and that of OFDMA technologies. The standard stage of CDMA technologies can smoothly evolve to HSPA+ with spectrum efficiency close to that of LTE.

LTE Overview

Long-term evolution version (4G) Mid-term evolution version Short-term evolution version Basic version

IMT-Adv

3GPP (R4)
Voice/Data N frequency point

3GPP (R5/6/7) HSPA/HSPA+ MBMS/Multi-Carrier

3GPP LTE OFDMA MIMO

Phase I

Phase II

Phase III

CDMA standard

OFDMA standard

TD-SCDMA evolution

1.1.5 CDMA200 Evolution


CDMA One is a collection of all IS-95-based CDMA products. More specifically, IS-95 is used as a standard for key technologies of all CDMA One-based products. When CDMA2000 1x employs 1.25 MHz bandwidth, the highest rate of single-carriers reaches 307.2 kbit/s, the peak rate of 1xEV-DO Rev.0 reaches 2.4 Mbit/s in the downlink, and the peak rate of Rev.A reaches 3.1 Mbit/s in the downlink.

CDMA200 evolution

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

1.2 LTE Overview and Standards Development


3GPP working groups started LTE standardization in December 2004. LTE focuses on the enhancement of UTRAN and UTRA. The establishment of 3GPP standards can be divided into four stages including requirements proposal, architecture establishment, detailed specifications, and testing and verification. 3GPP works in workgroup mode and RAN1/2/3/4/5 workgroups are directly related to LTE.

LTE Overview

Organization and establishment stages of 3GPP standards

2 LTE Indexes and Requirements

Knowledge points Spectrum division LTE system requirements Others Physical channels and mapping relationship Figure 6 shows the LTE indexes and requirements prescribed by 3GPP.

LTE indexes and requirements

2.1 Frequency Band Division


Table 2 lists the E-UTRA frequency bands.

E-UTRA frequency bands E-UTRA Operating Band FUL_low FUL_high 1 2 3 4 5 6 7 8 9 10 11 12 13 14 17 ... 33 34 35 36 37 38 39 40 1900 MHz 2010 MHz 1850 MHz 1930 MHz 1910 MHz 2570 MHz 1880 MHz 2300 MHz 1920 MHz 2025 MHz 1910 MHz 1990 MHz 1930 MHz 2620 MHz 1920 MHz 2400 MHz 1900 MHz 2010 MHz 1850 MHz 1930 MHz 1910 MHz 2570 MHz 1880 MHz 2300 MHz 1920 MHz 2025 MHz 1910 MHz 1990 MHz 1930 MHz 2620 MHz 1920 MHz 2400 MHz TDD TDD TDD TDD TDD TDD TDD TDD 704 MHz 716 MHz 734 MHz 746 MHz FDD 1920 MHz 1850 MHz 1710 MHz 1710 MHz 824 MHz 830 MHz 2500 MHz 880 MHz 1749.9 MHz 1710 MHz 1427.9 MHz 698 MHz 777 MHz 788 MHz 1980 MHz 1910 MHz 1785 MHz 1755 MHz 849 MHz 840 MHz 2570 MHz 915 MHz 1784.9 MHz 1770 MHz 1452.9 MHz 716 MHz 787 MHz 798 MHz FDL_low FDL_high 2110 MHz 1930 MHz 1805 MHz 2110 MHz 869 MHz 875 MHz 2620 MHz 925 MHz 1844.9 MHz 2110 MHz 1475.9 MHz 728 MHz 746 MHz 758 MHz 2170 MHz 1990 MHz 1880 MHz 2155 MHz 894MHz 885 MHz 2690 MHz 960 MHz 1879.9 MHz 2170 MHz 1500.9 MHz 746 MHz 756 MHz 768 MHz FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD FDD Uplink (UL) operating band BS receive UE transmit Downlink (DL) operating band BS transmit UE receive Duplex Mode

2.2 Peak Data Rate


The instantaneous downlink peak rate reaches 100 Mbit/s (5 bit/s/Hz) at 20 MHz
6

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

downlink spectrum band (two transmit antennas on the network side and two receive antennas on the UE side). The instantaneous uplink peak rate reaches 50 Mbit/s (2.5 bit/s/Hz) at 20 MHz uplink spectrum band (one receive antenna on the UE side). Widebands, MIMOs, and advanced modulation technologies are the key to increasing peak data rates.

2.3 Control Plane Delay


From residence to activation, similarly, from the idle mode to CELL_DCH state of Release 6, the transmission delay time of the control plane is shorter than 100 ms and does not include paging delay time or NAS delay time. From sleep to activation, similarly, from the CELL_PCH state to CELL_DCH state of Release 6, the transmission delay time of the control plane is shorter than 50 ms and does not include the DRX interval. Additionally, if the control plane operates at 5 MHz spectrum band, each cell is expected to support 200 activated users. In the case of higher spectrum bands, each cell is expected to support 400 activated users.

2.4 User Plane Delay


User plane delay is the unidirectional transmission time that a packet is transmitted from the IP layer of a UE/RAN edge node to the IP layer of a RAN edge node/UE. The RAN edge node indicates the interface nodes of the RAN and core network. In the case of "zero loads" (a single user and a single data flow) and "small IP packets" (only one IP header and no effective load), the user plane delay is expected to be no longer than 5 ms.

2.5 User Throughput


Downlink:
7

LTE Overview

1.

The user throughput per MHz at the 5% Cumulative Distribution Function (CDF) must reach two to three times the throughput of R6 HSDPA.

2.

The average user throughput per MHz must reach three to four times the throughput of R6 HSDPA.

R6 HSDPA uses one transmitter one receiver (1T1R) while LTE uses two transmitter/two receiver (2T2R). Uplink: 1. The user throughput per MHz at the 5% CDF must reach two to three times the throughput of R6 HSUPA. 2. The user throughput per MHz must reach two to three times the throughput of R6 HSUPA. R6 HSUPA uses 1T2R, and so does LTE.

2.6 Spectrum Efficiency


Downlink: On a network with effective load, the target LTE spectrum efficiency (measured by the bit quantity per site, per Hz, and per second) is three to four times more efficient than R6 HSUPA. R6 HSDPA uses 1T1R while LTE uses 2T2R. Uplink: On a network with effective load, the target LTE spectrum efficiency (measured by the bit quantity per site, per Hz, and per second) is two to three times more efficient than R6 HSUPA. R6 HSUPA uses 1T2R, and so does LTE.

2.7 Mobility
E-UTRAN can provide optimum network performance for mobile users at the speed of 015 km/h, high performance services at the speed of 15 120 km/h, and cell network services at the speed of 120350 km/h (the speed even reaches 500 km/h at specified bands). Voice services and other realtime services provided in the R6 CS domain are supported by PS domain on the E-UTRAN and all these services can reach or exceed the quality of UTRAN services. The interrupt time caused by handovers within the E-UTRA system
8

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

must be shorter than or equal to the handover time of the GERAN CS domain. In a special case where the moving speed exceeds 250 km/h (in a high-speed train), the physical layer parameters of E-UTRAN must be set to be capable of protecting the connections between users and networks at the highest speed of 350 km/h (the speed even reaches 500 km/h at specified bands).

2.8 Coverage
The E-UTRA system must flexibly support all coverage scenarios on the basis of reusing the current UTRAN sites and frequencies to meet the preceding performance indexes such as the user throughput, spectrum efficiency, and mobility. The performance requirements of the E-UTRA system within different coverage scope are listed as follows: 1. Coverage radius within 5 km: The preceding performance indexes such as the user throughput, spectrum efficiency, and mobility must be fully satisfied. 2. Coverage radius within 30 km: The throughput and spectrum efficiency are allowed to slightly drop but within an acceptable range, and the mobility index must be fully satisfied. 3. Maximum coverage radius: 100 km.

2.9 Spectrum Flexibility


On the one hand, the spectrum flexibility allows deployment of E-UTRA at varied bands including 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz. The E-UTRA supports paired and unpaired spectrums. On the other hand, the spectrum flexibility allows consolidation of spectrum bands.

2.10 Coexistence and Interoperability with Existing 3GPP Systems


Interoperability requirements of the E-UTRA and 3GPP systems include but not limited to:
9

LTE Overview

1.

E-UTRAN

and

UTRAN/GERAN

multi-mode

terminals

support

UTRAN/GERAN measurement and handover between E-UTRAN systems and UTRAN/GERAN systems. 2. 3. The E-UTRAN system supports inter-system measurement. The handover interrupt time between R-UTRAN and UTRAN must be shorter than 300 ms for realtime services. 4. The handover interrupt time between E-UTRAN and UTRAN must be shorter than 500 ms for non-realtime services. 5. The handover interrupt time between E-UTRAN and GERAN must be shorter than 300 ms for realtime services. 6. The handover interrupt time between E-UTRAN and GERAN must be shorter than 500 ms for non-realtime services. 7. Paging information of only one of the GERAN, UTRA, or E-UTRA systems needs to be monitored for multi-mode terminals in non-active state (similar to R6 Idle mode or Cell_PCH state).

2.11 Reducing CAPEX and OPEX


The flattening of the system architecture and the decrease in intermediate nodes dramatically reduces the equipment costs and maintenance costs.

10

3 LTE Architecture

Knowledge points Radio protocol structure S1 interface X2 interface

3.1 System Architecture


LTE adopts an OFDM-based air interface technology which is different from those of 2G and 3G. LTE adopts a flat network architecture within which E-UTRAN contains only eNodeBs instead of RNC, so as to optimize the traditional 3G network architecture. LTE supports functions of PDCP/RLC/MAC/physical layer protocols on the E-UTRA user plane and functions of the RRC protocol on the control plane. Figure 8 shows the EUTRAN system architecture.

E-UTRAN architecture 11

eNodeBs are connected over an x2 interface and every eNodeB is connected to the Evolved Packet Core (EPC) network over an S1 interface. The user plane of S1 interfaces terminates on the Serving-Gateway (S-GW) and the control plane of S1 interfaces terminates on the Mobile Management Entity (MME). The other end of the control plane and user plane terminates on the eNodeB. Functions of all NEs in the preceding figure are listed as follows: eNodeB Besides the original eNodeB functions, eNodeB of LTE undertakes most of original RNC functions such as physical layer, MAC (including HARQ), RLC layer (including ARQ functions), PDCP, RRC, scheduling, radio access control, access mobility management, and radio resource management among different cells. LTE eNodeBs have the following functions: Manage radio resources: Radio bearer control, radio access control, connection mobility control, and dynamic resource assignment of uplink and downlink (scheduling). Compress IP headers and encrypt user data streams. Choose the UE-attached MME when the MME routing information cannot be known from the information provided for the UE. Transmit routing data of user planes to the S-GW. Schedule and transmit the paging information initiated by the MME. Schedule and transmit the broadcast information initiated by the MME or O&M. Measure the mobility and scheduling information and perform measurement reporting configuration. Schedule and transmit the Earthquake and Tsunami Warning System (ETWS) information initiated by the MME.

MME As the control core of the SAE, MME implements such functions as user access control, service bearer control, paging, and handover control.
12

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

The function of the MME is separated from that of the gateway. The control plane/user plane separated structure facilitates network deployment, single technology evolution, and flexible capacity expansion. NAS signaling NAS signaling security AS security control Mobile signaling among 3GPP radio networks The reachability of an UE in the idle state (including the control and implementation of paging signal re-transmission) Tracking area list management P-GW or S-GW selection MME selection at the time of handover SGSN selection at handover to 2G or 3GPP network Roaming Authentication Bearer management, including dedicated bearer establishment ETWS signal transmission

S-GW As the anchor point at local eNodeB handover, S-GW implements the following functions: data transfer between the eNodeB and the public data gateway, downlink packet buffer, and user-based billing. Local mobile anchor points at eNodeB handover Mobile anchor points among 3GPP systems.
13

LTE Overview

Downlink packet buffering and initialization of network-triggered service request procedure in the E-UTRAN idle mode Lawful interception Packet routing and forwarding Transport-layer packet marking (uplink/downlink) Accounting on user and QCI granularity for inter-operator charging. Uplink/downlink charging per UE, PDN, or QCI

PDN gateway (P-GW) As the designated anchor point of the data bearer, the Public Data Network Gateway (PGW) has the following functions: Packet forwarding, packet resolving, lawful interception, service-based billing, QoS control, and interconnection with non-3GPP networks. Per-user packet filtering (for example, utilize deep packet inspection) Lawful interception IP address assignment of the UE Transport-layer packet marking (downlink) Uplink/downlink service level charging, gating, and rate enforcement Aggregate Maximum Bit Rate (AMBR)-based downlink rate control

As shown in the preceding figure, the original lu interface, lub interface, and lur interface are replaced with the S1 interface and X2 interface in the new LTE architecture. Figure 8 shows the functional split between E-UTRAN and EPC. Yellow boxes depict the logical nodes, white boxes the functional entities of the control plane, and blue boxes the radio protocol layers.
14

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Functional split between E-UTRAN and EPC

3.2 Radio Protocol Architecture


3.2.1 Control Plane Protocol Architecture
Figure 10 shows the control plane protocol architecture.

Control plane protocol stack

15

LTE Overview

The PDCP terminates at eNodeB and implements functions such as control plane encryption and integrity protection. The RLC and MAC terminate at eNodeB on the network side and implement identical functions of the user plane and control plane. The RRC terminates at eNodeB and implements such functions as broadcast, paging, RRC connection management, RB control, mobility, and UE measurement reporting and control. The NAS terminates at MME and implements such functions as EPS bearer management, authentication, idle-mode EPS Connection Management (ECM), idle-mode ECM paging, and security control.

3.2.2 User Plane Protocol Architecture


Figure 11 shows the user plane protocol architecture.

User plane protocol stack

The user plane PDCP, RLC, and MAC terminate at eNodeB and implements such functions as header compression, encryption, scheduling, ARQ, and HARQ.

3.3 S1 Interface and X2 Interface


Different from those in 2G and 3G systems, S1 interface and X2 interface are newly added in the LTE system.
16

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

3.3.1 S1 Interface
The S1 interface is defined as the interface between the E-UTRAN and EPC. The S1 interface contains two parts: the control plane S1-MME interface and user plane S1-U interface. The S1-MME interface is defined as the interface between the eNodeB and MME; the S1-UE interface is defined as the interface between the eNodeB and S-GW. Figure 12 and Figure 13 respectively show the protocol stack architecture of the S1MME interface and S1-U interface.

S1-AP

SCTP IP Data link layer Physical layer

S1 interface control plane (eNodeB-MME)

User plane PDUs

GTP-U UDP IP Data link layer Physical layer

S1 interface user plane (eNodeBS-GW)

17

LTE Overview

The S1 interface has the following acknowledged functions: E-RAB service management Establishment, modification, and release

UE mobility in the ECM-CONNECTED state Handover within the LTE system Handover between the LTE system and the 3GPP system

S1 paging NAS signaling transmission S1 interface management Error indication Reset

Network sharing Roaming and area restriction NAS node selection Initial context establishment UE context modification MME load balance Location report ETWS message transmission Overload
18

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

RAN information management The S1 interface has the following acknowledged signaling procedures:

E-RAB signaling procedure E-RAB establishment E-RAB modification MME-initiated E-RAB release eNodeB-initiated E-RAB release

Handover signaling procedure Handover preparation Resource assignment Handover termination Handover cancellation

Paging NAS transmission procedure Direct uplink transmission (initial UE message) Direct uplink transmission (uplink NAS transmission) Direct downlink transmission (downlink NAS transmission)

Error indication procedure eNodeB-initiated error indication MME-initiated error indication


19

LTE Overview

Reset eNodeB-initiated reset MME-initiated reset

Initial context establishment UE context modification S1 establishment eNodeB configuration update MME configuration update Location report Location report control Location report Location report failure indication

Overload startup Overload stop Write replacement alarm Directly transmitted information transfer Figure 14 shows the S1 interface signaling procedure.

20

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Initial context establishment (blue parts) in Idle-to-Active procedure

The similarities between S1 interface and X2 interface lie in the fact that S1-U and X2U adopt the same user plane protocol to reduce protocol processing at eNodeB data forward.

3.3.2 X2 Interface
The X2 interface is defined as the interface between eNodeBs. The X2 interface contains two parts: the X2-CP and X2-U, where the X2-CP is the control plane interface between eNodeBs and the X2-U is the user plane interface between eNodeBs. Figure 15 and Figure 16 respectively show the protocol stack architecture of the X2-CP interface and X2-U interface.

21

LTE Overview

X2-AP

SCTP IP Data link layer Physical layer

X2 interface control plane

User plane PDUs

GTP-U UDP IP Data link layer Physical layer

X2 interface user plane

The X2-CP has the following functions: UE mobility in the ECM-CONNECTED state within the LTE system Context transfer from the source eNodeB to the target eNodeB User plane channel control between the source eNodeB and the target eNodeB Handover cancellation
22

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Uplink load management General X2 interface management and error processing Error indication

The X2-CP interface has the following acknowledged signaling procedures: Handover preparation Handover cancellation UE context release Error indication Load management The management of load among cells is implemented over the X2 interface. Figure 17 shows that the LOAD INDICATOR message is used for load state communication among eNodeBs.

eNB [X2 AP] LOAD INDICATOR

eNB

X2 interface LOAD INDICATION message

23

4 Physical Layer

4.1 Frame Structure


The LTE system supports the following two radio frame structures: Structure 1: Applicable to the FDD mode. Structure 2: Applicable to the TDD mode. Figure 18 shows the frame structure 1. Every 10 ms radio frame is divided into ten subframes of fixed length. Each sub-frame contains two time slots each of which is 0.5 ms long.

Frame structure 1

For FDD, at every 10 ms, ten sub-frames can be used for downlink transmission and another ten sub-frames can be used for uplink transmission. The uplink transmission and downlink transmission are separated on the frequency domain.

4.2 Physical Resources


The minimum resource unit for uplink/downlink transmission in the LTE system is called the Resource Element (RE). At the time of data transmission, the LTE system consolidates uplink and downlink timefrequency domain physical resources into Resource Blocks (RBs) for scheduling and allocation.
21

Several REs constitute an RB. There are 12 consecutive sub-carriers on the frequency domain and seven consecutive OFDM symbols (six marks with the Extended CP). That is, the frequency domain width is 180 kHz and the time length is 0.5 ms. Figure 19 and Figure 20 respectively show the physical resource structures of downlink and uplink slots.

Physical resource structure of downlink slot

22

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Physical resource structure of uplink slot

4.3 Physical Channels


The downlink physical channels contain the following channels: 1 Physical Broadcast Channel (PBCH) The coded BCH transmission block maps to four sub-frames within an 40 ms interval. The 40 ms timing is obtained by blind tests, namely, no specified signaling
23

LTE Overview

indicates the 40 ms timing. With excellent-enough channels, every sub-frame that the PBCH located can separately decode signals.

Physical Control Format Indicator Channel (PCFICH) Notify the number of PDCCH-occupied OFDM mark to the UE. Transmit the information in every sub-frame.

Physical Downlink Control Channel (PDCCH) Notify the resource assignment information of the PCH and DL-SCH and DLSCH-related HARQ information to the UE. Carry the uplink scheduling information.

Physical HARQ Indicator Channel (PHICH) Carry the HARQ ACK/NACKs for uplink data transfer.

Physical Downlink Sharing Channel (PDSCH) Carry the DL-SCH and PCH information.

Physical Multicast Channel (PMCH) Carry the MCH information.

The uplink physical channels contain the following channels: 1 Physical Uplink Control Channel (PUCCH) Carry HARQ ACK/NACKs for downlink data transfer. Carry the scheduling request information. Carry the CQI report information.
24

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Physical Uplink Sharing Channel (PUSCH) Carry the UL-SCH information.

Physical Random Access Channel (PRACH) Carry the random access preamble.

4.4 Transport Channels


The downlink transport channels contain the following channels: 1 Broadcast Channel (BCH) 2 Fixed predefined transport format Broadcast in the entire coverage area of the cell

Downlink Sharing Channel (DL-SCH) Support HARQ. Implement dynamic link adaptation by varying the demodulation, coding mode, and transmit power. Support broadcast in the entire cell. Support beamforming. Support dynamic or semi-static resource allocation. Support the UE Discontinuous Reception (DRX) to enable UE power saving. Support the MBMS transmission.

Paging Channel (PCH) Support the UE DRX to save power. (The network notifies the DRX period to the
25

LTE Overview

UE.) Broadcast in the entire coverage area of the cell Map to physical resources which can be used dynamically also for traffic or other control channels.

Multicast Channel (MCH) Broadcast in the entire coverage area of the cell Support Multicast/Broadcast over Single Frequency Network (MBSFN) combing of MBMS transmission on multiple cells. Support semi-static resource allocation.

The uplink transport channels contain the following channels: 1 Uplink Sharing Channel (UL-SCH) Support beamforming. Implement dynamic link adaptation by varying the transmit power, potential demodulation, and coding mode. Support HARQ. Support dynamic or semi-static resource allocation.

Random Access Channel (RACH) Carry limited control information. Have collision risks.

26

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

4.5 Mapping Between Transport Channels and Physical Channels


Figure 21 and Figure 22 respectively show the mapping relationships between downlink/uplink transport channels and downlink/uplink physical channels.

Mapping between downlink transport channels and downlink physical channels

Mapping between uplink transport channels and uplink physical channels

4.6 Physical Signals


Physical signals correspond to several physical layer REs, but do not carry any information that comes from higher layers. The downlink physical signals include the reference signal and the synchronization signal. Reference signal The downlink reference signals include the following three types of reference signals:
27

LTE Overview

Cell-specific reference signals, associated with non-MBSFN transmission MBSFN reference signals, associated with MBSFN transmission UE-specific reference signals

Synchronization signals The synchronization signals include the following two types of signals: Primary synchronization signal Secondary synchronization signal

For FDD, the primary synchronization signal maps to the last OFDM symbol of the time slot 0 and time slot 10. The secondary synchronization signal maps to the second last OFDM symbol of the time slot 0 and time slot 10. The uplink physical signals include the reference signals. Reference signals The uplink reference signals include the following two types of signals: Demodulation reference signals, associated with PUSCH or PUCCH transmission Sounding reference signals, not associated with PUSCH or PUCCH transmission

The demodulation reference signals and the sounding reference signals use the same base sequence set.

4.7 Physical Layer Model


The following figures show the physical layer models of various types of channels. Node Bs in all of the following figures are called eNodeBs or eNodeB in LTE.

28

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Node B
Channel-state information, etc.
N Transport blocks (dynamic size S1..., SN)
ACK/NACK ACK/NACK HARQ info

UE

Error indications

HARQ

HARQ info

HARQ

CRC CRC
Coding + RM Coding + RM

Redundancy for error detection

CRC CRC
Coding + RM Decoding + RM

MAC scheduler

Redundancy version

Redundancy for data detection

Interleaving
Modulation scheme Resource/power assignment Antenna mapping

Interl.

Deinterleaving
QPSK, 16QAM, 64QAM

Interl.

Data modulation

Data modulation

Data modulation
RB mapping

Data demodulation

RB mapping Resource mapping


Multi-antenna processing

Resource demapping

Antenna mapping

Antenna demapping

physical layer model for DL-SCH transmission

Node B
Single Transport blocks (fixed size S)

UE

Error indication

CRC
Coding + RM

CRC
Decoding + RM

Interleaving

Deinterleaving

Data modulation

QPSK only

Data demodulation

Resource mapping

Resource demapping

Antenna mapping

Antenna demapping

Physical layer model for BCH transmission

29

LTE Overview

Node B
Single Transport blocks (dynamic size S)

UE

Error indication

CRC
Coding + RM

CRC
Decoding + RM

MAC scheduler

Interleaving
Modulation scheme Resource/power assignment Antenna mapping

Deinterleaving

Data modulation

Data demodulation

Resource mapping

Resource demapping

Antenna mapping

Antenna demapping

Physical layer model for PCH transmission

Node B
N Transport blocks (dynamic size S1..., SN)

UE

Error indications

CRC CRC
Coding + RM Coding + RM

CRC CRC
Coding + RM Decoding + RM

MAC scheduler

Interleaving
Modulation scheme Resource/power assignment Antenna mapping

Interl.

Deinterleaving

Interl.

Data modulation

Data modulation

Data modulation
RB mapping

Data demodulation

RB mapping Resource mapping

Resource demapping

Antenna mapping

Antenna demapping

Semi-static configuration

Physical layer model for MCH transmission

30

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Node BError
Channel -state information, etc. indications
ACK/NACK

UE

HARQ

HARQ info

ACK/NACK

HARQ

CRC CRC MAC scheduler


Coding + Decoding + RM RM

CRC CRC
Coding + RM Coding + RM

Uplink transmission control

Interl. Deinterleaving
Modulation scheme Resource assignment Antenna mapping

Interl. Interleaving
Data modulation Data modulation
RB mapping Resource mapping
Modulation scheme Resource/power assignment

Data demodulation RB mapping

Data modulation

Resource demapping

Antenna demapping

Physical layer model for UL-SCH transmission

4.8 Physical Layer Procedures


4.8.1 Synchronization Procedures
Cell search Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects that cells physical layer cell ID. E-UTRA cell search is based on various signals transmitted in the downlink such as primary and secondary synchronization signals, and downlink reference signals. Timing synchronization Timing synchronization procedures include radio synchronization, and transmission timing adjustments. link monitoring, inter-cell

4.8.2 Power Control


Power control determines the energy per resource element (EPRE). EPRE denotes the energy prior to CP insertion. EPRE also denotes the average energy taken over all constellation points for the modulation scheme applied. Uplink power control determines the average power of one DFT-SOFDM symbol on a physical channel.

31

LTE Overview

Uplink power control Uplink power control procedure controls the transmit power of different uplink physical channels.

Downlink power allocation eNodeB determines the downlink transmit energy per resource element.

4.8.3 Random Access Procedures


Prior to initiation of the non-synchronized physical random access procedure, physical layer shall receive the following information from the higher layers: 1. Random access channel parameters (PRACH configuration, frequency position, and preamble format). 2. Parameters for determining the root sequences and their cyclic shifts in the preamble sequence set for the cell (index to root sequence table, cyclic shift (Ncs), and set type (normal or high-speed set)). From the physical layer perspective, the physical random access procedure encompasses the transmission of random access preamble and random access response. The remaining messages are scheduled for transmission by the higher layer on the shared data channel and are not considered part of the L1 random access procedure. The following steps are required for the physical random access procedure: 1. Physical layer procedure is triggered upon request of a preamble transmission by higher layers. 2. A preamble index, preamble transmission power (PREAMBLE_TRANSMISSION_POWER), associated RA-RNTI, and PRACH resource are indicated by higher layers as part of the request. 3. Determine preamble transmit power: PPRACH = min{Pmax, PREAMBLE_RECEIVED_TARGET_POWER + PL}; where, Pmax indicates the maximum allowed power configured at higher layers, and PL indicates UEcalculated downlink path loss. 4. A preamble sequence is then selected from the preamble sequence set using the
32

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

preamble index. 5. A single preamble transmission then occurs using the selected preamble sequence with transmission power PREAMBLE_TRANSMISSION_POWER on the indicated PRACH resource. 6. The associated PDCCH with RA-RNTI is detected in the random access response window controlled by higher layers. If an associated PDCCH with RA-RNTI is detected then the corresponding PDSCH transport block is passed to the higher layers. Higher layers resolve the transport block and indicate the 20-bit UL-SCH grant to the physical layer.

33

5 Layer 2
Layer 2 consists of three sublayers PDCP, RLC, and MAC. Figure 28 and Figure 29 respectively show Layer 2 downlink and uplink structures.

Layer 2 downlink structure

32

Layer 2 uplink structure

The connection points among sublayers are known as the Service Access Points (SAP). The service provided by PDCP is referred to as the radio bearer. The PDCP provides the Robust Header Compression (ROHC) and security protection. The SAP between physical layer and MAC layer provides transport channels and that between MAC layer and RLC layer provides logical channels. The MAC layer provides multiplexing and mapping of logical channels (radio bearer) to transport channels (transport block). Only one transport block is generated at each TTI (1 ms) in the uplink or downlink in the case of non-MIMO.

5.1 MAC Sublayer


5.1.1 MAC Functions
The MAC sublayer provides the following functions:

33

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Mapping between logical channels and transport channels. MAC Service Data Unit (SDU) multiplexing/demultiplexing. Scheduling information report. Error correction through HARQ Logical channel prioritization of the same UE. UE prioritization through dynamic scheduling. Selection of transmission formats. Padding.

5.1.2 Logical Channels


MAC provides different types of data transmission services. The type of each logical channel is defined based on the type of transmitted data. Logical channels are categorized into: Control channels: used to transfer data on the control plane. Traffic channels: used to transfer data on the user plane.

Control channels include: Broadcast Control Channel (BCCH). The BCCH is a downlink channel used to broadcast system control messages. Paging Control Channel (PCCH). The PCCH is a downlink channel used to transfer paging messages and system information change notifications. The PCCH is used to page a UE when the UE cell location is unknown to the network. Common Control Channel (CCCH).

34

LTE Overview

The CCCH is used to transfer control messages between UEs and network when there is no RRC connection between them. Multicast Control Channel (MCCH). A point-to-multipoint downlink channel used for transmitting MBMS control information from the network to the UE, for one or several MTCHs. This channel is only used to UEs that receive MBMS. Dedicated Control Channel (DCCH). A point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. This channel is used by UEs having an RRC connection. Traffic channels include: Dedicated Traffic Channel (DTCH). The DTCH is a point-to-point channel, dedicated to one UE, for the transfer of user information. Multicast Traffic Channel (MTCH). A point-to-multipoint downlink channel for transmitting traffic data from the network to the UE. This channel is only used to UEs that receive MBMS.

5.1.3 Mapping Between Logical Channels and Transport Channels


Figure 30 and Figure 31 respectively show the mapping between downlink and uplink logical channels and transport channels.

35

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Mapping between downlink logical channels and transport channels

Mapping between uplink logical channels and transport channels

5.2 RLC Sublayer


5.2.1 RLC Functions
The RLC sublayer provides the following functions: Transfer of upper layer PDUs. Error Correction through ARQ (only for AM data transfer). Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer). Re-segmentation of RLC data PDUs (only for AM data transfer).
36

LTE Overview

In sequence delivery of upper layer PDUs (only for UM and AM data transfer). Duplicate detection (only for UM and AM data transfer). Protocol error detection and recovery. RLC SDU discard (only for UM and AM data transfer). RLC re-establishment.

5.2.2 PDU Structure


Figure 32 shows the RLC PDU structure. The PDU sequence number carried by the RLC header is independent of the SDU sequence number (that is, the PDCP sequence number). The red dotted lines in Figure 32 indicate segmentation positions.

RLC PDU structure

5.3 PDCP Sublayer


5.3.1 PDCP Functions
The main services and functions of the PDCP sublayer for the user plane include: Header compression and decompression: ROHC only.
37

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

Transfer of user data. In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM.

Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM.

Retransmission of PDCP SDUs at handover for RLC AM. Ciphering and deciphering. Timer-based SDU discard in uplink. The main services and functions of the PDCP sublayer for the control plane include:

Ciphering and Integrity Protection. Transfer of control plane data.

5.3.2 PDU Structure


Figure 33 shows the PDCP PDU structure. PDCP PDU and PDCP header are octet-aligned. PDCP header can be either 1 or 2 bytes long.

PDCP PDU structure

38

6 RRC

6.1 RRC Functions


Main Functions of RRC include: Broadcast of system information related to the NASs Broadcast of system information related to the ASs Paging Establishment, retention, and release of RRC connection between UEs and EUTRANs, including: Allocation of temporary identifiers between UEs and E-UTRANs Configuration of the Signaling Radio Bearers (SRBs) for RRC connection Low priority and high priority SRBs Security management including key management Establishment, configuration, retention, and release point-to-point RBs Mobility management, including: Measurement report and reporting control of the mobile UEs between cells and between RATs. Handover UE cell selection and reselection; cell selection and reselection control Context forwarding during handover
38

MBMS notification Establishment, configuration, retention, and release of RBs for the MBMS QoS management UE measurement report and reporting control NAS direct transfer

6.2 RRC State


RRC state includes RRC_IDLE and RRC_CONNECTED RRC idle state (RRC_IDLE) PLMN selection DRX configured by NAS System information broadcast Paging Cell reselection mobility A unique identifier allocated to a UE within a Tracking Area (TA) No RRC contexts stored in eNodeBs

Connection state (RRC_CONNECTED) The UE has an E-UTRAN-RRC connection. The UE has a context in E-UTRAN. The E-UTRAN knows the cell which the UE belongs to.

39

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

The network can transmit and receive data to/from the UEs. Network controlled mobility (handover). Neighbor cell measurements. The PDCP/RLC/MAC features of the RRC_CONNECTED The UE can transmit and receive data to/from the networks. The UE intercepts controlled signaling channels related to the shared data channels to view that whether the UE is allocated any data on the shared data channel. The UE also reports channel quality information and feeds back information to eNodeB. The DRX cycle can be conformed according to the UE mobility level to save UE power and enhance resource efficiency. This function is controlled by eNodeB.

6.3 NAS State and the Relationship With the RRC state
The NAS state model can be described by the two-dimensional state model of the EPS Mobility Management state (EMM) and the EPS Connection Management state. EMM state: EMM-DEREGISTERED state EMM-REGISTERED state

ECM state: ECM-IDLE state ECM-CONNECTED state

40

LTE Overview

Note: The EMM state and the ECM state are mutually independent. The relationship between the NAS state and the RRC state is as follows: EMM-DEREGISTERED state + ECM-IDLE state RRC_IDLE state Mobility feature: PLMN selection UE location: Unknown to the network.

EMM-REGISTERED state + ECM-IDLE state RRC_IDLE state Mobility feature: Cell selection UE location: Known to the network at TA level.

EMM-REGISTERED state + ECM-CONNECTED state + RB Established RRC_CONNECTED state Mobility feature: Handover UE location: Known to the network at cell level.

6.4 RRC Procedure


RRC procedure includes the System Information, Connection Control, mobility procedure, measurements, and direct transfer.

6.4.1 System Information


System information includes the Master Information Block (MIB) and a series of System Information Blocks (SIBs). Master Information Block: defines the most important physical information of the cells and is used to receive a further system information. System Information Block Type 1: assesses the related information of whether the UE is allowed to access to a cell and defines the dispatch of other system
41

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

information blocks. System Information Block Type 2: includes common and shared channel information. System Information Block Type 3: includes cell reselection information; mainly related to the service cells. System Information Block Type 4: includes cell reselection related service frequency points and intra-frequency neighboring cell information. System Information Block Type 5: includes cell reselection related other E-UTRA frequency points and inter-frequency neighboring cell information. System Information Block Type 6: includes cell reselection related UTRA frequency points and UTRA neighboring cell information. System Information Block Type 7: includes cell reselection related GERAN frequency points information. System Information Block Type 8: includes cell reselection related CDMA2000 frequency points and CDMA2000 neighboring cell information. System Information Block Type 9: includes home eNodeB identifiers (HNBID). System Information Block Type 10: includes ETWS primary notification. System Information Block Type 11: includes ETWS secondary notification. The MIB maps to the BCCH and BCH. The SI maps to the BCCH and DL-SCH, and is identifies through the System Information RNTI (SI-RNTI). The MIB uses a fixed dispatch cycle of 40 ms. The System Information Block Type 1 uses a fixed dispatch cycle of 80 ms. The other SI dispatch cycle is not fixed and indicated by the System Information Block Type 1.

6.4.2 Connection Control


RRC connection control includes: Paging
42

LTE Overview

RRC connection establishment Initial security activation RRC connection reconfiguration Counter check RRC connection re-establishment RRC connection release Radio resource configuration SRB addition/ modification DRB release SRB addition/ modification MAC main reconfiguration Semi-persistent scheduling reconfiguration Physical channel reconfiguration

Radio link failure related actions

43

7 Core LTE Technologies

7.1 Duplex Mode


In addition to FDD and TDD duplex modes, the LTE system is expected to further support the half-duplex FDD.

7.2 Multi-access Mode


OFDMA is employed as the multiplexing scheme in the LTE downlink systems.

Multiplexing scheme in LTE downlink systems

DFT-S-OFDM (also called SC-FDMA) is employed as the multiplexing scheme in the LTE uplink systems.

43

Multiplexing scheme in LTE uplink systems

7.3 Multi-antenna Technologies


Downlink multi-antenna transmission: Multi-antenna transmission supports two or four antennas. The maximum number of code words is 2 and irrelevant of the number of antennas, but there is a fixed mapping relationship between core words and layers. Figure 35 shows the general relationship among code words, layers, and antenna ports.

Physical channel processing

Multi-antenna technologies include the SDM and transmit diversity. The SDM supports SU-MIMO and MU-MIMO. When a MIMO channel is solely assigned to a single UE, this is called SU-MIMO. When MIMO data streams are spatially assigned to different UEs, this is called MU-MIMO. Uplink multi-antenna transmission: The baseline antenna configuration for uplink MIMO is either SIMO 1X2 antenna configuration or MU-MIMO. To allow for MU-MIMO reception at the Node B, allocation of the same time and frequency resource to several UEs, each of which
44

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

transmitting on a single antenna, is supported. Closed loop type adaptive antenna selection transmit diversity shall be supported for FDD (optional in UE).

7.4 Link Adaptation


Downlink adaptation: Refer to the adaptive modulation and coding (AMC) that is applied with three modulation schemes (QPSK, 16QAM, and 64QAM) and variable code rates. Uplink adaptation: Include three link adaptation techniques: 1) adaptive transmit bandwidth, 2) transmit power control, and 3) adaptive modulation and channel code rate.

7.5 HARQ and ARQ


E-UTRAN provides ARQ and HARQ functionalities.

7.5.1 HARQ
The HARQ within the MAC sublayer has the following characteristics: N-process Stop-And-Wait HARQ is used. The HARQ transmits and retransmits TBs.

In the downlink: Asynchronous adaptive HARQ PUSCH or PUCCH used for ACK/NACKS for DL (re-)transmissions PDCCH used to signal the HARQ process number and if re-transmission or transmission Adaptive re-transmissions scheduled through PDCCH
45

LTE Overview

In the uplink: Synchronous HARQ Maximum number of re-transmissions configured per UE (instead of per radio bearer)

PHICH used to transmit ACK/NACKs for non-adaptive UL (re-)transmissions HARQ operation in uplink is governed by the following principles: Regardless of the content of the HARQ feedback (ACK or NACK), when a PDCCH for the UE is correctly received, the UE follows what the PDCCH asks the UE to do i.e. perform a transmission or a retransmission (referred to as adaptive retransmission). When no PDCCH addressed to the C-RNTI of the UE is detected, the HARQ feedback dictates how the UE performs retransmissions. NACK: The UE performs a non-adaptive retransmission. ACK: The UE does not perform any UL (re)transmission and keeps the data in the HARQ buffer.

Measurement gaps are of a higher priority than HARQ retransmissions: Whenever an H-ARQ retransmission collides with a measurement gap, the HARQ retransmission does not take place.

7.5.2 ARQ
The ARQ within the RLC sublayer has the following characteristics: The ARQ retransmits RLC SDUs or RLC PDUs (segments). ARQ retransmissions are based on either RLC status reports or HARQ/ARQ interactions.

The RLC must poll RLC status reports. Status reports can be triggered by upper layers.
46

Chapter Error! Use the Home tab to apply 1 to the text that you want to appear here. Error! Use the Home tab to apply 1 to the text that you want to appear here.

7.5.3 HARQ/ARQ Interactions


If the HARQ transmitter detects a failed delivery of a TB for example, maximum retransmission limit is reached the relevant transmitting ARQ entities are notified and potential retransmissions and re-segmentation can be initiated.

47

8 Abbreviations
Abbreviation 3GPP BPSK CAPEX DFT DRX E-MBMS eNodeB E3G EPC E-UTRA HCR HeNB IASA IFFT LCR LDPC LTE MIMO MME OFDM OPEX PAPR QAM QoS QPSK RRC SAE SC-FDMA SDM S-GW TTI Full Name 3rd Generation Partnership Project Binary Phase Shift Keying Capital Expenditure Discrete Fourier Transform Discontinuous Reception Evolved Multimedia Broadcast and Multicast Service Evolution Node B evolved 3G Evolved Packet Core Evolved Universal Terrestrial Radio Access High Chip Rate Home eNodeB Inter Access System Anchor Inverse Discrete Fourier transform Low Chip Rate low-density parity-check Long Term Evolution Multiple Input Multiple Output Mobile Management Entity Orthogonal Frequency Division Multiplex Operating Expenditure Peak to Average Power Ratio QUADRATURE AMPLITUDE MODULATION Quality of Service QUADRATURE PHASE SHIFT KEYING Radio Resource Control System Architecture Evolution Single Carrier Frequency Division Multiple Access Spatial Division Multiple Serving Gateway Transmission Time Interval

48

9 References
SN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Name 25.912 Feasibility study for evolved Universal Terrestrial Radio Access (UTRA) and Universal Terrestrial Radio Access Network (UTRAN) 25.913 Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN) 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Overall description 25.814 Physical layer aspects for evolved Universal Terrestrial Radio Access (UTRA) 36.211 Physical Channels and Modulation 36.212 Multiplexing and channel coding 36.213 Physical layer procedures 36.214 Physical layer Measurements 36.302 Services provided by the physical layer 36.331 Radio Resource Control (RRC) 36.104 Base Station (BS) radio transmission and reception 36.321 Medium Access Control (MAC) protocol specification 23.401 General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access 23.203 Policy and charging control architecture

50

Das könnte Ihnen auch gefallen