Change Notification Support for Pure S

This chapter contains the following topics:

Revision History


Note

Revision history details are not provided for features introduced before release 21.24.

Revision Details

Release

First introduced

Pre 21.24

Feature Description

Cisco CUPS supports the Change Notification in Pure-S CUPS. If ULI/UCI changes are valid in CNReq, it generates the SGW CDR for ULI change. To support SGWCDR, SGW-C needs to fetch the latest data usage from U-Plane. After receiving the latest usage report, it triggers the CDR generation request. The Change Notification may contain Secondary RAT usage IE, in that case, if SGW generate SGWCDR, it contains the Secondary RAT usage.

How It Works

Call Flow

The following call flow shows the Change Notification support for Pure-S:

Figure 1. Change Notification Request

On receiving the Change Notification Request:

  • If Secondary RAT Usage Data Report is present, it is included in CDR

  • If ULI/UCI change is valid:

    • Added support to send the Event to SMGR to trigger Sx_Session_Modification request with Query URR to fetch latest data usage from U-Plane.

    • Added the pending state to get latest data usage to trigger ULI/UCI change CDR.

    • Send event to trigger generate CDR.