Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 16
P-GW Enhancements for 16.2 ▀
Release Change Reference, StarOS Release 16 ▄
325
CSCuo95038 - TMOPL: PGW forces lower AMBR values than received
Feature Changes
P-GW forces lower AMBR values than received
Previous Behavior: In absence of PCRF, the APN AMBR that was received in the MOB BEARER REQUEST during
GnGp HO was not applied.
GnGp HO was not applied.
New Behavior: In absence of PCRF, the APN AMBR received in MOB BEARER REQUEST during GnGp HO will
now be applied.
now be applied.
CSCup44058 - Acct msg shows both v4 and v6 addr even if v4 is denied for
static alloc
Feature Changes
Accounting messages for both IPv4 and IPv6 address
Accounting start and stop messages showed both IPv4 and IPv6 address even if IPv4 address allocation was denied for
static address allocation.
static address allocation.
Previous Behavior: If IPv4 or IPV6 type failed when a UE request was received for dual PDP type, then the radius
account failed IP address/PDP type.
account failed IP address/PDP type.
New Behavior: If IPv4/IPv6 address allocation fails, then a new PDP type is sent and the correct IP address is in
radius accounting.
radius accounting.
CSCup51117 - Difference in behaviour for eHRPD and LTE for fragmented
output packets
Feature Changes
Behavior for eHRPD and LTE for Fragment Output Packets
For P-GW service, Radius accounting was previously done post fragmentation at the session manager for downlink
data. However, Gy/Gz accounting was done by ECS which was not aware of the fragmentation.
data. However, Gy/Gz accounting was done by ECS which was not aware of the fragmentation.
In order to be in sync, Radius accounting for P-GW service is now done prior to fragmentation. This change is done
with acceptance that the P-GW CDR's and the S-GW CDR's may differ in data count because the S-GW does not
reassemble these packets.
with acceptance that the P-GW CDR's and the S-GW CDR's may differ in data count because the S-GW does not
reassemble these packets.
Previous Behavior: For downlink data, the LTE P-GW used to account the additional bytes was added as a result of
fragmentation in Radius accounting only.
fragmentation in Radius accounting only.
New Behavior: For downlink data, the LTE P-GW does not account for the additional bytes added as a result of
fragmentation at the P-GW session manager in Radius accounting.
fragmentation at the P-GW session manager in Radius accounting.