TIA J-STD-025-2000 Lawfully Authorized Electronic Surveillance Upgrade and Revision of IS-J-STD-025 This Standard is Available Simultaneously with J-STD-025-A and J-STD-025-B [ReplT.pdf

1、JOINT STANDARD ANSI - J- STD- O2 5 -2 O O0 Approved December 19, 2000 Lawfully Authorized Electronic Surveillance J-STD-025 (Upgrade and Revision of IS-J-STD-025) DECEMBER 2000 Jointly Developed By: TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Indusiry Association represents the co

2、mmunications sector of Sponsored by the Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE Standards and Publications are adopted in accordance with the American National St

3、andards Institute (ANSI) patent policy. By such action, the Telecommunications Industry Association or the Alliance for Telecommunications Industry Solutions or its sponsored Committee T1 does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adoptin

4、g the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicabilit

5、y of regulatory limitations before its use. (From Project No. 4846, formulated under the cognizance of the TIA TR-45.2 Subcommittee and Committee Tl.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2000 Standards Telephone: 703/907- 7700; FAX: 703/907-7728. This document is being published by

6、Global Engineering on behalf of TIA and ATIS on behalf of Committee T1. This Standard was coordinated between ATIS Committee T1 and TIA. A Word from TIA TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturer

7、s and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his/her particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmem

8、ber of TIAEIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA/EIA members, whether the standard is to be used either domestically or international

9、ly. A Word fmm ATIS Committee T1 Established in February 1984, Committee T1 develops technical standards, reports and requirements regarding interoperability of telecommunications networks at interfaces with end-user systems, carriers, information and enhanced-service providers, and customer premise

10、s equipment (CPE). Committee T1 is sponsored by ATIS and is accredited by ANSI. This document is issued under a joint copyright by ATIS and TIA. No part of this publications may be reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of ATIS. For i

11、nformation contact ATIS at 202/628- 63 80. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE OF COPYRIGHT This document is issued under a joint copyright by the Telecommuni

12、cations Industry Association and the Alliance for Telecommunications Industry Solutions, and may not be reproduced without permission. Organizations may obtain permission to reproduce a limited number of copies by entering into a license agreement. For information, contact: Global Engineering Docume

13、nts 15 Inverness Way East Englewood, CO 801 12-5704 or call U.S.A. and Canada (1-800-854-7179) International (303) 37-7956 Or ATIS Document Center: www.atis.org Alliance for Telecommunications Industry Solutions 1200 G Street, NW Suite 500 Washington, DC 20005 (202) 628-6380 NOTICE FROM PATENT HOLDE

14、RS The users attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewith. The paten

15、t holder has, however, filed a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain a license. Details may be obtained from the Telecommunications Industry Association, Alliance for Telecommunications

16、 Industry Solutions or the American National Standards Institute. Copyright Telecommunications Industry Association 2000 All rights reserved This document is subject to change. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or ne

17、tworking permitted without license from IHS-,-,-TINEIA-J-STD-025 ; Abstract 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 This Standard defines the interfaces between a telecommunica

18、tion service provider (TSP) and a Law Enforcement Agency (LEA) to assist the LEA in conducting lawfully authorized electronic surveillance. A TSP, manufac- turer, or support service provider that is in compliance with this Standard will have a “safe harbor” under Section 107 of the Communications As

19、sistance for Law Enforcement Act (CALEA), Public Law 103-414: “a TSP shall be found to be in compliance with the assistance capability requirements under CALEA Section 103, and a manufacturer of telecommunication trans- mission or switching equipment or a provider of telecommunication support servic

20、es shall be found in compliance with CALEA Section 106.” I Abstract Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TINEIA-J-STD-025 Date Document Revision History Reason for Ch

21、ange May 2000 September 2000 I November 1997 1 Interim standard version approved for publication. I Incorporate addenda for TINEIA-J-STD-025 TINEIA-J-STD-025 Standard version approved for publica- tion. I I- I7 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

22、 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 Document Revision History II Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TINEIA-J-STD-025 1 2

23、3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 Contents Abstract i Document Revision History . . . . . . . . . . . ,. . . . . . . . ii Contents . 111 List of Tables . v111 List of Fig

24、ures ix Foreword xi Introduction . . . ., . . . . . . . . . . . . . ,. . . . . . . . . 1 1.1 General 1 1.2 Purpose 2 1.3 Scope . 2 1.4 Organization 2 References . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25、 . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Definitions and Acronyms . . . . . . . . . . . ,. . . . . . . 4 Stage 1 Description: User Perspective . 13 . . 4.1 4.2 4.3 4.4 4.5 4.6 Overview . . . , . . . . . . . . . . . . . . .

26、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Introduction . . . . . . . . . . . . . ,. . . . . . . . .13 4.2.1 Assumptions 13 4.2.2 General

27、 Background 14 4.2.3 Call Content Channels and Call Data Channels 15 Non-Call Associated Information Surveillance Service Description-Serving System IAP . Call Associated Information Surveillance Service Description-Call-Identifying Informa- tion IAP ., . . . . . . . . . . . . . ,. . . . . . . . .17

28、 Content Surveillance Service Description . . . . . . . . . . . . 18 4.5.1 Circuit IAP . 18 4.5.2 Packet Data TAP 22 Restrictions . . . . . . . . . . . . ,. . . . . . . . .26 4.6.1 Lack of CDC and CCC Synchronization . 26 4.6.2 CDC Congestion 26 4.6.3 CCC Exhaustion 26 4.6.4 CCC Congestion 26 Stage

29、2 Description: Network Perspective 27 5.1 Introduction . 27 5.2 Stage 2 Methodology 27 5.3 Network Reference Model 5.3.1 Functional Entities . 29 Access Function (AF) 29 Delivery Function (DF) . 29 Collection Function (CF) . 30 Service Provider Administration Function (SPAF) . 30 Law Enforcement Adm

30、inistration Function (LEAF) . . 30 5.3.2 Interface Reference Points . 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1.4 5.3.1.5 . 111 Contents Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TINE

31、IA-J-STD-025 5.3.2.1 Reference Point a 30 5.3.2.2 Reference Point b 30 5.3.2.3 Reference Point c 31 5.3.2.4 Reference Point d 31 5.3.2.5 Reference Point e 31 Message Descriptions . 3 1 5.4.1 Answer 32 5.4.2 CCClose 33 5.4.3 CCOpen 34 5.4.4 Change 35 5.4.5 Origination 35 5.4.6 PacketEnvelope . 37 5.4

32、 5.4.7 Redirection 38 5.4.8 Release 39 5.4.9 Servingsystem 40 5.4.10 TerminationAttempt . 41 6 Stage 3 Description: Implementation Perspective 42 6.1 6.2 6.3 6.4 6.5 6.6 Protocol Definition . 42 CDC Protocol Definition 42 6.2.1 6.2.3 CDC Syntax Definitions . 43 CDC Message Definitions 44 6.3.1 Answe

33、r Message . 44 6.3.2 CCClose Message . 44 6.3.3 CCOpen Message . 45 6.3.4 Change Message . 45 6.3.5 Origination Message . 46 6.3.6 PacketEnvelope Message 47 6.3.7 Redirection Message . 48 6.3.9 Servingsystem Message . 49 6.3.10 TerminationAttempt Message 49 CDC Parameter Definitions . 49 6.4.1 Beare

34、rcapability . 49 6.4.2 CallIdentity . 50 6.4.3 CaseIdentity 50 6.4.4 CCCIdentity 50 6.4.5 IAPSystemIdentity 5 1 6.4.6 Location 5 1 6.4.7 PartyIdentity . 5 1 6.4.8 PDUType 52 6.4.9 RedirectedFromInformation . 52 6.4.10 Timestamp 53 6.4.1 1 TransitCarrierIdentity . 53 ccc Protocols 54 6.5.1 CCC Encodi

35、ng for Circuit-Mode Services . 54 6.5.2 CCC Encoding for Packet-Mode Services . 54 LAESP Compatibility Guidelines 54 6.6.1 Guidelines For Forward Compatibility . 54 6.6.2 Guidelines For Backward Compatibility 55 6.6.2.1 Existing Messages 55 CDC Underlying Data Transmission 42 6.2.2 CDC Parameter Enc

36、oding Objectives 42 6.3.8 Release Message . 48 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 Contents IV Copyright Telecommunications Industry Association Provided by IHS under l

37、icense with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TINEIA-J-STD-025 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 Annex A A . 1 A.2

38、 A.3 A.4 AS A.6 Annex B B.l B . 2 B.3 B . 4 B . 5 B . 6 6.6.2.2 Parameters in Existing Messages 55 6.6.2.3 New Messages . 56 6.6.2.4 New Parameters . 56 6.6.2.5 New Parameter Fields 56 6.6.2.6 New Parameter Values 56 Deployment Examples . 57 Possible Network Deployment of IAPs 57 Access and Delivery

39、 Function Equipment Configuration 59 Implementation of the d-interface . 62 Implementation of the e-interface . 64 Possible CDC Protocol Stacks 66 Possible CCC Protocol Stacks 67 CCC Delivery Methods 70 Circuit-Mode vs . Packet-Mode . 70 Overview . 71 Dedicated Circuit CCC Delivery 72 B.3.1 Obtain N

40、etwork Address of Destination . 73 B.3.2 Setup CCC to Destination . 73 B.3.3 Destination Acceptance or Refusal of a CCC . 74 B.3.4 CCC Continuity Verification . 74 B.3.5 Associate Intercept Subject and Call Identity to the CCC 75 B.3.6 Call Content Transfer 75 B.3.7 Early CCC Release by the Destinat

41、ion 76 B.3.8 Disassociate CCC 76 B.3.9 Normal CCC Release by the Source . 76 Trunk Group CCC Delivery 77 B.4.1 Obtain Network Address of Destination . 78 B.4.2 Setup CCC to Destination . 78 B.4.3 Destination Acceptance or Refusal of a CCC . 79 B.4.4 CCC Continuity Verification . 82 B.4.5 Associate I

42、ntercept Subject and Call Identity to the CCC 82 B.4.6 Call Content Transfer 83 B.4.7 Early CCC Release by the Destination 83 B.4.8 Disassociate CCC 84 B.4.9 Normal CCC Release by the Source . 84 B.5.1 Obtain Network Address of Destination . 86 B.5.2 Setup CCC to Destination . 86 B.5.3 Destination A

43、cceptance or Refusal of a CCC . 87 B.5.4 CCC Continuity Verification . 87 B.5.5 Associate Intercept Subject and Call Identity to the CCC 87 B.5.6 Call Content Transfer 87 B.5.7 Early CCC Release by the Destination 87 B.5.8 Disassociate CCC 88 B.5.9 Normal CCC Release by the Source . 88 Packet Data C

44、CC Delivery . 88 B.6.1 Obtain Network Address of Destination . 89 B.6.2 Setup CCC to Destination . 89 B.6.3 Destination Acceptance or Refusal of a CCC . 89 CCC Continuity Verification . 89 Associate Intercept Subject and Call Identity to the CCC Static Directory Number CCC Delivery . 85 B.6.4 B.6.5

45、89 V Contents Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TINEIA-J-STD-025 B . 7 B.8 B . 9 B.10 B.ll B.12 B.13 Annex C c.1 c.2 c . 3 Annex D D . 1 D.2 D.3 D.4 D.5 D.6 D.7 D.

46、8 D.9 B.6.6 Call Content Transfer . 90 B.6.7 B.6.8 Disassociate CCC . 90 B.6.9 Delivery Bearer Service . 90 Separated Content Delivery . 90 Early CCC Release by the Destination . 90 Normal CCC Release by the Source . 90 Combined Content Delivery . 9 1 Signaling for Switched Delivery 92 Call Content

47、Delivery Delay 92 Call Content Distribution . 93 DTMF C-Tone Signaling Procedures 93 CDC Delivery Methods 95 Dedicated Data Circuit CDC Delivery . 95 Dedicated Data Link CDC Delivery 96 Call Data Distribution 96 Information Access Scenarios . 97 Simple Abandoned Call Attempt . 101 Partial Dial Aband

48、on 101 Pre-Answer Abandon . 102 Simple Outgoing Call . 103 Re-Origination 104 Simple Incoming Call . 105 Call Waiting and Recall . 106 D.7.1 Call Waiting and Recall with a Single Call Identity . 107 D.7.2 Call Waiting and Recall with Separate Leg Identities 108 D.7.3 Call Waiting with Talking Party

49、Disconnect . 110 D.8.1 Call Waiting with Talking Party Disconnect and a Single Call Identity 111 D.8.2 Call Waiting with Talking Party Disconnect and Separate Leg Identities . 112 D.8.3 Call Waiting with Talking Party Disconnect and Separate Calls . 113 Call Held and Retrieved . 114 Call Waiting and Recall with Separate Calls 109 D.10 Three-way Calling. Plu