LTE End-To-End Solution Call Flows With Performance Measurements 5.0 Preliminary

8/12/2019 LTE End-To-End Solution Call Flows With Performance Measurements 5.0 Preliminary

1/130

Title page

Alcatel-Lucent Long Term Evolution (LTE)End-to-End Solution | Release LE5.0Call Flows with Performance Measurements

Technical Description9YZ-03745-9408-TQZZA

Issue 0.03 | May 2012

Alcatel-Lucent ProprietaryUse pursuant to applicable agreements


2/130

Legal notice

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective

owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright 2012Alcatel-Lucent. All rights reserved.

Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside

Alcatel-Lucent without its written authorization.

Not to be used or disclosed except in accordance with applicable agreements.

Mandatory Customer Information

Interference information: Part 15 of FCC rules

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits

are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment

generates, uses, and can radiate radio frequency energy, and if not installed and used in accordance with the documentation, may cause harmful interference

to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to

correct the interference at his/her own expense.

Security statement

In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such event,

applicable tariffs require the customer to pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any

allowance or give any credit for charges that result from unauthorized access.

To obtain technical support, documentation, and training or submit feedback:

The ordering number for this document is 9YZ-037459408TQZZA. To order this or other Alcatel-Lucent information products, the Online Customer

Support (OLCS) web site, provides access to technical support, related documentation, related training, and feedback tools. The site also provides account

