05 RA4133 RL20 LTE Paging and RRC Connection E01

LTE Radio Performance Management
Introduction
[RL20] RA4133-20A
Paging and RRC Connection
Module 5
1 Nokia Siemens Networks RA4133 EN20GLA0

Course Objectives
After completing this learning element, the

participant will be able to:
Explain idle and connected states within LTE

Understand paging and idle mode DRX
Describe RACH procedure (RACH preamble, open loop
power control)
Understand L1 TA synchronization and cyclic prefix within
different cell size areas.
Describe the phases, counters and related KPIs defined for the RRC
connection setup procedure.
Distinguish the RRM functionalities related with the control of the
radio link quality for idle and connected mode.

Idle and Connected States within LTE

RRC States in 3G
UTRA RRC Connected Mode
UE in DRX mode UE in DRX mode

discontinuous reception URA_PCH CELL_PCH discontinuous reception
Dedicated resources Common resources

allocated (DCH/HS) CELL_DCH CELL_FACH allocated (RACH/FACH)
Tx and Rx mode Tx and Rx mode
Cell selection
Cell re-selection Idle Mode
Listen to paging

RRC States in LTE
E-UTRA RRC Connected Mode In LTE one distinguishes just between

RRC connected
UE has E-UTRAN RRC connection
UE has context in E-UTRAN RRC idle
E-UTRAN knows UEs cell
There are no sub-states for RRC
UE identified by C-RNTI
UE Network data exchange possible
connected mode
Handover mobility
Neighbour cell measurements
UE reports CQI to eNB
eNB controlled DRX/DTX period
RRC connection
establishment /
release
Idle Mode
No RRC context stored in the eNB
UE specific DRX configured by NAS
Cell re-selection mobility
Broadcast of system information
Paging
UE identified by ID which is unique in a tracking area
NAS States in LTE - EMM
Definition of main EPS Mobility Management states
EMM-DEREGISTERED
The UE is not reachable by a MME
UE context can still be stored in the UE and MME
EMM-REGISTERED
UE enters to EMM-Registered with Attach or Tracking Area Update (TAU) procedure
The UE location is known with accuracy of the tracking area list
UE has at least one active PDN connection
After Detach procedure the state is changed to EMM-DEREGISTERED
EMM states in UE EMM states in MME

Detach Detach
Attach reject Attach reject
TAU Reject TAU Reject
All Bearer Deactivated All Bearer Deactivated
EMM-DEREGISTERED EMM-REGISTERED EMM-DEREGISTERED EMM-REGISTERED
Attach accept Attach accept

TAU Accept

NAS States in LTE - ECM
Definition of EPS Connection Management states
ECM-IDLE
UE is in ECM-IDLE state when no NAS signaling connection between UE and network exists
In the EMM-REGISTERED and ECM-IDLE state, the UE shall perform
Tracking Area Update
Periodic Tracking Area Update
Service Request
Answer to paging from MME with Service Request
UE and MME enter the ECM-CONNECTED state when signaling connection is established.
ECM-CONNECTED
UE location is known in the MME with an accuracy of a serving eNodeB.
For a UE in the ECM-CONNECTED state, there exists a signaling connection between the UE and the MME
The S1 release procedure changes the state at both UE and MME from ECM-CONNECTED to ECM-IDLE
EMC states in UE ECM states in MME

RRC Released S1 Released
ECM-IDLE ECM-CONNECTED ECM-IDLE ECM-CONNECTED
RRC Established S1 Established
ECM Connected = RRC Connected + S1 Connection

Summary of LTE States
EMM state ECM state RRC state UE Location Mobility
EMM_
ECM_IDLE RRC_IDLE Unknown PLMN Selection
Deregistered
EMM_
ECM_IDLE RRC_IDLE Tracking Area Cell Reselection
Registered
EMM_ ECM_ RRC_

Cell Handover
Registered Connected Connected

Paging and Idle Mode DRX

