Beruflich Dokumente
Kultur Dokumente
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 Mobile Communications Evolution ....................................................................................... 1 1.1.2 Comparison Among WCDMA, TD-SCDMA, and CDMA2000 ........................................... 2 1.1.3 WCDMA Evolution ............................................................................................................... 2 1.1.4 TD-SCDMA Evolution .......................................................................................................... 3 1.1.5 CDMA200 Evolution ............................................................................................................. 4 1.2 LTE Overview and Standards Development ..................................................................................... 4 2 LTE Indexes and Requirements ............................................................................................................... 7 2.1 Overview ........................................................................................................................................... 7 2.2 Frequency Band Division .................................................................................................................. 8 2.3 Peak Data Rate .................................................................................................................................. 9 2.4 Control Plane Delay .......................................................................................................................... 9 2.5 User Plane Delay............................................................................................................................... 9 2.6 User Throughput ............................................................................................................................. 10 2.7 Spectrum Efficiency ........................................................................................................................ 10 2.8 Mobility........................................................................................................................................... 10 2.9 Coverage ......................................................................................................................................... 11 2.10 Spectrum Flexibility ...................................................................................................................... 11 2.11 Coexistence and Interoperability with Existing 3GPP Systems .................................................... 12 2.12 Reducing CAPEX and OPEX ....................................................................................................... 12 3 LTE Architecture ..................................................................................................................................... 13
i
3.1 System Architecture ......................................................................................................................... 13 3.2 Radio Protocol Architecture ............................................................................................................ 17 3.2.1 Control Plane Protocol Architecture .....................................................................................17 3.2.2 User Plane Protocol Architecture .........................................................................................18 3.3 S1 Interface and X2 Interface .......................................................................................................... 18 3.3.1 S1 Interface ...........................................................................................................................19 3.3.2 X2 Interface ..........................................................................................................................23 4 Physical Layer........................................................................................................................................... 27 4.1 Frame Structure................................................................................................................................ 27 4.2 Physical Resources .......................................................................................................................... 27 4.3 Physical Channels ............................................................................................................................ 29 4.4 Transport Channels .......................................................................................................................... 31 4.5 Mapping Between Transport Channels and Physical Channels ...................................................... 32 4.6 Physical Signals ............................................................................................................................... 33 4.7 Physical Layer Model ...................................................................................................................... 34 4.8 Physical Layer Procedures ............................................................................................................... 37 4.8.1 Synchronization Procedures .................................................................................................37 4.8.2 Power Control .......................................................................................................................37 4.8.3 Random Access Procedures ..................................................................................................38 5 Layer 2 ....................................................................................................................................................... 41 5.1 MAC Sublayer ................................................................................................................................. 42 5.1.1 MAC Functions ....................................................................................................................42 5.1.2 Logical Channels ..................................................................................................................43 5.1.3 Mapping Between Logical Channels and Transport Channels .............................................44 5.2 RLC Sublayer .................................................................................................................................. 45 5.2.1 RLC Functions ......................................................................................................................45
ii
5.2.2 PDU Structure ...................................................................................................................... 46 5.3 PDCP Sublayer ............................................................................................................................... 46 5.3.1 PDCP Functions ................................................................................................................... 46 5.3.2 PDU Structure ...................................................................................................................... 47 6 RRC ........................................................................................................................................................... 49 6.1 RRC Functions ................................................................................................................................ 49 6.2 RRC State........................................................................................................................................ 50 6.3 NAS State and the Relationship With the RRC state ...................................................................... 51 6.4 RRC Procedure ............................................................................................................................... 52 6.4.1 System Information .............................................................................................................. 52 6.4.2 Connection Control .............................................................................................................. 53 7 Core LTE Technologies ............................................................................................................................ 55 7.1 Duplex Mode .................................................................................................................................. 55 7.2 Multi-access Mode .......................................................................................................................... 55 7.3 Multi-antenna Technologies ............................................................................................................ 56 7.4 Link Adaptation............................................................................................................................... 56 7.5 HARQ and ARQ ............................................................................................................................. 57 7.5.1 HARQ .................................................................................................................................. 57 7.5.2 ARQ ..................................................................................................................................... 58 7.5.3 HARQ/ARQ Interactions ..................................................................................................... 58 Appendix A Abbreviations ......................................................................................................................... 59 Appendix B References .............................................................................................................................. 61
iii
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 low-speed 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.1-1 shows the development and evolution of wireless communication technologies.
Table 1.1-1Comparison among WCDMA, TD-SCDMA, and CDMA2000 Standard Inheritance basis Synchronous mode Chip rate System bandwidth Core network Voice coding mode GSM Asynchronous 3.84 Mcps 5 MHz GSM MAP AMR WCDMA 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
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.
Long-term evolution version (4G) Mid-term evolution version Short-term evolution version Basic version
IMT-Adv
3GPP (R4)
Voice/Data N frequency point
Phase I
Phase II
Phase III
CDMA standard
OFDMA standard
Down Link
100 Mbps
2 Mbps
1 Mbps CDMA2000 1x CDMA One 100 kbps 1 Mbps 10 Mbps 100 Mbps Uplink
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.
2.1 Overview
Knowledge points Spectrum division LTE system requirements Others Physical channels and mapping relationship Figure 2.1-1 shows the LTE indexes and requirements prescribed by 3GPP.
LTE features
Enhanced spectrum efficiency Lower OPEX and CAPEX Different bandwidth supported
Table 2.2-1 E-UTRA frequency bands E-UTRA Operating Band FUL_low FUL_high FDL_low FDL_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 8 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 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
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.
2.8 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 15120 km/h, and cell network services at the speed of 120350 km/h (the speed even reaches 500 km/h at specified bands).
10
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.
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 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.9 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.
11
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).
12
3 LTE Architecture
MME / S-GW
MME / S-GW
X2
eNB eNB
S1
eNB
X2
S1
S1
X2
S1
E-UTRAN
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
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.
As the control core of the SAE, MME implements such functions as user access control, service bearer control, paging, and handover control. 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
15
Mobile anchor points among 3GPP systems. 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 (P-GW) 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 3.1-2 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.
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.
eNB Inter Cell RRM RB Control Connection Mobility Cont. MME Radio Admission Control NAS Security eNB Measurement Configuration & Provision Dynamic Resource Allocation (Scheduler) RRC PDCP S-GW RLC MAC S1 PHY Packet Filtering internet E-UTRAN EPC Mobility Anchoring UE IP address allocation P-GW Idle State Mobility Handling EPS Bearer Control
eNB
17
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), idlemode ECM paging, and security control.
The user plane PDCP, RLC, and MAC terminate at eNodeB and implements such functions as header compression, encryption, scheduling, ARQ, and HARQ.
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.
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 3.3-1 and Figure 3.3-2 respectively show the protocol stack architecture of the S1-MME interface and S1-U interface.
S1-AP
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 RAN information management
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.
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 Reset eNodeB-initiated reset
21
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 3.3-3 shows the S1 interface signaling procedure.
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.
UE
Paging
eNB
Paging
MME
S1-AP: INITIAL UE MESSAGE (FFS) + NAS: Service Request + eNB UE signalling connection ID
S1-AP: INITIAL CONTEXT SETUP REQUEST + (NAS message) + MME UE signalling connection ID + Security Context + UE Capability Information (FFS) + Bearer Setup (Serving SAE-GW TEID, QoS profile) S1-AP: INITIAL CONTEXT SETUP COMPLETE + eNB UE signalling connection ID + Bearer Setup Confirm (eNB TEID)
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 3.3-4 and Figure 3.3-5 respectively show the protocol stack architecture of the X2-CP interface and X2-U interface.
23
X2-AP
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
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.
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 3.3-6 shows that the LOAD INDICATOR message is used for load state communication among eNodeBs.
eNB
25
4 Physical Layer
#0 slot
#1 Sub-frame
#2
#18
#19
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.
and allocation. 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 4.2-1 and Figure 4.2-2 respectively show the physical resource structures of downlink and uplink slots.
DL RB k N RB N sc 1
subcarrier s subcarrier s
DL RB N RB N sc
RB N sc
Resource element
(k , l )
k 0
l0
DL N symb
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.
One uplink slot Tslot
UL RB k N RB N sc 1
subcarrier s subcarrier s
UL RB N RB N sc
RB N sc
Resource element
(k , l )
k 0
l0
UL N symb
indicates the 40 ms timing. With excellent-enough channels, every sub-frame that the PBCH located can separately decode signals. 2. Physical Control Format Indicator Channel (PCFICH) Notify the number of PDCCH-occupied OFDM mark to the UE. Transmit the information in every sub-frame. 3. 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. 4. Physical HARQ Indicator Channel (PHICH) Carry the HARQ ACK/NACKs for uplink data transfer. 5. Physical Downlink Sharing Channel (PDSCH) Carry the DL-SCH and PCH information. 6. 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. 2. Physical Uplink Sharing Channel (PUSCH)
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.
Carry the UL-SCH information. 3. Physical Random Access Channel (PRACH) Carry the random access preamble.
31
Map to physical resources which can be used dynamically also for traffic or other control channels. 4. 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. 2. Random Access Channel (RACH) Carry limited control information. Have collision risks.
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.
BCH MCH PCH DL-SCH
PBCH
PMCH
PDSCH
PDCCH
Figure 4.5-1 Mapping between downlink transport channels and downlink physical channels
UL-SCH
RACH
PUSCH
PRACH
PUCCH
Figure 4.5-2 Mapping between uplink transport channels and uplink physical channels
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.
34
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
CRC CRC
Coding + RM Decoding + RM
MAC scheduler
Redundancy version
Interleaving
Modulation scheme Resource/power assignment Antenna mapping
Interl.
Deinterleaving
QPSK, 16QAM, 64QAM
Interl.
Data modulation
Data modulation
Data modulation
Resource demapping
Antenna mapping
Antenna demapping
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
35
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
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
Resource demapping
Antenna mapping
Semi-static configuration
Antenna demapping
36
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
CRC CRC
Coding + RM Coding + RM
Uplink transmission c
Interl. Deinterleaving
Modulation scheme Resource assignment Antenna mapping
Interl. Interleaving
Data modulation Data modulation
RB mapping Resource mapping
Modulation scheme Resource/power assignment
Data modulation
Resource demapping
Antenna demapping
constellation points for the modulation scheme applied. Uplink power control determines the average power of one DFT-SOFDM symbol on a physical channel. 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.
(PREAMBLE_TRANSMISSION_POWER),
PRACH resource are indicated by higher layers as part of the request. 3. Determine preamble
38
transmit
power:
PPRACH
min{Pmax,
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_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 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 RARNTI is detected then the corresponding PDSCH transport block is passed to the higher layers. Higher layers resolve the transport block and indicate the 20bit UL-SCH grant to the physical layer.
39
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.
Radio Bearers ROHC PDCP Security Security Security Security ROHC ROHC ROHC
RLC
...
...
CCCH BCCH
PCCH
MAC
Multiplexing UE1
Multiplexing UEn
HARQ
41
RLC
...
MAC
Multiplexing
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.
42
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.
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.
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.
PCCH BCCH CCCH DCCH DTCH MCCH MTCH
PCH
BCH
DL-SCH
MCH
Figure 5.1-1 Mapping between downlink logical channels and transport channels
CCCH
DCCH
DTCH
RACH
UL-SCH
Figure 5.1-2 Mapping between uplink logical channels and transport channels
45
Re-segmentation of RLC data PDUs (only for AM data transfer). 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.
n+1
n+2
n+3 ...
RLC header
RLC header
RLC PDU
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.
Header compression and decompression: ROHC only. 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.
PDCP header
47
6 RRC
49
MBMS notification Establishment, configuration, retention, and release of RBs for the MBMS QoS management UE measurement report and reporting control NAS direct transfer
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.
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 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
51
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.
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.
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 EUTRA 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.
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
54
Frequency domain Channel coding/ interleaving/ scrambling QAM modulation QPSK/16QAM/64QAM Serial > Parallel .. .
Time domain
OFDM modulation
DFT-S-OFDM (also called SC-FDMA) is employed as the multiplexing scheme in the LTE uplink systems.
DFT
.. .
DFT-SOFDM modulation
55
code words
layers
antenna ports
Scrambling
Scrambling
Modulation mapper
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 transmitting on a single antenna, is supported. Closed loop type adaptive antenna selection transmit diversity shall be supported for FDD (optional in UE).
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.
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.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 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
57
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.
58
Appendix A 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
59
Appendix B 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
61