IMS For LTE

1
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
This package contains slides from
many, many contributors including:
BRIGANT, Eric
BROUWER, Wim
CARSON, Chris
FAGGION, Nadège
LICHTER, Joe
SACHDEV, Vineet
URIE, Alistair
YU, Jim
You, of course, get credit for

delivering it. Add your name in place
of “Speaker Name” and delete this
whole note. 
Voice and SMS in LTE

Technical Overview
Speaker Name
Date

AGENDA You will have to modify the agenda
based on the sections you include in
your talk
1. Introduction
2. Solution Architecture Overview
3. End-User Services
4. Regulatory Services
5. Provisioning / migrating subscribers
6. Roadmap
7. Supporting Sections
3
1. Introduction

Voice in LTE
Introduction
• Initial LTE deployments were focused on data services
- However, carriers are quickly expanding to voice services as well
• In an attempt to ease introduction of voice in LTE, phased approaches are available:
Circuit-Switched Fallback (CSFB) Dual-Transceiver Handsets (SVLTE)
• This method drops the UE from LTE to • Approach requiring specialized handsets
CDMA 1x any time a voice all is active has traction among CDMA operators
IMS with GSMA VoLTE
• This is the widely accepted

target architecture for voice in LTE
• Note there are other niche approaches that a small set of vendors and service providers are
pursuing:
- Use SIP UE with proprietary enhancements to MSC
- This method enhances an existing MSC with a SIP Gm interface (i.e. NSN ―FastTrack‖)
- These approaches have limited traction in the market place. The supporting ecosystem is uncertain.
5
Market and network trends impacting voice
solution for LTE
• Voice remains important but no longer is the dominant service in terms of radio
network load
- Market will however split between ―legacy‖ and ―rich‖ services
- Some operators targeting ―rich‖ services only for power users with others planning to generalize
―rich‖ services to all users
- ―Legacy‖ services expected to remain the only option for legacy terminals
• LTE rollout will be similar to 3G
- Gradual increase in covered area across network
- Some operators targeting LTE coverage to exceed 3G deployment
- Others planning to always have wider 3G coverage than LTE
- May also depend on frequency bands allocated for LTE - i.e., higher bands may result in coverage
holes indoors etc.
- Support for users roaming onto networks without LTE coverage will remain key requirement
for at least 10 years
• SMS solution typically required from day 1
- Data only terminals MAY be an exception depending on configuration update mechanism
6
Assumed requirements for Voice and SMS over LTE
capable terminals
• Services
- Voice service continuity to be ensured during handover to CDMA access
- Solution to support handover from CDMA to LTE requires standardization when, and if, agreed
technical solution and need has been determined
- Voice service may be controlled using IMS servers and applications

- Including when in CDMA circuit mode
- Voice service to be available while roaming on other LTE networks

- Independent of preferred voice solution of visited network
• Network
- Voice specific functionality in E-UTRAN and EPC to be minimized
- Header compression (RoHC) and Semi-Persistent Scheduling in E-UTRAN
- Possibly CSFB and/or SRVCC support in MME
- Possibly CSFB and/or SRVCC support in MSCs
- No additional requirements imposed on roaming partner networks

7
Options for Supporting Voice and SMS with LTE
There are three options we can discuss for voice/SMS services with LTE:
Option Description Comment
Attractive as a means of re-using all

UE is registered in LTE and is paged
CS Fall-back the CS infrastructure. Note this
over LTE but takes call in CDMA
(CSFB) option precludes simultaneous LTE
Circuit mode
data and voice (different carriers)
Simultaneous UE maintains simultaneous Offered in the UE at the expense of

Voice and LTE registration on LTE network for data greater complexity and shorter
(SVLTE) and legacy network for voice/SMS battery life.
Uses a standard 3GPP IMS and LTE Call control for native LTE voice and
features to improve voice capacity SMS service is provided by IMS. IMS-
Continuity Options: based call control can be provided in
Voice over LTE the CDMA domain via the IMS
(VoLTE) • Hand-down to CDMA circuit
anchoring for calls originated in
domain
CDMA circuit mode.
• LTE <-> eHRPD PS HO required if
VoIP over eHRPD is supported
8
Voice with LTE and CDMA Networks
Standards
• VoLTE Standards span 3GPP R8 (2008) to current release
- All variants of CDMA (1x, 1x Advanced, EVDO Rev A, Multi-Carrier EVDO and DO
Advanced) have been enhanced to allow delivery of voice in a mixed LTE/CDMA
network including options for 1x CSFB, 1x SRVCC, 1x DRVCC, and VoIP handover
via eHRPD PSHO.
• Alcatel-Lucent is a very active participant in 3GPP and 3GPP2. 3GPP2
references include
- C.S0087: E-UTRAN – cdma2000 HRPD Connectivity and Inter-working Air Interface
- C.S0097: E-UTRAN – cdma2000 1x Connectivity and Interworking Air Interface
- A.S0022: IOS for eHRPD RAN Interfaces and Interworking with E-UTRAN
- X.S0042: Voice Call Continuity Between IMS and Circuit Switched Systems
- X.S0057: E-UTRAN – eHRPD Connectivity and Interworking: Core Network Aspects
9
GSMA VoLTE (formerly referred to as OneVoice)
• GSM Association (GSMA) sponsored IR.92 profile is an industry effort to

ease the introduction of VoLTE/VoIMS via specification of critical inter-
working requirements between UE and network vendors
- Work initiated within standalone "One Voice" forum and transferred to GSMA
IREG RiLTE in early 2010
• Alcatel-Lucent was one of the original members of the One Voice forum
and is an active participant within RiLTE working group managing this
profile
• We have completed an end-to-end evaluation of the GSMA VoLTE IR.92
Profile v2.0 specification across the ALU portfolio and ALU LTE Solution is
currently ready for initial UE interoperability testing of this profile
• ALU is committed to supporting GSMA VoLTE IR.92 profile and IR.88
10
Primary Migration strategies for Voice and SMS
services: Industry Trends
Initial LTE launch Service Rollout Mass market Network optimization
Data modems only. Including smartphones; earliest Full range of terminals; earliest Full range of terminals
test 2H2011; deploy 1H2012 2013+
Deploy 1H2011 test 1H2011; deploy 2H2011
Option for data only devices
LTE only Data LTE and eHRPD LTE and eHRPD LTE and eHRPD
only devices Data only devices Data only devices Data only devices
VoLTE with IMS VoLTE IMS VoLTE

(complete LTE (complete LTE
DRVCC SRVCC coverage) coverage)
IMS VoLTE/VoIP IMS VoLTE/VoIP

SVLTE over eHRPD over eHRPD
LTE with Dual Tx IMS VoLTE with IMS VoLTE with

CSFB S102 SRVCC CDMA S102 SRVCC CDMA
IP-Optimized
solution
Voice and SMS via

IP+Circuit S102 CSFB
solution
11
2a. Solution Architecture Overview:
Circuit-Switched Fallback

CS Fallback
and SMS over S102
• Approach
- Voice call setup (either mobile originated or incoming page) triggers UE move from LTE to
1x to then support voice over CS
- SMS delivery over LTE using S102 interface
• Handover
- LTE->1x: Data session suspended during voice call
• Key elements
- Upgrade to MME, E-UTRAN and all MSCs (or installation of IWS) for S102 interface in LTE
coverage area
- Only selected MSC need be upgraded if only used for SMS over S102, e.g., for SMS to data-only
endpoints
- CSFB client in terminal
• Target usage
- Operators with embedded 1x network building LTE overlay, or
CS Fallback and SMS over
- Operators building LTE network and choosing SMS over S102 S102 are both defined in
3GPP TS 23.272. + 3GPP2
C.S0097
13
CS Fallback - High Level Architecture
MSC MSC
CDMA 1X CDMA 1x
CS Network CS Network
New interface
“S102” from MSC
to MME
E-UTRAN MME E-UTRAN MME
PDN PDN
SGW PGW SGW PGW

eNode B Data eNode B
Circuit Voice
Paging/SMS Data
While carrying data only No Simultaneous Voice + Data
- Handset uses LTE network where - Handset falls back to legacy circuit
possible to achieve highest throughput coverage for voice
- Handset served by an MSC in legacy - Data sessions suspended
network for voice and SMS
CSFB Tradeoff
- Incoming voice calls paged over S102
interface from MSC to MME, similar to Gs - Re-uses legacy circuit infrastructure
interface in GPRS
- But at the cost of Inter-RAT handover per
- SMS delivered over S102 – without voice call, and suspended data sessions
requiring inter-RAT handover
14
CS Fallback: Roaming Considerations
• If a UE requires CSFB and CSFB is Figure A.5-1 from 3GPP TS 23.221:

UE behavior for CS Voice only
available in a visited network,
roaming voice service operates in
the visited network with the same
UE is set to CS
Voice only
restrictions as in today‘s roaming Fail or Success with

“SMS only” indication
environment. or Success with
“CSFB Not Preferred”
indication
• If a UE requires CSFB and CSFB is UE initiates a
combined EPS/
UE checks for
not available in a visited network, IMSI attach
procedure
voice centric or
data centric setting Voice centric
the UE will disable E-UTRAN Success with no
capability and select a CDMA “SMS-only” indication

and no “CSFB Not Data centric
network
Preferred” indication
• Further details can be found in UE uses CSFB UE stays in current

RAT
UE reselects to
other RAT
3GPP TS 23.221 Annex A
15
CS Fallback
Benefits, Costs, and Limitations
• Benefits • Limitations
• Provides mechanism for basic, transparent • CSFB procedures in eUTRAN require per-call
voice service to LTE handsets migration to CDMA
- Applicable to voice handsets if LTE is - Increases call setup delay
deployed in advance of IMS
- Range of figures depending on network
- Applicable to LTE roamers whose home conditions
network is not IMS capable
- Does not require IMS client in UE
• Can be used to provide ―basic‖ voice service
to certain users in networks where IMS
voice is available as a premium service
• Costs
• Requires support of S102 interface on MME
and MSCs
- S102 required on only a subset of MSCs if
only SMS delivery (not CSFB) is required
16
2b. Solution Architecture Overview:
Simultaneous Voice and LTE (SVLTE)

Simultaneous (Circuit) Voice and LTE (SVLTE)
MSC
CDMA 1x
BTS CS Network
E-UTRAN MME
PDN Circuit Voice

SGW PGW Data
eNode B
• SVLTE
• ―Two phones in one‖ to re-use legacy voice capabilities while offering LTE for data
• Particularly attractive to CDMA-2000 operators as it provides data connectivity during voice
calls
• SVLTE is not defined in standards
- It is a handset ecosystem marketing term
- No hard-and-fast rules on network or handset impact
- To date Alcatel-Lucent has done IOT only with LTE / CDMA 1x handsets: No network impact
• SVLTE is not known to have traction among 3GPP operators
- UMTS offers simultaneous voice and data already
18
Device Options – Two Example Device Solutions
• Qualcomm‘s SVLTE/SVDO – Qualcomm Simultaneous V&D
- Enables Dual Transceiver Devices capable of
- Simultaneous 1x Voice with LTE Data, and
Rx/Tx Rx/Tx
- Simultaneous 1x Voice with eHRPD (EV-DO) Data
- Qualcomm 2-chip initial solution: ―Fusion‖ DO/
1x
LTE
- MDM9600 supporting LTE and EV-DO (eHRPD) data
- MSM8655 supporting 1x Voice and Smartphone operating system
- Devices would have one transceiver for Voice, and one serving LTE and EV-DO
- Qualcomm planning single-chip SVLTE/SVDO follow on solution
• ―CSFB‖ Dual Receiver for LTE data and 1x CS Voice

Rx Tx Rx
- Standards-based device with separate receiver for LTE and CDMA
1x /
- The device shown at right has a single Tx, but Separate receivers LTE
DO
for LTE and eHRPD
- A Dual Tx device may be capable of simultaneous 1x Voice with LTE Data
19
2c. Solution Architecture Overview:
Voice over LTE

VoLTE
Required Solution Enhancements
• Approach:
- Provide voice to LTE UEs using IMS to provide the voice services
• Key elements:
- LTE E-UTRAN enhanced for VoIP delivery
- IMS core with Telephony Application Server (TAS) to provide end-user services
- VCC to provide handover capabilities between different radio domains (i.e.,
packet and circuit)
• The next slides will explore each of these areas in more detail
21
VoLTE
Alcatel-Lucent Products
CDMA 1X 8615 IeCCF
8610 ICC 5110 SMS C
1357 ULIS
BTS MSC
PSTN/PLMN VitalQIP
Elements
added for IMS
eHRPD
eHRPD
BTS HSGW
eRNC
7510 MG
5420 PCM
5060 MGC-8
IMS Core
5420 CTS
(TAS)
E-UTRAN
5780 DSC 8650 SDM
9471 MME
Enhanced Packet Core

