Ieee p802. 21m Media Independent Services Framework Project
Deriving generic IEEE 802.21 QoS parameters
Download 3.39 Mb.
|
- Navigate this page:
- Packet loss rate
- Packet error rate
- Average transfer delay
- Packet transfer delay jitter
- (to be excluded) (informative) Handover procedures
Deriving generic IEEE 802.21 QoS parametersGeneralThe following subclauses describe how to derive generic QoS parameters from IEEE Std 802.11 link measurement parameters. This derivation relies on incremental values of counters as specified in the IEEE Std 802.11. Note that the parameters are unicast parameters that are unrelated to multicast traffic. Packet loss rateTo calculate the packet loss rate (PLR), one uses Equation (1).  (1)
According to IEEE Std 802.11, a packet is a MAC user data packet or MAC service data unit (MSDU). The PLRMSDU can be derived from the Transmit Stream/Category Measurement Report using Equation (2).
=
The packet error rate (PER) can be calculated using Equation (3).  (3)
Unlike for PLR, this parameter is only defined for the IEEE 802.11 MPDU. The PER can be derived from the STA Statistics Report information element using Equation (4).  (4)
Average transfer delayIn IEEE Std 802.11k, the transmit delay (MSDU delay) is defined as follows: Transmit delay (MSDU delay): The delay shall be measured from the time the MSDU is passed to the MAC sublayer until the point at which the entire MSDU has been successfully transmitted including receipt of the final ACK. If the average MSDU transmit delay is used for the IEEE 802.21 average transfer delay, it can be derived from Transmit Stream/Category Measurement Report.
QoS Metric information element includes:
Average Transmit Delay parameters Variance calculation using discrete density function is given as 
Therefore, the packet transfer delay jitter for MSDU level is 
where,
N = the number of bins of Transmit Delay Histogram Pi= the value (measured percentile) of ith bin of Transmit Delay Histogram xi = the mean value of the delay range of ith bin (to be excluded)
|
(2)
|
MIS message name |
Reference point |
|
MIS_Capability_Discover |
RP1, RP2, RP3, RP4, RP5 |
|
MIS_Event_Subscribe |
RP1, RP3 |
|
MIS_Event_Unsubscribe |
RP1, RP3 |
|
MIS_Register |
RP1, RP3, RP5 |
|
MIS_DeRegister |
RP1, RP3, RP5 |
|
|
|
|
MIS_Link_Detected |
RP1, RP3 |
|
MIS_Link_Up |
RP1, RP3, RP5 |
|
MIS_Link_Down |
RP1, RP3, RP5 |
|
MIS_Link_Parameters_Report |
RP1, RP3, RP5 |
|
MIS_Link_Going_Down |
RP1, RP3, RP2 |
|
MIS_Link_Handover_Imminent |
RP1, RP3, RP2 |
|
MIS_Link_Handover_Complete |
RP1, RP3 |
|
|
|
|
MIS_Link_Get_Parameters |
RP1, RP3, RP2 |
|
MIS_Link_Configure_Thresholds |
RP1, RP3 |
|
MIS_Link_Actions |
RP1, RP3 |
|
MIS_Net_HO_Candidate_Query |
RP1, RP3 |
|
MIS_MN_HO_Candidate_Query |
RP1, RP3 |
|
MIS_N2N_HO_Query_Resources |
RP5 |
|
MIS_MN_HO_Commit |
RP1, RP3 |
Table D.1—Mapping MIS messages to reference points (continued)
-
MIS message name
Reference point
MIS_Net_HO_Commit
RP1, RP3
MIS_N2N_HO_Commit
RP5
MIS_MN_HO_Complete
RP1, RP2, RP3
MIS_N2N_HO_Complete
RP5
MIS_Get_Information
RP1, RP2, RP3, RP4, RP5
MIS_Push_Information
RP1, RP2, RP3, RP4, RP5
MIS_Auth
RP1, RP3
MIS_Termination_Auth
RP1, RP3
MIS_Push_Key
RP1, RP3
Share with your friends: