Mapping Of Same AVPs Multiple Times Does Not Map To The Event Fields In BRM DB (Doc ID 2116174.1)

Last updated on APRIL 19, 2016

Applies to:

Oracle Communications Pricing Design Center - Version 11.1.0.7.0 to 11.1.0.7.0 [Release 11.1.0]
Oracle Communications BRM - Elastic Charging Engine - Version 11.2.0.7.0 to 11.2.0.7.0 [Release 11.2.0]
Information in this document applies to any platform.

Goal

1. It is observed that if request specification file is enriched having multiple occurrences of the same AVPs mapped to different event fields in BRM (e.g. "networkAttributeItem" value is same for 2 event fields) then one is not able to map to event fields in BRM database. As soon as multiple occurrence is removed, it works.

Issue is observed on trying to map the calling_from into two different event fields. On doing rating, it fails during Initiate request itself.

How to resolve this?


2. If the requirement is as described below then how to map it in Request specification XML?

There are multiple AVP groups of same type in CCR. For example.

Subscription-Id (443,M,l=44) =
Subscription-Id-Type (450,M,l=12) = END_USER_E164 (0)
Subscription-Id-Data (444,M,l=21) = 2348040001013
Subscription-Id (443,M,l=44) =
Subscription-Id-Type (450,M,l=12) = END_USER_IMSI (1)
Subscription-Id-Data (444,M,l=23) = 621401000000013
  
  
Here the requirement is to store all values of Subscription-Id-Data i.e. (2348040001013 & 621401000000013) in the Database.

Request specification XML is as below :

<simpleAttributeItem>
<name>PRIMARY_MSID</name>
<description>User msisdn</description>
<type>STRING</type>
<persistedName>event_dlay_sess_tlcs_t.primary_msid</persistedName>
<attributeItemSupportedBy>
<targetApplicationSpecName>Pricing</targetApplicationSpecName>
<targetApplicationSpecName>Convergent Charging</targetApplicationSpecName>
</attributeItemSupportedBy>
<networkAttributeItem>Subscription-Id.Subscription-Id-Data</networkAttributeItem>
</simpleAttributeItem>

<simpleAttributeItem>
<name>IMSI</name>
<description>User IMSI</description>
<type>STRING</type>
<persistedName>event_dlay_sess_tlcs_t.imsi</persistedName>
<attributeItemSupportedBy>
<targetApplicationSpecName>Pricing</targetApplicationSpecName>
<targetApplicationSpecName>Convergent Charging</targetApplicationSpecName>
</attributeItemSupportedBy>
<networkAttributeItem>Subscription-Id.Subscription-Id-Data</networkAttributeItem>
</simpleAttributeItem>

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms