The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
CPS Central allows service providers to create policies that are customized to their particular business requirements through the Policy Builder interface which is a web-based application with a graphical user interface (GUI) that enables rapid development of innovative new services.
Policy Builder interface supports both configuration of the overall CPS cluster of virtual machines (VMs) as well as the configuration of services and advanced policy rules.
Service configuration objects are used to drive the system.
Services, Service Options and Use Case Templates enable you to configure these objects.
A service is a code to label the service and a collection of Service Options which define the service.
Multiple services can be assigned to a single subscriber where the service options are combined between all the assigned services.
Perform the following steps to create a new service:
Service Options provides concrete values which can be reused for multiple services.
The configurable values in a Service Option are set up by the Use Case Template object. The Use Case Template can provide defaults to the Service Option or hide values in Service Configuration objects based on the necessity of certain use cases.
The following parameters can be configured under Service Option:
Parameter |
Description |
---|---|
Name |
Name of the service option which is referenced by the Service. |
Use Case Template |
Link to view the associated Use Case Template. |
Service Configurations |
|
PreDefinedRule Parameters |
|
Add |
Select to add a parameter from the Use Case Template even if it is not marked as 'Allow Override'. It also allows customizing a parameter that didn't exist previously in the Use Case Template or was removed from the Service Option. |
Remove |
Select to remove a parameter from the Service Option. This means that the value specified for the Use Case Template's version of this parameter is used. |
Display Name |
Display Name of the parameter. It can be updated by either the Service Option or the Use Case Template. |
Value |
Value of the parameter to be set. |
Pull Value From... |
Enables setting this value dynamically through AVP's, Custom Reference Data or the 'Policy State'. |
Subscriber AVP Code |
Enables pulling values from AVPs on the subscriber. This field now also supports AVP's on the subscriber's session and 'Policy Derived AVP's added in policies. |
Custom Reference Data Column |
Enables pulling the value from the Custom Reference Data table's column specified. |
Bind to Session/Policy State |
Enables pulling the value from the state of the system. This uses any of the preconfigured 'Policy State Data Retrievers' that are plug-in code that know how to get a certain value from the system. |
Dynamic Reference Data Key |
Enables pulling the value from other reference data configuration (Policy Builder or CRD, for example, Account Balance Templates) as value for the use case attribute. Currently, only Account Balance Template type attributes are supported. The intended Account Balance Template code can be configured in the text field. Both Policy Builder and CRD Balance templates can be pulled using this field. Policy Builder templates are checked first, if not found then CRD templates are searched. |
Use case templates are the building blocks of the Policy Builder service model architecture that include the following functionalities:
Defines the Service Configuration objects to be set by a Service Option.
Provides default values and/or hides values based on a use case.
Enables service creation.
A copy of the Use Case Options is created while copying a Use Case Template.
The following parameters can be configured under Use Case Template:
Parameter |
Description |
---|---|
Use Case Initiators |
Group of conditions which indicate if the Service Configuration objects within a use case template are used. If no use case initiators are specified, the Service Configuration objects will always be added. |
Service Initiators (OR Together) |
Service Initiators are groups of conditions. If the service initiators on a Use Case Template is true then that Use Case template is active and the Service Configurations are used. When you add multiple Service Initiators, the Use Case Template is activated and Service Configurations are used when any one of these initiators is true, as indicated by the caption “OR Together”. The Plus/X keys enables the user add or remove a service initiator. The Up/Down arrow enables the user to move the initiators up and down. This affects the order in which the service initiators are evaluated. |
Name |
Name of the initiator. |
Actions |
|
Service Configurations |
|
Name |
Name of the Use Case Template which can be modified. |
Add |
Enables you to add a Use Case Template. |
Remove |
Enables you to remove a Use Case Template. |
Service Configuration Parameters |
Enables you add the Service Configuration objects needed to configure a use case. |
Display Name |
Display Name |
Value |
Value of the parameter to be set. |
Bind Field |
This is an internal field that should be modified only when requested by the BU and may be removed in future releases. |
Allow Override |
Indicates whether an option will be displayed for configuration in the Service Option by default. |
Create Child: Use Case Option |
Enables you to create a child use case option of a use case template. |
Copy: Current Use Case Template |
Enables you to create a copy the current Use Case Template. |
Documentation |
Enables you to write notes about the implementation for reference. |
For more information regarding Service Configuration Objects, refer to CPS Mobile Configuration Guide.
Reference Data provides access to configure various aspects of the system in order to make the system ready for operation and to provide settings and parameters that are referenced by policy rules across various services.
You need to define a system as it represents the customer deployment. The system represents a set of PCRF clusters that share the same session database.
Each system contains one or more clusters that represent a single high availability site environment. A cluster is used to define configurations related to the blades and shares the same set of policy directors. In Policy Builder, the Environment specific data section displays a list of system configurations that enables you to perform create, read, update, and delete (CRUD) operations and to create clusters which can further overwrite and customize system configurations.
Perform the following steps to configure a system:
Step 1 | Log in to the CPS Central. | ||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||
Step 3 | Select System (beta version) under Reference Data. | ||||||||||||||||
Step 4 | Click New System. | ||||||||||||||||
Step 5 | Enter the values
in each field as described in the following table:
| ||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to add clusters:
Step 1 | To add clusters, click Add Clusters. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Enter the
values in each field as described in the following table:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Save. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click
Done.
For field descriptions of system configuration templates, refer to Plug-in Configuration in CPS Mobile Configuration Guide. |
This section includes the following topics:
Diameter Clients enables you to create different clients based on the interface. The clients defined can be used to configure a policy so that different clients get different service configuration objects.
You need to create specific client that corresponds to your interface and if there is no specific client for your interface select the generic Diameter Clients. You can also use the diameter client to filter the service objects that are going to be used in a policy.
The interface specific diameter clients are built on top of the generic Diameter Clients. They add specific behavior and should always be used in the context of the specific interface.
CPS supports the following Diameter Clients:
Diameter Client: The generic diameter client object should be used for any interface that does not have a matching specific diameter client.
Gx Client: The specific diameter client object should be used only in relation with the Gx interface. It adds Gx specific features to the generic diameter client.
Rx Client: The specific diameter client object should be used only in relation with the Rx interface. It adds Rx specific features to the generic diameter client.
Gxx Client: The specific diameter client object should be used only in relation with the Gxx interface. It adds Gxx specific features to the generic diameter client.
Gy Client: The specific diameter client object should be used only in relation with the Gy interface. It adds Gy specific features to the generic diameter client.
Perform the following steps to create diameter clients:
Step 1 | Log in to the CPS Central. | ||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||
Step 3 | Select Diameter Clients under Reference Data. A Diameter Clients editor page is displayed with the following options:
| ||||||||||||||
Step 4 | To create diameter clients, select Diameter Client. | ||||||||||||||
Step 5 | Enter the values in each field as described in the following table:
| ||||||||||||||
Step 6 | Click Save. |
Perform the following steps to create Gx clients:
Step 1 | To create Gx clients, select Gx Client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Enter the
values in each field as described in the following table:
For more information, see CPS Mobile Configuration Guide. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to create Rx clients:
Step 1 | To create Rx clients, select Rx Client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Enter the
values in each field as described in the following table:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to create Gxx clients:
Step 1 | To create Gxx clients, select Gxx Client. | ||||||||||||||||||||||||
Step 2 | Enter the values in each field as described in the following table:
| ||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to create Gy clients:
Step 1 | To create Gy clients, select Gy Client. | ||||||||||||||||||||
Step 2 | Enter the values in each field as described in the following table:
| ||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to create Sy clients:
Step 1 | To create Sy clients, select Sy Client. |
Step 2 | Expand Sy Clients, and click Sy Client under Create Child in the Sy Clients Summary pane. |
Step 3 | Configure the client as needed. |
Step 4 | Set the
Counter
Lookahead Interval Minutes option to the number of minutes to look
ahead to determine when the lookahead balance states configured for the
SyServerSLRInformation service configuration object will expire, refresh, or
start. It is set to 180 minutes by default.
For more information, see CPS Mobile Configuration Guide. |
Diameter Defaults provides global default values for different modules of the system. There should be one object for each diameter default type.
CPS supports the following Diameter Defaults:
Gx Profile: Provides default values to be used for Gx default bearer QoS parameters as well as some specific behavior related to default bearer QoS.
Custom AVP Profile: Allows the service provider to extend the diameter dictionary with new vendor specific AVPs along with a source for that AVP and a destination where the AVP is used. It consists of the following components:
MPS Profile: Provides MPS attributes required for priority service provisioning. The priority level value from service configuration takes precedence over MPS Profile value.
Rx Profile: Provides default values and specific values to be used by the different QoS parameter mapping functions at PCRF as per 3GPP TS 29.213. Also provides a mechanism to authorize the Rx IMS sessions.
Sd Push Rules: Supports the Sd solicited reporting scenario when the TDF-Information grouped AVP is not sent from the PCEF to the PCRF in a Gx CCR-i.
Time of Day Schedule: Allows different PCC rules to be installed on a per time-of-day basis. Based on the defined schedules PCRF will look ahead one scheduled interval every time the policy is re-evaluated and will schedule for each PCC rule an activation time using the Rule-Activation-Time AVP and de-activation time using the Rule-Deactivation-Time AVP.
For more information, see CPS Mobile Configuration Guide.
Perform the following steps to add Custom AVP Profiles:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Select Diameter Defaults under Reference Data. A Diameter Defaults editor page is displayed with the following options: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | To add custom AVP profiles, select Custom Avp Profile. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Enter the
values in each field as described in the following tables:
Avp Mappings The custom AVP mapping includes the following mappings:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to add Gx profiles:
Step 1 | To add Gx profiles, select Gx Profile. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Enter the values
in each field as described in the following table:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to add Mps profiles:
Step 1 | To add Mps profiles, select Mps Profile. | ||||||||||||
Step 2 | Enter the values
in each field as described in the following table:
| ||||||||||||
Step 3 | Click Save. |
Perform the following steps to add Rx profiles:
Step 1 | To add Rx profiles, select Rx Profile. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Enter the
values in each field as described in the following table:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to add Sd Push Rules:
Step 1 | To add Sd Push Rules, select Sd Push Rules. | ||||||||||||||
Step 2 | Enter the values in each field as described in the following table:
| ||||||||||||||
Step 3 | Click Save. |
Perform the following steps to add Tod Schedules:
Step 1 | To add Tod schedules, select Tod Schedule. | ||||||||||||
Step 2 | Enter the values in each field as described in the following table:
| ||||||||||||
Step 3 | Click Save. |
The Rule Retry Profiles enables you to activate a retry timer with a number of retries for Traffic Detection functions that are INACTIVE. The number of retries and the timer interval between each retry can be configured.
Perform the following steps to create a rule retry profile:
Step 1 | Log in to the CPS Central. | ||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||
Step 3 | Select Rule Retry Profiles under Reference Data. | ||||||||||||||
Step 4 | To create a new rule retry profile, click Rule Retry Profile. | ||||||||||||||
Step 5 | Enter the values in each field
as described in the following table:
| ||||||||||||||
Step 6 | Click Save. |
This section includes the following topics:
An account balance is a group of quotas. You can create a balance (quota grouping) called Data and have several quotas defined such as Monthly, Top-up, and Bonus. When the subscriber uses a particular account, the usage is charged based on their Data balance and the MsBM determines which underlying quota should be debited based on rules set up in QNS.
The Quota templates defines the specifications of the quota. You can view existing account balance templates or create account balance templates with the available quota templates.
Perform the following steps to create an account balance template:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||||||||||||
Step 3 | Select Account Balance Templates under Reference Data. | ||||||||||||||||||||||||||||
Step 4 | To create account balance templates, click Account Balance Template. | ||||||||||||||||||||||||||||
Step 5 | Enter the values in each field as described in the following
table:
| ||||||||||||||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to create a one time quota template:
Step 1 | To create a one time quota template, click One Time Quota Template. | ||||||||||||||||||||||||||||||
Step 2 | Enter the values in each field as described in the following table:
| ||||||||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to create a recurring quota template:
Step 1 | To create a recurring quota template, click Recurring Quota Template. | ||||||||||||||||||||||||||||||||||||||||||
Step 2 | Enter the
values in each field as described in the following table:
| ||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Save. |
Perform the following steps to create a rollover quota template:
Step 1 | To create a rollover quota template, click Rollover Quota Template. | ||||||||||||||||||||||||||||
Step 2 | Enter the
values in each field as described in the following table:
| ||||||||||||||||||||||||||||
Step 3 | Click Save. |
Tariff Times is the CPS nomenclature for defining rates. Rates provide a mechanism to alter a quota that is billed.
You can view existing tariff times and create a new Tariff Time.
Perform the following steps to create a new tariff time:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||||||
Step 3 | Select Tariff Times under Reference Data. | ||||||||||||||||||||||
Step 4 | To create a new tariff time, click Tariff Time. | ||||||||||||||||||||||
Step 5 | Enter the values
in each field as described in the following table:
| ||||||||||||||||||||||
Step 6 | Click Save. |
This section includes the following topics:
Search Table Groups enables logical grouping of multiple customer reference data tables.
Parameter |
Description |
---|---|
Name |
Name of the Search Table Group. |
Evaluation Order |
Order in which groups get evaluated, starting with 0 and going higher. |
Result Columns |
These are the AVPs that will be added into processing. These need to be mapped to be the same as values from underlying tables. This allows populating the same AVPs from different tables. |
Name |
Name of the AVP. It should start with alphanumeric characters, should be lowercase, and should not start with numbers, no special characters are allowed, use "_" to separate words. For example, logical_apn = GOOD, logicalAPN = BAD, no_spaces |
Display Name |
More human readable name of the AVP. |
Use In Conditions |
Represents the availability of the row for conditions in Policies or Use Case Templates. There is a performance cost to having these checked, so it is recommended to uncheck unless they are required. |
Default Value |
The default value if no results are found from a Customer Reference Data Table. |
Table Search Initiators (OR Together) |
This section controls whether or not the Search Table Group and all tables below will be executed. |
Name |
Name of the table search initiators. |
Custom Reference Data Trigger is a group of conditions used to evaluate a table. This can be used to derive the same data in different ways depending on the conditions.
Parameter |
Description |
---|---|
Name |
Name of the table that will be stored in the database. |
Custom Reference Data Initiators (OR Together) |
Group of conditions that can be used to decide whether to evaluate a table or not. This can be used to derive the same data in different ways depending on conditions. |
Custom Reference Data tables define custom derived data for installation and to make decisions based on that data.
The following parameters can be configured under Custom Reference Data Tables:
Field |
Description |
---|---|
Name |
Name of the table that will be stored in the database. It should start with alphanumeric characters, should be lowercase or uppercase but not mixed case, and should not start with numbers, no special characters are allowed, use “_” to separate words. For example, logical_apn = GOOD, logicalAPN = BAD, no_spaces. |
Display Name |
Name of the table that will be displayed in Control Center. |
Cache Results |
Indicates if the tables should be cached in memory and should be checked for production. |
Activation Condition |
Custom Reference Data Trigger that needs to be true before evaluating this table. It can be used to create multiple tables with the same data depending on conditions or to improve performance if tables do not need to be evaluated based on initial conditions. |
Svn Crd Data |
When enabled, indicates that the CRD table is an SVN CRD table and CRD data for the table is fetched from CRD CSV file present in SVN data source. When disabled, indicates that the CRD table data needs to be fetched from Mongo database. |
Best Match |
When enabled, look-ups occur within a CRD table in the following order: |
Evaluation Order |
Indicates the order the tables within the search table group should be evaluated. Starting with 0 and increasing. |
Columns |
|
Name |
Name of the column in the database. |
Display Name |
More readable display name. |
Use In Conditions |
Represents the availability of the row for conditions in Policies or Use Case Templates. There is a performance cost to having these enabled, so it is recommended to disable unless they are required. |
Type |
Determines the values in the control centre as described below:
|
Key |
Indicates that this column is all or part of the key for the table that makes this row unique. By default, a key is required. Keys also are allowed to set the Runtime Binding fields to populate this data from the current message/session. Typically, keys are bound to data from the current session (APN, RAT Type) and other values are derived from them. Keys can also be set to a value derived from another custom reference data table. |
Required |
Indicates whether this field will be marked required in Control Center. A key is always required. |
Column Details |
|
Valid Values |
|
All |
All the values of the type selected by the user. |
List of Valid |
A list of name/display name pairs that will be used to create the list. Valid values can also contain a name which will be the actual value of the column and a display value which allows the Control Center to display use name. |
Name |
The name of the column in the database. |
Display Name |
Readable display name. |
Validation |
|
Regular Expression |
The Java regular expression that will be run on the proposed new cell value to validate it. |
Regular Expression Description |
A message to the user indicating what the regular expression is trying to check. |
Runtime Binding |
Runtime binding is how key column data gets filled out (bound) from data in the current session. There are multiple ways to bind this data and it is also possible to set an operator to define what should match (equals, less than, etc). |
None |
|
Bind to Subscriber AVP |
This pulls the value from an AVP on the subscriber. It will also pull values from a session AVP or a Policy Derived AVP. |
Bind to Session/Policy State |
This pulls the value from a Policy State Data Retriever which knows how to retrieve a single value for a session. |
Bind to a result column from another table |
This allows the key to be filled out from a columns value from another table. This allows 'normalizing' the table structure and not having on giant table with a lot of duplicated values. |
Bind to Diameter request AVP code |
This allows the key be filled out from an AVP on the diameter request. |
Matching Operator |
This allows the row to be 'matched' in other ways than having the value be 'equals'. Default value is equals. |
For more information, see CPS Mobile Configuration Guide.
This section includes the following topic:
LDAP Server Sets
The LDAP Server Set represents a connection to a logical set of LDAP servers that is reusable across Domain definitions.
You can create a new LDAP Server Set.
Perform the following steps to create a new LDAP Server Set:
Step 1 | Log in to the CPS Central. | ||||||
Step 2 | Click Policy Builder. | ||||||
Step 3 | Select LDAP Server Sets under Reference Data. | ||||||
Step 4 | To create a new LDAP Server Set, click Ldap Server Set. | ||||||
Step 5 | Enter the values in each field as described in the following
table:
| ||||||
Step 6 | Click Save. |
This section includes the following topics:
Notification enables sending messages to subscribers. Service Providers can use messages to alert the subscriber on issues and offers on their network.
The CPS for Mobile supports the following notification types:
Apple Push Notifications: To configure CPS to send a message to a subscriber with an Apple iPhone or other iOS device.
Email Notifications: To configure CPS to send an email notification to a subscriber.
SMS Notifications: To configure CPS to send a text notification to a subscriber.
Real Time Notifications: Realtime Notifications allows you to send SOAP/XML messages to a defined server when policy thresholds are breached.
GCM: Google Cloud Messaging enables you to send messages to a subscriber on an android device.
Perform the following steps to add an apple push notification:
Step 1 | Log in to the CPS Central. | ||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||
Step 3 | Select Notifications under Reference Data. | ||||||||||||||||
Step 4 | To create an apple push notification, click Apple Push Notification. | ||||||||||||||||
Step 5 | Enter the values
in each field as described in the following table:
| ||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to add an email notification:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||
Step 3 | Select Notifications under Reference Data. | ||||||||||||||||||
Step 4 | To create an email notification, click Email Notification. | ||||||||||||||||||
Step 5 | Enter the values in each field as described in the following
table:
| ||||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to add an SMS notification:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||||||||||||||||
Step 3 | Select Notifications under Reference Data. | ||||||||||||||||||||||||||||||||
Step 4 | To create an SMS notification, click SMS Notification. | ||||||||||||||||||||||||||||||||
Step 5 | Enter the values
in each field as described in the following table:
For more information of WAP Push configuration, refer to CPS Mobile Configuration Guide. | ||||||||||||||||||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to add a real time notification:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||||||||
Step 3 | Select Notifications under Reference Data. | ||||||||||||||||||||||||
Step 4 | To create an real time notification, click Real Time Notification. | ||||||||||||||||||||||||
Step 5 | Enter the values
in each field as described in the following table:
For more information, see CPS Mobile Configuration Guide. | ||||||||||||||||||||||||
Step 6 | Click Save. |
Perform the following steps to add a GCM notification:
Step 1 | Log in to the CPS Central. | ||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||
Step 3 | Select Notifications under Reference Data. | ||||||||||||||
Step 4 | To create a GCM notification, click GCM Notification. | ||||||||||||||
Step 5 | Enter the values in each field as described in the following
table:
| ||||||||||||||
Step 6 | Click Save. |
You can create domains to authorize a user, view existing domains and to perform CRUD on Domain.
Domain controls the authorization of a user. If a user is authorized, the domain can auto-provision a user in USuM (including a default Service). If a user is not auto-provisioned, the user is provisioned by an API into USuM before being assigned to a service on the network.
After logging in, you can go through a single domain authorization process. Your domain is determined by location and if it does not match any of the domains you will be marked as default.
Perform the following steps to create an authorized domain:
Step 1 | Log in to the CPS Central. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Select Domains under Reference Data. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | To authorize a domain, click Domains. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Enter the values
in each field as described in the following table:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | Click Save. |
The Advanced tab includes the following options:
The Advanced tab options should be used only under Cisco guidance. For further assistance and support:
Contact your Cisco Systems, Inc. technical representative.
Call the Cisco Systems, Inc. technical support number.
Write to Cisco Systems, Inc. at support@cisco.com.
The Import/Export option enables you to perform the following operations:
Export CPS Service Configuration into a single file
Import CPS Service Configuration to another environment.
For more information, see Export and Import Service Configurations in CPS Operations Guide.
You can view the SVN CRD data of a specific versioned CRD table under the Versioned Custom Reference Data option. The versioned CRD tables represents a combined list of custom reference data tables present under Custom Reference Data tables and different Search Table Groups whose Svn Crd Data checkbox is enabled.
Perform the following steps to view the CRD data of a versioned CRD table:
Step 1 | Navigate to Versioned Custom Reference Data under Policy Builder. |
Step 2 | To view details, select a versioned CRD table listed.
The versioned CRD table details is displayed. |
Perform the following steps to import CRD data of a versioned CRD table:
Step 1 | Navigate to Versioned Custom Reference Data under Policy Builder. |
Step 2 | Click Import option provided against the CRD table whose data you want to import.
The File to Import dialog box is displayed from where you can select a CSV file containing CRD data to be imported. |
Step 3 | Select a file. |
Step 4 | After the file is loaded, select Import.
File imported success message is displayed. |
The Experimental CRD visualization option under Policy Builder enables you to view Search Table Group relationships graphically. The nodes displayed are Search Table Groups and the links show where column data for a search table group is pulled from another table with the “Bind to a result column from another table” setting.
You can select an STG element, view its details in the Selected Info dialog box and save the layout.
STG displays the following information:
Layout nodes.
Switched display of STG elements to list STG result columns instead of CRD Columns.
Indicates columns in CRD tables under STG displaying ‘keys’ (key symbol) or ‘required’ (*).
Indicates where columns get their values from such as subscriber AVP, other CRD column, and session data field.
Note | This is a proof of concept (POC) feature and is subject to change at the sole discretion of Cisco. Accordingly, Cisco will have no liability in the failure of its functionality. |
Perform the following steps to view details of the STG element:
Step 1 | Log in to the CPS Central. | ||||||||
Step 2 | Select Experimental CRD visualization under Policy Builder. | ||||||||
Step 3 | To view details,
select an STG element.
The following details are displayed:
|
Policy Builder displays an option that enables you can view a list of repositories as follows:
Select Repository to navigate repositories list page, to view repository details and to reload configurations of the selected repository.
Select the drop-down to view the available repositories.
To switch to a new repository by selecting a repository from the dropdown list, user will have to re-login to authenticate the user with the selected repository.
Fields |
Description |
||
---|---|---|---|
Name |
Name of the repository |
||
URL |
URL of the branch of the version control software server that are used to check in this version of the data. |
||
SVN Username |
Username that is configured to view Policy Builder data. |
||
Temp Directory |
Temporary working local directory for the policy configurations. |
||
Reload Repository |
Select to reload the repository from the file system.
|
Perform the following steps to add a new repository:
Step 1 | In CPS Central,
navigate to
Policy
Builder Overview.
A Choose Policy Builder Data Repository dialog box is displayed. | ||||||||
Step 2 | Click
Add
Repository link.
| ||||||||
Step 3 | Enter valid
values.
| ||||||||
Step 4 | Click
OK.
|
When you select Policy Builder option in the CPS Central interface, a Choose Policy Builder Data Repository dialog box is displayed which enables you to select a repository.
Note | The dialog box to select a repository is displayed only if you have not loaded any repository earlier. In case any error occurs while loading the available repositories, an error dialog is displayed. When you click Close, the Central landing page is displayed. |
Perform the following steps to select a repository:
Step 1 | In CPS Central,
navigate to
Policy
Builder Overview.
A Choose Policy Builder Data Repository dialog box is displayed. | ||
Step 2 | Click the Select Repository drop-down. | ||
Step 3 | Select a repository from the drop-down list. | ||
Step 4 | Click
Done.
The selected repository is loaded.
|
Perform the following steps to switch repositories:
Step 1 | In CPS Central, navigate to Policy Builder Overview. | ||
Step 2 | Select the
Switch
Repository icon.
A Choose Policy Builder Data Repository dialog box is displayed.
| ||
Step 3 | Click the Select Repository drop-down. | ||
Step 4 | Select a repository from the drop-down list. | ||
Step 5 | Click
Done.
The selected repository is loaded.
|
Publish enables you to publish all the changes made in the Policy Builder.
Perform the following steps to publish changes:
Step 1 | Log in to the CPS Central. | ||||||||||||
Step 2 | Click Policy Builder. | ||||||||||||
Step 3 | Select Publish.
The following table describes the various URL/fields available in Publish:
|