11

ProjectProject IEEE 802 Executive Committee Study Group on Mobile Broadband Wireless Access IEEE 802 Executive Committee Study Group on Mobile Broadband Wireless Access <<http://ieee802.org/20http://ieee802.org/20>>

TitleTitle Implication of End-user QoS requirements on PHY & MACImplication of End-user QoS requirements on PHY & MAC

Date SubmittedDate Submitted 2003-11-102003-11-10

Source(s)Source(s) Anna TeeAnna Tee Voice: 972-761-7437Voice: 972-761-7437Fax: 972-761-7909Fax: 972-761-7909Email: a.tee@samsung.comEmail: a.tee@samsung.com

Joseph R. ClevelandJoseph R. Cleveland Voice: 972-761-7981Voice: 972-761-7981Fax: 972-761-7909Fax: 972-761-7909Email: jclevela@sta.samsung.comEmail: jclevela@sta.samsung.com

Jin Weon ChangJin Weon Chang Voice: +82-31-279-5117Voice: +82-31-279-5117Fax: +82-31-279-5130Fax: +82-31-279-5130Email: jwchang@ieee.orgEmail: jwchang@ieee.org

Re:Re: 802.20 WG Call for Contributions802.20 WG Call for Contributions

AbstractAbstract This document gave a brief overview of the QoS classification and requirements by ITU and 3GPP, and used the This document gave a brief overview of the QoS classification and requirements by ITU and 3GPP, and used the information to derive the latency and error rate requirements for 802.20 in support of IETF DiffServ structure. information to derive the latency and error rate requirements for 802.20 in support of IETF DiffServ structure.

PurposePurpose Contribute to the discussion and development of the 802.20 Requirements on Latency and FER as related to QoSContribute to the discussion and development of the 802.20 Requirements on Latency and FER as related to QoS

NoticeNotice This document has been prepared to assist the IEEE 802.20 Working Group. It is offered as a basis for discussion and This document has been prepared to assist the IEEE 802.20 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 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 in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.contained herein.

ReleaseRelease The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, 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 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 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 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 MBWA ECSG.also acknowledges and accepts that this contribution may be made public by IEEE 802 MBWA ECSG.

Patent PolicyPatent Policy The contributor is familiar with IEEE patent policy, as outlined in The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations ManualSection 6.3 of the IEEE-SA Standards Board Operations Manual < <http://standards.ieee.org/guides/opman/sect6.html#6.3http://standards.ieee.org/guides/opman/sect6.html#6.3> and in Understanding Patent Issues During IEEE Standards > and in Understanding Patent Issues During IEEE Standards Development <Development <http://http://standards.ieee.org/board/pat/guide.htmlstandards.ieee.org/board/pat/guide.html>.>.

C802.2-03/106

22

Implication of End-user QoS Implication of End-user QoS

Requirements on PHY & MACRequirements on PHY & MAC

Joseph ClevelandJoseph Cleveland

Anna TeeAnna Tee

November 03, AlbuquerqueNovember 03, Albuquerque

33

Scope of 802.20Scope of 802.20

As described in the PAR and quoted in Section 1.3 of 802.20 As described in the PAR and quoted in Section 1.3 of 802.20 Requirements Document Rev. 8c [1]:Requirements Document Rev. 8c [1]:

““Specification of physical and medium access control layers of an air Specification of physical and medium access control layers of an air interface for interoperable mobile broadband wireless access systems, interface for interoperable mobile broadband wireless access systems, operating in licensed bands below 3.5 GHz, operating in licensed bands below 3.5 GHz, optimized for IP-data optimized for IP-data transporttransport, with peak data rates per user in excess of 1 Mbps. It , with peak data rates per user in excess of 1 Mbps. It supports various vehicular mobility classes up to 250 Km/h in a supports various vehicular mobility classes up to 250 Km/h in a MAN environmentMAN environment and targets spectral efficiencies, sustained user and targets spectral efficiencies, sustained user data rates and numbers of active users that are all significantly higher data rates and numbers of active users that are all significantly higher than achieved by existing mobile systems.”than achieved by existing mobile systems.”

44

ApplicationsApplications

Examples of possible applications that are Examples of possible applications that are IP-based data, in mobility IP-based data, in mobility environment of up to 250 km/h in a MAN environmentenvironment of up to 250 km/h in a MAN environment, as described in , as described in Section 2 of the Requirements document:Section 2 of the Requirements document:

