Lawfully Authorized Electronic Surveillance (laes) for cdma2000




Yüklə 166.91 Kb.
tarix01.03.2016
ölçüsü166.91 Kb.








Lawfully Authorized Electronic Surveillance (LAES)

for cdma2000

Voice over IP (VoIP)




PN-3-0196

To be published as
TIA-1066


Copyright © 1995-2006 Telecommunications Industry Association.

All rights reserved.



Revision History

Ver.

Date

Source

Comment

1.0

4 March 05

Editor

Balloted text

2.0

28 Sep 05

Editor

Re-Ballot text

3.0

7 Dec 05

Editor

Default Ballot text

4.0

18 Jan 06

Editor

Second Default Ballot text

5.0

26 Apr 06

Editor

Pre-publication text





































Abstract

This cdma2000®1 Standard for Lawfully Authorized Electronic Surveillance (LAES) for Voice over Internet Protocol (VoIP) addresses the interfaces between a Service Provider (SP) and a Law Enforcement Agency (LEA) to assist the LEA in conducting electronic surveillance for cdma2000® VoIP service based on Multi-Media Domain (MMD).

This Standard provides capabilities for the reporting of Communication-Identifying Information (CII) and Communication Content (CC).

LAES for cdma2000 VoIP



Contents

List of Figures iii

List of Tables iv

Foreword v

1 Introduction 1

2 General 1

3 Purpose 1

4 Scope 1

5 Organization 1

6 References 3

7 Normative References 3

8 Informative References 3

9 Definitions, Acronyms and Abbreviations 4

10 Definitions 4

11 Acronyms and Abbreviations 6

12 Electronic Surveillance Architecture 8

13 Stage 1 Description: User Perspective 9

14 Introduction 9

15 Surveillance Events 9

15.1.1 CII Events 9

15.1.2 CC Events 11

16 General Capabilities 11

16.1.1 Communications Delivery 12

16.1.2 Timing Information 12

17 Stage 2 Description: Network Perspective 13

18 MMD Architecture 13

18.1.1 cdma2000 MMD Control Plane Architecture 14

19 Intercept Access Points 16

19.1.1 VoIP CII-IAPs 16

19.1.2 VoIP CC-IAPs 16

20 Use of ATIS-678 for VoIP CII Event Reporting 17

20.1.1 ATIS-678 Messages Utilized for cdma2000 VoIP CII Event Reporting 17

20.1.2 ServingSystem Event Reporting 18

21 CC Delivery Format 20

22 Stage 3 Description: Implementation Perspective 21

23 cdma2000 Object Tree 21

24 Abstract Syntax Notation Modules 21

A Annex A (Normative): Mapping of SIP CII Messages 22

A.1 Message Mappings 22

A.1 Message Mappings 22

B Annex B (Normative): cdma2000 VoIP CII and CC Delivery—Abstract Syntax Notation 23




List of Figures

Electronic Surveillance Model 8

cdma2000 Multi-Media Control Plane Architecture 14

Functional Architecture for Multi-Media Domain Interception 15

cdma2000 Object Tree 21




List of Tables


Foreword

(This foreword is not part of this Standard.)

This Standard was developed by TIA Subcommittee TR-45.6, cdma2000® Wireless Packet Data Technology.

At the time of publication, work is also on-going in the area of Multi-Media Domain (MMD) intercept.

While this standard supports both signaling and content for conference calls, support for conference servers is outside the scope of this document.

There are two annexes in this Standard. Both are normative and considered part of this Standard.



  1. Introduction




  1. General

This Standard addresses the interfaces between a Service Provider (SP) and a Law Enforcement Agency (LEA) to assist the LEA in conducting lawfully authorized electronic surveillance (LAES) for cdma2000 Voice over Internet Protocol (VoIP).

For the purposes of this Standard, “communications” is either communication-identifying information (CII) or communication content (CC), or both CII and CC. As used in this Standard, the term “electronic surveillance” refers to the lawfully authorized interception of communications for a particular communication subscriber. In this Standard, the terms ‘intercept subject’ and ‘subject’ refer to a communication service subscriber whose communications have been authorized by a court to be intercepted and delivered to a LEA.

The network intercepts on identities found in communications at Intercept Access Points (IAPs). The ability to intercept a specific subject’s communications is determined by the ability of the network to associate the communications with the subject’s identity or identities as derived from the lawful authorization.

In order for a SP to deliver intercepted communications to a LEA, a LEA must serve the SP with the necessary legal authorization identifying the intercept subject (or the facilities authorized to be intercepted by the court order), the communications to be intercepted, and the jurisdiction of the legal authorization. Once the authorization is obtained, the SP shall intercept and deliver the authorized communications toward the LEA’s procured equipment, facilities, or services.



  1. Purpose

