Transcript IEEE C802.16m-08/681r2

Efficient 16m MAC Addressing
IEEE 802.16 Presentation Submission Template (Rev. 9)
Document Number:
IEEE C802.16m-08/681r2
Date Submitted:
2008-07-07
Source:
Kanchei (Ken) Loa, Yi-Hsueh Tsai, Chun-Yen Hsu,
Yung-Ting Lee, Youn-Tai Lee, Hua-Chiang Yin,
Institute for Information Industry
E-mail: [email protected]
Shiann-Tsong Sheu
National Central University
Whai-En Chen,
National Ilan University
*<http://standards.ieee.org/faqs/affiliationFAQ.html>
Venue:
IEEE 802.16m-08/024- Call for comments and contributions on project 802.16m system description document (SDD)
Topic: Upper MAC concepts and methods (addressing)
Base Contribution:
N/A
Purpose:
Propose a efficient addressing method
Notice:
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.
Release:
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.
Patent Policy:
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 >.
Introduction
• The legacy CID has different meanings
depending on the context of its usage
[Yair Bourlas’s e-mail on 04/23/2008]:
– It is used as SS address in the MAP for resource
allocation
– It is used as service flow ID in the MAC header
• To reduce the addressing overhead in the MAP
and MAC PDU header, instead of using legacy
CID, we propose to use a pair of Station ID
(SID) and a Transport ID (TID)
Example
• For example, we can use a pair of 4~12-bit
SID and 4-bit TID to replace the legacy 16-bit
CID (4-bit SID could be used for femto cell)
• The MAP only requires 4~12-bit SID as the SS
address
• The PDU MAC header only requires 4-bit TID
as the service flow ID
• During handover, the target BS only need to
reassign a 4~12-bit SID, instead of all 16-bit
SS CIDs. The TIDs remain the same
Legacy Management CID
• In the legacy 16e, BS will assign a pair of
(basic and primary) management CIDs to SS
during initial ranging phase. The basic CID is
used in the MAP for resource allocation
• Basic and primary management CIDs reflect
the fact that there are inherently different
levels of QoS for management traffic between
an SS and the BS
Proposed Station ID (SID)
• We propose using a cell-wide unique ID, such
as SID (Station ID), instead of using basic CID,
to represent a subscriber station in the MAP
• Since the SID has already appeared in the
MAP for target SS identification, the SID in
the management MAC PDU header can be
eliminated completely, except during CDMA
ranging
Proposed Station ID (SID)
• Different levels of QoS (i.e. basic, primary or
secondary) for management messages, if
necessary, could be indicated in the
management MAC PDU header by 2 bits
Legacy Transport CID
• In legacy 16e, in order to establish a service
flow, the BS will assign a cell-wide transport
CID with an associated access-network-wide
unique SFID to SS
• Then the assigned transport CID will be used
as a service flow ID in the MAC PDU header
to identify the service flow which the payload
is assigned to
Proposed Transport ID (TID)
• We propose that for each service flow of an SS,
the BS assigns a subscriber-station-wide
unique TID (Transport ID) for that SS. Thus,
the SID + TID will uniquely map to the
associated SFID in the BS cell
Proposed Transport ID (TID)
• Since the SID has already appeared in the
MAP for target SS identification, the MAC
PDU header only requires the TID, except
during CDMA ranging
• SID in the MAP + TID in the MAC PDU
header uniquely maps to SFID
During Handover
• In legacy 16e, during handover, the target BS
have to reassign all SS CIDs including basic +
primary management CID and transport CIDs
associated with the service flow
• Since the TID (Transport ID) is subscriberstation-wide unique, it remains unchanged
during handover. Thus, the target BS only
need to reassign an SID
Reduced Generic MAC Header
• Legacy Generic MAC header requires 16-bit
CID for addressing
• The proposed management MAC PDU header
only requires 2 bits for addressing
• The proposed transport MAC PDU header
only requires 4 bits for addressing
• The size of the Generic MAC header could be
reduced or more bits in the MAC header could
be reserved for other purposes
Conclusions
• To reduce the addressing overhead, we
propose to use a Station ID (SID) in the MAP
and a Transport ID (TID) in the MAC header
• During handover, the target BS only need to
reassign an SID, instead of all SS CIDs
• The size of the Generic MAC header could be
reduced or more bits in the MAC header could
be reserved for other purposes