Manage Fraud Protection Push Task Updates

Edit a Fraud Protection List Push Task

Note:

A push task can only be modified if its status is either PartiallyConfigured or NotScheduled.
  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab, select the Fraud Protection List (FPL) that you want to modify and click Edit.

    Note:

    If the push task cannot be edited because it is configured or you not have permission to modify it, this Edit button changes to View and the Edit FPL push task configuration pane is in read-only mode.
  3. In the Edit FPL push task configuration pane, you can modify the following fields:
  4. In the Device group tasks table and select the Network Function (NF) and click Manage to edit device in the push task.
  5. In the Select Device dialog box, expand a device folder in the Managed devices table, select a device row, and click Add to add an additional device or if you want to remove a device from the push task, select the device row and click Remove.

    The device, its network function and folder structure moves to the Targeted devices table and the folder structure is collapsed.

    • The device must be capable of using the fraud protection feature.
    • A push task is limited to one platform and software version at a time.
    • In the case of an HA device pair, the FPL push task is applied to both devices.

    Note:

    If you receive a Warning message that says the FPL file on the device you adding does not match the FPL that you are using for the push task, you must use Configuration Manager or the device ACLI to change the FPL file name on the device to match the FPL of your FPL push task in order for the FPL push task to be used with the device you are adding. Refer to the device documentation for more information about changing the FPL file name on the device.
  6. Repeat the previous steps to add or remove additional targeted devices. Up to twenty devices can be added to a push task.

    Note:

    Device filtering is applied after the first device is selected.
  7. Click OK. The device(s) appear in the Device group tasks table, which displays the network function (NF) name and its device(s).
  8. Click Apply.
  9. In the success dialog box, click OK.
    The changes that you made appear in the FPL push tasks table.

Commit a Fraud Protection List Push Task Manually

A Fraud Protection List (FPL) push task can be committed manually if the Auto commit checkbox is not checked in the FPL push task configuration pane.

  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab and select an FPL push task from the FPL push tasks table and click Commit.
  3. In the confirmation dialog box, click Yes.
  4. Click Refresh to confirm the FPL push task status changed from Success to Committed.

Update Fraud Protection List Changes Manually When Automatic Updates are Enabled

When the Fraud Protection Manager is configured to automatically push notifications to devices, any user changes made to a Fraud Prevention List (FPL) are delivered to the devices on the next incident reported by the FDP that is registered to the FPL.

For changes that need to be pushed to the device immediately, use the following procedure to manually push changes.
  1. Stop the automation on the current FPL push task.
  2. Expand the Fraud Protection Manager slider and click Fraud protection list.
  3. Click the Device association tab, select the Fraud Protection List (FPL) that you want to modify and click Edit.
  4. Make the necessary changes to the FPL.
  5. In the Edit FPL push task configuration pane, set the Task type drop-down list to On demand.

    This pushes your FPL changes to the device.

  6. Create a new automatic FPL push task once the manual push task completes. For details on creating an FPL push task, see "Add a Fraud Protection List Push Task".

Stop Fraud Protection List Push Task Updates

Until the FPL push task is committed, you can stop it and perform a rollback to restore the original configuration settings if the push task is in a WaitStarting, Failed, Success or Scheduled state.

  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab, and select the FPL push task that you want to roll back from the FPL push tasks table and click Abort.
  3. In the confirmation dialog box, click Yes.
After an FPL push task with a Failed or Success state is aborted; all changes on all targeted devices are rolled back to their previous state before the FPL push task was executed. If the FPL push task was in a WaitStarting or Scheduled when it was aborted, the FPL push task status changes to NotScheduled.

Copy a Fraud Protection List Push Task

