Cisco ASR 5000 Series, Обзор продукта

Страница: 749 / 992

Enhanced Charging Service Overview
Enhanced Services in ECS ▀
Cisco ASR 5000 Series Product Overview ▄
OL-22938-02
For x-header insertion, there should either be a post-processing rule whose charging-action gives no
disposition-action or the packet should not match any of the post-processing rules so that the disposition
action obtained from charging-rule matching is applied.
Time-of-Day Activation/Deactivation of Rules
Within a rulebase, ruledefs/groups-of-ruledefs are assigned priorities. When packets start arriving, as per the priority
order, every rule/group-of-ruledefs in the rulebase is eligible for matching regardless of the packet arrival time. By
default, the ruledefs/groups-of-ruledefs are active all the time.
The Time-of-Day Activation/Deactivation of Rules feature uses time definitions (timedefs) to activate/deactivate static
ruledefs/groups-of-ruledefs such that they are available for rule matching only when they are active.
Important:
The time considered for timedef matching is the system‘s local time.
How the Time-of-Day Activation/Deactivation of Rules Feature Works
The following steps describe how the Time-of-Day Activation/Deactivation of Rules feature enables charging according
to the time of the day/time:
Step 1
Timedefs are created/deleted in the Active Charging Service Configuration Mode.
A maximum of 10 timedefs can be created in an ECS service.
Step 2
Timedefs are configured in the Timedef Configuration Mode. Within a timedef, timeslots specifying the day/time for
activation/deactivation of rules are configured.
A maximum of 24 timeslots can be configured in a timedef.
Step 3
In the Rulebase Configuration Mode, timedefs are associated with ruledefs /groups-of-ruledefs along with the charging
action.
One timedef can be used with several ruledefs/group-of-ruledefs. If a ruledef/group-of-ruledefs does not have
a timedef associated with it, it will always be considered as active.
Step 4
When a packet is received, and a ruledef/group-of-ruledefs is eligible for rule matching, if a timedef is associated with
the ruledef/group-of-ruledefs, before rule matching, the packet-arrival time is compared with the timeslots configured in
the timedef. If the packet arrived in any of the timeslots configured in the associated timedef, rule matching is
undertaken, else the next ruledef/group-of-ruledefs is considered.
This release does not support configuring a timeslot for a specific date.
If, in a timeslot, only the time is specified, that timeslot will be applicable for all days.
If for a timeslot, ―start time‖ > ―end time‖, that rule will span the midnight. I.e. that rule is considered to be
active from the current day till the next day.
If for a timeslot, ―start day‖ > ―end day‖, that rule will span over the current week till the end day in the next
week.
In the following cases a rule will be active all the time: