LTE End To End Call Flow: With Logs Using Common Troubleshooting Tools

LTE end to end Call Flow
with Logs using common troubleshooting Tools
1 © Nokia Siemens Networks 2011 LTE End to End Call flow with common troubleshooting Tools / Shomik Pathak / April 2012
3GPP interfaces
S16 IMS Core
A-SBC S/I-CSCF
BTS/NodeB BSC/RNC SGSN P-CSCF
Pre R8 Gb/ w/SBC Mw
PCRF
2G/3G Iu Gxc(*) Rx
Gn Mg/Mi
R7 DT Gn
BTS BSC Ia MGCF
2G SGSN Gx
R8 2G Abis Gb Gm BG Mn
S4
SGi MGW
S5 SGi
S12 DT S4 PGW
SGW SGi
NodeB RNC
R8 3G Iub Internet
Iu_c
Gr/S6d CNR/HSS Operator services

uSGSN S3
S11 S6a
eNodeB S1-U
LTE
S1-MME SGs MSC
MME
Control plane
S10
User plane
LIG EMS
* Needed only with S5 PMIP
Functional Split between E-UTRAN and EPC
eNB
Inter Cell RRM
RB Control
Connection Mobility Cont.

MME
Radio Admission Control
NAS Security
eNB Measurement
Configuration & Provision
Idle State Mobility
Handling
Dynamic Resource
Allocation (Scheduler)
EPS Bearer Control
RRC
PDCP
S-GW P-GW
RLC
Mobility UE IP address
MAC Anchoring allocation
S1
PHY Packet Filtering
internet
E-UTRAN EPC
X2AP ids •TAI list(c) HSS/EIR
Protocol Stack X2AP X2AP Diameter Diameter
•GUMMEI(c)
SCTP SCTP SCTP/TCP •MME S1AP id(to eNb) SCTP/TCP •IMSI(c)
& Identifiers•eNB id(c) IP IP IP
•STMSI(to UE)
IP
(to MME>EPC)
•TAI(c) (to MME>EPC) •GUTI (to UE) •PDN id/APN
•PLMN(c) (to MME>EPC) •TAI list(to UE) (to MME>EPC)
•IMSI(to HSS) L2 L2 L2 L2
•PGW id
•IMEI(c) •eNb S1AP id(to MME)
L1 L1 (to MME>EPC)
•CRNTI(to UE) PHY L1
Control Plane
UE •ECGI(c)(to MME>EPC) X2-c eNb S6a/S6d/S13

MME
eNb
NAS NAS
SRB S1AP ids GTPcv2 GTPcv2 GTPcv2
RRC RRC S1AP S1AP GTPc TEIDs GTPc TEIDs
PDCP PDCP SCTP SCTP UDP UDP UDP

•IP (to UE)
RLC RLC IP IP IP IP IP •PGW id(c)
MAC MAC L2 L2 L2 L2 L2
PHY PHY PHY L1 L1 L1 L1

S11
Uu S1-c (S3/S4/S8/S10/S16) SGW S5/S8 PGW SGi P
App D
End to End service N
APN
IP IP
User Plane
EPS Bearer (ID)

PDCP PDCP GTPu GTPu GTPu
E-RAB (ID)
UDP UDP UDP
RLC RLC
IP IP IP
MAC MAC
L2 L2 L2
PHY PHY L1 L1 L1
S1-u
Radio Bearer S1-u Bearer S5/S8 Bearer
DRB ID DL DRB ID UL S1-u TEID DL S1-u TEID UL S5-u TEID DL S5-u TEID UL
Protocol stack
GTP-u carrying SCTP carrying
(Another view) User Traffic S1AP & NAS
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
ROHC ROHC ROHC ROHC ROHC ROHC
PDCP
c/u
Security Security Security Security Security Security

RB SRB1 SRB2 DRB4 DRB5 SRB0 SRB1 SRB2 DRB4 DRB5 SRB0
Radio Bearers
CCC
CCC
BCC
PCC
RLC
Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ

AM or TM AM or UM AM or UM AM or UM AM or UM AM or UM
H
DCCH DTCH DCCH DTCH
Logical channels
Scheduling / Priority Handling Scheduling / Priority Handling

MAC
Multiplexing UE1 Multiplexing UEn Multiplexing
BCH
PCH
HARQ HARQ HARQ
RACH
1TB/TTI/Ant 1TB/TTI/Ant DL-SCH UL-SCH
Transport channels
1TB/TTI
PHY
PDCCH Physical channels

PDSCH PBCH PUCCH PUSCH PRACH
5 © Nokia Siemens Networks 2011

UE
LTE End to End Call flow with common troubleshooting Tools / Shomik Pathak / April 2012
Protocol Stack
(Another view)
1 TBS per TTI per antenna
Ultimately TBS + Coding + CRC is

6 © Nokia Siemens Networks 2011 what is sent out by PHY
Work sheet HSS
MME DNS
PCRF
UE eNB SGW PGW
What’ the point?
 N/A
Who’s talking to who? (Source/Destination?)

 N/A
Which is the channel path taken? Or who carries the payload?

 N/A
