1. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: Evaluation of Layer 2 Routing Proposal
Date Submitted: 13 July, 2014
Source: Seong-Soon Joo, Youn-Kwan Kim, In-Hwan Lee, Hyo-Chan Bang
Company: ETRI, Catholic University
Address: 161 Gajeong-dong, Yuseong-gu, Daejeon, KOREA
Voice: , FAX: ,
Re:
Abstract: As a final contribution proposal for the IEEE TG10 standards, the layer 2 routing specification is evaluated.
Purpose: Response to the IEEE TG10 call for contribution
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
<author>, <company>

2. Evaluation of Layer 2 Routing Proposal
<month year>
doc.: IEEE <doc#>
Evaluation of Layer 2 Routing Proposal
Seong-Soon Joo*,
Youn-Kwan Kim, In-Hwan Lee, Hyo-Chan Bang
ETRI
<author>, <company>

3. Simulation Set (I) L2R network for simulation topology
visibility of 3 grid points, neighbor consist of 28 nodes
11 X 11 (121 nodes), 33 X 33 (1,089), 100 X 100
multicast : 1 to 5 (11x11), 1 to 10 (33x33), 1 to 20 (100x100)
m to 1 : 5 to 1(11x11), 10 to 1 (33x33), 20 to 1 (100x100)
PAN coordinator – device
PHY data rate : 100Kbps (option: 250Kbps)
application packet rate : 1pkt/30min (up), 1pkt/300min to M-1 device (down)
packet size : 100 bytes
Peer to Peer
PHY data rate : 250Kbps (option: 20Kbps, 2Mbps option)
application packet rate : 1pkt/min (option: 1pkt/sec, 1pkt/30min)
packet size : 255 bytes (option: 31bytes, 2,047bytes)
energy consumption
TX : 28mA
RX : 11.2mA
idle : 1.5uA
battery capacity : 2,000mAh
link failure rates
one-hop neighbor (10-6), one-hop across (10-5)
two-hop neighbor (10-4), two-hop half across (10-3), two-hop across (10-2)
three-hop neighbor (10-1)

4. Simulation Set (II) evaluation cases evaluation parameter
PAN coordinator – device : multicast
device – device : unicast
device – device : multicast
multiple devices – device : m to 1
route update
1min for 11x11
10min for 33x33
evaluation parameter
amount of memory per node used for routing
calculation cost
control traffic
when initializing network
when updating network
when sending data packets
recovery time of link failure
complexity scales with the size of the network
end to end packet loss ratio
end to end delay
life time of battery

5. Emulation (I) set simulation scenario set device deployment
configure PHY (rate)
configure MAC (async/beacon/CSMA/TDMA/superframe)
configure APPL (packet rate, size)
configure scenario (PAN-device: 1-m, device-device: 1-1/1-m/m-1), number of device/coord
set device deployment
assign extended address (sequential number), location (x,y), neighbor list
assign role of device (PAN coord, cluster root capable, router capable, device)
assign enter/exit device, configure scenario
set simulation active time/deactive time to each device

6. Emulation (II) PAC coordinator start network associate device
scan
associate device
assign address
set link
assign cluster root
maintain cluster matrix table
update cluster matrix table
serve to application user
route generated application data
forward application data to/from higher layer
bridge to core network

7. Emulation (III) cluster root router join to PAN establish link routing
scan neighbor
select parent based on distance to PAN coord, radio metric (RSSI)
request address allocation(or cluster root), routing table(cluster matrix)
establish link
routing
check within same cluster
select inward or outward link based on address
not in same cluster
calculate route metric
select cluster tree link or inter cluster mesh link
forwarding packet
queuing
route update
maintain link within cluster
send hello periodically to device
request link status
maintain cluster root
send hello periodically to root router
request cluster root status
update route table
within cluster
cluster matrix for whole network

8. Emulation (IV) router device application user network events
join to PAN
routing
route update
device
data
application user
generate data
receive data
network events
device join/leave
router join/leave
cluster root router join/leave

9. Emulation (IV) emulator scheduler device emulator
memory
control processor
MAC
PHY
radio communication emulator
interference
transmission
application user emulator
L2R network emulator
PAC coordinator
cluster root router
router
end device

10. L2R PHY/MAC Set PHY MAC PAN coordinator – device : 100Kbps
868MHz, O-QPSK, 25ksymbol/s
BaseSlotDuration (2.4ms, 30bytes)
device – device : 250Kbps
2.4G, OQPSK, 62.5ksymbol/s
BaseSlotDuration (0.96ms, 30bytes)
MAC
superframe
slot length = 2SO * BaseSlotDuration
superframe duration = slot length x 16
beacon interval = 2BO * BaseSlotDuration x 16
nonbeacon-enabled PAN
100Kbps
slot length = 19.2ms
IEEE beacon enabled PAN
250Kbps : BO = 7 (BI = sec), SO = 3 (SD = ms)
slot length = 7.68ms, CAP = 8 x 7.68 = 56.54ms, CFP = 7 x 7.68 = 53.76ms
IEEE e DSME PAN
250Kbps : BO = 7, SO = 3, MO = 5 (number of superframe in a multi-superframe = 25-3)

11. Emulation Results (I) amount of memory per node used for routing
neighbor device table + cluster matrix + route table
neighbor device table
router address
16 bit address (cluster ID + router ID)
64 bit address
link list
link
link ID
link type (CAP/CFP, default/shared/dedicated)
slot ID
link quality (RSSI, interference level)
queue load (frame count, loss count)
size of device table
number of device * { route address (2+8) + number of link * link infor ( ) }
11x11
number of device =8, number of link = 2
176bytes

12. Emulation Results (II)
cluster matrix table
router address
16 bit address (cluster ID + router ID)
64 bit address
reflector address
address assigned in the parent cluster or
address of opposite end neighbor router on mesh link
distance to PAN coordinator
cluster configuration
depth/number of router/number of device
child cluster list
16 bit address
size of cluster matrix table
number of cluster {route address (2+8+2) +(1+3) + number of child root * route address (2+2) }
11x11
number of cluster =9, number of child root = 8
432bytes

13. Emulation Results (III)
route table
device address
16 bit address (cluster ID + router ID)
route list
route
link ID
route cost (distance, link quality, router load)
size of route table
number of device * { device address (2) + number of route * route infor (1+1) }
11x11
number of device in a cluster = 24, number of route = 8
432bytes
amount of memory per node used for routing
11 x 11
= 1,040bytes

14. Emulation Results (IV)
control traffic
11 x 11
when initializing network
1 packet upward
5 packets downward
when updating network
full update : 5 packets downward
partial update : 1 packet downward
when sending data packets
no control packet needed

15. Emulation Results (V) recovery time of link failure end to end delay
11x11, IEEE beacon enabled PAN (BO=7)
edge device recovery time : sec
end to end delay
11x11, IEEE beacon enabled PAN (BO=7, BI=1.96sec)
edge device to PAN coordinator : 3hops, 5.88 sec