Embed Size (px)
Citation preview
I t t R ti DiInterconnect Routing DiscoveryGateway, Service and Portability resolution with ENUM
Tim WardTimothy ward@neustar biz
The GSMA’s PathFinder project, implemented and operated by Neustar to support the hierarchical ENUM model described in GSMA IR67, has been the basis for trials, pilots and early adopters as IMS is deployed. This session will describe some of the lessons learned and provide insight to the debates over the role of ENUM [email protected] p gas both a technology and a service, and how the original model has evolved to support the diversity of number portability implementations around the world.
A dAgenda» Practical experience of ENUM for IMS interconnect» Extending ENUM address resolution to service discovery» Extending ENUM address resolution to service discovery» Number portability and integration with existing
architectures» ENUM to resolve evolution, migration and coexistence» Demo» Demo
2
ENUM S b k dENUM... Some background
» Public ENUMPublish/Discover an address in a Public
» Publish/Discover an address in a public IP network... The internet
» Private ENUMAddressing within a closed» Addressing within a closed, private network
» Private subnet addressesCarrier ENUM
Private
» Carrier ENUM» Addressing between networks» IPX or interconnect addresses Carrier
» Address lookup...» Gateway discovery» Service discovery Private
3
y» Attribute discovery
Wh t bl d C i ENUM l ?What problems does Carrier ENUM solve?
» Scaling .... How to maintain numbering and addressing for over 8000 operatorsoperators» 3 or 4 per country + national fixed + international....Interconnect voice to 200
countries100 1500 operators per country 8000 globally 1 6M specific number blocks» 100-1500 operators per country... 8000 globally, 1.6M specific number blocks
» Voice and SMS... And MMS -> 10 or more services» 20-30 interconnects -> thousands of ilogical nterconnect
» Technology Migration... Is the called number circuit or IMS?» Interconnect information management... Mechanism to allow
interconnect partners to request dynamic information» Control operational costs... Automate manual processes that have
become more complex» Integration of new interconnect services... Mapping of number into any
© Neustar, Inc. / Proprietary and Confidential4
» Integration of new interconnect services... Mapping of number into any service identifier
IMS I t t ENUMIMS Interconnect - ENUM» Theory... Function in IP, based on DNS to
support E164 numbersURI?
Carrier IPX
» Practice... Service to enable technology transition and coexistence» Number to URI translation Service?
Operator» Number to URI translation» Existence – does a service exist for this
number?E ti ti hi h S t ?
Service?
System?
» Exception routing – which System? Technology? Service?
» Address and route translationOperator
Route?
Translate?
» Number Portability» Complement SS7 SIP and DIAMETER for
query/response
Operator
5
query/response
I l t tiImplementation» Is the ENUM system supporting private or carrier clients?
» Which addressing realm?» Are the clients trusted?» Policy based responses?» Billing Dispute resolution support» Billing, Dispute resolution, support
» Supporting ENUM with DNS technology» Number block polution» Fragmentation
» Support for recursion...» NS and NAPTR records
» Integration of number portabilityReq irement to map ro ting n mber or prefi into Name Ser er URI
$ORIGIN 0.0.7.7.4.4.e164enum.net.3.2.1.0.0.9 IN NS dns1.mnc001.mcc234.3gppnetwork.org
» Requirement to map routing number or prefix into Name Server URI» Allow subscribers to port from non-IMS to IMS
» Support ENUM REGEX data format
$ORIGIN 0.0.7.7.4.4.e164enum.net.3.2.1.0.0.9 NAPTR 100 10 "u" "E2U+SIP"
"!^.*$!sip:\\[email protected];user=phone!" .
NAPTR 100 10 "u" "E2U+SIP“
6
"!^.*$!sip:[email protected];user=phone!" .
S i DiService Discovery» ENUM service records... Identify specific gateway URI for each service
type» Multiple service specific records» Multiple service specific records
» E2U+sip, E2U+im, E2U+MMS:mailto, E2U+pres, E2U+pstn:sip, E2U+pstn:tel, E2U+sms:mailto, E2U+h323, ….
» Use of context attributes» User=phone, npdi, wireless=y, sigtran=ver
$ORIGIN 0.0.7.7.4.4.e164enum.net.3.2.1.0.0.9 NAPTR 100 10 "u" "E2U+SIP"
"!^.*$!sip:[email protected];user=phone!" .NAPTR 100 10 "u" "E2U+PSTN:SIP"
"!^.*$!sip:[email protected]!" .$ p @ p gpp gNAPTR 100 10 "u" "E2U+MMS:mailto"
"!^.*$!mailto:+447700900123/[email protected]!" .
7
N b P t bilitNumber Portability – supporting local regulatory strategypp g g y gy» Initial proposals in IR67 proposed
authoratitive hierarchical tiersT0 Gl b l» T0 – Global name server directory based on country code
» T1 – National name server di t i b d bdirectories based on number block allocation including NP exceptionsT2 O t NAPTR» T2 – Operator NAPTR server with service gateway URIs
» Revised flexible model allowing t d t l l ticountry and operator level options
» Global number block directory» Central, regional or operator NP
8
, g pcorrection records
E l ti Mi ti d C i tEvolution, Migration and Coexistence
» E164 number remains the global identifier» Which services does it support?
Whi h i t t t h l h ld b d t it?» Which interconnect technology should be used to access it?» Which gateway should be used, and are there alternatives?
» Mechanism to discover destination attributes» Attributes can be pre agreed, negotiated or discovered» Routing decisions may be different for different attributes
» Does it need transcoding?» Does it need transcoding?» Does it need differentiated QOS?
» Other end to end information?T i ti l» Termination class
» Premium rate» Subscriber preferences
9
p
;; QUESTION SECTION: ;2.1.3.5.0.0.0.1.0.2.6.8.3.e164enum.net. IN NAPTR ;;;; QUESTION SECTION: ;2.1.3.5.0.0.0.1.0.2.6.8.3.e164enum.net. IN NAPTR ;;
ANSWER SECTION: 2 1 3 5 0 0 0 1 0 2 6 8 3 e164enum net 900 IN NAPTR 10 1 "u" "E2U+sip"2.1.3.5.0.0.0.1.0.2.6.8.3.e164enum.net. 900 IN NAPTR 10 1 u E2U+sip "!^(.*)$!sip:\\[email protected]\;user=voice!" . ;;
2.0.3.5.0.0.0.1.0.2.6.8.3.e164enum.net. 900 IN NAPTR 10 1 "u" "E2U+sip" p"!^(.*)$!sip:\\[email protected]\;user=voice!" .
2.0.3.5.0.0.0.1.0.2.6.8.3.e164enum.net. 900 IN NAPTR 10 1 "u" "E2U+sms:mailto" "!^( *)$! \\1@ il i k t l !""!^(.*)$!sms:\\[email protected]!" . ;;
0.1.3.5.0.0.0.1.0.2.6.8.3.e164enum.net. 900 IN NAPTR 10 1 "u" "E2U+sip" "!^( *)$!sip:3862010005310@10 10 132 2!"! (. )$!sip:[email protected]! .
AUTHORITY SECTION:AUTHORITY SECTION: 0.1.0.2.6.8.3.e164enum.net. 900 IN NS ns1.iskratel.com. 0.1.0.2.6.8.3.e164enum.net. 900 IN NS ns2.iskratel.com.
© Neustar, Inc. / Proprietary and Confidential11
