The Netloc and RAN/NAS Cause Code feature is supported in non-CUPS architecture. With this release, this feature is qualified in CUPS architecture.

This feature is used to send detailed RAN and/or NAS release cause code information from the access network to PCRF.

This feature is in compliance with Release 12 specification of 3GPP TS 29.212.

If the supported features "netloc-ran-nas-code" and "netloc" are enabled, then netloc-ran-nas-cause code are sent to the PCRF through CCR-U/CCR-T message.

In the Charging-Rule-Report AVP and CCR-T, the Diameter AVP “RAN-NAS-Release-Cause” is included for bearer and session deletion events respectively when the NetLoc-RAN-NAS-Cause supported feature is enabled and the RAN/NAS cause is received from the access side.

In the CCR-U and CCR-T, the network location is sent in the Diameter AVP “3GPP-User-Location-Info” and/or “3GPP-MS-TimeZone” is included for creation/updation/deletion of bearer or session events respectively when the NetLoc-RAN-NAS-Cause supported feature is enabled and the Netloc is received from the access side.

Use the following configuration to enable the feature.

configure 
   contextcontext_name 
      ims-auth-serviceservice_name 
         policy-control 
            diameterencode-supported-featuresnetloc-ran-nas-cause 
            end 

NOTES:

• netloc-ran-nas-cause : Enables the Netloc-RAN-NAS-Cause feature. By default, this supported feature will be disabled.

• If the supported features "netloc-ran-nas-code" and "netloc" are enabled, then netloc-ran-nas-cause code will be sent to PCRF.

• To disable this supported feature, use the following command:

  [ default | no ] diameter encode-supported-features

• This feature is supported only for standard Gx dictionary (r8-gx-standard and dpca-custom8).