1. Implementing Roaming
  2. Setting Up Pipeline Manager for Roaming Outcollect Processing

7 Setting Up Pipeline Manager for Roaming Outcollect Processing

This chapter describes how to configure Oracle Communications Billing and Revenue Management (BRM) Pipeline Manager for roaming outcollect processing.

Note:

The following pipeline configuration applies to rating TAP roaming usage events only.

For more information about roaming outcollect processing, see "About Processing Visiting Subscribers' Roaming Usage".

Setting Up Roaming Outcollect Processing Pipelines

Configure the following pipelines to set up roaming outcollect processing:

Configuring the Splitter Pipeline

Configure the splitter pipeline by performing the following tasks:

Configuring the Splitter Pipeline DataDescription Registry Section

Configure the splitter pipeline DataDescription registry section by setting the stream formats, input mapping, and output mapping as follows:

DataDescription
{
   Standard 
   {
   ModuleName = Standard 
   Module
   {
   StreamFormats
   {
     SOL42_FORINPUT     = ./formatDesc/Formats/Solution42/SOL42_V670_REL_FORINPUT.dsc
     SOL42              = ./formatDesc/Formats/Solution42/SOL42_V670_REL.dsc          
   }
   InputMapping
   {
     SOL42_FORINPUT     = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InMap.dsc
   }
   OutputMapping
   {
     SOL42              = ./formatDesc/Formats/Solution42/SOL42_V670_REL_OutMap.dsc
   }
   }
   }
}
Configuring the Splitter Pipeline Input Processing

Configure input processing for the splitter pipeline as follows:

  1. (Optional) Configure a Batch Controller and a Batch Handler to send call data records (CDRs) from your mediation system to the input directory of the splitting pipeline.

    Note:

    You do not need to configure a Batch Controller and a Batch Handler if your mediation system is set up to send incoming CDRs directly to the splitter pipeline.

  2. Configure the INP_GenericStream input module to map CDR fields to event data record (EDR) container fields:

    1. Set the Grammar registry entry to the standard BRM input grammar description file: 

      Grammar = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InGrammar.dsc

    2. Configure the EXT_InFileManager registry entry to specify information about the input file.

      Note:

      In the default Pipeline_home/conf/roaming.reg registry file, the input format is the standard BRM input grammar. If you are using a different input format, you will need to modify the input grammar.

      For example:

      Grammar = ./formatDesc/Formats/Solution42/yourInputGrammarFile.dsc
Configuring the Splitter Pipeline Function Modules

The splitter pipeline uses the FCT_EnhancedSplitting module to split EDRs into home and roaming EDRs. See "Configuring the Splitter Pipeline Input Processing".

Configuring the Splitter Pipeline Output Processing

Configure output processing for the splitter pipeline as follows:

  1. Configure routing home and roaming EDRs to different output streams as follows:

    1. Create a system brand called HOME to associate with home EDRs and a system brand called ROAM to associate with roaming EDRs.

    2. Define splitting rules and associate the rules with the system brands.

    3. Configure FCT_EnhancedSplitting and use the SystemBrand entry to map the system brands to the home and roaming EDR output streams as follows: 

      ModuleName = FCT_EnhancedSplitting
Module
{
     Active           = True 
     DataConnection   = ifw.DataPool.Login 
     DefaultOutput    = RoamOutput 
     SystemBrands 
     {  
        HOME          = HomeOutput
        ROAM          = RoamOutput
     }
}

      The DefaultOutput entry specifies the default output stream for EDRs that do not match the splitting rules.

  2. Configure an output stream to write home EDRs to an output file to be processed by the normal rating pipeline.

    1. Set the Grammar registry entry of the OUT_GenericStream module to the standard BRM output grammar description file: 

      Grammar=./FormatDesc/Solution42/SOL42_V670_REL_OutGrammar.dsc

    2. Configure EXT_OutFileManager to specify information about the output file.

  3. Configure another output stream to write roaming EDRs to an output file to be processed by the outcollect rating pipeline.

    1. Set the Grammar registry entry of the OUT_GenericStream module to the standard BRM output grammar description file: 

      Grammar=./FormatDesc/Solution42/SOL42_V670_REL_OutGrammar.dsc

    2. Configure EXT_OutFileManager to specify information about the output file.