(Voice + Data) 5450 ISC 5900 MRF
5420 SCG
94xx eNB
7750 SGW
7750 PGW
22
VoLTE Required LTE E-UTRAN Enhancements for
VoIP Delivery
• Header compression using Robust Header Compression (RoHC)
- Reduced overhead but robust to consecutive packet errors.
• Delay management for VoIP QoS control
- QoS policy enforcement through Priority management
- Air interface resource management for VoIP QoS control
- Bearer QoS with DSCP marking in backhaul
- Smaller scheduling interval (TTI = 1ms)
• Semi-persistent scheduling for VoIP
- Reduce scheduling overhead
• Short PDCP sequence number to reduce the packet overhead.
• RLC UM (RLC Unacknowledged Mode, no retransmission)
- Reduce the delay and jitter of VoIP packets.
23
IMS core with Telephony Application Server (TAS)
• The IMS core and TAS adds the following components:
- Session manager consisting of P-CSCF, S-CSCF, I-CSCF, and BGCF, provided by the 5450 ISC
- TAS to provide the voice services - uses 5420 CTS
- SCC AS providing service centralization and VCC – provided by 5420 SCG
- Web portal to support subscriber feature configuration such as call forwarding – uses 5420
PCM
- MGCF and MGW to provide connectivity to the PSTN
- These functions are provided by the 5020/5060 MGC-8 and the 7510 MG respectively
- Media resource function to support functions such as announcements and conferencing
capabilities - provided by the 5900 MRF
- DNS/ENUM server to resolve IP addresses and E.164 addresses
- This function is provided by VitalQIP. Note this function could be shared with the DNS function
already in the LTE network
• The IMS core and TAS also leverage the following entities from LTE:
- Home Subscriber System for subscriber data (8650 SDM)
- Offline charging function (8615 IeCCF)
- Online charging function (8610 ICC)
- Lawful intercept gateway (1357 ULIS)
24
VoLTE – user plane aspects
Two party calls
LTE to LTE call
MSC • VoLTE to VoLTE call
CDMA
- Each UE has dedicated signaling connection to
own S-SCCF and TAS (may be shared)
HSGW - Direct packet voice connection between two
parties, routed via own PGW (may be shared)
E-UTRAN MME IMS
SCC AS TAS
- Each UE has dedicated QCI=1 bearer established for
PDN voice service
SGW PGW - If UE not on same network then user plane carried
eNode B over inter-operator interconnection (normally via
GSMA sponsored IPX)
• VoLTE to CS call
VoLTE to mobile CS - LTE connected UE has dedicated signaling
MSC
connection to own S-CSCF and TAS
CDMA
CS Network - CS connected UE has dedicated signaling
connection to MSC
- During call MSC and IMS linked together using
HSGW MGW
MGCF ISUP via MGCF (or using SIP if MSC supports IP)
E-UTRAN MME SCC
IMS TAS - Media path connected via MGW under control of
MGCF
PDN
- LTE connected UE has dedicated QCI=1 bearer
eNode B
SGW PGW established for voice service
Circuit Voice Circuit signaling Packet Voice IMS Signaling Packet Data
25
VoLTE – user plane aspects
Multi-party calls
LTE to LTE conference call
• VoLTE to VoLTE conference call
MSC
CDMA CS Network - Each UE has dedicated signaling connection to
own S-SCCF and TAS (may be shared)
- Media path from each UE directed to conference
HSGW bridge hosted by MRF (Media Resource Function)
E-UTRAN MME IMS
SCC AS TAS - Each UE has dedicated QCI=1 bearer established for
+ voice service
PDN
MRF
eNode B
SGW PGW
• VoLTE to CS call
- Each UE has dedicated signaling connection to
LTE to LTE call with 3rd party on hold own S-SCCF and TAS (may be shared)
MSC - Direct packet voice connection between two
CDMA
CS Network
active parties, routed via own PGW (may be
shared)
- Each active UE has dedicated QCI=1 bearer
established for voice service
HSGW
- Media path for held UE directed to
MME IMS TAS
E-UTRAN SCC AS announcement service hosted by MRF (Media
PDN
Resource Function)
MRF
- Held UE has dedicated QCI=1 bearer established for
SGW PGW voice service
eNode B
26
VoLTE – Hand down to 3G network
• Voice Call Continuity is used to provide session continuity from LTE to

CDMA for voice calls
• Two options exist:
- Handover while remaining in packet (PS)
- Handover from LTE to 3G eHRPD can be done without the need for SRVCC
- Handover to circuit (CS)
- SRVCC requires UE and network functionality along with bearer path reconfiguration by
SCC AS
- Alternatively UE based dual transceiver solution can be used with SCC AS bearer
reconfiguration to provide hand down.
• When handing over to CDMA, PS data services are suspended
• Note that CS handover from CDMA to LTE is not defined in the standards
- UE needs to wait for call using CS bearer to end before reselecting LTE cell
- ―Reverse‖ SRVCC now being worked in standards
27
VoLTE handover to legacy mobile network
Using PS handover (towards eHRPD only)
Before…
MSC
• Approach
CDMA
CS Network
MGW
- Simple PS handover triggered by
HSGW
MGCF
IMS TAS
MME involving HSGW and S/PGW
E-UTRAN MME SCC
PDN • Service restrictions

SGW PGW
eNode B
- Full IMS services maintained during
handover and remainder of call
… after - Gm signaling interface available
MSC
CDMA
CS Network
- PS Voice bearer support required
- VoIMS is not viable over 1x
HSGW MGW
MGCF
E-UTRAN MME SCC
IMS TAS
PDN
SGW PGW
eNode B
28
Using SRVCC (―B‖ party in CS network)
MSC Before…
CDMA
CS Network
• Approach
- SRVCC mechanism triggered by MME,
HSGW MGW
MGCF involving MSC and SCC
E-UTRAN MME IMS
SCC
PDN
TAS
- Parallel PS handover used for data
services
SGW PGW
eNode B
• Service restrictions
… after - (Most) IMS services maintained during
CDMA
MSC handover and remainder of call
CS Network
- Available over all mobile networks with
SRVCC roaming agreements
HSGW MGW
MME
MGCF
IMS
- Requires SRVCC support in visited network
E-UTRAN SCC
TAS
PDN
SGW PGW
eNode B
Figures are simplified
29
Using SRVCC (―B‖ party in LTE)
MSC Before…
CDMA
CS Network
• Approach
HSGW MGW
MGCF - SRVCC mechanism triggered by MME,
E-UTRAN MME SCC
IMS
TAS
involving MSC and SCC
PDN
- Parallel PS handover used for data
eNode B
SGW PGW
services
… after
MSC - (Most) IMS services maintained during
CDMA
CS Network handover and remainder of call
- Available over all mobile networks with
HSGW MGW SRVCC roaming agreements
MGCF
E-UTRAN MME IMS
SCC
TAS - Requires SRVCC support in visited network
PDN
SGW PGW
eNode B
30
Using DRVCC (―B‖ party in CS network) – No S102
MSC Before…
CDMA
• Approach
CS Network
HSGW MGW
- DRVCC mechanism triggered by UE,
E-UTRAN MME
MGCF
SCC
IMS UE initiated new HO leg in CDMA
TAS
PDN - Parallel PS handover used for data
eNode B
SGW PGW
services
… after
CDMA
MSC - (Most) IMS services maintained
CS Network
during handover and remainder of
call
HSGW MGW
E-UTRAN MME
MGCF
SCC
IMS - Available over all mobile networks
TAS
PDN
SGW PGW
eNode B
31
VoLTE and CDMA Integration Implementation Options

VoLTE with CDMA Circuit
Routing Through IMS
• Calls are routed through the IMS to fulfill a variety of requirements – not
all requirements apply to all solutions.
- Domain Selection - Incoming calls to UE with combined VoLTE/Circuit solutions
must be routed to the appropriate domain. This is usually achieved via VCC
application server on the IMS
- Domain Transfer - Hand down from VoIP to Circuit is controlled by the VCC
application server on the IMS
- IMS Based Services – Those calls on which IMS based services are desired
(including calls in the CDMA network) must be routed through the IMS and TAS
for services control. Some next generation services examples include:
- Simultaneous ringing of desk, cellular, home phones
- Time of day routing to desk, cellular, home
- Call logging and account codes
- Powerful call blocking
- Enterprise extension dialing
- etc.
33
VoLTE with CDMA Circuit
Supplementary Services
• Supplementary Services provisioning and status are sync‘ed between the

IMS and CDMA networks – to a greater or lesser degree
• Supplementary Services are categorized into groups as follows
- Static (not changeable by the end user) Services such as caller ID presentation
and restriction must be consistently configured on both the IMS (TAS) and CDMA
(HLR) initially.
- Semi-static (changed by the end user and remain in that state until changed
back by the end user e.g., temporarily persistent status) such as CW Disable, ID
Privacy, Call Forwarding, Call Blocking. These services are further categorized
based on application to incoming or outgoing calls – of those listed ID Privacy is
the only service that applies to outgoing calls. The service activation data for
this category of services may require special handling
- Per call service activation such as Cancel Call Waiting (for this call only). These
services are provided by the serving system (IMS or CDMA)
- Mid call services such as Three Way Calling, Call Hold, Call Transfer, Accept
Waiting Call. These services are provided by the serving system (IMS or CDMA)
34
Service Delivery Options –
IMS Service Delivery in LTE (Baseline)
UE Initiates call using SIP signaling
TAS applies originating features
Call routed to B-party
IP Bearer is set up
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN
PCRF HSS/HLR
MME

(Voice + Data) CSCF MRF
eNode B
SGW
PGW
Packet Voice IMS Signaling
35
IMS Service Delivery in LTE to PSTN
Call routed to MGCF (B-party in PSTN)
MGCF signals PSTN
PSTN/PLMN
MGCF instructs MGW to set up PSTN connection
IP Bearer is set up
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN
PCRF HSS/HLR
MME

eNode B
SGW
PGW
36
IMS Service Delivery - Attributes
• Features provided by IMS & TAS
• Simultaneous LTE voice and data supported
• Call Flow supports LTE to CDMA Hand-down (SRVCC or DRVCC)
37
IMS Service Delivery in eHRPD Gm Method with eHRPD Bearer

MGCF signals PSTN
MSC
PSTN/PLMN MGCF instructs MGW to set up PSTN connection
IP Bearer is set up
eHRPD
Core
BTS HSGW
eRNC
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR

eNode B
SGW
PGW
38
IMS Service Delivery in eHRPD - Attributes
• Features provided by IMS & TAS
• Requires ―optimized‖ PS-PS Handover support
- Supports handover in both directions
• Simultaneous voice and data supported
• Well suited to handle ―small coverage holes‖ in LTE layer
• Avoids need for SRVCC or DRVCC as long as eHRPD is available
• Better quality (PS HO to eHRPD)
• This option is attractive for service providers that have a large embedded
base of eHRPD voice-enabled packet networks
39
IMS Anchored Solution for calls in CDMA
• Standard solution as described in 3GPP2 X.S0042-A – Voice Call Continuity
between IMS and Circuit Switched Systems
• In general, the solution is designed to anchor all voice calls through the
IMS and IMS application servers. This is intended to provide IMS Next Gen
Services to the subscribers both when in IMS and when in CDMA circuit.
• Anchoring Options
- For incoming calls this can be achieved in several ways
- Terminating Triggers at the Home MSC. In this case, it is possible to use multiple
terminating triggers at the Home MSC to support both legacy network incoming call
services and IMS anchoring
- Assigning an IMS number or porting the existing number to IMS
- Modification of the HLR to support forced routing to IMS at LOCREQ
- For originations in the CDMA network, this is achieved via (WIN or pre-WIN)
Originating Triggers. This may be problematic when the user is roaming outside
the service provider coverage depending on trigger support from roaming
partners.
40
Anchoring Options at the VCC Anchoring Function
• 5420 SCG receives the Invoke and responds with the Return Result for the
cases below.
• Origination anchoring
- OriginationRequest: ANSI-41D (pre-WIN)
- OriginationRequest: ―Origination Attempt Authorized‖
- OriginationRequest: ―All Calls‖
• Termination anchoring
- New assigned directory number in IMS number range
- Re-use of an existing number
- number portability or
- AnalyzedInformation: Initial Termination at Home MSC or
- AnalyzedInformation: Advanced Termination Trigger at Home MSC
• Support of multiple trigger options allows some services (e.g., CRBT) to

