Infrastructure enum etsi tr 102 055 enum workshop november 2004
Download
1 / 13

Infrastructure ENUM ETSI TR 102 055 ENUM Workshop November 2004 - PowerPoint PPT Presentation


  • 192 Views
  • Uploaded on
  • Presentation posted in: General

Infrastructure ENUM ETSI TR 102 055 ENUM Workshop November 2004. Richard Stastny, ÖFEG*. * The opinions expressed here may or may not be that of my company. What is ENUM?. A protocol defined by IETF in RFC 3761

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha

Download Presentation

Infrastructure ENUM ETSI TR 102 055 ENUM Workshop November 2004

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Infrastructure enum etsi tr 102 055 enum workshop november 2004

Infrastructure ENUMETSI TR 102 055ENUM WorkshopNovember 2004

Richard Stastny, ÖFEG*

* The opinions expressed here may or may not be that of my company

Richard Stastny


What is enum

What is ENUM?

  • A protocol defined by IETF in RFC 3761

  • ENUM is a database in the DNS used to find services (URIs) related to E.164 numbers in a well defined domain (e164.arpa)

  • It is therefore:

    • based on IETF principles

    • a service on the (public) Internet

    • end-to-end

    • end-user opt-in (calling and called)

  • Because ITU-T and national E.164 resources are used, it is also:

    • national opt-in

  • Carriers, operators, service providers,…

    • have no say in ENUM

Richard Stastny


What is required by carriers

What is required by Carriers?

  • If carriers want to interconnect (peer)

    • using IP-based technology

    • and E.164 numbers,

  • they have to use something else (e.g. another database)

    • to route calls within their networks

    • or to route calls between networks

  • If this other database is using ENUM technology, some name it

    • Carrier “ENUM”

    • Infrastructure “ENUM”

    • Operator “ENUM”

    • Enterprise “ENUM”

    • Corporate “ENUM”

Richard Stastny


Carrier internal use

Carrier Internal Use

  • Carriers may use ENUM technology to find within their network

    • the VoIP servers hosting their subscribers

    • Interworking servers (e.g. SIP/H.323)

    • the egress border elements to other IP-based networks

    • the egress gateways to PSTN-based networks

  • The ENUM database may also

    • interwork with existing IN (NP) databases

    • may be provisioned from the same administrative database

  • The root of the database may be in any domain

  • the administration of the database is carrier internal matter

Richard Stastny


Carrier shared use

Carrier Shared Use

  • Any con-federation of carriers may use ENUM technology to find

    • the ingress border elements of the other IP-based networks

    • not end-to-end, but network-to-network

  • the shared DB may either be in a

    • IP-based network shared between carriers (extranet)

    • or on the Internet (e.g. e164.info or even DUNDi)

  • The root of the database may be in any domain

  • the administration of the database is a con-federation internal matter (no regulators involved)

  • in the rare case that all carriers agree to use a common shared database on the Internet

    • an implementation in .arpa (e.g. e164c.arpa) is recommended

Richard Stastny


Is co existence possible

Is co-existence possible?

  • to be reachable via ENUM, an end-user needs a URI resolvable on the Internet (e.g. SIP AoR), provided:

    • by himself (DIY)

    • by his corporation

    • by a virtual VoIP provider

  • a carrier hosting a subscriber with an E.164 number within his network MAY provide this subscriber with an URI (or he may not)

  • if this is the case, the user may be reachable both via ENUM and the carrier database

  • the carrier may also lookup ENUM on behalf of his subscriber first, then lookup the carrier database(s) and finally may route the call via the PSTN

  • so ENUM may co-exist with other routing mechanisms

Richard Stastny


Some voip scenarios

Some VoIP Scenarios

DNS

ENUM

Internet

DB

NGN A

NP

DB

PSTN

DB

NGN B

Richard Stastny


From the internet

From the Internet

tel:+xxx

DNS

ENUM

sip:user@host

sip:user@host

Internet

sip:user@host

tel:+xxx

tel:+xxx

DB

NGN A

tel:+xxx

NP

tel:+xxx

DB

PSTN

tel:+xxx

DB

tel:+xxx

NGN B

Richard Stastny


From the pstn

From the PSTN

DNS

ENUM

sip:user@host

Internet

tel:+xxx

tel:+xxx

ENUM number range

DB

NGN A

tel:+xxx

NP

tel:+xxx

DB

PSTN

tel:+xxx

DB

tel:+xxx

NGN B

number range or ported

Richard Stastny


From the ngn

From the NGN

DNS

ENUM

sip:user@host

Internet

tel:+xxx

tel:+xxx

ENUM number range

DB

NGN A

tel:+xxx

NP

tel:+xxx

DB

PSTN

tel:+xxx

DB

tel:+xxx

NGN B

number range or ported

Richard Stastny


Walled gardens current tispan plan

Walled Gardens – current TISPAN plan

Internet

TISPAN NGN

GSMA GRX

PSTN

Richard Stastny


Walled gardens possible solution

Walled Gardens – possible solution

Internet

TISPAN MoU

GSMA GRX

PSTN

Richard Stastny


The end

The End

Thank you

Richard Stastny

ÖFEG

+43 664 420 4100

richard.stastny@oefeg.at

Richard Stastny


ad
  • Login