CSFB To 2G 3G - E2E Message Flows

1/21 MBB LTE SD P&C LTE E2E Field Performance
- CSFB to 2G/3G -
3 LTE E2E Field Performance

4 - CSFB to 2G/3G -
5
7 - Technical Note on E2E Message Flows -

8
10
11 Document Status: Draft, Internal
12 Release 1.0, Issue 04
13 Date: 30th November 2012
14
15
16
17
18
19 Issued by the Nokia Siemens Networks GmbH & Co. KG
20 Copyright  Nokia Siemens Networks GmbH & Co. KG 2012
21 All Rights Reserved
Author: Dr. Andras Balazs MBB LTE SD P&C
22
MBB LTE SD P&C For NSN internal use only Tel.: +49.175.261.5151
Dr. A. Balazs Email: andras.balazs@nsn.com
2/21 LTE E2E Field Performance
- CSFB to 2G/3G -
1 Table of Contents
2 1. General Information ............................................................ 3

3 1.1 Revision History............................................................................................ 3
4 1.2 References ................................................................................................... 4
5 1.3 Abbreviations ................................................................................................ 5
6 1.4 Glossary ....................................................................................................... 6
7 1.5 List of Figures and Tables ............................................................................ 6
8 2. Scope ................................................................................. 7
9 2.1 Feature Support............................................................................................ 7
10 2.2 Call Scenarios .............................................................................................. 7
11 2.3 Network Architecture .................................................................................... 8
12 3. Message Flow Descriptions ................................................ 9

13 3.1 Combined EPS/IMSI Attach and Detach ....................................................... 9
14 3.2 CSFB to UTRAN w/ Redirect ........................................................................ 9
15 3.2.1 Mobile Originated Call (MOC) ....................................................................... 9
16 3.2.1.1 Overview ..................................................................................................................... 9
17 3.2.1.2 LTE Service Request and Redirect to UTRAN ......................................................... 12
18 3.2.1.3 Initial UTRAN Access................................................................................................ 13
19 3.2.1.4 Location Area Update (LAU) ..................................................................................... 13
20 3.2.1.5 Routing Area Update (RAU) ..................................................................................... 14
21 3.2.1.6 UTRAN Service Request .......................................................................................... 15
22 3.2.1.7 CS Call Setup ........................................................................................................... 16
23 3.2.2 Mobile Terminated Call (MTC) .................................................................... 17
24 3.2.2.1 Overview ................................................................................................................... 17
25 3.2.2.2 Paging, Service Request and Redirect ..................................................................... 19
26 3.2.2.3 Paging Response & CS Call Setup .......................................................................... 20
27 3.2.3 Call Release ............................................................................................... 21
28
- CSFB to 2G/3G -
1 1. General Information
2 1.1 Revision History
Version Date Change Notes
V1.01 31.03.2012 First draft.
V1.02 07.04.2012 Second draft.
V1.3 05.07.2012 Additional CSFB scenarios
V1.4 30.11.2012 KPI definitions and targets removed. They are part of the “standard” LTE Field
Performance KPI Definitions and Targets documents. References added.
3
4 Authors
Name Department
Dr. Andras Balazs MBB LTE SD P&C
Krystian Krysmalski NWS LTE RA RD Sys SA NE
- CSFB to 2G/3G -
1 1.2 References
[3GPP23.272] 3GPP TS 23.272 v.8.10.0 (2010-12) Circuit Switched (CS) fallback in Evolved Packet System (EPS);
Stage 2 (Release 8)
[3GPP23.272] 3GPP TS 23.272 v.9.10.0 (2011-12) Circuit Switched (CS) fallback in Evolved Packet System (EPS);
Stage 2 (Release 9)
[3GPP23.401] 3GPP TR 23.401; v.8.x.x; General Packet Radio Service (GPRS) enhancements for Long Term
Evolution (LTE) access
[3GPP24.008] 3GPP TR 24.008; V8.5.0 (2009-03); Mobile Radio Interface Layer 3 Specification; Core network
protocols; Stage 3.
[3GPP25.913] 3GPP TR 25.913; V8.0.0 (2008-12); Requirements for Evolved UTRA (E-UTRA) and Evolved
UTRAN (E-UTRAN).
[3GPP25.943] 3GPP TR 25.943; V8.0.0 (2008-12); Deployment Aspects (Release 8).
[3GPP32.450] 3GPP TS 32.450, V8.1.0 (2009-06); Telecommunication management; Key Performance Indicators
for E-UTRAN: Definitions (Release 8).
[3GPP32.451] 3GPP TS 32.451, V8.0.0 (2009-03); Telecommunication management; Key Performance Indicators
for E-UTRAN: Requirements (Release 8).
[3GPP32.814] 3GPP TS 32.814, V7.0.0 (2007-03); Telecommunication management; UTRAN and GERAN Key
Performance Indicators (KPI), (Release 7)
[3GPP36.300] TS 36.300; v 8.x.x; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2
[3GPP36.306] TS 36.306; V8.3.0 (2009-03); Evolved Universal Terrestrial Radio Access (E-UTRA); User
Equipment (UE) Radio Access Capabilities.
[3GPP36.331] TS 36.331; V8.6.0 (2009-06); Evolved Universal Terrestrial Radio Access (E-UTRA); Radio
Resource Control (RRC) protocol specification
[3GPP36.401] TS 36.401; v 8.x.x; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture
description
[3GPP36.413] TS 36.413; V8.6.1 (2009-06); Evolved Universal Terrestrial Access Network (E-UTRAN) ; S1
Application Protocol (S1 AP)
2
[E2E_Field_KPI_Def] LTE E2E Field Network Performance for Offer and Acceptance, KPI Definitions and
Measurement Methods, MBB LTE SD P&C, V4.02, 30.11.2012.
[RL40_Field_KPI_Targets] LTE E2E Field Network Performance for Offer and Acceptance, KPI Targets for RL40, MBB
LTE SD P&C, V4.03, 30.11.2012.
- CSFB to 2G/3G -
1 1.3 Abbreviations
2 For the purposes of the present document, the abbreviations given in [3GPP21.905] and the
3 followings apply.
4 AF Application Function 65 NRT Non Real Time

