Oea100007 CSFB Solution Issue1.00

CSFB Solution
www.huawei.com
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
References
3GPP TS 23.272 Circuit Switched (CS) fallback in Evolved P

acket System (EPS)
3GPP TS 29.118 Mobility Management Entity (MME) Visito

r Location Register (VLR) SGs interface specification (Relea
se 8)
Page 3
Training Objectives
After learning this course, you can:
Describe the fundamentals of the CSFB.
Describe the key procedures of the CSFB.
Describe the SGs interface and protocol.
Describe the feature data configuration of the CSFB.
Describe the network deployment of the CSFB.
Page 4
Contents
1. CSFB Fundamentals
2. Key Procedures
3. SGs Interface and Protocol
4. Feature Data Configuration
5. Network Deployment
Page 5
Origin of the CS Fallback Solution

Key issues
How can telecom operators provide the voice and SM services before
the IMS is deployed at the initial stage of the LTE?
The UE cannot provide the IMS service in the LTE coverage scope.
After falling back to the existing 2G/3G network, the UE initiates and
completes the Circuit Switched domain (CS) service.
GU CS
Page 6
Voice Service of the CS Fallback
The CSFB service must be deployed by using the current 2G/3G CS network. The service
provides a fallback technology to ensure that a subscriber can be registered to the LTE-SAE
network and the traditional CS network at the same time. To use the voice service, the
subscriber falls back to the CS through the LTE-SAE network first.
Page 7
PS and SMS Services in the CSFB

The SM service does not
need to fall back, but is
transmitted transparently
at the SGs interface.
When the voice

service falls
back, the data
service is
switched to the
2G/3G PS or
suspended.
For the SMS service, the EPC network does not require the UE to
fall back to the traditional CS to send or receive SMs. SMs are
transferred
network. This
directly through the LTE NA signaling on the EPC

greatly improves the efficiency of the SMS service.
Page 8
Features of the CSFB Solution
The MSC/VLR supports the SGs interface.
The MME supports the SGs interface.
The UE supports both the CS service and PS service.
Solution
Strengths
CS Fallback Low terminal cost.

Supporting the SMS over
SGs SM solution.
Minor change to the
network; a fast and highly
efficient transition
solution.
Weaknesses
Requiring full-network
coverage of 2G/3G wireless
signals.
The 2G/3G CS network
must be upgraded.
The LTE/SAE network must
support the related
functions.
Page 9
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
SGs Interface and Protocol
Feature Data Configuration
Network Deployment
Page 10
Contents
2. Key Procedures
2.1 CS Mobility Management Procedure
2.2 Voice Service Procedure (MO)
2.3 Voice Service Procedure (MT)
2.4 SM Service Procedure
Page 11
Attach (combined EPS/IMSI Attach)
Page 12
Combined EPS/IMSI Attach Procedure

The UE registers with the CS network and EPC network at the same time by using
the attach procedure.
Attach type
Combined EPS/IMSI
Attach
UE is capable to use
CSFB
Derive VLR NO.

TAI -> LAI -> VLR NO.
Create SGs association
Save
Save the
the MME
MME
address
address to
to
forward
forward the
the
paging
paging message
message
The MSC/VLR stores the MME

Attach accept
The MME sends TMSI
and TAI
Page 13
Attach Procedure Trace
After "CSFB prefer" i

s set on the UE, the
UE initiates combine
d attach.
Page 14
Attach Procedure Trace (Cont.)
Page 15
The MME Sends an LA Update Req to

the MSC
When receiving the combin

ed attach request, the MME
sends an LA update messag
e to the MSC.
Page 16
The MSC Answers the LA Update Res

p to the MME
The MSC saves the MM
E information to forward
downlink paging to the
MME.
Page 17
Attach Accept Trace
After the combined location

update, the UE saves the
TA list, LAI, GUTI, and
TMSI at the same time.
Page 18
UE-Initiated Detach Procedure

