4 Provisioning Non-Telco Services by Using Services Framework

This document describes how to set up services framework for provisioning non-telco services in Oracle Communications Billing and Revenue Management (BRM).

Topics in this document:

• Specifying the Non-Telco Services Supported by Services Framework

• Customizing the Provisioning Mode Based on Service Order Attributes

• Setting a Timeout Value for Requests Sent in Confirmed Mode

See also:

• About Provisioning

• Setting Up Provisioning for GPRS Services

• Implementing Provisioning Tags for Telco Services

• Testing Provisioning Using BRM Network Simulator

• About XML Provisioning

Note:

• For telco services, use Services Framework Manager to define provisioning tags in most cases. You must use Services Framework Manager if the provisioning tag creates supplementary services or service extensions. See "Provisioning Telco Services by Using Services Framework Manager".

• For non-telco services, the provisioning tag framework is the recommended method of creating provisioning tags. However, you can also use Services Framework Manager to provision non-telco services. See "Provisioning Non-Telco Services by Using Services Framework".

Specifying the Non-Telco Services Supported by Services Framework

You specify the non-telco services supported by Services Framework by editing the pin_service_framework_permitted_service_types.xml configuration file. You then load the XML file into the BRM database's /config/service_framework/permitted_service_types object by using the "load_pin_service_framework_permitted_service_types" utility.

The pin_service_framework_permitted_service_types.xml file specifies the following for each supported service:

• The provisioning configuration object, which defines the fields to include in a service order.

• The service order configuration object, which specifies the service order state transitions.

• The provisioning mode: Queued or Confirmed.

  Note:

  You use the XML file primarily to configure your non-telco services, but you can use it to specify the provisioning mode for telco services. To do this, list only the telco service and the provisioning mode.

To specify the supported non-telco services, perform these tasks:

1. Open the BRM_home/sys/data/config/pin_service_framework_permitted_service_types.xml file in an XML editor.

2. For each non-telco service supported by Services Framework, add the following entries:

   1. Specify the supported non-telco service on the ServiceType line. For example, replace ServiceType with /service/cable.

      <ServiceType>ServiceType</ServiceType>
      

   2. Specify the provisioning configuration object to use on the ConfigTypeProvisioningDetails line. For example, replace ProvDetails with /config/telco/provisioning/cable.

      <ConfigTypeProvisioningDetails>ProvDetails</ConfigTypeProvisioningDetails>
      

      For information, see "About Adding Details to the Service Order".

   3. Specify the service order configuration object to use on the ConfigTypeServiceOrderState line. For example, replace SOstate with /config/telco/service_order_state/cable.

      <ConfigTypeServiceOrderState>SOstate</ConfigTypeServiceOrderState>
      

      For information, see "About Valid Service Order State Transitions".

   4. Specify the provisioning mode on the ProvisioningMode line. Replace Value with 0 for Queued mode and with 1 for Confirmed mode.

      <ProvisioningMode>Value</ProvisioningMode>
      

3. Save and close the file.

4. Use the following command to load the list of non-telco services into the database:

   load_pin_service_framework_permitted_service_types
   

   See "load_pin_service_framework_permitted_service_types".

   Note:

   This utility requires 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.

5. Stop and restart the CM.

To verify that the data loaded successfully, you can display the /config/service_framework/permitted_service_types object by using Object Browser or by using the robj command with the testnap utility. See "Reading an Object and Writing Its Contents to a File" in BRM Developer's Guide.

Customizing the Provisioning Mode Based on Service Order Attributes

By default, Services Framework assigns provisioning modes to events based on the service. You can customize Services Framework to assign the provisioning mode based on other attributes, such as service order details, by customizing the PCM_OP_TCF_POL_PROV_HANDLE_SVC_ORDER policy opcode. You can also customize the policy opcode to modify service order event details before they are published to the external provisioning agent.

You customize the policy opcode to find events with specific flist fields, assign the appropriate provisioning tag and change service order details, and then return the provisioning mode in the PIN_FLD_MODE output flist field.

Setting a Timeout Value for Requests Sent in Confirmed Mode

When provisioning service orders in Confirmed mode, dm_prov_telco waits for a response from the external provisioning agent before activating the service in the BRM database. If the external provisioning agent encounters an error or fails, dm_prov_telco might have to wait indefinitely. To prevent this problem, you can configure dm_prov_telco to close the connection and roll back the transaction if the wait exceeds a specified amount of time.

To specify a timeout value, perform these tasks:

1. Open the dm_prov_telco configuration file (BRM_home/sys/dm_prov_telco/pin.conf) in a text editor.

2. Set the prov_timeout entry to the amount of time, in seconds, that dm_prov_telco waits for a response from the external provisioning agent before timing out. For example, to set the timeout value to 30 seconds, enter the following:

   -dm_provision prov_timeout 30
   

   By default, the timeout value is set to 20. If you specify 0, dm_prov_telco waits an infinite amount of time for the external provisioning agent to respond.

3. Save and close the file.

4. Stop and restart dm_prov_telco.