для Cisco Cisco Packet Data Gateway (PDG)
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters
and/or fields in new or modified schema and/or show command output. For details, refer to the Statistics and
Counters Reference for this release.
and/or fields in new or modified schema and/or show command output. For details, refer to the Statistics and
Counters Reference for this release.
3GPP Rel.9 Compliance for Flow-Description AVP
CSCun50355 - PGW: Gx Rel10 Flow Direction AVP and GTPv2 TFT mismatch
Applicable Products: GGSN, P-GW, SAEGW
Feature Changes
Currently, PCEF is 3GPP Rel. 8 compliant for IPFilterRule in Flow-Description AVP. When PCRF sends the
CCA-U/RAR with Flow-Description in Rel. 9 format during a network-initiated dedicated bearer creation or
modification, PCEF was misinterpreting the source and destination IP address, resulting in sending a wrong
TFT to UE.
CCA-U/RAR with Flow-Description in Rel. 9 format during a network-initiated dedicated bearer creation or
modification, PCEF was misinterpreting the source and destination IP address, resulting in sending a wrong
TFT to UE.
To make the PCEF 3GPP Rel. 9 compliant for Flow-Description AVP, the following changes are implemented:
• Interpretation of the source and destination IP address in IPFilterRule in Flow-Description AVP is
changed to maintain 3GPP Rel.9 compliancy. That is, when a Rel. 9 Flow-Description for UPLINK is
received during a network-initiated bearer creation or modification, the source IP address is interpreted
as remote and the destination as local IP address.
received during a network-initiated bearer creation or modification, the source IP address is interpreted
as remote and the destination as local IP address.
• Traffic flow direction is interpreted from a new Diameter AVP "Flow-Direction". This new AVP indicates
the direction/directions that a filter is applicable, downlink only, uplink only or both downlink and uplink
(bidirectional).
(bidirectional).
Backward compatibility is maintained, i.e. both Rel. 8 (permit in/out) and Rel. 9 (permit out with flow-direction)
formats are accepted by PCEF.
formats are accepted by PCEF.
Per the 3GPP Rel. 8 standards, during a network-initiated bearer creation or modification, the IPFilterRule in
Flow-Description is sent as "permit in" for UPLINK and "permit out" for DOWNLINK direction. From 3GPP
Rel. 9 onwards, the Flow-Description AVP within the Flow-Information AVP will have only "permit out"
and the traffic flow direction is indicated through Flow-Direction AVP. In 3GPP Rel. 9 format, both UPLINK
and DOWNLINK are sent as "permit out" and hence the usage of "permit in" is deprecated.
Flow-Description is sent as "permit in" for UPLINK and "permit out" for DOWNLINK direction. From 3GPP
Rel. 9 onwards, the Flow-Description AVP within the Flow-Information AVP will have only "permit out"
and the traffic flow direction is indicated through Flow-Direction AVP. In 3GPP Rel. 9 format, both UPLINK
and DOWNLINK are sent as "permit out" and hence the usage of "permit in" is deprecated.
This behavior is applicable for 3GPP Rel. 9 compliant PCEF and PCRF only when the supported feature
negotiated in CCA-I is rel. 9 or above through the diameter update-dictionary-avps { 3gpp-r9 | 3gpp-r10
} CLI command.
negotiated in CCA-I is rel. 9 or above through the diameter update-dictionary-avps { 3gpp-r9 | 3gpp-r10
} CLI command.
Important
Called-Station-ID AVP in CoA and DM Messages
CSCuy67680 - Ignore called-station-id received in radius CoA/DM messages
Applicable Products: GGSN, HA, PDSN, P-GW, SAEGW
Release Change Reference, StarOS Release 19
4
AAA Changes in Release 19
3GPP Rel.9 Compliance for Flow-Description AVP