GR 2975 CORE : ISSUE 3

Preface
1. Introduction
1.1 Scope and purpose
1.2 Structure of this document
1.3 Target audience
1.4 Requirements terminology
1.5 Requirement labeling conventions
1.5.1 Numbering of requirement and related objects
1.5.2 Requirement, conditional requirement, and objective object
         identification
2. SAS configuration management
2.1 Service planning and negotiation
2.1.1 Lawful access services
2.1.1.1 Intercept requests
2.1.1.2 Subscriber information requests
2.1.2 Intercept service parameter negotiation
2.1.2.1 CDC provisioning
2.1.2.2 CCC provisioning
2.1.3 Operations systems access
2.1.4 Automation of subscriber information retrieval
2.1.5 SAS application and platform administration
2.2 SA user command interaction with SAS
2.2.1 Intercept data entry
2.2.1.1 Object ID generation
2.2.1.2 Traditional intercept data entry
2.2.1.3 Network-based intercept data entry
2.2.2 Network-based profile and intercept creation
2.2.3 Network-based intercept activation
2.2.4 Network-based intercept modification
2.2.5 Network-based profile and intercept deletion
2.2.6 SAS user interface
2.3 Operations interface
2.3.1 Interface information model
2.3.2 SAI transactions
2.3.2.1 CREATE transactions
2.3.3.2 UPDATE transactions
2.3.2.3 DELETE transactions
3. Record management
3.1 Information model
3.1.1 Information model diagram
3.1.2 Information model dictionary
3.1.3 Information model attribute dictionary
3.1.3.1 Data type definitions
3.1.3.2 Attribute definitions
3.2 Information queries
3.2.1 Intercept query
3.2.2 Delivery channel query
3.2.3 Intercepts by IAP network element query
3.2.4 Intercepts due to expire query
3.2.5 Intercept statistics query
3.2.6 Administrative log query
3.2.7 Intercept information request query
3.2.8 Ad-hoc query
3.3 Information backup and archive
3.4 SAS and IAP network element database synchronization
4. Security management
4.1 The TMN structure for security management
4.2 Prevention of security compromise
4.3 Detection of security compromise
4.4 Security administration
4.5 Security feature requirements
4.5.1 Identification
4.5.2 Authentication
4.5.3 System access control
4.5.4 Resource access control
4.5.5 Alarm management
4.5.6 Security log (audit)
4.5.7 Security administration
5. System performance
5.1 Scalable system growth
5.2 Modular system development
5.3 Number of simultaneous users
5.4 Number of switches
5.5 Database size
5.6 Simultaneous remote access sessions
6. Fault management
6.1 SAS self diagnostics
6.2 Connectivity tests
6.2.1 Interface to network element and OSS(s) tests
6.2.2 CDC test
6.3 Alarms and notification management
6.3.1 Network element alarms
6.3.2 SAS alarms
6.4 Trouble administration
Appendix A: A word about billing data
A.1 Usage management
A.2 Tariffing/pricing
A.3 Offline processing
Appendix B: SAS operation procedures - a user perspective
B.1 Court order processing
B.2 Intercept subject profiling
B.3 Facilities assignment
B.4 Network element provisioning
B.4.1 Surveillance profile creation
B.4.2 Surveillance setup
B.4.3 Surveillance activation/deactivation
B.4.4 Surveillance modification
B.4.5 Transfer of surveillance information from IAP network
              element to SAS
B.5 SAS notifications, maintenance and information
              management
B.5.1 Lawful access expiration notification
B.5.2 Reaction to notifications from the IAP network element
B.5.3 Determine surveillance status - perform CDC checks
B.5.4 SAS diagnostics
B.5.5 Backup of SAS information
B.5.6 Reconciliation of data stored in an IAP network
              element and in SAS
B.6 General administration
B.6.1 Administration log
B.6.2 Database reports
Appendix C: Sample message flow - laesCase provisioning with
              preassigned resources
Acronyms
References

Contains generic requirements for a Surveillance Administration System (SAS). The SAS is an Operations Support System (OSS) that can be used by wireline and wireless telecommunications service providers to administer and provision lawful access requests in one or many network elements. The SAS may be used to administer both CALEA-type traditional surveillances. CALEA-type surveillances need that Intercept Access Points (IAPs), such as end office switches, be provisioned to access and deliver call content and call identifying details to law enforcement. Traditional surveillances on the other hand, use loop-based techniques and as such the role of the SAS is to track intercept related information.