Cisco Cisco Packet Data Gateway (PDG)
Policy Control Configuration Mode Commands
▀ diameter update-dictionary-avps
▄ Command Line Interface Reference, StarOS Release 16
7866
applied, the Supported-Features AVP with feature bit 1 being set will be sent in the CCR-I to indicate that
3GPP Rel. 9 AVPs are also supported.
Both
3GPP Rel. 9 AVPs are also supported.
Both
default
and
no
command have the same behavior, as if the CLI command is not configured. Hence, in
the output of
show configuration verbose
command, the
default
and
no
command is shown as
no
diameter update-dictionary-avps
.
This CLI command when configured results in behavioral changes as indicated in the following table.
Possible Upgrade Scenarios
Behavior
3GPP Rel. 7 based dictionary
upgraded to 3GPP Rel. 9
For example:
upgraded to 3GPP Rel. 9
For example:
diameter dictionary dpca-
custom4
custom4
diameter update-dictionary-
avps 3gpp-r9
avps 3gpp-r9
In the CCR-I, Supported-Features AVP will be encoded with value 2 for the Feature-List
AVP.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 2
The Feature-List AVP value suggest that it is 3GPP Rel. 9 compliant. But, it is not fully
complaint to 3GPP Rel. 9.
In the current release, for this upgrade scenario (3GPP Rel. 7 to 3GPP Rel. 9), only volume
reporting related AVPs mentioned in the 3GPP Rel. 9 will be supported.
AVP.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 2
The Feature-List AVP value suggest that it is 3GPP Rel. 9 compliant. But, it is not fully
complaint to 3GPP Rel. 9.
In the current release, for this upgrade scenario (3GPP Rel. 7 to 3GPP Rel. 9), only volume
reporting related AVPs mentioned in the 3GPP Rel. 9 will be supported.
3GPP Rel. 7 based dictionary
upgraded to 3GPP Rel. 8
For example:
upgraded to 3GPP Rel. 8
For example:
diameter dictionary dpca-
custom4
custom4
diameter update-dictionary-
avps 3gpp-r8
avps 3gpp-r8
In the CCR-I, Supported-Features AVP will be encoded with value 1 for the Feature-List
AVP.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 1
The Feature-List AVP value suggest that it is 3GPP Rel. 8 compliant. But, it is not fully
complaint to 3GPP Rel. 8.
In the current release, for this upgrade scenario (3GPP Rel. 7 to 3GPP Rel. 8), none of the
features mentioned in 3GPP Rel. 8 will be supported.
AVP.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 1
The Feature-List AVP value suggest that it is 3GPP Rel. 8 compliant. But, it is not fully
complaint to 3GPP Rel. 8.
In the current release, for this upgrade scenario (3GPP Rel. 7 to 3GPP Rel. 8), none of the
features mentioned in 3GPP Rel. 8 will be supported.
3GPP Rel. 8 based dictionary
upgraded to 3GPP Rel. 9
For example:
upgraded to 3GPP Rel. 9
For example:
diameter dictionary r8-gx-
standard
standard
diameter update-dictionary-
avps 3gpp-r9
avps 3gpp-r9
In the CCR-I, value for the Feature-List AVP in the Supported-Features AVP will be 2.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 2
The Feature-List AVP value suggest that it is 3GPP Rel. 9 compliant. But, it is not fully
complaint to 3GPP Rel. 9.
Currently for this upgrade scenario (3GPP Rel. 8 to 3GPP Rel. 9), only volume reporting
related AVPs mentioned in 3GPP Rel. 9 will be supported.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 2
The Feature-List AVP value suggest that it is 3GPP Rel. 9 compliant. But, it is not fully
complaint to 3GPP Rel. 9.
Currently for this upgrade scenario (3GPP Rel. 8 to 3GPP Rel. 9), only volume reporting
related AVPs mentioned in 3GPP Rel. 9 will be supported.
3GPP Rel. 9 based dictionary
upgraded to 3GPP Rel. 10
For example:
upgraded to 3GPP Rel. 10
For example:
diameter dictionary r8-gx-
standard
standard
diameter update-dictionary-
avps 3gpp-r10
avps 3gpp-r10
In the CCR-I, value for the Feature-List AVP in the Supported-Features AVP will be 8.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 8
The Feature-List AVP value suggest that it is 3GPP Rel. 10 compliant. But, it is not fully
complaint to 3GPP Rel. 10.
[V] [M] Supported-Features:
[M] Vendor-Id: 10415
[V] [M] Feature-List-ID: 1
[V] [M] Feature-List: 8
The Feature-List AVP value suggest that it is 3GPP Rel. 10 compliant. But, it is not fully
complaint to 3GPP Rel. 10.
In 14.1 and later releases, Supported-Features AVP is extended to support 3GPP Rel. 10 in EPS 3.0 in
addition to 3GPP Rel. 8 and Rel. 9. If the
addition to 3GPP Rel. 8 and Rel. 9. If the
diameter update-dictionary-avps 3gpp-r10
command is
applied, the Supported-Features AVP with feature bit 1 being set will be sent in the CCR-I / CCA to indicate
that 3GPP Rel. 10 AVPs are also supported. The 'M' bit setting for the Feature-List AVP and Feature-List-ID
AVP must be the same as defined in 3GPP TS 29.229 and must not be affected by the 'M' bit setting of the
Supported-Features AVP.
that 3GPP Rel. 10 AVPs are also supported. The 'M' bit setting for the Feature-List AVP and Feature-List-ID
AVP must be the same as defined in 3GPP TS 29.229 and must not be affected by the 'M' bit setting of the
Supported-Features AVP.
Example