My Oracle Support Banner

RAR Generation Issue in SCP Model (Doc ID 2890996.1)

Last updated on SEPTEMBER 12, 2022

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Symptoms

One user has configured Service Control Point (SCP) Internet Protocol (IP) and port number in SCP authorities.

In a test scenario of sending Re-Auth Requests (RAR) after enabling SCP (Model-C), the Charging Function (CHF) is sending the RAR to Session Management Function (SMF) via SCP for re-authorization using Notify Uniform Resource Identifier (URI) instead of SCP Uniform Resource Locator (URL).

Below are some points to be noted:

1) notifyUri
    It should contain SMF URL along with the path. CHF will get notifyUri in all the charging request.
    e.g.:
    notifyUri: http://<IP>:65513/nchf-convergedcharging/v2/chargingdata/0050811062ab1fdf

2) target-apiroot
    It is the part of the header and should contain SMF URL. CHF should take URL part from notifyUri and set it here.
    e.g.:
    3gpp-sbi-target-apiroot:http://<IP>:65513

3) End point URL where CHF has to send the request would be in this format: SCP_URL/nscp-route/path
    e.g.:
    http://<IP>:80/nscp-route/nchf-convergedcharging/v2/chargingdata/014781f062ab2b77

4) SMF has to send update request immediately after getting RAR from CHF.
    This is tested using curl and it is working as expected.

The point 3) requires code changes.



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.