The reference architecture described in clause 5.1 and shown in Figure S.4.1.2-1 and Figure S.4.1.3-1 applies with the exception and addition listed in the following:

• PCEF resides in the IP-Edge in the Broadband Forum access network;
• Gxx reference point is not used.

This reference point corresponds to the Gx which resides between the PCEF in the IP-Edge and the PCRF. The same functionality as defined in clause 5.2.2 with the following exceptions:

• No provisioning of IP flow mobility routing information from PCEF to PCRF is performed.
• Negotiation of IP-CAN bearer establishment mode (UE-only or UE/NW) does not apply.

In addition, for the purpose of convergence between 3GPP access and Broadband Forum access network, the Gx reference point enables the transfer of PCC rules for an IP-CAN session that exists in the PCEF for a fixed device or for a 3GPP UE.

For the purpose of policy and charging control convergence between 3GPP and Broadband Forum access network, the Sp reference point allows the PCRF to request subscription information from the SPR based on a subscriber ID that is defined in clause S.5.2.1. When the subscriber Id is an IMSI, the PDN identifier is the NSWO-APN. When the subscriber Id is used to identify a fixed device no PDN identifier is applicable.

For the purpose of convergence between 3GPP access and Broadband Forum access network, the Ud reference point provides the same functionality as the Sp reference point described in clause S.4.2.2.

These reference points provide the same functionality as defined in the clauses 5.2.4 and 5.2.5 respectively. For the purpose of convergence between 3GPP access and BBF access network, the functions of credit management and reporting is defined in clause S.5.1.6. The Gz and Gy interfaces are specified in TS 32.240 and the functionalities required across the Gz and Gy reference point are defined in TS 32.251.

These reference points provide the same functionality as defined in the clause 5.2.10 and 5.2.11 respectively. In addition for the purpose of convergence between 3GPP and BBF access network, the functions of credit management and reporting are defined in clause S.5.1.6. The Gzn and Gyn interfaces are specified in TS 32.240 and the functionalities required across the Gzn and Gyn reference point are defined in TS 32.251.

For the purpose of convergence between 3GPP and Broadband Forum access network, the Sd reference point allows PCRF to have dynamic control over the application detection and control behaviour at a TDF for a fixed device or for a 3GPP UE. The Sd reference point enables the signalling of ADC decision, which governs the ADC behaviour. The Sd reference point provides the same functionality as the Sd described in clause 5.2.8.

For routed mode RG with NAT, one IP-CAN session shall be established for each corresponding Subscriber IP session on the IP-Edge for the IPv4 address and/or IPv6 address or IPv6 prefix assigned to the RG. In case of routed mode RG when the PPP pass-through feature is enabled (see requirement R-10 in TR 124 Issue 3 [34b]) an IP-CAN session shall be established for the each single fixed device starting the PPP session. In this case the 3GPP UE does not have Subscriber IP session in IP-Edge. For bridged mode RG, one IP-CAN session shall be established for each corresponding Subscriber IP session on the IP-Edge for each IPv4 address and/or IPv6 address or IPv6 prefix assigned to the fixed device or 3GPP UE which established a Subscriber IP session in fixed broadband network. For routed mode RG with IPv6 when stateless IPv6 address autoconfiguration is used by the end-device behind the RG, one IP-CAN session shall be established for each corresponding Subscriber IP session on the IP-Edge for the IPv6 prefix assigned to the RG. When stateful IPv6 address configuration is used by the end-devices, one IP-CAN session may be established for each end-device. For routed mode RG, the successful completion of 3GPP-based access authentication and assignment of IP address to the 3GPP UE shall not result in any IP-CAN session establishment if the IP address assignment does not result in a new Subscriber IP Session in the IP-Edge. In this case the pre-existent IP-CAN session for the RG is used. A device connected to the RG (e.g. VoIP phones) may also initiate a Subscriber IP session when the RG is configured in bridge mode or when the PPP pass-through feature is enabled on the Routing RG (see requirement R-10 in TR 124 Issue 3 [34b]).

The Subscriber ID represents the identity of the User. For the 3GPP UE the Subscriber ID is the IMSI. The Subscriber ID used by fixed device at establishment of Subscriber IP session in fixed broadband access network can be the Access Line Identifier (physical and logical circuit ID) or the username, for example when the Subscriber IP session is a PPP Session. For the RG and fixed device based on Broadband Forum specification, the Subscriber ID is defined in Broadband Forum WT 134 [31] specification.

The fixed broadband access network in the convergent scenario supports the Event triggering mechanisms described in clause 6.1.4. The event triggers applicable are listed in the following:

For the purpose of credit management of an IP-CAN session for a fixed devices or a 3GPP UE using NSWO, the description in clause 6.1.3 applies with the following exceptions: the subscription identity is provided by PCEF or TDF to the OCS as defined in clause S.5.1.2 and the applicable credit-reauthorization triggers are defined in the Table S.5.1.6-1:

The definition of PCC rule and PCC Rule operations in clauses 6.3.1 and 6.3.2 are applicable, except:

• PS to CS session continuity;
• User Location Report.

Table 6.4 applies with the following exceptions:

• Authorized QoS per bearer and authorized MBR per QCI are not applicable for Fixed Broadband Access.
• Charging characteristics profile for 3GPP UE is not available at the PCEF/IP-Edge.
• No Charging Characteristics profile is defined for fixed devices.

The BBF AAA may provide a default Access Profile QoS for the IP-CAN session that may contain QoS information. The PCRF may provide dynamically the default QoS for the IP-CAN session to the PCEF over Gx or alternatively may provide a default QoS profile name for those cases when the default QoS profile is provisioned in the IP-Edge/PCEF. The PCEF enforces the default QoS or the default QoS profile for the IP-CAN session provisions over Gx. The PCEF does not enforce the default Access Profile QoS provided by BBF AAA for the IP-CAN session if PCRF is deployed. The default QoS consists of a QCI and MBR. The IP-Edge/PCEF shall be able to convert default QoS into Fixed Broadband Access QoS attribute values. In the IP-Edge, the QCI and optionally the ARP priority level is used to determine the DSCP code value or other transport specific information element and the MBR is used for bandwidth limitation for the DSCP code value. The PCEF/IP-Edge shall enforce first the QoS for the packets that matches a service data flow template in an installed PCC Rule for which specific QoS enforcement actions are provided then the IP-Edge/PCEF shall enforce the default QoS for all downlink and uplink traffic for the IP-CAN session.

The PCRF functionality defined in clause 6.2.1.0 shall apply, with the following exceptions:

• No negotiation of IP-CAN bearer establishment mode applies.
• No subscription to changes of IP-CAN type, RAT type or Access Network Information applies to the PCEF.
• No event triggers that the TDF can subscribe to need to be monitored by the PCRF.
• Usage Monitoring Control as defined in clause 6.6 applies with the following exceptions:
  • In the routed RG with NAT mode, the IP-CAN session is per RG in the PCEF/IP-Edge, the PCRF retrieves the usage monitoring related information from the SPR using the subscriber-id provided over Gx. The PCRF decides how to allocate a usage threshold to each existing IP-CAN session and/or MK.
  • In the bridge RG mode and in routed RG mode without NAT there may be a separate fixed subscriber session (i.e. IP-CAN session) for the each device behind the RG. The PCRF retrieves usage monitoring related information from the SPR using the subscriber-id and, if the request is for a 3GPP UE, the NSWO APN provided over Gx. The PCRF decides how to allocate a usage threshold to each existing IP-CAN session and/or Monitoring Key.

The PCC requirements for the PCEF is located in the Fixed Broadband Access are defined in TR-300 [37]. The PCEF performs the following Fixed Broadband specific functions: In addition, the following functions are not supported:

• No UE and/or NW initiated bearer procedures and no enforcement of the authorized QoS for an IP-CAN bearer is supported for Fixed Broadband Access.

The AF functionality defined in clause 6.2.3 shall apply, except for the following functionality:

• No subscription to changes of IP-CAN type, RAT type or Access Network Information applies.

The SPR functionality defined in clause 6.2.4 shall apply. For Fixed Broadband Access the SPR may provide the subscription profile information per subscriber and PDN in case of a 3GPP UE or per subscriber in case of a fixed device or RG:

• Subscriber Identifier in the form of an IMSI, MSISDN for a 3GPP UE or in the form of a user-name or Access Line Identifier (physical and logical circuit ID) for fixed device or RG;
• A PDN ID in the form of the NSWO-APN.

The OCS functionality defined in clause 6.2.5 shall apply. For Fixed Broadband Access the PCEF provides the Subscriber Identifier that may be e.g. IMSI for a 3GPP UE or a user name or Access line identifier for a fixed devices or RG to the OCS. The PCEF or TDF also sends Access line id (physical and logical circuit ID) to the OCS when the subscriber ID identifies a 3GPP UE or a fixed device behind the RG.

The OCS functionality defined in clause 6.2.6 shall apply. For Fixed Broadband Access the PCEF provides the Subscriber Identifier that may be e.g. IMSI for a 3GPP UE or a user name or Access line identifier for a fixed devices or RG to the OFCS. The PCEF or TDF also sends Access line id (physical and logical circuit ID) to the OFCS when the subscriber ID identifies a 3GPP UE or a fixed device behind the RG.

The SPR data listed in clause 6.2.3 are stored in the UDR, the subscriber identifier and the PDN ID defined in S.6.1.4 applies.

The TDF functionality defined in clause 6.2.9 shall apply. For Fixed Broadband Access, the TDF does not subscribe to event triggers indication from the PCRF at any IP-CAN session procedure.