Cisco Cisco Packet Data Interworking Function (PDIF)
Policy Control Configuration Mode Commands
▀ diameter encode-supported-features
▄ Command Line Interface Reference, StarOS Release 18
8092
diameter encode-supported-features
This command enables/disables encoding and sending of Supported-Features AVP.
Product
GGSN
P-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control
Configuration
Configuration
configure > context context_name > ims-auth-service service_name > policy-control
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-imsa-dpca)#
Syntax
diameter encode-supported-features { adc-rules | netloc | netloc-ran-nas-cause | pending-
transactions | session-recovery | session-sync | sponsored-connectivity }
transactions | session-recovery | session-sync | sponsored-connectivity }
{ default | no } diameter encode-supported-features
adc-rules
This keyword enables configuration of Application Detection and Control (ADC) rules over Gx interface. For
ADC 6th bit of supported feature will be set. By default, this supported feature will be disabled.
ADC 6th bit of supported feature will be set. By default, this supported feature will be disabled.
Important:
ADC Rule support is a licensed-controlled feature. Contact your Cisco account representative for
detailed information on specific licensing requirements.
This keyword “
adc-rules
” will be available only when the feature-specific license is configured.
In release 18, the gateway node will use ADC functionality over Gx as defined in the Release 11 specification
of 3GPP standard. ADC extension over Gx provides the functionality to notify PCRF about the start and stop
of a specific protocol or a group of protocols, and provide the possibility to PCRF that with the knowledge of
this information, change the QoS of the user when the usage of application is started and until it is finished.
The provision of ADC information is done through the ADC rule, the action initiated by PCRF is done
through the PCC rule.
ADC rules are certain extensions to dynamic and predefined PCC rules in order to support specification,
detection and reporting of an application flow. These rules are installed (modified/removed) by PCRF via
CCA-I/CCA-U/RAR events. ADC rules can be either dynamic PCC or predefined PCC rules, and the existing
attributes of dynamic and predefined rules will be applicable.
Dynamic PCC rule contains either traffic flow filters or Application ID. When Application ID is present, the
rule is treated as ADC rule. Application ID is the name of the ruledef which is pre-defined in the boxer
configuration. This ruledef contains application filters that define the application supported by P2P protocols.
PCEF will process and install ADC rules that are received from PCRF interface, and will detect the specified
applications and report detection of application traffic to the PCRF. PCRF in turn controls the reporting of
application traffic.
of 3GPP standard. ADC extension over Gx provides the functionality to notify PCRF about the start and stop
of a specific protocol or a group of protocols, and provide the possibility to PCRF that with the knowledge of
this information, change the QoS of the user when the usage of application is started and until it is finished.
The provision of ADC information is done through the ADC rule, the action initiated by PCRF is done
through the PCC rule.
ADC rules are certain extensions to dynamic and predefined PCC rules in order to support specification,
detection and reporting of an application flow. These rules are installed (modified/removed) by PCRF via
CCA-I/CCA-U/RAR events. ADC rules can be either dynamic PCC or predefined PCC rules, and the existing
attributes of dynamic and predefined rules will be applicable.
Dynamic PCC rule contains either traffic flow filters or Application ID. When Application ID is present, the
rule is treated as ADC rule. Application ID is the name of the ruledef which is pre-defined in the boxer
configuration. This ruledef contains application filters that define the application supported by P2P protocols.
PCEF will process and install ADC rules that are received from PCRF interface, and will detect the specified
applications and report detection of application traffic to the PCRF. PCRF in turn controls the reporting of
application traffic.