1 / 20

CALEA and J-STD-025 revisions

CALEA and J-STD-025 revisions. CALEA. Communications Assistance for Law Enforcement Act (1994) Standardized access to telecommunications systems using new technologies. CALEA. Call-identifying information

dezso
Download Presentation

CALEA and J-STD-025 revisions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CALEAandJ-STD-025 revisions

  2. CALEA • Communications Assistance for Law Enforcement Act (1994) • Standardized access to telecommunications systems using new technologies

  3. CALEA • Call-identifying information • "dialing" or signaling which identifies the destination, direction, origin or termination of each communication generated or received by a subscriber by means of any equipment, facility, or service of a TSP • Call content • actual voice or, for data, the payload

  4. Two types of links between the accessing system and law enforcement CDC Call Data Channel CCC Call Content Channel CDC carries real-time signaling of call or other events using a standard set of messages J-STD-025

  5. J-STD-025 • Intercept information is gathered at Intercept Access Points (IAPs). Placement of IAPs within the access system is left to implementation.

  6. LAES Messages Answer Change Origination PacketEnvelope Redirection Release Serving System Termination Attempt CCOpen CCClose J-STD-025 (pub. 1997)

  7. J-STD-025A Architecture

  8. CALEA Third Report & Order • Released by FCC August 31, 1999 • Six of nine "punch list" items are required • Location is required • Whitepaper on packet data from TIA • Submitted in September, 2000 • Compliance deadline for expected new revision of standard and delivery of packet data using "interim solution": 9/30/2001

  9. J-STD-025A • Punch List ( 6 required, 3 not required ) • Content of subject-initiated conference calls • Party Hold, Join, Drop on conference calls • Subject-initiated dialing and signaling • In-band and out-of-band signaling • Timing information • Dialed Digit Extraction • Surveillance Status Message • Feature Status Message • Continuity Check Tone

  10. J-STD-025A • Incorporates six required punch list items • Sent to publication April 2000 as TIA Interim Standard/T1 Trial Use Standard • No enhancements to packet data sections • Suspended before ANSI publication due to US Court of Appeals Decision of August 15, 2000

  11. Court of Appeals Decision • Court of Appeals Decision vacated four of six required punch list features: • Post cut-through dialed digit extraction • Party Hold/Join/Drop information • Subject initiated dialing and signaling information • In-band and out-of-band signaling NOTE: It is not clear as to how the punch list items will apply to packet data

  12. Packet Data • Packet-mode: a communication where individual packets or virtual circuits of a communication within a physical circuit are switched or routed by the accessing telecommunication system. Each packet may take a different route through the intervening network (s).

  13. Packet Data • Two Solutions • PacketEnvelope message over the Call Data Channel • Send packets over Call Content Channel

  14. PacketEnvelope • The PacketEnvelope message is used to convey data packets over the CDC as they are intercepted. This solution is intended for low-volume packet communication (e.g., SMS). • Triggers: • packet-mode user communication intended for the intercept subject is detected • packet-mode user communication from the intercept subject is detected

  15. PacketEnvelope • Parameters: • CaseIdentity (M) • IAPSystemIdentity (C) • TimeStamp (M) • CallIdentity(C) • Location (C) • Packet Information (M)

  16. Packet Data over CCC • CCOpen message • The CCOpen message may be triggered when a delivery CCC is required for packet-mode data. The CCOpen is required when intercepted packets are to be delivered over a circuit or over a packet switched data network.

  17. CCOpen • Parameters • CaseIdentity (M) • IAPSystemIdentity (C) • TimeStamp (M) • Content Type (M) • PDUType (e.g., IP, PPP, X.25 LAPB) • CCCIdentity (M)

  18. CCClose • Parameters: • CaseIdentity (M) • IAPSystemIdentity (C) • Timestamp (M) • CCCIdentity (M)

  19. Packet Data Interception • Annex A.1 indicates nodes which could contain a Call-Identifying Information IAP, but does not dictate placement • Annexes A.5 and A.6 indicate possible CCC protocol stacks but leave flexibility • Annex B contains a description of CCC delivery methods, with B.6 focussing on Packet Data CCC Delivery

  20. CALEA and J-STD-025 revisions Chair: Terri L. Brooks (Nokia) Vice-Chair: Gary V. Pellegrino (CRAG) Editor: Brye Bonner (Motorola)

More Related