name: QBC
full_form: QoS flow Based Charging
context: QoS flow Based Charging allows the SMF to collect charging information related to data volumes per PDU session, categorized per QoS Flow. QBC doesn't support quota management. The user can be identified by SUPI. For a given PDU session, QBC shall be performed by the SMF within the same charging session used for Flow Based Charging. For the case where QBC is performed from SMF in VPLMN, Flow Based Charging is not applicable and there is no possibility to have quota management for the PDU Session. For the case where QBC is performed from SMF in HPLMN, FBC can be performed or not performed at the same time according to operator's policy. The SMF categorizes the volume within PDU session by QoS Flow identified by QoS Flow Identifier (QFI). The amount of data counted for the QoS Flow shall be the user plane payload at the UPF. Table 5.2.1.6.1 summarizes the set of default trigger conditions and their category which shall be supported by the SMF in QBC. For "immediate report" category, the
description: QoS flow Based Charging (QBC) is a procedure that allows the Session Management Function (SMF) to collect charging information related to data volumes per PDU session, categorized per QoS Flow. It enables the SMF to perform charging based on the quality of service flows within a PDU session.
explanation: The context describes QBC as a mechanism for collecting and categorizing charging information, which is a procedural aspect of network operation. The text outlines specific steps and rules for how QBC is performed, such as identifying users by SUPI, performing QBC within the same charging session as Flow Based Charging, and categorizing volume within PDU sessions by QoS Flow.
section_title: 5.2.1.6QoS flow Based Charging (QBC)
biotag_Context: B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Measurement,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Network Function,O,O,B-Technology,I-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Procedure,O,O,O,B-Network Function,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Connection,O,O,B-Measurement,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,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,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Measurement,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O