Content for  TS 23.402  Word version:  18.3.0

If dynamic PCC is deployed, the procedure given in Figure 6.6.1-1 is used by the PCRF to provision rules to the Trusted non-3GPP IP access and for the Trusted non-3GPP IP access to enforce the policy by controlling the resources and configuration in the trusted non-3GPP access. The access specific procedure executed in the trusted non-3GPP access is not within the scope of this specification.

This procedure concerns both the non-roaming (as Figure 4.2.2-1) and roaming case (as Figure 4.2.3-1). In the roaming case, the vPCRF in the VPLMN forwards messages between the Trusted Non-3GPP IP Access and the hPCRF in the HPLMN. In the case of Local Breakout (as Figure 4.2.3-4), the vPCRF forwards messages sent between the PDN-GW and the hPCRF. In the non-roaming case, the vPCRF is not involved at all. The optional interaction steps between the gateways and the PCRF in the procedures only occur if dynamic policy provisioning is deployed. Otherwise policy may be statically configured with the gateway.

This clause is related to the case when network-initiated dynamic resource allocation is supported, and it is utilized for the S2c traffic flow aggregates. The procedure described in this clause may also be used subsequent to the S2c Attach procedure described in clause 6.3. In this case, the PCRF may push specific PCC rules to the PDN-GW and QoS Policy rules to the Trusted Non-3GPP Access system, in case the Access System supports PCC.

This procedure concerns both the non-roaming (as Figure 4.2.2-2) and roaming case (as Figure 4.2.3-3). In the roaming case, the vPCRF in the VPLMN forwards messages between the Trusted Non-3GPP IP Access and the hPCRF in the HPLMN. In the case of Local Breakout (as Figure 4.2.3-4), the vPCRF forwards messages sent between the PDN-GW and the hPCRF. In the non-roaming case, the vPCRF is not involved at all. Steps 1-4 are the same as in steps 1-4 in clause 6.6.1. Step 4 may be skipped in case the PCC rules at the PDN-GW are already up-to-date.