1. 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 Location Dependent Interception Joint meeting SA 3 LI & TC LI Portugal July 2004 TD08 Bernhard Spalt

2. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 2 History Requirements / Definitions CS Solution PS Solution IP / IMS Solution Hints Agenda

3. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 3 History Location Dependent Interception was fixed in SMG 10 WP D Mainly driven by Alcatel and Siemens via their customers Globalstar and Iridium Fixed in GSM 02.33 & 03.33 I.e. Solution for a cell oriented network Current specification: TS 33.106 TS 33.107

4. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 4 Requirements / Definitions Interception Area: is a subset of the Public Lands Mobile Network (PLMN) service area comprised of a set of cells which define a geographical zone Location Dependent Interception: is interception within a PLMN service area that is restricted to one or several Interception Areas (IA) Location Dependent Interception allows a PLMN to service multiple interception jurisdictions within its service area. Multiple law agencies with their own interception areas can be served by the PLMN. All the information or rules given for interception within a PLMN apply to interception within an IA when Location Dependent Interception is invoked. A target may be marked in one or more different IAs within the same PLMN. Interception is not required nor prohibited by this standard when Location Dependent Interception is active and the location of the target subscriber is not known or available.

5. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 5 Usual LI situation INE LEA Target COUNTRY A COUNTRY C COUNTRY B MD/ DF DF Delivery Function INEIntercepting Network Element LEA Law Enforcement Agency MDMediation Device HI 1 HI2 HI3 X1_1 X2 X3 INE LEA Target MD/ DF HI 1 HI2 HI3 X1_1 X2 X3

6. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 6 Location dependent interception LEA A COUNTRY A COUNTRY C COUNTRY B LEA C INE LEA B Target MD/ DF HI 1 HI2 HI3 X1_1 X2 X3 One network / operator is offering their service in several countries

7. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 7 Implementation options In case of location dependent interception the following network/national options exist: -target location versus Interception Areas (IAs) check in the MSC/VLR and Delivery Functions (DFs); -target location versus IAs check in the DFs (physical collocation of the DFs to the MSC/VLR, GMSC is required). Note:The IA is previously defined by a set of cells. From the location of the target this set of cells permits to find the relevant IA.

8. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 8 CS Solution The location dependency check occurs at the establishment of each call. Subsequent dependency checks for simultaneous calls (CH/CW/MTPY) are not required, but can be a national option. If a target is marked using an IA in the MSC/VLR, the MSC/VLR shall perform a location dependency check at call set-up. Only if the target's location matches the IA the call is intercepted. If a target is marked using an IA in the DF2, the DF2 shall perform a location dependency check at reception of the first IRI for the call. Only if the target's location matches the IA for certain LEAs the IRI is relayed to these LEAs. All subsequent IRIs for the call are sent to the same LEAs. If a target is marked using an IA in the DF3, the DF3 shall perform a location dependency check at reception of the CC. Only if the target's location matches the IA for certain LEAs the CC is relayed to these LEAs.

9. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 9 PS Solution In case of location dependent interception : -for each target, the location dependency check occurs at each packet data session establishment or release and at each cell and/or RA update to determine permanently the relevant IAs (and deduce, the possible LEAs within these IAs), -concerning the IRI: -when an IA is left, a GPRS detach event is sent when changing SGSNs or a cell and/or RA update event is sent when changing IAs inside the same SGSN to DF2P. -when a new IA is entered a cell and/or RA update event is sent to DF2P and, optionally, a Start of Interception with Active PDP Context event for each PDP context -concerning the CC, when crossing IAs, the CC is not sent anymore to the DF3P of the old IA but sent to the DF3P of the new IA.

10. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 10 IP / IMS Solution Until now nothing was fixed in the specifications! No location information is usually available at this node! Supported via the administration interface  activated in the relevant nodes

11. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 11 Hints Not applicable to LDI: Interception in the Gateway (MTC Roamers) Serving System / HLR Interception Interception of CFU in the Gateway.......................

12. © Siemens, 2004 12,302,337,422,54 12,30 5,93 1,06 1,27 8,27 SA 3 LI & TC LI Joint meeting Seite 12 Thanks ! For further details: Bernhard.spalt@siemens.com