(NGN) Documents - Telcordia Information SuperStore - Telcordia ...

Telcordia Roadmap to 

Next Generation Network (NGN) 

Documents 

An SAIC Company 

Telcordia Technologies Roadmap Series 

ROADMAP-TO-NGN-1 

Issue 2, August 2008


Roadmap to NGN Documents Issue 2, August 2008 

Copyright Page 

Telcordia Roadmap to 

Next Generation Network (NGN) Documents 

Prepared for Telcordia Technologies by: Network Services and Assurance Organization. 

To obtain copies of this document, contact your company’s document coordinator or your 

Telcordia account manager, or call + 1.732.699.5828 (Worldwide), or visit our Web site at: 

http://telecom-info.telcordia.com. 

Copyright © 2002, 2008 Telcordia Technologies, Inc. All rights reserved. 

Trademark Acknowledgments 

Telcordia is a trademark of Telcordia Technologies, Inc. 

TRA is a trademark of Telcordia Technologies, Inc. 

CPSQ is a trademark of Telcordia Technologies, Inc. 

ii


Issue 2, August 2008 Roadmap to NGN Documents 

Roadmap Series Notice of Disclaimer 


This Roadmap Series document is published by Telcordia Technologies to inform 

the industry of Telcordia Roadmap to NGN Documents. Telcordia reserves the right 

to revise this document for any reason (consistent with applicable provisions of the 

Telecommunications Act of 1996 and applicable FCC rules). 

TELCORDIA MAKES NO REPRESENTATION OR WARRANTY, EXPRESSED 

OR IMPLIED, WITH RESPECT TO THE SUFFICIENCY, ACCURACY, OR 

UTILITY OF ANY INFORMATION OR OPINION CONTAINED HEREIN. 

TELCORDIA EXPRESSLY ADVISES THAT ANY USE OF OR RELIANCE 

UPON SAID INFORMATION OR OPINION IS AT THE RISK OF THE USER 

AND THAT TELCORDIA SHALL NOT BE LIABLE FOR ANY DAMAGE OR 

INJURY INCURRED BY ANY PERSON ARISING OUT OF THE 

SUFFICIENCY, ACCURACY, OR UTILITY OF ANY INFORMATION OR 

OPINION CONTAINED HEREIN. 

This Roadmap document is not to be construed as a suggestion to anyone to modify 

or change any product or service, nor does this document represent any 

commitment by anyone, including but not limited to Telcordia, to purchase, 

manufacture, or sell any product with the described characteristics. 

Readers are specifically advised that any entity may have needs, specifications, or 

requirements different from the generic descriptions herein. Therefore, anyone 

wishing to know any entity’s needs, specifications, or requirements should 

communicate directly with that entity. 

Nothing contained herein shall be construed as conferring by implication, estoppel, 

or otherwise any license or right under any patent, whether or not the use of any 

information herein necessarily employs an invention of any existing or later issued 

patent. 

TELCORDIA DOES NOT HEREBY RECOMMEND, APPROVE, CERTIFY, 

WARRANT, GUARANTEE, OR ENDORSE ANY PRODUCTS, PROCESSES, 

OR SERVICES, AND NOTHING CONTAINED HEREIN IS INTENDED OR 

SHOULD BE UNDERSTOOD AS ANY SUCH RECOMMENDATION, 

APPROVAL, CERTIFICATION, WARRANTY, GUARANTY, OR 

ENDORSEMENT TO ANYONE. 

If further information regarding technical content is required, please contact: 

Anand Akundi 

Telcordia Technologies 

One Telcordia Drive, Room 4A605 

Piscataway, NJ 08854-4151 

Phone: + 1.732.699.6031 

E-Mail: aakundi@telcordia.com 

iii




iv 

For general information about this or any other Telcordia documents, please 

contact: 

Telcordia Customer Service 

One Telcordia Drive, Room 1B180 


+ 1.732.699.5828 (Worldwide) 

+ 1.732.336.2226 (FAX) 

http://telecom-info.telcordia.com



Contents 

Contents 

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 

1.1 The Telcordia Roadmap to Technology Series . . . . . . . . . . . . . . . . . . 1–1 

1.2 History of Telcordia Generic Requirements . . . . . . . . . . . . . . . . . . . . 1–1 

1.3 Organization of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 

2. Overview of NGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1 

2.1 Introduction to Next Generation Networks . . . . . . . . . . . . . . . . . . . . 2–1 

2.1.1 Next Generation Network Framework Architecture . . . . . . . . . . . . 2–2 

3. Your Roadmap to NGN Documents . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 

3.1 List of Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 

3.2 NGN Generic Requirements (GR) Documents . . . . . . . . . . . . . . . . . . 3–2 

3.3 NGN Special Reports (SR) Documents . . . . . . . . . . . . . . . . . . . . . . 3–21 

4. NGN Subject Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 

5. Telcordia Contacts and General Information . . . . . . . . . . . . . . . . . . . . 1–1 

5.1 The Importance of Telcordia Generic Requirements . . . . . . . . . . . . . . . 1–1 

5.1.1 The Value and Role of Telcordia Generic Requirements . . . . . . . . 1–1 

5.1.2 Why Participate in Telcordia Generic Requirements? . . . . . . . . . . 1–1 

5.2 Telcordia Subject Matter Experts (SMEs) . . . . . . . . . . . . . . . . . . . . . 1–3 

5.3 General Document Ordering Information . . . . . . . . . . . . . . . . . . . . . 1–3 

5.3.1 Telcordia Information SuperStore . . . . . . . . . . . . . . . . . . . . . . 1–3 

5.3.2 Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4 

5.3.3 AXESS Point Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4 

5.4 Other Telcordia Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5 

5.4.1 The Telcordia Standards Knowledgebase (TSK) . . . . . . . . . . . . . . 1–5 

5.4.2 Telcordia Routing Administration . . . . . . . . . . . . . . . . . . . . . . 1–5 

5.4.3 Telcordia Numbering Services Center . . . . . . . . . . . . . . . . . . . . 1–7 

5.4.4 Other Telcordia Websites of General Interest . . . . . . . . . . . . . . . 1–9 

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary–1 

v



Contents 

vi



List of Figures 


Figure 2-1 NGN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3 

vii




viii



List of Tables 


Table 4-1 Subject-to-Document Cross-Reference . . . . . . . . . . . . . . . . 4–1 

ix




x



Foreword 

Foreword 

For over 20 years, Telcordia Technologies has been in the business of not only 

developing top-of-the-line products for the telecommunications industry, but also 

writing documents for these products (see About Telcordia Technologies for a 

detailed look at the company history). 

One particular technology area that has amassed a particularly high number of 

invaluable reference sources is the Telcordia Generic Requirements product line, 

which includes legacy Technical Advisories (TAs) and Technical References 

(TRs), as well as the extensive list of Generic Requirements (GRs). These 

documents are technical specifications for new, as well as existing, technologies 

or services. These proposed requirements are developed to provide customers 

with timely, high-quality solutions to address their needs in areas such as: 

Interface Specifications 

Equipment Capabilities 

Performance Characteristics: Quality and Reliability. 

The published documents are widely utilized and referenced. They address a 

broad range of technologies such as voice to data to video; cable to optical fiber; 

to wireless and transport; to routing, switching, and signaling; and services 

including reliability, engineering, operations, and maintenance. So broad a range, 

in fact, that finding exactly what you need for your company can be a daunting 

task. And, to add to this complexity, Telcordia also produces a multitude of 

Special Reports (SRs) that discuss general topics of interest in these range of 

technologies. 

Telcordia, with a long history of being proactive in industry, is doing something to 

help you find what you need. We’re doing the research for you. 

With the Roadmap to Technology series, Telcordia is helping you find the exact 

document you need if you are interested in a particular GR technology. In each 

Roadmap document, we have compiled an extensive list of all the relevant 

documents for that technology, with abstracts for each. We also provide an 

abridged Table of Contents for each document, and an index to topic areas. You 

can search by document title or by topic area. 

The documents also contain background information on the technology area - a 

quick tutorial on the technology and its evolution - and feature handy reference 

material on other Telcordia products, Telcordia contacts, and a how-to guide for 

searching the Telcordia websites. 

The Roadmap to Technology series will be evolving, so make sure to regularly 

check back with Telcordia to check on its status. 

xi



Foreword 

xii 

About Telcordia Technologies 

For more than two decades, Telcordia has supported leading communications 

companies around the globe with a robust, end-to-end portfolio of software, 

services, and research that spans key functions, including: 

Planning & Engineering: GIS-based systems for planning, designing, 

engineering, and documenting complex communications networks 

Fulfillment: a flexible, proven approach for managing inventory, provisioning 

automation, fallout resolution, and number management 

Service Delivery: a set of service creation and control enablers for creating 

and deploying advanced services for fixed, mobile and converged operators 

Service Management: multi-layer, configurable service quality solutions that 

enhance customer experience 

Telcordia is one of the world’s foremost providers of software and services for IP, 

wireline, wireless, and cable networks. It offers communications companies the 

elements they require to manage and grow their networks in an era of 

unprecedented global opportunity. The efforts of Telcordia on behalf of its 

customers have resulted in many awards and industry recognition. 

Telcordia puts its Elements of Success — innovation, experience, technical and 

industry reach — into Action on every solution deployment or consulting 

engagement. This focus on success represents the evolution of its operating 

philosophy of openness and flexibility known as the Telcordia® Elementive 

approach. 

The Telcordia depth and breadth of experience is evident in its ability to solve 

complex network and operations challenges and deliver solutions that touch 

nearly every corner of telecommunications, from the infrastructure upon which 

one of the world's largest telephone networks is built, to the rapidly expanding IP 

and mobile markets. Today, Telcordia software handles 80% of the fixed access 

lines, 100% of the toll-free traffic, and 90% of the wireless number portability 

market in the USA. Telcordia consulting and transaction Services provide 

forward-thinking operators with the tools and expert advice they seek to optimize 

processes, integration, interconnection, routing and numbering. 

Behind the scenes, Telcordia can draw upon the packaged intelligence found in 

more than 800 patents, developed to encourage progress in the 

telecommunications industry. Telcordia Research has led to ADSL, ATM, Frame 

Relay, SONET, AIN, ISDN, and many other industry breakthroughs. The Telcordia 

Software Systems organization has been certified to the ISO 9001 standard and 

registered to the TL 9000 quality standard for the telecommunications industry, 

and Telcordia people sit on some of the industry’s most influential standards 

bodies and forums.



Foreword 

Telcordia has a demonstrated ability to plan thoroughly and deliver properly. This 

talent helps enable Telcordia - in ways few other companies can - to fulfill the 

promise of seamless, converged services through rational network evolution, to 

fulfill the demand for unprecedented service choice and personalization, and to 

fulfill customers’ rising expectations of quality and convenience. 

For more information about Telcordia Technologies, contact your local account 

executive or call: + 1.732.699.5828 (Worldwide). 

xiii



Foreword 

xiv



Introduction 

1 Introduction 

This Telcordia Roadmap to Technology document, ROADMAP-TO-NGN-1, is a 

handy reference guide to all essential Telcordia documents related to NGN 

Technologies. It contains a listing of the Generic Requirement (GR) and Special 

Report (SR) documents that Telcordia has published on the technology, and also 

features an abridged Table of Contents for each as well as a detailed index. 

1.1 The Telcordia Roadmap to Technology Series 

Telcordia Technologies has a long history of being proactive in the 

telecommunications industry. Therefore, it is not surprising that we are 

responding to the industry’s request to provide an avenue for our customers to 

find what they need, when they need it. 

With the Roadmap to Technology series, Telcordia is helping you find the exact 

document you need if you are interested in a particular GR technology. In each 

Roadmap document, we have compiled an extensive list of all the relevant 

documents for that technology, with abstracts for each. We also provide an 

abridged Table of Contents for each document, and an index to topic areas. You 

can search by document title or by topic area. 

The documents also contain background information on the technology area - a 

quick tutorial on the technology and its evolution - and feature handy reference 

material on other Telcordia products, Telcordia contacts, and a how-to guide for 

searching the Telcordia websites. 

1.2 History of Telcordia Generic Requirements 

Telcordia Technologies, Inc. (formerly Bellcore) was created during the 

divestiture of the Bell System, in 1984, to serve as the center of technological 

expertise and innovation for the newly formed seven Regional Bell Operating 

Companies (RBOCs). Originally those RBOCs were the major clients and funders 

of Telcordia, and therefore, the primary funders and audience for the information 

products that resulted from the sharing of their ideas and expertise, i.e., Generic 

Requirements (GRs). The GRs were just that, generic in nature, and were 

developed in a phased process that started with a preliminary Framework 

Advisory (FA), followed by a Technical Advisory (TA), and then a more mature 

document known as a Technical Reference (TR). These GRs promoted the 

development of most of the telecommunications technologies we use today. 

The multiple audiences for these documents consisted of primary users (those 

who made decisions−planners or funders, such as the RBOCs, or acted on the 

information−implementers or technical analysts) and secondary users (those 

affected by the decisions and actions). The RBOCs used the Generic 

1–1



Introduction 

1–2 

Requirements to describe the technical details of products they wished to have 

their suppliers design. The purpose of the generic requirements was, and still is, 

to promote interoperability, network reliability, and integrity. 

With the inception of the Telecommunications Act of 1996 (TA96), the GR 

development process was broadened. Under TA96, industry-wide Generic 

Requirements from non-credited organizations, such as Telcordia, are established 

through processes that are open to funding and participation by all interested 

parties. Hence, invitations to fund and participate are announced in the monthly 