5 AMBR Aggregate Maximum Bit Rate 66 OAM Operations and Maintenance
6 AS Application Server 67 p2e Picture-to-eye (for Video delay)
7 ASP Application Service Provider 68 PAPR Peak-to-Average-Power Ratio
8 AV Audio / Video 69 PCC Policy and Charging Control
9 AVP Attribute Value Pair 70 PD Packet Delay
10 AWGN Additive White Gaussian Noise 71 PDU Packet Data Unit
11 BLER (Radio) Block Error Rate (initial, target) 72 PDCP Packet Data Convergence Protocol
12 CDF Cumulative Distribution Function 73 PDV Packet Delay Variation
13 CN Core Network 74 P-GW Packet Data Network (PDN) Gateway
14 CQI Channel Quality Indication 75 PLMN Public Land Mobile Network
15 CSFB Circuit Switched Fallback 76 PLR Packet Loss Rate
16 DL Downlink 77 PM Performance Management (of OAM)
17 ECR Effective Coding Rate 78 PS Packet Switched
18 eNB eNodeB 79 QAM Quadrature Amplitude Modulation
19 EPC Evolved Packet Core 80 QoE Quality of Experience
20 EPS Evolved Packet System 81 QoS Quality of Service
21 EPA Extended Pedestrian A 82 QPSK Quadrature Phase-Shift Keying
22 EVA Extended Vehicular A 83 OFDM Orthogonal Frequency Division Multiplex
23 ETU Extended Typical Urban 84 PCC Policy and Charging Control
24 E-RAB Evolved Radio Access Bearer 85 PCEF Policy & Charging Enforcement Function
25 E-UTRAN Evolved UTRAN 86 PCRF Policy and Charging Rule Function
26 FER Frame Error Rate (audio, or video) 87 PDF Policy Decision Function
27 FTP File Transfer Protocol 88 P-CSCF Proxy-Call Session Control Function
28 GBR Guaranteed Bit Rate 89 RAN Radio Access Network
29 GMC Golden Master Configuration 90 RAT Radio Access Technology
30 GTP GPRS Tunnelling Protocol 91 SLA Service Level Agreement
31 GUTI Globally Unique Temporary UE Identifier 92 SLO Service Level Objective
32 HARQ Hybrid Automatic Repeat Request 93 RPS Requests per Second
33 HLR Home Location Register 94 RRC Radio Resource Control
34 HSPA High Speed Packet Access 95 RAB Radio Access Bearer
35 HSS Home Subscriber Server 96 RB Radio Bearer
36 ICMP Internet Control Message Protocol 97 RT Real Time
37 IE Information Element 98 SAE System Architecture Evolution
38 IETF Internet Engineering Task Force 99 SCTP Stream Control Transmission Protocol
39 IP Internet Protocol 100 SDF Service Data Flow
40 IP-CAN IP Connectivity Access Network 101 SE Spectral Efficiency
41 ISD Inter-site Distance 102 SFS System Feature Specification
42 IMSI International Mobile Subscriber Identity 103 S-GW Serving Gateway
43 IWF Inter-working Function 104 SIR Signal to Interference Ratio
44 KPI Key Performance Indicator 105 SINR Signal to Interference and Noise Ratio
45 KQI Key Quality Indicator 106 SNR Signal to Noise Ratio
46 L3 Layer 3 107 SPR Subscriber Profile Repository
47 LTE Long Term Evolution 108 TA Tracking Area
48 LoS Line of Sight 109 TAU Tracking Area Update
49 M2e Mouth-to-ear (for Audio delay) 110 TP Throughput
50 MAP Mobile Application Part 111 TTI Transmission Time Interval
51 MBR Maximum Bit Rate 112 UDR User Data Repository
52 MIMO Multiple Input, Multiple Output 113 UE User Equipment
53 MM Mobility Management 114 UL Uplink
54 MME Mobility Management Entity 115 UTRAN Universal Terrestrial RAN
55 MMC Mobile to Mobile Call 116 WS Work-station
56 MOS Mean Opinion Score 117
57 MOS-CQ MOS – Conversational Quality
58 MOS-LQ MOS – Listener Quality
59 MOC Mobile Originated Call
60 MT Mobile Termination (of the UE)
61 MTC Mobile Terminated Call
62 MTSI Multi-media Telephony Service over IMS
63 NAS Non-Access Stratum
64 NE Network Element
6/21 NWS LTE RA RD Sys SA NE LTE E2E Field Network Performance
1 1.4 Glossary
Accessibility Accessibility is the ability of a service to be obtained, within specified tolerances and other
given conditions, when requested by the user [ITUE800].
Availability Availability of an item to be in a state to perform a required function at a given instant or at

