Charging rule install avp

Field Summary Fields inherited from interface org. The elements in the given array are ChargingRuleDefinition objects. Note: the array must not be altered by the caller following this call, and getChargingRuleDefinitions is not guaranteed to return the same array instance, e. The elements in the given array are byte[] objects.

Note: the array must not be altered by the caller following this call, and getChargingRuleNames is not guaranteed to return the same array instance, e. The elements in the given array are String objects. Note: the array must not be altered by the caller following this call, and getChargingRuleBaseNames is not guaranteed to return the same array instance, e.

The Match Lists will be downloaded in a local machine. Importing Configuration Object Files. The Upload option appears on the screen. Attention : This import strategy can result in object inconsistency. For example, if you import a ZIP file that only contains traffic profiles, all the traffic profiles are deleted first. However, if existing policies depend on the existing traffic profiles, and the import file does not contain them, the policies can become invalid.

The configuration objects and their configuration settings are imported into the database. After the import is complete, the window reports the results for each json file contained in the ZIP file. Exporting All Configuration Object Files. The Export All option appears on the screen. Previous Next JavaScript must be enabled to correctly display this content.

The login page opens. Enter your Username. Enter your Password. Click Login. Tha main page opens. Configuring Services and Manageable Objects This section describes how to create and manage the services and manageable objects that are available to be used in policies.

A charging server is an application that calculates billing charges. The Charging Server Management screen appears. The Create Charging Server page opens.

The name can only contain the characters A through Z, a through z, 0 through 9, period. Free-form text that identifies the charging server within the network. Enter up to characters. The FQDN fully qualified domain name assigned to the charging server.

The charging server is displayed on the Charging Server Management page. Note: Use pencil icon or trash bin icon available in the next column to edit or update the created charging server. The supported outgoing Diameter messages set or remove third-party AVPs. Note: The Diameter messages listed are examples only. There are many messages associated with Diameter. A third-party AVP is identified by a unique identifier in the following format: name : vendorId. The name can only contain the characters A—Z, a—z, 0—9, period.

The maximum length is characters. To add a vendor to the list, see Managing Custom Vendors. Note: This box is checked automatically if the value of the vendor ID is not 0. The AVP is created. Creating a Custom Vendor To create a custom vendor:. The Custom Vendor Management screen appears. The Create Custom Vendor page opens. The vendor is created. Modifying a Custom Vendor To modify a custom vendor definition:. The Custom Vendor Management page opens in the work area, listing the defined vendors.

For a description of the fields contained on this page, see Creating a Custom Vendor. The Vendor is modified. Deleting a Custom Vendor You cannot delete a custom vendor definition that is used in a CoA template. To delete a custom vendor definition:. The custom vendor definition is deleted. Note: Media Profiles is a function that is applicable to Cable mode only.

The Media Profile Management screen appears. The Create Media Profile page opens. Enter a string of up to characters. Valid payload numbers range from 0 through Enter -1 to indicate an unknown payload number. The valid range is an integer from 1 through KHz. This is the length of time represented by one audio frame. A single RTP packet may contain multiple audio frames.

The bitrate is calculated using the frame size in milliseconds, the frame size in bytes, and the packetization time. The valid range is 0 through ms. This is the size represented by one audio frame. The valid range is 1 through 1, bytes.

The valid range is 1 through The media profile is created. Note: Use pencil icon or trash bin icon available in the next column to edit or update the created media profile. Session Viewer The Session Viewer displays detailed session information for a specific subscriber. The Session Viewer page appears. From the Identifier Type drop-down menu, select the identifier type for the selected session type. Click Query. Information about the subscriber session s is displayed.

The Core Service screen appears. Click Edit to edit the core service configurations. This enables the Add button in Advance Settings group.

Click Add. The Add Advanced Settings window opens. Enter the values in Key and Value fields. Click Save. The Policy Runtime Environment screen appears. Click Edit to edit the settings.

Enter the value in Log Level field. The default value is WARN. Click Add in the Supported Services group. The Add Supported Services screen appears.

Enter the following information to create service: Service Name : Enter the service name. Service Label : Enter the service label. The services get listed in the Supported Services list. The supported services are pcrf-core and pds. Note: Use Edit or Delete buttons available in the next column to update or delete the services. Click Create. The Create Project window opens.

In the Name field, enter the name for the project. In the Description field, enter the description for the project. In the Service Type , select the service from list of services already created in Settings section. The policy project is created. Select the policy project created and click Open. This opens a Blockly editor. The policy for the selected policy project is created.

Managing State Variables State Variables are set within a policy action to be used at a later time during policy rule execution in either conditions or actions. The names of these variables are not predefined and are determined at the time of creation. State variables have a scope which determines how long the value persists after it is set. The scopes are: Subscriber Policy Evaluation State Variables — This variable exists locally and has a value as long as the associated subscriber has at least one session.

After the last session is terminated these variables no longer have value and will no longer be available for use in policies.

Session State Variables — This variable has a value that is saved as long as the session the variable is associated with is still valid. After the session is terminated, this variable no longer has value and will no longer be available for use in policies.

Policy Evaluation State Variables — This variable are available for the lifetime of a policy evaluation cycle the process of evaluating all the policies for a single request or context Data Source State Variables — Note: State Variables are only supported for Session Management service.