Handling Temporary Failure During UBR-MBC Collision

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

  • S-GW

Applicable Platform(s)

  • ASR 5500

  • VPC-DI

  • VPC-SI

Feature Default

Disabled-Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

Not Applicable

Revision History

Revision Details

Release

S-GW sends the Update Bearer Response message to P-GW with the cause code as 110 (Temp_Rejected_Due_To_Handover_In_Progress) when it identifies an ongoing Update Bearer Request message.

21.12.15

First introduced.

Pre 21.2

Feature Changes

Previous Behavior: During a 3G to 4G handover, when PCRF initiates a QoS Class Index (QCI) change, MME neither rejects nor processes the Update Bearer Request message and it fails to send the Update Bearer Response message back to P-GW through S-GW. At the same time, MME tries to send the Modify Bearer Command (MBC) message to P-GW through S-GW. Then, S-GW sends the Update Bearer Response message to P-GW with the cause code as 89 (Service_Denied) when it identifies an ongoing Update Bearer Request message. MME is unable to update the QoS change because P-GW does not retry to send the Update Bearer Request message after it receives the Update Bearer Response message with the cause code as Service_Denied.

New Behavior: In 21.12.15 and later releases, S-GW sends the Update Bearer Response message to P-GW with the cause code as 110 (Temp_Rejected_Due_To_Handover_In_Progress) when it identifies an ongoing Update Bearer Request message. In this case, P-GW with the existing cause-code temp-fail configuration retries to send the Update Bearer Request message and MME is updated with the QCI change.


Note

The temp-fail CLI for P-GW must be configured for the solution to work properly.

Customer Impact: Not applicable

Command Changes

egtp cause-code temp-failure ubr-mbc-collision

To enable the temporary failure of Update Bearer Request (UBR)-MBC collision handling functionality, use the following configuration:

configure 
   contextcontext_name 
      sgw-serviceservice_name 
         [default | no] egtp cause-code temp-failure ubr-mbc-collision 
         end

NOTES:

  • no Disables the specified parameter.

  • cause-code Configures the collision-handling failure response.

  • temp-failure Configures the temporary failure response during collision-handling.

  • ubr-mbc-collision Configures the service to send cause code 110 (temporary failure) for UBR-MBC collision. The default behavior is disabled.

  • default Sets or resets the corresponding parameter to its default value.

Performance Indicator Changes

show sgw-service name sgw-service

The output of this command includes the following field:

  • temp-failure ubr-mbc-collision: Indicates whether the temporary failure configuration for Update Bearer Request (UBR)-MBC collision is enabled or disabled.