When a Fraud Protection List (FPL) push task is executed successfully, it cannot be modified, which includes adding devices. However, you can copy an existing FPL push task and save it as a new FPL push task. The new FPL push task can then be applied to a different set of devices. Copies of an FPL push task can be used to divide large numbers of devices into smaller groups of devices that repeat the same push task.

  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab, and select the FPL push task that you want to copy from the FPL push tasks table and click Copy.
  3. In the Copy FPL push task configuration pane, provide a new name for the push task and make any other changes for the new FPL push task. See the Edit a Fraud Protection List Push Task section for more information about modifying these parameters or adding or removing devices.
  4. Click Apply.
  5. In the success dialog box, click OK.
    The changes that you made appear in the FPL push tasks table.

Resubmit a Device Group Push Task

You can resubmit a push task to start execution for the targeted device group network function (NF) if the status of the push task is in the Failed, ResetToReady, or RollbackFailed state.

Note:

You must wait for the running push task to complete before you can resubmit it. A warning appears if you try to resubmit a push task that is currently running.
  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab to access the Fraud Protection List (FPL) push task information.
  3. In the Device group tasks table, select the push task row and click Resubmit.

View Fraud Protection List Push Task Information

  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab to access the Fraud Protection List (FPL) push task information.
  3. In the FPL push tasks table, the following column information displays all the push tasks configured in SDM:

View Device Group Push Tasks

The Device group tasks table displays a summary of a the best-effort device tasks that are launched or scheduled to be launched in parallel for the selected push task in the Fraud Protection List (FPL) push tasks table.

Note:

Oracle Communications Session Delivery Manager (SDM) uses a prefix name plus the name of the applied FPL configuration XML file as the compressed file name that is pushed to the device to replace the FPL file on the device. The syntax of the file is as follows: OCSDM_<globalID>_<FPLFilename>.xml.gz, where the globalID is the unique global identifier that is specified during the SDM installation, and the FPL file name. For example, OCSDM_EastCluster_FPLConfig.xml.gz.
  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab to access the Fraud Protection List (FPL) push task information.
  3. In the Device group tasks table, view the following column information:
    Name Description
    Network function The name of the network function (NF) to which the device(s) belong.
    Device group The device group name.
    Status A device task can have the following status:
    • Ready—The push task is ready to run and waiting for the SDM scheduler to initiate the push task to start on the device.
    • ResetToReady— When the push task restarts, all the failed tasks are reset to this state to distinguish the initial Ready state of the device task.
    • Starting—The intermediate state between the Ready and Running states when users submit or resubmit the device task.
    • Running—The push task started and is currently processing.
    • Success—The push task completed successfully.
    • Failed—The push task failed during execution and any changes are rolled back.
    • RolledBack— The push task is rolled back successfully.
    • RollBackFailed—The push task is rolled back unsuccessfully.
    Start time The SDM server start date and local time at which the push task was scheduled to start or the time when a task within a push task is started. The following criteria are used:
    • If the push task has not reached its scheduled start time to start all individual tasks for this push task to display the same start time.
    • When an individual push task starts, it replaces the scheduled start time with the time it started processing.
    End time The end time is the server local time when the following conditions occur for this device task:
    • The device task finished successfully and paused.
    • A failed condition has been met and the device task stopped as a result of the failure.

    Note:

    If any one of the devices fail to do FPL file updates, then the device is automatically rolled back to the original FPL file.
  4. (Optional) Click Refresh to update the contents in the Device group tasks table.
  5. (Optional) Select an NF from the Device group tasks table and click Logs to view logs for the targeted device group node. Logs are maintained separately for each device group in the table.

Search for a Fraud Protection List Push Task

Refer to the Fraud Protection Manager Search Filters section for more information on filtering when you use a search criteria.

  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab, click Search.
  3. In the FPL push task search dialog box, complete any of the following fields:
  4. Click OK.

Delete a Fraud Protection List Push Task

A Fraud Protection List (FPL) push task can be manually deleted only if it is in the PartialConfigured, NotScheduled, Aborted, or Committted state.

  1. Expand the Fraud Protection Manager slider and click Fraud protection list.
  2. Click the Device association tab, and select the FPL push task from the FPL push tasks table and click Delete.
  3. In the confirmation dialog box, click Yes.