RA47055EN16AGLA0 Basic Signaling

LTE Basic Signaling Slide 1

NokiaEDU LTE Basic Signaling LTE Optimization Principles [FL16A] Module 05

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

1


Copyright and confidentiality

The contents of this document are proprietary and confidential property of Nokia. This document is provided subject to confidentiality obligations of the applicable agreement(s). This document is intended for use of Nokia’s customers and collaborators only for the purpose for which this document is submitted by Nokia. No part of this document may be reproduced or made available to the public or to any third party in any form or means without the prior written permission of Nokia. This document is to be used by properly trained professional personnel. Any use of the contents in this document is limited strictly to the use(s) specifically created in the applicable agreement(s) under which the document is submitted. The user of this document may voluntarily provide suggestions, comments or other feedback to Nokia in respect of the contents of this document ("Feedback").

2

Such Feedback may be used in Nokia products and related specifications or other documentation. Accordingly, if the user of this document gives Nokia Feedback on the contents of this document, Nokia may freely use, disclose, reproduce, license, distribute and otherwise commercialize the feedback in any Nokia product, technology, service, specification or other documentation. Nokia operates a policy of ongoing development. Nokia reserves the right to make changes and improvements to any of the products and/or services described in this document or withdraw this document at any time without prior notice. The contents of this document are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose,

RA47055EN16AGLA0

are made in relation to the accuracy, reliability or contents of this document. NOKIA SHALL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT or for any loss of data or income or any special, incidental, consequential, indirect or direct damages howsoever caused, that might arise from the use of this document or any contents of this document. This document and the product(s) it describes are protected by copyright according to the applicable laws. Nokia is a registered trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.

© Nokia 2016

RA47055EN16AGLA0

2


Index - EMM and ECM/RRC states - Signaling example: Attach + default bearer establishment - Backup slides

4

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

3


EMM & ECM States Transitions Power On Release due to Inactivity

Registration (Attach)

• Allocate S-TMSI • Allocate IP address + default bearer • Authentication • Establish security context EMM_Deregistered ECM_Idle

• Release RRC + S1 connection • Configure DRX for paging • eNB initiated (inactivity timer)

EMM_Registered

EMM_Registered

ECM_Connected

ECM_Idle

New Traffic

Deregistration (Detach) Change PLMN

• Release S-TMSI • Release IP addresses • UE, MME or HSS initiated

• Activate RRC + S1 connection

Timeout of Periodic TA Update

• Release S-TMSI • Release IP addresses 5

RA47055EN16AGLA0

© Nokia 2016

C-RNTI: Cell Radio Network Temporary Identifier. Uniquely identifies a UE within a cell. Only exists if UE is connected. Assigned by the eNodeB. S-TMSI: SAE- Temporary Mobile Subscriber Identifier: uniquely identifies the UE within a tracking area. Assigned by the MME. TA Update: Tracking Area Update

RA47055EN16AGLA0

4


UE EMM / RRC States Transition - Two main UE EMM states *) : • REGISTERED • DEREGISTERED

- EMM-REGISTERED has two substates: • IDLE (=ECM-IDLE + RRC-IDLE) • CONNECTED (=ECM-CONNECTED + RRC-CONNECTED)

- Bookkeeping of UE state in MME (MML command ZMMO) - DEREGISTERED: UE location unknown to MME, UE cannot be paged. - REGISTERED: EPS default bearer has been activated (“always-on”, UE has IP@). Two substates: • ECM-IDLE/RRC-IDLE: UE location known at TA level. Transition to CONNECTED takes place by: i) paging needed if DL user data arrives; ii) UE triggers RRC CONNECTION REQUEST. UE makes cell reselection and TAU. • ECM-CONNECTED/RRC-CONNECTED: UE location known at cell level, UE is in RRCCONNECTED. UE changes cell by handover. *) also transition states between these are defined in 3GPP, skipped here.

6

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

5


Moving from IDLE to CONNECTED -

UE moves from IDLE to CONNECTED by sending an initial NAS message

-

The initial NAS message in 3GPP Rel8 can be

•

EMM ATTACH REQUEST;

•

EMM DETACH REQUEST;

•

EMM TRACKING AREA UPDATE REQUEST;

•

EMM SERVICE REQUEST; or

•

EMM EXTENDED SERVICE REQUEST (CSFB call)

-

Default bearer is set up at the same time with attach

-

Signaling bearers are setup, when UE moves to CONNECTED: SRB ID

7

RA47055EN16AGLA0

© Nokia 2016

ESM = EPS Session Management

