Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 33.127  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   5…   5.4…   5.6…   5.7…   6…   6.2.2…   6.2.3…   6.2.5…   6.3…   6.3.3…   6.3.4…   6.4…   7…   7.3…   7.4…   7.4.7…   7.5…   7.6…   7.7…   7.8…   7.9…   7.10…   7.11…   7.12…   7.13…   7.14…   7.15…   7.16…   8…   A…   A.2…   A.3…   A.4…   B…   D…   E… 
6.3 EPC  6.3.1 General  6.3.2 LI at the MME  6.3.2.1 Architecture  6.3.2.2 Target identities  6.3.2.3 IRI events  6.3.2.3.1 Option A  6.3.2.3.2 Option B  6.3.2.4 Common IRI parameters  6.3.2.5 Specific IRI parameters  6.3.2.5.1 Option A  6.3.2.5.2 Option B  6.3.2.6 Network topologies 
...

 

6.3  EPC  p. 57

6.3.1  General  p. 57

The present document specifies three options for EPC interception capabilities:
For implementations that include EPS/5GS interworking, Option A shall be used.
For virtualised 4G implementations from Release 15 onwards (including combined 4G / 5G scenarios), 4G shall be virtualised based on the architecture in clause 5.6. For such implementations the LI architecture for 4G / LTE shall be implemented using an ADMF as defined in the present document (including LIPF and LICF split). However, equivalent reference points as specified in TS 33.107 shall be used where appropriate (e.g. X2 is equivalent to LI_X2 in the present document and MDF is equivalent to MF/DF). Security and audit requirements as defined in clause 8 of the present document shall be applied to such 4G scenarios.
Up

6.3.2  LI at the MME  p. 58

6.3.2.1  Architecture  p. 58

In the EPC network, the MME handles the mobility management and connection management as specified in TS 23.401. The MME shall have LI capabilities to generate the target UE's network access, registration and connection management related xIRI. Extending the generic LI architecture presented in clause 5, Figure 6.3-1 below gives a reference point representation of the LI architecture with MME as a CP Network Element providing the IRI-POI functions.
Copy of original 3GPP image for 3GPP TS 33.127, Fig. 6.3-1: LI architecture for LI at MME
Figure 6.3-1: LI architecture for LI at MME
(⇒ copy of original 3GPP image)
Up
The LICF present in the ADMF receives the warrant from an LEA, derives the intercept information from the warrant and provides the same to the LIPF.
The LIPF present in the ADMF provisions the IRI-POI (over LI_X1) present in the MME and the MDF2.
The IRI-POI present in the MME detects the target UE's access and mobility related functions (network access, registration and connection management), generates and delivers the xIRI to the MDF2 over LI_X2. The MDF2 delivers the IRI messages as part of the Interception Product to the LEMF over LI_HI2.
Up

6.3.2.2  Target identities  p. 59

The LIPF provisions the IRI-POI present in the MME with the following target identities:
  • IMSI.
  • MSISDN.
  • IMEI.
The interception performed on the above three identities are mutually independent, even though, an xIRI may contain the information about the other identities when available.

6.3.2.3  IRI events  p. 59

6.3.2.3.1  Option A  p. 59
The IRI-POI present in the MME shall generate xIRI, when it detects the following specific events or information:
  • Attach.
  • Detach.
  • Tracking Area/EPS Location Update.
  • Start of interception with EPS attached UE.
  • Unsuccessful communication related attempt.
  • Identifier association.
  • Positioning info transfer.
  • Handover.
  • Trace.
  • Service accept.
The attach xIRI is generated when the IRI-POI present in an MME detects that a target UE has performed an E-UTRAN attach procedure including via a HeNB. The attach xIRI describes the type of attach performed. Unsuccessful registration shall be reported only if the target UE has been successfully authenticated.
The detach xIRI is generated when the IRI-POI present in an MME detects that a target UE has detached from the EPS including via a HeNB. The detach xIRI shall indicate whether it was a UE-initiated or a network-initiated detach.
The tracking area/EPS location update xIRI is generated each time the IRI-POI present in an MME detects that the target UE location is updated due to target UE mobility (e.g. in case of X2 based handover, S1 based handover) or when the MME observes target UE location information during some service operation (e.g., periodic Tracking Area Update, UE triggered Service Request). If the information in the MME received over S1 (TS 36.413) includes one or more cell IDs, then all cell IDs shall be reported to the LEMF whenever location reporting is triggered at the MME.
The start of interception with EPS attached UE xIRI is generated when the IRI-POI present in an MME detects that interception is activated on a target UE that is already attached to the EPS. If there are multiple PDN connections active for the target, then a start of interception with EPS attached UE xIRI is generated for each of them.
When additional warrants are activated on a target UE, MDF2 shall be able to generate and deliver the start of interception with E-UTRAN attached UE related IRI messages to the LEMF associated with the warrants without receiving the corresponding start of interception with already registered UE xIRI.
The unsuccessful communication related attempt xIRI is generated when the IRI-POI present in an MME detects that a target UE initiated communication procedure (e.g. service request, SMS) is rejected or not accepted by the MME before the proper NF handling the communication attempt itself is involved.
The identifier association xIRI is generated each time the IRI-POI in the MME detects a GUTI allocation change for an IMSI associated with the target UE.
The IRI-POI in the MME shall support per target selective activation or deactivation of reporting of only identifier association xIRI independently of activation of LI for all other events. When identifier association xIRI only reporting is activated, the IRI-POI in the MME shall also generate Tracking Area/EPS Location Update xIRI.
The positioning info transfer xIRI is generated when the IRI-POI present in the MME detects one the following events:
  • network-based or network-assisted positioning requests, responses or reports related to a target UE are being exchanged between E-SMSC and eNB via the MME.
  • UE-based or UE-assisted positioning requests, responses or reports related to a target UE are being exchanged between E-SMLC and the target UE via the MME.