Telcordia Digest of Technical Information (http://www.telcordia.com/digest). 

Telcordia may also solicit general industry non-proprietary comments regarding 

a GR at publication and for the life of any GR issue. While unsolicited comments 

are welcome, work effort by Telcordia regarding such comments depends on the 

degree of funding support for such GR work. 

Telcordia GRs Today 

Telcordia GRs promote revenue opportunities and contribute to cost savings 

throughout the industry. They help service providers plan their networks and 

purchase equipment for use in and with those networks. Moreover, suppliers have 

benefited from Telcordia GRs when designing their products to meet the needs of 

their customers. 

GRs are widely accepted. For example, the FCC’s Network Reliability Council 

(NRC) 1996 survey found Telcordia GRs to be the most widely used reference on 

network reliability and integrity within the industry. 

Telcordia GRs offer timely, high-quality, implementable solutions that customers 

can consider. To achieve this, Telcordia provides leadership and the technical and 

editorial resources to produce GRs that satisfy deliverable milestones. Also, the 

process has been replaced by one document called a GR-CORE. Mostly open, 

closed, and pending technical issues are shared through a companion document 

called a GR-ILR (GR Issues List Report). 

Section 5.1 describes the Value and Role of Telcordia GRs and the benefits of 

funding and participating in Telcordia GR projects. 

1.3 Organization of This Document 

The remainder of the document is organized as follows: 

Section 2, “Overview of NGN,” takes a high-level look at NGN technologies and 

reviews its history. 

Section 3, “Your Roadmap to NGN Documents,” lists all the Telcordia 

documents related to the subject area. The section includes an informative 

abstract and an abridged Table of Contents for each document.



Introduction 

Section 4, “NGN Subject Index,” provides a detailed subject listing, which cites 

each document in which the information is found. When you find the relevant 

subject area, the abridged Table of Contents can point you to the actual section. 

Section 5, “Telcordia Contacts and General Information,” provides contact 

information on the specific technology, general document ordering 

instructions, information on other selected Telcordia technologies, and 

information for useful websites. 

Glossary, provides definitions of terms derived from the documents listed in 

Section 3 as well as a detailed acronym list. 

1.4 Reason for Reissue 

Issue 2 of ROADMAP-TO-NGN-1 replaces Issue 1, and contains changes to the NGN 

documents since 2002. 

1–3



Introduction 

1–4



Overview of NGN 

2 


For more than a century, the only network most people came in contact with was 

the one that allowed them to make telephone calls, the Public Switched Telephone 

Network (PSTN) 1 . During this time, it is likely that very few PSTN users ever 

considered that they were utilizing a network, or thought about the network 

infrastructure that made telephone calls happen. A caller simply picked up the 

telephone receiver, heard dial tone, and dialed a number, blissfully unaware of the 

combination of signaling, transport, and network intelligence that was being 

engaged. The introduction of personal computers and local area networking in the 

workplace began to change this, but it was not until the Internet revolution that the 

idea of using a network became commonplace. 

2.1 Introduction to Next Generation Networks 

Telecommunications networks have traditionally focused on the support of voice 

traffic and services. As a result, the PSTN has been optimized for voice traffic and 

services through a combination of circuit-switching, Time-Division Multiplexing 

(TDM), and Signaling System Number 7 (SS7). This voice infrastructure, developed 

and refined over the past century, has matured into a high-quality, reliable network. 

The network is ubiquitous and highly secure. Over the past decades, numerous 

voice services have been introduced in the PSTN. 

With the growth of computing and networking, there has been a significant 

development of a data communications infrastructure. The data communications 

infrastructure was primarily developed to help corporations and other private 

networks (such as Universities) send information within a defined and closely 

managed group. 

The explosive growth of the Internet, with its accessibility to businesses and 

residences, has led to a new way of looking at the data communications 

infrastructure. The growth of the Internet has popularized the deployment of packet 

switching, and more and more public carriers have had to start considering using 

packet switching for the parallel data infrastructure. The Internet (and, in 

particular, use of the Internet Protocol) provides a framework for sending and 

receiving voice, data, video, and multimedia over a common infrastructure. The 

Internet also provides a model for an infrastructure that can support a wide variety 

of applications, that could be rapidly introduced, often relying on intelligence being 

distributed at the “edges” of the network. 

As technology has evolved, it is clear that Next Generation Networks (NGNs) are 

emerging. The goal of NGNs is to use the best from the voice and data 

communications infrastructures. Thus, the vision of NGN is to provide a common 

infrastructure that supports a wide range of applications, including voice, data, 

1. For purposes of this discussion, radio, and television are not considered, as these involve broadcasting of 

information in one direction, rather than bi-directional, point-to-point communication. 

2–1




2–2 

video, and multimedia, while maintaining the high reliability, security, ubiquity, and 

controlled Quality of Service (QoS) offered by today’s voice infrastructure. The 

NGN is intended to be able to support users with a wide range of Customer 

Premises Equipment (CPE), from the telephony phones in the PSTN to Internet 

appliances including PCs and Personal Digital Assistants (PDAs), using a variety of 

wireline and wireless access technologies. NGN is intended to provide an 

infrastructure to rapidly offer new innovative applications and services and offer 

service providers the option of time or usage-sensitive billing. 

The convergence of voice and data on the same network, coupled with the flexible, 

open architecture of these networks, creates a platform for the development of 

advanced features and services. Therefore, a Next Generation Network is define as 

follows: 

A Next Generation Network is a packet-based multi-service network 

supporting voice service, data applications, and advanced features. 

An important component of NGN is Voice Over Packet (VoP). VoP transports voice 

calls on packet-based data networks. The NGN/VoP presents carriers with an 

opportunity to migrate all information transport, i.e., voice, data, fax, image, and 

video, onto a single medium. This would likely create significant cost reductions on 

transport, switching, on-site cabling and equipment, and administration and 

management, with the single network for both voice and data communications. 

2.1.1 Next Generation Network Framework Architecture 

Figure 2-1 illustrates the functional elements in a typical NGN framework 

architecture. The key functional elements shown in the figure are defined below. 

The architecture relies on a Core Network and an Access Network for providing the 

necessary connectivity and transport. The Core Network is the packet transport 

network (typically based on IP-networking) that provides connectivity to the 

functional elements in the NGN. The Access Network represents the local loop 

network of the NGN. There are various ways of offering access to the NGN. The 

Access Network could be based on the existing copper plant of LECs or could use 

other technical options such as Hybrid Fiber-Coax (HFC), Digital Subscriber Loop 

(DSL), wireless access, etc. 

However, the descriptions of the Functional Elements (FEs) and the interfaces do 

not imply any specific physical implementation. Various suppliers have developed 

products with functional elements with a single node that communicate with the 

relevant elements in other nodes. This framework does not endorse any particular 

physical architecture.




• Signaling Gateway (SGW) 

Figure 2-1 NGN Architecture 

The Signaling Gateway (SGW) provides an interface between the Call Connection 

Agent (CCA) and traditional Signaling System 7 (SS7) signaling nodes in the PSTN 

network. The basic function of the Signaling Gateway is to intercept SS7 signaling 

messages from one network and convert and encapsulate them for transport in the 

NGN to the CCA. The resulting end-to-end signaling connectivity is used to manage 

the facility interface to the PSTN network provided by the NGN Trunk Gateway. 

The SGW is described in detail in GR-3053-CORE, Voice over Packet: NGN Signaling 

Gateway Generic Requirements. 

Trunk Gateway (TGW) 

The Trunk Gateway (TGW) provides an interface between the PSTN digital trunk 

facilities and the NGN core network. The TGW interface extracts digital voice 

samples from Time Division Multiplexing (TDM) trunks and converts them to a 

packetized user information stream for transport over the NGN core network, and 

performs the inverse functions in the reverse direction. The TGW also performs 

silence suppression and other signal processing on the user information stream 

2–3




2–4 

when requested by the CCA to improve the efficiency of the core network transport 

function. 

The TGW is described in detail in GR-3054-CORE, Voice over Packet: NGN Trunk 


Access Gateway (AGW) 

The Access Gateway (AGW) provides an interface to the NGN for PSTN interfaces 

like analog line circuits, Basic Rate Interface (BRI), Primary Rate Interface (PRI), 

and non-Integrated Services Digital Network (ISDN) PBX trunks, and digital loop 

carrier. The AGW interface performs the same type of user information stream 

processing functions as the TGW. In addition, it performs Call Associated Signaling 

(CAS) management functions, notifying the CCA of changes in access line signaling 

state, playing tones and announcements, and applying signaling towards the PSTN 

endpoint. 

The AGW is described in detail in GR-3055-CORE, Voice over Packet: NGN Access 


Network Mediation Gateway (NMGW) 

The Network Mediation Gateway (NMGW) is the interface point between packetbased 

Access Networks and the NGN Core Network. It provides interworking 

functions to mediate any differences in transport, signaling, and Quality of Service 

(QoS) mechanisms between the Access Network and the Core Network. NMGW 

functions include network protection and security, connection management, traffic 

management and aggregation, and generation of tones and announcements on 

behalf of Customer Gateways. Several Customer Gateways access the NGN through 

an NMGW. 

The NMGW is described in detail in GR-3062-CORE, VOP: NGN Network 

Mediation Gateway Framework Generic Requirements.



Your Roadmap to NGN Documents 

3 


This section lists all the Telcordia documents related to NGN. Section 3.1, “List of 

Documents,” lists all Telcordia documents related to NGN. Section 3.2, “NGN 

Generic Requirements (GR) Documents,” provides an abstract and an abridged 

Table of Contents for all the Generic Requirements documents related to NGN. All 

of the GR documents in this section are available as individual documents or as a 

complete set, FR-NGN-01, NGN Family of Requirements. Section 3.3, “NGN 

Special Reports (SR) Documents,” provides an abstract and an abridged Table of 

Contents for Special Reports (SR) related to NGN. 

3.1 List of Documents 

GR-3051-CORE, Voice over Packet: NGN Call Connection Agent Generic 

Requirements 

GR-3053-CORE, Voice over Packet (VoP): Next Generation Network (NGN) 

Signaling Gateway Generic Requirements 

GR-3054-CORE, Voice over Packet: NGN Trunk Gateway Generic 

Requirements 

GR-3055-CORE, Voice over Packet: NGN Access Gateway Generic 

Requirements 

GR-3058-CORE, Voice over Packet (VoP): Next Generation Networks (NGN) 

Accounting Management Generic Requirements 

GR-3059-CORE, Generic Requirements for Voice Over Packet End-to-End 

Performance 

GR-3060-CORE, Framework Generic Requirements for Voice Over Packet 

(VOP) Network Services 

GR-3061-CORE, VOP: NGN Customer Gateway Framework Generic 

Requirements 

GR-3062-CORE, VOP: NGN Network Mediation Gateway Framework 

Generic 

GR-3070-CORE, Voice over Packet: NGN Element Management System 

(EMS) Generic Requirements 

GR-3071-CORE, VoP Element Management System (EMS) - Network 

Management System (NMS) Interface Generic Requirements 

SR-4717, Voice Over Packet in Next Generation Networks: An Architectural 

Framework 

SR-5074, Integrating Voice and Data Services in Next Generation Networks - 

An Architectural Framework 

SR-5093, VOP: Operator Services in an NGN 

3–1




3–2 

SR-NOTES-SERIES-09, Telcordia Notes on CPE for Next Generation 

Network Access 

SR-NOTES-SERIES-11, Telcordia Notes on IP Centrex. 

3.2 NGN Generic Requirements (GR) Documents 

This section lists all the Telcordia Generic Requirements (GR) documents related 

to NGN. A Document Abstract and an abridged Table of Contents for each 

document is provided. For the user’s convenience, all the GR documents listed in 

this section are available individually or as a complete set. The set ordering number 

is FR-NGN-01, NGN Family of Requirements. 

GR-3051-CORE, Voice over Packet: NGN Call Connection Agent Generic 

Requirements 

Today's Public Switched Telephone Network (PSTN) is engineered to efficiently 

transport voice traffic and services. However, the volume of data traffic (e.g., 

Internet traffic) carried by the PSTN is growing rapidly, and soon it will exceed the 

volume of voice traffic. This suggests that, going forward, it will be more efficient 

to engineer and operate networks optimized to handle data traffic. Packet-based 

transport and switching technologies are logical choices for such networks. In other 

words, voice traffic should be packetized and handled like data in the future. As 

data traffic continues to grow, users of network services are increasingly seeking 

value-added, multi-faceted communications capabilities such as unified messaging 

and complete service/terminal mobility. Users are also seeking higher 

communications bandwidths and greater control over that bandwidth. A Voice over 

Packet (VoP) network is envisioned as the first evolutionary step in satisfying these 

demands, while enabling new services and revenue streams to network providers, 

and potentially reducing the management costs and time to market. SR-4717, Voice 

Over Packet in Next Generation Networks: An Architectural Framework, provides 

a comprehensive framework for the support of voice and other narrowband 

services over packet-based networks. Such support includes traditional access 

methods, signaling interfaces, call processing, vertical services, and accounting. 

Moreover, these functions are distributed across the following functional entities: 

Trunk/Access Gateways, Signaling Gateways, Call Connection Agents, Service 

Agents, and Billing Agents. GR-3051-CORE provides the Telcordia view of 

proposed generic requirements and objectives for a Call Connection Agent. In 

general, these requirements can be divided into four groups: interface requirements, 

connection control requirements, call processing requirements, and management 

and operations requirements. These requirements also align with standards and 

also adds support for Fax relay, Fax Store and Forward, Customer Gateways, and 

Network Mediation Gateways.




Contents 

1. Introduction 

2. VoP Architecture 

2.1 Overview 

2.2 Functional Elements 

2.3 Interfaces and Protocols 

2.4 Assumptions 

2.5 High-Level Call Flows 

3. CCA Functional Architecture and High-Level Requirements 

3.1 CCA Functional Architecture 

3.2 Modularity, Scalability and Extensibility 

3.3 Resource Management and Connection Control 

3.4 Routing Analysis and Name/Address Resolution 

4. Interface Requirements 

4.1 Lower Layer Requirements 

4.2 Services, Support & Operations Interfaces 

4.3 CCA to BGW or VFS Gateway Control 

4.4 CCA-to-CCA Interface 

5. Call Processing and Connection Control Procedures 

5.1 Overview 

5.2 BGW/VFS Gateway Control Procedures 

5.3 TGW Procedures 

5.4 AGW procedures 

5.5 CCA to CCA Procedures 

5.6 Call Routing 

5.7 User and Service Profiles 

6. Management and Operations 

6.1 Overview of NGN VOP Network Management Framework 

6.2 Configuration Management 

6.3 Fault Management 

6.4 Performance Management 

Appendix A: Detailed Message Flows for the Reference Call Cases 

A.1 Successful Call Set Up 

A.2 Successful Call Release Initiated by the Calling Party 

Appendix B: Informative Summary of H.248 Changes from Issue 1 

Appendix C: Customer Gateway 

C.1 Customer Gateway to CCA Interface Signaling 

C.2 Customer Gateway to Network Mediation Gateway Bearer 

Association 

C.3 Non-Call-Associated Procedures 

3–3




3–4 

C.4 Customer Gateway Call Control Procedures 

C.5 Customer Gateway Specific Subscription/Administration 

Parameters 

Appendix D: Network Mediation Gateway 

D.1 NMGW Signaling interface 

D.2 NMGW Generic Procedures 

D.3 Network Mediation Gateway to Customer Gateway Bearer 

Association 

D.4 NMGW Call Control Procedures 

Appendix E: Handling SIP and H.323 Terminals in an NGN/VOP Network 

E.1 Support for H.323 Terminals 

E.2 Support for SIP Terminals 

GR-3053-CORE, Voice over Packet (VoP): Next Generation Network (NGN) 

Signaling Gateway Generic Requirements 

This document provides generic requirements applicable to Signaling Gateways 

(SGWs) in Voice over Packet (VoP) Next Generation Networks (NGNs). The SGW 

provides signaling connectivity between a Signaling System Number 7 (SS7) 

signaling network and a VOP network. The SGW requirements are based on the VOP 

network architecture assumptions described in GR-3051-CORE, Voice over 

Packet: NGN Call Connection Agent Generic Requirements. Specifically, this 

document describes the functional requirements for the SS7 interface, packet 

network interface, management interworking between the SS7 and packet network, 

and interaction between the SGW and the Call Connection Agent (CCA) in the VOP 

network. Also, an overview of the VoP network management strategy and detailed 

functional operations requirements that need to be supported by an SGW are 

specified. 

Contents 



2.1 Overview 




3. SGW Functional Architecture and High-Level Requirements 

3.1 SS7 Network Access Architecture 

3.2 Signaling Protocols 

4. Interface - Functional Requirements 

4.1 SS7 Network Protocol Interface - Functional Requirements




4.2 Core Network/CCA Signaling Interfaces 

4.3 Interworking Function 

5. Operations 

5.1 Management Framework 




6. Performance, Capacity, and Reliability Requirements 

7. Spatial and Environmental Requirements 

7.1 Equipment 

7.2 Electromagnetic and Electrical Environment 

Appendix A: Message Flow Examples 

A.1 Transfer of Message 

A.2 SS7 Network Management Interworking Examples 

GR-3054-CORE, Voice over Packet: NGN Trunk Gateway Generic 

Requirements 

This document sets forth the functionality and interfaces for a Trunk Gateway 

(TGW), which provides the communications interface between the Public Switched 

Telephone Network (PSTN) Trunk interface and the Core Network (CN) within the 

Voice over Packet (VoP) architecture. One or more TGWs (in the same geographic 

region) may operate under the control of a Call Connection Agent (CCA) to provide 

interfaces to the PSTN. For voice traffic arriving at the TGW from the PSTN, the 

TGW extracts digital voice samples from a specified trunk and inserts them into 

data packets, which are then routed through the CN to the destination [either to a 

receiving TGW or an Access Gateway (AGW)]. For data traffic arriving at the TGW 

from the CN, the TGW extracts the voice samples from the received packets, 

performs the inverse coding conversion, and places the resulting digital signals on 

a specified trunk for transmission to the destination (via the PSTN). In addition, the 

TGW may perform signal quality enhancements and silence suppression to send 

packets only when a talker is active to optimize the utilization of the CN. This 

document states in detail all aspects of the TGW functionalities, as well as its 

interface to the rest of the VoP network elements and management systems. The 

scope is limited to a set of generic functional requirements and interface 

specifications. This document does not present capacity, size, and throughput 

generic requirements, which are all vendor-specific issues. 

Contents 



2.1 Overview 

3–5




3–6 




2.5 High-level Call Flows 

3. TGW Functional Architecture and High-Level Requirements 

3.1 TGW Functional Architecture 

3.2 Connection Control and Resource Management 

3.3 Routing Analysis 

3.4 Modularity, Scalability and Extensibility 

4. Interface Requirements 

4.1 Bearer Transport Interface 

4.2 Gateway Connection Control Transport 

4.3 Gateway Control Interface 

4.4 Trunk Interface 

5. Connection Control Procedures 

5.1 Non-Call-Related Procedures 

5.2 Normal Call-Related Procedures 

5.3 Core Network Connection Procedures 

6. Media Processing 

6.1 Media Detection 

6.2 Continuity Tone Detection, Generation, and Loop-back 

6.3 Echo Cancellation 

6.4 Comfort Noise Insertion 

6.5 Encoding and Transcoding Functions 

6.6 Silence Detection/Suppression 

6.7 Packetization Functions 

6.8 Receive Path Delay 

7. Management and Operations Requirements 

7.1 Overview of NGN VOP Network Management Strategy 

7.2 Configuration Management Requirements 

7.3 Fault Management Requirements 

7.4 Performance Management Requirements 

GR-3055-CORE, Voice over Packet: NGN Access Gateway Generic 

Requirements 

This document describes the architecture, interfaces, and functionality of the 

Access Gateway (AGW) component of a Voice over Packet (VoP) network. The 

Access Gateway is an edge vehicle component of the VOP architecture that enables 

existing Public Switched Telephone Network (PSTN) line-side devices such as 

voice-grade analog station equipment, Integrated Digital Services Network (ISDN) 

Basic and Primary Rate connecting equipment, Private Branch Exchange (PBX)




switching systems, Key Telephone Systems (KTS), Integrated Digital Loop Carrier 

(IDLC) Remote Digital Terminals (RDTs) to be used transparently with a VoP core 

packet transport network. These generic criteria specify the operation of the device 

interface, signaling management, and user information path control functions of the 

VoP Access Gateway. The intent is to ensure the interoperability of the components 

of the PSTN and VoP networks, without constraining the implementation choices 

available to the manufacturer. The requirements describe the physical layer 

termination and real-time control functions for connecting PSTN devices to the VoP 

network. The requirements also describe the AGW interactions with the Call 

Connection Agent (CCA) and the procedures for transporting user information and 

associated signaling and control information over the core packet network. 

Contents 



2.1 VoP Overview 



2.4 Assumptions, Dependencies, and Constraints 

3. Access Gateway Architecture and High-Level Requirements 

3.1 Overview of AGW Architecture 

3.2 Modularity and Scalability 

3.3 Line-Side Interface Service Criteria 

3.4 Signaling Call Processing Control 

3.5 User Information Path Connection Control 

4. Access Interface Requirements 

4.1 Voice-Grade Analog Interfaces 

4.2 ISDN Basic Rate Interface - Option 

4.3 ISDN Primary Rate Interface - Option 

4.4 IDLC Interface - Option 

4.5 Conventional DS1 Interface to a PBX - Option 

5. Interface to the Core Network 

5.1 Core Network Assumptions 

5.2 Bearer Transport Interface 

5.3 Bearer Connection Control Interface 

5.4 Simple Control Transmission Protocol (SCTP) 

5.5 CCA to AGW Control Interface 

6. AGW Signaling Requirements 

6.1 Call Origination 

6.2 Call Termination 

6.3 Call Clearing/Disconnect 

6.4 Additional Considerations Regarding Access Interfaces 

3–7




3–8 

6.5 CCA Signaling Requirements 

6.6 Announcements 

6.7 Core Network Signaling Requirements 

6.8 Identifier Allocation, Release, and Management 

7. User Information Processing Requirements 

7.1 Fax/Modem Detection 

7.2 Echo Cancellation 

7.3 Silence Detection and Comfort Noise Insertion 

7.4 Receive Path Delay Control 

7.5 Packetization/Depacketization 

8. Management and Operations Criteria 

8.1 Overview of NGN VOP Network Management Strategy 




9. Miscellaneous Criteria 

9.1 Physical and Environmental 

9.2 Powering 

9.3 Quality and Availability/Reliability 

9.4 Electromagnetic Compatibility and Electrical Safety Criteria 

9.5 Synchronization 

9.6 System Administration 

GR-3058-CORE, Voice over Packet (VoP): Next Generation Networks 

(NGN) Accounting Management Generic Requirements 

Competition for telecommunications services remains high. Presently, the 

technological base for telecommunications is moving away from traditional Time 

Division Multiplexing (TDM) switching systems and toward alternative 

technologies such as data networks based on Internet Protocol (IP) and 

Asynchronous Transfer Mode (ATM). The newer networks have become 

technically competitive, cost-effective alternatives to the existing circuit-switchingbased 

solutions. 

While IP/ATM technologies have greatly matured, both new and traditional 

telecommunications service providers are finding that the transformation to a 

broadband Next Generation Network (NGN) has proven to be somewhat more time 

consuming and difficult than initially envisioned. One factor that has hindered the 

quick development and deployment of "carrier-grade" IP/ATM-based networks is 

the relative lack of industry-accepted standards and comprehensive generic 

requirements, particularly with regard to usage measurements. This GR addresses 

the need for accounting management standards by providing comprehensive 

generic requirements for generating meaningful usage measurements for NGN 

elements that must be integrated into the existing network fabric of the PSTN.




GR-3058 defines the capabilities of a platform capable of producing data about the 

services used by an end customer or another carrier, and provides the data in a form 

that enables a carrier's Billing System to determine the charges for this service 

usage. 

This document includes the description of basic functionality needed to generate, 

process, and output the data describing network usage, and deliver that usage data 

to downstream systems. 

Contents 


2. System Overview 

2.1 VoP Functional Elements 

2.2 VoP Accounting Management System Architecture 

2.3 System Interfaces 

2.4 Usage Measurements for VoP Services 


3. Call Event Accounting Management Generic Requirements 

3.1 Introduction 

3.2 Usage Measurement Recording 

3.3 Call Connection Requirements 

3.4 Supplementary Services Generic Requirements 

3.5 CALEA 

3.6 Usage Measurement Outputting 

3.7 Usage Measurement Storage 

3.8 Operations 

4. Billing Agent Accounting Management Generic Requirements 


4.2 CDR Generation and Formatting 

4.3 Billing AMA Format (BAF) Recording 

4.4 IPDR CDR Generation and Formatting 

4.5 Usage Validation 

4.6 CDR Outputting 

4.7 CDR File Storage 

4.8 Operations 

5. Network Component to BA Interface Generic Requirements 


5.2 Overview 

5.3 Upper Layer Protocol 

5.4 Middle Layer Protocols 

5.5 Lower Layer Protocols 

6. BA/Application Systems Interface Generic Requirements 


3–9




3–10 

6.2 File Transfer Protocol 

6.3 Telnet 

6.4 Middle Layer Protocols 

6.5 Lower Layer Protocols 

6.6 Data Compression 

7. BA/Element Management System Interface Generic Requirements 

Appendix A: Call Connection Scenarios and Recording Responsibility 

A.1 RADIUS 

A.2 Diameter 

A.3 Mapping Diameter/RADIUS Fields to Usage Elements in PDU 

Appendix B: Formatting PDUs 

B.1 On-Net Call Origination 

B.2 Disconnect PDU 

GR-3059-CORE, Generic Requirements for Voice Over Packet End-to-End 

Performance 

This document sets forth generic end-to-end performance requirements for packet 

based networks providing voice service using Next Generation Networks (NGN) 

architecture. These requirements consist of performance parameters definitions, 

objectives, and allocation rules. The end-to-end objectives may be specialized to 

specific networks through the use of the allocation rules. To complement these 

allocation rules, objectives are also given for selected network elements in the NGN 

architecture. Both the case of pure IP and ATM networks are considered, along with 

the case of a hybrid IP and ATM network. These requirements provide a basis for 

interworking between networks, and give guidance to equipment manufacturers. 

They offer consistency with the minimal performance floors of standards, and can 

be used in network design and capacity planning. 

Contents 


2. VoP Performance Models 

2.1 Measurement Points 

2.2 Performance Significant Reference Events 

2.3 Signaling Reference Models 

2.4 Transport Reference Models 

3. Signaling Performance 

3.1 Delay Concepts 

3.2 Classification of Call Attempts and Call Releases 

3.3 Access Function Performance Parameter Definitions 

3.4 Access Function Objectives 

3.5 Access Function Allocation Rules




3.6 Disengagement Function Performance Parameter Definitions 

3.7 Disengagement Function Objectives 

3.8 Disengagement Function Allocation Rules 

4. Transport Performance Requirements 

4.1 Performance Parameters 

4.2 Reference Events for Transport Parameters 

4.3 Objectives and Allocation Rules 

4.4 QoS Mappings of ATM to IP (for IP over ATM) 

5. Network Element Performance 

5.1 Information Transfer Performance of Network Elements 

5.2 Call Connection Agent 

5.3 Access Gateway 

5.4 Trunk Gateway 

5.5 Signaling Gateway 

5.6 Core Router 

5.7 Signaling Performance of Network Elements 

6. Network Service Availability 

6.1 Availability Parameters 

6.2 Service Availability Definition 

Appendix A: Definition of IP and ATM Transport Performance Parameters 

A.1 IP Transport Performance Parameters from I.380 

A.2 ATM Transport Performance Parameters from I.356 

Appendix B: Specialization of Performance Parameters to CCA 

GR-3060-CORE, Framework Generic Requirements for Voice Over Packet 

(VOP) Network Services 

This document contains the Telcordia Technologies view of proposed Framework 

Generic Requirements for Voice over Packet (VoP) Network Services. The 

framework generic requirements in this document are based on the Framework 

Architecture material on VoP Networks and VoP Network Services in SR-4717, 

Voice Over Packet in Next Generation Networks: An Architectural Framework. 

The purpose of this GR is to document the philosophy and architecture associated 

with decomposition of conventional Public Switched Telephone Network (PSTN) 

and Integrated Services Digital Network (ISDN) services across the various 

elements in a VoP network, identify the common signaling protocols used by these 

VoP network elements to allow for the provision of VoP Network Services to endusers, 

serve as a common reference for subsequent GRs documenting the specifics 

of groups of VoP Network Services, and to serve as an updatable repository of all 

protocols used to support all VoP Network Services. This Framework GR describes 

procedures for providing VoP Network Services using functionality distributed 

among the following VoP network elements: the Call Connection Agent (CCA), the 

3–11




3–12 

Services Agent (SA), the Access Gateway (AG), and the Signaling Gateway (SG). 

This Framework GR is not intended to provide complete requirements for VoP 

Network Services. Instead, it will serve as the foundation for comprehensive service 

requirements in other GRs that are to be developed in the future. The specific 

services that are covered in these future GRs will depend on the direction of the 

funding clients for these GRs. The Framework GR covers the following types of 

services, which are provided to VoP Network end-users who are connected to the 

VoP Network at the Access Gateway: Residential and business services for users 

connected to the AG by conventional PSTN line-side interfaces. These services are 

drawn from such conventional service categories as Plain Old Telephone Service 

(POTS) services, Basic Business Group (BBG) or Centrex Services, Custom Local 

Calling Area Signaling Services (CLASS), and Intelligent Network (IN) Services; 

Residential and business services for users connected to the AG by ISDN Basic Rate 

Interfaces (BRIs); Private Branch Exchange (PBX) Services for users connected to 

the AG by conventional PSTN trunk-side interfaces, and PBX Services for users 

connected to the AG by ISDN Primary Rate Interfaces (PRI). This document covers 

both the pre-IN and IN Transaction Capabilities Application Part (TCAP) protocols 

for VoP Network Services. Pre-IN TCAP is used with Toll-Free Service and Calling 

Name Identification Services in PSTNs today. IN TCAP is used with Local Number 

Portability service in PSTNs today. Both pre-IN TCAP and IN TCAP are included in 

this Framework GR to support VoP Network interworking with existing PSTN 

implementations of these services. To facilitate rapid introduction of new network 

services in the VoP network environment, this Framework GR also describes a 

framework for an Application Programming Interface (API) to allow for third party 

service creation. The API connects an external Service Definition Environment 

(SDE) to the Call Connection Agent and Services Agent in the VoP Network, and 

allows a third party to create new VoP Network Services for end-users on the VoP 

Network. 

Contents 


2. VoP Network Services Philosophy 

2.1 Functional Elements and Their Roles 

2.2 Interfaces and Protocols - Overview 

3. End-User Interfaces and Classes of Services Supported in VoP Networks 

3.1 End-User Interfaces 

3.2 Classes of Services 

4. Individual Services Supported in VoP Networks 

4.1 Generally Available Services 

4.2 Residential and Small Business Services for Analog Lines 

4.3 Large Business Services for Analog Lines 

4.4 Residential and Small Business Services for ISDN BRIs 

4.5 Large Business Services for ISDN BRIs 

4.6 Services for Conventional DS1 Trunks




4.7 Services for ISDN PRIs 

5. Call Flows and High-Level Requirements for Select Set of Features 

5.1 Toll-Free Service 

5.2 Local Number Portability 

5.3 Call Waiting 

5.4 Calling Number Identification 

5.5 Calling Name Identification 

6. CCA-AG Protocols for VoP Network Services 

6.1 Megaco/H.248 Protocol for Analog Line Control 

6.2 ISDN and SCTP Protocols for DS1 Trunks, ISDN BRIs, and 

ISDN PRIs 

6.3 Use of Megaco/H.248 for Core Network Connection Control for DS1 

Trunks, BRIs, and PRIs 

6.4 Protocol Elements Used to Support VoP Network Services 

7. CCA-SG Protocols for VoP Network Services 

7.1 Support for ISUP Protocols 

7.2 Use of Pre-IN TCAP Versus IN TCAP for VoP Network Services 

7.3 Support for SCCP/TCAP Protocols 

7.4 Support for MTP Protocols 

8. CCA-CCA Protocols for VoP Network Services 

8.1 BICC Protocol Impacts from VoP Network Services 

9. CCA Support of an API for Third-Party Creation of VoP Network Services 

9.1 Security Interface 

9.2 Call Control Interface 

9.3 User Interaction Interface 

9.4 Charging/Accounting Interface 

GR-3061-CORE, VOP: NGN Customer Gateway Framework Generic 

Requirements 


Customer Gateway (CGW) component of a Next Generation Network (NGN) 

network. The Customer Gateway is Customer Premises Equipment (CPE) that 

provides an interface between end user voice and data devices and broadband 

access circuits that connect to the NGN. The CGW can be structured to provide 

NGN access for large businesses using Private Branch Exchanges (PBXs) and for 

residences and small businesses using telephones, Personal Computers (PCs), and 

other traditional voice and data devices. The CGW connects to the NGN via an 

Access Network that terminates at a Network Mediation Gateway (NMGW). The 

NMGW validates CPE-provided information for the purposes of end-user 

identification and billing, and provides an interface to the Core Network. The CGW 

has a signaling interface through the NMGW to the Call Connection Agent (CCA); 

3–13




3–14 

the CCA assists the CGW in establishing voice calls. The generic criteria in this 

document state the architecture, interfaces, and functionality of the NGN Customer 

Gateway. The intent is to help ensure the interoperability of the components within 

the NGN, with other NGNs, and with other networks like the Public Switched 

Telephone Network (PSTN), without constraining the implementation choices 

available to the manufacturer. The generic requirements describe the physical layer 

termination and real-time control functions for interfacing user voice/data devices 

to a broadband access network for NGN access. The requirements also describe the 

CGW interactions with the NMGW and the procedures for transporting user bearer 

information, associated signaling and control information, and data over the core 

packet network. 

Contents 


2. NGN Architecture Overview 

2.1 High-Level View of a Next Generation Network Architecture 



3. Customer Gateway Architecture and High-Level Requirements 

3.1 Overview of Customer Gateway Architecture 

3.2 Physical Characteristics 

3.3 Size, Modularity, Scalability 

3.4 Customer Gateway Functions 

3.5 Network Access Interface Function 

3.6 Signaling Exchange Function 

3.7 User Information Management Function 

4. Protocols for Transport, Connection Management, Device Control and Call 

Control 

4.1 CGW Transport Requirements 

4.2 Connection Management and Device Control Using H.248 

5. Call Processing 

5.1 R/SB GW-to-R/SB GW Call, Analog Line Case 

5.2 Error Cases During Call Establishment 

6. Services 

6.1 NGN Reference Model – Gateways, Networks, and Services 

6.2 Defining NGN Services and Applications 

6.3 Extending PSTN and ISDN Services to NGN 

6.4 Third-Party Service Development for NGN Services 

6.5 Voice, Data, Video, and Multimedia in an NGN 

6.6 New NGN Applications for CGW End Users 

7. Customer Gateway Service Activation




7.1 Residential/Small Business Gateway Configuration and Installation 

Appendix A: IP Phones 

A.1 General Description 

A.2 Protocol 

Appendix B: CGW User-Side PSTN Interface Signaling and Supervision 

Requirements 

B.1 Analog Line Supervision and Signaling Criteria 

B.2 Conventional DS1 Interface (Non-ISDN Trunks) 

B.3 ISDN Primary Rate Interface 

GR-3062-CORE, VOP: NGN Network Mediation Gateway Framework 

Generic Requirements 


Network Mediation Gateway (NMGW) component of a Next Generation Network 

(NGN). The NMGW is a functional entity that interfaces with both the Access 

Network and the NGN Core Network. As such, it controls subscriber access to the 

NGN, regardless of the access technology used by the subscribers. It can be a standalone 

device or can be incorporated by a manufacturer into the functions of another 

network element. The functions of the NMGW are varied and may include: - 

Network protection, i.e., user authorization, address masking, toll fraud prevention, 

admission control, and traffic throttling - Aggregation of connections from multiple 

Customer Gateways (CGWs) for delivery of signaling information to the call 

connection agent - Audible ring generation and network announcements - Valueadded 

data services, Virtual Private Networks (VPNs), subscriber management and 

firewalls. The NMGW may also participate in the mechanism for dynamic 

bandwidth allocation over the Customer Premises Equipment (CPE) interface 

between voice and data applications to ensure the requested quality of service for 

the connection. These generic criteria present the architecture, interfaces, and 

functionality of the NGN Network Mediation Gateway. The intent is to ensure the 

interoperability of the components within the NGN as well as for interworking with 

other networks and with Public Switched Telephone Network (PSTN) user 

equipment, without constraining the implementation choices available to the 

manufacturer. The generic requirements also describe the NMGW interactions with 

the Customer Gateway as well as the Call Connection Agent (CCA) and the 

procedures for transporting user information and associated signaling and control 

information over the core packet network. 

Contents 


2. NGN Architecture Overview 

2.1 High-Level View of a Next Generation Network Architecture 



3–15




3–16 

3. NMGW Architecture and General Requirements 

3.1 Network Topologies and QoS Issues 

3.2 NMGW Functions 

4. Protocols for Transport, Connection Management, and Call Control 

4.1 Transport 

4.2 Connection Management and Control Using H.248 

4.3 Identifier Allocation, Release, and Management 

5. Call Processing 

5.1 R/SB GW-to-R/SB GW Call, Analog Line Case 

5.2 Error Cases During Call Establishment 

GR-3070-CORE, Voice over Packet: NGN Element Management System 

(EMS) Generic Requirements 

This document describes the functionality and interfaces for a Voice over Packet 

(VoP) Element Management System (EMS). The VoP EMS will operate at the 

Element Management Layer (EML) of the Telecommunications Management 

Network (TMN) architecture. In general, this layer has responsibility for functions 

such as control and coordination of VOP Functional Elements (FEs), providing a 

gateway to VoP FEs for the Network Management Layer (NML) and higher layers, 

and maintenance of statistics and history pertaining to the VoP FEs. More 

specifically, this document details a set of ‘generic’ functional requirements on a 

VoP EMS to support the management of VoP networks and services. This GR 

provides network management generic requirements that are common across the 

VoP FEs as well as requirements for network management interfaces to each of the 

VoP FEs and the VoP Billing Agent. In addition, this document specifies network 

management functional requirements specific to each of the VoP FEs across the 

Configuration Management, Fault Management, Performance Management, and 

Security Management functional areas. This document is intended to be used as a 

functional and interface requirements reference in the design and implementation 

of a VoP EMS. Additionally, the document can be employed for testing and 

verification of the EMS functions and interfaces. To demonstrate the potential use 

of the requirements provided in this document, the GR also details several example 

operations scenarios. 

Contents 





2.3 Interfaces and Protocols




3. VoP Network Management Architecture 

3.1 Overview of NGN VoP Network Management Strategy 

4. Configuration Management 

4.1 Capacity Installation 

4.2 Service Activation 

4.3 Status and Control 

5. Fault Management 

5.1 RAS Quality Assurance 

5.2 Alarm Surveillance 

5.3 Fault Localization 

5.4 Testing 

6. Performance Management 

6.1 General Requirements 

6.2 Performance Monitoring Requirements 

7. Security Management 

7.1 VoP EMS Security Features 

7.2 Prevention 

7.3 Detection 

7.4 Containment and Recovery 

7.5 FE Security Administration 

8. Management Interface Requirements 

8.1 CORBA 

8.2 SNMP 

8.3 CMIP 

8.4 Bulk Data Transfer 

Appendix A: Configuration Management Scenario 

Appendix B: Fault and Performance Management Scenario 

GR-3071-CORE, VoP Element Management System (EMS) - Network 

Management System (NMS) Interface Generic Requirements 

This Generic Requirements (GR) document provides an information model 

definition that supports the Voice over Packet (VoP) Element Management System 

(EMS) to Network Management System (NMS) interface. This GR contains both a 

logical model and the associated CORBA IDL interface definition in support of the 

VoP EMS-NMS management interface. This GR provides a set of ‘generic’ 

requirements on the interactions between a VoP NMS and VoP EMSs that manage 

Call Connection Agents (CCAs), Signaling Gateways (SGWs), Trunk Gateways 

(TGWs), and Access Gateways (AGWs). This GR is intended to be used as an 

interface requirements reference in the design and implementation of the Voice 

3–17




3–18 

over Packet EMS and NMS. Additionally, the GR can be employed for testing and 

verification of the VoP EMS-NMS interface functions. The following industry 

communities are potential users of these requirements: - VoP network element 

suppliers wanting to develop, test, and package EMS-NMS functionality with VoP 

network equipment - Third party software providers wanting to develop and test 

EMS-NMS functionality for single or multi-vendor VoP network equipment - VoP 

network and service providers wanting requirements to drive the evaluation, 

selection, and testing of network element supplier equipment. 

Contents 






3. VoP Network Management Architecture 

3.1 Overview of NGN VoP Network Management Strategy 

4. Logical Information Model 

4.1 Class Diagram 

4.2 Inheritance Diagram 

4.3 CCA Managed Element 

4.4 TGW Managed Element 

4.5 AGW Managed Element 

4.6 SGW Managed Element 

4.7 BA Managed Element 

4.8 CCA-CCA Interface 

4.9 CCA-AGW Interface 

4.10 AGW-CCA Interface 

4.11 CCA-SGW Interface 

4.12 SGW-CCA Interface 

4.13 CCA-TGW Interface 

4.14 TGW-CCA Interface 

4.15 CCA-BA Interface 

4.16 BA-CCA Interface 

4.17 Recording Parameter 

4.18 Core Network Interface 

4.19 EMS-CCA Interface 

4.20 EMS-AGW Interface 

4.21 EMS-TGW Interface 

4.22 EMS-SGW Interface 

4.23 EMS-BA Interface 

4.24 UDP Current Data 

4.25 IP Current Data 

4.26 Ethernet Current Data




4.27 RTP Current Data 

4.28 M3UA Current Data 

4.29 MEGACO Current Data 

4.30 ISDN L3 Current Data 

4.31 BICC Current Data 

4.32 H.248’ Current Data 

4.33 IUA Current Data 

4.34 SCTP Current Data 

4.35 MTP3 Current Data 

4.36 SS7 Link Set Current Data 

4.37 SS7 Link Marginal Performance Current Data 

4.38 SS7 Link Current Data 

4.39 SS7 Destination Current Data 

4.40 M3UA Systems Total Current Data 

4.41 Processor Current Data 

4.42 Equipment Unit Current Data 

4.43 ATM Current Data 

4.44 Call Related Procedures Current Data 

4.45 Call Processing Current Data 

4.46 Congestion Current Data 

4.47 Transport Current Data 

4.48 MTP2 Profile 

4.49 MTP3 Profile 

4.50 MTP2 Congestion-Threshold Parameter Profile 

4.51 M3UA ASP Parameter Profile 

4.52 IUA ASP Parameter Profile 

4.53 SCTP Parameter Profile 

4.54 Subscriber Profile 

4.55 Directory Number 

4.56 Analog Subscriber Line 

4.57 ISDN BRI/PRI Subscriber Line 

4.58 DS1 PBX Trunk 

4.59 IDLC Interface 

4.60 Trunk Group 

4.61 Trunk Circuit 

4.62 Trunk Termination Point 

4.63 SGW SS7 Link Set 

4.64 SS7 Destinations 

4.65 SS7 Signaling Link 

4.66 SGW SS7 Signaling Routes 

4.67 Log 

4.68 Current Data 

4.68.1 History Data 

4.69 CurrentDataR1 

4.70 HDScanner 

4.71 Threshold Data 

4.72 Managed Element 

3–19




3–20 

4.73 Equipment 

4.74 Software 

4.75 CircuitPack 

4.76 Termination Point 

4.77 Equipment Holder 

4.78 Link End 

Appendix A: Information Model IDL 

A.1 IDL Definition




3.3 NGN Special Reports (SR) Documents 

This section lists all the Telcordia Special Reports documents related to NGN. A 

Document Abstract and an abridged Table of Contents for each document is 

provided. 

SR-4717, Voice Over Packet in Next Generation Networks: An Architecture 

Framework 

The network of the future will be dominated by data, and Next Generation 

Networks (NGN) are being built for this purpose. At the heart of NGN is Voice over 

Packet (VoP), a packet-switched architecture that includes Voice over Internet 

Protocol (VoIP), Asynchronous Transfer Mode (ATM), and Frame Relay. In such 

packet-based environments, voice, data, fax, and video will be run over a single 

network. The result will be network and operations cost efficiencies and an 

increase in carrier revenues through the creation of new services. This Special 

Report explains the essential elements needed to build VoP networks. It provides a 

comprehensive framework for the support of voice and other narrowband services 

over packet-based networks. The VoP network that is discussed in this document 

places significant emphasis on interoperability, scalability, and seamless 

interworking with the Public Switched Telephone Network (PSTN). Such issues 

will be important for the VoP solution to be widely deployed. This document is 

organized into 7 sections: Section 1 presents introductory and background 

information, and discusses the motivation for Voice over Packet. Section 2 presents 

an overview of the current industry and standards activities on VoP, and discusses 

the need for VoP Generic Requirements (GRs). Section 3 identifies characteristics 

of a VoP network, such as network services, network capabilities, as well as its 

relationship with the Next Generation Network. Section 4 describes the high-level 

VoP architecture framework, together with illustration of the call flows and 

identification of GRs needed for VoP. Section 5 discusses the functionality of the 

significant components of a VoP network. Section 6 presents the Operations and 

Maintenance framework for VoP and the major issues involved. Section 7 discusses 

the migration strategies for various existing networks toward the VoP network 

discussed, and the migration beyond VoP and toward NGN. 

Contents 

1. Introduction and Background 

2. Current Industry Status 

2.1. Network Operators 

2.2. Supplier Segment 

2.3. Standards and Forum Segment 

2.4. Need for Generic Requirements 

3–21




3–22 

3. Characteristics of VoP Networks 

3.1. Target Customers and Markets for VoP Services 

3.2. Types of VoP Calls Supported 

3.3. VoP Services 

3.4. Role of CPE 

3.5. Network Aspects 

3.6. Business Aspects 

3.7. Regulatory/Public Policy Aspects (U.S.) 

3.8. Relationship of VoP Networks to Next Generation Networks 

4. Technology and Architecture Framework 

4.1. Key Technology Considerations in Industry 

4.2. Architecture for Voice over Packets 

4.3. Sample Call Flows 

4.4. Implementations of Framework Architecture in Physical Nodes 

4.5. Roadmap for Generic Requirements 

5. Functional Requirements for VoP Network 

5.1. Gateway Requirements 

5.2. Call Connection Agent Requirements 

5.3. Service Agent Functions 

5.4. Core Network Functional Requirements 

5.5. Support for End User Services 

5.6. End-to-End Performance Requirements in Packet Based Networks 

5.7. Billing Usage Measurements Requirements 

5.8. Security Requirements 

6. Operations and Management Architecture 

6.1. Introduction 

6.2. Business Processes and Functions 

6.3. Information Architecture 

6.4. Framework to Structure Solutions 

7. Evolution to NGN 

7.1. Migration of PSTN/ISDN Circuit-Switched Networks to VoP 

7.2. Migration from First Generation IP Voice Solutions to VoP 

7.3. Migration from Wireless Networks to VoP 

7.4. Evolution of VoP Networks to Next Generation Networks 

Appendix A: Features and Abilities 

A.1. General Features 

A.2. Custom Calling Features 

A.3. CLASS Features 

A.4. Centrex Features 

A.5. Other Features 

A.6. ISDN Features 

A.7. AIN Features




Appendix B: Capabilities to be Supported by the VoP Network 

B.1. Originating Services/Capabilities 

B.2. Terminating Services/Capabilities 

B.3. Network Services/Capabilities 

Appendix C: Message Flows 

C.1. Sample Call Flows 

SR-5074, Integrating Voice and Data Services in Next Generation 

Networks - An Architectural Framework 

This research report and resource guide defines the architecture and network 

operations capabilities of Next Generation Networks (NGNs). It was written for 

industry stakeholders and observers seeking to understand the complex issues and 

emerging trends associated with offering integrated voice and data services to 

residential and business customers. This document places significant emphasis on 

integrated voice and data services, discussing applications and protocols as well as 

support for E911, Local Number Portability, security, and reliability. The report also 

describes new network elements to provide direct packet access to business and 

residential customers, and defines a framework for NGN in wireless networks. This 

document is a companion document to SR-4717, Voice Over Packet in Next 

Generation Networks: An Architectural Framework. Voice Over Packet is a 

packet-switched architecture that includes Voice over Internet Protocol (VoIP), 

Asynchronous Transfer Mode (ATM), and Frame Relay. 

Contents 


2. Industry Status of NGN 

2.1 Status of NGN in Carrier Networks 

2.2 VoP/NGN Activity in Industry Bodies 

3. Defining an Infrastructure for VoP in NGN 

3.1 Current Status of Architecture for VoP Defined in GR Program 

3.2 Enhancements to VoP Framework Architecture 

4. Enhancing the VoP Architecture Towards NGN 

4.1 Interworking of NGN VoP Networks with H.323 Equipment 

4.2 New Gateways and CPEs to be Supported for NGN 

4.3 Numbering and Addressing Issues 

4.4 Security in NGN 

4.5 Reliability in VOP/NGN 

5. Wireless Evolution to NGN 

5.1 Migration to Third Generation Wireless Networks 

5.2 Wireless Next Generation Network (WNGN) 

3–23




3–24 

5.3 Framework Architecture for WNGN 

5.4 Summary 

6. Features and Services for NGN 

6.1 Services in VOP/NGN 

6.2 Key Network Features Likely To Be Mandated for VOP/NGN 

6.3 Operator Services in VOP/NGN 

7. VOP/NGN Operations 


7.2 Operations Goals 

7.3 Key Business Processes 

7.4 Information Architecture 

7.5 VOP/NGN Operations Framework 

7.6 Logical Management Architecture and Interfaces 

7.7 Gap Assessment of Industry VOP/NGN Operations Activities 

Appendix A: Proposed 3GPP and 3GPP2 All IP Architectures 

A.1 Proposed 3GPP All IP Architecture 

A.2 Proposed 3GPP2 All IP Network 

A.3 Alignment of 3GPP and 3GPP2 All-IP Architectures 

SR-5093, VOP: Operator Services in an NGN 

This document describes a Next Generation Network (NGN)/Voice Over Packet 

(VOP) architecture that is capable of providing operator services by either including 

the operator services capabilities within NGN/VOP functional entities or by 

interworking with existing Operator Services Systems (OSSs). The NGN/VOP 

operator services may be provided to customers served by the NGN/VOP 

architecture or to customers served by the Public Switched Telephone Network 

(PSTN). The architecture described in this document is based on the NGN/VOP 

architecture described in SR-4717, Voice Over Packet in Next Generation 

Networks: An Architectural Framework and SR-5074, Integrating Voice and Data 

Services in Next Generation Networks -An Architectural Framework. The 

architecture definition in this document supports existing operator services, such 

as busy line verification/interrupt, directory assistance, directory assistance call 

completion, calling card, and 0-/assist, and new operator services, such as enhanced 

directory assistance, live web-site assistance, and e-mail and voice mail to and from 

operators. This SR identifies new Functional Entities, describes call flows for many 

scenarios, proposes information flows among the Functional Entities, and 

discusses protocol alternatives for the new interfaces. 

Contents 


2. General Information 

2.1 Business Drivers for Migration Toward an NGN




2.2 Key NGN/VOP Operator Services Architecture Objectives 

2.3 VOP Architecture 

2.4 Operator Services Architecture Description 

3. NGN/VOP Operator Services Architecture 

3.1 Overview 


3.3 Logical Interfaces 

3.4 NGN/VOP Operator Services Architecture Assumptions 

4. Call Flows 

4.1 Call Completion Operator Services 

4.2 Queuing and Call Distribution 

4.3 Verbal Request for Data 

4.4 Web-Site Assistance 

4.5 Messages to Operators 

4.6 Busy Line Verification/Interrupt 

4.7 Alternate Billing 

4.8 Connection Hold and Ringback 

4.9 Transfer 

4.10 1+ Coin Sent Paid 

4.11 Real-Time Rating 

4.12 Intercept 

4.13 Non-published Messaging 

4.14 Monitor 

4.15 Future NGN/VOP Operator Services Call Flows 

5. Information Flows and Protocol Alternatives 

5.1 Protocol Overview 

5.2 CCA to BTN Interface 

5.3 CCA to Operator Workstation Interface 

5.4 CCA/OS SA to Operator Workstation Interface 

5.5 QCD to Operator Workstation Interface 

5.6 CCA to VFS Interface 

5.7 CCA/OS SA to VFS Interface 

5.8 CCA to Signaling Gateway Interface 

5.9 CCA to Trunk Gateway Interface 

5.10 CCA/OS SA to QCD Interface 

5.11 WCS to QCD Interface 

5.12 WCS to Operator Workstation Interface 

5.13 CCA/OS SA to Agent Message Handler Interface 

5.14 Agent Message Handler to QCD Interface 

5.15 Agent Message Handler to Operator Workstation Interface 

5.16 CCA to CCA Interface 

5.17 CCA to AGW Interface 

5.18 CCA to RGW Interface 

5.19 CCA/OS SA to H.323-capable CPE Interface 

3–25




3–26 

5.20 QCD to Force Management System (FMS) Interface 

5.21 CCA/OS SA to Operator Services Database Interface 

5.22 Operator Workstation to Automated Monitoring System Interface 

6. Recommended Path Forward 

SR-NOTES-SERIES-09, Telcordia Notes on CPE for Next Generation 

Network Access 

This release in the popular Telcordia Notes on . . . series of documents, Telcordia 

Notes on CPE for Next Generation Network Access, looks at the end-user customer 

premises equipment available for accessing a Next Generation Network (NGN). 

Often referred to as a Customer Gateway (CGW) or an Integrated Access Device 

(IAD), these devices allow a user to access network-provided voice and data 

services via a packet-based broadband access facility. This document examines the 

functionality required of such devices and provides a survey of currently available 

products. With Telcordia Notes on CPE for Next Generation Network Access, you 

will learn about: - The evolution of NGN - NGN architecture and current status of 

deployment - Hybrid architectures This document also contains CGW and IAD 

Product Information and provides the capabilities of each product. A 

comprehensive Glossary and Reference List are included. With the Notes on . . . 

series, Telcordia Technologies has devised a starting point for your search through 

the rapidly developing world of telecommunications. Written by the authors of the 

successful Telcordia Notes on the Network document (SR-2275), this series 

similarly contains technical material of interest to engineering and planning groups, 

as well as descriptions of the characteristics and background of these subjects in 

layman's terms. The difference is that Telcordia Notes on . . . zeros in on one 

technology in each document and breaks it down into manageable terms. From the 

history, background, and basic elements through a discussion of what the future 

may bring, our subject matter experts cover the important aspects in as few words 

as possible. The CD-ROM version of this document is packaged together with the 

paper edition as an added bonus. 

Contents 

1. Overview 

2. Description of Next Generation Network Architecture 

2.1 The NGN Core Network 

2.2 The NGN Core Network Elements 

2.3 The NGN Access Network 

2.4 NGN Standards and Specifications 

3. Detailed Description of the CGW/IAD 

3.1 CGW/IAD Role in the NGN 

3.2 CGW/IAD Functions 

4. Listing of Customer Gateways and Integrated Access Devices




5. Product Information 

5.1 Accelerated Networks AN-24/28 

5.2 Accelerated Networks AN-30 

5.3 Accelerated Networks AN-32 

5.4 Accelerated Networks AN-28-BRI 

5.5 Accelerated Networks AN-30-PRI 

5.6 Alcatel Speed Touch 710 IAD 

5.7 Cisco Systems 827-4V 

5.8 Cisco IAD2420 Series 

5.9 Cisco CVA120 Series 

5.10 Clarent CPG 101 Gateway 

5.11 Clarent CPG 2102S Gateway 

5.12 CopperCom MXR 100 




5.16 Efficient Networks 7800 Family NG-IAD 

5.17 Efficient Networks SpeedStream 8600 Series 

5.18 Integral Access - PurePacket OUTburst - Vx 

5.19 Jetstream Communications IAD-802 


5.21 Jetstream Communications IAD-Flex 160 


5.23 Lucent Technologies CellPipe IAD 4A/4S 

5.24 Lucent Technologies CellPipe IAD 8S 

5.25 Lucent Technologies CellPipe IAD 8DSU 

5.26 Lucent Technologies CellPipe MOD IAD 

5.27 Nortel Networks - Universal Edge 624 

5.28 Polycom NetEngine 6100-4 

5.29 Polycom NetEngine 6200 and 6300 Series 

5.30 Polycom NetEngine 7200 and 7300 Series 

5.31 Polycom NetEngine 8000 

5.32 Tollbridge Technologies TB55 

5.33 Tollbridge Technologies TB50 

5.34 Zhone Technologies - Z-Edge 64 

SR-NOTES-SERIES-11, Telcordia Notes on IP Centrex 

This release of the popular Telcordia Notes on . . . series, Telcordia Notes on IP 

Centrex, discusses IP Centrex from the network architecture, deployment, and 

marketing perspectives. IP Centrex is a network-based service that uses VoIP in the 

enterprises LAN and on the broadband access facility to the service providers 

network. IP Centrex can provide a number of new capabilities and benefits for 

enterprise customers and their service providers. Readers will learn: - the two major 

architectural approaches for offering IP Centrex, including the network equipment 

and Customer Premises Equipment (CPE) required for each approach - the benefits 

3–27




3–28 

and applications that IP Centrex customers can enjoy - the advantages IP Centrex 

offers to service providers - the technical hurdles that equipment suppliers and 

service providers must address before IP Centrex service can be offered - how IP 

Centrex and IP PBX compare to each other. This SR is intended for three types of 

readers: - Enterprise customers currently using conventional Centrex or 

conventional PBXs. The information in this SR can help customers in their 

discussions with potential service providers or PBX suppliers. (Note the SR does 

not discuss the capabilities of any particular PBX model or Centrex offering.) - 

Service providers, including Local Exchange Carriers and Application Service 

Providers. The information in this SR can help service providers better evaluate 

various alternatives as they formulate IP Centrex plans. - Suppliers of IP Centrex 

network equipment or CPE. The information in this SR can help equipment 

suppliers better understand the challenges that their service provider customers are 

facing. With the Notes on . . . series, Telcordia Technologies has devised a starting 

point for your search through the rapidly developing world of telecommunications. 

Written by the authors of the successful Telcordia Notes on the Network document 

(SR-2275), this series similarly contains technical material of interest to 

engineering and planning groups, as well as descriptions of the characteristics and 

background of these subjects in layman's terms. The difference is that Telcordia 

Notes on . . . zeros in on one technology in each document and breaks it down into 

manageable terms. From the history, background, and basic elements through a 

discussion of what the future may bring, our subject matter experts cover the 

important aspects in as few words as possible. The CD-ROM version of this 

document is packaged together with the paper edition as an added bonus. 

Contents 


2. Centrex History 

3. IP Centrex Architectures 

3.1 Class 5 Switch Architecture 

3.2 Softswitch Architecture 

3.3 IntraLAN Voice Paths 

4. IP Centrex Customer Premises Equipment (CPE) 

4.1 Station Equipment 

5. Benefits of IP Centrex for Customers 

5.1 General Centrex Benefits 

5.2 IP Centrex Benefits 

6. IP Centrex Applications and Configurations 

6.1 The Introduction of IP Phones 

6.2 Replacement of Legacy Station Equipment with IP Phones 

6.3 Hotelling 

6.4 The Use of Customer Gateways 

6.5 Unrestricted Multilocation Centrex for Branch Offices




6.6 Unrestricted Multilocation Centrex for Telecommuting Application 

6.7 Virtual Call Centers 

6.8 Road Warriors 

7. Benefits of IP Centrex for Service Providers 

7.1 Benefits Applying to Class 5 Switch and Softswitch Platforms 

7.2 Benefits Applying to Class 5 Switch Platforms 

7.3 Benefits Applying to Softswitch Platforms 

8. Hurdles and Challenges to IP Centrex Deployment 

8.1 Network Equipment Challenges 

8.2 Service Provider Challenges 

8.3 Enterprise Challenges 

8.4 Softswitch Challenges 

9. IP PBXs 

9.1 Benefits of IP PBXs and IP Centrex 

10. Conclusions 

10.1 IP PBXs and IP Centrex 

10.2 Established Service Providers and Greenfield Operators 

10.3 Class 5 Switch and Softswitch IP Centrex 

Appendix A: IP Telephony Protocols for IP Centrex 

A.1 Class 5 Switch-Based IP Centrex 

A.2 Softswitch-Based IP Centrex 

Appendix B: Centrex Features 

B.1 Analog-Like Centrex Features 

B.2 ISDN Features Available for IP Centrex Stations 

3–29




3–30



NGN Subject Index 

4 


Table 4-1 Subject-to-Document Cross-Reference 

Subject Telcordia Document 

AGW Signaling 

Requirements 

GR-3055 

Announcements GR-3055 

Call Clearing/Disconnect GR-3055 

Call Connection Agent (CCA) 

Signaling Requirements 

GR-3055 

Call Origination GR-3055 

Call Termination GR-3055 

Core Network Signaling 

Requirements 

GR-3055 

Identifier Allocation, Release, 

and Management 

GR-3055 

Access Interface 

Requirements 

GR-3055 

Conventional DS1 Interface 

to a PBX - Option 

GR-3055 

IDLC Interface - Option GR-3055 

ISDN Basic Rate Interface - 

Option 

GR-3055 

ISDN PRimary Rate Interface 

- Option 

GR-3055 

Voice-Grade Analog 

Interfaces 

Architecture 

GR-3055 

Access Gateway (AGW) GR-3055 

Call Connection Agent (CCA) GR-3051 

Customer Gateway (CGW) GR-3061 

NGN GR-3061, GR-3062, SR-5074 

Network Mediation Gateway 

(NMGW) 

GR-3062 

Signaling Gateway (SGW) GR-3053 

Trunk Gateway (TGW) GR-3054 

4–1




4–2 



SS7 Network Access 

Architecture 

GR-3053 

VoP GR-3051, GR-3053, GR-3054, GR-3055, GR-3070, 

GR-3071, SR-4717, SR-5074, SR-5093 

Billing Agent Accounting 

Management Requirements 

GR-3058 

Operations GR-3058 

Usage Record File Storage GR-3058 

Usage Record Generation & 

Formatting 

GR-3058 

Usage Record Outputting GR-3058 

Usage Validation GR-3058 

Call Flows GR-3060 

Calling Name Identification GR-3060 

Calling Number Identification GR-3060 

Call Waiting GR-3060 

Local Number Portability GR-3060 

Toll-Free Service 

Connection Call Procedures 

GR-3060 


BGW/VFS Gateway GR-3051 


Call Routing GR-3051 

CCA to CCA GR-3051 

Core Network Connection 

Procedures 

GR-3054 


Non-Call-Related Procedures GR-3054 

Normal Call-Related 

Procedures 

GR-3054 

Trunk Gateway (TGW) GR-3051; GR-3054 

User and Service Profiles 

Fault Management 

GR-3051 


Alarm Surveillance GR-3070







Element Management System GR-3070 

(EMS) 

Fault Localization 

RAS Quality Assurance GR-3070 


Testing GR-3070 


High Level Requirements 




Features GR-3060 

Line-Side Interface Service GR-3055 

Criteria 

Modularity, Scalability & GR-3051 

Extensibility 

Resource Management & GR-3051 

Connection Control 

Routing Analysis and Name/ GR-3051 

Address Resolution 

Signaling Call Processing GR-3055 

Control 



User Information Path GR-3055 

Connection Control 

Individual Services GR-3060 

Supported in VoP Networks 

Large Business Services for GR-3060 

Analog Lines 

Large Business Services for GR-3060 

ISDN BRIs 

Residential & Small Business GR-3060 

Services for Analog Lines 

4–3




4–4 



Residential & Small Business 

Services for ISDN BRIs 

GR-3060 

Services foe Conventional 

DS1 Trunks 

GR-3060 

Services for ISDN PRIs 

Interface Requirements 

GR-3060 


Bearer Transport Interface GR-3054 

Billing Agent (BA)/ 

Application Systems 

GR-3058 

Billing Agent (BA)/Element 

Management System 

GR-3058 


CCA/Billing Agent (BA) GR-3058 

CCA to BGW or VFS Gateway 

Control 

GR-3051 

CCA-to-CCA Interface GR-3051 

Core Network/CCA Signaling 

Interfaces 

GR-3053 

Element Management System 

(EMS) 

GR-3070 

Gateway Connection Control 

Transport 

GR-3054 

Gateway Control Interface GR-3054 

Interworking Function GR-3053 

Lower Layer Requirements GR-3051 

NGN Accounting 

Management 

GR-3058 

Services, Support & 

Operations Interfaces 

GR-3051 


SS7 Network Protocol 

Interface 

GR-3053 

Trunk Gateway (TGW) GR-3054






Interface to the Core 

Network 

GR-3055 

Bearer Connection Control 

Interface 

GR-3055 

Bearer Transport Interface GR-3055 

CCA to AGW Control 

Interface 

GR-3055 

Core Network Assumptions GR-3055 

Simple Control Transmission 

Protocol (SCTP) 

GR-3055 

Logical Information Model 

Management & Operations 

GR-3071 



Configuration Management GR-3051; GR-3053; GR-3054; GR-3055; GR-3070 

Fault Management GR-3051, GR-3053; GR-3054; GR-3055 

Performance Management GR-3051; GR-3053; GR-3054; GR-3055 



Media Processing GR-3054 

Comfort Noise Insertion GR-3054 

Continuity Tone Detection, 

Generation, and Loop-back 

GR-3054 

Echo Cancellation GR-3054 

Encoding & Transcoding 

Functions 

GR-3054 

Media Detection GR-3054 

Packetization Functions GR-3054 

Receive Path Delay GR-3054 

Silence Detection/ 

Suppression 

GR-3054 

Network Element 

Performance 

GR-3059 

Access Gateway GR-3059 

Call Connection Agent GR-3059 

4–5




4–6 



Core Router GR-3059 

Information Transfer GR-3059 

Performance of Network 

Elements 

Signaling Gateway GR-3059 

Signaling Performance of GR-3059 

Network Elements 

Trunk Gateway GR-3059 

Operator Services in an SR-5093 

NGN 

Performance Management 





(EMS) 

Monitoring Requirements GR-3070 



VoP End-to-End Performance GR-3059 

Protocols 

CCA-AG for VoP Network GR-3060 

Services 

CCA-CCA for VoP Network GR-3060 

Services 

CCA-SG for VoP Network GR-3060 

Services 


Network Mediation Gateway GR-3062 

Framework 

Requirements 





(EMS)






Network Mediation Gateway GR-3062 

Framework 

NGN Accounting 

GR-3058 

Management 



VOP End-to-End 

GR-3059 

Performance 

VoP EMS-NMS GR-3071 

VoP Network Services GR-3060 

Security Management 

Containment & Recovery GR-3070 

Detection GR-3070 

FE Security Administration GR-3070 

VoP EMS Security Features GR-3070 

Services GR-3061 

Defining NGN Services & GR-3061 

Applications 

Extending PSTN & ISDN GR-3061 

Services to NGN 

New NGN Applications for GR-3061 

CGW End Users 

NGN Reference Model - GR-3061 

Gateways, Networks, & 

Services 

Third-Party Service GR-3061 

Development for NGN 

Services 

Voice, Data, Video, & GR-3061 

Multimedia in an NGN 

Signaling Performance GR-3059 

Access Function Allocation GR-3059 

of Delay 

Access Function Objectives GR-3059 

Access Function 

GR-3059 

Performance Parameter 

Definitions 

4–7




4–8 



Classification of Call 

Attempts & Call Releases 

GR-3059 

Delay Concepts GR-3059 

Disengagement Function 

Allocation Rules 

GR-3059 


Objectives 

Gr-3059 


Performance Parameter 

Definitions 

GR-3059 

Spatial & Environmental 

Requirements 

GR-3053 

Equipment GR-3053 

Electromagnetic & Electrical 

Environment 

GR-3053 

Transport Performance 

Requirements 

GR-3059 

Objectives & Allocation Rules GR-3059 

Performance Parameters GR-3059 

QoS Mappings of ATM to IP 

(for IP over ATM) 

GR-3059 

Reference Events for 

Transport Parameters 

GR-3059 

Usage GR-3058 

Measurement Outputting GR-3058 

Measurement Storage GR-3058 

Record Generation & 

Formatting 

GR-3058 

Record File Storage GR-3058 

Record Outputting GR-3058 

Validation GR-3058 

User Information 

Processing Requirements 

GR-3055 

Echo Cancellation GR-3055 

Fax/Modem Detection GR-3055






Packetization/ 

Depacketization 

GR-3055 

Receive Path Delay Control GR-3055 

Silence Detection & Comfort 

Noise Insertion 

GR-3055 

VoP Network Services GR-3060; SR-5074 

VoP Performance Models GR-3059 

Measurement Points GR-3059 

Performance Significant 

Reference Events 

GR-3059 

Signaling Reference Models GR-3059 

Transport Reference Models GR-3059 

4–9




4–10



Telcordia Contacts and General Information 

5 


This section presents general information on various topics of interest in 

Telcordia, including: 

The Value and Role of Telcordia Generic Requirements and the Benefits of 

Funding and Participating in Telcordia Generic Requirements projects 

Contact information on Telcordia subject matter experts for this technology 

area 

How to order Telcordia documents via phone, fax, mail, or on-line 

A review of some new and exciting Telcordia resources 

A listing of selected Telcordia websites. 

5.1 The Importance of Telcordia Generic Requirements 

This section briefly reviews some important features related to Telcordia Generic 

Requirements, including their value and role in industry and why funding their 

development can help your company shape industry standards. 

5.1.1 The Value and Role of Telcordia Generic Requirements 

Open standards such as Telcordia GRs benefit consumers, enterprises, 

service/network providers, equipment suppliers, and even nations by 

Promoting interoperability and interconnection 

Promoting innovation by establishing minimum requirements 

Stimulating competition among service providers and suppliers by supporting 

interconnection in a multi-service provider/supplier environment 

Fostering economies of scale by establishing common requirements across a 

larger user community, thereby potentially reducing unit costs. 

5.1.2 Why Participate in Telcordia Generic Requirements? 

Telcordia invites all interested parties to participate in the ongoing evolution of 

Generic Requirements for the telecom industry. Participants can provide 

nonproprietary input into the technical description of the material, comment on 

the draft text, review drafts of proposed revisions, and help resolve issues. They 

can also provide input for the final content of the proposed Generic 

Requirements. Service providers and equipment suppliers who participate in 

developing the requirements benefit from potential reduced costs in future 

network operations and product development, and from the ability to influence 

5–1




5–2 

the technical content of the Generic Requirements. In addition, participants have 

access to requirements information and trends, as they evolve, before publication 

to the industry in general. 

The Telcordia GR process is attractive to customers because it provides them 

with an opportunity to 

Shape the direction of work related to technologies and services that can 

potentially increase revenues or reduce the costs of service or product 

planning, implementation, or operations 

Have early access to requirements information that can be factored into 

service or product planning, and improve their time-to-market 

Influence the technical content of the GR document 

Have a decision-making role in resolving technical disputes 

Work with other industry leaders to discuss their needs and solutions that can 

satisfy them 

Receive a pre-publication copy of the GR before it is generally available to the 

public, and receive a final publication copy of the GR as soon as it can be 

distributed. 

Another valuable feature of GR development is that companies participating in 

GR development work are granted a license to copy GR text for use internally 

(including their majority affiliates), and to incorporate GR text into product and 

service specifications. This is important to companies when they are 

communicating in the global economy and trying to reduce the costs associated 

with documenting the features and characteristics of products and services. 

In October of each year, a GR Forecast is announced to provide the industry with 

a first look at the proposed Telcordia generic requirements development projects 

for the coming year. The listing is not all-inclusive, as many other projects emerge 

throughout the year to meet customer needs as new technologies, service 

capabilities, or issues surface that can benefit from modifications to existing GR 

documents or necessitate development of new ones. 

If you are interested in learning more about participation opportunities for Fiber 

and Optical Technologies related generic requirements, you may contact any of 

the Telcordia Subject Matter Experts (SMEs) listed in Section 5.2. Also, a listing 

of all current Invitations to Fund and Participate, can be viewed at 

http://www.telcordia.com/services/genericreq/index.html.




5.2 Telcordia Subject Matter Experts (SMEs) 

The following Telcordia contacts can assist you with answering questions about 

these documents: 

Anand Akundi 

Telcordia Technologies 

One Telcordia Drive, Room 4A605 


Phone: + 1.732.699-6031 

E-Mail: aakundi@telcordia.com 

5.3 General Document Ordering Information 

Telcordia documents may be ordered via phone, fax, mail, or on-line. They may 

be ordered from the Telcordia Information SuperStore (see Section 5.3.1), 

Telcordia Customer Service (see Section 5.3.2), or via the AXESS Point service 

(see Section 5.3.3). 

5.3.1 Telcordia Information SuperStore 

The Telcordia Information SuperStore contains the product line of technical 

documents and other information products. You can order, search, or browse the 

Store at http://telecom-info.telcordia.com. 

To Order Documents Online From the Telcordia Information SuperStore 

1. Go to the SuperStore Web site: http://telecom-info.telcordia.com 

(At this site, the Search and Browse selections provide access to the 

Telcordia catalog of technical information.) 

2. If you know the document number, enter it in the Search box in the left 

margin and click Search. 

3. Click on the desired product match. 

If you do not know the document number, do the following: 

1. Click on Search located on the top bar. 

2. In the Keywords field, enter the keywords (or document number), then click 

Submit Search. 

3. Click on the desired product match. 

5–3




5.3.2 Customer Service 

5–4 

Telcordia Customer Service is available to take your document order, or to field 

any questions you might have concerning your order or on general topics within 

the company. You may contact Telcordia Customer Service either via phone, fax, 

e-mail, or USA mail. 

To Contact Telcordia Customer Service 

Telcordia Customer Service 

One Telcordia Drive, Room 1B180 


+ 1.732.699.5828 (Worldwide) 

+ 1.732.336.2226 (FAX) 

http://telecom-info.telcordia.com 

5.3.3 AXESS Point Service 

AXESS Point service is your gateway to Generic Requirements documents. 

AXESS Point is the on-line technical information resource that delivers up-to-date 

Telcordia technical documents directly to your desktop, and provides a flexible 

full-search capability across the entire Telcordia document database. To view a 

demonstration of AXESS Point service, visit 

http://telecom-info.telcordia.com/site-cgi/ido/index.html 

When activated at your company, AXESS Point service provides a direct, userfriendly, 

secure link to our integrated information delivery service that provides 

Web-based access to your Telcordia Technologies documentation. The service is 

convenient, increases productivity by eliminating the need for paper documents, 

and reduces the time spent searching for information. 

To request Telcordia AXESS Point service, contact your local Telcordia Account 

Executive, or use the following options: 

Phone: Customer Service Center 

+ 1.732.699.5828 (Worldwide) 

FAX: + 1.732.336.2226




5.4 Other Telcordia Resources 

As a world-wide leader in telecommunications, Telcordia is constantly evolving 

by adding products and other resources to its vast product line. The following 

subsections discuss just a few of some of the more innovative product areas. 

5.4.1 The Telcordia Standards Knowledgebase (TSK) 

The Telcordia Standards Knowledgebase can be your eyes and ears in the 

telecommunications industry standards arena. It will help you keep up with the 

IEC, IETF, ITU-T, SG 16, and many other telecom standards bodies. You will also 

benefit from the latest technical analyses of standards for Wireless, NGN/IP 

Telephony, Optical Networking, Numbering, and more. 

Authored by our technical experts, each report contains a comprehensive review 

and an in-depth analysis of the key issues discussed at specific telecom standards 

meetings. Reports become accessible to you within five business days of each 

meeting, and can be viewed on-line, or downloaded and printed. 

Yearly report package subscriptions are available for the following topics: 

NGN/IP Telephony 

Optical Transmission & Networking 

Wireless 

Network Management 

Numbering 

National and International Standards Policy 

T1 Technical subcommittees 

Quarterly Report Collection 

Regulator’s Package. 

Telcordia also offers full access to our entire database of reports on a 

subscription basis. 

To request more detailed information on these, and other report packages, 

contact Cliff Halevi at 1-866-TSK-INFO, or at chalevi@telcordia.com. 

5.4.2 Telcordia Routing Administration 

The Telcordia Routing Administration (TRA) supports the telecommunications 

industry by providing essential data services and products for completion and 

proper rating of Public Switched Telephone Network (PSTN) calls. TRA is the 

industry-recognized source of routing and rating information products. Through 

data collection, validation, and dissemination processes for its clients, TRA 

5–5




5–6 

shares numbering and networking information and access to the local exchange 

environment in a cost-effective, accurate, and timely manner. 

Through the Telcordia Fair Share Plan, the TRA data collection process gives 

local service providers the ability to report data on Central Office Codes (also 

known as prefixes, exchanges, and NXXs), switch-to-switch homing, switch 

services, operator-to-operator routing, and other data, thus providing an effective 

means to report data used in rating a call. Rating data includes identifying the time 

zone a prefix is in and the basic location served by the prefix. Vertical and 

horizontal coordinates are provided for switch locations and for the rate center 

used in certain call rating processes. 

The following lists some TRA-related products: 

Telcordia LERG Routing Guide 

The Telcordia LERG Routing Guide helps to properly route and complete 

calls, prepares for the monthly changes in the PSTN network, and provides 

physical routing details to support interconnection agreements. Engineers 

responsible for call routing, switch translations, and switch homing 

arrangements, and those involved with supporting interconnection 

agreements, use the LERG Routing Guide on an ongoing basis. Key data 

elements include 

— North American Numbering Plan Central Office Codes 

— Signaling System 7 (SS7) Network Codes 

— Access Tandem Codes 

— Rate Centers and Localities 

— Tandem Homing Arrangements 

— Thousands Block Pooling Assignments, and other system codes. 

Telcordia TPM Data Source 

The Telcordia TPM Data Source provides data for accurate rating and billing 

of calls. Service providers can help to avoid revenue loss by utilizing the TPM 

Data Source to associate the appropriate Revenue Accounting Office (RAO) 

to NPA/NXXs. Key data elements include 

—Numbering Plan Area 

— NXX Code 

— Operating Company Number 

— Thousands Block Pooling Indicator 

— Vertical and Horizontal Coordinates data 

— Revenue Accounting Office 

— Portability Indicator.




Telcordia Area Code Split Exchange Diskette 

The Telcordia Area Code Split Exchange Diskette is used for maintaining 

databases containing telephone data for telemarketing, customer service, 

enterprise switchboard services, and others needing to prepare for upcoming 

area code splits and exchanges impacted by the splits. 

For a full catalog of TRA products and services, call TRA customer service at 

1.866.672.6997 (USA) or at + 1.732.699.6700 (Worldwide). 

5.4.3 Telcordia Numbering Services Center 

In today’s environment, obtaining and managing numbering resources is a 

complex and time-consuming process. Carriers are responsible for providing 

timely and accurate utilization and forecast data for geographic numbering 

resources, and assignees of numbering resources must have arrangements in 

place for inputting the necessary rating and routing information. In addition, 

applications for Central Office Codes (NXX), 1K Blocks (NXX-X), Operating 

Company Numbers (OCN), COMMON LANGUAGE® Location Identifiers 

(CLLI), Signaling System 7 (SS7) Point Codes, and International Mobile 

Subscriber Identifiers (IMSI) need to be planned and managed. 

The Telcordia Numbering Services Center integrates a diverse portfolio of 

telecommunications numbering services into “one-stop-shopping.” It will help 

you manage your numbering resources and obligations and meet the reporting 

requirements of the FCC, and help ensure that your information is reflected 

accurately in the Telcordia LERG Routing Guide. The Center is staffed by many 

experts with a combined 115 years of experience with domestic and international 

numbering and dialing issues. By helping to manage your numbering obligations, 

this service can help you maximize the efficiency of your numbering staff and 

concentrate instead on bringing in revenues and profits. It will help lower your 

costs, and provide the relevant information to the FCC and the LERG Routing 

Guide in the required formats. 

Telcordia also offers numbering administration services of new and innovative 

numbering conservation methodologies for both state and nationwide trials. 

Telcordia Numbering Consulting Services can outsource a service provider’s 

numbering administration functions or analyze and recommend methodologies 

for making those functions more efficient, allowing service providers to 

concentrate on their core business. 

Available services are: 

The Telcordia Number Resource Utilization/Forecast (NRUF) Services 

Each carrier is responsible for providing timely and accurate utilization and 

forecast data for geographic numbering resources to the North American 

Number Pooling Administration (NANPA) and the Pooling Administrator 

(PA). The sanction for noncompliance is the withholding of numbering 

resources by the NANPA and the PA. Service provider participation in the 

5–7




5–8 

semi-annual NRUF Report is mandatory so that more complete information 

can be gathered to improve forecasts of NPA code exhaust. In addition, 

because of the large amount of utilization and forecast data to be collected, 

electronic data collection and storage is utilized to improve efficiencies and to 

enhance data analysis and reporting capabilities. As such, the preferred 

electronic data filing methods are either electronic file transfer or electronic 

spreadsheet. 

Our NRUF filing services include storage, categorization, and analysis on a 

monthly basis, of each carrier’s number utilization information, and the 

preparation of the semi-annual NRUF Form 502 reports for electronic filing 

with the NANPA. Telcordia can also provide custom reports for carriers 

obligated to file special utilization reports with state regulatory agencies, as 

well as 1K Block assessment reports for carriers required to participate in 1K 

pooling. 

The Telcordia AOCN Services 

Applicants for numbering resources must have arrangements for an entity 

(internal or external) to act as their agent (known as the AOCN) for inputting 

the necessary rating and routing information into an integrated systems 

environment called the Business Integrated Routing and Rating Database 

System (BIRRDS). As the owner/operator of the BIRRDS database, Telcordia 

has unmatched expertise in populating all of the necessary fields on behalf of 

your company. Having your company’s routing and rating information 

correctly entered into BIRRDS is critical to effective routing and accurate 

rating of calls to your network. 

Telcordia Numbering Services 

Telcordia can be your one-stop shopping resource for all your numbering and 

addressing needs. Each of the services listed below can be subscribed to 

separately or be combined with others into custom service packages: 

— Central Office Code (NXX) and 1K Block (NXX-X) applications 

— Operating Company Number (OCN) applications 

— COMMON LANGUAGE® Location Identifier (CLLI) applications 

— SS7 Point Code and IMSI applications 

— 800 RESPORG services. 

Consulting Services 

Telcordia consultants can help you maximize the efficiency of your 

numbering staff and concentrate on bringing in revenues and profits by letting 

us help manage your numbering obligations. We offer: 

— Number Inventory Planning 

— Numbering OSS Analysis 

— Numbering Methods and Procedures Development




— Numbering Standards and Regulatory Consulting 

— Numbering Resource Acquisition Service. 

Services and Seminars 

If members of your staff need to come up to speed on current numbering 

processes and issues, or if they are interested in learning more about the hot 

new numbering topics such as ENUM, Unassigned Number Porting (UNP), 

Location Portability, or Individual Telephone Number (ITN) Pooling, we have 

the world leaders with this expertise available to discuss it with you today. 

Telcordia offers periodic and customized seminars on the current events in 

numbering technology and numbering regulation. 

For more information, please contact the Telcordia Numbering Services Center 

on-line at www.numberingcenter.telcordia.com 

5.4.4 Other Telcordia Websites of General Interest 

This section lists some other websites of general interest in Telcordia. 

http://www.telcordia.com/digest 

This website takes you to The Telcordia Digest of Technical Information. 

This is a monthly publication that provides the telecommunications industry 

with important, time-sensitive notices of Telcordia generic requirements work 

projects; these notices provide up-to-date information on new generic 

requirements that have become available, are being developed, or have been 

updated. Telcordia generic requirements documents are developed by 

telecommunications engineers and other technical specialists who are 

familiar with the stringent parameters of requirements work and understand 

the needs of local exchange carriers. We invite your company’s participation 

in this important work. 

http://www.telcordia.com/services/training/ 

This website contains detailed descriptions for over 600 telecommunications 

training courses, products, and services designed to help you improve your 

telecommunications knowledge and skills. 

5–9




5–10



Glossary 

Glossary Glossary 

Definition of Terms 

ABCD codewords — used on a GR-303-CORE interface to represent analog line 

states; for NGN access to a Class 5 switch, ABCD codewords are transferred 

across the packet interface between the IAD and Voice Gateway in the same 

virtual circuit used to carry bearer information (see Call Associated Signaling). 

Access Control List (ACL) — a security mechanism that defines the functions 

that a group of users can access. 

Access Gateway (AGW) — a NGN element that provides access to the NGN for 

traditional telephony interfaces like analog lines, BRI, PRI and non-ISDN 

trunks. 

Access Network — provides transport of packet information between the 

customer premises and the Core Network; bordered by the CGW/IAD and the 

NMGW. 

Address Resolution Protocol (ARP) — a protocol used by routers to map IP 

addresses to lower layer (Ethernet or ATM) addresses; specified in RFC 826. 

American National Standards Institute (ANSI) — the primary organization 

for fostering the development of technology standards in the United States. 

ANSI works with industry groups and is the United States member of the 

International Organization for Standardization (ISO) and the International 

Electrotechnical Commission (IEC). 

Assured Forwarding (AF) — see Differentiated Services. 

Asynchronous Transfer Mode (ATM) — a connection-oriented mechanism for 

transporting data in packet networks; ATM carries data formatted in 53 byte 

cells (48 bytes of data and a 5 byte header) over fixed paths called virtual 

circuits; ATM provides mechanisms for bandwidth allocation and quality of 

service; specified in I.363 (see ATM Adaption Layer, virtual circuit). 

ATM Adaption Layer (AAL) — used to segment data for transport in ATM cells 

and to reassemble data received in ATM cells; different AALs are appropriate 

for different types of traffic; specified in I.363. 

AAL1 is suitable for constant bit rate, connection-oriented traffic that is 

intolerant of delay, like voice and video (I.363.1). 

AAL2 is suitable for variable bit rate, connection-oriented traffic intolerant of 

delay like voice and video, traffic from multiple users can be multiplexed over 

a single virtual circuit (I.363.2). 

AAL3/4 is suitable for connection-oriented and connectionless data traffic 

tolerant of delay (I.363.3). 

AAL5 is suitable for all types of traffic (I.363.5). 

Glossary–1



Glossary 

Available Bit Rate (ABR) — ATM service category (also called traffic class) 

that supports data rates up to a peak cell rate, a flow control mechanism allows 

the sender to adjust the rate of transmission (see Virtual Circuit). 

Basic Rate Interface (BRI) — a digital interface to the customer premises that 

provides two 64 kbps B-channels for user information and a 16 kbps D-channel 

for call control using Q.931 protocol; also supports X.25 packet - see ISDN. 

Best Effort — traffic receiving “best effort” treatment receives no guarantees for 

packet treatment; network nodes will autonomously decide to delay or drop 

packets when congestion occurs. 

Border Gateway Protocol (BGP) — protocol used between routers in different 

networks to exchange routing information, specified in RFC 1771. 

Bridge — facilitates the exchange of packets between devices and networks; a 

bridge is a less sophisticated device than a router, using simpler mechanisms 

to direct packets. 

Broadband — describes a circuit with a large capacity for carrying packet 

information; i.e. high bandwidth. 

Call Associated Signaling (CAS) — information for call setup and feature 

support is exchanged over the data path used to carry bearer information; 

inband signaling. 

Call Connection Agent (CCA) — NGN network element that provides the 

intelligence for call processing and feature support; directs the other NGN 

elements to establish and tear down connections, monitor and report on 

events, and provide feedback to the user. 

Cell — see ATM 

Cell Delay Variation Tolerance (CDVT) — specifies the acceptable variation 

in cell arrival times for a ATM virtual circuit; part of the ATM quality of service 

parameters. 

Circuit Emulation Service (CES) — describes use of ATM to provide constant 

bit rate transport similar to traditional Public Switched Telephone Network 

trunks, specified in AF-VTOA-0078. 

Class 5 Switch — node in the Public Switched Telephone Network that 

terminates subscriber lines and provides call processing and features; the Class 

5 Switch is connected to other Class 5 Switches and tandem switches by 

interoffice trunks. 

Codec — the scheme used to digitize and compress an analog signal and return a 

received signal to analog; also refers to the hardware module that performs 

compression and decompression, several codecs have been specified by the 

ITU. 

Comfort Noise — a receiving device generates comfort noise for the user during 

periods when no data is received due to silence suppression at the transmitting 

end. 

Glossary–2



Glossary 

Common Channel Signaling (CCS) — signaling for several calls is combined 

on a dedicated transmission path separate from the bearer path used for each 

call; out-of-band signaling. 

Compression — used to reduce the amount of information needed to represent a 

stream of data; compression increases the number of users a circuit can 

support by reducing the amount of bandwidth needed for each active user (see 

Codec). 

Computer Telephony Integration (CTI) — applications that are based on use 

of a computer to control telephone calls and exchange information with the 

telephony network; a simple example is use of received caller id information to 

direct an incoming call to a specific agent. 

Constant Bit Rate (CBR) — ATM service category or traffic class; provides a 

fixed rate of data transmission (see Virtual Circuit). 

Core Network — consists of high capacity broadband circuits and switches or 

routers; provides transport of user information and signaling. 

Customer Gateway (CGW) — NGN element at the customer premises that 

provides an interface for user devices to share a broadband network access 

facility. 

Data Local Exchange Carrier (DLEC) — a service provider that provides data 

transport and services; an example is a DSL provider that provides a DSL 

circuit and Internet Access. 

Data Over Cable Service Interface Specifications (DOCSIS) — a set of 

standards for transferring data via cable TV. DOCSIS is managed by the 

Multimedia Cable Network System, an organization formed by four major cable 

operators. 

Differentiated Services (DiffServ) — a mechanism used in IP networks to 

indicate the quality of service that should be provided to packets of a specific 

traffic class; the traffic class is identified by the value of the diffserv code point 

(DSCP) found in the header of the IP packet; Assured Forwarding (RFC 2597) 

and Expedited Forwarding (RFC 2598) are examples of per-hop-behaviors 

(PHB) that describe a the treatment for a class of traffic. 

Digital Subscriber Line (DSL) — a broadband access arrangement that 

provides high data rate transmission over the same copper facilities used to 

provide analog telephone service; there are several types of DSL circuits, 

including: 

Asymmetrical DSL (ADSL) - provides up to 9 MBPS downstream (networkto-user) 

and up to 640 kbps upstream (user-to-network), can simultaneously 

support analog telephone service. 

G.Lite - a simple version of ADSL that provides up to 1.5 Mbps downstream 

and up to 512 kbps upstream. 

Glossary–3



Glossary 

High data rate DSL (HDSL) - provides T1 (1.544 Mbps) or E1 (2.048 Mbps) 

data rates, used for trunk type applications. 

Symmetrical DSL (SDSL) - similar data rates to HDSL but used for 

subscriber access like ADSL, can simultaneously support analog telephone 

service. 

Very high data rate DSL (VDSL) - provides up to 52 Mbps downstream and 

2.3 Mbps upstream. 

Domain Name Server (DNS) — translates host names used to identify 

computers into Internet addresses. 

Dynamic Host Configuration Protocol (DHCP) — protocol used for dynamic 

assignment of IP addresses to nodes within a network, specified in RFC 2131. 

Echo Cancellation — technique for preventing a transmitted signal from being 

played back to the sender from the receiving end; echo cancellation can disrupt 

the operation of certain types of modems, specified in G.168. 

Encapsulation — enclosing one type of packet or piece of data in another, such 

as encapsulating an IP packet in an ATM cell or a byte of encoded voice in an 

RTP packet. 

Encryption — used to prevent user data from being read by anyone but the 

intended receiver. 

Ethernet — a physical and framing mechanism used in local networks and for 

network access; Ethernet LANs may operate at 10 Mbps (10BaseT) or 100 Mbps 

(100BaseT), specified in IEEE 802.3. 

Expedited Forwarding (EF) — see Differentiated Services 

File Transfer Protocol (FTP) — protocol used to transfer text and binary files 

across IP networks; TFTP is a simplified version of FTP. 

firewall — protects devices in a local network from unauthorized access from 

outside the network. 

Forwarding Equivalency Class (FEC) — see Multi-protocol Label Switching 

Frame — generally, a unit of data; HDLC is used to frame IP packets; on a T1, a 

frame is a combination of 24 time slots (see Frame Relay). 

Frame Relay (FR) — a simple transport mechanism that transmits data 

(possibly already encapsulated in another protocol) in variable length frames; 

originally conceived to replace dedicated private lines, it may be used for 

transport in access arrangements but is not suitable for use in core networks, 

specified in I.233 and ANSI T1.606, T1.617, T1.618. 

Gateway — a device that provides an interface point between two networks. 

H.248 — protocol for connection management and call processing in packet 

networks in support of multimedia services, employs a master-slave call 

model. 

Glossary–4



Glossary 

H.323 — protocol for multimedia communication in packet networks; includes 

peer-to-peer and master-slave call models. 

High-level Data Link Control (HDLC) — protocol used to provide link control 

and framing for IP, specified in ISO/IEC 3309. 

HomePNA (Phoneline Networking Alliance) — a means for networking 

devices using in-home telephone wiring. 

HyperText Transfer Protocol (HTTP) — protocol used to transmit 

information on the Internet. 

Institute of Electrical and Electronics Engineers (IEEE) — professional 

society for engineers that also issues standards for telecommunications and 

computing. 

Integrated Access Device (IAD) — see Customer Gateway 

Integrated Local Management Interface (ILMI) — protocol used for 

network management over an ATM interface, specified in AF-ILMI-0065. 

Integrated Services Digital Network (ISDN) — protocol used for call control 

on digital access interfaces; see Basic Rate Interface (BRI) and Primary Rate 

Interface (PRI). 

International Telecommunication Union (ITU) — international standards 

body sponsored by the United Nations; members are governments and entities 

designated by governments; specifications issued by the ITU for 

telecommunications standards are called “Recommendations”. 

Internet Engineering Task Force (IETF) — technical group that produces 

specifications defining standards for the Internet, called Requests for 

Comment (RFC), most RFCs are applicable for packet networks other than the 

Internet, like local and wide area private networks. 

Internet Packet Exchange (IPX) — protocol used in local area networks that 

use Novell Netware. 

Internet Protocol (IP) — a connectionless, best effort mechanism for 

transporting data in packet networks used in the Internet and most other data 

networks; other protocols, like Transmission Control Protocol and User 

Datagram Protocol, are used in conjunction with IP to carry user data, 

specified in RFC 791 and RFC 2460. 

Interworking — function that allows dissimilar networks to communicate; 

usually provided by a gateway. 

Jitter — variations in the time it takes for packets to travel from source to 

destination causes the packets to arrive out of sequence, degrading the 

reproduced voice signal. 

Jitter Buffer — used to reduce the impact of jitter on the reproduced voice 

signal, a jitter buffer collects arriving packets for a specified period of time so 

they may be resequenced before the voice signal is reproduced. 

Glossary–5



Glossary 

Label Distribution Protocol (LDP) — protocol used to distribute information 

related to the labels used in Multiprotocol Label Switching, specified in RFC 

3036 

Latency — time it takes for a packet, cell, or frame to travel from one point to 

another in a network, includes processing time as well as transport time; delay. 

Line sharing — when DSL service and analog telephone service on the same loop 

are provided by different service providers. 

Loop — the copper wires that connect the customer premises and the central 

office used to provide telephone service. 

Loop Emulation Service (LES) — describes use of ATM to provide variable bit 

rate service used for access to the network from the customer premises, 

specified in AF-VMOA-0145. 

Maximum Burst Size (MBS) — specifies the maximum number of cells that can 

be transmitted between the Sustained Cell Rate and the Peak Cell Rate on an 

ATM virtual circuit with a variable bit rate service category. 

Media Gateway Control Protocol (MGCP) — master-slave protocol used for 

call control and feature support in packet networks. 

Megaco — Internet Engineering Task Force version of H.248. 

Minimum Cell Rate (MCR) — specifies the minimum guaranteed rate at which 

data can be sent on an ATM virtual circuit with an available bit rate service 

category. 

Modem — converts between digital signals and analog signals so that data devices 

can send and receive information over analog telephone lines. 

MultiProtocol Label Switching (MPLS) — a mechanism for providing traffic 

management and quality of service in IP networks; MPLS sets up paths based 

on labels that are similar in concept to ATM virtual circuits, the forwarding 

equivalency class describes the treatment that packets of a certain class, 

indicated by the label, should receive, specified in RFC 3031 and RFC 3032. 

Network Address Translation (NAT) — mapping of IP addresses used in the 

local network to publicly known addresses; mapping can be one-to-one, manyto-one, 

and many-to-many; provides security by hiding addresses used in the 

local network from outside users and address flexibility and conservation by 

allowing a local addressing scheme that does not require use of publicly 

assigned addresses. 

Network Mediation Gateway (NMGW) — NGN element that provides an 

interface between the core network and packet access facilities from customer 

premises. 

Next Generation Network (NGN) — a multi-service network that transports 

voice, data and signaling in packet form. 

Glossary–6



Glossary 

Open Shortest Path First (OSPF) — protocol used by routers to exchange 

information used to determine how packets should be routed, specified in RFC 

2328. 

Packet — generally, a unit of data; data is transported in IP networks in packets; 

ATM cells and Frame Relay frames are protocol specific packets. 

Packet Delay — packets traveling across a network may be delayed before 

reaching the intended destination; during times of congestion, network nodes 

may hold packets until the traffic load has subsided, depending on the quality 

of service specified for the traffic type; see Latency. 

Packet Loss — packets that do not arrive at the intended destination are lost; 

during times of congestion, network nodes may intentionally drop packets to 

reduce the total traffic load, depending on the quality of service specified for 

the traffic type. 

Password Authentication Protocol (PAP) — protocol for user authentication 

using text passwords. 

Peak Cell Rate (PCR) — specifies the maximum rate at which data is expected 

to be sent can be sent on an ATM virtual circuit with an variable bit rate service 

category; data can be sent at the PCR only until the Maximum Burst Size is 

reached. 

Per Hop Behavior (PHB) — see Differentiated Services 

Permanent Virtual Circuits (PVC) — see Virtual Circuits 

Plain Old Telephone Service (POTS) — the basic voice telephony service over 

the 0 to 4 kHz frequency spectrum. POTS is synonymous with the Public 

Switched Telephone Network (PSTN). 

Point-to-Point Protocol (PPP) — protocol that provides link control and 

framing for IP packets. 

Port — physical interface point where one device is connected to another; also 

refers to software identifier of interface used for the exchange of information 

between two applications. 

Primary Rate Interface (PRI) — a digital interface to the customer premises 

that provides twenty-three 64 kbps B-channels for user information and a 64 

kbps D-channel for call control using Q.931 protocol; also supports X.25 packet 

- see ISDN. 

Public Switched Telephone Network (PSTN) — the world-wide network of 

TDM circuits and switches that provides voice call processing, features and 

services. 

Pulse Code Modulation (PCM) — technique for converting analog voice into a 

digital signal; in a NGN, the digital signal is then encapsulated in packets for 

transport. 

Glossary–7



Glossary 

Quality of Service (QoS) — the treatment that a type of traffic in a network 

should receive; the degree of delay, loss, and jitter that packets associated with 

a particular data stream encounter will impact on the quality the application 

provides for the user; for example, reproduced voice will be unintelligible 

unless a given quality of service is provided for packets carrying the voice 

information as they travel across the network from sender to receiver. 

Real-time — real-time applications, such as voice and video, require there be 

little-to-no delay between sending information from the source and delivery to 

the destination. 

Real-time Control Protocol (RTCP) — protocol that provides a feedback 

mechanism for RTP. 

Real Time Protocol (RTP) — protocol for transporting real-time data in IP 

packets, specified in RFC 1889. 

Registered Jack (RJ) — plugs and receptacles (jacks) registered with the FCC; 

RJ-11 is the common, 6-wire (of which 4 are used) connector used for analog 

telephones interfaces, RJ-45 is the 8 wire connector commonly used for data 

devices. 

Request for Comment (RFC) — documents and specifications issued by the 

Internet Engineering Task Force are identified as RFCs. 

Resource Reservation Protocol (RSVP) — protocol used in IP networks to 

request resources and quality of service treatment for an end-to-end flow of 

data, specified in RFC 2205. 

Router — intelligent device that controls the transport of information between 

devices in a data network; routers use configuration information and 

information exchanged with other routers to select the best route to a 

destination and to determine the treatment to provide to individual packets in 

times of congestion. 

Routing Information Protocol (RIP) — protocol used by routers to exchange 

information used to determine how packets should be routed, specified in RFC 

2453. 

Session Initiation Protocol (SIP) — protocol similar to other protocols used 

in the Internet that can be used to set up connection in data networks, 

including connections for voice calls, can operation as a peer-to-peer protocol 

and as a master-slave protocol, specified in RFC 2543. 

Signaling Gateway (SGW) — NGN element that provides an interface for 

signaling between the NGN and other networks. 

Signaling System 7 (SS7) — architecture and protocol for common channel 

signaling used in the Public Switched Telephone Network; the SS7 network 

consists of Signaling Transfer Points, Service Control Points and Service 

Switching Points. 

Glossary–8



Glossary 

Signaling Transfer Point (STP) — A signaling point with the function of 

transferring signaling messages from one signaling link to another and 

considered exclusively from the viewpoint of the transfer. 

Silence Suppression — technique for reducing the amount of data needed to 

represent a voice signaling by limiting transmission during periods of silence. 

Simple Gateway Control Protocol (SGCP) — protocol for call control and 

feature support in packet networks that employs a master-slave model; SGCP 

has been lost support as compared to MGCP. 

Simple Network Management Protocol (SNMP) — protocol used to 

communicate network management information. 

Soft Switch — term commonly used by industry for a Call Connection Agent. 

Spanning Tree — algorithm used by a bridge to select a route for packets, 

specified in IEEE 802.1d (see Bridge). 

Sustainable Cell Rate (SCR) — specifies the average rate at which data is 

expected to be sent can be sent on an ATM virtual circuit with an variable bit 

rate service category, see peak cell rate, maximum burst size. 

Switched Virtual Circuits (SVC) — see Virtual Circuits 

Synchronous Optical Network (SONET) — United States (ANSI) standard for 

synchronous data transmission on optical media. The international equivalent 

of SONET is know as the Synchronous Digital Hierarchy (SDH). Together, 

digital networks can interconnect internationally and existing conventional 

transmission systems can take advantage of optical media through tributary 

attachments. 

Telnet — protocol that allows a user gain access to a device remotely using 

another device. 

Time Division Multiplexing (TDM) — technique used in the Public Switched 

Telephone network for transporting multiple conversations over the same 

facility, data for each conversation is carried in a time slot dedicated for the 

length of the conversation, T1 and E1 circuits make use of TDM. 

Transmission Control Protocol (TCP) — protocol used to provide reliable 

end-to-end transport of IP packets, specified in RFC 793. 

Transport — in this document, refers to the mechanism used to carry data 

between nodes in a network. 

Trivial File Transfer Protocol (TFTP) — see File Transfer Protocol 

Trunk Gateway (TGW) — NGN element that provides an interface for user 

information to be exchanged between the NGN and other networks. 

Unbundled Loop — loop unbundling allows on service provider to provide 

service, such as DSL or analog phone service, over a loop supplied by a 

different provider. 

Glossary–9



Glossary 

Unified Messaging — services that allows access to different types of messages 

(i.e. voice, fax, E-mail etc.) using various interfaces (i.e. PC, phone etc.). 

Unspecified Bit Rate (UBR) — ATM service category that offers no quality of 

service guarantees; see best effort. 

User Datagram Protocol (UDP) — protocol used to address IP packets to a 

specific application, identified by a port number, within a destination node 

identified by its IP address, specified in RFC 768. 

User-to-Network Interface (UNI) — refers to the protocols used for signaling 

between the customer premises equipment and the network in ATM and Frame 

Relay. 

Variable Bit Rate (VBR) — ATM service category intended for applications that 

send data at rates that vary with time; real-time (rt) and non real-time (nrt) 

versions of VBR can be used depending on whether the application is sensitive 

to delay VBR-rt. 

Variable Bit Rate-nrt (VBR-nrt) — AVBR-nrt is designed for applications that 

are bursty in nature, but are not sensitive to delay. 

Variable Bit Rate-nrt (VBR-rt) — AVBR-rt is designed for applications with 

variable transmission rates that operate in real-time, like voice and video. 

Virtual Circuits (VC) — specified end-to-end path through a data network, VCs 

may be predefined (permanent virtual circuit) or set up and torn down as 

needed (switched virtual circuit); in ATM, service categories are associated 

with virtual circuits to indicate how bandwidth should be allocated and the 

quality of service that should be provided, a virtual path identifier/virtual 

circuit identifier (VPI/VCI) is used to identify a VC; virtual circuits are used in 

Frame Relay as well. 

Virtual Private Network (VPN) — use of shared public or wide area network 

facilities to connect locations in what appears to the users to be a dedicated 

private network. 

V5 — protocol for signaling analog and ISDN call control information, specified in 

ETSI EN 300 324-1. 

Glossary–10



Glossary 

Acronyms 

AAL ATM Adaptive Layer 

ABR Available Bit Rate 

ACL Access Control List 

ADPCM Adaptive Differential Pulse Code Modulation 

ADSL Asymmetric Digital Subscriber Line 

AGW Access Gateway 

ANLC Access Network Logical Connection 

API Application Programming Interface 

ARP Address Resolution Protocol 

ASP Application Service Provider 

ATM Asynchronous Transfer Mode 

BA Billing Agent 

BBG Basic Business Group 

BERT Bit Error Rate Test 

BGP Border Gateway Protocol 

BGW Bearer Gateway 

BICC Bearer Independent Call Control 

BNC Backbone Connection Network 

BRI Basic Rate Interface 

CAS Call Associated Signaling 

CBR Constant Bit Rate 

CCA Call Connection Agent 

CCS Common Channel Signaling 

CGW Customer Gateway 

CHAP Channel Handshake Authentication Protocol 

CN Core Network 

CNLC Core Network Logical Connection 

CPE Customer Premise Equipment 

DHCP Dynamic Host Configuration Protocol 

DLEC Data Local Exchange Carrier 

DNS Domain Name Server 

DSL Digital Subscriber Line 

DSLAM Digital Subscriber Line Access Multiplexer 

Glossary–11



Glossary 

DSO Digital Signal Level Zero (64 kbps) 

EF Expedited Forwarding 

EML Element Management Layer 

EMS Element Management System 

FE Functional Element 

GR Generic Requirement 

GW Gateway 

HFC Hybrid Fiber-Coax 

IAD Integrated Access Device 

IDLC Integrated Digital Loop Carrier 

IN Intelligent Network 

IOS Internetwork Operations Systems 

IP Internet Protocol 

IPX Internet Packet Exchange 

ISDN Integrated Services Digital Network 

ISP Internet Service Provider 

ISUP ISDN User Part 

kbps kilobits per second 

KTS Key Telephone System 

LED Light Emitting Diode 

MGCP Media Gateway Control Protocol 

NE Network Element 

NGN Next Generation Network 

NMGW Network Mediation Gateway 

NML Network Management Layer 

NMS Network Management System 

OSS Operator Services System 

PBX Private Branch Exchange 

PCM Pulse Code Modulation 

PDA Personal Digital Assistant 

POTS Plain Old Telephone Service 

PPP Point to Point Protocol 

PRI Primary Rate Interface 

PSTN Public Switched Telephone Network 

PVC Permanent Virtual Circuit 

QoS Quality of Service 

Glossary–12



Glossary 

RAS Reliability, Availability, and Survivability 

RBOC Regional Bell Operating Company 

RDT Remote Digital Terminal 

RIP Routing Information Protocol 

RTCP Real-time Control Protocol 

RTP Real-time Transport Protocol 

SA Services Agent 

SCCP Signaling Connection Control Part 

SCP Service Control Point 

SCTP Signaling Control Transmission Protocol 

SDE Service Definition Environment 

SGCP Simple Gateway Control Protocol 

SGW Signaling Gateway 

SIP Session Initiation Protocol 

SNMP Simple Network Management Protocol 

SS7 Signaling System 7 

SSP Signaling Switching Point 

STP Signaling Transfer Point 

SVC Switched Virtual Circuit 

TCAP Transaction Capabilities Part 

TCP Transmission Control Protocol 

TDM Time Division Multiplexing 

TFTP Trivial File Transfer Protocol 

TGW Trunk Gateway 

TMN Telecommunications Management Network 

ToS Type of Service 

UBR Unspecified Bit Rate 

UDP User Datagram Protocol 

UNI User Network Interface 

USB Universal Serial Bus 

VC Virtual Circuit 

VCI Virtual Channel Identifier 

VoDSL Voice over Digital Subscriber Line 

VoFR Voice over Frame Relay 

VoIP Voice over IP 

VoP Voice over Packet 

Glossary–13



Glossary 

VP Virtual Path 

VPI Virtual Path Identifier 

VPN Virtual Private Network 

Glossary–14

TELCORDIA ENTERPRISE LICENSE AGREEMENT AND LIMITED WARRANTY 

For Technical Documents: Generic Requirements (GRs), Special Reports (SRs), Technical References (TRs), Technical 

Advisories (TAs), Family of Requirements (FRs), Family of Documents (FDs), Framework Advisories (FAs), Science 

Technologies (STs), Message Driven Program (MDPs), Information Publications (IPs), Audio Visuals (AVs) and 

Telcordia Practices (BRs) 

IMPORTANT! READ CAREFULLY 

USE OF THIS PRODUCT INDICATES THAT YOU (LICENSEE OR USER) HAVE READ AND ACCEPT THE TERMS OF THIS 

AGREEMENT. IF YOU DO NOT AGREE WITH THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED 

PRODUCT WITH ALL SEALS INTACT TO THE ADDRESS LISTED BELOW FOR A TELCORDIA CREDIT. 

1. LICENSE GRANT 

Telcordia grants to customer (“Licensee”) a non-exclusive, nontransferable, 

limited license to use this Licensed Product by 

employees of Licensee (“Users”) for internal business purposes only. 

All intellectual property rights, title and interest in all Licensed 

Products furnished to Licensee remain in Telcordia. This License 

does not preclude the execution of additional license agreements with 

Licensee for the Licensed Product(s). 

Telcordia has exclusive rights to all Licensed Products which are 

protected by United States and international copyright laws. 

2. LICENSEE’S USE: 

a) Licensee may place the Licensed Products on a Local Area 