DTX and DRX for LTE
DTX/DRX means that the UE transceiver is switched off for some predefined time
periods
E-UTRA RRC
Air interface is
switched off Connected Mode
for time
periods
eNode B
Idle Mode
This saves power on one side but might UE specific DRX
have the following consequences configured by NAS
Longer call setup time
Lower user throughput achievable

DTX and DRX for LTE
DTX/DRX options according 3GPP
In Idle mode for Paging
This means that the UE is listening to page messages in predefined time opportunities
only and sleeping all other time
Supported in RL10 DTX/DRX
Not
supported in
RL10 E-UTRA RRC
Connected Mode
In connected mode no DTX/DRX
UE is switched off for predefined time interval
Not supported in RL10
Idle Mode
DTX/DRX UE specific DRX
supported in configured by NAS
RL10

DRX for Paging
The UE may use DRX in idle mode in order to reduce power consumption
One Paging Occasion (PO) is a sub-frame where P-RNTI may be transmitted on the
PDCCH addressing the page message
One Paging Frame (PF) is a radio frame, which may contain one or several Paging
Occasions
When DRX is used the UE needs to monitor just one PO per DRX cycle

Paging Related Parameters in RL20
Default paging cycle defPagCyg (LNCEL, 32rf/64rf/128rf/256rf, 128rf)
Defines the cell specific paging DRX cycle duration
Value 32rf corresponds to 32 radio frames, 64rf corresponds to 64 radio frames and so on
One radio frame corresponds to 10ms in time
Increasing the parameter value saves battery capacity in idle mode as listening to paging is less
frequent. But the call setup time is getting longer due to longer average paging time
Optionally an UE specific paging cycle length might be signaled by the core network. In this case the
UE follows the shorter of the two cycles
Number of paging occasions pagingNb (LNCEL,

oneT/halfT/quarterT/oneEighthT/oneSixteenthT/oneThirtySecondT, quarterT)
Defines the number of possible paging occasions per radio frame, i.e. the density of paging occasions
Used to calculate the number of paging occasions within one paging DRX cycle, which in turn is used
to calculate the paging occasions
Example: quarterT means that there is one page occasion every 4th radio frame

Page Counters
M8008C1
Number of RRC paging requests
M8008C2
Number of discarded paging requests
Updated when the maximum number of paging records is S1
reached for the next paging occasion that corresponds to M 8008 C1C3 paging messages
the paging request
RRC allows up to 16 paging records per paging occasion S1
M8008C3
Number of transmitted RRC paging messages
M8008C2
cell
cell
cell
M8008C1 M8008C3

Page KPIs
E-UTRAN RRC Paging Discard Ratio
Describes the paging request discard ratio on RRC level
Summarization
Logical formula formula (PI ID) Summarization formula (Abbreviation)
Paging DCR = 100% * sum([M8008C2]) 100% * sum([DISC_RRC_PAGING]) / sum
(discarded RRC paging / sum([M8008C1]) ([RRC_PAGING_MES])
records / transmitted
RRC paging records) *
100%