The UE deregisters from the EPC or CS network by using the detach procedure.
UE-initiated detach
procedure
MME-initiated detach
procedure
HSS-initiated detach
procedure
Detach type
Combined EPS/IMSI
Detach
EPS detach
IMSI detach
Remove SGs
association
The MSC removes the MME
Page 19
Detach Request from UE
Type of detach (In the UE to

network direction):
(1) EPS detach
(2) IMSI detach
(3) Combined EPS/IMSI detach
Page 20
EPS Detach Indication on the SGs Int

erface
The association between

the MME and MSC is
removed through this
message.
Page 21
Detach Accept
Page 22
MME-Initiated Detach Procedure

After the procedure ends, the MSC/VLR removes the SGs association of MME related to this UE.
UE
MME
MSC/VLR
HSS
1.MME-initiated Detach as specified in TS 23.401

2.EPS/IMSI
Detach Indication
3.Remove SGs
association
Page 23
HSS-Initiated Detach Procedure
When changing
the subscription
data, the HSS
initiates a detach
procedure.
Page 24
Combined TA/LA Update Procedure
Page 25
Contents
2. Key Procedures
Page 26
CSFB MO Call in Active Mode - PS HO S

upported
Step 1-2
CSFB
1a.1b include CS fallback Indicator
Step 4-6 call

service
Page 27
Extended Service Request (step1a)
The UE sends a CSFB indicator in th

e extended service request.
Page 28
Initial Context Setup Req (step1b)

Instruct the
eNodeB to
execute CSFB
Page 29
Initial Context Setup Resp (step1b)
This message means eNodeB

receive CSFB indicator.
The IE in this message is

eaningless.
Page 30
CSFB MO Call in Active Mode - PS H

O Supported (Step 23)
Handover preparation and start of handover execution is as follows:
The eNodeB requests the UE to report the measurement

result. The eNodeB selects the target cell.
Handover
preparation
Start of
execution
The Ho From E-UTRAN Command message

contains the CS Fallback Indicator.
If Step 4 fails, the CSFB procedure also fails.
Page 31
CSFB MO Call in Active Mode - PS H

O Supported (Step7)
The downlink packet
cached in the PGW is
forwarded between
the source eNodeB
and target RNC.
The target SGSN

updates the tunnel
address to the PGW.
The resource is
removed at the
E-UTRANside.
Page 32
Mobile Originating call in Active Mode

PS HO Not Supported
Step 1-2
CSFB
Step 3-5
RRC
release
6. If the RA/LA changes, the

location update procedure
may be triggered.
Step 7 PS
suspend
Step 9-10
call service
7a. If the target network does not

support DTM, the PS
service is suspended. The
MME deactivates the GBR
bearer and keeps the nonGBR bearer.
Page 33
Mobile Originating Call in Idle Mode
If the UE is in the idle state, the UE must change to the E

MM-CONNECTED activation state before initiating a call.
The UE first sends a service request message to set up a
n S1 connection.
After the UE is activated, the Mobile Originating call in Act

ive Mode procedure starts.
Page 34
Contents
2. Key Procedures
Page 35
CS Fallback MT Procedure
Phase 1: The MME receives a Paging message from the SGs interface and pages the
UE.
Optional procedure: The subscriber returns to the connected state from the idle state.
Phase 2: The subscriber is relocated to the target cell (through reselection or handover).
Phase 3: The paging response is initiated at the CS.
Page 36
Callee Service Procedure in the Connected

State - Supporting PS Handover
The UE falls
back to the CS
Page 37
Service Procedure of the Callee in the Connected

State - Not Supporting the PS Handover
Suspend the
PS service
Page 38
Service Procedure of the Callee in the

Idle State
The UE first changes from the ECMidle state to the ECMconnected state
.
UE
eNodeB
MME
RNC/
BSC
MSC
HSS
GMSC
1.IAM
2. SRI procedure
3. IAM
6. Paging
5. Paging
4. Paging
7a. Extend Service Request
7b. Initial UE Context Setup

8a. PS handover
8b. eNB assisted
cell change
8c. Location Area Update
8d. Paging Response
Page 39
Service Procedure of the Callee in the