VoIP / Video conferencingVoIP / Video conferencing Audio / video messaging Audio / video messaging Video (e.g., MPEG2, MPEG4, H.323,…)Video (e.g., MPEG2, MPEG4, H.323,…) Web browsing (HTTP, TCP)Web browsing (HTTP, TCP) E-mail (UDP)E-mail (UDP) File Upload and Download (FTP, TCP)File Upload and Download (FTP, TCP) Video and/or audio streaming Video and/or audio streaming IP multicastIP multicast Interactive internet gamingInteractive internet gaming TelemetryTelemetry Location based services (e.g., E-911)Location based services (e.g., E-911) Telematics (= a subset of the above + vehicular specific applications)Telematics (= a subset of the above + vehicular specific applications) ……

55

Application requirements to the end-usersApplication requirements to the end-users

Major parameters are: Major parameters are: Data RateData Rate LatencyLatency Latency variation Latency variation Information loss ratioInformation loss ratio

Various applications can be classified into different groups, Various applications can be classified into different groups, based on their latency and error tolerance requirements. based on their latency and error tolerance requirements.

66

User-centric Delay and Packet Loss User-centric Delay and Packet Loss requirements – ITU G.1010*requirements – ITU G.1010*

0%

Packet Loss

Command/ control

(eg Telnet,Interactive

games)

Conversationalvoice and video

Voice/videomessaging

Streamingaudio/video

Transactions(eg E-commerce,Web-browsing, E-

mail access)

Messaging,Downloads

(eg FTP,still image)

Fax

Background(eg Usenet)

5%

100 msec 1 sec 10 sec 100 sec

Zeroloss

Delay

Source: ITU G.1010 [“Draft New Recommendation G.QoSRQT – End-user Multimedia QoS Categories”, ITU-T study group 12, contribution 37, August 2001]

77

End-user QoS Categories Mapping End-user QoS Categories Mapping - ITU G.1010- ITU G.1010

Errortolerant

Errorintolerant

Interactive(delay <<1 sec)

Responsive(delay ~2 sec)

Timely(delay ~10 sec)

Non-critical(delay >>10 sec)

Conversationalvoice and video

Voice/video messaging

Streaming audioand video

Fax

Background(eg Usenet)

Messaging,Downloads

(eg FTP, still image)

Transactions(eg E-commerce,WWW browsing,

Email access)

Command/control(eg Telnet,

interactive games)

88

UMTS QoS classesUMTS QoS classes

Adopted performance targets similar to ITU-T’s collection of information - 3GPP TS Adopted performance targets similar to ITU-T’s collection of information - 3GPP TS 22.105 [3]22.105 [3]

Four different QoS classes are defined in 3GPP TS 23.107 [4], as follows:-Four different QoS classes are defined in 3GPP TS 23.107 [4], as follows:-

Traffic class

Conversational class

conversational RT

Streaming class

streaming RT

Interactive class

Interactive best effort

Background

Backgroundbest effort

Fundamentalcharacteristics

- Preserve timerelation (variation)between informationentities of the stream

Conversational pattern(stringent and low delay )

- Preserve timerelation (variation)between informationentities of the stream

- Request responsepattern - Preserve payloadContent

- Destination isnot expectingthe data within acertain time- Preservepayload content

Example of theapplication

- voice - streaming video - Web browsing - Backgrounddownload of emails

99

Performance targets for Conversational/Real-Time Performance targets for Conversational/Real-Time Services (audio and video applications)Services (audio and video applications)

- Source: 3GPP TS 22.105 V6.2.0 & G.1010- Source: 3GPP TS 22.105 V6.2.0 & G.1010

* Assumes adequate echo control** Exact values depend on specific codec, but assumes use of a packet loss concealment algorithm to minimise effect of packet loss

MediumMedium ApplicationApplication Degree of Degree of symmetrysymmetry

Typical Data rates/Typical Data rates/Amount of DataAmount of Data

Key performance parameters and target Key performance parameters and target valuesvalues

End-to-end OneEnd-to-end Oneway Delayway Delay

Delay VariationDelay Variationwithin a callwithin a call

InformationInformationLoss**Loss**

AudioAudio ConversationalConversationalvoicevoice

Two-wayTwo-way 4 - 64 kb/s4 - 64 kb/s <150 msec<150 msecPreferred*Preferred*

<400 msec <400 msec limit*limit*

< 1 msec < 1 msec < 3% < 3% PacketPacket

Loss RatioLoss Ratio