The purpose of this Standard is to facilitate a SP’s assistance to law enforcement. This Standard defines a method to support electronic surveillance for cdma2000 VoIP based on Multi-Media Domain (MMD). Compliance with this Standard is intended to provide SPs with a Safe Harbor as permitted under Section 107(a) of the Communications Assistance for Law Enforcement Act (CALEA) statute.

  1. Scope

The scope of this Standard is to define the electronic surveillance capabilities to support LAES on the interfaces between a SP and a LEA to assist the LEA in conducting electronic surveillance for cdma2000 VoIP service based on MMD.

  1. Organization

Section 2: “References” is a list of references used in the preparation of this Standard.

Section 3: “Definitions and Acronyms” defines words and acronyms that are used in this Standard.

Section 4: “Electronic Surveillance Architecture” defines the surveillance model and functional entities.

Section 5: “Stage 1 Description: User Perspective” defines electronic surveillance from the law enforcement user point of view.

Section 6: “Stage 2 Description: Network Perspective” defines electronic surveillance from the network point of view.

Section 7: “Stage 3 Description: Message Implementation Perspective” provides the implementation perspective of electronic surveillance for cdma2000 VoIP.

Annex A (Normative): “SIP CII Surveillance Messages” provides the message and parameter mappings from SIP standard signaling to surveillance messages reported to the LEA by the SP for a cdma2000 VoIP intercept.

Annex B (Normative): “cdma2000 VoIP CII and CC Delivery Abstract Syntax Notation” provides the ASN.1 for CII and CC.



  1. References




  1. Normative References

The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers of currently valid national standards published by them.

American National Standards Institute (ANSI) Accredited standards

[025-A] ANSI-J-STD-025-A-2003, Lawfully Authorized Electronic Surveillance; 2003.



Alliance for Telecommunications Industry Solutions (ATIS) and Telecommunications Industry Association (TIA) Standards

[ATIS-678] ATIS 1000678.2006, Lawfully Authorized Electronic Surveillance (LAES) for Voice over Packet Technologies in Wireline Telecommunications Networks, Version 2 (Revision of ANS T1.678-2004), Alliance for Telecommunications Industry Solutions.

[873] TIA-873, IP Network for cdma2000® Spread Spectrum Systems; 2003.

[025-B] TIA/EIA/J-STD-025-B, Lawfully Authorized Electronic Surveillance; 2003.



Federal Communications Commission (FCC)

[99-230] FCC 99-230, CC Docket No. 97-213, Third Report and Order, Released 8/31/99.



International Telecommunication Union, Telecommunication Standardization Sector (ITU-T)

[Y-101] Y.101, Global Information Infrastructure Terminology: Terms and definitions, March 2000.



Internet Engineering Task Force (IETF)

[SIP] RFC 3261, SIP: Session Initiation Protocol, June 2002.



  1. Informative References

Telecommunications Industry Association (TIA) Standards

[NAM] TSB-151, IP Network Reference Model (NRM) for cdma2000® Spread Spectrum Systems; 2003.



  1. Definitions, Acronyms and Abbreviations




  1. Definitions

Associate

A communications user whose equipment, facilities, or services are communicating with a subject.



Call Management Server (CMS)

A core network function that includes sending and receiving signaling and call control information (e.g., SIP messages) for the management of a call to and from endpoints (e.g., mobile station.).



Collection Function (CF)

The location where the intercepted communications content and communication-identifying information is collected by a law enforcement agency (LEA).



Communication-Identifying Information (CII)

Signaling information that identifies the origin, direction, destination, or termination of each communication generated or received by a subscriber by means of any equipment, facility, or service of a Service Provider.



Conference URI

A SIP URI that uniquely represents a conference.



Core Network

Defined in [Y-101] to be “a portion of the delivery system composed of networks, system equipment, and infrastructures, connecting the service providers to the access network”.



Delivery Function (DF)

A logical entity in the Service Provider’s network that delivers intercepted communications content and communications-identifying information toward one or more Collection Functions for each LEA requesting intercept.

e’ interface

The interface between a Delivery Function and a Collection Function.



Electronic Surveillance

The statutory-based legal authorization, process, and associated technical capabilities and activities of LEAs related to the interception of wire, oral, or electronic communications while in transmission as authorized under U.S. law. As used herein, also includes the acquisition of communication-identifying information. As used in this Standard, surveillance refers to a single communication intercept, pen register, or trap and trace. Its usage in this Standard does not include administrative subpoenas for obtaining a subscriber’s toll records and information about a subscriber’s service that a LEA may employ before the start of a communication intercept, pen register, or trap and trace. For the purposes of this document, LI and LAES are synonymous with electronic surveillance.



Intercept Access Point (IAP)

A point within a communications system where some of the communications content or communication-identifying information of an intercept subject’s equipment, facilities and services are accessed.



