1. 21-06-0493-07-0000 1 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0493-07-0000 Title: Media Independent Handover QOS Framework and parameters Date Submitted: March 9, 2006 Presented at IEEE 802.21 session #13 in Denver, Colorado Authors or Source(s): Nada Golmie, Ulises Olvera, Reijo Salminen, Mathieu Peresse, Eric Njedjou Abstract: Description of proposed MIH QoS Metrics and considerations of interworking with media specific technologies

2. 21-06-0493-07-0000 2 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 and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html> Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 http://standards.ieee.org/board/pat/guide.html

3. 21-06-0493-07-0000 3 Motivation and objectives Propose a QOS framework for the MIH including a set of MIH QOS performance metrics : 1. are derived from media and technology specific parameters. 2. scale well across different media types 3. can be provided as a service to the MIH user (application) MIH QOS framework consists of: 1. MIH QOS performance metrics (MIH QOSM) 2. Primitives to ( a) communicate MIH user (application) QOS requirements to the MIH (b) extract network specific measurements (c) set trigger thresholds for these measurements and (d) report QoS events upon threshold crossing (e) report real-time measurements to the MIH user

4. 21-06-0493-07-0000 4 Network QOS Model Access Network... IP Network Cloud DestinationSource Performance targets for audio and video applications Table I.1/ITU-T G1010 Application QoS Req. Voice Video Delay (ms)<150 ms PLoss<3%<1% Access Network Net. Perf. Param. QOS Classes Class 0Class 1Class 2Class 3Class4 IPTD100 ms400 ms100 ms400 ms1s IPDV50 ms UUU IPLR1 x 10 -3 IPER1 x 10 -4 Network IP performance objectives Table 1/ ITU-T Y.1541 No target performance metrics are published Requirements Static parameters Services Real-time parameters

5. 21-06-0493-07-0000 5 Network performance measures a layered approach TE ER Terminal Equipment Edge Router Protocol Stack LAN UNI User-Network Interface ER... IP Network Cloud (may be comprised of Network Sections belonging to one or more network operators) ER DSTSRC AN Segment #1 Segment #n Layer 1 Layer 2 Layer 3 Layer 4 Layer 5 End-to-end delay = delay AN + delay segment #1 + …+ delay segment#n + delay AN Layer 1 Layer 2 Example of delay calculation at layer 3

6. 21-06-0493-07-0000 6 Why do we care about QoS requirements in MIH and in 802.21? MIH is supposed to facilitate handovers among heterogeneous network technologies in order to provide seamless mobility and ubiquitous connectivity (“always best connected”) Providing seamless mobility has specific performance implications with respect to the application requirements, for example: Minimize handover latency so as to minimize the end-to-end delay and meet the application delay requirements Minimize the packet loss incurred during a handover so as to minimize the end-to-end packet loss and meet the application packet loss requirements.

7. 21-06-0493-07-0000 7 Proposed MIH QOS Framework PHY MAC RSSI, BER, Power level, Delay, Packet Loss, Delay Variation, Throughput, Network Layer Throughput, Delay, Transport Layer Throughput, delay, delay variation Application Layer MIH QOS Model (QOSM) PTD PDV PLR PER Throughput Extract parameter list Set parameter thresholds Cellular Delay, Packet Loss, Delay Variation, Throughput, Application QOS Req. MIH QOS parameters report MIH User

8. 21-06-0493-07-0000 8 Proposed MIH QOS Model (QOSM) The MIH QOSM consists of the following performance metrics: 1.Packet Transfer Delay (PTD): upper bound on the mean delay. 2.Packet Delay Variation (PDV): upper bound on the 1-10 -3 quantile on the PTD minus the minimum IPTD. 3.Packet Loss Ratio (PLR): upper bound on the packet loss probability. 4.Packet Errored Ratio (PER): 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.

9. 21-06-0493-07-0000 9 An example of mapping of MIH User QOS onto MIH QOSM 3GPP UMTS (TS 23.107)-ITU-T (Y.1541) Source: Liaison Statement on Mapping between ITU-T and 3GPP QoS Classes and Traffic Descriptors. Technical Specification Group Services and System Aspects. Meeting #23, Phoenix, AZ, USA, 15-18 March 2004 Real TimeBest Effort Conversational Preserve time relation (variation) between info entities of the stream Conversational Pattern (stringent and low delay) Streaming Preserve time relationship between info entities of the stream Interactive Request/Response pattern Preserve Payload content Background Destination is not expecting data within a certain time Preserve payload content Transfer delay SDU error ratio Transfer delay SDU error ratio Transfer delay SDU error ratio Class 0 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 IPTD≤400 ms,100 ms, 1 s, IPLR≤10 -3 ms, IPER≤10 -4 ms Class 3 Class 4 Class 5 Best Effort 3GPP UMTS QoS Y.1541 QoS Class

