scope:

This standard specifies requirements and information models for the interface between Network Elements (NEs) and Service Provider Administrative Operations Systems for Law Enforcement Surveillance Management. It addresses the functionality addressed by the "a and c" reference points in J-STD-025. This standard supports subsets of configuration, fault, and security management functions required to manage access and delivery functions referenced in J-STD-025. This standard provides an information model needed to administer establishment and removal of surveillance. This standard supports a TMN Q3 interface as referenced in ANSI T1.210, T1.204, and T1.208. The following types of functionality are covered:

• Provisioning and activation or deactivation of a lawful surveillance.

• Provisioning of a lawful surveillance including the associated delivery resources.

• Ability to set up surveillance profiles (to control information provided by the lawful surveillance across the "e" interface).

• Supports secure transmission of management information for LAES operations.

• Provide event notifications for state changes of resources related to LAES.

• Ability to modify selected parameters of a lawful surveillance.

Purpose

The Law Enforcement community contracts with network Service Providers for telecommunications features that provide data and/or content of phone conversations related to a specific subject pursuant to a lawfully authorized court order. Establishment of a surveillance on a subject is controlled by the Service Providers administrative system and its interface to a Network Element (e.g., switching system).

The purpose of this standard is to provide a TMN Q3 interface standard that allows the LAES OS to manage LAES capabilities in the NEs (per the functionality scope described in 1.2).

Application

This model is a framework for defining management information to be exchanged by implementations of the Common Management Information Service Element (CMISE). The interactive class of OAM&P applications is supported in this standard by defining object classes, their attributes, and their relationships.

The goal of the LAES Operations Interface is to have it apply to many network technologies that LAES is being applied to, e.g., wireline and wireless. Thus, the LAES Operations Interface managed information is defined such that all or a major portion could be applied to a variety of current and new Network Elements (NEs) and network technologies.