Cisco Cisco ASR 5000 Manual Técnico
CLI for configuring the charging action to perform DSCP marking is as follows:
Bearer Binding Support
Cisco ASR5x00 PGW supports PCEF functionality which is compliant with the 3GPP based PCC
framework based on 3GPP spec TS 23.203 & TS 29.212
framework based on 3GPP spec TS 23.203 & TS 29.212
Being a PCEF it needs to support SDF or PCC-rule level Policy and Charging enforcement, thus
supporting flow-based QOS and Charging enforcement. In addition to this, PGW also needs to
support Bearer-Binding function. Bearer-Binding is a process of binding PCC-rules to a particular
bearer. For EPS, PGW needs to support PCEF based Bearer-Binding for IPCAN Session type
3GPP EPS. In PCEF based bearer binding, PCRF is unaware of the bearers and it just provides
the PCC-rules to PCEF to bind it to the bearers. PGW (PCEF) receives the directives from PCRF
to activate/update/deactivate the PCC-rules, based on this PGW then generates requests to either
create/update/delete the EPS bearers using PGW initiated create/update/delete bearer
procedures.
supporting flow-based QOS and Charging enforcement. In addition to this, PGW also needs to
support Bearer-Binding function. Bearer-Binding is a process of binding PCC-rules to a particular
bearer. For EPS, PGW needs to support PCEF based Bearer-Binding for IPCAN Session type
3GPP EPS. In PCEF based bearer binding, PCRF is unaware of the bearers and it just provides
the PCC-rules to PCEF to bind it to the bearers. PGW (PCEF) receives the directives from PCRF
to activate/update/deactivate the PCC-rules, based on this PGW then generates requests to either
create/update/delete the EPS bearers using PGW initiated create/update/delete bearer
procedures.
At PGW, each PCC-rule to be activated is received from PCRF, with its own PCC-rule level QOS,
which includes QCI, ARP, and Data rates (only MBR if QCI is non-GBR QCI else both MBR and
GBR if QCI is GBR QCI). Each EPS bearer is uniquely identified by a combination of QCI+ARP.
During Bearer-Binding a candidate bearer to bind a rule to be identified based on whether the
bearer QCI+ARP matches with that of the PCC-rule.
which includes QCI, ARP, and Data rates (only MBR if QCI is non-GBR QCI else both MBR and
GBR if QCI is GBR QCI). Each EPS bearer is uniquely identified by a combination of QCI+ARP.
During Bearer-Binding a candidate bearer to bind a rule to be identified based on whether the
bearer QCI+ARP matches with that of the PCC-rule.
A new PCC rule is bound to a bearer by Bearer-Binding function in following manner:
If there already exists a bearer whose QCI+ARP matches with PCC-rules QCI+ARP, that
bearer is selected to bound the PCC-rule. In this case an PGW initiated Update Bearer
procedure is triggered to add the packet-filters pertaining to this PCC-rule to the bearer and if
it is a GBR bearer then the GBR and MBR data rates are updated as per the addition GBR
and MBR data rate needed for this new PCC rule. For non-GBR, no any MBR data rate
change is conveyed, as there is no per bearer level MBR data rate for non-GBR bearers.
bearer is selected to bound the PCC-rule. In this case an PGW initiated Update Bearer
procedure is triggered to add the packet-filters pertaining to this PCC-rule to the bearer and if
it is a GBR bearer then the GBR and MBR data rates are updated as per the addition GBR
and MBR data rate needed for this new PCC rule. For non-GBR, no any MBR data rate
change is conveyed, as there is no per bearer level MBR data rate for non-GBR bearers.
●
If there is no any existing bearer whose QCI+ARP matches to that of the PCC-rules, then the
PGW triggers a PGW initiated Create Bearer procedure to create a new bearer with the new
QCI+ARP combination.
PGW triggers a PGW initiated Create Bearer procedure to create a new bearer with the new
QCI+ARP combination.
●