02 LTE Signaling and Protocols

LTE Signaling and Protocols
www.huawei.com
Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Daily Life of a Smart Phone
Paging
Power procedure
Power
on TAU procedure of
When you are
free
Detach
Procedur
e
Dedicated Bearer Procedure
Initial
Handover Procedure
attachmen
t When you are busy

Page2
Objective
After completing this course, you will be able to :
Describe LTE protocol stacks and basic functions
Outline UE network access process
Describe Dedicated bearer setup, modification, and release procedur
es
Describe paging process
Describe TAU process
Describe handover procedures and scenarios
Describe detach process and scenarios

Page3
Contents
1. Basics for LTE Signaling and Protocols
2. UE Power on and Attach Procedure
3. Dedicated Bearer Procedure
4. Paging Procedure
5. TAU Procedure
6. Handover Procedure
7. Detach Procedure

Page4
LTE/EPC Network Architecture
PCRF
S6a
HSS
Rx
Gx
S11
MME
S1-C S5 SGi Operators
S1-U IP Service
E-UTRAN S-GW PDN-GW
E-UTRAN: consists of eNodeBs, which integrate function of UTRAN/BSS

used in UMTS/GSM networks, it mainly controls the radio resource.
MME: provides functions such as mobility management, UE
identification, and security.
S-GW: terminates the S1 interfaces to E-UTRAN.
P-GW: terminates the SGi interface to PDN.

Page5
Control Plane Protocol Stack
RRM and RRC functionality ar

e moved from RNC/BSC to e
NodeB

Page8
User Plane Protocol Stack

Page9
UE ID in Bearers and Protocol Stacks
Identity of user plane
EPS bearer identity
The EPS bearer identifier identifies an EPS bearer when the UE attaches to the E-
UTRAN.
EPS bearer identifiers are allocated by the MME.
There is a one-to-one mapping between radio bearers and EPS bearers, and the m
apping is provided by the E-UTRAN.
Identity of control plane
eNB UE S1AP ID: Uniquely identifies a UE over the S1 interface within an eNodeB.
MME UE S1AP ID: Uniquely identifies a UE over the S1 interface within the MME.
Old eNB UE X2AP ID: Uniquely identifies a UE over the X2 interface within the source
eNodeB.
New eNB UE X2AP ID: Uniquely identifies a UE over the X2 interface within the target e
NodeB.

Page10
UE ID in EUTRAN(AS Layers)
RNTI(Radio Network Temporary Identifier): consists of 32 bits
Type Scenario How to Acquire Valid Rage
Used to identify the Based on the RACH
RA-RNTI random access preamble location within a cell
response 0001~003C
Used to identify the
Temporar UE before contention eNodeB assign it in random
y resolution during access response message within a cell
C-RNTI random access 003D~FFF3
procedure
eNodeB assign it after RRC
Identify RRC
C-RNTI connection setup within a cell
connected UE
003D~FFF3
Indentify the UE when eNodeB assign it when
SPS-
adopt semi-persist enter the SPS mode within a cell
CRNTI
scheduling (003D~FFF3)
Identify the paging Whole
P-RNTI FFFE(Fixed)
message scheduling network
Identify the SIB Whole
SI-RNTI FFFF(Fixed)
message scheduling network

Page11
UE ID in EPC (NAS Layer)
Type Name Source Function
International
Unique UE ID, used for the UE
IMSI Mobile Subscriber USIM
authentication
Identity
Temporary Mobile Temporary UE ID in specific MSC

MSC
TMSI Subscriber server, used to replace IMSI for
server
Identity security
packet temporary Temporary UE ID in specific

P-TMSI mobile subscriber SGSN SGSN, used to replace IMSI for
identity security
Globally Unique
Global temporary UE ID, used to
GUTI Temporary MME
replace IMSI for security.
Identifier
Shortened form of the GUTI to
SAE Temporary
enable more efficient radio
S-TMSI Mobile Station MME
signalling procedures(e.g. paging
Identifier
and Service Request)

Page12
GUTI Composition and Related Concepts
The GUTI is allocated when the UE performs initial regi
stration(i.e.Attach) with an MME, and is then typically
changed whenever the UE performs some EMM-proce
dure such as TA Update.
GUMMEI
MMEI
GUTI
12 bits 8~12 bits 16 bits 8 bits 32 bits
S-TMSI

Page13
Contents
2. UE Power-on and Attach Procedure
4. Paging Procedure
5. TAU Procedure
7. Detach Procedure

Page14
General Procedure after UE Power-on
PLMN selection (cell search): After a UE is powered on, the UE
searches and registers with a PLMN for downlink synchronizatio
n.
System information reception: The UE performs admission an
d camping only after layers 1 and 2 are configured.
Random access: The eNodeB coordinates contentions between
UEs for uplink synchronization.
Attach: After a UE attaches to the network, the MME creates an
MM context and a default bearer is established between the UE a
nd the P-GW. In addition, the P-GW assigns an IP address to the
UE.
Common procedure: authentication and security mode control.

Page15
Contents
2.1 PLMN Selection
2.2 Radom Access
2.3 Basics for Attach Procedure
2.4 Attach Procedure

Page16
PLMN Selection Procedure
Inter-layer
message
within UE
Inter-lay
message
within UE
Invisible Partial Visible

visible

Page17
PLMN Selection
When UE is powered on, it firstly selects the last RPLMN
RPLMN
and attempts to register on that PLMN. If it fails to do th
EPLMN
at ,UE attempt to register the other PLMNs with followin If present
High priority
g order: EHPLMN

The EHPLMN with the highest priority if the EHPLMN list is (if present)
present and not empty, or the HPLMN if the EHPLMN list is

HPLMN
not present, or is present and empty.

Each combination of PLMN with radio access technology (R
AT) in the "User Controlled PLMN Selector with Access Tech UPLMN
nology" data file in the USIM, in order of priority.

Each combination of PLMN with RAT in the "Operator Cont OPLMN
rolled PLMN Selector with Access Technology" data file in t
he USIM, in order of priority. Other PLMN

Other combinations of PLMNs with RATs providing high-qu
ality signals, in a random order.