Intercept Subject

A telecommunication service subscriber whose communication-identifying information and communications content or communications-identifying information only have been authorized by a court to be intercepted and delivered to a LEA. The identification of the subject is limited to identifiers used to access the particular equipment, facility, or communication service (e.g., network address, terminal identity, subscription identity).



Law Enforcement Agency (LEA)

A government entity with the legal authority to conduct electronic surveillance (e.g., the Federal Bureau of Investigation or a local police department).



Lawful Intercept (LI)

See Electronic Surveillance.



Mobile Station

A wireless terminal used by subscribers to access network services over a radio interface.



Pen Register

Is defined in 18 U.S.C. § 3127(3) as “a device or process which records or decodes dialing, routing, addressing, or signaling information transmitted by an instrument or facility from which a wire or electronic communication is transmitted, provided, however, that such information shall not include the contents of any communication, but such term does not include any device or process used by a provider or customer of a wire or electronic communication service for billing, or recording as an incident to billing, for communications services provided by such provider or any device or process used by a provider or customer of a wire communication service for cost accounting or other like purposes in the ordinary course of its business”.



Subject

See Intercept Subject.



Surveillance

Within this Standard surveillance refers to electronic surveillance (see Electronic Surveillance).



Trap and Trace

Is defined in 18 U.S.C. § 3127(4) as “a device or process which captures the incoming electronic or other impulses which identify the originating number or other dialing, routing, addressing, and signaling information reasonably likely to identify the source of a wire or electronic communication, provided, however, that such information shall not include the contents of any communication”.



  1. Acronyms and Abbreviations

ANS American National Standard

ANSI American National Standards Institute

APDU Application Protocol Data Unit (see [ATIS-678])

ASN.1 Abstract Syntax Notation One

ATIS Alliance for Telecommunications Industry Solutions

BGCF Breakout Gateway Control Function

CALEA Communications Assistance for Law Enforcement Act

CC Communication Content

CF Collection Function

CII Call Identifying Information

CMS Call Management Server

CS Circuit Switched

CSCF Call Session Control Function

DDE Dialed Digit Extraction

DF Delivery Function

DSR Direct Signal Reporting

FCC Federal Communications Commission

HSS Home Subscriber System

IAP Intercept Access Point

I-CSCF Interrogating CSCF

IETF Internet Engineering Task Force

IP Internet Protocol

ITU-T International Telecommunication Union, Telecommunication Standardization Sector

LAES Lawfully Authorized Electronic Surveillance. See Electronic Surveillance

LAESP LAES Protocol

LEA Law Enforcement Agency

LI Lawful Intercept

MGCF Media Gateway Control Function

MMD Multi-Media Domain

MRFC Media Resource Function Control

MRFP Media Resource Function Processor

MS Mobile Station

OID Object Identifier

P-CSCF Proxy CSCF

PLMN Public Land Mobile Network

PSTN Public Switched Telephone Network

S-CSCF Serving CSCF

SDP Session Description Protocol

SIP Session Initiation Protocol

SIP URI Session Initiation Protocol Uniform Resource Identifier

SP Service Provider

TEL URL Telephone Uniform Resource Locator

TIA Telecommunications Industry Association

URI Uniform Resource Identifier

URL Uniform Resource Locator

VoIP Voice over IP



  1. Electronic Surveillance Architecture

Interception is comprised as five major functions: access, delivery, collection, service provider administration, and law enforcement administration.2 These functions are discussed without regard to their implementation. The relationships between these functions are shown in Figure 1.



  1. Electronic Surveillance Model

The Access Function, consisting of one or more IAPs, isolates an intercept subject’s communications unobtrusively.

The Delivery Function, consisting of one or more entities, is responsible for delivering intercepted communications to one or more Collection Functions.

The Service Provider Administration Function is responsible for informing the SP Access and Delivery Functions of the subject’s identity and the type of communications to be intercepted.

The Collection Function (CF) is responsible for collecting and analyzing intercepted communications. The CF is the responsibility of the LEA.

The Law Enforcement Administration Function is responsible for controlling the LEA CF. The Law Enforcement Administration Function is the responsibility of the LEA.

The lawful authorization, while neither a network entity nor an interface reference point, is an important part of VoIP LAES. No intercepts shall take place without specific lawful authorization.



  1. Stage 1 Description: User Perspective




  1. Introduction

This section presents the law enforcement user perspective (Stage 1) requirements for LAES for VoIP services based on MMD in cdma2000 telecommunications networks; communication-related events that represent or generate CII; and general capabilities needed for LAES for cdma2000 VoIP service based on MMD.

A SP is required to provide access to the VoIP communication content and communication-identifying information or communication-identifying information only for intercept subjects.

