DOCSLIB.ORG

(54) METHODS.SYSTEMSAND.COMPETEB. E.R. 39 Style Alm 573

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

US00839 1273B2 (12) United States Patent (10) Patent No.: US 8,391,273 B2 Ku (45) Date of Patent: Mar. 5, 2013 (54) METHODS.SYSTEMSAND.COMPETEB.PROGRAMI PRODUCTS FOR PROVIDING 2007/0061397E.R. A1 3/200739 GregoratStyleacket al.et al.................... alm 573. INTRA-CARRIER P-BASED CONNECTIONS 2007/0133574 A1 6/2007 Tejani et al. USINGA COMMON TELEPHONE NUMBER 2007/0165613 A1* 7/2007 Soo et al. ...................... 370,356 MAPPING ARCHITECTURE 2007/0286379 A1* 12/2007 Wiatrowski et al. ..... 379,201.01 2008.0002665 A1 1/2008 Soo et al. .... 370,352 2008/00 19356 A1 1/2008 Marsico ........................ 370,352 (75) Inventor: Bernard Ku, Austin, TX (US) 2008.0025492 A1* 1/2008 Heinze et al. ............ 379,220.01 2008. O198997 A1* 8, 2008 Sterman et al. .......... 379,220.01 (73) Assignee: AT&T Intellectual Property I, L.P., 2009/0227276 A1* 9/2009 Agarwal et al. ............... 455,466 Reno, NV (US) 2010/0158201 A1* 6/2010 Vijay Marathe et al. ....... 379,36 2011/0038468 A1 2/2011 Hannan et al. ........... 379,112.01 (*) Notice: Subject to any disclaimer, the term of this 2011/0149956 A1*ck 6, 2011 Alt et al. ....................... 370,352 patent is extended or adjusted under 35 FOREIGN PATENT DOCUMENTS U.S.C. 154(b) by 1111 days. JP 2007243564 A * 9, 2007 (21) Appl. No.: 12/338,259 OTHER PUBLICATIONS Lind, “ENUMOverview”, CC1 ENUM LLCPETPAC, 6 pages, Jun. (22) Filed: Dec. 18, 2008 13, 2006. (65) Prior Publication Data (Continued) US 2010/O157977 A1 Jun. 24, 2010 Primary Examiner — Chi Pham (51) Int. Cl Assistant Examiner — Ahmed Elallam H04L 2/28 (2006.01) SEg: Agent, or Firm — Myers Bigel Sibley & H04L 2/64 (2006.01) s H04L 2/66 (2006.01) (57) ABSTRACT 52) U.S. C. ........ 370/351: 370/252: 370/352: 370/401 - (52) s s s 3791900 Internet protocol (IP) based calls from a first terminal in an IP (58) Field of Classification Search .................. 370/352, politiesEllistina 370/353,354,356, 252,351,389, 401; 379/220.01, ystem. p hati p 379,221.O2,900 request at a common communications COre that 1S COmmon to - v- both the IP based communications system and the other com See application file for complete search history. munications system, a query is transmitted to a private tele (56) References Cited phone number mapping database that contains routing infor mation for terminals in both the IP based communications U.S. PATENT DOCUMENTS system and the other communications system requesting 7,624,417 B2 11/2009 Dua routing information for the second terminal. Routing infor 7,787,445 B2 8, 2010 Marsico mation for the call setup request is received from the private 7,944.912 B2 5/2011 Kobayashi et al. telephone number mapping database for routing the call. 7.948,967 B2 * 5/2011 Ku ................................ 370,351 7.974,295 B2 * 7/2011 Tuohino et al. ............... 370/401 18 Claims, 11 Drawing Sheets ed RIVATE MS-BASED US 8,391.273 B2 Page 2 OTHER PUBLICATIONS Stastny et al., “ENUM The bridge between telephony and Wikipedia, the free encyclopedia, “Telephone Number Mapping”. Internet’. Eures.com message, http://www.eures.com.de/message? http://en.wikipedia.org/wiki/Telephone Number Mapping, 7 messageSep2004/ENUM The bridge between telephony pages, Last Downloaded: Oct. 17, 2008. Faltstrom, “E. 164 number and DNS, Network Working Group, and Internet, 4 pages, Last Downloaded: Oct. 20, 2008. Cisco Systems, Inc. (Sep. 2000), 10 pages, http://www.ietforg/rfc/ Höneisen et al., “SWITCH (The Swiss Education & Research Net rfc2916.txt, Last Downloaded: Oct. 20, 2008. work) Hitchhikers Guide to ENUM Services ENUM Beyond Wikipedia, the free encyclopedia, “Voice peering'. http://en. SIP, Version 1.0, 13 pages (2005). wikipedia.org/wiki/Voice peering, 1 page, Last Downloaded: Oct. 20, 2008. * cited by examiner U.S. Patent Mar. 5, 2013 Sheet 1 of 11 US 8,391,273 B2 TIERO (COUNTRY CODE e164.arpa REGISTRY) TER 1 nSanp, enum.Com (TELEPHONE NUMBER (4.1.2.1.e164.arpa) SWeden enum.COm REGISTRY) TIER 2 (APPLICATION e164.att.net e164.xyz.com INFORMATION) FIGURE 1 U.S. Patent Mar. 5, 2013 Sheet 2 of 11 US 8,391,273 B2 THIRD PARTY TER 2. ENUM SERVICE PROVIDER 50 BVoIP OTHER MOBILITY OSS/BSS CARRIERS 22 60 PRIVATE ENUM 24 MOBILITY OSS/BSS 42 PRIVATE ENUM 44 CVoIP OSS/BSS 32 PRIVATE ENUM 34 FIGURE 2 U.S. Patent Mar. 5, 2013 Sheet 3 of 11 US 8,391,273 B2 OSS/BSS 224 t < D. CARRIERB CARRIERA TER 2* TER 2 ENUM 220 OTHER NETWORKS is real ro MOBILITY HOME OSS/BSS NETWORK 114 100 TER Of ENUM PRIVATE (LOCAL COPY) ENUM 112 110 QUERY - - - - DATA TRANSFER FIGURE 3 U.S. Patent Mar. 5, 2013 Sheet 4 of 11 US 8,391,273 B2 CARRIER B CARRIER B NETWORK TIER2 200 ENUM 220 NETWORK ENTRY POINT 228 TER O/1 ENUM 210 CARRIERA PRIVATE TIER 2* ENUM ENUM 110 130 CARRIERA HOME NETWORK 100 FIGURE 4 U.S. Patent Mar. 5, 2013 Sheet 5 of 11 US 8,391,273 B2 CARRIERB NETWORK 200 TER O/1 ENUM 210 CARRIERA PRIVATE TIER 2* ENUM ENUM 130 CARRIERA HOME NETWORK FIGURE 5 U.S. Patent Mar. 5, 2013 Sheet 6 of 11 US 8,391,273 B2 TER Of1 ENUM 140 PRIVATE ENUM MS-BASED NETWORK U.S. Patent Mar. 5, 2013 Sheet 7 of 11 US 8,391,273 B2 TER O/1 ENUM MS-BASED NETWORK FIGURE 7 U.S. Patent Mar. 5, 2013 Sheet 8 of 11 US 8,391,273 B2 TER O/1 TIER2 PRVATE ENUM ENUM ENUM 140 130 110 MS-BASED NETWORK 100 FIGURE 8 U.S. Patent Mar. 5, 2013 Sheet 9 of 11 US 8,391,273 B2 RECEIVE CALL SETUP REQUEST 602 FORWARD CALL SETUP REQUEST TO CORE 604 TRANSMIT OUERY TO PRIVATE ENUM 606 RECEIVENAPTR FROMPRIVATE ENUM 608 ROUTE CALL ACCORDING TO ROUTING INFORMATION IN NAPTR 610 FIGURE 9 U.S. Patent Mar. 5, 2013 Sheet 10 of 11 US 8,391,273 B2 RECEIVE RESPONSE FROM PRIVATE ENUM 702 RESPONSE INCLUDES NAPTRT 704 ROUTE CALL PER NAPTR NAPTR PONTS TO PSTN2 708 706 NAPTR INCLUDES LNP DATA2 710 OBTAN LNP DATA 712 FORWARD CALL TO PSTN 714 FIGURE 10 U.S. Patent Mar. 5, 2013 Sheet 11 of 11 US 8,391,273 B2 86 RAM ROM EPROM 80 82 84 FIG. 11 US 8,391,273 B2 1. 2 METHODS, SYSTEMS, AND COMPUTER packetized and communicated over the Internet. A telephone PROGRAMI PRODUCTS FOR PROVIDING call may thereby be communicated through the Internet to a INTRA-CARRIER P-BASED CONNECTIONS VoIP provider, which converts the call back to an analog USINGA COMMON TELEPHONE NUMBER signal and places the call through a PSTN that is local to the MAPPING ARCHITECTURE called terminal. Alternatively, the VoIP provider can process the call entirely in digital form if the called terminal/tele RELATED APPLICATIONS phone is also a VoIP phone. A user can thereby dial a tele phone number in a conventional manner and have the call The present application is related to co-pending and com routed partly or entirely through the Internet, instead of monly assigned U.S. application Ser. No. 12/336,972, 10 through the PSTN. Similarly, an analog telephone can place a entitled “METHODS, SYSTEMS, AND COMPUTER PRO call to a VoIP telephone. The telephone call is routed through GRAM PRODUCTS FOR ENABLING NON-IMS QUE the PSTN to the VoIP provider, which converts the call into a RIES OF A COMMON TELEPHONE NUMBER MAP digital signal, packetizes the digital information and trans PING SYSTEM filed on Dec. 17, 2008, and to co-pending mits the packets to the called VoIP telephone. and commonly assigned U.S. application Ser. No. 12/338, 15 Furthermore, some telephone carriers have converted their 273, entitled “METHODS, SYSTEMS, AND COMPUTER backbone networks to carry Voice traffic, including even PROGRAMPRODUCTS FOR PROVIDING INTER-CAR Voice traffic that originates and terminates at analog tele RIER IP-BASED CONNECTIONS USING A COMMON phones, using VoIP. VoIP is therefore expected to play a TELEPHONE NUMBER MAPPING ARCHITECTURE significant role in voice telephony in the future. However, the filed on Dec. 18, 2008, the disclosures of which are incorpo convergence of traditional analog telephony and VoIP tele rated herein by reference. phony has been hampered by the fact that IP addressing is substantially different from E.164 addressing. As noted BACKGROUND above, E. 164 addressing uses the ten-digit NPA-NXX XXXX addressing format. In contrast, IP communications The present disclosure relates to communications net 25 utilize a 32-bit IP address, which is divided into four 8-bit works, and, more particularly, to routing IP-based connec numbers having a hierarchical relationship that designates a tions between different networks in an intra-carrier environ sub-network and a terminal within the sub-network. ment. Since the E. 164 numbering system and the IP address Historically, voice telephone calls have been carried over system are separate, a VoIP telephone may be associated with circuit-switched telephone networks, such as the Public 30 both an IP address and an E. 164 telephone number. Further Switched Telephone Network (PSTN). The PSTN was origi more, a party calling a VoIP telephone using an E. 164 tele nally designed to carry voice traffic over switched analog phone number may not be aware of the IP address of the VoIP lines. However, the backbone transmission network of the telephone. PSTN is now entirely digital, although analog circuits are still used to connect some analog telephones to the PSTN.
Recommended publications
  • RFC 2168 Resolution of Uris Using the DNS June 1997

    RFC 2168 Resolution of Uris Using the DNS June 1997

    Network Working Group R. Daniel Request for Comments: 2168 Los Alamos National Laboratory Category: Experimental M. Mealling Network Solutions, Inc. June 1997 Resolution of Uniform Resource Identifiers using the Domain Name System Status of this Memo =================== This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Abstract: ========= Uniform Resource Locators (URLs) are the foundation of the World Wide Web, and are a vital Internet technology. However, they have proven to be brittle in practice. The basic problem is that URLs typically identify a particular path to a file on a particular host. There is no graceful way of changing the path or host once the URL has been assigned. Neither is there a graceful way of replicating the resource located by the URL to achieve better network utilization and/or fault tolerance. Uniform Resource Names (URNs) have been hypothesized as a adjunct to URLs that would overcome such problems. URNs and URLs are both instances of a broader class of identifiers known as Uniform Resource Identifiers (URIs). The requirements document for URN resolution systems[15] defines the concept of a "resolver discovery service". This document describes the first, experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR (Naming Authority PoinTeR), that provides rules for mapping parts of URIs to domain names. By changing the mapping rules, we can change the host that is contacted to resolve a URI. This will allow a more graceful handling of URLs over long time periods, and forms the foundation for a new proposal for Uniform Resource Names.
  • Voip): SIP and Related Protocols Fall 2013, Period 1 Lecture Notes of G

    Voip): SIP and Related Protocols Fall 2013, Period 1 Lecture Notes of G

    IK2554 Practical Voice Over IP (VoIP): SIP and related protocols Fall 2013, Period 1 Lecture notes of G. Q. Maguire Jr. For use in conjunction with: Henry Sinnreich and Alan B. Johnston, Internet Communications Using SIP: Delivering VoIP and Multimedia KTH Information and Services with Session Initiation Protocol, 2nd Edition, Wiley, Communication Technology August 2006, ISBN: 0-471-77657-2. © 2004-2013 G.Q.Maguire Jr. All rights reserved. No part of this course may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without written permission of the author. Last modified: 2013.08.30:12:51 Maguire Cover.fm Total pages: 1 [email protected] 2013.08.30 Module 1: Introduction........................................................................... 35 Welcome to the course! .......................................................................... 36 Staff Associated with the Course............................................................ 37 Instructor (Kursansvarig) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37 Goals, Scope and Method....................................................................... 38 Goals of the Course - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38 Scope and Method - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  • A Telephone Domain Name System (T-DNS) for Internet Telephony Service at All IP Network

    A Telephone Domain Name System (T-DNS) for Internet Telephony Service at All IP Network

    A Telephone Domain Name System (T-DNS) for Internet Telephony Service at All IP Network oMi-Ryong Park, Chang-Min Park, and Jong-Hyup Lee Router Technology Department, Network Research Lab., ETRI 161 Kajong-Dong, Yusong-Gu, Taejon, 305-350, Korea Tel: +82-42-860-1211, Fax: +82-42-860-5213 Abstract: - Lately, Internet is generally accepted as a principle communication protocol for voice and data networks. Moreover data and voice is converging with one network over the Internet. Each node has its own IP address for existing packet data on the Internet. Even multi-media terminals including Internet phone, Internet fax, and Internet-enabled electric devices, are transferring variable-sized packets. There are several working groups for studying converged data and voice communication in Internet. Such converged network services especially for Internet telephony as Voice over IP (VoIP) or SoftSwitch have already been suggested. We believe that the VoIP service become a killer application on the Internet for the future. Many protocols such as Session Initiation Protocol (SIP), Media Gateway Control Protocol (MGCP), MEGACO, SIGTRAN of Internet Engineering Task Force (IETF) and H.323 series of International Telecommunication Unit (ITU-T), are accepted as standards required for the VOIP service. In this paper, we suggest a Telephone-Domain Name System (T-DNS) architecture for detecting simply the destination IP address at the converged network. T-DNS is based on a Client and Server and an original Internet Domain Name Service (DNS) model. But it expands the DNS architecture for detecting destination IP address by querying the Uniform Resource Locator (URL) of telephone numbers.
  • DNS/ENUM Guidelines for Service Providers & GRX/IPX

    DNS/ENUM Guidelines for Service Providers & GRX/IPX

    GSM Association Non Confidential Official Document IR.67 IR.67 - DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers 6.0 1 December 2011 This is a non-binding permanent reference document of the GSM Association. Security Classification – NON-CONFIDENTIAL GSMA Material Copyright Notice Copyright © 2011 GSM Association Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V6.0 Page 1 of 78 GSM Association Non Confidential Official Document IR.67 Table of Contents IR.67 - DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers .......... 1 6.0 ............................................................................................................................... 1 1 December 2011 ....................................................................................................... 1 1 Introduction ...................................................................................................... 5 1.1 Overview ..................................................................................................... 5 1.2 Scope .......................................................................................................... 5 1.3 Definition of Acronyms and Abbreviations ................................................... 5 1.4 Definition of Terms ...................................................................................... 6 1.5 Document Cross-References ...................................................................... 7 2 DNS
  • Technical Realization of Communication Networks

    Technical Realization of Communication Networks

    TECHNISCHE UNIVERSITAT ••• WIEN • • • institute of Vienna University of Technology • e • telecommunications Lecture Notes Technical Realization of Communication Networks Course Number: 388.031 Part : Networking o. Univ. Prof. Dr. Hannen R. van As Institute of Telecommunications Vienna University of Technology 2011 2 CONTENTS 1.5.14 Adrnii;sion control 59 l.5.15 Flow control .... 60 1.5.16 Congestion control 61 1.6 Mobility 62 1. 7 Security . .. 63 Contents 2 Source and transmission coding 65 2.1 Introduction . 66 2.2 Source coding . 67 2.3 Linc coding aJJd modulation . 68 2.3.1 Binary coding . 69 1 Networking 1 2.3.2 I3lock <.'Oding .... 70 1.1 Network architecture . 2 2.3.3 Convolution coding . 71 1.1.1 Network planes . .. 2 2.4 Modulation . 72 1.1.2 Wired and wireless media 3 2.4.l OFDM ....... 73 1.1.3 Transmission . 3 2.4.2 CMSK .. .. ... 74 1.1.4 Switching . 9 2.5 System-related coding and tra.nsrnh;sion 75 1.1.5 Signaling and control . 13 2.5.1 PCM .......... .... 76 1.1.6 Network intelligence 14 1.1.7 Network management 14 3 Tuansmission 77 1.1.8 Service transport . 14 3.1 Introduction . 78 1.1.9 Communication and content services 14 3.2 Transmission media . 82 1.1.10 Technological layering 14 3.2.l CoaxiaJ cable 82 1.1.11 Geographical areas 15 3.2.2 Copper twisted pair 82 1.2 Protocol Architecture 19 3.2.3 Fiber . 83 1.3 Network protocols 23 3.2.4 Free-space optic link 83 1.4 Network availability 27 3.2.5 Frequency spcctmrn 83 1.5 Network control .
  • March 22, 2006 Marlene H. Dortch Federal Communications Commission Office of the Secretary 445 12Th Street, SW Washington, DC 2

    March 22, 2006 Marlene H. Dortch Federal Communications Commission Office of the Secretary 445 12Th Street, SW Washington, DC 2

    1875 K Street, NW Washington, DC 20006 Tel: 202 303 1000 Fax: 202 303 2000 March 22, 2006 Marlene H. Dortch Federal Communications Commission Office of the Secretary 445 12th Street, SW Washington, DC 20554 Re: In re Telecommunications Relay Services and Speech-to-Speech Services for Individuals with Hearing and Speech Disabilities; Petition for Declaratory Ruling on Video Relay Service Interoperability, CG Docket No. 03-123 Dear Ms. Dortch: On March 20, 2006, representatives of Snap Telecommunications, Inc. (“Snap”), Aequus Technologies Corp. (“Aequus”), and WorldGate Communications, Inc. (“WorldGate”) met with Tom Chandler, Chief, Disability Rights Office; Jay Keithley, Deputy Bureau Chief, Consumer & Governmental Affairs Bureau; Greg Hlibok, Disability Rights Office; and Sharon Diskin, Office of the General Counsel. Also attending the meeting were David Dinin, President, Aequus; Daryl Crouse, President and Founder, Snap; Randy Gort, General Counsel, WorldGate; Richard Westerfer, Chief Operating Officer and Senior Vice-President, WorldGate; and the undersigned. During the meeting, the parties supported the petition in the above-captioned proceeding and opposed restrictive marketing practices, IP blocking, or other techniques by a VRS provider designed to prevent a hearing-impaired individual from placing a VRS call to a different VRS provider. However, the parties also cautioned the Commission to avoid the adoption of requirements in this proceeding that could have the inadvertent effect of impeding the ability of new or existing VRS providers from introducing VRS equipment and services implementing the newer and more robust open standard called Session Initiation Protocol (“SIP”). The parties described the benefits of SIP in providing functionally equivalent service for the hearing-impaired community, the fact that SIP is increasingly being embraced as the standard of choice in the video phone and VoIP arenas, and that SIP is the focus of significant efforts by various industry players to establish E-911 solutions for VoIP and VRS.
  • Dns Applications and Resource Records

    Dns Applications and Resource Records

    10 DNS APPLICATIONS AND RESOURCE RECORDS 10.1 INTRODUCTION DNS inherently lends itself well to “translating” a given piece of information into another related piece of information. This resolution process is the very reason for DNS’s invention, and it has been extended beyond resolving hostnames into IP addresses and vice versa to support a broad variety of applications. Virtually any service or application that requires translation of one form of information into another can leverage DNS. Each resource record configured in DNS enables this lookup function, returning a resolution answer for a given query. The DNS server parses the query from the Question section of the DNS message,* seeking a match within the corresponding domain’s zone file for the query’s QNAME, QCLASS, and QTYPE. Each resource record has a Name (aka Owner) field, Class (Internet class is assumed if not specified), and Type field. The RData field contains the corresponding answer to the query. The resource record type defines the type and format of the question (owner/name field) and corresponding answer (RData field). In some instances, multiple resource records may match the queried name, type, and class. In such cases, all matching records, called a Resource Record Set (RRSet), are returned in the Answer section of the response message. * Refer to Figure 9.12. IP Address Management: Principles and Practice, by Timothy Rooney Copyright Ó 2011 the Institute of Electrical and Electronics Engineers, Inc. 10.1 INTRODUCTION 177 Most, but not all, new applications require new resource record types to enable definition of application-specific information, and these new resource record types are standardized via the IETF RFC process.
  • ENUM Guidelines for Service Providers and IPX Providers

    ENUM Guidelines for Service Providers and IPX Providers

    GSM Association Non-confidential Official Document NG.105 - ENUM Guidelines for Service Providers and IPX Providers ENUM Guidelines for Service Providers and IPX Providers Version 1.1 28 May 2018 This is a Non-binding Permanent Reference Document of the GSMA Security Classification: Non-confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association. Copyright Notice (Test) Copyright © 2018 GSM Association Disclaimer The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. V1.1 Page 1 of 55 GSM Association Non-confidential Official Document NG.105 - ENUM Guidelines for Service Providers and IPX Providers Table of Contents 1 Introduction
  • Vitalqip® DNS/DHCP & IP Management Software ENUM

    Vitalqip® DNS/DHCP & IP Management Software ENUM

    VitalQIP® DNS/DHCP & IP Management Software ENUM Manager Release 1.2 User’s Guide 190-409-067R7.1 Issue 1 August 2007 Alcatel-Lucent - Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright © 2007 Alcatel-Lucent. Unpublished and not for publication. All rights reserved. Copyright © 2007 Alcatel-Lucent. All Rights Reserved. This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the material. This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the material. Trademarks All trademarks and service marks specified herein are owned by their respective companies. Licenses Apache This product includes software developed by the Apache Software Foundation (http:// www.apache.org/). Alcatel-Lucent - Proprietary See notice on first page. Contents About this document 1 ENUM
  • ENUM: an Enabler for Voip and Next Generation Services

    ENUM: an Enabler for Voip and Next Generation Services

    ITU Workshop on “Origin Identification and Alternative Calling Procedures” (Geneva, Switzerland, 19-20(AM) 2012) ENUM: an Enabler for VoIP and Next Generation Services Steven D. Lind Senior Member of the Technical Staff, AT&T [email protected] Geneva, Switzerland, 19-20 March(AM) 2012 What is ENUM? Provides mapping from E.164 numbers to IP resources Telephone number as domain name Built on top of DNS Number “holder” needs to opt-in Example: +1-973-236-6787 Lookup 7.8.7.6.6.3.2.3.7.9.1.e164.arpa sip:[email protected] DNS sip: [email protected] mailto:[email protected] mailto:[email protected] Geneva, Switzerland, 19-20 March(AM) 2012 2 Assumption Use of standard telephone numbers (ITU-T Recommendation E.164) is not going away PSTN/analog terminals are going to be around IP phones will use 12-button keypad Globally unique identifier that has established familiarity with end users Geneva, Switzerland, 19-20 March(AM) 2012 3 Types of ENUM End-User ENUM used to discover IP endpoints where data is placed in a public ENUM tree by end-users (or their agents) Provider ENUM (aka Carrier or Infrastructure ENUM) used to discover IP-based points of interconnection where data is placed in a private ENUM tree by carriers of record Geneva, Switzerland, 19-20 March(AM) 2012 4 Why is ENUM Important? ENUM will enable VoIP interoperability E.164 addresses will be used as names in VoIP networks ENUM enables call routing between VoIP service providers E.164 addresses are not directly routable in an IP/VoIP network Use ENUM to map E.164 number to an Internet address that can be used to setup communication (e.g.
  • ENUM & DNS Principles for an Interoperator IP Backbone Network

    ENUM & DNS Principles for an Interoperator IP Backbone Network

    ETSI TS 184 010 V3.1.1 (2011-08) Technical Specification Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); ENUM & DNS Principles for an Interoperator IP backbone network 2 ETSI TS 184 010 V3.1.1 (2011-08) Reference DTS/TISPAN-04015-NGN-R3 Keywords DNS, ENUM ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
  • Itu-T Supplement to Rec. E.164 Operational and Administrative Issues Associated with National Implementations of the Enum Functi

    Itu-T Supplement to Rec. E.164 Operational and Administrative Issues Associated with National Implementations of the Enum Functi

    ITU-T SUPPLEMENT TO REC. E.164 (CLEAN VERSION) OPERATIONAL AND ADMINISTRATIVE ISSUES ASSOCIATED WITH NATIONAL IMPLEMENTATIONS OF THE ENUM FUNCTIONS DRAFT # 11.2 STATUS: REVISED DRAFT #11.2 UPDATED DURING THE 7-16 MAY 2002 STUDY GROUP 2 MEETING IMPORTANT NOTE on the STATUS of ITU-T SUPPLEMENTS: Supplements are only informative and are, therefore, not considered to be an integral part of any Recommendation(s). They do not imply any agreement on the part of the ITU-T (Recommendation A.13, 10/2000, Section 2.4) - 2 - ENUM supplement to ITU-T Rec. E.164 OPERATIONAL AND ADMINISTRATIVE ISSUES ASSOCIATED WITH NATIONAL IMPLEMENTATIONS OF THE ENUM FUNCTIONS Table of Contents 1 Introduction ............................................................................................................................... 2 2 Scope ........................................................................................................................................... 2 3 References .................................................................................................................................. 2 3.1 IETF .................................................................................................................................... 2 3.2 ITU ...................................................................................................................................... 2 4 Definitions .................................................................................................................................. 2 4.1 General