1. Policy and Charging Application
  2. Configuration
  3. PCA Configuration
  4. Online Charging DRA Configuration
  5. OCSs
  6. Deleting an OCS

Deleting an OCS

Use this procedure to delete an OCS.

This procedure describes the recommended steps for deleting an OCS from a Policy and Charging configuration. In this procedure, OCS refers to a Diameter peer of the PCA, which is sometimes referred to as an OCS Front-end.

The OCS procedure minimizes disruption to policy signaling by:
  • Preventing sessions from creating new bindings to an OCS that has been removed
  • Allowing sessions with existing bindings to continue to use an OCS that has been removed until those sessions terminate normally

The procedure describes the recommended steps for deletion of an OCS from a Policy and Charging configuration. In this procedure, OCS refers to a Diameter peer of the PCA, sometimes referred to as an OCS Front-End.

Note:

The PCRF removal procedure is restricted to SOAM servers.
  1. Use Diameter, and then Configuration, and then Peer Nodes from the SOAM GUI screen to determine the Peer Node name of the OCS(s) being removed.
  2. Use Diameter, and then Configuration, and then Route Groups from the SOAM GUI screen to filter by Peer Node with the corresponding Peer Node name of the OCS. This will display only the Route Groups that are associated with the OCS.
  3. From the same GUI screen, determine if there are any Route Groups that contain other Peer Nodes in addition to the OCS to be removed.
    There are generally at least two Route Groups for each OCS. One Route Group with only the specified OCS peer, and one or more Route Groups with the specified OCS peer plus other OCS peers. The goal is to leave the route group with only the specified OCS peer, but delete the OCS peer from the other route groups. This allows routing for existing bindings to the OCS peer, but prevents alternate routing to the OCS peer.
  4. From the same GUI screen, edit each of the determined Route Groups and remove the OCS/OCS Front-End Peer Nodes from the Route Group.
    This prevents alternate routing selection of the OCS peer being removed.
  5. Use Policy and Charging, and then Configuration, and then Online Charging DRA, and then OCSs from the SOAM GUI screen to delete the OCS.
    This prevents new Bindings from using the OCS peer being removed.
  6. After enough time has elapsed such that all Diameter sessions that could be bound to the OCS peer should have terminated normally, use Main Menu, and then Policy and Charging, and then Configuration, and then Online Charging DRA, and then OCSs on the SOAM GUI screen to delete the route group containing only the OCS peer being removed.
  7. Use Diameter, and then Maintenance, and then Connections from the SOAM GUI screen to find the connection for the OCS Peer Node and disable it
  8. Use Diameter, and then Maintenance, and then Connections from the SOAM GUI screen to delete the connection to the OCS Peer Node.
  9. Use Diameter, and then Configuration, and then Peer Nodes from the SOAM GUI screen to delete the Diameter Peer Node for the OCS being removed.