Where is it acknowledged? Or is it?

 N/A
How is QOS/KPI satisfied?

 N/A
Related parameters?
 N/A
Cell Camping
Primary and Secondary Synch Channels
Find PCI through Synch channels
• The primary and secondary synchronization signals are used from the UE for the initial cell search. The
synchronization signals are transmitted twice per 10 ms in predefined slots. In the frequency domain, they
are transmitted on 62 subcarriers within 72 reserved subcarriers around DC subcarrier. Thus the UE can
synch to 5ms time.
• There are 3 different two-dimensional orthogonal sequences and 168 different two-dimensional pseudo-
random sequences. Each cell identity corresponds to a unique combination of one orthogonal sequence
and one pseudo-random sequence, thus allowing for 504 unique cell identities 168 cell identity groups with
3 cell identities in each group
• The 504 available physical layer cell identities are grouped into 168 physical layer cell identity groups,
each group contains 3 unique identities (0,1 or 2). The secondary synchronization signal carries the
physical channel cell identity group, and the primary synchronization channel carries the physical layer
unique identity (0, 1or 2).
– Primary Synchronization Signal (PSS) detection to obtain the physical layer cell ID(within a group of three) and slot
synchronization.
– Secondary Synchronization Signal (SSS) detection to obtain the Cyclic Prefix (CP)length, the physical layer cell group ID
and the frame synchronization.
Decoding LTE common channels LTE signal analyzer
eNB is transmitting all

common channels.
LTE signal analyzer shows

correct power levels.
Total configured power of 20

Watts i.e. 43dBm is spread
over 300 subcarriers to give
~18.3dBm per RE.
Power is static for all

channels.
UE decodes the physical cell

id 222 from P-Synch/S-Synch
and the MIB/SIBs from
BCH/PDSCH.
MIB and SIBs
MIB/SIB(1/2)
• The MIB is mapped on the BCCH and carried on BCH while all other SI messages are mapped on the
BCCH and dynamically carried on DL-SCH where they can be identified through the SI-RNTI (System
Information RNTI).
o Both MIB and SystemInformationBlockType1use a fixed schedule with a periodicity of 40 and 80 ms
respectively while the scheduling of other SI messages is flexible and indicated by
SystemInformationBlockType1.
• System information is divided into the MasterInformationBlock (MIB) and a number of

SystemInformationBlocks (SIBs):
o MasterInformationBlock defines the most essential physical layer information of the cell required to
receive further system information;
o SystemInformationBlockType1 contains information relevant when evaluating if a UE is allowed to
access a cell and defines the scheduling of other system information blocks;
o SystemInformationBlockType2 contains common and shared channel information;
o SystemInformationBlockType3 contains cell re-selection information, mainly related to the serving cell;
o SystemInformationBlockType4 contains information about the serving frequency and intra-frequency
neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a
frequency as well as cell specific re-selection parameters);
MIB/SIB(2/2)
o SystemInformationBlockType5 contains information about other E‑UTRA frequencies and inter-

frequency neighbouring cells relevant for cell re-selection (including cell re-selection parameters
common for a frequency as well as cell specific re-selection parameters);
o SystemInformationBlockType6 contains information about UTRA frequencies and UTRA neighbouring
cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as
well as cell specific re-selection parameters);
o SystemInformationBlockType7 contains information about GERAN frequencies relevant for cell re-
selection (including cell re-selection parameters for each frequency);
o SystemInformationBlockType8 contains information about CDMA2000 frequencies and CDMA2000
neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a
frequency as well as cell specific re-selection parameters);
o SystemInformationBlockType9 contains a home eNB identifier (HNBID);
o SystemInformationBlockType10 contains an ETWS primary notification;
o SystemInformationBlockType11 contains an ETWS secondary notification.
Log view
TTI Trace
MIB scheduled
MIB and SIB1 decoding when SFN mod 4 =
• MIB Scheduling (3GPP 36.331): 0, in sub frame # 0
– Periodicity: 40 ms
– Repetition: 10 ms
message { message {
dl-Bandwidth n25 Only SFN updates in dl-Bandwidth n25
phich-Config { phich-Config {
every MIB period
phich-Duration normal phich-Duration normal
phich-Resource oneSixth } phich-Resource oneSixth }
systemFrameNumber '10101000'B systemFrameNumber '00111101'B
spare '0000000000'B } spare '0000000000'B }
}BCCH-BCH-Message }BCCH-BCH-Message
• SIB1 Scheduling (3GPP 36.331): SIB1 scheduled

when SFN mod 8 =
– Periodicity: 80 ms 0, in sub frame # 5
– Repetition: 20 ms
– SIB1 contains the scheduling
information for SI messages
Log view
TTI Trace
time MIB/SI Size
• SI2: [h:min:s:ms]
SFN eSFN
(bytes)
SIB ID
– Periodicity: 160 ms 13:37:06:824 960 0 31 SI2

