voice over lte
Post on 07-Nov-2014
242 Views
Preview:
DESCRIPTION
TRANSCRIPT
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Voice and SMS in LTE Technical Overview
Speaker Name Date
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
3
AGENDA
1. Introduction
2. Solution Architecture Overview
3. End-User Services
4. Regulatory Services
5. Provisioning / migrating subscribers
6. Roadmap
7. Supporting Sections
You will have to modify the agenda
based on the sections you include in
your talk
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
1. Introduction
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
5
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:
• 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.
Circuit-Switched Fallback (CSFB)
• This method drops the UE from LTE to CDMA 1x any time a voice all is active
Dual-Transceiver Handsets (SVLTE)
• Approach requiring specialized handsets has traction among CDMA operators
IMS with GSMA VoLTE
• This is the widely accepted target architecture for voice in LTE
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
6
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
7
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
8
Options for Supporting Voice and SMS with LTE
There are three options we can discuss for voice/SMS services with LTE:
Option Description Comment
CS Fall-back
(CSFB)
Attractive as a means of re-using all
the CS infrastructure. Note this
option precludes simultaneous LTE
data and voice (different carriers)
UE is registered in LTE and is paged
over LTE but takes call in CDMA
Circuit mode
Voice over LTE
(VoLTE)
Uses a standard 3GPP IMS and LTE
features to improve voice capacity
Continuity Options:
• Hand-down to CDMA circuit
domain
• LTE <-> eHRPD PS HO required if
VoIP over eHRPD is supported
Call control for native LTE voice and
SMS service is provided by IMS. IMS-
based call control can be provided in
the CDMA domain via the IMS
anchoring for calls originated in
CDMA circuit mode.
Simultaneous
Voice and LTE
(SVLTE)
Offered in the UE at the expense of
greater complexity and shorter
battery life.
UE maintains simultaneous
registration on LTE network for data
and legacy network for voice/SMS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
9
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
10
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
11
Primary Migration strategies for Voice and SMS services: Industry Trends
Initial LTE launch Data modems only.
Deploy 1H2011
Service Rollout Including smartphones; earliest
test 1H2011; deploy 2H2011
Mass market Full range of terminals; earliest
test 2H2011; deploy 1H2012
Option for data only devices
SVLTE
Voice and SMS via S102 CSFB
IMS VoLTE (complete LTE
coverage)
VoLTE with
DRVCC SRVCC
IMS VoLTE with S102 SRVCC CDMA
LTE only Data only devices
IMS VoLTE/VoIP over eHRPD
IMS VoLTE/VoIP over eHRPD
Network optimization Full range of terminals
2013+
IP-Optimized solution
IP+Circuit solution
LTE and eHRPD Data only devices
IMS VoLTE (complete LTE
coverage)
IMS VoLTE with S102 SRVCC CDMA
LTE and eHRPD Data only devices
LTE and eHRPD Data only devices
LTE with Dual Tx CSFB
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
2a. Solution Architecture Overview: Circuit-Switched Fallback
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
13
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
- Operators building LTE network and choosing SMS over S102 CS Fallback and SMS over
S102 are both defined in
3GPP TS 23.272. + 3GPP2
C.S0097
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
14
CDMA 1x
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME
CDMA 1X
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME
CS Fallback - High Level Architecture
While carrying data only
- Handset uses LTE network where possible to achieve highest throughput
- Handset served by an MSC in legacy network for voice and SMS
- Incoming voice calls paged over S102 interface from MSC to MME, similar to Gs interface in GPRS
- SMS delivered over S102 – without requiring inter-RAT handover
No Simultaneous Voice + Data
- Handset falls back to legacy circuit coverage for voice
- Data sessions suspended
CSFB Tradeoff
- Re-uses legacy circuit infrastructure
- But at the cost of Inter-RAT handover per voice call, and suspended data sessions
Data
Data
Circuit Voice
Paging/SMS
New interface “S102” from MSC
to MME
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
15
CS Fallback: Roaming Considerations
• If a UE requires CSFB and CSFB is available in a visited network, roaming voice service operates in the visited network with the same restrictions as in today‘s roaming environment.
• If a UE requires CSFB and CSFB is not available in a visited network, the UE will disable E-UTRAN capability and select a CDMA network
• Further details can be found in 3GPP TS 23.221 Annex A
UE is set to CS
Voice only
Success with no
“SMS-only” indication
and no “CSFB Not
Preferred” indication
UE checks for
voice centric or
data centric setting
UE stays in current
RAT
Data centric
Voice centric
UE reselects to
other RATUE uses CSFB
Fail or Success with
“SMS only” indication
or Success with
“CSFB Not Preferred”
indicationUE initiates a
combined EPS/
IMSI attach
procedure
Figure A.5-1 from 3GPP TS 23.221:
UE behavior for CS Voice only
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
16
CS Fallback Benefits, Costs, and Limitations
• Benefits
• Provides mechanism for basic, transparent voice service to LTE handsets
- Applicable to voice handsets if LTE is deployed in advance of IMS
- Applicable to LTE roamers whose home 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
• Limitations
• CSFB procedures in eUTRAN require per-call migration to CDMA
- Increases call setup delay
- Range of figures depending on network conditions
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
2b. Solution Architecture Overview: Simultaneous Voice and LTE (SVLTE)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
18
CDMA 1x
BTS
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME
Simultaneous (Circuit) Voice and LTE (SVLTE)
• 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
Circuit Voice
Data
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
19
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
- Simultaneous 1x Voice with eHRPD (EV-DO) Data
- Qualcomm 2-chip initial solution: ―Fusion‖
- 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
- Standards-based device with separate receiver for LTE and CDMA
- The device shown at right has a single Tx, but Separate receivers
for LTE and eHRPD
- A Dual Tx device may be capable of simultaneous 1x Voice with LTE Data
Rx/Tx Rx/Tx
DO/ LTE
1x
Rx
LTE 1x / DO
Tx Rx
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
2c. Solution Architecture Overview: Voice over LTE
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
21
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
22
IMS Core
7510 MG
5450 ISC
5060 MGC-8
5900 MRF
5420 PCM
5420 CTS (TAS)
VoLTE Alcatel-Lucent Products
Enhanced Packet Core (Voice + Data)
5780 DSC E-UTRAN
94xx eNB
7750 PGW 7750 SGW
9471 MME
eHRPD
eRNC BTS
BTS
8650 SDM
PSTN/PLMN
MSC
eHRPD
HSGW
Elements
added for IMS
CDMA 1X
5420 SCG
8615 IeCCF 8610 ICC
1357 ULIS
VitalQIP
5110 SMS C
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
23
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
24
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)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
25
CDMA
HSGW
MSC
CS Network
PDN
IMS TAS
MGW MGCF
VoLTE – user plane aspects Two party calls
• VoLTE to VoLTE call
- Each UE has dedicated signaling connection to own S-SCCF and TAS (may be shared)
- Direct packet voice connection between two parties, routed via own PGW (may be shared)
- Each UE has dedicated QCI=1 bearer established for voice service
- If UE not on same network then user plane carried over inter-operator interconnection (normally via GSMA sponsored IPX)
• VoLTE to CS call
- LTE connected UE has dedicated signaling connection to own S-CSCF and TAS
- CS connected UE has dedicated signaling connection to MSC
- During call MSC and IMS linked together using ISUP via MGCF (or using SIP if MSC supports IP)
- Media path connected via MGW under control of MGCF
- LTE connected UE has dedicated QCI=1 bearer established for voice service
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC AS TAS
LTE to LTE call
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
E-UTRAN
eNode B PGW SGW
MME SCC
VoLTE to mobile CS
CDMA
HSGW
MSC
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
26
VoLTE – user plane aspects Multi-party calls
• VoLTE to VoLTE conference call
- Each UE has dedicated signaling connection to own S-SCCF and TAS (may be shared)
- Media path from each UE directed to conference bridge hosted by MRF (Media Resource Function)
- Each UE has dedicated QCI=1 bearer established for voice service
• VoLTE to CS call
- Each UE has dedicated signaling connection to own S-SCCF and TAS (may be shared)
- Direct packet voice connection between two active parties, routed via own PGW (may be shared)
- Each active UE has dedicated QCI=1 bearer established for voice service
- Media path for held UE directed to announcement service hosted by MRF (Media Resource Function)
- Held UE has dedicated QCI=1 bearer established for voice service
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC AS TAS
LTE to LTE conference call
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
MRF
+
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC AS TAS
LTE to LTE call with 3rd party on hold
MRF
CDMA
HSGW
MSC
CDMA
HSGW
MSC
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
27
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
28
VoLTE handover to legacy mobile network Using PS handover (towards eHRPD only)
CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC TAS
Before…
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
• Approach
- Simple PS handover triggered by MME involving HSGW and S/PGW
• Service restrictions
- Full IMS services maintained during handover and remainder of call
- Gm signaling interface available
- PS Voice bearer support required
- VoIMS is not viable over 1x
CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC TAS
… after
MGW
MGCF
MGW
MGCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
29
VoLTE handover to legacy mobile network Using SRVCC (―B‖ party in CS network)
… after
CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC
TAS
• Approach
- SRVCC mechanism triggered by MME, involving MSC and SCC
- Parallel PS handover used for data services
• Service restrictions
- (Most) IMS services maintained during handover and remainder of call
- Available over all mobile networks with SRVCC roaming agreements
- Requires SRVCC support in visited network
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
Before… CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC
TAS
MGW
MGW
MGCF
MGCF
Figures are simplified
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
30
VoLTE handover to legacy mobile network Using SRVCC (―B‖ party in LTE)
… after
CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC
TAS
• Approach
- SRVCC mechanism triggered by MME, involving MSC and SCC
- Parallel PS handover used for data services
• Service restrictions
- (Most) IMS services maintained during handover and remainder of call
- Available over all mobile networks with SRVCC roaming agreements
- Requires SRVCC support in visited network
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
Before…
MGW
MGCF
CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC
TAS
MGW MGCF
Figures are simplified
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
31
VoLTE handover to legacy mobile network Using DRVCC (―B‖ party in CS network) – No S102
… after
CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC
TAS
• Approach
- DRVCC mechanism triggered by UE, UE initiated new HO leg in CDMA
- Parallel PS handover used for data services
• Service restrictions
- (Most) IMS services maintained during handover and remainder of call
- Available over all mobile networks
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
Before… CDMA
HSGW
MSC
CS Network
PDN
E-UTRAN
eNode B PGW SGW
MME IMS SCC
TAS
MGW
MGW
MGCF
MGCF
Figures are simplified
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
VoLTE and CDMA Integration Implementation Options
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
33
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
34
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)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
35
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options – IMS Service Delivery in LTE (Baseline)
MGW
CSCF
MGCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
TAS
Packet Voice IMS Signaling
Call routed to B-party
IP Bearer is set up
TAS applies originating features
UE Initiates call using SIP signaling
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
36
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options – IMS Service Delivery in LTE to PSTN
MGW
CSCF
MGCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
PSTN/PLMN
TAS
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
Call routed to MGCF (B-party in PSTN)
MGCF signals PSTN
MGCF instructs MGW to set up PSTN connection
IP Bearer is set up
TAS applies originating features
UE Initiates call using SIP signaling
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
37
Service Delivery Options – 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)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
38
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options –
IMS Service Delivery in eHRPD Gm Method with eHRPD Bearer
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
eHRPD
eRNC BTS
MRF
PCM
HSS/HLR
PSTN/PLMN MSC
Core
HSGW
TAS
MGCF
Circuit Voice Packet Voice IMS Signaling Packet Data Circuit signaling
Call routed to MGCF (B-party in PSTN)
MGCF signals PSTN
MGCF instructs MGW to set up PSTN connection
IP Bearer is set up
TAS applies originating features
UE Initiates call using SIP signaling
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
39
Service Delivery Options – 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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
40
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
41
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
42
eHRPD
RNC BTS
BTS PSTN/PLMN
MSC
eHRPD
HSGW
CDMA
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options –
Limited IMS Service Delivery in CDMA: WIN Anchoring Originating Call
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
MSC initiates call to PSI DN
MSC has originating attempt trigger for UE pointing to
SCC AS. Sends trigger with dialed digits.
UE Initiates call to MSC
MGCF signals PSTN
MGCF instructs MGW to set up PSTN connection
TAS applies originating features
Call routed to MGCF (B-party in PSTN)
SCC AS saves dialed digits and returns PSI DN
SCC AS sends INVITE to TAS with saved dialed digits
MGCF routes call to SCC AS
MGCF sets up incoming circuit bearer
MGCF
TAS
SCC AS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
43
Service Delivery Options –
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
44
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options – Local Service Delivery in CDMA: MSC Provides Services
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
PSTN/PLMN
eHRPD
RND HSGW
TAS
MGCF
CDMA
BTS
SCC AS
MSC
UE Initiates call to B-party
MSC routes call to B-party
Circuit bearer is completed
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
45
Service Delivery Options –
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
46
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options – WIN Anchoring for Incoming Calls
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
PSTN/PLMN
TAS
MGCF
CDMA
BTS
SCC AS
H-MSC
Call initiated to UE at Home MSC
H-MSC sends triggered message to SCC AS
which saves call info and returns a PSI DN
MSC sets up a call to PSI DN
MSC
SCC AS sends INVITE to TAS with
saved dialed digits
MGCF routes call to SCC AS
MGCF sets up incoming circuit bearer
TAS applies terminating features Call is routed back to SCC AS for domain
selection
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
47
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options – Domain Selection to CDMA
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
PSTN/PLMN
TAS
MGCF
CDMA
BTS
SCC AS
H-MSC
MSC
TAS applies terminating features
Call is routed to SCC AS for domain
selection
Call routed into IMS and to TAS
SCC AS does not find UE registered in IMS and
queries the HLR for routing digits
HLR returns routing digits
Call routed through MGCF to routing
destination
Call delivered to UE
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
48
Enhanced Packet Core (Voice + Data)
IMS Core
Service Delivery Options – Domain Selection to LTE
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
PSTN/PLMN
TAS
MGCF
CDMA
BTS
SCC AS
H-MSC
MSC
TAS applies terminating features
Call is routed to SCC AS for domain
selection
Call routed into IMS and to TAS
SCC AS does find UE registered in IMS and
routes the call through the S-CSCF
S-CSCF routes call to UE Contact Address
Bearer path is allocated and connected
Call delivered to UE
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
49
Service Delivery Options –
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
50
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).
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
51
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
52
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
VoLTE Handoff Options
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
54
VoLTE Handoff Options
* Non-Optimized eHRPD HO supports Single or Dual Radio devices. However, for
VoLTE HO, separate receivers for LTE and eHRPD may improve handoff delay.
Approach Destination Network
Enhancement Required?
Device Availability
Non-Optimized eHRPD
eHRPD VoIP None Dual Receiver or
Dual Radio * Today
Optimized eHRPD eHRPD VoIP S101
Single or Dual Radio
C.S0087 Tunnel
Future
1x DRVCC 1x CS VCC App
Server Dual Radio Future
1x SRVCC 1x CS S102 Single Radio
C.S0097 Tunnel Future
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
55
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
56
1xEV-DO
(HRPD and eHRPD)
3GPP2
LTE
3GPP
IMS
Interworking LTE with EV-DO via eHRPD (Optimized)
eNode B
Packet
Switched Core
AAA
HSS PCRF
Evolved Packet Core
SW upgrade on existing equipment
Legacy EV-DO AT
LTE UE
HA
Internet / Intranet
MME
SGW PDN
GW
eHRPD
Potential future SW upgrade on existing
equipment
S101
With addition of “Optimized Handoff” with S101 signaling for pre-registration and handoff,
and S103 for data forwarding, handoff performance improves
S103
RNC / eRNC
BTS
LTE-eHRPD
PDSN
HS GW
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
57
LTE
3GPP
LTE VoIP “DRVCC” Handoff to CDMA 1x Circuit Switch Voice (without S102)
eNode B
CDMA2000 1X
3GPP2 Legacy 1X AT
LTE UE
Circuit
Switched
Core
(Voice)
PSTN
ANSI41 Voice
Channels
MSC/
BSC
BTS
HSS PCRF
Evolved Packet Core PDN
GW
SGW
MME
LTE supports VoIP and Hands Off to CDMA2000
1X Circuit Network outside of LTE Coverage
LTE - 1X AT IMS
SCG MGC/MGW
Internet / Intranet
HLR
IMS SCG VCC application allows dual radio LTE VoIP services to hand off to 1X CS Voice without S102.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
58
VCC : IMS to CS Handover Call Flow – “DRVCC”
Circuit Bearer Path
Signaling Path
BS
MSC
IMS domain
CSCF
SCG
CTS TAS
Broadband Access
PSTN
MGW
MGCF MGW
MGCF
LTE RAN & EPC
1) Existing VoLTE call between the Handset on LTE and PSTN user.
2) Handover Trigger
3) 1X Orig 4) INVITE
5) VCC updates the IP addresses for the existing call to connect to the new, incoming call MGW.
6) BYE pCSCF
VoIP Bearer Path
VCC App Server
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
59
LTE
3GPP
LTE VoIP SRVCC Handoff to CDMA 1x Circuit Switch Voice (with S102)
eNode B
CDMA2000 1X
3GPP2 Legacy 1X AT
LTE UE
Circuit
Switched
Core
(Voice)
PSTN
ANSI41 Voice
Channels
MSC/
BSC
BTS
HSS PCRF
Evolved Packet Core PDN
GW
SGW
MME
LTE supports VoIP and Hands Off to CDMA2000
1X Circuit Network outside of LTE Coverage
LTE - 1X AT
S102
IMS SCG VCC application with S102 allows LTE VoIP services to hand off to 1X CS Voice.
S102 is used for Hand Off Signaling
IMS
SCG MGC/MGW
Internet / Intranet
HLR
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
60
VCC : IMS to CS Handover Call Flow - SRVCC
Circuit Bearer Path
Signaling Path
BS
MSC
IMS domain
CSCF
VCC App Server
CTS TAS
Broadband Access
PSTN
MGW
MGCF MGW
MGCF
LTE RAN & EPC
1) Existing VoLTE call between the Handset on LTE and PSTN user.
2) Handover Trigger
3) 1x Orig
4) INVITE
6) VCC reconfigures the IP addresses for the existing call to connect to the new, incoming call.
7) BYE pCSCF
VoIP Bearer Path
S102
5) HO Command
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
62
BTS
CDMA
Enhanced Packet Core (Voice + Data)
IMS Core
Single Radio Voice Call Continuity PS to CS (E-UTRAN/CDMA SRVCC)
MGW
CSCF
PCRF E-UTRAN
eNode B
PGW SGW
MME
MRF
PCM
HSS/HLR
PSTN/PLMN
TAS
MGCF
MSC
UE reports signal strength to eNB
eNB decides HO is required and sends request to MME
MME sends request to MSC enhanced with S102 interface*
MSC prepares handover, signals BTS and initiates call to SCC AS using STN-SR MGCF instructs MGW to update IP connection
TAS forwards to MGCF
SCC AS sends RE-INVITE to TAS with new bearer IP
MGCF routes call to SCC AS
MGCF sets up incoming circuit bearer
In parallel to IMS processing the MSC sends HO
response back to MME
UE tunes to new network
SCC AS
UE in LTE with established call to PSTN subscriber
UE measures signal strength
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
63
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
VoLTE and topologies for large geographic regions Where the speed of light is perceptible to the end user….
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
65
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)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
66
Topology 1: Dynamic Allocation Model
LTE TAS
(CTS)
EPC
5450 ISC
S-CSCF
A-BGF
P-CSCF
PCRF
P-GW
S-GW
Region X SCC AS
(SCG)
I-CSCF
MSC
MSC
.
.
.
VitalQIP DNS
LCP DNS
UE1
LTE TAS
(CTS)
EPC
5450 ISC
S-CSCF
PCRF
P-GW
S-GW
Region Y (UE Home) SCC AS
(SCG)
I-CSCF
MSC
MSC
.
.
.
VitalQIP DNS
LCP DNS
A-BGF
P-CSCF
UE1 AS and IMS Core
Depends on region
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
67
CTS User Profile Data Options Primary/Protect & CSD
. . .
. . .
Other
Apps
App
Server
App
Server
App
Server
App
Server
App
Server
Sub A Data Sub B Data Sub C Data Sub D Data
App
Server
App
Server
App
Server
HSS
Sub A Data Sub B Data Sub C Data Sub D Data Sub E Data Sub F Data Sub G Data Sub H Data
•Primary/Protect Option CSD Option
Sub A Data Sub B Data Sub C Data Sub D Data
Sub E Data Sub F Data Sub G Data Sub H Data
Sub E Data Sub F Data Sub G Data Sub H Data
Geo-redundant Pair
Geo-redundant Pair
Centralized Subscriber Database and Dynamic CTS Assignment
With this option, CTS specific service data for a subscriber is stored as repository (transparent) data in the HSS
Any CTS can retrieve a copy of a subscriber’s data from the HSS and process calls to/from the subscriber
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
68
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).
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
69
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
70
Topology 2: Home IMS/AS and Home P-CSCF
LTE TAS
(CTS)
EPC
5450 ISC
S-CSCF
A-BGF
P-CSCF
PCRF
P-GW
S-GW
Region X SCC AS
(SCG)
I-CSCF
MSC
MSC
.
.
.
VitalQIP DNS
LCP DNS
UE1
LTE TAS
(CTS)
EPC
5450 ISC
S-CSCF
PCRF
P-GW
S-GW
Region Y (UE Home) SCC AS
(SCG)
I-CSCF
MSC
MSC
.
.
.
VitalQIP DNS
LCP DNS
A-BGF
P-CSCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
71
Topology 3: Home IMS/AS, Regional P-CSCF
LTE TAS
(CTS)
EPC
5450 ISC
S-CSCF
A-BGF
P-CSCF
PCRF
P-GW
S-GW
Region X SCC AS
(SCG)
I-CSCF
MSC
MSC
.
.
.
VitalQIP DNS
LCP DNS
UE1
LTE TAS
(CTS)
EPC
5450 ISC
S-CSCF
PCRF
P-GW
S-GW
Region Y (UE Home) SCC AS
(SCG)
I-CSCF
MSC
MSC
.
.
.
VitalQIP DNS
LCP DNS
A-BGF
P-CSCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
72
Voice Gap Call Flow w/ Transport Delay Consideration (LTE UE1 to LTE UE2)
MSC+MG
CFI-CSCF SCC AS1 S-CSCF Orig TAS S-CSCF S-CSCF2 Term AS S-CSCF2 SCC AS2 S-CSCF2
Invite (STN-SR, MGW
SDP) Invite (STN-SR, 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)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
ENUM lookup
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)
200 OK (SDP Answer)
P-CSCF
(w/ SBC)
200 OK (SDP Answer)
Re-Invite(MGW SDP)
MGW control
MGW control
MGW control
UE2
v
MGW control
Re-Invite(MGW SDP)
200 OK (SDP Answer)
UE1
v
Call Setup
MSC initiates a call to the Session Transfer
Number for Single Radio (STN-SR). STN-
SR is a provisioned fixed value retrieved
from HSS
Transport Delay
Dynamic Home P-CSCF
Regional P-CSCF
Dynamic Home P-CSCF
Regional P-CSCF
Dynamic Home P-CSCF
Regional P-CSCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
73
Voice Gap Call Flow w/ Transport Delay Consideration (LTE UE1 to PSTN)
MSC+MG
CFI-CSCF SCC AS1 S-CSCF Orig TAS S-CSCF MGCF
Invite (STN-SR, MGW
SDP) Invite (STN-SR, MGW
SDP)Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
ENUM lookup
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
MGW control
MGW control
MGW control
UE1
v
Call Setup
MSC initiates a call to the Session Transfer
Number for Single Radio (STN-SR). STN-
SR is a provisioned fixed value retrieved
from HSS
PSTN
Transport Delay
Dynamic Home P-CSCF
Regional P-CSCF
Dynamic Home P-CSCF
Regional P-CSCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
74
Voice Gap Call Flow w/ Transport Delay Consideration (LTE UE1 to LTE UE2 (3G))
MSC+MG
CFI-CSCF SCC AS1 S-CSCF Orig TAS S-CSCF S-CSCF2 Term AS S-CSCF2 SCC AS2 MGCF
Invite (STN-SR, MGW
SDP) Invite (STN-SR, 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)
Re-Invite(MGW SDP)
Re-Invite(MGW SDP)
ENUM lookup
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)
200 OK (SDP Answer)
MGW control
MGW control
MGW control
UE2
v
MGW control
UE1
v
Call Setup
MSC initiates a call to the Session Transfer
Number for Single Radio (STN-SR). STN-
SR is a provisioned fixed value retrieved
from HSS
Transport Delay
Dynamic Home P-CSCF
Regional P-CSCF
Dynamic Home P-CSCF
Regional P-CSCF
Dynamic Home P-CSCF
Regional P-CSCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
77
SRVCC Voice Gap Estimate Comparison (for home network scenarios with ~40ms one way transport delay) LTE UE1 to LTE UE2
in LTE Coverage
LTE UE1 to PSTN LTE UE1 to LTE UE2
in 3G Coverage
Mean Peak Mean Peak Mean Peak
UE1 and UE2/PSTN
same region
180 275 130 205 175 270
UE1 and UE2/PSTN
across country
220 335 205 265 215 330
LTE UE1 to LTE UE2
in LTE Coverage
LTE UE1 to PSTN LTE UE1 to LTE UE2
in 3G Coverage
Mean Peak Mean Peak Mean Peak
UE1 and UE2/PSTN
home region
190 295 130 205 175 270
UE1 and UE2/PSTN
across country
315 475 210 321 300 450
LTE UE1 to LTE UE2
in LTE Coverage
LTE UE1 to PSTN LTE UE1 to LTE UE2
in 3G Coverage
Mean Peak Mean Peak Mean Peak
UE1 and UE2/PSTN
home region
190 295 130 205 175 270
UE1 and UE2/PSTN
across country
260 395 210 321 300 450
*Assume Border Gateway anchoring/pivoting with P-CSCF (and no media release)
Dynamic AS
Home IMS/AS and Home P-CSCF
Home IMS/AS and Regional P-CSCF
Why does IMS location matter if Bearer is optimized – shortest path? Is assumption that bearer also goes to IMS?
APPLIES for CDMA?
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
78
Other Considerations
Characteristic Dynamic Allocation Home P-CSCF/Home Region
Local P-CSCF/Home region
Voice Gap Most scenarios under 300ms
Some cross country scenarios over 300ms
Most cross country scenarios over 300ms
P-CSCF Selection Dynamic – PGW assisted Static (e.g. provisioned in handset)
Dynamic – PGW assisted
I-/S-CSCF Selection I-/S- always local to P-CSCF
I-/S- always local to P-CSCF
Need mechanism to determine
UE home region (e.g. regional
domain names)
CTS selection Requires CSDB and regional DNS for local CTS assignment
Always assigned in home network
Always assigned in home network
SCG Selection Dynamic allocation based on regional DNS
Always assigned in home network
Always assigned in home network
STN-SR Routing Unique STN-SR to each SCG, could require write to PS/CS HSS
Static STN-SR; requires capacity engineering; resource utilization considerations
Static STN-SR ; requires capacity engineering; resource utilization considerations
What if additional app servers?
Need dynamic allocation for all
Always in home network? Always in home network?
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
79
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
80
Voice Interruption Time (from 3GPP TR 23.856)
UE MSC
MGW
Remotea4.200 OK
b1.HO CMD
Downlink
IMS Bearer before HO
Uplink
a1.Invite
Downlink
SCC ASa3.Answer
a2.OfferMME/eNodB
b2.HO CMD
Uplink
IMS Bearer after HO
b3.Tune to CS
CS Bearer after HO
- 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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
81
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
82
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)
After transfer After transfer
UE
I/S-CSCF,
SCC AS
ATCF
ATGW Before transfer
SN HN
MSC
ServerUE
Before transfer
Gm
Mw
Serving Leg Home Leg
After transfer Remote
End
Access Leg
Remote
Leg
CS radio
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
83
IMS Enhanced Packet Core (Voice + Data)
IMS Core
eSRVCC - IMS Registration
E-UTRAN
eNode B
PGW SGW
HSS/HLR
TAS
MSC
SCC AS
MGW
MGCF
VPLMN HPLMN
MME
Remote UE
• HSS updates the MME/SGSN with the new value of STN-eSR
• SC AS populates the new value of STN-eSR in the HSS user data
P-CSCF
ATCF
• ATCF adds STN-eSR into the REGISTER propagated to the SCC AS
PCRF Impacted Entity
CDMA
BTS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
84
IMS
HSPA
RNC NB
Enhanced Packet Core (Voice + Data)
IMS Core
eSRVCC – IMS Session Establishment
PCRF
E-UTRAN
eNode B
PGW SGW
HSS/HLR
TAS
MSC
SCC AS
MGW
P-CSCF
MGCF
VPLMN HPLMN
MME SGSN
Remote UE
• Remote leg between the SCC AS and the remote UE
• The ATCF inserted in the sig. path. The ATGW may be inserted in the data plane
ATGW
ATCF
Impacted Entity
• Home leg between the ATCF and the SCC AS
• Access leg between UE and ATCF
CDMA
BTS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
85
CDMA
BTS
IMS
HSPA
RNC NB
Enhanced Packet Core (Voice + Data)
IMS Core
eSRVCC – Access Transfer
E-UTRAN
eNode B
PGW SGW
HSS/HLR
TAS
MSC
SCC AS
MGCF
VPLMN HPLMN
MME SGSN
Remote UE
• 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)
P-CSCF
ATGW
PCRF
1. Voice over IMS 2. SRVCC trigger
3. Voice over CS
ATCF
MGW
Impacted Entity
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
2d. Solution Architecture Roaming considerations
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
87
LTE-LTE : Home routed traffic scenario
E-UTRAN
SGW eNB
MME
PGW
S11
S1u S5 SGi
HSS
S1-mme
Data Services
(e.g., VPN, FTP)
S6a
PGW
HPCRF
SG
i
DNS S8
Inter PLMN IP Backbone
HPLMN
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.
DNS
Inter PLMN IP Backbone required GSMA IR.34
Gx Rx
Home operator’s IP
services
PDN GW IP address •HSS IP Address
• PDN GW IP address •APN & Default PDN GW ID (FQDN or IP address) •vplmnAddressallowed =No
VPCRF
S9
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
88
LTE - Local breakout model (new model)
E-UTRAN
SGW eNB
MME
PGW
VPCRF
S11
S1u S5 SGi
HSS
S1-mme
Data Services
(e.g., VPN, FTP)
S6a
HPCRF Rx
DNS
S9 HPLMN
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)
Home operator’s IP
services
•vplmnAddressallowed =yes
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
89
IMS Roaming: P-CSCF in Visited network
E-UTRAN
SGW eNB
MME
PGW
S11
S1u S5 SGi
HSS
S1-mme
Data Services
(e.g., VPN, FTP)
S6a
PGW
HPCRF
SG
i
DNS S8
Inter PLMN IP Backbone IPX
HPLMN
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.
DNS
Gx Rx
P-CSCF
S-CSCF
I-CSCF IMS
P-CSCF
PGW
VPCRF
S9
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
90
IMS Roaming Session Flow
eNode BeNode B
eNode BeNode B
IBCF
IBCF IBCF
IBCF
HSSHSS
B
G
W
B
G
W
I
B
C
F
I
B
C
F
SGW PGW
P-CSCF
S-CSCF
TAS
I-CSCFS-CSCF
TAS
P-CSCF
PGW SGW
Visiting1
Home1Home2
Visiting2
ENUM
ENUM
1
2
3
4
5
6
7
8
910
11
12
13
14
15
16
IPX
Originating subscriber is from Home1 and is roaming in Visiting1
Destination subscriber is from Home2 and is roaming in Visiting2
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
91
Diameter Routing Architecture (as proposed by GSMA)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
92
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.
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
3. End User Services
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
94
Telephony Application
Server
Alcatel-Lucent Offer for Voice Service on IMS Core Elements
Alcatel-Lucent 5420 Converged Telephony Server
(CTS)
Telephony services to any SIP, IP or POTS subscriber, mobile and fixed
Residential services
Business services
PBX trunking
Regulatory feature support
Scalable, Robust
End User Control & Administration
Alcatel-Lucent 5420 Personal Communication
Manager (PCM)
End user self-care and administrator management of call features, call logs, voice mail
Consistent look-and-feel end user interface via standard web browser
Click-to-dial any phone number on any web page
Find me/follow me
Open APIs
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
95
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
96
5420 CTS Feature Packages
• Feature Packages
• Silver Residential/Consumer
- Includes MMTel Features
• Gold Residential/Consumer
• Core Business
• Premium Business
• US Military
• PBX VPN
• A la Carte Features
• Attendant Console
• Deluxe Auto Attendant
• Hunt Group Queuing
• Large Call Limit
• Location Based Services
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
97
5420 CTS Feature Package Silver Residential/ Gold Residential • User Call Services: • Anonymous Call Rejection • Automatic Call Back • Automatic Recall • Call Barring (Outgoing Calls)
- Generalized Category Names - Outgoing Call Barring
• Call Blocking (Incoming Calls) - Incoming - Incoming Intl
• Call Completion to Busy Subscriber - Call Completion to Busy Subscriber - Blocking Completion to Busy Subscriber
• Call Forwarding: - Bearer-Based Call Forwarding - Call Deflection - Call Forwarding Always (CFA) (Variable) - Call Forwarding Busy (CFB) - Call Forwarding Default - Call Forwarding Local - Call Forwarding No Answer (CFNA) - Call Forwarding Password Protected - Call Forwarding Unregistered (CFU) - Call Forwarding to Voicemail (CFVM) - Inhibition of Incoming Forwarded Calls (IIFC)
• Call Hold – Consultation • Call Transfer Features:
- Call Transfer with Consultation - Call Transfer Blind (Local, Network with Dedicated Access Code,
Network from 3-way call) - Call Transfer from 3-way - Timed Reminder on Transfer
• Call Waiting Terminating: - Advanced Endpoints - Flashable Endpoints (INFO Method) - TISPAN Simple Endpoint - Cancel: Per Call, Mid Call, Persistent - Caller ID with Call Waiting
• Calling Line ID Related Features: - Calling Line ID Presentation, Restriction, w/ Override - Connected Line Identity Presentation, Restriction - Calling Name Identification Presentation, Restriction
• Calling Party Category (CPC) • Conference Calling (3-Way, N-Way, Programmable
3-way, TISPAN) • Configurable Feature Codes (NANPA Vertical Service
Codes) • Device Extensions • Dial Code Feature Status Interrogation • Do Not Disturb (DND) • Dual Mode Service/ Single Number Service • End Point Support
- Advanced End-Point - Flashable End-Point (INFO Method) - TISPAN Simple End-Point
• Hotline • Intercept Referral • Multiple Ring Patterns
- Multiple Directory Number - Distinctive Ringing with Call Waiting
• Personal Ring Back tone (PRBT) • Phone Context
•Reminder Call •Remote Access Service •Selective Calling Features:
- Selective Call Acceptance (SCA) - Selective Call Forwarding (SCF) - Selective Call Rejection (SCR) - Selective Distinctive Alerting - Wild Card Characters in Screening List
•Service Suspension •Simultaneous Ringing •Speed Dialing (1 or 2 digit) •Star Code Access to Voicemail •Voice Messaging Interfaces:
- SIP and SMDI - Message Waiting Indicator - VM Originated Calls
•Warmline
Additional Supported Services: •Customized Announcements •Directory Service •Fax •Local Number Expansion to National Number •Lucent Communication Manager User Interface •Overlap Digit Sending •Shared HSS Data (with Alcatel-Lucent USDS) •Terminating Feature Precedence •Video Call – Point to Point
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
98
Example 5420 CTS Feature Package Core Business/ Premium Business
• User Call Services:
• All supplementary services in the Silver Package, plus:
• Account Codes
• Authorization Codes
• Basic Auto-Attendant
• Call Park and Call Pick-Up:
- Call Park and Retrieve
- Hard Hold
- Directed Call Park and Retrieve
- Call Pick-Up
- Directed Call Pick-Up
- Directed Call Pick-Up with Barge-In
• 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
• Additional Supported Services:
• DID/DOD
• Communication Manager User Interface
• Voice VPN via PDP and Closed User Group
• Incremental Services in Premium
• Package:
• Music on Hold
• Time of Day/ Day of Week settings via CM
• User Controlled Call Barring
• More to be added in future releases
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
99
Subscriber Features
Calling Line ID Presentation
Calling Line ID Restriction
Calling Name
Call Forwarding Unconditional
Call Forwarding on MS Busy
Call Forwarding on No Reply
Call Waiting
Call Hold
Multi-Party Services
Call Barring of All Outgoing Calls
Call Barring of All Outgoing International Calls
Barring of All Outgoing Calls except directed to Home PLMN Country (BOIC-exHC).
Hotline
Operator Barring
Unstructured Supplementary Service Data
Subscriber Programming
Voice Messaging
Location Based Services
5420 CTS Supports Subscriber Features Provided By 3G MSC
Provided fully by 5420 CTS
IMS Standards Based Offering
Regulatory Features (see next Section)
Emergency Service (E-CSCF Based)
Support for standard CTM for deaf (Cellular Text Modem)
Support for Lawful Intercept (CSCF Based)
Support for Mobile Number Portability
Malicious call trace
Subscriber Features – CAMEL (see next slide)
Pre-paid
VPN
Personal Ring Back Tone
Smart Limits
Abbreviated Dialing
Modified cdc 29 oct 2010
re-integrate
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
100
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
101
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
102
IP Network 8650 SDM
CTS Interworking with Voice Mail Systems
IP Access – Fixed & Mobile
5420 CTS
Residential +
Business TAS
5450 ISC
SIP-ISC
SIP-ISC
Sh
http Published
APIs
Custom Client
VoIP Mobile Phone
Soft Client
SIP Endpoint
John Bill Susan
…. John Bill Susan
….
• CTS redirects calls to VM number configured for subscriber
• CTS forwards MWI status to endpoints • MWI status also reported to web
portal using PCM APIs • Star Code Access to VM • CTS interworks with 5100 Converged
Messaging System (CMS) as well as many other VM Systems
Custom Client 5420 PCM
5100 CMS (AnyPath)/
Other VM Systems
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
4. Regulatory Services
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Regulatory Services: LI / CALEA
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
105
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
106
Lawful Intercept Architecture
eNodeB
7750
SGW
Bearer & Control
Control Only
For simplicity, not all interfaces/connections are shown.
UE
eNodeB
8650
HSS
7750
PDN-GW
9471
MME
Managed
Core Network PSTN
SGSN GGSN RNC
NodeB
PDN
IMS
UE
---> - Admin (X1)
IRI – Intercept Related Information (X2)
CC – Content of Communications (X3)
SBC – Session Border Controller
CSCF - Call Session Control Function
SBC
CSCF
IRI
IRI
Provider/LEA
1357 ULIS / SS8
HI
5750
PCRF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
107
Converged IMS
LTE
LEMF/MC
Standardized External Interfaces
Internal Interfaces
Administration Function
IMC
Unique Interception Management Center (IMC) handles lawful interception administration function:
• Centralizes management of all lawful interception orders, particularly warrants activation or deactivation.
• Concentrates all IRI received from the LIGs and transmits it to the LEMF/MC.
• Provides single management across all domains.
Legacy Wireline
IRI: Interception Related Information
CC: Content of Communication
LEMF: Lawful Enforcement Monitoring Facility
MC: Monitoring Center
Alcatel-Lucent Solution: 1357 Unified Lawful Interception Suite (ULIS)
LIP
Distributed Lawful Interception Probes (LIP) handles Internal Interception Function:
• Can generate internal IRI or CC when no active solution is available in the Core Network.
LIGs Distributed Lawful Interception Gateways (LIG) handles IRI & CC mediation functions:
• Generates and delivers IRI and CC according to the network topology and the LEMF or MC.
• 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 CS) or IP (LIG IP).
IRI & CC Mediation Function
Legacy Wireless
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
108
LEA domain Network Operator domain
LEMF
LEA
Internal
Interfaces
INI
Administration
function
IRI mediation
function
CC mediation
function
HI1
HI3
HI2 Network
Internal
Functions
IIF
Intercept Related
Information (IRI)
Content of
Communication (CC)
External
Interfaces
HI
Alcatel-Lucent Lawful Interception Solution Mapping of the main functional entities
Mediation
1357 ULIS functions are mapped on Standard LI Model
LIP
IMC
LIG
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
109
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Regulatory Services: Emergency Services
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
111
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
112
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)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
113
Emergency Services in LTE (VoIMS) High Level Architecture/Call Flow
SGW
E-UTRAN
eNB
MME
PGW
P-CSCF MGCF/MGW
GMLC/LRF
E-SMLC
E-CSCF
Emergency Service Network
PSAP
5. Request Location Info
6. Retrieve Subscriber
Location from E-SMLC
Map x,y to
street
information.
3. Request ESRN from LRF
4. Route Call to PSAP
8. Location Info Response (x,y)
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.
1. UE Initiates
Emergency Call
7. Retrieve Location
data from UE
or eNB 2. P-CSCF recognizes
emergency call and
routes to E-CSCF
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Regulatory Services: Number Portability
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
115
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
116
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
BGCF S-CSCF MGCF
3i
1
ENUM
2i 4
PSTN/PLMN
Networks
IBCF
IP
Networks
5
3ii 2ii
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
117
Number Portability – High Level Flow in IMS using NP DB
BGCF S-CSCF
NP
DB
3
4
MGCF
5i
PSTN/PLMN
Networks
IP
Networks
6ii
1
ENUM
2
IBCF
5iii
MGCF
5ii 6i
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Regulatory Services: TTY/TDD
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
119
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
UPDATE for CDMA
V.18 GTT-IP
New
Transcoding
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Regulatory Services: GETS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
121
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
122
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Provisioning and Subscriber Migration
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
124
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
125
FM, PM
OAM&P Management Architecture (Fault, Configuration, Performance Mgmt)
5420 PCM
Portal
OMC-P
Customer FM/PM OSS
FM, PM, CM
FM, CM
FM, PM,
CM
FM: SNMPv2c PM: SFTP of XML Files
CM FM, PM
1360 COM CM: SOAP XML/
CORBA
IMS
VitalQIP
E-NUM
DNS
DHCP
CTS
ISC
SCG
MGC-8
MGCF
7510 MG
MGW
5025 SG
VSG
8610
ICC
OCS
8650 SDM
HSS/SPR
Common
FM, PM
5900 MRF
MRF
9400s eNB
9471 MME
7750 SGW
5780 DSC
7750 PGW
8950 SAM/
Customer OSS
IeCCF
FM
1357
ULIS
5110 SMSC-C
8950 AAA
XMC 5620 SAM
LTE
FM CM FM, PM CM FM, PM
CM FM, PM
FM: SNMPv2c PM: SFTP of XML Files
FM: SOAP XML/
JMS PM: SFTP
CM
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
126
OAM&P Management Architecture (Accounting)
Customer BSS
8615 eCCF
Rf diameter
ftp (CDR)
BTS
ASN.1 BER
(3GPP
standard) 8610 ICC
Ro
Diameter
Only from IMS-GWF
CTS
ISC
SCG MGC-8
MGCF
7750 SGW
7750 PGW
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
127
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
128
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Roadmap
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
130
LTE Solution High-level Roadmap
Use limit ph1 (Gx and QoS)
Subs. tiers ph1 (AMBR, QCI)
Network Share Ph1 (MOCN)
Public Safety Ph2 (Priority)
CMAS (Warning system)
VoLTE Ph2 (GSMA comply)
Local Breakout
Voice over LTE Ph1
(VoLTE)
Roaming (Home PGW)
Public Safety Ph1 (Deploy)
eMBMS Ph1 (TDD)
LE2.0/2.1 LE3.0/3.1 LE4.0
High Speed Data Seamless interworking and
basic voice Capacity management and
VoLTE introduction
Mobility ph1 (Intra LTE,
GSM, WCDMA, eHRPD)
Guaranteed Bit Rate
4 EPS bearers per UE
Per call meas. Data (PCMD)
Mobility ph3 (1x)
CSFB Ph2 (eCSFB, GSM,
1x)
E2E call trace
LE5.0
Enriched Quality of
Experience
New Business Models & Apps.
Enablement
QoS enhance. (FIR, MBR)
Mobility ph4+ (TDD<>FDD)
PCMD enhance. (+IMS)
Mass market VoLTE and service optimization
Use limit ph2+ (Sponsor) Subs. tiers ph2+ (MBR,GBR)
VoLTE Ph3+
(SRVCC, ICS, roam, IRAT)
eMBMS ph2 (FDD, CP)
Net. Sharing Ph2+ (Core)
Pub.Sfty. Ph3+(Pub. Priv.)
LE6.0+
SMS over SGs
Scalability and cost efficiency
Mobility ph2 (enh.3GPP)
CS Fallback Ph1 (WCDMA)
8 EPS bearers per UE
In Development
Under Plan
Released
eNB
5,10,20 MHz bandwidths
FDD: 700,AWS, 800, 2.6
TDD: 2300,2600
2x2 MIMO: TxDiv, OL, CL
VLAN, IPsec, GPS, SyncE
MME/SGSN/PCRF: ATCAv2
SGW/PGW/GGSN: 7750SR
SON: Plug&Play, ANR
eNB
Addtnl. bands/bandwidth
4RX div, extended cell
Semi-pers. sched., RoHC
eMCTA Ph2
SGW/PGW/GGSN:
Converged SGW/PGW
SON: IRAT ANR
SAM conv. OAM (+WCDMA)
eNB
Additional bands
eMCTA ph1
IEEE 1588v2
TDD 8 Tx/Rx beam form.
SGW/PGW/GGSN:
Converged GGSN/PGW
SAM Converged OAM
(ePC+ Backhaul + RAN)
R8 Jun 09 R8 Dec 09 R9 Sep 10 3GPP Alignment R9/10 TBC
2010 2011 2012 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
eNB
enh. MIMO
eMCTA Ph3
ICIC
Metro cell / SNAP
MME/SGSN:
Idle signaling reduction
Priority paging
SON: mobility,outage
Derisk Deploy. E2E Validation E2E Validation E2E Validation E2E Validation
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Supporting Material
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Network Element Overview
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
133
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)
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
134
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.
Solid field proven software and middleware on next generation hardware
Field proven
carrier-grade
OAM&P middleware
which provides:
•Alarms
•Asserts & audits
•Logging
•Measurements
•Realtime
performance
update
Evolved to next
generation ATCA
hardware for
increased
performance and
capacity
Full-Size Compact
AdvancedTCA (PICMG3.x)
Red Hat Enterprise Linux 5
Full Frame Compact
cPSB (PICMG2.16)
MontaVista Linux CGE4.0
Hardware & OS Interface Wrappers
Common OAM&P Switchover, Software update, Audits, Measurements, Data Base, Asserts, Alarms, Security (e.g., IPsec, SSH, Central PW
mgt, OS hardening, etc.)
Man
ag
em
en
t Inte
rface
Co
nfig
ura
tion
Data
base / iH
SS
CD
R / iC
CF
“Protocol-Assist” Communications Bus
5450 IP
Sessio
n C
on
trol
(I/P/S
/E-C
SC
F/B
GC
F)
5450 IP
Reso
urc
e C
on
trol
(PD
F, R
AC
F)
Access G
ate
way C
on
trol
Fu
nctio
n (H
.248)
5420 S
erv
ice
Co
ntin
uity
Gate
way
5420 C
on
verg
ed
Tele
ph
on
y S
erv
er
Fu
ture
Ap
plic
atio
n
2G
+ 3
G M
SC
Call P
rocessin
g
WR
LS
SS
7 D
ev
ice S
erv
er
Common OAM&P
Infrastructure
Session
Management
H.2
48 D
ev
ice S
erv
er
SS
7 D
ev
ice S
erv
er
Device
Servers
Application
Servers
MS
I Call P
rocessin
g
IOS
Dev
ice S
erv
er
5060 M
GC
-8
MM
E A
pp
licatio
n
(MIF
/ MA
F)
LV
I Ap
plic
atio
n
LIF
/ LA
F)
NEW
APPLICATIONS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
135
5450 IP Session Control Function (5450 ISC) Scalable SIP Session Control
• 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)
- Shelves are independent
- 1 pair of blades per shelf for high capacity Ethernet switching
- 1 pair of blades in shelf providing OAM, FSDB and CTS functions
- 1 to 5 add‘l blade pairs per shelf providing IMS Session Resource control functionality (P/I/S-CSCF, BGCF)
- Grown in 1 pair increments
- Each blade pair supports ~780K residential subs
- Single shelf supports ~3.9M subs
- Single cabinet supports ~7.8M residential subs
• Full redundancy (1+1 within shelf) • Automatic switchover to standby blade
• Hot swappable
• In-service growth/degrowth
• ETSI/NEBS compliant
PDU
5450 ICS 1 2 3 4 5 6 7 8 9 10 11 12 13 14
OAM
Eth
ern
et
Sw
itch
Eth
ern
et
Sw
itch
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ShM
C S
hM
C
ATCA
ISC
OAM
5450 ICS 1 2 3 4 5 6 7 8 9 10 11 12 13 14
OAM
Eth
ern
et
Sw
itch
Eth
ern
et
Sw
itch
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ISC
ShM
C S
hM
C
ATCA
ISC
OAM
Switching
Processing – Disk-full
Processing – Disk-less
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
136
5420 Converged Telephony Server (5420 CTS)
Switching
Processing – Disk-full
Processing – Disk-less
• 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
- 1 pair of blades in shelf providing OAM, FSDB and CTS functions
- 1 to 5 add‘l blade pairs per shelf with FSDB and CTS
- Each blade pair supports ~850K residential subs
- Single shelf supports ~5M subs
- Single cabinet supports ~10M residential subs
• Full redundancy (1+1 within shelf) • Automatic switchover to standby blade
• Dynamic subscriber-to-blade assignment when using Centralized Subscriber DataBase (CSDB)
• Hot swappable
• In-service growth/degrowth
• ETSI/ NEBS compliant
PDU
5420 CTS 1 2 3 4 5 6 7 8 9 10 11 12 13 14
OAM
+ F
SD
B +
CTS
Eth
ern
et
Sw
itch
Eth
ern
et
Sw
itch
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
ShM
C S
hM
C
ATCA
FSD
B +
CTS
OAM
+ F
SD
B +
CTS
5420 CTS 1 2 3 4 5 6 7 8 9 10 11 12 13 14
OAM
+ F
SD
B +
CTS
Eth
ern
et
Sw
itch
Eth
ern
et
Sw
itch
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
FSD
B +
CTS
ShM
C S
hM
C
ATCA
FSD
B +
CTS
OAM
+ F
SD
B +
CTS
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
137
5420 Service Continuity Gateway (5420 SCG)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
Hub
Hub
OA
M S
erv
er
Reg S
ub D
B
SS
7
SS
7
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
NS
CG
(applic
atio
n)
reg S
ub D
B
Hub
Hub
PDU
OA
M S
erv
er
5420 SCG shares a common software load with 5420 CTS, 5450 ISC, 5060 ICS, etc.
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-Rouzic)
SCG R8 (ATCA-Molene)
Subscriber Capacity/ Cabinet
~1.4M (two chassis)
~7.2M (two chassis)
Availability 3Q10 1H11
•Traffic Assumption -- 100% of the subscribers are IMS registered
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
138
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
139
5020 MGC-8 overview (Today)
Highly Scalable
- Up to 7 processor pairs per chassis for call processing
- 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
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
AT&T
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
140
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
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
141
7510 Media Gateway overview
• 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
Sample configuration (TGW)
Superior flexibility and cost efficiency to support traffic growth and service innovation
• 1500+ units shipped worldwide
• 15 MGCs supported
• 120 – 32,000 DS0 IP-TDM
• 32,000 sessions IP-IP
Circ
uit P
orts
Packet P
orts
N+1
Contro
l
IP/TD
M sw
itch
Media
Media
Media
N
+1
Packet P
orts
Packet P
orts
Packet P
orts
Packet P
orts
Circ
uit P
orts
N+1
Circ
uit P
orts
Circ
uit P
orts
Circ
uit P
orts
Contro
l
IP/TD
M sw
itch
Media
Media
Media
Circ
uit P
orts
7510 Media Gateway
CIMs MCMs SCMs, SFMs PIMs MCMs
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
142
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
143
VitalQIP® IP Address Management Solution
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
144
VitalQIP Key Features
•Full IP Management Software
- Holistic IP Network View
- Manage DNS domains, DHCP scopes, IP networks, subnets and objects
- Manage IP network and DHCP scope utilization
•Market Proven Scalability
- Millions of IP addresses
- Hundreds of thousands of domains
•Industry Leading Performance
- Highest Performing DHCP Server
- Exodus Labs certified
•Security
- Administrator access security
- Secure configuration pushes
- Secure DNS updates
•High Availability
- DHCP Failover, DNS master/slaves
•Extend Management Capabilities
- Audit Manager, Services Manager, SNMP Module, Network Allocator, Usage Billing Interface, API Toolkit, AutoDiscovery, Workflow Manager, Registration Manager, ENUM, DHCP Rules Manager
• Windows 2000/2003 Support
- Continuing support of Microsoft W2K DNS/DHCP Servers
- Active directory support integration
•Usability
- Simplifies creation and tracking of DNS and DHCP information
- Variety of GUIs simplifies information entry and formatting
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
145
Charging call flows in SRVCC context Alcatel-Lucent implementation
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
146
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
147
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
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
148
Voice Call Handling -VoLTE
Call establishment – MO from LTE user to an IMS-user served by different S-CSCF (1)
UL data (SIP Invite)
PGW PCRF P-CSCF S-CSCF1/
IMS-GWF SCC AS CDF/OFCS
Invite Invite (caller ID)
Invite
180 Ringing
180 Ringing
Rx: AAR (ICID)
Rx: AAA
Gx: RAR
Gx: RAA
SGW
ICID is created for this session (network part)
OCF/OCS
Invite (caller ID)
Invite (called ID)
UE2
180 Ringing 180 Ringing
Call set-up
Service request & authentication
MME eNB
180 Ringing 180 Ringing
Policy decision: QoS and charging (PCC rule)
Create Bearer Request
Create Bearer Response
GCID1 created for the signalling
Allocate S1 and radio Bearer for RTP dedicated bearer
GCID2 created
In green: online charging
In blue: offline charging Radio procedures for the creation of the dedicated bearer
Ro: CCR-E for CLIP*
Ro: CCA-E
TAS
Invite
Invite (called ID)
Ro: CCR-I for SIP session Ro: CCA-I
180 Ringing
*other
supplementary
services are
possible
S-CSCF2 not
represented,
CDR created
with this
entity
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
149
PGW PCRF P-CSCF S-CSCF1/
IMS-GWF SCC AS CDF/OFCS
200 OK
SGW OCF/OCS
200 OK
UE2 MME eNB
Rf: ACR Start
Rf: ACA
All IMS messages not shown (e.g. PRACK)
200 OK
200 OK
Rf: ACR Start
Rf: ACA
Ro: CCR-U for IMS session update Ro: CCA-U
200 OK
Rf: ACR Start
Rf: ACA 200 OK 200 OK
In green: online charging
In blue: offline charging
Voice Call Handling -VoLTE
Call establishment – MO from LTE user to an IMS-user served by different S-CSCF (2)
TAS
Rf: ACR Start
Rf: ACA
200 OK
200 OK
Rf: ACA
Rf: ACR Start
Rf: ACA
Rf: ACR Start
Linked to the
remote leg
Linked to LTE leg
Alcatel-Lucent solution is flexible to
offer several configurations
for the creation of the
CDR
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
150
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
151
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
152
top related