demo/ggsn/model/CLIrecords.java

/**
 * CLIrecords.java
 * 
 * Ericsson CLI interface records/messages
 */

// Restart - restart node, for instance after changing
// the node configuraion
record  Restart { }

record  Prepare {
	String[] cmds;
}

record  Restore {
	String[] cmds;
}

/**
 * Configuration
 * 
 * Sample GGSN configuration from  test_basic.ttcn  :
 * 
    f_sr_TELNET_Configuration(
        {   "set services ggsn charging charging-format 6",
            "set services ggsn charging cdr-attribute record-extension",
            "set services ggsn charging characteristics profile8 transfer-type gtp-prime",
            "set services ggsn charging characteristics profile8 gtp-prime gateway " & tsp_CGF_IpAddr,
            "set services ggsn charging characteristics profile8 change-limit 1",
            "set services ggsn charging characteristics default profile8"
        });  
 *
 *  4th command above relies on an IP address taken from TTCN configuration item "tsp_CGF_IpAddr"
 *  For the pilot we define all configuration commands at the harness level.
 *  Only use "configuration identifiers" at model level, for instance "DEFAULT_CONFIG"??
 *  
 *  It would be possible to define (alternative) configuration at the model level,
 *  and still apply variable substitution on the TTCN level.
**/

record  Configure {
	String[] cmds;
	
	// 100222: Feature based configuration
	// On the model level we only take care that certain things assume the
	// node is configured in a certain way. For instance, the part of the
	// model describing how a CDR is sent out can only be done if the node
	// has been set up with charging enabled;
	
	boolean enableCharging;
	boolean enableRadiusAuth;
}

record OverrideConfiguration {
	// If we want to tailor the cleanup we can add data items
	// here to control the cleanup.
	boolean overrideCharging;
	boolean overrideRadiusAuth;
}