registration for new users.(https://support.alcatel-lucent.com).


PRELIMINARY

P

RELIMINARY
https://support.alcatel-lucent.com/https://support.alcatel-lucent.com/https://support.alcatel-lucent.com/


3/130


4/130

2.1.11 Failed Attach -- Initial Context Setup Failure due to Error in Context SetupRequest from

MME ................................................................................................................................................................................... 2-152-15

2.2 Tracking Area Update Scenarios

2.2.1 Successful TAU with Different MME, Different SGW ................................................................................ 2-162-16

2.2.2 Successful TAU with Same MME, Same SGW .............................................................................................. 2-172-17

2.2.3 Successful TAU with Same MME, Different SGW ....................................................................................... 2-182-18

2.2.4 Failed TAU with Same MME and Same SGW ................................................................................................ 2-192-19

2.2.5 Failed TAU with Different MME, Different SGW ......................................................................................... 2-202-20

2.3 Service Requests Scenarios

2.3.1 Successful Network Initiated Service Request ................................................................................................. 2-222-22

2.3.2 Successful UE Invoked Service Request ............................................................................................................

2-232-23

2.3.3 Failed UE Invoked Service Request ..................................................................................................................... 2-242-24

2.3.4 Failed UE Invoked Service Request -- No Response from the UE .......................................................... 2-252-25

2.3.5 Failed UE Invoked Service Request -- Security Activation Failure ......................................................... 2-262-26

2.3.6 Failed UE Invoked Service Request -- Integrity Failure .............................................................................. 2-272-27

2.3.7 Failed UE Invoked Service Request -- RRC Connection Reestablishment ........................................... 2-282-28

2.3.8 Failed UE Invoked Service Request -- Initial Context Setup Failure at eNodeB Level ...................

2-292-29

2.3.9 Failed UE Invoked Service Request S1 Connection Failure, No Answer from the MME ............... 2-302-30

2.3.10 Failed UE Invoked Service Request -- STMSI Missing in Service Request Message .................2-312-31

2.3.11 Failed Network Initiated Service Request ....................................................................................................... 2-322-32

2.3.12 Failed Network Initiated Service Request -- No Response from the UE ............................................. 2-332-33

2.3.13 Failed Network Initiated Service Request -- Security Activation Failure ............................................ 2-342-34

2.3.14 Failed Network Initiated Service Request -- Integrity Failure ................................................................. 2-352-35

2.3.15 Failed Network Initiated Service Request -- RRC Connection Reestablishment ............................. 2-362-36

2.3.16 Failed Network Initiated Service Request -- Initial Context Setup Failure at eNodeB Level................................................................................................................................................................................................ 2-372-37

2.3.17 Failed Network Initiated Service Request -- S1 Connection Failure, No Answer from the

MME ................................................................................................................................................................................... 2-382-38

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

iv Alcatel-Lucent ProprietaryUse pursuant to applicable agreements

Alcatel-Lucent LTE Solution9YZ-03745-9408-TQZZA Release LE5.0

Issue 0.03 May 2012PRELIMINARY

P

RELIMINARY


5/130

2.3.18 Failed Network Initiated Service Request -- S-TMSI Missing from Request Message .................2-392-39

2.4 S1 Release Scenarios

2.4.1 Successful MME Initiated S1 Release ................................................................................................................ 2-402-40

2.5 Detach Scenarios

2.5.1 Successful MME Initiated Detach ........................................................................................................................ 2-412-41

2.5.2 Successful UE Initiated Detach .............................................................................................................................. 2-422-42

2.6 Security Function Scenarios

2.6.1 Successful Authentication and NAS Security Activation ............................................................................. 2-432-43

2.6.2 Failed Authentication and NAS Security Activation ...................................................................................... 2-442-44

2.6.3 Failed NAS Security Activation ............................................................................................................................ 2-452-45

2.6.4 Successful ME Identity Check ............................................................................................................................... 2-462-46

2.7 Session Management and QoS Scenarios

2.7.1 Dedicated Bearer Activation Scenarios ............................................................................................................... 2-472-47

2.7.2 Bearer Modification with Bearer QoS Update Scenarios ............................................................................. 2-522-52

2.7.3 Bearer Modification Without Bearer QoS Update Scenarios ...................................................................... 2-572-57

2.7.4 UE Requested Bearer Resource Modification Scenarios ............................................................................. 2-602-60

2.7.5 UE initiated Bearer Resource Allocation Scenarios ....................................................................................... 2-622-62

2.7.6 HSS Initiated Subscribed QoS Modification Scenarios ................................................................................ 2-642-64

2.7.7 Bearer Deactivation Scenarios ............................................................................................................................... 2-692-69

2.8 X2/S1 Handover Scenarios

2.8.1 X2 Handover Scenarios ............................................................................................................................................2-732-73

2.8.2 S1 Handover Scenarios .............................................................................................................................................2-862-86

2.8.3 LTE to eHRPD Active Handover (Non-optimized with LTE Measurement) .....................................

2-1022-102

2.9 Multiple PDN Scenarios

2.9.1 Successful UE requested PDN Connectivity .................................................................................................. 2-1032-103

2.9.2 Failed UE Requested PDN Connectivity ......................................................................................................... 2-1042-104

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

Alcatel-Lucent LTE Solution9YZ-03745-9408-TQZZA Release LE5.0Issue 0.03 May 2012


v

PRELIMINA

RY

PRELIMINARY


6/130

2.9.3 Failed UE Requested PDN Connectivity -- eNodeB ERAB Setup Failure ......................................... 2-1052-105

2.9.4 Failed UE Requested PDN Connectivity -- RRC Reconfiguration Refused by the UE .................2-1062-106

2.9.5 Failed UE Requested PDN Connectivity -- No Answer from the UE ................................................... 2-1072-107

2.9.6 Failed UE Requested PDN Connectivity -- Request Not Accepted by the Network .......................

2-1082-108

2.9.7 PDN Disconnection Scenarios ............................................................................................................................. 2-1092-109

2.10 RRC Connection Request Scenarios

2.10.1 RRC Connection Request -- Sunny Day ........................................................................................................ 2-1132-113

2.10.2 RRC Connection Request -- No Answer from the UE ............................................................................. 2-1142-114

2.10.3 RRC Connection Request -- MME Overload 1 ........................................................................................... 2-1152-115

2.10.4 RRC Connection Request -- MME Overload .............................................................................................. 2-1162-116

2.10.5 RRC Connection Request -- eNodeB Failure .............................................................................................. 2-1172-117

Index

Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

vi Alcatel-Lucent ProprietaryUse pursuant to applicable agreements



P

RELIMINARY


7/130


8/130

Assumed knowledge

The reader must be familiar with:

General knowledge of eNodeB and MME performance measurement counters

Understanding of LTE elements and procedures as specified in 3GPP TS 23.401

v8.6.0

Understanding of NAS Messaging as specified in 3GPP TS 24.301

Understanding of Tunneling messaging as specified in 3GPP TS 29.274.

Basically, the reader should have an understanding of the performance measurements and

an understanding of the LTE procedures that make up the call flows.

Related information

Refer to the Alcatel-Lucent LTE Solution | LE5.0 Operations, Administration, and

Maintenance document, 9YZ037459401TQZZA for a description of LTE and the

End-to-End LTE Solution.

To obtain technical support, documentation, and training or submit feedback:

The Online Customer Support (OLCS) web site,

(https://support.alcatel-lucent.com)

provides access to technical support, related documentation, related training, and

feedback tools. The site also provides account registration for new users.

How to comment

Alcatel-Lucent has made every effort to ensure that this information product meets yourneeds. Alcatel-Lucent is interested in your comments and suggestions to improve this

information product. You may submit comments and suggestions on this and other

Alcatel-Lucent training and information products via:

The Internet

E-mail

Facsimile

Via the Internet

To submit comments via the Internet, please visit the "Talk to Lucent" web site at:

(http://www.lucent-info.com/comments)

Via e-mail

To submit comments via e-mail, please send your message to:

[email protected]

About this document

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

viii Alcatel-Lucent ProprietaryUse pursuant to applicable agreements



P

RELIMINARY
https://support.alcatel-lucent.com/http://www.lucent-info.com/commentshttp://www.lucent-info.com/commentshttps://support.alcatel-lucent.com/


9/130

1 1Introduction

1.1 Call Flows with Performance Measurements

Overview

This document provides the call flows for LTE performance measurements for the

eNodeB, MME, and SGW in the Alcatel-Lucent LTE system. Performance measurementsprovide the basis for performance evaluation, capacity engineering and help in

troubleshooting. To understand the meaning of these performance measurements, it is

necessary to understand the relative sequence of pegging these measurements. Call flows

provide useful context for showing the sequence of events and when the PMs are pegged

under what conditions.

The scenarios contained herein are selected sunny and rainy day scenarios. 3GPP2

Handovers are covered in this version. Handovers to 3GPP will be provided in a future

version of this document. Note that not all of the LTE PMs are included in the call flows.

The scope of this document includes PMs for eNodeB, MME, and SGW. Call flows are

based on scenarios defined in 3GPP TS 23.401. Maintenance actions that result in specific

PMs being pegged are not covered in this document.

For a complete list of eNodeB PMs, please refer to document 9YZ-03990-0105-RKZZA,

Alcatel-Lucent 9412 eNodeB Counters Reference Guide.

For a complete list of MME PMs, please refer to document 418-111-209, Alcatel-Lucent

9471 MME Observation Counters.

For a complete list of SGW PMs, please refer to document 93-0363-04-xxAlcatelLucent

7750 SR OS MG KPI/KCI Counters.

Guide to the Document

The diagrams in the document indicate where PMs are pegged in the eNodeB, MME, and

SGW. The eNodeB PMs are in the green ovals in the diagrams. The MME PMs are blue.

And the SGW PMs are in purple. Triggers for pegging PM counts may be receipt of a

...................................................................................................................................................................................................................................



1-1

PRELIMINA

RY

PRELIMINARY


10/130

particular message or the sending of a particular message, as shown in the example below

for the eNodeB counts. Also, sometimes more than one PM may be pegged at the same

point in the call flow, such as in the MME oval.

The following is a sample diagram provided only to show how PMs are represented.

Legend:

eNodeB PMs are represented in the green text.

MME PMs are represented in the blue text.

SGW PMs are represented in the purple text.

FAILURE SCENARIOS:The call flows for failure scenarios depict where in the call

flow certain errors can occur and the corresponding failure counters that are pegged as a

result of the failure. Most of the failure call flows show multiple error scenarios.

Typically, if the error occurs and the call flow ends at that point, an EXITwill be shown

in the call flow. This indicates that the rest of the call flow would not continue. If the error

does not occur, the success counter would be pegged (refer to success scenarios) and the

call flow continues until if/when it encounters another error. In some cases, a failure does

not end the call flow, in which case, aContinuewill be shown in the call flow.

Introduction 1.1 Call Flows with Performance Measurements

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................

1-2 Alcatel-Lucent ProprietaryUse pursuant to applicable agreements



P

RELIMINARY


11/130

2 2Call Flow Diagrams

2.1 Attach Scenarios

2.1.1 Successful Attach Procedure

...................................................................................................................................................................................................................................



2-1

PRELIMINA

RY

PRELIMINARY


12/130

Call Flow Diagrams2.1 Attach Scenarios


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


13/130



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-3

PRELIMINA

RY

PRELIMINARY


14/130

2.1.2 Successful Emergency Attach Procedure



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


15/130



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-5

PRELIMINA

RY

PRELIMINARY


16/130

2.1.3 Failed Attach Procedure



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


17/130



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-7

PRELIMINA

RY

PRELIMINARY


18/130

2.1.4 Failed Attach -- S1 Connection Failure, No Responsefrom MME


2.1.4 Failed Attach -- S1 Connection Failure, No Responsefrom MME

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


19/130

2.1.5 Failed Attach -- Initial Context Setup Failure, No answerfrom the UE


2.1.5 Failed Attach -- Initial Context Setup Failure, Noanswer from the UE

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-9

PRELIMINA

RY

PRELIMINARY


20/130

2.1.6 Failed Attach -- RRC Security Mode Failure


2.1.6 Failed Attach -- RRC Security Mode Failure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


21/130

2.1.7 Failed Attach -- Security Activation Failure or SecurityAlgorithm Not Compatible


2.1.7 Failed Attach -- Security Activation Failure or SecurityAlgorithm Not Compatible

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-11

PRELIMINA

RY

PRELIMINARY


22/130

2.1.8 Failed Attach -- Integrity Verification Failure


2.1.8 Failed Attach -- Integrity Verification Failure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


23/130

2.1.9 Failed Attach -- RRC Connection Reestablishment


2.1.9 Failed Attach -- RRC Connection Reestablishment

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-13

PRELIMINA

RY

PRELIMINARY


24/130

2.1.10 Failed Attach -- Initial Context Setup Failure in theeNodeB


2.1.10 Failed Attach -- Initial Context Setup Failure in theeNodeB

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


25/130

2.1.11 Failed Attach -- Initial Context Setup Failure due toError in Context SetupRequest from MME


2.1.11 Failed Attach -- Initial Context Setup Failure due toError in Context SetupRequest from MME

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-15

PRELIMINA

RY

PRELIMINARY


26/130

2.2 Tracking Area Update Scenarios

2.2.1 Successful TAU with Different MME, Different SGW

Call Flow Diagrams2.2 Tracking Area Update Scenarios

2.2.1 Successful TAU with Different MME, Different SGW

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


27/130

2.2.2 Successful TAU with Same MME, Same SGW


2.2.2 Successful TAU with Same MME, Same SGW

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-17

PRELIMINA

RY

PRELIMINARY


28/130

2.2.3 Successful TAU with Same MME, Different SGW


2.2.3 Successful TAU with Same MME, Different SGW

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


29/130

2.2.4 Failed TAU with Same MME and Same SGW


2.2.4 Failed TAU with Same MME and Same SGW

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-19

PRELIMINA

RY

PRELIMINARY


30/130

2.2.5 Failed TAU with Different MME, Different SGW

In these scenarios, there are some checks that the MME does to determine if the request is

Inter MME and Inter SGW. If failures occur before those checks, then the InterMME

and InterSGW counters are not pegged.


2.2.5 Failed TAU with Different MME, Different SGW

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


31/130

Call Flow Diagrams 2.2.5 Failed TAU with Different MME, Different SGW

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-21

PRELIMINA

RY

PRELIMINARY


32/130

2.3 Service Requests Scenarios

2.3.1 Successful Network Initiated Service Request

Call Flow Diagrams2.3 Service Requests Scenarios

2.3.1 Successful Network Initiated Service Request

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


33/130

2.3.2 Successful UE Invoked Service Request


2.3.2 Successful UE Invoked Service Request

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-23

PRELIMINA

RY

PRELIMINARY


34/130

2.3.3 Failed UE Invoked Service Request


2.3.3 Failed UE Invoked Service Request

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


35/130

2.3.4 Failed UE Invoked Service Request -- No Response fromthe UE


2.3.4 Failed UE Invoked Service Request -- No Responsefrom the UE

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-25

PRELIMINA

RY

PRELIMINARY


36/130

2.3.5 Failed UE Invoked Service Request -- Security ActivationFailure


2.3.5 Failed UE Invoked Service Request -- SecurityActivation Failure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


37/130

2.3.6 Failed UE Invoked Service Request -- Integrity Failure


2.3.6 Failed UE Invoked Service Request -- Integrity Failure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-27

PRELIMINA

RY

PRELIMINARY


38/130

2.3.7 Failed UE Invoked Service Request -- RRC ConnectionReestablishment


2.3.7 Failed UE Invoked Service Request -- RRC ConnectionReestablishment

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


39/130

2.3.8 Failed UE Invoked Service Request -- Initial ContextSetup Failure at eNodeB Level


2.3.8 Failed UE Invoked Service Request -- Initial ContextSetup Failure at eNodeB Level

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-29

PRELIMINA

RY

PRELIMINARY


40/130

2.3.9 Failed UE Invoked Service Request S1 ConnectionFailure, No Answer from the MME


2.3.9 Failed UE Invoked Service Request S1 ConnectionFailure, No Answer from the MME

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


41/130

2.3.10 Failed UE Invoked Service Request -- STMSI Missing inService Request Message


2.3.10 Failed UE Invoked Service Request -- STMSI Missingin Service Request Message

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-31

PRELIMINA

RY

PRELIMINARY


42/130

2.3.11 Failed Network Initiated Service Request


2.3.11 Failed Network Initiated Service Request

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


43/130

2.3.12 Failed Network Initiated Service Request -- NoResponse from the UE


2.3.12 Failed Network Initiated Service Request -- NoResponse from the UE

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-33

PRELIMINA

RY

PRELIMINARY


44/130

2.3.13 Failed Network Initiated Service Request -- SecurityActivation Failure


2.3.13 Failed Network Initiated Service Request -- SecurityActivation Failure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


45/130

2.3.14 Failed Network Initiated Service Request -- IntegrityFailure


2.3.14 Failed Network Initiated Service Request -- IntegrityFailure

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-35

PRELIMINA

RY

PRELIMINARY


46/130

2.3.15 Failed Network Initiated Service Request -- RRCConnection Reestablishment


2.3.15 Failed Network Initiated Service Request -- RRCConnection Reestablishment

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


47/130

2.3.16 Failed Network Initiated Service Request -- InitialContext Setup Failure at eNodeB Level


2.3.16 Failed Network Initiated Service Request -- InitialContext Setup Failure at eNodeB Level

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-37

PRELIMINA

RY

PRELIMINARY


48/130

2.3.17 Failed Network Initiated Service Request -- S1Connection Failure, No Answer from the MME


2.3.17 Failed Network Initiated Service Request -- S1Connection Failure, No Answer from the MME

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


49/130

2.3.18 Failed Network Initiated Service Request -- S-TMSIMissing from Request Message


2.3.18 Failed Network Initiated Service Request -- S-TMSIMissing from Request Message

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-39

PRELIMINA

RY

PRELIMINARY


50/130

2.4 S1 Release Scenarios

2.4.1 Successful MME Initiated S1 Release

Call Flow Diagrams2.4 S1 Release Scenarios

2.4.1 Successful MME Initiated S1 Release

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


51/130

2.5 Detach Scenarios

2.5.1 Successful MME Initiated Detach

Call Flow Diagrams2.5 Detach Scenarios

2.5.1 Successful MME Initiated Detach

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-41

PRELIMINA

RY

PRELIMINARY


52/130

2.5.2 Successful UE Initiated Detach

Call Flow Diagrams2.5 Detach Scenarios

2.5.2 Successful UE Initiated Detach

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


53/130

2.6 Security Function Scenarios

2.6.1 Successful Authentication and NAS Security Activation

Call Flow Diagrams2.6 Security Function Scenarios

2.6.1 Successful Authentication and NAS Security Activation

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-43

PRELIMINA

RY

PRELIMINARY


54/130

2.6.2 Failed Authentication and NAS Security Activation


2.6.2 Failed Authentication and NAS Security Activation

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


55/130

2.6.3 Failed NAS Security Activation


2.6.3 Failed NAS Security Activation

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-45

PRELIMINA

RY

PRELIMINARY


56/130

2.6.4 Successful ME Identity Check


2.6.4 Successful ME Identity Check

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


57/130

2.7 Session Management and QoS Scenarios

2.7.1 Dedicated Bearer Activation Scenarios

2.7.1.1 Successful Dedicated Bearer Activation

(*) Refer to2.7.4 UE Requested Bearer Resource Modification Scenarios (p. 2-60)and

to2.7.5 UE initiated Bearer Resource Allocation Scenarios (p. 2-62)for UE Initiated

Bearer Modification/Allocation.

Call Flow Diagrams2.7 Session Management and QoS Scenarios


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-47

PRELIMINA

RY

PRELIMINARY


58/130

2.7.1.2 Failed Dedicated Bearer Activation Failure in Create Bearer Request



Bearer Modification/Allocation attempt counts.



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


59/130

2.7.1.3 Failed Dedicated Bearer Activation ERAB Setup Failure in eNodeB






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-49

PRELIMINA

RY

PRELIMINARY


60/130

2.7.1.4 Failed Dedicated Bearer Activation No Answer from the UE






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


61/130

2.7.1.5 Failed Dedicated Bearer Activation RRC Reconfiguration Refused by the UE






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-51

PRELIMINA

RY

PRELIMINARY


62/130

2.7.2 Bearer Modification with Bearer QoS Update Scenarios

2.7.2.1 Successful Bearer Modification With Bearer QoS Update

The following procedure applies to both PGW-Initiated bearer modification and

UE-Initiated bearer modification (see2.7.4.1 Successful UE Requested Bearer ResourceModification (p. 2-60)).






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


63/130

2.7.2.2 Failed Bearer Modification With Bearer QoS Update Failure in Update Bearer RequestMessage






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-53

PRELIMINA

RY

PRELIMINARY


64/130

2.7.2.3 Failed Bearer Modification With Bearer QoS Update Failure in ERAB Modification ateNodeB






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


65/130

2.7.2.4 Failed Bearer Modification With Bearer QoS Update No Answer from the UE






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-55

PRELIMINA

RY

PRELIMINARY


66/130

2.7.2.5 Failed Bearer Modification With Bearer QoS Update RrcConnectionReestablishmen-tRequest Received from the UE






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


67/130

2.7.3 Bearer Modification Without Bearer QoS UpdateScenarios

2.7.3.1 Successful Bearer Modification Without Bearer QoS Update

The following procedure applies to both PGW-Initiated bearer modification andUE-Initiated bearer modification (see2.7.4.1 Successful UE Requested Bearer Resource

Modification (p. 2-60)).






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-57

PRELIMINA

RY

PRELIMINARY


68/130

2.7.3.2 Failed Bearer Modification Without Bearer QoS Update -- Failure in Update BearerRequest Message






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


69/130

2.7.3.3 Failed Bearer Modification Without Bearer QoS Update Failure in Session Mgmt Responsefrom UE






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-59

PRELIMINA

RY

PRELIMINARY


70/130

2.7.4 UE Requested Bearer Resource Modification Scenarios

2.7.4.1 Successful UE Requested Bearer Resource Modification

The rest of the call flow follows as one of the following: Dedicated bearer activation as in Section2.7.1.1 Successful Dedicated Bearer

Activation (p. 2-47)

Bearer modification procedure as in2.7.3.1 Successful Bearer Modification Without

Bearer QoS Update (p. 2-57)

Dedicated bearer deactivation procedure as in Section2.7.7.1 Successful PDN

Gateway initiated bearer deactivation (p. 2-69).



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


71/130

2.7.4.2 Failed UE Requested Bearer Resource Modification -- Failure at PGW

The rest of the call flow follows as one of the following:

Dedicated bearer activation as in Section2.7.1.1 Successful Dedicated Bearer

Activation (p. 2-47) Bearer modification procedure as in2.7.3.1 Successful Bearer Modification Without






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-61

PRELIMINA

RY

PRELIMINARY


72/130

2.7.5 UE initiated Bearer Resource Allocation Scenarios

2.7.5.1 UE Initiated Bearer Resource Allocation

The rest of the call flow follows as one of the following: Dedicated bearer activation as in Section2.7.1.1 Successful Dedicated Bearer

Activation (p. 2-47)

Bearer modification procedure as in2.7.3.1 Successful Bearer Modification Without






....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................




P

RELIMINARY


73/130

2.7.5.2 Failed UE Requested Bearer Resource Allocation, Failure at PGW



....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................



2-63

PRELIMINA

RY

PRELIMINARY


74/130

2.7.6 HSS Initiated Subscribed QoS Modification Scenarios

2.7.6.1 Successful HSS Initiated Subscribed QoS Modification


2.7.6 HSS Initiated Subscribed QoS Modification Scenarios

....................................................................................................................................................................................................................................

............................................................................................................................................................................................

Documents

LTE End-To-End Solution Call Flows With Performance Measurements 5.0 Preliminary