any instant of time within a given time interval, assuming that the required external
resources are provided [ITUE800].
Confidence level Statistical confidence level expressed as a percentage denotes the probability that a
measurement sample lies inside of a predefined range of values. E.g. the statistical
statement that the mean transport delay is <= 100ms has a 95% confidence level if at most
5 samples out of 100 measurements lie above 100ms.
Integrity The degree to which a service is provided without excessive impairments, once obtained.
The acceptable level of impairments has to be specified. [ITUE800]
Reference cluster It is a well defined part of the mobile operator´s live network, selected for the execution of
field performance tests. It shows the typical traffic characteristics (traffic mix and load
distribution) of the operator´s network.
Reference conditions These are the conditions, which are to be met in the lab, or in the reference cluster during
field network tests. The conditions cover traffic load levels, air link conditions, transport link
capacities, network element configurations, mobile terminal categories, etc.
Retainability 3GPP term with reference to ITU, but ITU does not define it. Reliability is used instead.
Reliability The probability that an item can perform a required function under stated conditions for a
given time interval, [ITUE800].
2
3 1.5 List of Figures and Tables

4 Figure 1: CSFB Network Architecture ............................................................ 8
5 Figure 2: CSFB to UTRAN w/ Redirect, MOC Overview ................................ 11
6 Figure 3: CSFB to UTRAN, LTE Service Request & Redirect ........................ 12
7 Figure 4: CSFB to UTRAN, RRC Connection Setup in UTRAN ..................... 13
8 Figure 5: CSFB to UTRAN, Location Area Update......................................... 14
9 Figure 6: CSFB to UTRAN, Routing Area Update and PDP Context Setup ... 15
10 Figure 7: CSFB to UTRAN, UTRAN Service Request .................................... 16
11 Figure 8: CSFB to UTRAN, CS Call Setup..................................................... 17
12 Figure 9: CSFB to UTRAN w/ Redirect, MTC Overview ................................. 18
13 Figure 10: CSFB to UTRAN, Paging, LTE Service Request & Redirect ......... 20
14 Figure 11: CSFB to UTRAN, Paging Response in UTRAN ............................ 21
15
16 No table of figures entries found.
NWS LTE RA RD Sys SA NE For NSN internal use only Tel.: +49.175.261.5151
7/21 LTE E2E Field Performance -
CSFB Message Flows
1 2. Scope
2 This Technical Note provides background information on CSFB call flows considering
3  LTE and UTRAN access network details, and

4  CS voice call setup procedure.
5 It analyses the resulting call setup latencies, provides a break-out of latencies for
6 each major phase and shows the latency differences to clean 3G calls for MOC and
7 MTC scenarios.
8 The target values are valid among RL30 reference conditions (GMC). Proposals for
9 performance optimized eNB parameter settings are also given to improve the LTE
10 budget of the CSFB call setup time in demo/trial scenarios.
11 Given the very high number of possible CSFB scenarios, an initial selection has been
12 made which allows for field verification testing using RL30.
13 2.1 Feature Support

14 The following features provide support for CSFB based voice services.
15 CSFB to UTRAN:
16 1. CSFB to UTRAN w/ Redirect w/o SIB (RL20, LTE562)
17 2. CSFB to UTRAN w/ Redirect and deferred SIB 11/12 reading
18 (RL20, LTE562; plus RU30EP1 support on UTRAN side)
19 3. CSFB to UTRAN w/ PS Handover (RL40, LTE736)
20 4. CSFB to UTRAN w/ Redirect using MC SIB (RL50, LTE1195)
21 CSFB to GERAN:
22 1. CSFB to GSM w/ Redirect w/o SIB (RL20, LTE562)
23 2. CSFB to GSM w/ Redirect using MC SIB (RL40, LTE984)
24 2.2 Call Scenarios
25 Call scenarios, 3G:
26  MOC: LTE (CSFB to 3G)  3G
27  MTC: 3G  LTE (CSFB to 3G)
28  MTM: LTE (CSFB to 3G)  LTE (CSFB to 3G)
29 Call scenarios, 2G:
33 Call scenarios, 2G/3G:
CSFB Message Flows

2 Interworking scenarios with PSTN and VoIP users connected via Fixed Access
3 Networks are not considered.
4 2.3 Network Architecture

5 The diagram below shows the CSFB LTE – 2G/3G network architecture. The SGs,
6 S3 and S4 interfaces play the central role.
8 Figure 1: CSFB Network Architecture
CSFB Message Flows
1 3. Message Flow Descriptions

2 3.1 Combined EPS/IMSI Attach and Detach
3 A dual mode UE attaches both to the LTE network, and to 2G/3G networks before
4 voice calls via CSFB can be initiated. The procedure is denoted as Combined
5 EPS/IMSI Attachment.
6 This section describes the combined Attach and Detach procedures. The standard
7 3GPP procedures are described in TS 23.401. Section 5.3.2 therein includes the
8 Attach procedures and Section 5.3.8 describes the Detach procedures.
9 3.2 CSFB to UTRAN w/ Redirect

10 3.2.1 Mobile Originated Call (MOC)
11 In the MOC scenario, the calling UE is located in an LTE cell, while the called UE
12 camps in 3G. In the MTC case, the roles are exchanged and the called UE is
13 camping on the LTE cell.
14 3.2.1.1 Overview
15 The diagram below shows an overview of the message flow sequence for a mobile
16 originated voice call, where the calling UE executes a CSFB to 3G before setting up
17 the call to the called UE, which camps in the 3G network. The initial states of UEs
18 are ECM_IDLE in LTE and CM_IDLE in 3G after a combined EPS/IMSI Attach, and
19 3G Attach, respectively. The diagram shows major phases of the setup procedure for
20 an LTE (CSFB 3G) to 3G voice call.
21 1. The calling UE indicates to MME/EPC that it wants to execute a CS voice call

