Presently the scope of policy is imperitive (event, condition, action) only - not declaritive or intent. Approach will be pragmatic in nature, establishing a model that meets the Policy team's near term needs, and then evolve from that base.

This is an abstract base class that represents how to form the action clause of a PolicyRule. Certain actions will take place if the condition clause is TRUE, others if the condition clause is FALSE. Additional metadata pertinant to the action. Defines the strategy to be used when executing the aggregated actions A PolicyEvent is an occurrence of an important event, and can be used to trigger the evaluation of a PolicyCondition or PolicyCondition clause in a PolicyRule. eventOrigin provides information on the entity that generates the event (DCAE, Vnf, monitors). The environment or entity in which the event occurred (Eg - Vnf, switch, eNodeB, or data center). The payload for the event. Classification that captures the symantics of that particular event categorization (enodeb, vnf) This class is a generalized aggregation container. It enables PolicyRules and/or PolicyGroups to be aggregated in a single container. Note that loops, including the degenerate case of a PolicyGroup that contains itself, are not allowed when PolicyGroups contain other PolicyGroups. This is a Boolean attribute that, if TRUE, signifies that evaluation (and possibly action execution) of this entity is mandatory and must be attempted. If the Mandatory property value of this entity is FALSE, then the evaluation of this entity is considered to be "best effort" and may be ignored. Notes: Not present in the ITU or CIM specs. This is a free-form string attribute that recommends how this policy object should be used. Notes: Not present in the ITU or CIM specs. This is a string attribute that defines a set of one or more keywords that a policy administrator may use to assist in characterizing or categorizing a policy object to facilitate search operations. The following keywords are pre-defined: Permitted Values: Unknown InstallPermissions ConfigChange InstallMethod Default Error Usage InternalError Security ExternalError Authentication Notification Authorization Publish Accounting Subscribe Auditing Publish-Subscribe Service Exception CustomerFacingService ResourceFacingService Notes: Not present in the ITU specs; the CIM defines a PolicyKeyword attribute, but its semantics are very different. This is a generic naming attribute that can be used to identify different policy entities. This enables commonName to be used to enforce enterprise or service provider generic naming and this attribute to be used to fine tune the naming of policy entities. Thus, commonName is public in scope and policyName is private to policy. Notes: Not present in the ITU specs or CIM specs. Represents a user-friendly identifier of an object. It is a (possibly ambiguous) name by which the object is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated. It is NOT used as a naming attribute (i.e., to uniquely identify an instance of the object). This is a string, and defines a textual free-form description of the object. Notes: This attribute doesn’t exist in M.3100. The CIM has two attributes for this purpose, Caption (a short description) and Description. Unambiguously distinguishes different object instances. It is the naming attribute of the object. This is a concrete base class for realizing the "event-condition-passaction-failaction" semantics that form a policy rule. The semantics of this rule are that the rule is evaluated when an event occurs. If the condition clause is satisfied, then the pass-action clause will be executed (otherwise, the fail-action clause will be executed). PolicyRules may be nested within PolicyRules. This is often needed in networking (e.g., bandwidth allocation). This is a Boolean attribute that, if TRUE, defines the condition clause of this rule to be represented in Conjunctive Normal Form (e.g., an AND of ORs). If the value of this attribute is FALSE, then the condition clause will be represented in Disjunctive Normal Form (e.g., an OR of ANDs). This attribute controls the setting of how multiple condition clauses (as represented by multiple PolicyConditionComposite objects) are treated in the PolicyRule. As such, it is different from the attribute PolicyConditionComposite.IsCNF, which controls how multiple PolicyConditionAtomic objects are treated in a (single) PolicyConditionComposite object. This is a Boolean attribute that, if TRUE, signifies that evaluation (and possibly action execution) of this entity is mandatory and must be attempted. If the Mandatory property value of this entity is FALSE, then the evaluation of this entity is considered to be "best effort" and may be ignored. Notes: Not present in the ITU or CIM specs. This is a free-form string attribute that recommends how this policy object should be used. Notes: Not present in the ITU or CIM specs. This is a string attribute that defines a set of one or more keywords that a policy administrator may use to assist in characterizing or categorizing a policy object to facilitate search operations. The following keywords are pre-defined: Permitted Values: Unknown InstallPermissions ConfigChange InstallMethod Default Error Usage InternalError Security ExternalError Authentication Notification Authorization Publish Accounting Subscribe Auditing Publish-Subscribe Service Exception CustomerFacingService ResourceFacingService Notes: Not present in the ITU specs; the CIM defines a PolicyKeyword attribute, but its semantics are very different. Version of the policy as defined by the developer. his is a Boolean attribute that, if TRUE, defines the condition clause of this rule to be represented in Conjunctive Normal Form (e.g., an AND of ORs). If the value of this attribute is FALSE, then the condition clause will be represented in Disjunctive Normal Form (e.g., an OR of ANDs). This attribute controls the setting of how multiple condition clauses (as represented by multiple PolicyConditionComposite objects) are treated in the PolicyRule. As such, it is different from the attribute PolicyConditionComposite.IsCNF, which controls how multiple PolicyConditionAtomic objects are treated in a (single) PolicyConditionComposite object. This is a concrete base class that is used to define the invariant characteristics (attributes, methods, constraints and relationships) of a PolicyRule entity. This is an enumerated integer that defines the strategy to be used when executing the sequenced actions aggregated by this PolicyRule. Defined execution strategies include: 0: Unknown 1: Do Until Success 2: Do All 3: Do Until Failure 4: Do All Without Failure or Do Nothing "Do Until Success" means that actions should be executed according to their predefined order, until successful execution of a single action. At that point, the process should stop (even if there are additional actions that could be executed). "Do All" means that all actions should be executed that are part of the set, according to their predefined order. This should continue, even if one or more of the actions fails. "Do Until Failure" means that all actions should be executed according to their predefined order until an action fails to execute. At that point, the entire sequence should be stopped. Finally, "Do All Without Failure or Do Nothing" means that all actions specified should be performed. However, if a failure occurs, then NONE of the actions should be performed. This implies EITHER the ability to look-ahead and ensure that the actions will be able to be performed successfully, or the ability to perform a rollback of that action and all previous actions when an error is encountered. This is an enumerated integer defines how the ordering of the PolicyActions associated with this PolicyRule is to be interpreted. Notes: Not present in the ITU or CIM specs (the CIM defined a subset of these values as an attribute in the PolicyRule). This is an attribute that contains an OCL expression to prescribe any limitations on the types of PolicyConditions that can be used with any PolicyRules that are derived from this particular PolicyRuleSpec. This enables a PolicyRuleSpec to be built that defines what types of PolicyConditions can be used to build PolicyRules. This in turn ensures that a given set of PolicyRules carry standard functionality. Notes: Not present in the ITU or CIM specs. This is an attribute that contains an OCL expression to prescribe any limitations on the types of PolicyEvents that can be used with any PolicyRules that are derived from this particular PolicyRuleSpec. This enables a PolicyRuleSpec to be built that defines what types of PolicyEvents can be used to trigger the evaluation of PolicyRules. This in turn ensures that a given set of PolicyRules carry standard functionality. Notes: Not present in the ITU or CIM specs. This is an attribute that contains an OCL expression to prescribe any limitations on the types of PolicyEvents that can be used with any PolicyRules that are derived from this particular PolicyRuleSpec. This enables a PolicyRuleSpec to be built that defines what types of PolicyEvents can be used to trigger the evaluation of PolicyRules. This in turn ensures that a given set of PolicyRules carry standard functionality. Notes: Not present in the ITU or CIM specs. This is an enumerated integer that specifies the particular decision strategy to be used in this PolicySet. Permitted Values: 0: Unknown 1: MatchFirst 2: MatchAll MatchFirst enforces the actions of the first rule that evaluates to TRUE; policy evaluation then STOPS, meaning that all subsequent rules are no longer evaluated. MatchAll enforces the actions of all rules that evaluate to TRUE. This is equivalent to performing two passes through the rule set. The first pass gathers all PolicyRules that evaluate to true and places them in a group. The second pass then executes only those rules that evaluated to true. Execution of these rules is controlled through the Priority property (on the aggregation PolicySetComponent), which defines the order in which the PolicyRules execute. List of Event Types to be considered by this event. This is the base class for all simple PolicyActions. A simple PolicyAction consists of a single Boolean clause, which is used to perform a single action. This consists of a single occurrence of a PolicyStatement, which is of the form: {SET | CLEAR} PolicyVariable to PolicyValue This is distinctly different from the PolicyActionVendor, which does not use a PolicyStatement. PolicyActionAtomic objects can also be used to form more complex action structures. A PolicyActionComposite object can be used to contain a group of PolicyActionAtomic objects - this grouping enables multiple PolicyActionAtomic objects to be executed as a group. Alternatively, a PolicyActionAtomic object can contain one or more PolicyActionAtomic objects (and also PolicyActionComposite groups if desired) to provide the semantics of a compound PolicyAction. In either case, the aggregation is done using the containedPolicyActions aggregation. This attribute is a non-negative integer and represents the particular sequence in which this element is executed as part of the overall policy structure. This will allow a policy engine to reference externally supplied arguments to this object as it is executed. Notes: Not present in the ITU specs; CIM 2.7 has a subset of these values. Tthe entity that is executing the policy. he set of entities that are affect-ed by the policy. This is an enumerated integer that is set by a policy application to define the state of execution of this policyAction. Permited Values: 0: not yet executed 1: executed with no errors 2: executed with errors but successfully rolled back 3: executed with errors and did not roll back 4: did not complete execution but successfully rolled back 5: did not complete execution and did not roll back Notes: Not present in the ITU or CIM specs. This attribute is a non-negative integer and represents the particular sequence in which this element is executed as part of the overall policy structure. For example if a composite is part of another composite policy structure. Notes: default is “1” This attribute is a non-negative integer and represents the particular sequence in which this element is executed as part of the overall policy structure. For example if a composite is part of another composite policy structure. Notes: default is “1” This is a Boolean attribute that, if TRUE, signifies that this PolicyAction has one or more sub-actions. Sub-actions are used to enforce a hierarchical nesting of actions, so that parent actions may control the evaluation and other semantics of sub-actions that they contain. Notes: Not present in the ITU or CIM specs. Specifies if the action is in confunctive normal form. Execution Strategy that applies to the entire workflow. Composite event has events This is an abstract base class that represents how to form the condition clause of a PolicyRule. This class can be used to represent rule-specific or reusable policy conditions. Policy conditions are of the form: {variable, operator, value} where the operator is usually the MATCH operator, but could be another type (e.g., compare) of operator. This gives the semantics of "IF the condition is TRUE (or FALSE)". The subclasses of PolicyCondition, along with its recursive aggregation, enable simple and compound (e.g., nested) PolicyConditions to be supported by the same structure. This is an enumerated integer that specifies the particular decision strategy to be used in this PolicySet. Permitted Values: 0: Unknown 1: MatchFirst 2: MatchAll MatchFirst enforces the actions of the first rule that evaluates to TRUE; policy evaluation then STOPS, meaning that all subsequent rules are no longer evaluated. MatchAll enforces the actions of all rules that evaluate to TRUE. This is equivalent to performing two passes through the rule set. The first pass gathers all PolicyRules that evaluate to true and places them in a group. The second pass then executes only those rules that evaluated to true. Execution of these rules is controlled through the Priority property (on the aggregation PolicySetComponent), which defines the order in which the PolicyRules execute. This is an enumerated integer that defines the strategy to be used when executing the sequenced actions aggregated by this PolicyRule. Defined execution strategies include: 0: Unknown 1: Do Until Success 2: Do All 3: Do Until Failure 4: Do All Without Failure or Do Nothing "Do Until Success" means that actions should be executed according to their predefined order, until successful execution of a single action. At that point, the process should stop (even if there are additional actions that could be executed). "Do All" means that all actions should be executed that are part of the set, according to their predefined order. This should continue, even if one or more of the actions fails. "Do Until Failure" means that all actions should be executed according to their predefined order until an action fails to execute. At that point, the entire sequence should be stopped. Finally, "Do All Without Failure or Do Nothing" means that all actions specified should be performed. However, if a failure occurs, then NONE of the actions should be performed. This implies EITHER the ability to look-ahead and ensure that the actions will be able to be performed successfully, or the ability to perform a rollback of that action and all previous actions when an error is encountered. This is an enumerated integer that is set by a policy application to define the state of execution of this policyAction. Permited Values: 0: not yet executed 1: executed with no errors 2: executed with errors but successfully rolled back 3: executed with errors and did not roll back 4: did not complete execution but successfully rolled back 5: did not complete execution and did not roll back Notes: Not present in the ITU or CIM specs. PolicyEvents can include a state chnage, a VES Event, or a configuration request. Model Based Strongly On the TMF SID Rooted PolicyEvent Some rules may not be created from a template "Guard" Policies - serve as overarching conditions.