Configuring the Outcollect Rating Pipeline

Configure the outcollect rating pipeline by performing the following tasks:

Configuring the Outcollect Rating Pipeline DataDescription Registry Section

Configure the Outcollect rating pipeline DataDescription registry section by setting the stream formats, input mapping and output mapping as follows:

DataDescription
{
   Standard 
   {
   ModuleName = Standard 
   Module
   {
   StreamFormats
   {
     SOL42    = ./formatDesc/Formats/Solution42/SOL42_V670_REL_FORINPUT.dsc
     Generic  = ./formatDesc/Formats/TAP3-NG/GenericBlocks.dsc
     TAP      = ./formatDesc/Formats/TAP3-NG/TAP_0312_Blocks.dsc
   }
   InputMapping
   {
     SOL42    = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InMap.dsc
   }
   OutputMapping
   {
   }
   }
   }
}
Configuring the Outcollect Rating Pipeline Input Processing

Configure input processing for the outcollect rating pipeline as follows:

  1. Configure the input stream.

    1. Set the Grammar registry entry for the INP_GenericStream module to the standard BRM input grammar description file: 

      Grammar = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InGrammar.dsc

    2. Configure EXT_InFileManager to specify information about the output file.

      Note:

      By default, the outcollect rating pipeline retrieves the roaming EDRs from the output directory of the splitter pipeline. Set OutputPath, OutputPrefix, and OutputSuffix to be the same as the splitter pipeline's output directory for roaming EDRs if you are implementing the default behavior.

Configuring the Outcollect Rating Pipeline Function Modules

Configure the registry entries for the following modules:

  • DAT_InterConnect, which provides network operator data for FCT_CarrierRating.

  • FCT_CarrierIcRating, which adds roaming data to EDRs for rating by the FCT_PreRating and FCT_MainRating modules.

  • FCT_PreRating, which calculates zones and creates impact categories.

  • FCT_MainRating, which performs the main rating functionality in a pipeline.

  • FCT_Rounding, which performs rounding for rating and discounting.

  • FCT_ExchangeRate, which converts the charge amount to SDR currency. Use the HomeCurrency entry to set currency to SDR as follows: 

    HomeCurrency = SDR

  • ISC_MiscOutCollect, which adds BASIC_SERVICE and SUPPLEMENTARY_SERVICE blocks to the EDR container for GSM services.

Configuring the Outcollect Rating Pipeline Output Processing

Configure output processing for the outcollect rating pipeline as follows:

  1. Configure outcollect TAP file generation for each roaming partner.

    During outcollect processing, roaming EDRs are identified by roaming partner and routed to the output streams unique for each partner. This enables the EDRs for one roaming partner to be isolated from the EDRs for another partner. To support this, do the following:

    1. Create a system brand for each roaming partner.

    2. Define splitting rules for each roaming partner.

    3. Configure FCT_EnhancedSplitting to route the rated EDRs to the corresponding network operator output stream using system brands.

      Note:

      You can use the Instances module to configure multiple system brands for FCT_EnhancedSplitting to route EDRs to multiple output streams.

      If FCT_EnhancedSplitting is unable to route the EDR using the splitting rules, it sends it to the default output which is mapped to the suspense output stream.

      In the following sample registry, OPR01 and OPR02 system brands are used to route EDRs to different output streams:

      ModuleName = FCT_EnhancedSplitting
Module
{
Active           = True 
DataConnection   = ifw.DataPool.Login 
DefaultOutput    = SuspenseCreateOutput 
SystemBrands 
{  
OPR01            = OPR01Output
OPR02            = OPR02Output
}
}

  2. Configure sequence generation for outcollect TAP files.

    1. Using Pricing Center or Pipeline Configuration Center (PCC), define a sequence generator for each roaming partner by entering a name and a unique sequence key.

    2. Configure each Sequencer by editing the SequencerPool section of the registry.

      Note:

      You can use the Instances module to configure multiple sequencers for multiple roaming partners.

    3. Set the SequencerInstance registry entry to the name of the sequence generator defined in step 2.a above.

    4. Set the SequencerType registry entry to Generation.

      The following sample configuration shows two Sequence Generators for NetworkOperator01 and NetworkOperator02.

      SequencerPool
{
SEQ_GEN_TAPOUT_NetworkOperator01
{ 
     Source = Database 
     Controller 
     { 
          SequencerType = Generation
          ReuseGap = True 
          SequenceLength = 5
          DatabaseConnection = ifw.DataPool.Login
     } 
}
SEQ_GEN_TAPOUT_NetworkOperator02
{ 
     Source = Database 
     Controller 
     { 
          SequencerType = Generation
          ReuseGap = True 
          SequenceLength = 5
          DatabaseConnection = ifw.DataPool.Login
     } 
}
}

  3. Configure an output stream for each roaming partner.

    For each roaming partner, configure the OUT_GenericStream module registry entries as follows:

    Note:

    You can use the Instances module to configure multiple output streams for multiple roaming partners.

    1. Set the Grammar registry entry to the TAP Output grammar description file: 

      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_OutGrammar.dsc

    2. Set Sequencer to the name of the Sequence Generator for generating sequence number for this roaming partner.

    3. Set Sender to the network operator ID sending the outcollect TAP file.

    4. Set Recipient to the roaming partner receiving the outcollect TAP file.

    5. Configure EXT_OutFileManager to specify the output file information.

      The following example shows output stream configurations for NetworkOperator01 and NetworkOperator02:

    NetworkOperator01Output
{
ModuleName  = OUT_GenericStream
...
Module
{
   Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_OutGrammar.dsc
   Sequencer = SEQ_GEN_TAPOUT_NetworkOperator01
   Sender = PORTL
   Recipient = OPRO1
   OutputStream
   {
     ModuleName = EXT_OutFileManager
     Module
     { OutputPath            = ./data/outcollect/tapout/opr01
       OutputPrefix          = CDPORTLOPR01 
       TempPrefix            = tmptest_opr01_
       TempDataPath          = ./data/outcollect/tapout/opr01
       TempDataPrefix        = test.opr01.tmp.
       TempDataSuffix        = .data
       UseInputStreamName    = [0,0]
       SequencerPrefix       = "" 
       AppendSequenceNumber  = True
     }
   }
}
}
NetworkOperator02Output
{
ModuleName  = OUT_GenericStream
...|
Module
{
   Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_OutGrammar.dsc
   Sequencer = SEQ_GEN_TAPOUT_NetworkOperator02
   Sender = PORTL
   Recipient = OPR02
   OutputStream
   {
     ModuleName = EXT_OutFileManager
     Module
     {
       OutputPath            = ./data/outcollect/tapout/opr02
       OutputPrefix          = CDPORTLOPR02 
       TempPrefix            = tmptest_opr02_
       TempDataPath          = ./data/outcollect/tapout/opr02
       TempDataPrefix        = test.opr02.tmp.
       TempDataSuffix        = .data
       UseInputStreamName    = [0,0]
       SequencerPrefix       = ""
       AppendSequenceNumber  = True
      }
   }
}
}

  4. Configure Event Handler to copy outcollect TAP files to a common directory and to move the original outcollect TAP files to the outcollect settlement pipeline input directory.

    1. For each network operator output stream configured in the outcollect rating pipeline, add the following to the Events subsection of the EventHandler registry: 

      EVT_OUTPUT_FILE_READY = ./bin/move_outcollectTap.pl

      The following example shows Event Handler configuration for NetworkOperator01Output and NetworkOperator02Output.

      EventHandler
{
     ModuleName = EVT
     Module
     {
        Events
        {
ifw.Pipelines.TAPOutCollectPipeline.Output.OutputCollection.NetworkOperator01Output.Module.OutputStream.Module
{
EVT_OUTPUT_FILE_READY = ./bin/move_outcollectTap.pl
}
ifw.Pipelines.TAPOutCollectPipeline.Output.OutputCollection.NetworkOperator02Output.Module.OutputStream.Module
{
EVT_OUTPUT_FILE_READY = ./bin/move_outcollectTap.pl
}
        }
     }
}

    2. Edit move_outcollectTap.pl.

      Edit the following line to specify the common directory to which the outcollect TAP files will be copied:

      my $COPY_DIR = "$ENV{IFW_HOME}/data/outcollect/tapout/common";

      Edit this line to specify the input directory of the outcollect settlement pipeline.

      my $MOVE_DIR = "$ENV{IFW_HOME}/data/outcollect/settlement/in";