continue to be offered in the Home MSC/WIN SCP if desired.
41
Limited IMS Service Delivery in CDMA: WIN Anchoring Originating Call
UE Initiates call to MSC
MSC has originating attempt trigger for UE pointing to
SCC AS. Sends trigger with dialed digits.
SCC AS saves dialed digits and returns PSI DN
CDMA MSC initiates call to PSI DN
MGCF sets up incoming circuit bearer
MGCF routes call to SCC AS
SCC AS sends INVITE to TAS with saved dialed digits
BTS MSC
PSTN/PLMN
MGCF signals PSTN
MGCF instructs MGW to set up PSTN connection
eHRPD
eHRPD
BTS HSGW
RNC
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR
Enhanced Packet Core CSCF

(Voice + Data) SCC AS MRF
eNode B
SGW
PGW
42
Limited IMS Service Delivery in CDMA: WIN Origination Anchoring
• Features initiated in origination dial string (e.g., CCW, extension dialing)

from IMS TAS
• Mid-call features (e.g., 3WC) from MSC
• Some services limit handover (e.g. conferencing)
• SCC AS with WIN support required to anchor call in IMS
• No impact on MSC (beyond support of WIN triggers)
• HLR provisioning of WIN triggers and appropriate end user services
• This may be attractive to service providers for early introductions
• May be an issue with origination trigger support when UE is roaming in
CDMA partner network
43
Local Service Delivery in CDMA: MSC Provides Services
UE Initiates call to B-party
MSC routes call to B-party
Circuit bearer is completed
MSC
PSTN/PLMN
CDMA
eHRPD
HSGW
BTS RND
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR

(Voice + Data) CSCF SCC AS MRF
eNode B
SGW
PGW
44
Local Service Delivery in CDMA: MSC Provides Services – Attributes
• All features from CDMA MSC while in CDMA Mode

• No handover support from or to LTE
• Need a mechanism to allow user in CDMA to activate services at the TAS
• No impact on MSC
• This option is primarily useful for LTE subscribers roaming into another
service provider‘s network
45
WIN Anchoring for Incoming Calls Call initiated to UE at Home MSC
H-MSC sends triggered message to SCC AS
PSTN/PLMN which saves call info and returns a PSI DN
MSC sets up a call to PSI DN
MGCF sets up incoming circuit bearer
MGCF routes call to SCC AS
SCC AS sends INVITE to TAS with
H-MSC saved dialed digits
TAS applies terminating features
Call is routed back to SCC AS for domain
selection
CDMA
MSC
BTS
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR

eNode B
SGW
PGW
46
Domain Selection to CDMA
Call routed into IMS and to TAS
PSTN/PLMN
Call is routed to SCC AS for domain
selection
SCC AS does not find UE registered in IMS and
queries the HLR for routing digits
HLR returns routing digits
H-MSC
Call routed through MGCF to routing
destination
Call delivered to UE
CDMA
MSC
BTS
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR

eNode B
SGW
PGW
47
Domain Selection to LTE
Call routed into IMS and to TAS
PSTN/PLMN
Call is routed to SCC AS for domain
selection
SCC AS does find UE registered in IMS and
routes the call through the S-CSCF
S-CSCF routes call to UE Contact Address
H-MSC
Bearer path is allocated and connected
Call delivered to UE
CDMA
MSC
BTS
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR

eNode B
SGW
PGW
48
Limited IMS Service Delivery in CDMA: WIN Termination Anchoring
• This is attractive when existing CDMA customers (DNs) are migrated to
VoLTE with CDMA
• Incoming Call Features (e.g., CF, Call Blocking, TOD routing, etc. ) from
IMS TAS
- Possible to provide some services (e.g., CRBT) at the Home MSC if that is desired
• Mid-call features (e.g., 3WC) from MSC
• Some services limit handover (e.g. conferencing)
• SCC AS with WIN support required to anchor call in IMS
• No impact on MSC (beyond support of WIN triggers)
• HLR provisioning of WIN triggers and appropriate end user services
• No issue with trigger support while CDMA roaming as all incoming calls
route through the Home MSC in the HPLMN
49
Basic VoLTE and CDMA Option
• Originations on CDMA network are NOT anchored through IMS
- It may be difficult or expensive to support anchoring of CDMA originations
through the IMS especially in the case of roaming in another CDMA network.
Thus Local Service Delivery at the Serving CDMA MSC provides the same solution
in both the home and visited CDMA networks.
• Incoming calls are routed through the IMS via following
- New assigned directory number in IMS number range or re-use of an existing
CDMA number via porting number to IMS or WIN triggers at the Home MSC
• Domain Transfer (SRVCC or DRVCC) supported for VoLTE to CDMA
• Services are provided by the serving network for originations and by the
IMS for terminations
- Incoming call semi-static feature activations (e.g., CF) at the IMS TAS via web
browser interface from smart phone or PC.
- Assume CW Disable (temporarily persistent) not supported
- Multi-party or held calls in the IMS are not controllable by the UE after VoLTE to
CDMA domain transfer (hand down).
50
Enhancements to Basic VoLTE and CDMA Option
• Add support for anchoring CDMA originations through IMS

- Gain the ability to offer TAS based enhanced or Next Generation services such as
extension dialing, call logging, consistently regardless of access network (LTE or
CDMA).
- Feature activation codes can be supported for semi-static feature changes since
the feature activation
• Add support for Ut interface in the TAS and UE
- Add the capability for the UE to determine the need for and automatically
perform feature activation via XML data interface (Ut) to the TAS perhaps via
features management GUI on the device
51
Roaming Impacts
• CDMA Roaming for VoLTE/CDMA users

- As discussed elsewhere, support of origination call triggers in a roaming partner
network may be problematic
- Similarly, support of S102 for SRVCC hand down to CDMA may not be supported
in all CDMA networks.
• LTE Roaming for VoLTE users
- GSMA specifies an architecture that provides for local breakout from the PGW to
a P-CSCF in the VPLMN and the reminder of the IMS in the Home PLMN (LBO to
Home IMS).
- Business issues such as charging and routing determination require additional
features currently targeted for Release 11. If the roaming partners agree that
those business issues can be avoided it may be possible to support VoLTE
roaming prior to Release 11.
52
VoLTE Handoff Options

VoLTE Handoff Options
Network
Approach Destination Enhancemen Device Availability
t Required?
Non-Optimized Dual Receiver or
eHRPD
eHRPD VoIP None Today
Dual Radio *
Single or Dual
Optimized eHRPD eHRPD VoIP S101 Radio Future
C.S0087 Tunnel
VCC App
1x DRVCC 1x CS Dual Radio Future
Server
Single Radio
1x SRVCC 1x CS S102 Future
C.S0097 Tunnel
* Non-Optimized eHRPD HO supports Single or Dual Radio devices. However, for

VoLTE HO, separate receivers for LTE and eHRPD may improve handoff delay.
54
VoLTE Handoff
• When VoLTE is used, a solution is required for dealing with mobility outside of an
area with LTE coverage, to provide voice call continuity
• Non-Optimized eHRPD – Upon reaching the edge of LTE coverage, a non-
optimized handover is executed without S101.
- Delay can be prohibitive, but studies are underway to improve performance to where it might
be acceptable for voice calls.
• Optimized eHRPD – Upon reaching edge of LTE coverage, an optimized handover
using S101 is executed. The call remains in the packet domain on eHRPD.
• 1x DRVCC – Similar to SRVCC, but device controls call establishment over 1x, no
need for S102 interface or GCSNA layer. Upon reaching edge of LTE coverage, UE
initiates 1x call setup while maintaining VoIP call leg. After 1x call is answered, UE
switches to circuit mode and UE is handed off to 1x. VCC App Server required.
- Partially standardized in X.S0042 as ―Dual Radio Domain Transfer.‖
• 1x SRVCC – Upon reaching the edge of LTE coverage, the 1x call is set up over the
S102 tunnel and then the UE handed over to 1x.
55
Interworking LTE with EV-DO via eHRPD SW upgrade on
(Optimized) existing equipment

Potential future SW
upgrade on existing
equipment
1xEV-DO
Packet
RNC / eRNC
Switched Core
(HRPD and eHRPD) Legacy EV-DO AT
PDSN HA
3GPP2 AAA
LTE-eHRPD
eHRPD IMS
HS GW
BTS Internet / Intranet
With addition of “Optimized Handoff” with
S101 signaling for pre-registration and handoff, S103
and S103 for data forwarding, S101
LTE handoff performance improves
3GPP PCRF HSS
LTE UE MME
Evolved Packet Core

SGW PDN
GW
eNode B
56
LTE VoIP “DRVCC” Handoff to CDMA 1x Circuit
Switch Voice (without S102)
PSTN
HLR Circuit
Switched
Core
MSC/ (Voice) ANSI41
Voice BSC
Channels
CDMA2000 1X
BTS
Legacy 1X AT
3GPP2
LTE supports VoIP and SCG

MGC/MGW
LTE - 1X AT
Hands Off to CDMA2000 IMS
1X Circuit Network
outside of LTE Coverage
Internet / Intranet
LTE
3GPP PCRF HSS

LTE UE MME
Evolved Packet Core

SGW PDN
GW
eNode B
IMS SCG VCC application allows dual radio LTE VoIP services to hand off to 1X CS Voice
without S102.
57
VCC : IMS to CS Handover Call Flow – “DRVCC”
5) VCC updates the IP
addresses for the existing
call to connect to the new, VCC App
SCGServer
incoming call MGW.
CTS TAS
4) INVITE CSCF
3) 1X Orig
MSC MGCF
BS
MGW
2) Handover MGCF
Trigger IMS
domain MGW
6) BYE pCSCF
Broadband PSTN
Access VoIP Bearer Path
1) Existing VoLTE call
between the Handset on LTE Circuit Bearer Path
LTE RAN
and PSTN user. Signaling Path
& EPC
58
LTE VoIP SRVCC Handoff to CDMA 1x Circuit
Switch Voice (with S102)
PSTN
HLR Circuit
Switched
Core
MSC/ (Voice) ANSI41
Voice BSC
Channels
CDMA2000 1X
BTS
Legacy 1X AT
3GPP2
S102
LTE supports VoIP and SCG

MGC/MGW
LTE - 1X AT
Hands Off to CDMA2000 IMS
1X Circuit Network
outside of LTE Coverage
Internet / Intranet
S102 is used for Hand
Off Signaling
LTE
3GPP PCRF HSS

LTE UE MME
Evolved Packet Core

SGW PDN
GW
eNode B
IMS SCG VCC application with S102 allows LTE VoIP services to hand off to 1X CS Voice.
59
VCC : IMS to CS Handover Call Flow - SRVCC
6) VCC reconfigures the IP
addresses for the existing
call to connect to the new, VCC App Server
incoming call.
CTS TAS
CSCF
4) INVITE
MSC MGCF
BS
MGW
MGCF
3) 1x Orig S102 IMS
domain MGW
2) Handover
5) HO Command
Trigger
7) BYE pCSCF
Broadband PSTN
Access VoIP Bearer Path
1) Existing VoLTE call
between the Handset on LTE LTE RAN Circuit Bearer Path
and PSTN user. & EPC Signaling Path
60
Single Radio Voice Call Continuity PS to CS
(E-UTRAN/CDMA SRVCC)
UE in LTE with established call to PSTN subscriber UE tunes to new network
UE measures signal strength MGCF sets up incoming circuit bearer
UE reports signal strength to eNB MGCF routes call to SCC AS
eNB decides HO is required and sends request to MME SCC AS sends RE-INVITE to TAS with new bearer IP
MME sends request to MSC enhanced with S102 interface* TAS forwards to MGCF
MSC prepares handover, signals BTS and initiates call to SCC AS using STN-SR MGCF instructs MGW to update IP connection
In parallel to IMS processing the MSC sends HO
response back to MME
MSC
CDMA PSTN/PLMN
BTS
MGW PCM
MGCF
IMS Core
TAS
E-UTRAN PCRF
MME HSS/HLR
Enhanced Packet Core CSCF