VideoVideo VideophoneVideophone Two-wayTwo-way 16 -384 kb/s16 -384 kb/s < 150 msec< 150 msecpreferredpreferred

<400 msec limit<400 msec limitLip-synch : Lip-synch : < 100 msec < 100 msec

< 1%< 1%Packet Packet

Loss Ratio Loss Ratio

Data Data TelemetryTelemetry- two-way control- two-way control

Two-wayTwo-way <28.8 kb/s<28.8 kb/s < 250 msec < 250 msec N.AN.A ZeroZero

DataData InteractiveInteractivegamesgames

Two-wayTwo-way < 1 KB< 1 KB < 250 msec < 250 msec N.AN.A ZeroZero

DataData TelnetTelnet Two-wayTwo-way(asymmetric)(asymmetric)

< 1 KB< 1 KB < 250 msec < 250 msec N.AN.A ZeroZero

1010

Performance targets for Interactive ServicesPerformance targets for Interactive Services – source: 3GPP TS 22.105– source: 3GPP TS 22.105 & ITU G.1010& ITU G.1010

MediumMedium ApplicationApplication Degree of Degree of symmetrysymmetry

Typical data rate/Typical data rate/Amount of dataAmount of data

Key performance parameters and target Key performance parameters and target valuesvalues

One-wayOne-wayDelay Delay

(response time)(response time)

DelayDelayVariationVariation

InformationInformationlossloss

AudioAudio VoiceVoiceMessagingMessaging

PrimarilyPrimarilyone-wayone-way

4-32 kb/s4-32 kb/s < 1 sec for< 1 sec forplayback playback < 2 sec for< 2 sec for

record record

< 1 msec < 1 msec < 3%< 3%Packet Packet

Loss Ratio Loss Ratio

DataData Web-browsingWeb-browsing- HTML- HTML

Primarily Primarily one-wayone-way

~ 10 kB~ 10 kB < 4 sec /page < 4 sec /page N.AN.A ZeroZero

DataData TransactionTransactionservices – highservices – high

priority priority e.g. e-commerce,e.g. e-commerce,

ATMATM

Two-wayTwo-way < 10 kB< 10 kB < 4 sec < 4 sec N.AN.A ZeroZero

DataData E-mailE-mail(server access)(server access)

PrimarilyPrimarilyOne-wayOne-way

< 10 kB< 10 kB < 4 sec< 4 sec N.AN.A ZeroZero

1111

Performance targets for Streaming Services Performance targets for Streaming Services – source: 3GPP TS 22.105– source: 3GPP TS 22.105 && ITU G.1010ITU G.1010

MediumMedium ApplicationApplication Degree ofDegree ofsymmetrysymmetry

Data rate/Data rate/Amount of dataAmount of data

Key performance parameters and target valuesKey performance parameters and target values

Start-upStart-upDelayDelay

Transport delayTransport delayVariationVariation

Packet loss atPacket loss atsession layersession layer

AudioAudio Speech, mixedSpeech, mixedspeech and music,speech and music,medium and highmedium and high

quality music quality music

Primarily Primarily one-wayone-way

5-128 kb/s5-128 kb/s < 10 sec < 10 sec < 1 msec < 1 msec < 1% Packet loss< 1% Packet lossratio ratio

VideoVideo Movie clips,Movie clips,surveillance, real-surveillance, real-

time videotime video

Primarily Primarily one-wayone-way

16 -384 kb/s16 -384 kb/s < 10 sec< 10 sec < 1 msec< 1 msec < 1% Packet loss< 1% Packet lossratio ratio

Data Data Bulk dataBulk datatransfer/retrieval,transfer/retrieval,

layout andlayout andSynchronisationSynchronisation

informationinformation

Primarily Primarily one-wayone-way

10 kB – 10 MB10 kB – 10 MB < 10 sec < 10 sec N.AN.A ZeroZero

Data Data Still imageStill image Primarily Primarily one-wayone-way

< 100 kB< 100 kB < 10 sec < 10 sec N.AN.A ZeroZero

1212

Value ranges for UMTS Bearer Service AttributesValue ranges for UMTS Bearer Service Attributes - 3GPP TS 23.107 V5.10.0- 3GPP TS 23.107 V5.10.0

Traffic classTraffic class Conversational Conversational classclass

Streaming classStreaming class Interactive classInteractive class Background Background classclass

Maximum bitrate (kbps)Maximum bitrate (kbps) <= <= 16 00016 000 <= <= 16 00016 000 <= <= 16 00016 000 – –overheadoverhead