Page KPIs
700,000
100.00
600,000
80.00
500,000
60.00
400,000
300,000
40.00
200,000
20.00
100,000
0.00 0
29.05.2011
17.06.2011
23.05.2011
25.05.2011
27.05.2011
31.05.2011
02.06.2011
04.06.2011
06.06.2011
09.06.2011
11.06.2011
13.06.2011
15.06.2011
19.06.2011
21.06.2011
LTE_5122a Paging Messages (#) LTE_5031aPaging Discard Ratio (%)

RACH Procedure

Overview
Physical Random Access Channel PRACH

UE already knows
PRACH preamble randomly selected MIB/SIB allocation
Random Access phase
retransmission on higher power level if not successful RACH procedure can start.

Physical Control Format Indicator Channel PCFICH UE waits for the Random Access
Response parameter. Therefore it
Number of OFDM symbols (1,2, or 3) for PDCCH
checks the PCFICH/PDCCH for the
Physical Downlink Control Channel PDCCH parameter allocation.
If not successful, the UE repeats the
UL & DL Resource Allocation + TPC; resources for RACH preamble with more power
Random Access response until the parameters are received.
Physical DL Shared Channel PDSCH These give the ID of the received
preamble, resources for UL, the C-
Random Access Response RAR: RNTI as local identity of the UE in
ID of received preamble, resource for UL Tx, C-RNTI & TA the cell and the TA.
Physical UL Shared Channel PUSCH Contention Resolution:

all other UEs
RRC Connection Request, C-RNTI, TMSI or random number
not receiving the right
answer (TMSI)
Physical DL Shared Channel PDSCH
restart Random
Contention Resolution: C-RNTI & TMSI or random number Access

RACH Usage
WCDMA RACH usage
Initial network access
Short message transmission
LTE RACH usage
Initial network access
Not for user data, which is exclusively sent on the Physical Uplink Shared Channel (PUSCH). One
exceptional case is that an UL synchronized UE is allowed to use the RACH to send a Scheduling
Request (SR) if it does not have any other UL resource allocated in which to send the SR.
Achieve uplink time synchronization for a UE which either has not yet acquired, or has lost its uplink
synchronization
UE in RRC_CONNECTED state, but not UL synchronized, needing to send new UL data or control
information (e.g. an event-triggered measurement report)
UE in RRC_CONNECTED state, but not UL synchronized, needing to receive new DL data, and
therefore to transmit corresponding ACK/NACK in the UL
UE in RRC_CONNECTED state, handing over from its current serving cell to a target cell
Transition from RRC_IDLE state to RRC_CONNECTED, for example for initial access or tracking
area updates
Recovering from radio link failure
Once UL synchronization is achieved for a UE, the eNodeB can schedule orthogonal uplink transmission
resources for it

Preamble Location
RACH operation uses around 1.08 MHz bandwidth equal to 6 resource blocks of 180 kHz
The location of those resource blocks is dynamically defined by two RRC Layer Parameters
PRACH configuration index prachConfIndex (LNCEL, 3..8/19..24, 3) defines allowed system frame and
sub-frame numbers for RACH attempts
PRACH frequency offset prachFreqOff (LNCEL, 0..94, 3) defines first physical resource block available
for PRACH in the UL system frequency band
PRACH only carries the preambles and is used during the RACH process
307200 Ts
CP Preamble
TCP TPRE TGT
Cyclic prefix Preamble Guard time

0.1 ms 0.8 ms 0.1 ms

Preamble Generation
While WCDMA offers 16 different preambles only, for LTE 64 preambles are available,
reducing the collision probability
The preambles are generated by so-called Zadoff-Chu-Sequences, generating quasi-
orthogonal pseudo-random number sequences
iMn( n 1) / N
Z (n) e
N = length of code (1..839) defines maximum desired cell radius
configured by operator
M = code number (0..63) distinguishes between users
random selected by UE
n = running number (0..N-1)
Z(n) = pseudo random number

Preamble Generation
Preamble transmission time within PRACH frame = 800 s
800
Transmission time of code with length N = N s (e.g. N = 839 800 )
839
839
Number of preambles per PRACH frame = (e.g. N = 839 1 preamble)
N
Large cell
Long code to ensure orthogonality
Few preambles per PRACH frame
Many collisions between users
Small cell
Short code required only
Many preambles per RACH frame
Few collisions between users

Preamble Generation
The code length N is configured by the parameter PRACH cyclic shift prachCS (LNCEL, 0..15,
1)
The parameter offers 16 options according the table below (the restricted set intended for fast
moving UE is not supported by RL10)
839
16 options

PRACH Power Ramping
Initial PRACH power
PPRACH = min { Pmax, PREAMBLE_RECEIVED_TARGET_POWER + PATHLOSS}
If no response for initial preamble, power ramping like in case of WCDMA
prachPwrRamp
Power ramping step
BCH information LNCEL
0/2/4/6 dB
UE sets the initial transmission power of
2 dB
RACH and send preamble signal
Preamble (RACH) preambTxMax

Preamble transmission maximum
Preamble (RACH)
LNCEL
Preamble (RACH) 3..8/10/20/50/100/200
8
PDCCH
Random access message

(UL-SCH) ulpcIniPrePwr
Preamble Initial received target power
LNCEL
-120..-90 dBm in steps of 2 dB
-104 dBm
PRACH Counters
M8001C6
Number of RACH setup attempts for small size messages
Update when eNodeB receives group A preamble
M8001C7
Number of RACH setup attempts for small size messages
Updated when eNodeB receives group B preamble
M8001C8
Number of RACH setup completions
Updated when eNodeB sends preamble response
M8001C6
M8001C8
M8001C7

TA Synchronization and Cyclic Prefix

LTE FDD Frame Structure
FDD Frame structure (also called Type 1 Frame) is common to both UL and DL
Divided into 20 x 0.5 ms slots
Structure has been designed to facilitate short round trip time
Frame length =10 ms

1 Frame = 10 sub-frames of 1 ms
each
1 Frame = 20 slots of 0.5 ms each
0.5 ms slot
1 slot = 7 (normal CP) or 6
sy0 sy1 sy2 sy3 sy4 sy5 sy6
symbols (extended CP)
10 ms frame
s0 s1 s2 s3 s4 s5 s6 s7 .. s18 s19
SF: SubFrame
s: slot
0.5 ms slot
Sy: symbol
SF0 SF1 SF2 SF3 .. SF9

1 ms sub-frame
Subframe Structure and CP length
Subframe length is 1 ms for all bandwidths
Slot length is 0.5 ms
1 Subframe = 2 slots
Slot carries 7 symbols with normal cyclic prefix or 6 symbols with long prefix
CP length depends on the symbol position within the slot
Normal CP: symbol 0 in each slot has CP = 160 x Ts (5.21s) and remaining symbols
have CP = 144 x Ts ( 4.7s)
Extended CP: CP length for all symbols in the slot is 512 x Ts (16.67s)
Ts: sampling time of the overall

channel
Short cyclic prefix:
Basic Time Unit
5.21 s
Ts = 32.5 ns
Long cyclic prefix:
1 sec
16.67 s Ts =
= Data
Subcarrier spacing X max FFT size
= Cyclic prefix Copy

Timing Advance Principle
UE 2
UE 1
a) UE Tx timing
D = 16 Ts
UE 1
UE 2
b) eNB Rx timing
UE 1
UE 2
Timing Advance UE 1 time
Timing Advance UE 2
Timing Advance Procedure
eNB measures the required timing advance based on the received UE signal arrival time
It commands the UE to adjust the transmission time. This is performed on a per-need basis
TA is signaled by means of a special MAC control element (LCID = 11101)
The signaled granularity is 16 Ts
The value range for adjustment is 6 bit and related to the current UL timing
As Ts = 1 / (2048 x 15000) sec = 1 / 30720000 sec the granularity is given by 0.52 sec
If UE is in-sync the timing advance is valid
Otherwise the RACH procedure establishes a valid timing advance
An 11 bit value (range 0..1282) is signaled to establish the initial offset
Maximum cell radius is 100 km Timing Advance TA

1 step corresponds to 78 m 11 bit TA command within Random
1282 steps correspond to 100 km Access Response
1282 * 0.52 us * speed of light = 100 km TA range 0.52 s .. 0.67 ms
0.67 ms corresponds to 100 km
TA update vendor specific

RRC Setup Procedure

Call Setup Overview
Core/IMS
UE
Physical Random Access Channel S1
PRACH preamble E-Node B MME

Idle to active
RRC phase
TA, scheduling, ID
RRC connection request
First KPI (like for WCDMA)
RRC connection setup
RRC setup success
RRC connection setup complete
NAS service request encapsulated in

connection service
Call & service setup
RRC connection setup complete

request
Connection setup
NAS phase
Security check/command encapsulated in

RRC connection reconfiguration
RRC connection
Reconfiguration complete
SIP invite
SIP session

process Terminating
SIP OK / ringing UE

RRC Connection Setup Overview (Positive)
UE
S1
E-Node B
Idle to active RRC phase
MME
M8013C17:SIGN_CONN_ESTAB_ATT_MO_S
M8013C18:SIGN_CONN_ESTAB_ATT_MT
RRCConnectionRequest M8013C19:SIGN_CONN_ESTAB_ATT_MO_D
1 M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS
M8013C21:SIGN_CONN_ESTAB_ATT_EMG
M8007C7: SRB1 setup attempts

2 RRCConnectionSetup
3 RRCConnectionSetupComplete M8007C8: SRB1 setup completions
(with encapsulated M8013C5: Signaling connection

NAS phase
NAS message) establishment completions
M8007 Radio Bearer Measurements

M8013 UE State Measurements

RRC Connection Setup Overview (Positive)
UE
S1
E-Node B
Idle to active RRC phase
MME
M8013C17:SIGN_CONN_ESTAB_ATT_MO_S
M8013C18:SIGN_CONN_ESTAB_ATT_MT
RRCConnectionRequest M8013C19:SIGN_CONN_ESTAB_ATT_MO_D
1 M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS
M8013C21:SIGN_CONN_ESTAB_ATT_EMG
M8007C7: SRB1 setup attempts

3 RRCConnectionSetupComplete
(with encapsulated
NAS phase
NAS message)

RRC Connection Request (Negative)
UE
S1
E-Node B MME
RRCConnectionRequest
1
RAC accepts or
rejects RRC M8013C8
Connection Request
Signaling connection establishment
2 RRCConnectionReject
failures due to rejection by RRM RAC
UE stays in Idle Mode

RRC Connection Setup (Negative)
UE eNB MME
1 RRCConnectionRequest
M8013C6
3 Missing RRCConnectionSetupComplete Signaling connection establishment
failures due RRC setup completions
missing
Does NOT trigger M8007C9/C12 !!

RRC Connection Setup (Negative)
UE eNB MME
1 RRCConnectionRequest
M8013C7
3 Erreneous or Incomplete Signaling connection establishment
RRCConnectionSetupComplete
failures due RRC setup completions
error
Triggers also M8007C9/C12
SRB1/2 setup failures

RRC Connection Setup Counter Summary
M8013C8
M8013C6
M8007C9/C12
M8013C7
At least:
M8007C8/C11 from all attempts
M8007C7/C10 M8013C5 minus rejects =
M8007C8/11 * 100 = Success setup ratio
M8007C7/10)
Rejections by RRM Missing/wrong

RAC completions
Setup attempts Successful setups

RRC Connection Setup KPIs
E-UTRAN RRC Connection Setup Success Ratio
Shows the setup success ratio for the elementary procedure "RRC connection
establishment" used to set up a radio connection from UE to eNB
Summarization
RCC Con SSR = (RRC 100 * sum ([SIGN_CONN_ESTAB_COMP]) / sum

connection setup ([SIGN_CONN_ESTAB_ATT_MO_S]+
completions / RRC [SIGN_CONN_ESTAB_ATT_MT]+
connection requests) * [SIGN_CONN_ESTAB_ATT_MO_D]+
100% [SIGN_CONN_ESTAB_ATT_OTHERS])

100.00 25,000
80.00 20,000
60.00 15,000
40.00 10,000
20.00 5,000
0.00 0
25.05.2011
15.06.2011
23.05.2011
27.05.2011
29.05.2011
31.05.2011
02.06.2011
04.06.2011
06.06.2011
09.06.2011
11.06.2011
13.06.2011
17.06.2011
19.06.2011
21.06.2011
LTE_5232a RRC Connection Establishment attempts due to MO-Signalling (#)
LTE_5233a RRC Connection Establishment attempts due to MT-Access (#)
LTE_5234a RRC Connection Establishment attempts due to MO-Data( #)
LTE_5235a RRC Connection Establishment attempts due to Others (#)
LTE_5220a RRC Success Ratio (%)
LTE_5218a RRC Connection Setup Success Ratio (%)

E-UTRAN RRC Connection Establishment Failure Ratio per Cause
Describes the ratio of a specific RRC connection setup failure cause related to
all RRC connection requests
Summarization
S1 SFR = (RRC RRC timer expiry failure (RRCCOMPL_MISSING)
Connection Setup cause
failure_x / 100 * sum ([SIGN_EST_F_RRCCOMPL_MISSING]) /
RRC Connection sum ([SIGN_CONN_ESTAB_ATT_MO_S]+
[SIGN_CONN_ESTAB_ATT_MT]+
requests) * 100%
[SIGN_CONN_ESTAB_ATT_MO_D]+
[SIGN_CONN_ESTAB_ATT_OTHERS])
Formula related to missing RRC setup completion

Other causes are
RRC protocol error (wrong RRC setup completion)
Radio access control failure (rejection by RRM RAC)

Radio Admission Control

Overview of RAC within RRM
RAC admits or rejects requests for establishment of Radio Bearers per cell based on:
Number of RRC connections per cell
Number of active users per cell RAC acts on:
Non QoS aware supported by RL10 Paging
Call establishment
request
Handover request
RAC algorithms controls

Signaling radio bearer
Data radio bearer
RAC RAC interacts

activities with Packet Packet Radio Admission control
Scheduler Scheduler
active
users configuration of
RLC layer
PDCP layer
eNode B
RAC load/data measurements
RAC
cell load
activities
measurements by UE
active active users &

# UE keeping and & users RRC connections
buffered DL/UL
measurements
eNode B
M8001C223 average
M8001C224 maximum
measurements of
UE's with data buffered (DL/UL) active users cell
M8001C147/150 average cell
M8001C148/151 maximum cell

Objective
Operator configures both maximum number of established RRC

connections and maximum number of active users per cell by O&M
threshold
RRC connection is established when the SRBs have been admitted and
successfully configured
UE is considered as active when Radio Bearer is established
Upper bound for maximum number of supported connections depends on
the BB configuration of eNB
RL T: All RRC connection setup request are admitted by default to

avoid RAC complexity
RL10: Possibility of giving priority to incoming HO based on the
HO cause
45 Nokia Siemens Networks Presentation

RA4133/ Author
EN20GLA0
/ Date
Controlled Services
RAC acts on the basis of events like:

Paging
Call establishment request
Handover request
RAC algorithms controls establishment of
Signaling radio bearer
Data radio bearer
RAC applies different criteria for call establishment and
mobility (HO)
Offset in terms of the number of RRC connections or active users
used
Aim is to keep the already established sessions active and support
user mobility

Interaction with other RRM Entities
RAC interacts with other RRM entities

Mobility management
Radio Bearer Management
UE State Management
RAC interacts with Packet Scheduler
RAC supports configuration of
RLC layer
PDCP layer

Interaction with other RRM Entities

RAC Parameters
Maximum number of RRC connections maxNumRrc (LNCEL, 0..800, 380)
Default value is for 10 MHz bandwidth
For 5 and 20 MHz bandwidth default is 190 and 760, respectively
Maximum number of active UEs maxNumSctUe (LNCEL, 0..800, 80)
Default value is for 10 MHz bandwidth
For 5 and 20 MHz bandwidth default is 40 and 160, respectively
Maximum amount of users per TTI on UL/DL (LNCEL, 1..10, 7)
Range is for 10 MHz bandwidth
For 5 and 20 MHz bandwidth range is 1..7 and 1..20, respectively

RA4133/ Author
EN20GLA0
/ Date
RAC Counters
Number of UEs monitored by cell load measurements
Number of active UE per cell
M8001C223 average
M8001C224 maximum
Number of UE with data buffered on DL
M8001C147 average
M8001C148 maximum
Number of UE with data buffered on UL
M8001C150 average
M8001C151 maximum
LTE 800 24 hour report

On cell level

RA4133/ Author
EN20GLA0
/ Date
Thank You !
51 Nokia Siemens Networks RA4133EN20GLA0

05 RA4133 RL20 LTE Paging and RRC Connection E01

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

05 RA4133 RL20 LTE Paging and RRC Connection E01

Hochgeladen von

Copyright:

Verfügbare Formate

LTE Radio Performance Management

1 Nokia Siemens Networks RA4133 EN20GLA0

Paging and RRC Connection

After completing this learning element, the

Explain idle and connected states within LTE

2 Nokia Siemens Networks RA4133 EN20GLA0

Idle and Connected States within LTE

3 Nokia Siemens Networks RA4133 EN20GLA0

UTRA RRC Connected Mode

UE in DRX mode UE in DRX mode

Dedicated resources Common resources

4 Nokia Siemens Networks RA4133 EN20GLA0

E-UTRA RRC Connected Mode In LTE one distinguishes just between

EMM states in UE EMM states in MME

EMM-DEREGISTERED EMM-REGISTERED EMM-DEREGISTERED EMM-REGISTERED

Attach accept Attach accept

6 Nokia Siemens Networks RA4133 EN20GLA0

EMC states in UE ECM states in MME

ECM-IDLE ECM-CONNECTED ECM-IDLE ECM-CONNECTED

RRC Established S1 Established

ECM Connected = RRC Connected + S1 Connection

EMM state ECM state RRC state UE Location Mobility

EMM_ ECM_ RRC_

8 Nokia Siemens Networks RA4133 EN20GLA0

Paging and Idle Mode DRX

9 Nokia Siemens Networks RA4133 EN20GLA0

10 Nokia Siemens Networks RA4133 EN20GLA0

11 Nokia Siemens Networks RA4133 EN20GLA0

12 Nokia Siemens Networks RA4133 EN20GLA0

Number of paging occasions pagingNb (LNCEL,

13 Nokia Siemens Networks RA4133 EN20GLA0

14 Nokia Siemens Networks RA4133 EN20GLA0

15 Nokia Siemens Networks RA4133 EN20GLA0

16 Nokia Siemens Networks RA4133 EN20GLA0

17 Nokia Siemens Networks RA4133 EN20GLA0

Physical Random Access Channel PRACH

Physical UL Shared Channel PUSCH Contention Resolution:

18 Nokia Siemens Networks RA4133 EN20GLA0

19 Nokia Siemens Networks RA4133 EN20GLA0

TCP TPRE TGT

Cyclic prefix Preamble Guard time

20 Nokia Siemens Networks RA4133 EN20GLA0

21 Nokia Siemens Networks RA4133 EN20GLA0

22 Nokia Siemens Networks RA4133 EN20GLA0

23 Nokia Siemens Networks RA4133 EN20GLA0

Preamble (RACH) preambTxMax

Random access message

25 Nokia Siemens Networks RA4133 EN20GLA0

TA Synchronization and Cyclic Prefix

26 Nokia Siemens Networks RA4133 EN20GLA0

Frame length =10 ms

27 Nokia Siemens Networks RA4133 EN20GLA0

Ts: sampling time of the overall

28 Nokia Siemens Networks RA4133 EN20GLA0

Timing Advance UE 1 time

Maximum cell radius is 100 km Timing Advance TA

30 Nokia Siemens Networks RA4133 EN20GLA0

RRC Setup Procedure

31 Nokia Siemens Networks RA4133 EN20GLA0

PRACH preamble E-Node B MME

NAS service request encapsulated in

RRC connection setup complete

Security check/command encapsulated in

32 Nokia Siemens Networks RA4133 EN20GLA0