13:37:06:984 976 0 31 SI2
13:37:07:144 992 0 31 SI2
13:37:07:304 1008 0 31 SI2
13:37:07:464 0 0 31 SI2
• SI3: time
SFN eSFN
MIB/SI Size
SIB ID
[h:min:s:ms] (bytes)
– Periodicity: 160 ms 13:37:06:834 961 0 10 SI3
13:37:06:994 977 0 10 SI3
13:37:07:154 993 0 10 SI3
SI window 13:37:07:314 1009 0 10 SI3
length = 13:37:07:474 1 0 10 SI3
10ms. So
• SI4: SI’s are time MIB/SI Size
SFN eSFN SIB ID
[h:min:s:ms] (bytes)
– Periodicity: 160 ms scheduled
10 ms apart 13:37:06:844 962 0 8 SI4
13:37:07:004 978 0 8 SI4
13:37:07:164 994 0 8 SI4
13:37:07:324 1010 0 8 SI4
13:37:07:484 2 0 8 SI4
• SI5:
time MIB/SI Size
SFN eSFN SIB ID
– Periodicity: 320 ms [h:min:s:ms] (bytes)
13:37:06:854 963 0 18 SI5
13:37:07:174 995 0 18 SI5
13:37:07:494 3 0 18 SI5
13:37:07:814 35 0 18 SI5
13:37:08:134 67 0 18 SI5
Log View
QXDM
MIB
SIB1
SIB2
SIB3
What’ the point?
 Read important system information before deciding to attach.

 eNB to UE

 MIB through BCH, SIBs through DL-SCH

 No

 N/A
Related parameters?
 siWindowLen, siXPeriodicity, siXRepetition
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Preamble
Msg1
What’ the point?
 Air interface is not synchronized, hence preamble needs to be sent to set it up. (unlike 3G no data is sent)

 UE PHY to eNB PHY (notified to MAC)

 PRACH

 N/A

 Depends on RACH configuration
Related parameters?
 rootSeqIndex, prachCS, prachConfigIndex
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
RACH(1/2)
• The RACH procedure is used in four cases:

o Initial access from disconnected state (RRC_IDLE) or radio failure
o Handover requiring random access procedure
o DL or UL data arrival during RRC_CONNECTED after UL PHY has lost synchronization (possibly due
to
o power save operation)
o UL data arrival when are no dedicated scheduling request (PUCCH) channels available
• There are two forms of the RACH procedure: LTE Rach cell sizes
o Contention-based, which can apply to all four events above, and
o Non-contention based, which applies to only handover and DL data arrival.
• The difference is whether or not there is a possibility for failure using an overlapping RACH preamble. In the
non-contention based random access procedure, there is no chance of a preamble collision because the code
is pre-assigned by the eNB
• There are two possible groups defined and one is optional. If both groups are configured the size of
message 3 and the pathloss are used to determine which group a preamble is selected from. The group to
which a preamble belongs provides an indication of the size of the message 3 and the radio conditions at
the UE. The preamble group information along with the necessary thresholds are broadcast on system
information.
RACH (2/2)
• Random access preamble:

sent on a special set of
physical layer resources,
which are a group of
subcarriers allocated for this
purpose
o Uses Zadoff-Chu
sequences, a CDMA-like
coding, to allow
simultaneous transmissions
to be decoded
o You have 838 distinct and
non-orthogonal ZC
sequences, called root
sequences (not logical but
physical root sequence)
o Each sequence is again 839
bit long. 3gpp chose 15
particular shifts as in Table
5.7.2-2 in 36.211.
Log view
QXDM
Parameter settings dictate
PRACH location and used
root sequences.
Different root sequences

are tried with increasing
power each try every 10ms
LLDM
BTSLog
Random Access Response
Msg2
Msg2
Random access response

o Generated by MAC and sent on Physical Downlink Control Channel (PDSCH)
o Addressed to RA-RNTI on PDCCH
o Sent within a time window of a few TTI
o For initial access, conveys at least RA-preamble identifier, timing alignment information, initial UL grant,
and assignment of temporary C-RNTI
o Intended for a variable number of UEs in one DL-SCH message.
What’ the point?
 Response to initial access, conveys at least RA-preamble identifier, timing alignment information, initial UL grant for 1 st
scheduled transmission, and assignment of temporary C-RNTI
 eNB MAC talking to UE MAC (addressed with RA-RNTI)

 DL-SCH>PDSCH.
 PDCCH AGG = 4 (not user configurable) and DCI format 1C
 No HARQ

 MAC sends this response on urgent basis to keep rach response within configured window
Related parameters?
 pdcchAggRaResp, raRespWinSize, maxCrRaDl
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log View QXDM
For msg2 MCS is derived from set

maxcrraresp parameter, MCS
selection starts from lowest point
and goes up to see when set cr
rate is satisfied (usually 0). PRB is DCI format 1C used
selected then to satisfy TBS. PDCCH decoded at 646.6
EMIL
MSG2 contains UL grant,

timing adjustment , crnti etc.
MSG2 contains UL grant,

timing adjustment , crnti etc.
BTSLog
Msg3
RRC Connection Request
RRC Connection Reconfiguration Complete (covered later)
RRC Connection Re-establishment (not covered)
Msg3
• First scheduled UL transmission on UL-SCH