The handover xIRI is generated when the IRI-POI in the MME detects that a target UE is the subject of a handover between radio access nodes in Intra EPS scenarios or scenarios when the target UE is the subject of a handover between EPS and any other RAT.
The trace xIRI is generated when the IRI-POI in the MME detects that a trace session has been initiated for a target.
The service accept xIRI is generated when the IRI-POI in the MME detects that the target UE service request has been accepted.
Up
6.3.2.3.2  Option B  p. 60
The IRI-POI present in the MME shall generate xIRI, when it detects the applicable events specified in TS 33.107.
In addition to the events specified in TS 33.107 the MME shall generate xIRI, when it detects the following additional event:
  • Identifier association.
  • Handover.
  • Trace.
  • Service accept.
The identifier association xIRI is generated each time the IRI-POI in the MME detects a GUTI allocation change for an IMSI associated with the target UE.
The IRI-POI in the MME shall support per target selective activation or deactivation of reporting of only identifier association xIRI independently of activation of LI for all other events. When identifier association xIRI only reporting is activated, the IRI-POI in the MME shall also generate Tracking Area/EPS Location Update xIRI.
The handover xIRI is generated when the IRI-POI in the MME detects that a target UE is the subject of a handover between radio access nodes in Intra EPS scenarios or scenarios when the target UE is the subject of a handover between EPS and any other RAT.
The trace xIRI is generated when the IRI-POI in the MME detects that a trace session has been initiated for a target.
The service accept xIRI is generated when the IRI-POI in the MME detects that the target UE service request has been accepted.
Up

6.3.2.4  Common IRI parameters  p. 61

The list of xIRI parameters are specified in TS 33.128. All xIRI shall include the following:
  • Target identity.
  • Time stamp.
  • Location information.
  • Correlation information.

6.3.2.5  Specific IRI parameters  p. 61

6.3.2.5.1  Option A  p. 61
The list of parameters in each xIRI are defined in TS 33.128. The following give a summary.
The attach xIRI shall include the following:
  • Attach type information.
  • Access type information.
  • HeNB information.
The detach xIRI shall include the following:
  • Detach Direction.
  • Detach type information.
  • HeNB information.
The tracking area/EPS location update xIRI shall include the following:
  • Location of the target (see clause 7.3).
  • HeNB information.
The start of interception with EPS attached UE xIRI shall include the following:
  • Attach type information.
  • Access type information.
  • PDN connection information.
The unsuccessful communication attempt xIRI shall include the following:
  • Rejected type of communication attempt.
  • Access type information.
  • Failure reason.
The identifier association xIRI shall include the following:
  • IMSI.
  • IMEI.
  • Temporary identifier association (i.e. GUTI).
  • Association change type indication.
The handover xIRI shall include the following:
  • Handover type and reason.
  • Radio related information.
  • UE capability information.
When the access type is non-3GPP, the IP address used by the UE to reach the N3A Entity shall be reported. The port shall also be reported if available.
The trace xIRI shall include the following:
  • Trace related information.
The UE policy transfer xIRI shall include the following:
  • UE policies.
The service accept xIRI shall include the following:
  • Service request related information.
  • Service accept related information.
Up
6.3.2.5.2  Option B  p. 62
The list of parameters in each xIRI are defined in TS 33.128, for events which are imported from clause 12.2.1.2 of TS 33.107.
The identifier association xIRI shall include the following:
  • IMSI.
  • IMEI.
  • Temporary identifier association (i.e. GUTI).
  • Association change type indication.
The handover xIRI shall include the following:
  • Handover type and reason.
  • Radio related information.
  • UE capability information.
When the access type is non-3GPP, the IP address used by the UE to reach the N3A Entity shall be reported. The port shall also be reported if available.
The trace xIRI shall include the following:
  • Trace related information.
The UE policy transfer xIRI shall include the following:
  • UE policies.
The service accept xIRI shall include the following:
  • Service request related information.
  • Service accept related information.
Up

6.3.2.6  Network topologies  p. 62

The MME shall provide the IRI-POI functions in the following network topology cases:
  • Non-roaming case.
  • Roaming case, in VPLMN.

Up   Top   ToC