5G Metadata Mapping for SGSN_PLMN_ID
(Doc ID 2831337.1)
Last updated on JANUARY 23, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Goal
In 4G, 4th Generation wireless, SGSN_PLMN_ID was mapped to Service-Information.PS-Information.SGSN-MCC-MNC-3GPP Diameter Attribute Value Pair (AVP).
In 5G, 5th Generation wireless, MCC and MNC are two different tags as nfConsumerIdentification.nFPLMNID.mcc and nfConsumerIdentification.nFPLMNID.mnc.
How the mapping can be configured in metadata? Without mapping MCC and MNC, will Charging Function (CHF) 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 |