PK SqEoa,mimetypeapplication/epub+zipPKSqEiTunesMetadata.plistx artistName Oracle Corporation book-info cover-image-hash 797659120 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 914223998 publisher-unique-id E25100-01 unique-id 122532805 genre Oracle Documentation itemName Oracle® Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4 releaseDate 2013-03-18T08:21:07Z year 2013 PKLF}xPKSqEMETA-INF/container.xml PKYuPKSqEOEBPS/rmg_nrtrde_about.htm Detecting Roaming Fraud Using NRTRDE

15 Detecting Roaming Fraud Using NRTRDE

This chapter provides an overview of the roaming incollect and outcollect processes for generating and processing roaming usage data for NRTRDE (Near Real-Time Roaming Data Exchange)


Note:

The NRTRDE feature replaces the High Usage Reports (HUR) feature.

Before reading this document, you should be familiar with the following:

About Roaming Data Usage Data for NTRTRDE

In NRTRDE, roaming usage data records are transferred in TD35 file format. A TD35 record is structurally similar to a TAP (Transfer Account Procedure) record and contains basic call details (without the charging information), to allow HPMN (Home Public Mobile Network) operators to quickly analyze the usage data. The actual charge information is still exchanged using TAP records.

Generally, the VPMN (Visited Public Mobile Network) operator generates the TD35 files and sends them to the HPMN operator. The HPMN operator processes the TD35 files and analyzes the roaming usage data to determine any fraudulent activity.

About Handling Roaming Usage Data for NRTRDE

Roaming partners exchange roaming usage data in near real time by sending the data in TD35 file format. Pipeline Manager handles TD35 files as follows:

About Generating Roaming Usage Data for NRTRDE

Figure 15-1 Generating Roaming Usage Data (Outcollect Processing)

Description of Figure 15-1 follows

Figure 15-1 shows a high-level overview of how roaming usage data is generated for NRTRDE during roaming outcollect processing:

  1. CDRs arrive at the splitter pipeline.

  2. The outcollect splitter pipeline converts incoming call data records (CDRs) into event data record (EDR) format and separates the EDRs into home subscribers' EDRs and visiting subscribers' roaming EDRs.

  3. Home subscribers' EDRs are sent to the normal rating pipeline to be rated and to the Rated Event Loader.

    Visiting subscribers' roaming EDRs are sent to the outcollect rating pipeline to be rated. The outcollect rating pipeline rates the visiting subscribers' roaming EDRs and generates TAP files and TD35 files for each roaming partner. A copy of the visiting subscribers' roaming EDRs is sent to the outcollect settlement pipeline from where they are sent to the rated event loader.

  4. The rated event loader send the data to be recorded in the BRM database.

See "About Processing Visiting Subscribers' Roaming Usage" and "Setting Up Pipeline Manager for NRTRDE" for more information.

About Processing Roaming Usage Data for NRTRDE

Figure 15-2 Generating Roaming Usage Data (Incollect Processing)

Description of Figure 15-2 follows

The following is a high-level overview of how roaming usage data is processed for NRTRDE during roaming incollect processing (shown in Figure 15-2):

  1. Incoming TD35 files are sent to the NRTRDE processing pipeline.

  2. The input module uses NRTRDE input grammar to convert the TD35 records into EDR format and performs file and record validations based on the TD35 specifications.

  3. For each TD35 record that fails validation, an NRTRDE error record is created in the Pipeline Manager database. Information stored in the error records is used in generating NRTRDE Error reports. See "About NRTRDE Reports".

  4. For each TD35 file processed, a file processing record is created in the Pipeline Manager database. Information stored in the file processing records is used in generating NRTRDE File Delivery reports. See "About NRTRDE Reports".

About NRTRDE Reports

During roaming incollect processing, the NRTRDE processing pipeline creates NRTRDE error records and NRTRDE file processing records in the Pipeline Manager database. The information stored in these records is used to generate NRTRDE reports. See "Creating NRTRDE Reports" for more information.

Setting Up Pipeline Manager for NRTRDE


Important:

You must have Roaming Manager installed and configured before you configure Pipeline Manager for NRTRDE. See "Installing TAP Roaming Manager" and "Setting Up Roaming for TAP" for more information.

Roaming usage data is transferred in TD35 file format between network operators for NRTRDE. To set up Pipeline Manager for NRTRDE, do the following:

  1. Create NRTRDE tables in the BRM database. See "Creating NRTRDE Tables in the BRM Database" for more information.

  2. Set up Pipeline Manager for generating roaming usage data. See "Setting Up Pipeline Manager for Generating Roaming Usage Data for NRTRDE" for more information.

  3. Set up Pipeline Manager for processing roaming usage data. See "Setting Up Pipeline Manager for Processing Roaming Usage Data for NRTRDE" for more information.

Creating NRTRDE Tables in the BRM Database

NRTRDE File Delivery and NRTRDE Error reports use the following tables located in the BRM database:

  • NRTRDE_FILES

  • NRTRDE_ERRORS

  • NRTRDE_SEQUENCES

Create these tables in your BRM database by manually running each of the SQL commands in the NRTRDE_Tables.sql script. This script is located in the Pipeline_ home/database/Oracle/Scripts directory, where Pipeline_ home is the directory where the Pipeline Manager is installed.

Setting Up Pipeline Manager for Generating Roaming Usage Data for NRTRDE


Note:

Before you set up Pipeline Manager for generating roaming usage date for NRTRDE, you must set up Pipeline Manager for roaming outcollect processing. See the discussion about setting up Pipeline Manager for TAP Outcollect processing in the BRM documentation.

TD35 files are generated during roaming outcollect processing by the outcollect rating pipeline. To configure roaming outcollect processing for TD35 file generation, do the following:

  1. Limit the number of records in a TD35 file. See "Limiting the Number of Records by Configuring a Batch Controller" for more information.

  2. Configure a sequence generation for NRTRDE files. See "Configuring a Sequence Generation for NRTRDE Files" for more information.

  3. Include descriptions for NRTRDE stream format. See "Including NRTRDE Stream Format Descriptions" for more information.

  4. Provide the required EDRs to roaming partner NRTRDE output streams. See "Providing Required EDRs to Roaming Partner NRTRDE Output Streams" for more information.

  5. Configure an NRTRDE output stream for each roaming partner in the outcollect rating pipeline. See "Configuring NRTRDE Output Stream for Roaming Partners" for more information.

Limiting the Number of Records by Configuring a Batch Controller

One of the requirements for NRTRDE is to limit the number of records in a TD35 file to a maximum of 1000 records.

When you have files with a large number of records, use the SplitSol42.sh script to split the files into multiple files and limit the number of records to a maximum of 1000 per TD35 file. You must run SplitSol42.sh on the output files generated by the outcollect splitter pipeline.

See "Controlling Batch Operations" in BRM System Administrator's Guide.

Configure a batch controller to invoke the SplitSol42.sh script as in the following example:

SplitSol42.sh source_directory target_directory

where:

  • source_directory is the source directory

  • target_directory is the input directory of the outcollect rating pipeline.

SplitSol42.sh splits the files in source_directory and puts the new files in target_directory. If a source file contains less than 1000 records, SplitSol42.sh moves the file to the target_directory.

Configuring a Sequence Generation for NRTRDE Files

Configure sequence generation for NRTRDE files as follows:

  1. Using Pricing Center, define a sequence generator for each roaming partner by entering a name and a unique sequence key. See the description on defining a sequence generation" in BRM Pricing Center Online Help.

  2. Configure each sequencer by editing the SequencerPool registry entries of the roaming registry (Pipeline_home/conf/roaming.reg), where Pipeline_home is the directory where Pipeline Manager is installed.

    1. Set the SequencerInstance name to the name of the sequence generator defined in the (previous step using) Pricing Center.

    2. Set the SequencerType registry entry to Generation.

The following sample configuration shows two sequence generators for HPMN operators hpmn01 and hpmn02:

SequencerPool
   {
      SEQ_GEN_NRTRDEOUT_hpmn01
      { 
         Source = Database 
         Controller 
         { 
            SequencerType = Generation
            ReuseGap = True 
            SequenceLength = 7
            DatabaseConnection = ifw.DataPool.Login
         } 
      }
      SEQ_GEN_NRTRDEOUT_hpmn02
      { 
         Source = Database 
         Controller 
         { 
            SequencerType = Generation
            ReuseGap = True 
            SequenceLength = 7
            DatabaseConnection = ifw.DataPool.Login
         } 
      }
}

Including NRTRDE Stream Format Descriptions

Edit the outcollect rating pipeline DataDescription registry entries to include the NRTRDE stream format description as follows:

DataDescription
{
   StreamFormats
   {
      SOL42 = ./formatDesc/Formats/Solution42/SOL42_V670_REL_FORINPUT.dsc
      TAP3 = ./formatDesc/Formats/TAP3/TAP3_v12_Blocks.dsc
      NRTRDE2 = ./formatDesc/Formats/TAP3/NRTRDE2_v01_Blocks.dsc
      SUSPENSE_CREATE_OUTPUT  = ./formatDesc/Formats/SuspenseHandling/SuspendedUsageCreation.dsc
      SUSPENSE_UPDATE_OUTPUT  = ./formatDesc/Formats/SuspenseHandling/SuspendedUsageUpdate.dsc
}
   InputMapping
   {
      SOL42 = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InMap.dsc
   }
   OutputMapping
   {
      SUSPENSE_CREATE_OUTPUT  = ./formatDesc/Formats/SuspenseHandling/SuspendedUsageCreationMapping.dsc
      SUSPENSE_UPDATE_OUTPUT  = ./formatDesc/Formats/SuspenseHandling/SuspendedUsageUpdateMapping.dsc
   }
}

Providing Required EDRs to Roaming Partner NRTRDE Output Streams

The ISC_NRTRDE_EventSplit script is provided for use by roaming outcollect processing to duplicate and route EDRs to the corresponding roaming partner NRTRDE output streams based on the SOURCE_NETWORK EDR field.

Configure ISC_NRTRDE_EventSplit in the outcollect rating pipeline. For example:

NRTRDE_EventSplit
     {
     FileName = ./iScriptLib/iScriptLib_Roaming/ISC_NRTRDE_EventSplit.isc
     }

See the description about ISC_NRTRDE_EventSplit in BRM Configuring Pipeline Rating and Discounting.

Configuring NRTRDE Output Stream for Roaming Partners

Configure an NRTRDE output stream for each roaming partner in the outcollect rating pipeline. For each roaming partner, configure the OUT_GenericStream module registry entries as follows:

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

    Grammar = ./formatDesc/Formats/TAP3/NRTRDE2_v01__OutGrammar.dsc
    
  2. Set the Sequencer registry entry to the name of the sequence generator for generating the sequence number for this roaming partner. See "Configuring a Sequence Generation for NRTRDE Files", described earlier.

  3. Set the Sender registry entry to the VPMN ID sending the TD35 file.

  4. Configure the EXT_OutFileManager registry entries to specify the output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

The following example shows output stream configurations for HPMN operators hpmn01 and hpmn02:

hpmn01NrtrdeOutput
{
ModuleName  = OUT_GenericStream
...
Module
{
   Grammar = ./formatDesc/Formats/TAP3/NRTRDE2_v01_OutGrammar.dsc
   DeleteEmptyStream = False
   Sequencer = SEQ_GEN_NRTRDEOUT_hpmn01
   Sender = PORTL
   Recipient = hpmn01
   OutputStream
   {
      ModuleName = EXT_OutFileManager
      Module
      {
         OutputPath            = ./data/outcollect/nrtrdeout/hpmn01
         OutputPrefix          = NRPORTLhpmn01
         TempPrefix            = tmptest_hpmn01_
         TempDataPath          = ./data/outcollect/nrtrdeout/hpmn01
         TempDataPrefix        = test.hpmn01.tmp.
         TempDataSuffix        = .data
         UseInputStreamName    = [0,0]
         SequencerPrefix       = ""
         AppendSequenceNumber  = True
      }
   }
}
}
hpmn02NrtrdeOutput
{
ModuleName  = OUT_GenericStream
...
Module
{
   Grammar = ./formatDesc/Formats/TAP3/NRTRDE2_v01_OutGrammar.dsc
   DeleteEmptyStream = False
   Sequencer = SEQ_GEN_NRTRDEOUT_hpmn02
   Sender = PORTL
   Recipient = hpmn02
   OutputStream
   {
      ModuleName = EXT_OutFileManager
      Module
      {
         OutputPath            = ./data/outcollect/nrtrdeout/hpmn02
         OutputPrefix          = NRPORTLhpmn02
         TempPrefix            = tmptest_hpmn02_
         TempDataPath          = ./data/outcollect/nrtrdeout/hpmn02
         TempDataPrefix        = test.hpmn02.tmp.
         TempDataSuffix        = .data
         UseInputStreamName    = [0,0]
         SequencerPrefix       = ""
         AppendSequenceNumber  = True
      }
   }
}
}

Setting Up Pipeline Manager for Processing Roaming Usage Data for NRTRDE

TD35 files are processed during roaming incollect processing by the NRTRDE processing pipeline.

To configure the NRTRDE processing pipeline, do the following:


Note:

For an example of NRTRDE processing pipeline configuration, see Pipeline_home/conf/roaming.reg, where Pipeline_home is the directory where Pipeline Manager is installed.

  1. Configure the NRTRDE processing pipeline DataDescription registry entries by setting the stream format as shown in this code sample:

    DataDescription
    {
       StreamFormats
       {
          NRTRDE2  = ./formatDesc/Formats/TAP3/NRTRDE2_v01_Blocks.dsc
       }
       InputMapping
       {
       }
       OutputMapping
       {
       }
    }
    
  2. Configure the NRTRDE processing pipeline input processing as follows:

    1. Set the Grammar registry entry for the INP_GenericStream input module to the NRTRDE input grammar description file with the following command:

      Grammar = ./formatDesc/Formats/TAP3/NRTRDE2_v01_InGrammar.dsc
      
    2. Configure the EXT_InFileManager registry entries to specify information about the NRTRDE input file. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

    The following example shows input processing for the NRTRDE processing pipeline.

    InputModule
    {
       ModuleName = INP_GenericStream
       Module
       {
          DefaultOutput  = DevNull
          Grammar     = ./formatDesc/Formats/TAP3/NRTRDE2_v01_InGrammar.dsc
          InputStream
          {
             ModuleName = EXT_InFileManager
             Module
             {
                InputPath   = ./data/incollect/nrtrdein/in
                InputPrefix = NR
                #InputPrefix = test_
                #InputSuffix = .edr
                DonePath    = ./data/incollect/nrtrdein/done
                DonePrefix  = test_NRTRDEInProcessingPipeline_
                DoneSuffix  = .done
                ErrorPath   = ./data/incollect/nrtrdein/error
                ErrorPrefix = test_NRTRDEInProcessingPipeline_
                ErrorSuffix = .err
                TempPrefix  = temp_NRTRDEInProcessingPipeline_
                Replace     = True
                InputDirEmptyTimeout = 10
             }
          }
       }
    }
    
  3. Configure the ISC_NrtrdeHeaderValidation_v2_01 iScript. For more information on ISC_NrtrdeHeaderValidation_v2_01, see BRM Configuring Pipeline Rating and Discounting.

  4. Configure the ISC_NRTRDE_ErrorReport iScript. For more information on ISC_NRTRDE_ErrorReport, see BRM Configuring Pipeline Rating and Discounting.

Creating NRTRDE Reports

Roaming NRTRDE reports include the following:

Use the NRTRDEReportGen64 utility to generate the "NRTRDE Delivery Report" and the "NRTRDE Error Report".

To run the NRTRDE reports, you use the NRTRDEReportGen64 utility. You can generate the reports for a specific VPMN operator or for all VPMNs. See "NRTRDEReportGen64".

iScripts

BRM provides the following iScripts for use with NRTRDE:


NRTRDE Delivery Report

The NRTRDE File Delivery report file lists all the TD35 files processed by the HPMN. You can generate the report for a specific VPMN operator or for all VPMNs.

Each NRTRDE File Delivery report includes a header record, one or more detail records, and a trailer record.

Header Record

The header record includes the following data:

ND,Version,HPMNId,VPMNId,SeqNo,CreationStartTime,PeriodStartTime,PeriodEndTime

where:

Detail Record

The detail records include the following data:

FileName,ReceivedTime

where:

Trailer Record

The trailer record includes the following data:

END,NumberOfRecords

where:

Delivery Report Example

The following example shows the output of a NRTRDE File Delivery report for HPMN XYZ99 and VPMN ABC01.

ND,1.0,XYZ99,ABC01,00001,20070215020000-0500,20070214000000-0500,20070214235959-0500
NRABC01XYZ990000001,20070214010000-0500
NRABC01XYZ990000002,20070214040000-0500
NRABC01XYZ990000003,20070214070000-0500
NRABC01XYZ990000004,20070214100000-0500
NRABC01XYZ990000005,20070214130000-0500
NRABC01XYZ990000006,20070214160000-0500
NRABC01XYZ990000007,20070214190000-0500
NRABC01XYZ990000008,20070214220000-0500
END,10

NRTRDE File Delivery Report File

NRTRDEReportGen64 generates the NRTRDE File Delivery report and sends the output to a file with the following file name format:

NDxxxxxyyyyySeqNo:

where:


NRTRDE Error Report

The NRTRDE Error report lists the TD35 records that failed the NRTRDE incollect validation process. You can generate the report for a specific VPMN (Visited Public Mobile Network) operator or for all VPMNs. You send this report to the VPMN for corrections.

Each NRTRDE Error report includes a header record, one or more detail records, and a trailer record.

Header Record

The header record includes the following data:

NE,Version,HPMNId,VPMNId,SeqNo,CreationStartTime,PeriodStartTime,PeriodEndTime

where:

Detail Record

The detail records include the following data:

FileName,RecordNo,RecordType,ErrorCode

where:

Trailer Record

The trailer record includes the following data:

END,NumberOfRecords

where:

Error Report Example

The following example shows the output of a NRTRDE Error report for HPMN XYZ99 and VPMN ABC01:

NE,1.0,XYZ99,ABC01,00001,20070215020000-0500,20070214000000-0500,20070214235959-0500
NRABC01XYZ990000004,,,400
NRABC01XYZ990000005,123,MOC,315
NRABC01XYZ990000005,145,MOC,315
NRABC01XYZ990000005,167,MTC,315
NRABC01XYZ990000005,753,GPRS,304,307,308
NRABC01XYZ990000006,,,117
END,8

NRTRDE Error Report File

NRTRDEReportGen64 generates the NRTRDE Error report and sends the output to a file with the following file name format:

NExxxxxyyyyySeqNo:

where:


NRTRDEReportGen64

Use the NRTRDEReportGen64 utility to generate the NRTRDE Delivery Report and the NRTRDE Error Report.

Location

Pipeline_home/bin

where Pipeline_home is the directory where Pipeline Manager is installed.

Syntax

NRTRDEReportGen64 database_access_library server_name user_name password database_name hpmn [vpmn]

Parameters

The parameters for this utility are:

Results

The NRTRDEReportGen64 utility generates the NRTRDE Error report and the NRTRDE File Delivery report with report period start as the previous report's report period end date and report period end as the current date.

PKD^TPKSqE#OEBPS/rmg_tapv311_outcollect_cf.htm Setting Up Pipeline Manager for Roaming Outcollect Processing

8 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 configurations 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 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.

    For more information about configuring a Batch Controller, see "Controlling Batch Operations" in BRM System Administrator's Guide.

  2. Configure the INP_GenericStream input module to map CDR fields to 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. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.


      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

      See "Configuring EDR Input Processing" in BRM Configuring Pipeline Rating and Discounting.


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. See the discussion about creating system brands in BRM Pricing Center Online Help.

    2. Define splitting rules and associate the rules with the system brands. See the discussion about defining splitting types in BRM Pricing Center Online Help.

    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 the EXT_OutFileManager to specify information about the output file. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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 the EXT_OutFileManager to specify information about the output file. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

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 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. See "DAT_InterConnect" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_CarrierIcRating, which adds roaming data to EDRs for rating by the FCT_PreRating and FCT_MainRating modules. See "FCT_CarrierIcRating" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_PreRating, which calculates zones and creates impact categories. See "FCT_PreRating" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_MainRating, which performs the main rating functionality in a pipeline. See "FCT_MainRating" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Rounding, which performs rounding for rating and discounting. See "FCT_Rounding" in BRM Configuring Pipeline 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.

    See "FCT_ExchangeRate" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_MiscOutCollect, which adds BASIC_SERVICE and SUPPLEMENTARY_SERVICE blocks to the EDR container for GSM services. See "ISC_MiscOutcollect" in BRM Configuring Pipeline Rating and Discounting.

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, you do the following:

    1. Create a system brand for each roaming partner. See the discussion about creating system brands in BRM Pricing Center Online Help.

    2. Define splitting rules for each roaming partner. See the discussion about defining splitting types in BRM Pricing Center Online Help.

    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. For more information, see "About Configuring Multiple Instances of Sequencers, Output Streams, or System Brands" in BRM System Administrator's Guide.

      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, define a sequence generator for each roaming partner by entering a name and a unique sequence key. For more information, see the discussion about defining a sequence generation in BRM Pricing Center Online Help.

    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. For more information, see "About Configuring Multiple Instances of Sequencers, Output Streams, or System Brands" in BRM System Administrator's Guide.

    3. Set SequencerInstance registry entry to the name of the sequence generator defined in step 1 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
           } 
      }
      }
      

      For more information about configuring sequencers, see "Checking and Generating Sequence Numbers" in BRM System Administrator's Guide.

  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. For more information, see "About Configuring Multiple Instances of Sequencers, Output Streams, or System Brands" in BRM System Administrator's Guide.

    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. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

      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
      }
              }
           }
      }
      

      For more information, see "Event Handler" in BRM Configuring Pipeline Rating and Discounting.

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

For more information, see "DAT_InterConnect" in BRM Configuring Pipeline Rating and Discounting.

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. See "FCT_PreSuspense" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Reject, which sends suspended EDRs to the reject output stream. See "FCT_Reject" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Suspense, which routes EDRs from SuspenseCreateOutput to SuspenseUpdateOutput during recycling. See "FCT_Suspense" in BRM Configuring Pipeline Rating and Discounting.

  • 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. See "DAT_Listener" in BRM Configuring Pipeline Rating and Discounting.

  • 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. See "DAT_Recycle" in BRM Configuring Pipeline Rating and Discounting.

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

For instructions on how to configure Suspense Manager, see "Configuring Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

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 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 Outcollect Settlement Pipeline Input Processing

Configure input processing for 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. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configuring 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. See "ISC_TAP_0311_InMap" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_ConsolidatedCP, which removes all non '00' impact category charge packets and sets the G/L ID. See "ISC_ConsolidatedCP" in BRM Configuring Pipeline Rating and Discounting.

    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 a internal service codes. Set MapGroup as follows:

    MapGroup = OUTCOLLECT
    

    See "FCT_ServiceCodeMap" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Account, which determines the roaming partner account and associates the EDR with this account. See "FCT_Account" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ExchangeRate, which converts charge amounts in the charge packets to the SDR currency. See "FCT_ExchangeRate" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ItemAssign, which assigns the bill item associated with the roaming partner account's outcollect service to the EDR. See "FCT_ItemAssign" in BRM Configuring Pipeline Rating and Discounting.

  • 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
    

    See "FCT_BillingRecord" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_RollbackSettlement, which rolls back transactions when an error occurs. See "ISC_RollbackSettlement" in BRM Configuring Pipeline Rating and Discounting.

Configuring Outcollect Settlement Pipeline Output Processing

Configure output processing for 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. See the discussion about creating system brands in BRM Pricing Center Online Help.

    2. Define splitting rules for GPRS and GSM EDRs. See the discussion about defining splitting types in BRM Pricing Center Online Help.

    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 RE Loader by configuring the OUT_GenericStream module:

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

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

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc
      
    3. Configure EXT_OutFileManager to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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 entry to RE Loader output grammar description file.

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc
      
    3. Configure EXT_OutFileManager to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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.

      For more information, see "Event Handler" in BRM Configuring Pipeline Rating and Discounting.

    2. Edit the move_TapSent.pl script:

      Edit this 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 TAP3 header information to an output file to be used by the RAP processing pipeline:

    1. Set the Grammar entry as follows:

      Grammar = ./formatDesc/Formats/TapHeaderInfo/TapHeaderInfo_OutGrammar.dsc
      
    2. Configure EXT_OutFileManager to specify output file information. See "EXT_OutFileManager"in BRM Configuring Pipeline Rating and Discounting.

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

You must configure the 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.

For complete details on how to configure RE Loader, see "Configuring Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.

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:

  • The FCT_BatchSuspense module, which suspends the TAP files and creates a batch suspense file. See "FCT_BatchSuspense" in BRM Configuring Pipeline Rating and Discounting.

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

  • The 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.

  • The DAT_Listener module, which dequeues the notification event from the BRM database and notifies the DAT_ResubmitBatch module. See "DAT_Listener" in BRM Configuring Pipeline Rating and Discounting.

  • The DAT_ResubmitBatch module, which retrieves the suspended batch file from the BRM database and sends it to the outcollect settlement pipeline for processing again. See "DAT_ResubmitBatch" in BRM Configuring Pipeline Rating and Discounting.

For instructions on how to configure Suspense Manager, see "Configuring Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

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 input processing for the RAP processing pipeline as follows:

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

    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. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configuring the RAP Processing Pipeline Function Modules

Configure the registry for the following modules:

  • ISC_RAP_0105_InMap module, which maps TAP data in the RAP file into the EDR container fields. See the discussion about ISC_RAP_0105_InMap in BRM Configuring Pipeline Rating and Discounting.

  • ISC_DupRAPRecords module, 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. See "ISC_DupRAPRecords" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_OverrideSuspenseParams module, which overrides the suspense parameters. See "ISC_OverrideSuspenseParams" in BRM Configuring Pipeline Rating and Discounting.

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 Acknowledgement file:

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

      Grammar = ./formatDesc/Formats/TAP3-NG/RAP_0105_AckOutGrammar.dsc
      
    2. Set DeleteEmptyStream to False.

    3. Set EXT_OutFileManager entries to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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 Grammar registry entry to the name of the RE Loader output grammar description file:

      Grammar = ./formatDesc/Formats/EET/EET_OutGrammar.dsc
      
    3. Set EXT_OutFileManager entries to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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 Grammar entry to the suspense batch record output grammar description file:

      Grammar = ./formatDesc/Formats/SBL/SuspenseBatchRecord_OutGrammar.dsc
      
    3. Set EXT_OutFileManager entries to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

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. See "FCT_PreSuspense" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Reject, which sends suspended files to the reject output stream. See "FCT_Reject" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Suspense, which routes EDRs from SuspenseCreateOutput to SuspenseUpdateOutput during recycling. See "FCT_Suspense" in BRM Configuring Pipeline Rating and Discounting.

  • 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 module, which dequeues the notification event from the BRM database and notifies the DAT_Recycle module.

  • DAT_Recycle module, 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.

For instructions on how to configure Suspense Manager, see "Configuring Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

Configuring Event Extraction Manager to Create the Backout File

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

To configure Event Extraction Manager, see "Using Event Extraction Manager" in BRM Setting Up Pricing and Rating.

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 entries to specify input file information. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configure the TAP Correction Pipeline Function Modules

Configure the registry for the following modules:

  1. ISC_TAP_0312_InMap module, which maps TAP data into the EDR container fields. See the discussion about ISC_TAP_0312_InMap in BRM Configuring Pipeline Rating and Discounting.

  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 Grammar registry entry to TAP output grammar description file.

      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_OutGrammar.dsc
      
    2. Set EXT_OutFileManager entries to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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 this line to specify the common directory where to copy the TAP files:

      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 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. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

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 a) and b) below.

    1. Create a system brand called GSMR for GSM EDRs and a system brand called GPRSR for GPRS EDRs. See the discussion about creating system brands in BRM Pricing Center Online Help.

    2. Define splitting rules for GPRS and GSM EDRs. See the discussion about defining splitting types in BRM Pricing Center Online Help.

    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 module as follows:

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

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

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc
      
    3. Configure EXT_OutFileManager to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

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

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

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

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

    3. Configure EXT_OutFileManager to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

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, you must configure the following Suspense Manager pipeline components:

  • FCT_PreSuspense appends suspense-related information to all EDRs. See "FCT_PreSuspense" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Reject sends suspended file to the reject output stream. See "FCT_Reject" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Suspense routes EDRs from SuspenseCreateOutput to SuspenseUpdateOutput during recycling. See "FCT_Suspense" in BRM Configuring Pipeline Rating and Discounting.

For instructions on how to configure Suspense Manager, see "Configuring Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

PK`**PKSqEOEBPS/rmg_tapv311_incollect.htm About Processing Home Subscribers' Roaming Usage

3 About Processing Home Subscribers' Roaming Usage

This chapter describes the roaming incollect process in Oracle Communications Billing and Revenue Management (BRM) for rating home subscribers' roaming usage.


Important:

  • The following sections describe the incollect process for processing TAP files only.

  • To process TAP files, TAP Roaming Manager requires Suspense Manager, Rated Event (RE) Loader, and InterConnect Manager to rate roaming usage. Suspense Manager, RE Loader, and InterConnect Manager are not part of TAP Roaming Manager and require separate licenses. You must install these supporting managers to rate roaming events. See "About Suspense Manager" and "Understanding Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.


Before reading this document, you should be familiar with the following:

Understanding Roaming Incollect Architecture and Process Flow

You use roaming incollect processing to process TAP files that contain call event detail records (TAP records) for all roaming activities performed by your subscribers on your roaming partners' networks. The incollect process architecture primarily consists of the validation, reprice, and settlement pipelines. These pipelines perform the following tasks:

Figure 3-1 depicts a high-level overview of the roaming incollect process architecture:

Figure 3-1 Roaming Incollect Process Architecture

Description of Figure 3-1 follows

As the above figure illustrates, incoming TAP files are handled during the incollect process as follows:

  1. The validation pipeline converts the TAP records in the TAP files into event data record (EDR) format and performs fatal error and severe error validations of the TAP file. For each file, one of the following actions is taken:

    • If a fatal error validation failure occurs, the entire TAP file is rejected, and a fatal error RAP file is created.

    • If a severe error validation failure occurs, only those records that fail are rejected, and a severe error RAP file is created.

    • If the TAP file has a sequence number greater than the one expected, a missing error RAP file is created and the TAP file is processed.

    • TAP records that pass validation are sent to an output file. A copy of the output file is sent to the reprice and settlement pipelines for further processing.

    For more information, see "How Roaming Usage Data Is Validated".

  2. The reprice pipeline processes the validation pipeline output file and rates the roaming usage events using the subscriber's roaming plan. Rated events are loaded into the BRM database by RE Loader.

    If the reprice pipeline fails to rate an event, the event is suspended and loaded into the BRM database using Suspended Event (SE) Loader. Using Suspense Management Center, the suspended events can be corrected and recycled to the reprice pipeline to be rated again.

    See "About Charging Your Subscribers for Their Roaming Usage" for more information.

  3. The settlement pipeline processes the validation output file and creates settlement events by associating the rated events with the roaming partner account in the BRM database. Settlement events are then loaded into the BRM database by RE Loader.

    If the settlement pipeline fails to create settlement events for any record, the pipeline rejects all the records in the file and the entire file is suspended and loaded into the BRM database. The suspended file can be corrected and recycled back to the settlement pipeline by using Suspense Manager.

    For more information, see "How Settlement Events for Incollect Roaming Charges Are Created".

  4. The Stop RAP Generator pipeline collects information on the incoming TAP files using the StopRapGen utility and generates the Stop Return RAP files to be sent to those visited network operators who have not provided the TAP files in seven days. The Stop Return RAP files sent to the visited network operator are loaded into the database by the UpdateTapInfo_StopRapout iScript.

    See "About Generating Stop Return RAP Files" for more information.

For detailed information on configuring incollect processing, see "Setting Up Pipeline Manager for Roaming Incollect Processing".

How Roaming Usage Data Is Validated

The validation pipeline processes TAP files as follows:

For information about configuring the validation pipeline, see "Configuring the Validation Pipeline".

About Validation Error Codes

When a TAP file validation failure occurs, Pipeline Manager reports an error code and a description of the error. The error codes are categorized as fatal (ERR_TAP3_FATAL), severe (ERR_TAP3_SEVERE), or warning (ERR_TAP3_WARNING). The description of the error includes the TAP field name, TAP field numeric ID, TD57 error code, and a description of the failure.

The following is an example of a fatal validation error:

Pipeline Error Name:

 ERR_TAP3_FATAL

Pipeline Error Description:

TAP Field Name: AccountingInfo, TAP Field Id: 15, TAP Error: 30, No Taxation group present and batch contains taxes.

TAP Validations That Are Not Supported

The ISC_TAP_0312_Validations module does not support all the TAP validations. For instance:

  • Syntax error validations on Integer fields that are handled by the parser.

  • Validations based on the roaming agreements.

  • Validations that are not possible due to pipeline architecture limitations.

The following tables list the validations that are not performed by the ISC_TAP_0312_Validations module. You can implement these validations by writing your own custom iScript or by adding these validations to the ISC_TAP_0312_Validations module.

Syntax Error Validations on Integer Fields

Table 3-1 lists the syntax error validations on integer fields.

Table 3-1 Syntax Error Validations on Integer Fields

TAP FieldError CodeTraffic TypeSeverityDescription

Action Code

10

SS

Severe

Syntax error.

Advised Charge

10

CONTENT

Severe

Syntax error.

Bearer Service Code

10

MOC, MTC

Severe

Syntax error.

Bearer Service Code

11

SS

Warning

Syntax error.

Call Event Details Count

10

AUDIT

Fatal

Syntax error.

Call Reference

10

MOC, MTC, SS, LCS

Severe

Syntax error.

Call Type Level 1

10

MOC, GPRS

Severe

Syntax error.

Call Type Level 2

10

MOC, GPRS

Severe

Syntax error.

Call Type Level 3

10

MOC, GPRS

Severe

Syntax error.

Called Place

10

MOC

Warning

Syntax error.

Called Region

10

MOC

Warning

Syntax error.

CAMEL Invocation Fee

10

MOC, MTC, GPRS

Severe

Syntax error.

CAMEL Service Key

10

MOC, MTC, GPRS

Warning

Syntax error.

CAMEL Service Level

10

MOC, MTC, GPRS

Severe

Syntax error.

Cause For Termination

10

MOC, MTC, GPRS

Severe

Syntax error.

Cell Identity

10

MOC, MTC, SS, GPRS

Warning

Syntax error.

Charge

10

CALLS

Severe

Syntax error.

Charge Refund Indicator

10

CONTENT

Severe

Syntax error.

Chargeable Units

10

CALLS

Severe

Syntax error.

Charged Party Id Type

10

CONTENT

Severe

Syntax error.

Charged Party Status

10

SCU

Severe

Syntax error.

Charged Units

10

CALLS

Warning

Syntax error.

Charging ID

10

GPRS

Severe

Syntax error.

CLIR Status Indicator

10

MOC, MTC, SCU

Warning

Syntax error.

Commission

10

CONTENT

Severe

Syntax error.

Content Charging Point

10

CONTENT

Severe

Syntax error and more than one timestamp present within Content Transaction Basic Info.

Content Charging Point

11

CONTENT

Warning

Syntax error and only one timestamp present within Content Transaction Basic Info.

Content Provider Id Type

10

CONTENT

Warning

Syntax error.

Content Provider Id Type

11

LCS

Severe

Syntax error.

Content Provider Identifier

10

CONTENT

Warning

Syntax error.

Content Provider Name

10</p>

CONTENT

Severe

Syntax error.

Content Transaction Code

10

CONTENT

Severe

Syntax error.

Content Transaction Type

10

CONTENT

Severe

Syntax error.

CSE Information

10

CALLS

Warning

Syntax error.

Customer Id Type

10

LCS

Severe

Syntax error.

Data Volume Incoming

10

GPRS, CONTENT

Severe

Syntax error.

Data Volume Outgoing

10

GPRS, CONTENT

Severe

Syntax error.

Default Call Handling Indicator

10

MOC, MTC, GPRS

Warning

Syntax error.

Discount Code

10

CALLS

Severe

Syntax error.

Discount Code

11

ACCTNG

Fatal

Syntax error.

Discount Rate

10

ACCTNG

Fatal

Syntax error.

Discount Value

10

CALLS

Severe

Syntax error.

Discountable Amount

10

CALLS

Severe

Syntax error.

Equipment Id

10

CONTENT

Warning

Syntax error.

Equipment Id Type

10

CONTENT, LCS

Warning

Syntax error.

Exchange Rate

10

ACCTNG

Fatal

Syntax error.

Exchange Rate Code

10

ACCTNG

Fatal

Syntax error.

Exchange Rate Code

11

CALLS

Severe

Syntax error.

Fixed Discount Value

10

ACCTNG

Fatal

Syntax error.

Fixed Network User Rate

10

MOC, MTC

Warning

Syntax error.

Home Id Type

10

CONTENT, LCS

Severe

Syntax error.

Home Identifier

10

CONTENT

Severe

Syntax error.

Home Location Description

10

CALLS

Warning

Syntax error.

IMS Signalling Context

10

GPRS

Severe

Syntax error.

ISP Id Type

10

CONTENT

Warning

Syntax error.

ISP Identifier

10

CONTENT

Warning

Syntax error.

Location Area Code

10

MOC, MTC, SS, GPRS

Warning

Syntax error.

Location Area Code

10

MOC, MTC, SS, GPRS

Warning

Syntax error.

Location Id Type

10

CONTENT

Warning

Syntax error.

Location Id Type

10

CONTENT

Warning

Syntax error.

Location Identifier

10

CONTENT

Warning

Syntax error.

Message Description

10

MESS DESC

Warning

Syntax error.

Message Description Code

10

MESS DESC, SCU

Warning

Syntax error.

Message Status

10

SCU

Severe

Syntax error.

Message Type

10

SCU

Severe

Syntax error.

Network Id Type

10

CONTENT

Warning

Syntax error.

Network Init. PDP Context

10

GPRS

Severe

Syntax error.

Number Of Decimal Places

10

ACCTNG

Fatal

Syntax error.

Object Type

10

CONTENT

Severe

Syntax error.

Paid Indicator

10

CONTENT

Severe

Syntax error.

Payment Method

10

CONTENT

Warning

Syntax error.

Priority Code

10

SCU

Severe

Syntax error.

Release Version Number

10

NOTIFICTN, BTCH CTRL

Fatal

Syntax error.

Serving Location Description

10

MOC, MTC, SS, GPRS

Severe

Syntax error.

SMS Destination Number

10

MOC

Severe

Syntax error.

SMS Originator

10

MTC

Warning

Syntax error.

Specification Version Number

10

NOTIFICTN, BTCH CTRL

Fatal

Syntax error.

TAP Decimal Places

10

ACCTNG

Fatal

Syntax error.

Tax Rate Code

10

ACCTNG

Fatal

Syntax error.

Tax Rate Code

11

CALLS

Severe

Syntax error.

Tax Value

10

CALLS

Severe

Syntax error.

Taxable Amount

10

CALLS

Severe

Syntax error.

Total Advised Charge

10

AUDIT

Fatal

Syntax error.

Total Advised Charge Refund

10

AUDIT

Fatal

Syntax error.

Total Call Event Duration

10

MOC, MTC, GPRS

Severe

Syntax error.

Total Charge

10

AUDIT

Fatal

Syntax error.

Total Charge Refund

10

AUDIT

Fatal

Syntax error.

Total Commission

10

AUDIT

Fatal

Syntax error.

Total Commission Refund

10

AUDIT

Fatal

Syntax error.

Total Data Volume

10

CONTENT

Severe

Syntax error.

Total Discount Refund

10

AUDIT

Fatal

Syntax error.

Total Discount Value

10

AUDIT

Fatal

Syntax error.

Total Tax Refund

10

AUDIT

Fatal

Syntax error.

Total Tax Value

10

AUDIT

Fatal

Syntax error.

Total Transaction Duration

10

CONTENT

Severe

Syntax error.

Transaction Authorization Code

10

CONTENT

Warning

Syntax error.

Transaction Description Suppression

10

CONTENT

Warning

Syntax error.

Transaction Detail Description

10

CONTENT

Warning

Syntax error.

Transaction Identifier

10

CONTENT

Severe

Syntax error.

Transaction Short Description

10

CONTENT

Warning

Syntax error.

Transaction Status

10

CONTENT

Severe

Syntax error.

Transparency Indicator

10

MOC, MTC

Severe

Syntax error.

User Protocol Indicator

10

MOC, MTC

Severe

Syntax error.

UTC Time Offset Code

10

NETWORK

Fatal

Syntax error.

UTC Time Offset Code

11

CALLS

Severe

Syntax error.


Out-of-Range Validations on Date Fields

Table 3-2 lists the out-of-range validations on date fields.

Table 3-2 Out-of-Range Validations on Date Fields

TAP FieldError CodeTraffic TypeSeverityDescription

Actual Delivery Timestamp

20

CONTENT

Severe

Value out of range and timestamp referenced as Charging Point.

Actual Delivery Timestamp

21

CONTENT

Warning

Value out of range and timestamp not referenced as Charging Point.

Call Event Start Timestamp

20

MOC, MTC, GPRS

Severe

Value out of range.

Charge Detail Timestamp

20

CALLS

Severe

Value out of range.

Charging Timestamp

20

CALLS

Severe

Value out of range.

Completion Timestamp

20

SCU

Warning

Value out of range and charging point is 'D'.

Completion Timestamp

21

SCU

Severe

Value out of range and charging point is 'C'

Deposit Timestamp

20

SCU

Warning

Value out of range and charging point is 'C'.

Deposit Timestamp

21

SCU

Severe

Value out of range and charging point is 'D'.

Earliest Call Timestamp

20

AUDIT

Warning

Value out of range.

File Available Timestamp

20

BTCH CTRL

Fatal

Value out of range.

File Available Timestamp

21

NOTIFICTN

Warning

Value out of range.

File Creation Timestamp

20

NOTIFICTN, BTCH CTRL

Warning

Value out of range.

Latest Call Timestamp

20

AUDIT

Warning

Value out of range.

Order Placed Timestamp

20

CONTENT

Severe

Value out of range and timestamp referenced as Charging Point.

Order Placed Timestamp

21

CONTENT

Warning

Value out of range and timestamp not referenced as Charging Point.

PDP Context Start Timestamp

20

GPRS

Warning

Value out of range.

Requested Delivery Timestamp

20

CONTENT

Severe

Value out of range and timestamp referenced as Charging Point.

Requested Delivery Timestamp

21

CONTENT

Warning

Value out of range and timestamp not referenced as Charging Point.

Transfer Cut Off Timestamp

20

BTCH CTRL

Fatal

Value out of range.


Validations Involving Bilateral Agreement

Table 3-3 lists the validations involving bilateral agreement.

Table 3-3 Validations Involving Bilateral Agreement

TAP FieldError CodeTraffic TypeSeverityDescription

Accounting Information

33

TFBATCH

Fatal

Item TAP Currency not present and currency other than SDR specified in roaming agreement.

AUDIT Control Information

36

TFBATCH

Fatal

Item Total Tax Refund present and use of Content Transaction not bilaterally agreed.

AUDIT Control Information

37

TFBATCH

Fatal

Item Total Discount Refund present and use of Content Transaction not bilaterally agreed.

AUDIT Control Information

38

TFBATCH

Fatal

Group Total Advised Charge Value present and use of Content Transaction not bilaterally agreed.

Call Event Details

32

TFBATCH

Severe

Service Centre Usage present although not agreed bilaterally.

Call Event Details

34

TFBATCH

Severe

Content Transaction present although not agreed bilaterally.

Call Event Details

35

TFBATCH

Severe

GPRS Call present although not agreed bilaterally.

Call Event Details

36

TFBATCH

Severe

Location Service present although not agreed bilaterally

CAMEL Invocation Fee

200

MOC, MTC, GPRS

Severe

CAMEL Invocation Fee not in line with roaming agreement

CAMEL Service Used

41

MOC, MTC, GPRS

Severe

Tax Information missing within the group and CAMEL Invocation Fee is greater than zero and taxation is expected according to roaming agreement.

CAMEL Service Used

42

MOC, MTC, GPRS

Severe

Tax Information present within the group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is greater than zero.

CAMEL Service Used

43

MOC, MTC, GPRS

Warning

Tax Information present within the group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is not greater than zero.

Charge

100

CALLS

Severe

Charge not in line with roaming agreement.

Charge Information

34

CALLS

Severe

Group Tax Information missing within group but expected in accordance with roaming agreement for that particular call. Tax Information group missing must be interpreted as Tax Value zero.

Charge Information

35

CALLS

Severe

Group Discount Information missing within group but expected in accordance with roaming agreement.

Charge Information

38

MOC, MTC

Severe

Breakout of Charge Types AIR (01) and/or TOLL (03) not present on a duration based charge, but expected in accordance with roaming agreement; i.e., only Charge Type 00 present within group. This validation rule can be applied only where bilaterally agreed

Charge Information

39

MOC, MTC

Severe

In accordance with roaming agreement, charges are defined in individual Charge Types, but the Charge for Charge Type 00 does not equal sum of Charges for the other Charge Types as stated within roaming agreement. This validation rule can be applied only w

Charge Information

40

CALLS

Severe

Group Tax Information present within group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is greater than 0 (zero).

Charge Information

41

CALLS

Warning

Group Tax Information present within group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is not greater than 0 (zero).

Chargeable Subscriber

32

MOC, MTC, SS, GPRS

Severe

MSISDN missing within group but expected in accordance with roaming agreement.

Charged Party Identifier

200

CONTENT

Severe

Item is an IMSI of a known network operator and initial characters are different from the network operator's MCC + MNC, or not as bilaterally agreed.

Customer Identifier

200

LCS

Severe

Item is an IMSI of a known network operator and initial characters are different from the network operator's MCC + MNC, or not as bilaterally agreed

Discount Code

200

CALLS

Severe

Referenced discount is not in line with roaming agreement.

Discountable Amount

22

CALLS

Severe

Discountable Amount is not in line with roaming agreement.

Geographical Location

31

MOC, MTC, SS, GPRS

Severe

Serving BID missing within group but expected in accordance with roaming agreement.

Geographical Location

32

MOC, MTC, SS, GPRS

Severe

Serving Location Description missing within group but expected in accordance with roaming agreement

IMSI

200

CALLS

Severe

First characters are different from home operators MCC + MNC, or not as bilaterally agreed (e.g., if the recipient has not been allocated a MCC and MNC).

Location Information

31

MOC, MTC, SS, GPRS

Severe

Group Geographical Information missing but Serving BID expected in accordance with roaming agreement.This validation rule can be applied only where bilaterally agreed between Sender and Recipient

Location Information

32

MOC, MTC, SS, GPRS

Severe

Group Geographical Information missing but Serving Location Description expected in accordance with roaming agreement.This validation rule can be applied only where bilaterally agreed between Sender and Recipient.

MSISDN

10

MOC, MTC, SS, GPRS

Warning

Syntax error and item MSISDN not expected in accordance with roaming agreement.

MSISDN

20

MOC, MTC, SS, GPRS

Warning

Number not represented in international format and MSISDN not expected in accordance with roaming agreement.

Operator Specific Information

30

ALL

Warning

Item is present without bilateral agreement

SCU Charge Type

32

SCU

Severe

Item Distance Charge Band Code missing within group and distance defined as a pricing parameter within SMS bilateral agreement.

Serving Network

20

MOC, MTC, SS, SCU, GPRS

Severe

Value out of range, i.e. it is neither a TADIG PMN Code nor a bilaterally agreed value.

TAP Currency

200

ACCTNG

Fatal

TAP Currency not in line with bilateral agreement.

Tax Rate Code

200

CALLS

Severe

The referenced Tax Rate is not in line with the roaming agreement at the corresponding call date. Note that, where variable tax rates apply to the call/event the exact validation of the tax rate may not be possible and, therefore, cannot be carried out.

Tax Value

200

CALLS

Severe

Tax Value is not in line with the roaming agreement at the corresponding call event date.

Taxable Amount

100

CALLS

Severe

Taxable Amount not in line with roaming agreement.


Validations That Require Additional Component Involvement

Table 3-4 lists the validations that require additional component involvement.

Table 3-4 Validations That Require Additional Component Involvement

Invalid or non transferable Supplementary Service Code and Action code combination present within group.

TAP FieldError CodeTraffic TypeSeverityDescription

Actual Delivery Timestamp

200

CONTENT

Severe

Actual Delivery Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file and the timestamp is referenced as the Charging Point.

Batch Control Information

37

TFBATCH

Warning

File Sequence Number previously received and rejected with fatal error, therefore RAP File Sequence Number expected but not present.

Batch Control Information

40

TFBATCH

Warning

RAP File Sequence Number present although File Sequence Number has not previously been rejected with a fatal error (e.g. previously missing or new files).

Call Event Start Timestamp

200

MOC, MTC, GPRS

Severe

Call Event Start Timestamp before the commercial roaming start date for the specific network service and the TAP file is not a test file

Call Type Level 1

102

MOC, GPRS

Severe

Item not specified according to how the call has been priced (as verified against the Sender's IOT).

Call Type Level 2

100

MOC, GPRS

Severe

Item not specified according to how the call has been priced (as verified against the Sender's IOT).

Call Type Level 3

100

MOC, GPRS

Severe

Item not specified according to how the call has been priced (as verified against the Sender's IOT).

Charging Timestamp

200

SS, LCS

Severe

Charging Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file.

Completion Timestamp

200

SCU

Severe

Completion Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file.

Content Transaction Basic Info

31

CONTENT

Severe

Item RAP File Sequence Number missing and Content Transaction previously received and rejected.

Content Transaction Basic Info

32

CONTENT

Warning

Item RAP File Sequence Number present and Content Transaction not previously received and rejected.

Content Transaction Basic Info

33

CONTENT

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

Deposit Timestamp

200

SCU

Severe

Deposit Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file.

Exchange Rate

200

ACCTNG

Fatal

Exchange Rate less than expected and referenced by one or more Call Event Details.

Exchange Rate Code

202

CALLS

Warning

The Exchange Rate referenced by Exchange Rate Code in Call Event Details is greater than expected.

File Sequence Number

200

NOTIFICTN, BTCH CTRL

Warning

File sequence number of the received file is greater than that expected.

File Sequence Number

201

NOTIFICTN, BTCH CTRL

Fatal

File sequence number of the received file has already been received and successfully processed and the file is not a copy of the original file.

GPRS Basic Call Information

31

GPRS

Severe

GPRS Call is being resubmitted and RAP File Sequence Number is missing within group.

GPRS Basic Call Information

38

GPRS

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

GPRS Basic Call Information

41

GPRS

Warning

Item RAP File Sequence Number present and call not previously received and rejected.

Location Service

32

LCS

Severe

Item RAP File Sequence Number missing and Location Service previously received and rejected.

Location Service

33

LCS

Warning

Item RAP File Sequence Number present and Location Service not previously received and rejected.

Location Service

34

LCS

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

MO Basic Call Information

33

MOC

Severe

Item RAP File Sequence Number missing and call previously received and rejected.

MO Basic Call Information

34

MOC

Warning

Item RAP File Sequence Number present and call not previously received and rejected.

MO Basic Call Information

36

MOC

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

MT Basic Call Information

33

MTC

Severe

Item RAP File Sequence Number missing and call previously received and rejected.

MT Basic Call Information

34

MTC

Warning

Item RAP File Sequence Number present and call not previously received and rejected.

MT Basic Call Information

35

MTC

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

Notification

37


Warning

File Sequence Number previously received and rejected with fatal error, therefore RAP File Sequence Number expected but not present.

Notification

38


Warning

RAP File Sequence Number present although File Sequence Number has not previously been rejected with a fatal error (e.g. previously missing or new files).

Order Placed Timestamp

200

CONTENT

Severe

Order Placed Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file.

Requested Delivery Timestamp

200

CONTENT

Severe

Requested Delivery Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file.

Service Centre Usage

31

SCU

Severe

Item RAP File Sequence Number missing and SCU previously received and rejected.

Service Centre Usage

32

SCU

Warning

Item RAP File Sequence Number present and SCU not previously received and rejected.

Service Centre Usage

37

SCU

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

Supplementary Service Event

31

SS

Severe

Item RAP File Sequence Number missing and SS previously received and rejected.

Supplementary Service Event

32

SS

Warning

Item RAP File Sequence Number present and SS not previously received and rejected.

Supplementary Service Event

35

SS

Warning

Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).

Supplementary Service Used

101

SS

Severe


Other Validations That Are Not Supported

Table 3-5 Other Validations That Are Not Supported

TAP FieldError CodeTraffic TypeSeverityDescription

CAMEL Invocation Fee

201

MOC, MTC, GPRS

Severe

CAMEL Invocation Fee is greater than 0 (zero) and CAMEL call not expected.

CAMEL Service Used

31

MOC

Severe

CAMEL Destination Number missing within group although number was modified by CAMEL (logical group 3G CAMEL Destination).

CAMEL Service Used

37

GPRS

Severe

Group GPRS Destination missing within group although APN was modified by CAMEL (logical group 3G CAMEL Destination).

Charged Party Identifier

10

CONTENT

Severe

Syntax error.

Charged Party Identifier

20

CONTENT

Severe

Value out of range and item is a MSISDN.

Customer Identifier

20

LCS

Severe

Value out of range and item is a MSISDN.

Destination Network

10

SCU, MOC

Warning

Syntax error.

Destination Network

20

SCU, MOC

Warning

Value out of range.

Dialled Digits

20

MOC

Severe

Value out of range.

Discount Value

22

CALLS

Severe

Where the associated Discount Code relates to a Discount Rate, the Discount Value does not correspond to the Discountable Amount and Discount Rate.

Distance Charge Band Code

20

SCU

Severe

Value out of range.

Equipment Id

100

CONTENT, LCS

Warning

Item content does not match Equipment Id Type.

ESN

10

MOC, MTC, SS, GPRS

Warning

Syntax error.

ESN

20

MOC, MTC, SS, GPRS

Warning

Value out of range.

GPRS Call

200

GPRS

Warning

Number of GPRS partials received exceeds limit defined by BARG in BA.12.

Home BID

10

CALLS

Warning

Syntax error.

Home BID

20

CALLS

Warning

Value out of range.

IMEI

10

MOC, MTC, SS, GPRS

Warning

Syntax error.

IMEI

20

MOC, MTC, SS, GPRS

Warning

Value out of range.

IMSI

10

CALLS

Severe

Syntax error.

IMSI

20

CALLS

Severe

Value out of range.

MDN

10

MOC, MTC, SS, GPRS

Warning

Syntax error.

MDN

20

MOC, MTC, SS, GPRS

Warning

Value out of range.

MIN

20

CALLS

Severe

Value out of range.

Network Access Identifier

20

GPRS

Severe

Value out of range.

Originating Network

10

MTC, SCU

Warning

Syntax error.

Originating Network

20

MTC, SCU

Warning

Value out of range.

Serving BID

20

MOC, MTC, SS, GPRS

Severe

Value out of range.

Serving BID

21

MOC, MTC, SS, GPRS

Severe

Value not assigned to Sender.

Supplementary Service Parameters

10

SS

Warning

Syntax error.

Supplementary Service Parameters

20

SS

Warning

Value out of range.

Tax Value

22

CALLS

Severe

Where the associated Tax Rate Code relates to a Tax Rate, the Tax Value does not correspond to the Taxable Amount (or Charge where no Taxable Amount present) and Tax Rate.


Transmitting TAP Files to the Validation Pipeline

When you receive TAP files from a clearing house or your roaming partner, you must put the files in the input directory of the validation pipeline for the pipeline to process them. If your mediation system does not automatically place the TAP files in this directory, you can configure a Batch Controller and write a custom Batch Handler to move the TAP files to the validation pipeline input directory.

For more information about Batch Controllers and Batch Handlers, see "Controlling Batch Operations" in BRM System Administrator's Guide.

About Charging Your Subscribers for Their Roaming Usage

Normally, the call event detail records in a TAP file contains the roaming charge and the calculated tax amount that your roaming partner passes to you after having rated your subscribers' usage based on the agreement between you and your roaming partner.

To bill your subscribers for their roaming charges, you can choose to accept the charges and the tax amount passed in by your roaming partner and use them to bill your subscribers or you can reprice or mark up the roaming EDRs based on your subscribers' roaming subscription plan or retail rate. See "Charging Your Subscribers for Their Roaming Usage".

To specify whether or not to apply the tax amount, you set the taxation flag in the roaming partner's account configuration. See "Choosing Whether to Apply Taxes for Roaming".

To rate the call event detail records, the reprice pipeline uses the same modules as the rating pipeline. For the list of modules used by the reprice pipeline, see "Configuring Reprice Pipeline Function Modules".

If the reprice pipeline is unable to process or rate the record due to errors such as incorrect rating configuration, the record is suspended and recycled using Suspense Manager. See "Processing EDRs Suspended by the Reprice Pipeline".

When the final charge calculation is complete, the IRL_EventTypeSplitting iRule routes the records to separate output streams based on the service type; for example, GSM and GPRS. The output module writes the records to an output file by using the RE Loader output grammar.

RE Loader reads the output file and loads each event into the BRM database. For instance, the GSM events are loaded into the /event/delayed/session/telco/gsm object and the GPRS events are loaded into the /event/delayed/session/telco/gprs object.

The event objects contain all data related to the event including your subscriber's rating and billing information and are associated with the /service/telco/gsm object, for GSM records, and /service/telco/gprs object, for GPRS records, of the subscriber's account. After the event objects are loaded into the database, you can run BRM billing to bill your subscribers for their roaming usage.

For information about RE Loader, see "Understanding Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.

Charging Your Subscribers for Their Roaming Usage

You can rerate the incollect data to bill your own subscribers for roaming usage. To do this, choose one of the following methods:

  • Passthrough rating

    The rated events delivered from other network operator costs are passed through to your retail billing system without being rated by you. This means that you assume the rating carried out by the other operator is correct.

  • Markup adding

    A specified value is added to the wholesale charge delivered by another network operator. The markup can be an absolute value, such as $1.00, or a percentage, such as 15%. Markup adding is usually performed after having applied a tariff check and validated the rated events from another network operator.

  • Complete rating

    The events are rated by using your pipeline configuration.

To specify how the call event detail records should be processed, you use Pricing Center to create rate plans and price models that define the criteria used to determine the charge. For more information, see "Defining Rate Plans for Rating Roaming Usage".

Processing EDRs Suspended by the Reprice Pipeline

If the reprice pipeline is unable to rate an EDR, it sets the error in the EDR and suspends it. The FCT_Reject module evaluates the error and routes the EDR to the suspense output stream as specified by the RejectStream pipeline registry entry.

Using SE Loader, you load the suspended EDRs into the BRM database. Using Suspense Management Center, you can query the suspended events and make the necessary corrections. After the corrections are made, you can recycle the events for processing.

When Pipeline Manager receives the recycle request, the INP_Recycle module retrieves the suspended records from the BRM database and routes the events to the pre-recycle pipeline. The pre-recycle pipeline converts the suspended events back to EDR format and sends the EDRs back to the reprice pipeline for rating.

For detailed information about how EDRs are suspended and recycled, see "About Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

Choosing Whether to Apply Taxes for Roaming

Your roaming partners will rate your subscribers' roaming usage and also calculate and apply the tax amount. You can choose whether or not to pass this tax charge on to your subscribers. You do this by setting the taxation flag in the network operator configuration. For more information, see "About Setting Up Network Operator Accounts".

During incollect processing, the DAT_InterConnect module retrieves the taxation flag value for each network operator from the Pipeline Manager database and stores this information in the in-memory cache.

When processing the EDRs, the ISC_ApplyTax module retrieves the PLMN ID for the network operator and passes this ID to the DAT_InterConnect module to get the taxation flag value for the network operator from the in-memory cache. If the taxation flag is set to on, the tax amount is passed to the subscriber; otherwise, the tax amount is ignored.

About Processing Your Subscribers' Prepaid Roaming Charges

The TAP file may contain postpaid roaming activities in addition to the prepaid activities.

Postpaid records are processed by the reprice pipeline, to be repriced based on your subscriber's roaming subscription plan, and by the settlement pipeline, for financial settlement with your roaming partner.

Unlike postpaid roaming activities, prepaid roaming activities are processed in real time. When a subscriber makes a prepaid call, the visited network operator sends the call data to the home network operator in real time. The home network operator rates the call and applies the balance impact in real time. The visited network operator also sends the roaming charges for the prepaid service to the home network operator in the TAP file. For more information on how prepaid events are processed, see "Understanding Prepaid AAA" in BRM Telco Integration.

Prepaid roaming activities are represented as CAMEL records in the TAP file. CAMEL records are processed by the settlement pipeline for financial settlement with your roaming partner. The settlement pipeline associates the CAMEL records with the roaming partner account and creates settlement records that are loaded into the BRM database.


Note:

By default, CAMEL records are also passed to the reprice pipeline even though it is prepaid and may not need repricing. This provides you the flexibility of how you want to process CAMEL records. For example, using custom iScripts, you may want to update CAMEL records to have zero balance, or you can choose to remove the records so that they are not processed by the reprice pipeline at all.

For more information about settling roaming charges, see "About Settling Roaming Charges".

About Repricing Optimally Routed Calls

Optimal call routing provides for seamless routing of calls. For example, suppose a mobile subscriber A has established mobile service with network operator X, and mobile subscriber B has mobile service with network operator Y in different service areas. In this case, calls between subscriber A and subscriber B are long-distance calls. However, when one subscriber is in the service area of the other, the call is routed locally.

If a call is optimally routed, the Destination Network field is set in the TAP file. The TAP mapping iScript maps the destination network into the DETAIL.DESTINATION_NETWORK field in the EDR container.

When the EDR is processed in the reprice pipeline, you can verify the roaming charges for optimally routed calls and reprice them. You can do this by using a custom iScript or by defining price models to reprice the call based on the value defined in the destination network field and use model selector to choose the proper price model at the time of repricing.

For more information about custom iScripts, see "Creating iScripts and iRules" in BRM Developer&#x2019;s Guide.

For more information about creating price models, see "Setting Up Pipeline Rate Plans" in BRM Setting Up Pricing and Rating.

PK6uuPKSqEOEBPS/cover.htm  Cover

Oracle Corporation

PK@t` PKSqE#OEBPS/rmg_tapv311_setup_roaming.htm Setting Up Roaming for TAP

6 Setting Up Roaming for TAP

This chapter describes how to set up roaming in Oracle Communications Billing and Revenue Management (BRM) to rate Transferred Account Procedure (TAP) roaming usage events.

Setting Up Roaming for TAP Roaming Usage Events

To set up roaming for incollect and outcollect processing, do the following:

  1. Install supporting managers. See "Installing Supporting Managers".

  2. Use Pricing Center to create network operator accounts in the Pipeline Manager database. When you create network operator accounts, you also define network models and interconnect products for rating roaming usage. See "About Setting Up Network Operator Accounts".

  3. Use Customer Center to create roaming partner accounts in the BRM database for storing settlement events and balance impacts. See "Defining Roaming Partner Accounts in the BRM Database".

  4. Create rate plans for rating roaming usage. See "Defining Rate Plans for Rating Roaming Usage".

  5. Define configuration parameters that are used for settlement processing. See "Defining Configuration Parameters for Roaming".

  6. Set up the default TAP currency. See "Setting Up the Default TAP Currency".

  7. (Optional) Configure the roaming registry file to also support TAP. See "Setting Up TAP Roaming Manager to Support TAP 3.11".

    By default, TAP Roaming Manager is configured to support TAP 3.12.

Installing Supporting Managers

Roaming incollect and outcollect processing for TAP roaming usage events requires Suspense Manager, to process suspended event detail records (EDRs); InterConnect Manager, to rate roaming usage; and Rated Event (RE) Loader, to load roaming usage events into the BRM database.

You must install and configure:


Note:

Suspense Manager, InterConnect Manager, and RE Loader, are not part of TAP Roaming Manager and requires separate licenses.

Defining Roaming Partner Accounts in the BRM Database

You use Customer Center to create roaming partner accounts in the BRM database for each roaming partner network operator, including yourself.

Roaming partner accounts are used to:

  • Store your roaming partner network operator's contact and payment information.

  • Store your roaming partner's subscribers' roaming events.

  • Store roaming charges.

  • Store your roaming partner network operator's Public Land Mobile Network (PLMN) ID as a service login.

  • Store the Special Drawing Rights (SDR) fraud limits in the corresponding /profile/acct_extrating object.


    Note:

    Only one account can exist for a roaming partner network operator.

To create roaming partner accounts in the BRM database, do the following:

Creating a Roaming Plan

To create a roaming plan:

  1. Create a product for incollect settlement called RoamingIncollect with the /service/settlement/roaming/incollect service.

  2. Create another product for outcollect settlement called RoamingOutcollect with the /service/settlement/roaming/outcollect service.

  3. Create a deal for incollect settlement called RoamingIncollectDeal and add the RoamingIncollect product to it.

  4. Create another deal for outcollect settlement called RoamingOutcollectDeal and add the RoamingOutcollect product to it.

  5. Create a roaming plan called RoamingPlan by adding the deals created in steps 3 and 4 to it.

  6. Assign a balance group to the RoamingIncollect product.

  7. Assign a different balance group to the RoamingOutcollect product.


    Note:

    You can refer to the sample roaming settlement plan BRM_Home\PricingCenter\Sample_Price_Plans\RoamingSettlementPlan.ipl file for sample settlement products, deals and plans.

    For roaming to work correctly, the roaming incollect and outcollect products must be assigned to different balance groups.


Creating Roaming Partner Accounts Using the Roaming Plan

To create the roaming partner account:

  1. Purchase the roaming plan.

  2. Assign the balance group associated RoamingIncollect to a bill unit.

  3. Assign the balance group associated RoamingOutcollect to a different bill unit.


    Note:

    You can choose to create a separate bill unit for each service or create one bill unit for both services. If you create one bill unit, the incollect and outcollect roaming charges will be summed up in one bill. By creating separate bill units, the incollect and outcollect roaming charges will be in separate bills.

Defining Rate Plans for Rating Roaming Usage

You use Pricing Center to create rate plans and price models that define the criteria used to determine the charge for rating roaming usage.

To create pipeline rate plans and price models, see "Pipeline Rate Plans" in BRM Setting Up Pricing and Rating.

When you create the rate plan, you can choose to modify or replace the charge passed in the TAP records from your roaming partner network operator. You can increase the passed-in price by a percentage (for example, 15%) or by a fixed amount (for example, $1.00). You can also replace the passed-in price with an amount you enter. See "Using Passthrough Prices" in BRM Setting Up Pricing and Rating.

Defining Configuration Parameters for Roaming

Define the following configuration parameters:

  1. Verify that the /item/settlement/roaming item type is defined in the /config/item_types storable object:

    0 PIN_FLD_ITEM_TYPES           ARRAY [6] allocated 6, used 6
    1     PIN_FLD_DESCR              STR [0] "Roaming Settlement"
    1     PIN_FLD_ITEM_SUB_TYPE      STR [0] ""
    1     PIN_FLD_ITEM_TAG           STR [0] "roaming_settlement"
    1     PIN_FLD_ITEM_TYPE          STR [0] "/item/settlement/roaming"
    1     PIN_FLD_PRECREATE          INT [0] 1
    1     PIN_FLD_TYPE              ENUM [0] 2
    

    If the /item/settlement/roaming item type is not defined, load the BRM_Home/sys/data/pricing/example/config_item_types.xml file into the BRM database by running the load_config_item_types utility. For more information, see "load_config_item_types" in BRM Configuring and Running Billing.

  2. Verify that the roaming_settlement item tag is defined in the /config/item_tags storable object:

    0 PIN_FLD_ITEM_TAGS             ARRAY [6] allocated 3, used 3
    1     PIN_FLD_EVENT_TYPE          STR [0] "/event/delayed/session/telco/*"
    1     PIN_FLD_ITEM_TAG            STR [0] "roaming_settlement"
    1     PIN_FLD_SERVICE_TYPE        STR [0] "/service/settlement/roaming/*"
    

    If the roaming_settlement item tag is not defined, load the BRM_Home/sys/data/pricing/example/config_item_tags.xml file into the BRM database by running the load_config_item_tags utility. For more information, see "load_config_item_tags" in BRM Configuring and Running Billing.

  3. Verify that the /service/settlement/roaming/outcollect and /service/settlement/roaming/incollect event types are defined in the /config/event_map storable object.

    0 PIN_FLD_EVENT_MAP                ARRAY [10] allocated 2, used 2
    1     PIN_FLD_PERMITTED              STR [0] "/service/settlement/roaming/outcollect"
    1     PIN_FLD_EVENTS               ARRAY [0] allocated 5, used 5
    2         PIN_FLD_COUNT              INT [0] 0
    2         PIN_FLD_EVENT_DESCR        STR [0] "Roaming Settlement Event"
    2         PIN_FLD_EVENT_TYPE         STR [0] "/event/delayed/session/telco/roaming"
    2         PIN_FLD_INDICATOR          INT [0] 0
    2         PIN_FLD_UNIT              ENUM [0] 0
    0 PIN_FLD_EVENT_MAP                ARRAY [11] allocated 2, used 2
    1     PIN_FLD_PERMITTED              STR [0] "/service/settlement/roaming/incollect"
    1     PIN_FLD_EVENTS               ARRAY [0] allocated 5, used 5
    2         PIN_FLD_COUNT              INT [0] 0
    2         PIN_FLD_EVENT_DESCR        STR [0] "Roaming Settlement Event"
    2         PIN_FLD_EVENT_TYPE         STR [0] "/event/delayed/session/telco/roaming"
    2         PIN_FLD_INDICATOR          INT [0] 0
    2         PIN_FLD_UNIT              ENUM [0] 0
    

    If the /service/settlement/roaming/outcollect and /service/settlement/roaming/incollect event types are not defined, edit the pin_event_map file and create the event mappings, and then run the load_event_map utility, which loads the event mappings into the BRM database. For more information, see "load_event_map" in BRM Setting Up Pricing and Rating.

  4. Verify that the SDR currency resource is defined in the /config/beid storable object.

    If the SDR currency is not defined, use Resource Editor to define the currency.

  5. Verify that the general ledger (G/L) ID used for tracking roaming charges (specified in the registry for ISC_ConsolidatedCP) is defined in the /config/glid storable object.

    If the G/L ID for roaming charges is not defined, edit the pin_glid file, and then run the load_pin_glid utility, which loads the G/L ID. For more information, see "load_pin_glid" in BRM Collecting General Ledger Data.

Setting Up the Default TAP Currency

BRM roaming uses SDR as the default TAP currency. You can configure BRM to use a currency other than SDR as the default TAP currency.

To configure BRM to use a currency other than SDR as the default TAP currency:

  1. Define the new default TAP currency resource. See "Setting Up Resources" in BRM Setting Up Pricing and Rating.

  2. Define the exchange rates for the new currency using Pricing Center. See the discussion about setting up currencies and exchange rates in the Pricing Center Help.

  3. Configure the new currency as the default TAP currency. See "Configuring the Default TAP Currency".

Configuring the Default TAP Currency

To configure the default TAP currency:

  1. Open the roaming registry file (Pipeline_Home/conf/roaming.reg), where Pipeline_Home is the directory in which you installed Pipeline Manager.

  2. For all instances of the FCT_ExchangeRate module in the roaming registry, change the HomeCurrency registry entry from SDR to the new default TAP currency.

  3. In the TAP input processing pipeline, set the TAPCurrency registry entry to the new default TAP currency.

  4. Save and close the file.


    Note:

    During TAP input file processing, if the TAP input file does not contain a currency in the TapCurrency field and if the TAPCurrency registry entry is set in the roaming registry file, the TAPCurrency value in the registry file is used as the default TAP currency. If the TAP input file does not contain a currency in the TapCurrency field and if the TAPCurrency registry entry is not set in the registry file, the default TAP currency is set to SDR.

Setting Up TAP Roaming Manager to Support TAP 3.11

The TAP 3.12 installation directory includes the roaming registry file (Pipeline_Home/conf/roaming.reg) that contains pipelines configured for processing TAP 3.12 files. To process both TAP 3.11 and TAP 3.12 files, you need to update the roaming registry file to contain similar pipeline sections configured for processing TAP 3.11 files.

For example, the pipelines section will contain two sections for the validation pipeline, one section named TAPInProcessingPipeline, for TAP 3.12 files, and another named TAPInProcessingPipeline_0311, for TAP 3.11 files. Each pipeline requires a separate input directory, and each pipeline requires a separate set of grammar files, mapping files, and iScripts.

To set up TAP Roaming Manager to support TAP 3.11:

  1. Verify that duplicates of the specific files required to continue processing TAP 3.11 files were created at the start of the installation process.

    Table 6-1 lists the files that should have been duplicated at the start of the installation process. For more information, See the discussion about backing up TAP 3.11 files in BRM Patch Set Installation Guide .

    Table 6-1 Files Duplicated During Patch Set Installation

    TAP 3.12 File NameTAP 3.11 File Name

    RAP_0105_AckOutGrammar.dsc

    RAP_0105_AckOutGrammar_0311.dsc

    RAP_0105_FatalReturn.dsc

    RAP_0105_FatalReturn_0311.dsc

    RAP_0105_InGrammar.dsc

    RAP_0105_InGrammar_0311.dsc

    RAP_0105_MissingReturn.dsc

    RAP_0105_MissingReturn_0311.dsc

    RAP_0105_OutGrammar.dsc

    RAP_0105_OutGrammar_0311.dsc

    RAP_0105_StopReturn.dsc

    RAP_0105_StopReturn_0311.dsc

    containerDesc.dsc

    containerDesc_0311.dsc


  2. Open the Pipeline_Home/conf/roaming.reg file.

  3. Duplicate the TAP 3.12 pipelines (listed in the left-hand column of Table 6-2) and update the duplicated pipelines to use TAP 3.11 (as shown in the right-hand column of Table 6-2) by doing the following:

    Table 6-2 Pipelines Requiring Configuration

    Pipeline Name and Data Provided for Use with TAP 3.12Pipeline Name and Data to Be Created for Use with TAP 3.11

    TAPCorrectionPipeline

    TAPCorrectionPipeline_0311

    RAPInProcessingPipeline

    RAPInProcessingPipeline_0311

    TAPOutCollectPipeline

    TAPOutCollectPipeline_0311

    TAPOutSettlementPipeline

    TAPOutSettlementPipeline_0311

    TAPInProcessingPipeline

    TAPInProcessingPipeline_0311

    StopRapGeneratorPipeline

    StopRapGeneratorPipeline_0311



    Important:

    The backup procedure during the installation used the extension _0311 to rename the required TAP 3.11 files and to associate them with the TAP 3.11 version to which they belong.

    The following steps use that _0311 name extension to update the roaming.reg file with the registry configuration appropriate for the processing of TAP 3.11 roaming usage events.

    If you chose a different naming structure for these files during the backup step, then, make sure that the roaming.reg file is updated to reflect that naming structure for proper processing of TAP 3.11 roaming usage events.


    1. Find the section for each pipeline under Pipelines.

      For example, the section for TAPInProcessingPipeline is:

      TAPInProcessingPipeline
          {
            Active = True
      ...
      ...
       } # END of Output    
          } # END TAPInProcessingPipeline
      
    2. Copy this entire section and paste it immediately under the original section.

    3. Rename the copied section to the name (appropriate for TAP 3.11) in the right-hand column of Table 6-2.

      For example:

      TAPInProcessingPipeline_0311
          {
            Active = True
      ...
      ...
       } # END of Output    
          } # END TAPInProcessingPipeline_0311
      

      You should now have two sections for that pipeline, the TAP 3.12 section followed by the duplicate (renamed) pipeline section for TAP 3.11. For example:

      TAPInProcessingPipeline
          {
            Active = True
      ...
      ...
       } # END of Output    
          } # END TAPInProcessingPipeline
      TAPInProcessingpipeline_0311
          {
            Active = True
      ...
      ...
       } # END of Output    
          } # END TAPInProcessingPipeline_0311
      
    4. The newly-created section for the TAP 3.11 pipeline contains TAP 3.12 iScript, grammar, and container description file names (because of the copying), so you must change the iScript, grammar, and container description file names for TAP 3.11 processing (using the entries in Table 6-3).

      For example, change the Grammar registry entry for TAPInProcessingPipeline_0311 from:

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

      to:

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

      This makes the Grammar registry entry in the TAPInProcessingPipeline_0311 section appropriate for processing TAP 3.11 roaming usage events:

      TAPInprocessingPipeline_0311
          {
            Active = True
      ...
      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0311_InGrammar.dsc
      ...
       } # END of Output    
          } # END TAPInProcessingPipeline_0311
      

      Table 6-3 lists file names you need to change in the TAP 3.11 pipeline to set up iScript, grammar, and container description files appropriate for TAP 3.11.


      Note:

      Not all the file names are contained in a pipeline section. For example, neither the original nor the duplicate section for TAPCorrectionPipeline contains the ISC_TAP_0312_Validations iScript entry (which is used to validate TAP 3.12 input data).

      Table 6-3 Basic Configuration Data for Duplicated Pipelines

      TAP 3.12 File NameTAP 3.11 File Name

      TAP_0312_OutGrammar.dsc

      TAP_0311_OutGrammar.dsc

      TAP_0312_InGrammar.dsc

      TAP_0311_InGrammar.dsc

      TAP_0312_Blocks.dsc

      TAP_0311_Blocks.dsc

      ISC_TAP_0312_Validations.isc

      ISC_TAP_0311_Validations.isc

      ISC_TAP_0312_InMap.isc

      ISC_TAP_0311_InMap.isc

      RAP_0105_AckOutGrammar.dsc

      RAP_0105_AckOutGrammar_0311.dsc

      RAP_0105_FatalReturn.dsc

      RAP_0105_FatalReturn_0311.dsc

      RAP_0105_InGrammar.dsc

      RAP_0105_InGrammar_0311.dsc

      RAP_0105_MissingReturn.dsc

      RAP_0105_MissingReturn_0311.dsc

      <6/td>

      RAP_0105_OutGrammar.dsc

      RAP_0105_OutGrammar_0311.dsc

      RAP_0105_StopReturn.dsc

      RAP_0105_StopReturn_0311.dsc

      containerDesc.dsc

      containerDesc_0311.dsc


    5. Configure the entry for InputPath in the InputStream section for the newly-created pipeline, as appropriate for TAP 3.11.

      Change the following:

      InputPath = ./data/incollect/tapin/in
      

      to:

      InputPath = ./data/incollect/tapin/in_0311
      

      For example:

      InputStream
              {
               ModuleName = EXT_InFileManager
               Module
                    {
                      InputPath = ./data/incollect/tapin/in_0311
      ...
      
    6. Configure the entry for DonePath in the InputStream section for the newly-created pipeline, as appropriate for TAP 3.11.

      Change the following:

      DonePath = ./data/incollect/tapin/done
      

      to

      DonePath = ./data/incollect/tapin/done_0311
      

      For example:

      InputStream
              {
               ModuleName = EXT_InFileManager
               Module
                    {
                      DonePath = ./data/incollect/tapin/done_0311
      ...
      
    7. Configure the entry for ErrorPath in the InputStream section for the newly-created pipeline, as appropriate for TAP 3.11.

      Change the following:

      ErrorPath = ./data/incollect/tapin/error
      

      to

      ErrorPath = ./data/incollect/tapin/error_0311
      

      For example:

      InputStream
              {
               ModuleName = EXT_InFileManager
               Module
                    {
                      ErrorPath = ./data/incollect/tapin/error_0311
      ...
      

    Repeat these steps for the remaining pipelines listed in Table 6-2.

  4. Save and close the file.

Verifying the Processing of Roaming Usage Events

To verify that TAP Roaming Manager processes roaming usage events correctly, check the following:

Improving System Performance When Rating Roaming Events

When you process TAP records and other service events (for example, GSM) in parallel, it can affect your system's performance. This occurs when TAP records are older than the GSM records. For accounts that have changed, the system has to reload old and new account data constantly which results in increased database access. You can improve system performance by creating a separate Pipeline Manager instance to process the TAP records separately.

PKg 2EӐɐPKSqEOEBPS/title.htm Oracle Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4

Oracle® Communications Billing and Revenue Management

Configuring Roaming in Pipeline Manager

Release 7.4

E25100-01

March 2013


Oracle Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4

E25100-01

Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

PKwQ PKSqEOEBPS/rmg_interconnect.htm Rating Interconnect Events

14 Rating Interconnect Events

This chapter describes how to set up the Oracle Communications Billing and Revenue Management (BRM) Pipeline Manager for rating interconnect events.

You should be familiar with how roaming events are rated by Pipeline Manager. See "About Rating Roaming Events".

For information about pipeline rating, see "About Pipeline Rating" in BRM Configuring Pipeline Rating and Discounting.

About Interconnect Rating

Interconnection means the process of handling events over physical lines between two or more network operators. The following types of network can be involved in an interconnect process:

An interconnect process always involves an originating and terminating network; a transit network is optional.

The cost added for handling an interconnect event is called the interconnect charge. An interconnect charge is calculated according to a service agreement between interconnect partners.

For information about processing settlements for rated interconnect events, see "About Managing Settlement for Interconnect Charges".

About Setting Up Interconnect Rating

To set up interconnect rating, do the following:

  1. Use Pricing Center to create network operators, network models, and interconnect products. When you set up interconnect rating, you also define the following:

    • The calculation mode to define which EDR data to rate for the network model, for example, inroute, outroute, or transit data. See the discussion about defining a network model in BRM Pricing Center Online Help.

    • Network elements to find the zone for interconnect calls.

      - Map points of interconnection (POIs) to area codes or logical point codes.

      - Assign switches to network operators.

      - Assign trunks to network operators.

      See the discussion about defining network elements in BRM Pricing Center Online Help.

  2. Configure the FCT_CarrierICRating module. See "About FCT_CarrierICRating Module".

  3. Configure the DAT_InterConnect module. See "About the DAT_InterConnect Module".

  4. Define aggregation scenarios. See "About Aggregation Scenarios for Roaming".

  5. Define network operator bill cycles. See "About Network Operator Bill Cycles".

About FCT_CarrierICRating Module

The FCT_CarrierIcRating module uses the interconnect products to identify the network operator and which rate plan to use.

The FCT_CarrierIcRating module creates associated charge breakdown records and charge packets that contain data used for rating roaming events, for example, the network operator and event timestamp. This data is used by the FCT_PreRating and FCT_MainRating modules to determine the impact category and calculate the charges for the event. The roaming data is used for both incollect and outcollect processing.

FCT_CarrierIcRating creates ratable charge packets for each valid roaming rate (IFW_ICPRODUCT_RATE) entry for the IC product.

When you configure the FCT_CarrierIcRating module:

  • Use the EdrNetworkModel entry to specify the network model, which identifies the home network to use for the pipeline. Use the code you entered in the Code field in Pricing Center when defining network models. See the discussion about defining a network model in BRM Pricing Center Online Help.

  • Use the IcProductGroup entry to specify the network model, which identifies the home network to use for the pipeline. Use the code you entered in the Interconnect Product Group field in Pricing Center when defining network models. See the discussion about defining an interconnect product group in BRM Pricing Center Online Help.

See "FCT_CarrierIcRating" in BRM Configuring Pipeline Rating and Discounting.

About the DAT_InterConnect Module

To provide roaming configuration data to pipeline function modules, you must configure the DAT_Interconnect module. This module caches interconnect and roaming related configuration data. This information is used by FCT_CarrierIcRating module.

To configure this module, see "DAT_InterConnect" in BRM Configuring Pipeline Rating and Discounting.

You can use the Reload semaphore to reload interconnect data. See "Reloading Data Into a Pipeline Manager Module" in BRM System Administrator's Guide.

About Aggregation Scenarios for Roaming

You use aggregation scenarios to do the following:

  • Aggregate charges for outcollect rating to send to network operators.

  • Aggregate charges for incollect processing to compare with the charges in the invoice sent to you from network operators.

Pipeline Manager aggregates settlement information for each network operator and stores it in the Pipeline Manager database. You can use this settlement information to bill your interconnect partners or verify interconnect charges.

To compare aggregated charges to those from network operators, you extract the aggregated settlement data from the Pipeline Manager database. This gives you a text file containing charge information. To bill network operators for interconnect charges, you load the extracted aggregation data into the BRM database and run billing. For more information, see "About Processing Outcollect Settlement Data".

You can also set up your own aggregation scenarios. See "Setting Up Pipeline Aggregation" in BRM Configuring Pipeline Rating and Discounting.

About Network Operator Bill Cycles


Note:

You only define network operator bill cycles when you use the settlement_extract utility to load aggregated settlement data into the BRM database.

You define bill cycles in Pricing Center for your interconnect partners. A bill cycle is defined as a billrun. Billruns are used to determine whether you have billed the network operator for roaming usage during a specified period.

When you define billruns, you enter the bill cycle period, and the begin and end dates of the bill cycle. All events generated within this period apply to the specified billrun.

To define billruns in Pricing Center, see the discussion about defining network operator bill cycles in BRM Pricing Center Online Help.

Closing a Billrun

Prior to extracting aggregated roaming settlement data from the Pipeline Manager database, you must close the bill cycle for the network operator. This ensures that only unbilled events are extracted for loading into the BRM database.

See the discussion about closing a network operator bill cycle in BRM Pricing Center Online Help.

About Setting Up Network Operator Accounts

To set up network operator accounts, you use Pricing Center to configure the following elements in the Pipeline Manager database:

About Network Operators

Use Pricing Center to create a network operator account in the Pipeline Manager database for every roaming partner.


Note:

When creating network operator accounts for roaming, the roaming partner account for that network operator must be created in the BRM database before creating a network operator account.

When you set up network operators, you include the following data:

  • Network operator name.

  • Network operator type, for example, interconnect partner or service provider partner. (This information is for your reference, not for processing.)

  • How to identify the network operator; for example, by the carrier access code or by the PLMN ID.

  • Whether to apply taxes for roaming charges.

  • (Roaming) The network operator's roaming partner account in the BRM database.

  • (Roaming) Fraud or high-usage limits.

To define network operators in Pricing Center, see the discussion about defining a network operator in BRM Pricing Center Online Help.

About Network Models

A network model identifies your roaming agreements and is associated with your home network. Each network operator representing a roaming partner is linked to the network model.

When you set up a roaming network model, you include the following data:

  • Model type. For roaming, this is always Reseller Roaming.

  • The network operator that represents your network.

  • Your home currency.

To define network models in Pricing Center, see the discussion about defining a network model in BRM Pricing Center Online Help.

About Interconnect Products

An IC product specifies the network data that identifies a network operator and type of service. You create one or more IC products for each network operator and link them to rate plans. You create IC products to select the rate plan to use for the network operator's services. For example, to use a rate plan that includes mailbox inquiries, you include a mailbox inquiry usage class in the IC product configuration. You identify the network operator by specifying the source and destination of the call.

You configure IC products in the IC product group in Pricing Center. When you configure an IC product, you specify the following information:

  • Validity dates

  • To identify the network operator:

    • Source and destination area codes

    • Source and destination networks

    • Transit area code

  • To identify the type of service:

    • Record type

    • Service code, service class, and usage class

Roaming events with data that matches an interconnect product belong to the associated network operator and are rated by using the associated rate plan. See "About Linking Rate Plans to Network Operators and IC Products".

To define interconnect products in Pricing Center, see the discussion about defining interconnect products in BRM Pricing Center Online Help.

About Interconnect Product Groups

An interconnect product group is a collection of interconnect product configurations. You create an interconnect product group to define the set of interconnect products available to each network model. You can create multiple interconnect product groups, but you use only one interconnect product group in a pipeline.

When you create interconnect product groups, you specify the following:

  • The network model that uses the interconnect product group.

  • The ranking of interconnect products in the interconnect product group. The first configuration that matches an event attribute will be used for rating.

An interconnect product can be in several interconnect product groups.

To create interconnect product groups in Pricing Center, see the discussion about defining an interconnect product group in BRM Pricing Center Online Help.

About Linking Rate Plans to Network Operators and IC Products

To rate a call and perform settlements, you must link the call attributes defined by the interconnect product to a network operator and rate plan. You can link each interconnect product to multiple network operators and rate plans. This allows you to:

  • Use a different rate plan for the same network operator. For example, you might use different rate plans for different types of services such as telephony and SMS, or for different types of usage such as mailbox inquiries and friends-and-family calls.

  • Use the same rate plan for different network operators. For example, you might have roaming agreements with two network operators that provide the same services.

To link the call attributes defined by the interconnect product to a network operator and rate plan:

  1. Use Pricing Center to link network operators to IC products and rate plans by configuring the following:

    • Validity dates.

    • The network model.

    • The rate plan.

    • The IC product.

    • Zone direction. For roaming, this is always Standard Zoning (A#->B#).

    See the discussion about linking an IC product to a network operator and a rate plan in BRM Pricing Center Online Help.

  2. Configure the FCT_CarrierIcRating module. See "About FCT_CarrierICRating Module".

About Managing Settlement for Interconnect Charges


Note:

To install Roaming Settlement Package, see "Installing Roaming Settlement Package" in BRM Installation Guide.

To manage settlement for interconnect charges, you do the following:

About Creating Accounts for Interconnect Partners

You create BRM accounts for each network operator by using Customer Center. For each network operator, create one parent account with a paying bill unit and two child accounts with nonpaying bill units.

Network operator accounts store the following information:

How Settlements Are Applied to Account Balances

When you rate usage by a visiting customer, you bill the visiting customer's network operator for that usage. Pipeline Manager aggregates charges for each network operator on a daily basis. When you load the aggregated settlement information and bill the accounts, the amount due is the difference between what you owe your partners and what they owe you. Amounts owed to you are included in the bill. The net roaming charges are stored in the balance impact of your roaming partner's parent account.

If there are any disputed items, you can use Customer Center to enter and clear the dispute.

About Price Plans for Roaming Partners

To support roaming settlements, the GSM sample price list includes a Settlement price plan. You apply this price plan to the network operator accounts that you create.

For information on creating price lists, see "About Creating a Price List" in BRM Setting Up Pricing and Rating.


Note:

Before you can use the sample Settlement price plan, you need to load the GSM Manager sample price list. See "About the Sample GSM Pricing Configuration" in BRM Telco Integration.

The Settlement price plan includes a Settlement deal and product. The Settlement product includes a rate plan as a placeholder for the settlement service. You define a rate plan for each network operator when you set up roaming in Pipeline Manager. See "About Setting Up Network Operator Accounts".

About Processing Outcollect Settlement Data

When Pipeline Manager rates roaming calls, it stores the settlement information, such as what is owed by each participating network provider, in the Pipeline Manager database. You extract the settlement information from the pipeline database and load it into the BRM database. After the settlement information is loaded, you can bill your network partners for the settlement amounts.

Before you can extract settlement information from the pipeline database and load it into the BRM database, you must complete the following tasks:

  1. Install the roaming settlements package. This package includes the utility and template files you use to extract and load settlement data. See "Installing Roaming Settlement Package" in BRM Installation Guide.

  2. Import the Universal Event Mapper settlement template by running the pin_uei_deploy utility. See "Importing the UE Mapper Settlement Template".

  3. Configure Universal Event (UE) Loader to load the settlement file. See "Configuring UE Loader to Load the Settlement Data File".

To get the settlement data from the Pipeline Manager database to the BRM database, you use the following:

The ASCII file created by the settlement_extract utility contains the settlement fees. There is one record for fees owed to each network. For example, if you have settlements between networks B and C, the file contains the following:

Settlement amounts can be in different currencies. You define the currencies when you set up roaming in Pipeline Manager.

Importing the UE Mapper Settlement Template

The UE Mapper settlement template specifies the format of the file containing settlement information.

When you install Roaming Settlement Package, you install the SettlementTemplate.xml template in the BRM_home/apps/uel directory. You must import the template into the BRM database by running the pin_uei_deploy utility.


Note:

To connect to the BRM database, the pin_uei_deploy utility needs a configuration (pin.conf) file in the directory from which you run the utility. See "Creating Configuration Files For BRM Utilities" in BRM System Administrator's Guide.

To import the SettlementTemplate.xml template:

  1. If you have not already done so, download and install Roaming Settlement package. See "Installing Roaming Settlement Package" in BRM Installation Guide.

  2. Run the pin_uei_deploy utility:

    pin_uei_deploy -c -t template_name -i SettlementTemplate.xml
    

    where template_name is the name you want to give to the template in BRM.

    For more information, see "pin_uei_deploy" in BRM Developer&#x2019;s Guide.

For more information about importing UE Mapper templates, see "Migrating Event Import Templates From One BRM Database to Another" in BRM Setting Up Pricing and Rating.

Configuring UE Loader to Load the Settlement Data File

After you extract settlement data by using the settlement_extract.pl utility, you load the data by using UE Loader. You must first configure UE Loader to load the settlement file.


Note:

Before following this procedure, you should be familiar with UE Loader. See "About Rating Events Created by External Sources" in BRM Setting Up Pricing and Rating.

To configure UE Loader to load the settlement data, see "Configuring the Universal Event Loader" in BRM Setting Up Pricing and Rating and be sure to modify the following settlement-specific entries in the UE Loader properties file (BRM_home/apps/uel/Infranet.properties):

  1. Open the BRM_home/apps/uel/Infranet.properties file in a text editor.

  2. If necessary, edit the infranet.connection entry to point to the correct database. For example:

    infranet.connection=pcp://root.0.0.0.1:password@localhost:37180/service/pcm_client
    
  3. Specify the following date/time format for the settlement file in the infranet.uel.date_pattern entry:

    infranet.uel.date_pattern=yyyy-MM-dd
    
  4. Specify the location of the settlement data file in the infranet.uel.event_log_file_location entry.


    Note:

    The default location is the C:/Portal/apps/uel directory. Modify this entry to specify the correct location, or move the settlement data file to this directory when you run UE Loader. For more information, see "Specifying the Event Log File Location" in BRM Setting Up Pricing and Rating.

Configuring UE Loader to Run Automatically (Optional)

If you load settlement data on a regular basis, you can schedule UE Loader to load the settlement file automatically. To do this, you use the Batch Controller and sample batch handler. For more information, see "Loading Events Automatically" in BRM Setting Up Pricing and Rating.


Note:

Before following this procedure, you should be familiar with the Batch Controller. See "Controlling Batch Operations" in BRM System Administrator's Guide.

To configure automatic loading:

  1. Create a UE Loader batch handler to load the settlement data file by using the sample batch handler. See "About SampleHandler" in BRM System Administrator's Guide.

    You specify the UE Mapper settlement template in the $TEMPLATE entry of the batch handler .values file (BRM_home/apps/sample_handler/samplehandler_config.values, unless you renamed the file). For example:

    $TEMPLATE = "CSTemplate_name";
    
  2. Configure the Batch Controller to start the UE Loader batch handler. See "Setting Activity Times and Triggers" in BRM System Administrator's Guide.

Extracting Settlement Information from the Pipeline Manager Database

You extract settlement information from the Pipeline Manager database by using the settlement extraction utility (BRM_home/apps/uel/settlement_extract.pl). This utility creates a data file containing settlement amounts and other activity information.


Note:

To ensure that only unbilled events are extracted, before extracting the settlement data, you must close the billrun for each roaming partner account. You close the billrun by using Pricing Center. See the discussion about closing a network operator bill cycle in BRM Pricing Center Online Help.

When the settlement_extract.pl utility extracts settlement data, it marks the data in the database as exported so the next time you run the utility, you export only new data. For this reason, you cannot use this utility to extract the same settlement information twice. However, if you make adjustments to the aggregated settlement amounts by using Pricing Center, you can extract the adjusted settlement data. For more information, see "About Adjusting Aggregated Settlement Amounts".


Note:

(HP-UX only) Before running this utility, you must load the libjava.sl (HP-UX PA-RISC) or libjava.so (HP-UX IA64) library. One way of doing this is to set the LD_PRELOAD environment variable to point to the library file.

For example (using the HP-UX PA-RISC library file):

# sateens LD_PRELOAD /u01/ape/oracle/product/817/JRE/lib/PA_RISC/native_threads/libjava.sl

Note:

To connect to the BRM database, the settlement_extract utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files For BRM Utilities" in BRM System Administrator's Guide.

To extract settlement information:

  1. Close the billrun for each roaming partner account.

  2. Use the following command to run the settlement_extract.pl utility:

    settlement_extract.pl [-u] dbsn username password [filepath]
    

    where dbsn is the Perl database source name.

    For example:

    settlement_extract.pl -u dbi:Oracle:orcl scott tiger /usr/home/files
    

    For more information, see "settlement_extract" in BRM Configuring Pipeline Rating and Discounting.

Loading Settlement Data into the BRM Database

To load the data in the settlement file, you run UE Loader.

There are two ways to run UE Loader:

About Adjusting Aggregated Settlement Amounts

Pipeline Manager stores aggregated settlement data in the IC_DAILY database table. If any aggregated settlement amounts are in error, you can use Pricing Center to adjust the aggregated amounts in the Pipeline Manager database and then load them into the BRM database.

To make adjustments, you search for the aggregated settlements you want to modify by searching for associated data such as network operators, IC products, and dates the events were aggregated. You then make changes and update the database. See the discussion about adjusting aggregated settlement amounts in BRM Pricing Center Online Help.

About Generating SMS Usage Reports

You can collect aggregated information about SMS messages exchanged between your subscribers' home networks and other networks for generating settlement reports. The FCT_AggreGate module includes a scenario defined to aggregate the number of SMS messages based on the following attributes:

The FCT_AggreGate module extracts the SMS usage information from the input call details record (CDR) files and creates aggregated data files. For more information about aggregation, see the following topics:

You use the Universal Event (UE) Loader to load the aggregate SMS information into the BRM database. UE Loader parses the FCT_AggreGate output files that contain the SMS message information and calls the PCM_OP_IC_LOAD_SMS_REPORT opcode to create or update the /sms_settle_report object in the BRM database. See "Loading SMS Data into the BRM Database".

You can run a report to generate SMS bulk reports from the data in the /sms_settle_report object.

For more information on BRM reports, see "About BRM Reports" in BRM Reports.

Generating an SMS Usage Report

To generate an SMS usage report, perform these tasks:

  1. Make sure you have installed and configured Pipeline Manager.

    See "Installing Pipeline Manager" in BRM Upgrade Guide.

  2. Install the roaming settlements package.

    See "Installing Roaming Settlement Package" in BRM Installation Guide.

  3. Install the BRM reports SMS Settlement Reports package.

    See "Installing BRM Reports" in BRM Reports.

  4. Create the aggregation scenario in the database.

    See "Creating the Aggregation Scenario in the Database".

  5. Configure the FCT_AggreGate registry file to specify the SMS Message scenario, SMS_SCE_01.

    See "Configuring the FCT_AggreGate Module to Collect SMS Usage Information".

  6. Load the SMS interworking message information for settlement reports into the BRM database.

    See "Loading the SMS Message Data into the Database".

  7. Run reports to generate the SMS bulk reports.

    See "Generating SMS Bulk Reports".

Creating the Aggregation Scenario in the Database

This section describes how to create aggregation scenarios in Oracle database.


Note:

You can also create aggregation scenarios by using Pricing Center. See the discussion about working with aggregation scenarios in BRM Pricing Center Online Help.

To create the aggregation scenario in an Oracle database, run the SMS_Interworking_Scenario.sql script from the Pipeline_home/database/Oracle/Scripts directory.

This SQL script creates the SMS_SCE_01 scenario in the database that the FCT_AggreGate module uses to collect SMS usage information.

Configuring the FCT_AggreGate Module to Collect SMS Usage Information

Add an entry for the SMS settlement report scenario in the registry file.

For example:

Aggregate
{
   ModuleName = FCT_AggreGate
   Module
 {
   Active = TRUE
   ScenarioReaderDataModule = ifw.DataPool.ScenarioReader
   Scenarios
  {
   SMS_SCE_01
   {
   TableName = TAB_SMS_RPT
   Threshold = 100000
   TempDir = sms_result/temp
   DoneDir = sms_result/done
   CtlDir = sms_result/ctl
   FieldDelimiter = ,
   FlushMode = 0
   }
  }
ResultFile
 {
   TempSuffix = .tmp
   DoneSuffix = .dat
   WriteEmptyFile = FALSE
 }
  ControlFile
 {
  Suffix = .ctl
  DataFilePath = TRUE
 }
}
}

For detailed information about configuring the FCT_AggreGate module, see "Setting Up Pipeline Aggregation" in BRM Configuring Pipeline Rating and Discounting.

Loading the SMS Message Data into the Database

When you install the roaming settlements package, you install the SMS settlement report template file (SMSSettlementRptTemplate.xml) in the BRM_home/apps/uel directory. This template is used by UE Loader to parse aggregated SMS settlement data when it loads the data into the BRM database.

  1. Import the SMSSettlementRptTemplate.xml template by running the pin_uei_deploy utility:

    pin_uei_deploy -c -t template_name -i SMSSettlementRptTemplate.xml 
    

    where template_name is the name you want to give the template.

    For more information, see "pin_uei_deploy" in BRM Developer&#x2019;s Guide.

  2. Configure Universal Event (UE) Loader to load the SMS settlement data by modifying the BRM_home/apps/uel/Infranet.properties file.

    See "Configuring the Universal Event Loader" in BRM Setting Up Pricing and Rating.

  3. To load the file manually, run UE Loader by using this command:

    uel -t template_name log_file_name 
    

    For example:

    uel -t SMSSettlementRpt SMSSettlementRpt.dat 
    

    Note:

    The SMSSettlementRpt.dat file contains the aggregated SMS settlement data output by the FCT_AggreGate module. UE Loader uses the .dat files to load the data into the BRM database.

    For more information on running UE Loader, see "Loading Events From External Sources" in BRM Setting Up Pricing and Rating.

  4. To run UE Loader automatically, create a UE Loader batch handler and configure the Batch Controller.

    See "Loading Events Automatically" in BRM Setting Up Pricing and Rating.

Generating SMS Bulk Reports

An SMS bulk report is a summary report of the aggregated information collected for SMS messages exchanged between the home network and other networks.

To generate an SMS bulk report, you run the BRM reports SMS Internetworking Bulk Data Report. You must have installed BRM reports and the SMS Settlement Reports package. This package includes the SMS Internetworking Bulk Data Report template, SMSinterworkingbulk.rpt. For more information, see "Installing BRM Reports" in BRM Reports.

For information on generating reports on SMS messages, see "SMS Settlement Reports" in BRM Reports.

For information on running BRM reports, see "Running BRM Reports" in BRM Reports.

Opcodes Used for Managing Settlement Data

For more information about settlement, see "About Managing Settlement for Interconnect Charges".

Use the following IC Daily standard opcodes to manage settlement data:

Loading Settlement Data into the BRM Database

Use PCM_OP_IC_DAILY_LOADER to load settlement data files into the BRM database. Settlement data files are generated by the settlement_extract utility and specify the amount you owe to each network partner. See "About Processing Outcollect Settlement Data".

Universal Event (UE) Loader calls this opcode when loading settlement data into the BRM database.


Note:

You configure UE Loader to call this opcode by using the Universal Event Mapper. See "Importing the UE Mapper Settlement Template".

PCM_OP_IC_DAILY_LOADER performs the following tasks:

  1. Prepares the data from the settlement data file.

  2. Records the event and updates the network provider's account balance in the BRM database.

  3. Creates an /event/activity/settlement object to record details about the roaming event.


    Note:

    Each event contains information for one network partner.

  4. Returns the POID of the /event/activity/settlement object.

Loading SMS Data into the BRM Database

Use PCM_OP_IC_LOAD_SMS_REPORT to validate SMS aggregation data and create or update the /sms_settle_report object. See "About Generating SMS Usage Reports".

Universal Event (UE) Loader calls this opcode when loading aggregated SMS data into the BRM database.


Note:

You configure UE Loader to call this opcode by using the Universal Event Mapper. See "Loading the SMS Message Data into the Database"

PCM_OP_IC_LOAD_SMS_REPORT performs the following tasks:

  1. Determines whether the /sms_settle_report object already exists in the BRM database.

    • If it finds the report object, it updates the object with the value for SMS_TOTAL from the input flist.

    • If it does not find the object, it creates the /sms_settle_report object.

  2. Returns the POID of /sms_settle_report object.

PKOMCPKSqEOEBPS/rmg_ciber_install.htmA Installing CIBER Roaming Manager

13 Installing CIBER Roaming Manager

This chapter describes how to install CIBER Roaming Manager.


Important:

  • Before you install CIBER Roaming Manager, you must install Interconnect Roaming Manager. See "Installing InterConnect Manager".

  • If you are installing CIBER Roaming Manager to replace an identical release (for example, to restore a clean version of the package), you must first uninstall the existing installation. See "Uninstalling CIBER Roaming Manager".


Installing CIBER Roaming Manager

To install CIBER Roaming Manager:

  1. If the Third-Party software package is not installed already, install it. See "Installing the Third-Party Software" in BRM Installation Guide.

  2. Go to the directory where you installed the Third-Party package and source the source.me:

    source source.me.sh
    

    C shell:

    source source.me.csh
    
  3. Download the CIBER Roaming Manager software to a temporary directory (temp_dir).


    Note:

    You must increase the heap size used by the Java Virtual Machine (JVM) before running the installation program to avoid “Out of Memory” error messages in the log file. For information, see "Increasing Heap Size to Avoid “Out of Memory” Error Messages".

  4. Go to temp_dir and enter the following command:

    7.4_CIBERRoaming_platform_64_opt.bin 
    

    Note:

    You can use the -console parameter to run the installation in command-line mode. To enable a graphical user interface (GUI) installation, install a GUI application such as X Windows and set the DISPLAY environment variable before you install the software.

  5. Follow the instructions displayed during installation.


    Note:

    If you do not specify an installation directory, CIBER Roaming Manager is installed in the /opt/ifw directory.

Uninstalling CIBER Roaming Manager

To uninstall CIBER Roaming Manager, run the uninstaller.bin program from Pipeline_home/uninstaller/CIBERRoaming/uninstaller.bin.

Increasing Heap Size to Avoid “Out of Memory” Error Messages

To avoid “Out of Memory” error messages in the log file after installation, increase the maximum heap size used by the Java Virtual Machine (JVM). The exact amount varies greatly with your needs and system resources. By default, the JVM used has a maximum heap size of 60 MB. Increase the maximum heap size to 120 MB by entering the following sample code in a text editor:

%IF_EXISTS%("INIT_JAVA_HEAP", "@INIT_JAVA_HEAP@20m") %IF_EXISTS%("MAX_JAVA_HEAP", "@MAX_JAVA_HEAP@120m")

where 20m and 120m indicate the minimum and maximum heap sizes respectively.

Save the file as Packagename.ja in the temporary directory (temp_dir) to which you downloaded the installation software.

Packagename indicates the name of the installation software. For example, if you downloaded the 7.4_Pipeline_solaris_64_opt.bin file on Solaris then, save the file as 7.4_Pipeline_solaris_64_opt.ja.

PK\PKSqEOEBPS/preface.htm  Preface

Preface

This document provides information about rating roaming usage using Oracle Communications Billing and Revenue Management (BRM) TAP Roaming Manager.

Audience

This document is intended for systems integrators, system administrators, database administrators, and other individuals who are responsible for maintaining BRM from release to release.

Downloading Oracle Communications Documentation

Product documentation is located on Oracle Technology Network:

http://docs.oracle.com

Additional Oracle Communications documentation is available from the Oracle software delivery Web site:

http://edelivery.oracle.com

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

PK!î PKSqE*OEBPS/img/prc_roaming_incollect_nrtrde.gifL#GIF89apw!,p (((000888@@@HHHPPPYYYaaaiiiqqqyyyH*\Ȱ! HHŋ3jȱǏ CIɓ(SX˗0cʜI͛8s"p >ꓨТC"]zѧJFʔԪSbzկZ˕زcӢ]{YKݻxĐ@߿ L0 r +^̸ KLˆ/k̙0ΠC83ӨSװ'MaȶsM4mNq+_`8m'N=7س;jW}ϫ_O<#ßO?GHZWV % V}F~e0Jd U@@ (xRK A(4]h $#@(Bť0&1P^_!y7ΆPDr|V*ifBN d#L খ7u^TTfqXaDp2@kl0fyS05@ y@gT! AiA)+AjzZlȊ@"Р *fsTAb6fd mnP :)Ӣkx@8<0L<0(KJP; +#pe7ȱ)0@@-N+[8Ϙ-AUX,P(Y?i9zw@{A`/$3;b*_ʇ"O @c\TUOjv۪is9A,º.*n,܀0=~sw[~.l  .rٳ.Y]|oo,~gMb : +Ԙ +D̥~_x/ncVڎv8/K^A3WɇU5 Y ^ǽ3]t S MLr`GYrYaҮV3`@K080U͈l h)ъ&iO-)vX]iA@@S6z(!&C@":%K6\3YkVm @] ^$L-cԀOR<0K&,R~ dˀ@lRFL?(~e䧲u|.4?r"dήEo.c+W(Z~OY=O%qIK;avMʇ|+e<2f0(`+-BBNI[e͞$>%$Ht5ԨK0RJ_S%PPΥFqMŦ:0@ES :c Ĝ4B:)y.yɣ~@槢II&~JºԱc-8%\bLJOt P.#y)b6X4!me#EڞjZŖA'@ծlݎ҅&h Zƌ+3Sߕ RC5 +I7}RJl i^ք>wx"C+! $ƈL%PGk Gۜ jPaE+1R 8VU.] x7~,2J@I ? u$m$0[>2 Gɕ*e`fv[d /ĵi)zY4.Ёe(Fqb&s킜P42Y1aY|2^5+5 |ez{r-Tk ANEC ]c]73 TRauF,ɹ#Dzs6SO :΢(zm[*!7\Io5;NIQ)-TU-M 7o# lm%,:9:B.U`˞=maB@>@*; bh:xJ ME&T+|WMz,(Pmq][ET;ߝ:﬉O,3h 4MZK 0 Ygw'ukG+@:Sv PKplږ"K 7`JhlF\rq)եrXE*ɶo606zKϜ` Ѹ$<5pi wVQ4v8Wzj$>``Y?4ћ@\ <{FNxs~!Aos=rO܄9tp,V5%+E0ҎnGZ?yl-,ri10dpρPw0CZPdQ'S6>[aJ'}悀9ŀ XΧpG1*:gCz)ex3a~~+w&Wգo}ahf.ug G30`lwqay2!51I7a5\9XqVg'&X5v:eom}hLvva4'Y=Chvg2Y.A4@OL(m^L!zr-h"+-e,Ro $+r+bi.5V&~pc40bdK,aDVBbnK;`$KxDhk4Ӕ-%0q1Z+">.}"NvFcb#HF8~.T(jJO\A$s1-DVaDAniI0CEe3 LP"35Y4[CtX!6n֖qV7ɇFqS(e.)g6dd|d1iDj@K DY7pC:g4F.OFX#SrF:KrU˥1YraB50S0D5 b?)^[f>cCf!N)pi@s]>p#J9.`|#UPVG%d, Q6ͥ- uk31awc c0&).Oj#h7(-P=F6F\275(MT95;pȟA^fxDb_GM R:M%VXA$%yrU_:uHl5c'Gl>*"+vZ#q,yz{7{RT7VF`JJOfdm"_bWxd&g2%u;B2/& Ip~ -ڪj1-vZv#Wt"ȧ|CɆb /`:#C.;"o#;B!/231B#H˲^;Ip#Xwm~=1ᡆ{BBb`T1QMֲ3VW5OSr"/X%/CU/R'+:/23R6)_7  y/0;ZpFGeocj Mi9 gY?LG-ap*D3伀03@qFo{éH.IR:b4}qUV;K}b-[N?'4 dS@$QN^-d#$'ч%ܰ QFpƦ/kƩTvT1)G|Aa{eI5sDURR,4*3e0k-$溾bGL}Xd2zI9Z;êt8lTC^)e8Wf`.F!/ŔYDk;H0[o01ZKYѡV&|1fmirnqE2Ș4t4Wv&` 6쉒< sy*R`Fݒ+_rqܼg aѡA2[ϡ'ѹ(!$]ҩyqMѐ#?2$9M$:$Ya$8 M=:=E "s#>\eO=TAnxh*+BY}alq"h!m ѠQ 5!đ؋!z-~Ȭ=-]؝qz!ٿ.؎aِ-}ن1ڦ} ۊڀQ۹ۻ!vAܼ=Mץ=]1i o-xݱ `nrޱ# [bˍf=Xݽa] `>q.`߱F<; 筦!aܶ% i Aԑ8Qؑ9W}ꮁA֖~Pq^}N@ӍQQ7>^0Sn @ *^>؎Q%0- 0 V J 2T=7_6o8=AD/~*  P xWqZ/|qb/FcbhpAH``? {O`Npuξ H/M|B[/H^M_! q<>.(2]Sa*v}'5 ֣#?AsΑaR0R*i,X̩O.pfB)̏j(+Ū#UIJ4*EjF58_@ DPB ać-^ĘQF=~RB  8a`:  M|"00 * Ԁ`hP(G#zUkH 30VXe͞՚Zd 'LKpn>(@ 6 &ldbdɕ|(fΝ=Lh*5& xȋ8fPT8О7k$=C e(Ak0uݽdBac,Xpz"? `2.(( ¬B 7p&rHD\.C41 @r"@Lr&,62:L t Ӫ B&"Xc(bJ=rl+ xl,O4tr, zC27bMܘB@ؓ? PQ'xL҈ՅtұQ֐,8V4'SS> x 8&0Eӂ 5@*(76jl(u`pV"x smguH - S ;TM7t>MbsK >P8.%)&hض*7dzʨqDIe\ *%QaO+ N$/ZOU8R>#wR#6A ]u RbŒ'c*pdRd ;u.@1fo">xj!?p&r?_0ͷ tRS =H/u&cHi{}a' Bs%^vަנO2@7_| i7Rٽ끥iAaErµ~0I =Uyk 7ąSxIni@1hަ$DTkg (`|/\x>}7!iCЇMsV7b||3

D4uyRXz`/1;Y]4Nz+|w3t_HZ vFHuhFcd.C5΄U!@ͅ^ⴚS@.oSb4(*7t56!<47=5.;XIk.@ e+Nm=m6.cɦ`P&rI$GWߔOGi^\A<*`nhy@HAVb0cEi]DCXI/)B`y:CqXD(D QrsƑ9:Vj$]%0&ŠI}n-Z0 q'Y'5#D 2<ܓ(Er xB:XkxlH7=;LXTS?['XMG~b D1OAޓ *aOחp&%.0 U)_2"zZ9J2D0KGkRv{bpyR[_ˆ#9wӹƾ' Ve:VQэhT?*4g}۪?/UOb ?cҾ?2Q !l@D@t| @ @@4@ɿyQbr_J?I;Y3%BJ«XB)#A)&,BijBByB-)C8C1dZJCy![0,l:8te JѣH*]ЦBJիX^!׮`ÊKl֯fM˶۷p&\kܻx.Y| LO +^̸_Ď#KLyjⰗ+k̹]A{MtggM~ɺװKMvaXqlLnygo7Eyp㧕vz֡;URVݷw3oyO_~~G_i~{A&d Q6{- zM EcAh C#cA9UbOgSF%B9EזyeuI'dJؚ'*xf S)ez'\fQզ袌ՠ5褔f!c0 gaerj^bz{ReV$oRE\bUbu_J䫄nj%:E!yd҉pJ;-,>:hĦKƹ7z~xe/p+Z7&,6j^U,o١͍l1P;0w|-lz"gLrQ`o f2nԾ. *ܯ0?7MNs0l%<,clUO]b4ks׶6)綍[5Nkm.G voֈpKl s y0 ]݌cΰlלi^ }8Ow8_>ξnT:wnUzr+vؖ[U+)|E:~||9K靕~>vւ[iζ0A{GF&h~+gj+ :K”@Ƀ#3!T6ۋ`RPm irCvagO{Ԡ%UOU8/ZEuܒCaEP`s?"za$4BpY4q}͂kJD(Cqs%aFq0)V0ÖGHQYhXK :%?qlca![H~mkgĥ!+9N<_2t( q.a4y]Frߌftn bږ,]mˍ:Ԅ-/ZwV 98o=?.4m^[ -aP*9+mbxDsһS2=}N9zIzhK; nQ褡QI ٣s jچyoc ]^z9٠ioz0*2: kJ Ʌ[ùF6Z}ʐq8Jz\z˹L|\GȤ"Eik"*E*t{w|ZJZ`::?TcË$pZK:4V}?ګg/ɓ:*7*['{H$F<\*rj~ɦjElӃ$4rqZ;q 9{RV KI:6MQs[%XJTĶﺢj{8  XMgJ 5V3X$p'۲;hBņH7*9UG?|79:3̚uBX\X] !*S{Ht/Xv'ڨB!Hy#Ō;XbJL*Ņ%KJjEt\ex0iȸ;||V{jr:u8O R|4˻ǫK`ʗJ {KkKOؼj@YkKuӕԻؾHuP8"H_ԻM vp#rq/ƾUkKajJ1٢#ѡ'|),r&<4<}JZɯ}~;>Bn[ pz9 ,eJL,VF:an˙f kŀ¾k|Ő9ǰڭi*v#njhn̶v \F} Ȑ|/ȓ ;Lƍ<ƛǝ̭TH^q:ʃʡȢ ʕąLnW˱,Vl˼< ̽L~\ܑ9I̻̜|Ь)Y\MȬ̌͘\<+;?mٴ]7.Eں^YgWJܷI8oG=teG˹ q|ڭղ@eHUm2SȁHca*w}zۙ|n@Q>mђ&v+S= VW:2~- >:K|}2=:~zm>.Y-nlƗL- .ВdQ~ENH5I/hזǼCf妿k.@S[^HaOM|I)y"=굎[<+Ƿ~v\y7l0iݾ}Զ{G}#NٮϞOZ >t8n^ߪι>F^Nq Zl (]Rdl Ϣ=^ # }v%/^L+ -sfixNG~0xNL"Ύ/@+tlM2?6SgÁ[Lo7T[ rX.x`>j_c&gr`u_sO {WmWO?5q̍Ƹ*(_ޤdk§o^1/̕_ϬP}|?D/EMxEnnn{^͏YGq_9cco> 4oAtJ1@ 3԰ZpmB 4DSTqEpCcCJIDG #ch1Htɜhm6(J,?8*K0,-2T34ӫM0\sNNJ9곻= tNBwJt MFutR)OSNN u:+EQU58L;uaKSA[s}Vԕ_u]Q^Uem&5YiZVm[oW7\%wTsU]vj7tߍ4^y^Bw9}ճ_85&X53a'ca,x׉ە.8H7>z;YȑhQ>dkY]_*f(qfeg~z$~hLYiy:uj3zڭ3:lflXFٵIUm`fm{ػΛSmc|p 7K |rAzv2s]k ͳWN=bY/ot_ruǣ5۫=vw>c>xȔ7RM|^QQgKen{K,n򍳒sw*HXuw2?("?4} }C'0O3'NCҞ#}TI{C [ h?Y/|m4*G+4[#5qfdBA(  A=$~6hj)5ܡ?|]!Ƙ#'̚ CE P\ 3Ԣ? 0h-E)dd#&?Nb)qӃ&ݸDM&yƪrx{dQQX(MYKZa%.L,T:M| 'K6撏%Y@=ͻ&0 ERIV1S`rФdfb(HNa',iN e"H"vR4*!yT#F^R -ZDBR%e72),gA :T3d?ZQLI&-y+8 62$M]^|+QiNN}*JiTJ':ձflqQ]S꧵^U|ZٕS\۪׽`uXu*=,bzҵfe-{IlgsXK`.p`:NpqKa24#+gZXҊ]Ge,A '<m|vFO-Lf gYäN0L1:?la)1W~ yza6oU25aҎ6q2MAR6O^р 3ymi7gi"q.` ]i61*̫y٢nwLo:2@['6Mx),BpOpkkI&E%yÎCM۬2iF7WOu\'}O{_jH^Mu\1VJ[@Ǜ"MAC2; ?;9d;5%ӣ@6;{3$\}*=@ <;J8{5כN*ԣ33;ћS&w#<((2k!$"4'\q{#B HmHebZgḏ\~>@N18KoAM9^nC|w=|So=fo_3U[VUoQ~X6ߔB/ԿRg} B`WHPz $y@DhApeT3޳X0 `crq(zSB/`csݥXY!pXEsU~8M- JɎ6q\'cO*Fat<2N"T̨x)P>g/ }țvn3[JҖHE"Xԓ$9PK2ENٙ*ʟ"i;O2@&7$R(y|( [e)%F'Y)V'\ن9!j\ )k^Sܦ8d13" BG72  AJH=tO|0fCRnp-\D::&ΉV8\(ՈDoɘԥL Io2SxW|)s UG^RT̫@>uJT 2UTU(OUIVs-$]]IXC֦cE*jf'jIzĭadkyh!32wT商UHNj҆z,2 EDKO3+`f>d2SeN{÷e!fڧ8v6|]D 5y2<62 M*$ya!5nۉt5ˀ 0Ys Len4tij2nD,R. MJCM[+\t(ϡPx , 25}2 ` OZ8Ȣڣg*QRۡC,%]5d "*NCIJXҎ$?EI.bTJɛ~I?-FN{K`̐RW)g5Y-)G:qur=ɻԒP5[Hv4;UQJIr'Uה70 :Zl8M@,15;.7U0#tΉ24"F-ʐb`9%sKVÍkě&<΁ ZGML!-1QE &ìewB[ugIMr+VP>"s,~g$HᩴHGRK'$s)-QwFȕpG]i⠀S̹V"LIevp\C`u>H—, 02n&߳u<vkzD$b*Ȼ^rר4/3 G?_juưL9lэzV|MhL(E*47 kq`6K#Gg.UfJ[-4 Fmsp;vOG}OR{#|r,[U|XjQ#W2S2;nmQ,qkd":3684~~QF~-pl%6{/'4\4SR "';sH{S~BfXSJ7T W~TAkgg!v&VK a"ݱ w\#J>nVHgbf#{a7jSRD1b=3g6E,9,5!!7Wr]@E3zdnW]=XH(b85p-q*h* BSkhvX/_!g$ aq\ qqZ"7ƒRWRKxQTG(IdI"t 4v)J* +**-/ (:ue619P5JĩB9`CzQ=X?]M>[ ^88fJTJXJcٖZ٥u8>_?Z:=)]?lYjJ1GaHh!X: sQh}^:ĥUxU*9X)sBeqvs"5 %f,n& ^aegsi!i6z#3Ea)~"VvHEa0`%SzБt7.Oro:aaΆ$3'7p-o 8z%Κ?*gI"Zzm?)ZDamhGs9xj߇Z@v*¯5G 5q2)ᚫm*\-|235犄]=jg(7ADs)E&L@˝%lLx(y5!8Qo:!HV57NēAAlб0W~hk ans.[Qx?(!brYֵct咅 n 8&jKwe떅oZLnqYsj74j&pKdcj;H3\z9kG{Y $5> ( m7Ņv jwȺNYQ{ۼj~y~=qb*4%5g=B'S[0 iXTcH'x^a74χ-ۧ^v'ò jenh*Ucq+<'܉T8#gHA.O@59|z2jf`TmwpAXjA8u«arxVa5[`ئ¬!)rb\ d)!nim^"&5qi8j<%ܗ| ho1}c \n\D<#v5C,,c+0憎u`iH[*8&s\H L}cyb=24G+y 3y8?q()##[g#q(2&ژ(vBX\&d4W.Q3'v<Ξ9v9/'ϸ2vW9\0eESS 34r6" +4#!@uW'A&Hva-͓xjb϶M@EvbOh!"lUv+MXY\&)rPnf封a^ޣx)A7g.1on`NqE6[Z(޵qNM#rR.]ԑ4\`w4|[.o3#d7骮2K: *fGjוRNOWǿ 'dT\N5L>^;PK8ɊPKSqE&OEBPS/img/prc_roaming_rapin_tap311.gifI&GIF89aK,KH*\ȰÇ#JHŋ3jȱǏ CIɓ(S\ɲ%B0cʜI͛8sS˟@ Jѣ( tӧPJJjӪIjʵׯR(vٳhӪ]+,ۊnʝK]q2̫߿ Lp0È+wT6kx˘3c9زPL ݆^ +M/] `L׿ 8Уm+_\ĉ_껳~~{ڸng{}w?? gzg_l%#ɶդqt v95v^{q\l=0X4n['aafhfxuҹw݄Nb>ɝfE"u3Zx"URy$[p_siu^Vwy YU(*w\:6*giBj)f鞗vߦhzc (*kmzU+V6ͪklbz^&"([szQoV+mH48b$5MF*K"i~EFJphfQ.Iod wt7Shkq+HU# KyMW1ogw|{9W.ކ>ɣ,3c ׌$gq?1r'Cm٬őV;c9 tVGm!d:*K781Tg k6}zOξgug?_I_IاP l d' EP n0{,BAq{% 5B/#l ;@6pa^HxޖآKq#O\KO3)ŊJǪD b&0+f"FL٪8a6JĎocF.9e6G"DcN7;j+LUID'vљ V3MG~Kn¼T+ eLfnflbA]mq#`RI^bsSلi8]25HcH~aNE\\hgILxYT.ixRQeXysp\TiY0],#(չ6f"fx&e;BveY\64kˌ1 )Y>Ť'#Y̋)lEۆKcM(?UB[BtrsV$gy<V/WJ SOuPƊI"Vե”bN (`P֭D&$RUԦQw5+KUf[+Y'TбleٹZW|mb܊ϒ'% iEY֠P#wiؐvjcַ֦-moM \uq툪$+A EH67k2{.q;S MW@oxBqm&n= f|u^7!) ^ 11Kn_VmRkN> l"[n[͡i5nqDҪwÝ.MXܵMLV*0W c>q1-'<-[B*[*$-[]*֐?bٸ> f Yl5΁+t^!b :)Wu3΍+fNJ3kBZN,=Mmq#jnY_ 4Id3f(Y5ӎ k8:Zr!\5 >t!c]v\_Ҭ2OR mjܵ i|dZRYW6l\z;f7%Qi]lc%vʖwZdNIg2oz]왬^Q.O$aG'W1K3qW]s%-g)r9aIO@U۶7=6x5#E5{n='tT5z9a-ׁ<먉Ѿiz?x=}K}ׁ $nh"u6u_X(TGx7qMgW:!"AGPcm7kq2W}OV$kGӀ~{`~wguflD&s/? 4Gf6N^₫DjXxr4gRfiORlXHaRXVd]ȄLq|PiNjwM}sSȅ慿d#/1:>eHhgghHvLvNxxjZ8v8fFh_tY]pxHpنt-^׌w~6[ćs7jTI$钲xJ|iv{)|sXv Ix% xvj]l)}NEGE)qu=F4H841QF#Tnw}z(و9jI#ǩ)Oz(9W-( y Yr699^%"ǞmYqiqEW>+_ QHI!iWT:ʡZ>:#J!Z'+z[%/;1J37Yu;?=:6CʣiBGp- W hEKY:WʥZ]I_ꥱ1ʦmڤIijBJJ*'§}& c*2J{*J!*~JZT 2u:xejک::ꤤyyL:g*ܸ;ʒbj;nezrwrΚȫժu'+Ժyv#k;II2Yʢꪒ*jӯ׺Ӳ$X X@*Sw<ؠq* Z=zA$޺&K谣t-%ryџ{I縱[zʃlȗ}9zz [;{b[J}lx&46b~gv(=AU(4B/#{>YtKgW ۲!w{lٷjzA<HJV4tF+jt 2k˸&GXfn{׵|K`۱ݪWy+۰q˯%h>OtWJiVf)h+joxҙyfy_)~L{K,KVpheu۸6\F;>Ɍٻ5۶k,z[[S+.[ 5(m6k\*ܹus#rFgخ'yM('&:É 7k9xcNIZ ^Sl{B||̕ˏ{ùɌƳY TQvMI}yT|J,+Yғ|3Fuq=uۇ۽+eI`_\lzrw6ug\:̰d| |,Ɇ|)~YÓ6lz$C83Ia\̻fH<߫ʺ[H*vXb)Ƒ ǔH[^z#\}!LOeC[ uzΉZVuܚkʕ5\ ̘$K&;j\i)~<2+bdT\)]{0:l 10 =-D=(m18לhol󛷑 ~ p)`z%<\|DJ>yС< Տb̝ØlM,.-mYmt}_y/d7Ѵ6 j=uVי' ?;#oԓӕ|4f=ڔ\A ۀۥ-oMf2R]zm]*ۧ< ˍh n]]KZ/Lx]ԨM cZ'; څmҽߥ. m NqΑI{l-ϵm79ܟ.ͭƽۛM%]Zm*~GT=.)Q4~6N(@;N5^G[yQbc;?>\⦭B( *bdf> >j Lmz|ڋ{>u^wyA~[S貊*=nՔ>C^>d4-\M?ߺa B`~㩮K]DƎB-:V^\~M4ɮ.N̾О~,T厧nnc혞 C.=Sn䋍܇ǝ)ּ?>n:yܞβ. .ߙn'~n#|qO^L9jƔy;6{]IPHS?do ^-$^w\ܙ}>~(9̘ÿiOROn=|;7~`oݘg_^͛no_b.G?w{9"ϻG: mwYEQ/qQ dk-/>2.biuJ_wȈ ߲dzٖ zP?/ $XA .dA%6E>E!v8dH!KXeEcM9u䩲OAެ9ϙ"LX)Ȕ)B8SRtʔVa:YeѮUSO-(WUuml߻k ay6jA2o'c+6L@ӌKB)LqEDJd&[pFqK)jQ UpGJB$IzP**[J3=.0L̒<J諑bF8qሲ5C6_SP<UK: MqPEKR@I53Yg@mlOzh}Yf{ΚKHt6 4VҺݑ%wlΪg~d.ѦeQTQcL6Zg[ߵwҾ.>E[C Xl#;Y8kQwfѽ#}YU\vYOtؓy,s}zUm-yߝlaΥ?zY{_|7|lom֟QL~k\~$M(`ha5hnp4`OgI~ Eo gqPi5az601UK62kq[("q ]#B~S[5h. P-^UhFYɄA%mUl?}07R)K=TA֔mB` tӨ9M} a󺸹`DEc"fߌ3oVNeLQ owu,Y|V-7jjtF9#W,4[WzdW,kZԜH jDoڻ1ݻϢY!Kw8Y<՘ GMlC1_˶haAY 7ҋO) /yhz[GMB!pnU`#;ۮ lk+zFyV~ s܍T9xZ3WD%Ķtj۵qHL0mߝ6p˲&)dT+ݟ v}\Jfs5bU;r~^c{0_;cu! zExfs}p 5reGi<\s-jwvW/^׍)!xV*<_#d;5~_ݼ|c=/{ےgz_ϽkۯIt{^w7>{~7nQ_߿gW,?翱[33c@C:K@'d?t{{: |s @@h;-$ #AЫ TW9lA=A L4>,곿T A+;"TBdB tBby)B,*۾.CڢBARaC334/0ٺ&Cq\=@D| ?DC#BD$'@lw:HݓTD}!MtĜCI4;2DR̾PlJJKEq| EX>E\'F;`4:?d,< ¬zƣS!ZF-y;G4+L:qSEk8TFݣu̻;ǵDFHr4zF9A^RǪ6vȉtGtȱCh^D3*(FGA,2GGșLHxl:"*kǣ@G,Eg#TʘExɄ 7o̳-ʫlE7?˥L/3DcTK5Q7@Őp GEI ͅEUL-MeK||" T%Nu"O[NUjS+r>/URau&bL#MV?%fgǔU}y lmK҃|iMG-Et3u%IKSEWm:WQ<ӽXW/ÊQ}5@8MO0YmXw-X=OEJG˔w؅  V\ YunG[ۘ^Q/j}H0S0 /OJlqAn|q{l)"{Kro\qo*$<1,9k ]٫Һ4+.҃Q:1I.|3~4jy=h/ [v𒝗ݰz-t}pߥ.q ۈ8Cn>R29ۜxkYZ;zٛ{ez.fZw䶓X~{.] oJA߰I.1mMsܻQڼW;a?,`o?lO.l`Bآh;N `w?v:do&)8ZEK`@ S~"TӲŎLeXgUA΃TF*EqVF<9 7S6dDP@,bD@QT,еE. a*1JjAy~ *H" ¹cјH-T$!IFDc4w iQ|B1zFTT9}h]ֲpeG`PRNF[_, +vKgNJfWmpkdzn"34 &5gLk*$f) OT&12(ѕMUrD:7yObg,L%/)J-2 APԛy\?)7tQDŽԤt2 v*8}LQҚ|e0('eLhc՗ DRLd7Q\6T)QNE}S!EH>rD+QUK)P ERF %(C(V&HN+]҉0Ӱ k=9zNJ=i%TT:ј,W|<òC)˴;S Z-lZΝV^yL!YWQ17|cn]ZacGr=3z.pz%e{^=YLIEqMc,{kK}K[lgn-ie k=b8w`[ǞuAx\NTmi'Y|8اiL1ٺccL80ZW&;7n W(8ti՞&ά;b'HɮdY 9Oh|epiOñ>P|F+ȴL"&̽j#WsH00*[!Y'hJAcUr/5m@'>2g^YC/XU[γMw.>8¥j$6m^;΢(mh@Ȱ7]6LxdF}L 8Q']Ե^m>zI ίF7dcepWisgGodF~ÓVo ˕wS/b|9oGIygH/>{+}o\oqWR}?ՏwoK}Ӿ<+׵a1Hs%2uw39wzegv؀vCgG<x&o: xu2xՁthIvZV_X3HV"[wTLeVVfEk8;qbIƋ,07x:p5KMyRT :sjƴbNK񍜊DZfTs1:Q+(BA(dTW貶ԎCzۥW>y ?(<zxk+:;뗿X $G.⨪lK=X 红a{i3o~K r˳bٲڻo ۪0cusZzfuLjr3[}Hw:B ˢt~k K'k܅sk˻:^+Zz8j yj'i$,hP1"\kO<@k\o#Ubk:OjPok~I )7%ó44lTMN{[Ł9L'{@gf̾pr*ܹhJ"ȭǐ_KLJ+ɇƋˊǗșܸ.<ɠɟɏ\ʊ>,ˢ ˷Lɭ˯Lg,̱,e \sɬg6|Ҽ(,υ~'l%ܠl{å[ΔrмΣ<̑|Ϯ|쬟| )\<-| q,m}͝-4 iW3҄ *Sҵ0Ϳ=˛8:a l@̽LL},-5Llռ2u,բb MEݗ O-0IiMaosݵ 1_ "MCԉmթԑE3:}oiϚj!Ⱥ bMR[i;%آ;=T-tM۬k]SXaJܘ+Dj,咵|] 2nvIlT,s܀%:o2M=ȹ}ؒ5{HYd㺳XG clkV߫؅.m .(F%15nC9);-I+\(ZLx݈HO 0ͪ0 ChV08(g6cJ]y[Xm^rֲ.unم---v$*4â*ł<羿.Oynm^ܩޞ o7]?~b!׾[|/QLg7'K5AOLO}JOz#?ASm\nY+띎͸NhOng0]Ѷ%C;캞̾n~OonhNؽnzr >>!;[ve^>+#< WF=_~&"^V~lpXS rH~rfԇ|0,u|.cfr$|$|*_ŽȃBZ-KOFȇ$ A &,B#6dxa cG3Bh"IQdK1eΤYM9sٓ$OA_tXѢ+y,iS% > ՟HWaŎY3riF.ԸUޅQbZ&\8aĄNU˘ܸ嫒ܐ*{5gEKڴOiYұz6I1ح=o `_y]nЋO^rCnRa߭?yfTs[uO}e./M68##&+AoB 3-̤73Ю72(<1D$/0qCk5RlQ*ZE |BKrI&MOG3A֮ܫ,m 14̠1+r79sK%*Ӽ=\sA +4LTMO@+4O9I\s 9ZBqq1\4BP#EXJ]U MYV\sFl3u %%ULeuf˭Zl}v[g[nIpa-w\tӵ0[vu]xU׺;PK' PKSqEOEBPS/rmg_rap_edr_mapping.htmJx RAP-to-EDR Field Mappings

9 RAP-to-EDR Field Mappings

This chapter describes RAP-to-EDR mapping used by Oracle Communications Billing and Revenue Management (BRM) TAP Roaming Manager when processing RAP input files.

For more information about RAP file processing, see "About Handling Rejected TAP Files".

Mapping of RAP Fields to EDR Fields

When processing incoming RAP files, TAP Roaming Manager copies the data in the RAP file into EDR container fields.

Table 9-1 lists the RAP field and the corresponding EDR field in the EDR container where the RAP field data is copied.

Table 9-1 Mapping of RAP Fields to EDR Fields

RAP FieldEDR FieldDescription

Sender

HEADER.SENDER

The Public Mobile Network (PMN) sending the data.

Recipient

HEADER.RECIPIENT

The PMN receiving the data sent by the Sender.

RapFileSequenceNumber

HEADER.RAP_FILE_SEQ_NO

A unique reference that identifies each RAP data interchange sent by one PMN to another.

RapFileCreationTimeStamp

HEADER.CREATION_TIMESTAMP

HEADER.UTC_TIME_OFFSET

The date and time the RAP file was created.

RapFileAvailable Timestamp

HEADER.TRANSMISSION_DATE

The date and time the RAP file was made available to the Recipient.

SpecificationVersionNumber

HEADER.SPECIFICATION_VERSION_NUMBER

The specification version number of the TAP file being exchanged between the VPMN and HPMN.

ReleaseVersion

HEADER.RELEASE_VERSION

The release version within the Specification Version Number of the TAP file being returned.

RapSpecificVersionNumber

HEADER.RAP_SPECIFICATION_VERSION_NUMBER

-

RapReleaseVersion

HEADER.RAP_RELEASE_VERSION

-

SeverReturnValue

TRAILER.TOTAL_CHARGE_VALUE_LIST

TOTAL_CHARGE_VALUE

-

TotalSeverReturnValue

TRAILER.TAP_TOTAL_CHARGE_VALUE

Total value of the severe returns within the RAP file.

ReturnCountDetail

TRAILER.TAP_TOTAL_NUMBER_OF_RECORDS

-

FileSequenceNumber

DETAIL.ASS_ROAMING_EXT.TAP_FILE_SEQ_NO

A unique reference which identifies the erroneous TAP file.

CalleventDetails

-

-

PathItemId

DETAIL.ASS_TAP3_ERR. TAP3_ERROR_APPLICATION_TAG

Tag Id refers to Application Tag Number as defined in the ASN.1 definition in TD.57.

PathItemLevel

DETAIL.ASS_TAP3_ERR.TAP3_ERROR_DEPTH

-

ErrorCode

DETAIL.ASS_TAP3_ERR.TAP3_ERROR_CODE

Code associated with the error found for a particular field.

StartMissingSequenceNumberRange

DETAIL.ASS_ROAMING_EXT.

START_MISSING_SEQ_NUM

The first sequence number of the series of missing TAP files.

EndMissingSequenceNumberRange

DETAIL.ASS_ROAMING_EXT.

END_MISSING_SEQ_NUM

The end sequence number of the series of missing TAP files

TotalTaxRefund

TRAILER.ASS_ROAMING_EXT.TOTAL_TAX_REFUND

-

FileTypeIndicator

HEADER.DATA_TYPE_INDICATOR

The type of data contained within the erroneous TAP file.

OperatorSpecInformation

DETAIL.OPERATOR_SPECIFIC_INFO

HEADER.OPERATOR_SPECIFIC_INFO

TRAILER.OPERATOR_SPECIFIC_INFO

Information that has been bilaterally agreed upon between the Sender and Recipient.

ItemOccurrence

DETAIL.ASS_ROAMING_EXT.ASS_RAP_EXT.ITEM_OCCURRENCE

The occurrence of the path item at the specified level.

ItemOffset

DETAIL.ASS_ROAMING_EXT.ITEM_OFFSET

The OffSet in bytes from the beginning of the file to the start of the item in error, beginning with an offset of zero.

ReturnDetailsCount

TRAILER.ASS_ROAMING_EXT.RETURN_DETAILS_COUNT

Number of returned details in the RAP file.

TotalDiscountRefund

TRAILER.ASS_ROAMING_EXT.TOTAL_DISCOUNT_REFUND

-

GuaranteedBitRate

DETAIL.ASS_ROAMING_EXT.GUARANTEED_BIT_RATE

-

MaximumBitRate

DETAIL.ASS_ROAMING_EXT. MAXIMUM_BIT_RATE

-

HSCSDIndicator

DETAIL.ASS_ROAMING_EXT.HSCSD_INDICATOR

-

SMSOriginator

DETAIL.ASS_ROAMING_EXT.SMS_ORIGINATOR

-

SMSDestinationNumber

DETAIL.ASS_ROAMING_EXT.

SMS_DESTINATION_NUMBER

-

DiscountableAmount

DETAIL.ASS_ROAMING_EXT. DISCOUNTABLE_AMOUNT

-

DiscountCode

DETAIL.ASS_ROAMING_EXT.DISCOUNT_CODE

-

NetworkAccessIdentifier

DETAIL.ASS_ROAMING_EXT.NETWORKACCESS_IDENTIFIER

-

IMSSignallingContext

DETAIL.ASS_ROAMING_EXT.ISM_SIGNALLING_CONTEXT

-

Imsi

DETAIL.ASS_ROAMING_EXT. IMSI

-

HomeBid

DETAIL.ASS_ROAMING_EXT.HOME_BID

-

HomeLocationDescription

DETAIL.ASS_ROAMING_EXT.HOMELOCATION_DESCRIPTION

-

Min

DETAIL.ASS_ROAMING_EXT.MOBILE_ID_NUMBER

-

Mdn

DETAIL.ASS_ROAMING_EXT.MOBILE_DIR_NUMBER

-

TotalAdvisedCharge

DETAIL.ASS_ROAMING_EXT.TOTAL_ADVISED_CHARGE

-

TotalAdvisedChargeRefund

DETAIL.ASS_ROAMING_EXT.TOTAL_ADVISED_CHARGE_REFUND

-

TotalCommission

DETAIL.ASS_ROAMING_EXT.TOTAL_COMMISSION

-

TotalCommissionRefund

DETAIL.ASS_ROAMING_EXT.TOTAL_COMMISSION_REFUND

-


PK(FJJPKSqEOEBPS/rmg_tapv311_install.htm Installing TAP Roaming Manager

5 Installing TAP Roaming Manager

This chapter describes how to install Oracle Communications Billing and Revenue Management (BRM) TAP Roaming Manager.


Note:

TAP Roaming Manager is an optional feature that requires a separate license.

System Requirements

TAP Roaming Manager is supported on the HP-UX IA64, Solaris, AIX, and Linux operating systems. For information on disk space requirements for the HP-UX IA64, Solaris, AIX, and Linux operating systems, see "Disk Space Requirements" in BRM Installation Guide.

Software Requirements

Before installing TAP Roaming Manager, you must install:

Installing TAP Roaming Manager

To install TAP Roaming Manager:

  1. If the Third-Party software package is not installed already, install it. See "Installing the Third-Party Software" in BRM Installation Guide.

  2. Go to the directory where you installed the Third-Party package and source the source.me file:

    Bash shell:

    source source.me.sh
    

    C shell:

    source source.me.csh
    
  3. Download the TAP Roaming Manager installation software to a temporary directory (temp_dir).


    Note:

    You must increase the heap size used by the Java Virtual Machine (JVM) before running the installation program to avoid “Out of Memory” error messages in the log file. For information, see "Increasing Heap Size to Avoid “Out of Memory” Error Messages" in BRM Installation Guide.

  4. Go to temp_dir and enter the following command:

    7.4_TAPRoamingmanager_platform_64_opt.bin -console
    

    Note:

    You can use the -console parameter to run the installation in command-line mode. To enable a graphical user interface (GUI) installation, install a GUI application such as X Windows and set the DISPLAY environment variable before you install the software.

  5. Follow the instructions displayed during installation.


    Note:

    If you do not specify an installation directory, TAP Roaming Manager is installed in the /opt/ifw directory.

Uninstalling TAP Roaming Manager

To uninstall TAP Roaming Manager, run the Pipeline_home/uninstaller/TAPRoamingmanager/uninstaller.bin.

PK9qPKSqEOEBPS/rmg_about.htm-QҮ About Rating Roaming Events

1 About Rating Roaming Events

This chapter provides an overview of rating roaming usage using Oracle Communications Billing and Revenue Management (BRM) TAP Roaming Manager.


Note:

TAP Roaming Manager is an optional feature that requires a separate license.

Before reading this document, you should be familiar with the following topics:

About Roaming

Roaming is the ability of a wireless network operator to provide services to mobile customers from another wireless network. For example, when a mobile customer makes a call from outside his home network, roaming allows him to access the same wireless services that he has with his home network provider through a visited wireless network operator.

A roaming agreement between the home network operator and the visited network operator defines the terms that enable each other's customers access to the wireless networks. The visited network operator records the activities performed by the roaming subscriber and then sends the call event details to the home network operator in the format agreed upon in the roaming agreement, usually Transferred Account Procedure (TAP) format. TAP is the process that allows a visited network operator to send call event detail records of roaming subscribers to their respective home network operators to be able to bill for the subscriber's roaming usage.

When the visited network operator sends a TAP file to the home network operator, after the initial TAP file is received, the home network operator expects more TAP files from the visited network operator.

If the visited network operator does not provide the TAP files for seven calendar days, the home network operator sends the Stop Return Returned Account Procedure (RAP) files to alert and notify the visited network operator that the TAP files have not been received for the last seven days.


Note:

The Stop Return RAP file is generated only if the home network operator has previously received, at a minimum, one TAP file from the visited network operator.

The Stop Return RAP file is generated every seven days, until a TAP file is received from the visited network operator.

The home network operator validates the data in the TAP files to ensure that it conforms to the TAP standard and to the terms of the roaming agreement. If the received TAP file contains any errors, the home network operator can reject the entire file or only the incorrect call event detail records. The incorrect file or records are returned to the visited network operator in a Returned Account Procedure (RAP) file.

RAP process is used to return rejected TAP files and records to the visited network operator for corrections. A RAP file contains the rejected TAP file or records and additional data about the error, such as the error code or the error cause. The visited network operator corrects the errors and sends the corrected TAP file back to the home network operator.

The visited network operator bills the home network operator for the roaming subscriber's usage using a rate agreed upon in the roaming agreement. The home network operator settles the charges with the visited network operator as part of the settlement process.

The home network operator then aggregates the roaming charges and bills its own subscribers for their usage in the visited network.

TAP Roaming Manager supports TAP3 format. With TAP Roaming Manager you can do the following:

  • When your subscribers (home subscribers) make calls on another network, the other network operator rates their calls and sends you an invoice along with the call event details for the calls. You can charge your subscribers for their roaming usage, and settle the charges with the other network operator. In this case, you use TAP Roaming Manager to perform incollect processing. See "About Roaming Incollect Processing".

  • When customers from another network (visiting subscribers) use your network, you can rate those calls. In this case, you use TAP Roaming Manager to perform outcollect processing. See "About Roaming Outcollect Processing".

  • Use the settlement process to settle incollect and outcollect settlement. See "About Settling Roaming Charges".

About Roaming Incollect Processing

You use roaming incollect processing to process TAP files that you receive from visited network operators. When your subscribers roam on a visited wireless network, the visited network operator records any activities that your subscribers perform on the visited network and sends you a TAP file describing your subscribers' call details and the charges for these activities.

Roaming incollect processing involves:

About Validating Roaming Usage Data

Validation of roaming usage data involves validating the TAP file and information in the call event detail records to ensure they conform to the GSM TD 57 specifications and to the terms of the roaming agreement. This includes:

  • Checking for correct syntax.

  • Checking that all mandatory fields are present and contain the correct data.

  • Verifying batch information such as total charges and total number of records.

  • Checking that the files are received in the correct order.

To validate the TAP file, the following types of validations are performed:

  • TAP3 fatal error validation

    TAP3 fatal error validation is performed first to ensure all required data is present and valid. For example, if the TAP file is missing a required block, the entire file is rejected and written to a RAP file.

  • TAP3 severe error validation

    TAP3 severe error validation is performed if fatal error validation is successful. TAP records are validated to check for incorrect or missing reference data or content. For example, if a TAP record is missing a required field, the record is rejected and written to a RAP file, but all other TAP records in the file are processed.

About Repricing Roaming Usage Events

When your subscribers use a roaming partner's network to access wireless services, the roaming partner network operator tracks their activities and rates the usage based on rates agreed upon in the roaming agreement between you and your roaming partner. Call event details received from your roaming partner network operators normally contain a charge for your subscribers' roaming usage based on this rate. This charge, referred to as the incollect roaming charge, is what you owe your roaming partner for your subscribers' usage of their wireless network.

You can choose to accept the charges passed in by your roaming partner and use them to bill your subscribers or you can reprice or mark up the records based on your subscribers' roaming subscription plan or retail rate.

Repricing includes a combination of prerating, rating, post-rating, discounting, and recycling activities. The rated records are then loaded into the subscriber's account in the BRM database to impact the subscriber's account balance.

About Generating Stop Return RAP Files

You use the Stop RAP Generator pipeline to generate Stop Return RAP files.


Important:

Ensure that you set up the Stop RAP Generator pipeline to generate Stop Return RAP files. See "Configuring the Stop RAP Generator Pipeline" for more information.

To generate Stop Return RAP files, use the Stop RAP Generator pipeline in conjunction with the StopRapGen utility. The StopRapGen utility collects the information required by the Stop RAP Generator pipeline to generate the Stop Return RAP files. Therefore, ensure that the output directory of the flat file generated by the StopRapGen utility is the same as the input directory for the Stop RAP Generator pipeline.

When you run the StopRapGen utility in conjunction with the Stop RAP Generator pipeline, Stop Return RAP files are created for the following:

  • TAP files that were received by BRM and stored in the database more than seven days ago

  • Stop Return RAP files that were sent more than seven days ago to the visited network operator

Additionally, the timestamp for when the Stop Return RAP file was sent is updated in the database.

See "StopRapGen" in BRM Configuring Pipeline Rating and Discounting for more information on the StopRapGen utility.

About Roaming Outcollect Processing

You use roaming outcollect processing to track and rate activities of subscribers from other wireless networks that roam on your network. Outcollect processing allows you to rate the visiting subscribers' roaming usage using InterCarrier Tariff rates and generate TAP files consisting of the visiting subscriber's call event detail records, which you send to your roaming partners along with an invoice to bill them for their subscribers' roaming usage.

Roaming outcollect processing involves:

About Splitting Home CDRs from Visiting Subscribers' CDRs

Some CDRs that you receive from the network switches are generated by your subscribers and some by visiting subscribers. The splitting process analyzes the CDRs and splits them into separate streams so that they can be rated by the appropriate rating pipeline.

  • The rating pipeline processes the CDRs generated by your own subscribers.

  • The outcollect rating pipeline processes the CDRs generated by visiting subscribers.

About Rating Visiting Subscribers' Roaming CDRs

The outcollect rating process rates the visiting subscribers' roaming CDRs based on the InterCarrier Tariff rates agreed upon between you and your roaming partners in the respective roaming agreements. This charge, referred to as the outcollect roaming charge, is what your roaming partner owes you for their subscribers' usage of your wireless network.

If your roaming partners find errors in the TAP files, they reject the file or records and send them back to you in a RAP file for corrections.

About Handling Rejected TAP Files

TAP files are validated by roaming partner network operators to ensure the data in the files are correct. TAP files and records that are rejected are sent to a RAP file.

  • When you send TAP files with visiting subscribers' call event detail records to your roaming partner, your roaming partner generates RAP files consisting of the TAP files or call event detail records with errors and sends them back to you for corrections. RAP files received from your roaming partners are processed during outcollect processing.

  • When your roaming partner sends you TAP files with your subscribers' call event detail records, you generate RAP files consisting of the TAP files or call event detail records with errors and send them back to your roaming partner for corrections. RAP files to be sent to your roaming partners are generated during incollect processing.

RAP files are generated according to the GSM TD32 specifications and includes information such as the receiving network operator of the RAP file; an error code indicating a fatal, severe, or missing error; the rejected TAP file or call event detail records; and the RAP file sequence number.

The RAP file error code is determined as follows:

  • If there are errors in the TAP file, a fatal error RAP file is created consisting of the TAP file.

  • If the TAP file has a sequence number that is greater than the one expected, a missing error RAP file is created indicating the missing files.

  • If there are errors in the TAP records, a severe error RAP file is created consisting of only the rejected records.

For more information on TD32 specifications, see the following:

http://www.gsma.com/

About Settling Roaming Charges

Roaming partner network operators bill each other for the roaming activities of their subscribers using a process known as settlement. Two activities occur during settlement:

  • Your roaming partner network operators bill you for your subscribers' usage of their wireless network. This is referred to as incollect settlement.

  • You bill your roaming partner network operators for their subscribers' usage of your wireless network. This is referred to as outcollect settlement.

Settlement events are not rated during the settlement process; instead, the event balance impacts are loaded into the BRM database for settlement.

For each roaming partner network operator, a network operator account is created in the Pipeline Manager database and a corresponding roaming partner account is created in the BRM database. The network operator configuration in the Pipeline Manager database stores product and rate information used to rate and reprice roaming events. The roaming partner account in the BRM database stores the incollect and outcollect settlement balance impacts used to bill the accounts.

When you run billing, for each roaming partner account, BRM billing opcodes read the settlement data and generate a bill for the total incollect charge amount (what you owe) and another bill for the total outcollect charge amount (what they owe). The amount that you owe your roaming partner network operator is the difference between the two.

About Near Real-Time Roaming Data Exchange and Roaming Fraud Detection

Near Real-Time Roaming Data Exchange (NRTRDE) is the exchange of roaming usage data between roaming partners in near real time. Exchanging roaming usage data in near real time enables network operators to monitor roaming usages frequently and to detect any fraudulent behavior and take necessary actions to minimize revenue loss. For example, network operators may decide to deny or limit access to subscribers that have exceeded their daily usage threshold (fraud limit).

You can set up Pipeline Manager for generating roaming usage data for NRTRDE. Once you have set up Pipeline Manager as required, you can run roaming NRTRDE reports. See "Detecting Roaming Fraud Using NRTRDE" for more information.

PKb2Q-QPKSqE!OEBPS/rmg_edr_tapv311_mapping.htm TAP and EDR Field Mappings

11 TAP and EDR Field Mappings

This chapter describes the mapping of fields from TAP file to the EDR container that Oracle Communications Billing and Revenue Management (BRM) uses when processing TAP input files and the mapping of fields from EDR container to TAP file used for generating TAP output files.

Before reading this document, you should be familiar with the following topics in the BRM documentation:

For TAP specifications, see the following:

http://www.gsmworld.com/

TAP-to-EDR Mapping

When processing incoming TAP files, BRM copies input data from TAP fields into EDR container fields. The table below lists the TAP fields and the corresponding EDR field(s) where the data from the TAP field is stored.

Some of the fields in the TAP file can map to multiple fields in the EDR container description file. For example, both the ACTUAL_DELIVERY_TIMESTAMP and ACT_DELIVERY_UTC_TIME_OFFSET fields in the Associated Content Extension Record of the EDR container description file store the data from the Actual Delivery Timestamp field in the TAP file.

For some other TAP fields, placement of the field within the TAP file determines where to copy the field's data in the EDR container description file. For example, depending on the context within the TAP file, Location Identifier can be mapped to the LOCATION_LIST.IDENTIFIER field in either Associated Location Extension Record or Associated Content Extension Record of the EDR container description file as shown in Table 11-1.

Table 11-1 TAP-to-EDR Mapping

TAP FieldEDR FieldComments

Access Point Name NI

GPRS Destination Camel Group:

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

GPRS Destination, other cases:

  • DETAIL.ASS_GPRS_EXT.APN_ADDRESS

Access Point Name NI and Access Point Name OI are mapped to a single EDR field as concatenated and comma-separated items.

Access Point Name OI

GPRS Destination Camel Group:

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

GPRS Destination, other cases:

  • DETAIL.ASS_GPRS_EXT.APN_ADDRESS

Access Point Name NI and Access Point Name OI are mapped to a single EDR field as concatenated and comma-separated items.

Action Code

DETAIL.ASS_GSMW_EXT.SS_PACKET.ACTION_CODE

No comment.

Actual Delivery Timestamp

DETAIL.ASS_CONT_EXT.ACTUAL_DELIVERY_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_CONT_EXT.ACTUAL_DELIVERY_TIMESTAMP and the UTC offset part is mapped to DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET.

Advised Charge

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE

No comment.

Advised Charge Currency

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE_CURRENCY

No comment.

Age Of Location

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.AGE_OF_LOCATION

No comment.

Basic HSCSD Parameters

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST

This is a block.

Basic Service Used

DETAIL.ASS_GSMW_EXT.BS_PACKET

This is a block.

Bearer Service Code

DETAIL.BASIC_SERVICE

No comment.

Call Event Details Count

TRAILER.TAP_TOTAL_NUMBER_OF_RECORDS

No comment.

Call Event Start Timestamp

DETAIL.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.CHARGING_START_TIMESTAMP and the UTC offset part is mapped to DETAIL.UTC_TIME_OFFSET.

Call Reference

DETAIL.ASS_LOCN_EXT.CALL_REFERENCE

For Location Services group, Call Reference is saved in the EDR field.

Call Type Level 1

DETAIL.CONNECT_TYPE

Call Type Level 1 and Call Type Level 2 are mapped to the EDR field as concatenated comma-separated items.

Call Type Level 2

DETAIL.CONNECT_TYPE

Call Type Level 1 and Call Type Level 2 are mapped to the EDR field as concatenated comma-separated items.

Call Type Level 3

DETAIL.CONNECT_SUB_TYPE

No comment.

Called Number

DETAIL.B_NUMBER & DETAIL.INTERN_B_NUMBER_ZONE & DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

The called number is the representation of the number dialled by the subscriber.

Called Place

DETAIL.DESCRIPTION

Destination Group.

The TAP fields Called Place and Called Region are mapped to the EDR field as concatenated comma-separated items.

Called Region

DETAIL.DESCRIPTION

Destination Group.

The TAP fields Called Place and Called Region are mapped to the EDR field as concatenated comma-separated items.

CAMEL Destination Number

DETAIL.ASS_CAMEL_EXT.DEST_GSMW_NUMBER_ORIGINAL

No comment.

Camel Invocation Fee

DETAIL.ASS_CAMEL_EXT.SERVER_TYPE_OF_NUMBER

The charge for the CAMEL invocation after discounts have been deducted.

CAMEL Service Key

DETAIL.ASS_CAMEL_EXT.SERVICE_KEY

No comment.

CAMEL Service Level

DETAIL.ASS_CAMEL_EXT.SERVICE_LEVEL

No comment.

CAMEL Service Used

DETAIL.ASS_CAMEL_EXT

This is a block.

Cause For Termination

DETAIL.CALL_COMPLETION_INDICATOR

If the TAP field value is less than 10, it is prefixed with 0.

Cell Identity

GPRS Network Location:

  • DETAIL.ASS_GPRS_EXT.CELL_ID

Network Location:

  • DETAIL.ASS_GSMW_EXT.CELL_ID

Present within groups:

  • GPRS Network Location

  • Network Location

Charge

DETAIL.ASS_CBD.CP.CHARGED_AMOUNT_VALUE

No comment.

Charge Refund Indicator

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CHARGE_REFUND_INDICATOR

No comment.

Charge Type

Taxation:

  • DETAIL.ASS_CBD.TP.CHARGE_TYPE

Charge Detail:

  • DETAIL.ASS_CBD.CP.IMPACT_CATEGORY

Present within groups:

  • Taxation, when the associated Tax Rate Code references a tax applied to a specific Charge Type.

  • Charge Detail

Chargeable Units

DETAIL.ASS_CBD.CP.CHARGEABLE_QUANTITY_VALUE

No comment.

Charged Party Equipment

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT

This is a block.

Charged Party Home Identification

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST

This is a block.

Charged Party Id Type

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.TYPE

No comment.

Charged Party Identification

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST

This is a block.

Charged Party Identifier

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.IDENTIFIER

No comment.

Charged Party Information

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO

This is a block.

Charged Party Location

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST

This is a block.

Charged Party Status

DETAIL.USAGE_DIRECTION

No comment.

Charged Units

DETAIL.ASS_CBD.CP.ROUNDED_QUANTITY_VALUE

No comment.

Charging ID

DETAIL.ASS_GPRS_EXT.CHARGING_ID

No comment.

Charging Timestamp

Supplementary Service Used:

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.UTC_TIME_OFFSET

Location Service Usage

  • DETAIL.ASS_GPRS_EXT.SERVICE_USED_CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GPRS_EXT.SERVICE_USED_UTC_TIME_OFFSET

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.UTC_TIME_OFFSET

Basic Service Used:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.UTC_TIME_OFFSET

GPRS Call (Record type MSS, SCU, and VAS):

  • DETAIL.CHARGING_START_TIMESTAMP

    and

  • DETAIL.UTC_TIME_OFFSET

Present within groups:

  • Supplementary Service Used. The timestamp is mandatory and occurs within Supplementary Service Event.

  • Location Service Usage. The timestamp is only present where it is not the same as the associated LCS Request Timestamp.

  • Basic Service Used. The timestamp is only present where it is not the same as an associated Call Event Start Timestamp.

CLIR Status Indicator

Call Originator and SCU Basic Information:

  • DETAIL.ASS_ROAMING_EXT.CLIR_INDICATOR

Third Party Information:

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.CLIR_INDICATOR

Present within groups:

  • Call Originator where available.

  • SCU Basic Information where available and the Charged Party Status indicates a terminating short message.

  • Third Party Information where available.

Commission

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.COMMISSION

No comment.

Completion Timestamp

DETAIL.CHARGING_END_TIMESTAMP

No comment.

Content Charging Point

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_CHARGING_POINT

No comment.

Content Provider

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST

This is a block.

Content Provider Id Type

LCS SP Identification:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.TYPE

Content Provider:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.TYPE

Mandatory within groups:

  • LCS SP Identification

  • Content Provider

Content Provider Identifier

LCS SP Identification:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.IDENTIFIER

Content Provider:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.IDENTIFIER

Mandatory within groups:

  • LCS SP Identification

  • Content Provider

Content Provider Name

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_NAME

No comment.

Content Service Used

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST

This is a block.

Content Transaction Code

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_CODE

No comment.

Content Transaction Type

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_TYPE

No comment.

CSE Information

DETAIL.ASS_CAMEL_EXT.CSE_INFORMATION

No comment.

Customer Id Type

Tracking Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.TYPE

Tracked Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.TYPE

Mandatory within groups:

  • Tracking Customer Identification

  • Tracked Customer Identification

Customer Identifier

Tracking Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.IDENTIFIER

Tracked Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.IDENTIFIER

Mandatory within groups:

  • Tracking Customer Identification

  • Tracked Customer Identification

Data Volume Incoming

GPRS Service Used:

  • DETAIL.VOLUME_RECEIVED

Content Service Used:

  • DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_INCOMING

Present within groups:

  • GPRS Service Used. Mandatory.

  • Content Service Used when available.

Data Volume Outgoing

GPRS Service Used:

  • DETAIL.VOLUME_SENT

Content Service Used:

  • DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_OUTGOING

Present within groups:

  • GPRS Service Used. Mandatory.

  • Content Service Used when available.

Default Call Handling Indicator

DETAIL.ASS_CAMEL_EXT.DEFAULT_CALL_HANDLING_INDICATOR

No comment.

Deposit Timestamp

DETAIL.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.CHARGING_START_TIMESTAMP and the UTC offset part is mapped to DETAIL.UTC_TIME_OFFSET.

Destination Network

DETAIL.DESTINATION_NETWORK

No comment.

Dialled Digits

  • DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

  • DETAIL.C_NUMBER

No comment.

Discountable Amount

DETAIL.ASS_ROAMING_EXT.DISCOUNTABLE_AMOUNT

The actual part of the Charge/Tax/CAMEL Invocation Fee to which the Discount Value and Discount Rate (Code) relate.

Discount Code

DETAIL.ASS_CBD.CP.GRANTED_DISCOUNT_AMOUNT_VALUE

No comment.

Discount Value

DETAIL.ASS_CBD.CP.GRANTED_DISCOUNT_AMOUNT_VALUE

No comment.

Distance Charge Band Code

DETAIL.ZONE_DESCRIPTION

No comment.

Earliest Call Timestamp

TRAILER.FIRST_START_TIMESTAMP

and

TRAILER.FIRST_CHARGING_UTC_TIME_OFFSET

The timestamp part of this item is mapped to TRAILER.FIRST_START_TIMESTAMP and the UTC offset part is mapped to TRAILER.FIRST_CHARGING_UTC_TIME_OFFSET.

Equipment Id

Charged Party Equipment:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.IDENTIFIER

Tracking Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_

  • INFO.EQUIPMENT.IDENTIFIER

Tracked Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.IDENTIFIER

Mandatory within groups:

  • Charged Party Equipment

  • Tracking Customer Equipment

  • Tracked Customer Equipment

Equipment Id Type

Charged Party Equipment:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.TYPE

Tracking Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.TYPE

Tracked Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.TYPE

Mandatory within groups:

  • Charged Party Equipment

  • Tracking Customer Equipment

  • Tracked Customer Equipment

ESN

DETAIL.ASS_GSMW_EXT.DEVICE_NUMBER

No comment.

Exchange Rate Code

DETAIL.ASS_CBD.CP.EXCHANGE_RATE

No comment.

File Available Timestamp

HEADER.TRANSMISSION_DATE

No comment.

File Creation Timestamp

HEADER.CREATION_TIMESTAMP

and

HEADER.UTC_TIME_OFFSET

The timestamp part of this item is mapped to HEADER.CREATION_TIMESTAMP and the UTC offset part is mapped to HEADER.UTC_TIME_OFFSET.

File Sequence Number

HEADER.SEQUENCE_NUMBER

HEADER.ORIGIN_SEQUENCE_NUMBER

No comment.

File Type Indicator

HEADER.DATA_TYPE_INDICATOR

No comment.

Fixed Network User Rate

DETAIL.ASS_GSMW_EXT.BS_PACKET.FNUR

No comment.

Fnur

DETAIL.ASS_GSMW_EXT.BS_PACKET.FNUR

No comment.

Geographical Location

DETAIL.GEOGRAPHICAL_LOCATION

The EDR field contains comma-separated tag-value pairs that indicate the geographical location of the serving network, serving BID, serving location description, longitude, and latitude.

The tag values of the corresponding fields are as follows:

  • ServingNetwork: 1

  • ServingBID: 2

  • ServingLocationDescription: 3

  • Longitude: 4

  • Latitude: 5

Example 1: If the TAP field values are as follows:

  • ServingNetwork: AIRTEL

  • ServingBID: AIRBID

  • ServingLocationDescription: Bangalore

  • Longitude: 111

  • Latitude: 103

The value of DETAIL.GEOGRAPHICAL_LOCATION would be 1,AIRTEL, 2,AIRBID, 3,Bangalore, 4,111,5,103.

Example 2: If the TAP field values are as follows:

  • ServingNetwork: AIRTEL

  • ServingBID: AIRBID

  • Latitude: 103

The value of DETAIL.GEOGRAPHICAL_LOCATION would be 1,AIRTEL, 2,AIRBID, 5,103.

Guaranteed Bit Rate

DETAIL.ASS_ROAMING_EXT.GUARANTEED_BIT_RATE

Describes the bitrate the UMTS bearer service must guarantee to the user or application for circuit switched UMTS.

GPRS Destination

GPRS Basic Call Information:

  • DETAIL.ASS_GPRS_EXT.APN_ADDRESS

CAMEL Service Used:

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

Present within groups:

  • GPRS Basic Call Information. Mandatory.

  • CAMEL Service Used where GPRS Destination has been modified by the CAMEL server.

Home Bid

DETAIL.ASS_ROAMING_EXT.HOME_BID

The Home BID (Billing Identifier) is a code identifying the home market area of the Chargeable Subscriber.

Home Id Type

Charged Party Home Identification:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.TYPE

Tracking Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.TYPE

Tracked Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.TYPE

Mandatory within groups:

  • Charged Party Home Identification

  • Tracking Customer Home Id

  • Tracked Customer Home Id

Home Identifier

Charged Party Home Identification:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.IDENTIFIER

Tracked Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Tracking Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Mandatory within groups:

  • Charged Party Home Identification

  • Tracking Customer Home Id

  • Tracked Customer Home Id

Home Location Description

DETAIL.ASS_ROAMING_EXT.HOMELOCATION_DESCRIPTION

A text description giving the home market area of the Chargeable Subscriber.

Horizontal Accuracy Delivered

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_DELIVERED

No comment.

Horizontal Accuracy Requested

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_REQUESTED

No comment.

HSCSD Indicator

DETAIL.ASS_ROAMING_EXT.HSCSD_INDICATOR

This indicator, set by the VPMN and passed to the Recipient, indicates that HSCSD has been used.

IMEI

  • DETAIL.ASS_GSMW_EXT.DEVICE_NUMBER

GPRS:

  • DETAIL.ASS_GPRS_EXT.DEVICE_NUMBER

Present within the group:

  • Equipment Identifier where available. Is not present when the terminal equipment is not involved in the call.

IMSI

  • DETAIL.ASS_GSMW_EXT.PORT_NUMBER

GPRS:

  • DETAIL.ASS_GPRS_EXT.PORT_NUMBER

Present within groups:

  • Chargeable Subscriber when MIN is not present. Mandatory.

  • GSM Chargeable Subscriber when available.

  • Must be present for WLAN usage when IMSI is used for identifying the chargeable user.

Initiating Party

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.INITIATING_PARTY

No comment.

Internet Service Provider

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST

This is a block.

ISP Id Type

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.TYPE

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.TYPE

No comment.

ISP Identifier

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.IDENTIFIER

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.IDENTIFIER

No comment.

Latest Call Timestamp

TRAILER.LAST_START_TIMESTAMP

and

TRAILER.LAST_CHARGING_UTC_TIME_OFFSET

The timestamp part of this item is mapped to TRAILER.LAST_START_TIMESTAMP and the UTC offset part is mapped to TRAILER.LAST_CHARGING_UTC_TIME_OFFSET.

LCS Request Timestamp

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQUEST_TIMESTAMP

and

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQ_UTC_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQUEST_TIMESTAMP and the UTC offset part is mapped to DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQ_UTC_OFFSET.

LCS SP Identification

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST

This is a block.

LCS SP Information

DETAIL.ASS_LOCN_EXT.LCSSP_INFO

This is a block.

LCS Transaction Status

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_TRANS_STATUS

No comment.

Local Currency

DETAIL.WHOLESALE_CHARGED_AMOUNT_CURRENCY

No comment.

Location Area Code

GPRS Network Location:

  • DETAIL.ASS_GPRS_EXT.LOCATION_AREA_INDICATOR

Network Location:

  • DETAIL.ASS_GSMW_EXT.LOCATION_AREA_INDICATOR

Mandatory within groups:

  • GPRS Network Location

  • Network Location

except where not supported by the network or the call does not terminate at the equipment.

Location Id Type

Charged Party Location:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.TYPE

Tracked Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.TYPE

Tracking Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.TYPE

Mandatory within groups:

  • Charged Party Location

  • Tracked Customer Location

  • Tracking Customer Location

Location Identifier

Charged Party Location:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.IDENTIFIER

Tracked Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.IDENTIFIER

Tracking Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.IDENTIFIER

Mandatory within groups:

  • Charged Party Location

  • Tracked Customer Location

  • Tracking Customer Location

Location Service Usage

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE

This is a block.

Maximum Bit Rate

DETAIL.ASS_ROAMING_EXT.MAXIMUM_BIT_RATE

The maximum bit rate available for circuit switched UMTS.

Mdn

DETAIL.ASS_ROAMING_EXT.MOBILE_DIR_NUMBER

Mobile Directory Number.

Message Description Code


Message Description Code is not mapped to any EDR field. The DETAIL.DESCRIPTION field in the SCU Charge Type group contains description text with Message Description Code.

Message Status

DETAIL.CALL_COMPLETION_INDICATOR

If the TAP field value is less than 10, it is prefixed with 0.

Message Type

DETAIL.QOS_USED

No comment.

Min

DETAIL.ASS_ROAMING_EXT.MOBILE_ID_NUMBER

Mobile Identification Number is an item which uniquely identifies the subscriber who has used the network.

Modification Timestamp

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MODIFICATION_TIMESTAMP

and

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MODIFICATION_TIMESTAMP and the UTC offset part is mapped to DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.UTC_TIME_OFFSET.

MSISDN

The TAP field is mapped to the following fields:

  • DETAIL.A_NUMBER

  • DETAIL.INTERN_A_NUMBER_ZONE

  • DETAIL.ASS_GSMW_EXT.A_NUMBER_USER

GPRS:

  • DETAIL.ASS_GPRS_EXT.A_NUMBER_USER

SCU:

  • DETAIL.ASS_GSMW_EXT.A_NUMBER_USER

  • DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

MTC:

  • DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

The EDR field is always prefixed with International Access Code.

Present within groups:

  • Chargeable Subscriber or GPRS Chargeable Subscriber when IMSI is present. Should be associated with IMSI.

  • GSM Chargeable Subscriber when available.

  • Present when expected in accordance with roaming agreement.

  • Present for WLAN network usage where the full IMSI or Network Access Identifier are not available.

Network Access Identifier

DETAIL.ASS_ROAMING_EXT.NETWORKACCESS_IDENTIFIER

The Network Access Identifier (NAI) is a username identifying a unique customer when generating WLAN CDRs.

Network Id Type

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.TYPE

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.NETWORK_LIST.TYPE

No comment.

Network Identifier

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.IDENTIFIER

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.NETWORK_LIST.IDENTIFIER

No comment.

Network Init. PDP Context

DETAIL.ASS_GPRS_EXT.NETWORK_INITIATED_PDP

No comment.

Object Type

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.OBJECT_TYPE

No comment.

Operator Spec Information

DETAIL.OPERATOR_SPECIFIC_INFO [if Record type is record_GPRS]

HEADER.OPERATOR_SPECIFIC_INFO [record_Header]

TRAILER.OPERATOR_SPECIFIC_INFO [record_Trailer]

This is an optional repeating field which contains operator specific information.

Order Placed Timestamp

DETAIL.ASS_CONT_EXT.ORDER_PLACED_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_CONT_EXT.ORDER_PLACED_TIMESTAMP and the UTC offset part is mapped to DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET.

Originating Network

DETAIL.SOURCE_NETWORK

No comment.

Paid Indicator

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAID_INDICATOR

A flag which shows that the Charged Party has paid for the service.

Partial Type Indicator

DETAIL.LONG_DURATION_INDICATOR

No comment.

Payment Method

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAYMENT_METHOD

No comment.

PDP Address

DETAIL.ASS_GPRS_EXT.PDP_ADDRESS

No comment.

PDP Context Start Timestamp

DETAIL.ASS_GPRS_EXT.PDP_CONTEXT_START_TIMESTAMP

and

DETAIL.ASS_GPRS_EXT.PDP_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_GPRS_EXT.PDP_CONTEXT_START_TIMESTAMP and the UTC offset part is mapped to DETAIL.ASS_GPRS_EXT.PDP_UTC_TIME_OFFSET.

Positioning Method

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.POSITIONING_METHOD

No comment.

Priority Code

DETAIL.QOS_REQUESTED

No comment.

RAP File Sequence Number

Call Event Details:

  • DETAIL.RAP_FILE_SEQ_NO

Batch Control Information and Notification:

  • HEADER.RAP_FILE_SEQ_NO

Must be present within groups:

  • Notification

  • Batch Control Information

Recipient

HEADER.RECIPIENT

No comment.

Recording Entity Code

Service Center Usage:

  • DETAIL.ASS_GSMW_EXT.ORIGINATING_SWITCH_IDENTIFICATION

Location Service:

  • DETAIL.ASS_LOCN_EXT.REC_ENTITY_CODE

Mandatory within groups:

  • Recording Entity Information

  • Location Service

  • Network Location

  • Service Center Usage where it must be of type 'Service Center'

In the case of GPRS network usage, two or more occurrences must be present within GPRS Network Location. One occurrence must be of type 'GGSN' (see Recording Entity Type) and all other occurrences must be of type 'SGSN'.

In the case of WLAN network usage, one occurrence must be present identifying the WLAN billing information recording entity.

Network Location:

Recording Entity Code is used to get corresponding Recording Entity ID. Recording Entity Code is not stored in any EDR field.

Rec Entity Code Information:

Recording Entity Code is used to get corresponding Recording Entity ID. Recording Entity Code is not stored in any EDR field.

Release Version Number

HEADER.RELEASE_VERSION

No comment.

Requested Delivery Timestamp

DETAIL.ASS_CONT_EXT.REQUESTED_DELIVERY_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.REQ_DELIVERY_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_CONT_EXT.REQUESTED_DELIVERY_TIMESTAMP, and the UTC offset part is mapped to DETAIL.ASS_CONT_EXT.REQ_DELIVERY_UTC_TIME_OFFSET.

Response Time

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME

No comment.

Response Time Category

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME_CATEGORY

No comment.

Sender

HEADER.SENDER

No comment.

Serving Bid

DETAIL.GEOGRAPHICAL_LOCATION

The Serving BID (Billing Identifier) is a code associated with a geographical area.

Serving Location Description

DETAIL.GEOGRAPHICAL_LOCATION

A text description giving the geographical location of the terminal equipment.

Serving Network

Serving Network:

  • DETAIL.ASS_GSMW_EXT.SERVING_NETWORK

Geographical Location:

  • DETAIL.GEOGRAPHICAL_LOCATION

Serving Network is stored in DETAIL.GEOGRAPHICAL_LOCATION along with other concatenated comma-separated tag-value pairs from Geographical Location.

Serving Parties Information

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO

This is a block.

SIM Toolkit Indicator

DETAIL.DISCOUNT_KEY

No comment.

SMS Destination Number

DETAIL.ASS_ROAMING_EXT.SMS_DESTINATION_NUMBER

The SMS Destination Number item contains the actual destination (intended recipient) of the SMS text message.

SMS Originator

DETAIL.ASS_ROAMING_EXT.SMS_ORIGINATOR

The SMS Originator holds the identification of the actual sender of the SMS

Specification Version Number

HEADER.SPECIFICATION_VERSION_NUMBER

No comment.

Supplementary Service Code

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_EVENT

No comment.

Supplementary Service Parameters

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_PARAMETERS

No comment.

Supplementary Service Used

DETAIL.ASS_GSMW_EXT.SS_PACKET

This is a block.

TAP Decimal Places

HEADER.TAP_DECIMAL_PLACES

No comment.

Tax Information

DETAIL.ASS_CBD.TP

This is a block.

Tax Rate Code

DETAIL.ASS_CBD.TP.TAX_CODE

Mandatory within groups:

  • Taxation

  • Tax Information

Tax Value

  • DETAIL.WHOLESALE_CHARGED_TAX_VALUE

  • DETAIL.ASS_CBD.TP.TAX_VALUE

No comment.

Taxable Amount

DETAIL.ASS_CBD.TP.TAXABLE_AMOUNT

No comment.

TeleService Code

  • DETAIL.BASIC_SERVICE

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.BASIC_SERVICE

The EDR fields are prefixed with 0.

Third Party Number

  • DETAIL.C_NUMBER

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.THIRD_PARTY_NUMBER

Present within the Third Party Information group where available.

Total Advised Charge

TRAILER.ASS_ROAMING_EXT.TOTAL_ADVISEDCHARGE

The sum of all the advised charges associated with the corresponding currency excluding those representing a refund.

Total Advised Charge Refund

TRAILER.ASS_ROAMING_EXT.TOTAL_ADVISEDCHARGE_REFUND

The sum of all the advised charges associated with the corresponding currency representing a refund.

Total Commission

TRAILER.ASS_ROAMING_EXT.TOTAL_COMMISSION

The sum of all the commissions associated with the corresponding currency excluding those representing a refund.

Total Commission Refund

TRAILER.ASS_ROAMING_EXT.TOTAL_COMMISSION_REFUND

The sum of all the commissions associated with the corresponding currency representing a refund.

Total Discount Refund

TRAILER.ASS_ROAMING_EXT.TOTAL_DISCOUNT_REFUND

The sum of the Discount Values plus each application of a Fixed Discount Value contained in the batch representing a refund.

Total Tax Refund

TRAILER.ASS_ROAMING_EXT.TOTAL_TAX_REFUND

The sum of the Tax Values contained in the batch representing a refund.

Total Transaction Duration

Total Transaction Duration:

  • DETAIL.ASS_CONT_EXT.TOTAL_TRANSACTION_DURATION

Total Call Event Duration:

  • DETAIL.TOTAL_CALL_EVENT_DURATION

No comment.

Total Call Event Duration

Total Call Event Duration:

  • DETAIL.TOTAL_CALL_EVENT_DURATION

Total Transaction Duration:

  • DETAIL.ASS_CONT_EXT.TOTAL_TRANSACTION_DURATION

No comment.

Total Charge

TRAILER.TOTAL_CHARGE_VALUE_LIST

This is a block.

Total Charge Refund

TRAILER.TOTAL_CHARGE_VALUE_LIST.TOTAL_CHARGE_REFUND

No comment.

Total Data Volume

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TOTAL_DATA_VOLUME

No comment.

Total Discount Value

TRAILER.TAP_TOTAL_DISCOUNT_VALUE

No comment.

Total Tax Value

TRAILER.TAP_TOTAL_TAX_VALUE

No comment.

Tracked Customer Equipment

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT

This is a block.

Tracked Customer Home Id

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST

This is a block.

Tracked Customer Identification

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST

This is a block.

Tracked Customer Information

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO

This is a block.

Tracked Customer Location

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST

This is a block.

Tracking Customer Equipment

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT

This is a block.

Tracking Customer Home Id

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST

This is a block.

Tracking Customer Identification

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST

This is a block.

Tracking Customer Information

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO

This is a block.

Tracking Customer Location

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST

This is a block.

Tracking Frequency

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.REQ_TRACKING_FREQUENCY

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_FREQUENCY

No comment.

Tracking Period

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.TRACKING_PERIOD

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_PERIOD

No comment.

Transaction Authorization Code

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_AUTH_CODE

No comment.

Transaction Description Suppression

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DESCRIPTION_SUPP

No comment.

Transaction Detail Description

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DETAIL_DESCRIPTION

No comment.

Transaction Identifier

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_IDENTIFIER

No comment.

Transaction Short Description

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_SHORT_DESCRIPTION

No comment.

Transaction Status

DETAIL.ASS_CONT_EXT.TRANSACTION_STATUS

No comment.

Transfer Cut Off Timestamp

HEADER.TRANSFER_CUTOFF_TIMESTAMP

No comment.

Transparency Indicator

DETAIL.ASS_GSMW_EXT.BS_PACKET.TRANSPARENCY_INDICATOR

No comment.

User Protocol Indicator

DETAIL.ASS_GSMW_EXT.BS_PACKET.USER_PROTOCOL_INDICATOR

No comment.

UTC Time Offset

File Creation Timestamp:

  • HEADER.UTC_TIME_OFFSET

Earliest Call Timestamp:

  • TRAILER.FIRST_CHARGING_UTC_TIME_OFFSET

Latest Call Timestamp

  • TRAILER.LAST_CHARGING_UTC_TIME_OFFSET

Mandatory within items:

  • File Creation Timestamp

  • Earliest Call Timestamp

  • Latest Call Timestamp

Mandatory within UTC Time Offset Information.

UTC Time Offset Code

Actual Delivery Timestamp:

  • DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET

Order Placed Timestamp:

  • DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET

Requested Delivery Time Stamp:

  • DETAIL.ASS_CONT_EXT.REQ_DELIVERY_UTC_TIME_OFFSET

LCS Request Timestamp:

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQ_UTC_OFFSET

Mandatory within UTC Time Offset Information.

Mandatory within items:

  • Call Event Start Timestamp

  • Charging Timestamp

  • Charge Detail Timestamp

  • Deposit Timestamp

  • Completion Timestamp

  • Order Placed Timestamp

  • Requested Delivery Timestamp

  • Actual Delivery Timestamp

  • LCS Request Timestamp

  • PDP Context Start Timestamp

In Date Time group, UTC Time Offset Code is only used to get corresponding UTC Time Offset, but is not mapped to any EDR field.

Vertical Accuracy Delivered

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_DELIVERED

No comment.

Vertical Accuracy Requested

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_REQUESTED

No comment.


EDR-to-TAP Mapping

When generating output TAP files, BRM maps EDR container fields to the fields in TAP output files. Table 11-2 lists the EDR and TAP field mappings that BRM uses when producing the output files.


Note:

Some of the fields in the EDR container file, such as DETAIL.UTC_TIME_OFFSET, can provide data to different fields in the output TAP file.

Table 11-2 EDR-to-TAP Mapping

<Ntd align="left" headers="r181c1-t4 r1c3-t4" rowspan="1" colspan="1">

No comment.

EDR FieldTAP FieldComments

DETAIL.A_NUMBER

MSISDN

No comment.

DETAIL.ASS_CAMEL_EXT

CAMEL Service Used

This is a block.

DETAIL.ASS_CAMEL_EXT.CSE_INFORMATION

CSE Information

No comment.

DETAIL.ASS_CAMEL_EXT.DEFAULT_CALL_HANDLING_INDICATOR

Default Call Handling Indicator

No comment.

DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

GPRS Destination

The EDR field contains concatenated and comma-separated values of Access Point Name NI and Access Point Name OI.

DETAIL.ASS_CAMEL_EXT.DEST_GSMW_NUMBER

Camel Destination Number

International Access Code prefixes the EDR field.

DETAIL.ASS_CAMEL_EXT.RECORD_NUMBER

TaxInformationList

No comment.

DETAIL.ASS_CAMEL_EXT.SERVER_TYPE_OF_NUMBER

CamelInvocationFee

No comment.

DETAIL.ASS_CAMEL_EXT.SERVICE_KEY

CAMEL Service Key

No comment.

DETAIL.ASS_CAMEL_EXT.SERVICE_LEVEL

CAMEL Service Level

No comment.

DETAIL.ASS_CBD.CP.CHARGEABLE_QUANTITY_VALUE

Chargeable Units

No comment.

DETAIL.ASS_CBD.CP.CHARGED_AMOUNT_VALUE

Charge

No comment.

DETAIL.ASS_CBD.CP.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

Charging Timestamp

No comment.

DETAIL.ASS_CBD.CP.EXCHANGE_RATE

Exchange Rate Code

No comment.

DETAIL.ASS_CBD.CP.GRANTED_DISCOUNT_AMOUNT_VALUE

  • Discount Value

  • Discount Code

No comment.

DETAIL.ASS_CBD.CP.IMPACT_

CATEGORY

Charge Type

No comment.

DETAIL.ASS_CBD.CP.PRODUCTCODE_USED

VAS:

  • VasShortDesc for the corresponding VAS Code

Camel:

  • Hard coded to CAMEL

In Charge Detail Group, values that are mapped to the EDR field depend on the service type: VAS or Camel.

DETAIL.ASS_CBD.CP.ROUNDED_QUANTITY_VALUE

Charged Units

No comment.

DETAIL.ASS_CBD.TP

Tax Information

This is a block.

DETAIL.ASS_CBD.TP.TAX_VALUE

Tax Value

No comment.

DETAIL.ASS_CBD.TP.TAXABLE_AMOUNT

Taxable Amount

No comment.

DETAIL.ASS_CONT_EXT.ACTUAL_DELIVERY_TIMESTAMP

Actual Delivery Timestamp

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO

Charged Party Information

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT

Charged Party Equipment

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.IDENTIFIER

Charged Party Equipment:

  • Equipment Id

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.TYPE

Charged Party Equipment:

  • Equipment Id Type

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST

Charged Party Home Identification

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.IDENTIFIER

Charged Party Home Identification:

  • Home Identifier

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.TYPE

Charged Party Home Identification:

  • Home Id Type

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST

Charged Party Identification

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.IDENTIFIER

Charged Party Identifier

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.TYPE

Charged Party Id Type

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST

Charged Party Location

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.IDENTIFIER

Charged Party Location:

  • Location Identifier

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.TYPE

Charged Party Location:

  • Location Id Type

No comment.

DETAIL.ASS_CONT_EXT.ORDER_PLACED_TIMESTAMP

Order Placed Timestamp

No comment.

DETAIL.ASS_CONT_EXT.RECORD_NUMBER

Keeps the number of records of contentTransaction.

No comment.

DETAIL.ASS_CONT_EXT.REQUESTED_DELIVERY_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

Requested Delivery Timestamp

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST

Content Service Used

This is a block.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE

Advised Charge

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE_CURRENCY

Advised Charge Currency

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CHARGE_REFUND_INDICATOR

Charge Refund Indicator

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.COMMISSION

Commission

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_CHARGING_POINT

Content Charging Point

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_CODE

Content Transaction Code

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_TYPE

Content Transaction Type

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_INCOMING

Data Volume Incoming

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_OUTGOING

Data Volume Outgoing

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.OBJECT_TYPE

Object Type

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAID_INDICATOR

Paid Indicator

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAYMENT_METHOD

Payment Method

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TOTAL_DATA_VOLUME

Total Data Volume

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_AUTH_CODE

Transaction Authorization Code

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DESCRIPTION_SUPP

Transaction Description Suppression

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DETAIL_DESCRIPTION

Transaction Detail Description

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_IDENTIFIER

Transaction Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_SHORT_DESCRIPTION

Transaction Short Description

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO

Serving Parties Information

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST

Internet Service Provider

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.IDENTIFIER

ISP Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.TYPE

ISP Id Type

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST

Network

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.IDENTIFIER

Serving Parties Info Block:

  • Network Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.TYPE

Serving Parties Info Block:

  • Network Id Type

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST

Content Provider

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.IDENTIFIER

Content Provider Block:

  • Content Provider Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.TYPE

Content Provider Block:

  • Content Provider Id Type

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_NAME

Content Provider Name

No comment.

DETAIL.ASS_CONT_EXT.TOTAL_TRANSACTION_DURATION

Total Transaction Duration

No comment.

DETAIL.ASS_CONT_EXT.TRANSACTION_STATUS

Transaction Status

No comment.

DETAIL.ASS_GPRS_EXT.APN_ADDRESS

GPRS Destination Group:

  • Access Point Name NI, if Camel option is not set.

  • Access Point Name OI, if Camel option is not set.

The EDR field contains concatenated and comma-separated values of Access Point Name NI and Access Point Name OI.

DETAIL.ASS_GPRS_EXT.CELL_ID

Cell Identity

No comment.

DETAIL.ASS_GPRS_EXT.CHARGING_ID

Charging ID

No comment.

DETAIL.ASS_GPRS_EXT.GGSN_ADDRESS

Recording Entity ID

Rec Entity Code Element Group.

Recording Entity Code is used to get corresponding Recording Entity ID. The obtained Recording Entity ID is stored in the EDR field.

DETAIL.ASS_GPRS_EXT.LOCATION_AREA_INDICATOR

Location Area Code

No comment.

DETAIL.ASS_GPRS_EXT.NETWORK_INITIATED_PDP

Network Init. PDP Context

No comment.

DETAIL.ASS_GPRS_EXT.PDP_ADDRESS

PDP Address

No comment.

DETAIL.ASS_GPRS_EXT.PDP_CONTEXT_START_TIMESTAMP

and

DETAIL.ASS_GPRS_EXT.PDP_UTC_TIME_OFFSET

PDP Context Start Timestamp

No comment.

DETAIL.ASS_GPRS_EXT.PORT_NUMBER

IMSI

No comment.

DETAIL.ASS_GPRS_EXT.SGSN_INFO_LIST.SGSN_ADDRESS and

DETAIL.ASS_GPRS_EXT.WLAN_ADDRESS

Recording Entity ID

Rec Entity Code Element.

The Recording Entity code is used to get corresponding Recording Entity ID. The Recording Entity ID is stored in the EDR field.

DETAIL.ASS_GSMW_EXT.BS_PACKET

  • Basic Service

  • Basic Service Used

This is a block.

DETAIL.ASS_GSMW_EXT.BS_PACKET.CHARGING_START_TIMESTAMP

and

DETAIL.ASS_GSMW_EXT.BS_PACKET.UTC_TIME_OFFSET

Charging Timestamp

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.FNUR

Fixed Network User Rate

No comment.

DETAIL.ASS_GSMW_EXT.BS_

PACKET.TRANSPARENCY_INDICATOR

Transparency Indicator

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.USER_PROTOCOL_INDICATOR

User Protocol Indicator

No comment.

DETAIL.ASS_GSMW_EXT.CELL_ID

Cell Identity

No comment.

DETAIL.ASS_GSMW_EXT.DEVICE_NUMBER

IMEI or ESN

No comment.

DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

  • Dialled Digits

  • MSISDN in MTC and SCU groups

No comment.

DETAIL.ASS_GSMW_EXT.LOCATION_AREA_INDICATOR

Location Area Code

No comment.

DETAIL.ASS_GSMW_EXT.ORIGINATING_SWITCH_IDENTIFICATION

  • Location Information

  • Recording Entity ID

No comment.

DETAIL.ASS_GSMW_EXT.PORT_NUMBER

IMSI

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET

Supplementary Service Used

This is a block.

DETAIL.ASS_GSMW_EXT.SS_PACKET.ACTION_CODE

Supplementary Service Action Code

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.CLIR_INDICATOR

CLIR Status Indicator

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_EVENT

Supplementary Service Code

No comment.

DETAIL.ASS_LOCN_EXT.CALL_REFERENCE

Call Reference

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO

LCS SP Information

This is a block.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST

LCS SP Identification

This is a block.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.IDENTIFIER

LCS SP Identification:

  • Content Provider Identifier

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.TYPE

LCS SP Identification:

  • Content Provider Id Type

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST

Internet Service Provider

This is a block.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.IDENTIFIER

LCS SP Information:

  • ISP Identifier

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.TYPE

LCS SP Information:

  • ISP Id Type

No comment.

DETAIL.ASS_LOCN_EXT.REC_ENTITY_CODE

Location Service:

  • Recording Entity Code

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE

Location Service Usage

This is a block.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.AGE_OF_LOCATION

Age Of Location

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_FREQUENCY

Tracking Frequency

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_PERIOD

Tracking Period

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_DELIVERED

Horizontal Accuracy Delivered

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_REQUESTED

Horizontal Accuracy Requested

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQUEST_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

LCS Request Timestamp

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_TRANS_STATUS

LCS Transaction Status

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.POSITIONING_METHOD

Positioning Method

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.REQ_TRACKING_FREQUENCY

Tracking Frequency

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME

Response Time

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME_CATEGORY

Response Time Category

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.TRACKING_PERIOD

Tracking Period

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_DELIVERED

Vertical Accuracy Delivered

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_REQUESTED

Vertical Accuracy Requested

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO

Tracked Customer Information

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT

Tracked Customer Equipment

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.IDENTIFIER

Tracked Customer Equipment:

  • Equipment Id

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.TYPE

Tracked Customer Equipment:

  • Equipment Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST

Tracked Customer Home Id

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Tracked Customer Home Id:

  • Home Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.TYPE

Tracked Customer Home Id:

  • Home Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST

Tracked Customer Identification

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.IDENTIFIER

Tracked Customer Identification:

  • Customer Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.TYPE

Tracked Customer Identification:

  • Customer Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST

Tracked Customer Location

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.IDENTIFIER

Tracked Customer Location:

  • Location Identifier


DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.TYPE

Tracked Customer Location:

  • Location Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO

Tracking Customer Information

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT

Tracking Customer Equipment

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.IDENTIFIER

Tracking Customer Equipment:

  • Equipment Id

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.TYPE

Tracking Customer Equipment:

  • Equipment Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST

Tracking Customer Home Id

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Tracking Customer Home Id:

  • Home Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.TYPE

Tracking Customer Home Id:

  • Home Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST

Tracking Customer Identification

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.IDENTIFIER

Tracking Customer Identification:

  • Customer Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.TYPE

Tracking Customer Identification:

  • Customer Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST

Tracking Customer Location

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.IDENTIFIER

Tracking Customer Location:

  • Location Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.TYPE

Tracking Customer Location:

  • Location Id Type

No comment.

DETAIL.ASS_ROAMING_EXT.CLIR_INDICATOR

CLIR Indicator

No comment.

DETAIL.ASS_ROAMING_EXT.GUARANTEED_BIT_RATE

GuaranteedBitRate

No comment.

DETAIL.ASS_ROAMING_EXT.HSCSD_INDICATOR

HSCSDIndicator

No comment.

DETAIL.ASS_ROAMING_EXT.MAXIMUM_BIT_RATE

MaximumBitRate

No comment.

DETAIL.ASS_ROAMING_EXT.MOBILE_DIR_NUMBER

Mdn

No comment.

DETAIL.ASS_ROAMING_EXT.MOBILE_ID_NUMBER

Min

No comment.

DETAIL.ASS_ROAMING_EXT.NETWORKACCESS_IDENTIFIER

NetworkAccessIdentifier

No comment.

DETAIL.ASS_ROAMING_EXT.RAP_FILE_SEQ_NO

FileSequenceNumber

No comment.

DETAIL.ASS_ROAMING_EXT.SMS_DESTINATION_NUMBER

SMSDestinationNumber

No comment.

DETAIL.ASS_ROAMING_EXT.SMS_ORIGINATOR

SMSOriginator

No comment.

DETAIL.ASS_ROAMING_EXT.HOME_BID

HomeBid

No comment.

DETAIL.ASS_ROAMING_EXT.HOMELOCATION_DESCRIPTION

HomeLocationDescription

No comment.

DETAIL.ASS_ROAMING_EXT.ISM_SIGNALLING_CONTEXT

IMSSignallingContext

No comment.

DETAIL.B_NUMBER

  • Called Number

  • Calling Number

  • Non Charged Number

International Access Code prefixes the EDR field.

DETAIL.BASIC_SERVICE

  • TeleService Code

  • Bearer Service Code

No comment.

DETAIL.C_NUMBER

  • Third Party Number

  • Dialled Digits

No comment.

DETAIL.CALL_COMPLETION_INDICATOR

  • Cause For Termination

  • Message Status

The EDR field is mapped to different TAP fields:

  • Service Center Usage Group. The EDR field is mapped to Message Status. If the value is less than 10, it is prefixed with 0.

  • GPRS/Mobile Originated/ Mobile Terminated Group. The EDR field is mapped to Cause for Termination. If the value is less than 10, it is prefixed with 0.

DETAIL.CHARGING_END_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

  • Completion Timestamp

  • Call Event Start Time Stamp

  • Charging Time Stamp (MSS, SCU, and VAS)

When the EDR is mapped to Completion Timestamp, the DETAIL.UTC_TIME_OFFSET part is not stored.

DETAIL.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

  • Deposit Timestamp

  • Charging Timestamp

  • Call Event Start Timestamp

No comment.

DETAIL.CONNECT_SUB_TYPE

Call Type Level 3

No comment.

DETAIL.CONNECT_TYPE

  • Call Type Level 1

  • Call Type Level 2

Contents of the EDR field are mapped as concatenated items to Call Type Level 1 and Call Type Level 2.

DETAIL.DESCRIPTION

  • Called Place

  • Called Region

  • Message Description Code

Destination:

  • Contents of the EDR field are mapped as concatenated comma-separated values into Called Place and Called Region.

SCU Charge Type:

  • The EDR field mapped to Message Description corresponds to the Message Description Code present in SCU Charge Type.

DETAIL.DESTINATION_NETWORK

Destination Network

No comment.

DETAIL.DISCOUNT_KEY

SIM Toolkit Indicator

No comment.

DETAIL.DURATION

Total Call Event Duration

No comment.

DETAIL.GEOGRAPHICAL_LOCATION

Geographical Location

Contents of the EDR field are mapped as comma-separated tag-value pairs.

The tag values of the corresponding fields are as follows:

  • ServingNetwork: 1

  • ServingBID: 2

  • ServingLocationDescription: 3

  • Longitude: 4

  • Latitude: 5

DETAIL.LONG_DURATION_INDICATOR

Partial Type Indicator

No comment.

DETAIL.OPERATOR_SPECIFIC_INFO

Operator Specific Information

No comment.

DETAIL.QOS_REQUESTED

  • Priority Code

  • Radio Channel Requested

No comment.

DETAIL.QOS_USED

  • Message Type

  • Radio Channel Used

No comment.

DETAIL.SOURCE_NETWORK

Originating Network

No comment.

DETAIL.USAGE_DIRECTION

Charged Party Status

No comment.

DETAIL.UTC_TIME_OFFSET

  • Charging Timestamp

  • LCS Request Timestamp

  • Actual Delivery Timestamp

  • Requested Delivery Timestamp

  • Order Placed Timestamp

  • Completion Timestamp

  • Deposit Timestamp

  • Call Event Start Timestamp

No comment.

DETAIL.VOLUME_RECEIVED

Data Volume Incoming

No comment.

DETAIL.VOLUME_SENT

Data Volume Outgoing

DETAIL.WHOLESALE_CHARGED_TAX_RATE

Tax Rate Code

No comment.

DETAIL.ZONE_DESCRIPTION

Distance Charge Band Code

No comment.

HEADER.CREATION_TIMESTAMP

and

HEADER.UTC_TIME_OFFSET

File Creation Timestamp

No comment.

HEADER.DATA_TYPE_INDICATOR

File Type Indicator

No comment.

HEADER.OPERATOR_SPECIFIC_INFO

Operator Specific Information

No comment.

HEADER.RECIPIENT

Recipient

No comment.

HEADER.SENDER

Sender

No comment.

HEADER.SEQUENCE_NUMBER

File Sequence Number

No comment.

HEADER.TRANSFER_CUTOFF_TIMESTAMP

and

HEADER.UTC_TIME_OFFSET

Transfer Cut Off Timestamp

No comment.

HEADER.TRANSMISSION_DATE

and

HEADER.UTC_TIME_OFFSET

File Available Timestamp

No comment.

TRAILER.OPERATOR_SPECIFIC_INFO

Operator Specific Information

No comment.


PK/lNPKSqE OEBPS/rmg_tapv311_settlement.htmG About Settling Roaming Charges

2 About Settling Roaming Charges

This chapter describes how settlement events for roaming charges are created and managed in Oracle Communications Billing and Revenue Management (BRM).

Before reading this document, you should be familiar with:

About Settlement Events

The settlement process creates settlement events with incollect roaming charges and outcollect roaming charges.

The settlement process stores incollect and outcollect settlement event records as individual events in the BRM database. This provides the following advantages:

  • It gives you the ability to include the event details along with the aggregated total roaming charges when you bill or invoice your roaming partner network operators.

  • It gives you the ability to generate reports based on the information stored in the settlement events.

  • It gives you the ability to audit and analyze the event data and generate financial reports.

When you run billing, BRM billing opcodes read the settlement event data and generate a bill for the total incollect charge amount (what you owe) and another bill for the total outcollect charge amount (what they owe). The amount that you owe your roaming partner network operator is the difference between the two.

How Settlement Events Are Created

Settlement events are created and used to bill and settle charges with your roaming partners.

How Settlement Events for Incollect Roaming Charges Are Created

Using the information in the validation pipeline output file, the incollect settlement pipeline creates settlement events that are loaded into the BRM database and used to settle charges with your roaming partners.

The incollect settlement pipeline processes the input file as follows:

  • The input module maps the contents of the file into an EDR container. For each EDR, it creates a DETAIL.ASS_ROAMING_EXT block and populates the SENDER and RECIPIENT fields. The sender is the network carrier (roaming partner) sending the TAP file and the recipient is the network carrier receiving the TAP file. Information stored in this block is used later by the pipeline to identify the roaming partner account information in the BRM database.

  • The ISC_ConsolidatedCP module removes all non '00' impact_category charge packets.

    The TAP input grammar creates individual charge packets as well as consolidated charge packets. However, the FCT_BillingRecord module considers all charge packets for creating balance packets. For this reason, the individual charge packets (non '00' impact category charge packets) are removed and only consolidated charge packets are considered so that the balance amounts in the balance packets are correct.

    This module also assigns the G/L Id to each consolidated charge packet based on the GL_CODE registry entry.

  • The FCT_ServiceCode module maps external service codes to internal service codes.

    The FCT_ServiceCode module maps all external service codes to /service/roaming/settlement/incollect in the BRM database.

  • The FCT_Account module uses the network operator account information in the pipeline in-memory cache to lookup the BRM account and associates the EDR with the BRM account and enriches the EDR with information related to the account service, product, and bill. For information about setting up network operator accounts, see "Defining Roaming Partner Accounts in the BRM Database".

  • The FCT_ItemAssign module assigns the bill item associated with the roaming partner account's incollect service to the EDR.

  • The FCT_ExchangeRate module converts the charge amount in the charge packets, which is usually in SDR currency, to the subscriber's billing currency.

  • The FCT_BillingRecord module creates the balance impact information from the charge amount provided in the EDR and associates this impact to the bill item. Balance impact information will contain the resource name, charge amount, bill item, and service information.

After the EDRs are enriched, the FCT_EnhancedSplitting module routes the EDRs to GPRS and GSM output streams. You use RE Loader to load the events into the BRM database. See "How Settlement Events Impact Roaming Partner Account Balance".

If there is any error in the settlement pipeline, the entire input file is suspended. See "About Handling Suspended Settlement Events".

How Settlement Events for Outcollect Roaming Charges Are Created

Using the information in the outcollect TAP files, the outcollect settlement pipeline creates settlement events that are loaded into the BRM database and used for billing your roaming partners.

The outcollect settlement pipeline processes the outcollect TAP file as follows:

  • The input module converts the outcollect TAP file back to EDR format and maps the TAP data to staging fields in the EDR container by using TAP input grammar.

  • The ISC_TAP_0312_InMap module maps the data in the staging fields to business fields in the EDR container. For each EDR, it creates a DETAIL.ASS_ROAMING_EXT block and populates the SENDER and RECIPIENT fields - The sender is the network carrier sending the TAP file and the recipient is the network carrier (roaming partner) receiving the TAP file. Information stored in this block is used later by the pipeline to identify the roaming partner account information in the BRM database.

  • The ISC_ConsolidatedCP module removes all non '00' impact_category charge packets.

    The TAP input grammar creates individual charge packets as well as consolidated charge packets. However, the FCT_BillingRecord module considers all charge packets for creating balance packets. For this reason, the individual charge packets (non '00' impact category charge packets) are removed and only consolidated charge packets are considered so that the balance amounts in the balance packets are correct.

    This module also assigns the G/L Id to each consolidated charge packet based on the GL_CODE registry entry.

  • The FCT_ServiceCode module maps external service codes to internal service codes.

    The FCT_ServiceCode module maps all external service codes to the /service/roaming/settlement/outcollect in the BRM database.

  • The FCT_Account module uses the network operator account information in the pipeline in-memory cache to lookup the BRM account and associates the EDR with the BRM account and enriches the EDR with information related to the account service, product, and bill. For information about setting up network operator accounts, see "Defining Roaming Partner Accounts in the BRM Database".

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

  • The FCT_ExchangeRate module converts the charge amount in the charge packets to SDR currency.

  • The FCT_BillingRecord module creates the balance impact information from the charge amount provided in the EDR and associates this impact to the bill item. Balance impact information will contain the resource name, charge amount, bill item, and service information.

After the EDRs are enriched, the FCT_EnhancedSplitting module routes the EDRs to GPRS and GSM output streams. You use RE Loader to load the events into the BRM database. See "About Loading Settlement Events into the BRM Database".

If there is any error in the settlement pipeline, the entire outcollect TAP file is suspended. See "About Handling Suspended Settlement Events".

After the settlement pipeline has successfully processed the outcollect TAP file, it generates a corresponding TAP Header Information file that stores lookup information. TAP files maintain a Lookup Directory for some items in the callEventDetails block, that specifies the item value.

For example, a callEventDetail specifies callEventStartTimeStamp by using two fields: LocalTimeStamp and UtcTimeOffsetCode. UtcTimeOffsetCode is a numeric code that points to the NetworkInfo->UtcTimeOffsetInfo entry in the Lookup Directory that specifies UtcTimeOffset value.

Any required lookup information such as UTC Time Offsets is written to the TAP Header Information file. This lookup information is later used by the RAP processing pipeline to reconstruct and reprocess the rejected TAP records. Based on the constructed rejected TAP records, the RAP processing pipeline generates the corresponding settlement backout record. See "About Processing Rejected Outcollect TAP Files and Records".

How Settlement Events Impact Roaming Partner Account Balance

Each roaming partner account in the BRM database is configured with two products, one for incollect settlement and another for outcollect settlement: for example, RoamingIncollect and RoamingOutcollect. The /service/settlement/roaming/incollect service is selected for the RoamingIncollect product and /service/settlement/roaming/outcollect service is selected for the RoamingOutcollect product. Each product is assigned a separate balance group and the balance groups are assigned separate bill units.

When incollect settlement events are loaded into the database, they are associated with the /service/settlement/roaming/incollect service and impact the bill unit for this service. The outcollect settlement events are associated with the /service/settlement/roaming/outcollect service and impact the bill unit for this service.

You create roaming partner accounts in Customer Center. For information on setting up roaming partner accounts, see "Setting Up Roaming for TAP".

For information about billing, see "About Billing" in BRM Configuring and Running Billing.

About Loading Settlement Events into the BRM Database

The incollect and outcollect settlement pipelines send settlement events to separate output streams based on the event type. The output files are generated using the RE Loader output grammar. RE Loader reads the output file and loads each event as an object into the BRM database.

For example, the GSM events are loaded into the /event/delayed/session/telco/gsm/roaming object, and the GPRS events are loaded into the /event/delayed/session/telco/gprs/roaming object.

The event object contains the roaming partner account and billing information.

Incollect settlement events are stored against the /service/settlement/roaming/incollect service object of the roaming partner account. As a result, all charges for incollect roaming events impact the roaming partner's bill unit associated with the /service/settlement/roaming/incollect service.

Outcollect settlement events are stored against the /service/settlement/roaming/outcollect service object of the roaming partner account. As a result, all charges for outcollect roaming events impact the roaming partner's bill unit associated with the /service/settlement/roaming/outcollect service.

For outcollect settlement events, RE Loader also creates a statistical record using the outcollect TAP file and stores the record in the /batch/rel object. This record contains the file name, sequence number in the header of the file, number of events in the file, and other information. Each /event/delayed/session/telco/gsm/roaming and /event/delayed/session/telco/gprs/roaming object created from the output file includes a link to the /batch/rel object. The information stored in the /batch/rel object is used to back out balance impacts of TAP records during RAP file processing.

After the events are loaded into the BRM database, you can run BRM billing to generate invoices and to settle the roaming charges with your roaming partners.

To configure RE Loader, see "Configuring Rated Event Loader to Load Settlement Events into the BRM Database".

About Handling Suspended Settlement Events

It is possible for processing errors to occur in the settlement pipeline; for example, when the pipeline fails to associate the EDR with a roaming partner account.

The ISC_RollbackSettlement module checks for errors in the EDR. When there is an error, it notifies the Transaction Manager (TAM) to roll back the transactions in the settlement pipeline. The TAM then notifies the FCT_BatchSuspense module to suspend the entire input file. FCT_BatchSuspense creates a batch file that contains the input file name, location of the file, reason code specifying the reason the file was suspended, pipeline name specifying the pipeline that suspended the file, and the EDRs in the input file. This file is loaded into the BRM database by using SB Loader.

Using Suspense Management Center, you can query the suspended file and resubmit the file for processing. When the Pipeline Manager receives the resubmit request, the DAT_ResubmitBatch module routes the file back to the settlement pipeline that originally suspended the file for processing again.

For detailed information about batch suspense, see "About Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

For more information about the TAM, see "About Pipeline Manager Transactions" in BRM System Administrator's Guide.

To configure Suspense Manager for settlement, see the following:

About Validating the Bill Amount

You can perform a rate plan check on the TAP files received from your roaming partner network operators to validate them against the rate plans in the appropriate roaming agreement.

After incollect settlement events have been loaded into the BRM database, you can run billing, which will generate a bill for the incollect roaming charges. Use the information on this bill to validate the invoices issued by your roaming partner network operators.

PK"!GGPKSqE OEBPS/toc.ncx9 Oracle® Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4 Cover Title and Copyright Information Contents Preface 1 About Rating Roaming Events 2 About Settling Roaming Charges 3 About Processing Home Subscribers' Roaming Usage 4 About Processing Visiting Subscribers' Roaming Usage 5 Installing TAP Roaming Manager 6 Setting Up Roaming for TAP 7 Setting Up Pipeline Manager for Roaming Incollect Processing 8 Setting Up Pipeline Manager for Roaming Outcollect Processing 9 RAP-to-EDR Field Mappings 10 TAP and EDR Input and Output Field Pairs 11 TAP and EDR Field Mappings 12 Rating CIBER Roaming Usage Events 13 Installing CIBER Roaming Manager 14 Rating Interconnect Events 15 Detecting Roaming Fraud Using NRTRDE 16 Installing InterConnect Manager Copyright PKNPKSqEOEBPS/rmg_edr_tap3_mapping.htm TAP and EDR Input and Output Field Pairs

10 TAP and EDR Input and Output Field Pairs

This chapter describes TAP-to-EDR mapping that Oracle Communications Billing and Revenue Management (BRM) uses when processing TAP input files and EDR-to-TAP mapping used for generating TAP output files. Before reading this document, you should be familiar with the following topics in the BRM documentation:

For TAP specifications, see the following:

http://www.gsmworld.com/

TAP-to-EDR Mapping

When processing incoming TAP files, BRM copies input data from TAP fields into EDR container fields.

Some of the fields in the TAP input files can map to multiple fields in the EDR container description file. For example, both the ACTUAL_DELIVERY_TIMESTAMP and ACT_DELIVERY_UTC_TIME_OFFSET fields in the Associated Content Extension Record of the EDR container description file store the data from the TAP Actual Delivery Timestamp field.

For some other TAP fields, placement of the field within the TAP file determines where to copy the field's data in the EDR container description file. For example, depending on the context within the TAP file, Location Identifier can be mapped to the LOCATION_LIST.IDENTIFIER field in either Associated Location Extension Record or Associated Content Extension Record of the EDR container description file.

Table 10-1 lists the TAP fields that BRM uses when reading the input files and the EDR fields that correspond to the TAP fields.

Table 10-1 TAP Fields in BRM

TAP FieldEDR FieldComments

Access Point Name NI

GPRS Destination Camel Group:

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

GPRS Destination, other cases:

  • DETAIL.ASS_GPRS_EXT.APN_ADDRESS

Access Point Name NI and Access Point Name OI are mapped to a single EDR field as concatenated and comma-separated items.

Access Point Name OI

GPRS Destination Camel Group:

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

GPRS Destination, other cases:

  • DETAIL.ASS_GPRS_EXT.APN_ADDRESS

Access Point Name NI and Access Point Name OI are mapped to a single EDR field as concatenated and comma-separated items.

Action Code

DETAIL.ASS_GSMW_EXT.SS_PACKET.ACTION_CODE

No comment.

Actual Delivery Timestamp

DETAIL.ASS_CONT_EXT.ACTUAL_DELIVERY_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_CONT_EXT.ACTUAL_DELIVERY_TIMESTAMP, and the UTC offset part is mapped to DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET.

Advised Charge

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE

No comment.

Advised Charge Currency

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE_CURRENCY

No comment.

Age Of Location

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.AGE_OF_LOCATION

No comment.

Air Interface User Rate Requested

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.AIUR

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.AIUR_REQUESTED

No comment.

Basic HSCSD Parameters

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST

This is a block.

Basic Service Used

DETAIL.ASS_GSMW_EXT.BS_PACKET

This is a block.

Bearer Service Code

DETAIL.BASIC_SERVICE

No comment.

Call Event Details Count

TRAILER.TAP_TOTAL_NUMBER_OF_RECORDS

No comment.

Call Event Start Timestamp

DETAIL.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.CHARGING_START_TIMESTAMP, and the UTC offset part is mapped to DETAIL.UTC_TIME_OFFSET.

Call Reference

DETAIL.ASS_LOCN_EXT.CALL_REFERENCE

For Location Services group, Call Reference is saved in the EDR field.

Call Type Level 1

DETAIL.CONNECT_TYPE

Call Type Level 1 and Call Type Level 2 are mapped to the EDR field as concatenated comma-separated items.

Call Type Level 2

DETAIL.CONNECT_TYPE

Call Type Level 1 and Call Type Level 2 are mapped to the EDR field as concatenated comma-separated items.

Call Type Level 3

DETAIL.CONNECT_SUB_TYPE

No comment.

Called Country Code

DETAIL.CALLED_COUNTRY_CODE

No comment.

Called Place

DETAIL.DESCRIPTION

Destination Group.

The TAP fields Called Place and Called Region are mapped to the EDR field as concatenated comma-separated items.

Called Region

DETAIL.DESCRIPTION

Destination Group.

The TAP fields Called Place and Called Region are mapped to the EDR field as concatenated comma-separated items.

Camel Call Reference

DETAIL.ASS_CAMEL_EXT.CAMEL_REFERENCE_NUMBER

No comment.

CAMEL Destination Number

DETAIL.ASS_CAMEL_EXT.DEST_GSMW_NUMBER_ORIGINAL

No comment.

Camel Initiated CF Indicator

DETAIL.ASS_CAMEL_EXT.CAMEL_INITIATED_CF_INDICATOR

No comment.

Camel Modification

DETAIL.ASS_CAMEL_EXT.CAMEL_MODIFICATION_LIST

All Camel Modification fields present in Camel Modification List are mapped to the EDR field as concatenated comma-separated items.

Camel Server Address

DETAIL.ASS_CAMEL_EXT.SERVER_ADDRESS

No comment.

CAMEL Service Key

DETAIL.ASS_CAMEL_EXT.SERVICE_KEY

No comment.

CAMEL Service Level

DETAIL.ASS_CAMEL_EXT.SERVICE_LEVEL

No comment.

CAMEL Service Used

DETAIL.ASS_CAMEL_EXT

This is a block.

Cause For Termination

DETAIL.CALL_COMPLETION_INDICATOR

If the TAP field value is less than 10, it is prefixed with 0.

Cell Identity

GPRS Network Location:

  • DETAIL.ASS_GPRS_EXT.CELL_ID

Network Location:

  • DETAIL.ASS_GSMW_EXT.CELL_ID

Present within groups:

  • GPRS Network Location

  • Network Location

Channel Coding Acceptable

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.CHANNEL_CODING_OK_LIST

All channel coding fields present in Channel Coding Acceptable List are mapped to the EDR field as concatenated comma-separated items.

Channel Coding Used

HSCSD Parameter Modification:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.CHANNEL_CODING_USED

Basic HSCSD Parameters:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.CHANNEL_CODING_USED

Channel Coding Acceptable List:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.CHANNEL_CODING_OK_LIST

No comment.

Charge

DETAIL.ASS_CBD.CP.CHARGED_AMOUNT_VALUE

No comment.

Charge Refund Indicator

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CHARGE_REFUND_INDICATOR

No comment.

Charge Type

Taxation:

  • DETAIL.ASS_CBD.TP.CHARGE_TYPE

Charge Detail:

  • TRAILER.TOTAL_CHARGE_VALUE_LIST.CHARGE_TYPE

  • DETAIL.ASS_CBD.CP.IMPACT_CATEGORY

Present within groups:

  • Taxation, when the associated Tax Rate Code references a tax applied to a specific Charge Type

  • Charge Detail

Chargeable Units

DETAIL.ASS_CBD.CP.CHARGEABLE_QUANTITY_VALUE

No comment.

Charged Party Equipment

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT

This is a block.

Charged Party Home Identification

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST

This is a block.

Charged Party Id Type

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.TYPE

No comment.

Charged Party Identification

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST

This is a block.

Charged Party Identifier

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.IDENTIFIER

No comment.

Charged Party Information

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO

This is a block.

Charged Party Location

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST

This is a block.

Charged Party Status

DETAIL.USAGE_DIRECTION

No comment.

Charged Units

DETAIL.ASS_CBD.CP.ROUNDED_QUANTITY_VALUE

No comment.

Charging Characteristics

DETAIL.USAGE_CLASS

No comment.

Charging ID

DETAIL.ASS_GPRS_EXT.CHARGING_ID

No comment.

Charging Timestamp

Supplementary Service Used:

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.UTC_TIME_OFFSET

Location Service Usage:

  • DETAIL.ASS_GPRS_EXT.SERVICE_USED_CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GPRS_EXT.SERVICE_USED_UTC_TIME_OFFSET

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.UTC_TIME_OFFSET

Basic Service Used:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.UTC_TIME_OFFSET

GPRS Call (Record type MSS, SCU, and VAS):

  • DETAIL.CHARGING_START_TIMESTAMP

    and

  • DETAIL.UTC_TIME_OFFSET

GPRS Service Usage Block:

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.UTC_TIME_OFFSET

GPRS Service Used Block:

  • DETAIL.ASS_GPRS_EXT.SERVICE_USED_CHARGING_START_TIMESTAMP

    and

  • DETAIL.ASS_GPRS_EXT.SERVICE_USED_UTC_TIME_OFFSET

Present within groups:

  • Supplementary Service Used. The timestamp is mandatory and occurs within Supplementary Service Event.

  • Location Service Usage. The timestamp is only present where it is not the same as the associated LCS Request Timestamp.

  • Basic Service Used. The timestamp is only present where it is not the same as an associated Call Event Start Timestamp.

CLIR Status Indicator

Call Originator and SCU Basic Information:

  • DETAIL.USAGE_CLASS

Third-Party Information:

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.CLIR_INDICATOR

Present within groups:

  • Call Originator where available.

  • SCU Basic Information where available and the Charged Party Status indicates a terminating short message.

  • Third-Party Information where available.

Commission

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.COMMISSION

No comment.

Completion Timestamp

DETAIL.CHARGING_END_TIMESTAMP

No comment.

Content Charging Point

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_CHARGING_POINT

No comment.

Content Provider

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST

This is a block.

Content Provider Id Type

LCS SP Identification:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.TYPE

Content Provider:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.TYPE

Mandatory within groups:

  • LCS SP Identification

  • Content Provider

Content Provider Identifier

LCS SP Identification:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.IDENTIFIER

Content Provider:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.IDENTIFIER

Mandatory within groups:

  • LCS SP Identification

  • Content Provider

Content Provider Name

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_NAME

No comment.

Content Service Used

DETAIL.ASS_CONT_EXT.SERVICE_

USED_LIST

This is a block.

Content Transaction Code

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_CODE

No comment.

Content Transaction Type

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_TYPE

No comment.

CSE Information

DETAIL.ASS_CAMEL_EXT.CSE_INFORMATION

No comment.

Customer Id Type

Tracking Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.TYPE

Tracked Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.TYPE

Mandatory within groups:

  • Tracking Customer Identification

  • Tracked Customer Identification

Customer Identifier

Tracking Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.IDENTIFIER

Tracked Customer Identification:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.IDENTIFIER

Mandatory within groups:

  • Tracking Customer Identification

  • Tracked Customer Identification

Data Volume Incoming

GPRS Service Used:

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.VOLUME_RECEIVED

Content Service Used:

  • DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_INCOMING

Present within groups:

  • GPRS Service Used. Mandatory

  • Content Service Used when available

Data Volume Outgoing



GPRS Service Used:

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.VOLUME_SENT

Content Service Used:

  • DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_OUTGOING

Present within groups:

  • GPRS Service Used. Mandatory

  • Content Service Used when available

Day Category

DETAIL.ASS_CBD.CP.DAY_CODE

No comment.

Default Call Handling Indicator

DETAIL.ASS_CAMEL_EXT.DEFAULT_CALL_HANDLING_INDICATOR

No comment.

Deposit Timestamp

DETAIL.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.CHARGING_START_TIMESTAMP, and the UTC offset part is mapped to DETAIL.UTC_TIME_OFFSET.

Destination Network

DETAIL.DESTINATION_NETWORK

No comment.

Dialled Digits

  • DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

  • DETAIL.C_NUMBER

No comment.

Discount Code

DETAIL.ASS_CBD.CP.GRANTED_DISCOUNT_AMOUNT_VALUE

No comment.

Discount Value

DETAIL.ASS_CBD.CP.GRANTED_DISCOUNT_AMOUNT_VALUE

No comment.

Distance Charge Band Code

DETAIL.ZONE_DESCRIPTION

No comment.

Dual Bearer Service Code

DETAIL.ASS_GSMW_EXT.BASIC_DUAL_SERVICE

The TAP field is prefixed with 1 and stored in the EDR field.

Dual Teleservice Code

DETAIL.ASS_GSMW_EXT.BASIC_DUAL_SERVICE

The TAP field is prefixed with 0 and stored in the EDR field.

Earliest Call Timestamp

TRAILER.FIRST_START_TIMESTAMP

and

TRAILER.FIRST_CHARGING_UTC_TIME_OFFSET

The timestamp part of this item is mapped to TRAILER.FIRST_START_TIMESTAMP, and the UTC offset part is mapped to TRAILER.FIRST_CHARGING_UTC_TIME_OFFSET.

Equipment Id

Charged Party Equipment:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.IDENTIFIER

Tracking Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.IDENTIFIER

Tracked Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.IDENTIFIER

Mandatory within groups:

  • Charged Party Equipment

  • Tracking Customer Equipment

  • Tracked Customer Equipment

Equipment Id Type

Charged Party Equipment:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.TYPE

Tracking Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.TYPE

Tracked Customer Equipment:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.TYPE

Mandatory within groups:

  • Charged Party Equipment

  • Tracking Customer Equipment

  • Tracked Customer Equipment

ESN

DETAIL.ASS_GSMW_EXT.DEVICE_NUMBER

No comment.

Exchange Rate Code

DETAIL.ASS_CBD.CP.EXCHANGE_RATE

No comment.

File Available Timestamp

HEADER.TRANSMISSION_DATE

No comment.

File Creation Timestamp

HEADER.CREATION_TIMESTAMP

and

HEADER.UTC_TIME_OFFSET

The timestamp part of this item is mapped to HEADER.CREATION_TIMESTAMP, and the UTC offset part is mapped to HEADER.UTC_TIME_OFFSET.

File Sequence Number

HEADER.SEQUENCE_NUMBER

No comment.

File Type Indicator

HEADER.DATA_TYPE_INDICATOR

No comment.

Fixed Network User Rate

DETAIL.ASS_GSMW_EXT.BS_PACKET.FNUR

No comment.

Fraud Monitor Indicator

DETAIL.FRAUD_MONITOR_INDICATOR

No comment.

Geographical Location

DETAIL.GEOGRAPHICAL_LOCATION

The EDR field contains comma-separated tag-value pairs that indicate the geographical location of the serving network, serving BID, serving location description, longitude, and latitude.

The tag values of the corresponding fields are as follows:

  • ServingNetwork: 1

  • ServingBID: 2

  • ServingLocationDescription: 3

  • Longitude: 4

  • Latitude: 5

Example 1: If the TAP field values are as follows:

  • ServingNetwork: AIRTEL

  • ServingBID: AIRBID

  • ServingLocationDescription: Bangalore

  • Longitude: 111

  • Latitude: 103

The value of DETAIL.GEOGRAPHICAL_LOCATION would be 1,AIRTEL, 2,AIRBID, 3,Bangalore, 4,111,5,103.

Example 2: If the TAP field values are as follows:

  • ServingNetwork: AIRTEL

  • ServingBID: AIRBID

  • Latitude: 103

The value of DETAIL.GEOGRAPHICAL_LOCATION would be 1,AIRTEL, 2,AIRBID, 5,103.

GPRS Destination

GPRS Basic Call Information:

  • DETAIL.ASS_GPRS_EXT.APN_ADDRESS

    and

  • DETAIL.ASS_GPRS_EXT.PDP_REMOTE_ADDRESS

CAMEL Service Used:

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

    and

  • DETAIL.ASS_CAMEL_EXT.DEST_GPRS_PDP_REMOTE_ADDRESS

Present within groups:

  • GPRS Basic Call Information. Mandatory.

  • CAMEL Service Used where GPRS Destination has been modified by the CAMEL server.

Home Id Type

Charged Party Home Identification:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.TYPE

Tracking Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.TYPE

Tracked Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.TYPE

Mandatory within groups:

  • Charged Party Home Identification

  • Tracking Customer Home Id

  • Tracked Customer Home Id

Home Identifier

Charged Party Home Identification:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.IDENTIFIER

Tracked Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Tracking Customer Home Id:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Mandatory within groups:

  • Charged Party Home Identification

  • Tracking Customer Home Id

  • Tracked Customer Home Id

Horizontal Accuracy Delivered

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_DELIVERED

No comment.

Horizontal Accuracy Requested

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_REQUESTED

No comment.

HSCSD Parameter Modification

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST

This is a block.

IMEI

  • DETAIL.ASS_GSMW_EXT.DEVICE_NUMBER

GPRS:

  • DETAIL.ASS_GPRS_EXT.DEVICE_NUMBER

Present within the group:

  • Equipment Identifier where available. Is not present when the terminal equipment is not involved in the call.

IMSI

  • DETAIL.ASS_GSMW_EXT.PORT_NUMBER

GPRS:

  • DETAIL.ASS_GPRS_EXT.PORT_NUMBER

Present within groups:

  • Chargeable Subscriber when MIN is not present. Mandatory.

  • GSM Chargeable Subscriber when available.

  • Must be present for WLAN usage when IMSI is used for identifying the chargeable user.

Initiating Party

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.INITIATING_PARTY

No comment.

Internet Service Provider

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST

This is a block.

ISP Id Type

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.TYPE

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.TYPE

No comment.

ISP Identifier

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.IDENTIFIER

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.IDENTIFIER

No comment.

Latest Call Timestamp

TRAILER.LAST_START_TIMESTAMP

and

TRAILER.LAST_CHARGING_UTC_TIME_OFFSET

The timestamp part of this item is mapped to TRAILER.LAST_START_TIMESTAMP and the UTC offset part is mapped to TRAILER.LAST_CHARGING_UTC_TIME_OFFSET.

LCS Request Timestamp

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQUEST_TIMESTAMP

and

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQ_UTC_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQUEST_TIMESTAMP and the UTC offset part is mapped to DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQ_UTC_OFFSET.

LCS SP Identification

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST

This is a block.

LCS SP Information

DETAIL.ASS_LOCN_EXT.LCSSP_INFO

This is a block.

LCS Transaction Status

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_TRANS_STATUS

No comment.

Local Currency

DETAIL.WHOLESALE_CHARGED_AMOUNT_CURRENCY

No comment.

Location Area Code

GPRS Network Location:

  • DETAIL.ASS_GPRS_EXT.LOCATION_AREA_INDICATOR

Network Location:

  • DETAIL.ASS_GSMW_EXT.LOCATION_AREA_INDICATOR

Mandatory within groups:

  • GPRS Network Location

  • Network Location

Except where not supported by the network or the call does not terminate at the equipment.

Location Id Type

Charged Party Location:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.TYPE

Tracked Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.TYPE

Tracking Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.TYPE

Mandatory within groups:

  • Charged Party Location

  • Tracked Customer Location

  • Tracking Customer Location

Location Identifier

Charged Party Location:

  • DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.IDENTIFIER

Tracked Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.IDENTIFIER

Tracking Customer Location:

  • DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.IDENTIFIER

Mandatory within groups:

  • Charged Party Location

  • Tracked Customer Location

  • Tracking Customer Location

Location Service Usage

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE

This is a block.

Message Description Code

-

Message Description Code is not mapped to any EDR field. The DETAIL.DESCRIPTION field in the SCU Charge Type group contains description text with Message Description Code.

Message Status

DETAIL.CALL_COMPLETION_INDICATOR

If the TAP field value is less than 10, it is prefixed with 0.

Message Type

DETAIL.QOS_USED

No comment.

Mobile Station Classmark

DETAIL.ASS_GSMW_EXT.MS_CLASS_MARK

No comment.

Modification Timestamp

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MODIFICATION_TIMESTAMP

and

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MODIFICATION_TIMESTAMP, and the UTC offset part is mapped to DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.UTC_TIME_OFFSET.

MSISDN

The TAP field is mapped to the following fields:

  • DETAIL.A_NUMBER

  • DETAIL.INTERN_A_NUMBER_ZONE

  • DETAIL.ASS_GSMW_EXT.A_NUMBER_USER

GPRS:

  • DETAIL.ASS_GPRS_EXT.A_NUMBER_USER

SCU:

  • DETAIL.ASS_GSMW_EXT.A_NUMBER_USER

  • DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

MTC:

  • DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

The EDR field is always prefixed with International Access Code.

Present within groups:

  • Chargeable Subscriber or GPRS Chargeable Subscriber when IMSI is present. Should be associated with IMSI.

  • GSM Chargeable Subscriber when available.

  • Present when expected in accordance with roaming agreement.

  • Present for WLAN network usage where the full IMSI or Network Access Identifier is not available.

Network Id Type

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.TYPE

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.NETWORK_LIST.TYPE

No comment.

Network Identifier

Serving Parties Information:

  • DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.IDENTIFIER

LCS SP Information:

  • DETAIL.ASS_LOCN_EXT.LCSSP_INFO.NETWORK_LIST.IDENTIFIER

No comment.

Network Init. PDP Context

DETAIL.ASS_GPRS_EXT.NETWORK_INITIATED_PDP

No comment.

Network Type

DETAIL.SOURCE_NETWORK_TYPE

No comment.

Number Of Channels

Basic HSCSD Parameters:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.NUMBER_OF_CHANNELS

HSCSD Parameter Modification:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MAX_NUMBER_OF_CHANNELS

No comment.

Number Of Channels Used

Basic HSCSD Parameters:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.NUMBER_OF_CHANNELS_USED

  • DETAIL.NUMBER_OF_UNITS

HSCSD Parameter Modification:

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.NUMBER_OF_

    CHANNELS_USED

No comment.

Object Type

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.OBJECT_TYPE

No comment.

Order Placed Timestamp

DETAIL.ASS_CONT_EXT.ORDER_PLACED_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_CONT_EXT.ORDER_PLACED_TIMESTAMP, and the UTC offset part is mapped to DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET.

Originating Network

DETAIL.SOURCE_NETWORK

No comment.

Paid Indicator

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAID_INDICATOR

No comment.

Partial Type Indicator

DETAIL.LONG_DURATION_INDICATOR

No comment.

Payment Method

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAYMENT_METHOD

No comment.

PDP Address

DETAIL.ASS_GPRS_EXT.PDP_ADDRESS

No comment.

PDP Context Start Timestamp

DETAIL.ASS_GPRS_EXT.PDP_CONTEXT_START_TIMESTAMP

and

DETAIL.ASS_GPRS_EXT.PDP_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_GPRS_EXT.PDP_CONTEXT_START_TIMESTAMP, and the UTC offset part is mapped to DETAIL.ASS_GPRS_EXT.PDP_UTC_TIME_OFFSET.

<p>Positioning Method

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.POSITIONING_METHOD

No comment.

Priority Code

DETAIL.QOS_REQUESTED

No comment.

QoS Delay

QoS Requested:

  • DETAIL.ASS_GPRS_EXT.QOS_REQUESTED_DELAY

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_DELAY

QoS Used:

  • DETAIL.ASS_GPRS_EXT.QOS_USED_DELAY

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_DELAY

No comment.

QoS Mean Throughput

QoS Requested:

  • DETAIL.ASS_GPRS_EXT.QOS_REQUESTED_MEAN_THROUGHPUT

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_MEAN_THROUGHPUT

QoS Used:

  • DETAIL.ASS_GPRS_EXT.QOS_USED_MEAN_THROUGHPUT

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_MEAN_THROUGHPUT

No comment.

QoS Peak Throughput

QoS Requested:

  • DETAIL.ASS_GPRS_EXT.QOS_REQUESTED_PEAK_THROUGHPUT

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_PEAK_THROUGHPUT

QoS Used:

  • DETAIL.ASS_GPRS_EXT.QOS_USED_PEAK_THROUGHPUT

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_PEAK_THROUGHPUT

No comment.

QoS Precedence

QoS Requested:

  • DETAIL.ASS_GPRS_EXT.QOS_REQUESTED_PRECEDENCE

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_PRECEDENCE

QoS Used:

  • DETAIL.ASS_GPRS_EXT.QOS_USED_PRECEDENCE

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_PRECEDENCE

No comment.

QoS Reliability

QoS Requested:

  • DETAIL.ASS_GPRS_EXT.QOS_REQUESTED_RELIABILITY

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_RELIABILITY

QoS Used:

  • DETAIL.ASS_GPRS_EXT.QOS_USED_RELIABILITY

  • DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_RELIABILITY

No comment.

Radio Channel Requested

  • DETAIL.QOS_REQUESTED

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.QOS_REQUESTED

No comment.

Radio Channel Used

  • DETAIL.QOS_USED

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.QOS_USED

No comment.

RAP File Sequence Number

Call Event Details:

  • DETAIL.RAP_FILE_SEQ_NO

Batch Control Information and Notification:

  • HEADER.RAP_FILE_SEQ_NO

Must be present within groups:

  • Notification

  • Batch Control Information

Recipient

HEADER.RECIPIENT

No comment.

Recording Entity Code

Service Center Usage:

  • DETAIL.ASS_GSMW_EXT.ORIGINATING_SWITCH_IDENTIFICATION

Location Service:

  • DETAIL.ASS_LOCN_EXT.REC_ENTITY_CODE

Mandatory within groups:

  • Recording Entity Information

  • Location Service

  • Network Location

  • Service Center Usage where it must be of type 'Service Center'

In the case of GPRS network usage, two or more occurrences must be present within GPRS Network Location. One occurrence must be of type 'GGSN' (see Recording Entity Type) and all other occurrences must be of type 'SGSN'.

In the case of WLAN network usage, one occurrence must be present identifying the WLAN billing information recording entity.

Network Location:

Recording Entity Code is used to get corresponding Recording Entity ID. Recording Entity Code is not stored in any EDR field.

Rec Entity Code Information:

Recording Entity Code is used to get corresponding Recording Entity ID. Recording Entity Code is not stored in any EDR field.

Release Version Number

HEADER.RELEASE_VERSION

No comment.

Requested Delivery Timestamp

DETAIL.ASS_CONT_EXT.REQUESTED_DELIVERY_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.REQ_DELIVERY_UTC_TIME_OFFSET

The timestamp part of this item is mapped to DETAIL.ASS_CONT_EXT.REQUESTED_DELIVERY_TIMESTAMP, and the UTC offset part is mapped to DETAIL.ASS_CONT_EXT.REQ_DELIVERY_UTC_TIME_OFFSET.

Response Time

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME

No comment.

Response Time Category

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME_CATEGORY

No comment.

Sender

HEADER.SENDER

No comment.

Serving Network

Serving Network:

  • DETAIL.ASS_GSMW_EXT.SERVING_NETWORK

Geographical Location:

  • DETAIL.GEOGRAPHICAL_LOCATION

Serving Network is stored in DETAIL.GEOGRAPHICAL_LOCATION along with other concatenated comma-separated tag-value pairs from Geographical Location.

Serving Parties Information

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO

This is a block.

SIM Toolkit Indicator

DETAIL.DISCOUNT_KEY

No comment.

Specification Version Number

HEADER.SPECIFICATION_VERSION_NUMBER

No comment.

Speech Version Requested

DETAIL.ASS_GSMW_EXT.BS_PACKET.SPEECH_VERSION_REQUESTED

No comment.

Speech Version Used

DETAIL.ASS_GSMW_EXT.BS_PACKET.SPEECH_VERSION_USED

No comment.

Supplementary Service Code

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_EVENT

No comment.

Supplementary Service Parameters

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_PARAMETERS

No comment.

Supplementary Service Used

DETAIL.ASS_GSMW_EXT.SS_PACKET

This is a block.

TAP Decimal Places

HEADER.TAP_DECIMAL_PLACES

No comment.

Tax Information

DETAIL.ASS_CBD.TP

This is a block.

Tax Rate Code

DETAIL.ASS_CBD.TP.TAX_CODE

Mandatory within groups:

  • Taxation

  • Tax Information

Tax Value

  • DETAIL.WHOLESALE_CHARGED_TAX_VALUE

  • DETAIL.ASS_CBD.TP.TAX_VALUE

No comment.

Taxable Amount

DETAIL.ASS_CBD.TP.TAXABLE_AMOUNT

No comment.

TeleService Code

  • DETAIL.BASIC_SERVICE

  • DETAIL.ASS_GSMW_EXT.BS_PACKET.BASIC_SERVICE

The EDR fields are prefixed with 0.

Third Party Number

  • DETAIL.C_NUMBER

  • DETAIL.ASS_GSMW_EXT.SS_PACKET.THIRD_PARTY_NUMBER

Present within the Third Party Information group where available.

Time Band

DETAIL.ASS_CBD.CP.TIME_INTERVAL_CODE

No comment.

Total Transaction Duration

Total Transaction Duration:

  • DETAIL.ASS_CONT_EXT.TOTAL_TRANSACTION_DURATION

Total Call Event Duration:

  • DETAIL.TOTAL_CALL_EVENT_DURATION

No comment.

Total Call Event Duration

Total Call Event Duration:

  • DETAIL.TOTAL_CALL_EVENT_DURATION

Total Transaction Duration:

  • DETAIL.ASS_CONT_EXT.TOTAL_TRANSACTION_DURATION

No comment.

Total Charge

TRAILER.TOTAL_CHARGE_VALUE_LIST

This is a block.

Total Charge Refund

TRAILER.TOTAL_CHARGE_VALUE_LIST.TOTAL_CHARGE_REFUND

No comment.

Total Data Volume

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TOTAL_DATA_VOLUME

No comment.

Total Discount Value

TRAILER.TAP_TOTAL_DISCOUNT_VALUE

No comment.

Total Tax Value

TRAILER.TAP_TOTAL_TAX_VALUE

No comment.

Tracked Customer Equipment

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT

This is a block.

Tracked Customer Home Id

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST

This is a block.

Tracked Customer Identification

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST

This is a block.

Tracked Customer Information

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO

This is a block.

Tracked Customer Location

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST

This is a block.

Tracking Customer Equipment

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT

This is a block.

Tracking Customer Home Id

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST

This is a block.

Tracking Customer Identification

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST

This is a block.

Tracking Customer Information

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO

This is a block.

Tracking Customer Location

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST

This is a block.

Tracking Frequency

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.REQ_TRACKING_FREQUENCY

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_FREQUENCY

No comment.

Tracking Period

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.TRACKING_PERIOD

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_PERIOD

No comment.

Transaction Authorization Code

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_AUTH_CODE

No comment.

Transaction Description Suppression

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DESCRIPTION_SUPP

No comment.

Transaction Detail Description

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DETAIL_

DESCRIPTION

No comment.

Transaction Identifier

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_IDENTIFIER

No comment.

Transaction Short Description

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_SHORT_DESCRIPTION

No comment.

Transaction Status

DETAIL.ASS_CONT_EXT.TRANSACTION_STATUS

No comment.

Transfer Cut Off Timestamp

HEADER.TRANSFER_CUTOFF_TIMESTAMP

No comment.

Transparency Indicator

DETAIL.ASS_GSMW_EXT.BS_PACKET.TRANSPARENCY_INDICATOR

No comment.

UMTS Quality Of Service Requested

DETAIL.ASS_GPRS_EXT.GS_PACKET.UMTS_QOS_REQUESTED

The EDR field contains comma-separated tag-value pairs mapped from UMTS Quality Of Service Requested.

The tag values of the corresponding fields are as follows:

  • QosTrafficClassKey: 1

  • QosMaxBitRateUpLnKey: 2

  • QosMaxBitRateDownLnKey: 3

  • QosGuaranteedBitRateDownLnKey: 4

  • QosGuaranteedBitRateUpLnKey: 5

  • QosAllocRetenPriorityKey: 6

UMTS Quality Of Service Used

DETAIL.ASS_GPRS_EXT.GS_PACKET.UMTS_QOS_USED

The EDR field contains comma-separated tag-value pairs mapped from UMTS Quality Of Service Used.

The tag values of the corresponding fields are as follows:

  • QosTrafficClassKey: 1

  • QosMaxBitRateUpLnKey: 2

  • QosMaxBitRateDownLnKey: 3

  • QosGuaranteedBitRateDownLnKey: 4

  • QosGuaranteedBitRateUpLnKey: 5

  • QosAllocRetenPriorityKey: 6

User Protocol Indicator

DETAIL.ASS_GSMW_EXT.BS_PACKET.USER_PROTOCOL_INDICATOR

No comment.

UTC Time Offset

File Creation Timestamp:

  • HEADER.UTC_TIME_OFFSET

Earliest Call Timestamp:

  • TRAILER.FIRST_CHARGING_UTC_TIME_OFFSET

Latest Call Timestamp

  • TRAILER.LAST_CHARGING_UTC_TIME_OFFSET

Mandatory within items:

  • File Creation Timestamp

  • Earliest Call Timestamp

  • Latest Call Timestamp

Mandatory within UTC Time Offset Information.

UTC Time Offset Code

Actual Delivery Timestamp:

  • DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET

Order Placed Timestamp:

  • DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET

Requested Delivery Timestamp:

  • DETAIL.ASS_CONT_EXT.REQ_DELIVERY_UTC_TIME_OFFSET

LCS Request Timestamp:

  • DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQ_UTC_OFFSET

Mandatory within UTC Time Offset Information.

Mandatory within items:

  • Call Event Start Timestamp

  • Charging Timestamp

  • Charge Detail Timestamp

  • Deposit Timestamp

  • Completion Timestamp

  • Order Placed Timestamp

  • Requested Delivery Timestamp

  • Actual Delivery Timestamp

  • LCS Request Timestamp

  • PDP Context Start Timestamp

In Date Time group, UTC Time Offset Code is only used to get corresponding UTC Time Offset, but is not mapped to any EDR field.

Value Added Service Used

DETAIL.ASS_VAS_EXT

This is a block.

VAS Code

  • DETAIL.ASS_VAS_EXT.VAS_CODE

  • DETAIL.ASS_GSMW_EXT.VAS_PRODUCT_CODE

No comment.

Vertical Accuracy Delivered

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_DELIVERED

No comment.

Vertical Accuracy Requested

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_REQUESTED

No comment.


EDR-to-TAP Mapping

When generating output TAP files, BRM maps EDR container fields to the fields in TAP output files. The following table lists the EDR and TAP pairs that BRM uses when producing the output files.

Some of the fields in the EDR container file, such as DETAIL.UTC_TIME_OFFSET, can provide data to different fields in the output TAP file as shown in Table 10-2.

Table 10-2 EDR Fields in BRM

EDR FieldTAP FieldComments

DETAIL.A_NUMBER

MSISDN

No comment.

DETAIL.ASS_CAMEL_EXT

CAMEL Service Used

This is a block.

DETAIL.ASS_CAMEL_EXT.CAMEL_INITIATED_CF_INDICATOR

Camel Initiated CF Indicator

No comment.

DETAIL.ASS_CAMEL_EXT.CAMEL_MODIFICATION_LIST

Camel Modification

Comma-separated list.

DETAIL.ASS_CAMEL_EXT.CAMEL_REFERENCE_NUMBER

Camel Call Reference

No comment.

DETAIL.ASS_CAMEL_EXT.CSE_INFORMATION

CSE Information

No comment.

DETAIL.ASS_CAMEL_EXT.DEFAULT_CALL_HANDLING_INDICATOR

Default Call Handling Indicator

No comment.

DETAIL.ASS_CAMEL_EXT.DEST_GPRS_APN_ADDRESS

GPRS Destination

The EDR field contains concatenated and comma-separated values of Access Point Name NI and Access Point Name OI.

DETAIL.ASS_CAMEL_EXT.DEST_GPRS_PDP_REMOTE_ADDRESS

Remote Pdp Address List

Comma-separated list.

DETAIL.ASS_CAMEL_EXT.DEST_GSMW_NUMBER

Camel Destination Number

International Access Code prefixes the EDR field.

DETAIL.ASS_CAMEL_EXT.DEST_GSMW_NUMBER_ORIGINAL

Camel Destination Number

No comment.

DETAIL.ASS_CAMEL_EXT.MSC_ADDRESS

Camel Msc Address

International Access Code prefixes the EDR field.

DETAIL.ASS_CAMEL_EXT.SERVER_ADDRESS

Camel Server Address

No comment.

DETAIL.ASS_CAMEL_EXT.SERVICE_KEY

CAMEL Service Key

No comment.

DETAIL.ASS_CAMEL_EXT.SERVICE_LEVEL

CAMEL Service Level

No comment.

DETAIL.ASS_CBD.CP.CHARGEABLE_QUANTITY_VALUE

Chargeable Units

No comment.

DETAIL.ASS_CBD.CP.CHARGED_AMOUNT_VALUE

Charge

No comment.

DETAIL.ASS_CBD.CP.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

Charging Timestamp

No comment.

DETAIL.ASS_CBD.CP.DAY_CODE

Day Category

No comment.

DETAIL.ASS_CBD.CP.EXCHANGE_RATE

Exchange Rate Code

No comment.

DETAIL.ASS_CBD.CP.GRANTED_DISCOUNT_AMOUNT_VALUE

  • Discount Value

  • Discount Code

No comment.

DETAIL.ASS_CBD.CP.IMPACT_CATEGORY

Charge Type

No comment.

DETAIL.ASS_CBD.CP.PRODUCTCODE_USED

VAS:

  • VasShortDesc for the corresponding VAS Code

Camel:

  • Hard coded to CAMEL

In Charge Detail Group, values that are mapped to the EDR field depend on the service type: VAS or Camel.

DETAIL.ASS_CBD.CP.ROUNDED_QUANTITY_VALUE

Charged Units

No comment.

DETAIL.ASS_CBD.CP.TIME_INTERVAL_CODE

Time Band

No comment.

DETAIL.ASS_CBD.TP

Tax Information

This is a block.

DETAIL.ASS_CBD.TP.CHARGE_TYPE

Charge Type

No comment.

DETAIL.ASS_CBD.TP.TAX_CODE

Tax Rate Code

No comment.

DETAIL.ASS_CBD.TP.TAX_VALUE

Tax Value

No comment.

DETAIL.ASS_CBD.TP.TAXABLE_AMOUNT

Taxable Amount

No comment.

DETAIL.ASS_CONT_EXT.ACTUAL_DELIVERY_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.ACT_DELIVERY_UTC_TIME_OFFSET

Actual Delivery Timestamp

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO

Charged Party Information

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT

Charged Party Equipment

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.IDENTIFIER

Charged Party Equipment:

  • Equipment Id

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.EQUIPMENT.TYPE

Charged Party Equipment:

  • Equipment Id Type

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST

Charged Party Home Identification

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.IDENTIFIER

Charged Party Home Identification:

  • Home Identifier

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.HOMEID_LIST.TYPE

Charged Party Home Identification:

  • Home Id Type

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST

Charged Party Identification

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.IDENTIFIER

Charged Party Identifier

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.ID_LIST.TYPE

Charged Party Id Type

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST

Charged Party Location

This is a block.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.IDENTIFIER

Charged Party Location:

  • Location Identifier

No comment.

DETAIL.ASS_CONT_EXT.CHARGED_PARTY_INFO.LOCATION_LIST.TYPE

Charged Party Location:

  • Location Id Type

No comment.

DETAIL.ASS_CONT_EXT.ORDER_PLACED_TIMESTAMP

and

DETAIL.ASS_CONT_EXT.ORDER_PLACED_UTC_TIME_OFFSET

Order Placed Timestamp

No comment.

DETAIL.ASS_CONT_EXT.RECORD_NUMBER

Keeps the number of records of contentTransaction.

No comment.

DETAIL.ASS_CONT_EXT.REQUESTED_DELIVERY_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

Requested Delivery Timestamp

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST

Content Service Used

This is a block.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE

Advised Charge

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.ADVISED_CHARGE_CURRENCY

Advised Charge Currency

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CHARGE_REFUND_INDICATOR

Charge Refund Indicator

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.COMMISSION

Commission

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_CHARGING_POINT

Content Charging Point

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_CODE

Content Transaction Code

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.CONTENT_TRANSACTION_TYPE

Content Transaction Type

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_INCOMING

Data Volume Incoming

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.DATA_VOLUME_OUTGOING

Data Volume Outgoing

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.OBJECT_TYPE

Object Type

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAID_INDICATOR

Paid Indicator

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.PAYMENT_METHOD

Payment Method

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TOTAL_DATA_VOLUME

Total Data Volume

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_AUTH_CODE

Transaction Authorization Code

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DESCRIPTION_SUPP

Transaction Description Suppression

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_DETAIL_DESCRIPTION

Transaction Detail Description

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_IDENTIFIER

Transaction Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVICE_USED_LIST.TRANSACTION_SHORT_DESCRIPTION

Transaction Short Description

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO

Serving Parties Information

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST

Internet Service Provider

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.IDENTIFIER

ISP Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.ISP_LIST.TYPE

ISP Id Type

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST

Network

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.IDENTIFIER

Serving Parties Info Block:

  • Network Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.NETWORK_LIST.TYPE

Serving Parties Info Block:

  • Network Id Type

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST

Content Provider

This is a block.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.IDENTIFIER

Content Provider Block:

  • Content Provider Identifier

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_LIST.TYPE

Content Provider Block:

  • Content Provider Id Type

No comment.

DETAIL.ASS_CONT_EXT.SERVING_PARTIES_INFO.PROVIDER_NAME

Content Provider Name

No comment.

DETAIL.ASS_CONT_EXT.TOTAL_TRANSACTION_DURATION

Total Transaction Duration

No comment.

DETAIL.ASS_CONT_EXT.TRANSACTION_STATUS

Transaction Status

No comment.

DETAIL.ASS_GPRS_EXT.A_NUMBER_USER

MSISDN

No comment.

DETAIL.ASS_GPRS_EXT.APN_ADDRESS

GPRS Destination Group:

  • Access Point Name NI if Camel option is not set.

  • Access Point Name OI if Camel option is not set.

The EDR field contains concatenated and comma-separated values of Access Point Name NI and Access Point Name OI.

DETAIL.ASS_GPRS_EXT.CELL_ID

Cell Identity

No comment.

DETAIL.ASS_GPRS_EXT.CHARGING_ID

Charging ID

No comment.

DETAIL.ASS_GPRS_EXT.DEVICE_NUMBER

IMEI

No comment.

DETAIL.ASS_GPRS_EXT.GGSN_ADDRESS

Recording Entity ID

Rec Entity Code Element Group.

Recording Entity Code is used to get corresponding Recording Entity ID. The obtained Recording Entity ID is stored in the EDR field.

DETAIL.ASS_GPRS_EXT.GS_PACKET

GPRS Service Used

This is a block.

DETAIL.ASS_GPRS_EXT.GS_PACKET.CHARGING_START_TIMESTAMP

and

DETAIL.ASS_GPRS_EXT.GS_PACKET.UTC_TIME_OFFSET

Charging Timestamp

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_DELAY

QoS Requested:

  • QoS Delay

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_MEAN_THROUGHPUT

QoS Requested:

  • QoS Mean Throughput

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_PEAK_THROUGHPUT

QoS Requested:

  • QoS Peak Throughput

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_PRECEDENCE

QoS Requested:

  • QoS Precedence

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_REQUESTED_RELIABILITY

QoS Requested:

  • QoS Reliability

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_DELAY

QoS Used:

  • QoS Delay

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_MEAN_THROUGHPUT

QoS Used:

  • QoS Mean Throughput

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_PEAK_THROUGHPUT

QoS Used:

  • QoS Peak Throughput

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_PRECEDENCE

QoS Used:

  • QoS Precedence

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.QOS_USED_RELIABILITY

QoS Used:

  • QoS Reliability

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.UMTS_QOS_REQUESTED

UMTS Quality Of Service Requested

The EDR field is mapped into concatenated and comma-separated tag-value pairs in UMTS Quality Of Service Requested.

The tag values of the corresponding fields are as follows:

  • QosTrafficClassKey: 1

  • QosMaxBitRateUpLnKey: 2

  • QosMaxBitRateDownLnKey: 3

  • QosGuaranteedBitRateDownLnKey: 4

  • QosGuaranteedBitRateUpLnKey: 5

  • QosAllocRetenPriorityKey: 6

DETAIL.ASS_GPRS_EXT.GS_PACKET.UMTS_QOS_USED

UMTS Quality Of Service Used

The EDR field is mapped into concatenated and comma-separated tag-value pairs in UMTS Quality Of Service Used.

The tag values of the corresponding fields are as follows:

  • QosTrafficClassKey: 1

  • QosMaxBitRateUpLnKey: 2

  • QosMaxBitRateDownLnKey: 3

  • QosGuaranteedBitRateDownLnKey: 4

  • QosGuaranteedBitRateUpLnKey: 5

  • QosAllocRetenPriorityKey: 6

DETAIL.ASS_GPRS_EXT.GS_PACKET.UTC_TIME_OFFSET

Charging Timestamp

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.VOLUME_RECEIVED

Data Volume Incoming

No comment.

DETAIL.ASS_GPRS_EXT.GS_PACKET.VOLUME_SENT

Data Volume Outgoing

No comment.

DETAIL.ASS_GPRS_EXT.LOCATION_

AREA_INDICATOR

Location Area Code

No comment.

DETAIL.ASS_GPRS_EXT.NETWORK_INITIATED_PDP

Network Init. PDP Context

No comment.

DETAIL.ASS_GPRS_EXT.ORIGINATING_SWITCH_IDENTIFICATION

Recording Entity ID

Rec Entity Code Element.

Recording Entity Code is used to get corresponding Recording Entity ID. The Recording Entity ID is stored in the EDR field.

DETAIL.ASS_GPRS_EXT.PDP_ADDRESS

PDP Address

No comment.

DETAIL.ASS_GPRS_EXT.PDP_CONTEXT_START_TIMESTAMP

and

DETAIL.ASS_GPRS_EXT.PDP_UTC_TIME_OFFSET

PDP Context Start Timestamp

No comment.

DETAIL.ASS_GPRS_EXT.PORT_NUMBER

IMSI

No comment.

DETAIL.ASS_GPRS_EXT.SERVICE_USED_CHARGING_START_TIMESTAMP

and

DETAIL.ASS_GPRS_EXT.SERVICE_USED_UTC_TIME_OFFSET

GGPRS Service Used Block:

  • Charging Timestamp

No comment.

DETAIL.ASS_GPRS_EXT.SGSN_ADDRESS

Recording Entity ID

Rec Entity Code Element.

Recording Entity Code is used to get corresponding Recording Entity ID. Recording Entity ID is stored in the EDR field.

DETAIL.ASS_GPRS_EXT.WLAN_ADDRESS

Recording Entity ID

Rec Entity Code Element.

The Recording Entity code is used to get corresponding Recording Entity ID. The Recording Entity ID is stored in the EDR field.

DETAIL.ASS_GSMW_EXT.A_NUMBER_USER

  • MSISDN

  • Third Party Number

No comment.

DETAIL.ASS_GSMW_EXT.BASIC_DUAL_SERVICE

  • Dual Teleservice Code

  • Dual Bearer Service Code

  • The EDR field is prefixed with 0.

  • The EDR field is prefixed with 1.

DETAIL.ASS_GSMW_EXT.BS_PACKET

  • Basic Service

  • Basic Service Used

This is a block.

DETAIL.ASS_GSMW_EXT.BS_PACKET.AIUR_REQUESTED

Air Interface User Rate Requested

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.CHARGING_START_TIMESTAMP

and

DETAIL.ASS_GSMW_EXT.BS_PACKET.UTC_TIME_OFFSET

Charging Timestamp

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.FNUR

Fixed Network User Rate

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.CHANNEL_CODING_OK_LIST

Channel Coding Acceptable

The EDR field is mapped as a comma-separated list of channel coding.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.CHANNEL_CODING_USED

Channel Coding Used

The EDR field is mapped as a comma-separated list of channel coding.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.NUMBER_OF_CHANNELS

Number Of Channels

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.NUMBER_OF_CHANNELS_USED

Number Of Channels Used

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST

Basic HSCSD Parameters

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST

HSCSD Parameter Modification

This is a block.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.AIUR

Air Interface User Rate Requested

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.CHANNEL_CODING_USED

Channel Coding Used

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.INITIATING_PARTY

Initiating Party

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MAX_NUMBER_OF_CHANNELS

Number Of Channels

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.MODIFICATION_TIMESTAMP

and

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.UTC_TIME_OFFSET

Modification Timestamp

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.HSCSD_INFO_PACKET.PM_LIST.NUMBER_OF_CHANNELS_USED

Number Of Channels Used

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.QOS_REQUESTED

Radio Channel Requested

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.QOS_USED

Radio Channel Used

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.SPEECH_VERSION_REQUESTED

Speech Version Requested

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.SPEECH_VERSION_USED

Speech Version Used

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.TRANSPARENCY_INDICATOR

Transparency Indicator

No comment.

DETAIL.ASS_GSMW_EXT.BS_PACKET.USER_PROTOCOL_INDICATOR

User Protocol Indicator

No comment.

DETAIL.ASS_GSMW_EXT.CELL_ID

Cell Identity

No comment.

DETAIL.ASS_GSMW_EXT.DEVICE_NUMBER

IMEI

No comment.

DETAIL.ASS_GSMW_EXT.DIALED_DIGITS

  • Dialled Digits

  • MSISDN in MTC and SCU groups

No comment.

DETAIL.ASS_GSMW_EXT.LOCATION_AREA_INDICATOR

Location Area Code

No comment.

DETAIL.ASS_GSMW_EXT.MS_CLASS_MARK

Mobile Station Classmark

No comment.

DETAIL.ASS_GSMW_EXT.NUMBER_OF_SS_PACKETS

  • Number of Supplementary Service Used blocks

  • Number of Supplementary Service Used Event blocks

No comment.

DETAIL.ASS_GSMW_EXT.ORIGINATING_SWITCH_IDENTIFICATION

  • Location Information

  • Recording Entity ID

No comment.

DETAIL.ASS_GSMW_EXT.PORT_NUMBER

IMSI

No comment.

DETAIL.ASS_GSMW_EXT.SERVING_NETWORK

Serving Network

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET

Supplementary Service Used

This is a block.

DETAIL.ASS_GSMW_EXT.SS_PACKET.ACTION_CODE

Action Code

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.BASIC_SERVICE_CODE_LIST

Basic Service Code SS

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.CLIR_INDICATOR

CLIR Status Indicator

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_EVENT

Supplementary Service Code

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.SS_PARAMETERS

Supplementary Service Parameters

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.THIRD_PARTY_NUMBER

Third Party Number

No comment.

DETAIL.ASS_GSMW_EXT.SS_PACKET.UTC_TIME_OFFSET

UTC Time Offset

No comment.

DETAIL.ASS_LOCN_EXT.CALL_REFERENCE

Call Reference

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO

LCS SP Information

This is a block.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST

LCS SP Identification

This is a block.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.IDENTIFIER

LCS SP Identification:

  • Content Provider Identifier

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ID_LIST.TYPE

LCS SP Identification:

  • Content Provider Id Type

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST

Internet Service Provider

This is a block.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.IDENTIFIER

LCS SP Information:

  • ISP Identifier

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.ISP_LIST.TYPE

LCS SP Information:

  • ISP Id Type

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.NETWORK_LIST.IDENTIFIER

LCS SP Information:

  • Network Identifier

No comment.

DETAIL.ASS_LOCN_EXT.LCSSP_INFO.NETWORK_LIST.TYPE

LCS SP Information:

  • Network Id Type

No comment.

DETAIL.ASS_LOCN_EXT.REC_ENTITY_CODE

Location Service:

  • Recording Entity Code

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE

Location Service Usage

This is a block.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.AGE_OF_LOCATION

Age Of Location

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_FREQUENCY

Tracking Frequency

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.DEL_TRACKING_PERIOD

Tracking Period

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_DELIVERED

Horizontal Accuracy Delivered

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.H_ACCURACY_REQUESTED

Horizontal Accuracy Requested

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_REQUEST_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

LCS Request Timestamp

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.LCS_TRANS_STATUS

LCS Transaction Status

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.POSITIONING_METHOD

Positioning Method

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.REQ_TRACKING_FREQUENCY

Tracking Frequency

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME

Response Time

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.RESPONSE_TIME_CATEGORY

Response Time Category

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_

USAGE.TRACKING_PERIOD

Tracking Period

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_DELIVERED

Vertical Accuracy Delivered

No comment.

DETAIL.ASS_LOCN_EXT.SERVICE_USAGE.V_ACCURACY_REQUESTED

Vertical Accuracy Requested

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO

Tracked Customer Information

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT

Tracked Customer Equipment

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.IDENTIFIER

Tracked Customer Equipment:

  • Equipment Id

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.EQUIPMENT.TYPE

Tracked Customer Equipment:

  • Equipment Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST

Tracked Customer Home Id

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Tracked Customer Home Id:

  • Home Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.HOME_ID_LIST.TYPE

Tracked Customer Home Id:

  • Home Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST

Tracked Customer Identification

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.IDENTIFIER

Tracked Customer Identification:

  • Customer Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.ID_LIST.TYPE

Tracked Customer Identification:

  • Customer Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST

Tracked Customer Location

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.IDENTIFIER

Tracked Customer Location:

  • Location Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKED_CUST_INFO.LOCATION_LIST.TYPE

Tracked Customer Location:

  • Location Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO

Tracking Customer Information

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT

Tracking Customer Equipment

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.IDENTIFIER

Tracking Customer Equipment:

  • Equipment Id

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.EQUIPMENT.TYPE

Tracking Customer Equipment:

  • Equipment Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST

Tracking Customer Home Id

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.IDENTIFIER

Tracking Customer Home Id:

  • Home Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.HOME_ID_LIST.TYPE

Tracking Customer Home Id:

  • Home Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST

Tracking Customer Identification

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.IDENTIFIER

Tracking Customer Identification:

  • Customer Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.ID_LIST.TYPE

Tracking Customer Identification:

  • Customer Id Type

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST

Tracking Customer Location

This is a block.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.IDENTIFIER

Tracking Customer Location:

  • Location Identifier

No comment.

DETAIL.ASS_LOCN_EXT.TRACKING_CUST_INFO.LOCATION_LIST.TYPE

Tracking Customer Location:

  • Location Id Type

No comment.

DETAIL.ASS_VAS_EXT

Value Added Service Used

This is a block.

DETAIL.ASS_VAS_EXT.UTC_TIME_OFFSET

UTC Time Offset

No comment.

DETAIL.ASS_VAS_EXT.VAS_CODE

VAS Code

No comment.

DETAIL.ASS_VAS_EXT.VAS_DESC

VAS Description

No comment.

DETAIL.ASS_VAS_EXT.VAS_SHORT_DESC

VAS Short Description

No comment.

DETAIL.B_NUMBER

  • Called Number

  • Calling Number

  • Non Charged Number

International Access Code prefixes the EDR field.

DETAIL.BASIC_SERVICE

  • TeleService Code

  • Bearer Service Code

No comment.

DETAIL.C_NUMBER

  • Third Party Number

  • Dialled Digits

No comment.

DETAIL.CALL_COMPLETION_

INDICATOR

  • Cause For Termination

  • Message Status

The EDR field is mapped to different TAP fields:

  • Service Center Usage Group. The EDR field is mapped to Message Status. If the value is less than 10, it is prefixed with 0.

  • GPRS/Mobile Originated/ Mobile Terminated Group. The EDR field is mapped to Cause for Termination. If the value is less than 10, it is prefixed with 0.

DETAIL.CALLED_COUNTRY_CODE

Called Country Code

-

DETAIL.CHARGING_END_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

  • Completion Timestamp

  • Call Event Start Time Stamp

  • Charging Time Stamp (MSS, SCU, and VAS)

When the EDR is mapped to Completion Timestamp, the DETAIL.UTC_TIME_OFFSET part is not stored.

DETAIL.CHARGING_START_TIMESTAMP

and

DETAIL.UTC_TIME_OFFSET

  • Deposit Timestamp

  • Charging Timestamp

  • Call Event Start Timestamp

No comment.

DETAIL.CONNECT_SUB_TYPE

Call Type Level 3

No comment.

DETAIL.CONNECT_TYPE

  • Call Type Level 1

  • Call Type Level 2

Contents of the EDR field are mapped as concatenated items to Call Type Level 1 and Call Type Level 2.

DETAIL.DESCRIPTION

  • Called Place

  • Called Region

  • Message Description Code

Destination:

  • Contents of the EDR field are mapped as concatenated comma-separated values into Called Place and Called Region.

SCU Charge Type:

  • The EDR field mapped to Message Description corresponds to the Message Description Code present in SCU Charge Type.

DETAIL.DESTINATION_NETWORK

Destination Network

No comment.

DETAIL.DISCOUNT_KEY

SIM Toolkit Indicator

No comment.

DETAIL.DURATION

Total Call Event Duration

No comment.

DETAIL.FRAUD_MONITOR_INDICATOR

Fraud Monitor Indicator

No comment.

DETAIL.GEOGRAPHICAL_LOCATION

Geographical Location

Contents of the EDR field are mapped as comma-separated tag-value pairs.

The tag values of the corresponding fields are as follows:

  • ServingNetwork: 1

  • ServingBID: 2

  • ServingLocationDescription: 3

  • Longitude: 4

  • Latitude: 5

DETAIL.INTERN_A_NUMBER_ZONE

MSISDN

No comment.

DETAIL.LONG_DURATION_INDICATOR

Partial Type Indicator

No comment.

DETAIL.OPERATOR_SPECIFIC_INFO

Operator Specific Information

No comment.

DETAIL.QOS_REQUESTED

  • Priority Code

  • Radio Channel Requested

No comment.

DETAIL.QOS_USED

  • Message Type

  • Radio Channel Used

No comment.

DETAIL.RAP_FILE_SEQ_NO

RAP File Sequence Number

No comment.

DETAIL.SOURCE_NETWORK

Originating Network

No comment.

DETAIL.SOURCE_NETWORK_TYPE

Network Type

No comment.

DETAIL.USAGE_CLASS

GPRS Chargeable Subscriber:

  • Charging Characteristics

SCU Basic Information, Call Originator:

  • CLIR Status Indicator

No comment.

DETAIL.USAGE_DIRECTION

Charged Party Status

No comment.

DETAIL.UTC_TIME_OFFSET

  • Charging Timestamp

  • LCS Request Timestamp

  • Actual Delivery Timestamp

  • Requested Delivery Timestamp

  • Order Placed Timestamp

  • Completion Timestamp

  • Deposit Timestamp

  • Call Event Start Timestamp

No comment.

DETAIL.VOLUME_RECEIVED

Data Volume Incoming

No comment.

DETAIL.VOLUME_SENT

Data Volume Outgoing

No comment.

DETAIL.WHOLESALE_CHARGED_TAX_RATE

Tax Rate Code

No comment.

DETAIL.WHOLESALE_CHARGED_TAX_VALUE

Tax Value

No comment.

DETAIL.ZONE_DESCRIPTION

Distance Charge Band Code

No comment.

HEADER.CREATION_TIMESTAMP

and

HEADER.UTC_TIME_OFFSET

File Creation Timestamp

No comment.

HEADER.DATA_TYPE_INDICATOR

File Type Indicator

No comment.

HEADER.OPERATOR_SPECIFIC_INFO

Operator Specific Information

No comment.

HEADER.RAP_FILE_SEQ_NO

RAP File Sequence Number

No comment.

HEADER.RECIPIENT

Recipient

No comment.

HEADER.RELEASE_VERSION

Release Version Number

No comment.

HEADER.SENDER

Sender

No comment.

HEADER.SEQUENCE_NUMBER

File Sequence Number

No comment.

HEADER.SPECIFICATION_VERSION_NUMBER

Specification Version Number

No comment.

HEADER.TAP_DECIMAL_PLACES

TAP Decimal Places

No comment.

HEADER.TRANSFER_CUTOFF_TIMESTAMP

and

HEADER.UTC_TIME_OFFSET

Transfer Cut Off Timestamp

No comment.

HEADER.TRANSMISSION_DATE

and

HEADER.UTC_TIME_OFFSET

File Available Timestamp

No comment.

TRAILER.LAST_START_TIMESTAMP

and

TRAILER.LAST_CHARGING_UTC_TIME_OFFSET

Latest Call Timestamp

No comment.

TRAILER.OPERATOR_SPECIFIC_INFO

Operator Specific Information

No comment.

TRAILER.TAP_TOTAL_DISCOUNT_VALUE

Total Discount Value

No comment.

TRAILER.TAP_TOTAL_NUMBER_OF_RECORDS

Call Event Details Count

No comment.

TRAILER.TAP_TOTAL_TAX_VALUE

Total Tax Value

No comment.

TRAILER.TOTAL_CHARGE_VALUE_LIST.CHARGE_TYPE

Charge Type

No comment.

TRAILER.TOTAL_CHARGE_VALUE_LIST.TOTAL_CHARGE_REFUND

Total Charge Refund

No comment.


PKZ R/PKSqEOEBPS/rmg_int_install.htmx Installing InterConnect Manager

16 Installing InterConnect Manager

This chapter describes how to install Interconnect Manager.


Important:

  • Before you install Interconnect Manager, you must install Pipeline Manager, Version 7.4. See "Installing Pipeline Manager" in BRM Installation Guide.

  • If you are installing Interconnect Manager to replace an identical release (for example, to restore a clean version of the package), you must first uninstall the existing installation. See "Uninstalling Interconnect Manager".


Installing Interconnect Manager

To install InterConnect Manager:

  1. If the Third-Party software package is not installed already, install it. See "Installing the Third-Party Software" in BRM Installation Guide.

  2. Go to the directory where you installed the Third-Party package and source the source.me:

    source source.me.sh
    

    C shell:

    source source.me.csh
    
  3. Download the InterConnect Manager software to a temporary directory (temp_dir).


    Note:

    You must increase the heap size used by the Java Virtual Machine (JVM) before running the installation program to avoid “Out of Memory” error messages in the log file. For information, see "Increasing Heap Size to Avoid “Out of Memory” Error Messages" in BRM Installation Guide.

  4. Go to temp_dir and run the installation program.

    To enable a graphical user interface (GUI) installation, install a GUI application such as X Windows and set the DISPLAY environment variable before you install the patch.

    7.4_Interconnect_platform_64_opt.bin -console
    
  5. Follow the instructions displayed during installation.


    Note:

    If you do not specify an installation directory, Interconnect Manager is installed in the /opt/ifw directory.

Uninstalling Interconnect Manager

To uninstall Interconnect Manager, run the uninstaller.bin from Pipeline_home/uninstaller/Interconnect.

PKa}xPKSqEOEBPS/content.opf1 Oracle® Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4 en-US E25100-01 Oracle Corporation Oracle Corporation Oracle® Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4 2013-03-18T08:21:07Z Oracle® Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager, Release 7.4 PK>Ý 61PKSqEOEBPS/dcommon/oracle-logo.jpgg3JFIFC    $.' ",#(7),01444'9=82<.342C  2!!22222222222222222222222222222222222222222222222222'7" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ?( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQE!KEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEzE7V%ȣOΏ9??:a"\fSrğjAsKJ:nOzO=}E1-I)3(QEQEQEQEQEQEQE֝Hza<["2"pO#f8M[RL(,?g93QSZ uy"lx4h`O!LŏʨXZvq& c՚]+: ǵ@+J]tQ]~[[eϸ (]6A&>ܫ~+כzmZ^(<57KsHf妬Ϧmnẁ&F!:-`b\/(tF*Bֳ ~V{WxxfCnMvF=;5_,6%S>}cQQjsOO5=)Ot [W9 /{^tyNg#ЄGsֿ1-4ooTZ?K Gc+oyڙoNuh^iSo5{\ܹ3Yos}$.nQ-~n,-zr~-|K4R"8a{]^;I<ȤL5"EԤP7_j>OoK;*U.at*K[fym3ii^#wcC'IIkIp$󿉵|CtĈpW¹l{9>⪦׺*ͯj.LfGߍԁw] |WW18>w.ӯ! VӃ :#1~ +މ=;5c__b@W@ +^]ևՃ7 n&g2I8Lw7uҭ$"&"b eZ":8)D'%{}5{; w]iu;_dLʳ4R-,2H6>½HLKܹR ~foZKZ࿷1[oZ7׫Z7R¢?«'y?A}C_iG5s_~^ J5?œ tp]X/c'r%eܺA|4ծ-Ե+ْe1M38Ǯ `|Kյ OVڅu;"d56, X5kYR<̭CiطXԮ];Oy)OcWj֩}=܅s۸QZ*<~%뺃ȶp f~Bðzb\ݳzW*y{=[ C/Ak oXCkt_s}{'y?AmCjޓ{ WRV7r. g~Q"7&͹+c<=,dJ1V߁=T)TR՜*N4 ^Bڥ%B+=@fE5ka}ędܤFH^i1k\Sgdk> ֤aOM\_\T)8靠㡮3ģR: jj,pk/K!t,=ϯZ6(((((((49 xn_kLk&f9sK`zx{{y8H 8b4>ÇНE|7v(z/]k7IxM}8!ycZRQ pKVr(RPEr?^}'ðh{x+ՀLW154cK@Ng C)rr9+c:׹b Жf*s^ fKS7^} *{zq_@8# pF~ [VPe(nw0MW=3#kȵz晨cy PpG#W:%drMh]3HH<\]ԁ|_W HHҡb}P>k {ZErxMX@8C&qskLۙOnO^sCk7ql2XCw5VG.S~H8=(s1~cV5z %v|U2QF=NoW]ո?<`~׮}=ӬfԵ,=;"~Iy7K#g{ñJ?5$y` zz@-~m7mG宝Gٱ>G&K#]؃y1$$t>wqjstX.b̐{Wej)Dxfc:8)=$y|L`xV8ߙ~E)HkwW$J0uʟk>6Sgp~;4֌W+חc"=|ř9bc5> *rg {~cj1rnI#G|8v4wĿhFb><^ pJLm[Dl1;Vx5IZ:1*p)إ1ZbAK(1ׅ|S&5{^ KG^5r>;X׻K^? s fk^8O/"J)3K]N)iL?5!ƾq:G_=X- i,vi2N3 |03Qas ! 7}kZU781M,->e;@Qz T(GK(ah(((((((Y[×j2F}o־oYYq $+]%$ v^rϭ`nax,ZEuWSܽ,g%~"MrsrY~Ҿ"Fت;8{ѰxYEfP^;WPwqbB:c?zp<7;SBfZ)dϛ; 7s^>}⍱x?Bix^#hf,*P9S{w[]GF?1Z_nG~]kk)9Sc5Ո<<6J-ϛ}xUi>ux#ţc'{ᛲq?Oo?x&mѱ'#^t)ϲbb0 F«kIVmVsv@}kҡ!ˍUTtxO̧]ORb|2yԵk܊{sPIc_?ħ:Ig)=Z~' "\M2VSSMyLsl⺿U~"C7\hz_ Rs$~? TAi<lO*>U}+'f>7_K N s8g1^CeКÿE ;{+Y\ O5|Y{/o+ LVcO;7Zx-Ek&dpzbӱ+TaB0gNy׭ 3^c T\$⫫?F33?t._Q~Nln:U/Ceb1-im WʸQM+VpafR3d׫é|Aү-q*I P7:y&]hX^Fbtpܩ?|Wu󭏤ʫxJ3ߴm"(uqA}j.+?S wV ~ [B&<^U?rϜ_OH\'.;|.%pw/ZZG'1j(#0UT` Wzw}>_*9m>󑓀F?EL3"zpubzΕ$+0܉&3zڶ+jyr1QE ( ( ( ( ( ( ( (UIdC0EZm+]Y6^![ ԯsmܶ捆?+me+ZE29)B[;я*wGxsK7;5w)}gH~.Ɣx?X\ߚ}A@tQ(:ͧ|Iq(CT?v[sKG+*רqҍck <#Ljα5݈`8cXP6T5i.K!xX*p&ќZǓϘ7 *oƽ:wlຈ:Q5yIEA/2*2jAҐe}k%K$N9R2?7ýKMV!{W9\PA+c4w` Wx=Ze\X{}yXI Ү!aOÎ{]Qx)#D@9E:*NJ}b|Z>_k7:d$z >&Vv󃏽WlR:RqJfGإd9Tm(ҝEtO}1O[xxEYt8,3v bFF )ǙrPNE8=O#V*Cc𹾾&l&cmCh<.P{ʦ&ۣY+Gxs~k5$> ӥPquŽўZt~Tl>Q.g> %k#ú:Kn'&{[yWQGqF}AЅ׮/}<;VYZa$wQg!$;_ $NKS}“_{MY|w7G!"\JtRy+贾d|o/;5jz_6fHwk<ѰJ#]kAȎ J =YNu%dxRwwbEQEQEQEQEQEQEQEQEQE'fLQZ(1F)hQ@X1KEQE-Q@ 1KE3h=iPb(((1GjZ(-ʹRPbR@ 1KE7`bڒyS0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((( g\==oNYdp+@jhs2X".]q8mQ\V_ Ehl%d24O@@^2QҬudKhCrnWS0H9Ey?H@2pX9[RFѯKEQK2@IԡtkRdX/m㸍d0WP3k|]1U@dPRY"Pp2H8;DzD<?;ۿb1@}gYywx4r@c ~5ChڥY[q"b gW_5h^Wwgy@\+#nܜ]*ǃ|M^->Y:+F8\i::΍c[w Fp}M\3Լg!?G9Qk$hڱ@D($P1׃jx%`]f;KXbv pé#pLx^JfbKXYPCaݎ6?G4me#ֵO IU¾/P0qJ+/x]/S?t9绗̗â4)%܈ Q`?[k:{6}g۹CU<x5xHN}ݡr*èe` =3_^HuW wqZ G7M*{ yYd^]P3uƺm֍-Q h76JȻ]StƺmQ0k]_u>ٮN=oQ|MѸw[!HU 'YτQH/Em_yxs=w\hg#m6/lݻ=|ykM.On--jO>?H@2pX9J+w}wXwZdn m[Qq;Ex:skzlbIMC-n=rƧO2OghԱdҹWg|bo'],Yᗏ5^vi}Q,ͣhղ &s\x+_iv~qio(Ry!VrB$U=[RFѯKEQK2@?~#_i cVjM6nFD2YxHcⅿ_Tu}6L/tch;s+΋ى{ n'RYѬuKu`5]CpHþ/?os$wSn^xI熿k'?`Ѭ!f|‹Fq`h׏/-Z;@Fcxi8FqJ?ZO|hi<=i;ލMV UF b6IBF-sy|-Mr,ڦгHΛ8cxǨW;Wu ][twiqHhĊY6nN+S>-s>#8 -rE$8\;6ّq;J+Ϗ6=^(ujm2cJc̿M]#>Xh4g1@Exyt9A7Ŀ OOr|<T1X&C:Ȱ^q`8$g( ( ( ( ( ( ( ( ( (8xo]D~-5وCis=B4  Vn!A Xj>ֵkk D%;ƒ5  3xUG͊(3񇁼KO&?hėlQKiro;aAFLđY:kՊ!t%9 6 oL8MGgؼ6߽sz?5Sg#b7ۻ;~=밢%|}ekΙun7#{;prEyޅ\m,lЅIot&1?%Wn0' Q?(ѷ~ [|/kpN3Š}7Ϳ~"XKgW5)SC椱p?;Լ!CG8%gt];KeRv0''AOL8蚍j6,u/]|.9'_L5xV?̖I# w@<GJ(״O8["yBא\\[d0(c E{%P9Z[\pxl#:wjxkEl4`ӭئEwAFF8*s__r^_ik7<4\X2HWt{U#}gكmpoDm֯jSXIc3rw;u֑i_'H"CzEbj??G_h߷nw}s{ Q?(ѷ~ [|/kpN3Š;zoek!F[#h۞r1\=½P{ xVCo"S|m 6G8#H '?xkV)knA|id|2ʰ%K?1SpHq+P_E|O[;H-'ͽv+\ʌ cgbX04MGDFw.mumݭ8ڻ (~񾃬y k7#$-9Sk?Vu_xrmM B2cR9m|!#oQ@<^GZ̛zV?MF?kk}:o۾._Tz(?&xA->_"uCug'&IP̧(9< SK|iw7DҼI HNށQ ]H^X7\P8?X3\OF ndg)+ ԔC\ߍ-OZ/?nѬD>P,1'*$ҽxmm常8` $Q@$/_ -1Z%MJY cSck gŸhU[}wO7yyqֽr ặXTeu# 8 sRP?K?}~ݹy1G& ,^~]vw8ǽvP>4ou]7֓m[SlҜ:Ȥ1`_y'jо]˰5֌$NLnvoOlzJcgyawݬ4 H8a~phZo kwY5I`xSA & tk{!+xHԬ@"0yzbQ@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@^_?QfyߜeB8CxVOh~啴KNxdK`HR8aN37 r?_ /;-!k%lӴK._q  u /NwgO]/@@i]TxU oZ͖xvfKԻC9`ws}:`1_?hо w|ݹ9wVe^xD0vn5cms g'Jx^×zܺaD2}/ I'oq뗾)=n!r(%y" pGH`p*p*IxϦ;EKcI ;qiV92&2~1+ɒ<\5QxJk}Ixv~AL+K/x:Huƍj5ם"lpr܎=2pA|`|5X}`lGG'YX.X/!Jp XvV2j  M23.ywl< W'QѼW׾oe;izXh~nx>&藐xO4ky{NR{M$I0s(`A޹?Ϡwc#衁  p%~> w\i>0_;O8ė$[DƻT8gο5ĽO_+RWh$x?-lh4W>"4]aRk2tg `d ʌ:}W'o_xLX]H9I!} @H!6|A?5$Ƙ^M?>ppx'%@C<5egϬGYYA²,('$W}ic7~ iWŲJ=ÕoܐAR2q]WpG⅝Z @8z74Oj3x7ב4+uK+3NWh~&x-%ĖC]|:a?|[KRq2%X<>ƀ=r=5(x[:ºE鉤#C)I̡P.Wǩ?kcVWW}M5hi;G0UT;l4O7u/4g#;eycMh`v0r{x,ˁr00TƉFVcs^,Ovi,]Ff…K:wIE=y65բ`02I_H;v->xHB,5I:;:!Gᶲ5OQok Դ JjSOKuᤷM̀1-qz旪XegU[F}K<8Wa<{ow:$3 G/mi=B-I0! [8k;_eWxM$<I7W85H4Ҟ$?k!efmF>VB1t_J=KjIeis~:TJgZ Zms˽5{-nФ ( ۺO1?Ǜm#'vzfš#~OO͟/\Ïi-(K6 K9/`*AV1C?@qk:/Kw ݡ7R2-d8'Z<ֺanUBFd`(q]xW_)' +@"@<\awmf1KsFnB0Tv1cP3$\<υ7 aT7YS ~OỎ [ ޻@_Jf}'HFhFVG.L7MѯZD.V1dPI .6kV.NKE Hw SA-i{K[Bf7>nn'Q'! v ?ud>%zwZ";D'.8 u'ij^1ӼQ\զ' kiu2B[= ?udGykº^x<%YSk} yK IT$fFBq"@w^YY*E( 2adn ckK~x #|DJ ,_.E A:k_ċ⏏7X]Y vћЌ&U X I+Oi0n߶3rc?e$Kr=+??j?= cZ^5mJii`4鹐899qD?$]( ( ( ( ( ( ( ( ( ( ( +IuO~Mj cw?c?G~9ּGaMP5}J(||݅des(KwWmI~k'Va߿W w˙FP~=*|u;ZM+cѻl$u:+/_m--j;K@7,Y@=N<zT7 xܑ8hc-m0g4V~>:hP[jCk`J8` 99? 7ݺ[k1޳U9)ı㹠n6ŭu lz+Lx#?!/W/E>p\߮F>߽ N@$p3WV~8 c|SNI]E}!Ds.pr~\; +UViZ osѻ8,p @'qGx@M&8K6$b`v*HPWP%4 s#WtdTjxpG^ n96.Dd1ˑ'< 3oy{jj> eԯe*"($ */G5r ~\&%B@C)G'9x^ԣIܤ@;9' 2q(r/ٛS5 Ir2i@28o>5M/T5 %p=ňUNY :Q\~O:v>$HTȪ# 9>sľ>. uhg m$"r8:+$>8]F9-u[}V9G>NzlkS@-u-;B7*UP=zXv?k֚I)5dad+ #Ƞ! JY?Ezvaoko"( H}3v_h}{R'r *p8G<= vfCཌྷ~BCǒ@܇ q3(b5{m'T˾}]/ sڼ|=xLHA& Ish(f~-m"i_諒bp$@W4]?.~"[G`2G%>@Q@Q@!1k ^ <w`ST! JY?Ezvaoko"( H}3vPEPEPEPEPEPEPEPEPEPEPEPEPNu?áطKq4ܟi 8${Y6ϯ޵\[WV( ۂGIF7bio&d߷nvsօ|6 6_'nky{?ߝuXX5N{H7V>J܃ᗂ|AoHop{4`0מ#}O?vy>}ŲK=Cuxb IJLݫ#;x\j5KdAV8a3=ᧃ/.xQei=vbК'+Qn|)9SHPa +!ojYk\(ć9w&qi%k\yOg9`{9* \xᢌΞ(DܪŋzJ#\ eai?O<ϳl~?U4o_6wn㽷vLdr=|+xZd.xA;\a;FpFqr~Uk[ׇ{0m4%S;G"bgG1U}pGzI$2<b@ A[6sayku2n#r0!G#  |)WO}4 ljH NAR=|-*amfeiM snJK }3N˵!7'ZwiƝ\|߲K.Aj;]KĞ*nt׶%I ck\Lύq#2qa?!{`Fe_.Folzf:֩As~3#3~+09\~ږeoO+[ 0(3Hgs㟶7|nÕ}>o/s8$ xr#5y>#s a [.d$3FAll@~wB}?w&lXfx鷌T`{ E9Q;iBN:#>]|.׈oM ä[EZE] 09,N@O CIfbIOy׶g kwpj{|KpΌC~m_mێ  !y$($s?@^.Y7YD"39c$I$Տ ~H[-2+7HnM˜n(B ặXTeu# 8 s^g#J;wMTɈQVqMzE[XYЛڊQW4cNծmio%k@ ytZYmNuIY7db p%@qlCX$ٿ(yf{iZVtqʓU7E9WGRz:UC] vb\ ~pCǒ 33(_:߈? i*9:8ݓ;ך]yڿ']^9>lWk>I$2<b@ AZ_4XƺZ٤&U*y$Xsր<^ e]ZIqV<2I*(IjjICX4 rVy;:#O1G ;o'9Ǘf6c/|/.5&;B$xi9(q<սO,n";ZcG Y -h\>Woj5 A}1.&3"6_XFXİM7Rm?GMM/!DRP<kJM}TԬ4<nkArpz4H?>P>ͳw:b7d2xºŮA{$sggtVc&I*kz&=}'VE|ȷn*Ax5@?-_W[ _c|r}my}7~y`MN5Ze}]|-v`p{օQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEPKzggPKSqEOEBPS/dcommon/cpyr.htmD Oracle Legal Notices

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Oracle Logo

PK0hPKSqEOEBPS/dcommon/oracle.gifJGIF87aiyDT2F'G;Q_oKTC[ 3-Bq{ttsoGc4I)GvmLZ).1)!ꑈ53=Z]'yuLG*)g^!8C?-6(29K"Ĩ0Яl;U+K9^u2,@@ (\Ȱ Ë $P`lj 8x I$4H *(@͉0dа8tA  DсSP v"TUH PhP"Y1bxDǕ̧_=$I /& .)+ 60D)bB~=0#'& *D+l1MG CL1&+D`.1qVG ( "D2QL,p.;u. |r$p+5qBNl<TzB"\9e0u )@D,¹ 2@C~KU 'L6a9 /;<`P!D#Tal6XTYhn[p]݅ 7}B a&AƮe{EɲƮiEp#G}D#xTIzGFǂEc^q}) Y# (tۮNeGL*@/%UB:&k0{ &SdDnBQ^("@q #` @1B4i@ aNȅ@[\B >e007V[N(vpyFe Gb/&|aHZj@""~ӎ)t ? $ EQ.սJ$C,l]A `8A o B C?8cyA @Nz|`:`~7-G|yQ AqA6OzPbZ`>~#8=./edGA2nrBYR@ W h'j4p'!k 00 MT RNF6̙ m` (7%ꑀ;PKl-OJPKSqEOEBPS/dcommon/doccd_epub.jsM /* Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2012.3.17 */ function addLoadEvent(func) { var oldOnload = window.onload; if (typeof(window.onload) != "function") window.onload = func; else window.onload = function() { oldOnload(); func(); } } function compactLists() { var lists = []; var ul = document.getElementsByTagName("ul"); for (var i = 0; i < ul.length; i++) lists.push(ul[i]); var ol = document.getElementsByTagName("ol"); for (var i = 0; i < ol.length; i++) lists.push(ol[i]); for (var i = 0; i < lists.length; i++) { var collapsible = true, c = []; var li = lists[i].getElementsByTagName("li"); for (var j = 0; j < li.length; j++) { var p = li[j].getElementsByTagName("p"); if (p.length > 1) collapsible = false; for (var k = 0; k < p.length; k++) { if ( getTextContent(p[k]).split(" ").length > 12 ) collapsible = false; c.push(p[k]); } } if (collapsible) { for (var j = 0; j < c.length; j++) { c[j].style.margin = "0"; } } } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(compactLists); function processIndex() { try { if (!/\/index.htm(?:|#.*)$/.test(window.location.href)) return false; } catch(e) {} var shortcut = []; lastPrefix = ""; var dd = document.getElementsByTagName("dd"); for (var i = 0; i < dd.length; i++) { if (dd[i].className != 'l1ix') continue; var prefix = getTextContent(dd[i]).substring(0, 2).toUpperCase(); if (!prefix.match(/^([A-Z0-9]{2})/)) continue; if (prefix == lastPrefix) continue; dd[i].id = prefix; var s = document.createElement("a"); s.href = "#" + prefix; s.appendChild(document.createTextNode(prefix)); shortcut.push(s); lastPrefix = prefix; } var h2 = document.getElementsByTagName("h2"); for (var i = 0; i < h2.length; i++) { var nav = document.createElement("div"); nav.style.position = "relative"; nav.style.top = "-1.5ex"; nav.style.left = "1.5em"; nav.style.width = "90%"; while (shortcut[0] && shortcut[0].toString().charAt(shortcut[0].toString().length - 2) == getTextContent(h2[i])) { nav.appendChild(shortcut.shift()); nav.appendChild(document.createTextNode("\u00A0 ")); } h2[i].parentNode.insertBefore(nav, h2[i].nextSibling); } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(processIndex); PKo"nR M PKSqEOEBPS/dcommon/blafdoc.cssc@charset "utf-8"; /* Copyright 2002, 2011, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2011.10.7 */ body { font-family: Tahoma, sans-serif; /* line-height: 125%; */ color: black; background-color: white; font-size: small; } * html body { /* http://www.info.com.ph/~etan/w3pantheon/style/modifiedsbmh.html */ font-size: x-small; /* for IE5.x/win */ f\ont-size: small; /* for other IE versions */ } h1 { font-size: 165%; font-weight: bold; border-bottom: 1px solid #ddd; width: 100%; text-align: left; } h2 { font-size: 152%; font-weight: bold; text-align: left; } h3 { font-size: 139%; font-weight: bold; text-align: left; } h4 { font-size: 126%; font-weight: bold; text-align: left; } h5 { font-size: 113%; font-weight: bold; display: inline; text-align: left; } h6 { font-size: 100%; font-weight: bold; font-style: italic; display: inline; text-align: left; } a:link { color: #039; background: inherit; } a:visited { color: #72007C; background: inherit; } a:hover { text-decoration: underline; } a img, img[usemap] { border-style: none; } code, pre, samp, tt { font-family: monospace; font-size: 110%; } caption { text-align: center; font-weight: bold; width: auto; } dt { font-weight: bold; } table { font-size: small; /* for ICEBrowser */ } td { vertical-align: top; } th { font-weight: bold; text-align: left; vertical-align: bottom; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } li { text-align: left; } dd { text-align: left; } td p:first-child, td pre:first-child { margin-top: 0px; margin-bottom: 0px; } table.table-border { border-collapse: collapse; border-top: 1px solid #ccc; border-left: 1px solid #ccc; } table.table-border th { padding: 0.5ex 0.25em; color: black; background-color: #f7f7ea; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } table.table-border td { padding: 0.5ex 0.25em; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } span.gui-object, span.gui-object-action { font-weight: bold; } span.gui-object-title { } p.horizontal-rule { width: 100%; border: solid #cc9; border-width: 0px 0px 1px 0px; margin-bottom: 4ex; } div.zz-skip-header { display: none; } td.zz-nav-header-cell { text-align: left; font-size: 95%; width: 99%; color: black; background: inherit; font-weight: normal; vertical-align: top; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-header-link { font-size: 95%; } td.zz-nav-button-cell { white-space: nowrap; text-align: center; width: 1%; vertical-align: top; padding-left: 4px; padding-right: 4px; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-button-link { font-size: 90%; } div.zz-nav-footer-menu { width: 100%; text-align: center; margin-top: 2ex; margin-bottom: 4ex; } p.zz-legal-notice, a.zz-legal-notice-link { font-size: 85%; /* display: none; */ /* Uncomment to hide legal notice */ } /*************************************/ /* Begin DARB Formats */ /*************************************/ .bold, .codeinlinebold, .syntaxinlinebold, .term, .glossterm, .seghead, .glossaryterm, .keyword, .msg, .msgexplankw, .msgactionkw, .notep1, .xreftitlebold { font-weight: bold; } .italic, .codeinlineitalic, .syntaxinlineitalic, .variable, .xreftitleitalic { font-style: italic; } .bolditalic, .codeinlineboldital, .syntaxinlineboldital, .titleinfigure, .titleinexample, .titleintable, .titleinequation, .xreftitleboldital { font-weight: bold; font-style: italic; } .itemizedlisttitle, .orderedlisttitle, .segmentedlisttitle, .variablelisttitle { font-weight: bold; } .bridgehead, .titleinrefsubsect3 { font-weight: bold; } .titleinrefsubsect { font-size: 126%; font-weight: bold; } .titleinrefsubsect2 { font-size: 113%; font-weight: bold; } .subhead1 { display: block; font-size: 139%; font-weight: bold; } .subhead2 { display: block; font-weight: bold; } .subhead3 { font-weight: bold; } .underline { text-decoration: underline; } .superscript { vertical-align: super; } .subscript { vertical-align: sub; } .listofeft { border: none; } .betadraft, .alphabetanotice, .revenuerecognitionnotice { color: #e00; background: inherit; } .betadraftsubtitle { text-align: center; font-weight: bold; color: #e00; background: inherit; } .comment { color: #080; background: inherit; font-weight: bold; } .copyrightlogo { text-align: center; font-size: 85%; } .tocsubheader { list-style-type: none; } table.icons td { padding-left: 6px; padding-right: 6px; } .l1ix dd, dd dl.l2ix, dd dl.l3ix { margin-top: 0ex; margin-bottom: 0ex; } div.infoboxnote, div.infoboxnotewarn, div.infoboxnotealso { margin-top: 4ex; margin-right: 10%; margin-left: 10%; margin-bottom: 4ex; padding: 0.25em; border-top: 1pt solid gray; border-bottom: 1pt solid gray; } p.notep1 { margin-top: 0px; margin-bottom: 0px; } .tahiti-highlight-example { background: #ff9; text-decoration: inherit; } .tahiti-highlight-search { background: #9cf; text-decoration: inherit; } .tahiti-sidebar-heading { font-size: 110%; margin-bottom: 0px; padding-bottom: 0px; } /*************************************/ /* End DARB Formats */ /*************************************/ @media all { /* * * { line-height: 120%; } */ dd { margin-bottom: 2ex; } dl:first-child { margin-top: 2ex; } } @media print { body { font-size: 11pt; padding: 0px !important; } a:link, a:visited { color: black; background: inherit; } code, pre, samp, tt { font-size: 10pt; } #nav, #search_this_book, #comment_form, #comment_announcement, #flipNav, .noprint { display: none !important; } body#left-nav-present { overflow: visible !important; } } PKT' hcPKSqE OEBPS/toc.htmph Oracle Communications Billing and Revenue Management Configuring Roaming in Pipeline Manager , Release 7.4

Contents

Preface

1 About Rating Roaming Events

2 About Settling Roaming Charges

3 About Processing Home Subscribers' Roaming Usage

4 About Processing Visiting Subscribers' Roaming Usage

5 Installing TAP Roaming Manager

6 Setting Up Roaming for TAP

7 Setting Up Pipeline Manager for Roaming Incollect Processing

8 Setting Up Pipeline Manager for Roaming Outcollect Processing

9 RAP-to-EDR Field Mappings

10 TAP and EDR Input and Output Field Pairs

11 TAP and EDR Field Mappings

12 Rating CIBER Roaming Usage Events

13 Installing CIBER Roaming Manager

14 Rating Interconnect Events

15 Detecting Roaming Fraud Using NRTRDE

16 Installing InterConnect Manager

PKhFuhphPKSqE OEBPS/rmg_tapv311_outcollect.htm About Processing Visiting Subscribers' Roaming Usage

4 About Processing Visiting Subscribers' Roaming Usage

This chapter describes the roaming outcollect process in Oracle Communications Billing and Revenue Management (BRM) for rating visiting subscribers' roaming usage.


Important:

  • The following sections describe the outcollect process for processing TAP files only.

  • To process TAP files, TAP Roaming Manager requires Suspense Manager, Rated Event (RE) Loader, and InterConnect Manager to rate roaming usage. Suspense Manager, RE Loader, and InterConnect Manager are not part of TAP Roaming Manager and requires separate licenses. You must install these supporting managers to rate roaming events. See "About Suspense Manager" and "Understanding Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.


Before reading this document, you should be familiar with the following:

Understanding Roaming Outcollect Architecture and Process Flow

You use roaming outcollect processing to process call detail records (CDRs) generated by visiting subscribers on your network. The outcollect process architecture primarily consists of the splitter, outcollect rating, and settlement pipelines. These pipelines perform the following tasks:

  • The splitter pipeline separates home subscribers' CDRs from visiting subscribers' roaming CDRs.

  • The outcollect rating pipeline rates the visiting subscribers' roaming CDRs based on InterCarrier Tariff rates and generates outcollect TAP files for each roaming partner.

  • The settlement pipeline creates settlement events by associating visiting subscribers' roaming CDRs with corresponding roaming partner accounts in the BRM database. These settlement events are loaded into the BRM database and impact your roaming partners' account balance.

Figure 4-1 depicts a high-level overview of the roaming outcollect process architecture:

Figure 4-1 Roaming Outcollect Process Architecture

Description of Figure 4-1 follows

As the above figure illustrates, incoming CDRs are handled during the outcollect process, as follows:

  1. The splitter pipeline converts the CDRs into event data record (EDR) format and separates the EDRs into home subscribers' EDRs and visiting subscribers' roaming EDRs.

    • Home subscribers' EDRs are sent to the normal rating pipeline to be rated and loaded into the BRM database by Rated Event (RE) Loader. If the rating pipeline fails to rate the EDR, the EDR is suspended and recycled by using Suspense Manager.

    • Visiting subscribers' roaming EDRs are sent to the outcollect rating pipeline to be rated.

    For more information, see "How Home CDRs Are Separated from Visiting Subscribers' CDRs".

  2. The outcollect rating pipeline rates the visiting subscribers' roaming EDRs and generates outcollect TAP files, for each roaming partner network operator, that you send to your roaming partners for verification and billing purposes. A copy of the outcollect TAP file is forwarded to the settlement pipeline for further processing.

    If the outcollect rating pipeline fails to rate the roaming EDR, the EDR is suspended and recycled by using Suspense Manager.

    For more information, see "How Visiting Subscribers' Roaming CDRs Are Rated".

  3. The settlement pipeline processes the outcollect TAP file and creates settlement events by associating the events with roaming partner accounts in the BRM database. Settlement events are loaded into the BRM database by RE Loader.

    If the settlement pipeline fails to create settlement events, the entire TAP file is suspended and loaded into the BRM database. The suspended TAP file can be corrected and recycled back to the settlement pipeline by using Suspense Manager.

    For more information, see "How Settlement Events for Incollect Roaming Charges Are Created".

For detailed information on configuring outcollect processing, see "Setting Up Pipeline Manager for Roaming Outcollect Processing".

How Home CDRs Are Separated from Visiting Subscribers' CDRs

The splitter pipeline processes CDRs as follows:

  • Incoming CDRs are converted to EDR format.

    The INP_GenericStream module provides the input interface to the splitter pipeline using BRM standard input grammar files. The input grammar converts CDRs into the internal EDR format that can be used by all BRM modules. If there are any errors, INP_GenericStream adds the error to the EDR container and sends the EDR to the reject stream.

    For more information, see "INP_GenericStream" in BRM Configuring Pipeline Rating and Discounting.

  • EDRs are separated into home and roaming EDRs.

    The FCT_EnhancedSplitting module separates the EDRs into home subscribers' EDRs and visiting subscribers' roaming EDRS so that they can be sent to the appropriate rating pipeline for processing.

    Home subscribers' EDRs are sent to the normal rating pipeline. Visiting subscribers' roaming EDRs are sent to the outcollect rating pipeline.

    You use Pricing Center to define the splitting rules: for example, you can define a rule using the source network EDR field to send home and roaming EDRs to different output streams.

    For more information, see "FCT_EnhancedSplitting" in BRM Configuring Pipeline Rating and Discounting.

  • EDRs are written to output files.

    The OUT_GenericStream module uses standard BRM SOL42 output grammar to write home and roaming EDRs to separate output files.

    As soon as the splitter pipeline generates the output files with the roaming EDRs, the outcollect rating pipeline retrieves the files and rates the roaming EDRs. See "How Visiting Subscribers' Roaming CDRs Are Rated".


    Note:

    • The splitter pipeline is optional. If your mediation system separates home CDRs from roaming CDRs before they are sent to the BRM Billing system, you do not need to use the splitter pipeline.

    • By default, the splitter pipeline does not validate incoming CDRs. You can choose to implement validation by writing your own custom iScripts and using Suspense Manager to handle any CDRs that are suspended due to validation failures.


For information about configuring the splitter pipeline, see "Configuring the Splitter Pipeline".

Transmitting CDRs to the Splitter Pipeline

External CDRs must be placed in the input directory of the splitter pipeline for the pipeline to process them. If your mediation system does not automatically place the CDRs in this directory, you can configure a Batch Controller and write a custom Batch Handler to move the CDRs to the splitter pipeline input directory.

For more information about Batch Controllers and Batch Handlers, see "Controlling Batch Operations" in BRM System Administrator's Guide.

How Visiting Subscribers' Roaming CDRs Are Rated

The outcollect rating pipeline processes the roaming EDRs as follows:

  • The contents of the splitter pipeline output file are mapped to the EDR container.

    The INP_GenericStream module uses BRM standard input grammar to parse the file and convert its contents into EDRs for rating.

  • A plan and product are selected to rate the roaming EDR.

    Based on the roaming agreement you have with your roaming partner, you set up intercarrier tariff plans and intercarrier products in Pricing Center. These plans and products are stored in the following tables:

    • IFW_NETWORKOPER

    • IFW_NETWORKMODEL

    • IFW_ICPRODUCT

    • IFW_ICPRODUCT_GRP

    • IFW_ICPRODUCT_RATE

    • IFW_ICPRODUCT_CNF

    To find the correct price basis for rating the roaming event, the FCT_CarrierIcRating module searches these tables to determine the rate plan that applies to the roaming event. It then adds the rate plan and other information such as the network operator, zones for the A and B numbers, and so forth to the EDR container. See "FCT_CarrierIcRating" in BRM Configuring Pipeline Rating and Discounting.

    For information on setting up intercarrier tariff plans and intercarrier products, see "Defining Roaming Partner Accounts in the BRM Database".

  • The impact category is selected.

    The FCT_PreRating module reads the EDR container to determine the phone number that originated the call, the destination phone number, and the start and end times of the call. Using this and other information in the EDR, this module determines the impact category and adds it to the EDR container along with supporting information on the zone model, service codes, and so forth.

  • The EDR is rated and the result is rounded.

    The FCT_MainRating module evaluates the contents of the EDR and retrieves the appropriate pricing information from the pipeline database. It then calculates the charge amount for the event and adds information on the currency type and other rating characteristics. FCT_MainRating passes the EDR to the FCT_Rounding module, which rounds the charge amount.

  • The charge for the event is converted from the local currency to Special Drawing Right (SDR) currency.

    The FCT_ExchangeRate module converts the amount in the charge packet to TAP currency (SDR).

  • Basic service and supplementary service packets are added to the EDR container for GSM services.

    The ISC_MiscOutCollect module adds BASIC_SERVICE and SUPPLEMENTARY_SERVICE blocks to the EDR container for GSM services. This is done to ensure that the TAP file generated by the pipeline contains all the required information.

If the outcollect rating pipeline is unable to rate the EDR, the EDR is suspended. See "Processing EDRs Suspended by the Outcollect Rating Pipeline".

After the EDRs are rated, the output modules generate outcollect TAP files for each roaming partner. These files contain the rated EDRs (in TAP format) for that partner. Your roaming partner uses the outcollect TAP files to verify their subscribers' roaming usage against the bill you send them and to perform their own rating on the events to bill their subscribers.

The following steps are performed to create and route outcollect TAP files to roaming partner network operator output streams:

  1. A sequence number is generated for the outcollect TAP file.

    Each outcollect TAP file is assigned a sequence number. Your roaming partner uses the sequence number to ensure that the TAP file you have sent them is not a duplicate and that there are no missing TAP files.

    The Sequence Generator is an instance of the Sequencer module that generates sequence numbers.

    Using Pricing Center, you define a Sequence Generator for each roaming partner. You define each sequence by specifying a unique sequence key that identifies the roaming partner. Depending upon the roaming partner receiving the TAP file, the Sequence Generator generates the sequence number based on the sequence key. For more information about the Sequencer, see "About Sequence Checking" in BRM System Administrator's Guide.

    A Sequence Generator can only be associated with one output stream. Because outcollect processing creates separate output streams for each roaming partner, a single Sequencer cannot be shared by multiple output streams. You must configure a Sequencer for each roaming partner output stream. For information on configuring sequence generation for your roaming partners, see "Configuring the Outcollect Rating Pipeline Input Processing".

  2. The EDRs are written to the corresponding roaming partner output stream.

    The FCT_EnhancedSplitting module routes each rated EDR to the corresponding roaming partner output stream. You use Pricing Center to define the splitting rules; for example, you can define a rule to route EDRs to different output streams based on the source network EDR field. The output module at each network operator output stream uses TAP output grammar to write the EDRs to output files. If FCT_EnhancedSplitting module is unable to route the EDR to an output stream, the EDR is routed to the suspense output stream.

When the outcollect TAP files are ready, the pipeline notifies the Event Handler by sending it the EVT_OUTPUT_FILE_READY event. Upon receiving this event notification, the Event Handler launches the move_outcollectTap.pl script, which copies the TAP files into the common directory (where all roaming partner network operator TAP files are stored until settlement events have been created) and moves the original outcollect TAP files to the settlement pipeline input directory for creating settlement events. See "About Settling Roaming Charges".


Note:

Settlement events are created to record the roaming charges and used to bill your roaming partners. DO NOT send the outcollect TAP files to your roaming partner network operators until settlement events and TAP Header information file have been successfully created by the settlement pipeline. Otherwise, billing errors can occur.


Note:

You must edit the move_outcollectTap.pl script to specify the common directory. By default, move_outcollectTap.pl copies the outcollect TAP files to the Pipeline_home/data/outcollect/tapout/common directory and moves the original outcollect TAP files to the Pipeline_home/data/outcollect/settlement/in directory. See "Configuring the Outcollect Rating Pipeline Input Processing".

For more information on configuring the outcollect rating pipeline, see "Configuring the Outcollect Rating Pipeline".

Processing EDRs Suspended by the Outcollect Rating Pipeline

If the outcollect rating pipeline is unable to rate an EDR, it sets the error in the EDR and suspends it. The FCT_Reject module evaluates the error and routes the EDR to the suspense output stream as specified by the RejectStream pipeline registry entry.

Using SE Loader, you load the suspended EDRs into the BRM database. Using Suspense Management Center, you can query the suspended events and make the necessary corrections. After the corrections are made, you can recycle the events for processing.

When the Pipeline Manager receives the recycle request, the INP_Recycle module retrieves the suspended records from the BRM database and routes the events to the pre-recycle pipeline. The pre-recycle pipeline converts the suspended events back to EDR format and sends the EDRs back to the outcollect rating pipeline for rating.

For detailed information about how EDRs are suspended and recycled, see "About Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

Transmitting Roaming EDRs to the Outcollect Rating Pipeline

In the default roaming registry, the outcollect rating pipeline's input stream is the same as the splitter pipeline's output stream. As soon as the splitter pipeline generates an output file, the outcollect rating pipeline processes the file.

You can choose to change the default behavior. For example, you can do any of the following:

  • Transfer output files from the splitter pipeline to the outcollect rating pipeline at release intervals. For example, you might want to send roaming EDRs for rating twice a day.

    To transfer roaming EDRs from the splitter pipeline to the outcollect rating pipeline at release intervals, you can do the following:

    • Set up the outcollect rating pipeline's input stream to be different from the splitter pipeline's output stream.

    • Configure a Batch Controller and a Batch Handler to move the roaming EDRs from the splitter pipeline's output stream to the input stream of the outcollect rating pipeline at specific time intervals.

    • Set the UnitsPerTranscation registry entry to a high number. The UnitsPerTransaction entry determines the number of input files received by the pipeline and consequently the number of output files generated.

  • Configure the outcollect rating pipeline to process the output files from the splitter pipeline only after a certain number of files have accumulated.

    To configure the outcollect rating pipeline to start processing after a certain number of input files has accumulated, you use the UnitsPerTransaction registry entry to specify the number of input files. For instance, when UnitsPerTransaction is set to 1, the pipeline starts processing as soon as it receives one input file. However, if UnitsPerTransaction is set to 10, the pipeline waits until ten input files are received before it starts to process them. For more information about pipeline transactions, see "About Pipeline Manager Transactions" in BRM System Administrator's Guide.

About Generation of Notification Files When There Is No Roaming Activity

The outcollect rating pipeline generates notification files when there is no roaming activity by a roaming partner's subscribers. If the input file of the outcollect rating pipeline doesn't contain any roaming EDRs for a network operator configured in this pipeline, a notification file is generated.

The notification file informs your roaming partner that none of its subscribers have been roaming on your network. The notification file is generated based on the information in the EDR header and trailer records and does not contain any call detail records.

About Sending Outcollect TAP Files to Your Roaming Partner


Note:

You send outcollect TAP files to your roaming partners only after settlement events and TAP Header information file have been successfully created by the settlement pipeline.

When the settlement pipeline finishes processing the outcollect TAP file, it notifies the Event Handler by sending it the EVT_OUTPUT_FILE_READY event. Upon receiving this event notification, the Event Handler launches the move_TapSent.pl script. This script identifies the corresponding outcollect TAP file previously stored in the common directory by the outcollect rating pipeline and moves the file to another pre-defined directory for sending the TAP file to your roaming partner or clearing house.


Note:

You must edit the move_TapSent.pl script to specify the common directory used for storing the outcollect TAP files and the directory used for sending the TAP files to your roaming partners or clearing house. By default, move_TapSent.pl uses the Pipeline_home/data/outcollect/tapout/common directory as the common directory and moves the TAP files to the Pipeline_home/data/outcollect/tapout/sent directory. See "Configuring Outcollect Settlement Pipeline Input Processing".

About Processing Rejected Outcollect TAP Files and Records

When you send outcollect TAP files to a roaming partner, the roaming partner validates the files to ensure there are no errors. If the validation fails, the partner generates a RAP file that includes the failed outcollect TAP file and records and sends it to you for corrections.

RAP file processing involves:

  • Correcting and reprocessing the erroneous TAP files and records and generating new TAP files to send to your roaming partner.

  • Backing out the balance impacts of settlement events associated with the erroneous TAP files and records that were previously recorded in the BRM database.

RAP files are handled by the RAP processing pipeline as follows:

  • The RAP file is parsed by the input module and a RAP Acknowledgement file is generated that you send to your roaming partner. The file includes information about the network operator who sent the RAP file, network operator receiving the file, RAP file sequence number, Acknowledgement file creation timestamp, and Acknowledgement file available timestamp.

  • For a fatal error RAP file, the entire file is suspended and sent to the TAP correction pipeline for corrections. See "Error Correction for TAP Files with Fatal Errors".

  • For a severe error RAP file, the records are suspended and sent to the outcollect rating pipeline for processing. See "Error Correction for TAP Files with Severe Errors".

  • For a missing error RAP file, a set of TAP notification files is generated for each missing sequence number.

  • To back out the balance impacts of the outcollect TAP file or records, the pipeline creates an ASCII file that specifies the extraction criteria for extracting settlement events associated with the TAP file or records. The pin_event_extract utility uses this file to extract the settlement events from the BRM database for backout-only rerating. See "Backing Out the Balance Impacts for the Rejected TAP Files and Records".

For information on configuring the RAP processing pipeline, see "Configuring the RAP Processing Pipeline".

Figure 4-2 depicts a high-level overview of the RAP processing architecture:

Figure 4-2 RAP Processing Architecture

Description of Figure 4-2 follows

Error Correction for TAP Files with Fatal Errors

TAP files with fatal errors are processed by RAP processing pipeline as follows:

  • The input module converts the contents of the TAP file back to EDR format and maps the contents to staging fields in the EDR container by using RAP input grammar.

  • The ISC_RAP_0105_InMap module maps the data in the staging fields to business fields in the EDR container. It creates a header and a trailer EDR that contain information about the RAP file and a single detail EDR that contains information about the rejected outcollect TAP file.

  • The ISC_DupRAPRecords module sends a copy of the detail EDR to an output stream. This output stream uses Event Extraction output grammar to write the EDRs to a file that is used by the pin_event_extract utility to extract settlement events from the BRM database for backout-only rerating. See "Backing Out the Balance Impacts for the Rejected TAP Files and Records".

  • The ISC_OverrideSuspenseParams module overrides the suspense parameters to recycle the suspended EDRs to the TAP correction pipeline.

The detail EDR is then routed to the suspense batch output stream. The suspense batch output stream writes the EDRs to a batch file. This batch file contains the TAP file name, location of the file, RAP error code, and the records in the TAP file. You load this file into the BRM database by using Suspended Batch (SB) Loader.

Using Suspense Management Center, you can query the suspended batch file to analyze the errors and resubmit the batch for processing. When Pipeline Manager receives the resubmit request, DAT_ResubmitBatch routes the batch file to the TAP correction pipeline.

In the TAP correction pipeline, the input mapping file maps the batch file into the EDR container. Using your own custom iScript, you implement the logic to make the necessary corrections by modifying and updating the EDR contents.

After the corrections have been made, the output module uses TAP output grammar to write the EDR to an output file, which includes the original outcollect TAP file sequence number and the original RAP file sequence number.

The TAP correction pipeline then notifies the Event Handler by sending it the EVT_OUTPUT_FILE_READY event. Upon receiving this event notification, the Event Handler launches the move_outcollectTap.pl script to copy the TAP file into the common directory (where all network operator outcollect TAP files are stored until settlement events have been created) and to move the TAP file to the settlement pipeline input directory for creating settlement events. See "About Settling Roaming Charges".

For information on configuring the TAP correction pipeline, see "Configuring the TAP Correction Pipeline".

Error Correction for TAP Files with Severe Errors

TAP files with severe errors are processed by RAP processing pipeline as follows:

  • The input module converts the call event detail records in the TAP file back to EDR format and maps the call event detail fields to staging fields in the EDR container by using RAP input grammar.

  • The ISC_RAP_0105_InMap module maps the data in the staging fields into business fields in the EDR container. It uses the lookup information in the TAP Header Information file, and information in the RAP file to create header and trailer EDRs. For each call event detail record, it creates an instance of the detail EDR with the call event details.

  • The ISC_DupRAPRecords module duplicates and sends a copy of the detail EDRs to the event extraction output stream. This output stream Kuses Event Extraction output grammar to write the EDRs to a file that is used by the pin_event_extract utility to extract settlement events from the BRM database for backout-only rerating. See "Backing Out the Balance Impacts for the Rejected TAP Files and Records".

  • The ISC_OverrideSuspenseParams module overrides the suspense parameters to recycle the suspended EDRs to the outcollect rating pipeline.

The detail EDRs are routed to the suspense output stream. The suspense output stream writes the EDRs to a suspense file. You load this file into the BRM database by using Suspense Event (SE) Loader.

Using Suspense Management Center, you can query the suspended EDRs and make the necessary corrections. After the corrections are made, you can recycle the EDRs for processing. When Pipeline Manager receives the recycle request, the DAT_Recycle module retrieves the suspended events from the BRM database and routes the events to the pre-recycle pipeline.

The pre-recycle pipeline converts the suspended events back to EDR format and sends the EDRs to the outcollect rating pipeline input directory.


Note:

The outcollect rating pipeline input directory also contains new roaming EDRs sent from the splitter pipeline.

The outcollect rating pipeline rates the recycled EDRs and newly arriving EDRs and generates a new outcollect TAP file. See "How Visiting Subscribers' Roaming CDRs Are Rated".

The outcollect rating pipeline notifies the Event Handler by sending it the EVT_OUTPUT_FILE_READY event. Upon receiving this event notification, the Event Handler launches the move_outcollectTap.pl script to copy the outcollect TAP file into the common directory (where all network operator outcollect TAP files are stored until settlement events have been created) and to move the original outcollect TAP file to the settlement pipeline input directory for creating settlement events. See "About Settling Roaming Charges".

Backing Out the Balance Impacts for the Rejected TAP Files and Records

The RAP processing pipeline creates an ASCII file that specifies the extraction criteria for extracting settlement events from the BRM database associated with the rejected outcollect TAP files and records.

For rejected TAP files, the ASCII file is created with a single record with the following information:

  • Outcollect TAP file sequence number

  • Network operator sending the TAP file

  • Network operator receiving the TAP file

For rejected TAP records, an ASCII file is created that contains a record for each rejected TAP record. Each record contains the following information:

  • Outcollect TAP file sequence number

  • Network operator sending the TAP file

  • Network operator receiving the TAP file

  • MSISDN

  • IMSI

  • Call event start timestamp

To back out the settlement event balance impacts (applied to the roaming partner's account when the outcollect TAP file was originally created), you manually run the Event Extraction Manager and specify the ASCII file in the input parameter. The Event Extraction Manager uses the information in the ASCII file to extract the settlement events from the BRM database and copies the event data to an output file in the standard BRM input format.

The backout pipeline processes the Event Extraction output file and creates shadow events to negate the balance impacts of the settlement events. The output module writes the shadow events to an output file using RE Loader output grammar. You use RE Loader to load the shadow events into the BRM database.

If the backout pipeline is unable to process the Event Extraction output file, it suspends the entire file. Using Suspense Management Center, you can resubmit the file for processing.

For more information about Event Extraction Manager, see "pin_event_extract" in BRM Setting Up Pricing and Rating.

For information on configuring the backout pipeline, see "Configuring the Backout Pipeline".

Including Country Codes in TAP Output Files

BRM maps the EDR container field DETAIL.CALLED_COUNTRY_CODE into the CalledCountryCode field in the output TAP file. To ensure that the CalledCountryCode field has a valid value in cases where the country code is not present in the EDR, you specify a default country code in the CalledCountryCode registry entry of the TAP outcollect pipelines.

The value of this entry is a three-character country code, such as USA or GBR, that specifies the destination country code for an international call. For example:

ifw.Pipelines.OutCollectPipeline.CalledCountryCode = USA
PKnhPKSqEOEBPS/rmg_ciber.htm]G Rating CIBER Roaming Usage Events

12 Rating CIBER Roaming Usage Events

This chapter describes how to set up the Oracle Communications Billing and Revenue Management (BRM) Pipeline Manager for rating CIBER events.

For information about pipeline rating, see "About Pipeline Rating" in BRM Configuring Pipeline Rating and Discounting.

About Processing CIBER OCC Records

Other charges and credits (OCC) records are CIBER records of types 50 and 52. When you configure a pipeline to create CIBER OCC records, one OCC record is generated for each day that a roaming subscriber makes one or more calls from a visited network. By default, a CIBER OCC record is created only for the first call processed for a subscriber for a particular day, with the day beginning at 12:00 a.m.

To generate CIBER OCC records for network operators, you configure the following components:

  1. Use Pricing Center to specify that CIBER OCC records are generated for network operators. See .

  2. Configure the FCT_CiberOcc function module to create CIBER OCC records. See "FCT_CiberOcc" in BRM Configuring Pipeline Rating and Discounting.

    Use the EdrNetworkModel entry to specify the network model, which identifies the home network to use for the pipeline. Use the value you entered in the Code field in Pricing Center when defining network models. See the discussion about defining a network model in BRM Pricing Center Online Help.

  3. Configure the FCT_DuplicateCheck function module to set an EDR field for duplicate EDRs. This field is checked by the FCT_CiberOcc module to determine whether to create an OCC record. See "Configuring Duplicate Check for CIBER OCC Records" and "FCT_DuplicateCheck" in BRM Configuring Pipeline Rating and Discounting.


Note:

To rate CIBER records, an EDR must be able to contain multiple charge packets. To enable this, create price models with multiple RUMs. See "About Pipeline Price Models" in BRM Setting Up Pricing and Rating.

CIBER OCC records are created only when the call record being processed by FCT_CiberOcc has OCC-associated charges. The type of call record determines which OCC record type is generated as shown in Table 12-1:

Table 12-1 Call Record Type

Call Record TypeType of OCC Record Generated

10, 20, 30

50

22, 32

52

Other call records

No OCC record is generated.


If a combination of these types occur for a subscriber on the same day, the type of OCC record created is based on the first processed call record.

About Generating CIBER OCC Records for Network Operators

You use Pricing Center to specify whether to generate CIBER records for other charges and credits (OCC records) during outcollect processing. These records let you apply surcharges when your partner's roaming customers make calls from your network.

To specify that CIBER OCC records be generated for a network operator, see the discussion about generating CIBER OCC records for the network operator in BRM Pricing Center Online Help.

Configuring Duplicate Check for CIBER OCC Records

You can avoid creating duplicate OCC records by configuring the FCT_CiberOcc module to work with the FCT_DuplicateCheck module.

  1. Determine which field you want to use for duplicate check. Typically, this field is DETAIL.ASS_CIBER_EXT.NO_OCC. If you use a different field, it must be an Integer value.

  2. Enter the field name in the FCT_CiberOcc module NoOCCField registry entry:

    NoOCCField = DETAIL.ASS_CIBER_EXT.NO_OCC
    
  3. Enter the same field name in the FCT_DuplicateCheck module DuplicateIndicatorField registry entry:

    DuplicateIndicatorField = DETAIL.ASS_CIBER_EXT.NO_OCC
    

    See "FCT_DuplicateCheck" in BRM Configuring Pipeline Rating and Discounting.

Changing the Default Time Scheme

A CIBER OCC record is generated only for the first call processed for a subscriber for the day, with the day beginning at 12:00 a.m. You can customize this feature to use another time scheme for all system identification numbers (SIDs). However, you cannot specify different time schemes for different SIDs.

To use another time scheme:

  1. Define a new EDR field that records an attribute of the call date and time.

    This field will be used to determine whether to generate an OCC record. For example, record a value between 1 and 12 to generate an OCC record once per month, or record a value between 1 and 52 to generate a weekly OCC record.

  2. Write an iScript that sets a value in the new EDR field based on the call date. (See "Creating iScripts and iRules" in BRM Developer&#x2019;s Guide.) This iScript must be executed in the pipeline before the FCT_DuplicateCheck module.

  3. Specify the new EDR field for duplicate checking in the Fields entry in the FCT_DuplicateCheck module registry. See "FCT_DuplicateCheck" in BRM Configuring Pipeline Rating and Discounting.

  4. Specify the values that describe the new time interval in the OCCIntervalIndicator and OCCDescription entries in the FCT_CiberOcc module registry. See FCT_CiberOcc in BRM Configuring Pipeline Rating and Discounting.

    • The OCCDescription entry specifies the service associated with the OCC.

      This value is entered in the OCC_DESCRIPTION field in the ASSOCIATED_CIBER_EXTENSION block of the OCC record created.


      Important:

        This field must not contain spaces. If you require spaces in the description, write an iScript to populate this field.

    • The OCCIntervalIndicator field specifies the interval at which the associated OCC record is generated.


      Important:

       To use an interval other than the default (daily), you must customize this feature. See "Changing the Default Time Scheme".

      Possible values:

      1 = Event (Generates an OCC record based on an event.)

      2 = Hourly

      3 = Daily

      4 = Weekly

      5 = Monthly

      This value is entered in the OCC_INTERVAL_INDICATOR field in the ASSOCIATED_CIBER_EXTENSION block of the OCC record.

  5. Change the DETAIL.ASS_CIBER_EXT.OCC_END_DATE field in the OCC record to the date or time specific to your needs. By default, this field is set to the value of OCC_START_DATE to apply a daily surcharge.


    Note:

    You can change the field by writing an iScript.

About Finding the Rate Plan for CIBER Records

To ensure that a rate plan is selected for every CIBER record, you must define a default Interconnect (IC) Product for source networks. IC products are linked to rate plans. If a search for a corresponding rate plan cannot be found for the source network, the rate plan for the default IC Product is used.

You configure IC Products in Pricing Center. To configure default IC products for source networks:

  1. In Pricing Center, go to the Interconnect Product Configuration tab. See the discussion about configuring an interconnect product in BRM Pricing Center Online Help.

  2. For every IC Product Configuration that has a value in the Source Network entry, add a new IC Product Configuration. In the new IC Product Configuration, specify the same value for Source Network and enter .* (a period and an asterisk) as the value for the following fields:

    • Destination Network

    • Origin Area Code

    • Destination Area Code

    • Transit Area Code

    • Record Type

    • Service Code

    • Service Class

    • Usage Class

    In the IC Product field, enter the product that you want to use as the default.

  3. Save the configuration.

Configuring EDR Field Validation

You configure an EDR field validation to ensure that your roaming partner has followed the agreed procedure for generating files and automatically return the single EDRs that do not match the agreement, without rejecting the entire file.

To perform EDR field validation, follow these procedures:

To perform additional EDR field validation, configure rule sets and assign the rule sets to the FCT_IRules module. See "Configuring Rule Sets for the EDR Field Validation".

Configuring the iRuleValidation Module

The iRuleValidation module is an instance of the FCT_IRules function module. To configure iRuleValidation, set up an instance of FCT_IRules in the FunctionPool section of the Pipeline Manager registry and use iRulesValidation as the module instance.

iRuleValidation uses one of the following XML files that contain the rules and rule sets used for validation:

  • The CIBER_VAL.xml file specifies the rules and rule items for CIBER records.

Rules in the .xml file must be loaded into the Pipeline Manager database before starting a pipeline. See "Importing and Exporting Validation Rules" in BRM Developer&#x2019;s Guide.

Specify the XML rules file in the Rules entry of the iRuleValidation registry.

For more information, see "iRuleValidation" IN BRM Configuring Pipeline Rating and Discounting.

Configuring Rule Sets for the EDR Field Validation

You configure rule sets for EDR field validation in the database. You name a rule set according to the format used, such as CIBER. Each rule set consists of a series of rules, defining one rule for each of the EDR fields that are validated. Each rule contains a rule item. This rule item represents the current default error condition that results in an error message.

There are several levels of error messages:

  • Severe errors

  • Fatal errors

  • Warning errors


    Note:

    In case of warning errors, Pipeline Manager generates an internal error that is logged in the stream log but does not return any detail. In this case, you discuss the settlement with your roaming partner using a conventional method, such as telephone or mail.

The rules and rule sets for EDR field validation are stored in the following database tables:

  • IFW_RULESET

  • IFW_RULESETLIST

  • IFW_RULE

  • IFW_RULEITEM

You can use the following tools to configure rules and rule sets:

  • Pricing Center. See the discussion about creating rules and rule items and creating rule sets and rule set lists in BRM Pricing Center Online Help.

  • The FCT_IRules module. This module can use rules stored in the database. See "FCT_IRules" in BRM Configuring Pipeline Rating and Discounting.

PK(bG]GPKSqE"OEBPS/rmg_tapv311_incollect_cf.htm Setting Up Pipeline Manager for Roaming Incollect Processing

7 Setting Up Pipeline Manager for Roaming Incollect Processing

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


Note:

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

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

Setting Up Roaming Incollect Processing Pipelines

Configure the following pipelines to set up roaming incollect processing:

Configuring the Validation Pipeline

Configure the validation pipeline by performing the following tasks:

Configuring the Validation 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 Validation Pipeline DataDescription Registry Section

Configure the validation 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
         RAP     = ./formatDesc/Formats/TAP3-NG/RAP_0105_Blocks.dsc
         SOL42   = ./formatDesc/Formats/Solution42/SOL42_V670_REL.dsc
       }
       InputMapping
       {
       }
       OutputMapping
       {
         SOL42   = ./formatDesc/Formats/Solution42/SOL42_V670_REL_OutMap.dsc
       }
     }
   }
}

Configuring Validation Pipeline Input Processing

Configure input processing for the validation pipeline as follows:

  1. (Optional) Configure a Batch Controller and a Batch Handler to send TAP files that you receive from the clearing house or your roaming partner to the input directory of the validation 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 TAP files directly to the validation pipeline.

    For more information about configuring a Batch Controller, see "Controlling Batch Operations" in BRM System Administrator's Guide.

  2. Configure sequence checking of incoming TAP files.

    1. Using Pricing Center, define a Sequence Checker with multiple sequences. Define each sequence by specifying a sequence key that is the same as the roaming partner ID. See the discussion about defining a sequence check in the Pricing Center Help for more information.

    2. Edit the SequencerPool section of the pipeline registry.

      • Set the sequencer instance to the name of the Sequence Checker defined in step a above.

      • Set the SequencerType registry entry to Check.

        For information, see "Sequencer" in BRM Configuring Pipeline Rating and Discounting.

    3. Assign the Sequencer to the pipeline output controller.

      • Set the Sequencer registry entry in the pipeline output controller to the name of the Sequence Checker.

      For more information, see "Output Controller" in BRM Configuring Pipeline Rating and Discounting.

    The following is a sample configuration for a Sequence Checker called SEQ_CHECK_TAPIN:

    SequencerPool
    {
       SEQ_CHECK_TAPIN 
       { 
          Source = Database
          Controller 
          { 
             SequencerType = Check
             ReuseGap = True 
             SequenceLength = 5
             DatabaseConnection = ifw.DataPool.Login
          }
       } 
    }
    ...
    ...
    ...
    ...
    Output
    {
    
         SequenceGeneration = Transaction
         Sequencer = SEQ_CHECK_TAPIN
    }
    

    For more information about configuring Sequencers, see "Checking and Generating Sequence Numbers" in BRM System Administrator's Guide.

  3. Configure the INP_GenericStream input module, which maps TAP input data to staging fields in the EDR container using the TAP input grammar file.

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

      Grammar = ./formatDesc/Formats/TAP3-NG/TAP_0312_InGrammar.dsc
      
    2. Configure the EXT_InFileManager registry entry to specify information about the input file. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configuring Validation Pipeline Function Modules

Configure the registry for the following modules:

  • ISC_TAP_0312_Validations, which validates the TAP input data. See "ISC_TAP_0312_Validations" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_TAP_0312_InMap, which maps TAP data from staging fields to the business fields in the EDR container. See "ISC_TAP_0312_InMap" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Reject, which sends invalid TAP records to the reject stream.

    • Set the StreamMap and UseRejectStream registry entries to the reject output stream.

    See "FCT_Reject" in BRM Configuring Pipeline Rating and Discounting.

  • UpdateTapInfo_Tapin, which stores information about incoming TAP files in the IFW_TAPINFO table used by the StopRapGen utility. See "UpdateTapInfo_Tapin" in BRM Configuring Pipeline Rating and Discounting.

Configuring Validation Pipeline Output Processing

Configure output processing for the validation pipeline as follows:

  1. Configure sequence generation for RAP files.

    1. Using Pricing Center, define a Sequence Generator. See the discussion about defining a Sequence Generator in the Pricing Center Help for more information.

    2. Edit the SequencerPool section of the registry.

      • Set the SequencerInstance registry entry to the name of the Sequence Checker defined in step 1a above.

      • Set the SequencerType registry entry to Generation.

        For information, see "Sequencer" in BRM Configuring Pipeline Rating and Discounting.

    For more information about configuring Sequencers, see "Checking and Generating Sequence Numbers" in BRM System Administrator's Guide.

  2. Configure a RAP output stream to write invalid TAP files and records to RAP files.

    1. Set the Grammar registry entry for the OUT_GenericStream module to the name of the RAP output grammar description file:

      Grammar = ./formatDesc/Formats/TAP3-NG/RAP_0105_OutGrammar.dsc
      
    2. Set the Sequencer registry entry for OUT_GenericStream to the Sequence Generator defined in step 1a above.

  3. Configure fatal RAP file generation by configuring the input module to write TAP files with a fatal error to a RAP file.

    1. Set the RapOutStream registry entry for the INP_GenericStream module to the RAP output stream.

    2. Set the Sequencer registry entry for INP_GenericStream to the Sequence Generator defined in step 1a above.

  4. Configure another output stream to write valid event data records (EDRs) to an output file to be processed by the reprice and incollect settlement pipelines.

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

      Grammar=./FormatDesc/Formats/Solution42/SOL42_V670_REL_OutGrammer.dsc
      
    2. Configure the EXT_OutFileManager registry entry to specify output file information. See "Output Controller" in BRM Configuring Pipeline Rating and Discounting.

  5. Configure Event Handler to send output files to the reprice and incollect settlement pipelines.

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

      EventHandler
      {
         ModuleName      = EVT
         Module
         {
            Events
            {
      ifw.Pipelines.TAPInProcessingPipeline.Output.OutputCollection.TAPInProcessingOutput.Module.OutputStream.Module
               {
                  EVT_OUTPUT_FILE_READY = ./bin/move_incollect_roam.pl
               }
             }
         }
      }
      

      where:

      TAPInProcessingPipeline is the name of the validation pipeline.

      TAPInProcessingOutput is the output stream for writing valid EDRs.

      For more information, see "Event Handler" in BRM Configuring Pipeline Rating and Discounting.

    2. Edit the move_incollect_roam.pl script.

      Edit the following line to specify the input directory of the reprice pipeline:

      my $COPY_DIR = "$ENV{IFW_HOME}/data/incollect/reprice/in";
      

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

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

Configuring the Reprice Pipeline

Configure the reprice pipeline by performing the following tasks:

Configuring the Reprice Pipeline DataDescription Registry Section

Configure the reprice 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 Reprice Pipeline Input Processing

Configure input processing for the reprice pipeline as follows:

  1. Configure the INP_GenericStream input module, which maps the contents of the validation pipeline output file into 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 input file information. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configuring Reprice Pipeline Function Modules

Configure the registry for the following modules:

  • ISC_ConsolidatedCP, which removes all non '00' impact category charge packets and sets the G/L ID. See "ISC_ConsolidatedCP" in BRM Configuring Pipeline Rating and Discounting.

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

  • FCT_ServiceCodeMap, which maps external service codes to internal service codes. See "FCT_ServiceCodeMap" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_UsageClassMap, which maps external codes for supplementary services, such as call forwarding, to internal usage classes. See "FCT_UsageClassMap" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Account, which identifies the subscriber account that generated the event. See "FCT_Account" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_ApplyTax, which checks whether incoming roaming charge tax amounts need to be passed on to the subscriber. See "Choosing Whether to Apply Taxes for Roaming" and "ISC_ApplyTax" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Filter_Set, which adds system products and discounts to the subscriber's list of products. See "FCT_Filter_Set" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_CustomerRating, which supplies rate plans for the FCT_MainRating module. See "FCT_CustomerRating" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_PreRating, which calculates zones and creates impact categories.

  • FCT_USC_Map, which performs usage scenario mappings. See "FCT_USC_Map" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_MainRating, which performs the main rating functionality in the pipeline. You can rerate the call, do markup, passthrough, etc. See "FCT_MainRating" inBRM Configuring Pipeline Rating and Discounting.

    • The total charge amount in the charge packets created by the input file should match the wholesale_charged_amount under the detail block.

    • Based on the rating product, the rating module will create an ASS_CBD with one CP.

    • FCT_MainRating works on the ASS_CBD rating and wholesale_charged_amount markup and updates the chargeamount field in the CP under ASS_CBD created by CustomerRating.

  • FCT_Rounding, which performs rounding of the charge value calculated by rating. See "FCT_Rounding" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ExchangeRate, which converts the TAP currency (SDR) to the subscriber's billing currency (for example, EURO). The exchange rate is determined based on the call time. See "FCT_ExchangeRate" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_DiscountAnalysis, which performs discounting analysis functions. See "FCT_DiscountAnalysis" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_PreDiscount, which determines the discount impact category.

  • FCT_Discount, which calculates and applies discounts. See "FCT_Discount" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Rounding, which rounds the discount value calculated by discounting. See "FCT_Rounding" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ApplyBalance, which adds discounts to the EDR balance. See "FCT_ApplyBalance" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ItemAssign, which identifies an appropriate bill item to be assigned to the EDR. See "FCT_ItemAssign" in BRM Configuring Pipeline Rating and Discounting.

  • 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:

    CurrencyType = B
    ChargeBreakDownRecord = 980
    

    See "FCT_BillingRecord" in BRM Configuring Pipeline Rating and Discounting.

Configuring Reprice Pipeline Output Processing

Configure output processing for the reprice pipeline as follows:

  1. Configure routing of EDRs to separate output streams based on service type:

    1. For each service type, configure an output module to write rated EDRs to an output file. This file is loaded into the BRM database by Rated Event (RE) Loader.

      • Set the Grammar registry entry for OUT_GenericStream to the RE Loader output grammar description file:

        Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc
        
      • Configure the EXT_OutFileManager registry entry to specify output file information.

        See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting for more information.

    2. Configure the IRL_EventTypeSplitting module to send EDRs to separate output streams based on service type. See "IRL_EventTypeSplitting" in BRM Configuring Pipeline Rating and Discounting for more information.

Configuring DAT_InterConnect

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

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

For more information, see "DAT_InterConnect" in BRM Configuring Pipeline Rating and Discounting.

Configuring Rated Event Loader for the Reprice Pipeline

You must configure RE Loader to load events rated by the reprice pipeline 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 file created by the reprice pipeline, how to process the events in the file, and so forth.

For complete details on how to configure RE Loader, see "Configuring Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.

Configuring Suspense Manager for the Reprice Pipeline

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

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

  • FCT_PreSuspense, which appends suspense-related information to the EDR. See "FCT_PreSuspense" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Reject, which sends suspended EDRs to the reject output stream. See "FCT_Reject" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Suspense, which adds suspense reason and suspense subreason codes to the EDRs. See "FCT_Suspense" in BRM Configuring Pipeline Rating and Discounting.

  • Suspense 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. See "DAT_Listener" in BRM Configuring Pipeline Rating and Discounting.

  • 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. See "DAT_Recycle" in BRM Configuring Pipeline Rating and Discounting.

  • The pre-recycle pipeline, which sends the EDRs to the reprice pipeline to be rated again.

For instructions on how to configure Suspense Manager, see "Configuring Suspense Manager" in BRM Configuring Pipeline Rating and Discounting.

Configuring the Incollect Settlement Pipeline

Configure the incollect settlement pipeline by performing the following tasks:

Configuring the Incollect Settlement Pipeline DataDescription Registry Section

Configure the incollect settlement 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 Incollect Settlement Pipeline Input Processing

Configure input processing for the incollect settlement pipeline as follows:

  1. Configure the INP_GenericStream input module, which maps the output file from the validation pipeline into EDR container fields:

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

      Grammar = ./formatDesc/Formats/Solution42/SOL42_V670_REL_InGrammar.dsc
      
  2. Configure the EXT_InFileManager registry entry to specify input file information. See "EXT_InFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configuring Incollect Settlement Pipeline Function Modules

Configure the registry for the following modules:

  • ISC_ConsolidatedCP, which removes all non-00 impact category charge packets and sets the G/L ID. See "ISC_ConsolidatedCP" in BRM Configuring Pipeline Rating and Discounting.

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

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

    MapGroup = INCOLLECT
    

    See FCT_ServiceCodeMap in BRM Configuring Pipeline Rating and Discounting.

  • FCT_Account, which determines the roaming partner account and associates the EDR with this account. See "FCT_Account" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ExchangeRate, which converts charge amount in the charge packets to the subscriber's billing currency. See "FCT_ExchangeRate" in BRM Configuring Pipeline Rating and Discounting.

  • FCT_ItemAssign, which assigns the bill item associated with the roaming partner account's incollect service to the EDR. See "FCT_ItemAssign" in BRM Configuring Pipeline Rating and Discounting.

  • 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
    

    See "FCT_BillingRecord" in BRM Configuring Pipeline Rating and Discounting.

  • ISC_RollbackSettlement, which rolls back transactions when an error occurs. See "ISC_RollbackSettlement" in BRM Configuring Pipeline Rating and Discounting.

Configuring Incollect Settlement Pipeline Output Processing

Configure output processing for the incollect settlement pipeline as follows:

  1. Configure GPRS and GSM EDR splitting:

    1. Create a system brand called GSMR to associate with GSM EDRs; create a system brand called GPRSR to associate with GPRS EDRs. See the discussion about creating system brands in the Pricing Center Help.

    2. Define splitting rules and associate the rules with the system brands. See the discussion about defining splitting types in the Pricing Center Help.

    3. Configure the FCT_EnhancedSplitting module and use the SystemBrands 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 RE Loader by configuring the OUT_GenericStream module as follows:

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

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

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc
      
    3. Configure the EXT_OutFileManager registry entry to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

  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 as follows:

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

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

      Grammar = ./formatDesc/Formats/Solution42/V670_EVENT_LOADER_OutGrammar.dsc
      
    3. Configure the EXT_OutFileManager registry entry to specify output file information. See "EXT_OutFileManager" in BRM Configuring Pipeline Rating and Discounting.

Configuring Rated Event Loader for the Incollect Settlement Pipeline

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 incollect settlement pipeline, how to process the events in the output file, and so forth.

For complete details on how to configure RE Loader, see "Configuring Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.

Configuring Suspense Manager for the Incollect Settlement Pipeline

You must configure Suspense Manager pipeline components to process input files suspended by the incollect settlement pipeline.

Input files suspended by the incollect settlement pipeline are processed by using the following Suspense Manager components:

  • FCT_BatchSuspense, which suspends the input file and creates a batch suspense file. See "FCT_BatchSuspense" in BRM Configuring Pipeline Rating and Discounting.

  • 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. See "DAT_Listener" in BRM Configuring Pipeline Rating and Discounting.

  • DAT_ResubmitBatch, which retrieves the suspended batch file from the BRM database and sends it to the incollect settlement pipeline for processing again. See "DAT_ResubmitBatch" in BRM Configuring Pipeline Rating and Discounting.

For instructions on how to configure Suspense Manager, see