22 (Extended Service Request with CSFB Indicator). The MME redirects it to 3G
23 (or 2G) according to operator policy.
24 2. The UE performs initial access to the 3G (or 2G) cell with best coverage and
25 sets up a signaling bearer to the BTS (RRC Connection Establishment).
26 3. Next, it has to perform a Location Area Update (LAU) procedure, since its
27 location area has changed with high probability since its attachment to the 3G
28 CS domain (during the combined EPS/IMSI attach procedure). The LAU
29 procedure includes the authentication and security mode setting procedure,
30 during which the user is authenticated and the security association is built to
31 the 3G CS domain.
32 4. After LAU, the CS call setup request is sent by the UE to the RNC/MCS.
33 Processing of the call setup request in the CS domain is running parallel to
34 the Routing Area Update procedure, which is also initiated by the UE.
35 5. If the called UE is idle, the MSC initiates a 3G paging procedure to locate it.
36 6. After the state of the called UE is changed to active, the MSC sends the call
37 setup request to it. This is immediately answered by the called UE with Call
38 Confirm. The MSC indicates Call Proceeding to the calling UE.
39 7. These messages are the triggers for the establishment of RABs on both sides
40 of the CS call for voice media exchange.
41 8. With availability of the appropriate RAB for voice, the called user is alerted,
42 and the calling user also receives ring tone.
CSFB Message Flows
1 9. After picking up the phone by the called user, the call is signaled to be
2 connected on both ends.
3 10. In the example shown, the calling UE re-selects the LTE cell after the
4 termination of the voice call.
CSFB Message Flows
LTE-Uu SGs Uu
UE A LTE+EPC A 3G RAN+CN UE B
Switch-on
Combined EPS/IMSI Attach

Dial UE B Initial UE A State:
- ECM_IDLE 3G Attach
Initial E-UTRAN Access LTE Network Initial UE B State: CM_IDLE
RRC Connection Establishment

CSFB to UTRAN w/ Redirect,
Ext. Service Request w/ CSFB Indicator (MO)
MOC: LTE (FB 3G)  3G
Initial UE Context Setup w/ CSFB
RRC Connection Release w/ Redirect
UE Context Release
Initial UTRAN Access incl. SIB Reading
Location Area Update Procedure with CSMO Flag - CS After LAU, PS & CS domain
procedures run in parallel.
Authentication & Security Mode Setup Procedure – CS
Routing Area Update (RAU) Procedure – PS

PDP Context Preparation
Authentication & Security Mode Setup Procedure – PS
PDP Context Activation
RANAP DT [ CM: Service Request, CC: Setup ]

Paging
CS Call Setup
3G Network Access, Side B
RANAP DT [ Paging Response ]
RANAP DT [ CM: Service Accept ]
CC: Setup
CC: Call Confirm

CC: Call Proceeding
RAB Assignment for Voice, Sides A & B

CC: Alerting CC: Alerting Alert User
Ringing (Ringing)
CC: Connect Phone

Pick-up
Call
CC: Connect Acknowledge
Established
Call
Established
Voice Conversation (Media Transfer)
Phone
Hang-up CS Call Release Call
Terminated
(Fast) Redirect to LTE
Initial E-UTRAN Access LTE Network
1 UE A LTE+EPC A 3G RAN+CN UE B
2 Figure 2: CSFB to UTRAN w/ Redirect, MOC Overview

CSFB Message Flows
1
2 3.2.1.2 LTE Service Request and Redirect to UTRAN
3 The diagram below shows the first phase of the MOC scenario. The procedure is
4 activated by the voice call request of the end-user. In this example, the initial mobility
5 state of the LTE UE is ECM_IDLE.
6 After random access to the LTE cell, the RRC connection (SRB1) is setup. According
7 to operator policy settings, the UE selects CSFB for the call and sends NAS
8 Extended Service Request to the MME indicating mobile originated call. The MME
9 stores the registered TAI, LAI and associated MSC/VLR of the calling UE.
10 Using configured priorities of network layers, and radio measurements by the UE, the
11 eNB decides about the cell the UE is directed to. The redirection information is sent
12 to the UE with an RRC Connection Release command. With the UE leaving the LTE
13 cell, the LTE network part of the CSFB procedure is concluded.
14 If the initial state of the UE is ECM_CONNECTED at the time of initiating the voice
15 call, the Redirection phase starts with the RRC UL INFORMATION TRANSFER
16 message of the UE, which carries the NAS Extended Service Request with CSFB
17 flag indicating the mobile originating call. Since the UE Context already exists in the
18 MME, the UE Context is modified (instead of created). The rest of the procedure is
19 identical to the case with UE initial state = ECM_IDLE.
UE eNB NB & RNC MME SAE GW MSC / VLR SGSN
EPS/IMSI
attached
ECM IDLE
RRC IDLE
RA PREAMBLE
RA RESPONSE
RRC CONNECTION REQUEST
RRC CONNECTION SETUP

COMPLTE
(L3 NAS: EXTENDED
SERVICE REQUEST with
mobile originating CSFB) S1-AP: INITIAL UE MESSAGE
A (L3 NAS: EXTENED SERVICE REQUEST)
S1-AP: INITIAL CONTEXT SETUP REQUEST

(with CSFB MOC Indicator)
UE Capability Enquiry (optional)
Selection of redirection targets
RRC CONNECTION S1-AP: INITIAL UE CONTEXT SETUP