Configuring the DAT_InterConnect Module

The DAT_InterConnect module provides network operator configuration information that is accessed by the FCT_CarrierICRating module.

Configure the DAT_InterConnect module in the DataPool registry section. When you configure DAT_InterConnect, you specify the database connection information to the BRM database.

Configuring Suspense Manager for the Outcollect Rating Pipeline

You must configure Suspense Manager pipeline components to process EDRs suspended by the outcollect rating pipeline.

EDRs suspended by the outcollect rating pipeline are processed by using the following Suspense Manager components:

  • FCT_PreSuspense, which appends suspense-related information to the EDR.

  • FCT_Reject, which sends suspended EDRs to the reject output stream.

  • FCT_Suspense, which routes EDRs from SuspenseCreateOutput to SuspenseUpdateOutput during recycling.

  • Suspended Event (SE) Loader, which loads suspended events from the reject output stream into the BRM database.

  • Suspense Management Center, which is used to query and edit the suspended events. After making the necessary corrections, you submit the suspended events to be recycled. When suspended events are submitted to be recycled, Suspense Management Center publishes a notification event that is queued in the BRM database to notify Pipeline Manager that events are ready to be recycled.

  • DAT_Listener, which dequeues the notification event from the BRM database and notifies the DAT_Recycle module.

  • DAT_Recycle, which creates a parameter file that allows the EXT_InEasyDB module to read suspended usage records associated with a recycle job. It also provides an interface for the INP_Recycle module to provide status updates about the EDR stream.

  • Pre-recycle pipeline, which sends the EDRs to the Outcollect rating pipeline to be rated again.

Configuring the Outcollect Settlement Pipeline

Configure the outcollect settlement pipeline by performing the following tasks:

Configuring the Outcollect Settlement Pipeline EDRFactory Registry

Set the EDRFactory Description entry to the TAP container description file as follows: 

Description = ./formatDesc/Formats/TAP3-NG/containerDesc.dsc
Configuring the Outcollect Settlement Pipeline DataDescription Registry Section

Configure the outcollect settlement pipeline DataDescription registry section by setting the stream formats, input mapping and output mapping as follows:

DataDescription
{
   Standard 
   {
   ModuleName = Standard 
   Module
   {
   StreamFormats
   {
     Generic        = ./formatDesc/Formats/TAP3-NG/GenericBlocks.dsc
     TAP            = ./formatDesc/Formats/TAP3-NG/TAP_0312_Blocks.dsc
     EVENT_LOADER   = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER.dsc
     TapHeaderInfo  = ./formatDesc/Formats/TapHeaderInfo/TapHeaderInfo.dsc
   }
   InputMapping
   {
   }
   OutputMapping

   {
     EVENT_LOADER    = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutMap.dsc          
     TapHeaderInfo   = ./formatDesc/Formats/TapHeaderInfo/TapHeaderInfo_OutMap.dsc
   }
   }
   }
}
Configuring the Outcollect Settlement Pipeline Input Processing

Configure input processing for the outcollect settlement pipeline as follows:

  1. Configure the INP_GenericStream input module to map outcollect TAP files into EDR containers.

    1. Set the Grammar registry entry to the name of the TAP input grammar description file: 

      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_InGrammar.dsc

    2. Configure EXT_InFileManager to specify input file information.

Configuring the Outcollect Settlement Pipeline Function Modules