• Uses HARQ;
• Size of the transport blocks depends on the UL grant conveyed in step 2 and is at least 80 bits.
• For initial access:
o Conveys the RRC Connection Request generated by the RRC layer and transmitted via CCCH;
o Conveys at least NAS UE identifier but no NAS message;
o RLC TM: no segmentation;
• For RRC Connection Re-establishment procedure:
o Conveys the RRC Connection Re-establishment Request generated by the RRC layer and transmitted via CCCH;
o RLC TM: no segmentation;
o Does not contain any NAS message.
• After handover, in the target cell:
o Conveys the ciphered and integrity protected RRC Handover Confirm generated by the RRC layer and transmitted via
DCCH;
o Conveys the C-RNTI of the UE (which was allocated via the Handover Command);
o Includes an uplink Buffer Status Report when possible.
• For other events:
o Conveys at least the C-RNTI of the UE .
What’ the point?
 1st scheduled UL transmission to request service

 UE RRC to eNB RRC

 PUSCH>UL-SCH>CCCH

 HARQ

 HARQ Nacks will delay call setup
Related parameters?
 HarqMaxMsg3, raLargeMcsUl, raSmallMcsUL, raSmallVolUL, raLargeVolUl.
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view
msg3
TTI trace
Retransmission in Msg3 2 PRB is usually

will delay call setup Msg3 always goes with chosen to fit that TBS
MCS 5 as TBS is set in SCF
BTSLog
Log view
Msg3 is prepared earlier,
but really sent on 647.2
QXDM
ACK is received 4ms later
Log view
EMIL
eNB is internally setting up the

user resources after RRC
connection request is received
Msg4
Contention Resolution
(+ RRC Connection Setup)
Contention Resolution on DL
• The eNodeB uses this optional step to end the RACH procedure
• Early contention resolution shall be used i.e. eNB does not wait for NAS reply before resolving contention
• Not synchronised with message 3;
• HARQ is supported;
• Addressed to:
o The Temporary C-RNTI on PDCCH for initial access and after radio link failure;
o The C-RNTI on PDCCH for UE in RRC_CONNECTED;
• HARQ feedback is transmitted only by the UE which detects its own UE identity, as provided in message
3, echoed in the Contention Resolution message;
• For initial access and RRC Connection Re-establishment procedure, no segmentation is used (RLC-TM).
• The Temporary C-RNTI is promoted to C-RNTI for a UE which detects RA success and does not already
have a C-RNTI; it is dropped by others. A UE which detects RA success and already has a C-RNTI,
resumes using its C-RNTI.
• RLC TM. No segmentation
What’ the point?
 RRC Setup is sent to setup SRB1 resources, power and PUCCH related resources.

 eNB MAC CE talking to UE MAC. eNB RRC talking to UE RRC.

 CCCH>DL-SCH>PDSCH. (addressed with C-RNTI of chosen UE)
 PDCCH AGG = 4 (user configurable) and DCI format 1A
 MAC HARQ - yes, RLC TM – no, RRC – Setup Complete

Related parameters?
 MaxCrRa4Dl, pdcchAggMsg4.
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
For msg4 MCS is derived from set
Log view maxcrmsg4 parameter, MCS
selection starts from lowest point
msg4
No CQI configured yet and goes up to see when set cr
rate is satisfied (in this case =1).
PRB is selected then to satisfy the
TTITrace
27 bytes TBS (in this case = 4)
BTSLog
EMIL
Log view
Contention Resolution goes
as MAC control element
RRC Connection Setup

message goes as MAC data
DCI format 1A
QXDM
Along with Ack for msg4, SR

Ack sent 4ms later
is sent together for msg5
RRC Connection Setup Complete
Msg5
(+ NAS: Attach Request)
What’ the point?
 Response to RRC Connection Setup and carry first NAS/Attach Request

 UE RRC talking to eNB RRC. UE NAS to MME NAS.

 PUSCH>UL-SCH>CCCH>SRB1. RRC carries NAS till enb. Then S1AP carries the same NAS over to MME.

 MAC HARQ – yes, RLC AM - yes

 HARQ/RLC Nacks will delay call setup. RRC setup complete pegs Call Accessibility counter.
Related parameters?
 iniMcsUl, iniPrbsUl, maxNumPrbSr
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view
IniMcsUl used
first here
TTI Trace
First CQI report
4ms earlier shows

PDCCH capacity used
for DL msg4 and UL
Grant for this msg5
BTSLog
Log view
EMIL
Log view Along with Ack for msg4, SR
is sent together for msg5
QXDM
Response to SR is first
UL grant with 4 PRBs as
set in maxNumPrbSr
First CQI requested.
SR also kick starts

proactive scheduling
from the very next TTI
starting with iniPrbUL
First CQI/RI report.
Log view
What NAS is carried by

RRC in air interface is
carried by S1AP (Initial
UE message) on S1-c
msg5+NAS(Attach
Request) S1AP + NAS(Attach
Request)
NAS Direct Transfers
Identity Request/Response
Authentication Request/Response
NAS Security Mode Command/Complete
What’ the point?
 Verify Identity of UE, Authenticate UE and setup NAS level security

 UE NAS to MME NAS.

 S1AP carries NAS till eNb. Then RRC carries the same NAS over to UE. PDSCH>DL-SCH>CCCH>SRB1.
 MAC HARQ - yes, RLC AM – yes, NAS - yes

 HARQ/RLC Nacks will delay call setup. Delays in core will affect call setup time.
