RTPFR:Operator Services Generic Requirements for the Use of Signaling System 7 (SS7) Release to Pivot (RTP) Phase II Network Capability
Document Number GR-3016
Issue Number 02
Issue Date Aug 2001
Components of this product are:
ABSTRACT: Issue 2 of GR-3016, RTPFR: Operator Services Generic Requirements for the Use of Signaling System 7 (SS7) Release to Pivot (RTP)
Phase II Network Capability, replaces Issue 1.
This document contains the Telcordia view of proposed generic requirements for the operator services procedures for using the
Signaling System 7 (SS7) RTP network capability. The operator services-specific procedures described in this document are for Local
Exchange Carrier (LEC) Stored Program Control Switching Systems (SPCS's) and Operator Services System (OSS) Core Systems. For
simplicity, throughout the document, an SPCS is referred to as a switch.
The OSS Core System is a terminating switch with operator services capabilities. An OSS comprises the Core System as well as
databases (e.g., Line Information Database [LIDB]) and Subsystems (e.g., Announcement Subsystem). In this document, the OSS Core System
is referred to as the OSS. The operator services capabilities that use RTP are Local Directory Assistance Call Completion (DACC),
National DACC, Calling Card, Third Number Billing, Operator Assisted Call Completion, 0-/Transfer, and 1-800/Alternate Access.
This document defines the operator services-specific capabilities for using RTP Phase II. The RTP Phase II network capability
permits the RTP II operator services at an OSS to optionally release the call back to a switch earlier in the call path for call
completion, rather than forward routing the call from the OSS.
In addition to the operator services-specific extensions to SS7 ISUP for use of the RTP network capability with TDM trunks, this
document applies the same operator services-specific extensions to new signaling (i.e., Bearer Independent Call Control [BICC]
signaling) used for establishment and release of operator services calls over an Asynchronous Transfer Mode (ATM) or Internet Protocol
(IP) backbone network. BICC is closely based on SS7 ISUP and is capable of carrying the SS7 ISUP service-specific parameters, such as
RTP-related operator services-specific parameters.
This document supports BICC signaling for call establishment, processing, and release over ATM or IP backbone networks, since ATM or
IP backbone networks may soon replace some circuit switched trunk groups and tandem switches to reduce the effort associated with
sizing of circuit switched trunk groups and tandem switches.
Issue 2 of GR-3016-CORE describes BICC signaling and the call scenarios in which BICC signaling is used. It references the BICC
generic requirements in GR-3100-CORE for call scenarios in which BICC signaling, rather than ISUP signaling, is used.
Issue 2 refers to logical traffic groups, rather than physical trunk groups, and refers to Serving Nodes (SNs), rather than RTP
switch, whenever BICC signaling is used.
When using GR-3016, you may need to refer to GR-317, GR-394, GR-2857, GR-2974, GR-3015, GR-3100,
GR-1144, GR-1277, GR-1298, and/or GR-1299. You may also want to refer to GR-478, GR-508, and GR-1100.
Table of Contents:
View Table of Contents