Configure the registry for the following modules:

  • ISC_TAP_0312_InMap, which maps TAP data into the EDR container fields.

  • ISC_ConsolidatedCP, which removes all non-00 impact category charge packets and sets the G/L ID.

    Use the GL_CODE entry to assign the G/L ID for outcollect settlement event balance impacts.

  • FCT_ServiceCodeMap, which maps external service codes to internal service codes. Set MapGroup as follows: 

    MapGroup = OUTCOLLECT

  • FCT_Account, which determines the roaming partner account and associates the EDR with this account.

  • FCT_ExchangeRate, which converts charge amounts in the charge packets to the SDR currency.

  • FCT_ItemAssign, which assigns the bill item associated with the roaming partner account's outcollect service to the EDR.

  • FCT_BillingRecord, which creates the balance impact information from the charge amount provided in the EDR and associates this impact to the bill item. Set the following entries as follows:

    CurrencyType = B
ChargeBreakDownRecord = 980

  • ISC_RollbackSettlement, which rolls back transactions when an error occurs.

Configuring the Outcollect Settlement Pipeline Output Processing

Configure output processing for the outcollect settlement pipeline as follows:

  1. Configure GPRS and GSM EDR splitting.

    1. Create a system brand called GSMR to associate with GSM EDRs, and a system brand called GPRSR to associate with GPRS EDRs.

    2. Define splitting rules for GPRS and GSM EDRs.

    3. Configure FCT_EnhancedSplitting and use the SystemBrand entry to map the system brands to the GPRS and GSM output streams as follows: 

      ModuleName = FCT_EnhancedSplitting
Module
{
     Active          = True 
     DataConnection  = ifw.DataPool.Login 
     DefaultOutput   = GSMOutput 
     SystemBrands 
     {  
        GSMR         = GSMOutput
        GPRSR        = GPRSOutput
     }
}

  2. Configure an output stream to write GSM EDRs to an output file to be processed by Rated Event (RE) Loader by configuring the OUT_GenericStream module.

    1. Set EventType to /event/delayed/session/telco/gsm/roaming.

    2. Set the Grammar registry entry to the RE Loader output grammar description file: 

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc

    3. Configure EXT_OutFileManager to specify output file information.

  3. Configure another output stream to write GPRS EDRs to an output file to be processed by RE Loader by configuring the OUT_GenericStream module.

    1. Set EventType to /event/delayed/session/telco/gprs/roaming.

    2. Set the Grammar registry entry to the RE Loader output grammar description file: 

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc

    3. Configure EXT_OutFileManager to specify output file information.

  4. Configure Event Handler to move outcollect TAP files from the common directory to another directory, from which they are sent to roaming partners.

    1. Add the Events subsection, as shown below, to the EventHandler registry: 

      EventHandler
{
ModuleName      = EVT
Module
{
   Events
   {
     ifw.Pipelines.TAPOutSettlementPipeline.Output.OutputCollection.GSMOutput.Module.OutputStream.Module
     {
       EVT_OUTPUT_FILE_READY = ./bin/move_TapSent.pl
     }
   }
}
}

      where:

      TAPOutSettlementPipeline is the name of the outcollect settlement pipeline.

      GSMOutput is the name of the output stream for GSM events.

    2. Edit the move_TapSent.pl script:

      Edit the following line to specify the common directory where the outcollect TAP files are stored.

      $IN_DIR = "$ENV{IFW_HOME}/data/outcollect/tapout/common";

      Edit this line to specify the directory where the outcollect TAP files will be moved to from the common directory (this is the directory from which outcollect TAP files can be sent to your roaming partner):

      $MOVE_DIR = "$ENV{IFW_HOME}/data/outcollect/tapout/sent";

  5. Configure the OUT_GenericStream module to write the TAP header information to an output file to be used by the RAP processing pipeline.

    1. Set the Grammar registry entry as follows: 

      Grammar = ./formatDesc/Formats/TapHeaderInfo/TapHeaderInfo_OutGrammar.dsc

    2. Configure EXT_OutFileManager to specify output file information.

Configuring Rated Event Loader to Load Settlement Events into the BRM Database

You must configure RE Loader to load settlement events into the BRM database. When you configure RE Loader, you specify information about how to connect to the BRM database, the location of the output files created by the outcollect settlement pipeline, how to process the events in the output file, and so forth.

Configuring Suspense Manager for the Outcollect Settlement Pipeline

You must configure Suspense Manager pipeline components to process TAP files suspended by the outcollect settlement pipeline.

