name: SBI
full_form: Service-Based Interface
context: As depicted in Figure 4.2.16-1, the 5G System architecture allows user plane information exposure to some NFs via service-based interface in UPF. Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface NOTE 1: In this Release of the specification, only NWDAF/DCCF/MFAF, NEF/AF and TSNAF/TSCTSF are considered as the receiver of the UPF event notifications. NOTE 2: UPF information exposure is not restricted to SBI interface, i.e. reporting via PFCP over N4 to SMF is still applicable. Not all events can be subscribed to UPF directly. The details and constraints for the subscription to UPF event exposure service (i.e. direct vs. indirect) and the information exposed to certain NFs by UPF, as well as the information contained in the event notifications, are defined in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ]  [3] and clause 5.8.2.17.
description: The Service-Based Interface (SBI) is a standardized interface within the 5G system architecture that enables user plane information exposure to certain Network Functions (NFs) via the User Plane Function (UPF). This interface allows for the exchange of specific event notifications between UPF and NFs such as NWDAF/DCCF/MFAF, NEF/AF, and TSNAF/TSCTSF, facilitating efficient data handling and management within the network.
explanation: SBI is classified as an Interface because it defines a standardized communication path for user plane information exchange between UPF and specific NFs in the 5G system architecture. This aligns with the context provided from 3GPP TS 23.501, highlighting its role in supporting service-based interactions within the network.
section_title: 4.2.16 Architecture to support User Plane Information Exposure via a service-based interface
biotag_Context: O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,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,B-Interface,O,O,O,O,B-Protocol,O,B-Interface,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,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O
biotag_Description: O,B-Interface,I-Interface,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Network,I-Network,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O