0% found this document useful (0 votes)
237 views13 pages

LTE Call Flows - Architecture Usman Ghani Ericsson

1. The document shows the overall architecture of an Evolved Packet System (EPS) including key network elements like the E-UTRAN, EPC, and interfaces between them. 2. The EPS architecture supports both LTE access (via the E-UTRAN) and non-3GPP access to the Evolved Packet Core (EPC). 3. The interfaces defined in the EPS architecture include S1 between E-UTRAN and EPC, S5/S8 between the EPC gateways, and X2 between eNodeBs in the E-UTRAN.

Uploaded by

usmanghani8257
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
237 views13 pages

LTE Call Flows - Architecture Usman Ghani Ericsson

1. The document shows the overall architecture of an Evolved Packet System (EPS) including key network elements like the E-UTRAN, EPC, and interfaces between them. 2. The EPS architecture supports both LTE access (via the E-UTRAN) and non-3GPP access to the Evolved Packet Core (EPC). 3. The interfaces defined in the EPS architecture include S1 between E-UTRAN and EPC, S5/S8 between the EPC gateways, and X2 between eNodeBs in the E-UTRAN.

Uploaded by

usmanghani8257
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 13

Overall Architecture MTAS

AS
AS AS
Service Layer

Application Servers Network & Service


management
IMS Control
WLAN I-CSCF layer OSS-RC EMA

MGC DNS/ MM DNS/ENUM


Broadband ENUM
Wired Access P-CSCF S-CSCF

PSTN IMS Connectivity Internet


A-SBG layer
N-SBG
Rx+

MGW User data


RTP/UDP GTP/UDP
PCRF
SIP/UDP or SIP/TCP
S7/Gx
GTP-C
CS Core GPRS EPC
Packet GGSN HSS ISUP
S6d
GWMSC Core S1-AP, X2-AP
Gxa CDMA2000
MSC SGSN HRPD H.248
S4 S6a
(EV-DO) Diameter
S2a PDSN
P-GW Other
S101 RNC
S3 MME
S5/S8
GERAN UTRAN S11 S103 Platforms / Concepts
S-GW
CPP /
RBS6000 TSP/NSP or
S1-CP S1-UP TSP/IS

E-UTRAN
Juniper/
SUN
X2-UP Redback
Uu

eNodeB X2-CP eNodeB


WPP IS

. Figure1 1 - EPS Architecture


3GPP TSG RAN

. Figure2 1 - EPS Architecture


LTE Specifications
36.201 – Physical layer general description 36.401 – E-UTRA Architecture Description
36.211 – Physical channels and modulation 36.410 – S1 interface general aspects & principle
36.212 – Multiplexing and channel coding 36.411 – S1 interface Layer 1
36.213 – Physical layer procedures 36.412 – S1 interface signalling transport
36.214 – Physical layer measurements 36.413 – S1 application protocol S1AP
36.414 – S1 interface data transport
36.420 – X2 interface general aspects and principles
36.421 – X2 interface layer1
36.422 – X2 interface signalling transport
36.423 – X2 interface application part X2AP
36.300 – E-UTRA overall description
36.442 – UTRAN Implementation Specific O&M Transport
36.302 – Services provided by the physical layer
36.304 – UE Functions related to idle mode
36.306 – UE radio access capabilities
23.002 – Network Architecture
36.321 – Medium Access Control (MAC)
23.003 – Numbering, addressing and identification
Protocol Specification
23.009 – Handover Procedures
36.322 – Radio Link Control (RLC)
23.048 – Security mechanisms for USIM application
Protocol Specification
23.401 – GPRS enhancements for eUTRA
36.323 – Packet Data convergence Protocol (PDCP)
23.907 – QoS Concept
Protocol Specification
36.331 – Radio Resource Control (RRC)
Protocol Specification
33.401 – System Architecture Evolution (SAE);
Security Architecture

36.101 – UE radio transmission and reception (FDD)


36.104 – BTS radio transmission and reception (FDD) 24.301 – NAS Protocol for Evolved Packet System (EPS)
36.113 – Base station EMC 24.302 – Access to the EPC via non 3GPP networks
36.133 – Requirements for support of Radio Resource
Management (FDD)
36.141 – Base station conformance testing (FDD)
All specifications can be found on the

web site www.3gpp.org


. Figure3 1 - EPS Architecture
Channel mapping
Downlink Uplink

PCCH MTCH MCCH BCCH DTCH DCCH CCCH DTCH DCCH CCCH
Logical Channels
“type of information”
MIB SIB (traffic/control)

PCH MCH BCH DL-SCH UL-SCH RACH


Transport Channels
“how and with what
characteristics”
(common/shared/mc/bc)
-Sched TF DL
-Sched grant UL -CQI
PDCCH -Pwr Ctrl cmd -ACK/NACK
info -HARQ info ACK/NACK -Sched req. Physical Channels
“bits, symbols,
PMCH PBCH PDSCH PCFICH PDCCH PHICH PUCCH PUSCH PRACH modulation, radio
frames etc”
-meas for DL sched
-meas for mobility -half frame sync -frame sync -measurements
-coherent demod -cell id -coherent demod for UL scheduling
-cell id group Physical Signals
“only L1 info”
RS P-SCH S-SCH RS SRS

. Figure4 1 - EPS Architecture


Radio Link Failure

RRC CONNECTION RE-ESTABLISHMENT REQUEST

RRC CONNECTION RE-ESTABLISHMENT

RRC CONNECTION RE-ESTABLISHMENT COMPLETE

RRC CONNECTION RE-ESTABLISHMENT REQUEST

RRC CONNECTION RE-ESTABLISHMENT REJECT

. Figure5 1 - EPS Architecture


MME
1. System Information *

Cell
Select *
RRC IDLE 2. Random Access Preamble
3. Random Access Response

4. RRC CONNECTION REQUEST

5. RRC CONNECTION SETUP

6. RRC CONNECTION SETUP COMPLETE (Attach Request)


7. INITIAL UE MESSAGE (Attach Request)

8.RRC DL INFORMATION TRANSFER (UE Identity Request) DL NAS TRANSFER (UE Identity Req)

9. RRC UL INFORMATION TRANSFER (UE Identity Response) UL NAS TRANSFER (UEid Response)

10.RRC DL INFORMATION TRANSFER (Authentication Request) DL NAS TRANSFER (Authentication)

11. RRC UL INFORMATION TRANSFER (Authentication Response) UL NAS TRANSFER (Auth. Response)

12. RRC DL INFORMATION TRANSFER (Security Mode Command) DL NAS TRANSFER (NAS SMC)
UE Attach

13. RRC UL INFORMATION TRANSFER (Security Mode Complete) UL NAS TRANSFER (NAS SMC)
14. INITIAL CONTEXT SETUP REQUEST
15. RRC SECURITY MODE COMMAND (EPS bearers, Attach Accept, Security)
16.RRC SECURITY MODE COMPLETE

17. RRC UE CAPABILITY ENQUIRY

18. RRC UE CAPABILITY iNFORMATION


19. UE CAPABILITY INFO INDICATION
20. RRC CONNECTION RECONFIGURATION (Bearer Setup) (UE Radio Capability)
21. RRC CONNECTION RECONFIGURATION COMPLETE
22. INITIAL CONTEXT SETUP RESPONSE
(EPS bearers)
23. RRC UL INFORMATION TRANSFER (Attach Complete)) UL NAS TRANSFER (Attach Complete)

24. UE CONTEXT RELEASE COMMAND


RRC IDLE
26. RRC CONNECTION RELEASE 25. UE CONTEXT RELEASE COMPLETE

. Figure6 1 - EPS Architecture


Sequence Numbering
WHY: * Reordering
* Duplicate detection
* Integrity protection
* Ciphering

eNB

SRB1_UL COUNT SRB1_UL

SRB1_DL COUNT SRB1_DL


UE
UE
UE
UE Ctx
DRB_UL COUNT-C DRB_UL
Ctx
DRB_DL COUNT-C DRB_DL

HOW:
PDCP SN:
HFN PDCP SN Next_PDCP_TX_SN
TX_HFN
COUNT
. Figure7 1 - EPS Architecture
Header Compression
8
WHY: Saving the bandwith by V=4 Hlen TOS Packet length
STATIC
HOW: *removing redundant info Identification Flags Fragment offset
Protocol Checksum INFERRED
*Encoding important info IPv
4
TTL
Source address CHANGES
*Hop by Hop Destination address
RARELY
*Unidirectional Source port Destination port
CHANGES
UD OFTEN
P Length Checksum
PT Appr. 30 of
V P X CC M Sequence no
40 octets are
RT Timestamp static or
P easily
SSRC Identifier
compressible!

UE/UE Context

PDCP PDU Header


Header PDCP PDU RB_UL PDCP PDU RB_UL

CRC Compressed Header


checksum covering the header before Contains encoded data
compression is included in the compressed header
UE/UE Context

