1. Diameter Custom Application User Guide with UDR
  2. DSA Tables
  3. TimeDistChk_Config Table
  4. Additional Provisioning Rules

Additional Provisioning Rules

Basic input data validation is done using the DCA Framework’s Configuration Data Provisioning GUI. Apart from that, below additional validation is performed during DSA business logic script compilation. If validation fails, the compilation also fails and Event #33309 is raised with appropriate error text. For script compilation, refer to the DCA Programmer’s Guide.

  • If Time-Distance Check (TimeDistChk) countermeasure is provisioned in Security_Countermeasure_Config Table and MCC_Or_VPLMNID configured in System_Config_Options Table is VPLMNID_Based, then this table cannot be empty. At least one entry needs to be provisioned.
  • Each Node_ID_1 and Node_ID_2 combination must be unique. No duplicate Node_ID_1 and Node_ID_2 combination is allowed. Not even by swapping Node_ID_1 and Node_ID_2 values.

    For example, an entry with Node_ID_1=10 and Node_ID_2=20 and another entry with Node_ID_1=20 and Node_ID_2=10 is not allowed.

  • At any given point of time, all the Node_ID_1 and Node_ID_2 combinations can have either VPLMN-IDs of networks (determined by the value configured in MCC_Or_VPLMNID of System_Config_Options Table). But not MCC.
  • Valid VPLMN-ID value range for Node_ID_1 and Node_ID_2 is a 6-digit OctetString with allowed digits of 0–9 and F. This validation is performed when MCC_Or_VPLMNID is configured as VPLMNID_Based in System_Config_Options Table.

Note:

F is allowed to act as filler for 2 digits MNC. Therefore, if F is present, it must be in the 3rd byte string. Format of the Visited-PLMN-Id defined in TS 3GPP TS 29.272.