C802.16gman-10/0053
Project
IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16>
Title
Proposed Table of Contents for 802.16n amendment
Date
Submitted
2010-11-04
Source(s)
Eldad Zeira
Eldad.zeira@interdigital.com
InterDigital Communications LLC
Re:
802.16n ToC
Abstract
This document proposes a beginning point for amendment ToC.
Purpose
To be discussed and decided by GRIDMAN.
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>.
C802.16gman-10/0053
New functionality for 802.16 may be written as a new chapter or as an amendment. The question is affected by the scope and depth of the predicted changes or additions to the baseline standard. In short, it
depends on what we expect:
1. A lot of small changes to existing text with full backward compatibility are easier to be drafted as
changes into the existing chapters of the specification.
2. A lot of additional text, e.g. to implement new functionality with limited backward compatibility is
easier to be drafted as new chapters (such as chapter 16 for AAI)
I’m inclined to think that alternative 2 is better for 802.16n.
Regardless of the decision for the above, WHAT we write or modify is either a PHY or a MAC function
(e.g. a new or modified MAC message). All modifications of an existing function (e.g. a MAC message)
should be treated in one section because eventually that MAC message must be defined in one spot.
Likewise a new MAC message can only be defined in one spot.
Once a function is defined an implementer may use it as desired, disregarding the original intent behind
the function.
A specification (whether amendment or a new chapter) must therefore be aligned with expected MAC or
PHY functions to be modified or drafted, and not aligned with features.
Therefore I propose that:
Proposal 1:
802.16n specification is to become a new chapter under 802.16.
Proposal 2:
802.16n specification is to be aligned with MAC / PHY and other relevant functions, existing or
new.
To start the work I have copied the table of contents from 802.16m (D9) without any changes. I have arbitrarily stayed within 3-4 levels.
Proposal 3:
GRIDMAN shall use the 802.16m ToC below as a starting point and discuss contributions against
it.
802.16e (2009) or 802.16j ToC may be added.
>>>>>>>>>>>>>>>>>
Proposed ToC Baseline
2. Normative references
3. Definitions
4. Abbreviations and acronyms
5. Service Specific CS
6. MAC common part sublayer
7. Security sublayer
<<<<<<<<<<<<<<<<<<<<<<<<<<
C802.16gman-10/0053
8. Physical layer (PHY)
10.
Parameters and constants
11.
TLV encodings
16.
WirelessMAN-Advanced Air Interface
17.
High Reliability (HR) Air Interface
17.1
Introduction
17.1.1 AMS Operational States
17.2
Medium access control
17.2.1
17.2.2
17.2.3
17.2.4
17.2.5
17.2.6
17.2.7
17.2.8
17.2.9
17.2.10
17.2.11
17.2.12
17.2.13
17.2.14
17.2.15
17.2.16
17.2.17
17.2.18
17.2.19
17.2.20
17.2.21
17.2.22
17.2.23
17.2.24
17.2.25
17.2.26
17.2.27
17.2.28
17.3
17.3.1
17.3.2
17.3.3
17.3.4
17.3.5
17.3.6
Addressing
MAC PDU formats
MAC Control messages
Construction and Transmission of MAC PDUs
AAI Security
MAC HO procedures
Persistent Scheduling in the Advanced Air Interface
Multicarrier operation
Group Resource Allocation
Connection Management
Bandwidth Request and Allocation Mechanism
Quality of Service (QoS)
ARQ mechanism
HARQ Functions
Network Entry and Initialization
Periodic Ranging
Sleep Mode
Idle mode
Deregistration with content retention (DCR) mode
Co-Located Coexistence (CLC)
Interference Mitigation Mechanism
MAC Control Reliability
Power Management for the Active Mode
Update of S-SFH IEs
Short Message Service
Coverage Loss Detection and Recovery from Coverage Loss
AMS deregistration
Support for Multicast Service
Physical layer
Introduction
OFDMA symbol description, symbol parameters and transmitted signal
Frame structure
Downlink physical structure
Downlink control structure
Downlink MIMO
C802.16gman-10/0053
17.3.7
17.3.8
17.3.9
17.3.10
17.3.11
17.3.12
17.3.13
17.3.14
17.4
Support for Femto ABS
17.4.1
17.4.2
17.4.3
17.4.4
17.4.5
17.4.6
17.4.7
17.4.8
17.4.9
17.4.10
17.4.11
17.4.12
17.4.13
17.5
Uplink physical structure
Uplink control channel
Uplink MIMO
Channel coding and HARQ
Link Adaptation
Error vector magnitude (EVM) and requirements
Channel quality measurements
Receiver requirements
General description
Femto base station subscription types
Femto ABS state diagram
PHY and MAC level identifier
Femto ABS initialization and de-attachment
Network synchronization
Network entry
Handover (HO)
Idle mode
Low-duty operation mode
Interference avoidance and interference mitigation
Power control
Femto ABS reliability
Multi-BS MIMO
17.5.1 DL Multi-BS MIMO
17.5.2 UL Multi-BS MIMO
17.6
Support for Relay
17.6.1 Relay Modes and General Description
17.6.2 Medium access control
17.6.2.1 Addressing
17.6.2.2 MPDU Formats
17.6.2.3 Construction and Transmission of MPDUs
17.6.2.4 Security
17.6.2.5 Handover
17.6.2.6 Scheduling and QoS
17.6.2.7 Bandwidth Request and Grant Management
17.6.2.8 ARQ
17.6.2.9 HARQ
17.6.2.10 Network Entry
17.6.2.11 Ranging
17.6.2.12 Sleep Mode
17.6.2.13 Idle Mode
17.6.2.14 ARS Configuration
17.6.2.15 ARS De-registration
17.6.2.16 Update of SFH
17.6.3 Physical Layer for TTR relay mode
17.6.3.1 Basic frame structure supporting ARS
17.6.3.2 Frame structure
17.6.3.3 Relay Downlink PHY Structure
17.6.3.4 Downlink Control Structure
C802.16gman-10/0053
17.6.3.5 Relay Uplink physical structure
17.6.3.6 Uplink Control Structure
17.6.4 Physical Layer for STR relay mode
17.7
Support for Self-organization
17.7.1 Self-Organization
17.7.2 Self Configuration
17.7.2.1 Femto ABS Neighbor Discovery
17.7.2.2 Macro ABS Neighbor List Self-discovery
17.7.2.3 Femto ABS Self-Configuration
17.7.3 Self Optimization
17.7.3.1 Support of Interference Mitigation
17.7.3.2 Support of Multi-BS MIMO
17.7.4 Support of Reconfigurations and Restart
17.7.5 MS assisted Femto ABS neighbor list update
17.8
Support for Location Based Services (LBS)
17.8.1 Location Determination Capability Negotiation
17.8.2 Basic LBS Support
17.8.3 Enhanced LBS Support
17.9
Support for Enhanced Multicast Broadcast Service
17.9.1 E-MBS Transmission Modes
17.9.1.1 Non-Macro Diversity Mode
17.9.1.2 Macro Diversity Mode
17.9.2 E-MBS Operation
17.9.2.1 E-MBS Connection Establishment
17.9.2.2 E-MBS Operation in Connected State
17.9.2.3 E-MBS Operation in Idle State
17.9.2.4 E-MBS Operation on the multi-carrier deployment
17.9.3 E-MBS Protocol Features and Functions
17.9.3.1 E-MBS Configuration Indicators
17.9.3.2 E-MBS Zone Configuration
17.9.3.3 E-MBS Scheduling Interval (MSI)
17.10
Support for Advanced Air Interface in LZone
17.10.1 Support for network topology advertisement
17.10.1.1 DL frame prefix
17.10.2 Support for zone switch operation
17.10.2.1 RNG-RSP management message encodings
17.10.2.2 RNG-REQ management message encodings
17.10.3 Migrating to AAI without impacting the deployed legacy network
17.11
Global Values