IEEE 802 21 MEDIA INDEPENDENT HANDOVER DCN 21

• IEEE 802. 21 MEDIA INDEPENDENT HANDOVER • DCN: 21 -06 -0493 -02 -0000 • Title: Media Independent Handover QOS Framework and parameters • Date Submitted: February 17, 2006 • Presented at IEEE 802. 21 session #13 in Denver, Colorado • Authors or Source(s): Nada Golmie, Ulises Olvera, Reijo Salminen • Abstract: Description of proposed MIH Qo. S Metrics and considerations of interworking with HL and media specific technologies 21 -06 -0493 -02 -0000 1

IEEE 802. 21 presentation release statements • This document has been prepared to assist the IEEE 802. 21 Working Group. It is offered as a basis for discussion and is not binding on the contributing • • individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802. 21. The contributor is familiar with IEEE patent policy, as outlined in Section 6. 3 of the IEEE-SA Standards Board Operations Manual <http: //standards. ieee. org/guides/opman/sect 6. html#6. 3> and in Understanding Patent Issues During IEEE Standards Development http: //standards. ieee. org/board/pat/guide. html> 21 -06 -0493 -02 -0000 2

Motivation and objectives • Propose a QOS framework for the MIH including a set of MIH QOS performance metrics that: 1. 2. 3. are derived from media and technology specific parameters across layers 1, 2, and 3 scale well across different media types are provided as a service to the application layer • MIH QOS framework consists of: 1. 2. MIH QOS performance metrics Primitives to 1. 2. 3. (a) extract network specific measurements (b) set trigger thresholds for these measurements and (c) report Qo. S events upon threshold crossing Mechanism to relay MIH QOS to application 21 -06 -0493 -02 -0000 3

Proposed MIH QOS Framework Application Layer MIH User MIH QOS parameters report Transport Layer MIH QOS Performance Metrics Throughput, delay variation Network Layer Throughput, Delay, Cellular Delay, Packet Loss, Delay Variation, Throughput, MAC Delay, Packet Loss, Delay Variation, Throughput, Extract parameter list Set parameter thresholds QOS parameter mapping implementation specific PHY RSSI, BER, Power level, 21 -06 -0493 -02 -0000 4

Figure 1/Y. 1541 – UNI-to-UNI reference path for network Qo. S objectives 21 -06 -0493 -02 -0000 5

Useful Performance Metrics ITU-T Y. 1541: Network Performance objectives for IP-based services. Metrics defined in ITU-T Y. 1540 • IP Packet Transfer Delay (IPTD): upper bound on the mean end-to-end delay (UNI-to-UNI). • IP Packet Delay Variation (IPDV): upper bound on the 1 -10 -3 quantile on the IPTD minus the minimum IPTD. • IP Packet Loss Ratio (IPLR): upper bound on the packet loss probability. • IP Packet Errored Ratio (IPER): upper bound on the number of errored packets per total packets sent. Other useful measures • Throughput (bits/s): the number of bits successfully received divided by the time it took to transmit them over the medium 21 -06 -0493 -02 -0000 6

Proposed MIH QOS Performance Metrics Propose to add the following QOS performance metrics definition for characterizing the MIH service in IEEE 802. 21 D 05 draft on section 5. 1. 3 Qo. S in latest 802. 21 draft (version 5) 1. IP Packet Transfer Delay (IPTD): upper bound on the mean end-to-end delay. 2. IP Packet Delay Variation (IPDV): upper bound on the 1 -10 -3 quantile on the IPTD minus the minimum IPTD. 3. IP Packet Loss Ratio (IPLR): upper bound on the packet loss probability. 4. IP Packet Errored Ratio (IPER): upper bound on the number of errored packets per total packets sent. 5. Throughput (bits/s): the number of bits successfully received divided by the time it took to transmit them over the medium. 21 -06 -0493 -02 -0000 7

Translation considerations of MIH Qo. S Metrics to 802 media specific parameters 802. 21 Qo. S Metric ITU-T 1540/1541 IETF NSIS qspec 802. 1 - ’AV bridging TG’ 802. 11 802. 16 802. 20 IPTD Path Latency TBD (included in draft. 1 AS PAR) Delay Bound (. 11 e) Maximum Latency Max_Latency TBD (included in draft. 1 AS PAR) Delay Bound (. 11 e) Tolerated Jitter Max_Jitter Packet Loss Ratio TBD dot 11 Counters. Group (. 11 k) N. A. Max_Packet_L oss_Rate Packet Error Ratio TBD Packet Error Rate N. A. Bandwidth TBD Maximum Sustained Traffic Rate Peak Rate, Bucket Size, Token Rate IPDV IPLR IPER Throughput N. A. Path Jitter dot 11 BSSLoad. Group (. 11 k) Qo. S Metrics Report (. 11 k) dot 11 Counters. Group (. 11 k) Qo. S Metrics Report (. 11 k) Minimum/Mean/Peak Data Rate (. 11 e) Translation ’challenge’ colour codes: Easy Medium Hard 21 -06 -0493 -02 -0000 8