(Voice + Data) SCC AS MRF
eNode B
SGW
PGW
62
Mid-Call Services with LTE to CDMA Hand-down
• Case 1: Mid-call service (3WC, CW, CT, Hold) occurs and returns to
single-party call prior to Hand-down.
- The mid-call (multi-party) was completely handled in IMS TAS. Hand-down is
not impacted.
• Case 2: Single party call is Handed-down to CDMA. Then a mid-call
service is initiated on the CDMA MSC
- The mid-call (multi-party) is completely handled in the CDMA MSC. The
Hand-down that occurred prior to the mid-call services is (clearly) not
impacted by the subsequent mid-call service. Note: multi-legged calls may
result in multiple calls through the IMS depending on anchoring strategy but
they are treated as independent calls by the IMS – no bridging is done in the
IMS.
• Case 3: Mid-call service (multi-party call) is active on the IMS WHEN
the hand-down is attempted
- If the multi-party call is stable (no party is on hold), the call will hand-down,
but UE control of the conference bridge is lost.
- If any of the parties are on hold, the hand-down is denied by the VCC
Application Server and the call continues in the LTE network
63
VoLTE and topologies for
large geographic regions
Where the speed of light is perceptible to the end user….

Alternate Home Network Topology Options
- Topology 1: Dynamic P-CSCF/IMS/AS

- Dynamic allocation of P-CSCF, UVP, CTS, SCC-AS based on user location
- Topology 2: Home IMS/AS and Home P-CSCF
- Home use of P-CSCF (w/ BGW)
- Home region IMS associated with UE
- Static Allocation of AS(s) (CTS, SCC-AS)
- Topology 3: Home IMS/AS and Regional P-CSCF
- Regional use of P-CSCF (w/ BGW)
- Home region IMS associated with UE
- Static Allocation of AS(s) (CTS, SCC-AS)
65
Topology 1: Dynamic Allocation Model
Region Y (UE Home)

Region X LTE TAS
(CTS)
SCC AS
(SCG)
LTE TAS SCC AS
(CTS) (SCG)
LCP DNS LCP DNS
MSC S-CSCF VitalQIP DNS VitalQIP DNS

MSC S-CSCF
. I-CSCF . I-CSCF
. 5450 ISC .
. . 5450 ISC
MSC MSC
PCRF PCRF
P-GW P-GW
A-BGF
S-GW A-BGF S-GW
P-CSCF
EPC P-CSCF EPC
AS and IMS Core

UE1 Depends on region UE1
66
CTS User Profile Data Options
Primary/Protect & CSD
CSD Option
•Primary/Protect Option
HSS
Sub A Data Sub A Data Other
Sub B Data Sub B Data Sub A Data
Sub C Data Sub C Data Sub B Data Apps
Sub D Data Sub D Data Sub C Data
Sub D Data
App App Sub E Data
Sub F Data
Server Server
... Sub G Data
Sub H Data
App App
Geo-redundant Pair Server Server
App App
Server ... Server
Sub E Data Sub E Data
Sub F Data Sub F Data
Sub G Data Sub G Data
Sub H Data Sub H Data Centralized Subscriber Database and Dynamic CTS Assignment
App App
With this option, CTS specific service data for a
Server Server subscriber is stored as repository (transparent) data in
the HSS
Any CTS can retrieve a copy of a subscriber’s data from
Geo-redundant Pair the HSS and process calls to/from the subscriber
67
CTS User Profile Data Options
Why CSD?
• Improved user profile data integrity (consistency, integrity, backup,
restore) because user profile data is being centralized in a single physical
database.
• Flexibility regarding scalability and geo-graphical redundancy because
session control and application layer are user-data-less (any ISC, CTS may
serve any user).
- Dynamic allocation of user to a CTS server based on location
 In our case, we will discuss on a per region basis
- When the network is extended with new CTS instances traffic may re-balance
automatically across the whole network and or region without the need of
moving users manually from one CTS to another CTS.
- Geographical redundancy is present by default. So, can be introduced on-the-fly
without needing to provision a Protect CTS/FSDB as well as re-provisioning of the
per user IFC (to point to Primary/Protect TAS instance).
68
CTS Dynamic Assignment Description
• The subscriber‘s iFC is stored in IMS HSS

- The iFC contains the CTS-FQDN;
• The CTS-FQDN resolution is based on local DNS resolution
- The Same CTS-FQDN will resolve differently in each region
- Example on next slide
• At UE registration, a CTS is selected and that CTS is notified of the registration
- The S-CSCF keeps that affiliation
- The CTS assignment information is stored in transparent HSS data
- The CTS queries HSS for a copy of subscriber‘s data and caches a copy in its local database, which it
uses to process subsequent calls to/from the subscriber
• The user will stay assigned to that CTS until:
- The user re-registers with a different S-CSCF
- Expiration of timed re-assignment (if AT&T uses this option)
- A duplex CTS failure
• If the user re-registers from another region:
- User will register with local P-CSCF, I-CSCF, and S-CSCF
- Resolution of CTS-FQDN in the other region will assign a local CTS instance
- Flow on next slide
69
Topology 2: Home IMS/AS and Home P-CSCF
Region Y (UE Home)

Region X LTE TAS
(CTS)
SCC AS
(SCG)
LTE TAS SCC AS
(CTS) (SCG)
LCP DNS LCP DNS

MSC S-CSCF
. I-CSCF . I-CSCF
. 5450 ISC .
. . 5450 ISC
MSC MSC
PCRF PCRF
P-GW P-GW
A-BGF
S-GW A-BGF S-GW
P-CSCF
EPC P-CSCF EPC
UE1
70
Topology 3: Home IMS/AS, Regional P-CSCF
Region Y (UE Home)

Region X LTE TAS
(CTS)
SCC AS
(SCG)
LTE TAS SCC AS
(CTS) (SCG)
LCP DNS LCP DNS

MSC S-CSCF
. I-CSCF . I-CSCF
. 5450 ISC .
. . 5450 ISC
MSC MSC
PCRF PCRF
P-GW P-GW
A-BGF
S-GW A-BGF S-GW
P-CSCF
EPC P-CSCF EPC
UE1
71
Voice Gap Call Flow w/ Transport Delay
Consideration (LTE UE1 to LTE UE2)
Dynamic Dynamic Dynamic
Home P-CSCF Home P-CSCF Home P-CSCF
Regional P-CSCF Regional P-CSCF Regional P-CSCF
MSC+MG P-CSCF
UE1 I-CSCF SCC AS1 S-CSCF Orig TAS S-CSCF S-CSCF2 Term AS S-CSCF2 SCC AS2 S-CSCF2 UE2
CF (w/ SBC)
Call Setup
Invite (STN-SR, MGW

SDP) Invite (STN-SR, MGW
MGW control SDP)
Re-Invite(MGW SDP)
ENUM lookup
MSC initiates a call to the Session Transfer Re-Invite(MGW SDP)
Number for Single Radio (STN-SR). STN-
SR is a provisioned fixed value retrieved
from HSS
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP) Re-Invite(MGW SDP)
Re-Invite(MGW SDP) MGW control
v
v
Re-Invite(MGW SDP)
200 OK (SDP Answer)
MGW control
200 OK (SDP Answer)

200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)

200 OK (SDP Answer)
200 OK (SDP Answer)
MGW control 200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer) Transport Delay
72
Consideration (LTE UE1 to PSTN)
Dynamic Dynamic
Home P-CSCF Home P-CSCF
Regional P-CSCF Regional P-CSCF
MSC+MG
UE1 I-CSCF SCC AS1 S-CSCF Orig TAS S-CSCF MGCF PSTN
CF
Call Setup
Invite (STN-SR, MGW

MGW control SDP)
Re-Invite(MGW SDP)
ENUM lookup
from HSS
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
MGW control
v
MGW control
200 OK (SDP Answer)

200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer) Transport Delay
200 OK (SDP Answer)
73
Consideration (LTE UE1 to LTE UE2 (3G))
Dynamic Dynamic Dynamic
Home P-CSCF Home P-CSCF Home P-CSCF
Regional P-CSCF Regional P-CSCF Regional P-CSCF
MSC+MG
UE1 I-CSCF SCC AS1 S-CSCF Orig TAS S-CSCF S-CSCF2 Term AS S-CSCF2 SCC AS2 MGCF UE2
CF
Call Setup
Invite (STN-SR, MGW

MGW control SDP)
Re-Invite(MGW SDP)
ENUM lookup
from HSS
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
v
v
MGW control
MGW control
200 OK (SDP Answer)

200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)

200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)
200 OK (SDP Answer)

Transport Delay
74
SRVCC Voice Gap Estimate Comparison APPLIES for CDMA?
(for home network scenarios with ~40ms one way
transport delay) LTE UE1 to LTE UE2 LTE UE1 to PSTN LTE UE1 to LTE UE2
in LTE Coverage in 3G Coverage
Mean Peak Mean Peak Mean Peak
Dynamic AS UE1 and UE2/PSTN 180 275 130 205 175 270
same region
UE1 and UE2/PSTN 220 335 205 265 215 330
across country
LTE UE1 to LTE UE2 LTE UE1 to PSTN LTE UE1 to LTE UE2
Home IMS/AS and Mean Peak Mean Peak Mean Peak
UE1 and UE2/PSTN 190 295 130 205 175 270
Home P-CSCF home region
UE1 and UE2/PSTN 260 395 210 321 300 450
across country
LTE UE1 to LTE UE2 LTE UE1 to PSTN LTE UE1 to LTE UE2
Home IMS/AS and Mean Peak Mean Peak Mean Peak
Regional P-CSCF UE1 and UE2/PSTN 190

home region
295 130 205 175 270
UE1 and UE2/PSTN 315 475 210 321 300 450

across country
MS location matter if Bearer is optimized – shortest path? Is assumption that bearer also g
*Assume Border Gateway anchoring/pivoting with P-CSCF (and no media release)
77
Other Considerations
Home P-CSCF/Home Local P-CSCF/Home

Characteristic Dynamic Allocation
Region region
Voice Gap Most scenarios under Some cross country Most cross country
300ms scenarios over 300ms scenarios over 300ms
P-CSCF Selection Dynamic – PGW assisted Static (e.g. provisioned in Dynamic – PGW assisted
handset)
I-/S-CSCF Selection I-/S- always local to P- I-/S- always local to P- Need mechanism to determine
CSCF CSCF UE home region (e.g. regional
domain names)
CTS selection Requires CSDB and Always assigned in home Always assigned in home
regional DNS for local CTS network network
assignment
SCG Selection Dynamic allocation based Always assigned in home Always assigned in home
on regional DNS network network
STN-SR Routing Unique STN-SR to each Static STN-SR; requires Static STN-SR ; requires
SCG, could require write capacity engineering; capacity engineering;
to PS/CS HSS resource utilization resource utilization
considerations considerations
What if additional app Need dynamic allocation Always in home network? Always in home network?
servers? for all
78
Voice Gap Time Result Summary
- Voice gap times are strongly dependent on transport delays, hence, are impacted
by network topology choices. Some network topologies result in more cases of
greater than 300ms voice gap times than others for home network SRVCC
scenarios
- Review of voice gap times associated with three common topology choices
suggest that Voice gap times could be reduced to around 300ms for most cases
using one of the following techniques :
- Delay HO command by fixed amount, e.g., 100-150 msec
- Higher voice gap numbers reduced by corresponding amount
(minimum voice gap of 100-150 msec remains)
- Impact on HO performance should be small
- Allows acceptable voice gap times with suboptimal network topologies
- Trigger HO command with first detection of downlink media
- Limit maximum HO delay to ~200-300 msec to limit impact on HO perf
- Minimize voice gap to 100-150 msec in wider range of cases than 1.
- Higher development impact than 1.
- An alternate option is eSRVCC
- Planned for 3GPP Release 10. Stage 2 Complete, Stage 3 expected to be completed in March 2011.
- ALU plans to support eSRVCC in its roadmap when Stage 3 is completely defined in standards.
79
Voice Interruption Time (from 3GPP TR 23.856)
IMS Bearer before HO
b3.Tune to CS
b2.HO CMD MME b1.HO CMD a1.Invite a2.Offer

UE MSC SCC AS Remote
/eNodB a4.200 OK a3.Answer
k
Uplin
k Uplin
CS Bearer after HO IMS Bearer after HO