Network, Wide Area Network, server, internal web site, or 

other electronic computing platform shared or accessible to 

employees or affiliates of Licensee. Licensee may make 

paper and electronic copies of Licensed Products as 

determined by Licensee to be necessary for Licensee's 

internal purposes; provided all copies, in whole or in part, of 

the Licensed Products shall bear the same Telcordia copyright 

and disclaimer notices legend as appear on the Licensed 

Products originally furnished to Licensee by Telcordia. 

b) Subject to the preceding paragraph, Licensee may reproduce 

and distribute Licensed Products to “Affiliates” defined as 

(i) the parent entity (corporation or partnership) which directly 

or indirectly owns the majority of the outstanding shares or 

interests of Licensee, (ii) a sibling entity (corporation or 

partnership) the majority of whose outstanding shares or 

interests are owned by its parent entity, or (iii) a subsidiary 

entity (corporation or partnership) the majority of whose 

outstanding shares or interests are owned by Licensee, 

provided, however, that such entity shall continue to remain an 

Affiliate hereunder only as long as the applicable ownership 

interest as described above exists. 

Licensee may sublicense the rights granted in this section to 

an Affiliate, provided Licensee shall remain responsible for any 

breach by such Affiliate. Licensee shall ensure that such 

Affiliate as assignee agrees to be bound by the rights, 