TAP files suspended by the outcollect settlement pipeline are processed by using the following Suspense Manager components:

  • FCT_BatchSuspense, which suspends the TAP files and creates a batch suspense file.

  • Suspended Batch (SB) Loader, which loads the batch suspense file into the BRM database.

  • Suspense Management Center, which is used to query and edit the batch suspense file. After making the necessary corrections, you submit the batch suspense file to be recycled. When the file is submitted for recycling, Suspense Management Center publishes a notification event to notify Pipeline Manager that the batch suspense file is ready for recycling.

  • DAT_Listener, which dequeues the notification event from the BRM database and notifies the DAT_ResubmitBatch module.

  • DAT_ResubmitBatch, which retrieves the suspended batch file from the BRM database and sends it to the outcollect settlement pipeline for processing again.

Configuring the RAP Processing Pipeline

Configure the RAP processing pipeline by performing the following tasks:

Configuring the RAP Processing Pipeline EDRFactory Registry

Set the EDRFactory Description entry to the TAP container description file as follows: 

Description = ./formatDesc/Formats/TAP3-NG/containerDesc.dsc
Configuring the RAP Processing Pipeline DataDescription Registry Section

Configure the RAP processing pipeline DataDescription registry section by setting the stream formats, input mapping and output mapping as follows: 

DataDescription
{
   Standard 
   {
   ModuleName = Standard 
   Module
   {
   StreamFormats
   {
     Generic                = ./formatDesc/Formats/TAP3-NG/GenericBlocks.dsc
     RAP                    = ./formatDesc/Formats/TAP3-NG/RAP_0105_Blocks.dsc
     SUSPENSE_BATCH_RECORD  = ./formatDesc/Formats/SBL/SuspenseBatchRecord.dsc
     EET                    = ./formatDesc/Formats/EET/EET.dsc
   }
   InputMapping
   {
   }
   OutputMapping
   {
     SUSPENSE_BATCH_RECORD  = ./formatDesc/Formats/SBL/SuspenseBatchRecord_OutMap.dsc
     EET                    = ./formatDesc/Formats/EET/EET_OutMap.dsc
}
}
}
}
Configuring the RAP Processing Pipeline Input Processing

Configure the INP_GenericStream input module to map RAP files into EDR containers.

Configure input processing for the RAP processing pipeline as follows:

  1. Set the Grammar registry entry to RAP input grammar description file: 

    Grammar = ./formatDesc/Formats/TAP3-NG/RAP_0105_InGrammar.dsc

  2. Set the following entries to specify information about the TAP Header Information file:

    • Set TapHeaderInfoFilePrefix to the file prefix. For example:

      TapHeaderInfoFilePrefix = test_

    • Set TapHeaderInfoFileSuffix to the file suffix. For example:

      TapHeaderInfoFileSuffix = .thi

    • Set TapHeaderInfoFieldSep to the field separator used in the file. For example:

      TapHeaderInfoFieldSep = ;

    • Set TapHeaderInfoFilePath to the path where the file is stored. For example:

      TapHeaderInfoFilePath = ./data/outcollect/settlement/out/tapheaderinfo

  3. Configure EXT_InFileManager to specify input file information.

Configuring the RAP Processing Pipeline Function Modules

Configure the registry for the following modules:

  • ISC_RAP_0105_InMap, which maps TAP data in the RAP file into the EDR container fields.

  • ISC_DupRAPRecords, which duplicates the EDR. For a fatal RAP file, it sends the duplicate EDR to the suspense batch record output stream. For a severe RAP file, it sends the duplicate EDR to the suspense output stream.

  • ISC_OverrideSuspenseParams, which overrides the suspense parameters.

Configuring the RAP Processing Pipeline Output Processing