10. 21-06-0493-07-0000 10 An example for mapping MIH QoSM to media specific real-time parameters 802.21 QoS Metric ITU-T 1540/1541 IETF NSIS qspec 802.1 - ’AV bridging TG’ 802.11802.16802.20 PTDIPTDPath LatencyTBD (included in draft.1AS PAR) Delay Bound (.11e) dot11BSSLoadGroup (.11k) QoS Metrics Report (.11k) Maximum Latency Max_Latency PDVIPDVPath JitterTBD (included in draft.1AS PAR) Delay Bound (.11e) dot11BSSLoadGroup (.11k) QoS Metrics Report (.11k) Tolerated Jitter Max_Jitter PLRIPLRPacket Loss Ratio TBD dot11CountersGroup (.11k) QoS Metrics Report (.11k) N.A.Max_Packet_L oss_Rate PERIPERPacket Error Ratio TBD dot11CountersGroup (.11k) QoS Metrics Report (.11k) Packet Error Rate N.A. ThroughputN.A.BandwidthTBD Minimum/Mean/Peak Data Rate (.11e) Maximum Sustained Traffic Rate Peak Rate, Bucket Size, Token Rate Translation ’challenge’ colour codes: Easy Medium Hard Functions that are mapping the MIH QOSM to media specific parameters is left implementation dependent fctn

11. 21-06-0493-07-0000 11 Next steps Make changes to the 802.21 draft D05 Investigate availability and use of media specific parameters informative material or annex added to 802.21 spec. Work with IETF Next Steps In Signaling (NSIS) Group. Establish a liaison with NSIS and ITU-T study group 12 working on network performance objectives for IP-based services.

12. 21-06-0493-07-0000 12 Additions and extensions to the 802.21 draft D05

13. 21-06-0493-07-0000 13 Proposed MIH QOS Model (QOSM) Propose to add the following QOS performance metrics definition for characterizing the MIH service in IEEE 802.21 D05 draft on section 5.1.3 QoS in latest 802.21 draft (version 5) The MIH QOSM consists of the following metrics: 1.Packet Transfer Delay (PTD): upper bound on the mean delay 2.Packet Delay Variation (PDV): upper bound on the 1-10 -3 quantile on the PTD minus the minimum IPTD. 3.Packet Loss Ratio (PLR): upper bound on the packet loss probability. 4.Packet Errored Ratio (PER): 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.

14. 21-06-0493-07-0000 14 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.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

15. 21-06-0493-07-0000 15 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” expect potential changes to this section 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.

16. 21-06-0493-07-0000 16 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 The parameters used in these commands are those discovered by the proposed Link_Parameter_Discover command. The same applies to the MIH_Configure_Thresholds. Therefore the primitives described in section 7.3.7.2 and 7.4.8.1 need to be changed in order to reflect that.

17. 21-06-0493-07-0000 17 Proposed reusing Link/MIH QOS parameters report Propose to use existing Link/MIH events in order to report MIH QOS parameters to the MIH user: 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. Check consistency with primitives described in section 7.

18. 21-06-0493-07-0000 18 Proposed QoS requirements primitives between the MIH user and the MIH Propose to add the following primitives to provide the MIH user (application) a standardized interface in order to communicate their QOS needs. One primitive using the Command Service: MIH_Configure_QoS.request/response: From MIH user to MIH. Parameters: Packet Transfer Delay, Packet Delay Variation, Packet Loss Ratio, Packet Errored Ratio, Throughput, MIH User ID, Mobile Node Address. One primitive using the Event Service: MIH_Configure_QoS.indication: From MIH to MIH user Parameters: Packet Transfer Delay, Packet Delay Variation, Packet Loss Ratio, Packet Errored Ratio, Throughput, MIH User ID, Mobile Node Address.

19. 21-06-0493-07-0000 19 Backup slides

20. 21-06-0493-07-0000 20 Useful Performance Metrics Background slide 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 The reason we care about this slide from an MIH perspective is that the MIH is providing a service to the application the same way the network does. Therefore in order to provide a better service to the application, the MIH needs to track and characterize its functionality/service in terms of how they impact the application QOS.

21. 21-06-0493-07-0000 21 NSIS layering

22. 21-06-0493-07-0000 22 QoS NSLP in a node

23. 21-06-0493-07-0000 23 Basic sender- and receiver initiated NSLP operations

24. 21-06-0493-07-0000 24 Changing QoS Models in NSLP RESERVE {QSpec1} RESERVE {QSpec2, QSpec1} RESERVE {QSpec2, QSpec1} RESERVE {QSpec1} As RESERVE enters the region, the end-to-end reservation is mapped into the local QoS Model, and put on top of QSpec stack. It is then popped off the stack at the egress.