obligations and limitations set forth herein, and such Affiliate 

shall be responsible for any breach by such Affiliate and 

Licensee shall ensure that Telcordia shall have the right of 

direct enforcement of such obligations against such Affiliate. If 

a direct enforcement claim is denied, for any reason, it is 

agreed that Licensor may assert such claim against Licensee. 

c) Licensee may copy portions of Licensed Products to create 

specifications and related documentation (the “Licensee 

Documentation”). 

d) Licensee may, in marketing a product or related services 

(collectively, “Licensee Product”), (i) make reference to the 

Licensed Product utilized in the development of Licensee 

Product; provided that Licensee shall make no statement, 

representation or warranty on behalf of Telcordia including but 

not limited to a certification by Telcordia of a product’s or related 

service’s compliance with the Licensed Product, unless 

otherwise agreed to by the parties in writing; or (ii) distribute the 

Licensee Documentation to a third party prior to sale of the 

Licensee Product. 

e) Licensee may refer to and/or incorporate portions of such 

Licensed Products in the Licensee Documentation for the 

Licensee Product and copy the Licensee Documentation for 

distribution in conjunction with the sale of the Licensee 

Product to any third party so long as the original Telcordia and 

copyright legends, as applicable, are acknowledged on the 

specifications and/or documentation. 

