The DCCA App tab is used to define the method for choosing attributes for messages sent by the Client, including the type of used units reported and the amount of usage reported in every CCR.
MSCC (Vendor Variant 1) MSCC Tab
|
|
MSCC (Vendor Variant None) MSCC Tab |
|
Credit Reported (Vendor Variant None) |
Measurements collected for Diameter Base related processing are reported on the Diameter DCCA Node report tab. Credit Control measurements are reported on the DCCA report tab.
DCCA Test |
The DCCA Test is available only when Vendor Variant is None on the Test Configuration tab. Use the drop-down list to select whether the DCCA test is a One Time Event or Session Based. Selecting the option as a One Time Event makes all the parameters on this tab unavailable. |
||||||||||||||||||
CCR-T Delay on Terminated MSCCs (s) |
Use to configure a delay for the CCR-T Delay on Terminated MSCCs ensure that the Server has time to send RAR message.
Enter the number of seconds to wait before the session is terminated via CCR-T after receiving FUI (Final-Unit-Indication) AVP on all MSCCs. A zero value indicates that session will be immediately terminated via CCR-T once all MSCCs are in terminate state. Tcl Parameter: DiaClnCcCcrtDelayOnMscc Options: 0 - 65535 Default: 0 |
||||||||||||||||||
Default CCF-Handling |
Use the drop-down list to select the default failure handling mode for the Client node when Dedicated SUTs are defined. Options: Terminate, Continue, or Retry-Terminate Default: Continue Tcl Parameter: DiaClnCcfHandling
|
||||||||||||||||||
Default Failover |
When the SUT configuration includes a secondary server or proxy, you can use the drop-down list to enable or disable failover support. Options: Supported or Not Supported Default: Supported Tcl Parameter: DiaClnCcFailover Failure HandlingThe server SUT may notify the Client node whether it supports failover with the CC-Session-Failover AVP, and it may instruct the node how to handle temporary or transport layer failures with the Credit-Control-Failure-Handling AVP. If the server does not include either or both AVPs in a CCA, the node's default behavior is governed with the following settings. If the server does include the AVPs, the values received will override the default behavior. |
||||||||||||||||||
MSCC |
The type of credit requested with the initial CCR and the actual credit usage that is reported by the Client with every update and termination CCR are defined in the Multiple Services Credit Control (MSCC) pane. The MSCC AVP is always included unless you check the Request Service Unit At Message Level box. A sub-tab is displayed for each MSCC, and the Client node will only report usage against a Rating Group if the DCCA SUT grants credit units for that group. |
||||||||||||||||||
Number of MSCCs |
Use the drop-down list to select the maximum number of MSCC AVPs.
Separate sub-tabs, labeled MSCC n, are displayed for each MSCC configuration. Options: 1 — 10 Default: 1 Tcl Parameter: DiaClnNumMscc
|
||||||||||||||||||
Multiple Services Support |
Use the Multiple Services Support checkbox to indicate Multiple Services Support during DCCA testing (RFC-4006).
Tcl Parameter: DiaClnCcMssEn Type: True, False Default: True
|
||||||||||||||||||
Include All MSCCs in Update Message |
Use this checkbox to include all the Multiple-Service-Credit-Control (MSCC) AVP in the update message. (The MSCC AVP is in the Credit Control Answer (CCA) sent from the DCCA). This parameter is available only when Vendor Variant is None on the Test Configuration tab. Tcl Parameter: DiaClnCcUpdateAllMsccsEn
|
||||||||||||||||||
Include Rating Group ID |
The identifier of the Rating Group associated with a credit service. Enter a valid Rating Group ID. Range: N/A Default: 1
|
||||||||||||||||||
AVP Configuration |
Click the View/Edit button to view or modify the RADIUS VSA or Diameter AVP configuration for the test.
|
||||||||||||||||||
AVP Database Size (bytes) |
AVP Database size for each Mscc configuration is set to zero by default. This buffer is used only when the auto increment is selected in the AVP Template and the AVP Database size should be large enough for holding the AVP Data. If the auto increment is not selected, the AVP Database size may be 0. DB Size (bytes) has been added to the VSA/AVP configuration window. This is the value the AVP Database estimator calculates that is required for the AVP Database size. It should be used when determining the size of the AVP Database Size in Bytes. Default: 0 Tcl Parameter: DiaClnMsccVsaDbSize_1
|
||||||||||||||||||
Max Num AVPs |
Enter the maximum number of AVPs that can be included in a CCR message. Tcl Parameter: DiaClnCcV1MsccVsaDbList_1
|
||||||||||||||||||
Apply Test Data File to AVP Configuration |
See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter: Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.
Tcl Parameter: DiaClnMsccCfgFileEn_1
|
||||||||||||||||||
Include Service IDs |
Use the checkbox to include the service identified in the Service-Identifier AVP. The specific service the request relates to is uniquely identified by the combination of Service-Context-Id and Service-Identifier AVPs. Tcl Parameter: DiaCInCcV1ServiceIdEn_1
|
||||||||||||||||||
Number of IDs |
Select the number of Service IDs to be included in the AVP. Range: 1 - 10 Default: 1 The number of tabs displayed for you to enter a Service ID, depends on the value you select from the Number of IDs dropdown list.
|
||||||||||||||||||
Update Time Interval |
The number of seconds the Client will wait, after receiving a credit grant for the Rating Group, before sending an update CCR reporting credit usage for the group. This timer also controls the interval spacing of subsequent update CCR messages. This parameter is available only when Vendor Variant is 1 on the Test Configuration tab. Range: N/A Default: 60 Tcl Parameter: DiaClnUpdateTime_1 If the SUT includes the Validity-Time AVP in CCA messages, you can check the Use Server Validity Time box to override the defined Update Time Interval with the time specified by the server. |
||||||||||||||||||
Delay Quota Request |
When the box is checked, the Client will wait for the specified number of seconds before requesting a credit grant with this MSCC. Range: N/A Default: 5
|
||||||||||||||||||
Reporting Method |
Update and termination CCR messages can report usage by time, by volume, or both depending on your selections. If usage is reported for this Rating Group, the defined units and amounts are sent in every CCR. Report Time QuotaWhen this box is checked, the Client can report credit usage by duration with the CC-Time AVP. Use the radio buttons to define the number of seconds reported. Tcl Parameter: DiaClnCcV1RptTimeQuotaEn_1
Range: 1 — 100 Default: 100 Tcl Parameter: DiaClnCcPctTime_1
Range: N/A Default: 1000 Tcl Parameter: DiaClnCcNumSecs_1 Report Volume QuotaWhen this box is checked, the Client can report credit usage by volume with the CC-Total-Octets, CC-Input-Octet, and CC-Output-Octets AVPs. Use the radio buttons to define the total number of octets reported. The total is evenly divided between CC-Input-Octet and CC-Output-Octets. Tcl Parameter: DiaClnCcRptVolQuotaEn_1
Range: 1 — 100 Default: 100 Tcl Parameter: DiaClnCcVolPctVol_1
Range: N/A Default: 1000 Tcl Parameter: DiaClnCcNumOctets_1
|
||||||||||||||||||
Credit Reported |
The parameters in the Credit Reported pane allows you to select credit usage reported by Percent of Quota or Volume and define the usage reported in every update CCR.
Options: Percent Quota (0), Volume (1) Default: Percent Quota Tcl Parameter: DiaClnCcV1RptUsuMethod_1
Tcl Parameter: DiaClnCcV1TariffEn_1
Options: None (0), On Validity Time (1), On Trigger (2), Mix (3) Interval (s): 0 - 4294967295 Default: 10
|