Cisco Cisco ASR 5000
ACS Configuration Mode Commands
▀ policy-control bind-default-bearer
▄ Command Line Interface Reference, StarOS Release 18
554
policy-control bind-default-bearer
For PCEF Bearer Binding in 3G and when BCM mode is UE only, this command allows you to enable/disable binding
rules having QoS of default bearer to the default bearer and to not ignore/ignore other rules.
rules having QoS of default bearer to the default bearer and to not ignore/ignore other rules.
Product
ACS
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration
active-charging service service_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-acs)#
Syntax
[ default | no ] policy-control bind-default-bearer
default
Configures this command with its default setting.
Default: Disables only binding those rules having QoS of default bearer to the default bearer and specifies to
not ignore other rules. Rules having respective QoS will get attached to the relevant bearers. Also TFT
updates towards the UE (access side) will not be suppressed.
Default: Disables only binding those rules having QoS of default bearer to the default bearer and specifies to
not ignore other rules. Rules having respective QoS will get attached to the relevant bearers. Also TFT
updates towards the UE (access side) will not be suppressed.
no
The
no
keyword functionality is same as the default setting.
Usage
This CLI command is used to bind all the PCC dynamic or predef rules received from PCRF (Bearer Control
Mode (BCM) is UE_only) without QoS and ARP or with the same QoS and ARP as that of the default bearer,
to the default bearer. This CLI is used for UE_Only mode.
In case no QoS is specified the rule gets attached to the default bearer. Also no TFT updates will be sent
towards UE (access side). So only one default bearer will ever be created.
On receiving a PCC dynamic rule or predef rule from PCRF, having QoS/ARP other than the default bearer,
then those rules are ignored and a response indicating that the rule could not be installed, is sent.
This CLI command will not work currently for dedicated bearers (secondary PDP contexts). Secondary
bearers initiated by UE are not supported.
Releases prior to 12.2, when UE_Only BCM is received from PCRF, IMSA terminates the call for P-GW
(GnGp setup). Release 12.2 onwards, the P-GW call is not terminated so as to be in compliance with 3GPP
standard specification TS 29.212, but Traffic Flow Template (TFT) updates towards UE (access side) will be
supported.
Mode (BCM) is UE_only) without QoS and ARP or with the same QoS and ARP as that of the default bearer,
to the default bearer. This CLI is used for UE_Only mode.
In case no QoS is specified the rule gets attached to the default bearer. Also no TFT updates will be sent
towards UE (access side). So only one default bearer will ever be created.
On receiving a PCC dynamic rule or predef rule from PCRF, having QoS/ARP other than the default bearer,
then those rules are ignored and a response indicating that the rule could not be installed, is sent.
This CLI command will not work currently for dedicated bearers (secondary PDP contexts). Secondary
bearers initiated by UE are not supported.
Releases prior to 12.2, when UE_Only BCM is received from PCRF, IMSA terminates the call for P-GW
(GnGp setup). Release 12.2 onwards, the P-GW call is not terminated so as to be in compliance with 3GPP
standard specification TS 29.212, but Traffic Flow Template (TFT) updates towards UE (access side) will be
supported.