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…


7.12  Datap. 123

7.12.1  Generalp. 123

This clause provides additional details on LI architecture, requirements and functionality for data services.

7.12.2  Packet header information reportingp. 123  Generalp. 123

A warrant that does not require the interception of communication contents, may require IRI messages that have to be derived from the user plane packets. One report type that requires such a capability is the packet header information report.  Report typesp. 123

Depending on the requirements of the warrant, packet header information reporting may be done either in per-packet form, as one or more Packet Data Header Reports (PDHR), or in summary form, as one or more Packet Data Header Summary Reports (PDSR).  Implementation approachesp. 124

To support the generation of related xIRI (i.e. that requires access to the user plane packets), the present document supports two implementation approaches:
  • In approach 1, xIRI (that includes the correlation number and the target identity) is generated by the IRI-POI in the UP Entity. The IRI-POI generates the xIRI from the user plane packets and sends it to the MDF2. The MDF2 generates the IRI messages and sends them to the LEMF.
  • In approach 2, xCC is generated by the CC-POI in the UP Entity as if the warrant involves the interception of communication contents. To enable this, the CC-POI is presumed to be present and provisioned in the UP Entity even when the warrant does not require the interception of communication contents. The CC-POI generates the xCC and sends it to the MDF3. The MDF3 (based on the provisioned intercept information) does not generate and deliver the CC to the LEMF. Instead, the MDF3 forwards the xCC to the MDF2 over LI_MDF interface. The MDF2 then generates the IRI messages from xCC and delivers those IRI messages to the LEMF.
In 5GS and CUPS EPS, the POI in the UP Entity requires a trigger to enable it to detect the user plane packets. The corresponding Triggering Function (IRI-TF or CC-TF) resides in the CP Entity that has the IRI-POI for the generation of other xIRI. The trigger sent by the IRI-TF or CC-TF to the corresponding POI includes the following:
  • User plane packet detection rules.
  • Target identity.
  • Correlation information.
  • MDF2 (in approach 1) or MDF3 (in approach 2) address.

Up   Top   ToC