3 GPP UMTS (TS 23. 107)-ITU-T (Y. 1541) Source: Liaison Statement on Mapping between ITU-T and 3 GPP Qo. S Classes and Traffic Descriptors. Technical Specification Group Services and System Aspects. Meeting #23, Phoenix, AZ, USA, 15 -18 March 2004 3 GPP UMTS Qo. S Real Time Conversational • Preserve time relation (variation) between info entities of the stream Y. 1541 Qo. S Class 0 Streaming Best Effort Interactive Background • Preserve time • Request/Respons relationship between info e pattern entities of the stream • Preserve Payload content • Destination is not expecting data within a certain time • Transfer delay • SDU error ratio • Conversational Pattern (stringent and low delay) • Preserve payload content IPTD≤ 100 ms, IPDV≤ 50 ms IPLR≤ 10 -3 ms, IPER≤ 10 -4 ms Class 1 IPTD≤ 400 ms, IPDV≤ 50 ms IPLR≤ 10 -3 ms, IPER≤ 10 -4 ms Class 2 Class 3 IPTD≤ 400 ms, 1 s, IPLR≤ 10 -3 ms, IPER≤ 10 -4 ms Class 4 Class 5 21 -06 -0493 -02 -0000 Best Effort 9

Proposed Link/MIH parameter discovery commands Propose to add the following MIH/Link commands for discovering link and network specific parameters Add following command to Table 5, section 6. 2, page 41 • Link Parameter Discover: Discover link specific parameters Add the following command to Table 4, section 6. 2. 6. 1, page 41 • MIH Parameter Discover: Discover higher layers specific parameters 21 -06 -0493 -02 -0000 10

Proposed Link/MIH parameter discovery primitives (2) Propose to add the following MIH/Link primitives for discovering link and network specific parameters: Add following command to Table 14, section 7. 2. 2. 1, page 65 • MIH Parameter Discover: Discover higher layer specific parameters Add the following command to Table 15, section 7. 2. 2. 2, page 65 • Link Parameter Discover: Discover link specific parameters Add the following primitives in section 7: “ 7. 3. 20 Link_Parameter_Discover. request” “ 7. 3. 21 Link_Parameter_Discover. response” “ 7. 4. 16 MIH_Parameter_Discover. request” “ 7. 4. 17 MIH_Parameter_Discover. response” Q 1: Do we want to make these information messages instead of commands? Q 2: section 7. 2. 1 lists media dependent SAPs. Additional information found in each of the standards could get fed into that section. The additional primitives in the media independent sections should address the scalability issue for future standards that we do nothing about today. A: If we use the example in slide, we could make any parameter fit ITU-T IPXX convention, just as defined in the example table 11 21 -06 -0493 -02 -0000

Proposed re-using Link/MIH parameter threshold setting commands Propose to re-utilize existing commands for setting Link/MIH parameter thresholds. • MIH Configure Link thresholds: Table 4, section 6. 2. 6. 1, page 41 • Link Configure thresholds: Table 5, section 6. 2. 6. . 2, page 41 Q: Link_Configure_Thresholds. request in section 7. 3. 7. 2, page 70 lists a number of parameters for the link. Is this an enumerated list? These parameters should correspond to the ones discovered by the Link_Parameter_Discover command. The same applies to MIH_Configure_Thresholds. request in section 7. 4. 8. 1 listed as “MIH_Configure”. 21 -06 -0493 -02 -0000 12

Proposed reusing Link/MIH QOS parameters report Propose to use existing Link/MIH events in order to report MIH QOS parameters to the application layer: Table 2, section 6. 1. 7 page 37: • Link Parameters Change: Link parameters have crossed specified thresholds Table 3, section 6. 1. 8, page 37 • MIH Link Parameters Report: Link parameters have crossed specified threshold and need to be reported. Sill need to check primitives in section 7. 21 -06 -0493 -02 -0000 13