f) Licensee must treat the Licensed Product(s) like any other 

copyrighted material. 

g) Except as otherwise stated, it is understood that the foregoing 

license does not include the right to make copies of the Licensed 

Products for sale to third parties or to create derivative works for 

sale. 

USER MAY NOT: 

a) Copy the Licensed Product, except as provided above; 

b) Make copies of the Licensed Product or portions thereof as are 

permitted above for internal purposes that contain provisions that 

conflict or differ in content from comparable provisions of the 

Licensed Product, unless such differences are identified 

specifically, and it is made clear in such copies that the results 

are not part of the Licensed Product; 

c) Transfer the Licensed Product to another party, except as 

provided above; 

d) Licensee may not make the Licensed Product available, in whole 

or in part for the purposes of external distribution to third parties 

other than Affiliates. 

e) Grant sublicenses, leases, or other rights to the Licensed 

Product or rent the Licensed Products to others, except as 

provided above; or 

f) Make telecommunications data transmissions of the Licensed 

Product to the public or any third party. 

g) Data, in whole or in part, may not be extracted from the Licensed 

Product(s) for use in any derivative Licensee product or used to 

verify and subsequently modify data in any Licensee product 

which is sold, licensed or otherwise provided to third parties 

unless Licensee has executed a separately negotiated Special 