<= <= 16 00016 000 – –overheadoverhead

Delivery orderDelivery order Yes/NoYes/No Yes/NoYes/No Yes/NoYes/No Yes/NoYes/No

Maximum SDU size (octets)Maximum SDU size (octets) <=1 500 or 1 502 <=1 500 or 1 502 <=1 500 or 1 502<=1 500 or 1 502 <=1 500 or 1 502<=1 500 or 1 502 <=1 500 or 1 502<=1 500 or 1 502

Delivery of erroneous SDUsDelivery of erroneous SDUs Yes/No/-Yes/No/- Yes/No/-Yes/No/- Yes/No/-Yes/No/- Yes/No/-Yes/No/-

Residual BERResidual BER 5*105*10-2-2, 10, 10-2-2, 5*10, 5*10-3-3,,1010-3-3, 10, 10-4-4, 10, 10-5-5, 10, 10-6-6

5*105*10-2-2, 10, 10-2-2, 5*10, 5*10-3-3,,1010-3-3, 10, 10-4-4, 10, 10-5-5, 10, 10-6-6

4*104*10-3-3, 10, 10-5-5, 6*10, 6*10-8-8 4*104*10-3-3, 10, 10-5-5, 6*10, 6*10-8-8

SDU error ratioSDU error ratio 1010-2-2, 7*10, 7*10-3-3, 10, 10-3-3, 10, 10-4-4, , 1010-5-5

1010-1-1, 10, 10-2-2, 7*10, 7*10-3-3,,1010-3-3, 10, 10-4-4, 10, 10-5-5

1010-3-3, 10, 10-4-4, 10, 10-6-6 1010-3-3, 10, 10-4-4, 10, 10-6-6

Transfer delay (ms)Transfer delay (ms) 100 – maximum value 100 – maximum value 280* – maximum 280* – maximum valuevalue

Guaranteed bit rate (kbps)Guaranteed bit rate (kbps) <= <= 16 00016 000 <= <= 16 00016 000

Traffic handling priorityTraffic handling priority 1,2,3**1,2,3**

Allocation/Retention priorityAllocation/Retention priority 1,2,31,2,3 1,2,31,2,3 1,2,31,2,3 1,2,31,2,3

Source statistic descriptorSource statistic descriptor Speech/unknownSpeech/unknown Speech/unknownSpeech/unknown

Signalling IndicationSignalling Indication Yes/No**Yes/No**

*If the User Equipment (UE) requests a transfer delay value lower than the minimum value, this shall not cause the network to reject the request from the UE. The network may negotiate the value for the transfer delay.**If signalling indication is set to ‘Yes’, the UE should set the traffic handling priority to ‘1’.

1313

Current QoS requirement in 802.20Current QoS requirement in 802.20 Support of IETF DiffServ (DS) [5] is described in Section 4.4.1 of the draft Support of IETF DiffServ (DS) [5] is described in Section 4.4.1 of the draft

802.20 requirements [1]802.20 requirements [1]

IETF DiffServ – classes of services specified in the DS codepoints IETF DiffServ – classes of services specified in the DS codepoints Expedited Forwarding (EF) [6]Expedited Forwarding (EF) [6] Assured Forwarding (AF) – 4 subclasses with 3 levels of drop precedence Assured Forwarding (AF) – 4 subclasses with 3 levels of drop precedence

through the mapping of DS codepoints [7]through the mapping of DS codepoints [7] Best EffortBest Effort

IETF DiffServ defined the QoS structure for IP packets at the Network LayerIETF DiffServ defined the QoS structure for IP packets at the Network Layer

How should the End user QoS requirements be mapped into the DiffServ How should the End user QoS requirements be mapped into the DiffServ classes at the Network layer?classes at the Network layer?

How should the DiffServ requirements at the Network layer be translated to How should the DiffServ requirements at the Network layer be translated to the related requirements at PHY and MAC layers in order to achieve the the related requirements at PHY and MAC layers in order to achieve the end-to-end QoS requirements?end-to-end QoS requirements?

1414

Information Flow between End-usersInformation Flow between End-users

Transmitted information path

Received information path

Scope of IEEE 802.20 Standard

1515

802.2 Logical Link Control (LLC)*802.2 Logical Link Control (LLC)*

Three forms of service supported, as viewed from the network layer:Three forms of service supported, as viewed from the network layer:

