Red
MAX
™
Base Station
user manual
Doc. #70-00058-01-01-DRAFT
Proprietary Redline Communications © 2006
November
29,
2006
Page 41 of 106
4.3
Creating Service Flows - Overview
There are four steps associated with creating service flows:
1. Create service class.
Each service class defines a set of QoS parameters that can be associated with a
service flow. Multiple service class definitions can be added to create a library of
service classes. By creating a set of standardized service classes, new service flows
can be added that conform to pre-defined service level agreements (SLAs). Each
service class definition includes traffic rates, latency settings, priority, and
transmission policy settings.
Note: A service class can not be deleted until all provisioned/active service flows
referencing this service class have been deleted.
2. Create service flow.
All service flows are based on existing service class definitions. Separate service
flows are required for downlink and uplink traffic. Each definition requires
identifying the subscriber, flow direction, class of service, and the classifier type.
3. Define
classifier.
A unique set of classifier rules can be defined for each service flow, depending on the
classification type (i.e., Packet, 802.3/Ethernet) selected when the service flow is
created. All associated classifiers are deleted when the service flow is deleted.
4. Activate
A new service flow is not activated until a classifier is assigned (click
Add
in the
Classifier
screen).
If the target subscriber is registered a Dynamic Addition Session (DSA) session is
initiated. During a DSA session, the service flow is in Requesting state. If the DSA
session is successful, the state is set to
Active
. If the DSA session is not successful, the
state is set to
Rejected
.
If the target subscriber is not registered, the service flow request is stored until the
associated subscriber is registered. The subscriber registration triggers the activation
of all associated service flows.