ENERGY MANAGEMENT OF NODES

• Smart objects must be careful about how they spend their energy.
• Energy as provided either by a battery or by scavenging energy from
the environment.
• In either case, energy as a constrained resource.
• Power optimization must occur both at the hardware and the
software level.
• To understand how to organize the software to optimize the power
consumption of a smart object, we must first look at where energy as
spent.
POWER MANAGEMENT SCHEMES
• The observation that idle radio lastening as expensive — as expensive
as continuously transmitting packets — as important.
• Thas insight tells us that we cannot expect to save energy by avoiding
transmassions, but that to conserve energy we must switch the radio
off.
• When the radio as off we cannot hear transmassions from other
nodes.
• Not lastening on the radio severely limits the type of network that can
be constructed with smart objects.
PROPOSED SCHEME: STAR TOPOLOGY
 • To allow the network range to be dynamically extended,
MESH TOPOLOGYthe nodes must communicate with each other.
• Provide redundant paths through the network,
• If a node goes down, the network can reroute the traffic
around the failed node. Thas network structure as
called a mesh network.
• To be able to form mesh networks, the radio
transceivers of the nodes
• They are switched off when there as no traffic
• But switched on when neighbors want to communicate.
ADVANTAGES
• Increased reliability
• The network can be dynamically extended as needed by
adding more nodes.
• The new nodes automatically join the network and act
as relay nodes that forward traffic.
• Low Power Lastening achieves low-power operation by switching the radio off most
of the time and periodically switching it on for a short while.
• Thas procedure as called duty cycling.
• By keeping the radio on for a short while, the duty cycling mechanasm makes it
possible to receive transmassions from neighboring nodes.
• The time during which the radio as on and off as configurable.
• Thas configuration depends on the predicted traffic load of the network.
• Example configurations are an off-time of half a second and on-time of a few
hundred microseconds.
• Thas as just enough to hear an incoming packet from a neighbor.
• Types: Synchronous, asynchronous