Gateway, Service and Portability resolution with ENUM

Transcription

1 Interconnect t Routing Discovery Gateway, Service and Portability resolution with ENUM Tim Ward Timothy.ward@neustar.biz p g 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 as both a technology and a service, and how the original model has evolved to support the diversity of number portability implementations around the world.

2 Agenda» Practical experience of ENUM for IMS interconnect» Extending ENUM address resolution to service discovery» Number portability and integration with existing architectures» ENUM to resolve evolution, migration and coexistence» Demo 2

3 ENUM S ENUM... Some b background k d» Public ENUM» Publish/Discover an address in a public IP network... The internet» Private ENUM» Addressing within a closed closed, private network» Private subnet addresses» Carrier ENUM» Addressing between networks» IPX or interconnect addresses» Address lookup...» Gateway discovery» Service discovery y» Attribute discovery 3 Public Private Carrier Private

4 What problems does Carrier ENUM solve?» Scaling... How to maintain numbering and addressing for over 8000 operators» 3 or 4 per country + national fixed + international...interconnect voice to 200 countries» operators per country globally, 1.6M specific number blocks» Voice and SMS... And MMS -> 10 or more services» 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 service identifier 4 Neustar, Inc. / Proprietary and Confidential

5 IMS Interconnect t - ENUM» Theory... Function in IP, based on DNS to support E164 numbers» Practice... Service to enable technology transition and coexistence» Number to URI translation Service?» Existence does a service exist for this number? System?» Exception routing which h System? Technology? Service?» Address and route translation» Number Portability» Complement SS7 SIP and DIAMETER for query/response URI? Route? Translate? Carrier IPX Operator Operator Operator 5

6 Implementation ti» Is the ENUM system supporting private or carrier clients?» Which addressing realm?» Are the clients trusted?» Policy based responses?» Billing, Dispute resolution, support» Supporting ENUM with DNS technology» Number block polution» Fragmentation» Support for recursion...» NS and NAPTR records» Integration of number portability» 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 e164enum.net IN NS dns1.mnc001.mcc234.3gppnetwork.org $ORIGIN e164enum.net NAPTR "u" "E2U+SIP" NAPTR "u" "E2U+SIP 6

7 Service Discovery» ENUM service records... Identify specific gateway URI for each service type» 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 e164enum.net NAPTR "u" "E2U+SIP" NAPTR "u" "E2U+PSTN:SIP" p g. NAPTR "u" "E2U+MMS:mailto" 7

8 Number N b P Portability t bilit supporting pp g local regulatory g y strategy gy» Initial proposals in IR67 proposed authoratitive hierarchical tiers» T0 Global Gl b l name server directory based on country code» T1 National name server di t i b directories based d on number b block allocation including NP exceptions» T2 Operator O t NAPTR server with service gateway URIs» Revised flexible model allowing country t and d operator t level l l options ti» Global number block directory» Central,, regional g or operator p NP correction records 8

9 Evolution, Migration and Coexistence» E164 number remains the global identifier» Which services does it support?» Which h interconnect t 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 differentiated QOS?» Other end to end information?» Termination class» Premium rate» Subscriber preferences 9

10 Thank you 10

11 ;; QUESTION SECTION: ; e164enum.net. IN NAPTR ;; ANSWER SECTION: e164enum e164enum.net. net 900 IN NAPTR 10 1 "u" "E2U+sip" "!^(.*)$!sip:\\1@ims.mnc41.mcc293.3gppnetwork.org\;user=voice!". ;; e164enum.net. 900 IN NAPTR 10 1 "u" "E2U+sip" "!^(.*)$!sip:\\1@iskratel.com\;user=voice!" e164enum.net. 900 IN NAPTR 10 1 "u" "E2U+sms:mailto" "!^(.*)$!sms:\\1@mail.iskratel.com!" i l!". ;; e164enum.net. 900 IN NAPTR 10 1 "u" "E2U+sip" "!^( (.*)$!sip: @ ! 132 2!". AUTHORITY SECTION: e164enum.net. 900 IN NS ns1.iskratel.com e164enum.net. 900 IN NS ns2.iskratel.com. 11 Neustar, Inc. / Proprietary and Confidential