1、 IHS Additional Content Page Access to Additional Content for ATIS-0700005 - 2007 (Click here to view the publication) This Page is not part of the original publication: This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the
2、 Copyright holder of this document. Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ATIS-0700005 ZIP File Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer The CII and CC Mediation Fun
3、ction(s) (MF) that perform the mapping; and The CII and CC information delivered to the LEA(s) over an “e” interface. The CII and CC MF(s) are based on the mapping functions as defined in 678, with enhancements as specified in this ATIS Standard. The CII and CC information delivered over the ”e” int
4、erface is based on 678 plus additional information. The reporting of CII via the encapsulated SIP messages as defined in 108 is out of scope of this ATIS Standard. 2 NORMATIVE REFERENCES The following standards contain provisions which, through reference in this text, constitute provisions of this A
5、TIS Standard. At the time of publication, the editions indicated were valid. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest
6、 version applies. 2.1 3rdGeneration Partnership Project (3GPP) Technical Specifications For the purpose of this ATIS Standard, the latest Release 6 version shall apply. NOTE Documents available at: . 228 3GPP TS 23.228, IP Multimedia Subsystem; Stage 2 (Release 6), v6.1.14.0. 229 3GPP TS 24.229, IP
7、Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 6), v6.11.0. 107 3GPP TS 33.107, Lawful interception architecture and functions (Release 6), v6.6.0. 108 3GPP TS 33.108, Handover interface for Lawful Interception (Re
8、lease 6), v6.10.0. ATIS-0700005 3 2.2 Alliance for Telecommunications Industry Solutions (ATIS) NOTE Documents available at: . 678 ATIS-1000678.2006, LAES for Voice over Packet Technologies in Wireline Telecommunications Networks, Version 2; and ATIS-1000678.a.2007, Supplement for LAES for Voice ove
9、r Packet Technologies in Wireline Telecommunications Networks. 025-B ANSI/J-STD-025-B-2006, Lawfully Authorized Electronic Surveillance. 2.3 International Telecommunication Union, Telecommunication Standardization Sector (ITU-T) NOTE Documents available at: . Y-101 Y.101, Global Information Infrastr
10、ucture Terminology: Terms and definitions, March 2000. X-680 X.680, Abstract Syntax Notation One (ASN.1): Specification of basic notation, July 2002. 2.4 Internet Engineering Task Force (IETF) NOTE Documents available at: . SDP RFC 2327, SDP: Session Description Protocol, April 1998. SIP RFC 3261, S
11、IP: Session Initiation Protocol, June 2002. 2.5 Federal Communications Commission (FCC) 99-230 FCC 99-230, CC Docket No. 97-213, Third Report and Order, Released August 31, 1999.105-153 FCC 05-153, ET Docket No. 04-295, First Report and Order and Further Notice of Proposed Rulemaking (NPRM), Septemb
12、er 23, 2005, which concludes that CALEA applies to facilities-based broadband Internet access providers and providers of interconnected Voice over Internet Protocol (VoIP).206-56 FCC 06-56, ET Docket No. 04-295, Second Report and Order and Memorandum Opinion and Order, Released May 12, 2006, which a
13、ddresses the assistance capabilities required, pursuant to section 103 of the Communications Assistance for Law Enforcement Act (CALEA), for facilities-based broadband Internet access providers and providers of interconnected Voice over Internet Protocol (VoIP).32.6 103rdCongress CALEA Communication
14、s Assistance for Law Enforcement Act (CALEA), Public Law 103-414, October 25, 1994. 1Available at . 2Available at . 3Available at . ATIS-0700005 4 Title 18 Wire and Electronic Communications Interception and Interception of Oral Communications, Title 18 of the United States Code, Chapter 119, Sectio
15、ns 2510 2522. 3 DEFINITIONS, ACRONYMS, communication-related events that represent or generate CII; and general capabilities needed for LAES for 3GPP VoIP and other multimedia services based on IMS (228, 229). 4.2 Electronic Surveillance Model LI is comprised of five major functions: access, deliver
16、y, collection, service provider administration, and law enforcement administration. These functions are discussed without regard to their implementation. The relationships between these functions are shown in Figure 1. ATIS-0700005 Service ProviderLaw Enforcement AgencyAccessDeliveryService Provider
17、AdministrationCollectionLaw EnforcementAdministrationLawfulAuthorizationFigure 1: Electronic Surveillance Model The Access Function, consisting of one or more IAP(s), isolates an intercept subjects communications unobtrusively. The Delivery Function, consisting of one or more entities, is responsibl
18、e for delivering intercepted communications to one or more Collection Function(s). The Service Provider Administration Function is responsible for informing the TSP Access and Delivery Functions of the intercept subjects identity and the type of communications to be intercepted. The Collection Funct
19、ion is responsible for collecting and analyzing intercepted communications. The Collection Function is the responsibility of the LEA. The Law Enforcement Administration Function is responsible for controlling and configuring the LEA CF. The Law Enforcement Administration Function is the responsibili
20、ty of the LEA. 4.3 Requirements A TSP shall provide access to the VoIP CC and CII or only CII, as required by the lawful authorization. When the voice, video, other IMS-based multimedia based services or any combination of these communication services are bundled as part of a single architecture (i.
21、e., IMS), the LI capabilities shall be provided. It shall be possible to provide CII for all sessions regardless of media type (i.e., the media type sub-field of a media description “m=” as defined in SDP) such as “audio”, “video”, “application”, “data”, or “control”. Note that a session description
22、 may contain a number of media descriptions. Support for CII mapped into discrete messages delivered to an LEA is based on the methodology described in 678 and expanded in this ATIS Standard. Subject to lawful authorization, CC shall be provided for sessions with audio, video or both media streams.
23、NOTE - Audio may be embedded in the video media stream. Subject to lawful authorization, CC shall be provided for other media type values (e.g., the media type sub-field=”application”). 8 ATIS-0700005 9 In the United States, TSP(s) shall be able to perform multiple simultaneous interceptions which i
24、nclude: The ability to access and monitor all simultaneous communications originated or received by the intercept subject; The ability for multiple LEA(s) to simultaneously monitor the same intercept subject while maintaining transparency, including between agencies; and The ability of the TSP to su
25、pport up to five (5) simultaneous and separate lawful interceptions on the same intercept subject. The LAES capabilities to provide CII and CC to an LEA for Server-based Conferencing is for further study. 4.4 Surveillance Events This section identifies communication-related events (termed surveillan
26、ce events) that generate CII and CC. 4.4.1 CII Events A CII event is a user action or signal that may cause a communication state change. These events are generally reflected by protocol messages that convey the state change. These events are not intended to reflect a particular technology, but to d
27、escribe the event in general. The mapping is intended to report those events based upon analysis of the intercepted messages. 678 contains the Stage 1 description for the CII events in this section. 4.4.1.1 CII Mapped Event Reporting The following 678 mapped messages are used to report CII events: A
28、nswer Change Origination Redirection Release ServingSystem ConferencePartyChange TerminationAttempt Connection ConnectionBreak NetworkSignal SubjectSignal MediaAndAddressReporting DirectSignalReporting (DSR) The DSR message may be used in conjunction with the above messages to report signaling that
29、cannot be mapped. ATIS-0700005 10 See Annex A of this ATIS Standard for the LAES support for IMS-based VoIP and other multimedia services specific SIP to surveillance message mapping. For SIP message mapping of the call hold event, SubjectSignal and ConnectionBreak messages shall be sent. For SIP me
30、ssage mapping of the call retrieve event, SubjectSignal and Connection messages shall be sent. 4.4.1.2 CII Dialed Digit Extraction Event Reporting In IMS-based VoIP, when the intercept subject dials or signals digits in the VoIP content stream after the session is established, the TSP shall isolate
31、and report to the LEA the dialled or signalled digits, when reasonably available, as CII to the LEA. A TSP may report dialled or signalled digits, when reasonably available, as CII. See Annex F of 678 for additional information. The following message is used for the Dialed Digit Extraction (DDE) eve
32、nt reporting: DialedDigitExtraction NOTE - The CII Dialed Digit Extraction event reporting is not required for other IMS-based multimedia services. 4.4.1.3 CII Location Reporting When the location is available at the IAP (e.g., P-Access-Network-Info-Header in 229) and delivery is authorized to ident
33、ify the location of the intercept subjects mobile terminal, location information shall be provided for the following events: Answer Origination Release Annex A provides the message and parameter mappings from SIP standard signaling to the surveillance messages reported to the LEA by the TSP for loca
34、tion information related to the intercept. The location information in TerminationAttempt described in 678 shall not be reported. 4.4.1.4 IMS 3GPP VoIP CII Serving System Event Reporting The serving system identification information includes the identity of the current system assigned to provide ser
35、vice for the Mobile Station (MS). Information regarding the occurrence of the event (e.g., identity of the system providing the intercept access, time, date) should be included. The IMS 3GPP VoIP ServingSystem event message shall be used to report the serving system identity currently serving the in
36、tercept subject (i.e., resulting from MS registration). The IMS 3GPP 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). 4.4.1.5 CII Event Reporting Requirements When a
37、LEA is only authorized to receive CII for an intercept subject, only CII events shall be reported. ATIS-0700005 11 4.4.2 Timing Requirements Timing information enables LEA(s) to associate CII with the content of communication. Timing information includes two elements: 1. Event Time-stamp - Each even
38、t report 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). 2. Event Timing Surve
39、illance 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 shall apply to the delivery of CII. A CII message shall be sent from the TSPs IAP to the LEAs CF with
40、in eight seconds of receipt of that message by the IAP at least 95% of the time, and with the CII event time-stamped to an accuracy of at least 200 milliseconds as defined in 99-230. If the GMT offset, as defined in X-680, of the CII IAP is available at the CII IAP or available at the MF/DF, it shal
41、l be reported as part of the timestamp information. The following timing requirements shall apply to the delivery of intercepted CC: When the CC is intercepted, the IAP shall expeditiously transmit the CC towards the MF/DF. 4.4.3 CC Related Events The following 678 messages are used to report CC-rel
42、ated events: CCOpen CCChange CCClose CCUnavailable UUContent 5 STAGE 2 DESCRIPTION: NETWORK PERSPECTIVE 5.1 Introduction This section identifies and describes the following: The triggering events and usage for the IMS 3GPP VoIP CII event messages; The information to be reported with each IMS 3GPP Vo
43、IP CII event message; and The application level CC delivery format and associated delivery information. Note that for the purpose of this ATIS Standard, the term IMS 3GPP VoIP CII pertains not only to the VoIP service but also to the other IMS-based multimedia services. Each message is described as
44、consisting of a set of parameters. Each parameter is either: Mandatory (M) - Required for the message; ATIS-0700005 Conditional (C) -Required in situations where a condition (defined in the usage column) is met; or Optional (O) - Provided at the discretion of the implementation. The information to b
45、e 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. 5.2 Architecture 5.2.1 Functional LI Architecture Figure 2 shows a general functio
46、nal LI architecture where both CC and CII are intercepted and delivered to LEA(s). This functional architecture assumes that one TSP 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 m
47、ore IAP(s) in the network for both CII and CC. Signaling SignalingCII IAPContent ContentCCIAPContentCIIMF-DFMF-DFContentCIICFeMF = Mediation FunctionDF = Delivery FunctionCF = Collection FunctiondFigure 2: Functional LI Architecture The “e” interface is the only interface addressed in this ATIS Stan
48、dard. The “d” interface is out of scope of this ATIS Standard. It is assumed that the LEA collection equipment maintains current state information concerning the associations between communication entities (i.e., intercept subject and associate(s). The collection equipment assumes that the last repo
49、rted association remains in effect until a subsequent message explicitly changes that association. 12 ATIS-0700005 13 5.2.2 Intercept Access Points With respect to multimedia services, IAP(s) are located in the network where multimedia (e.g., VoIP) communications are lawfully intercepted. There are two fundamental types of IAP(s): Communication-Identifying Information IAP (CII-IAP) Communication Content
