G.4 Cross reference of terms between J-STD-025‑A and 3GPP

33.1083G Security3GPPHandover interface for Lawful Interception (LI)Release 17TS

Table G-1: Cross Reference of Terms between J-STD-025‑A and 3GPP

J-STD-025‑A		3GPP LI Specifications TS 33.106 [18], TS 33.107 [19]
–	Call Content	CC	Content of Communication
CCC	Call Content Channel	–	Handover Interface port 3
CDC	Call Data Channel	–	Handover Interface port 2
CF	Collection Function	LEMF	Law Enforcement Monitoring Facility
–	Call-identifying Information	IRI	Intercept Related Information
–	Call-identifying message	–	IRI record
DF	Delivery Function	–	Delivery Function / Mediation Function
–	a-interface	–	X1_1 interface
–	b-interface	–	HI1 interface
–	c-interface	–	X1_2 and X1_3 interfaces
–	d-interface	–	X2 and X3 interfaces
–	e-interface	HI	Handover Interface (HI2 and HI3)
IAP	Intercept Access Point	ICE+INE	Intercepting Control Element + Intercepting Network Element
–	Intercept subject	–	Target
LAES	Lawful Authorized Electronic Surveillance	LI	Lawful Intercept
–	CaseIdentity	LIID	Lawful Interception IDentifier
LEAF	Law Enforcement Administration Function	ADMF	Administration Function
SPAF	Service Provider Administration Function	ADMF	Administration Function
–	SystemIdentity	NID	Network IDentifier
TSP	Telecommunication Service Provider	NO/AN/SP	Network Operator, Access Network Provider, Service Provider

Annex H (normative):
United States lawful interception

This annex shall apply equally to all 3GPP and non-3GPP access types which are connected to EPC, excluding CS domain (which is not covered by this document).

With respect to the handover interfaces they have to be capable of delivering intercepted communications and IRI information to the government in a format such that they may be transmitted by means of equipment, facilities, or services procured by the government to a location other than the premises of the carrier.

With respect to location information ‘when authorized’ means the ability to provide location information on a per-surveillance basis.

The delivery methods described in this document are optional methods and no specific method is required in the United States. For systems deployed in the U.S., only ULIC version 1, including the timestamp attribute, shall be used.

The specification of lawful intercept capabilities in this document does not imply that those services supported by these lawful intercept capabilities are covered by CALEA. Inclusion of a capability in this document does not imply that capability is required by CALEA. This document is intended to satisfy the requirements of section 107 (a) (2) of the Communications Assistance for Law Enforcement Act, Pub. L. 103-414 such that a telecommunications carrier, manufacturer, or support service provider that is in compliance with this document shall have "Safe Harbor".

In the United States, for a broadband access intercept pertaining to:

1) 3GPP GPRS/UMTS access,

a) The SGSN and the HSS shall perform interception. GGSN may optionally support interception, however, it has to support interception in the cases outlined below.

b) The GGSN shall support interception in the following cases:.

– If direct tunnel functionality as defined in TS 23.060 [42] is used in the network,

– If the network supports roaming and the communications comes into the GGSN from a SGSN (in the visited network) over a Gp interface.

c) For any other scenario where the traffic does not pass the SGSN, the GGSN shall support interception.

2) 3GPP I-WLAN access,

a) the PDG, WAG, and AAA server shall perform interception.

NOTE: WLAN Interworking specification (TS 29.234 [41]) is no longer maintained in Release 12 and onwards.

3) Access Via 3GPP EPC

a) The S-GW, MME and the HSS shall perform interception.

b) The PDN Gateway shall support interception in the following cases:

– The network supports roaming and the communications comes into the PDN Gateway from an S-GW (in the visited network) over an S8 interface.

– Non-3GPP access is used to access the EPC via the PDN Gateway

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

For systems deployed in the U.S, use ATIS-0700005 [55] for the reporting of IRI and CC interception for IMS VoIP and other Multimedia Services.

For IMS-based VoIP Dialled Digits Reporting (DDR) message definition, see ATIS-0700005 [55].

NOTE 1: The term, Dialed Digit Extraction (DDE), used in [55] is the same as Dialed Digit Reporting (DDR) in this specification.

NOTE 2: Dialled Digits are keypad digits 0, 1, 2, 3, 4, 5, 6, 7. 8, 9, *, and # entered by the target.

NOTE 3: DDR does not apply to PS domain and IMS-based multi-media services other than voice.

For systems deployed in the U.S., the network element identifier is required.

For systems deployed in the U.S., the following two records are also required for the packet domain:

1. a REPORT record shall be triggered when the 3G SGSN receives an SMS-MO communication from the target’s mobile station;

2. a REPORT record shall be triggered when the 3G SGSN receives an SMS-MT communication from the SMS-Centre destined for the target’s mobile station.

For systems deployed in the U.S., when a mobile terminal is authorized for service with another network operator or service provider, or within another service area as defined in J-STD-025- B [65], a Serving System REPORT record or a Serving Evolved Packet System REPORT Record shall be triggered.

For systems deployed in the U.S., the timestamp reported shall be coded as generalized time and provide either coordinated universal time or local time with the local time differential from coordinated universal time.

For systems deployed in the U.S., Packet Data Header Information REPORT Records shall be delivered to Law Enforcement for IRI only authorizations where the timestamps shall be coded as specified above.

Annex I (informative):
Void

Annex J (normative):
Definition of the UUS1 content associated and sub-addressing to the CC link