Professional Documents
Culture Documents
Unit 2 Whole
Unit 2 Whole
Unit 2 Whole
If two nodes are out of reach, they cannot hear each other. This
gives rise to the well-known hidden-terminal/exposed-terminal
problems. The hidden-terminal problem occurs specifically
for the class of Carrier Sense MultipleAccess (CSMA) protocols,
where a node senses the medium before starting to transmit a
packet.
If the medium is found to be busy, the node defers its packet to
avoid a collision and a subsequent
retransmission. Consider the example in Figure 5.1. Here, we have
three nodes A, B, and C that
are arranged such that A and B are in mutual range, B and C are in
mutual range, but A and C
cannot hear each other. Assume that A starts to transmit a packet to
B and some time later node C
also decides to start a packet transmission. A carrier-sensing
operation by C shows an idle medium
sinceC cannot hear A’s signals. When C starts its packet, the signals
collide at B and both packets
are useless. Using simple CSMA in a hidden-terminal scenario thus
leads to needless collisions.
In the exposed-terminal scenario
MACA EXAMPLES:
1. MACA avoids the problem of hidden terminals
A and C want to send to B
A sends RTS first
C waits after receiving CTS from B
Collisions collisions incur useless receive costs at the destination node, useless transmit costs at the
source node, and the prospect to expend further energy upon packet retransmission. Hence,
collisions should be avoided, either by design (fixed assignment/TDMA or demand assignment
protocols)
Overhearing Unicast frames have one source and one destination node.and it send to another node.
Idle listening A node being in idle state is ready to receive a packet but is not currently
receivingAnything
Over emmiting:
Node send data when receiving node not ready to accept data.
.
Bluetooth
Bluetooth specification details the entire protocol stack. Bluetooth employs
Radio Frequency (RF) for communication. It makes use of frequency
modulation to generate radio waves in the ISM band.
When more than two Bluetooth devices communicate with one another, this is
called a PICONET. A Piconet can contain up to seven slaves clustered around a
single master. The device that initializes establishment of the Piconet becomes
the master.
The master is responsible for transmission control by dividing the network into a
series of time slots amongst the network members, as a part of time division
multiplexing scheme which is shown below.
he features of Piconets are as follows −
Within a Piconet, the timing of various devices and the frequency hopping
sequence of individual devices is determined by the clock and unique 48-
bit address of master.
There is no direct connection between the slaves and all the connections are
essentially master-to-slave or slave-to-master.
Slaves are allowed to transmit once these have been polled by the master.
Problem in wsn:
◾ The reason we need network protocol such as LEACH is due to the fact that a node in the
network is no longer useful when its battery dies
◾ This protocol allows us to choose out the lifespan of the nodes, allowing it to do only the
minimum work it needs to transmit data
The Cluster-Head
◾ The LEACH Network is made up of nodes, some of which are called cluster-heads
The job of the cluster-head is to collect data from their surrounding nodes and pass
it on to the base station
◾ The LEACH network has two phases: the set-up phase and the steady-state
▪
▪ If n < T(n), then that node becomes a cluster-head
The Steady-State
Advantages:
3)as compared with other clustering protocol Leach life time is more
DisAdvantages:
simple and does not rely on costly network topology maintenance and complex
route discovery algorithms. Flooding uses a reactive approach whereby each
node receiving a data or control packet sends the packet to all its neighbors.
After transmission, a packet follows all possible paths.
Features
TCP is reliable protocol. That is, the receiver always sends either positive or
negative acknowledgement about the data packet to the sender, so that the
sender always has bright clue about whether the data packet is reached the
destination or it needs to resend it.
TCP ensures that the data reaches intended destination in the same order it
was sent.
Upon reception of this segment (which is often called a SYN segment), the server host replies
with a segment containing :
This segment is often called a SYN+ACK segment. The acknowledgment confirms to the client
that the server has correctly received the SYN segment. The sequence number of
the SYN+ACK segment is used by the server host to verify that the client has received the
segment. Upon reception of the SYN+ACKsegment, the client host replies with a segment
containing :
At this point, the TCP connection is open and both the client and the server are allowed to
send TCP segments containing data. This is illustrated in the figure below.
Establishment of a TCP connection
UDP is stateless.
UDP Operation:
The different operations of UDP are as follows:
Connectionless Services:
UDP provides a connectionless service. This means that each user datagram sent
by UDP is an independent datagram. There is no relationship between the
different user datagrams even if they are coming from the same source process
and going to the same destination program. The user datagrams are not
numbered. Also, there is no connection establishment and no connection
termination. This means that each user datagram can travel on a different path.
UDP is a very simple, unreliable transport protocol. There is no flow control and
hence no window mechanism. The receiver may overflow with incoming
messages. There is no error control mechanism in UDP except for the checksum.
The lack of flow control and error control means that the process using UDP
should provide these mechanisms.
To send a message from one process to another, the UDP protocol encapsulates
and decapsulates messages in an IP datagram.
Queuing:
In UDP, queues are associated with ports. Consider the following figure
At the client site:
When a process starts, it requests a port number from the operating system.
Some implementations create both an incoming and an outgoing queue
associated with each process. Other implementations create only an incoming
queue associated with each process. The queues opened by the client are, in
most cases, identified by ephemeral port numbers. The queues function as long
as the process is running. When the process terminates, the queues are
destroyed.
The client process can send messages to the outgoing queue by using the source
port number specified in the request. UDP removes the messages one by one
and, after adding the UDP header, delivers them to IP. An outgoing queue can
overflow. If this happens, the operating system can ask the client process to wait
before sending any more messages.
At the server site, the mechanism of creating queues is different. In its simplest
form, a server asks for incoming and outgoing queues, using its well-known port,
when it starts running. The queues remain open as long as the server is
running.
Mobile ip
Mobile IP is a communication protocol (created by extending Internet Protocol, IP) that allows the users to
move from one network to another with the same IP address. It ensures that the communication will
continue without the user’s sessions or connections being dropped.
Terminologies:
Mobile Node (MN)
is the hand-held communication device that the user carries e.g. Cell phone.
Home Network is a network to which the mobile node originally belongs as per its assigned IP address
(home address).
Home Agent (HA)
is a router in-home network to which the mobile node was originally connected
Home Address
is the permanent IP address assigned to the mobile node (within its home network).
Foreign Network
is the current network to which the mobile node is visiting (away from its home network).
Foreign Agent (FA)
is a router in a foreign network to which the mobile node is currently connected. The packets from the home
agent are sent to the foreign agent which delivers them to the mobile node.
Correspondent Node (CN)
is a device on the internet communicating to the mobile node.
Care-of Address (COA)
is the temporary address used by a mobile node while it is moving away from its home network.
Foreign agent COA,
the COA could be located at the FA, i.e., the COA is an IP address of the FA. The FA is the tunnel end-
point and forwards packets to the MN. Many MN using the FA can share this COA as a common COA.
Co-located COA,
the COA is co-located if the MN temporarily acquired an additional IP address which acts as COA. This
address is now topologically correct, and the tunnel endpoint is at the MN. Co-located addresses can be
acquired using services such as DHCP.
Network integration
Agent Advertisement
HA and FA periodically send advertisement messages into their
subnets
MN reads a COA from the FA advertisement messages
Registration (always limited lifetime!)
MN signals COA to the HA via the FA, HA acknowledges
Messeges need to be secured by authentication
Advertisement
HA advertises the MN IP address (as for fixed systems)
routers adjust their entries, (HA responsible for a long time)
All packets to MN are sent to HA
Encapsulation
Optimization of packet forwarding
Triangular Routing
sender sends all packets via HA to MN
Triangular routes longer, higher latency and network load
“Solutions”
HA informs a sender about the location of MN
sender learns current location of MN
direct tunneling to this location
big security problems!
Change of FA
packets on-the-fly during the change can be lost
new FA informs old FA to avoid packet loss
old FA forwards remaining packets to new FA
Update also enables old FA to release resources for MN
Mobile IP was developed for IPv4, but IPv6 simplifies the protocols
security is integrated, not add-on, authentication of registration included
COA can be assigned via auto-configuration (DHCPv6 is one candidate)
every node has address autoconfiguration
no need for a separate FA, all routers perform router advertisement
MN can signal a sender directly the COA, without HA
„soft“ hand-over, i.e. without packet loss supported
MN sends the new COA to its old router
old router encapsulates all packets for MN, forwards them to new COA
authentication is always granted
Security
FA typically belongs to another organization
authentication with FA problematic
patent and export restrictions
Firewalls
Firewalls filter based on IP addresses
FA encapsulates packets from MN
Home firewalls rejects packet from MN (unless reverse tunneling)
MN can no longer send packets back to home network
QoS, etc..
Security, firewalls, QoS etc. are topics of current research and discussions!