23.2033GPPPolicy and charging control architectureRelease 17TS
The same requirements as defined in clause 4 4 to support usage monitoring and clause 4.5 to support application detection and control applies.
S.3.1 General Requirements
The same requirements as defined in clause 4 applies with the following exception and addition:
– For Fixed devices the policy and charging control shall be possible only in non- roaming scenario.
– For Fixed Broadband Access, PCC decisions shall be based on subscription information for both fixed device and/or fixed access line.
– PCRF shall control directly the PCEF in the IP-Edge in the fixed broadband access without the mediation of the BPCF defined in TS 23.139 .
NOTE 1: In this Release of the specification, Policy and charging control for layer 2 sessions are out of the scope.
– An IP-CAN session shall be established on the IP-Edge per IPv4 address and/or IPv6 address or IPv6 prefix known in the IP-Edge.
PCC shall be supported for both the IP-CAN session established for the RG and for each IP-CAN session created for every device (i.e. fixed device or 3GPP UE) behind the RG that is visible in the IP-Edge/PCEF.
NOTE 2. In this Release the identification of end-user devices behind a RG configured in routed mode is not supported.
NOTE 3: In this Release of the specification, there is no support for IMS-based emergency services.
NOTE 4: In this Release of the specification, there is no support for traffic steering control.
S.3.2 Charging Related Requirements
The same requirements as defined in clauses 4.2.1, 4.2.2 and 4.2.2.a apply, with the exception and addition listed in the following:
– The architecture shall provide charging for traffic exchanged by fixed devices and NSWO traffic to/from 3GPP UEs in the following scenarios:
– 3GPP IP-Edge based charging with PCEF located in the fixed broadband access network;
– Traffic Detection Function (TDF)-based charging;
– AAA-based charging,
– The requirements for the AAA-based charging solution are described in clause S.8.
NOTE 1: The selection of which accounting methods enabled is based on deployment option and there is no dynamic capability negotiation.
NOTE 2: The same accounting method is applicable to all devices connected to the same fixed broadband access network.
Charging interaction per device (i.e. fixed device or 3GPP UE) is possible only when an IP-CAN session exists for the 3GPP UE or fixed device connected behind a RG.
NOTE 3: For a 3GPP UE or a fixed device behind a NATed RG it is not possible to perform charging for that specific device.
Inter operator settlements are assumed to ensure support of the case of an UE receiving NSWO over a Fixed Broadband Access (FBA), when the HPLMN and the FBA Service Provider support different charging options.
It shall be possible for the charging system to select the applicable rate based on:
– home/visited IP‑CAN;
– QoS provided for the service;
– Time of day;
– Location of the subscriber.
– Subscriber identifier.
Home/visited IP-CAN is not applicable for charging of fixed devices.
S.3.3 Policy Control Requirements
The same requirements as defined in clause 4.3 applies with the exception and addition listed below:
– The PCEF in the IP-Edge shall be able to enforce policies and to perform the appropriate mapping from QoS parameters it receives from the PCRF to Broadband Forum specific parameters.
NOTE: How the IP-Edge performs such mapping is out of 3GPP scope.
– PCC shall provide QoS control on a service data flow/detected application traffic basis, for IP traffic exchanged by fixed devices and for NSWO traffic exchange by 3GPP UEs in the fixed broadband access.
– Requirements for QoS control at IP-CAN bearer level defined in clause 22.214.171.124 are not applicable for Fixed Broadband Access.