D ow
nlink MGW nlink
D ow
- The voice downlink media flow is interrupted after step a2 or step b2, and
restored after both step a4 and step b3 are finished. So the interruption time of
the flow is:
- Td = MAX(Ta1+Ta2+Ta3+Ta4-Tb1-Tb2, Tb3)
- Steps (Tb1+Tb2) happen in the network that the UE currently attaches, with few
signalling nodes and faster signalling processes. It is reasonable to assume that
duration of (Tb1+Tb2) is shorter than the total duration of (Ta1+Ta2+Ta3+Ta4)
in roaming case (either the UE or the remote is roaming or both) or the case of
the UE and remote are not in the same PLMN.
- Tb3 is specified less than 300 ms according to TS 36.133, and normally is about
100 ms
80
Introducing ATCF/ATGW to reduce voice
interruption time during AT
- Ta1+Ta2+Ta3+Ta4 represents the transmitting and processing time
delay of the messages for remote update procedure. It is dependent
on the serving IMS network of the SRVCC UE, as well as the home
IMS network of the SRVCC UE, and the remote network of the remote
end.
- The interruption time may be worsened in following scenarios:
- The call is inter-operator, with more entities involved;
- The remote users is roaming;
- The poor performances in any of the networks involved, causing additional
delay;
- The poor performance of the remote end, causing additional delay;
- The access bandwidth is limited.
Conclusion: the study has shown that the performance of SRVCC
handover is mainly dependant on the delay brought by the remote
update procedure. Thus the introduction of ATCF/ATGW for media
anchoring in the serving network to reduce voice interruption time.
81
eSRVCC- Basic concepts
• P-CSCF is in VPLMN
• An ATCF (Access Transfer Control Functionality ) inserted in the IMS sig. path at REGISTER
- The @ of the ATCF passed to the MME as a STN-eSR
• The VATF anchors voice media (in an ATGW) at sip session set-up when relevant
• The MSC invoked by the MME at SR-VCC HO issues the SRVCC procedure per REl8/9 specs
- This SRVCC procedure targets the ATCF (STN-eSR)
- Access Transfer and UE RAT change performed simultaneously (same concept as Rel9 SRVCC)
Access Leg
Serving Leg Home Leg
SN HN
Remote Remote
MSC ATCF After transfer I/S-CSCF,
UE After transfer After transfer Leg End
Server ATGW Before transfer SCC AS
CS radio Mw
Gm
Before transfer
UE
82
eSRVCC - IMS Registration
• ATCF adds STN-eSR into the • SC AS populates the new value of STN-
REGISTER propagated to the SCC AS eSR in the HSS user data
• HSS updates the MME/SGSN with the
new value of STN-eSR
MSC
MGCF Remote UE
CDMA MGW
BTS
HSS/HLR
MME IMS Core

TAS
E-UTRAN
Enhanced Packet Core IMS

(Voice + Data)
ATCF SCC AS
eNode B
P-CSCF
SGW PGW
Impacted Entity
VPLMN HPLMN
PCRF
83
eSRVCC – IMS Session Establishment
• The ATCF inserted in the sig. path. The • Home leg between the ATCF and the SCC
ATGW may be inserted in the data plane AS
• Remote leg between the SCC AS and the
• Access leg between UE and ATCF remote UE
MSC
MGCF Remote UE
CDMA MGW
BTS
HSS/HLR
MME IMS Core

TAS
SGSN
E-UTRAN ATGW

(Voice + Data) SCC AS
HSPA ATCF
eNode B
P-CSCF
NB SGW PGW
RNC
Impacted Entity
VPLMN HPLMN
PCRF
84
eSRVCC – Access Transfer
• The SRVCC per Rel9 takes place (no change). The signalling for Call anchoring onto
CS domain only needs to go to the ATCF+ATGW (SCC AS no longer receives STN-SR)
1. Voice over IMS
2. SRVCC trigger
3. Voice over CS
MSC
MGCF
Remote UE
CDMA
MGW
BTS
HSS/HLR
MME IMS Core TAS

SGSN
E-UTRAN ATGW

(Voice + Data) ATCF SCC AS
HSPA
eNode B
P-CSCF
SGW PGW
NB
RNC VPLMN HPLMN
Impacted Entity
PCRF
85
2d. Solution Architecture
Roaming considerations

LTE-LTE : Home routed traffic scenario
• PDN GW IP address
•APN & Default PDN GW ID HPCRF Rx
PDN GW IP (FQDN or IP address) Gx
address •vplmnAddressallowed =No
•HSS IP Address SG
PGW i Home operator’s IP
DNS HSS services
HPLMN
Inter PLMN IP
Backbone S9
S6a
DNS VPCRF
S8
MME
Inter PLMN IP Backbone required
S1-mme GSMA IR.34
S11
E-UTRAN
S1u S5 SGi Data Services
eNB SGW PGW (e.g., VPN, FTP)
VPLMN
Principle
Most Operators use home routed model. This model consists in routing the traffic back from the
visited network to the home PDN GW.
• Using the home PDN-GW, the subscriber home operator can still connect with the requested
external IP networks access public internet access, IMS services or for private networks like
corporate networks or web based services.
• The subscriber’s profile and security credential will be retrieved from the HSS and the user
experience will remain the same as if in home within the capabilities of the visited network and
possible restrictions subject to Roaming agreements.
87
LTE - Local breakout model (new model)
Rx
•vplmnAddressallowed =yes HPCRF
Home operator’s IP
HSS services
S9 HPLMN
S6a
DNS VPCRF
MME
S1-mme
S11
E-UTRAN
S1u S5 SGi Data Services
eNB SGW PGW (e.g., VPN, FTP)
VPLMN
Principle
This model consists in using services available within the capabilities of the visited network.
• The SGW and the PGW are used in the visited network and not require from Home Operator
any IP backbone interconnection.
• The subscriber’s profile will be retrieved from the HSS in the home network and the user
experience will depend of the capabilities of the visited network and possible restrictions
that may have been agreed in Roaming agreements.
• Offer Services not requiring an operator control in the home network (internet access)
88
IMS Roaming: P-CSCF in Visited network
HPCRF Rx
S-CSCF
Gx
SG
DNS PGW i P-CSCF IMS I-CSCF

HSS
HPLMN
Inter PLMN IP
Backbone IPX S9
S6a
DNS S8 VPCRF
MME P-CSCF
S1-mme
S11
E-UTRAN PGW
S1u SGi
eNB SGW S5
PGW Data Services
(e.g., VPN, FTP)
VPLMN
•Principle
•P-CSCF located in visited network : P-CSCF of visited network discuss
directly with I-CSCF of home network.
•I-CSCF is a contact point between visited and home networks.
89
IMS Roaming Session Flow
Home1
Home2
HSS
HSS 5 TAS I I 10 TAS
B B 9
7 C C 12
F F
6 11
ENUM 4 I-CSCF
S-CSCF 8 S-CSCF 13
IBCF IBCF
IPX 14
3 ENUM
IBCF
IBCF
Visiting1 2 Visiting2
15
P-CSCF
B B
P-CSCF 16
G G
W W
eNode B
1
eNode B PGW SGW
SGW PGW
 Originating subscriber is from Home1 and is roaming in Visiting1

 Destination subscriber is from Home2 and is roaming in Visiting2
90
Diameter Routing Architecture (as proposed by
GSMA)
91
Benefits of including Diameter Routing Agents in
Diameter Architecture
- Solution to Diameter signalling scalability. Presence of DRA functions will
eliminate the geometric explosion of diameter interfaces between clients
and servers (e.g., MME and HSS).
- DRA(s) will maintain or have access to Subscriber to Diameter Server
mapping database to route an incoming Diameter message from a client
to the server.
- Secure point of interconnect for inbound and outbound roamers.
- A DRA function can provide such interconnection in a secure manner without
exposing the internal topology of the operator‘s network. It will determine
whether a specific Diameter message is meant for internal HPLMN
consumption or for a VPLMN based on the network domain/realm information
that identifies the Diameter Server.
92
3. End User Services

Alcatel-Lucent Offer for Voice Service on IMS
Core Elements
Telephony
End User Control &
Application Administration
Server
Alcatel-Lucent Alcatel-Lucent
5420 Converged Telephony Server 5420 Personal Communication
(CTS) Manager (PCM)
 Telephony services to any SIP, IP or  End user self-care and
POTS subscriber, mobile and fixed administrator management of call
features, call logs, voice mail
 Residential services
 Consistent look-and-feel end user
 Business services interface via standard web
 PBX trunking browser
 Regulatory feature support  Click-to-dial any phone number
on any web page
 Scalable, Robust
 Find me/follow me
 Open APIs
94
Voice in LTE
VoIMS related Standards in 3GPP
• 22.173, IMS Multimedia Telephony Service and supplementary services; Stage 1
• 22.228, Service Reqs for the IP Multimedia Core Network Subsystem
• 23.204, Support of SMS over generic 3GPP Internet Protocol (IP) access; Stage 2
• 23.216, Single Radio Voice Call Continuity (SRVCC); Stage 2
• 23.228, IP Multimedia Subsystem (IMS); Stage 2
• 23.237, IP Multimedia Subsystem (IMS) Service Continuity; Stage 2
• 23.272, Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2
• 23.292, IP Multimedia Subsystem (IMS) centralized services; Stage 2
• 24.229, IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3
• 24.628, Common Basic Communication Procedures
• 29.864, Service Data Descriptions for AS Interoperabilty
• 32.260, IMS Charging
• 32.299, Charging Management – Diameter Charging Applications
• 24.173, Multimedia Telephony Service and Supplementary Services
• 24.604, Communication Diversion (CDIV)
• 24.605, Conference
• 24.606, Message Waiting Indication (MWI)
• 24.607, Originating ID Presentation and Restriction (OIP/OIR)
• 24.608, Terminating ID Presentation and Restriction (TIP/TIR)
• 24.610, Communication Hold
• 24.611, Anonymous Communication Rejection; Call Barring (CB)
• 24.615, Communication Waiting (CW)
• 24.616, Malicious Communication Identification (MCID)
• 24.629, Explicit Communication Transfer (ECT)
• 24.642, Completion of Communication to Busy Subscriber (CCBS)
•And many, many more
95
5420 CTS Feature Packages
• Feature Packages • A la Carte Features
• Silver Residential/Consumer • Attendant Console

- Includes MMTel Features • Deluxe Auto Attendant
• Gold Residential/Consumer • Hunt Group Queuing
• Core Business • Large Call Limit
• Premium Business • Location Based Services
• US Military
• PBX VPN
 Every subscriber is assigned a feature package, and optionally a la carte

features
 Service provider selects which features in the feature package are enabled
per sub
 5420 PCM subscriber licenses purchased separately
 Multiple feature packages can be supported per 5420 CTS
 Feature packages can be customized per service provider
96
5420 CTS Feature Package
Silver Residential/ Gold Residential • Reminder Call
• User Call Services: • Remote Access Service
• Anonymous Call Rejection • Selective Calling Features:
• Call Waiting Terminating: - Selective Call Acceptance (SCA)
• Automatic Call Back - Advanced Endpoints
• Automatic Recall - Selective Call Forwarding (SCF)
- Flashable Endpoints (INFO Method)
• Call Barring (Outgoing Calls) - TISPAN Simple Endpoint
- Selective Call Rejection (SCR)
- Generalized Category Names - Cancel: Per Call, Mid Call, Persistent - Selective Distinctive Alerting
- Outgoing Call Barring - Caller ID with Call Waiting - Wild Card Characters in Screening List
• Call Blocking (Incoming Calls) • Calling Line ID Related Features: • Service Suspension
- Incoming - Calling Line ID Presentation, Restriction, w/ Override • Simultaneous Ringing
- Incoming Intl Connected Line Identity Presentation, Restriction
-
• Speed Dialing (1 or 2 digit)
• Call Completion to Busy Subscriber - Calling Name Identification Presentation, Restriction
- Call Completion to Busy Subscriber • Calling Party Category (CPC) • Star Code Access to Voicemail
- Blocking Completion to Busy Subscriber • Conference Calling (3-Way, N-Way, Programmable • Voice Messaging Interfaces:
• Call Forwarding: 3-way, TISPAN) - SIP and SMDI
- Bearer-Based Call Forwarding • Configurable Feature Codes (NANPA Vertical Service - Message Waiting Indicator
- Call Deflection Codes) - VM Originated Calls
- Call Forwarding Always (CFA) (Variable) • Device Extensions • Warmline
- Call Forwarding Busy (CFB) • Dial Code Feature Status Interrogation
- Call Forwarding Default • Do Not Disturb (DND)
- Call Forwarding Local Additional Supported Services:
• Dual Mode Service/ Single Number Service
- Call Forwarding No Answer (CFNA)
• End Point Support
• Customized Announcements
- Call Forwarding Password Protected • Directory Service
- Call Forwarding Unregistered (CFU) - Advanced End-Point
- Call Forwarding to Voicemail (CFVM) - Flashable End-Point (INFO Method) • Fax
- Inhibition of Incoming Forwarded Calls (IIFC) - TISPAN Simple End-Point • Local Number Expansion to National Number
• Call Hold – Consultation • Hotline • Lucent Communication Manager User Interface
Call Transfer Features: • Intercept Referral
• • Overlap Digit Sending
Call Transfer with Consultation • Multiple Ring Patterns
- • Shared HSS Data (with Alcatel-Lucent USDS)
- Call Transfer Blind (Local, Network with Dedicated Access Code, - Multiple Directory Number
Network from 3-way call) - Distinctive Ringing with Call Waiting • Terminating Feature Precedence
- Call Transfer from 3-way • Personal Ring Back tone (PRBT) • Video Call – Point to Point
- Timed Reminder on Transfer • Phone Context
Incremental Services in Gold Package:

• Basic Auto-Attendant
• Multiple Subscriber Number (MSN)
• Music on Hold
• Time of Day/ Day of Week setting for several supplementary services via PCM
• User Controlled Call Barring via CM
97
Example 5420 CTS Feature Package
Core Business/ Premium Business
• User Call Services: • Additional Supported Services:
• All supplementary services in the Silver Package, plus: • DID/DOD
• Account Codes • Communication Manager User Interface
• Authorization Codes • Voice VPN via PDP and Closed User Group
• Basic Auto-Attendant
• Call Park and Call Pick-Up:
- Call Park and Retrieve • Incremental Services in Premium
- Hard Hold • Package:
- Directed Call Park and Retrieve
• Music on Hold
- Call Pick-Up
• Time of Day/ Day of Week settings via CM
- Directed Call Pick-Up
• User Controlled Call Barring
- Directed Call Pick-Up with Barge-In
• More to be added in future releases
• Closed User Group
- Closed User Group Call Limit
• Direct Dial to Voicemail
• Flexible Calling Line ID/ Group ID Delivery
• Multi-Line Hunt Groups
- Sequential, Circular, Uniform Hunting
- Member(s) Make Busy, Group Make Busy, Stop Hunt
- No Hunt Member
• Organizational Support
• Private Dial Plan
- Extension Dialing
- Private Dialing Extension Display
• Sequential Ringing
• Transfer to User‘s Voicemail
• Mobile Extension and Virtual Office
98
5420 CTS Supports Subscriber Features Provided
Modified cdc 29 oct 2010
re-integrate
By 3G MSC
Subscriber Features Subscriber Features – CAMEL (see next
 Calling Line ID Presentation slide)
 Calling Line ID Restriction  Pre-paid
 Calling Name  VPN
 Call Forwarding Unconditional  Personal Ring Back Tone
 Call Forwarding on MS Busy  Smart Limits
 Call Forwarding on No Reply  Abbreviated Dialing
 Call Waiting
 Call Hold
 Multi-Party Services Regulatory Features (see next Section)
 Call Barring of All Outgoing Calls  Emergency Service (E-CSCF Based)
 Call Barring of All Outgoing International  Support for standard CTM for deaf
Calls (Cellular Text Modem)
 Barring of All Outgoing Calls except  Support for Lawful Intercept (CSCF Based)
directed to Home PLMN Country (BOIC-  Support for Mobile Number Portability
exHC).
 Malicious call trace
 Hotline
 Operator Barring
 Unstructured Supplementary Service Data
 Subscriber Programming Provided fully by 5420 CTS
 Voice Messaging IMS Standards Based Offering
 Location Based Services
99
Feature Support For Legacy WIN Features
• The following features are traditionally provided in wireless networks using WIN
services. In IMS they can be provided using alternative methods as described
below:
- Prepaid
- Prepaid services provided using the 3GPP standard Ro interface
- 8610 ICC app server can provide the prepaid service logic
- VPN
- CTS can support up to 3,000 private dialing plans in support of VPN service
- Personal ring back tone
- CTS, with the MRF, can provide personal ring back tones when callers call a user.
- In addition we have a full-feature 5900 PRBT application server
- Smart Limits
- CTS and PCM have a rich set of services to control calling behavior, including:
- Selective call acceptance to block all calls except from certain numbers
- Selective call rejection to block only certain numbers
- Ability to set times during which calling is allowed
- Abbreviated dialing
- CTS supports speed dialing (1 or 2 digits).
- Can be programmed either through touch tones or the PCM web portal
100
Subscriber Programming of Supplementary
Services
• Two methods are currently defined in 3GPP 23.173 (section 4.3) for supporting
subscriber configuration (e.g. to configure call forwarding number):
- Use of Ut interface (XCAP/HTTP)
- Use of * xy ―star codes‖
• GSMA VoLTE profile has made support for the Ut option mandatory
- Unlikely they will make support for any other option mandatory
• Additionally the spec recognizes that other options are possible, such as the use of
a web portal, but these are outside the scope of the specification
• ALU will need to support the Ut interface when UE are available that support it
- Ut through data connection. Feature updates during a call are buffered until the call
releases
- Will be supported through PCM
- For trials we will use the web portal interfacing to PCM as interim
- Continue to use *xy codes for per call features or if Origination Anchoring in IMS
101
CTS Interworking with Voice Mail Systems
Custom
5420 PCM Client
http
Published
5100 CMS (AnyPath)/ APIs
Other VM Systems
5420 CTS
SIP-ISC
Residential +
SIP-ISC
Business TAS
Sh
5450 ISC
IP Network
8650 SDM
IP Access – Fixed & Mobile

John
Bill
Susan
John
• CTS redirects calls to VM number
…. configured for subscriber
Bill Custom
Susan Client • CTS forwards MWI status to endpoints
VoIP Mobile Phone
…. SIP Endpoint
• MWI status also reported to web
Soft Client portal using PCM APIs
• Star Code Access to VM
• CTS interworks with 5100 Converged
Messaging System (CMS) as well as
many other VM Systems
102
4. Regulatory Services

Regulatory Services:
LI / CALEA

Lawful interception
• Requirement
- National requirements to handle lawful interception
• Solutions
- CSFB: Visited PLMN MSC based solution
- VoIMS: Home and Visited PLMN IMS solution as per 23.107
• Applicable standards:
- 3GPP TS 33.106, Lawful interception requirements, Stage 1
- 3GPP TS 33.107, Lawful interception architecture and functions
- 3GPP TS 33.108, Handover interface for lawful interception
- ATIS TI.678 LAES for Voice over Packet Technologies in Wireline
Telecommunications Networks
105
Lawful Intercept Architecture
For simplicity, not all interfaces/connections are shown.
Provider/LEA
8650
Bearer & Control
HSS
Control Only
eNodeB
HI
9471 IRI
MME
eNodeB 1357 ULIS / SS8

UE
IRI
7750
SGW 7750
PDN-GW CSCF
5750
IMS
PCRF
SBC
NodeB Managed PSTN
UE Core Network
RNC SGSN GGSN

PDN
---> - Admin (X1)

IRI – Intercept Related Information (X2)
CC – Content of Communications (X3)
SBC – Session Border Controller
CSCF - Call Session Control Function
106
Alcatel-Lucent Solution: 1357 Unified Lawful Interception
Suite (ULIS)
Unique Interception Management Center (IMC)
handles lawful interception administration function: Converged
• Centralizes management of all lawful IMS
interception orders, particularly warrants
activation or deactivation. Legacy LTE
Wireline
• Concentrates all IRI received from the LIGs and
transmits it to the LEMF/MC. Internal
Interfaces
• Provides single management across all domains.
Distributed Lawful Interception Gateways (LIG) LIP

IMC LIGs
handles IRI & CC mediation functions:
Administration
• Generates and delivers IRI and CC according to Function IRI & CC Mediation Legacy
the network topology and the LEMF or MC. Function Wireless
• Number of LIGs depends on the network size and
the targeted traffic flows.
• According to CC delivery type toward LEMF/MC,
the LIG architecture can be circuit switched (LIG Standardized
External Interfaces
CS) or IP (LIG IP).
Distributed Lawful Interception Probes (LIP) IRI: Interception Related Information

handles Internal Interception Function: LEMF/MC CC: Content of Communication
LEMF: Lawful Enforcement Monitoring
• Can generate internal IRI or CC when no active Facility
solution is available in the Core Network. MC: Monitoring Center
107
Alcatel-Lucent Lawful Interception Solution
Mapping of the main functional entities
Network Operator domain Mediation LEA domain
IMC
Administration HI1 LEA
function
Intercept Related LEMF

Network Information (IRI) IRI mediation
HI2
Internal function
Functions
Content of
Communication (CC) CC mediation HI3
function
IIF
Internal External
Interfaces Interfaces
INI HI
LIG
LIP
1357 ULIS functions are mapped on Standard LI Model

108
Lawful Intercept General Voice Requirements –
IMS VOIP
• It is a requirement to report forked/spawned calls by application servers or other
B2BUAs on behalf of surveillance subject
• It is a requirement to intercept forwarded calls/redirected calls, transferred calls,
3-way or multi-way calls, conference calls, or any other call scenarios that will be
made available to subscribers as part of the service offering
• SIP URI and tel URI shall be supported as target IDs
• If reasonably available, a subject‘s location shall be reported when a call is made
or ended
• Intercept jurisdiction shall be supported
- Jurisdiction shall be either one specific state, multiple states, or nationwide
109
Emergency Services

Emergency Services
• Requirement
- National requirements to handle (and route) emergency call and corresponding
location mechanism to be supported
• Solutions
- CSFB: MSC based with 3G sourced location
- VoIMS: As per 23.167 (release 9)
- VPLMN located E-CSCF plus MME and SRVCC extensions in Release 9
- Requires IMS based PSAP database in addition to existing MSC database
111
CSFB emergency services: 3G1x
• LTE-3G1X offers two approaches to CSFB and legacy emergency services.

They are:
- Dual transceiver solution; and
- Circuit Switching Fallback (CSFB) solution with single transceiver (single
transmitter and single/dual receiver)
112
Emergency Services in LTE (VoIMS)
High Level Architecture/Call Flow
Emergency
5. Request Location Info Service Network
GMLC/LRF 8. Location Info Response (x,y)
6. Retrieve Subscriber 3. Request ESRN from LRF

Location from E-SMLC E-SMLC
MME P-CSCF E-CSCF MGCF/MGW

PSAP
7. Retrieve Location
data from UE 2. P-CSCF recognizes 4. Route Call to PSAP
or eNB emergency call and
routes to E-CSCF Map x,y to
eNB SGW PGW street
information.
E-UTRAN
1. UE Initiates
Emergency Call
Note: As part of the Emergency Attach or Emergency PDN Connectivity Request procedure the MME sends
Location Report to GMLC containing UE identity, UE positioning capability and the MME IP address.
113
Number Portability

Number Portability
• Requirement
- Support porting out and porting in of LTE subscribers to/from another service
provider
• Solutions
- CDMA: Current NP solutions in place in CDMA networks
- Triggered at MSC using ANSI-41 NPREQ queries to NP SCP DB
- VoIMS: Current NP solutions in use in IMS based network
- NP data stored in ENUM Servers; Query performed by S-CSCF/IBCF
- NP data stored in regional/country wide NP DB; Query performed by MGCF/IBCF
- Both solutions already supported by ALU products in our LTE solution
115
Number Portability – High Level Flow in IMS using
ENUM Server
1. S-CSCF performs ENUM on Terminating DN
ENUM returns e2u+pstn with routing information (e.g. RN and NPDI indication or
routing prefix)
For “ported out” to IP, ENUM could return e2u+sip
2. S-CSCF routes to i) BGCF or ii) IBCF based on ENUM service e2u+pstn/e2u+SIP
3. BGCF routes based on routing information to
i. MGCF for PSTN/PLMN termination
ii. IBCF for IP termination (Route header = IBCF, Route header = proxy in IP
network)
5, IBCF routes on Route header = proxy in IP network
ENUM
1
3i 4
2i
PSTN/PLMN
Networks
S-CSCF BGCF MGCF
2ii
3ii
5
IP
Networks
IBCF
116
Number Portability – High Level Flow in IMS using
NP DB
1. S-CSCF performs ENUM on Terminating DN
ENUM returns NXDOMAIN
2. S-CSCF routes to BGCF
3. BGCF routes to MGCF
3. MGCF performs NP query if the called number is within range of list of ported out
numbers
4. MGCF routes to PSTN/PLMN/IP
NP
DB
4
5i
PSTN/PLMN
2 3
Networks
5ii 6i
S-CSCF BGCF MGCF

MGCF
1
5iii
6ii
ENUM IP
Networks
IBCF
117
TTY/TDD

UPDATE for CDMA
TTY/TDD Support in LTE
• TTY/TDD service will be a regulatory mandate for voice over IMS
• The service is of such high priority that 3GPP is working the introduction of
standards in TS 23.226 as a set of CRs in 3GPP Release 9
• Key capability required for LTE/IMS solution is trans-coding between V.18 and
GTT-IP (Global Text Telephony/RTP) in the MGCF and MGW
V.18 GTT-IP
New
Transcoding
119
GETS

