Page History

...

Policy and Rules Management allow non-developer secondary users to create policies and rules and apply them to services. The scope of policies includes, but is not limited to, definition and configuration of quality of service policies. Some key functional requirements for managing policies include capabilities to author policies and store policies, and to approve and validate policies and execute policies at runtime.

Quality of Service Policies include the following capabilities

• definition and configuration of Quality of Service policy and related rule
• apply policies to services
• author policy
• store policies
• approve policies
• validate policies
• execute policies at runtime
• descriptions to enable the policy modules to be visible, where the description includes a unique identifier for the policy and the metamodel representation of the meaning of terms used to describe the policy, its functions, and its effects;
• one or more discovery mechanisms that enable searching for policies that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual policy descriptions through some repository mechanism;
• accessible storage of policies and policy descriptions, so service participants can access, examine, and use the policies as defined.
• expression of assertion and commitment policy constraints;
• expression of positive and negative policy constraints;
• expression of permission and obligation policy constraints;
• nesting of policy constraints allowing for abstractions and refinements of a policy constraint;
• definition of alternative policy constraints to allow for the selection of compatible policy constraints for a consumer and provider;
• composition of policies to combine one or more policies.
• decision procedures which must be able to measure and render decisions on constraints;
• enforcement of decisions;
• measurement and notification of obligation constraints;
• auditability of decisions, enforcement, and obligation measurements;
• administration of policy and contract language artifacts;
• storage of policies and contracts;
• distribution of policies/contracts;
• conflict resolution or elevation of conflicts in policy rules;
• delegation of policy authority to agents acting on behalf of a client;
• decision procedures capable of incorporating roles and/or attributes for rendered decisions.

This Functional Profile includes, but is not limited to, the following capability elaborations:

...

Quality of Service Policy Model with capabilities to create, destroy, edit, maintain service descriptions.

Policy and Rules Quality of Service Management allow non-developer secondary users to create policies and rules and apply them to services. The scope of policies includes, but is not limited to, definition and configuration of quality of service policies. Some key functional requirements for managing policies include capabilities to author policies and store policies, and to approve and validate policies and execute policies at runtime

The Quality of Service Policy Model implementation includes the following capabilities

• definition and configuration of Quality of Service policy and related rule
• apply policies to services
• author policy
• store policies
• approve policies
• validate policies
• execute policies at runtime
• descriptions to enable the policy modules to be visible, where the description includes a unique identifier for the policy and the metamodel representation of the meaning of terms used to describe the policy, its functions, and its effects;
• one or more discovery mechanisms that enable searching for policies that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual policy descriptions through some repository mechanism;
• accessible storage of policies and policy descriptions, so service participants can access, examine, and use the policies as defined.
• expression of assertion and commitment policy constraints;
• expression of positive and negative policy constraints;
• expression of permission and obligation policy constraints;
• nesting of policy constraints allowing for abstractions and refinements of a policy constraint;
• definition of alternative policy constraints to allow for the selection of compatible policy constraints for a consumer and provider;
• composition of policies to combine one or more policies.
• decision procedures which must be able to measure and render decisions on constraints;
• enforcement of decisions;
• measurement and notification of obligation constraints;
• auditability of decisions, enforcement, and obligation measurements;
• administration of policy and contract language artifacts;
• storage of policies and contracts;
• distribution of policies/contracts;
• conflict resolution or elevation of conflicts in policy rules;
• delegation of policy authority to agents acting on behalf of a client;
• decision procedures capable of incorporating roles and/or attributes for rendered decisions.