Skip Headers
Oracle® Communications Billing and Revenue Management Telco Integration
Release 7.5

E16721-10
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

21 Adding New Prepaid Services

This chapter describes how to add a prepaid service to your Oracle Communications Billing and Revenue Management (BRM) system by using Services Framework Manager.

About Adding a Prepaid Service

Complete these tasks to add a new prepaid service to your BRM system:

  1. Extending Configuration, Event, Service, and Device Objects.

  2. Creating and Loading Configuration Files.

  3. Modifying Policy Files.

  4. Modifying service-specific helper opcodes. See "Services Framework AAA Manager FM Helper Opcodes" in BRM Developer's Reference.

  5. Writing custom opcodes that run during service order and device state changes. See "Writing a Custom Facilities Module" in BRM Developer's Guide.

  6. Modifying the XML provisioning payload file created by the Services Provisioning Data Manager. See "load_pin_telco_provisioning".

  7. Modifying Customer Center to Support Your New Service.

  8. Testing Provisioning by the Network Simulator.

Extending Configuration, Event, Service, and Device Objects

This section describes how to extend objects to support your new service (service_name).

  1. Make sure your Oracle Data Manager (dm_oracle) configuration file (BRM_Home/sys/dm_oracle/pin.conf) has write_enable parameters set to 1:

    - dm dd_write_enable_objects 1
    - dm dd_write_enable_fields 1
    - dm dd_write_enable_portal_objects 1
    
  2. Extend the classes listed in Table 21-1 by using Storable Class Editor.

    In this table, service_name indicates your service name:

    Table 21-1 Class Extensions

    Extension Notes

    /config/telco/service_name

    Do not add new fields to this extended class.

    /config/telco/service_order_state/service_name

    Do not add new fields to this extended class.

    /event/provisioning/service_order/telco/service_name

    Instances of this class are the provisioning service orders for your new service.

    (Optional) Add fields to the extended class.

    /service/telco/service_name

    This class contains the service definitions for your new service.


  3. If the new service requires a new device or devices in addition to the default number device (/device/num), extend the classes listed in Table 21-2 by using Developer Center:

    In this table, device_name indicates your device name.

    Table 21-2 Device Extensions

    Extended Class Notes

    /device/device_name

    None

    /config/device_state/device_name

    See load_pin_device_state


For more information about creating custom fields, see "Creating Custom Fields and Storable Classes" in BRM Developer's Guide.

Creating and Loading Configuration Files

This section describes how to create and load configuration files to support your new service.

  1. Check in the directory where you run the load utilities to verify that you have a configuration (pin.conf) file that connects to the correct Connection Manager (CM).

  2. Create a localized string configuration file and load it by running the load_localized_string utility.

  3. Load any new devices. See "Installing and Configuring Number Manager and Number Administration Center".

    Important:

    If you are using /device/num, use Number Administrator to load the devices. If you are creating a custom device, you must create and run a load utility for it.
  4. Define the device-to-service mappings in a text file and load it by running the load_pin_device_permit_map utility.

    The default device-to-service mappings text file shipped with Number Manager is BRM_Home/sys/data/config/pin_device_permit_map.

    See "Defining Device-to-Service Associations" in BRM Developer's Guide.

  5. Add provisioning configuration information to a text file and load it by running the load_pin_telco_provisioning utility.

    The following sample provisioning definition is for a service called cellular:

    Service provisioning info:
    
    /service/telco/cellular, D,
    "NAME" "MOBTEL",
    PIN_FLD_TELCO_FEATURES[*].PIN_FLD_NAME
    /device/num, I, PIN_FLD_DEVICE_ID "MSISDN"
    

    Tip:

    See the sample input file BRM_Home/sys/data/config/pin_conifg_telco_service_order.

    After you load this file, a single instance of /config/telco/service_name is created.

  6. Define provisioning service order states in a text file and load it with the load_pin_telco_service_order_state utility.

    The following sample state definition is for a service called cellular:

    /config/telco/service_order_state/cellular
    /event/provisioning/service_order/telco/cellular
    # NEW -> READY (starting state)
    1: 1: 0: 0
    2: 0:0
    3: 0:0
    4: 0:0
    5: 0:0
    

    Tip:

    See the sample input file BRM_Home/sys/data/config/pin_telco_svc_order_state.

    After you load this file, a single instance of /config/telco/service_order_state is created.

  7. Define provisioning tags, service features, and account- and service-level extended rating attributes (ERAs) in a text file and load it with the load_pin_telco_tags utility.

    The following sample provisioning tags entry is in an input file for a service called cellular:

    provisioning_tag        "/config/telco/cellular"        "Voice Add On Corporate Plus: Promotions and
    SS"    "Promotion and SS (currently: MPTY and F&F)" "y"
    features                "MPTY"
    service_era             "FRIENDS_FAMILY" 12 13 "n"
    service_era             "HOME_REGION"   14 15 "y"
    account_era             "SPECIAL_DAY"   2 3
    

    After you load this file, a single instance of /config/telco/service_name and /config/account-era is created.

This completes creating and loading configuration files.

Modifying Policy Files

You may need to modify some policy opcodes to support your new service.

  1. Configure these subscription policy opcodes to load and validate tags for the new service:

    • PCM_OP_SUBSCRIPTION_POL_PURCHASE_PROD_PROVISIONING

    • PCM_OP_SUBSCRIPTION_POL_CANCEL_PROD_PROVISIONING

    • PCM_OP_SUBSCRIPTION_POL_GET_PROD_PROVISIONING_TAGS

      Tip:

      For examples, look for tag_fn_tcf functions and functions defined for /service/telco. Copy and extend these functions as required.
  2. Generate the facilities module fm_subscription_pol.so by using the make command and move the file to the BRM library.

  3. (Optional) Modify the PCM_OP_CUST_POL_PREP_INHERITED opcode to capture and process additional information for /service/telco/service_name.

  4. Generate the facilities module fm_cust_pol.so by using the make command and move the file to the BRM library.

  5. (Optional) Add any required code to a policy opcode and modify PCM_OP_TCF_POL_APPLY_PARAMETER to call it. See the PCM_OP_GSM_POL_APPLY_PARAMETER code for a service-specific example.

  6. Generate the facilities module fm_tcf_pol.so by using the make command and move the file to the BRM library.

  7. Stop and restart Connection Manager (CM). See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

    Tip:

    Set the log level to 3 to see if all the provisioning tags and features are loaded for /config/telco/service_name during startup.
  8. Define a pricing plan based on the extended service.

This completes policy file modifications.

Modifying Customer Center to Support Your New Service

This section describes how to configure Customer Center to support your new service.

Before modifying Customer Center service and device panels, you should read "About Customizing the Services Framework Manager Client".

Create Service Panels

  1. Create an extended service panel for any additional information needed for the service that is not already captured in the device panels. See "Creating Custom Service Panels".

  2. If you are using a device other than /device/num, create a panel for each device that will be associated with the service. See "Creating Custom Device Panels".

  3. Create a device search entry panel for each device. See "Creating Custom Device Search Panels".

  4. Create a device search results panel for each device. See "Creating Custom Device Search Results Panels".

Configure Customer Center by Using Configurator

To configure Customer Center:

  1. Start Configurator. See "Using Configurator to Configure Customer Center" in BRM Developer's Guide.

  2. Specify any extended service panels and configure layout options by using Service Configurator. See "Telco Service Configurator".

  3. Specify any device panels and configure layout options by using Device Configurator. See "Telco Device Configurator".

You can now create accounts for the new service using the price plan defined earlier. You can see service orders being generated by using Event Browser.

Note:

You do not need to modify the History and Promotion panels to support your new service. When you view the history of a device, the device type is automatically passed in. This enables you to view the history of any device associated with any service without any customization. The Promotion panel automatically displays all account- and service-level ERAs belonging to an account.

Testing Provisioning by the Network Simulator

You can test provisioning of your services by using the Network Simulator. See "Testing Provisioning Using BRM Network Simulator".