Evaluation Test Cases for Interactive Real-Time Media over Wireless Networks
draft-ietf-rmcat-wireless-tests-02

Abstract

It is evident that to ensure seamless and robust user experience across all type of access networks multimedia communication suits should adapt to the changing network conditions. There is an ongoing effort in IETF RMCAT working group to standardize rate adaptive algorithm(s) to be used in the real-time interactive communication. In this document test cases are described to evaluate the performances of the proposed endpoint adaptation solutions in LTE networks and Wi-Fi networks. The proposed algorithms should be evaluated using the test cases defined in this document to select most optimal solutions.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on November 8, 2016.

Copyright Notice

Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Terminologies
• 3. Cellular Network Specific Test Cases
• 3.1. Varying Network Load
• 3.1.1. Network Connection
• 3.1.2. Simulation Setup
• 3.2. Bad Radio Coverage
• 3.2.1. Network connection
• 3.2.2. Simulation Setup
• 3.3. Desired Evaluation Metrics for cellular test cases
• 4. Wi-Fi Networks Specific Test Cases
• 4.1. Bottleneck in Wired Network
• 4.1.1. Network topology
• 4.1.2. Test setup
• 4.1.3. Typical test scenarios
• 4.1.4. Expected behavior
• 4.2. Bottleneck in Wi-Fi Network
• 4.2.1. Network topology
• 4.2.2. Test setup
• 4.2.3. Typical test scenarios
• 4.2.4. Expected behavior
• 4.3. Potential Potential Test Cases
• 4.3.1. EDCA/WMM usage
• 4.3.2. Legacy 802.11b Effects
• 5. Conclusion
• 6. Acknowledgements
• 7. IANA Considerations
• 8. Security Considerations
• 9. References
• 9.1. Normative References
• 9.2. Informative References
• Authors' Addresses

1. Introduction

Wireless networks (both cellular and Wi-Fi [IEEE802.11] local area network) are an integral part of the Internet. Mobile devices connected to the wireless networks produces huge amount of media traffic in the Internet. They covers the scenarios of having a video call in the bus to media consumption sitting on a couch in a living room. It is a well known fact that the characteristic and challenges for offering service over wireless network are very different than providing the same over a wired network. Even though RMCAT basic test cases defines number of test cases that covers lots of effects of the impairments visible in the wireless networks but there are characteristics and dynamics those are unique to particular wireless environment. For example, in the LTE the base station maintains queues per radio bearer per user hence it gives different interaction when all traffic from user share the same queue. Again, the user mobility in a cellular network is different than the user mobility in a Wi-Fi network. Thus, It is important to evaluate the performance of the proposed RMCAT candidates separately in the cellular mobile networks and Wi-Fi local networks (IEEE 802.11xx protocol family ).

RMCAT evaluation criteria [I-D.ietf-rmcat-eval-criteria] document provides the guideline to perform the evaluation on candidate algorithms and recognizes wireless networks to be important access link. However, it does not provides particular test cases to evaluate the performance of the candidate algorithm. In this document we describe test cases specifically targeting cellular networks such as LTE networks and Wi-Fi local networks.

2. Terminologies

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 [RFC2119]

3. Cellular Network Specific Test Cases

A cellular environment is more complicated than a wireline ditto since it seeks to provide services in the context of variable available bandwidth, location dependencies and user mobilities at different speeds. In a cellular network the user may reach the cell edge which may lead to a significant amount of retransmissions to deliver the data from the base station to the destination and vice versa. These network links or radio links will often act as a bottleneck for the rest of the network which will eventually lead to excessive delays or packet drops. An efficient retransmission or link adaptation mechanism can reduce the packet loss probability but there will still be some packet losses and delay variations. Moreover, with increased cell load or handover to a congested cell, congestion in transport network will become even worse. Besides, there are certain characteristics which make the cellular network different and challenging than other types of access network such as Wi-Fi and wired network. In a cellular network -

[QoS-3GPP] to ensure high quality user experience, adaptive real-time applications are desired.

• The bottleneck is often a shared link with relatively few users.
  • The cost per bit over the shared link varies over time and is different for different users.
  • Left over/ unused resource can be grabbed by other greedy users.
• Queues are always per radio bearer hence each user can have many of such queues.
• Users can experience both Inter and Intra Radio Access Technology (RAT) handovers ("handover" definition in [HO-def-3GPP] ).
• Handover between cells, or change of serving cells (see in [HO-LTE-3GPP] and [HO-UMTS-3GPP] ) might cause user plane interruptions which can lead to bursts of packet losses, delay and/or jitter. The exact behavior depends on the type of radio bearer. Typically, the default best effort bearers do not generate packet loss, instead packets are queued up and transmitted once the handover is completed.
• The network part decides how much the user can transmit.
• The cellular network has variable link capacity per user
  • Can vary as fast as a period of milliseconds.
  • Depends on lots of facts (such as distance, speed, interference, different flows).
  • Uses complex and smart link adaptation which makes the link behavior ever more dynamic.
  • The scheduling priority depends on the estimated throughput.
