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

Packet System (EPS)
3GPP TS 29.118 Mobility Management Entity (MME) Visitor Location Register (VLR) SGs interface specification
(Release 8)
Page 2
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 3
Contents
1. CSFB Fundamentals
2. Key Procedures 3. SGs Interface and Protocol
4. Feature Data Configuration 5. Network Deployment
Page 4
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.

MME
IMS CN SAE-GW
GU CS
Page 5
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 6
PS and SMS Services in the CSFB

Um/Uu Iu-cs/A BS Iu/Gb MSC Server
When the voice service falls back, the data service is switched to the 2G/3G PS or suspended.
Uu
SGSN Gn/S3
SGs S6a
The SM service does not need to fall back, but is transmitted transparently at the SGs interface.
HSS
S1-C S1-U eNB
S11
SAE-GW
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
directly through the LTE NA signaling on the EPC network. This

greatly improves the efficiency of the SMS service.
Page 7
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
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.
CS Fallback Low terminal cost. Supporting the SMS over SGs SM solution. Minor change to the network; a fast and highly efficient transition solution.
Page 8
Contents
1. Fundamentals
Page 9
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 10
Attach (combined EPS/IMSI Attach)

MSC Server
BSC/RNC
SGSN
SGs MME
1 1 3 3 eNB SAE-GW
Page 11
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
UE
MME 1. Attach Request
MSC/VLR
HSS
Combined EPS/IMSI Attach UE is capable to use CSFB
2. Step 3 to step 16 of the Attach procedure specified in TS 23.401

Derive VLR NO.
3. Derive VLR number 4. Location Update Request
TAI -> LAI -> VLR NO.
Create SGs association

Save the MME address to forward the paging message
5. Create SGs association

The MSC/VLR stores the MME
6. Location update in CS domain

Attach accept
7. Location Update Accept 8. Step 17 to step 26 of the Attach procedure specified in TS 23.401
The MME sends TMSI and TAI
Page 12
Attach Procedure Trace
After "CSFB prefer"

is set on the UE, the UE initiates combined attach.
Page 13
Attach Procedure Trace (Cont.)
Page 14
The MME Sends an LA Update Req to the MSC
When receiving the

combined attach request,
the MME sends an LA

update message to the MSC.
Page 15
The MSC Answers the LA Update Resp to the MME

The MSC saves the MME information to forward downlink paging to the MME.
Page 16
Attach Accept Trace
After the combined location update, the UE saves the TA list, LAI, GUTI, and TMSI at the same time.
Page 17
UE-Initiated Detach Procedure

The UE deregisters from the EPC or CS network by using the detach procedure.
MME HSS MSC/VLR
UE 1. Detach Request
2. Step 2 to step 10 of the UE-initiated Detach procedure for E-UTRAN as specified in TS 23.401 3a. IMSI Detach Indication 3b. EPS Detach Indication 5. Detach Accept 4. Remove SGs association
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
6. Step 12 to step 14 of the UE-initiated Detach procedure for E-UTRAN as specified in TS 23.401
Page 18
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 19
EPS Detach Indication on the SGs Interface
The association between the MME and MSC is removed through this message.
Page 20
Detach Accept
Page 21
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 22
HSS-Initiated Detach Procedure

UE MME MSC/VLR HSS
When changing the subscription data, the HSS initiates a detach procedure.
1. Step 1a to step 7b of HSS-initiated detach as specified in TS 23.401 2. EPS Detach Indication 3. Remove SGs association 4. Step 8a to step 10a of HSS-initiated detach as specified in TS 23.401
Page 23
Combined TA/LA Update Procedure

UE 1. UE determines to perform TAU new MME old MME MSC/VLR HSS
2. TAU Request 3. Step 4 to step 19 of TAU procedure as specified in TS 23.401 4. Location Update Request
5. Location update in CS domain 6. Location Update Accept 7. TAU Accept 8. TAU Complete
Page 24
Contents
2. Key Procedures
Page 25
CSFB MO Call in Active Mode - PS HO Supported

