Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 33.107  Word version:  16.0.0

Top   Top   Up   Prev   Next
0…   4   5…   5A…   6…   7…   7A…   8…   9…   10…   11…   12…   12.2…   12.3…   12.4…   12.5…   13…   14…   15…   16…   17…   18…   19…   20…   21…   22…   23…   A…   B…   C…   D…   E…   F…   G…   H…   I…   J…   L…

 

13  Lawful Interception for 3GPP H(e)NBs |R12|

13.0  General

Home Node B (HNB) and Home enhanced Node B (HeNB) are jointly referred to as H(e)NB as defined in TS 22.220. As identified in TS 33.106, lawful interception for 3GPP H(e)NBs can be based on three different targets: a target accessing a H(e)NB, a target CSG of a H(e)NB, and a target H(e)NB.
LI for a target CSG is FFS.
LI for a target H(e)NB is FFS.
LI for Local IP Access (LIPA) via a H(e)NB is FFS.
Up

13.1  Provision of Intercepted Content of Communications for 3GPP H(e)NBsWord‑p. 170
The access method for the delivery of intercepted content of communications (CC) is based on duplication of packets without modification.
See clause 13.4 for UMTS HNB specifics and 13.5 for HeNB specifics.

13.2  Provision of Intercept Related Information for 3GPP H(e)NBs

13.2.1  X2-interface

The following information needs to be transferred to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI, IMEI, MSISDN, ME Id);
  • events and associated parameters as defined in sections 13.4.3 may be provided;
  • the H(e)NB location (if available);
  • date/time of H(e)NB location (if H(e)NB location provided);
  • H(e)NB ID.
H(e)NB location information needs to be transferred from the location verifying nodes per TS 33.320to the DF2 in order to allow the DF2 to perform its functionality. The manner that the location verifying node provides the DF2 with the H(e)NB location is outside the scope of this document.
The IRI should be sent to DF2 using a reliable transport mechanism.
Up

13.3  3GPP H(e)NB LI Events and Event Information

For a target UE that is attached to any H(e)NB, LI events and messages for 3GPP H(e)NBs defined in this clause shall be reported in addition to the LI events and messages defined in other clauses of this document. H(e)NB LI events and event information are included in 13.4 for UMTS HNBs and 13.5 for HeNBs.
A set of possible elements as shown below is used to generate the events. Information associated with the events is transmitted from the IRI ICES to DF2.
Element
Definition/Usage

Cause
Reason for an error or an action
Context-Id
Unique identifier for a UE used by the HNB and HNB GW.
CSG Identity
Uniquely identifies a CSG within one PLMN. Note: Open H(e)NBs do not have associated CSGs.
CSG List
Identifies the membership of a given CSG (i.e., CSG Identities and associated expiration data for the UEs).
Destination cell ID
Resultant cell ID after handover (HNB ID or PLMN cell ID)
Event type
Description which type of event is delivered
Event date
Date of the event generation
Event time
Time of the event generation.
Handover Direction
Identifies if the handover is inbound (from macro network to H(e)NB), outbound (from H(e)NB to macro network) or intra-H(e)NB (between H(e)NBs).
H(e)NB Identity
Uniquely identifies a H(e)NB (i.e., H(e)NB equipment ID and H(e)NB name)
H(e)NB IP Address
Reports the location of the H(e)NB used during location verification..
H(e)NB Location
When authorized, reports the location of the H(e)NB used during location verification prior to H(e)NB activation.
H(e)NB Time of Location
Date/Time of H(e)NB location. The time when location was obtained by the location source node.
IAs
The observed Interception Areas
Initiator
The initiator of an action (e.g., network or specific network entity, target, associate)
ISP Operator Identity
Identifies the ISP through which the H(e)NB is connected to the SeGW
Network Identifier
Unique identifier for the operator and the element carrying out the LI operations
Observed MSISDN
MSISDN of the target.
Observed IMSI
IMSI of the target.
Observed IMEI
IMEI of the target.
Observed ME Id
ME Id of the target; when it coincides with the IMEI, it shall be checked for each activation over the radio interface
Security Gateway IP Address
The IP Address of the Security Gateway used by the H(e)NB to terminate the tunnel from the H(e)NB
Source Cell ID
Original cell ID prior to handover (HNB ID or PLMN cell ID)
Tunnel Protocol
The tunnel protocol used between the H(e)NB and the SeGW

Up

13.4  UMTS Home Node B (HNB)Word‑p. 171

13.4.0  General

Figures 13-1 shows the reference architectures upon which Lawful Interception for 3GPP HNBs is based.
[not reproduced yet]
Figure 13-1: 3GPP UMTS HNB Architecture Basis for Lawful Interception
Up

13.4.1  Intercepted Content of Communications for 3GPP UMTS HNBsWord‑p. 172
Editor's note: This section is a place holder for the scenarios where the target of interception is either a CSG or a HNB.

13.4.2  Intercept Related Information

13.4.2.0  General

Figures 13-2 show the transfer of intercept related information to the DF2.
[not reproduced yet]
Figure 13-2: Provision of Intercept Related Information for 3GPP UMTS HNB
Up