Unacknowledged Connectionless modeUnacknowledged Connectionless mode No need to establish data link level connectionNo need to establish data link level connection For point-to-point, multicast and broadcast applicationsFor point-to-point, multicast and broadcast applications

Connection modeConnection mode Need to establish a data link level connection Need to establish a data link level connection Provides data link layer sequencing, flow control and error recoveryProvides data link layer sequencing, flow control and error recovery For point-to-point applicationsFor point-to-point applications

Acknowledged connectionless modeAcknowledged connectionless mode No need to establish data link level connectionNo need to establish data link level connection LLC acknowledgement requiredLLC acknowledgement required For point-to-point applicationsFor point-to-point applications

Source: IEEE 802.2 Standard [8]Source: IEEE 802.2 Standard [8]

1616

QoS Implication on PHY and MACQoS Implication on PHY and MAC

User-perceivable performance described by QoS requirementsUser-perceivable performance described by QoS requirements

QoS requirements need to be accomplished from the transmitting to the QoS requirements need to be accomplished from the transmitting to the receiving endreceiving end

Impact of each layer along the transmission path need to be considered for Impact of each layer along the transmission path need to be considered for an optimized systeman optimized system

=> Derive PHY and MAC layer requirements from User-driven performance => Derive PHY and MAC layer requirements from User-driven performance requirements, based on reasonable assumptions on the apportionment requirements, based on reasonable assumptions on the apportionment between different layers.between different layers.

Latency, Delay Variation and Error Rate are the main performance Latency, Delay Variation and Error Rate are the main performance parameters related to the PHY and MAC layers.parameters related to the PHY and MAC layers.

Tradeoff between Latency and Error Rate performance in an optimized Tradeoff between Latency and Error Rate performance in an optimized dynamic system.dynamic system.

1717

Information lossInformation loss

Error correction at the PHY layer, may correct errors through re-transmissionsError correction at the PHY layer, may correct errors through re-transmissions Error detection at the MAC sublayer, corrected through re-transmissions, with Error detection at the MAC sublayer, corrected through re-transmissions, with

increased latency ~ increased latency ~ nn x ARQ loop delay, where x ARQ loop delay, where n n = number of re-transmisisons = number of re-transmisisons Possible error detection at the LLC sublayer, corrected through LLC re-transmission, Possible error detection at the LLC sublayer, corrected through LLC re-transmission,

depending on the mode of operation at LLC sublayerdepending on the mode of operation at LLC sublayer Error detection at TCP layer, corrected through re-transmission, but with increased Error detection at TCP layer, corrected through re-transmission, but with increased

latency ~ latency ~ MM x Round Trip Time (RTT), x Round Trip Time (RTT), MM = number of TCP re-transmisisons = number of TCP re-transmisisons For UDP, error packets will be detected and discarded without re-transmissionFor UDP, error packets will be detected and discarded without re-transmission

End-to-end LatencyEnd-to-end Latency

