How Is the WALLET_TYPE Passed to the Control Plan When Defined as a PI CCS_BPL=EXE Command Parameter ?
Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.0.0 and later
Information in this document applies to any platform.
This document explains how the information contained in the WALLET_TYPE parameter of the Provisionning Interface (PI) command CCSBPL=EXE is passed to the Control Plan (CP) through the Advanced Calling Services (ACS) internal Initial Detection Point (IDP).
The CCSBPL=EXE command supports the WALLET_TYPE as optional parameter. Please refer to the following Product Documentation guide : CCS Provisioning Interface Commands, where the CCSBPL=EXE command is described as :
This command allows the system admin to use the PI to trigger a BPL. This basically allows a Control Plan to be triggered from the PI on the SMS to run a particular service scenario, according to the following communication path :
PI [SMS] ---PI command*---> smsTrigDaemon [SMS] ---XML---> xmlTcapInterface [SLC] ---IDP**---> slee_acs [SLC] ---IDP**---> Control Plan (CP) runs the service according to the parameters in the IDP.
The CCSBPL=EXE PI commands accepts the WALLET_TYPE as an (optional) parameter, the CCS Provicioning Interface Commands guide says :
WALLET_TYPE : The applicable wallet type. Values are:
In other words, this document explains how the "Primary" or "Secondary" information recorded in the PI command* is translated into information in the IDP** generated by the xmlTcapInterface to trigger the CP. Or more simply said :
How is the WALLET_TYPE information passed from the PI command to the CP ?
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