Cisco Cisco Packet Data Gateway (PDG)
P-GW to Initiate CRA IE in UBReq Immediately
CSCuy95645 - PGW to initiate CRA IE in UBReq immediately
Applicable Products: P-GW, SAEGW
Feature Changes
For activating location reporting for a UE over Gx, RAR from PCRF was sent with the event trigger
"USER_LOCATION_CHANGE". On receiving this event trigger, P-GW should typically send CRA IE with
"Start Reporting " towards the MME to enable the Location-Change reporting for the UE in an MME.
"USER_LOCATION_CHANGE". On receiving this event trigger, P-GW should typically send CRA IE with
"Start Reporting " towards the MME to enable the Location-Change reporting for the UE in an MME.
Earlier, P-GW was not initiating Update Bearer Request procedure explicitly to inform only CRA IE and was
relying on any other procedure like QoS change happening at same time or in future. This resulted in delay
in updating required action at the MME. After this feature change, P-GW would immediately initiate Update
Bearer Request, even for updating only CRA IE, if there are no other changes detected in RAR received with
ULI_LOCATION_CHANGE event trigger. If there are other changes detected in RAR, CRA IE would be
combined with Update Bearer Request initiated for the same.
relying on any other procedure like QoS change happening at same time or in future. This resulted in delay
in updating required action at the MME. After this feature change, P-GW would immediately initiate Update
Bearer Request, even for updating only CRA IE, if there are no other changes detected in RAR received with
ULI_LOCATION_CHANGE event trigger. If there are other changes detected in RAR, CRA IE would be
combined with Update Bearer Request initiated for the same.
Previous Behavior: Earlier, P-GW initiated update Bearer procedure was not triggered when the ULI event
trigger was received from a RAR than a CCA-U.
trigger was received from a RAR than a CCA-U.
New Behavior: Now, P-GW initiated update bearer procedure for CRA IE is triggered, if RAR is received
with the ULI trigger.
with the ULI trigger.
IPv4v6 PDN Rejection
CSCuz51684 - IPv6 pdn rejected if UE req v6 addr n Access-Accept has Framed Prefix
Applicable Products: P-GW, SAEGW
Feature Changes
IPv4 or IPv6 PDN were rejected, when the UE requests IPv4 or IPv6 static address when the CLI command
ipv6 address alloc-method no-dynamic was configured under the APN. However, Ipv4v6 PDN was accepted
when the UE requested static IPv6 address when the CLI command ipv6 address alloc-method no-dynamic
was configured.
ipv6 address alloc-method no-dynamic was configured under the APN. However, Ipv4v6 PDN was accepted
when the UE requested static IPv6 address when the CLI command ipv6 address alloc-method no-dynamic
was configured.
Old Behavior: Earlier, Ipv4v6 PDN was accepted when the UE requested static IPv6 address when the CLI
command ipv6 address alloc-method no-dynamic was configured.
command ipv6 address alloc-method no-dynamic was configured.
New Behavior: Now, Ipv4v6 PDN is rejected when the UE requested static IPv6 address when the CLI
command ipv6 address alloc-method no-dynamic is configured.
command ipv6 address alloc-method no-dynamic is configured.
L2TP Password Behavior Parity Between P-GW and GGSN
CSCuz59475 - L2TP password behavior parity between PGW and GGSN
Applicable Products: P-GW, SAEGW
Release Change Reference, StarOS Release 19
326
SAEGW Changes in Release 19
P-GW to Initiate CRA IE in UBReq Immediately