QoS Implication on PHY and MACQoS Implication on PHY and MAC

)()(

)(

sinPrPr

//

sinPrPr

7

3

7

1

CB

A

DelaygocesDelayopagation

iLayerinDelayLayersLLCMACPHYinDelay

DelaygocesDelayopagationiLayerinDelayLatencyendtoEnd

i

i

Notes: (A) Dependent on traffic loading, protocols, and delay in the lower layers, in some cases(B) Dependent on distance between user terminal and base station(C) Dependent on Implementation

1818

IEEE 802 Error Rate RequirementIEEE 802 Error Rate Requirement

KrateerrorOctetOctetsKwithpacketaforrateError )1(1

IEEE Std 802-2001 specified the error rate performance for IEEE 802 LANs and MANs in section 7.3 [9, 10]:

- Probability of error of data delivered to the MAC Service Access Point (MSAP) at the receiver < 8x10-8 per octet of MAC Service Data Unit (SDU) length

- For MAC SDU length = 1024 octets,

MAC SDU packet error rate, Pe < ~ 8 x 10-5

Assume the same packet size and independent PER for each re-transmission, nePsionsretransmisnafterrateerrorPacket 1

Number of retransmissionsNumber of retransmissions 11 22 33

Residual Packet Error Rate for Residual Packet Error Rate for PPee = 8 x 10 = 8 x 10-5-5

6.4 x 106.4 x 10-9-9 5 x 105 x 10-13-13 4.096 x 104.096 x 10-17-17

Residual Packet Error Rate for Residual Packet Error Rate for PPee = 0.25 = 0.25

6.25 x 106.25 x 10-2-2 1.56 x 101.56 x 10-2-2 3.9 x 103.9 x 10-3-3

1919

Recommended Latency and Packet Error Rate Recommended Latency and Packet Error Rate Performance Targets for IEEE 802.20Performance Targets for IEEE 802.20

Latency & Error Rate forLatency & Error Rate fordifferent application different application

classesclasses

Expedited Forwarding Expedited Forwarding (EF)(EF)

Assured Assured Forwarding (AF)Forwarding (AF)

Best EffortBest Effort(BE)(BE)

~ 30 ms (TBR)~ 30 ms (TBR) ~ 30 ms – 10 s (TBR)~ 30 ms – 10 s (TBR) >> 10 s (TBR)>> 10 s (TBR)

Error TolerantError Tolerant 3 x 103 x 10-2-2 1010-2-2 – 2.5 x 10 – 2.5 x 10-1 -1 (TBR)(TBR) 2.5 x 102.5 x 10-1 -1 (TBR)(TBR)

Error IntolerantError Intolerant 5 x 105 x 10-13-13 (TBR) (TBR) 5 x 105 x 10-13-13 – 8 x 10 – 8 x 10-5-5 (TBR) (TBR) 8 x 108 x 10-5-5

- Assured Forwarding class can be further sub-divided into 4 subclasses

- Mapping of applications to the various classes depend on implementation

- Requirements for the proposal: to demonstrate that the error rates can be achieved with the corresponding latency

2020

Industrial QoS Related ActivitiesIndustrial QoS Related Activities

Standards organizations that are working on QoS issues:Standards organizations that are working on QoS issues: IEEE 802.11e, 802.11n (High Throughput WLAN Standard)IEEE 802.11e, 802.11n (High Throughput WLAN Standard) IETFIETF ITU-T, ITU-R ITU-T, ITU-R 3GPP3GPP T1A1T1A1 3GPP23GPP2

Some of the Issues: [11]Some of the Issues: [11] allocation of performance requirements along the transmission path traversed by allocation of performance requirements along the transmission path traversed by

the information packets, to achieve the end-to-end performance targets.the information packets, to achieve the end-to-end performance targets.

IP QoS interoperability – differences in the definition of QoS classes by different IP QoS interoperability – differences in the definition of QoS classes by different standards for different technologies across the network that connects the two standards for different technologies across the network that connects the two end-users. end-users.

2121

List of ReferencesList of References

[1] Draft 802.20 Requirements Document – Ver. 8c, Oct. 28, 2003.[1] Draft 802.20 Requirements Document – Ver. 8c, Oct. 28, 2003.[2] ITU G.1010 [“Draft New Recommendation G.QoSRQT – End-user [2] ITU G.1010 [“Draft New Recommendation G.QoSRQT – End-user

Multimedia QoS Categories”, ITU-T study group 12, contribution 37, Multimedia QoS Categories”, ITU-T study group 12, contribution 37, August 2001]August 2001]

[3] 3GPP TS 22.105, "Services and service capabilities“[3] 3GPP TS 22.105, "Services and service capabilities“[4] 3GPP TS 23.107, "QoS concept and Architecture" [4] 3GPP TS 23.107, "QoS concept and Architecture" [5] RFC 2475, “An Architecture for Differentiated Services”[5] RFC 2475, “An Architecture for Differentiated Services”[6] RFC 2598, “An Expedited Forwarding PHB”[6] RFC 2598, “An Expedited Forwarding PHB”[7] RFC 2597, “Assured Forwarding PHB Group”[7] RFC 2597, “Assured Forwarding PHB Group”[8] ANSI/IEEE 802.2(ISO/IEC 8802-2:1998), “Part 2, Logical Link [8] ANSI/IEEE 802.2(ISO/IEC 8802-2:1998), “Part 2, Logical Link

Control”, 1998 editionControl”, 1998 edition[9] IEEE Std 802 -2001, “IEEE standard for Local and Metropolitan [9] IEEE Std 802 -2001, “IEEE standard for Local and Metropolitan

Area Networks: Overview and Architecture”Area Networks: Overview and Architecture”[10] C802.20-03/83r1, “FER: Do We Need It?”, J. Cleveland et. al., [10] C802.20-03/83r1, “FER: Do We Need It?”, J. Cleveland et. al.,

Sept. 8, 03. Sept. 8, 03. [11] http://www.itu.int/ITU-T/worksem/qos/index.html[11] http://www.itu.int/ITU-T/worksem/qos/index.html