name: PFCP
full_form: Packet Forwarding Control Protocol
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 Packet Forwarding Control Protocol (PFCP) is a protocol used in the 5G system architecture for reporting user plane information exposure from the User Plane Function (UPF) to other Network Functions (NFs), such as the Session Management Function (SMF), over the N4 interface. This protocol enables the exchange of information related to user plane events, allowing NFs to subscribe to and receive notifications about specific events.
explanation: PFCP is classified as a Protocol because it defines the rules for data transmission and communication between UPF and other NFs in the 5G system architecture. It facilitates the exposure of user plane information via service-based interfaces, enabling efficient network operations and management.
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-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network,I-Network,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O