IEEE C802.16m-09/0651
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed Text Related to Addressing for the IEEE 802.16m Amendment
Date
Submitted
2009-03-02
Source(s)
Kiseon Ryu
Voice: +82-31-450-2067
E-mail: ksryu@lge.com
LG Electronics
Re:
IEEE 802.16m-09/0012, “Call for Comments and Contributions on Project 802.16m
Amendment Working Document”.
Target topic: “Addressing”
Abstract
The contribution proposes the text of Addressing to be included in the 802.16m amendment.
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>.
Proposed Text for Addressing Section in the IEEE 802.16m Amendment
Working Document
Kiseon Ryu
LG Electronics
1. Introduction
This contribution includes the proposed text for Addressing in the IEEE 802.16m Amendment. The technical
text and ToC are inherited from the 802.16m SRD [1], and the IEEE 802.16m SDD [2] and the IEEE P802.16
Rev2/D9 [3]. Moreover, this contribution follows the tentative outline and style guide in the IEEE 802.16m
Amendment [4]. In this contribution, amendment text including several illustrations is proposed for the section
in which 16m members have enough consensus.
1
IEEE C802.16m-09/0651
2. Modifications from the SDD and key descriptions
SDD contains two sections related to the text for addressing, which are 10.1 Addressing and 10.9 Connection
Management. This contribution proposes to merge the SDD text defined in 10.1 and 10.9, except the subsection
10.9.3 Emergency service flow, into one section in the Amendment Working Document to avoid existence of
redundant text in different sections.
3. References
[1] IEEE 802.16m-07/002r8, “802.16m System Requirements Document (SRD)”
[2] IEEE 802.16m-08/003r7, “The Draft IEEE 802.16m System Description Document”
[3] IEEE P802.16 Rev2 / D9, “Draft IEEE Standard for Local and Metropolitan Area Networks: Air Interface
for Broadband Wireless Access,” Jan. 2009.
[4] IEEE 802.16m-08/043, “Style guide for writing the IEEE 802.16m amendment”
[5] IEEE 802.16m-09/0010, “IEEE 802.16m Amendment Working Document”
4. Text proposal for the IEEE 802.16m amendment
----------------------------------------------------- Start of the text ----------------------------------------------------------
2
IEEE C802.16m-09/0651
15. Advanced Air Interface
15.2. Medium Access Control
15.2.1.
Data/Control Plane
15.2.1.1
Addressing
The AMS shall have a global address and logical addresses that identify the AMS and connections during
operation. The AMS, ARS and ABS are identified by the globally unique 48-bit IEEE Extended Unique
Identifier (EUI- 48™) based on the 24-bit Organizationally Unique Identifier (OUI) value administered by the
IEEE Registration Authority [16].
The logical identifiers shall be defined with Station Identifier (STID) and the Flow Identifier (FID). The ABS
shall assign a STID to the AMS during network entry and network re-entry, which uniquely identifies the AMS
within the domain of the ABS. STIDs shall be reserved for broadcast, multicast, and ranging.
Each AMS connection shall be assigned a FID that uniquely identifies the connection within the AMS. FIDs
shall identify management connections and transport connections. FIDs shall be pre-assigned for management
connection and reserved for indication of the header type other than Generic MAC Header.
Connections shall be identified by the combination of STID and FID. Two types of connections shall be used for
management connections and transport connections. Management connections shall be used to carry MAC
management messages. Transport connections shall be used to carry user data including upper layer signaling
messages such as DHCP, etc and data plane signaling such as ARQ feedback. Fragmentation shall be supported
on transport connections. Fragmentation may be supported on the unicast management connection.
Management connections are bi-directional. Default values of FIDs shall be reserved for unicast management
connections and emergency service flows. Management connections shall be automatically established after a
STID is assigned to an AMS during AMS initial network entry.
Transport connection is uni-directional and established with unique FID assigned during service flow
establishment procedure. Each admitted/active service flow shall be uniquely mapped to a transport connection.
Transport connection shall be released when the associated service flow is removed. The ABS and AMS may
establish/change/release multiple connections using a single message transaction on a management connection.
Transport connections shall be pre-provisioned or dynamically created. Pre-provisioned connections shall be
established by system for an AMS during the AMS network entry. ABS or AMS may create new connections
dynamically if required. A connection may be created, changed, or torn down on demand.
------------------------------------------------------ End of the text ---------------------------------------------------------3