RE: stds-80220-requirements: Latency and Packet Error rate (4.1.8 )
Dear all,
Wish you have a happy and healthy New Year!
The four classes of traffic are similar to ITU recommendations G.1010. One
possibility would be to determine the corresponding performance targets for
each of the classes, then map these classes to the DiffServ classes. My
original suggestion is to bypass the translation between the four ITU
classes and DiffServ classes. Based on my understanding, an application
should have already been placed into an appropriate DiffServ class at the
network layer before the data packets get to the MAC and PHY layers. In that
case, we need only to specify the performance requirements for 802.20 to
support the various DiffServ classes, which in turn depend on the end user
requirements for the various applications.
I think that the IETF document as quoted:
"draft-baker-diffserv-basic-classes-01.txt" is a good reference as it
provides guidelines for configuring the DiffServ classes to meet various
application requirements. Would anybody know if there would be a similar
replacement for this draft after this particular document expires on April
2004?
While this Internet draft provides a detail description on how to use the
different DiffServ classes, the required probability of packet loss or error
rate is not very clear. For example, for the Low Latency Service class, it
was stated in the draft (page 25) that: "The probability of loss of CS3
traffic may not exceed the probability of AF21 and AF21 traffic may not
exceed the probability of loss of AF22 traffic, which in turn may not exceed
the probability of loss of AF23."
This Internet draft would be very helpful in terms of mapping an application
to a DiffServ class, and to determine the "relative" performance between
different classes and subclasses. However, it seems that we still have to
face the problem of determining the error rate limits for the different
classes of traffic somewhere, such as in the evaluation criteria document or
some kinds of minimum performance requirements standard, if not in the
current requirements document. Even in the 3GPP standard, there are various
service classes defined to support different latency and error rate
performance targets, as quoted in November's contribution C802.20-03/106.
Best regards,
Anna.
-----Original Message-----
From: owner-stds-80220-requirements@majordomo.ieee.org
[mailto:owner-stds-80220-requirements@majordomo.ieee.org] On Behalf Of
Migaldi Scott-W10265
Sent: Tuesday, January 06, 2004 3:30 PM
To: 'Branislav Meandzija'; Humbert, John J [NTWK SVCS];
stds-80220-requirements@ieee.org
Cc: Landon, Jim [GMG]
Subject: RE: stds-80220-requirements: Latency and Packet Error rate (4.1.8 )
This is a good step forward and I offer a more streamlined requirement for
the group's consideration . This requirement is similar to those found in
other wireless data service specification and requirements documents.
--
The system shall support a variety of traffic classes with different latency
and packet error rate requirements as suggested in the RFC "Configuration
Guidelines for DiffServ Service Classes"
http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-01.tx
t.
Class Attributes of Traffic
-----------------------------------------------------------
Conversational | Two-way, low delay, low data loss
| rate, sensitive to delay variations.
-----------------------------------------------------------
Streaming | Same as conversational, one-way,
| less sensitive to delay. May require
| high bandwidth.
-----------------------------------------------------------
Interactive | Two-way, bursty, variable
| bandwidth requirements moderate
| delay, moderate data loss rate
| correctable in part.
-----------------------------------------------------------
Background | Highly tolerant to delay and data
| loss rate has variable bandwidth.
-----------------------------------------------------------
--
-----Original Message-----
From: Branislav Meandzija [mailto:bran@arraycomm.com]
Sent: Tuesday, November 18, 2003 21:11
To: Humbert, John J [NTWK SVCS]; stds-80220-requirements@ieee.org
Cc: Landon, Jim [GMG]
Subject: RE: stds-80220-requirements: Latency and Packet Error rate
(4.1.8)
(Please ignore my first message on this subject, this is the complete text)
Given that the air interface is going to be used for IP traffic in the
DiffServ context, I propose we replace the text of 4.1.8 and 4.1.9 with the
following paragraph or delete it as the below requirement is implied by
4.1.14 and 4.4.1:
Proposed Text: combining 4.1.8 and 4.1.9 or delete 4.1.8 and 4.1.9
4.1.8 Latency and Packet Error Rate
The system shall support a variety of traffic classes with different latency
and packet error rate requirements as suggested in the RFC "Configuration
Guidelines for DiffServ Service Classes"
http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-01.tx
t.
Rationale
The service classes, specified in the RFC, define the required treatment for
IP traffic in order to meet user, application or network expectations. The
RFC associates application requirements with the different service classes
and suggests packet flow treatment (i.e. Active Queue Management
techniques). Different operators are given the flexibility to define
different latency targets and packet error rates in conjunction with system
specifications and SLAs within the framework meaningful for IP networks and
defined by DiffServ and the RFC. The Table 1 below (from the RFC)
illustrates the relationship between service classes and DS codepoint(s)
assignment with application examples (application requirements are in the
RFC). Table 2 (also from the RFC) summarizes suggested QoS mechanisms used
for each class.
------------------------------------------------------------------
| Service | DSCP | DSCP | Application |
| Class name | name | value | Examples |
|===============+=========+=============+==========================|
|Administration | CS7 | 111000 | Heartbeats, SSH, Telnet |
|---------------+---------+-------------+--------------------------|
|Network Control| CS6 | 110000 | Network routing |
|---------------+---------+-------------+--------------------------|
| Telephony | EF,CS5 |101010,101000| IP Telephony |
|---------------+---------+-------------+--------------------------|
| Multimedia |AF41,AF42|100010,100100| Video conferencing |
| Conferencing | AF43 |100110 | Interactive gaming |
|---------------+---------+-------------+--------------------------|
| Multimedia |AF31,AF32|011010,011100|Broadcast TV, Pay per view|
| Streaming |AF33, CS4|011110,100000|Video surveillance |
|---------------+---------+-------------+--------------------------|
| Low Latency |AF21,AF22|010010,010100|Client/server transactions|
| Data |AF23, CS3|010110,011000|peer-to-peer signaling |
|---------------+---------+-------------+--------------------------|
|High Throughput|AF11,AF12|001010,001100|Store&forward applications|
| Data |AF13, CS2|001110,010000|Non-critcal OAM&P |
|---------------+---------+-------------+--------------------------|
| Standard | DF,(CS0)| 000000 | Undifferentiated |
| | | | applications |
|---------------+---------+-------------+--------------------------|
| Low Priority | CS1 | 001000 | Any flow that has no BW |
| Data | | | assurance |
------------------------------------------------------------------
Table 1: DSCP to Service Class Mapping
------------------------------------------------------------------
| Service | DSCP | Conditioning at | PHB | Queuing| AQM|
| Class | | DS Edge |Reference| | |
|===============+======+===================+=========+========+====|
|Administration | CS7 |Police using sr+bs | RFC2474 |Priority| No |
|---------------+------+-------------------+---------+--------+----|
|Network Control| CS6 |Police using sr+bs | RFC2474 | Rate | No |
|---------------+------+-------------------+---------+--------+----|
| Telephony |EF,CS5|Police using sr+bs | RFC3246 |Priority| No |
|---------------+------+-------------------+---------+--------+----|
| | AF41 | | | | Yes|
| Multimedia | AF42 | Using trTCM | RFC2597 | Rate | per|
| Conferencing | AF43 | (RFC2698) | | |DSCP|
|---------------+------+-------------------+---------+--------+----|
| | AF31 | Police using sr+bs| | | |
| |------+-------------------| | | Yes|
| Multimedia | AF32 | Police sum using | | Rate | per|
| Streaming | AF33 | sr+bs | RFC2597 | |DSCP|
| |------+-------------------| | |----|
| | CS4 |Police using sr+bs | | | No |
|---------------+------+-------------------+---------+--------+----|
| | AF21 | | | | Yes|
| Low | AF22 | Using srTCM | | | per|
| Latency | AF23 | (RFC 2697) | RFC2597 | Rate |DSCP|
| Data |------+-------------------| | |----|
| | CS3 |Police using sr+bs | | | No |
|---------------+------+-------------------+---------+--------+----|
| | AF11 | | | | Yes|
| High | AF12 | Using srTCM | | | per|
| Throughput | AF13 | (RFC 2697) | RFC2597 | Rate |DSCP|
| Data |------+-------------------| | |----|
| | CS2 |Police using sr+bs | | | No |
|---------------+------+-------------------+---------+--------+----|
| Standard | DF | Not applicable | RFC2474 | Rate | Yes|
|---------------+------+-------------------+---------+--------+----|
| Low Priority | CS1 | Not applicable | pdb-le | Rate | Yes|
| Data | | | -draft | | |
------------------------------------------------------------------
Table 2: Summary of QoS Mechanisms used for each Service Class
-----Original Message-----
From: owner-stds-80220-requirements@majordomo.ieee.org
[mailto:owner-stds-80220-requirements@majordomo.ieee.org]On Behalf Of
Humbert, John J [NTWK SVCS]
Sent: Thursday, November 13, 2003 4:13 PM
To: stds-80220-requirements@ieee.org
Cc: Landon, Jim [GMG]
Subject: stds-80220-requirements: Latency and Packet Error rate (4.1.8)
Attached is the contribution that Anna provided at the Plenary meeting,
1) The CG needs to come to consensus on the TBR values.
2) Is there still a need to specify ARQ loop delay to be consistent
with the PAR?
<<Latency&PacketErrorRate.doc>>
John J. Humbert
6220 Sprint Parkway
Mailstop KSOPHD0504 - 5D276
Overland Park, KS 66251-6118
PCS (816) 210-9611