Idle State
The UE first changes from the ECMidle state to the ECMconnected state.
UE
eNodeB
MME
RNC/
BSC
MSC
HSS
GMSC
1.IAM
2. SRI procedure
3. IAM
6. Paging
5. Paging
4. Paging
7a. Extend Service Request
7b. Initial UE Context Setup

8a. PS handover
8b. eNB assisted
cell change
8c. Location Area Update
8d. Paging Response
Page 40
Paging from MSC
Page 41
Paging from MME to eNodeB
The MME indicates that the subscriber is

paged in the specified TA.
Page 42
Extended Service Req
Page 43
The MME Sends the Initial UE Context S

etup Message
Page 44
Contents
2. Key Procedures
Page 45
CS Fallback MO SMS over SGs
Page 46
CS Fallback MO SMS over SGs
Page47
CS Fallback MT SMS over SGs
Page 48
CS Fallback MT SMS over SGs
Page49
System Implementation of the SMS
The following figure shows the system implementation of the SMS:
UE
eNodeB
MME
MSC
When the Short Message Service (SMS) is provided, the MME functions as an interme
diate forwarding node to forward the messages between the UE and the MSC. The MM
E assists the UE and MSC in completing the SM function.
Different from the voice function, the SM function does not require the UE to fall back to
the GERAN/UTRAN. The E-UTRAN is directly used to provide the UE with the SMS.
Page 50
SM Procedure of the Caller in the Idl

e State
Page 51
SM Procedure of the Caller in the Acti

vated State
SM procedure of the caller of the CSFB in the activated state

The SM procedure of the caller in the activated state is similar to that in the idle sta
te. For the SM procedure of the caller in the activated state, the UE does not need
to initiate a service request procedure, but interacts with the MME directly on the e
xisting signaling connection.
Procedure of multiple SMs of the caller

When the first caller's SM has not been sent completely, the UE sends another SM.
The UE first sends the Uplink NAS Transport message to the MME, but does not th
e acknowledgement message in Step 11 in the preceding figure. This avoids reest
ablishment of the air interface and S1 interface connection after the air interface an
d S1 interface are released.
Page 52
SM Procedure of the Callee in the Idle

State
Page 53
SM Procedure of the Callee in the Co

nnected State
SM procedure of the callee in the connected state

The SM procedure of the callee in the connected state is similar to that in the i
dle state. For the SM procedure of the callee in the activated state:
- After receiving the SGsAP Paging Request message in Step 5 in the precedi
ng figure, the MME queries the UE context and knows that the current UE is c
onnected. The MME does not page the UE, namely, Step 6 to Step 8 in the pre
vious figure are skipped, and Step 8a is executed directly. The MME sends an
SGsAP Service Requestmessage to the MSC/VLR, indicating that the NAS m
essage can be transferred between the UE and the MME.
Page 54
Procedure of Multiple SMs of the Call

ee
Procedure of multiple SMs of the callee

When the MSC requires to send more than one SM to the UE, the M
SC does not send the SGsAP Release Request message in Step 16
in the preceding figure. The MSC first sends an SGsAP Downlink Uni
tdata message to transfer the new SM to the MME. This avoids re-pa
ging of the UE after the air interface and S1 interface are released.
Page 55
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
Network Deployment
Page 56
Newly Added SGs Interface
Among the voice features of the CS Fallback, the most important interface is
the SGs interface. The SGs interface between the MME and MSC server is
used to process the mobility management and voice service paging
procedure between the EPS and the CS. In addition, the SGs interface also
provides the SMS transmission function (SMS over SGs).
The transport layer of the SGs interface uses SCTP to guarantee

transmission reliability.
Page 57
Message Functions of SGs

Message Name
Function
SGsAP-LOCATION-UPDATEREQUEST
Attach, Combined LA/TA: The MME sends a

location update message to the MSC.
SGsAP-EPS-DETACH-INDICATION
message
EPS detach.
SGsAP-IMSI-DETACH-INDICATION
IMSI detach.
SGsAP-SERVICE-REQUEST
SMT: The MME sends a service request as

