P.3 High Level Requirements

23.2033GPPPolicy and charging control architectureRelease 17TS

The same requirements as defined in clause 4 applies with the following exceptions:

– no UE initiated resource reservation procedures are supported for EPC-based Fixed Broadband Access.

– The support of traffic steering control for the traffic in the (S)Gi-LAN is only applicable to the EPC-routed traffic of Home-routed scenario.

In addition, it shall be possible to.

– perform resource reservation (e.g. admission control request to the Fixed Broadband Network) based on the bandwidth requirements and the QoS attributes of a service request for EPC-routed traffic in the Fixed Broadband network;

– provide information to identify a 3GPP UE in the Fixed Broadband Network.

– perform resource reservation (e.g. admission control request to the Fixed Broadband Network) based on the bandwidth requirements and the QoS attributes of a service request for non-seamless WLAN offloaded traffic in the Fixed Broadband network. In this case the non-seamless WLAN offloaded traffic shall be managed by PCRF as an IP-CAN session identified by one IPv4 and/or an IPv6 prefix together with UE identity information and Non-seamless WLAN offload APN. The IP‑CAN session for NSWO exists as long as UE Local IP addresses/prefix is announced to the IP network and authorized by EPC. The NSWO-APN is an APN allowing the BPCF to indicate to PCRF that for subscribers of a certain HPLMN the IP-CAN session is related to NSWO traffic.

NOTE 1: The NSWO-APN is not used for the selection of a PDN GW.

NOTE 2: Dynamic provisioning from the HPLMN of NSWO-APN to BPCF is out of the scope of this Release.

NOTE 3: The naming convention of NSWO-APN is left to operator’s implementation decision.