name: LISSF
full_form: Lawful Interception State Storage Function
context: The LISSF is a function that makes it possible for other LI functions to share information with each other. There can be multiple instances of the LISSF in the network being handled by the same ADMF. The LISSF can be implemented as a separate function or within the ADMF. The LISSF may be used to transfer LI state information between LI functions. The following restrictions on the use of the LISSF shall apply: - The LISSF shall be subject to the same location, geographic, security and other physical environment constraints as the LI functions for which it is storing data. - LI state information stored in an LISSF shall only be accessible by the LI functions specifically authorised by the LICF. - Other than the time required to acquire the LI state information, the use and placement of an LISSF within the LI architecture shall not introduce additional delay. - The LISSF shall be directly under the control of the ADMF, and it shall be directly accessible and auditable by the LICF.
description: The Lawful Interception State Storage Function (LISSF) is a network function responsible for storing and sharing lawful interception state information among various LI functions within the network. It operates under the control of the Administration Function (ADMF) and is subject to specific security, location, and accessibility constraints.
explanation: The context explicitly describes the LISSF as a 'function' that enables information sharing between other Lawful Interception (LI) functions, highlighting its role in facilitating communication and data exchange within the network. This aligns with the definition of a Network Function, which includes components that perform specific tasks or operations within the telecommunications infrastructure.
section_title: 6.2.7.2	LI State Storage Function (LISSF)
biotag_Context: O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Parameter,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,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,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,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-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O