Surveillance Administration System Generic Requirements
Document Number GR-2975
Issue Number 03
Issue Date Sep 2000
ABSTRACT: Issue 3 of GR-2975, Surveillance Administration System Generic Requirements, replaces Issue 2.
This document contains generic system requirements for a Surveillance Administration System (SAS). The SAS is an operations support
system (OSS) used by wireline and wireless telecommunications providers to administer and provision lawful access requests. Lawful
access requests come in the form of intercept court orders and subpoena requests from authorized agencies, such as Law Enforcement
Agencies (LEAs). Intercept court orders authorize access to a subject's call-identifying information and possibly communication
content. Subpoena requests generally require disclosure of certain subscriber information. This document focuses on the SAS
functionality needed to support intercept request administration and provisioning. Additional system requirements necessary to support
subpoena processing are provided, as needed, in the form of conditional requirements.
Two categories of intercept requests, known as network-based and traditional, are supported by the SAS. Network-based intercepts use
a special lawful access feature in an Intercept Access Point (IAP) to extract call-identifying information and communications content.
Telecommunication service providers were mandated to support network-based intercepts by the Communications Assistance for Law
Enforcement Act (CALEA). IAPs, such as end-office switches, require provisioning and operational functions from the SAS to enable a
CALEA intercept. Detailed requirements for a wireline switch-based intercept feature are provided in GR-2973. Traditional
intercepts, on the other hand, use loop-based access techniques to monitor a subject's signaling and communication. They require the
installation of a special intercept device for wireline intercepts. For traditional intercepts, the SAS is primarily an administration
system tracking intercept-related information.
Issue 3 of GR-2975 considered the six punch list items mandated by the FCC, along with other changes to clarify the SAS functions.
However, after a thorough review, the six new punch list items did not significantly affect the content of this document. Here is a
summary of the changes made to Issue 3.
- SAS is described in the context of existing network OSS's. SAS architecture information has been expanded to describe it in the
context of the TMN layered model and existing network OSS's.
- The CCC and CCC Group assignment were removed for Pen Register surveillance, because with the new punch list item, dialed digits are
sent over the CDC. (Refer to GR-2973).
- Some changes were made to the SAI transaction messages. Specifically, the MOC value (=) was added to certain parameters in the Create
CCC, Create CCGroup and Create CDC confirmation messages.
- Minor clarifications were added in the areas of performance of queries, number of interfacing systems, administration of recurring
data and providing maintenance information to central office personnel.
It is important to note that on August 15, 2000, the US Court of Appeals for the District of Columbia vacated in part and remanded
to the FCC, for further proceedings consistent with their opinion, the FCC's Third Report and Order dealing with four of the six punch
list items. Accordingly, Interim Standard J-STD-025A, which this document is based on, contains capabilities that may not be required
When using GR-2975, you may need to refer to GR-2973, TR-TSY-000827, GR-828 and ITU-T X.733. You may also want to refer
to TIA/EIA J-STD-025, J-STD-025A, ITU-T X.25, and/or ANSI T1.260.
Components of this product are:
Table of Contents:
View Table of Contents
We can accept credit cards, Wire Transfers, or Purchase Orders. For PDF, EMAIL, or DOWNLOAD media, you must complete your purchase online by credit card, or by calling Customer Service. If you have additional payment questions or we can assist in any way, please contact Customer Service. You can also go to our Ordering/Payment FAQs page for further information. See our Return Policy for details on returns.