My Oracle Support Banner

5G || Metadata Mapping For SGSN_PLMN_ID (Doc ID 2831337.1)

Last updated on JANUARY 03, 2022

Applies to:

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

Goal

In 4G , SGSN_PLMN_ID was mapped to Service-Information.PS-Information.SGSN-MCC-MNC-3GPP Diameter Attribute Value Pair (AVP).

In 5G , MCC and MNC are as two different tags nfConsumerIdentification.nFPLMNID.mcc and nfConsumerIdentification.nFPLMNID.mnc.

How mapping can be configured in metadata? Without mapping MCC MNC , will CHF wont be able to meet roaming requirements ?

Solution

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
Goal
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.