Page18
Q&A
Q1: When a UE moves to a different country, two VPLMNs a
re available for GSM and LTE services. In addition, roaming
is available between the HPLMN and these VPLMNs. In this
case, which PLMN will the UE register with?
Q2: What role does the EPC play in PLMN selection?

Page19
Contents
2.1 PLMN Selection
2.1.1 Cell Search
2.1.2 System Information Reception
2.1.3 Cell Selection
2.2 Radom Access


Page20
Page21
BCCH
decodin
MIB&SIB reception g
RS
measure
RSRP/RSRQ ment
SSS
decodin
Frame synchronization
g
Obtain PCI
PSS
decoding
Slot synchronization
Cell Search Procedure
Synchronization Signals
UEs perform synchronization and obtain PCIs using synchronization signals.
PCI = 3 x Physical cell group ID ( N (1) ) + Cell ID (
(2))
ID N ID
Synchronization signals are classified into the primary synchronization signal (PS
S) and secondary synchronization signal (SSS).
Position in the time and frequency domains:
Time domain: The PSS and SSS have different positions in the time domai
n for LTE FDD and TDD .
Frequency domain: The PSS and SSS are located in the middle of the freq
uency domain.
Sequence:
PSS: Zadoff-Chu sequence
SSS: binary M-sequence

Page22
Functions of PSS and SSS
PSS
Provides downlink synchronization information for UEs. Each PS
S uses one of the three ZC sequence types, and different ZC seq
uences are used for neighboring cells or sectors.
These three ZC sequences are mapped to three different Cell ID
s.
Value range: 0,1,2
SSS
Enables the UE to perform accurate synchronization and carries
the physical cell group ID.
Value range: 0~167

Page23
Synchronization Channel: Cell Search and Dow
nlink Synchronization
PSS and SSS Location for FDD

Page24
Synchronization Channel: Cell Search and Dow
nlink Synchronization
PSS and SSS Location for TDD

Page25
Contents
2.1 PLMN Selection
2.1.1 Cell Search
2.2 Radom Access


Page26
System Information Reception Process
Why is the system information reception procedure required ?
The UE configures each layers parameters based on the parameter s
ettings in the system information received on the RRC layer before re

questing network camping and admission.
What information does the system information contain ?
One master information block (MIB) and 13 system information bloc
ks (SIBs), including UE parameters set by the eNodeB.
How is the system information

received ?
The figure in the right shows
procedure the system information is
received.

Page27
MIB Mapping & Delivery
MIB introduction
Carried by BCCH->BCH->PBC
H
Deliver very basic system info
rmation, including system fra MIB block
me number, DL bandwidth an
d PHICH configuration Coded block
Broadcast period: 40ms
Radio
4
frame
symbols
1 2 3 4 5 6 0 1 2 3 4 5 6
SSS PSS PBCH

40ms PBCH TTI
PBCH Location(FDD)

Page28
MIB Mapping & Delivery
MIB introduction
Carried by BCCH->BCH->PBC
H
Deliver very basic system info
rmation, including system fra MIB block
me number, DL bandwidth an
d PHICH configuration Coded block
Broadcast period: 40ms
Radio
4
frame
symbols
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1 2
PBCH SSS PSS
40ms PBCH TTI
PBCH Location(TDD)

Page29
SIB Mapping & Delivery
SIBs are mapping on BCCH->DL-SCH-> PDSCH:
SIB1 and SIB2 are mandatory, and others are optional.
Period of SIBs
SIB1: 80ms
From SIB2 to SIB8, SIB10 and SIB11: It is a flexible period, wit
h 80,160,320,1280,2560 and 5120ms.

Page30
SIB Information
Type Contents
Cell selection and camp related parameters SI period
SIB1
for other SIBs
Common physical channel configuration, UE timer, uplink
SIB2
bandwidth
SIB3 Common parameters for cell reselection
Intra-frequency neighbor list; Neighbor reselection
SIB4
parameters; Neighbor black list
Inter-frequency list and corresponding cell reselection
parameters
SIB5 Inter-frequency neighbor list and corresponding cell
reselection parameters
SI
Inter-frequency black list
SIB6 UMTS frequency list
SIB7 GSM frequency list
SIB8 CDMA2000 frequency list and neighbor list
SIB9 Home eNodeB information
SIB10 ETWS primary notification
SIB11 ETWS secondary notification
SIB12 CMAS notification
SIB13 MBMS control information

Page31
System Message Tracing Cases
MIB
SIB1
SI
MCC:460
Other SIBs MNC:01

