CarrierENUM - PowerPoint PPT Presentation

1 / 8
About This Presentation
Title:

CarrierENUM

Description:

Given a portability-corrected destination carrier ID from Step-1, Step-2 answers ... Multiple vendors are delivering Carrier-ENUM solutions today using the existing ... – PowerPoint PPT presentation

Number of Views:27
Avg rating:3.0/5.0
Slides: 9
Provided by: douglas121
Category:

less

Transcript and Presenter's Notes

Title: CarrierENUM


1
  • Carrier-ENUM
  • Implementation
  • North-American Mobile Operators

Glenn Marschel President NetNumber,
Inc. gmarschel_at_netnumber.com
2
About NetNumber
Background
  • Provider of next generation addressing solutions
    to service providers based on the NetNumber
    TITAN platform.
  • Common platform for legacy SS7/C7 addressing
    services and next generation Carrier-ENUM
    addressing services
  • Carrier-ENUM Private, secure, operator-controlled
    discovery of IP-based services.
  • MMS Portability-corrected addressing for
    cross-operator MMS services.
  • IMS Portability-corrected I-CSCF discovery from
    a dialed E.164.
  • VoIP Service provider controlled end-to-end
    VoIP addressing.
  • Number-Portability Highly efficient portability
    resolution via SS7, SIGTRAN, SIP DNS
    interfaces.
  • Support provided for both AIN and SRF portability
    solutions.
  • GTT Subscriber specific resource discovery via
    GTT translations and SCCP addressing techniques.
  • SMS Portability-corrected Service Provider ID
    (SPID) to enable SMS direct-connect between
    mobile operators.

3
NetNumber Clients
Background
4
ENUM Implementation Background
Background
  • Broad industry support exists for the use of ENUM
    as a standard query/response protocol for the
    discovery of IP-services associated with a dialed
    number.
  • Two distinct ENUM models have been identified
  • User-ENUM End-user controlled Tier-0, Tier-1,
    Tier-2 infrastructure deployed on the public
    Internet that enables a user to associate
    IP-services with his/her E.164 number under the
    domain e164.arpa.
  • Carrier-ENUM Service-provider controlled ENUM
    database used to facilitate the interconnection
    of IP-based services between carriers/operators
    by translating a dialed E.164 into a
    portability-corrected network entry-point address
    for a destination carrier.
  • Sometimes referred to as Operator-ENUM or
    Infrastructure-ENUM.

5
Carrier-ENUM In ProductionUse Existing SPID
databases to fulfill the role of the root
Background
  • Service-Provider-ID Database Model
    (SPID-Resolution) Utilizes existing industry
    sources of number-block-assignment and
    number-portability data to determine which
    destination operator controls a given dialed
    E.164. (No requirement for Tier-0 and Tier-1
    root infrastructure)
  • Central-database Used by mobile operators in
    USA today for MMS.
  • North-American portability database (NPAC)
    identifies the destination operator.
  • Block-assignment Used in non-ported-networks
    to support MMS.
  • Simple number-block assignment data identifies
    the carrier.
  • IMSI-database Use mobile operators in Europe
    to interconnect MMS.
  • MAP SRI-for-SM query returns portability-correct
    ed IMSI address with MCC MNC that identifies
    destination carrier.

6
Resolution Logic
Architecture
  • The Carrier-ENUM address resolution process
    breaks down into two logical steps
  • Step 1 Identify the destination operator
  • Given a dialed E.164, Step-1 answers the
    question Which destination carrier is
    responsible for this dialed number?
  • The key issue in Step-1 is number-portability.
  • Step 2 Apply local policy to the selection of an
    appropriate interconnect address.
  • Given a portability-corrected destination carrier
    ID from Step-1, Step-2 answers the question
    Which interconnect address should I use for this
    destination carrier?
  • The key issue in Step-2 is selection of an
    interconnect address that takes into account the
    relationship that exists between the originating
    carrier and the destination carrier.
  • Should this session be routed directly to the
    destination carrier or should it be routed via an
    intermediary service provider?

7
For More Information
GSMNA Addressing Task Force Carrier-ENUM
Implementation Guidelines
February 2006
8
Conclusions
Summary
  • Multiple vendors are delivering Carrier-ENUM
    solutions today using the existing industry
    databases with no requirement for a new Tier-0,
    Tier-1 and Tier-2 DNS root
  • On-site or third-party hosted solutions.
  • Multiple resolution models utilized on a
    country-by-country basis.
  • Central portability database
  • Number-block assignment database.
  • IMSI query.
  • ENUM provides a standard query/response protocol
    but DNS-delegation through a Tier-0, Tier-1,
    Tier-2 infrastructure is not a requirement for
    Carrier-ENUM.
Write a Comment
User Comments (0)
About PowerShow.com