Related parameters?
 N/A
•GUMMEI(c)
•STMSI(to UE)
IP
(to MME>EPC)
•PGW id
L1 L1 (to MME>EPC)
Control Plane

NAS is secured. MME
eNb
NAS NAS

•IP (to UE)

S11
App D
APN
IP IP
User Plane
EPS Bearer (ID)

E-RAB (ID)
UDP UDP UDP
RLC RLC
IP IP IP
MAC MAC
L2 L2 L2
PHY PHY L1 L1 L1
S1-u
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view EMIL
Log view
Wireshark
UL and DL direct NAS direct
Log view transfers authenticate with HSS
and give NAS security Authentication
Request
S1AP/NAS/Auth
Req
RRC/NAS/Auth Req
S1AP/NAS/Auth Authentication
Response Response
RRC/NAS/Auth
Response
S1AP/NAS/Sec
Command
RRC/NAS/Sec
Complete S1AP/NAS/Sec
RRC/NAS/Sec
Command Complete
SAE selection and GTP tunnel setup
SGW/SGW selection based on DNS queries
GTP tunnel/session setup
What’ the point?
 Select SGW/PGW and setup S1-U from SGW side and S5/S8 GTP tunnel for default bearer.

 MME GTPcv2 talking to SGW GTPcv2. SGW GTPcv2 talking to PGW GTPcv2.

 UDP

 DNS – yes, GTPcv2 - yes

 Delays in core will affect call setup time.
Related parameters?
 N/A
eNb
•TAI list(c) HSS/EIR
•GUMMEI(c)
•STMSI(to UE)
IP
(to MME>EPC)
•PGW id
L1 L1 (to MME>EPC)
Control Plane
UE •ECGI(c)(to MME>EPC) X2-c S6a/S6d/S13

MME
eNb
NAS NAS

•IP (to UE)

S11
App D
APN
IP IP
User Plane
EPS Bearer (ID)

E-RAB (ID)
UDP UDP UDP
RLC RLC
IP IP IP
MAC MAC
L2 L2 L2
PHY PHY L1 L1 L1
S1-u
Log view
Wireshark
SGW IP address DNS

queried based on TAI
PGW IP address DNS

queried based on APN
TEID is the field present in the

GTP-C header and using which
the tunnel is identified. FTEID is
Fully Qualified Tunnel End Point
Identifier. This IE is used to send
TEID/GRE Key and IP info of
sending entity.
Log view
SGW/PGW is found by MME and
GTP session requests are sent to Location Update
setup GTP tunnels. Request
Location Update
Answer
Create session Create session

SGW PGW
DNS query for SGW DNS query for PGW

address address
Create session Create session

response SGW response PGW
Attach accept
S1AP Initial Context Setup Request
NAS Attach Accept
(+ NAS ESM Activate Default EPS Bearer Context Request)
What’ the point?
 Respond to NAS attach request, assign UE IP and setup EPS bearer
 Setup Initial E-RAB context
 MME NAS to eNB S1AP.

 SCTP

 S1AP – yes(Initial context setup response). When sent over the air later RRC – yes, RLC – yes, MAC- yes, NAS – yes(attach
complete)
 HARQ/RLC Nacks will delay call setup. Delays in core will affect call setup time.
Related parameters?
 N/A
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view EMIL
Log view
Wireshark
Log view Initial context for default bearer is
sent and NAS sends UE IP, EPS
bearer etc to UE
S1AP Initial Context

Setup + NAS Attach
RRC Security
(+ optional UE Capability Enquiry)
What’ the point?
 Setup RRC level security with the key received in Attach Request
 Optionally request UE capability
 UE RRC and eNB RRC

 PUSCH>UL-SCH>CCCH>SRB1.
 PDSCH>DL-SCH>CCCH>SRB1.
 RRC – yes, RLC – yes, MAC- yes

 HARQ/RLC Nacks will delay call setup.
Related parameters?
 actCiphering
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view EMIL
Log view RRC is secured with key received
in Attach Accept
RRC Security Mode
RRC UE capability
Inquiry Indication
RRC Connection Reconfiguration
(+ NAS Attach Accept [ ESM Activate default EPS bearer])
RRC Connection Reconfiguration Complete
What’ the point?
 Once RRC is ciphered, RRC will configure handover measurements, srb2 and the default bearer drb4 (eps bearer id 5)
 MME NAS Attach Accept (ESM Activate EPS default bearer) container is relayed to eNB NAS
 eNB RRC and UE RRC

 RRC – yes, RLC – yes, MAC- yes

 HARQ/RLC Nacks will delay call setup.
Related parameters?
 Parameters related to handover, PUCCH, RLC, BSR, PHR etc.
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view EMIL
Log view RRC is reconfigured to configure
measurements for handovers,
srb2 and drb 4(eps id 5)
RRC Reconf + NAS

