Question: In Policy and Charging Control (PCC), how is authorized QoS per service data flow provisioned within a QoS rule?
Option 1: By including the Bearer-Identifier AVP in the QoS-Information AVP for CCA commands only.
Option 2: Through a separate provisioning procedure outside of the QoS rule provisioning, using RAR commands exclusively.
Option 3: By omitting the QoS-Rule-Definition AVP in both CCA and RAR commands for specific service data flows.
Option 4: By including the QoS-Information AVP within the QoS-Rule-Definition AVP in either CCA or RAR commands, without a Bearer-Identifier AVP.
Explanation: This is correct because authorized QoS per service data flow is provisioned as part of the broader QoS rule provisioning procedure. This involves embedding the QoS-Information AVP within the QoS-Rule-Definition AVP in either a CCA or RAR command, without including a Bearer-Identifier AVP, ensuring service data flow specificity without bearer identification. This approach supports efficient policy management in telecom networks, particularly in 4G/LTE and evolving 5G architectures where granular QoS control is crucial.