License Agreement with Telcordia, except as provided above. 

3. AUDITS 

Upon reasonable written notice to Licensee, Telcordia shall have the 

right to review Licensee’s compliance with the terms and conditions of 

this License Agreement (“Agreement”). If such review reveals a 

violation of the requirements set forth herein, in addition to any other 

remedies it may have, Telcordia may terminate this Agreement in 

accordance with the Termination section of this Agreement. 

4. FEES AND PAYMENTS 

All fees and charges due hereunder shall be paid in full within thirty 

(30) days of the date of the invoice. Overdue payments are subject to 

a late payment charge, calculated and compounded monthly, and 

calculated at an annual rate of either (1) one percent (1%) over the 

prime rate available in New York City, as published in The Wall Street 

Journal on the first Monday (or the next bank business day) following 

the payment due date; or (2) 18 percent (18%), whichever shall be

higher. If the amount of the late payment charge exceeds the 

maximum permitted by law, the charge will be reduced to that 

maximum amount. 

Licensee shall pay or reimburse Telcordia for all sales or use taxes, 

duties, or levies imposed by any authority, government or government 

agency (other than those levied on the net income of Telcordia) in 

connection with this Agreement. If Telcordia is required to collect a 

tax to be paid by Licensee, Licensee shall pay this tax on demand. If 