Attach accept + ESM Act
S1AP Initial Context Setup Response
Optional S1AP UE Capability Info Indication
What’ the point?
 Response to MME’s Initial Context Setup Request to setup ERAB id 5.

 eNB S1AP and MME S1AP

 SCTP.

 S1AP – No. It is an acknowledgment itself.

Related parameters?
 N/A
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view
Wireshark
Log view EMIL
Log view ERAB id 5 is setup successfully
S1AP Initial Context

Setup response
Attach Complete
NAS Attach Complete
(+ NAS ESM Activate Default EPS Bearer Context Accept)
What’ the point?
 Response to Attach Request and response to ESM Activate Default EPS Bearer Context Accept

 UE NAS to MME NAS


 RLC – yes, MAC- yes. NAS – No. It is an acknowledgment itself.

Related parameters?
 N/A
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view
Wireshark
Log view EMIL
Log view EPS bearer is setup in UE
S1AP NAS Attach

RRC NAS Attach Complete + EPS bearer re
Complete + EPS bearer acc
GTP tunnel setup modification
Modify Bearer Request/Response
What’ the point?
 Modify/notify S1-U TEID from the enb side.

 MME GTPcv2 talking to SGW GTPcv2. SGW GTPcv2 talking to PGW GTPcv2.

 UDP

 GTPcv2 - yes

Related parameters?
 N/A
•GUMMEI(c)
•STMSI(to UE)
IP
(to MME>EPC)
•PGW id
L1 L1 (to MME>EPC)
Control Plane

MME
eNb
NAS NAS

•IP (to UE)

S11
App D
APN
IP IP
User Plane
EPS Bearer (ID)

E-RAB (ID)
UDP UDP UDP
RLC RLC
IP IP IP
MAC MAC
L2 L2 L2
PHY PHY L1 L1 L1
S1-u
Log view
Wireshark
Log view S1-U TEID from enb side is
notified
GTPc Modify Bearer

Request
GTPc Modify bearer

response
End to End DATA!
Work sheet QOS
Identifiers
(Completed for Log Set 2)
HSS
S6a
IP=
IP=10.52.40.93
MME IP=10.52.65.4
DNS
IP=10.52.65.20
S1ap id 1235 Teid 0x0b000026
S11
S1c PCRF
Teid 0xa100009b
S1ap id 9
srb0
IP=10.48.131.74 Teid 0xa2000b0 Teid 0x720008a8
srb1 IP=10.48.123.98 IP=10.52.40.116
srb2 IP=10.48.123.98 IP=10.52.40.112
UE Uu
eNB S1u
SGW IP=10.52.40.114
S5
IP=10.52.130.163
PGW
drb4 F9010 Teid 0x00000611 Teid 0x8840015d Teid 0x8940015d Teid 0x8e7008a7
Log view
Wireshark
TTI Trace DL
Log view
3 Ues in
subframe 8
TTI Trace UL
3 Ues in
subframe 6
Add Dedicated Bearer!
PCRF/PGW always initiates Dedicated Bearer
Work sheet QOS
Identifiers
(Completed for Log Set 4)
HSS
S6a
IP=
IP=10.52.40.93
MME IP=10.52.65.4
DNS
IP=10.52.65.20
S1ap id 918
Teid 0x03000085
S11
S1c PCRF
Teid 0x71000004
S1ap id 17
srb0
IP=10.48.131.5 Teid 0x >>>> Teid 0x72000004
srb1 IP=10.48.123.99 IP=10.48.130.141
srb2 IP=10.48.123.99 IP=10.52.40.137
UE Uu
eNB S1u
SGW IP=10.52.40.137
S5
IP=10.52.130.137
PGW
Drb4/ERAB5 Teid 0x000000c1 Teid 0x1000005 Teid 0x >>>> Teid 0x1000005
F9010
X2 HANDOVER Start!
RRC Measurement Report
Handover Procedure
Note: X2-based handover without Serving GW relocation
Handover Late Path
Before handover Radio Handover
Preparation Switching
SAE GW SAE GW SAE GW SAE GW
MME MME MME MME
Source Target
eNB eNB
= Data in radio = GTP tunnel = S1 signalling

= Signalling in radio = GTP signalling = X2 signalling
For internal use
Unique document identifier (ID) / Version number / Life cycle status
104 © Nokia Siemens Networks 2011 Presentation / Author / Date
What’ the point?
 Send a3 or a5 based measurement report

 UE RRC to eNB RRC

 PUSCH>UL-SCH>DCCH>SRB1

 HARQ – yes, RLC yes

 HARQ and RLC Nacks could delay measurement report and risk dropping of call.
Related parameters?
 Handover related parameters
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view
EMIL
Log view
RRC Measurement
Report
X2 Handover Preparation
X2AP Handover Request
X2AP Handover Acknowledge (+RRC Connection Reconfiguration)
RRC Connection Reconfiguration
What’ the point?
 Prepare for HO by sending request to target cell. Relay RRC connection reconfiguration from target to the UE.

 X2AP of source eNB to X2AP of target eNB. eNB RRC to UE RRC

 SCTP on X2-C. PUSCH>UL-SCH>DCCH>SRB1.

 X2AP – yes. HARQ – yes, RLC yes for RRC.

 HARQ and RLC Nacks could delay measurement report and risk dropping of call. Delays in core could result in dropped calls.
