IEEE C802.16m-09/0635
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
QoS and Service Flow Management
Date
Submitted
2009-03-02
Source(s)
Roberto Albanese, Andrea Bacioccola, Jan
Suumaki
roberto.albanese@nokia.com
Nokia
haihong.zheng@nokia.com
Haihong Zheng, Shashikant Maheshwari,
Xiaoyi Wang
NSN
Re:
802.16m AWD: QoS
Abstract
The contribution proposes text to the 802.16m Amendment for QoS support and service flow
management.
Purpose
To be discussed and adopted by TGm for the 802.16m amendment.
Notice
Release
Patent
Policy
This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It
represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion.
It is not binding on the contributor(s), who 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.16.
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
<http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and
<http://standards.ieee.org/guides/opman/sect6.html#6.3>.
Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and
<http://standards.ieee.org/board/pat>.
1
IEEE C802.16m-09/0635
QoS and Service Flow Management
1
Introduction
According to the SRD requirement document [2], the Advanced System has to efficiently handle VoIP traffic,
which may be characterized by different QoS requirements and patterns. For example, voice codecs such as G.
723, G. 729, AMR use silence suppression mechanism to reduce bandwidth consumption during silence period.
Silence Insertion Descriptor (SID) frame may be transmitted periodically or non-periodically.
The Advanced System supports adaptation of service flow QoS parameters. One or more sets of QoS
parameters are defined for one service flow. A service flow with two sets of parameters (SET_1, SET_2) could
be associated to a VoIP connection using silence suppression mechanism. SET_1 can be defined as the set of
QoS parameters to be used during voice frames; SET_2 can be defined as the set of QoS parameters during SID
frames.
The AMS and ABS negotiate the supported QoS parameter sets during service flow management procedure. In
addition, the AMS may request the ABS to switch between service flow QoS parameter sets with explicit
signaling.
2
Text proposal for the 802.16m amendment
================= Start of Proposed Text ========================
15.2.x Quality of Service (QoS)
The QoS-related concepts such as service flow QoS scheduling, dynamic service flow management and two-phase
activation model follow the procedure defined in section 6.3.14. In addition, multiple service flow parameter sets may be
defined for a single service flow (section 15.2.x.1) and the procedure of dynamical switching between different service
flow parameter sets are defined in section 15.2.x.2.
15.2.x.1 Multiple Service Flow Parameter Sets
QoS requirement and traffic characteristics of one service flow may vary during different period of the service
flow life time. The service flow parameters may be divided into two categories: the common service flow
parameters and the variable service flow parameters. The variable service flow parameters are categorized into
more than one service flow parameter set. Each set is uniquely identified by a Service_Flow_Parameter_Set_ID.
The combination of one service flow parameter set and the common service flow parameters defines the QoS
requirement of the service flow during one time period. The service flow parameters may be pre-defined using
service class or negotiated between AMS and ABS during AAI-DSA and AAI-DSC procedure.
2
IEEE C802.16m-09/0635
15.2.x.2 Switching between Service Flow Parameter Sets
The default service flow parameter set (identified by Service_Flow_Parameter_Set_ID with value 0) is used
after the service flow is established. When the QoS requirement or the traffic characteristics for UL or DL
traffic changes from one set to another, the AMS requests the ABS to switch the Service Flow parameter set.
The request may be carried in the Fast Feedback Control Channel (details TBD) or
Service_Flow_Parameter_Set_Switch signaling header (details TBD). Upon receiving the request, the ABS
schedules traffic and allocates resource according to the new service flow parameter set. The ABS may
autonomously switch from one service flow parameter set to another and schedule DL traffic accordingly, if it
detects the change of the traffic characteristics.
============================== End of Proposed Text ===============
References
[1] IEEE P802.16 Rev2/D9, “Draft IEEE Standard for Local and Metropolitan Area Networks: Air Interface
for Broadband Wireless Access Systems,” Jan. 2009.
[2] IEEE 802.16m-07/002r8, “802.16m System Requirements”
[3] IEEE 802.16m-08/003r7, “The Draft IEEE 802.16m System Description Document”
[4] IEEE 802.16m-08/043, “Style guide for writing the IEEE 802.16m amendment”
3