1. <doc.: IEEE 802.15-doc>
<month year>
<doc.: IEEE doc>
January 2014
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [PHY frame structures comparison and harmonization]
Date Submitted: [ January 3rd, 2014]
Source: [Marco Hernandez, Huan-Bang Li, Igor Dotlić, Ryu Miura ]
Company: [NICT]
Address: [3-4 Hikarino-oka, Yokosuka, , Japan]
Voice:[ ] Fax: [ ] []
Re: [In response to call for technical guidance document contributions TG8]
Abstract: [ ]
Purpose: [Material for discussion in TG]
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
Hernandez,Li,Dotlić,Miura (NICT)
<author>, <company>

2. <737r0> Cho harmonized frame structure
January 2014
<737r0> Cho harmonized frame structure
The radio resource is comprised of successive superframes with fixed time duration and low duty cycle.
The superframe consists of synchronization, discovery, peering and payload or data communication that includes scheduling.
The data communication interval supports CAP and CFP
It is excellent as it contains all elements needed for a PAC system
Hernandez,Li,Dotlić,Miura (NICT)

3. <377r0> Shannon (Samsung)
January 2014
<377r0> Shannon (Samsung)
Discovery frame
Data frame
Hernandez,Li,Dotlić,Miura (NICT)

4. <377r0> Shannon (Samsung)
January 2014
<377r0> Shannon (Samsung)
The discovery structure is similar to <737r0>
The data frame structure is similar to <737r0> (including scheduling period).
Except feedback channel and ACK signal.
There is not synchronization frame.
There is not peering frame.
Suggested harmonization:
Add synchronization and peering frames similar to <737r0>.
Hernandez,Li,Dotlić,Miura (NICT)

5. <701r2> Marco (NICT)
January 2014
<701r2> Marco (NICT)
Similarities to <737r0>
Frame structure
Sync region
Discovery region
Peering region
Data region (including scheduling)
Discovery structure
The sync, discovery (without preamble) and peering “regions”
have the same <737r0> structure.
The data regions differ in the use of time-frequency resource block.
Peering structure
Hernandez,Li,Dotlić,Miura (NICT)

6. <701r2> Marco (NICT)
January 2014
<701r2> Marco (NICT)
Suggested harmonization:
in <701r2> rename blocks as synchronization, discovery, peering and data (including scheduling). Delete preamble in discovery block.
In the data communication interval of <737r0> consider to include time-frequency resources like in the discovery and peering intervals.
In the peering region of <737r0> consider how to accommodate the peering procedure of clause of <701r2>.
Hernandez,Li,Dotlić,Miura (NICT)

7. <373r1> BJ (ETRI) Data frame closely tight to CSMA.
January 2014
<373r1> BJ (ETRI)
Data frame
Data frame closely tight to CSMA.
There is no discovery, peering and scheduling intervals (due to the nature of CSMA)
Hernandez,Li,Dotlić,Miura (NICT)

8. <373r1> BJ (ETRI) Suggested harmonization:
January 2014
<373r1> BJ (ETRI)
Suggested harmonization:
It is possible to accommodate this data frame in the CAP of the frame structure proposed in <737r0>.
Adapt the distributed network synchronization in order for PAC devices to know when the CAP starts and ends.
Hernandez,Li,Dotlić,Miura (NICT)

9. <384r0> Park (ETRI) Discovery frame
January 2014
<384r0> Park (ETRI)
Discovery frame
File under discovery, but it looks like a data frame with synch (preamble).
There is no peering interval.
I am not sure if the accompanying MAC does not require a scheduling interval.
Hernandez,Li,Dotlić,Miura (NICT)

10. January 2014
<384r0> Park (ETRI)
As this is intended for an optional low power PHY with FSK modulation:
Suggested harmonization:
Adapt the discovery, peering and scheduling intervals of <737r0>.
Hernandez,Li,Dotlić,Miura (NICT)

11. January 2014
Conclusion
The proposed harmonization of frame structure seems to be achieved by <737r0>, <377r0> , <707r2> and <373r1>.
The accompanying MAC is a mix of distributed synchronous and CSMA.
The frame structure of <384r0> is missing elements like peering, scheduling and how the discovery/peering procedure is done.
Recommended for Call for Contributions.
Hernandez,Li,Dotlić,Miura (NICT)