name: TF
full_form: Triggering Function
context: When the TF in an SMF in an SMF set is provisioned by the LIPF with a specific XID and access to an LISSF function, the TF shall use the LISSF to retrieve LI state information. If the implementation of the SMF set does not ensure that active SM contexts are always present in some SMF of the SMF set, when a task previously provisioned by the LIPF in the TF is deactivated, the TF shall request the records associated to the XID (received from the LIPF) from the LISSF, by performing a search as described in clause 5.10.3, using the XID as a search criteria. If no records are found, the TF may assume that no previous interception has occurred and proceed accordingly. When a TF detects that its parent SMF is retrieving state for a targetted PDU session from the UDSF, the TF shall request records associated with that PDU session from the LISSF by performing a search as described in clause 5.10.3 and using the UDSFRecordID used by the SMF as a search criteria. When a TF detects that its parent
description: The Triggering Function (TF) is a component within the Session Management Function (SMF) set, responsible for retrieving Lawful Interception (LI) state information from the LISSF function and managing tasks provisioned by the Lawful Interception Policy Function (LIPF). It plays a crucial role in ensuring that active SM contexts are present in some SMF of the SMF set and handling records associated with specific XIDs or PDU sessions.
explanation: The TF is classified as a Network Function based on its role within the SMF set, interacting with other network functions like LISSF and LIPF to manage lawful interception tasks and retrieve state information. The context highlights its responsibilities in retrieving LI state, handling records, and ensuring active SM contexts are present.
section_title: 6.2.3.10.3	Retrieving LI state
biotag_Context: O,O,B-Miscellaneous,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,B-Message,O,O,O,O,B-Network Function,O,O,B-Miscellaneous,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Miscellaneous,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,B-Message,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,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,B-Miscellaneous,I-Miscellaneous,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Connection,O