Tools
Sorted by:
Try your query at:
 |
 |
 |
 |
 |
 |
Results 1 - 10
of
19,379
Table 1. Costs to evaluate the Tate Pairing on MICAz.
2007
"... In PAGE 6: ...lscript = 170141188531071632644604909702696927233; h = 222060320700642449943812747791145685108; where h stands for the cofactor of the curve order #E(Fq)1. Results in Table1 were measured on a MICAz node running TinyOS [18]. The average execution time to compute a pairing is 30.... ..."
Cited by 2
Table 3: User interface node comparison. MICAz is running In-Situ/Sensory Data Display application under TinyOS with the radio reception enabled.
2006
"... In PAGE 7: ... The LCD module, however, is a small, self-contained device that provides sufficient functionality for the user interface and naturally interfaces with the host mote via the standard 51-pin connector. The power consumption of the LCD module running the remote sensory data display application with the display on is 60mA to 110mA at 3V depending on the backlight intensity, which translates to 180mW to 330mW ( Table3 ). An iPaq PDA running Microsoft Windows CE operating system consumes 1.... ..."
Cited by 4
Table 14: Lifetime of the evaluated nodes considering diverse duty cycle settings Duty cycle [%] Tmote Sky MICAz MICA2 MICA2DOT
"... In PAGE 27: ...ations each node is able to process in these diverse duty cycle settings differ as mentioned in section 2.1.2. Anyway, Table14 shows that for the agriculture scenario the duty cycle cannot be much more than 1 % to reach the requested lifetime of 5 months. In the homeland security scenario if the requested lifetime is about two days, all nodes manage this lifetime even with 100 % duty cycle.... ..."
TABLE VI SIMULATED CLOCK SPEED FOR SIMULATED 2 -D GRID OF MICAZ MOTES. EACH ROW HAS FIXED NUMBER OF NODES PER HOST AND EACH COLUMN HAS FIXED NUMBER OF HOSTS. ALL VALUES ARE NORMALIZED TO REAL TIME CLOCK SPEED.
2005
Cited by 3
Table 1 shows the code sizes of these schemes compiled for MICAz motes, assuming that each node uses up to 14 anchors. These numbers are obtained using the check size.pl script provided in the TinyOS distribution. Note that the RAM size does not include the memory consumed by local variables in stack. Since the nesC Compiler optimizes the whole program by default, to compare the size of code fairly, we disabled the optimization of nesC compiler.
"... In PAGE 9: ... Table1 : Code sizes of secure and resilient localization schemes under comparison (up to 14 location references) 4.2 Field Experiments We perform a series of outdoor field experiments using MICAz motes to compare the proposed schemes with the other alternatives under investigation.... ..."
Table 2. Memory usage and performance of Surge on the MicaZ mote platform.
in HERMES: A Software Architecture for Visibility and Control in Wireless Sensor Network Deployments
"... In PAGE 8: ... We used the Rate Adaptive Time Syn- chronization (RATS) protocol [26] to time-synchronize the nodes and collected statistics on packet latency and num- ber of packets delivered to the base staton. Table2 presents memory usage and performance statistics for Surge on plain SOS, and on SOS+HERMES in four cases: no interposition module, Surge interposition module loaded with interposi-... ..."
Table 1. Comparison of wireless sensor nodes.
1993
"... In PAGE 22: ... The ZigBee protocol is capable of supporting over 64000 nodes for each network coordinator, and multiple network coordinators can be linked together to support very large networks. Various system requirements influence the capability of wireless networking sensor systems, and the discussion above is summarized in Table1 . Conforming to the re- quirements, the BTnode, and the Mica-Z platforms are interesting nodes for creat- ing an ad-hoc network of wireless sensors.... ..."
Cited by 1
Table 3. Performance Comparison: Eco vs. MICA2-DOT vs. MI- CAz
2005
"... In PAGE 5: ...3. Performance Table3 compares the performance of the Eco node, MICA2-DOT, and MICAz. Both MICA2-DOT and MICAz have a larger size of program memory and an external 512KB flash memory for data acquisition.... ..."
Cited by 10
Table 12: Estimated amount of signature generation / verification operations and key exchange operations for the client and server side on a MICA2/MICAz and TelosB with the 6750 Ws of energy available by the double AA battery pack as well as on the MICA2DOT with the 4400 Ws available by the cr2354 cell battery. If the calculation if followed by transmission the amount of operations is reduced by about 1 per cent Node Crypto- Signature
2006
"... In PAGE 14: ... With the values collected so far we calculate the amount of public key cryp- tography operations the nodes can perform with the available amount of energy. See Table12 . According to our estimations, at 100 % duty cycle, the processing unit of TelosB is able to run for 156.... ..."
Cited by 10
Table 13: Estimated duty cycle and lifetime for RSA-1024 signature generation on a MICA2, MICAz and TelosB with the 6750 Ws of energy available by the double AA battery pack as well as on the MICA2DOT with the 4400 Ws available by the cr2354 cell battery. If the calculation if followed by transmission the values are about 1 per cent worse RSA-1024 signature generation Node duty cycle lifetime
2006
"... In PAGE 14: ...nd MICA2DOT for 77.1 hours with the available energy. Thus, the use of public key cryptography shall not increase the duty cycle of the node in a sig- nificant manner. The results in Table13 and Table 14 show that the numbers for ECC-160 are reasonable. They are even for RSA-1024, but in both cases, only if the operations are used with care.... ..."
Cited by 10
Results 1 - 10
of
19,379