UE/MS eNodeB BSS/RNS MME MSC SGSN Serving GW 1a. Extended Service Request 1b. S1-AP Message with CS Fallback indicator 2. Optional Measurement Report Solicitation 3. PS HO as specified in 23.401 [2] (preparation phase and start of execution phase) 4. CM Service Request 4. A/Iu-cs message (with CM Service Request)
Step 1-2 CSFB
1a.1b include CS fallback Indicator
Step 4-6 call service
5. CM Service Reject
5. CM Service Reject
If the MSC is changed
Location Area Update or Combined RA/LA Update 6. CS call establishment procedure
7. PS HO as specified in 23.401 [2] (continuation of execution phase)
Page 26
Extended Service Request (step1a)
The UE sends a CSFB indicator in

the extended service request.
Page 27
Initial Context Setup Req (step1b)

Instruct the eNodeB to execute CSFB
Page 28
Initial Context Setup Resp (step1b)
This message means eNodeB receive CSFB indicator.
The IE in this message is meaningless.
Page 29
CSFB MO Call in Active Mode - PS HO Supported (Step 23)
Handover preparation and start of handover execution is as follows:

UE Source eNodeB Target RNC Source MME Source Target Target SGSN Serving GW Serving GW PDN GW HSS
Uplink and DownlinkUser Plane PDUs 1. Handover Initiation
The eNodeB requests the UE to report the measurement result. The eNodeB selects the target cell.
3. Forward Relocation Request 4. Create Session Request
2. Handover Required
Handover preparation
4a. Create Session Response 5. RelocationRequest 5a. Relocation Request Acknowledge 6. Create Indirect Data Forwarding Tunnel Request 6a. Create Indirect Data Forwarding Tunnel Response 7. Forward Relocation Response 8. Create Indirect Data Forwarding Tunnel Request 8a. Create Indirect Data Forwarding Tunnel Response
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 30
CSFB MO Call in Active Mode - PS HO 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 31
Mobile Originating call in Active Mode PS HO Not Supported

UE/MS eNodeB BSS/RNS MME MSC S-GW SGSN 1a. Extended Service Request
Step 1-2 CSFB Step 3-5 RRC release
1b. S1-AP message with CS Fallback indicator 2. Optional Measurement Report Solicitation 3a. NACC, 3b. RRC connection release 4. S1-AP: S1 UE Context Release Request 5. S1 UE Context Release 6. LA Update or Combined RA/LA Update or RA Update or LA Update and RA Update 7a. Suspend (see 23.060) 7b. Suspend Request / Response
6. If the RA/LA changes, the location update procedure may be triggered.
Step 7 PS suspend
9. CS MO call
8. Update bearer(s)
10a. Service Reject
Step 9-10 call service
10b. Location Area Update 10c. CS MO call
In case MSC is changed
11. Routing Area Update or Combined RA/LA Update
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 32
Mobile Originating Call in Idle Mode
If the UE is in the idle state, the UE must change to the EMM-CONNECTED activation state before initiating a
call. The UE first sends a service request message to set

up an S1 connection.
After the UE is activated, the Mobile Originating call in
Active Mode procedure starts.
Page 33
Contents
2. Key Procedures
Page 34
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.
MSC Server 1
BSC/RNC 5
SGSN
SGs 2 MME
3 3 4 5 4 5 eNB
Page 35
Callee Service Procedure in the Connected State - Supporting PS Handover