This Standard supports CII being mapped into discrete messages based on [ATIS-678] (See Section 5.2.1.1) which shall then be delivered to a LEA. This method is preferred by LEA. Alternatively, as determined by pre-existing agreement between the SP and the LEA, a SP may deliver CII in encapsulated Session Initiation Protocol (SIP) messages (i.e., Direct Signal Reporting (DSR) messages) (See Section 5.2.1.2). If encapsulation is used by the SP, CII will not be altered.

Some circumstances dictate that the subject’s intercepted communications need to be delivered to more than one LEA CF simultaneously. This will occur when different LEAs are conducting independent investigations on the same subject. The Delivery Function (DF) shall duplicate the CC, CII, or both, and deliver only authorized CC and CII or CII only, to the LEA. No more than five CFs are required to be supported for any single intercept subject.



  1. Surveillance Events

This section identifies communication-related events (termed surveillance events) that generate CII and CC.

Only the SIP aspects of [ATIS-678] apply to the cdma2000 LAES support for VoIP.



      1. CII Events

A CII event is a user action or signal that may cause a communication state change. These events are not intended to reflect a particular technology, but to describe the event in general.

[ATIS-678] contains the Stage 1 description for the CII events in this Section. Section 5.2.1.5 of this Standard describes the usage of the ServingSystem event.



        1. CII Mapped Event Reporting

The following [ATIS-678] mapped messages are used to report CII events:

  • Answer

  • Change

  • Origination

  • Redirection

  • Release

  • ConferencePartyChange

  • TerminationAttempt

  • Connection

  • ConnectionBreak

  • DialedDigitExtraction (DDE)

  • NetworkSignal

  • SubjectSignal

  • MediaAndAddressReporting

In some circumstances, the DSR message (See Section 5.2.1.2) may be used in conjunction with the above messages.

See Annex A of this Standard for the specific SIP to surveillance message mapping.



        1. CII DSR Event Reporting

The following [ATIS-678] DSR message can be alternatively used for the mapped messages in Section 5.2.1.1 to report CII events:

  • DirectSignalReporting (DSR)

        1. CII DDE Event Reporting

In cdma2000 VoIP, when the subject dials or signals digits in the VoIP content stream after the session is established, the SP shall isolate and report the dialed or signaled digits when reasonably available (See Section 6.2.1) as CII to the LEA. A SP may report dialed or signaled digits other than those that are call completing and has no obligation to determine which dialed or signaled digits actually complete or could complete a call.

        1. CII Location Reporting

Location information is provided for the following events when the location is reasonably available at the IAP and delivery is authorized to identify the location of the intercept subject’s mobile terminal.

  • Answer

  • Origination

  • Release

  • TerminationAttempt

Location information shall be derived from SIP VoIP signaling (i.e., P-Access-Network-Info-Header in [873]).

        1. cdma2000 VoIP CII ServingSystem Event Reporting

The serving system identification information includes the identity of the current system assigned to provide service for the MS. Information regarding the occurrence of the event (e.g., identity of the system providing the intercept access, time, date) should be included.

The cdma2000 VoIP ServingSystem event message shall be used to report the serving system identity currently serving the intercept subject (i.e., resulting from MS registration).



The cdma2000 VoIP ServingSystem event message shall also be used to report addressing and contact information registered by the intercept subject (i.e., registered via the SIP “REGISTER” method).

        1. CII Reporting Guidelines

When a LEA is only authorized to receive CII for an intercept subject, only cdma2000 VoIP CII events shall be reported.

      1. CC Events

The following [ATIS-678] mapped messages are used to report CC events:

  • CCOpen

  • CCChange

  • CCClose

  • CCUnavailable

  1. General Capabilities

This section describes the general capabilities to support LAES for cdma2000 Voice over IP based on MMD:

  • The CII-IAP(s) shall be capable of intercepting and delivering VoIP information to the DF for an intercept subject along with other information (e.g., subject identity) as required by this Standard for CII reporting. All SIP VoIP messages to or from a targeted subscriber, and all SIP VoIP messages executed on behalf of a targeted subscriber for VoIP session control are intercepted at the IAP(s).

  • The CII should be sent with a reliable transport mechanism as agreed to between the SP and the LEA.

  • Signaling associated with the subject’s communication may be identified by SIP URI, TEL URL, or by other means.

  • A SP shall be responsible for decrypting or decompressing, or ensuring the LEA’s ability to decrypt or decompress, any communication or signaling encrypted or compressed by a subscriber or customer, when the encryption or compression was provided by the SP and the SP possesses the information necessary to decrypt or decompress the communication or signaling. A SP that provides the LEA with information about how to decrypt or decompress a communication or signaling (e.g., identifying the type of compression software used to compress the communication or signaling, directing the LEA to the appropriate vendor that can provide decryption or decompression equipment, or providing the encryption key used to encrypt the communication or signaling) fully satisfies its obligation under the preceding sentence.

  • Once Lawful Interception is activated, interception should occur expeditiously but should not be initiated for an on-going call. Once deactivated, Lawful Interception should end expeditiously.

  • Interception of CII does not constitute a guarantee that the intercepted CII was also received by the subject or associates. For example, when signaling to a mobile station (MS) is intercepted, it is not known whether the signaling is actually received by the MS due to extraordinary network conditions (e.g., network congestion/failure and air interface problems).

  • Only the communication (i.e., CC) transmitted to, or received from, the intercept subject under surveillance3 shall be delivered to the LEA. Only the information (i.e., CII) transmitted to, or received from, or associated with the intercept subject’s equipment, facilities, or service under surveillance shall be delivered to the LEA.

      1. Communications Delivery