excluding SIB1
and SIB2
TAC:21
Cell ID:7B8FF
Cell is not barred
Intra-freq
Reselection is
allowed
-128dBm, value range:
INTEGER ( 70
22

Page32
Q&A
Please list the type of system message
What are the major information included in each message?
Which message delivers system downlink and uplink band

width?

Page33
Contents
2.1 PLMN Selection
2.1.1 Cell Search
2.2 Radom Access


Page34
Cell Selection and Camping

Page35
Cell Selection Criteria
Criteria for cell selection: Srxlev and

Squal

Page36
Contents
2.1 PLMN Selection
2.1.1 Cell Search
2.2 Radom Access


Page37
Random Access Overview
Purpose of random access
Get uplink synchronization
Acquire uplink scheduling resource
Scenarios:
Case1: UE initial attach
Case2: RRC reestablishment after RRC drops
Case3: Handover to a new cell
Case4: Downlink data arrival in eNodeB when UL out-of-sync occurs
Case5: Uplink data detected by UE when UL out-of-sync occurs
Case6: When UE trigger LCS(Location service)

Page38
Classification of Random Access
Contention based Non-contention based
UE randomly selects a pream Before random access,

ble and sends it, conflict migh eNodeB assigns a
t occurs. dedicated preamble to UE,
(Case1, Case2 and Case5) so there is no conflict.
(Case3, Case4 and Case6)

Page39
Random Access
Signaling Flow
UE sends RA Preamble carrying

RA-RNTI and eNodeB decode the
preamble and get RA-RNTI
eNodeB sends RA Response with RA-RNTI it

decoded from the preamble.
UE decode the RA Response and gets RB
Assignment and MCS configuration and
configures itself with this information to
receive RRC Connection Request via DCI
Format 0
UE sends RRC Connection Request using
TC-RNTI it got from RA Response
Contention based UE receives RRC Connection Setup using
TC-RNTI it got from RA Response
This RRC Connection Setup message
carries CRNTI
From this point, UE and network exchange
Notes message with the CRNTI
Real line: L3 messages
Dash line: L1 & L2 messages

Page40
Contents
2.1 PLMN Selection
2.2 Radom Access
2.3.1 Status of Protocol Layer
2.3.2 Connection Management Overview
2.3.3 Signaling Messages

Page41
RRC Status & Transition
RRC_IDLE mode: No RRC connection is established for a UE.
DRX enabled to reduce UE power consumption
Monitoring of paging channels
No RRC context
Neighboring cell measurements No data transfer
and cell reselection RRC IDLE Cell reselection
Reception of paging and
System information detection system information messages
Periodic TAU
RRC_CONNECTED: An RRC
RRC connection RRC connection
connection is established for a
setup release
UE.
Mobility management RRC context information available
Data transfer in the uplink and (specified by the C-RNTI)

RRC Data transfer
downlink CONNECTE Handover
Channel quality and feedback D PDCCH and SI reception
CQI and feedback information
information provision provision
DRX activation

Page42
NAS States
NAS states include:
EMM state

EMM state: Indicates whether the UE is registered in
the MME.
ECM state: Indicates whether a NAS connection is es
tablished between a UE and MME. The ECM is valid o
nly in the EMM-REGISTERED state.
ESM state

Indicates whether an EPS bearer is available.

Page43
EMM and ECM States
Detach
Attach request rejected
TAU rejected
E-UTRAN interface disabled after a UE is
handed over to a non-3GPP RAT
All bearers removed
EMM-DEREGISTERED EMM-REGISTERED In UEs
Attach request accepted
EMM state Detach

switching Attach request rejected
TAU rejected
All bearers removed
In the MME
EMM-DEREGISTERED EMM-REGISTERED
Attach request accepted
TAU request accepted
when the UE moves from
GERAN or UTRAN to E-
UTRAN
RRC connection release
ECM-IDLE ECM-CONNECTED In UEs
RRC connection setup
ECM state
switching S1 connection release
ECM-IDLE In the MME
ECM-CONNECTED
S1 connection
establishment

Page44
NAS States Transition
ESM-ACTIVE EMM-REGISTERED
PDN context EMM context:
IP address, APN, and QoS IMSI, GUTI, and TA list
parameter IP address and security
S5 IP address and TEID connection
S11 IP address and TEID
(S1-U IP address and ECM-IDLE
TEID)
No NAS connection
Data transport is available TAU
for a UE in the ECM-
CONNECTED state. NAS NAS connection
connection release
One default bearer setup
No, one, or more
ECM-CONNECTED
NAS connection
dedicated bearers
available
Data transport
The last EPS EPS bearer available
bearer is setup Detac Attac
released. h h
ESM-INACTIVE EMM-
No PDN context DEREGISTERED
No EMM context

Page45
NAS Procedures-EMM

Page46
NAS Procedure - ESM
ESM Procedures
Default EPS Bearer Context
Activation
Dedicated EPS Bearer Context
Activation
EPS Bearer Context Modification
EPS Bearer Context Deactivation
UE Requested PDN Connectivity
UE Requested PDN Disconnect
UE Requested Bearer Resource
Allocation
UE Requested Bearer Resource
Modification
ESM Information Request
ESM Status

Page47
Relationship Between RRC Status and
NAS Status
2:Idle/ Connecting to
1:Off Attaching 3:Active
Registered EPC
EMM DEREGISTERED REGISTERED
ECM IDLE CONNECTED
RRC IDLE CONNECTED IDLE CONNECTED

Page49
Contents
2.1 PLMN Selection
2.2 Radom Access

Page50
Connection Management
In an LTE system, connection m
anagement is performed over t UE eNodeB MME S-GW
he connectivity between the UE NAS events (such
Paging
as Paging
and eNodeB and that between Response) trigger
RRC connection
MMEs. It includes establishmen Random access procedure
t of user- and control-plane con RRC connection establishment

nections: Signaling S1 signaling
connection
connection
Control-plane connection est establishment establishment
ablishment: also known as sign Security mode control

aling connections, including RR
C connections and S1 signaling E-RAB establishment
connections E-RAB release & signaling connection release
User-plane connection establ
ishment : also known as E-RAB Connection management process
setup

Page51
Signaling Connection Establishment
In most cases, signaling
connections are establis RRC
connection
hed to facilitate service (Uu interface)
bearer establishment. Signaling
connections
In some cases, however, Dedicated S1
connection
signaling connections ar (S1 interface)
e established not for a s
ervice bearer but for a s
pecific signaling proce
ss, such as TAU.

Page53
RRC Connection
The RRC connection is a layer 3 connection between the UE and
eNodeB, and its setup is initiated by the UE.
Radio Bearer
(RB)
SRB DRB
RRC
SRB0 SRB1 SRB2

(CCCH) (DCCH) (DCCH
Bears RRC Bears RRC signaling (that Bears NAS

signaling before may include NAS signaling signaling.
the RRC messages) and NAS SRB2 is set up
connection is set signaling transmitted before after AS
up. SRB2 is set up. encryption.

Page54
LTE DL/UL Signaling Mapping in Different Layers
Downlink Uplink

Page56
S1 Control Plane ID
How to identify the dedicated S1 message for UE?
eNodeB and MME maintain the following unique ID for each
UE to identify the different S1 dedicated link
eNB S1AP UE ID: assigned by eNodeB ( Id 5 in the example )
MME S1 AP UE ID: assigned by MME ( Id 100 in the example )

Page57
S1 User Plane ID
How to identify the dedicated S1 user data?

Tunnel ID is used on each side to identify the user plane

Page58
Contents
2.1 PLMN Selection
2.2 Radom Access

Page59
Messages Carried by SRB0/SRB2
Messages carried by SRB0
RRC Connection Reestablishment
RRC Connection Reestablishment Reject
RRC Connection Reestablishment Request
RRC Connection Reject
RRC Connection Request
RRC Connection Setup
Messages carried by SRB2
DL Information Transfer ( NAS )
UL Information Transfer ( NAS )

Page60
Messages Carried by SRB1 (1/2)
CSFB Parameters Request CDMA2000
CSFB Parameters Reponse CDMA2000
Handover From EUTRA Preparation Request ( CDMA2000 )
Measurement Report
Mobility From UTRA Command
RRC Connection Reconfiguration
RRC Connection Reconfiguration Complete
UL Handover preparation Transfer ( CDMA2000 )
DL Information Transfer ( NAS )
UL Information Transfer ( NAS )

Page61
NAS Messages Via RRC Messages
RRC Connection Setup Complete Initial NAS message
ATTACH REQUEST including PDN Connection Request
DETACH REQUEST detach triggered by UE in idle mode
TRACKING AREA UPDATE REQUEST triggered by UE in idle mode
SERVICE REQUEST
RRC Connection Reconfiguration
ATTACH ACCEPT
TRACKING AREA UPDATE ACCEPT depending on if there are services
to be established or not )
ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST
ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
The MODIFY EPS BEARER CONTEXT REQUEST

Page63
NAS Messages Via RRC Messages (Con.)
UL Information Transfer DL Information Transfer
GUTI REALLOCATION COMPLETE

AUTHENTICATION RESPONSE
AUTHENTICATION FAILURE GUTI REALLOCATION COMMAND
SECURITY MODE COMPLETE AUTHENTICATION REQUEST
SECURITY MODE REJECT AUTHENTICATION REJECT
IDENTITY RESPONSE SECURITY MODE COMMAND
ATTACH COMPLETE IDENTITY REQUEST
DETACH REQUEST Detach triggered by UE in connection ATTACH REJECT
mode DETACH REQUEST Detach triggered by EPC in
DETACH ACCEPT Detach triggered by EPC connection mode
TRACKING AREA UPDATE REQUEST triggered by UE in DETACH ACCEPT Detach triggered by UE
connection mode TRACKING AREA UPDATING REJECT
TRACKING AREA UPDATE COMPLETE TRACKING AREA UPDATE ACCEPT depending on if
ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT there are services to be established or not
ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT SERVICE REJECT
ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
MODIFY EPS BEARER CONTEXT REQUEST only modify
ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT
MODIFY EPS BEARER CONTEXT ACCEPT TFT
MODIFY EPS BEARER CONTEXT REJECT PDN CONNECTIVITY REJECT
DEACTIVATE EPS BEARER CONTEXT ACCEPT PDN DISCONNECT REJECT
PDN CONNECTIVITY REQUEST BEARER RESOURCE ALLOCATION REJECT
PDN DISCONNECT REQUEST BEARER RESOURCE MODIFICATION REJECT
BEARER RESOURCE ALLOCATION REQUEST
BEARER RESOURCE MODIFICATION REQUEST

Page64
Contents
2.1 PLMN Selection
2.2 Radom Access

Page65
Attachment Introduction
Function of attachment
The UE registers to the EPC.
During network attach, a default EPS bearer is established for alway
s-online IP connectivity.
The MME and UE construct the MM context and EPS bearer context
for the UE. The S-GW and P-GW construct the EPS bearer context fo
r the UE. The default bearer is established between the UE and the
P-GW, and the UE obtains the IP address from the P-GW.

Page66
General Procedure of Attachment
Signaling
connection
setup
(RRC and S1
dedicated
signaling)
NAS procedure
(Authentication &
NAS security)
User plane
setup
(Default EPS
bearer setup)

Page67
RRC Connection Establishment Process
During RRC connection setup, SRB1 is set up.
SRB 0 / CCCH / UL-SCH / PUSCH
SRB 0 / CCCH / DL-SCH / PDSCH
SRB 1 / DCCH / UL-SCH / PUSCH

Page68
Content of the RRC Connection Request Mess
age
Information Elements
S-TMSI
UE Identity
Random Value
Emergency
High Priority Access
Establishment Mobile Terminating Access

Cause Mobile Originating Signaling
Mobile Originating Data
Delay Tolerant Access (3GPP Release 10)

Page70
Relationship between Establishment Cau
se and NAS Procedure
RRC Establishment
NAS Procedure
Cause
Mobile Originating Signaling
Attach Attach Delay Tolerant Access
Emergency
Detach Detach Mobile Originating Signalling
Tracking Mobile Originating Signalling
Area TAU Delay Tolerant Access
Update Emergency
User plane radio resources request Delay Tolerant Access
Emergency
Service Uplink signaling resources request Delay Tolerant Access
Request Emergency
Paging response for PS core network domain Mobile Terminating Access
PDN connectivity request with cause
Emergency
emergency
Mobile originating CS fallback
Delay Tolerant Access
Extended Mobile terminating CS fallback Mobile Terminating Access
Service Mobile originating CS fallback emergency call Emergency
Request Mobile Terminating Access
Packet services via S1 Delay Tolerant Access
Emergency

Page72
RRC Connection Establishment Tracing Cases

Page74
Initial UE Message
After RRC connect establishment , eNodeB delivers the first NAS
message , which is carried by RRC Connection Setup Complete i
n Uu interface and Initial UE Message in S1 interface, to MME.
Initial UE Message includs the following NAS procedure:
EMM: Attach request
ESM: PDN connectivity request
The first UL NAS message

Page75
Initial UE Message Tracing Cases(1/2)

Page76
Initial UE Message Tracing Cases(2/2)

Page77
NAS Procedure Introduction
After UE sends the first NAS message to MME, MME initiate
s NAS procedure for authentication and NAS security

By the authentication process, a new set of cipher keys are ge
nerated.
If MME could not obtain IMSI from UEs old TMSI, then it initials U
E identity flow to let UE report its IMSI
By the security command process, MME could perform cipher
ing and integrity protection for NAS

Page78
Authentication and NAS Encryption Process
NAS messages are transparently transmitted through the eNode
B in both uplink and downlink.
Authentication
NAS security

Page79
Uplink Information Transfer
Function of the Uplink Information Transfer message
Using this message, the UE sends the NAS information or no
n-3GPP indication to the eNodeB. So NAS information to be

transported is encapsulated in this message.
When NAS information or non-3GPP indication needs to be trans
ported, the UE initializes the uplink information transfer process
by sending an Uplink Information Transfer message.
The purpose of NAS connection is to exchange signaling messag
es between UE and MME over the S1 interface. So NAS signaling i
s contained in the Initial UE Message, Downlink NAS Transfer, or
Uplink NAS Transfer message.

Page80
S1AP Identification Cases
The first DL NAS Transfer
message contains MME
UE S1AP ID mapping to
eNB UE S1AP ID to
identify a certain UEs
message in SI interface.

Page81
Initial UE Context Setup Procedure
When a UE attempts to access the network, the EPC requests the eNode
B to set up the initial context for the UE.
During the initial UE context setup procedure, the default bearer is
set up for the UE. According to 3GPP TS 23.401, the EPC allocates a d
efault bearer to the UE when the UE initially accesses the PDN. Thi
s default bearer is released only when the UE exits the PDN.

Page82
Initial UE Context Setup Procedure - Request
Its purpose is to setup necessar
y UE context including E-RAB co
ntext, security key, handover res
(SGW IP)
triction list, etc.

Page83
Initial UE Context Setup Request Case
3

Page84
Initial UE Context Setup Process - Response
IEs(Information Elements) in Initial Context Setup Response message ar
e as following:

Page85
Initial UE Context Setup Response Case

Page86
AS Security Setup
AS security comprises of the int
egrity protection of RRC signalli
ng (SRBs) as well as the cipheri
ng of RRC signalling (SRBs) and
user data (DRBs).
Integrity protect: only for
Control Plane SRB, supporti

ng AES, snow3G and Null
Ciphering: for both Control
Plane SRB and User Plane D

RB, supporting AES, snow3
G and Null

Page87
UE Capability Query Process
If no UE capability in MME, eNodeB will trigger UE capability que
ry and store it and also inform MME.
If MME already stored UE capability, it will forward to eNodeB vi
a S1 initial contexts setup request message.

Page90
UE Capability Query Tracing Cases
LTE only UE RRC UE Cap Enquiry
3GPP Release & UE category
Supported band class RRC UE Cap Info
Inter-frequency measurement capability
Features(such as ARN)
supported indicator (see 36.331)

Page91
RRC Connection Reconfiguration Process
Upon receiving an RRC Connection Reconfiguration message from the eNodeB
over the radio interface, a UE configures SRB2 and the default DRB and sends
an RRC Reconfiguration Complete message to the eNodeB.
This process is also used

for radio bearer
management during E-
RAB setup, no specific
message except for RRC
Connection
Reconfiguration
messages is used for
signaling exchange
between eNodeBs and
UEs.
Page93
RRC Reconfiguration Case SRB2&DRB Setu
p
Key IEs
radioResourceConfiguration (fo
r SRB2 and possible DRBs) d
efault bearer setup
nas-DedicatedInformation d
efault bearer setup
RRC Reconfiguration process ca
n also be used for the following
configuration
measurementConfiguration
measurement control
mobilityControlInformation
handover command

Page94
RRC Reconfiguration Case Measurement C
ontrol Message

Page95
Release Process of Signaling Connection Overvie
w
This process involves the following releases:
Release of S1 connection
Release of RRC connection, including all radio bearers and signaling connectio
ns between UEs and eNodeBs
The signaling connection release process starts in either of the following
scenarios:
The MME sends a UE Context Release Command message to the eNodeB.
The eNodeB sends a UE Context Release Request message to the MME upon d
etecting the causes such as timer expiration in the eNodeB, a handover, or ot
her radio events. In this situation, release process of signaling connection is tr
iggered when the MME responds with a UE Context Release Command messa
ge.

Page96
Release Process of Signaling Connection
Reasons for S1 Dedicated Signaling Release
1.eNodeB triggers for example, detect UE is in user inactivity for a long
time
2. eNodeB O&M system triggers
3. MME O&M system triggers
UE eNodeB MME S-GW

1. S1-AP: S1 UE Context Release Request
2.1 Release Access Bearers Request
2.2 Release Access Bearers Response
3. S1-AP: S1 UE Context Release Command
4. RRC connection release
5. S1-AP: S1 UE Context Release Complete

Page97
Release of S1 Signaling Connection
Release of S1-AP and S1-U connections
Before the S1 connection is released
MME
eNodeB S-GW P-GW
After the S1 connection is released

MME
eNodeB S-GW P-GW

Page98
Release of Signaling Connection Cases
Key IEs
MME UE S1AP ID

eNB UE S1AP ID
Cause

Page99
Q&A
Please review the major step for initial attachment.
What is the relevant ID for control plane and user plane on

each interface?

Page100
Contents
4. Paging Procedure
5. TAU Procedure
7. Detach Procedure

Page101
EPS Bearer Introduction
In the EPS, bearers are the basic QoS control unit.
An EPS bearer is used to transmit all the service flows associated with the sa
me QoS policy between a UE and an P-GW. All the service flows transmitted
on the same EPS bearer are subject to the same data transmission treatment
related to scheduling, queue management, transmission rate restrictions, an
d RLC configurations.

Page102
Default Bearers and Dedicated Bearers
In the EPS, the default bearer is set up and remains established throughout the
lifetime of the PDN connection in order to provide the UE with always-on IP con
nectivity to that PDN.
Other EPS bearers routing to the same PDN are known as dedicated bearers. D
edicated bearers can be set up or modified only upon the request of the MME,
and all the bearer-level QoS parameters are assigned by the EPC.
Service 1
(e.g. Internet)
Service 2
(e.g. P2P file Sharing) Packet flows
Service 3
(e.g. IMS-voice or MTV)

Page103
EPS Bearer Types and Associations
EPS bearer types based on the EPS bearer types based on bit rate guarantee
setup time
Default bearer Non-GBR bearers (for non-
The default bearer is a user
realtime services)
bearer that meets default Non-GBR bearers are not
QoS requirements for data allocated fixed network

and signaling. resources. They are applicable
The default bearer is set up
to non-realtime services, such
when a UE initially attaches as email, FTP, and HTTP
to the EPS. It remains services.
established to provide the UE
with always-on IP
connectivity. GBR bearers (for realtime
Dedicated bearer services)
Dedicated bearers are SAE GBR bearers are permanently
bearers used for specific allocated dedicated network

services. resources. They are applicable
All bearers except default
to realtime services, such as
bearers are dedicated voice, video, and realtime
bearers. gaming services.
Page104
QoS Architecture in EPS
QCI: QoS Class Indicator

ARP: Allocation and Retention Priority
GBR: Guaranteed Bit Rate
MBR: Maximum Bit Rate
AMBR: Aggregation Maximum Bit Rate

Page108
QoS Parameters: QCI
QCI

Value range: 1 to 9

Each EPS bearer is defined with a QCI.
The QCI determines how an IP packet on a bearer is processed
on the user plane.
Packet Packet
Resour Priorit Delay Error
QCI Example Service
ce Type y Budget Loss
(ms) Rate
1 GBR 2 100 10-2 Conversational voice
2 GBR 4 150 10-3 Conversational video
3 GBR 3 50 10-3 Realtime gaming
Non-conversational
4 GBR 5 300 10-6
voice
Non-
5 1 100 10-6 IMS signaling
GBR
Non-
6 6 300 10-6 TCP-based video
GBR
Non- Voice, video, and
7 7 100 10-3
GBR interactive gaming
Copyright 2014 Non-
Huawei Technologies Co., Ltd. All rights
8 8 300 10-6 reserved.
Page110
TCP-based video
GBR
QoS Parameters: ARP
Allocation/Retention Priority (ARP)
The ARP of a bearer is used to decide whether the requested beare
r can be established or modified and whether such a request is reje
cted when network resources are limited.
The following IEs are related to ARP:
Priority Level
Used for this decision to ensure that the request of the bearer with
the higher priority level is preferred.
Pre-emption Capability
Defines whether a bearer with a lower ARP priority level should be
dropped to free up the required resource.
Pre-emption Vulnerability
Defines whether a bearer is applicable for such dropping by a pre-e
mption capable bearer with a higher ARP priority value.

Page111
QoS Parameters: GBR and Non-GBR
GBR bearer
For a GBR bearer, a fixed amount of bandwidth resources is preserve
d, regardless of whether the resources are used or not.
Non-GBR bearer
For a non-GBR bearer, no fixed amount of bandwidth resources is pr
eserved, and therefore traffic is not ensured.

Page 112
QoS Parameters: AMBR
Aggregate Maximum Bit Rate (AMBR)
The AMBR is applicable only to non-GBR bearers.
APN-AMBR (uplink and downlink)
The APN-AMBR limits the aggregate bit rate that can be provid
ed across all non-GBR bearers related to all PDN connections o
n the same APN.
The APN-AMBR is provided by the P-GW which E-UTRAN doesn
t need
UE-AMBR (uplink and downlink)
The UE-AMBR is the aggregate maximum bit rate that is expect
ed on all the non-GBR bearers related to a UE.
The UE-AMBR is provided on the eNodeB.

Page113
AMBR Case
APN-AMBR1
Default
PGW Bearer
PDN1
PDN Context A
APN:A
UE-AMBR
PDN Context B APN-AMBR2

Default
PGW Bearer Bearer(GBR) PDN2
Dedicated
PDN Context C APN:B
APN-AMBR3 APN:C Default

PDN Context D Bearer PDN3
PGW Default
Bearer Bearer(Non-GBR) PDN4
Dedicated
APN:D
APN-AMBR4

Page114
QoS Subscription
Pre-EPS
QoS is subscribed in HLR
EPS
QoS is subscribed in HSS and PCRF

HSS for default bearers
PCRF for dedicated bearers

Page115
Setup/Modification/Release of Dedicated Beare
rs
Setup and modification of a dedicated bearer
Both can be initiated by a UE or a MME only when a UE is in connecte
d mode. That is to say, an eNodeB can not actively initiate this proces
s.
If the QoS of the default EPS bearer cannot meet service requiremen
ts, the UE can initiate the dedicated bearer setup process.
Release of the dedicated bearer
The process can be initiated by an eNodeB or a MME only when a UE
is in connected mode.

Page116
Dedicated EPS Bearer Setup Flow and Parameters

Page117
The Dedicated Bearer Setup Process
The E-RAB setup procedure is used to set up dedicated bearers. I
f the initial UE context is set up and new services are required, th
e E-RAB setup process is initiated.

Page118
Dedicated Bearer Modification Process
The E-RAB modification process is triggered if service attributes required
by the UE are modified and related parameters need to be modified.
Messages are transparently transported between UEs and MMEs if only
TFT parameters are to be modified.

Page119
Dedicated Bearer Release Process
An E-RAB release process is initiated to release an E-RAB when th
e UE completes the services carried on the E-RAB.

Page120
Dedicated Bearer Procedures Cases
Tracing in Uu interface
Tracing in S1 interface

Page121
Q&A
Which two parts does an E-RAB consist of?
In which scenario is the E-RAB Setup Request message s
ent?

Page122
Error Correction
Please analyze whether there is any error in the following dedicat
ed establishment procedure triggered by a UE, and correct them.

Page123
Contents
4. Paging Procedure
5. TAU Procedure
7. Detach Procedure

Page124
Paging Procedure
Triggered by:

MME or eNodeB

Although the procedure is triggered by different originators, t
he paging mechanism in Uu interface is the same.
MME-triggered paging eNodeB-triggered paging

When the MME initiates a paging When a SI message is changed, the
procedure, the eNodeB transmits eNodeB will send a paging message
the paging message on the PCCH to notify change(s) of one or more SI
to the UEs in all the cells message(s) and send the updated SI
belonging to TAs in a TAL message in the next SI message
specified in the paging message. modification period.
The paging message contains the To ensure all UEs in EMM registered
UE ID and domain information, mode in the cell can receive the SI
which indicates the paging message, the eNodeB sends paging
source. messages in all possible time during
The UE ID may be S-TMSI or IMSI. the DRX cycle.

Page125
Paging Procedure

Page127
Service Request Procedure Overview(1/2)
Trigger time
After attaching to a network, a UE will be in the idle mode, then when the UE w
ants to initiate any service, it will active the service request procedure. That is t
o say, the service request procedure is triggered when the following two conditi
ons are met:
The UE has no RRC connection but uplink data initiates requests.
The UE is in ECM idle mode and downlink data arrives.
Trigger condition
UE-triggered (service request)
EPC-triggered (paging+ service request or the eNodeB needs to initiate a signali
ng procedure for UEs in idle mode, such as the detach procedure)
Result
Uu interface: a RRC connection.
S1 interface: a S1-AP connection and a S1-U Bearer.

Page128
Service Request Procedure Overview (2/2)
Scenario and Procedure
MO(Mobile-Originated) case
The UE performs a random access procedure before initiating a s

ervice request procedure.
MT(Mobile-Terminated) case
After receiving downlink data, the MME sends paging messages to
UEs. Then, the UE performs the random access procedure and ini
tiates the service request procedure.
The service request message is encapsulated in an RRC Conne
ction Setup Complete message.

Page129
Service Request Flow
The service request procedure includes the following steps:
Random access
E-RAB setup
UE registration information and capability information are

available on the EPC, and therefore authentication and UE c
apability query are not required during the service request
procedure. ( different with 3G )

Page 130
Service Request Flow UE Initiates
UE-triggered service request procedure when in MO.
UE eNodeB MME S-GW P-GW HSS

1. NAS: Service Request
2. Authentication/Security
3. S1-AP: Initial Context Setup Request
4. Radio bearer establishment
5. Uplink data
6. S1-AP: Initial Context Setup Complete

7. Modify Bearer Request
8. Modify Bearer Response

9. Downlink data

Page131
Service Request Procedure EPC Initiates
EPC-triggered service request procedure when MT.
UE eNodeB MME S-GW P-GW
1. Downlink
data
2. Downlink data notification
3. Downlink data notification
4. Paging ack
5. Service Request Procedure
Downlink data

Page132
S1AP-Paging Message
Tracing Case of Paging
- S1 Interface
Used to allocate paging
subframe for UE
S-TMSI will be used for

paging for security
Indicates this paging

is from CS or PS
TAC where the paging

should be delivered
Page133
Tracing Case of Paging - Uu Interface
RRC-Paging Message
RRC Connection Request Message

Page134
Tracing Case of Paging Service Request
1
Initial UE Msg Message

Page135
Tracing Case of Paging Triggered by eNodeB
RRC_PAGING

Page136
Q&A
After network attachment, the default bearer has set up th
e context information. Why the service request is required i
n the paging procedure?
Use the 3900 Series LTE eNodeB V100R003C00SPC420 Offli

ne tool to open files in the following path: http://wss.huawei.co
m/sites/lsdd/Shared Documents/00_HQ/ENG/05 LTE/LTE FDD/01 Principl
e/06 Exercise Library/LTE Signaling/Paging

Page137
Contents
4. Paging Procedure
5. TAU Procedure
7. Detach Procedure

Page138
Definition of the TA
To locate the UE, the LTE network coverage is divided into multiple tracking areas (TAs)
. TA is a basic unit for UE location management and paging in the LTE system. The func
tions of the TA resemble those of the LA and RA used in 3G systems.
A TA is identified by a tracking area code (TAC) and contains one or multiple cells. The
TAC is broadcast in SIB1 in the same way as the LAC and RAC in 3G systems.
The TAI uniquely identifies a TA in the network operation. A TAI consists of an MCC, an
MNC, and a TAC, with a length of six bytes.
SGSN
EPC
MME S-GW RNC RNC RNC
eNodeB eNodeB eNodeB NodeB NodeB NodeB NodeB NodeB
TA1 TA2 TA3 Cell1 Cell2 Cell3 Cell4 Cell5 Cell6

TA3 RA1 RA2
EPS UMTS

Page139
Definition of the TAL
A TAL is a list of TAIs, which will be delivered to a UE during the attach
procedure or TAU procedure.
When a UE attaches to a network, the MME allocates a TAL that are containe
d in the ATTACH ACCEPT or TAU ACCEPT message to the UE.
The UE saves the TAL after receiving it. The UE can move between TAs conta
ined in this list and no TAU is required.
The EPC sends UE
paging messages in
all cells included in
the TAL.
The number of TAIs
in a TAL is variable.
A TAL includes a
maximum of 16
TAIs.
Page140
TAU Definition and Trigger Conditions
When a UE moves from a TA contained in a TAL to another TA contained
in another TAL, the UE must register with the new TA to change its positi
on information. This process is called Tracking Area Update (TAU).
The UE The UE enters a TA contained in a new TAU

1
TAL.
sends a TAU The TAUs are
request classified into two

2 The periodic TAU timer expires. types based on the
when any
UE status:
trigger
3
The UE reselects an E-UTRAN cell from TAU in idle mode
another RAT cell.
condition is TAU in connected
met. mode

Page141
Functions of the TAU
Registering UE position information in the network
Allocating new GUTI to the UE (Optional)
Changing the states of the UE and MME from EMM-DEREGI
STERED to EMM-REGISTERED
Enabling UEs in idle mode to initiate the TAU request and s
et up user plane resources

Page142
TAU Procedure
The TAU procedure includes the following steps:
Random access

Mo-Signaling as the cause value for RRC setup
TAU update
Authentication and Bearer establishment procedure are not re
quired during a TAU procedure. Connections will be released u
pon the TAU completes.

Page143
the UE in idle mode
enters a TAI not
stored in its TAI list
UE context updates
between MMEs
Only if TAU Accept message carries a

new GUTI does a UE need to respond by
TAU Complete message
TAU in Idle Mode

Copyright Idle
The UE enters 2014modeHuawei
again Technologies Co., Ltd. All rights reserved.
Page144
TAU in Connection Mode
NAS signaling connection will not be released when TAU is compl
eted in connection mode.
The UE in
connection mode
enters a TAI not
stored in its TAI list
UE context updates
between MME
These two messages will

not appear when there is
no new GUTI assigned in
TAU Accept

Page145
Q&A
Why is the TA updated?
Please draw the TAU signaling flow.

Page146
Contents
4. Paging Procedure
5. TAU Procedure
7. Detach Procedure

Page147
Handover Overview
What is handover?
A UE in connected mode moves across different cells and completes t
he UE context update. This process is called handover.
Handover types in the LTE system
Intra-RAT handover
Intra-eNodeB handover
X2-based inter-eNodeB handover with the MME unchanged
S1-based inter-eNodeB handover with the MME or S-GW probably changed
If no X2 link is available, the inter-eNodeB handover is performed on the S1 link
.
Note: If both a X2 and S1 links are available, the X2 link is preferentially used
for the inter-eNodeB handover.
Inter-RAT handover
Handover between LTE and WCDMA, handover between LTE and GSM or EDEG, and h
andover between LTE and CDMA2000

Page148
Handover Procedure Overview

Page149
Intra-eNodeB Handover
1. The UE submits measurement reports to the eNodeB to initia
te a handover.
2. The eNodeB delivers an RRC Connection Reconfiguration me
ssage to the UE to request the UE to handover to another cell
.
The most important IE in the RRC Connection Reconfigura Handover
tion message is MobilityControlInfo. This IE indicates a
Uu Uu
handover command.
3. After receiving the RRC Connection
Reconfiguration message, the UE accesses the
target cell based on the configurations contained
in the message. After successfully entering the
target cell, the UE sends an RCC Connection
Reconfiguration Complete message to the
eNodeB, indicating that the handover succeeds.
4. After receiving the RCC Configuration
Reconfiguration Complete message, the eNodeB
delivers measurement configurations based on the
configurations of the new cell.
Page150
Inter-eNodeB X2 Handover Procedure(1/
2)

Page151
Inter-eNodeB X2 Handover Procedure(2/2)

Page152
Tracing Case of Inter-eNodeB X2 Handover
Key IEs in RRC C
ON RECFG messa
ge
PCI of target cell

frequency of target cell,
needed to deliver when
inter-frequency HO
bandwidth of target cell
target cell
assigns new
CRNTI for
the UE
security algorithm
parameters used
in target cell

Page153
S1 HO Procedure

Page154
Contents
4. Paging Procedure
5. TAU Procedure
7. Detach Procedure

Page155
Detach Flow Overview
The Detach procedure allows:
The UE to inform the network that it does not want to access the EPS any longer,
and
The network to inform the UE that it does not have access to the EPS any longer.
The UE is detached either explicitly or implicitly:
Explicit detach
Implicit detach
A detach procedure can be initiated by:
UE
MME
HSS

Page156
UE-initiated Detach Procedure Overview
UE eNodeB MME S-GW P-GW
1. Detach request
2. Delete session request

Release
3. Delete session response default bearer
4. Delete session request
5. Delete session response
6. Detach accept
7. Signaling connection release These two messages do not
exist if a UE initiates the
detach procedure due to
power-of not to disable the
function of attachment.
Page157
Detach Procedure Initiated by UE Power-off
The Detach Request message contains an 8-bit field "Detach ty
pe", which contains a 1-bit "Switch off" indication.
1: switch off, indicates that the UE is powered off. The following fig
ure shows the detach procedure.
0: normal detach, indicates that the UE is detached not due to UE
power-off.

Page158
Detach Procedure Initiated by UE in Idle M
ode
Differences between
Idle mode and
Connected mode

Page159
Detach Procedure Initiated by UE in Connecte
d Mode
Differences between
Idle mode and
Connected mode

Page160
Detach Procedure Initiated by MME
The MME initiated detach procedure is either explicit (e.g. by O&M interv
ention) or implicit.
If the UE is in ECM-CONNNECTED state the MME may explicitly detach the UE
by sending a Detach Request message to the UE. Refer to the following figure.
The MME may implicitly detach a UE, if it has not had communication with UE
for a long period of time. The MME does not send the Detach Request (Detach
Type) message to the UE for implicit detach. The implicit detach is local to the
MME, i.e. an SGSN registration will not be detached.

Page161
Detach Procedure Initiated by HSS
The HSS-Initiated Detach procedure is initiated by the HSS. The H
SS uses this procedure for operator-determined purposes to req
uest the removal of a subscriber's MM and EPS bearer at the MM
E and also at the SGSN if both an MME and an SGSN are register
ed in the HSS.

Page162
Q&A
Use the 3900 Series LTE eNodeB Offline tool to open files in the followi
ng signaling file:
http://wss.huawei.com/sites/lsdd/Shared Documents/00_HQ/ENG/05 LTE/LTE FDD/01 Princi
ple/06 Exercise Library/LTE Signaling/Detach
Based on the signaling file, how to determine whether a UE is d
etached due to power-off or not? If the UE is detached not due t
o power-off, is the UE in idle mode or connected mode during t
he detach procedure?

Page163
Summary
Typical signaling basic principles
Typical signaling procedures
Case of typical signaling procedures

Page164
Thank you
www.huawei.com

02 LTE Signaling and Protocols

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

02 LTE Signaling and Protocols

Hochgeladen von

Copyright:

Verfügbare Formate

LTE Signaling and Protocols

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

2. UE Power on and Attach Procedure

3. Dedicated Bearer Procedure

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

E-UTRAN: consists of eNodeBs, which integrate function of UTRAN/BSS

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

RRM and RRC functionality ar

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Temporary Mobile Temporary UE ID in specific MSC

packet temporary Temporary UE ID in specific

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

12 bits 8~12 bits 16 bits 8 bits 32 bits

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

2. UE Power-on and Attach Procedure

3. Dedicated Bearer Procedure

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Invisible Partial Visible

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

present and not empty, or the HPLMN if the EHPLMN list is

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Q2: What role does the EPC play in PLMN selection?

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

2.2 Radom Access

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

PSS and SSS Location for FDD

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

PSS and SSS Location for TDD

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

2.2 Radom Access

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

ettings in the system information received on the RRC layer before re

How is the system information

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

SSS PSS PBCH

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

PBCH SSS PSS

40ms PBCH TTI

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Other SIBs MNC:01

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

What are the major information included in each message?

Which message delivers system downlink and uplink band

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

2.2 Radom Access

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Criteria for cell selection: Srxlev and

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

2.2 Radom Access

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2014 Huawei Technologies Co., Ltd. All rights reserved.

Contention based Non-contention based