UE/MS eNodeB BSS/RNS MME MSC 1a. Paging Request 1a. CS Paging Notification 1b. Extended Service Request 1a. Service Request 1c. CS Paging Reject 1d. S1-AP Message with CS Fallback indicator 2. Optional Measurement Report Solicitation 3. PS HO as specified in 23.401 [2] (preparation phase and start of execution phase) SGSN Serving GW
4a. Location Area Update or Combined RA/LA Update 4b. Paging Response 4b. A/Iu-cs message (with Paging Response) 5a. Establish CS connection 5b. Connection Reject
Option 1: MSC is not changed
The UE falls back to the CS
5b. Signalling Connection Release
5b. Location Area Update or Combined RA/LA Update 5b. CS call establishment procedure
6. PS HO as specified in 23.401 [2] (continuation of execution phase)
Page 36
Service Procedure of the Callee in the Connected State - Not Supporting the PS Handover
UE/MS eNodeB BSS/RNS MME MSC S-GW SGSN 1a. CS Paging Notification 1b. Extended Service Request 1a. Paging Request 1a. Service Request 1c. CS Paging Reject
1d. S1-AP message with CS Fallback indicator 2. Optional Measurement Report 3a. NACC, 3b. Signalling connection release 4. S1-AP: S1 UE Context Release Request
5. S1 UE Context Release 6. LA Update or Combined RA/LA Update or RA Update or LA Update and RA Update
Suspend the PS service
7a. Suspend (see TS 23.060) 7b. Suspend Request / Response 8. Update bearer(s) 9. Paging Response
9a. Establish CS connection Option 1: MSC is not changed Option 2: MSC is changed
9b. Signalling Connection Release
9b. Connection Reject
9c. Roaming Retry for CS Fallback (clause 7.5)
Page 37
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 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
Paging from MSC
Page 40
Paging from MME to eNodeB
The MME indicates that the subscriber is paged in the specified TA.
Page 41
Extended Service Req
Page 42
The MME Sends the Initial UE Context Setup Message
Page 43
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 44
CS Fallback MO SMS over SGs

MSC Server 4 BSC/RNC SGSN SGs 3 MME
12 12 5 5 eNB SAE-GW
Page 45
CS Fallback MO SMS over SGs
Page46
CS Fallback MT SMS over SGs

MSC Server 1 BSC/RNC SGSN SGs 25 MME
3 3 4 6 4 6 eNB SAE-GW
Page 47
CS Fallback MT SMS over SGs
Page48
System Implementation of the SMS
The following figure shows the system implementation of the SMS:
When the Short Message Service (SMS) is provided, the MME functions as an
intermediate forwarding node to forward the messages between the UE and the MSC. The MME 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 49
SM Procedure of the Caller in the Idle State

MS/UE MME MSC/VLR HLR/HSS SMSIWMSC SC
1. EPS/IMSI attach procedure 2. UE triggered Service Request 3. Uplink NAS Transport 4. Uplink Unitdata 5. Forward Short Message 4a. Downlink Unitdata 4a. Downlink NAS Transport 8. Delivery report 9. Downlink Unitdata 10. Downlink NAS Transport 11. Uplink NAS Transport 12. Uplink Unitdata 13. Release Request 6. Message transfer 7. Delivery report
Page 50
SM Procedure of the Caller in the Activated 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
state. 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 existing 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 the acknowledgement message in Step 11 in the preceding figure. This avoids reestablishment of the air interface and S1 interface connection after the air interface and S1 interface are released.
Page 51
SM Procedure of the Callee in the Idle State

SMSSMS GMSC
MS/UE
eNodeB
MME
MSC/VLR
HLR/HSS
SC
1. EPS/IMSI attach procedure
2. Message transfer 3. Send Routeing Info For Short Message 4. Forward Short Message
5. Paging 7. Paging 6. Paging
8. Service Request 9b. Downlink NAS Transport 9c. Uplink NAS Transport 10. Uplink NAS Transport
8a. Service Request 9a. Downlink Unitdata 9d. Uplink Unitdata 11. Uplink Unitdata 12. Delivery report 13. Delivery report
15. Downlink NAS Transport
14. Downlink Unitdata 16. Release Request
Page 52
SM Procedure of the Callee in the Connected 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 idle state. For the SM procedure of the callee in the activated state: - After receiving the SGsAP Paging Request message in Step 5 in the
preceding figure, the MME queries the UE context and knows that the current
UE is connected. The MME does not page the UE, namely, Step 6 to Step 8 in
the previous figure are skipped, and Step 8a is executed directly. The MME
sends an SGsAP Service Requestmessage to the MSC/VLR, indicating that
the NAS message can be transferred between the UE and the MME.
Page 53
Procedure of Multiple SMs of the Callee
Procedure of multiple SMs of the callee