Licensee fails to pay these taxes, duties or levies, Licensee shall pay 

all reasonable expenses incurred by Telcordia, including reasonable 

attorney's fees, to collect such taxes, duties or levies. 

Telcordia shall provide Licensee with one (1) Copy of the Licensed 

Product. Any additional copies in cd or paper media will be provided 

to Licensee at a cost of $75.00 per copy. Please contact our 

Customer Call Center noted below. 

5. LIMITED WARRANTY 

Telcordia warrants that the media on which the Licensed Product is 

provided is free from defects in materials and workmanship for 90 

days. Licensee’s sole remedy for breach of this warranty is 

Telcordia’s Product Replacement Plan described below. This 

warranty applies only to the original Licensee. 

6. DISCLAIMER OF WARRANTIES 

EXCEPT AS SET FORTH ABOVE, THE LICENSED PRODUCT IS 

PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER 

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE 

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 

FOR A PARTICULAR PURPOSE, EVEN IF TELCORDIA HAS BEEN 

MADE AWARE OF SUCH PURPOSE, OR ANY WARRANTY 

AGAINST INFRINGEMENT OF PATENTS OR OTHER 

INTELLECTUAL PROPERTY RIGHTS. LICENSEE ASSUMES 

RESPONSIBILITY FOR THE SELECTION OF THE LICENSED 

