Cisco Cisco Packet Data Interworking Function (PDIF)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
• GTPP Enhancements
• Lawful Intercept Enhancements
• MVG Enhancements
• NAT Enhancements
• SNMP MIB Enhancements
• System and Platform Enhancements
Correction for Unexpected Session Deletion on the S-GW
CDETS = CSCux10033 - Unexpected Session Deletion on S-GW
Applicable Products: S-GW
The fix implemented for CSCux10033 has resulted in a behavior change.
Consider the following scenario:
• The egtp cause-code temp-fail dbf-proc CLI command is configured on the S-GW.
• A Modify Bearer Request (MBR) message is received by the S-GW from the MME.
• The Bearer context instance value is set to 1 under the MBR message.
• In response to this MBR, the P-GW sends a Delete Bearer Request message (DBR) to the S-GW.
This led to an unexpected event for the bearer at the S-GW, and the call was dropped.
Previous Behavior: The S-GW removed the bearer as soon as the MBR was received by changing the bearer
state to 'disconnecting'.
state to 'disconnecting'.
New Behavior: The S-GW marks this bearer as an IDLE bearer but does not remove it. The S-GW waits for
a Delete Bearer Command/Delete Bearer Response (DBC/DBR) message to delete the bearer as an expected
scenario. The S-GW also permanently suspends this bearer by changing its state to drop data on idle at the
session manager. Since this bearer is to be removed, the S-GW blocks any data level signaling. Thus, any
new downlink data will not trigger a Downlink Data Notification procedure (DDN) for this suspended bearer.
A DDN will be triggered for all other bearers with downlink data if they are in the IDLE state.
a Delete Bearer Command/Delete Bearer Response (DBC/DBR) message to delete the bearer as an expected
scenario. The S-GW also permanently suspends this bearer by changing its state to drop data on idle at the
session manager. Since this bearer is to be removed, the S-GW blocks any data level signaling. Thus, any
new downlink data will not trigger a Downlink Data Notification procedure (DDN) for this suspended bearer.
A DDN will be triggered for all other bearers with downlink data if they are in the IDLE state.
Customer Impact: The S-GW complies with version 10 of 3GPP 29.274. There will be no impact if the
MME complies with the same version. In the case of non-compliance, the MME does not send a DBC. The
bearer remains idle with the S-GW and will eventually be deleted when the next MBR is received.
MME complies with the same version. In the case of non-compliance, the MME does not send a DBC. The
bearer remains idle with the S-GW and will eventually be deleted when the next MBR is received.
S-GW Enhancements for 19.2
This section identifies all of the S-GW enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the S-GW Administration
Guide for this release.
Guide for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line
Interface Reference for this release.
Interface Reference for this release.
Release Change Reference, StarOS Release 19
416
S-GW Changes in Release 19
Correction for Unexpected Session Deletion on the S-GW