RA47055EN16AGLA0

6


Index - EMM and ECM/RRC states - Signaling example: Attach + default bearer establishment - Backup slides

8

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

7


Signaling example, Attach Request UE

eNB

MME

PRACH RANDOM ACCESS PRACH RANDOM ACCESS RESPONSE

Steps:

PUSCH (Msg3) RRC: Connection Request random access procedure

RRC: Connection Setup RRC: Connection Setup Complete + EMM ATT_REQ + ESM PDN CONN_REQ

S1AP: INITIAL UE MESSAGE + EMM ATT_REQ + ESM PDN CONN_REQ

NAS Security Establishment (Authentication + NAS security start)

S1AP: INITIAL CONTEXT SETUP REQUEST + EMM ATT_ACC + ESM ACT_DEF_BEAR_REQ

RRC: Security Mode Command RRC: UECapabilityEnquiry

1. 2. 3. 4. 5. 6. 7.

Random Access Initial NAS msg NAS security S1 init setup RRC sec + UE cap SRB2/DRB setup NAS reply

RRC: Security Command Complete UE radio capabilities available à DRB can be established

RRC: UECapabilityInformation

DRB and SRB2 Configuration

RRC: RRCConnectionReconfiguration + EMM ATT_ACC + ESM ACT_DEF_BEAR_REQ RRC:

RRCConnectionReconfigurationComplete S1AP:

INITIAL CONTEXT SETUP RESPONSE

S1AP:

UE CAPABILITY INFO INDICATION