Regulatory Features
GETS - Introduction
• GETS standards are in the process of being defined and drafts are
available:
- National Security/Emergency Preparedness (NS/EP) – Internet Protocol (IP)
Multimedia Subsystem (IMS) Core Network Industry Requirements (IR) for Next
Generation Network (NGN) Government Emergency Telecommunications Service
(GETS), Phase 1, Voice Service
- National Security/Emergency Preparedness (NS/EP) – LTE Access Network
Industry Requirements (IR) for Next Generation Network (NGN) Government
Emergency Telecommunications Service (GETS)
• Implementation of GETS not planned pending government funding
121
Regulatory Features
GETS – Work items
• The following enhancements are expected in support of GETS:
- Provide priority treatment to GETS users in LTE
- Mainly affects eNB admission control algorithm, some impact on PCRF
- Support priority paging of UE in LTE when terminating calls from GETS user
- IMS TAS and ISC need to recognize specific GETS calls and GETS prefixes and
provide GETS treatment, including assuring priority treatment is provided for the
call
- MGC-8 needs to recognize GETS calls and provide appropriate GETS treatment,
including mapping priority from SIP to ISUP
Current view is that GETS is not required for voice introduction

122
Provisioning and Subscriber Migration

OAM&P Overview
• The EMS and NMS in the end-to-end LTE OAM solution can be grouped
into three parts:
1. LTE (and IP Router)-specific EMS
• 5620 SAM
2. Common NMS
• 8950 SAM required flow-thru subscriber provisioning
• 8615 IeCCF for offline charging
• 8610 ICC for online charging
• Note 1357 ULIS is managed independently
3. IMS-specific EMS
1360 COM
The next slides shows the end-to-end architecture and the roles the various
EMS/NMS support
124
OAM&P Management Architecture
(Fault, Configuration, Performance Mgmt)
Customer FM/PM OSS
FM: SOAP XML/ PM: SFTP FM: SNMPv2c PM: SFTP of XML
JMS 8950 SAM/ Files
Customer OSS
CM FM, PM
CM: SOAP XML/ 1360 COM
5620 CORBA
SAM XMC
1357 CM
ULIS OMC-P
5110 FM, PM, CM

SMSC-C FM, PM FM, PM, FM
CM FM, PM CM FM, PM CM
CM FM, PM FM, PM FM, CM FM
8950 9400s 7750 5780
AAA eNB PGW 8650 SDM VitalQIP 5900 MRF 5420 PCM MGC-8 IeCCF 8610
DSC CTS
HSS/SPR E-NUM MRF MGCF ICC
Portal
7750 9471 DNS SCG OCS
SGW MME
DHCP 7510 MG
ISC
MGW
5025 SG
VSG
LTE Common IMS
125
OAM&P
Management Architecture (Accounting)
Customer BSS
ftp (CDR)
ASN.1 BER
(3GPP
8610 ICC standard)
8615 eCCF
Ro
Rf diameter
Diameter
BTS
CTS
7750 7750 SCG

MGC-8
SGW PGW
MGCF ISC
Only from IMS-GWF
126
OAM&P Overview
• 1360 Com (merged OMC-P/XMC) provides:
- Full FCAPS support for CTS, PCM, SCG, and IMS Core components
- Centralized operations making it easy to manage
• Features Include:
- Fault Management (FM)
- Alarm Display, Forwarding, and Filtering
- Configuration Management (CM)
- Java-based Client GUI and SOAP XML API for flow-thru provisioning
- Performance Monitoring (PM)
- Collect, analyze, display data, and provide interface to northbound OSS
- Security
- Extensive password controls and 5 default user levels
- Customizable Node and Switch Access Lists
- SSH, SSL, RADIUS Authentication
127
OMC-P/XMC - Scalability
• Current architecture scales with equipment modules

- A new 1360 COM server is added for each 4 million subscribers
• Planned enhancements to system scalability:
- Adding provisioning queues per FSDB to increase provisioning rates
- Planning additional tuning to further leverage multiple processors and cores
within the system server
- Single sign-on will help make multiple 1360 COM systems operate as a cohesive
unit
- Continue to leverage advances in hardware technologies to increase capacity of a
single 1360 COM System
128
Roadmap

Released
LTE Solution High-level Roadmap In Development

Under Plan
2010 2011 2012

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
LE2.0/2.1 LE3.0/3.1 LE4.0 LE5.0 LE6.0+
Seamless interworking and Capacity management and Mass market VoLTE

High Speed Data
basic voice VoLTE introduction and service optimization
3GPP Alignment R8 Jun 09 R8 Dec 09 R9 Sep 10 R9/10 TBC
eNB eNB eNB eNB
5,10,20 MHz bandwidths Additional bands Addtnl. bands/bandwidth enh. MIMO
FDD: 700,AWS, 800, 2.6 eMCTA ph1 4RX div, extended cell eMCTA Ph3
Scalability and TDD: 2300,2600 IEEE 1588v2 Semi-pers. sched., RoHC ICIC
cost efficiency 2x2 MIMO: TxDiv, OL, CL TDD 8 Tx/Rx beam form. eMCTA Ph2 Metro cell / SNAP
VLAN, IPsec, GPS, SyncE SGW/PGW/GGSN: SGW/PGW/GGSN: MME/SGSN:
MME/SGSN/PCRF: ATCAv2 Converged GGSN/PGW Converged SGW/PGW Idle signaling reduction
SGW/PGW/GGSN: 7750SR SAM Converged OAM SON: IRAT ANR Priority paging
SON: Plug&Play, ANR (ePC+ Backhaul + RAN) SAM conv. OAM (+WCDMA) SON: mobility,outage
Mobility ph1 (Intra LTE, Mobility ph2 (enh.3GPP) Mobility ph3 (1x) QoS enhance. (FIR, MBR)
Enriched GSM, WCDMA, eHRPD) CS Fallback Ph1 (WCDMA) CSFB Ph2 (eCSFB, GSM, Mobility ph4+ (TDD<>FDD)
Quality of Guaranteed Bit Rate 8 EPS bearers per UE 1x) PCMD enhance. (+IMS)
Experience 4 EPS bearers per UE E2E call trace
Per call meas. Data (PCMD)
SMS over SGs Voice over LTE Ph1 Use limit ph1 (Gx and QoS) Use limit ph2+ (Sponsor)
(VoLTE) Subs. tiers ph1 (AMBR, QCI) Subs. tiers ph2+ (MBR,GBR)
New Business Roaming (Home PGW) Network Share Ph1 (MOCN) VoLTE Ph3+
Models & Apps. Public Safety Ph1 (Deploy) Public Safety Ph2 (Priority) (SRVCC, ICS, roam, IRAT)
Enablement eMBMS Ph1 (TDD) CMAS (Warning system) eMBMS ph2 (FDD, CP)
VoLTE Ph2 (GSMA comply) Net. Sharing Ph2+ (Core)
Local Breakout Pub.Sfty. Ph3+(Pub. Priv.)
Derisk Deploy. E2E Validation E2E Validation E2E Validation E2E Validation
130
Supporting Material

Network Element Overview

Network Element Overview
Introduction
• This section provides an overview of the various network elements added
to LTE to support VoIMS
• Most of the elements are built on the Alcatel-Lucent Linux Control
Platform (LCP)
- Used for Session Manager, TAS, and SCC AS
- MME and LVI application used in LTE built on same hardware, OS, and OAM
infrastructure
- 5060 MGC-8 uses same hardware, OS, and OAM infrastructure (2H2010)
133
Alcatel-Lucent Linux Control Platform (LCP)
One Platform, One Code Base, Multiple Real-Time Applications, Multiple
Environments Same application software runs on existing cPSB and new ATCA platform; Ensures compatibility
with deployed IMS Core network elements.
Field proven Common OAM&P Session Application Device NEW
carrier-grade Infrastructure Management Servers Servers APPLICATIONS
OAM&P middleware
2G + 3G MSC Call Processing

which provides:
5450 IP Resource Control
WRLS SS7 Device Server

Access Gateway Control
5450 IP Session Control
•Alarms
(I/P/S/E-CSCF/BGCF)
Continuity Gateway
H.248 Device Server
MSI Call Processing

Future Application
SS7 Device Server
IOS Device Server

Telephony Server
5420 Converged
•Asserts & audits
Management Interface
Function (H.248)
5420 Service
(PDF, RACF)
MME Application
•Logging Database / iHSS
LVI Application
Configuration
5060 MGC-8
(MIF / MAF)
CDR / iCCF
•Measurements
LIF / LAF)
•Realtime
performance
update
Evolved to next
“Protocol-Assist” Communications Bus
generation ATCA
hardware for Common OAM&P
increased Switchover, Software update, Audits, Measurements, Data Base, Asserts, Alarms, Security (e.g., IPsec, SSH, Central PW
performance and mgt, OS hardening, etc.)
capacity
Hardware & OS Interface Wrappers
Red Hat Enterprise Linux 5 MontaVista Linux CGE4.0
AdvancedTCA (PICMG3.x) cPSB (PICMG2.16)
Full-Size Compact Full Frame Compact
Solid field proven software and middleware on next generation hardware

134
5450 IP Session Control Function (5450 ISC)
Scalable SIP Session Control
PDU
• Performance & Modularity
- ATCA PICMG 3.1 based solution
- Platform used by many ALU products
- In-house design for most components
- ~ 5K shelves and 40K blades already deployed
- Each blade has two Quad-core processors (IMS 9.2) 5450 ICS
- Shelves are independent 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ethernet Switch
Ethernet Switch
- 1 pair of blades per shelf for high capacity Ethernet switching
1 pair of blades in shelf providing OAM, FSDB and CTS functions
ShMC ShMC
-
OAM
OAM
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
- 1 to 5 add‘l blade pairs per shelf providing IMS Session Resource
control functionality (P/I/S-CSCF, BGCF)
ATCA
- Grown in 1 pair increments
- Each blade pair supports ~780K residential subs 5450 ICS
1 2 3 4 5 6 7 8 9 10 11 12 13 14
- Single shelf supports ~3.9M subs
Ethernet Switch
Ethernet Switch
- Single cabinet supports ~7.8M residential subs
ShMC ShMC
OAM
OAM
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
• Full redundancy (1+1 within shelf)
• Automatic switchover to standby blade ATCA
• Hot swappable
• In-service growth/degrowth Switching
• ETSI/NEBS compliant Processing – Disk-full
Processing – Disk-less
135
5420 Converged Telephony Server (5420 CTS)
PDU
• Performance & Modularity
- Same ATCA platform as used for 5450 ISC
- Each blade has two Quad-core processors (IMS 10.0)
- Shelves are independent
- 1 pair of blades per shelf for high capacity Ethernet switching
5420 CTS
- 1 pair of blades in shelf providing OAM, FSDB and CTS functions 1 2 3 4 5 6 7 8 9 10 11 12 13 14
1 to 5 add‘l blade pairs per shelf with FSDB and CTS
Ethernet Switch
Ethernet Switch
-
OAM + FSDB + CTS

OAM + FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
- Each blade pair supports ~850K residential subs
ShMC ShMC
- Single shelf supports ~5M subs
- Single cabinet supports ~10M residential subs
ATCA
• Full redundancy (1+1 within shelf) 5420 CTS

1 2 3 4 5 6 7 8 9 10 11 12 13 14
• Automatic switchover to standby blade
Ethernet Switch
Ethernet Switch
OAM + FSDB + CTS
OAM + FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
FSDB + CTS
• Dynamic subscriber-to-blade assignment when
ShMC ShMC
using Centralized Subscriber DataBase (CSDB)
• Hot swappable
• In-service growth/degrowth ATCA
• ETSI/ NEBS compliant
Switching
Processing – Disk-full
Processing – Disk-less
136
5420 Service Continuity Gateway (5420 SCG)
5420 SCG shares a common software load with 5420
CTS, 5450 ISC, 5060 ICS, etc. PDU
ALU Linux Control Platform (LCP) components
• IMS Call Server (Card name: NSCG)
- B2BUA and call processing
• Registered sub DB
- Per subscriber registration data
• SS7
- SCCP/SIGTRAN M3UA interface for ANSI-41/ETSI/WIN/MAP/CAP interfaces
• OA&M Server
- Management interfaces for OA&M
- aka Management Interface Agent (MI-Agent)
SCG (ATCA- SCG R8
Rouzic) (ATCA-Molene)
Subscriber Capacity/ ~1.4M ~7.2M

