Export/Import Rules

The Rule Template can be provisioned with up to 250 rules and data related to the template. To Export or Import rules from provisioned Rule Templates use the Export function on the Diameter > Mediation > Rule Sets > {name} [Export] or Import function on the Diameter > Mediation > Rule Sets > {name} [Import] page.

The Export/Import function is used to solve the following two scenarios:

1. The rules of template X are imported back to template X. Each template is uniquely identified by a UUID number. With the exported rules, the XML-file contains the UUID number as part of a template definition. If the UUID number is the same, the rules are imported back to the original template and no mapping is necessary for the conditions or actions. The rules are imported even if the user changes the name of the template, while in a Test or Active state. A new UUID number is assigned to the template when the user moves the original template to the development state and changes in conditions/actions.
2. The rules of template X are imported to template Y. In this case the UUID number of the original template does not match with the UUID number of the target template. The process is performed to import by mapping the conditions and actions as follows:
   1. Table 2-33 table means that if the condition name of the target template is the same as in the original template, the values from the xml-file are imported for this condition.

      Table 2-33 Conditions Correlated by the Condition Name

      Template X	Template Y
      A: User-name	A: User-name
      B: Host IP	B: Connection
      C: Visited-PLMN-Id	C: Visited-PLMN-Id
      D: Proxy-Host	D: Host IP

      The rules mapping process for the conditions are exported from Template X are imported to Template Y as follows:

      • A => A
      • B => D
      • C => C

      The values of condition D of Template X are not used.

      Condition B of template Y uses the default value defined in the template since no match was found for it. If no default value was provisioned for the mandatory condition in the template, the error message is expected.

   2. Table 2-34 table means that if the values of the action from the xml--file are imported to the action of the same type and matched columns in the target template.

      Table 2-34 Actions are Correlated by their Type and Order

      Template X	Template Y
      A: Add AVP	A: Add AVP
      B: Change AVP code	B: Add AVP
      C: Add AVP	C: Add AVP
      D: Add AVP	D: Add AVP
      E: Set Route List	E: Set AVP value
      F: Set AVP value	F: Set AVP value
      G: Set AVP value	G: Set Route List
      H: Set AVP value	N/A

      The actions are correlated as follows:

      • A => A
      • C => B (second Add AVP to second Add AVP)
      • D => C (third Add AVP to third Add AVP)
      • default values => D (there is not fourth Add AVP action in the XML file)
      • F => E (first Set AVP value to first Set AVP value)
      • G => F (second Set AVP value to second Set AVP value)
      • E => G (first Set Route List to first Set Route List)

      The failures are logged during the import process.

The Import of Rules is very similar to the Insert of Rules. The difference is the data source (xml file instead of values entered on the web page). During the Import, the same checks are performing as seen Adding a Rule to a Rule Set.