13.4.2.1  X2-interface

The following information needs to be transferred from the HNB GW to the DF2 in order to allow a DF2 to perform its functionality:
  • target identity (IMSI, IMEI, MSISDN, ME Id);
  • events and associated parameters as defined in section 13.4.3 may be provided;
  • the HNB location (if available);
  • date/time of HNB location (if HNB location provided);
  • HNB Identity.
HNB location information needs to be transferred from the location verifying node to the DF2 in order to allow the DF2 to perform its functionality.
The IRI should be sent to DF2 using a reliable transport mechanism.
Up

13.4.3  3GPP UMTS HNB LI Events and Event InformationWord‑p. 173
The following events are applicable at the HNB GW:
  • Target UE Registration to HNB;
  • Target UE De-Registration from HNB;
  • Start of Interception with HNB attached UE;
  • Target UE HNB Handover.
A set of possible elements used to generate the events is found in clause 13.3 in Table 13. Information associated with the events is transmitted from the HNB GW to DF2.

13.4.4  Structure of HNB Events

13.4.4.1  Target UE Registration to HNB

This event reports when a target UE is attempting to register to any HNB. This event is generated when
  • a HNB GW sends a UE REGISTRATION ACCEPT message towards a target UE, or
  • a HNB GW sends a UE REGISTRATION REJECT message towards a target UE, or
  • a HNB GW receives an SCCP Connection Confirm (CC) or Connection Refused (CREF) messages from the Core Network
The elements, shown in Table 13a, will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed ME Id
Event Type
Event Time
Event Date
Network Identifier
Context-ID (for successful connection)
H(e)NB Identity
H(e)NB Location
H(e)NB Time of Location
H(e)NB IP Address
Security Gateway IP address
Tunnel Protocol
ISP Operator Identity
Cause (of failed connection, e.g., "Refusal Cause" of SCCP CREF)
CSG Identity (if closed/hybrid HNB)
CSG List (if closed/hybrid HNB) - See Note 1
IAs (if applicable)

Up

13.4.4.2  Target UE De-Registration from HNBWord‑p. 174
This event reports a when a target UE is de-registered to any HNB. This event is generated when
  • a HNB GW receives a UE DE-REGISTER message from the HNB, or
  • a HNB GW receives a RANAP Release Iu Connection Command message from the Core Network
The elements, shown in Table 13b, will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed ME Id
CSG Identity (if closed or hybrid H(e)NB)
Event Type
Event Time
Event Date
Network Identifier
H(e)NB Identity
H(e)NB Location
H(e)NB Time of Location
Initiator (i.e., HNB or Network)
Cause (of de-registration action, if known)
IAs (if applicable)

Up

13.4.4.3  Start of Intercept with HNB attached UE

This event will be generated if interception for a target UE is started when the target UE has already registered and is receiving service from a HNB. The elements, shown in Table 13c, will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed ME Id
H(e)NB Identity
CGS Identity (if closed or hybrid H(e)NB)
Event Time
Event Date
Network Identifier
H(e)NB IP Address
Security Gateway IP address
Tunnel Protocol
ISP Operator Identity
CSG List (if closed or hybrid HNB) - See Note 1
H(e)NB Location
H(e)NB Time of Location
IAs (if applicable)

Up

13.4.4.4  Target UE HNB Handover

This event reports a when a registered target UE moves from a cell on the serving PLMN to a HNB, from a HNB to a cell on the serving PLMN, or from a HNB to another HNB. This event is generated when
  • a HNB GW receives an inbound UE relocation trigger (e.g., RANAP Relocation Request message from the Core Network), or
  • a HNB GW receives a HNBAP: UE RELOCATION COMPLETE message from the Destination HNB (i.e., the "Target HNB" per TS 25.467) , or
  • a HNB GW acts as a Iurh proxy and sends a RADIO LINK RESTORE INDICATION message from the "Drift HNB" to the "Serving HNB" per TS 25.467) (i.e., a target UE is involved in a soft handover between HNBs)
The elements, shown in Table 13d, will be delivered to the DF2, if available.
Information Element

Observed MSISDN
Observed IMSI
Observed IMEI
Observed ME Id
Event Type
Event Time
Event Date
Network Identifier
Context-ID (for successful connection)
Cause (of failed connection, e.g., "Refusal Cause" of SCCP CREF)
CSG Identity (if closed/hybrid HNB)
CSG List (if closed/hybrid HNB) - See Note 1
Handover Direction
Source cell ID (HNB ID or PLMN cell ID)
Destination cell ID (HNB ID or PLMN cell ID)
IAs (if applicable)

Up

13.5  Home enhanced Node B (HeNB)Word‑p. 175
Figure 13-3 show the reference architectures upon which Lawful Interception for 3GPP HeNBs is based. Per TS 36.300, HeNB GW is optional.
[not reproduced yet]
Figure 13-3: 3GPP HeNBs Architecture Basis for Lawful Interception
Up
In the case where the UE is the target of intercept, LI functionality is specified in clause 12.


Up   Top   ToC