Related parameters?
•GUMMEI(c)
•STMSI(to UE)
IP
(to MME>EPC)
•PGW id
L1 L1 (to MME>EPC)
Control Plane

MME
eNb
NAS NAS

•IP (to UE)

S11
App D
APN
IP IP
User Plane
EPS Bearer (ID)

E-RAB (ID)
UDP UDP UDP
RLC RLC
IP IP IP
MAC MAC
L2 L2 L2
PHY PHY L1 L1 L1
S1-u
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view EMIL
Wireshark
Log view
X2AP Handover
Request
RRC Connection
Reconfiguration
X2AP Handover
Acknowledge
X2 Handover Execution
RRC Connection Reconfiguration Complete
RRC Connection Reconfiguration (HO Measurement)
RRC Connection Reconfiguration Complete (HO Measurement)
What’ the point?
 Camp to new cell and receive new reconfigurations for radio.

 eNB RRC and UE RRC

 HARQ – yes.

Related parameters?
Protocol stack
SGW MME
eNB RRC
Radio Bearers
DL
UL
RB
PDCP
c/u

Radio Bearers
CCC
CCC
BCC
PCC
RLC

H
DCCH DTCH DCCH DTCH
Logical channels

MAC
BCH
PCH
HARQ HARQ HARQ
RACH
Transport channels
1TB/TTI
PHY


