G.3 Top-level LIPF provisioning logic

33.1283GPPProtocol and procedures for Lawful Interception (LI)Release 18SecurityStage 3TS

The flow-chart in figure G.3-1 shows a top-level logic within the LIPF to branch off into separate processes according to the service type defined in the present document.

Figure G.3-1: Top-level view of LIPF logic in handling the service type

Based on the LI functionality defined in the present document:

– For the service type of Data, it is assumed that the NFs in the packet core network are involved and hence, provide the IRI and CC interception.

– For the service type of Voice, it is assumed that the NFs in the IMS domain are involved and hence, provide the IRI and CC interception.

– For the service type of Messaging (that includes SMS and MMS), the NFs in the packet core network, IMS or MMS Proxy Relay are involved and hence, provide the IRI and CC interception. The interception of SMS has only the IRIs.

– For the service type of PTC, the PTC Server is involved and hence, provides the IRI and CC interception.

– For the service type of LALS, the LI-LCS Client provides the IRI interception, and the CC interception does not apply to LALS.

The UDM and HSS are also the NFs that have the IRI-POI and the provisioning of IRI-POI in UDM and HSS is independent of the service type indicated in the warrant as long as the target is not indicated as a non-local ID.