name: SX3LIF
full_form: Split X3 LI Interworking Function
context: HeNB location and HeNB IP Address is outside the scope of this document. Additional information on HeNB interception is found in Clause 13. Figure 12.1.4 depicts the LI configuration for SGW and PGW with PLMN implementing CUPS (see TS 23.214 [75]). This is described in clause 12.9. The Sxa' and SXb' are the LI specific instances of Sxa and Sxb reference points. The X2 reference point support at SX3LIF is required only if the first option described in (sub) clauses 12.9.4.1 and 12.9.4.2 are used to generate the IRI events that require access to the user plane packets (e.g. packet data header information). The IRI events generated by the SX3LIF are therefore limited to the IRI events that require access to user plane packets. The administrative information passed onto the SX3LIF is to provide the DF2 and DF3 addresses to enable SX3LIF to deliver those IRI events to the DF2, and the CC to the DF3. The target identities for 3GPP HeNB interception can be IMSI, MSISDN, IMEI, or ME Id. Use
description: The Split X3 LI Interworking Function (SX3LIF) is a network function responsible for interworking between different Lawful Intercept (LI) functions in the Evolved Packet System (EPS). It plays a crucial role in generating IRI events that require access to user plane packets and delivering them to the designated authorities.
explanation: The context explicitly mentions SX3LIF as an entity involved in LI functional architecture for EPS, handling specific instances of reference points (Sxa' and Sxb'), and interacting with other network components like SGW and PGW. This indicates its role as a Network Function within the telecommunications infrastructure.
section_title: 12.1	LI functional architecture for EPS
biotag_Context: B-Network Function,O,O,B-Network Function,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Network Function,O,B-Network Function,O,B-Network,O,B-Technology,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Network Function,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Message,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Organization,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O