F.3 Binding Mechanisms

29.2133GPPPolicy and charging control signalling flows and Quality of Service (QoS) parameter mappingRelease 17TS

F.3.1 NSWO traffic

The binding mechanism in clause 5 applies, except that the QoS rule generation as described in clause 5.4 and the bearer binding as described in clause 5.4 do not apply since the Fixed Broadband Access network does not support the concept of a bearer and multiple bearers as defined in 3GPP network.

The following exceptions or modifications in PCC rule authorization also apply:

– The PCRF does not authorize traffic mapping information from the UE.

– The PCEF in the IP Edge would map the received QoS information over Gx into the relevant data as specified in Broadband Forum.

– MPS, RLOS and emergency services are not supported.

– BCM concept is not applied.

F.3.2 Traffic from fixed devices

The binding mechanism as described in Annex F.3.1 applies to the scenario of traffic from fixed devices with the following exceptions or modifications:

– S9 reference point is not applicable.

– The Subscriber Identifier used by fixed device at establishment of Subscriber IP session in Fixed Broadband Access network can be the Access Line Identifier (Physical-Access-ID AVP and Logical-Access-ID AVP) or the username (Subscription-Id AVP), for example when the Subscriber IP session is a PPP Session.

NOTE: In case the Subscriber Identifier in the IP-CAN and the application level identity for the fixed device are of different kinds, the PCRF needs to map between them. Such mapping is not subject to specification within this TS.