each proposal when possible. This document is to be used as a comparison basis for the merging/down-selection process. Functionalities from the TGD Functionality NICT OKI ETRI 1(Hybrid ETRI 2 (TCT) L2R) Mesh topology Yes Yes Yes Yes discovery (enhanced beacons) (Hello frames) (PANN and (Link setup Topology: Topology: Tree PANN RP) request/response) Hierarchical mesh Topology: Tree Tiered cluster tree tree Mesh Routing Yes Yes Yes Yes -US: Hop-by-hop -US: Hop-by-hop -US, DS: -US, DS, P2P: from child to parent child to parent using routing using cluster table or brother using using neighbor table and route table neighbor table table -P2P: -DS: -DS: source routing establishment * Hop-by-hop parent with PREQ and to or brother -P2P: Combination PREQ RP, then using neighbor table, of US and DS Hop by hop using * Proactive source routing table routing -P2P: Combination of US and DS Extensible mesh routing Using the Link Using the Neighbor Using the Metric architecture (metric quality metric field in metric container in field in PANN alternative, selection, EB for 1 or more Hello frames for 1 and PREQ for 1 notification, new metrics or more metrics metric metrics) Unicast Yes Yes Yes Yes Broadcast Yes: packet Flooding with forwarded once if at random jitter 1 child exists Route discovery Proactive Proactive US/DS: proactive Proactive P2P: reactive Low operation To see from the simulations results Mesh Security Only devices from KMP the same PAN sharing the same
each proposal when possible. This document is to be used as a comparison basis for the merging/down-selection process. Functionalities from the TGD Functionality NICT OKI ETRI 1(Hybrid L2R) ETRI 2 (TCT) Mesh topology discovery Yes (enhanced beacons) Topology: Hierarchical mesh tree Yes (Hello frames) Topology: Tree Yes (PANN and PANN RP) Topology: Tree Yes (Link setup request/response) Tiered cluster tree Mesh Routing Yes -US: Hop-by-hop from child to parent or brother using neighbor table -DS: * Hop-by-hop parent to or brother using neighbor table, * Proactive source routing -P2P: Combination of US and DS Yes -US: Hop-by-hop child to parent using neighbor table -DS: source routing -P2P: Combination of US and DS Yes -US, DS: using routing table -P2P: establishment with PREQ and PREQ RP, then Hop by hop using routing table Yes -US, DS, P2P: using cluster table and route table Extensible mesh routing architecture (metric alternative, selection, notification, new metrics) Using the Link quality metric field in EB for 1 or more metrics Using the Neighbor metric container in Hello frames for 1 or more metrics Using the Metric field in PANN and PREQ for 1 metric Unicast Yes Yes Yes Yes Broadcast Yes: packet forwarded once if at 1 child exists Flooding with random jitter Route discovery Proactive Proactive US/DS: proactive P2P: reactive Proactive Low operation To see from the simulations results Mesh Security Only devices from the same PAN sharing the same KMP
15-14-0520-00-0010-list-of-functionalities.docx