The Services tab
allows for creation of reusable policy rules that control how subscribers are
granted network services, quota and notifications. Services are broken down
into three core areas: Domains, Services and Use Case Templates. The following
section provides an overview of the Services tab, however detailed instructions
on how to build a service are covered in later chapters of this guide.
The creation of a new
service begins with creating a Use Case Template (UCT) for the service. UCTs
consist of Service Configurations specific to the service that will be created.
For example, a Service Configuration might provide for the setup of a Gx Rule
or Basic QoS. The UCT is also used to configure Use Case Initiators (UCI) which
are instructions on when a specific Service Configuration should be in effect.
An example of the UCI might be “only send this Gx Rule when the account balance
is depleted”. Multiple UCIs can be configured for each Service Configuration
allowing for complex logic as to when the configuration should or should not be
Once a UCT and
associated UCIs are defined, it becomes the basis for Service Options, which
are specific instances of the UCT that are populated with data specific to the
service. Multiple Service Options can be created from a single UCT; for
example, a UCT that provides for passing QoS parameters can be reused with
different QoS values for different customers. Multiple Service Options can be
layered to create the end Service.
Figure 2. Services
The Domains panel
within the Services tab handles the initial interaction of the client device
with the policy engine, and covers tasks including client authentication,
default provisioning of unknown clients and qualifying a client for particular
system defaults and services.
For more information on the
Services tab, refer to the