Content for  TS 23.203  Word version:  19.0.0

A "Fixed Broadband Access IP-CAN" is a fixed access broadband network that provides IP connectivity to a UE. The Fixed Broadband Access IP-CAN reuses the definition of an IP-CAN session in this specification. The AF can provide the NATed IP address and ports used by the UE (for IMS, according to TS 23.228). The Fixed Broadband Access network does not support the concept of a bearer and multiple bearers as defined in TS 23.401. However, DSCP marking provides QoS support on transport network layer so that QoS and charging policies can be applied per SDF. Case 1, no Gateway Control Session applies for Fixed Broadband Access. The procedures cover both non-roaming and roaming with access to NSWO APN for a 3GPP UE. For the roaming case with access to NSWO APN, the V-PCRF interacts with the IP-Edge PCEF and, if Sd applies, with the TDF.

The PCEF located in the IP-Edge initiates the Gx IP-CAN Session establishment as defined in clause 7.2. The session is initiated after that the IP-Edge becomes aware of an IPv4 address and/or an IPv6 prefix has been assigned to the fixed device and/or 3GPP UE. In route mode configuration with NATed RG, the session is initiated after the RG has been connected to the network and has been assigned an IPv4 address and/or IPv6 Prefix. The IPv4 address and/or IPv6 Prefix are assigned as per Broadband Forum specifications and it is out of scope of 3GPP. In bridge mode, the session is initiated after the device has been authenticated has been assigned an IPv4 address and/or IPv6 address or IPv6 Prefix by the Fixed Broadband access. Operator policies in the PCEF indicate if dynamic policy control is provided. In addition, the NSWO-APN is also configured for subscribers on a PLMN basis. The PCEF located in the IP-Edge includes in the IP-CAN Session establishment message the Subscriber-Id, NSWO-APN if available, IP-CAN type, the Default QoS if available, the PLMN id if available and the location information as defined in clause S.6.1.1.1. The IP-Edge maps the Default-Access-Profile QoS to Default-QoS as defined in clause S.5.5.1. The PCRF may provision a Default QoS or a Default QoS profile, PCC Rules to activate and Events Triggers to report.

This procedure is in accordance with clause 7.3.2 with the exceptions listed in this Annex. The UE-initiated IP-CAN session termination is not to applicable to Fixed Broadband Access. The IP-CAN session termination is triggered by PCEF when Subscriber IP session is terminated. The trigger to terminate the Subscriber IP session may be HSS/AAA request to detach the UE or may be Broadband Forum specific (e.g. RG switch off, loss of transmission, IP address lease expiration PPPoE session termination, etc) and out of the scope of 3GPP. In routed mode configuration with NAT this procedure is applicable only when IP session from RG is terminated, e.g. when RG switches off or when public IP address assigned to the RG is released, etc.

This procedure is in accordance with clause 7.5 when the UE's (i.e. RG, fixed device or 3GPP UE) profile changes.

PCRF discovery and selection follows the principles defined in clause 7.6 with the following modification:

• The Subscriber ID specified in clause S.5.1.2 is used as user identity.
• For a 3GPP UE, the NSWO-APN is also available.
• The IPv6 address may be included in the IP-CAN session establishment in the case of bridge-mode RG.

To transport charging information about 3GPP UE, the Gza reference point is located between Accounting Interworking function in the BBF defined network and the 3GPP offline charging system OFCS located in the VPLMN (roaming scenario) or in the HPLMN (non-roaming scenario). To transport charging information about fixed devices, the Gza reference point is located between the Accounting Interworking function in the BBF defined network and the 3GPP offline charging system located in the HPLMN (only non-roaming scenario).

The Gya reference point is located between the Accounting Interworking function in the BBF defined Access Network and the 3GPP online charging system OCS located in the HPLMN and it transports charging information for 3GPP UE. The Gya reference point is located between the Accounting Interworking function in the BBF defined Access Network and the 3GPP online charging system located in the HPLMN and it transports charging information for fixed device.

This reference point is defined in BBF TR-300 [37].

The charging support for NSWO traffic for 3GPP UE and fixed devices can be provided when the BBF network reports per-user accounting data via B and Gya/Gza reference points. Offline and online charging may be supported by the 3GPP and BBF domain. In this Release, in case of AAA-based charging, the Online charging is supported based on existing capability supported by B reference point and IP-Edge with limitation based on AAA RADIUS/Diameter accounting in the BBF network (e.g. BNG capability, usage of RADIUS over B reference point). For RG in routed mode configuration with NAT, the single devices (i.e. fixed device and 3GPP UE) connected behind a RG can not be recognised, so the accounting is performed only for the RG. In case of RG bridge mode configuration and in routed mode configuration without NAT the AAA based charging is performed per single devices having a Subscriber IP session. In order to allow performing charging for fixed devices, the following assumptions are made about functionality in the Fixed Broadband Network:

• The BBF network is able to collect per user accounting data for fixed devices and periodically report this data via the B reference point.

The Accounting Interworking Function that performs translation of the accounting signalling and parameters that are understood by the IP-Edge into the credit management signalling and parameters that are understood by the OCS and the OFCS is defined in BBF TR-300 [37].