RELEASE RESPONSE
(with Redirect Info)
B
S1-AP: UE CONTEXT RELEASE REQUEST
UE leaves LTE cell
and searches for S1-AP: UE CONTEXT RELEASE COMMAND
suitable UTRAN cell
S1-AP: UE CONTEXT RELEASE COMPLETE
20
21 Figure 3: CSFB to UTRAN, LTE Service Request & Redirect
CSFB Message Flows
1 3.2.1.3 Initial UTRAN Access
2 The diagram below shows the second phase of the MOC scenario until the RRC
3 connection is established for SRB1.
UE eNB NB RNC MME SAE GW MSC / VLR SGSN
UE tunes to
UARFCN of
selected cell and
searches for
SysInfo
RRC: RRC CONNECTION REQUEST (RACH:CCCH)

A
NBAP: RADIO LINK SETUP
AAL2/IP transport setup
RRC: RRC CONNECTION SETUP (FACH:CCCH)
L1 synchronization
RRC: RRC CONNECTION SETUP COMPLETE (DCH:DCCH)

B
RRC: MEASUREMENT CONTROL (DCH:DCCH)
5 Figure 4: CSFB to UTRAN, RRC Connection Setup in UTRAN
6 3.2.1.4 Location Area Update (LAU)
7 The diagram below shows the Location Area Update procedure including
8 Authentication and Security Mode Setting for the CS domain of the 3G network.
9 The UE executes the LAU procedure if the Location Area Identifier of the just
10 accessed UTRAN cell is not found in its list of LAIs that has been received during
11 combined EPS/IMSI Attach. Since the LAU is the first procedure of the UE in
12 UTRAN, it always contains the procedure “Authentication and Security Mode
13 Setting”.
14 There are two “Network Modes of Operation – NMO”, the UE may follow. NMO I
15 devices execute combined RA/LA updates, while NMO II/III devices execute these
16 separately. Since NMO II and III modes also require support on the NW side, the
17 current description assumes NMO I, because this is the more typical case and it
18 works in all network topologies.
19 At the end of the LAU procedure, security associations are established between the
20 UE and the CS domain of UTRAN using a temporary IMSI (TMSI) of the UE, which
21 was allocated by the MCS controlling the location area.
22 After successful LAU, the UE issues a CM Service Request indicating that it wants to
23 setup a CS call. In addition, an NMO I type terminal starts the Routing Area Update
24 procedure, as well. The two procedures are running in parallel in the CS and PS
25 domains, respectively.
26
CSFB Message Flows
LOCATION AREA UPDATE – may be executed as part of

Combined RAU/LAU procedure if Gs IF exists
RRC: INITIAL DIRECT TRANSFER (CS domain)

MM: LOCATION UPDATE REQUEST (DCH:DCCH) RANAP: INITIAL UE MESSAGE
C (MM: LOCATION UPDATE REQUEST)
SACK CC Connection Confirm
Authentication & Security Mode Setting - CS
RANAP: DIRECT TRANSFER

(MM: LOCATION UPDATE ACCEPT)
RRC: DL DIRECT TRANSFER
MM: LOCATION UPDATE ACCEPT (DCH:DCCH)
RRC: UL DIRECT TRANSFER

MM: TMSI REALLOCATION COMPLETE (DCH:DCCH)
D RANAP: DIRECT TRANSFER
(TMSI REALLOCATION COMPLETE)
Next steps: UE initiates RAU & CS call setup procedures,

which are running in parallel.
• MOC starts with CM Service Request

• MTC continues with MM Paging Response
2 Figure 5: CSFB to UTRAN, Location Area Update
3 3.2.1.5 Routing Area Update (RAU)
4 The diagram below shows the Routing Area Update procedure including
5 Authentication and Security Mode Setting for the PS domain of the 3G network.
6 Upon receiving a RAU Request, the SGSN queries the MME for all information on
7 the EPS bearer(s) of the UE and prepares for setting up the corresponding PDP
8 Contexts in 3G. After establishing the necessary security associations for NAS
9 signaling in the PS domain, it instructs the SAE-GW to start forwarding DL IP packets
10 from the PDN-GW directly to the SGSN (instead of the S-GW). On the other hand, it
11 starts the activation of PDP Contexts in UTRAN by instructing it to create the
12 corresponding RABs and RBs. Only after the RABs have been created, the RNC
13 accepts the RAU request toward the UE.
14 If some of the PDP Contexts could not be created or activated, the corresponding
15 EPS bearers will be removed by the PDN-GW. Upon expiry of relevant timers, the
16 MME triggers the release of EPS bearers, in this case not by the PDN-GW, but by
17 the S-GW.
18 After mapping all EPS bearers to PDP Contexts in the 3G PS domain and activating
19 the corresponding RABs and RBs, the RAU Request of the UE is accepted by the
20 SGSN. The procedure ends with the RAU Complete message of the UE.
21 It has to be noted, that the RAU procedure is actually unnecessary if the UE returns
22 to LTE after terminating the CS voice call and no PS domain services have been
23 used in 3G. Omitting RAU, or simplifying it in case of basic (or “pure”) CS voice calls
24 could significantly speed up the CSFB procedure.
CSFB Message Flows
UE eNB NB RNC MME SAE-GW MSC / VLR SGSN
RRC: INITIAL DIRECT TRANSFER [PS domain]

GMM: ROUTING AREA UPDATE REQUEST
RANAP: INITIAL UE MESSAGE
E (GMM: ROUTING AREA UPDATE REQUEST)
SGSN CONTEXT REQUEST