PRODUCT TO ACHIEVE ITS INTENDED RESULTS, AND FOR THE 

USE AND RESULTS OBTAINED FROM THE LICENSED PRODUCT. 

7. LIMITATION OF LIABILITY 

THE ENTIRE LIABILITY OF TELCORDIA, AND LICENSEE’S 

EXCLUSIVE REMEDY, IS THE REPLACEMENT OF ANY LICENSED 

PRODUCT WHICH DOES NOT MEET THE TELCORDIA LIMITED 

WARRANTY AND IS RETURNED TO TELCORDIA WITHIN 90 

DAYS. 

IN NO EVENT WILL TELCORDIA BE LIABLE TO LICENSEE FOR 

ANY DAMAGES, INCLUDING DIRECT DAMAGES, LOST PROFITS, 

OR OTHER INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY OR 

CONSEQUENTIAL DAMAGES ARISING OUT OF THIS 

AGREEMENT, EVEN IF TELCORDIA HAS BEEN ADVISED OF THE 

POSSIBILITY OF SUCH DAMAGES. 

THE WARRANTY GIVES LICENSEE SPECIFIC LEGAL RIGHTS, 

AND LICENSEE MAY ALSO HAVE OTHER RIGHTS WHICH VARY 

FROM STATE TO STATE. SOME STATES DO NOT ALLOW THE 

EXCLUSION OR LIMITATION OF INCIDENTAL OR 

CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION MAY 

NOT APPLY TO LICENSEE. 

8. THIRD PARTY PRODUCTS AND INFORMATION WARRANTY 

Telcordia does not warrant Third Party products or information which 

Telcordia may use to prepare the Licensed Product. Third Party 

products or information may be warranted by Third Parties as 

expressly provided in the documentation accompanying the Third 

Party product or information, if any. Licensee’s exclusive remedy 

under any Third Party warranty is as provided in the Third Party 

documentation accompanying the Third Party product or information, 

if any. 

9. LICENSED PRODUCT REPLACEMENT PLAN 

During the first 30 days after Licensee licenses the Telcordia Licensed 

Product, Telcordia will replace at no charge any Licensed Product 

which is returned to Telcordia because its media is defective in 

materials or workmanship. Returns for replacement of a defective 

Licensed Product should be sent postpaid to Telcordia using the 

Return Policy procedures stated below. 

10. RETURN POLICY 

Licensed Product(s) may be returned within 30 days of receipt for 

Telcordia credit only. Returned Licensed Products must be in their 

original packaging with all seals intact. Returns not found to be 

defective in materials or workmanship will be subject to a 10% 

restocking fee. Licensed Products that have been delivered 

electronically (downloaded from the Superstore) are not eligible for 

credits, refunds or returns, even if duplicative with Licensed Products 

that are the subject of prior or contemporaneous orders. Licensee 

assumes all responsibility for managing its inventory of Licensed 

Product(s). 

11. TERMINATION 

If Licensee or its User breaches one or more of its obligations under 

this Agreement, Telcordia may elect at any time, in addition to any 

other remedy, to terminate the license and rights granted. Prior to the 

termination, Telcordia must give Licensee two (2) months written 

notice specifying the breach. Telcordia may terminate the license and 

rights granted if Licensee does not remedy all breaches specified in 

the written notice within the two (2) month notice period. Upon 

termination of the license and rights granted, Licensee shall destroy or 

return all Licensed Product(s) and Documentation, including all 

copies, and certify in writing to Telcordia the destruction or return. 

12. PUBLICITY 

Notwithstanding anything herein to the contrary, each party is 

prohibited from using in advertising, publicity, promotion, 

marketing, or other similar activity, any name, trade name, 

trademark, or other designation including any abbreviation, contraction 

or simulation of the other without the prior, express, written 

permission of the other. 

13. GENERAL 

Reexport. Licensee acknowledges that any commodities and/or 

technical data provided under this Agreement is subject to the Export 

Administration Regulations (“the EAR”) administered by the U.S. 

Commerce Department and that any export or re-export thereof must 

be in compliance with the EAR. Licensee agrees that it shall not 

export or reexport, directly or indirectly, either during the term of this 

Agreement or after its expiration, any commodities and/or technical 

data (or direct products thereof) provided under this Agreement in any 

form to destinations in Country Groups D:1 or E:2, as specified in 

Supplement No. 1 to Part 740 of the EAR, and as modified from time 

to time by the U.S. Department of Commerce, or to recipients or 

destinations that are otherwise controlled or embargoed under U.S. 

law. 

Foreign Tax Payment. For a Licensee which is not a United States 

corporation, Telcordia will not accept remittance of less than the full 

amount billed to Licensee as full payment unless: 

a) Licensee withholds that amount to satisfy tax withholding 

requirements imposed by the country (other than the United 

States) in which Licensee resides or in which Licensee has 

accepted delivery of the Licensed Product; and 

b) Licensee furnishes a receipt issued by the withholding tax 

jurisdiction and certifying deposit of the withheld amount into its 

treasury or other tax depository to Telcordia’s sole credit, or a 

certification on Licensee’s stationery that Licensee has deposited 

the withheld amount into its tax jurisdiction’s treasury or other tax 

depository to Telcordia’s sole credit. 

Further, to ensure the orderly processing of Telcordia tax returns, 

Licensee shall provide to Telcordia a summary of all amounts withheld 

during the year no later than ten business days after December 31 of 

each year. 

Governing Law. This Agreement is a contract between Telcordia and 

the Licensee of the Licensed Product. This contract is to be 

interpreted in the federal and state courts of New Jersey, in 

accordance with the laws of the State of New Jersey without regard to 

its conflict of laws principles, and the parties consent to the jurisdiction 

of such courts for this purpose. 

Entire Agreement. Licensee further agree that this is the complete 

and exclusive statement of the Agreement between Licensee and 

Telcordia and supersedes any proposal or prior Agreement, oral or 

written, or any other communication between us relating to the subject 

matter of this Agreement.

All questions about this Agreement should be directed to: 

Telcordia Technologies, Inc. 

Customer Service Center 

One Telcordia Drive, RRC 1B180 

Piscataway, NJ 08854 

Phone: 1.866.672.6997 (USA) 

+1.732.699.6700 (Worldwide) 

END OF TERMS AND CONDITIONS 

Agreed: 

Company:___________________________________ 

_ 

Name:_______________________________________ 

Signature:___________________________________ 

Date:________________________________________ 

Revised 4/07

(NGN) Documents - Telcordia Information SuperStore - Telcordia ...

Create successful ePaper yourself

Delete template?

Save as template?