Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
P-GW Changes in Release 15.0
P-GW Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
405
Cause inside Bearer Context in response messages will only be validated if Message level cause is
accepted
The code is currently dependent on availability of the Bearer Context and refers to the Cause Code
within the Bearer Context when the response message (Create Bearer, Update Bearer, Delete
Bearer*), indicates other than ACCEPTED or PARTIALLY_ACCEPTED. With this change, P-GW
driver level populates the Bearer Context information from the Message level information for such
scenarios. This information would further get passed to the SessMgr over the SNX interface. This
helps re-use the Session Manager logic for handling the information within the Bearer Context
without much change.
within the Bearer Context when the response message (Create Bearer, Update Bearer, Delete
Bearer*), indicates other than ACCEPTED or PARTIALLY_ACCEPTED. With this change, P-GW
driver level populates the Bearer Context information from the Message level information for such
scenarios. This information would further get passed to the SessMgr over the SNX interface. This
helps re-use the Session Manager logic for handling the information within the Bearer Context
without much change.
Allow Up to Three P-CSCF Addresses for IPv4 and IPv6 in P-GW
Previous Behavior:
1. CLI is used to configure the P-CSCF IPv4 and IPv6 addresses (primary and secondary) in APN.
2. CreateSessionReq is received requesting both P-CSCF IPv4 and IPv6 addresses.
3. CreateSessionResp is sent with 2 primary (1 IPv4 and 1 IPv6) and 2 secondary addresses (1 IPv6 and 1 IPv6).
2. CreateSessionReq is received requesting both P-CSCF IPv4 and IPv6 addresses.
3. CreateSessionResp is sent with 2 primary (1 IPv4 and 1 IPv6) and 2 secondary addresses (1 IPv6 and 1 IPv6).
New Behavior:
1. CLI has been enhanced to configure up to 3 IPv4 (priority 1-3) and 3 IPv6 (priority 1-3) P-CSCF addresses in
APN.
2. CreateSessionReq is received requesting both P-CSCF IPv4 and IPv6 addresses.
3. CreateSessionResp is sent with 3 IPv4 and 3 IPv6 addresses.
3. CreateSessionResp is sent with 3 IPv4 and 3 IPv6 addresses.
Change for UDP Packet with Source Port 4500
Previous Behavior: P-GW handles UDP packet with source port 4500, destination port 434 as combo-phone request,
triggering IPsec tunnel setup.
triggering IPsec tunnel setup.
New Behavior: P-GW will not detect combo-phone request and treat UDP packet with source port4500, destination
port 434 as normal MIP RRQ.
port 434 as normal MIP RRQ.
Configurable Subscriber State Management Audit Process
A new
audit
command and keywords in Context Configuration mode allow an operator to specify the start time and
periodicity for generating Interchassis Session Recovery (ICSR) Service Redundancy Protocol (SRP) audit statistics.
This audit ensures that two ICSR peers are in synch and identifies any discrepancies prior to scheduled or unscheduled
switchover events.
This audit ensures that two ICSR peers are in synch and identifies any discrepancies prior to scheduled or unscheduled
switchover events.
Customer 4G Network Upgrade 3GPP Standard Baseline Release Compliance for P-GW / HSGW /
ePDG
All PGW/HSGW/ePDG interfaces upgraded to support, at a minimum, inbound 3GPP R11 IEs that are needed to
support features requested by customer.
support features requested by customer.
Network elements need to gracefully handle any new IE sent by Peer that is not supported by the network
element.
Network elements should comply to Interface specifications updated with the call flows and IEs necessary for
the features.
IE will be used as defined by 3GPP specifications and other relevant Diameter specifications.
The following interfaces are supported:
PGW: S6b, S5/S8, Gx, Gy, Rf, S2a, S2b, X3