Telcordia
`Notes on the Networks
`
`
`
`Telcordia Technologies Special Report
`SR-2275
`Issue 4
`October 2000
`
`An SAIC Company
`
`AT&T Exhibit 1033
`AT&T v. VoIP, IPR 2017-01384, Page 1
`
`

`

`Telcordia Notes on the Networks
`Copyright Page
`
`SR-2275
`Issue 4
`October 2000
`
`Telcordia Notes on the Networks
`
`SR-2275 replaces SR-2275, Bellcore Notes on the Networks, Issue 3, December 1997.
`
`Related documents:
`
`SR-NOTES-SERIES-01, Telcordia Notes on the Synchronous Optical Network
`(SONET)
`SR-NOTES-SERIES-02, Telcordia Notes on Dense Wavelength-Division
`Multiplexing (DWDM) and Optical Networking
`SR-NOTES-SERIES-03, Telcordia Notes on Number Portability and
`Number Pooling
`SR-NOTES-SERIES-04, Telcordia Notes on the Evolution of Enhanced
`Emergency Services.
`
`To obtain copies of this document, contact your company’s document coordinator
`or your Telcordia account manager, or call +1 800.521.2673 (from the USA and
`Canada) or +1 732.699.5800 (all others), or visit our Web site at www.telcordia.com.
`Telcordia employees should call +1 732.699.5802.
`
`Copyright © 2000 Telcordia Technologies, Inc. All rights reserved. This document
`may not be reproduced without the express written permission of Telcordia
`Technologies, and any reproduction without written authorization is an
`infringement of copyright.
`
`Trademark Acknowledgments
`Telcordia is a trademark of Telcordia Technologies, Inc.
`CLCI, CLEI, CLFI, CLLI, ISCP, NMA, and SEAS are trademarks of Telcordia Technologies, Inc.
`COMMON LANGUAGE, SPACE, TELEGATE, AIRBOSS, and TIRKS are registered trademarks of
`Telcordia Technologies, Inc.
`CLASS is a service mark of Telcordia Technologies, Inc.
`Appletalk is a registered trademark of Apple Computer, Inc.
`DECNet is a trademark of Digital Equipment Corporation.
`1/1AESS, 4ESS, 5ESS, Dataphone, and SLC are registered trademarks of Lucent Technologies, Inc.
`DMS-10, DMS-100F, DATAPATH, and TOPS are trademarks of Nortel.
`DMS-100 is a registered trademark of Nortel.
`NEAX-61E is a trademark of NEC America, Inc.
`EWSD is a registered trademark of Siemens AG.
`
`Any other companies and products not specifically mentioned herein are trademarks or service marks
`of their respective trademark and service mark owners.
`
`ii
`
`AT&T Exhibit 1033
`AT&T v. VoIP, IPR 2017-01384, Page 2
`
`

`

`Telcordia Notes on the Networks
`Network Architectures and Services
`
`SR-2275
`Issue 4
`October 2000
`
`prevents repetitive call attempts to reach distant busy lines, reducing inefficient
`use of circuits.
`(cid:127) TCAP supports cellular switching functions such as automated user
`registration.
`(cid:127) There is an ability to protect the transfer of TCAP information against a variety
`of security threats, as needed.
`
`14.2.2.5 Operations, Maintenance, and Administration Part (OMAP)
`
`OMAP is the layer of the SS7 protocol that is specified for managing the CCS
`network by using SS7 to transport operation and maintenance information between
`SPs. Architecturally, OMAP lies above TCAP in the SS7 protocol stack and uses the
`remote operations service of TCAP to communicate between OMAP applications.
`OMAP functions include network monitoring, routing updates, signaling network
`management, automatic call gapping, and consolidation of Operations,
`Administration, and Maintenance (OA&M) information. OMAP currently performs
`these functions through the following procedures:
`(cid:127) MTP Routing Verification Test (MRVT) — verifies MTP routing data for a
`Destination Point Code (DPC).
`(cid:127) SCCP Routing Verification Test (SRVT) — verifies SCCP routing data for a
`global title address.
`(cid:127) Link Equipment Failure (LEF) — notifies an SP of a signaling terminal or
`interface equipment failure at the far end of a signaling link.
`(cid:127) Link Fault Sectionalization (LFS) — identifies the failed component on a
`signaling link.
`(cid:127) Circuit Validation Test (CVT) — ensures that two exchanges have sufficient and
`consistent translation data for placing a call on a specific circuit of an
`interexchange circuit group.
`
`More details on the SS7 protocol can be found in Section 6 of this document and in
`GR-246-CORE.
`
`14.2.3 CCS Call Setup
`
`This section describes an example of basic intraLATA Plain Old Telephone Service
`(POTS) call setup using CCS and gives additional information on interLATA and
`ISDN calls.
`
`The ISDNUP portion of the SS7 protocol is used to support call setup. The Initial
`Address Message (IAM) is a mandatory message sent in the forward direction to
`initiate seizure of an outgoing circuit and to transmit address and other information
`relating to the routing and handling of a call. The Address Complete Message (ACM)
`is a message sent in the backward direction indicating that all the address signals
`
`14–10
`
`AT&T Exhibit 1033
`AT&T v. VoIP, IPR 2017-01384, Page 3
`
`

`

`SR-2275
`Issue 4
`October 2000
`
`Telcordia Notes on the Networks
`Network Architectures and Services
`
`required for routing the call to the called party have been received. The Answer
`Message (ANM) is a message sent in the backward direction indicating that the call
`has been answered. The Release Message (REL) is a message sent in either
`direction indicating that the circuit identified in the message is being released due
`to the reason (cause) supplied and is ready to be put in the idle state on receipt of
`the Release Complete Message (RLC). The RLC is a message sent in either direction
`in response to the receipt of an REL.
`
`The following describes how these messages are used for setup of an intraLATA
`interoffice call. This call scenario is for an intraLATA call switched through an
`Access Tandem (AT) where a Continuity Check Message (COT) is required. Refer
`to Figure 14-4 for a diagram of the scenario.
`
`When the customer dials an intraLATA interoffice call, the originating office sends
`an IAM over the SS7 signaling link to the AT via the STP pair. The AT then sends an
`IAM to the terminating office indicating the circuit to be used for the call between
`the AT and the terminating office. When the terminating office receives the IAM and
`the COT, it sends an ACM to the AT and applies power ringing to the called party’s
`line. When the AT receives the ACM, it sends an ACM to the originating end office.
`When the called party goes off-hook, an ANM is sent from the terminating end office
`to the AT. When the AT receives the ANM, it sends an ANM to the originating end
`office. After the calling and called party finish their conversation, one party will go
`on-hook. If the calling party goes on-hook, the originating end office sends an REL
`to the AT. When the access tandem receives the REL, it sends an RLC to the
`originating office, and sends an REL to the terminating office. When the terminating
`office receives the REL, it sends an RLC to the AT.
`
`CCS-based POTS call setup to ICs uses the same switch-to-switch message flow as
`described above for an intraLATA call. For calls routed to ICs, however, additional
`optional parameters may be included in the IAM depending on which IC has been
`selected. Examples of these additional optional parameters include Charge Number
`(containing Automatic Number Identification [ANI]), Carrier Identification
`Parameter (containing the 3- or 4-digit Carrier Identification Code [CIC] for the
`call), and Calling Party Number (CPN).
`
`14–11
`
`AT&T Exhibit 1033
`AT&T v. VoIP, IPR 2017-01384, Page 4
`
`

`

`Telcordia Notes on the Networks
`Network Architectures and Services
`
`SR-2275
`Issue 4
`October 2000
`
`Legend:
`
`ACM
`
`ANM
`
`AT
`
`COT
`
`EO
`
`IAM
`
`REL
`
`RLC
`
`SP
`
`STP
`
`=
`
`=
`
`=
`
`=
`
`=
`
`=
`
`=
`
`=
`
`=
`
`=
`
`Address Complete Message
`
`Answer Message
`
`Access Tandem
`
`Continuity Check Message
`
`End Office
`
`Initial Address Message
`
`Release Message
`
`Release Complete Message
`
`Signaling Point
`
`Signaling Transfer Point
`
`Figure 14-4. CCS IntraLATA Call Setup
`
`14–12
`
`AT&T Exhibit 1033
`AT&T v. VoIP, IPR 2017-01384, Page 5
`
`

`

`SR-2275
`Issue 4
`October 2000
`
`Telcordia Notes on the Networks
`Network Architectures and Services
`
`From a message flow standpoint, ISDN call setup is basically the same as POTS call
`setup. The key differences are in the bearer capabilities that can be requested (such
`as 64 clear channel) and additional information that can be sent as part of call setup
`(such as high-layer and low-layer compatibility).
`
`More information on CCS call setup can be found in GR-317-CORE, Switching
`System Generic Requirements for Call Control Using the Integrated Services
`Digital Network User Part (ISDNUP); GR-394-CORE, Switching System Generic
`Requirements for Interexchange Carrier Interconnection Using the Integrated
`Services Digital Network User Part (ISDNUP); TR-NWT-000444, Switching
`System Generic Requirements Supporting ISDN Access Using the ISDN User Part;
`and GR-905-CORE, Common Channel Signaling (CCS) Network Interface
`Specification (CCSNIS) Supporting Network Interconnection, Message Transfer
`Part (MTP), and Integrated Services Digital Network User Part (ISDNUP).
`Sections 14.3 through 14.9 describe CCS-based services such as CLASS features,
`ISDN, ABS, 800 Data Base Service, AIN, and ISCP, and give examples of call
`processing for those services.
`
`14.3 CLASS Features
`
`CLASS features provide capabilities beyond existing call-management services,
`such as Custom Calling services, and are generally based on the transport of the
`Calling Party Number (CPN). Most of the CLASS features do not require the use of
`specialized Customer Premises Equipment (CPE). The CLASS Calling Identity
`Delivery (CID) services that do require some form of specialized CPE are Calling
`Number Delivery (CND), Calling Name Delivery (CNAM), Calling Identity Delivery
`on Call Waiting (CIDCW), Call Waiting Deluxe (CWD), and Bulk Calling Line
`Identification (BCLID). The interface between the switch and the customer’s CPE
`display device is described in GR-30-CORE, Voiceband Data Transmission
`Interface Generic Requirements.
`
`CLASS features have been tariffed for use by residence and small-business
`customers since 1987. The availability of the features varies among LECs, individual
`regulatory jurisdictions, and exchange serving areas. Some of the features, such as
`Automatic Callback (AC), require the customer to dial a vertical service code (for
`AC, the code is *66). Other CLASS features, such as the CID features identified
`above, do not require any special dialing by the customer. Vertical service codes are
`administered by the North American Numbering Plan (NANP). Increasingly, LECs
`are offering selected CLASS features and Custom Calling services on a pay-per-use
`as well as a subscription basis.
`
`CLASS features can be used by customers with dial pulse (rotary) and Dual-Tone
`Multifrequency (DTMF) telephone sets. Rotary customers typically dial “11” instead
`of the “*,” which is not available on rotary dials. With the convenience and screening
`capabilities the CLASS features provide, customers are afforded greater control
`over their calls. The provision of these services depends on the installation of the
`CLASS feature hardware and software in the end offices and CCS in the end offices
`
`14–13
`
`AT&T Exhibit 1033
`AT&T v. VoIP, IPR 2017-01384, Page 6
`
`