Configure output processing for the RAP processing pipeline as follows:

  1. Configure the OUT_GenericStream module to generate the RAP Acknowledgment file.

    1. Set the Grammar registry entry to RAP Acknowledgment output grammar description file: 

      Grammar = ./formatDesc/Formats/TAP3-NG/RAP_0105_AckOutGrammar.dsc

    2. Set DeleteEmptyStream to False.

    3. Configure EXT_OutFileManager to specify output file information.

  2. Configure an output stream to generate output files to be processed by Event Extraction Manager by configuring the OUT_GenericStream module as follows:

    1. Set EventType to /event_extract.

    2. Set the Grammar registry entry to the name of the RE Loader output grammar description file: 

      Grammar = ./formatDesc/Formats/EET/EET_OutGrammar.dsc

    3. Configure EXT_OutFileManager to specify output file information.

  3. Configure another output stream to generate suspense batch record files by configuring the OUT_GenericStream module as follows:

    1. Set EventType to /suspended_batch/rapin.

    2. Set the Grammar registry entry to the suspense batch record output grammar description file: 

      Grammar = ./formatDesc/Formats/SBL/SuspenseBatchRecord_OutGrammar.dsc

    3. Configure EXT_OutFileManager to specify output file information.

Configuring Suspense Manager for the RAP Processing Pipeline

You must configure Suspense Manager pipeline components to process TAP files and records suspended by the RAP processing pipeline.

EDRs suspended by the RAP processing pipeline are processed by using the following Suspense Manager components:

  • FCT_PreSuspense, which appends suspense-related information to all EDRs.

  • FCT_Reject, which sends suspended files to the reject output stream.

  • FCT_Suspense, which routes EDRs from SuspenseCreateOutput to SuspenseUpdateOutput during recycling.

  • Suspended Event (SE) Loader, which loads suspended events from the reject output stream into the BRM database.

  • Suspended Batch (SB) Loader, which loads suspended batch files into the BRM database.

  • Suspense Management Center, which is used to query and edit the suspended events. After making the necessary corrections, you submit the suspended events to be recycled. When suspended events are submitted to be recycled, Suspense Management Center publishes a notification event that is queued in the BRM database to notify Pipeline Manager that events are ready to be recycled.

  • DAT_Listener, which dequeues the notification event from the BRM database and notifies the DAT_Recycle module.

  • DAT_Recycle which creates a parameter file that allows the EXT_InEasyDB module to read suspended usage records associated with a recycle job. It also provides an interface for the INP_Recycle module to provide status updates about the EDR stream.

  • Pre-recycle pipeline, which sends the EDRs to the outcollect rating pipeline.

Configuring Event Extraction Manager to Create the Backout File

Event Extraction Manager creates the backout file used by the backout pipeline.

Configuring the TAP Correction Pipeline

Configure the TAP correction pipeline by performing the following tasks:

Configuring the TAP Correction Pipeline EDRFactory Registry

Set the EDRFactory Description entry to the TAP container description file as follows: 

Description = ./formatDesc/Formats/TAP3-NG/containerDesc.dsc
Configuring the TAP Correction Pipeline DataDescription Registry Section

Configure the TAP correction pipeline DataDescription registry section by setting the stream formats, input mapping and output mapping as follows: 

DataDescription
{
   Standard 
   {
   ModuleName = Standard 
   Module
   {
   StreamFormats
   {
     Generic = ./formatDesc/Formats/TAP3-NG/GenericBlocks.dsc
     TAP = ./formatDesc/Formats/TAP3-NG/TAP_0312_Blocks.dsc
   }
   InputMapping
   {
   }
   OutputMapping
   {
   }
   }
   }
}
Configuring the TAP Correction Pipeline Input Processing

Configure input processing for the TAP correction pipeline as follows:

  1. Configure the INP_GenericStream input module to map TAP files into EDR containers.

    1. Set the Grammar registry entry to the name of the TAP input grammar description file: 

      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_InGrammar.dsc

    2. Configure EXT_InFileManager to specify input file information.

Configure the TAP Correction Pipeline Function Modules

Configure the registry for the following modules:

  1. ISC_TAP_0312_InMap, which maps TAP data into the EDR container fields.

  2. Configure your custom iScript to make corrections to the TAP file.

Configuring the TAP Correction Pipeline Output Processing

Configure output processing for the TAP correction pipeline as follows:

  1. Configure the OUT_GenericStream output module to map the EDR to the TAP files.

    1. Set the Grammar registry entry to TAP output grammar description file: 

      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_OutGrammar.dsc

    2. Configure EXT_OutFileManager to specify output file information.

  2. Configure Event Handler to send TAP files to the outcollect settlement pipeline.

    1. Set the Events subsection in the EventHandler section as follows: 

      EventHandler
{
   ModuleName      = EVT
   Module
   {
     Events
     {
       ifw.Pipelines.TAPCorrectionPipeline.Output.OutputCollection.TAPOutput.Module.OutputStream.Module
      {
        EVT_OUTPUT_FILE_READY = ./bin/move_outcollectTap.pl
      }
     }
   }
}

      where:

      TAPCorrectionPipeline is the name of the TAP correction pipeline.

      TAPOutput is the name of the TAP correction pipeline output stream.

    2. Edit the move_outcollectTap.pl script:

      Edit the following line to specify the common directory where to copy the TAP files:

      my $COPY_DIR = "$ENV{IFW_HOME}/data/outcollect/tapout/common";

      Edit the following line to specify the input directory of the outcollect settlement pipeline:

      my $MOVE_DIR = "$ENV{IFW_HOME}/data/outcollect/settlement/in";

Configuring the Backout Pipeline

Configure the backout pipeline by performing the following tasks:

Configuring the Backout Pipeline DataDescription Registry Section

Configure the backout pipeline DataDescription registry section by setting the stream formats, input mapping and output mapping as follows: 

DataDescription
{
   Standard 
   {
   ModuleName = Standard 
   Module
   {
   StreamFormats
   {
     SOL42_FORINPUT = ./formatDesc/Formats/Solution42/SOL42_V670_REL_FORINPUT.dsc
     EVENT_LOADER   = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER.dsc
   }
   InputMapping
   {
     SOL42_FORINPUT = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InMap.dsc
   }
   OutputMapping
   {
     EVENT_LOADER   = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutMap.dsc
   }
   }
   }
}
Configuring the Backout Pipeline Input Processing

Configure input processing for the backout pipeline as follows:

  1. Configure INP_GenericStream module to map RAP files into EDR containers.

    1. Set the Grammar registry entry to RAP input grammar description file. 

      Grammar = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InGrammar_BACKOUT.dsc

    2. Configure EXT_InFileManager to specify input file information.

Configuring the Backout Pipeline Output Processing

Configure output processing for the backout pipeline as follows:

  1. Configure GPRS and GSM EDR splitting.

    Note:

    If you previously configured GPRS and GSM EDR splitting, you can use the existing system brands and splitting rules. You can skip steps 1.a and 1.b below.

    1. Create a system brand called GSMR for GSM EDRs and a system brand called GPRSR for GPRS EDRs.

    2. Define splitting rules for GPRS and GSM EDRs.

    3. Configure FCT_EnhancedSplitting and use the SystemBrand entry to map the system brands to the GPRS and GSM output streams. For an example configuration, see "Configuring the Outcollect Rating Pipeline Input Processing".

  2. Configure an output stream to write GSM EDRs to an output file to be processed by RE Loader by configuring OUT_GenericStream as follows:

    1. Set EventType to /event/delayed/session/telco/gsm/roaming.

    2. Set the Grammar registry entry to the RE Loader output grammar description file: 

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc

    3. Configure EXT_OutFileManager to specify output file information.

  3. Configure another output stream to write GPRS EDRs to an output file to be processed by RE Loader by configuring OUT_GenericStream as follows:

    1. Set EventType to /event/delayed/session/telco/gprs/roaming.

    2. Set the Grammar registry entry to the RE Loader output grammar description file: 

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc

    3. Configure EXT_OutFileManager to specify output file information.

Configuring Suspense Manager for the Backout Pipeline

It is possible that the backout pipeline is unable to process the Event Extraction Manager output file. When this occurs, the backout pipeline suspends the entire file. To handle suspension in the pipeline, configure the following Suspense Manager pipeline components:

  • FCT_PreSuspense, which appends suspense-related information to all EDRs.

  • FCT_Reject, which sends suspended files to the reject output stream.

  • FCT_Suspense, which routes EDRs from SuspenseCreateOutput to SuspenseUpdateOutput during recycling.