. Figure8 1 - EPS Architecture


Logical Channel Prioritzation UL
Priority order

Bj B3 B2 B1
TTI n+3
TTI n+2
TTI n+1
... Max Bucket size= PBR x BSD
At each TTI
TTI n Bucket size = bucket size + PBR

DTCH DTCH DCCH DCCH


... PBR LCH4
PBR LCH3
PBR LCH2

PBR LCH1
UL-SCH

. Figure9 1 - EPS Architecture


S-GW MME
Source eNB Target eNB
RRC 1. RRC CONNECTION RECONFIGURATION
CONNECTED (Bearer Setup,Measurement conf))

2. RRC Measurement Report


(Event A3)
3. HO
Decision

4. X2 HANDOVER REQUEST

5.Admission
TRELOCprep Control
6. X2 HANDOVER REQUEST
ACKNOWLEDGE
8. Start Data
forwarding 7. X2 SN STATUS TRANSFER
X2 Handover

T304
10. RRC CONNECTION RECONFIGURATION 9. Buffer
(Handover Command,Measurement conf) Forwarded
Data
Regenerate
11 MAC: CFRA Random Access Preamble
Security Keys
12. MAC Random Access Response (UL allocation + TA)

13. RRC CONNECTION RECONFIGURATION COMPLETE


(Handover Complete)
14.Data Transfer in Target
15. S1 PATH SWITCH REQUEST
16. S5 USER PLANE
17.Data Transfer in Target UPDATE REQ
18. S5 USER PLANE
UPDATE RSPONSE
19. S1 PATH SWITCH RESPONSE

RRC 20. X2 UE CONTEXT RELEASE


CONNECTED 21. Forward if any
Data in transition
and release
. Figure101 - EPS Architecture
DL Data Forwarding
end marker
S-GW
PDCP SN is continuous
through Handover

X2APNext SN = 7

Transmitter State 6 5 4

6 Source eNB Target eNB


5

4
Status:
Receiver State
ACK 4 & 5

5
4
• Source forwards outstanding un-ACK:ed SDUs to target with their SN attached.
• Source tells Target what PDCP SN to allocate next.
• Non-outstanding SDUs are forwarded (in order) without SN
• Target “prioritizes” forwarded SDUs.
• UE re-orders PDCP SDUs based on the SN.
• UE may submit a PDCP Status to guide Target re-Tx
• NO Data forwarding for SRBs; PDCP SN and HFN are reset @ target

. Figure111 - EPS Architecture


UL Data Forwarding
S-GW
PDCP SN is continuous
“3”
through Handover

“4”
Receiver State
X2_AP:
6 ACK 4, NACK 5

5
6
Source eNB Target eNB
4

3 PDCPStatus report:
5
Transmitter State ACK4, NACK 5
6
5

3
• Source forwards SDUs received out-of-sequence to
Target with their SN attached.
• Target re-orders PDCP SDUs.
• Target may submit a PDCP Status
(or, a Status tunneled from Source)
to UE to guide re-transmissions to Target.

. Figure121 - EPS Architecture


S-GW S-GW MME MME
Source
Source eNB
eNB Target
Target eNB
eNB Source Target Source Target
RRC 1. RRC CONNECTION RECONFIGURATION
CONNECTED (Bearer Setup,Measurement conf))

2. RRC Measurement Report


S1 Handover
(Event A3)
3. HO
Decision

4. S1 HANDOVER REQIRED
(Source to Target Transparent Container ) 5. S10 FORWARD RELOCATION
TS1RELOCprep REQUEST
6. S11 CREATE BEARER REQ/RES
7. S1 HANDOVER REQUEST

8. Admission
Control
9. S1 HANDOVER REQUEST ACKNOWLEDGE
10. S10 FORWARD RELOCATION
RESPONSE
11. S11 CREATE BEARER REQ/RES
UP Forwarding
12. S1 HANDOVER COMMAND
T304 12. RRC CONNECTION RECONFIGURATION
(Handover Command,Measurement conf)
13 MAC: CFRA Random Access Preamble
Regenerate 14. MAC Random Access Response (UL allocation + TA)
Security Keys
15. RRC CONNECTION RECONFIGURATION COMPLETE
(Handover Confirm) 16. S1 HANDOVER NOTIFY

17.Data Transfer in Target

18.S10 FORWARD RELOCATION


RRC COMPLETE/ ACK
CONNECTED 19. S1 UE CONTEXT RELEASE COMMAND
(Cause: Successful Handover)

. Figure131 - EPS Architecture

You might also like