For EPC based Fixed Broadband Access Interworking with EPC-routed traffic the credit management, reporting, usage monitoring, termination actions, service data flow prioritization and standardized QoS characteristics as defined in clause 6.1
For non-seamless WLAN offloaded traffic service data flow prioritization as defined in clause 6.1
applies. For scenario with TDF, usage monitoring as defined in clause 6.1
applies. For NSWO traffic in other scenarios, without TDF, usage monitoring is out of scope of this specification. For all scenarios, credit management, termination actions and reporting for NSWO traffic are out of scope of this specification.
The purpose of policy interworking via S9a for non-seamless WLAN offloaded traffic (PCC Rules provisioned for the UE local IP address) is to enable policy control in the BBF domain in two different ways:
Gate enforcement. The BPCF is expected to provide information over R interface to control whether a service data flow, which is subject to policy control, pass through the BNG if and only if the corresponding gate is open.
QoS enforcement: The BPCF is expected to provide information over R interface to control the authorized QoS of a service data flow according to the QoS information received over S9a interface.
The complete specification of the BPCF is defined in BBF TR-134  and BBF TR-203  and BBF TR-291  and it is out of the scope of 3GPP.
The information contained in a PCC Rule generated by the PCRF for NSWO traffic includes Service Data Flow Detection and Policy Control information elements specified in Table 6.3
. The PCC rules for NSWO traffic do not include the Charging and Usage Monitoring Control elements specified in Table 6.3
For Fixed Broadband Access the event triggers in Table P.5.1-1
shall apply in addition to the ones in Table 6.2