|
|
IP Config Info
Last updated: July 22, 2008
This section is only applicable to the lab application.
Association between ReservationLabel, IP Flow, and QoS profile is established via negotiation of attributes Reservation
KK
QoSRequestFwd and Reservation
KK
QoSRequestRev which specify a set of Profile IDs (see
MFPA Profile ID
for details). The AT doesn't interpret the Profile ID, but just sends it to the AN in an MFPA/EMPA message to request additional IP flows.
IP Configuration Rules (see
IP Config Rule
for details) are used to configure requested IP Flows for MFPA: which RLP FLow (see
MFPA RLP Flow Mapping
for details) to map,
MFPA Reservation Idle State
,
MFPA AN Scheduler Priority (0 is lowest)
and Data Throughput Monitor Context (see
MFPA Forward IP Config Rule DTM Context
and
MFPA Reverse RLP Flow DTM Context
for details).
IP Configuration Rule specifies how the Profile IDs requested are applied to the MFPA IP Forward/Reverse Configuration Rule Profile ID and determines if there is a "match". If IP FLows don't match any MFPA IP Forward/Reverse Configuration Rule Profile ID, they will be configured by the Default Rule. Then the IP Flows will be mapped to the RLP FLow specified by the
MFPA RLP Flow Mapping
of the Default Rule. However if the RLP Flow you set is not be activated by
RLP Parameters
, the IP Flows will be mapped to the Default RLP Flow (RLP Flow 00).
IP Config Rule
Six IP Configuration Rules (Rule1 - Rule6) and one default rule can be selected to configure requested IP Flows for MFPA. When a session is open, changing the IP Configuration Rule will not result in a session re-negotiation.
Forward/Reverse Config Rule Parms
-
MFPA Profile ID
Different Applications have different QoS requirements, all QoS for a certain application is called QoS profile for this application. In oder to distinguish QoS profiles, the QoS profile is specified as a single 16-bit number profile ID. Profile ID is used by the test set to map forward/Reverse IP Flows to RLP Flows.
-
MFPA RLP Flow Mapping
This setting is used by the test set to map requested IP Flows to RLP Flows. The test set supports 5 RLP Flows: Flow 00, Flow 01, Flow 02, Flow 03 and Flow 04.
-
MFPA Reservation Idle State
This setting is used to configure how the reservation state changes according to the call connection state.
-
No Change: Reservation does not change states when a Connection is opened or closed.
-
Close with Connection: Reservation transitions to the Close state when a Connection is closed.
-
Follow Connection: Reservation transitions to the Open state when a Connection is opened and transitions to the Close state when a Connection is closed.
-
MFPA AN Scheduler Priority (0 is lowest)
This setting assigns a priority for the test set to use when deciding which flow to send to the AT. Lower numbers indicate higher priority. The test set will use MFPA/EMPA KK Forward Flow Requested Priority first, then MFPA IP Forward Mapping Rule AN Scheduler Flow Priority when determining a flow's priority.
Forward DTM Context Parms
-
MFPA Forward IP Config Rule DTM Context
This setting specifies to which context the Forward IP Flows will be used in
Data Throughput Monitor
. In the Forward Link, this setting is defined per IP Config Rule, there are 7 settings (including default rule). The Forward IP Flows can map to
Context 1 Rx
,
Context 2 Rx
,
Context 3 Rx
,
Context 4 Rx
or
None
.
-
DTM Context X Name
In order to make Contexts which represent different applications easy to be distinguished on the
Data Throughput Monitor
screen. Users can set the name for each Context according to the applications by using this setting. Ten names can be selected:
Audio Rx
,
BE Rx
,
Context 1 Rx
,
Control Rx
,
Gaming Rx
,
RTCP Rx
,
SIP RX
,
Text Rx
,
Video Rx
and
VOIP Rx
.
Reverse DTM Context Parms
-
MFPA Reverse RLP Flow DTM Context
This setting specifies which context the Reverse IP Flows will map used in
Data Throughput Monitor
. In the Reverse Link, this setting is defined per RLP Flow, there are 5 settings. The Reverse IP Flows can map to
Context 1 Tx
,
Context 2 Tx
,
Context 3 Tx
,
Context 4 Tx
or
None
.
-
DTM Context X Tx Name
In order to make Contexts which represent different applications easy to be distinguished on the
Data Throughput Monitor
screen. Users can set the name for each Context according to the applications by using this setting. Ten names can be selected:
Audio Tx
,
BE Tx
,
Context 1 Tx
,
Control Tx
,
Gaming Tx
,
RTCP Tx
,
SIP TX
,
Text Tx
,
Video Tx
and
VOIP Tx
.
|
|