Handling Simultaneous Gy RARs from Different DRAs with Different RGs

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

P-GW

Applicable Platform(s)

  • ASR5500

  • VPC-DI

  • VPC-SI

Feature Default

Disabled - Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

  • P-GW Administration Guide

  • Command Line Interface Reference

Revision History

Revision Details

Release

Enhancement of Gy interface on P-GW to handle multiple DRA.

21.28

Feature Description

In P-GW, if there are Multiple Diameter Routing Agents (DRA) and if P-GW receives simultaneously more than one Reauthorization Request (RAR) each with different rating-group (RG) from different DRAs than from the last diameter request, P-GW aborts the previous transaction (the one with the Credit Control Request –Update message, which is pending from a previous RAR) and re-uses the same cc-request-number for next Credit Control Request –Update message (CCR-U) (binding toward new peer).

This resulted in quota not getting applied to RG received through previous RARs. Hence, traffic does not get forwarded for that rating group or service-id wRAs.

In StarOS 21.28 and later releases, P-GW accepts both RGs from different peer by using a configurable CLI command diameter pending-ccau allow-on-rar-peer-switch under the ACS configuration mode. That is, this CLI allows you to configure the DCCA client to prevent the aborting of a pending CCRU request received in case of RAR, which is received from a different host or peer on the Gy interface.

How it Works

There is a change in the handling of aborting the previous pending requests. Currently, When a DCCA client is in pending state, upon receiving RAR through a different peer, the DCCA client aborts the diameter message (at ACS manager level). Due to the enhancement of the Gy interface on P-GW to handle multiple DRA features, P-GW now avoids this aborting of previous pending requests and accepts both RGs from a different peer.

After receiving a new RAR either from a new peer or host, P-GW updates the session to a new peer or host. Then checks for any pending state of Multiple Service Credit Control (MSCC) and avoids the subsequent action of aborting of pending CCRU requests.

The following call flow and procedure describes how P-GW accepts both RGs from different peer.

Figure 1. Call Flow

Configuring Multiple DRA over Gy Interface

Use the following configuration commands to configure different DRAs.


configure 
     context context_name 
     active-charging service acs_service_name> 
          credit-control [ group cc_group_name ] 
               diameter dictionary dictionary 
              [ no ] diameter pending-ccau allow-on-rar-peer-switch  
          exit 

NOTES:

  • diameter dictionary dictionary : Set the diameter dictionary to handle different DRAs. For example, diameter dictionary dcca-custom-26

  • diameter pending-ccau allow-on-rar-peer-switch : Allows DCCA client to prevent the abort of pending CCAU request in case of RAR being received from different host/peer on the Gy interface.

  • [ no ] diameter pending-ccau allow-on-rar-peer-switch : Disables the DCCA client from preventing the abort of pending CCAU requests.

Monitoring and Troubleshooting

This section provides information regarding monitoring and troubleshooting of multiple DRA messages on the Gy interface.

Show Commands and Outputs

This section provides information regarding show commands and outputs in support of this feature.

show active-charging service all

Table 1. show active-charging service all
Field Description

pending ccau:

allow-on-rar-peer-switch

Displays whether abort of pending CCAU request in case of RAR being received from different host/peer on Gy interface is enabled or disabled. If this feature is enabled the functionality is applicable only to new diameter sessions.