1. doc.: IEEE 802. 15-12-0509-00-0008 Submission, Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Merged Comments to DCN385-02 TGD Draft] Date Submitted: [18 September 2012] Source: [Seung-Hoon Park] Company [Samsung Electronics] Address [416, Maetan-3Dong, Yeongtong-Gu, Suwon-Si, Gyeonggi-Do, 443-742, Korea] Voice:[+82-10-9349-9845], FAX: [+82-31-279-0813], E-Mail:[shannon.park@samsung.com] Re: [.] Abstract:[Merged comments to revise TGD draft document (based on DCN385-02)] Purpose:[To summary and compare comments to TGD draft document] 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.

2. doc.: IEEE 802. 15-12-0509-00-0008 Submission Merged Comments to DCN385-02 TGD Draft September 18, 2012 Seung-Hoon Park Slide 2,

3. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 2.2 Specific definitions to this standard CommenterComments Eldad Zeira  Add “PAC Peer Aware Communication”  Discovering PD (DPD) means a PD which is doing discovery function and is not connected yet. Connected PD (CPD) means a PD which is connected to another PD. [Eldad] Suggest replacing above with the following definitions: PPD – Peered PD, a device which has been peered with another device. PSPD – Peer seeking PAC device, a device which is actively attempting to discover / be discovered by other devices in order to peer. (Note that this definition allows a PD to seek other devices while already being peered)  SG - Service Group - a collection of PDs that are members of the same service set. [Eldad] we need to define what is a service set Suhwook Kim  Add “Peering: To establish a link or multiple links between PDs or among PDs for the purpose of announcing information or exchanging traffic.”, Slide 3

4. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4. General Description, Slide 4 CommenterComments Eldad Zeira  This clause provides the basic framework of PDs and links. The framework serves as a prerequisite to supporting the functions of PDs and links and their interactions specified later in detail. It covers amongst others the following aspects — the architecture, components, services, the network topology used for medium access, the transmission range, the reference model used for functional partitioning, and the time base used for access scheduling, and the security paradigm used for message protection. Suhwook Kim  It covers the following aspects — the architecture, components, services, the network topology used for medium access, the transmission range, the reference model used for functional partitioning, and the time base used for access scheduling, and the security paradigm used for message protection. [Suhwook] It’s redundant  *To be re-written**.

5. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.1 Concepts and architecture, Slide 5 CommenterComments Eldad Zeira  This section describes general concepts, e.g. sects. 4.1, 4.5 in [1] with some of the original material moved elsewhere. [Editor’s comments] 4.1 Concepts and architecture, and 4.5 Topology from DCN385-01. Eldad suggested to merge 4.1 and 4.5 into single sub-clause. –Shannon will provide a clean version.  802.15.8 PAC shall support a fully distributed, decentralized, data scalable, and self organized system composed of single type of PAC device to be named PAC Devices, or PDs.  Some of these devices may be able to connect on an opportunistic basis to infrastructure through means, which is out of scope for 802.15.8.  802.15.8-PAC shall support Oone-to-one and, one-to-many communications topology shall be supported.

6. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.1 Concepts and architecture, Slide 6 CommenterComments Suhwook Kim  This subclause presents the concepts of IEEE 802.15.8 and how the architectural components are related to the overall procedure. [Suhwook] It’s redundant.  802.15.8 PAC shall support low data rate long distance.  PAC shall support scalable data rate to accommodate many applications such as listed in the Application Matrix (doc. #). [Suhwook] It’s ambiguous. PAC supports not only low data rate long distance but also high data rate short distance, or etc.  Possibly aided by higher layers, PD shall support selective exchange of data with specific other PDs or groups of PDs  Possibly aided by higher layers, a PD shall support data transfers between itself and identified PDs or groups. [Suhwook] What is ‘selective’ exchange of data?  PAC shall support both one-way and two-way communications. [Suhwook] PAC supports both one way and two/multi way communication.

7. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.1 Concepts and architecture, Slide 7 CommenterComments Seung-Hoon Park  Replace “802.15.8 PAC shall support a fully distributed, decentralized, data scalable, and self organized system.” to “802.15.8 PAC shall support a fully distributed, decentralized, and self organized system.  “Possibly aided by higher layers, PD shall support selective exchange of data with specific other PDs or groups of PDs.” [Shannon] Define “selective exchange of data”.  Add “IEEE 802.15.8 PAC shall provide discovery for peer information without peering. Peering is a function to establish single link or multiple links. Discovery without peering is beneficial by reducing redundant procedures to setup links and to exchange data among non-peer PDs. So discovery after peering shall be avoided in the efficiency aspect and novelty of 802.15.8.”  Exchange of messages for the purpose of discovery alone shall be minimized.

8. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.2 Components (States of devices?), Slide 8 CommenterComments Eldad Zeira  Discovering PD (DPD) means a PD which is doing discovery function and is not connected yet. Connected PD (CPD) means a PD which is connected to another PD. [Eldad] Suggest replacing above with the following definitions: PPD – Peered PD, a device which has been peered with another device. PSPD – Peer seeking PAC device, a device which is actively attempting to discover / be discovered by other devices in order to peer. (Note that this definition allows a PD to seek other devices while already being peered)  SG - Service Group - a collection of PDs that are members of the same service set. [Eldad] we need to define what is a service set

9. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.2 Components (States of devices?), Slide 9 CommenterComments Suhwook Kim  Discovering PD (DPD) means a PD which is doing discovery function and is not peeredconnected yet. PeeredConnected PD (PPDCPD) means a PD which is peeredconnected to another PD within a service [group ]. Service Group (SG) means a collection of PDs which are connected by the same service set. [Suhwook] If ‘A’ PD is peered to ‘B’ PD for a service and discovering to ‘C’PD for the other service, ‘A’ PD is DPD and PPD. Therefore I suggest the category is only applied to within a service [group]. Seung-Hoon Park  Replace The title “Components” to “Roles”. [Shannon] There is no hierarchy within PDs. However, a PD can take a specific role according to event (e.g. peering)

10. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.3 Topology, Slide 10 CommenterComments Eldad Zeira  An illustrative 802.15.8-PAC topology is depicted in Fig. 1:  Fig. 1: 802.15.8-PAC topology. Solid lines are 802.15.8-PAC links. Red solid lines are one to many links. The dashed link to server is out of scope. “Delete the line and Server from the figure

11. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.3 Topology, Slide 11 CommenterComments Seung-Hoon Park  Add a figure

12. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.4. Services, Slide 12 CommenterComments Eldad Zeira  802.15.8 PAC shall support a PD ability to: Discover other PDs or groups of other PD’s in proximity and be discoverable by them Discover other PDs or groups of other PD’s in proximity but not be discoverable by them Be discoverable by other PDs or groups of other PD’s but not discover them Neither discover nor be discoverable Communications with discovered PDs. Suhwook Kim Title “Services” [Suhwook] The contents are not suitable to the title. Please change the title to such as PD ability or fill the contents to fit the title.

13. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.4. Services, Slide 13 CommenterComments Seung-Hoon Park  Replace “802.15.8 PAC shall support a PD ability to:” to “802.15.8 PAC shall provide a discovery service that user or application aware peers in the proximity. 802.15.8 PAC shall support a PD discovery ability to:”  Add “802.15.8 PAC shall provide traffic services such as best effort, non real-time, real-time, streaming, gaming or etc.”

14. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.5 Reference model, Slide 14 CommenterComments Eldad Zeira Group’s: move the contents to “Concepts and Architectures” subclause. “Add other relevant layers above MAC sublayer”  Modify the title to “Reference protocol model”  “Message security services are to occur at the MAC sublayer, and security key generationsoperations are to take place inside and/or outside the MAC sublayer.”  Modify picture Fig. Xxx: Protocol Architecture. Grayed out boxes signify layers and nodes not specified by 15.8. Dotted lines signify an intermittent connection

15. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 4.5 Reference model, Slide 15 CommenterComments Suhwook Kim  “All PDs are internally partitioned into a physical (PHY) layer and a medium access control (MAC) sublayer of the data link layer,” [Suhwook] Why PHY layer and MAC sublayer?

16. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6. Functional requirements, Slide 16 CommenterComments Suhwook Kim  This cause contains system level functional requirements targeting peak spectral efficiency, latency, synchronization time, discovery capacity, scheduling, QoS, interference management, power management, system complexity, security.

17. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.1 Multiple access, Slide 17 CommenterComments Eldad Zeira  The multiple access schemes shall be designed as follows:. Contention-free access scheme, contention- based, or other access scheme may be considered for control and data transmission.  Multiple access schemes shall be supported. (Accepted)  [Eldad] Since any multiple access is either contention- based or contention-free I suggest replace with a simpler statement: Suhwook Kim  The multiple access schemes shall be designed as follows: Contention-free access scheme, contention-based, or other access scheme may be considered for control and data transmission. [Suhwook] ‘Shall’ PAC support both of them?  802.15.8 PAC shall support prioritized channel access. [Suhwook] What’s the prioritized channel access?

18. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.2 Synchronization, Slide 18 CommenterComments Eldad Zeira  Remove this sub-clause Suhwook Kim  It’s not decided which the system supports synchronization or not. Seung-Hoon Park  Leave this sub-clause. [Shannon] a minimum of synchronization functionality is required for data transmission/reception or ranging.  Add “A transmitting PD and a receiving PD shall be synchronized to support low duty cycling as well as ranging.”  [Shannon] Link-level synchronization to Tx-Rx pair shall be provided for low power consumption as well as ranging.  Add “ A multiple of proximal PDs shall be synchronized for efficient channel access.” [Shannon] System-level synchronization shall be provided to get higher throughput from synchronous channel access mechanism than one from asynchronous channel access mechanism.

19. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.3 Discovery (1), Slide 19 CommenterComments Suhwook Kim  IEEE 802.15.8 shall support that PD finish the discovery of other PDs [within the same service] before peering. 802.15.8 PAC shall support data discovery latency to xxx ms. Possibly aided by higher layers, 802.15.8 PAC shall support selective discovery and discoverability by specific other PDs or groups of PDs. [Suhwook] groups of PDs  It’s ambiguous. Seung-Hoon Park Group’s decision  Replace the title “Discovery (PD discovery or Peer discovery)” to “Peer discovery” [Shannon] The “Peer” information can include Application, service, user (nick)name PAC Device type, and capability A PAC Device shall support peer discovery, service di scovery, and group discovery. Peer discovery includes device discovery.

20. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.3 Discovery (2), Slide 20 CommenterComments Eldad  802.15.8 PAC shall support a PD ability to: Discover other PDs or groups of other PD’s in proximity and be discoverable by them Discover other PDs or groups of other PD’s in proximity but not be discoverable by them Be discoverable by other PDs or groups of other PD’s but not discover them Neither discover nor be discoverable Communications with discovered PDs.

21. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.4 Peering (Link establishment, or association), Slide 21 CommenterComments Suhwook Kim  “ 802.15.8 PAC shall support a quick peering between PDs that have already discovered each other.” [Suhwook] Do we support peering without discovering? Seung-Hoon Park  Replace the title “Peering (Link establishment, or association)” to “Peering”  “802.15.8 PAC shall support a quick peering between PDs that have already discoveredpeered each other.”

22. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.8 Multicast and 6.9 Broadcast, Slide 22 CommenterComments Eldad Zeira  [Eldad] isn't it covered under one to many?

23. doc.: IEEE 802. 15-12-0509-00-0008 Submission Comments to 6.10 Multi-hop support, Slide 23 CommenterComments Seung-Hoon Park  Add “Only relay-enabled PDs decided by peer information shall relay discovery messages and/or data from PDs in the proximity.” [Shannon] Only users in the same peer group can support relaying. How selfish user helps relaying for different group users? So it shall be decided by peer information.