Cabinet (two chassis) (two chassis)
Availability 3Q10 1H11
OAM Server
OAM Server
•Traffic Assumption -- 100% of the subscribers are IMS registered
137
5420 PCM Overview
- Enables end user control and management of CTS based features

- Web browser option
- PC Client option
- Integrates with CTS to expose APIs for user several user interface
options
- Also includes APIs to other IMS Apps Servers
( PS/XDMS, MMIM, etc )
- PCM 7.0 Available on commercial rack mount
server – HP DL380 G6
- Capacity
- 2.0 BHCA: A-node: 600K subs, D-node 1M subs ( est )
- 1M subscribers, geo-redundant
- 4 A + 2 D nodes
- Approx 3M subs per cabinet
- Designed for 99.999% reliability
138
5020 MGC-8 overview (Today)
Future-Proof Investment
- Multiple Applications Support
- NGN Class 4 Local, Access, and Toll Tandems
- CDMA Gateway MSC (GMSC)
- IMS Media Gateway Control Function (MGCF)
- Interconnection Border Control (IBCF)
- Multi-Protocol Support for legacy and converged
network operation
- Seamless migration from legacy TDM to VoIP to
Highly Scalable Converged IMS on same platform
- Up to 7 processor pairs per chassis for call processing AT&T

- Scales up to 4M BHCA for Class 4 configuration
5 9’s Reliability
- No single point of failure
- In-service SW upgrades
- Failovers with no loss of standing calls or billing
records
- Geographic redundancy available
139
5060 MGC-8 overview (2H2010)
Future-Proof Investment
- Multiple Applications Support
- NGN Class 4 Local, Access, and Toll Tandems
- CDMA Gateway MSC (GMSC)
- IMS Media Gateway Control Function (MGCF)
- Interconnection Border Control (IBCF)
- Multi-Protocol Support for legacy and converged
network operation
- Seamless migration from legacy TDM to VoIP to
Converged IMS on same platform
Leveraging ATCA
- MGC-8 Features on an Industry Standard ATCA Platform
- Leverages Common Hardware and Procedures with other IMS
Network Elements (5450 ISC, 5060 ICS, 5420 CTS, etc)
- Opportunity for equipment co-residency
- Planned Capacity Greater than ALGP Platform
Availability:
- Mid 2010 for trials, Deployment with IMS 9.0
140
7510 Media Gateway overview
7510 Media Gateway
• 1500+ units shipped
worldwide
Circuit Ports N+1
Packet Ports N+1

IP/TDM
IP/TDM switch
Circuit switch
Packet Ports
Packet Ports
Packet Ports
Packet Ports
Circuit Ports
Circuit Ports
Circuit Ports
Circuit Ports
Media N+1
Control
Control
Media
Media
Media
Media
Media
• 15 MGCs supported
Ports
• 120 – 32,000 DS0 IP-TDM
• 32,000 sessions IP-IP CIMs MCMs SCMs, SFMs MCMs PIMs
Sample configuration (TGW)

• Purpose-built for IP media networking; flexible; low TCO
• IP-to-TDM, IP-to-IP, TDM-to-TDM (zero latency)
• Rich CODEC suite (G7xx, AMR, GSM, EVRC-x ,G.728, HD-
VoIP)
• Multiprotocol, full standard profiles
(H.248 Mn/Ia, SIGTRAN IUA/MxUA, SIP 7515)
• Strong silicon application accelerators (IPsec,
ATCA AMC daughter boards, and so on)
• NEBS, CE, MII and national certifications
Superior flexibility and cost efficiency to support traffic growth and service innovation
141
5900 Media Resource Function (5900 MRF)
• Provides advanced media functions such as:
- Fixed audio and video announcements
- Variable audio announcements
- IN-type variable parts support (price, duration, date, time, number, integer)
- Channels mixing for audio conferencing purpose
- RTP streams duplication for legal intercept (audio and video)
- Text-to-speech (option)
- RTSP Audio and Video streaming
• DTMF detection
• Codecs:
- Audio: G.711 a/-law, AMR-NB (all bit rates), G.726, G.729A, EVRC, EVRC .0, G.722.2
(AMR-WB)
- Video: H.263, H.264
• Various HW platforms to server individual customer need
• Can be pooled for high availability
142
VitalQIP® IP Address Management Solution
143
VitalQIP Key Features
•Full IP Management Software •High Availability
- Holistic IP Network View - DHCP Failover, DNS master/slaves
- Manage DNS domains, DHCP scopes, •Extend Management Capabilities
IP networks, subnets and objects
- Audit Manager, Services Manager,
- Manage IP network and DHCP scope SNMP Module, Network Allocator,
utilization Usage Billing Interface, API Toolkit,
AutoDiscovery, Workflow Manager,
•Market Proven Scalability Registration Manager, ENUM, DHCP
- Millions of IP addresses Rules Manager
- Hundreds of thousands of domains • Windows 2000/2003 Support
•Industry Leading Performance - Continuing support of Microsoft W2K
DNS/DHCP Servers
- Highest Performing DHCP Server
- Active directory support integration
- Exodus Labs certified
•Usability
•Security
- Simplifies creation and tracking of
- Administrator access security DNS and DHCP information
- Secure configuration pushes - Variety of GUIs simplifies information
- Secure DNS updates entry and formatting
144
Charging call flows in SRVCC context
Alcatel-Lucent implementation
145
Scope (1/2)
• The subject of this presentation is the call flows for charging (online and offline) in the
context of SRVCC with Alcatel-Lucent LTE-IMS solution
- When the call is established
- When the user moves from LTE to CS
• The same PGW is considered for data (IMS based data i.e. IM, chat, RCS like
applications) and voice
• The data like internet, video streaming, … without IMS is not considered
• In the following call flows, we consider that the Attach procedure has been done. As a
consequence, the default bearer (allowing the ‗always on‘ connection) as well as the
SIP signalling dedicated bearer has been created.
• QCI 5 is assigned to this bearer for SIP signalling so that it gets a higher priority than
the default bearer carrying the usual traffic for Internet-access.
• The Register message is vehiculed on this bearer. In consequence, the following call
flow assumes the SIP Registration has been done.
• On the IMS APN, a dedicated bearer is established dynamically at voice call setup and
released at voice call termination using interactions with the P-CSCF and PCRF (Rx
interface) to apply the dynamic PCC rules
• 3 legs have to be considered:
- leg 1 between the calling UE and the SCC AS through the EPC (the user is in LTE network)
- leg 2 between the SCC AS and the (remote) called party
- leg 3, after the HO, between the calling UE and the SCC AS through the MSC server/MGCF
146
Scope (2/2)
• 3 levels of charging information could be grouped (correlated) to provide a unique CDR for
end-to-end session to Billing, by using correlation id exchanged between different levels
• The same should be applied in online charging using same charging group avoiding to
make separated accounts reservation at each different level
• Here is the list of correlation identifiers exchanged & inserted within CDR:
- Intra-level correlation
 Bearer Domain: LTE Charging (GCID) :
 GCID is generated by the PGW at bearer Context activation
 SGW & PGW shares same GCID
 Session Domain: including Application Servers
 IMS Charging ID (ICID) transferred all along SIP session between NE.
 ICID is generated by the P-CSCF, MGCF, AS (Rule : first node creates ICID)
- Inter-level correlation :
 3GPP provides mechanisms to enable operators for PS domain and IMS Domain CDR doing
a correlation: during session establishment PGW and P-CSCF exchange GCID and ICID.
Then GCID and ICID are conveyed within the signalling part to feed all IMS NE
- Inter-network correlation used either for interconnect billing or reconciliation (roaming not shown here):
 Inter-operator Identifier (IOI): Origin-IOI and Term-IOI
• A first ChargingID or GCID is allocated for the access part (LTE). An ICID is created by the
P-CSCF for the charging session for the network part (IMS)
• A second GCID will be created with the dedicated bearer used for the voice traffic
• Cf 32.260 Chapter 6.3.1.1, GCID is provided from following AVP: 3GPP-Charging-Id AVP
included in PS-Information AVP
147
Voice Call Handling -VoLTE
Call establishment – MO from LTE user to an IMS-user served by different S-CSCF (1)
S-CSCF1/
eNB MME SGW PGW PCRF P-CSCF CDF/OFCS TAS SCC AS OCF/OCS UE2
IMS-GWF
Call set- Service request & GCID1 created for ICID is created for this
up authentication the signalling session (network part)
UL data (SIP Invite) Invite (caller ID) Invite Invite (caller ID)
Invite (called ID)
Invite
Ro: CCR-E for CLIP*
Invite
Ro: CCA-E
Ro: CCR-I for SIP session
Ro: CCA-I S-CSCF2 not
Invite (called ID) represented,
180 Ringing CDR created
with this
180 Ringing
entity
180 Ringing
180 Ringing 180 Ringing 180 Ringing
180 Ringing
Policy decision: QoS and Rx: AAR (ICID)
charging (PCC rule)
Gx: RAR
Allocate S1 and radio Bearer

for RTP dedicated bearer
Create Bearer Request

Gx: RAA Rx: AAA In green: online charging
Radio procedures for the
creation of the dedicated
bearer
In blue: offline charging
Create Bearer Response GCID2 created
*other
supplementary
services are
possible
148
Voice Call Handling -VoLTE
Call establishment – MO from LTE user to an IMS-user served by different S-CSCF (2)
S-CSCF1/
eNB MME SGW PGW PCRF P-CSCF CDF/OFCS TAS SCC AS OCF/OCS UE2
IMS-GWF
All IMS
200 OK messages
Ro: CCR-U for IMS session update not shown
(e.g.
Ro: CCA-U PRACK)
Linked to the Rf: ACR Start

remote leg Rf: ACA
200 OK
Rf: ACR Start Alcatel-Lucent
solution is
Rf: ACA
200 OK flexible to
offer several
Rf: ACR Start configurations
Rf: ACA for the
creation of the
200 OK
CDR
Rf: ACR Start
Rf: ACA
200 OK
Rf: ACR Start

Rf: ACA
200 OK
Rf: ACR Start

Linked to LTE leg
Rf: ACA
200 OK 200 OK 200 OK
In green: online charging
In blue: offline charging
149
150
151
152

IMS For LTE

Uploaded by

Copyright:

Available Formats

IMS For LTE

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

IMS For LTE

Uploaded by

Copyright:

Available Formats

1

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

You, of course, get credit for

Voice and SMS in LTE

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Circuit-Switched Fallback (CSFB) Dual-Transceiver Handsets (SVLTE)

IMS with GSMA VoLTE

• This is the widely accepted

- Voice service may be controlled using IMS servers and applications

- Voice service to be available while roaming on other LTE networks

- No additional requirements imposed on roaming partner networks

Attractive as a means of re-using all

Simultaneous UE maintains simultaneous Offered in the UE at the expense of

• GSM Association (GSMA) sponsored IR.92 profile is an industry effort to

Option for data only devices

VoLTE with IMS VoLTE IMS VoLTE

IMS VoLTE/VoIP IMS VoLTE/VoIP

LTE with Dual Tx IMS VoLTE with IMS VoLTE with

Voice and SMS via

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

SGW PGW SGW PGW

• If a UE requires CSFB and CSFB is Figure A.5-1 from 3GPP TS 23.221:

restrictions as in today‘s roaming Fail or Success with

the UE will disable E-UTRAN Success with no

capability and select a CDMA “SMS-only” indication

• Further details can be found in UE uses CSFB UE stays in current

3GPP TS 23.221 Annex A

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

PDN Circuit Voice

• ―CSFB‖ Dual Receiver for LTE data and 1x CS Voice

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

Enhanced Packet Core

• Voice Call Continuity is used to provide session continuity from LTE to

PDN • Service restrictions

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

• Supplementary Services provisioning and status are sync‘ed between the

Enhanced Packet Core

Packet Voice IMS Signaling

Enhanced Packet Core

UE Initiates call using SIP signaling

Enhanced Packet Core

• Support of multiple trigger options allows some services (e.g., CRBT) to

Enhanced Packet Core CSCF

• Features initiated in origination dial string (e.g., CCW, extension dialing)

Enhanced Packet Core

• All features from CDMA MSC while in CDMA Mode

Enhanced Packet Core

Enhanced Packet Core

Enhanced Packet Core

• Add support for anchoring CDMA originations through IMS

• CDMA Roaming for VoLTE/CDMA users

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

* Non-Optimized eHRPD HO supports Single or Dual Radio devices. However, for

(Optimized) existing equipment

Evolved Packet Core

LTE supports VoIP and SCG

3GPP PCRF HSS

Evolved Packet Core