Various technologies can be used to support the ‘e’ interface between a SP and law enforcement.

      1. Timing Information

Timing information enables LEAs to associate CII with the content of communication. Timing information includes two elements:

  • Event Time-stamp - Each surveillance message shall contain a time-stamp that is recorded within a specific amount of time from when the event triggering the surveillance message was detected (i.e., the time difference between the time the CII triggering event was detected and the time recorded in the time-stamp).

  • Event Timing – Surveillance messages shall be sent to the LEA within a defined amount of time after the information pertaining to the CII triggering event is available at the IAP.

The following timing requirements from [99-230] shall apply to the delivery of CII.

  • A communication-identifying message shall be sent from the carrier's IAP to the LEA's Collection Function within eight seconds of receipt of that message by the IAP at least 95% of the time, and with the communication event time-stamped to an accuracy of at least 200 milliseconds.

The following timing requirements shall apply to the delivery of intercepted VoIP content.

  • Intercepted VoIP content shall be expeditiously transmitted by the IAP towards the DF with its interception.

  1. Stage 2 Description: Network Perspective

This section identifies the triggering events and usage for the VoIP CII event messages, identifies and describes the information to be reported with each VoIP CII event message, and also describes the application level CC delivery format and associated delivery information.

The communication events described in Stage 1 convey the basic information for reporting the disposition of a communication. This section describes those events and supporting information.

Each message is described as consisting of a set of parameters. Each parameter is either:


  • mandatory (M)—required for the message; or

  • optional (O)—provided at the discretion of the implementation; or

  • conditional (C)—required in situations where a condition (defined in the usage column of the table) is met.

The information to be carried by each parameter is identified. Please note that both optional and conditional parameters at Stage 2 are considered to be OPTIONAL syntactically in Abstract Syntax Notation One (ASN.1) Stage 3 descriptions.

  1. MMD Architecture

The cdma2000 MMD system is a distributed architecture that provides Multi-Media services, which includes VoIP service. The architecture is based on SIP standard signaling.

There are different instances of the Call Session Control Function (CSCF) that manage the SIP sessions:



  • Serving CSCF (S-CSCF): This entity is always located in the home network and performs the session control services for the MS. It maintains a session state as needed by the network operator for support of the services. Within an operator’s network, different S-CSCFs may have different functionalities. The functions performed by the S-CSCF during a session include:

  • Processes registration requests and makes its information available through the location server (e.g., Home Subscriber System (HSS));

  • Provides session control for the registered endpoint's sessions;

  • Provides endpoint(s) with service related information (e.g., notification of tones/announcement together with location of additional media resources, billing notification and forwarding information); and

  • Interacts with Public Switched Telephone Network (PSTN) or Circuit Switched (CS) networks through the Breakout Gateway Control Function (BGCF)/Media Gateway Control Function (MGCF).

  • Proxy CSCF (P-CSCF): This entity may be located either in the visited or home network. The P-CSCF is used to proxy requests from the MS to a serving CSCF in the home network and to return responses from the home network to the MS.

  • Interrogating-CSCF (I-CSCF): The I-CSCF is the entry point to the network responsible for locating the S-CSCF serving the user.

Figure 2 is a composite from figures in [NAM] and illustrates the cdma2000 Multi-Media session control architecture:



  1. cdma2000 Multi-Media Control Plane Architecture

The BGCF and MGCF are used for interfacing with the PSTN and other circuit switched based Public Land Mobile Networks (PLMNs).

Media Resource Function Control (MRFC) and Media Resource Function Processor (MRFP) are used to provide control and mixing of media resources and handling of Multi-Media conferences.

There are multiple types of application servers in the network with different interfaces to other network entities.


      1. cdma2000 MMD Control Plane Architecture

Figure 3 shows a general functional LI architecture for a cdma2000 Multi-Media network where both CC and CII are intercepted and delivered to LEAs. This functional architecture assumes that one SP is providing both CC and packet transport. The DF can be separated into CII delivery and CC delivery or can be combined into CII and CC delivery. There may be one or more IAPs in the network for both CII and CC.

