March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Comparison of use cases and their requirements in and in Sections 5 and 6 of Date Submitted: March 17, 2014 Source: Jaehwan Kim (ETRI), Sangjae Lee (ETRI), Sangsung Choi (ETRI), Soo-Young Chang (SYCA), and Kyuyong Lee (A2UICT)Voice: , l: Re: [ TG10 TGD] Abstract: In , use cases are described in Sections 5 and 6. The TG10 group decided to include description of all use cases to Section 5 and their requirements to Section 6. This document was prepared to check all use cases which are described in are included in Sections 5 and 6. Purpose: To prepare the evaluation methodology for TG10. 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

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 2 Applications in doc Smart Metering (HAN and NAN)included in 5.1 in – Advanced metering infrastructure (AMI): Smart City (Street Lighting/Parking/Meters) included in 5.2 in All applications listed in are also included in

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 3 Requirements in doc (Dynamic) Address network changes on the order of a minute time frame Minimizes impact to route handling Route establishment and continuity – Effective frame forwarding Priority vs. sphere of relevance (right size fit for the priority level) – Impact of maintaining security (don’t break it) Impacts on provisioning, joining Dynamic route reconfiguration – Discovery and addition of new nodes – Breaking of established routes – Loss and recurrence of routes – Pruning of routes – Restart of network

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 4 Requirements in doc (cont’d) Route determination metrics and real time gathering of link status (Policy & Metrics) – Intra Quality of individual hop Quality of end-to-end route – Reduction of end-to-end retransmissions Latency Data rate/multi-hop end-to-end route time Resources (constraints) – Inter workings Reported to system management – Persistent/consistent issues – Node outage (failure detection) Respond to system management feedback

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 5 Requirements in doc (cont’d) Support scalability – Node density, network size etc. – Hardware resource requirements – Behavior at restarts – Secondary, tertiary route considerations – Scalability of # takeout points - bridges to connecting networks (take out points) Management of flooding, multicasts – Support of broadcast – Support of (efficient) multicast Allowing for single hop appearance at the networking layer (not breaking standard L3 mechanisms) Multiple route approaches within a network, possibilities include: – Concentric based – Linear (highway based) – Function /behavior/ priority based

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 6 Subsections in for requirements Dynamic) Address network changes on the order of a minute time frame – Routing Metrics – Discovery and Association with a L2R Network – Frequency Agility Minimizes impact to route handling – 7.4. Control Traffic Overhead Route establishment and continuity – Purpose of PAR Priority vs. sphere of relevance (right size fit for the priority level) – Mesh Security Impacts on provisioning, joining – 6.1. Mesh Topology Discovery

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 7 Subsections in for requirements (cont’d) Dynamic route reconfiguration – Purpose of PAR Route determination metrics and real time gathering of link status (Policy & Metrics) – Quality of Service – 7.5. Route Acquisition Time Support scalability – 6.7. Memory Usage – 6.8. Mesh Network Size – 7.7. Scalability to Network Size Management of flooding, multicasts – 6.4. Mesh Broadcast Data Delivery Allowing for single hop appearance at the networking layer – Purpose of PAR Multiple route approaches within a network, possibilities include: – 6.3. Extensible Mesh Routing Architecture

March 2014 doc.: IEEE Submission Jaehwan Kim (ETRI) Slide 8 Conclusion The goal of this document is to check whether all applications and related requirements listed in are included in All applications listed in are also included in All requirements listed in are also included in