Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 17
P-GW Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
403
CSCup89213 - Incorrect cause-code in DB Req for PCRF initiated session
termination
Feature Changes
Incorrect cause-code in DB Requirement for PCRF Initiated Session Termination
Previous Behavior: For a APN with default/no pdn-behavior, a DB Request went out with the Cause Code
“Reactivation Requested”. This occurred whenever a P-GW PDN deletion was triggered when a PCRF connection
failure/result code based failure/imsa service was removed from a configuration. However, according to a specific
customer specification for an APN with default/no pdn-behavior, a Cause Code IE should not be included if a message
is caused by PCRF initiated PDN disconnect procedure in a Delete Bearer Request.
“Reactivation Requested”. This occurred whenever a P-GW PDN deletion was triggered when a PCRF connection
failure/result code based failure/imsa service was removed from a configuration. However, according to a specific
customer specification for an APN with default/no pdn-behavior, a Cause Code IE should not be included if a message
is caused by PCRF initiated PDN disconnect procedure in a Delete Bearer Request.
New Behavior: For an APN with default/no pdn-behavior, a DB request will not include a Cause Code IE when a
PCRF initiated P-GW PDN deletion is triggered. The trigger can be a PCRF connection failure/result code based
failure/imsa service that is removed from a configuration.
PCRF initiated P-GW PDN deletion is triggered. The trigger can be a PCRF connection failure/result code based
failure/imsa service that is removed from a configuration.
Customer Impact: For an APN with default/no pdn-behavior, a DB request will not include a Cause Code IE when a
PCRF initiated P-GW PDN deletion is triggered. The trigger can be a PCRF connection failure/result code based
failure/imsa service that is removed from a configuration.
PCRF initiated P-GW PDN deletion is triggered. The trigger can be a PCRF connection failure/result code based
failure/imsa service that is removed from a configuration.
CSCuq19244 - PGW doesnt initiate dns query to resolve p-cscf addr after
ehrpd-epdg ho
Feature Changes
P-GW Did Not Initiate DNS Query to Resolved P-CSCF Address after Inter-tech Handoffs
P-GW did not initiate P-CSCF Discovery to resolved P-CSCF Address after following inter-tech handoff scenarios if P-
CSCF Address information is already missing.
CSCF Address information is already missing.
Previous Behavior: If P-CSCF address information was already missing, then the P-GW did not initiate P-CSCF
Discovery to resolve the P-CSCF address after the following inter-tech handoff scenario.
Discovery to resolve the P-CSCF address after the following inter-tech handoff scenario.
eHRPD to S2B
LTE to S2B
S2B to LTE
S2A to LTE
Important:
LTE to S2A Handoff is intentionally NOT mentioned here as P-CSCF IE is not supported
for this Handoff.
New Behavior: If P-CSCF address information is already missing, then the P-GW initiates P-CSCF Discovery to
resolve the P-CSCF address after the following inter-tech handoff scenarios.
resolve the P-CSCF address after the following inter-tech handoff scenarios.
eHRPD to S2B
LTE to S2B