.



  1. Functional Architecture for Multi-Media Domain Interception

The ‘e’ interface is the only interface considered for standardization in this document.

It is assumed that the LEA collection equipment maintains current state information concerning the associations between communication identities. The collection equipment assumes that the last reported association remains in effect until a subsequent VoIP message explicitly changes that association.



  1. Intercept Access Points

With respect to Multi-Media services, IAPs are places in the network where Multi-Media (e.g., VoIP) communications are lawfully intercepted. There are two fundamental types of IAPs:

  • Communication-Identifying Information IAPs (CII-IAPs)

  • Communication Content IAPs (CC-IAPs)

CII-IAPs and CC-IAPs are associated with CII and CC intercept functions that perform the actual interception of communication information and content. The CII-IAP provides expeditious access to the reasonably available CII for communications made by an intercept subject or for communications made to an intercept subject or communications made on behalf of the intercept subject. The CII-IAP shall access the CII for the intercept subject unobtrusively. Access to CII shall not deny the availability of any service to either the subject or associates.

CII-IAPs and CC-IAPs may be distributed to enable the interception and reporting of CII and CC from different network elements. Placement of IAPs is network specific and may vary between networks. For example, if a P-CSCF exists in a home network, it may not be necessary to have CII-IAPs at both a P-CSCF and S-CSCF because all necessary CII may be intercepted and reported at the S-CSCF.



      1. VoIP CII-IAPs

CII is reasonably available if the information is present at the VoIP CII-IAP. CII is “reasonably available” to a SP if it is present at a VoIP CII-IAP and can be made available without the SP being unduly burdened with network modifications. The determination of what does or does not “unduly burden” the SP is beyond the scope of this Standard.

Network protocols (except the LAESP) do not need to be modified solely for the purpose of passing CII. The specific elements of CII that are reasonably available at any one IAP may vary.

VoIP CII-IAP(s) are places in the network where lawfully authorized CII is intercepted. VoIP CII-IAPs are associated with CII intercept functions that perform the actual interception of CII. CII intercept functions are associated with one or more network elements. CII intercept functions may be collocated within the same network element or may be distributed among multiple network elements.

The placement of VoIP CII-IAP(s) is dependent on the SP implementation.



      1. VoIP CC-IAPs

VoIP CC-IAPs intercept communication content between an intercept subject and the associate(s). A VoIP CC-IAP provides the intercept capability for the VoIP communication or session content. It intercepts the required content and presents it to the DF. See Section 6.4 for details on content intercept.

When legally authorized, the SP shall access and deliver communications content, if reasonably available, for the duration of communications originated by and terminated to the surveillance subject’s equipment, facilities, or service4.

VoIP CC-IAP(s) are places in the network where lawfully authorized content is intercepted. VoIP CC-IAPs are associated with CC intercept functions that perform the actual interception of communication content. CC intercept functions are associated with one or more network elements. CC intercept functions may be collocated within the same network element or may be distributed among multiple network elements.

The placement of VoIP CC-IAP(s) is dependent on the SP implementation.



  1. Use of ATIS-678 for VoIP CII Event Reporting

In [ATIS-678], network CII information is mapped into Voice over Packet enhanced [025-A] messages. This Standard uses some of those enhanced messages (see Section 6.3.1) to support cdma2000 VoIP CII events.

      1. ATIS-678 Messages Utilized for cdma2000 VoIP CII Event Reporting

The following LAES messages, which are defined in [ATIS-678], are utilized for cdma2000 VoIP CII reporting:

  • Answer

  • CCClose

  • CCOpen

  • Change

  • Origination

  • Redirection

  • Release

  • ServingSystem

  • TerminationAttempt

  • ConferencePartyChange

  • Connection

  • ConnectionBreak

  • DialedDigitExtraction (DDE)

  • NetworkSignal

  • SubjectSignal

  • MediaAndAddressReporting

  • CCChange

  • CCUnavailable

  • DirectSignalReporting (DSR)

      1. ServingSystem Event Reporting




        1. ServingSystem Event Reporting for SIP Registration per ATIS-678

For registration, the following parameters as defined in the ServingSystem Event in [ATIS-678] are to be used without change:

  1. ServingSystem Message Parameters for SIP Registration

Parameter

MOC

Usage

CaseIdentity

M

Identifies the Intercept Subject.

IAPSystemIdentity

C

Included to identify the system containing the IAP, when the underlying data carriage does not imply that system.

TimeStamp

M

Identifies the date and time that the event was detected.

SystemIdentity

C

Provided to identify the serving system when the intercept subject is authorized for service by the TSP.

NetworkAddress

C

For further study in VoP. Provided for backward compatibility with J-STD-025A.

RequestIdentity

C