RRC: UL NAS INFO TRANSFER (EMM ATT_COMPLETE + ESM ACT_DEF_BEAR_SUCC S1AP: UL NAS TRANSPORT (EMM ATT_COMPLETE + ESM ACT_DEF_BEAR_SUCC)

9

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

8


Random Access Procedure, general The random access procedure is performed for the following five events: 1.

Initial access from RRC_IDLE (as in this signaling example);

2.

RRC Connection Re-establishment procedure;

3.

Handover;

4.

DL data arrival during RRC_CONNECTED requiring random access procedure, when UL TA synchronization status is “non-synchronized”

5.

UL data arrival during RRC_CONNECTED requiring random access procedure, when UL TA synchronization status is "non-synchronized" or there are no PUCCH resources for SR available

Furthermore, the random access procedure takes two distinct forms:

•

Contention based (applicable to all five events);

•

Non-contention based (applicable to handover and DL data arrival).

10

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

9


Random Access Procedure, contention-based MME

eNB

UE

1 PRACH MAC Random Access Preamble

2 PDCCH MAC RA-RNTI 2 PDSCH MAC Random Access Response 3 UL-SCH RLC TM SRB0 RRC-ConnectionRequest() 4 PDSCH MAC Contention Resolution

DL-SCH RLC TM SRB0 RRC-ConnectionSetup UL-SCH RLC AM SRB1 RRC-ConnectionSetupComplete (NAS)

11

RA47055EN16AGLA0

S1AP: initiatingMessage INITIAL UE MESSAGE (NAS)

© Nokia 2016

RA47055EN16AGLA0

10


Random Access Procedure, contention-based (1/2)

UE

1

eNB

Random Access Preamble

1. Random Access Preamble on RACH in uplink: Random Access Response

3

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.

2

Scheduled Transmission

2. Random Access Response generated by MAC on DL-SCH: Contention Resolution

12

• Semi-synchronous (within a flexible window of which the size is one or more TTI) with message 1; • No HARQ; • Addressed to RA-RNTI on PDCCH; • Conveys at least RA-preamble identifier, Timing Alignment information, initial UL grant and assignment of Temporary C-RNTI (which may or may not be made permanent upon Contention Resolution); • Intended for a variable number of UEs in one DL-SCH message.

4

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

11


Random Access Procedure, contention-based (2/2) 3. First scheduled UL transmission on UL-SCH: • •

UE

1

eNB


Random Access Response

3

Scheduled Transmission

Contention Resolution

13

2

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: • Conveys the RRC Connection Request generated by the RRC layer and transmitted via CCCH; • Conveys at least NAS UE identifier but no NAS message; • RLC TM: no segmentation; For RRC Connection Re-establishment procedure: • Conveys the RRC Connection Re-establishment Request generated by the RRC layer and transmitted via CCCH; • RLC TM: no segmentation; • Does not contain any NAS message. After handover, in the target cell: • Conveys the ciphered and integrity protected RRC Reconfig Complete generated by the RRC layer and transmitted via DCCH; • Conveys the C-RNTI of the UE (which was allocated via the Handover Command); • Includes an uplink Buffer Status Report when possible. For other events: • Conveys at least the C-RNTI of the UE.

4

4. Contention Resolution on DL: Early contention resolution shall be used i.e. eNB does not wait for NAS reply before resolving contention Not synchronized with message 3; HARQ is supported; - Addressed to: The Temporary C-RNTI on PDCCH for initial access and after radio link failure; 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 CRNTI, resumes using its C-RNTI.

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

12


Random Access Procedure, dedicated preamble

UE

0. Random Access Preamble assignment via dedicated signaling in DL: • eNB assigns to UE a non-contention Random Access Preamble (a Random Access Preamble not within the set broadcasted on BCH). • Signalled via: • HO command generated by target eNB and sent via source eNB for handover; • PDCCH in case of DL data arrival

eNB

RA Preamble assignment

0


1

1. Random Access Preamble on RACH in uplink: • UE transmits the assigned non-contention Random Access Preamble. Random Access Response

2

2. Random Access Response on DL-SCH: • Semi-synchronous (within a flexible window of which the size is one or more TTI) with message 1; • No HARQ; • Addressed to RA-RNTI on PDCCH; Conveys at least: • Timing Alignment information and initial UL grant for handover; • Timing Alignment information for DL data arrival; • RA-preamble identifier. • Intended for one or multiple UEs in one DL-SCH message.

14

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

13


Signaling example, Attach Request (NEXT) UE

eNB

MME


Steps:







1. 2. 3. 4. 5. 6. 7.

Random Access Initial NAS msg NAS security S1 init setup RRC sec + UE cap SRB2/DRB setup NAS/S1AP cleanup







S1AP:



15

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

14


RRC Connection Setup (sent on SRB0, RLC TM) RRC SIGNALING MESSAGE Time:

13:32:15.561

RRCConnectionSetup

(3GPP TS 36.331 ver 8.7.0 Rel 8)

DL-CCCH- Message message c1 rrcConnectionSetup rrc-TransactionIdentifier :2 criticalExtensions c1 rrcConnectionSetup-r8 radioResourceConfigDedicated srb-ToAddModList srb-ToAddModList value 1 srb-Identity : 1 rlc-Config : defaultValue logicalChannelConfig : defaultValue mac-MainConfig explicitValue ul-SCH-Config maxHARQ-Tx : n3 periodicBSR-Timer : infinity retxBSR-Timer : sf2560 ttiBundling : false timeAlignmentTimerDedicated physicalConfigDedicated pusch-ConfigDedicated betaOffset-ACK-Index : 10 betaOffset-RI-Index : 12 betaOffset-CQI-Index :8 cqi-ReportConfig cqi-ReportModeAperiodic : rm30 nomPDSCH- RS- EPRE- Offset schedulingRequestConfig setup sr-PUCCH-ResourceIndex : 18 sr-ConfigIndex :7 dsr-TransMax : n64

16

RA47055EN16AGLA0

Establishing SRB1, 3GPP, default RLC config used in this example

TA Timer value = 5120ms : sf5120

Aperiodic CQI reporting :0

SR-PUCCH config

© Nokia 2016

RA47055EN16AGLA0

15



eNB

MME


Steps:







1. 2. 3. 4. 5. 6. 7.








S1AP:



17

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

16


NAS AKA + NAS Security Mode Command UE

MME AUTHENTICATION REQUEST

AUTHENTICATION RESPONSE AUTHENTICATION REJECT

UE

Start T3460 Stop T3460 if authentication failed

UE derives internally encryption and integrity keys based on RAND and USIM-stored secret K

MME SECURITY MODE COMMAND

SECURITY MODE COMPLETE

Start T3460 Stop T3460

NAS signaling encryption and integrity protection started (note: RRC security started later with separate RRC msg)

OR SECURITY MODE REJECT

18

RA47055EN16AGLA0

Stop T3460

© Nokia 2016

RA47055EN16AGLA0

17



eNB

MME


Steps:







1. 2. 3. 4. 5. 6. 7.

Random Access Initial NAS msg NAS security S1 Init Cntx Setup RRC sec + UE cap SRB2/DRB setup NAS/S1AP cleanup







S1AP:



19

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

18


S1AP Initial Context Setup, information elements From MME to eNB:

UE-AMBR stored in HSS E-RAB list for setting up RRC security for setting up RRC security if MME has this stored, it sends to BTS if MO/MT CSFB to 2G/3G LAC, needed in LAU in target RAT

20

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

19


S1AP Initial Context Setup, example

UE-AMBR

Default RAB info

S-GW IP@ for this S1 bearer

21

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

20



eNB

MME


Steps:







1. 2. 3. 4. 5. 6. 7.








S1AP:



22

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

21


Security Mode Command / Complete Time: 13:57:43.491 SecurityModeCommand (3GPP TS 36.331 ver 8.7.0 Rel 8) DL-DCCH-Message message c1 securityModeCommand rrc-TransactionIdentifier :2 criticalExtensions c1 securityModeCommand-r8 securityConfigSMC securityAlgorithmConfig cipheringAlgorithm : eea2 integrityProtAlgorithm : eia2

Ciphering + integrity algorithm used

Time: 13:57:43.491 SecurityModeComplete (3GPP TS 36.331 ver 8.7.0 Rel 8) UL-DCCH-Message message c1 securityModeComplete rrc-TransactionIdentifier criticalExtensions securityModeComplete-r8

23

:2 :

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

22


UE capability enquiry (3GPP TS 36.300) - eNB needs to know UE Radio Capability • Received from MME in S1 INITIAL CONTEXT SETUP REQUEST, or • Enquired from UE using RRC UECapabilityEnquiry (eNB updates MME after this)

UE

MME

eNB S1-AP: INITIAL CONTEXT SETUP REQUEST <23.401: UE Security Capabilities + 36.331: UE Radio Capability:

UERadioAccessCapabilityInformation> S1-AP: INITIAL CONTEXT SETUP RESPONSE

eNB decides if more capabilities are needed, e.g. based on - which other RATs the UE supports - if such neighbour cells are present RRC: UECapabilityEnquiry <36.331: RAT-Type> RRC: UECapabilityInformation <36.331: RAT-Type + UE-CapabilityRATContainer>

eNB keeps capabilities during RRC CONNECTED state and builds one UERadioAccessCapabilityInformation message consisting of all known capabilities excluding the UTRAN capability S1-AP: UE CAPABILITY INFO INDICATION <36.331: UE Radio Capability:

UERadioAccessCapabilityInformation>

MME keeps capabilities until DETACH or ATTACH (see 23.401, 5.11.2) 24

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

23


UE Capability Info, Feature Group Indicator bitmap …. …. interRAT-BandList value 5 interRAT-NeedForGaps : true interRAT-BandList value 6 interRAT-NeedForGaps : true featureGroupIndicators Bin : 5E 0D D8 80 (= 1577965696) interRAT-Parameters utraFDD supportedBandListUTRA-FDD supportedBandListUTRA-FDD value 1 supportedBandListUTRA-FDD value 2 geran supportedBandListGERAN supportedBandListGERAN value 1 supportedBandListGERAN value 2 supportedBandListGERAN value 3 supportedBandListGERAN value 4 interRAT-PS-HO-ToGERAN : false

25

RA47055EN16AGLA0

Not decoded by all tools, see TS 36.331 Annex B

: bandI : bandVIII

: gsm850 : gsm900E : gsm1800 : gsm1900

© Nokia 2016

RA47055EN16AGLA0

24


UE Capability Info, Feature Group Indicator bitmap featureGroupIndicators: 5e0dd880 [bit length 32] 0... .... = Indicator 1: Intra-subframe freq hopping for PUSCH scheduled by UL grant; DCI format 3a; PDSCH transmission mode 5;Aperiodic CQI/PMI/RI report on PUSCH: Mode 2-0 and 2-2 - Not supported

.1.. .... = Indicator 2: Simultaneous CQI and ACK/NACK on PUCCH (format 2a/2b); Absolute TPC command for PUSCH; Resource alloc ty pe 1 for PDSCH; Periodic CQI/PMI/RI report on PUCCH: Mode 2-0 and 2-1 - Supported ..0. .... = Indicator 3: 5bit RLC UM SN; 7bit PDCP SN - Not supported ...1 .... = Indicator 4: Short DRX cy cle - Supported

.... 1... = Indicator 5: Long DRX cy cle; DRX command MAC control element - Supported .... .1.. = Indicator 6: Prioritised bit rate - Supported .... ..1. = Indicator 7: RLC UM - Supported

.... ...0 = Indicator 8: EUTRA RRC_CONNECTED to UTRA CELL_DCH PS handov er - Not supported 0... .... = Indicator 9: EUTRA RRC_CONNECTED to GERAN GSM_Dedicated handov er - Not Supported .0.. .... = Indicator 10: EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order; EUTRA RRC_CONNECTED to GERAN (Pac ket_) Idle by Cell Change Order w ith NACC - Not supported

..0. .... = Indicator 11: EUTRA RRC_CONNECTED to CDMA2000 1x RTT CS Activ e handover - Not supported ...0 .... = Indicator 12: EUTRA RRC_CONNECTED to CDMA2000 HRPD Activ e handov er - Not supported .... 1... = Indicator 13: Inter-frequency handov er - Supported .... .1.. = Indicator 14: Measurement reporting ev ent: Ev ent A4 - Neighbor > threshold; Measurement reporting ev ent: Ev ent A5 - Serv ing < threshold1 & Neighbor > threshold2 - Supported .... ..0. = Indicator 15: Measurement reporting ev ent: Ev ent B1 - Neighbor > threshold - Not supported .... ...1 = Indicator 16: non-ANR related periodical measurement reporting - Supported 1... .... = Indicator 17: Periodical measurement reporting for SON / ANR; ANR related intra-frequency measurement reporting ev ents - Supported .1.. .... = Indicator 18: ANR related inter-frequency measurement reporting ev ents - Supported ..0. .... = Indicator 19: ANR related inter-RAT measurement reporting ev ents - Not supported ...1 .... = Indicator 20: SRB1 and SRB2 for DCCH + 8x AM DRB; SRB1 and SRB2 for DCCH + 5x AM DRB + 3x UM DRB (if indicator 7 is supported) - Supported .... 1... = Indicator 21: Predefined intra- and inter-subframe frequency hopping for PUSCH w ith N_sb > 1; Predefined inter-subframe frequency hopping for PUSCH w ith N_sb > 1 - Supported .... .0.. = Indicator 22: UTRAN measurements, reporting and measurement reporting ev ent B2 in E-UTRA connected mode - Not supported .... ..0. = Indicator 23: GERAN measurements, reporting and measurement reporting ev ent B2 in E-UTRA connected mode - Not supported .... ...0 = Indicator 24: 1x RTT measurements, reporting and measurement reporting ev ent B2 in E-UTRA connected mode - Not supported 1... .... = Indicator 25: Inter-frequency measurements and reporting in E-UTRA connected mode - Supported .0.. .... = Indicator 26: HRPD measurements, reporting and measurement reporting ev ent B2 in E-UTRA connected mode - Not supported ..0. .... = Indicator 27: EUTRA RRC_CONNECTED to UTRA CELL_DCH CS handov er - Not supported ...0 .... = Indicator 28: TTI bundling - Not supported .... 0... = Indicator 29: Semi-Persistent Scheduling - Not supported .... .0.. = Indicator 30: Handov er betw een FDD and TDD - Not supported

.... ..0. = Indicator 31: Undefined - Not supported .... ...0 = Indicator 32: Undefined - Not supported

26

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

25



eNB

MME


Steps:







1. 2. 3. 4. 5. 6. 7.





THIS IS THE SUPERMESSAGE !




S1AP:



27

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

26


SRB2 and DRB establishment (1) RRC SIGNALING MESSAGE Time: 13:32:15.666 RRCConnectionReconfiguration (3GPP TS 36.331 ver 8.7.0 Rel 8) DL-DCCH-Message message c1 rrcConnectionReconfiguration rrc-TransactionIdentifier : 1 criticalExtensions c1 rrcConnectionReconfiguration-r8 measConfig measObjectToAddModList measObjectToAddModList value 1 measObjectId : 1 measObject measObjectEUTRA carrierFreq : 3350 allowedMeasBandwidth : mbw100 presenceAntennaPort1 : false neighCellConfig Bin : 0 (2 bits) reportConfigToAddModList reportConfigToAddModList value 1 reportConfigId : 3 reportConfig reportConfigEUTRA triggerType event eventId

Measurement configuration (more details in HO signaling)

- In NSN implementation, this RRC message • Configures measurements • Configures PUCCH and periodic CQI reporting • Configures DRX (optional) • Sets up SRB2 • Sets up DRB

28

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

27


SRB2 and DRB establishment (2) … cont’d from prev slide

Piggybacked NAS msg, ATTACH ACCEPT + EPS DEFAULT BEARER ACTIVATION REQUEST

quantityConfig

quantityConfigEUTRA measGapConfig

:

: release

dedicatedInfoNASList dedicatedInfoNASList value 1 Hex : 07420149 064042F4 7024C200 315201C1 0509FFFF FFFF0B06 6E746E6C 74650363 6F6D0501 0A159406 27148080 21100401 00108106 00000000 83060000 0000500B F642F470 04D23803 0002BF

SRB2 setup with default RLC config

radioResourceConfigDedicated srb-ToAddModList srb-ToAddModList value 1

srb-Identity

:2

rlc-Config

: defaultValue

logicalChannelConfig

: defaultValue

drb-ToAddModList

drb-ToAddModList value 1 eps-BearerIdentity drb-Identity

:5

:4

UE should send PDCP status report in RLC_AM handover

pdcp-Config discardTimer

DRB setup for default EPS bearer

: ms300

rlc-AM statusReportRequired

headerCompression

: true

: notUsed

PDCP config

29

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

28


SRB2 and DRB establishment (3) … cont’d from prev slide rlc-Config am ul-AM-RLC t-PollRetransmit pollPDU : p16 pollByte : kBinfinity maxRetxThreshold dl-AM-RLC t-Reordering : ms50 t-StatusProhibit logicalChannelIdentity logicalChannelConfig ul-SpecificParameters priority : 16 prioritisedBitRate bucketSizeDuration logicalChannelGroup mac-MainConfig explicitValue ul-SCH-Config

RLC configuration for DRB, DRB logical channel id =4

: ms250

: t16

: ms30 :4

: kBps64 : ms50 :1

MAC configuration, buffer status reporting and power headroom reporting

periodicBSR-Timer : sf20 retxBSR-Timer : sf2560 ttiBundling : false timeAlignmentTimerDedicated : sf5120 phr-Config setup periodicPHR-Timer prohibitPHR-Timer dl-PathlossChange

30

: sf200 : sf100 : dB6

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

29



eNB

MME


Steps:






RRC: Security Mode Command

1. 2. 3. 4. 5. 6. 7.


RRC: UECapabilityEnquiry RRC: Security Command Complete UE radio capabilities available à DRB can be established






S1AP:



31

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

30


Exercises

32

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

31


Signaling exercise RRC and NAS message exercise Connect NAS messages to correct RCC messages (which carries the NAS message) [ Nemo log 4 Signaling excercise.1.nmf can be used]

RRC messages (Network Entry as seen in Nemo)

NAS messages (not in correct order)

•

Time

•

14:32:40.440

Uplink

RRCConnectionRequest

ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_ACCEPT

•

14:32:40.514

Downlink

RRCConnectionSetup

ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_REQUEST

•

14:32:40.514

Uplink

RRCConnectionSetupComplete

•

14:32:40.514

Downlink

DLInformationTransfer

•

14:32:40.514

Uplink

ULInformationTransfer

•

14:32:40.551

Downlink


•

14:32:40.731

Uplink


•

14:32:40.731

Downlink


•

14:32:40.731

Uplink


•

14:32:51.783

Downlink

SecurityModeCommand

•

14:32:51.783

Uplink

SecurityModeComplete

•

14:32:51.783

Downlink

UECapabilityEnquiry

IDENTITY_RESPONSE

•

14:32:51.783

Uplink

UECapabilityInformation

PDN_CONNECTIVITY_REQUEST

•

14:32:51.803

Downlink

RRCConnectionReconfiguration

•

14:32:51.827

Uplink

RRCConnectionReconfigurationComplete

•

14:32:51.835

Uplink


33

Direction

Message

RA47055EN16AGLA0

ATTACH_ACCEPT

ATTACH_COMPLETE ATTACH_REQUEST AUTHENTICATION_REQUEST AUTHENTICATION_RESPONSE

IDENTITY_REQUEST

SECURITY_MODE_COMMAND SECURITY_MODE_COMPLETE

© Nokia 2016

RA47055EN16AGLA0

32


Basic signaling exercise Nemo log file: Nemo log 4 Signaling excercise.1.nmf

Open the Nemo log and answer the questions: 1. What is the establishment cause for RRC Connection?

34

2.

What transmission mode is used in the network ?

3.

What is the IP address assigned to the UE in LTE?

4.

What is the APN used?

5.

Are there any maximum bit rate limitations for the user?

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

33


Mobility analysis exercise, 3G-LTE mobililty Log file name: Nemo log 5 LTE 3G mobility.1.nmf

Open the Nemo log and answer the questions: 1. How many times UE is moving from LTE to 3G? 2. What is the reason for each LTE to 3G transition? 3. What is the reselection criteria from 3G->LTE? 4. How long 3G->LTE reselection takes?

35

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

34


Basic Signaling

Backup Slides

36

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

35


Index - Dedicated bearer establishment - Handover signaling • Measurement configuration • Intra-LTE handover • LTEà3G ISHO

37

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

36


Dedicated Bearer Establishment UE

eNB

P-GW

MME

Attach and Default Bearer Activation

Triggering of Dedicated Bearer activation

triggering of Dedicated Bearer activation

RRC: UL NAS INFO TRANSFER + ESM BEARER RESOURCE ALLOCATION REQUEST S1AP: UL NAS TRANSPORT (ESM BEARER RESOURCE ALLOCATION REQUEST) optional procedure, P-GW may also trigger dedicated bearer creation without UE requesting it

GTPv2: Bearer Resource Command

Create Bearer

S1AP: E-RAB SETUP + ESM ACTIVATE DEDICATED BEARER REQUEST DRB Configuration

RRC: RRCConnectionReconfiguration + ESM ACTIVATE DEDICATED BEARER REQUEST

RRC: RRCConnectionReconfigurationComplete

RRC: UL NAS INFO TRANSFER + ESM ACTIVATE DEDICATED BEARER REQUEST ACCEPT S1AP: UL NAS TRANSPORT (ESM ACTIVATE DEDICATED BEARER REQUEST ACCEPT)

38

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

37


UL ESM Bearer Resource Allocation Request NAS EPS session management messages: Bearer resource allocation request (0xd4) 0000 .... = Spare half octet: 0 .... 0101 = Linked EPS bearer identity: EPS bearer identity value 5 (5) Traffic Flow Template - Traffic flow aggregate

Length: 13 001. .... = TFT operation code: Create new TFT (1) ...0 .... = E bit: Parameters list is not included .... 0001 = Number of packet filters: 1 Packet filter 0 0011 .... = Packet filter direction: Bidirectional (3) .... 0000 = Packet filter identifier: 0 Packet evaluation precedence: 0x00 (0) Packet filter length: 0x09 (9) Packet filter component type identifier: (16) IPv4 remote address type IPv4 adress: 10.102.50.0 (10.102.50.0) IPv4 address mask: 255.255.255.0 (255.255.255.0) EPS quality of service - Required traffic flow QoS Length: 9 Quality of Service Class Identifier (QCI): QCI 6 (6) UE->NW Subscribed maximum bit rate for uplink/ NW->UE Reserved UE->NW Subscribed maximum bit rate for downlink/ NW->UE Reserved Guaranteed bit rate for uplink : 0 kbps Guaranteed bit rate for downlink : 0 kbps Use the value indicated by the maximum bit rate for uplink in octet 4. Use the value indicated by the maximum bit rate for downlink in octet 5. Use the value indicated by the Guaranteed bit rate for uplink in octet 6. Use the value indicated by the Guaranteed bit rate for downlink in octet 7.

39

RA47055EN16AGLA0

Request to create a new Traffic Flow Template (Dedicated Bearer)

Packet Filter for the TFT, requested by UE

© Nokia 2016

RA47055EN16AGLA0

38



40

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

39


Measurement configuration investigation Using the Nemo Log 1 RF exercise log

For the measurement report below, identify the, frequency,

RAT type Measurement type What action is taken after the report is received and why? RRC SIGNALING MESSAGE Time: 10:01:09:704 MeasurementReport (3GPP TS 36.331 ver 10.6.0 Rel 10) UL-DCCH-Message message c1 measurementReport criticalExtensions c1 measurementReport-r8 measResults measId : 1 measResultPCell rsrpResult :42 RsrqResult : 12 measResultNeighCells measResultListEUTRA measResultListEUTRA value 1 physCellId : 408 measResult rsrpResult : 52

41

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

40


Index - Dedicated bearer establishment - Handover signaling • Measurement configuration • Intra-LTE handover • LTEà3G ISHO - TDD LTE specific signaling.

42

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

41


Inter-eNB handover, more complete (3GPP 36.300) UE

Source eNB

Target eNB

Serving

MME

Gateway

0. Area Restriction Provided 1. Measurement Control packet data

packet data

Legend

UL allocation 2.

L3 signalling

Measurement Reports

L1/L2

signalling

3. HO decision 4.

User Data

Handover Preparation

Handover Request 5. Admission Control

6. Handover Request Ack DL allocation RRC Conn. Reconf. incl. mobilityControlinformation

8.

Handover Execution

Deliver buffered and in transit packets to target eNB SN Status Transfer

Data Forwarding

Buffer packets from Source eNB 9. 10. 11.

Synchronisation UL allocation

+

TA for UE

RRC Conn. Reconf. Complete packet data

packet data 12. Path Switch Request

13. User Plane update request

End Marker

14.

Switch DL path

packet data End Marker

15.User Plane update response 16.Path Switch Request Ack

17. UE Context Release

Handover Completion

7.

Detach from old cell and synchronize to new cell

18. Release Resources

43

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

42


Handover Preparation, step 1/3 1.

The source eNB configures the UE measurement procedures with an RRC RECONFIGURATION

UE

Source Target

2. UE is triggered to send MEASUREMENT REPORT to the source eNB. It can be event triggered or periodic

1. RRC Reconfiguration

3. Source eNB makes handover decision based on UE report + load and service information

2. Measurement report

4. The source eNB issues a HANDOVER REQUEST to the target eNB

MME

GW

RRC Reconfiguration Complete

3. HO decision

5. Target eNB performs admission control

4. HO request

6. Target eNB sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB

5. Admission control 6. HO request ack.

44

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

43


Handover Execution, step 2/3 7. Source eNB generates the RRC RECONFIGURATION towards UE informing it to move to the target cell Source eNB starts forwarding packets to target eNB 8. Source eNB sends status information to target eNB

UE

Source

Target eNB can begin to send data to UE

45

RA47055EN16AGLA0

GW

Forward packets to target 8. Status transfer

DL pre-synchronization is obtained during cell identification and measurements

11. UE sends RRC RECONFIGURATION COMPLETE to target eNB

MME

7. RRC Reconfiguration

9. UE performs the final synchronization to target eNB and accesses the cell via RACH procedure

10. Target eNB gives the uplink allocation and timing advance information

Target

9. Synchronization

Buffer packets from source

10. UL allocation and timing advance 11. RRC Reconf. Complete

© Nokia 2016

RA47055EN16AGLA0

44


Handover Completion, step 3/3 12.Target eNB sends a PATH SWITCH message to MME to inform that the UE has changed cell

UE

Source Target

MME

GW

13.MME sends a USER PLANE UPDATE REQUEST message to Serving Gateway 14.Serving Gateway switches the downlink data path to the target side

12. Path switch request

13. User plane update request 14. Switch downlink path

15.Serving Gateway sends a USER PLANE UPDATE RESPONSE message to MME 16.MME confirms the PATH SWITCH message with the PATH SWITCH ACK message 17.By sending RELEASE RESOURCE the target eNB informs success of handover to source eNB and triggers the release of resources 18.Upon reception of the RELEASE RESOURCE message, the source eNB can release radio and Cplane related resources associated to the UE context

15. User plane update response 16. Path switch request ack. 17. Release resources

18. Release resources

46

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

45


Handover command • RRCConnectionReconfiguration with MobilityControlInfo (”Handover command”) HandoverCommand : { criticalExtensions c1 : handoverCommand-r8 : { handoverCommandMessage { message c1 : rrcConnectionReconfiguration : { rrc-TransactionIdentifier 1, criticalExtensions c1 : rrcConnectionReconfiguration-r8 : { mobilityControlInfo { targetPhysCellId 343, t304 ms100,

C-RNTI in the target cell

newUE-Identity '11111001 10011010'B, radioResourceConfigCommon { rach-ConfigCommon { preambleInfo { numberOfRA-Preambles n40, preamblesGroupAConfig {

sizeOfRA-PreamblesGroupA n4, messageSizeGroupA b144, messagePowerOffsetGroupB dB10 } }, powerRampingParameters { powerRampingStep dB4, preambleInitialReceivedTargetPower dBm-90 }, ra-SupervisionInfo { preambleTransMax n8, ra-ResponseWindowSize sf10, mac-ContentionResolutionTimer sf64

47

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

46



48

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

47


Inter-RAT Handover to WCDMA Flow

MME LTE, Source:CelI

Measurement Report

WCDMA, Target Cell

Triggered EventA2

RRC Connection Reconfiguration

New MeasConfig used for IRAT Handover

RRC Connection Reconfiguration Complete

Measurement Report

Triggered EventB2 Handover Preparation

MobilityFromEUTRAcommand

Handover Preparation Successful Handover Command

HandoverToUTRANComplete

49

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

48


Handover Preparation

LAC:2031(Hex) = 8241 Dec

TargetCellId: 6291758 = 60 01 2E (Hex) => 60Hex is RNC-id = 96 Dec => 01 1E Hex is Cell-id = 302 Dec

50

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

49


Handover Preparation Success

51

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

50


UEContextRelease

52

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

51


NokiaEDU

RA47055EN16AGLA0

© Nokia 2016

RA47055EN16AGLA0

52

RA47055EN16AGLA0 Basic Signaling

Recommend Documents