Each EPS bearer is
mapped to one SGSN CONTEXT RESPONSE
PDP context.
(PDP Contexts, …)
SGSN creates
corresponding
PDP contexts
SGSN CONTEXT ACKNOWLEDGEMENT
Authentication & Security Mode Setting - PS
GTP: UPDATE PDP CONTEXT REQUEST

SGSN informs S-GW about activated bearers;
From this point onwards DL packets are
transferred to SGSN. GTP: UPDATE PDP CONTEXT RESPONSE
SACK: SM Modify PDP Context Request
Activate PDP contexts in UTRAN.

RANAP: SM Modify PDP Context Accept
RANAP: DT (GMM: ROUTING AREA UPDATE ACCEPT)

RRC: DL DIRECT TRANSFER
GMM: ROUTING AREA UPDATE ACCEPT (DCH:DCCH)

GMM: ROUTING AREA UPDATE COMPLETE
F RANAP: DT (GMM: ROUTING AREA UPDATE COMPLETE)
(if new P-TMSI and/or TMSI was allocated)
2
3 Figure 6: CSFB to UTRAN, Routing Area Update and PDP Context Setup
4 3.2.1.6 UTRAN Service Request
5 The caller UE indicates to the 3G network that it wants to setup a CS call using the
6 CM Service Request. If the MSC does not have a valid identification of the UE, it
7 requests it with an Identity Requests from the RNC. If the RNC has cached
8 information, it can return the IMEI otherwise it queries it from the UE directly. The
9 RNC may have this information from a previous Authentication and Security mode
10 Setting procedure. When the Service Request is accepted by the MSC, it indicates
11 toward the RNC that the core network is prepared for the CS call. However, the
12 called UE must be paged before the CC Setup request can be forwarded if it is in
13 IDLE state.
14 The paging and the random access procedures are standard 3G procedures, they
15 are not described here. The RRC Connection Establishment in UTRAN is shown in
16 Figure 4. After the RRC connection has been established, the MSC can send the CC
17 Setup request in a RANAP message to the called UE. Figure 7 below shows the
18 UTRAN Service Request part of the overall call procedure, while the latter can be
19 seen in Figure 2.
20 The CC Setup message describes the requested bearer capabilities (FR/HR

21 speech), called party number, other call control parameters (like DTMF) and the list
22 of codec supported by the caller.
CSFB Message Flows
RRC: INITIAL DIRECT TRANSFER

MM: CM SERVICE REQUEST w/ CS MO flag (DCH:DCCH)
G RANAP: DT (CM SERVICE REQUEST)
- ServiceType = MOC Establishment
SACK: DT (MM IDENTITY REQUEST)

RRC: DL DIRECT TRANSFER - IdentityType = IMEI
MM: IDENTITY REQUEST, IdentityType (DCH:DCCH)

MM: IDENTITY RESPONSE - IMEI (DCH:DCCH)
RANAP: DT (MM IDENTITY RESPONSE - IMEI)
SACK: DT (CM SERVICE ACCEPT)

- CS domain service prepared for MOC
RANAP: DT (CC SETUP)

H
Next steps:
• MSC initiates Paging of UE B if it is not connected.
• Then, it continues with CC Setup toward UE B
1
2 Figure 7: CSFB to UTRAN, UTRAN Service Request
3 3.2.1.7 CS Call Setup
4 After the called UE received the CC Setup message, it confirms its reception with CC
5 Call Confirm before ringing to the called user. The diagram below (see Figure 8)
6 shows the A side of the message flow after the MSC has received call confirmation
7 from the B side user. It indicates with Call Proceeding to the calling UE that the
8 processing of the call has started, but will take some time, since the RAB for the
9 voice media still has to be established. The RAB Assignment Request specifies the
10 QoS profile, which is consistent with the parameters of the voice call, e.g.
11 conversational traffic class, maximum and guaranteed bit rates, transfer delay target,
12 residual BER, source statistic descriptor (speech), etc. and transport binding (TFT).
13 The RAB Assignment Response indicates to the MSC that the required RAB incl. RB
14 could be created for the voice conversation. The call setup procedure continues with
15 the CC Alerting message toward the calling UE, where a ring tone is generated. This
16 indicates to the calling UE that the call is cross-connected. The latency between
17 dialing the last number by the caller to hearing the ring tone is the “Post-dial delay”,
18 which is the most important E2E latency KPI of voice telephony (Figure 2 shows the
19 trigger events on UE A side).
20 The CS call setup phase is essentially the same for MOC and MTC calls.
CSFB Message Flows
After Paging and sending CC Setup to UE B,

MSC receives CC: Call Confirm from UE B.
RANAP DT (CC: CALL PROCEEDING)

RRC: DL DT (CC: CALL PROCEEDING)
RAB Assignment for Voice RANAP: RAB ASSIGNMENT REQUEST

I
QAAL2: ESTABLISH REQUEST
NBAP: RADIO LINK QAAL2: ESTABLISH RESPONSE

RECONFIGURATION PREPARE
NBAP: RADIO LINK

RECONFIGURATION READY
QAAL2: ESTABLISH REQUEST
QAAL2: ESTABLISH CONFIRM
NBAP: RADIO LINK

RECONFIGURATION COMMIT
RRC: RADIO BEARER SETUP (DCH:DCCH)
RRC: RADIO BEARER SETUP COMPLETE (DCH:DCCH)

