Timer and Distance Based Routing Protocol for Continuous Monitoring Application in WSN

Abstract

Dissemination of gathered data to sink is one of the main aspects in wireless sensor networks. Gathered data can be sent to the sink either directly or through multi-hop path. For an application like continuous monitoring of data, data have to be reported continuously to sink. As a result, node that form a part of static path towards sink, especially nodes near the sink may dissipate energy rapidly resulting in hotspot problem. Recent studies reveal the use of mobile sink as an efficient method for collecting data, as it avoids the hotspot problem that happens with static sink. While using mobile sink, we need to take care in maintaining dynamic paths and delay constraints. In this paper, we have used the concept of both mobile sink and static sink. Additionally we have introduced a timer and distance based approach for determining a better path. Here, we distribute the load among different CHs and use dynamic shorter paths, as opposed to usual fixed longer paths. Extensive simulations are carried out in Castalia-3.2 for evaluation of our approach. Our results show improved energy efficiency and network lifetime as compared to using static sink and mobile sink separately. The proposed system also reduces end to end delay by which applications like continuous monitoring can be enhanced.

An Authentication-Based Secure Data Aggregation Method in Internet of Things

“…In WSN [19,25], the radio energy dissipation model is used to transmit m bit message over a distance d in the transmission is according to (1). This energy model is also used in the proposed method.…”

“…Fig. 15 Registration steps of the proposed authentication protocol second cluster head, the first cluster head computes A i according to (18), using T i and CK ′ , and then computes P ′ 4 according to (19) and compares P ′ 4 with the received P 4 according to (20). It ends the session if the two values not equal.…”

“…In the proposed method, in none of the authentication operations, the node ID is sent directly. In the authentication steps, the pseudonym is used to identify the cluster heads, as shown in (18) and (19). The pseudonym is updated to prevent tracking attacks after each authentication operation under (24) and (25).…”