1. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Report on the High-Rate Editing Status]
Date Submitted: [12 Nov., 2007]
Source: [Youngae Jeon, Seonghee Lee, Sangsung Choi] Company [ETRI]
Address [161, Gajeong-dong, Youseong-gu, Daejeon, Korea]
Voice: [ ], FAX: [ ],
Abstract: [This document describes the modified and complemented IEEE P draft for high-data- rate WPAN mesh.]
Purpose: [To report the modified and complemented IEEE P draft for high-data-rate WPAN mesh.]
Notice: This document has been prepared to assist the IEEE P 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 P
Y. Jeon, ,S. Lee, S. Choi
<author>, <company>

2. Report on HR Progress Sep. 2007, Hawaii Interim Meeting
Report on HR Progress
Sep. 2007, Hawaii Interim Meeting
- Group decided to include High Rate document in the
upcoming letter ballot.
- Group decided to complete the HR document by the two
weeks before November Plenary at Atlanta
Organize a consortium for editing HR document in Korea
- ETRI
- Gwngwoon University
- Hannam University
3 times Teleconference during last 2 months
Completed the HR Document at October 31, 2007
- Correction grammatical error by native speakers
Distribute the document all TG5 Members at Nov. 5, 2007
Y. Jeon, ,S. Lee, S. Choi

3. Content of HR Draft 1. Overview 2. Normative References 3. Definition
Content of HR Draft
1. Overview
2. Normative References
3. Definition
4. Abbreviations and Acronyms
5. General Description
6. Layer management
7. General Mesh Frame Format
8. Mesh Extensions to Single-hop MAC Protocols
9. Mesh Serve Support
Annex A
Update, complement, or fill out all Chapters & Annex.
Y. Jeon, ,S. Lee, S. Choi

4. Major Editing Subjects
Major Editing Subjects
Reference Model
Primitives
Frame formats
Synchronization
Routing
Y. Jeon, ,S. Lee, S. Choi

5. Reference Model MAC Enhancement Mesh MAC SAP, Mesh MAC (Data)
Reference Model
before
after
MAC Enhancement
Mesh MAC SAP, Mesh MAC (Data)
Mesh MLME SAP, Mesh MLME (Management)
Y. Jeon, ,S. Lee, S. Choi

6. Primitives (1) Modification Primitives Because of Distributed MAC
Primitives (1)
before
after
Name
Req.
Ind.
Res.
Con.
MSME-RESET
6.2.1 -
6.2.2
MSME-GET
6.2.3
6.2.4
MSME-SET
6.2.5
6.2.6
MSME-SCAN
6.2.7
6.2.8
MSME-MESH-START
6.2.9
6.2.10
MSME-JOIN
6.2.11
6.2.12
6.2.13
MESM-LEAVE
6.2.14
6.2.15
6.2.16
MSME-MESH-DISCOVERY
6.2.17
6.2.18
Name
Req.
Ind.
Res.
Con.
MESH-MLME-RESET
6.2.1 -
6.2.2
MESH-MLME-GET
6.2.3
6.2.4
MESH-MLME-SET
6.2.5
6.2.6
MESH-MLME-SCAN
6.2.7
6.2.8
MESH-MLME-BEACON-START
6.2.9
6.2.10
MESH-MLME-BEACON-STOP
6.2.11
6.2.12
MESH-MLME-BEACON
6.2.13
Modification Primitives
Because of Distributed MAC
join/leave  beacon start/stop/indication
Y. Jeon, ,S. Lee, S. Choi

7.
Primitives (2)
Update, complement, or fill out the descriptions on the primitives
Elements
Type
Valid range
Description
When generated
Effect of receipt
Y. Jeon, ,S. Lee, S. Choi

8. Frame Formats Correct errors and make up for the missing parts
Frame Formats
Correct errors and make up for the missing parts
Frame formats
General mesh frame
Mesh data frame
Mesh command frame
Subfield descriptions
Indication
Valid value
Basic operation
Y. Jeon, ,S. Lee, S. Choi

9.
Synchronization
Section 8.7 of the former HR draft is reserved for the synchronization of the Mesh WPAN; however, it was empty.
Section 8.7 of the current HR draft has generally described about the synchronization as other sections do.
Annex A(15.3/3b MAC layer changes) describes a synchronization mechanism in detail.
Y. Jeon, ,S. Lee, S. Choi

10. Routing We eliminated “Topology Server” from the routing options.
Routing
We eliminated “Topology Server” from the routing options.
Too many routing options.
We need to reduce some of them.
Not suitable for the distributed environments of the MPNC-based mesh topology.
A single failure of topology server stops the routing function over the whole network.
The recovery process is too complicated.
Can be replaced by tree routing.
Y. Jeon, ,S. Lee, S. Choi