RANAP: RAB ASSIGNMENT RESPONSE
RRC: MEASUREMENT CONTROL (DCH:DCCH)
J
RRC: DL DT (CC: ALERTING) RANAP: DT (CC: ALERTING)
RRC: DL DT (CC: CONNECT) RANAP: DT (CC: CONNECT)
RRC: UL DT (CC: CONNECT ACKNOWLEDGE)

RANAP: DT (CC: CONNECT ACKNOWLEDGE)
2 Figure 8: CSFB to UTRAN, CS Call Setup
3 3.2.2 Mobile Terminated Call (MTC)

4 In MTC scenario, the calling UE is in a 3G cell, while the called UE camps in LTE.
5 3.2.2.1 Overview
6 The initial states of UEs are similar to the MOC case. The major phases of the setup
7 procedure are also the same, but they happen on different sides of the call.
8 1. The calling UE in the 3G CS domain indicates to the MSC with a CM Service

9 Request that it wants to execute a voice call to UE B. Since UE B has been
10 previously registered at the CS domain of the 3G network, the VLR/MSC
11 knows its latest location and starts to page it via the corresponding MME.
12 2. The called UE performs initial access to LTE (E-UTRAN cell) and sets up an
13 SRB1 bearer to the eNB (RRC Connection Establishment).
14 3. The phases of the CSFB procedure are the same as in the MOC. As a result,
15 the UE B is connected to the 3G network.
16 4. The connected UE B concludes the Paging procedure by sending a Paging
17 Response message to the MSC. This MSC can be different from the one,
18 which has originated the Paging Request.
19 5. After Paging, the CS call setup procedure is continued by the MSC by
20 sending the CC: Setup request to UE B.
21 6. The next steps are again the same as in the MOC case.
CSFB Message Flows
1
LTE-Uu SGs Uu
UE B LTE+EPC A 3G RAN+CN UE A
Switch-on 3G Attach
Combined EPS/IMSI Attach Initial UE A State: CM_IDLE Dial UE B
3G Network Access, Side A
Initial UE B State: ECM_IDLE CS Call
0.25 s
RANAP DT [ CM Service Request,
DL NAS TP / SGs-AP [Paging] - 100 – 120 ms CC: Setup ]
Initial E-UTRAN Access LTE Network

CSFB to UTRAN w/ Redirect
MTC: 3G  LTE (FB 3G)
100 – 130 ms
Ext. Service Request w/ CSFB Indicator (MT)
Initial UE Context Setup
RRC Connection Release
UE Context Release
Initial UTRAN Access
0.75 s
1.0-1.2 s
Location Area Update Procedure with CSMT Flag - CS After LAU, PS & CS domain
procedures run in parallel.
Authentication & Security Mode Setup Procedure – CS
Routing Area Update (RAU) Procedure – PS
PDP Context Preparation

2.3 – 2.4 s
Authentication & Security Mode Setup Procedure – PS
PDP Context Activation

RANAP DT [ Paging Response ]
CC: Setup
CS Call Setup
CC: Call Confirm
CC: Call Proceeding
4.0 – 4.1 s
RAB Assignment for Voice

Radio Bearer Setup Radio Bearer Setup
Alert User
(Ringing) CC: Alerting CC: Alerting
Ringing
Phone
Pick-up CC: Connect
CC: Connect Acknowledge

Call
Established
Voice Conversation (Media Transfer)

Phone
Call Hang-up
CS Call Release
Terminated
~1s
(Fast) Redirect to LTE
LTE Network
~0.1s
Initial E-UTRAN Access After call release,

re-select LTE.
UE A LTE+EPC A 3G RAN+CN UE B
2
3 Figure 9: CSFB to UTRAN w/ Redirect, MTC Overview
CSFB Message Flows
1 3.2.2.2 Paging, Service Request and Redirect
2 The diagram below shows the message flow of the first phase of a Mobile
3 Terminated Call (MTC) on the LTE side of the network. The procedure is activated by
4 the voice call request of the 3G user (see Figure 9).
5 In the example, the initial mobility state of the called UE is ECM_IDLE. For this
6 reason, the MSC first has to page it in the LTE network. It can do this, because the
7 UE was previously attached to the CS domain of the 3G network with the Combined
8 EPS/IMSI Attach procedure. The tracking area of the UE´s is known, since it has
9 been regularly updated with the RA and LA Update procedures.
10 In the ECM_CONNECTED case (the called UE having an active RRC connection),

11 the procedure is largely simplified, since neither random access to E-UTRAN, nor
12 RRC Connection Establishment is necessary. The Paging Request of the MSC is
13 responded by the MME with SGs Service Request immediately after it has notified
14 the UE with CS Service Notification about the incoming 3G CS event. In the
15 ECM_IDLE case, this happens only after the LTE Extended Service Request with
16 Mobile Terminating Call indication is received by the MME. Otherwise, the procedure
17 is very much the same for both the ECM_IDLE and for ECM_CONNECTED cases.
18 After contention based random access to the LTE cell, an RRC connection is
19 established to send NAS Extended Service Request to the MME indicating CSFB
20 due to an incoming MTC. The rest of the procedure is the same as for the MOC case
21 (the cause for the CSFB is always indicated as MTC).
22 The subsequent phases of the CSFB MTC scenario, the Initial Access to UTRAN,
23 the RRC Connection Establishment, as well as the LAU/RAU procedures are the
24 same as in the MOC case and are not described here.
CSFB Message Flows
UE eNB NB & RNC MME SAE GW MSC / VLR SGSN
SGs-AP: PAGING REQUEST

