MS Reported FER Parameters
Last updated: October 28, 2004
This section is only applicable to the lab application.
The MS Reported FER Parms menu can be accessed in two ways:
-
- select the
MS Reported FER Info ( F1 ) on Call Control 4 of 4 , or
- select the
Forward Power Control ( F2 ) on the Call Control 4 of 4
These parameters are used to control FER reporting from the MS when FPC Mode is set to 000-Primary 800 .
-
-
Frame Interval of Report (Frames)
It specifies the total number of F-FCH frames over which the MS is to count frame errors for periodic reporting of FER.
This parameter can be changed at any time. It is converted according to Frame Interval of Report (Frames) and sent to the MS in the PWR_REP_FRAMES field in the System Parameters Message or MC-RR Parameters Message (while in idle), or the Power Control Parameters Message (after a call connected).
When the Periodic Report Enable is set to On and the total number of frames received on the F-FCH (which is recorded in the TOT_FRAMES counter in the MS, see Background Information ) reaches this setting, the MS sends the Power Measurement Report Message (PMRM) to the test set and the FER results are displayed on MS Reported Frame Error Rate Information window. After sending a PMRM, the MS will set its TOT_FRAMES and BAD_FRAMES counters to zero.
GPIB Command: CALL:MS:FERate:REPort:INTerval
When the TOT_FRAMES reaches the
Frame Interval of Report (Frames) setting, the MS sets both TOT_FRAMES and BAD_FRAMES counters to zero regardless of whether the PMRM is sent.
Frame Interval of Report (Frames)
|
Frame Interval of Report (Frames)
|
PWR_REP_FRAMES
|
|
Frame Interval of Report (Frames) = [2 (PWR_REP_FRAMES/2) * 5]
|
|
5
|
0
|
|
7
|
1
|
|
10
|
2
|
|
14
|
3
|
|
20
|
4
|
|
28
|
5
|
|
40
|
6
|
|
56
|
7
|
|
80
|
8
|
|
113
|
9
|
|
160
|
10
|
|
226
|
11
|
|
320
|
12
|
|
452
|
13
|
|
640
|
14
|
|
905
|
15
|
Frame Delay of Report (Frames)
It specifies the delay period (in units of frames) that the MS waits after sending a PMRM before restarting frame counting for power control purpose.
This parameter can be changed at any time. It is converted by the formula of [Frame Delay of Report (Frames) = PWR_REP_DELAY * 4 ] and sent to the MS in the PWR_REP_DELAY field in the System Parameters Message or the MC-RR Parameters Message (while in idle), or the Power Control Parameters Message (after a call connected).
GPIB Command: CALL:MS:FERate:REPort:DELay
Periodic Report Enable
It is used to enable (On) or disable (Off) the MS to generate periodic-PMRMs when the specified interval ( Frame Interval of Report (Frames) ) is reached.
This parameter can be changed at any time. It is sent to the MS in the PWR_PERIOD_ENABLE field (On = 1, Off = 0) in the System Parameters Message or MC-RR Parameters Message (while in idle), or the Power Control Parameters Message (after a call connected).
GPIB Command: CALL:MS:FERate:REPort:PERiod[:STATe] .
Threshold Report Enable
It is used to enable (On) or disable (Off) the MS to generate threshold-based PMRMs when the detected bad frames reaches the specified threshold ( Bad Frame Threshold (Frames) ).
This parameter can be changed at any time. It is sent to the MS in the PWR_THRESH_ENABLE field (On = 1, Off = 0) in the System Parameters Message or MC-RR Parameters Message (while in idle), or the Power Control Parameters Message (after a call connected).
GPIB Command: CALL:MS:FERate:REPort:THReshold[:STATe]
Bad Frame Threshold (Frames)
It specifies the number of bad frames detected by the MS on the F-FCH in a measurement period ( Frame Interval of Report (Frames) ) to trigger a threshold-based FER reporting.
This parameter can be changed at any time. It is sent to the MS in the PWR_REP_DELAY field in the System Parameters Message or the MC-RR Parameters Message (while in idle), or the Power Control Parameters Message (after a call connected).
When the Threshold Report Enable is set to On and the number of bad frames detected on the F-FCH (which is recorded in the BAD_FRAMES counter in the MS, see Background Information ) reaches this setting, the MS sends the PMRM to the test set and the FER results are displayed on the MS Reported Frame Error Rate Information screen. After sending a PMRM, the MS will set TOT_FRAMES and BAD_FRAMES counters to zero.
GPIB Command: CALL:MS:FERate:REPort:THReshold:BAD
When the TOT_FRAMES reaches the
Frame Interval of Report (Frames) setting, the MS sets both TOT_FRAMES and BAD_FRAMES counters to zero regardless of whether the PMRM is sent.
Background Information
The MS maintains the following frame counters for the F-FCH:
-
- A counter (TOT_FRAMES) for the total number of frames received on the F-FCH. The MS will increment the TOT_FRAMES counter by 1 for every received 20 ms frame on the F-FCH
- A counter (BAD_FRAMES) for the number of bad frames detected on the F-FCH. If the received 20 ms frame is bad or one of the 5 ms frames (test set does not support 5 ms frames) is bad, the MS will increment BAD_FRAMES counter by 1.
To support the forward power control on the forward fundamental channel (F-FCH), the MS reports frame error rate statistics to the base station via Power Measurement Report Message (PMRM). If the base station enables periodic reporting (PWR_PERIOD_ENABLE equal to '1' ), the MS reports frame error rate statistics at specified intervals (that is, when TOT_FRAMES equal to [2 (PWR_REP_FRAMES/2) * 5]). If the test set enables threshold reporting (PWR_THRESH_ENABLE equal to '1' ), the MS reports frame error rate statistics when the frame error rate reaches a specified threshold (that is, when BAD_FRAMES equal to PWR_REP_THRESH). Also, periodic reporting and threshold-based reporting can be independently enabled or disabled by the base station.
After sending a PMRM, the MS will set both TOT_FRAMES and BAD_FRAMES counters to zero.