the response message of paging.
Service indicator: CS call indicator
or SMS indicator.
SGsAP-PAGING-REQUEST
MT: The MSC sends a Paging message to

the MME.
SGsAP-UPLINK-UNITDATA
SMO: The MME sends an SM to the MSC.
SGsAP-DOWNLINK-UNITDATA
SMT: The MSC sends an SM to the MME.
Page 58
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
Network Deployment
Page 59
7. CSFB Feature Related Configuration (1)
Operation procedure
1.
Establish inter-device communication between the MME and MSC:

- Run the ADD SCTPPARA command to add the SCTP parameter template of association
path between the MME and MSC.

- Run the ADD VLR command to add the SCTP association information from the MME to t
he specified MSC.
- Run the DSP VLR command to query whether the SCTP association state between the M
ME and MSC is normal.
2.
Activate the CSFB service:

- Run the ADD LAIVLR command to add an LA of MSC coverage.
- Run the ADD TAILAI command to add a TA range of LA coverage.

- Run the SET SGSPARA command to set the service running parameters of the SGs inter
face.
Note: The CSFB feature requires license support. Run the DSP LICENSE command to view w
hether the current license supports the CSFB feature.
Page 60
7. CSFB Feature Related Configuration

(2)
Establish inter-device communication between the MME and MSC.
[USN MML]: Add the SCTP parameter template of association path between t
he MME and MSC.
ADD SCTPPARA: SCTPPARAINDEX="SCTP Protocol Parameter Index";
[USN MML]: Add the SCTP association information from the MME to the specif
ied MSC.
ADD VLR: VLRNO = "VLR No.", IPTYPE = IPV4, VLRIPV4_1 = "VLR IPv4
Address 1", VLRIPV4_2 = "VLR IPv4 Address 2", SUBRACKNO = "Subrac
k No.", SLOTNO = "Slot No.", LOCALIPV4_1 = "Local IPv4 Address 1", LO
CALIPV4_2 = "Local IPv4 Address 2", SCTPINDX = "SCTP Protocol Para
meter Index";
[USN MML]: Query whether the SCTP association state between the MME an
d MSC is normal.
DSP VLR: VLRNO = "VLR No.";
Page 61
7. CSFB Feature Related Configuration

(3)
Step 2 Activate the CSFB service.
Add LAs of MSC coverage.
[USN MML]: ADD LAIVLR: BGNLAI = "Beginning LAI", ENDL

AI = "End LAI", VLRNO = "VLR No.";
Add a TA range of LA coverage.
[USN MML]: ADD TAILAI: BGNTAI = "Beginning TAI", ENDTA

I = "End TAI", LAI = "LAI";
Page 62
7. CSFB Feature Related Configuration (3)
Step 3 Set the service running parameters of the SGs in

terface.
[USN MML]: SET SGSPARA: TS6_1 = "Location Update Timer",

TS8 = "EPS Separation Timer", TS9 ="Display IMSI Separation Ti
mer", TS10="Implicit IMSI Separation Timer", NS8 = "EPS Separa
tion Retransmission Times", NS9 = "Display IMSI Separation Retr
ansmission Times", NS10 = "Implicit IMSISeparation Retransmiss
ion Times";
Page 63
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
Network Deployment
Page 64
CS Fallback Deployment
Solution 1
Strengths
1.
2.
Solution 2
Deployment principles
The live network is upgraded

on a small scale. Only one to
two MSC servers need to be
upgraded or newly deployed
for each MSC pool.
The solution can resolve the
problem of Roaming Retry.
Weaknesses
The function of MSC pool must be

supported.
Strengths
The function of MSC pool does not

need support.
Weaknesses
All the MSCs in the LTE coverage of

