impact of carrier enum on intl traffic delivery mikael schachne belgacom ics

Belgacom ICS Confidential

Impact of Carrier ENUM on International Traffic Delivery

Mobile World Congress - ENUM Seminar18th February 2009, BarcelonaMikaël SchachneHead of Data Product Management Belgacom ICS


• Belgacom ICS at a glance

• Carrier Services Overview & Evolution

• Routing Options & Challenges

• Assessing the ENUM Benefits

• What’s Next?

Agenda


About Belgacom ICSAbout Belgacom ICS

Belgacom ICS Confidential09-Feb-24 5


27%

18%

12%

43%CapacityMobile DataVoice OutsourcingVoice Hubbing


Carrier Services Overview & EvolutionCarrier Services Overview & Evolution


Roaming or Roaming or Interworking Interworking

PartnersPartners

• 1 agreement with the Hub (AA.7x & AA.8x)

• 1 technical connection

• 1 financial relation

• 1 IREG & TADIG tests

Multilateral

Bilaterals

Rest of WorldRest of World

Extend footprint through a single interfaceExtend footprint through a single interfaceExtend footprint through a single interface

Roaming Hubbing

QoS Testing &

Monitoring

SMS & MMS Hubbing

Carrier Services

Voice Transit

Hub Provider

Belgacom ICS Confidential09-Feb-24 10

GRX

Past(TDM)

Future IPX Proxy3 GPP

VoIP/DSL IPv6 IPv6

SMSMMS

InternetCurrentEvolution(Hybrid)

IP

Softswitch

FIX/Mobile PSTN

VoIP

PSTN

FIXMobileTDM

All VoIP / IMS

Evolution of technologies

Belgacom ICS Confidential09-Feb-24

Introduce new services

Cost Reduction

Routing Flexibility & Scalability

Quality (reduce transcoding & SPOF)

Convergence

Line

Car

d

Line

Car

dSwitchingMatrix

Call Control ProcessorsSS7

E1

IP

NGNSIP/IMS

Why Embracing NGN Technologies?


IP INTERWORKING FABRICIP INTERWORKING FABRIC

The IPX Model

Multilateral & open for MNOs, FNOs and ISPsMultilateral & open for MNOs, FNOs and ISPs Enables cascading of payments & E2E SLAs in a secured environmenEnables cascading of payments & E2E SLAs in a secured environmentt


• Commercial IPX will start mid 2009

• PVI (Packet Voice Interworking) is the main driver for 2009. SIP-I driven.

• GRX & MMS will be integrated into IPX• Market evolving towards IP and new IMS services

• Existing services (Voice)• New services (IM, Video/Image Sharing, PoC, Gaming)

• Create new Revenues via new services and new type of SPs

• Opportunity to develop new Hubbing services

The IPX Road


• IPX is new : prove the telecom world that it can work

• SIP URI Routing & MNP

• Introduce E2E & IP Quality of Service

• Setup monitoring architecture (KPI/SLA)

• Vendors SIP-I support & interoperability in general. Devil is in the details.

• Charging validation

IPX Challenges


Routing Options & ChallengesRouting Options & Challenges


User plane

Control plane

TDM TDM• Interconnection still based on SS7 for user and control plane• Release 4 architecture not relevant for IP interconnection• Relying on HLR Interrogation & MSISDN Routing Tables

MNO A MNO B

Interconnections usually performed via CarriersInterconnections usually performed via Carriers

SS7 SS7

MGW MGW MSSMSS

Traditional SS7 Interworking

User plane

Control planeSTP

Voice Switch SMS HubRoaming Hub

routingSTP STP


User plane

Control plane

MNO A MNO B

Problem of SIPProblem of SIP--I interworking if no MNP solution is availableI interworking if no MNP solution is available

MGW MGW MSSMSS

Packet Voice InterworkingSIP-I

TCP/UDP/SCTPIP

L2,L1

Codec RTPUDPOP

L2,L1

PVI Provider

IPX

User plane

Control plane


• Wrong route selection • Operator might not be able to send traffic• Hub could terminate traffic to wrong destination• Risk of undelivered traffic if no solution available on

terminating party• Could lead to asymmetrical routing• Troubleshooting complexity• Increase loop risk• Billing issues between hubs & MNOs

MNP Impact


SIP-I Interworking with MNP

user planecontrol plane

IPX2MNO1 MNO2IPX1

MNO3

SS7TDM

BG

BGBG

Option a: MNO2 forwards call to MNO3

Option b: IPX2 terminates call to MNO3

Mobile customer +32474xxcalls +393930xxx

Ported-in MNO C subscriber +397870xxx

MNO1 routes the call towards the “number owning network” MNO2

Direct MNP access, Call Forwarding & HLR Lookup as only optionsDirect MNP access, Call Forwarding & HLR Lookup as only options

MNPDB


Routing with ENUMRouting with ENUM


Interworking with ENUM

user planecontrol plane

IPX2MNO1 MNO2IPX1

MNO3

MNPBG

BG

Mobile customer +32474xxcalls +393930xxx

Ported-in MNO C subscriber +397870xxx

MNO1 routes the call towards the “number owning network” MNO2

Routing performed after ENUM lookup Routing performed after ENUM lookup Traffic terminated directly by IPX to correct destination networTraffic terminated directly by IPX to correct destination networkk

MNPDB

ENUM Tier 0 MNPDB

MNPDB

SIP Redirect or DNS query

Option b: Operators providing Ported NumbersENUM Tier 1

Option a: Redirection to countrylevel ENUM DB


• Standardized solution for MNP

• Direct routing

• Transparency• Facilitate symmetrical routing• Security thanks to policy-based ENUM access• Accurate Billing & Reporting

• Open to IPX, MNOs, FNOs and xSPs

• Cost-efficient

ENUM Benefits


WhatWhat’’s next ?s next ?


Going Forward

• IPX is taking shape and should embrace any carrier services

• MNP solution is required for any services

• ENUM as ideal but solution also required for countries without centralized MNP DB

• Assessment of all available options within relevant WG/bodies

• Migration to ENUM under reasonable timeline

• Solution required in hybrid environment

• Consensus required to define architecture and business models in all scenarios

• Connect to ALL MNP DBs


Thank you! Thank you! www.belgacom‐ics.com

http://www.belgacom-ics.com/


BackBack‐‐upupwww.belgacom‐ics.com

http://www.belgacom-ics.com/

impact of carrier enum on intl traffic delivery mikael schachne belgacom ics

Technology