May, 2008 IEEE P802.15-d

IEEE P802.15

Wireless Personal Area Networks

Project / IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Title / TG4e Technical Requirements
Date Submitted / 14 May 2008
Source / [Pat Kinney]
[Kinney Consulting LLC]
[Chicago, IL, USA] / Voice: [847-960-3715]
Fax: []
E-mail: [
Re: / IEEE 802.15.4-2006 Standard for Telecommunications and Information Exchange between Systems – LAN, MAN Specific Requirements – Part 15: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (WPAN).
Abstract / This documents describes the technical requirements for proposals for TG4e.
Purpose / To accompany the Call for Proposals and to motivate contributions by providing content guidance.
Notice / This document has been prepared to assist the IEEE P802.15. 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 in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release / The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.


TG4e Proposal Content Guidance

Purpose

·  This document has been drafted to assist those who wish to make a proposal to the TG4e MAC amendment task group.

·  The General section lists documents to which the proposer should refer, and lists some content that all proposers should consider in their proposal

·  The MAC section lists technical areas of the MAC to which the task group wishes to entertain proposals. The proposer should refer to the specific area that the proposal dwells upon for specific technical content subjects. It is not required that a proposal address every subject but the proposer should be aware that he/she could be asked questions on those subjects.

General

·  Proposals shall comply with the TG4e PAR (15-07-0xxx-02-0sg4e) and 5 Criteria document (15-07-0861-00-0000-sg4e-5c)

·  New terms should be defined by the proposer

·  Proposals should refer to IEEE 802.15.4-2006 for guidance

·  Coexistence statement

·  How proposal relates to other standards (IETF, ISA, ISO, IEEE)

MAC

·  Channel Hopping/AFA

o  Centralized vs. distributed

o  Minimum number of channels

o  Regulatory issues

o  Channel occupancy time

o  Hopping Rate

o  Clock accuracy (ppm)

o  Number of Simultaneously Operating PANs (SOPs)

o  Static vs. adaptive hopping sequence assignment

o  Prioritization of channels (i.e. white/black listing)

o  Network acquisition and acquisition time

o  Support for non-hopping devices

o  Synchronization method

o  Hopping Sequence length (dynamic vs. static)

o  Sequence generation: Algorithmic vs. Table

o  AFA: network wide vs. partial

o  AFA: centralized vs. distributed

·  Time Division Multiple Access (TDMA)/Determinism

o  Centralized vs. decentralized

o  Duration of TDMA slots

o  TDMA slot duration (equal/non-equal)

o  TDMA slot duration static vs. dynamic

o  Maximum number of TDMA slots before repetition

o  Slot combining

o  Support for retries

o  Slot allocation

o  Structure of TDMA individual slot (guard time, Phy characteristics, CCA period, ack, retry, etc.)

o  TDMA slot sharing

o  Support for broadcast and multicast

o  How to handle bursty traffic

o  Network capacity (throughput, channel utilization)

o  Slot allocation/deallocation mechanism

o  Scalability

o  Event driven transmissions

o  Support for TDMA/CSMA network

o  Capability to talk to legacy devices

o  Timing requirements

·  Superframe Structure (or equivalent)

o  Beacon enabled network or non-beacon enabled network

o  Centralized or decentralized

o  Backward compatibility

o  Scalability

o  Adaptive/dynamic or static

o  Support for CAP and CFP behavior

o  Number of maximum GTSs

o  GTS interval

o  Mechanism to share GTS and transmission direction

o  Support for peer to peer communication

o  Capability for end devices to have their own Superframe

o  Support to QoS

o  Support for low energy operation

o  Support for Channel Hopping

o  Allocation and de-allocation of GTSs

·  Packet Structure

o  Packet types

o  Support for QoS

o  Longest packet

o  Fragmentation support

·  Time Synchronization

o  Clock accuracy

o  Method for time synchronization

o  Synchronization propagation (number of device hops)

o  Time propagation (absolute and/or relative)

o  Time to acquire synchronization

o  How often to synchronization

o  Phy support for time synchronization

o  Inter-PAN synchronization

·  Mesh Support

o  Neighborhood link state information management

§  Overhead (formation, maintenance, etc.)

o  Path redundancy

o  TG5 support

o  Device redundancy

o  Edge throughput (aggregate ingress/egress capacity)

o  What topologies are supported

o  Number of device hops

o  Metrics for path selection

o  Mechanism for path selection

o  Broadcast and multicast

o  Broadcast/multicast acknowledgement

·  Reliability/Fail detect/fail recovery

o  Non-detected corrupt packets

o  Packet drop policy

o  Error reporting (route selection, next hop selection, etc.)

o  Broadcast and Multicast reliability

o  Device failure detection (e.g. coordinator, PAN coordinator, etc.)

o  Link quality and failure detection

o  Recovery time from link failure

o  Recovery time for coordinator failure

o  Logging mechanism

o  Packet error detection and correction (EDAC)

o  Tolerance to node failure

·  QoS/Latency/Priority

o  Priority levels (e.g. 2, 3, 4, etc)

o  Latency jitter range

o  Latency

§  Channel access delay

§  Node association delay

§  re-association

§  Handling bursty packet arrivals

§  buffer management mechanisms

·  CSMA/CCA

o  Back-off mechanisms

o  Channel hopping CSMA

o  CCA mechanism

o  Fairness

o  Channel utilization

o  Recovery from a bad CSMA channel

·  Phy Support

o  Transmit power control

o  Ability to adapt to new Phy parameters (e.g. multiple data rates, frame sizes, etc)

o  Requirements for frequency changes (e.g. timing)

o  Support for Phy frame extension (e.g. use of reserved bits)

·  Security

o  Encryption

o  Authentication

o  Authorization

o  Key management

o  Replay attack defenses

·  Network Management support

o  Error reporting (statistics)

o  Diagnostics

o  Option management

o  Firmware update (OTA)

o  Multiple coordinators

o  Support for Network formation and maintenance

·  Energy Management

o  Manage duty cycles

o  Load balancing

o  Reporting period adjustment

o  Message aggregation

o  Hybrid ARQ (to reduce energy expended in retries)