the live network must be upgraded.
In addition, the network must be
upgraded to support the Roaming
Retry function.
1. Deploy the MSC server and MME that support the SGs interface. Ensure that other network entities of the SAE are not affected.
2. Ensure the mapping between the TA and the LA to avoid execution of unnecessary LAU and Roaming Retry procedures during
CS Fallback.
3. For solution 1, you are advised to deploy a new pair of MSC servers of high capacity and high integration to provide the CS
fallback service.
4. For solution 2, the software is upgraded for only the MSC in the common coverage area of the LTE and 2G/3G networks where the
CS fallback service will be provided. You are advised to use the active plane and standby plane to upgrade the software in turn and
minimize the service interruption time.
Page 65
Impact Factors of CSFB Performance
The TAI List of the LTE network is inconsistent with the LAC of the CS network. The location up
date procedure is added to the caller procedure. The roaming retry procedure is added to the c
allee procedure. The CSFB procedure latency is added.
The coverage scope of

TA List covers LA 1
and LA 2.
TA1
TA1
TA6
TA2
TA2
TA4
TA3
MSC 1
TA3
TA6
LA 2
MSC 2
BSC 1 BTS 1
The UE is powered
on at LA 1 and
registered with
MSC 1.
LA 1
BTS 2
LTE TA List
When the UE initiates a

caller service at LA 2, the
location must be reupdated. MSC 2 is used to
initiate the caller service.
Location update is not initiated when the

subscriber moves from LA 1 to LA 2.
BSC 2
Page 66
Impact Factors of the CSFB (Call

er Procedure)
The TA List is
consistent with the LA
planning. As a result,
the LAU procedure is
initiated after CSFB.
Page 67
Impact Factors of the CSFB (Callee P

rocedure)
The TA List is
consistent with the LA
planning to avoid
initiation of the
roaming retry
procedure after the
CSFB
Page 68
SMS over SGs Deployment
Deployment principles
1. Deploy the MSC server and MME that support the SGs interface. Ensure that other network
entities of the SAE are not affected.
2. The telecom operator can deploy a small number of MSC servers as required. The minimum
number of MSC servers is one in the whole network.
3. Deployment of the SMS network is not affected, such as SM-SC.
Page 69
Voice Solution to UE Settings

The UE, MSC, and MME jointly implement the CSFB function.
IMS PS Voice preferred
Reference from 3GPP TS 23.221 Annex A.2
1.
2.
CS Voice preferred
Reference from 3GPP TS 23.221 Annex A.3
A subscriber can set the voice mode as desired.

Adding the network capability enables the subscriber to enjoy uninterrupted voice service when
roaming between different networks.
Page 70
CS Fallback Latency Analysis

During the CS fallback procedure, the CSFB needs additional latency (that is, PS
HO/NACC/RRC Release)
UE/MS
The UE initiates a call
eNodeB
MME
BSS/RNS
MSC
Serving
GW
SGSN
1a. Extended Service Request

1b. S1-AP Request message with CS Fallback indicator
1c. S1-AP Response message
2. Optional Measurement Report Solicitation
3a. PS HO as specified in 23.401 [2] (preparation phase and start of execution phase)
Additional
3b. Suspend
latency
4a. Location Area Update or Combined RA/LA Update
3c. Update Bearer(s)
4b. CM Service Request

4b. A/Iu-cs message (with CM Service Request)
5. CM Service Reject
5. CM Service Reject
If the MSC
is changed
Location Area Update or Combined RA/LA Update
Normal CS
procedure
6. CS call establishment procedure

7. PS HO as specified in 23.401 [2] (continuation of execution phase)
Page 71
P-GW/
GGSN
CS Fallback Latency Analysis
CSFB to GERAN
CSFB to UTRAN
RRC
Latency (ms)
GERAN
PS HO
Plain RRC
native
case
release
RRC release
Latency
UTRAN
PS HO
RRC
Release
(ms)
native
case
Release
(cached
100
100
100
150
150
150
Measurement
320
PS HO
250
RRC release
50
50
320
1530
250
750
750
750
2000-5000
2000-5000
2000-5000
2000-5000
3070-6070
2820-5820
4580-7580
3300-6300
100
100
(SIB cache)
100
150
150
150
Idle to active (E-
2640
UTRAN)
250
50
50
2600
600
SIBs)
Idle to active (E-UTRAN)

Extended service req.
Measurement
PS HO
RRC release
Camp/Access in GERAN
GERAN RRC connection
1000
1000
1000
setup
2000-5000
2000-5000
2000-5000
2000-5000
3000-6000
4890-7890
5900-8900
3900-6900
NAS/E2E procedure (M-M)

Total
Extended service
req.
Camp/Access in
UTRAN
UTRAN RRC
connection setup
NAS/E2E
procedure (M-M)
Total
Page 72
CS Fallback Performance Optimization
Common optimization methods
Selective idle mode camping: In idle state, the UE camps

in the 2G/3G cell. The method ensures that the call latency
of the CSFB is consistent with the native CS call latency,
but the PS service performance is not guaranteed.
Enhanced RRC redirection with SIB: The method is a R9

feature. The RRC Release message contains the 2G/3G
SIB information. This prevents the UE from consuming
time to read SIB on the 2G/3G network.
Page 73
Comparison between the SRVCC and

CSFB
Highlight
SRVCC
CSFB
Coverage
Supports LTE + IMS hot spot

coverage and provides voice and
data services.
Provides PS services within the

LTE coverage, and voice
services within the 2G/3G
coverage.
Trigger condition
Triggered when a subscriber

moves from a location within the
LTE coverage to a location within
the 2G/3G coverage.
Triggered when the subscriber

uses the CS service.
The MME
addresses the
MSC.
Queries the DNS according to the

Target ID.
Target ID -> hostname -> IP
Configures the MSC IP statically

according to the Target TAI.
Target TAI -> LAI -> VLR NO. ->
MSC IP
Voice indicator in
the extended
service request.
SRVCC indicator
CSFB indicator
Attach type
EPS attach
Combined IMSI/EPS attach
UE settings
SRVCC preferred
CSFB preferred
Page 74
Comparison between the SRVCC and

CSFB
Highlight
SRVCC
CSFB
Network
deployment
Requires the IMS, and uses

the IMS and CS to implement
voice services.
Uses the CS to implement

voice services.
Upgrades the MME/E-MSC to

support the Sv interface.
Upgrades the MME/E-MSC

to support the SGs interface.
Upgrades the HSS to support

theSTR-SN and C-MSISDN.
Null
STR-SN handover number: The SRVCC/IWF uses the number as the

called number for routing to the SRVCC AS.
CMSISDN: The SRVCC AS uses the number to associate the CS
session with the original IMS session.
Page 75
Summary
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
Network Deployment
Page 76
Thank you
www.huawei.com

Oea100007 CSFB Solution Issue1.00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oea100007 CSFB Solution Issue1.00

Uploaded by

Copyright:

Available Formats

CSFB Solution

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

3GPP TS 23.272 Circuit Switched (CS) fallback in Evolved P

3GPP TS 29.118 Mobility Management Entity (MME) Visito

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

After learning this course, you can:

Describe the fundamentals of the CSFB.

Describe the key procedures of the CSFB.

Describe the SGs interface and protocol.

Describe the feature data configuration of the CSFB.

Describe the network deployment of the CSFB.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Origin of the CS Fallback Solution

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Voice Service of the CS Fallback

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

PS and SMS Services in the CSFB

When the voice

directly through the LTE NA signaling on the EPC

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Features of the CSFB Solution

The MSC/VLR supports the SGs interface.

The MME supports the SGs interface.

The UE supports both the CS service and PS service.

CS Fallback Low terminal cost.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Attach (combined EPS/IMSI Attach)

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Combined EPS/IMSI Attach Procedure

Derive VLR NO.

The MSC/VLR stores the MME

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Attach Procedure Trace

After "CSFB prefer" i

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Attach Procedure Trace (Cont.)

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

The MME Sends an LA Update Req to

When receiving the combin

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

The MSC Answers the LA Update Res

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Attach Accept Trace

After the combined location

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

UE-Initiated Detach Procedure

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Detach Request from UE

Type of detach (In the UE to

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

EPS Detach Indication on the SGs Int

The association between

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

MME-Initiated Detach Procedure

1.MME-initiated Detach as specified in TS 23.401

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

HSS-Initiated Detach Procedure

Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.

Combined TA/LA Update Procedure