RRC: DL INFORMATION
S1-AP: DL NAS TRANSPORT (NAS: PAGING)
TRANSFER
(NAS: PAGING) Paging with Indication of
CS event in 3G
Retry (optionally)
RA PREAMBLE
Retry (optionally)
Initial E-UTRAN Access
RA RESPONSE & RRC Connection
Establishment
RRC CONNECTION REQUEST
RRC CONNECTION SETUP COMPLETE

S1-AP: INITIAL UE MESSAGE
(NAS: EXT. SERVICE REQUEST (NAS: EXTENED SERVICE REQUEST)
w/ MT CSFB) SGs-AP: SGs Service Request
S1-AP: INITIAL CONTEXT SETUP REQUEST
(with MT CSFB Indicator)

UE Capability Enquiry (optional)
Extended Service Request w/
Selection of redirection targets MTC Indication & Redirect
RRC CONNECTION
S1-AP: INITIAL UE CONTEXT SETUP RESPONSE
RELEASE
(with Redirect Info)
S1-AP: UE CONTEXT RELEASE REQUEST

UE leaves LTE cell Release of UE Context &
and searches for S1-AP: UE CONTEXT RELEASE COMMAND RRC Connection (UE goes ECM_IDLE)
suitable UTRAN cell
S1-AP: UE CONTEXT RELEASE COMPLETE
2 Figure 10: CSFB to UTRAN, Paging, LTE Service Request & Redirect
3 3.2.2.3 Paging Response & CS Call Setup
4 After Paging Response has been received by the MSC, it can send the CC Setup
5 request in a RANAP message to the called UE, see Figure 7 below.
6 The CC Setup message describes the requested bearer capabilities (FR/HR

7 speech), called party number, other call control parameters (like DTMF) and the list
8 of codec supported by the caller.
9 The subsequent CS Call Setup procedure is identical to the MOC case.
CSFB Message Flows

MM: PAGING RESPONSE (DCH:DCCH)
G
RANAP: DT (PAGING RESPONSE )
SACK: DT (CC Setup)

- CS domain service prepared for MTC
MM: CC Setup(DCH:DCCH)
H
1
2 Figure 11: CSFB to UTRAN, Paging Response in UTRAN
3 3.2.3 Call Release

4 The call release diagram is tbd.
14

CSFB To 2G 3G - E2E Message Flows

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CSFB To 2G 3G - E2E Message Flows

Hochgeladen von

Copyright:

Verfügbare Formate

1/21 MBB LTE SD P&C LTE E2E Field Performance

3 LTE E2E Field Performance

7 - Technical Note on E2E Message Flows -

11 Document Status: Draft, Internal

12 Release 1.0, Issue 04

13 Date: 30th November 2012

19 Issued by the Nokia Siemens Networks GmbH & Co. KG

20 Copyright  Nokia Siemens Networks GmbH & Co. KG 2012

21 All Rights Reserved

Author: Dr. Andras Balazs MBB LTE SD P&C

2 1. General Information ............................................................ 3

12 3. Message Flow Descriptions ................................................ 9

V1.01 31.03.2012 First draft.

V1.02 07.04.2012 Second draft.

V1.3 05.07.2012 Additional CSFB scenarios

Dr. Andras Balazs MBB LTE SD P&C

Krystian Krysmalski NWS LTE RA RD Sys SA NE

[3GPP25.943] 3GPP TR 25.943; V8.0.0 (2008-12); Deployment Aspects (Release 8).

4 AF Application Function 65 NRT Non Real Time

Availability Availability of an item to be in a state to perform a required function at a given instant or at

3 1.5 List of Figures and Tables

16 No table of figures entries found.

3  LTE and UTRAN access network details, and

13 2.1 Feature Support

1  MTM: LTE (CSFB to 3G)  LTE (CSFB to 2G)

4 2.3 Network Architecture

8 Figure 1: CSFB Network Architecture

1 3. Message Flow Descriptions

9 3.2 CSFB to UTRAN w/ Redirect

21 1. The calling UE indicates to MME/EPC that it wants to execute a CS voice call

Combined EPS/IMSI Attach

Initial E-UTRAN Access LTE Network Initial UE B State: CM_IDLE

RRC Connection Establishment

RRC Connection Release w/ Redirect

Initial UTRAN Access incl. SIB Reading

RRC Connection Establishment

Routing Area Update (RAU) Procedure – PS

Authentication & Security Mode Setup Procedure – PS

PDP Context Activation

RANAP DT [ CM: Service Request, CC: Setup ]

CC: Call Confirm

RAB Assignment for Voice, Sides A & B

CC: Connect Phone

Voice Conversation (Media Transfer)

(Fast) Redirect to LTE

Initial E-UTRAN Access LTE Network

RRC Connection Establishment

2 Figure 2: CSFB to UTRAN w/ Redirect, MOC Overview

UE eNB NB & RNC MME SAE GW MSC / VLR SGSN

RRC CONNECTION REQUEST

RRC CONNECTION SETUP

RRC CONNECTION SETUP

S1-AP: INITIAL CONTEXT SETUP REQUEST

UE Capability Enquiry (optional)

Selection of redirection targets

RRC CONNECTION S1-AP: INITIAL UE CONTEXT SETUP

21 Figure 3: CSFB to UTRAN, LTE Service Request & Redirect

1 3.2.1.3 Initial UTRAN Access

UE eNB NB RNC MME SAE GW MSC / VLR SGSN

RRC: RRC CONNECTION REQUEST (RACH:CCCH)

AAL2/IP transport setup

RRC: RRC CONNECTION SETUP (FACH:CCCH)

RRC: RRC CONNECTION SETUP COMPLETE (DCH:DCCH)