Include to identify an address registration or deregistration request within a system, when available.

AddressRegistrationType

C

Indicates whether an address registration, address deregistration, or both were detected. Provide when appropriate.

RegisteringPartyIdentity

C

Identifies the party for whom address registration, deregistration, or both, are being attempted. Provide when appropriate.

RequestingPartyIdentity

C

Include to identify the party requesting the address registration, deregistration, or both, when different from the RegisteringPartyIdentity.

RegistrarIdentity

C

Identifies the registrar to which the address registration request, deregistration request, or both, are destined. Provide when appropriate.

RequestAddressInformation

C

Address information attempted to be registered, deregistered, or both, when present.

ResponseAddressInformation

C

Address information included in the response to the attempt to register, deregister, or both register and deregister address information, when present.

FailureReason

C

Include to indicate the reason that an address registration, deregistration, or both, were unsuccessful, when the registration, deregistration, or both, are unsuccessful.

ExpirationPeriod

C

Include to identify the address-independent registration lifetime applicable to the registered addresses, when known.

Protocol-Specific Parameters

C

Included, when protocol-specific parameter information from VoP signaling protocols (e.g., SIP message contents) are to be mapped into this message. For detailed descriptions of the mapping of this information, see the protocol-specific mapping annexes (e.g., [ATIS-678] Annex B on SIP mappings).

EncapsulatedSignalingMessage

O

The signaling message received from the intercept subject, sent to the intercept subject, or sent or received on behalf of the intercept subject, which stimulated the sending of the ServingSystem message.

        1. ServingSystem Event Reporting for Terminal Registration

As defined in this Standard, the ServingSystem Event is also used to report terminal registration. The ServingSystem Message shall be triggered when:

  • the MS is authorized with another SP or in another service area.

The event may be optionally reported when the subject is registering in the home network.

The ‘SystemIdentity’ parameter is used to report the serving system identity.

For terminal registration, the following parameters are to be used:


  1. ServingSystem Message Parameters for Terminal Registration

Parameter

MOC

Usage

CaseIdentity

M

Identifies the Intercept Subject.

IAPSystemIdentity

C

Included to identify the system containing the IAP, when the underlying data carriage does not imply that system.

TimeStamp

M

Identifies the date and time that the event was detected.

SystemIdentity

C

Include, when authorizing service to a SP, to identify the SP



  1. CC Delivery Format

Delivery of CC for cdma2000 VoIP is based on the CC delivery method in [ATIS-678]. See the CDMA2000-VoIP-CC-Module in Annex B of this Standard for the content delivery format.

When CC is intercepted, a LAES CCOpen message is sent to the LEA(s) indicating CC will be delivered. As part of that CCOpen message, the format of the CC Headers encapsulating the intercepted CC is identified. See the ‘ContentDeliveryFormat’ parameter description in [ATIS-678] and in Section 7.2 of this Standard for more detail.



  1. Stage 3 Description: Implementation Perspective




  1. cdma2000 Object Tree



  1. cdma2000 Object Tree

  1. Abstract Syntax Notation Modules

With respect to the CC delivery format, the CC module object identifier (OID) containing the definition (i.e., the defined format) for the CC Header is sent in the ‘ContentDeliveryFormat’ parameter to the LEA(s) to identify the specific CC header format being used. The specific ASN.1 field containing the OID is the ‘cc-APDU’ field in ‘ContentDeliveryFormat’ (see T1S1-LAES-VoP-Abstract-Syntax-Module [ATIS-678]).

For cdma2000 VoIP CC delivery, the OID for the cdma2000 CC module (CDMA2000-VoIP-CC-Module) is used and sent in the ‘cc-APDU’ field of the LAES CCOpen message (see Annex B of this Standard and the CDMA2000-VoIP-CII-Module ASN.1 in Annex B of this Standard).



  1. Annex A (Normative): Mapping of SIP CII Messages

This annex is normative and is considered part of this Standard.

This annex provides the message and parameter mappings from SIP standard signaling to the surveillance messages reported to the LEA by the SP for a VoIP intercept that are not defined in [ATIS-678].

The tables in [ATIS-678] Annex B provide the SIP standard signaling to surveillance messages for those [ATIS-678] messages used in this document (See Sections 5.2.1.1 and 5.2.2). The term “CMS” as used in [ATIS-678] Annex B is replaced by the term “CSCF”.


    1. Message Mappings

This section provides additions or enhancements to the mapping tables in [ATIS-678] Annex B to support cdma2000 VoIP.

Table 2 provides additional mappings for the cdma2000 SIP VoIP location parameter.



  1. Mapping of SIP Location Information to ATIS-678 Mapped Messages

SIP

Message

Parameter

ATIS-678 Mapped

Message

Parameter

Description

200-OK(INVITE)

P-Access-Network-Info-Header



Answer