When the MSC requires to send more than one SM to the UE, the MSC does not send the SGsAP Release Request message in Step
16 in the preceding figure. The MSC first sends an SGsAP Downlink

Unitdata message to transfer the new SM to the MME. This avoids re-paging of the UE after the air interface and S1 interface are released.
Page 54
Contents
1. Fundamentals
Page 55
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 56
Message Functions of SGs

Message Name Function
SGsAP-LOCATION-UPDATEREQUEST
SGsAP-EPS-DETACH-INDICATION message SGsAP-IMSI-DETACH-INDICATION SGsAP-SERVICE-REQUEST
Attach, Combined LA/TA: The MME sends a location update message to the MSC.
EPS detach. IMSI detach. SMT: The MME sends a service request as the response message of paging. Service indicator: CS call indicator or SMS indicator. MT: The MSC sends a Paging message to the MME. SMO: The MME sends an SM to the MSC. SMT: The MSC sends an SM to the MME.
SGsAP-PAGING-REQUEST SGsAP-UPLINK-UNITDATA SGsAP-DOWNLINK-UNITDATA
Page 57
Contents
1. Fundamentals
Page 58
7. CSFB Feature Related Configuration (1)
Operation procedure
- Run the ADD SCTPPARA command to add the SCTP parameter template of association
1. Establish inter-device communication between the MME and MSC:

path between the MME and MSC. - Run the ADD VLR command to add the SCTP association information from the MME to the specified MSC. - Run the DSP VLR command to query whether the SCTP association state between the MME 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 interface. Note: The CSFB feature requires license support. Run the DSP LICENSE command to view whether the current license supports the CSFB feature.
Page 59
Establish inter-device communication between the MME and MSC.
[USN MML]: Add the SCTP parameter template of association path between
the MME and MSC.
ADD SCTPPARA: SCTPPARAINDEX="SCTP Protocol Parameter Index";
[USN MML]: Add the SCTP association information from the MME to the
specified MSC.
ADD VLR: VLRNO = "VLR No.", IPTYPE = IPV4, VLRIPV4_1 = "VLR IPv4
Address 1", VLRIPV4_2 = "VLR IPv4 Address 2", SUBRACKNO =
"Subrack No.", SLOTNO = "Slot No.", LOCALIPV4_1 = "Local IPv4

Address 1", LOCALIPV4_2 = "Local IPv4 Address 2", SCTPINDX = "SCTP
Protocol Parameter Index";
[USN MML]: Query whether the SCTP association state between the MME and
MSC is normal.
DSP VLR: VLRNO = "VLR No.";
Page 60
Step 2 Activate the CSFB service.
Add LAs of MSC coverage.
[USN MML]: ADD LAIVLR: BGNLAI = "Beginning LAI",

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

ENDTAI = "End TAI", LAI = "LAI";
Page 61

Step 3 Set the service running parameters of the SGs interface.
[USN MML]: SET SGSPARA: TS6_1 = "Location Update Timer",
TS8 = "EPS Separation Timer", TS9 ="Display IMSI Separation

Timer", TS10="Implicit IMSI Separation Timer", NS8 = "EPS
Separation Retransmission Times", NS9 = "Display IMSI

Separation Retransmission Times", NS10 = "Implicit
IMSISeparation Retransmission Times";
Page 62
Contents
1. Fundamentals
Page 63
CS Fallback Deployment
MSC Pool Solution1: Depoly SGs MSC server per pool MSC Server Solution2: Upgrade all MSCs
Solution 1
Strengths
1.
2. Weaknesses
HSS
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.
MME Pool
The function of MSC pool must be supported. The function of MSC pool does not need support. 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.
Solution 2
Strengths Weaknesses
GW Pool
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. 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 64
Impact Factors of CSFB Performance
The TAI List of the LTE network is inconsistent with the LAC of the CS network. The location update procedure is added to the caller procedure. The roaming retry procedure is added to the callee procedure. The CSFB procedure latency is added.
The coverage scope of TA List covers LA 1 and LA 2.
TA1 TA1 TA6 TA2 TA4 TA3 TA2
MSC 1
BSC 1 BTS 1
TA3 TA6
LA 2
MSC 2
LA 1
LTE TA List
BTS 2
BSC 2
The UE is powered on at LA 1 and registered with MSC 1.
Location update is not initiated when the subscriber moves from LA 1 to LA 2.
When the UE initiates a caller service at LA 2, the location must be reupdated. MSC 2 is used to initiate the caller service.
Page 65
Impact Factors of the CSFB (Caller Procedure)