• Both Quality of Service (QoS) and non-QoS radio bearers can be used.

Hence, a real-time communication application operating in such a cellular network need to cope with shared bottleneck link and variable link capacity, event likes handover, non-congestion related loss, abrupt change in bandwidth (both short term and long term) due to handover, network load and bad radio coverage. Even though 3GPP define QoS bearers

Different mobile operators deploy their own cellular network with their own set of network functionalities and policies. Usually, a mobile operator network includes 2G, EDGE, 3G and 4G radio access technologies. Looking at the specifications of such radio technologies it is evident that only 3G and 4G radio technologies can support the high bandwidth requirements from real-time interactive video applications. The future real-time interactive application will impose even greater demand on cellular network performance which makes 4G (and beyond radio technologies) more suitable access technology for such genre of application.

The key factors to define test cases for cellular network are

[LTE-simulator].

• Shared and varying link capacity
• Mobility
• Handover

However, for cellular network it is very hard to separate such events from one another as these events are heavily related. Hence instead of devising separate test cases for all those important events we have divided the test case in two categories. It should be noted that in the following test cases the goal is to evaluate the performance of candidate algorithms over radio interface of the cellular network. Hence it is assumed that the radio interface is the bottleneck link between the communicating peers and that the core network does not add any extra congestion in the path. Also the combination of multiple access technologies such as one user has LTE connection and another has Wi-Fi connection is kept out of the scope of this document. However, later those additional scenarios can also be added in this list of test cases. While defining the test cases we assumed a typical real-time telephony scenario over cellular networks where one real-time session consists of one voice stream and one video stream. We recommend that an LTE network simulator is used for the test cases defined in this document, for example-NS-3 LTE simulator

3.1. Varying Network Load

The goal of this test is to evaluate the performance of the candidate congestion control algorithm under varying network load. The network load variation is created by adding and removing network users a.k.a. User Equipments (UEs) during the simulation. In this test case, each of the user/UE in the media session is an RMCAT compliant endpoint. The arrival of users follows a Poisson distribution, which is proportional to the length of the call, so that the number of users per cell is kept fairly constant during the evaluation period. At the beginning of the simulation there should be enough amount of time to warm-up the network. This is to avoid running the evaluation in an empty network where network nodes are having empty buffers, low interference at the beginning of the simulation. This network initialization period is therefore excluded from the evaluation period.

This test case also includes user mobility and competing traffic. The competing traffics includes both same kind of flows (with same adaptation algorithms) and different kind of flows (with different service and congestion control). The investigated congestion control algorithms should show maximum possible network utilization and stability in terms of rate variations, lowest possible end to end frame latency, network latency and Packet Loss Rate (PLR) at different cell load level.

3.1.1. Network Connection

Each mobile user is connected to a fixed user. The connection between the mobile user and fixed user consists of a LTE radio access, an Evolved Packet Core (EPC) and an Internet connection. The mobile user is connected to the EPC using LTE radio access technology which is further connected to the Internet. The fixed user is connected to the Internet via wired connection with no bottleneck (practically infinite bandwidth). The Internet and wired connection in this setup does not add any network impairments to the test, it only adds 10ms of one-way transport propagation delay.

                       
                 uplink                     
++)))        +-------------------------->         
++-+      ((o))                                   
|  |       / \     +-------+     +------+    +---+
+--+      /   \----+       +-----+      +----+   |
         /     \   +-------+     +------+    +---+
 UE         BS        EPC        Internet    fixed
             <--------------------------+          
                      downlink                    

                             uplink
                       +----------------->+
      +------+                                       +------+
      | MN_1 |))))                             /=====| FN_1 |
      +------+    ))                          //     +------+
          .        ))                        //         .    
          .         ))                      //          .    
          .          ))                    //           .    
      +------+         +----+         +-----+        +------+
      | MN_N | ))))))) |    |         |     |========| FN_N |
      +------+         |    |         |     |        +------+
                       | AP |=========| FN0 |
     +----------+      |    |         |     |      +----------+
     | MN_tcp_1 | )))) |    |         |     |======| MN_tcp_1 |
     +----------+      +----+         +-----+      +----------+
           .          ))                 \\             .    
           .         ))                   \\            .    
           .        ))                     \\           .    
     +----------+  ))                       \\     +----------+
     | MN_tcp_M |)))                         \=====| MN_tcp_M |
     +----------+                                  +----------+
                      +<-----------------+
                              downlink