For each Online Charging System the SAPC needs to communicate with, provision the charging profile in the /profiles/online-charging-system/<profileId> URI in the provisioning REST API with the following attributes:

• Set profileId attribute with a charging profile name

• Set serverRealm attribute to the realm of the Online Charging System

• Set syVersion attribute to specify the Sy interface version to use:

  • Value 0: 3GPP standard Sy interface.

  • Value 1: Ericsson Sy interface.

An example to configure an Online Charging System is the following:

Example 1   Configuration of Charging Systems

PUT /profiles/online-charging-system/OcsWestMadrid

{
	"profileId" : "OcsWestMadrid",
	"serverRealm" : "ocs3gpprealm.com",
	"syVersion" : 0
}

Subscribers can be provisioned only in Charging Systems without the need of provisioning corresponding resources in the SAPC database. In this case, the following configurations (for the SAPC to initiate communication towards a Charging System) apply:

• Policies for dynamic Charging System selection as described in Configure Policies for Dynamic Charging System Selection

• Or the default configuration as described in Configure Default Charging System.

In this case, the resulting Subscriber profile is a combination of the Subscriber data provisioned in the SAPC internal database (subscribers URI in the provisioning REST API) and the subscription information (Policy Groups and activation/deactivation time) obtained from Charging System.

The mapping between the Policy Groups obtained from Ericsson Sy interface and the SAPC Subscriber Group is needed in case it is needed to associate some static qualification data that characterize such group.

In this case, the following configurations (for the SAPC to initiate communication towards a Charging System) apply:

• Provisioning Charging System at Subscriber profile described in Provisioning at Subscriber Profile

  Note:

  This option does not apply in case Autoprovisioning (refer to Configuration Guide for Subscription and Policies) is enabled in the SAPC.

• Policies for dynamic Charging System selection as described in Configure Policies for Dynamic Charging System Selection

• Or the default configuration as described in Configure Default Charging System

To assign statically a Charging System to a subscriber:

• Add a value that corresponds to the profileId attribute in the/profiles/online-charging-system/<profileId> URI in the provisioning REST API to the onlineChargingSystemProfileId JSON attribute inside the staticQualification attribute in the subscriber URI in the provisioning REST API.

The following example shows how to associate a particular Charging System for a single subscriber:

Example 2   Provisioning of Subscriber

 
PUT /subscribers/34600320101

{
	"dataplans" : 
	[
		
		{
			"dataplanName" : "MobileBroadband"
		}
	],
	"staticQualification" : 
	{
		"onlineChargingSystemProfileId" : "OcsWestMadrid"
	},
	"subscriberId" : "34600320101"
}


PUT /dataplans/MobileBroadband

{
        "dataplanName" : "MobileBroadband"
}

To avoid communication with any Charging System for a subscriber provisioned in the SAPC, use a <charging system name identifier> in the onlineChargingSystemProfileId JSON attribute inside the staticQualification attribute in the subscribers URI in the provisioning REST API that does not correspond to any existing entry of the /profiles/online-charging-system/<profileId> URI in the provisioning REST API.

Example 3   Provisioning of Subscriber

 
PUT /subscribers/34600320102

{
	"staticQualification" : 
	{
		"onlineChargingSystemProfileId" : "NoOcs"
	},
	"subscriberId" : "34600320102"
}

It is possible to use flexible conditions to assign a Charging System to Subscribers in the SAPC, by using Charging System policies.

To configure policies for Charging System selection, configure the following objects:

• For Global policy locator, use the following REST URI: /locators/resources/any/contexts/charging-system

• Within the outputAttributes attribute in the /rules/<ruleId> URI in the provisioning REST API set:

  • attrName attribute to charging-system.

  • attrValue with the alias used in /profiles/online-charging-system for this OCS, for example "OCS_1"

Figure 2 shows an example of selection of OCS using policies.

Figure 2   Configuration for Charging System selection based on IMSI

Figure 2 shows an example for the SAPC configuration for the following case: a postpaid Charging System has to be selected for subscribers whose first IMSI character matches certain number; and other Charging System applies for the rest of subscribers.

The following example completes the configuration for Figure 2.

Example 4   Configuration of default Charging System

PUT /rules/r_0

{
	"condition" : "(firstCharsOf(AccessData.subscriber.imsi, 1) == \"2\")",
	"outputAttributes" : 
	[
		
		{
			"attrName" : "charging-system",
			"attrValue" : "\"OCS_postPaid\"",
			"result" : "permit"
		}
	],
	"ruleName" : "r_0"
}


PUT /rules/r_1

{
	"condition" : "(firstCharsOf(AccessData.subscriber.imsi, 1) != \"2\")",
	"outputAttributes" : 
	[
		
		{
			"attrName" : "charging-system",
			"attrValue" : "\"OCS_prePaid\"",
			"result" : "permit"
		}
	],
	"ruleName" : "r_1"
}


PUT /policies/pGlobal

{
	"policyName" : "pGlobal",
	"ruleCombiningAlgorithm" : "permit-overrides",
	"rules" : [ "r_0", "r_1" ]
}


PUT /locators/resources/any/contexts/charging-system

{
	"policies" : [ "pGlobal" ]
}

PUT /profiles/online-charging-system/OCS_postPaid

{
	"profileId" : "OCS_postPaid",
	"serverRealm" : "ocsrealm.com",
	"syVersion" : 1
}


PUT /profiles/online-charging-system/OCS_prePaid

{
	"profileId" : "OCS_prePaid",
	"serverRealm" : "newocsrealm.com",
	"syVersion" : 1
}

To configure a default entry that applies to all subscribers without any static Online Charging System qualification, configure the profileId attribute with the "default" value in the /profiles/online-charging-system URI in the provisioning REST API as follows:

Example 5   Configuration of default Charging System

PUT /profiles/online-charging-system/default

{
	"profileId" : "default",
	"serverRealm" : "newocsrealm.com",
	"syVersion" : 1
}