UE/MS eNodeB BSS/RNS MME MSC S-GW SGSN 1a. Extended Service Request 1b. S1-AP message with CS Fallback indicator 2. Optional Measurement Report Solicitation 3a. NACC, 3b. RRC connection release 4. S1-AP: S1 UE Context Release Request 5. S1 UE Context Release 6. LA Update or Combined RA/LA Update or RA Update or LA Update and RA Update 7a. Suspend (see 23.060) 7b. Suspend Request / Response 8. Update bearer(s)
The TA List is consistent with the LA planning. As a result, the LAU procedure is initiated after CSFB.
9. CS MO call
10a. Service Reject 10b. Location Area Update 10c. CS MO call

In case MSC is changed
11. Routing Area Update or Combined RA/LA Update
Page 66
Impact Factors of the CSFB (Callee Procedure)

GMSC HLR Old
VMSC/VLR
1
New
VMSC/VLR
2
SAE/LTE
MS
SRI (B, GMSC@,call Ref.,Roamingretry) PRN (call ref.,GMSC@, Roaming retry) PRN ACK (MSRN) SRI ACK Paging IAM (MSRN)
CSFallback
LocUpdate Authentication Procedure Update Location 3 Cancel Location Old MSC stops paging timer Cancel Location Ack and inform GMSC Insert Subscriber Data (multiple) RCH (call reference, roaming retry) REL RLCs
4 5
ACK
2nd SRI (B, basic call interrogation) HLR delays the sending of PRN until location update 6 procedure finishes
The TA List is consistent with the LA planning to avoid initiation of the roaming retry procedure after the CSFB
Insert Subscriber Data (continued) Update Location Ack PRN PRN ACK (MSRN) 2nd SRI ACK (MSRN)
7
Further procedures related to location update. e.g. ciphering, TMSI reallocation.
IAM (MSRN) New VMSC/VLR may delay setup until 8 location update procedure finishes LocUpdate Accept Cmplt TMSI
Normal MT call procedure follows.
Page 67
SMS over SGs Deployment

MSC MSC Server
MSC
MME Pool
HSS
GW Pool
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 68
Voice Solution to UE Settings
The UE, MSC, and MME jointly implement the CSFB function.
IMS PS Voice preferred
UE is set to IMS voice preferred, CS voice secondary
CS Voice preferred
UE initiates EPS attach procedure (non combined)
Fail or Success with SMS only indication or Success with CSFB Not Preferred indication
UE is set to CS Voice preferred, IMS PS Voice secondary
UE checks for IMS voice supported Indication from Network
Not supported
UE performs combined TAU for CSFB as in TS 23.272 Success with no SMS-only and no CSFB Not Preferred indication
Fail or Success with SMS only indication or Success with CSFB Not Preferred indication UE checks for IMS voice supported Indication from Network UE checks for voice centric or data centric setting
UE checks for voice centric or data centric setting
Voice centric
UE initiates a combined EPS/ IMSI attach procedure Success with no SMS only indication and no CSFB Not Preferred indication
Not supported
Voice centric
Supported TAU performed
Data centric
Supported TAU performed
Data centric
UE uses IMS Voice
UE uses CSFB
UE stays in current RAT
UE reselects to other RAT
UE uses CSFB
UE uses IMS Voice
UE stays in current RAT
UE reselects to other RAT
Reference from 3GPP TS 23.221 Annex A.2
Reference from 3GPP TS 23.221 Annex A.3
1. 2.
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 69
CS Fallback Latency Analysis