location [5] Location



Provides location information when available.

INVITE

P-Access-Network-Info-Header



Origination

location [8] Location



Provides location information when available.

INVITE

P-Access-Network-Info-Header



Termination Attempt

location [6] Location



Provides location information when available.

BYE

P-Access-Network-Info-Header



Release

location [4] Location



Provides location information when available.



  1. Annex B (Normative): cdma2000 VoIP CII and CC Delivery—Abstract Syntax Notation

This annex is normative and is considered part of this Standard.
CDMA2000-VoIP-CII-Module

{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cii-voip(2) version-1(0)}


DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
CaseIdentity,

IAPSystemIdentity,

Timestamp

FROM Laesp-j-std-025-b

{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) j-std-025(0) j-std-025-b(2) version-1(0)}
Answer,

CCClose,


CCOpen,

Change,

Origination,

Redirection,

Release,


ServingSystem,

TerminationAttempt,



ConferencePartyChange,

Connection,

ConnectionBreak,

DialedDigitExtraction,

NetworkSignal,

SubjectSignal,

DirectSignalReporting,

MediaAndAddressReporting,

CCChange,

CCUnavailable

FROM T1S1-LAES-VoP-Abstract-Syntax-Module

{iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) t1-678(0) cii(0) common (0) version-2(1)}
cdma2000VoIPCCDeliveryHeaderModuleOID

FROM CDMA2000-VoIP-CC-Module

{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cc-voip(3) version-1(0)};
ccDeliveryHeaderModuleOID OBJECT IDENTIFIER ::= {cdma2000VoIPCCDeliveryHeaderModuleOID}
cdma2000-VoIP-CII-Module-OID OBJECT IDENTIFIER ::=

{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cii-voip(2) version-1(0)}

-- OID created from CDMA2000-VoIP-CII-Module Identifier
protocolIdentifier OBJECT IDENTIFIER {cdma2000-VoIP-CII-Module-OID}
CDMA2000-VoIP-Protocol ::= SEQUENCE {

protocolIdentifier OBJECT IDENTIFIER,

voipMessage CDMA2000voipMessage

}
CDMA2000voipMessage ::= CHOICE {

cdma2000VoIP-answer [1] Answer,

cdma2000VoIP-ccClose [2] CCClose,

cdma2000VoIP-ccOpen [3] CCOpen, -- use OID ccDeliveryHeaderModuleOID

-- with CCDeliveryFormat



cdma2000VoIP-change [4] Change,

cdma2000VoIP-origination [5] Origination,

null-6 [6] NULL, -- reserved by [ATIS-678]

cdma2000VoIP-redirection [7] Redirection,

cdma2000VoIP-release [8] Release,

cdma2000VoIP-servingSystem [9] ServingSystem,

cdma2000VoIP-termAttempt [10] TerminationAttempt,

null-11 [11] NULL, -- reserved by [ATIS-678]



cdma2000VoIP-conferencePartyChange [12] ConferencePartyChange,

cdma2000VoIP-connection [13] Connection,

cdma2000VoIP-connectBreak [14] ConnectionBreak,

cdma2000VoIP-dialedDgtExtrn [15] DialedDigitExtraction,

cdma2000VoIP-networkSignal [16] NetworkSignal,

cdma2000VoIP-subjectSignal [17] SubjectSignal,

cdma2000VoIP-directSignalReporting [18] DirectSignalReporting,

cdma2000VoIP-mediaAndAddressReporting [19] MediaAndAddressReporting,

cdma2000VoIP-ccChange [20] CCChange,

cdma2000VoIP-ccUnavailable [21] CCUnavailable,

null-22 [22] NULL, -- reserved by [ATIS-678]

null-23 [23] NULL, -- reserved by [ATIS-678]

null-24 [24] NULL -- reserved by [ATIS-678]

}

END -- of CDMA2000-VoIP-CII-Module



CDMA2000-VoIP-CC-Module

{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cc-voip(3) version-1(0)}


DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
CC-APDU

FROM CCDeliveryHeaderModule

{iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) t1-678(0) ccdeliveryheader(1) version-1(0)};
cdma2000VoIPCCDeliveryHeaderModuleOID OBJECT IDENTIFIER ::=

{iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cc-voip(3) version-1(0)}



-- OID created from CDMA2000-VoIP-CC-Module Identifier
CDMA2000VoIP-CC-APDU ::= CC-APDU
END -- of CDMA2000-VoIP-CC-Module

1 cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA)

2 See [025-A] and [ATIS-678] for further information.

3 Note that intercepting CC not sent to or received from the subject (e.g., subject’s equipment, facilities, or service such as redirected calls or conferences on hold) are for further study.

4 Interception of redirected CC is for further study.



Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©azrefs.org 2016
rəhbərliyinə müraciət

    Ana səhifə