Академический Документы
Профессиональный Документы
Культура Документы
A B
Interface
Interfaces are bidirectional: they specify a set
of commands, which are functions to be implemented by
the interface’s provider, and a set of events, which are
functions to be implemented by the interface’s user.
For a component to call the commands in an interface, it
must implement the events of that interface.
A single component may use or provide multiple
interfaces and multiple instances of the same interface.
Interface (provide and use)
User
Commands
Interface
Events
Provider
Module BlinkC {
use interface xxxx;
provide interface xxxxxxx;
.........
}
18
If a component calls a command, it uses the interface
and the component which implements this command is
the provider of this interface.
If a component calls an event function, it is the provider
of the event, and the component which implements this
event function is the user of the event.
Configuration and Modules
Components are classified into configuration components
and modules.
Modules provide the implementations of one or more
interfaces.
Configurations are used to assemble other components
together, connecting interfaces used by components to
interfaces provided by others.
NETWORK ARCHITECTURE
It introduces the basic principles of turning individual
sensor nodes into a wireless sensor network. In this
optimization goals of how a network should function are
discussed as :
Sensor network scenarios
Optimization goals and figures of merit
Gateway concepts
SENSOR NETWORK SCENARIOS
Types of sources and sinks:
Source is any unit in the network that can provide
information (sensor node).
A sink is the unit where information is required, it could
belong to the sensor network or outside this network to
interact with another network or a gateway to another
larger Internet.
Single-hop sensor network :
There are three types of sinks in a very single – hop
sensor network :
In the first case, the sink could be an another sensor
node from a sensor network.
this second case, the sink could be an actual device, for
example, a hand-held or PDA used to interact with the
sensor network;
It could also be merely a gateway to another larger
network such as the Internet, where the actual request
for the information comes from some node "far away"
and only indirectly connected to such a sensor network.
These main types of sinks are illustrated by Figure
showing sources and sinks in direct communication.
Multi-hop networks
Because of limited distance the direct communication
between source and sink is not always possible.
In WSNs, to cover a lot of environment the data packets
taking multi hops from source to the sink.
To overcome such limited distances it better to use
relay stations, The data packets taking multi hops from
source to the sink as shown in Figure, Depending on
the particular application of having an intermediate
sensor node at the right place is high.
Three types of mobility
In the scenarios discussed above, all participants were
stationary. But one of the main virtues of wireless
communication is its ability to support mobile participants
In wireless sensor networks, mobility can appear in three
main forms:
1. mobility of the sensor nodes
2. mobility of the sink node(s)
3. mobility of a monitored event/object.
1. Node mobility
This kind of mobility occurs when at least part of the
sensor nodes is mobile.
A mobile node is an Internet-connected device whose
location and point of attachment to the Internet may
frequently be changed. This kind of node is often a
cellular telephone or handheld or laptop computer.
2. Sink mobility
The second kind of mobility refers to a situation in which
sink nodes are able to autonomously move in the
monitored region, with the purpose of collecting data
from the sensor network.
As the location of the sink is changing, sensor nodes are
enabled to send the data packages to the sink when sink
is nearby.
3. Event or Object mobility:
In tracking applications, the cause of the events or the
objects to be tracked can be mobile.
In such scenarios, it is (usually) important that the
observed event is covered by a sufficient number of
sensors at all time.
As the event source moves through the network, it is
accompanied by an area of activity within the network.
works under the event-driven data model. In this case,
modeling the occurrence and mobility of an event to be
monitored (e.g., a gas leak and movement of the
resulting gas plume) is useful for understanding the
resulting data traffic pattern in the WSN.
Similarly, when the WSN is used for target tracking,
modeling target movement is useful for estimating the
amount and pattern of data generated in the WSN
during target tracking.
OPTIMIZATION GOALS AND FIGURES OF MERIT
For all WSN scenarios and application types have to face
the challenges such as
How to optimize a network and How to compare these
solutions?
How to decide which approach is better?
How to turn relatively inaccurate optimization goals into
measurable figures of merit?
For all the above questions the general answer is obtained
from
Energy efficiency
Scalability
Robustness
Gateway Concept
SCALABILITY
The ability to maintain performance characteristics
irrespective of the size of the network is referred to as
scalability.
With WSN potentially consisting of thousands of
nodes, scalability is an obviously essential requirement
The need for extreme scalability has direct
consequences for the protocol design.
Often, a penalty in performance or complexity has to
be paid for small networks .
Architectures and protocols should implement
appropriate scalability support rather than trying to be
as scalable as possible.
Applications with a few dozen nodes might admit more-
efficient solutions than applications with thousands of
nodes.
Robustness
Wireless sensor networks should also exhibit an
appropriate robustness.
They should not fail just because a limited number of
nodes run out of energy, or because their environment
changes and severs existing radio links between two
nodes.
If possible, these failures have to be compensated by
finding other routes.
GATEWAY CONCEPTS
• Need for gateways
The integration of the WSN with Internet is required to
share data over the web. Among many solutions, the
simplest gateway based approach does the conversion of
protocol stacks and logical address formats used in both
networks.
The phenomenon sensed in the sensor network needs to
be accessed by a remote user. The communication may be
from WSN to remote user or remote user to WSN.
That is, whenever there is an alert message indicating the
detection of abnormality, the network transmits the
message to the user, while a query can be sent by the
remote user to obtain the status of the application
In both scenarios, a link is required that interconnects
remote user with the network. Gateway does this task.
Figure 1.16 shows this networking scenario,
The WSN first of all has to be able to exchange data
with such a mobile device or with some sort of gateway,
which provides the physical connection to the Internet.
The gateway node could be fixed or mobile with an
ability to connect sensor networks to the outer existing
communication infrastructure, such as Internet, cellular
and satellite networks. Similarly the memory capacity is
also more.
A wireless sensor network with gateway node, enabling
access to remote client via the internet