During the CS fallback procedure, the CSFB needs additional latency (that is, PS
HO/NACC/RRC Release)
UE/MS eNodeB BSS/RNS MME MSC SGSN Serving GW P-GW/ GGSN
The UE initiates a call
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 3c. Update Bearer(s) 4a. Location Area Update or Combined RA/LA Update 4b. CM Service Request 4b. A/Iu-cs message (with CM Service Request) 5. CM Service Reject 5. CM Service Reject
latency
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 70
CS Fallback Latency Analysis
CSFB to GERAN
Latency (ms) GERAN native 0 PS HO case 100 Plain RRC release 100 RRC release (SIB cache) 100
CSFB to UTRAN
RRC Latency (ms) UTRAN native PS HO case RRC Release Release (cached SIBs)
100
Idle to active (E-UTRAN) Extended service req. 0 150 150 150 Idle to active (EUTRAN) Extended service req. Measurement 1000 0 1000 1000 PS HO RRC release 2000-5000 2000-5000 2000-5000 2000-5000 Camp/Access in UTRAN UTRAN RRC connection setup NAS/E2E procedure (M-M) Total 3070-6070 2820-5820 4580-7580 2000-5000 2000-5000 2000-5000 750 0 750 0 0 0 320 320 250 0 0 0 0 50 1530 0 150 150 0 100 100
Measurement
PS HO RRC release
0
0 0 0
2640
250 0 0
0
0 50 2600
0
0 50 600
150
Camp/Access in GERAN GERAN RRC connection
0 0 50 250
setup
NAS/E2E procedure (M-M)

Total 3000-6000 4890-7890 5900-8900 3900-6900
750
2000-5000
3300-6300
Page 71
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 72
Comparison between the SRVCC and CSFB

Highlight Coverage SRVCC Supports LTE + IMS hot spot coverage and provides voice and data services.
Triggered when a subscriber moves from a location within the LTE coverage to a location within the 2G/3G coverage. Queries the DNS according to the Target ID. Target ID -> hostname -> IP SRVCC indicator
CSFB Provides PS services within the LTE coverage, and voice services within the 2G/3G coverage.
Triggered when the subscriber uses the CS service.
Trigger condition
The MME addresses the MSC.
Configures the MSC IP statically according to the Target TAI. Target TAI -> LAI -> VLR NO. -> MSC IP CSFB indicator
Voice indicator in the extended service request. Attach type UE settings
EPS attach SRVCC preferred
Combined IMSI/EPS attach CSFB preferred

Page 73
Comparison between the SRVCC and CSFB

Highlight Network deployment SRVCC Requires the IMS, and uses the IMS and CS to implement voice services. Upgrades the MME/E-MSC to support the Sv interface. CSFB Uses the CS to implement voice services. 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 74
Summary
1. Fundamentals
Page 75
Thank you
www.huawei.com

Oea100007 CSFB Solution Issue1.00

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Oea100007 CSFB Solution Issue1.00

Загружено:

Авторское право:

Доступные форматы

CSFB Solution

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

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

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

After learning this course, you can:

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

4. Feature Data Configuration 5. Network Deployment

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

Origin of the CS Fallback Solution

completes the Circuit Switched domain (CS) service.

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

S1-C S1-U eNB

directly through the LTE NA signaling on the EPC network. This

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

Features of the CSFB Solution

The UE supports both the CS service and PS service.

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

4. Feature Data Configuration 5. Network Deployment

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

MME 1. Attach Request

Combined EPS/IMSI Attach UE is capable to use CSFB

2. Step 3 to step 16 of the Attach procedure specified in TS 23.401

3. Derive VLR number 4. Location Update Request

TAI -> LAI -> VLR NO.

Create SGs association

5. Create SGs association

6. Location update in CS domain

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

Attach Procedure Trace

After "CSFB prefer"

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 the MSC

When receiving the

the MME sends an LA

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

The MSC Answers the LA Update Resp to the MME

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

Attach Accept Trace

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

UE-Initiated Detach Procedure

UE-initiated detach procedure MME-initiated detach procedure HSS-initiated detach procedure

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

Detach Request from UE

Type of detach (In the UE to network direction):

(1) EPS detach

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

EPS Detach Indication on the SGs Interface

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

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

MME-Initiated Detach Procedure

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

HSS-Initiated Detach Procedure

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