UE
Log view
EMIL
Log view
X2AP SN Status
Transfer
RRC
Reconfiguration Complete
RRC Connection
Reconfiguration (Measurem
X2 Handover Completion
S1AP Path Switch Request
GTPc Modify Bearer Request
GTPc Modify Bearer Response
S1AP Path Switch Response
What’ the point?
 Switch user plane path to the new target eNB

 eNB S1ap and MME S1AP. MME GTPcv2 and SGW/PGW GTPcv2

 SCTP in S1c. UDP in S11.

 S1AP – yes. GTPcv2 -yes

 Delays in core may lead to user data interruptions.
Related parameters?
 N/A
•GUMMEI(c)
•STMSI(to UE)
IP
(to MME>EPC)
•PGW id
L1 L1 (to MME>EPC)
Control Plane

MME
eNb
NAS NAS

•IP (to UE)

S11
App D
APN
IP IP
User Plane
EPS Bearer (ID)

E-RAB (ID)
UDP UDP UDP
RLC RLC
IP IP IP
MAC MAC
L2 L2 L2
PHY PHY L1 L1 L1
S1-u
Log view
Wireshark
Log view S1AP Path Switch
Request Modify Bearer
Request
S1AP Path Switch

Modify Bearer Response
Response
End to End DATA!
Between Target eNB and SGW
HSS
Work sheet S6a
QOS
Identifiers
(Completed for Log Set 4) IP=
IP=10.52.40.93
MME IP=10.52.65.4
DNS
IP=10.52.65.20
S1ap id 918
Teid 0x03000085
S11
S1c PCRF
Teid 0x71000004
S1ap id 17
srb0
IP=10.48.131.5 Teid 0x >>>> Teid 0x72000004
srb1 IP=10.48.123.99 IP=10.48.130.141
srb2 IP=10.48.123.99 IP=10.52.40.137
UE Uu
eNB S1u
SGW IP=10.52.40.137
S5
IP=10.52.130.137
PGW
F9010
Drb5/ERAB6 X2ap id 2 Teid 0x000000c2 Teid 0x1000006 Teid 0x >>>> Teid 0x1000006
Teid 0x0000001a
Teid 0x0000001c S1ap id 3
Teid 0x00000019
eNB Teid 0x0000001b
APPENDIX
LTE Identifiers
IMSI International Mobile Subscriber Identity • Unique identification of mobile (LTE) subscriber
• Network (MME) gets the PLMN of the subscriber
MSIN Mobile Subscriber Identification Number • assigned by operator
TAI Tracking Area Identity • To identify Tracking Area
• Globally unique
MMEI MME Identifier • To identify a MME uniquely within a PLMN
• Operator commissions at eNb
GUMMEI Globally Unique MME Identity • To identify a MME uniquely in global
• GUTI contains GUMMEI
S-TMSI SAE Temporary Mobile Subscriber Identity • To locally identify a UE in short within a MME group (Unique within a MME Pool)
M-TMSI MME Mobile Subscriber Identity • Unique within a MME
GUTI Globally Unique Temporary UE Identity • To identify a UE between the UE and the MME on behalf of IMSI for security reason
PDCCH formats
3G vs LTE: Mobility and Connection terminology
• Physical downlink control channel (PDCCH)
• Informs the UE about the resource allocation of PCH and DL-SCH, and Hybrid ARQ information related
to DL-SCH
• Carries the uplink scheduling grant
• In general the number of bits required for resource assignment depends on the system bandwidth, and
therefore the message sizes also vary with the system bandwidth.
• 16 bit CRC is appended to each PDCCH and scrambled with UE CRNTI for UEs to identify its allocation.
This saves the additional payload but at the cost of a small increase in the probability of falsely detecting
a PDCCH intended for another UE.
• For robustness against transmission errors, PDCCH information bits are coded and rate matched. They
are then scrambled with cell specific scrambling sequence to reduce possibility of confusion with
neighboring cell PDCCH transmissions.
Supported DCI formats [5.3.3.1 in 3GPP-36.212]
DCI Format Purpose # of bits including 16 bit
CRC (for 10Mhz BW and 4
antennas at eNB)
0 PUSCH grants 42
1 PDSCH assignments with a single codeword 47
1A PDSCH assignments using a compact format for single codeword and allocating 42
dedicated preamble signature.
1B PDSCH assignments for a single codeword rank-1 transmission with Precoding 46
1C PDSCH assignments using a very compact scheduling of one codeword. 26
1D PDSCH assignments for multi-user MIMO 46
2 PDSCH assignments for closed-loop MIMO operation 62
2A PDSCH assignments for open-loop MIMO operation 58
3 Transmit Power Control (TPC) commands for multiple users for PUCCH and 42
PUSCH with 2-bit power adjustments
3A Transmit Power Control (TPC) commands for multiple users for PUCCH and 42
PUSCH with 1-bit power adjustments
DCI Form at PDSCH transm ission
(this field only
valid for inc17 Single Dual Closed Closed
onw ards) Stream Stream loop Loop
Single Tx Open SM SM
Stream Diversity loop SM 1 CW 2 CW
BCCH, PCCH, dlMimoMode = 0 1C
CCCH, RAR dlMimoMode > 0 1C
TM1: Single-antenna port; port 0 1

DCCH, DTCH TM2: Transmit Diversity 1
and MAC TM3: Open Loop spatial Multiplexing 2A
CEs TM4: Closed Loop Spatial Multiplexing 2
TM6: Closed Loop Rank=1 precoding 1B
spatial mode SingleTx TxDiv SM SM SM

numberOfLayers 1 2 2 1 2
PHY_PdschSendReq param eters
codeBookIndex 0 0 0 0,1,2,3 1 or 2
codeWordIndex 0 0 0 or 1 0 0 or 1

LTE End To End Call Flow: With Logs Using Common Troubleshooting Tools

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE End To End Call Flow: With Logs Using Common Troubleshooting Tools

Uploaded by

Copyright:

Available Formats

LTE end to end Call Flow

with Logs using common troubleshooting Tools

Gr/S6d CNR/HSS Operator services

Inter Cell RRM

Connection Mobility Cont.

UE •ECGI(c)(to MME>EPC) X2-c eNb S6a/S6d/S13

PDCP PDCP SCTP SCTP UDP UDP UDP

PHY PHY PHY L1 L1 L1 L1

EPS Bearer (ID)

Security Security Security Security Security Security

Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ

Scheduling / Priority Handling Scheduling / Priority Handling

Multiplexing UE1 Multiplexing UEn Multiplexing

PDCCH Physical channels

5 © Nokia Siemens Networks 2011

1 TBS per TTI per antenna

Ultimately TBS + Coding + CRC is

UE eNB SGW PGW

Who’s talking to who? (Source/Destination?)

Which is the channel path taken? Or who carries the payload?

Where is it acknowledged? Or is it?

How is QOS/KPI satisfied?

eNB is transmitting all

LTE signal analyzer shows

Total configured power of 20

Power is static for all

UE decodes the physical cell

• System information is divided into the MasterInformationBlock (MIB) and a number of

o SystemInformationBlockType5 contains information about other E‑UTRA frequencies and inter-

• SIB1 Scheduling (3GPP 36.331): SIB1 scheduled

– Periodicity: 160 ms 13:37:06:824 960 0 31 SI2

Who’s talking to who? (Source/Destination?)

Which is the channel path taken? Or who carries the payload?

Where is it acknowledged? Or is it?

How is QOS/KPI satisfied?

Security Security Security Security Security Security

Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ

Scheduling / Priority Handling Scheduling / Priority Handling

Multiplexing UE1 Multiplexing UEn Multiplexing

PDCCH Physical channels

19 © Nokia Siemens Networks 2011

Who’s talking to who? (Source/Destination?)

Which is the channel path taken? Or who carries the payload?

Where is it acknowledged? Or is it?

How is QOS/KPI satisfied?

Security Security Security Security Security Security

Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ

Scheduling / Priority Handling Scheduling / Priority Handling

Multiplexing UE1 Multiplexing UEn Multiplexing

PDCCH Physical channels

22 © Nokia Siemens Networks 2011

• The RACH procedure is used in four cases:

• Random access preamble:

Different root sequences

Random access response

Which is the channel path taken? Or who carries the payload?

How is QOS/KPI satisfied?

Security Security Security Security Security Security

Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ Seg/ARQ

Scheduling / Priority Handling Scheduling / Priority Handling

Multiplexing UE1 Multiplexing UEn Multiplexing

PDCCH Physical channels

29 © Nokia Siemens Networks 2011