This document discusses network management for wireless sensor networks. It begins by introducing traditional network management models like SNMP and TOM and identifies requirements that are unique to managing WSNs. It then presents an example management architecture called MANNA. Key issues that are discussed include designing the system for limited sensor node resources, using network management to monitor resource levels and optimize performance, and challenges around naming and localization in WSNs.

1. NETWORK MANAGEMENT
FOR
WIRELESS SENSOR
NETWORKS
Pertemuan 07
Oleh Albert Sagala

2. INTRODUCTION
• In this chapter we first briefly introduce
traditional network management models,
then identify issues and requirements of a
network management system for WSNs and
present an existing network management
architecture. Issues of naming and localization
as they relate to WSN management are also
discussed.
ABS/NETWORK MANAGEMENT FOR WSN 2

3. NETWORK MANAGEMENT
REQUIREMENTS
ABS/NETWORK MANAGEMENT FOR WSN 3

4. TRADITIONAL NETWORK
MANAGEMENT MODELS
• Simple Network Management Protocol
– The simple network management protocol (SNMP) for
managing networks is in broad use today. It includes three
components: a network management system NMS),
managed elements, and agents. NMS is a set of
applications that monitor and/or control managed
elements. It can request management information (or
attributes) from the agent and present the results to NM
users in the form of figures or tables. It can also set
attributes within the agent.
• Telecom Operation Map
• Neither SNMP nor TOM is designed particularly for
wireless sensor networks.
ABS/NETWORK MANAGEMENT FOR WSN 4

5. EXAMPLE OF MANAGEMENT
ARCHITECTURE: MANNA
ABS/NETWORK MANAGEMENT FOR WSN 5

6. NETWORK MANAGEMENT DESIGN
ISSUES
• WSN is a special type of wireless network,
possibly with ad hoc structure and probably
with limited resources. Due to these WSN
constraints, networking protocols, the
application model, middleware, and sensor
node operating systems should be designed
very carefully. Network management for
WSNs is required to use those limited
resources effectively and efficiently.
ABS/NETWORK MANAGEMENT FOR WSN 6

7. Network management is much more important for
WSNs than for traditional networks for the following
reasons:
1. In order to deploy an adaptive and resource-
efficient algorithm in WSNs, the current
resource level needs to be gathered through
network management. For example, the
power availability should be known before
switching a sensor node from active (or
sleep) mode to sleep (or active) mode. Most
traditional networks do not have these
requirements.
ABS/NETWORK MANAGEMENT FOR WSN 7

8. 2. Most WSN applications need to know the
coverage area so that they ensure that the
entire space is being monitored. Topology
management can be used in case an uncovered
area is detected. Generally, there are three
approaches to increasing the coverage area: (1)
increase the node’s radio power, (2) increase
the density of deployment of senor nodes, and
(3) move the sensor nodes around to achieve
equal distribution.
ABS/NETWORK MANAGEMENT FOR WSN 8

9. 3. Nodes in WSNs are usually arranged in an ad
hoc manner. The parameters of this ad hoc
network are obtained by the network
management system.
4. Collaboration and cooperation between
sensor nodes are required to optimize system
performance. Network management is an
effective tool to provide the platform required
for this purpose.
ABS/NETWORK MANAGEMENT FOR WSN 9

10. OTHER ISSUES RELATED TO NETWORK
MANAGEMENT
ABS/NETWORK MANAGEMENT FOR WSN 10

11. Naming
• A node in a networked system is identified through naming.
This identifier is then used for communication between
nodes. Generally, there are two traditional approaches to
naming: low level and high level. Low-level naming such as
node addresses is typically application independent but
topology and location dependent.
• On the other hand, high-level naming is usually application
dependent and location independent. High-level naming is
built on the top of low-level naming.
• Communication between applications uses high-level
naming only, whereas physical communication relies on
low-level naming.
ABS/NETWORK MANAGEMENT FOR WSN 11

12. • For example, the domain name system (DNS)
in the Internet uses two types of naming: a
domain name and an IP address. The domain
name is used by applications such as Internet
browers, and the IP address is used by routing
protocol to guarantee packet forwarding.
ABS/NETWORK MANAGEMENT FOR WSN 12

13. Localization
• Sensor nodes are distributed all over the place for sensing and
data collection. It is usually helpful if the locations of sensor
nodes are also known. Advantages of this knowledge are that
(1) some applications, such as those for tracking of objects,
are highly location dependent; (2) location-based routing,
which may also result in energy conservation is enabled; (3)
knowledge of location usually enhances security; (4) locations
are helpful for sensor network management and monitoring;
(5) locations stimulate the creation of new applications; (6)
sensor nodes that move can be controlled through knowledge
of their location; and (7) for applications with low-level
naming and/or data-centric WSNs, knowledge of location
information is absolutely necessary.
ABS/NETWORK MANAGEMENT FOR WSN 13