EPS Architecture
EPS Architecture
EPS Interface protocols
LTE Channels
DL Channels
DL Channels
UL Channels
UL Channels
Example
xx-RNTI
Uu Interface Sublayers
Random Access procedure
Random Access Procedure (1/4)
(Contention based)
0.- eNB broadcast RACH and PRACH
configuration on SIB2
0.1. 64 preambles are configured per cell
1. UE selects randomly one of the
preambles and send it using an Initial
Tx Power.
1.1. Initial Tx Power is calculated
internally based on broadcasted
parameters.
1.2. When two UE’s transmit the same
preamble on the same PRACH
occasion, a contention decision should
be made.
Random Access Procedure (2/4)
(Contention based)
2. After sending the preamble, the UE waits for a Random Access Response (RAR).
2.1. The UE search for a RAR within a “Response Window” (parameter).
2.2. The response window starts during the 3rd subframe after sending the preamble
2.3. The RAR location is indicated by a PDCCH which CRC is encoded with the RA-RNTI.
2.4. The RA-RNTI is calculated as: RA-RNTI (FDD) = (1+t_id); where t_id is the subframe
index (0..9).
2.5. If UE does not find a PDCCH with the RA-RNTI within the window:
2.5.1. check if UE has transmitted Max allowed preamble transmissions.
2.5.2. Increase Preamble Tx couter (this will increase the next Tx power)
2.5.3. wait for Backoff indicator to expire
2.5.4. Select another preamble and transmit it with new increased tx power.
Random Access Procedure (3/4)
(Contention based)
2A.- The RAR includes several subheaders, one per UE to be addressed by that RAR.
There are two types of subheaders:
2A.1. Backoff Indicator (optional): Indicates the time to wait before next RA attempt.
2A.2. UE Specific. These includes a subheader and a payload:
2A.2.1. RAPID: Random Access Preamble ID. Id the UE. In case on Contention, this can be
received by more than one UE. (subheader)
2A.2.2. Timing advance Information. (payload)
2A.2.3. UL grant: for the UE to send the Msg3. In case of contention, 2xUE’s will send its
Msg3 on the same resources. (payload)
2A.2.4. temporary C-RNTI. (payload)
3. UE sends Initial L2/L3 msg (Msg3, i.e. RRCConnectionRequest) on the UL RB’s
indicated on the RAR.
3.1. In case on contention, 2xUE’s will use the same UL RB’s to send their L3 msg.
3.2. layer 3 msg contains an Unique UE ID. Either S-TMSI or a randomly generated
40 bits number.
Random Access Procedure (4/4)
(Contention based)
4.- eNB will reply with a UE Contention Resolution Id MAC Control Element.
4.1. As 2xUE’s send their Initial L3 msg at the same time and on the same RB’s,
they will interfere each other. The eNB may detect one of them, none of them or
both of them.
4.2. In the CRID CE, the eNB includes a copy of the L3 message sent by one of the
UE. This will solve the contention as the Initial L3 msg is unique.
4A. After successful reception of the CRID, the UE considers the temporary C-RNTI
as the C-RNTI.
RRC Connection SetUp procedure
RRC Connection Setup Procedure (1/2)
1.- UE sends RRCConnectionRequest message.
1.1. This msg is the Initial L2/L3 msg (Msg3) of the RA Procedure.
1.2. The msg uses SRB0 which is transported onto CCCH / UL-SCH / PUSCH
1.3. This msg includes:
1.3.1: UE Identity: S-TMSI (if UE is registered already on the TA) or Random number (40 bits)
1.3.2. Establishment Cause: Emergency, MT Access, MO Signalling, MO Data
RRC Connection Setup Procedure (2/2)
2.- eNB sends RRCConnectionSetup message.
2.1. The msg uses SRB0 which is transported onto CCCH / DL-SCH / PDSCH
2.2. This msg contains SRB1 configuration information.
2.2.1: SRB1 Retransmission timer, PDU size, re-ordering timer, etc..
2.2.2. This message may include also CQI reporting configuration information, phys CH configuration,
Power Control information, etc..
2.3. When the UE receives this msg, the UE makes the transition to RRC_CONNECTED
Mode
3. UE send RRCConnectionSetupComplete message.
3.1. This msg includes (list not complete):
• RRC Transaction ID
• PLMN ID
• Registered MME: GUMMEI (if available) (PLMN ID + MMEGI + MMEC)
• Dedicated NAS Information: Attach, Detach, TAU, Service Request, Extended Service Request (i.e. CSFB)
RRCConnectionRequest
RRCConnectionSetup 1/4
RRCConnectionSetup 2/4
RRCConnectionSetup 3/4
RRCConnectionSetup 4/4
RRCConnectionSetupComplete
Initial AS Security
TS 36.331
AS security comprises of the integrity protection of RRC signalling (SRBs) as
well as the ciphering of RRC signalling (SRBs) and user data (DRBs).
The AS applies three different security keys: one for the integrity protection of
RRC signalling (KRRCint), one for the ciphering of RRC signalling (KRRCenc) and one
for the ciphering of user data (KUPenc). All three AS keys are derived from the
KeNB key. The KeNB is based on the KASME key, which is handled by upper layers.
Initial AS Security
RLC
RLC: UM Header with Extensions
RLC: UM
Example Segmentation/Concatenation
RLC: AM
Example Segmentation/Concatenation
S1AP
S1AP
Source to Target Transparent Container
TS 36.413
Included in the HANDOVER REQUIRED message
Options:
Source eNB to Target eNB Transparent Container IE (Intra LTE HO)
Source RNC to Target RNC Transparent Container IE (HO to UTRAN) (TS 25.413)
Source BSS to Target BSS Transparent Container IE (HO to 2G) (TS 48.018)
S1AP
Target to Source Transparent Container
TS 36.413
Included in the HANDOVER COMMAND message
Options:
Target eNB to Source eNB Transparent Container IE (Intra LTE HO)
Target RNC to Source RNC Transparent Container IE (HO to UTRAN) (TS 25.413)
Target BSS to Source BSS Transparent Container IE (HO to 2G) (TS 48.018)
NAS
NAS Message format
NAS Protocol Discriminator
NAS
EPS Mobility Managements (EMM) messages
NAS
EPS Session Managements (ESM) messages
CS FallBack
CSFB Architecture
CSFB
•CS Fallback requires the introduction ofthe SGs interface.
•SGs interface connects the MME (LTE PS core network) to the MSC (2G and 3G CS
core network).
•The MSC can use this interface to fo rward CS core network domain paging
messages to the UE on LTE
•Signalling across the SGs interface is based upon the SGs Application Protocol
(SGsAP) (TS 29. 1 18).
•A UE using CS Fallback must be registered with both the EPC and CS core network
domains. This is achieved by completing a “combined EPS/IMSI Attach” procedure
from the LTE network.
CSFB
