Processing sequence:
The order in which the priority elements are to be taken into account when compiling the screen must be specified. This determines the order and ultimately the priority with which the traffic streams are selected for a new stage.
Priority value:
Depending on the priority flag, a traffic stream can be given a supplement to its standard priority value. The size of this surcharge depends on the weight of the priority flag, which can be given for each priority element. This means that a traffic stream in a lower-prioritised priority element can be assigned a higher weighting than a traffic stream in a higher-prioritised priority element. The standard weighting is inverse to the processing sequence. This means that the first priority element according to the processing sequence receives the lowest weighting, while the last priority element according to the processing sequence receives the highest weighting.
Cycle end:
The cycle end for the re-service flag can be set as follows.
- Cycle second
- Rank
- Priority element
Cycle end by rank:
For cycle end by priority element rank, the rank of the priority element in question for which the internal flag is to be deleted must be entered. If a cycle end of another priority element is to be effective instead of a rank in the priority element in question, the parameter cycle end by rank of priority element must be left blank. Instead, the reference to the relevant priority element must be set in the cycle end by priority element parameter.
Cycle end by priority element:
If the cycle end of another priority element is valid for the priority element in question, the reference to the relevant priority element must be specified for cycle end by priority element. If the rank of the priority element in question is to be effective instead of another priority element, the cycle end by priority element parameter must be left blank. Instead, the desired rank must be entered for the cycle end by rank.
|
Display |
Identifier |
Values |
Description |
|
Sequence |
Processing sequence |
|
The order in which the priority elements are to be considered in the stage configuration is to be specified. This determines the order and ultimately the priority with which the traffic streams are selected for a new stage. |
|
|
|
|
|
|
|
|
1 .. 6 |
Ranking of priority elements. |
|
|
The order in which the priority elements are to be considered in the stage configuration is to be specified. This determines the order and ultimately the priority with which the traffic streams are selected for a new stage. They are specified in the order in which they are processed. |
||
|
|
|
|
|
|
|
|
List |
All priority elements in the order of their processing. |
|
|
|
Depending on the priority flag, a traffic stream can be given a supplement to its default priority value. The size of this supplement depends on the weight of the priority flag, which can be given for each priority element. Thus, a traffic stream in a lower priority element can be given a higher weight than a traffic stream in a higher priority element. The default weighting is inverse to the processing order. This means that the first priority element according to the processing sequence is given the lowest weight, and the last priority element according to the processing sequence is given the highest weight. |
|
|
|
|
|
|
|
|
|
1 .. 6 / 24 |
Priority value. |
|
CycleEndRank |
Cycle end according to rank |
|
In the case of cycle end by rank priority element, it must be entered at which rank in the main series of the priority element concerned the internal identifier is to be deleted. |
|
|
|
|
|
|
|
|
1 .. 64 |
Rank in the main series. |
|
CycleEndPE |
Cycle end according to priority element |
|
If the cycle end of another priority element is valid for the priority element in question, the reference to the authoritative priority element must be indicated in the case of cycle end by priority element. |
|
|
|
|
|
|
|
|
List |
All existing priority elements. |