Documente Academic
Documente Profesional
Documente Cultură
www.huawei.com
References
Page 3
Training Objectives
Page 4
Contents
1. CSFB Fundamentals
2. Key Procedures
3. SGs Interface and Protocol
4. Feature Data Configuration
5. Network Deployment
Page 5
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
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
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
Page 8
Solution
Strengths
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
Page 12
Combined EPS/IMSI
Attach
UE is capable to use
CSFB
Page 13
Page 14
Page 15
Page 16
Page 17
Page 18
Detach type
Combined EPS/IMSI
Detach
EPS detach
IMSI detach
Remove SGs
association
The MSC removes the MME
Page 19
Page 20
Page 21
Detach Accept
Page 22
UE
MME
MSC/VLR
HSS
Page 23
When changing
the subscription
data, the HSS
initiates a detach
procedure.
Page 24
Page 25
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 26
Page 27
Page 28
Page 29
Page 30
Handover
preparation
Start of
execution
Page 31
The resource is
removed at the
E-UTRANside.
Page 32
Step 7 PS
suspend
Step 9-10
call service
Page 33
Page 34
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 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).
Page 36
The UE falls
back to the CS
Page 37
Suspend the
PS service
Page 38
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
Page 39
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
Page 40
Page 41
Page 42
Page 43
Page 44
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 45
Page 46
Page47
Page 48
Page49
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
Page 51
Page 52
Page 53
Page 54
Page 55
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
SGs Interface and Protocol
Feature Data Configuration
Network Deployment
Page 56
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).
Page 57
Function
SGsAP-LOCATION-UPDATEREQUEST
SGsAP-EPS-DETACH-INDICATION
message
EPS detach.
SGsAP-IMSI-DETACH-INDICATION
IMSI detach.
SGsAP-SERVICE-REQUEST
SGsAP-PAGING-REQUEST
SGsAP-UPLINK-UNITDATA
SGsAP-DOWNLINK-UNITDATA
Page 58
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
SGs Interface and Protocol
Feature Data Configuration
Network Deployment
Page 59
Operation procedure
1.
2.
Page 60
[USN MML]: Add the SCTP parameter template of association path between t
he MME and MSC.
[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.
Page 61
Page 62
Page 63
Contents
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
SGs Interface and Protocol
Feature Data Configuration
Network Deployment
Page 64
CS Fallback Deployment
Solution 1
Strengths
1.
2.
Solution 2
Deployment principles
Weaknesses
Strengths
Weaknesses
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
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.
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
BSC 2
Page 66
The TA List is
consistent with the LA
planning. As a result,
the LAU procedure is
initiated after CSFB.
Page 67
The TA List is
consistent with the LA
planning to avoid
initiation of the
roaming retry
procedure after the
CSFB
Page 68
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
1.
2.
CS Voice preferred
Page 70
eNodeB
MME
BSS/RNS
MSC
Serving
GW
SGSN
Additional
3b. Suspend
latency
5. CM Service Reject
If the MSC
is changed
Normal CS
procedure
Page 71
P-GW/
GGSN
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
2640
UTRAN)
250
50
50
2600
600
SIBs)
1000
1000
1000
setup
2000-5000
2000-5000
2000-5000
2000-5000
3000-6000
4890-7890
5900-8900
3900-6900
Extended service
req.
Camp/Access in
UTRAN
UTRAN RRC
connection setup
NAS/E2E
procedure (M-M)
Total
Page 72
Page 73
SRVCC
CSFB
Coverage
Trigger condition
The MME
addresses the
MSC.
Voice indicator in
the extended
service request.
SRVCC indicator
CSFB indicator
Attach type
EPS attach
UE settings
SRVCC preferred
CSFB preferred
Page 74
SRVCC
CSFB
Network
deployment
Null
Page 75
Summary
1.
2.
3.
4.
5.
Fundamentals
Key Procedures
SGs Interface and Protocol
Feature Data Configuration
Network Deployment
Page 76
Thank you
www.huawei.com