The document discusses various wireless network access methods, particularly focusing on Mobile IP, which enables mobile nodes to maintain their IP addresses while switching networks. It outlines the components involved, such as home agents and foreign agents, the process of tunneling, encapsulation, and the challenges including security issues and quality of service. Additionally, it covers the session initiation protocol concerning mobile communications and highlights the integration of Mobile IP with IPv6 to enhance efficiency and security.

1. 2
UNIT I
MULTIPLE RADIO ACCESS

2. UNIT I MULTIPLE RADIO ACCESS
 Medium Access Alternatives: Fixed-Assignment for Voice Oriented
Networks Random
 Access for Data Oriented Networks , Handoff and Roaming Support,
Security and
 Privacy
3

3. Fixed-Assignment for Voice
Oriented Networks Random
 FDMA
 TDMA
 CDMA
 Comparation of FDMA,TDMA and CDMA
 Performance of fixed assignment access methods
4

4. Introduction
 Access methods commonly used in wireless networks.
 Access methods from part of layer 2 of OSI protocol and layer 3 of
IEEE 802 LANs
5

5. UNIT II
MOBILE NETWORK LAYER
6

6. Mobile Network Layer
 Introduction
 Mobile IP: IP Packet delivery, Agent discovery
 Tunneling and Encapsulation
 IPV6 - Network layer in the internet
 Mobile IP session initiation protocol (SIP)
 Mobile ad-hoc network (MANET)
 Routing Methods
 Destination Sequence distance vector (DSDV)
 Dynamic source routing (DSR)
7

7. Motivation for Mobile IP
 Routing
 Based on IP destination address, network prefix (e.g. 129.13.42)
determines physical subnet
 Change of physical subnet implies change of IP address to have
a topological correct address (standard IP) or needs special
entries in the routing tables
 Specific routes to end-systems?
 Change of all routing table entries to forward packets to the right
destination
 Does not scale with the number of mobile hosts and frequent
changes in the location, security problems
 Changing the IP-address?
 Adjust the host IP address depending on the current location
 Almost impossible to find a mobile system, DNS updates take to
long time
 TCP connections break, security problems
8

8. Requirementsfor Mobile IPv4
 Transparency
 mobile end-systems keep their IP address
 continuation of communication after interruption of link possible
 point of connection to the fixed network can be changed
 Compatibility
 support of the same layer 2 protocols as IP
 no changes to current end-systems and routers required
 mobile end-systems can communicate with fixed systems
 Security
 authentication of all registration messages
 Efficiency and scalability
 only little additional messages to the mobile system required
(connection typically via a low bandwidth radio link)
 world-wide support of a large number of mobile systems in the whole
Internet
9

9. Terminology
 Mobile Node (MN)
 system (node) that can change the point of connection
to the network without changing its IP address
 Home Agent (HA)
 system in the home network of the MN, typically a router
 registers the location of the MN, tunnels IP datagrams to the COA
 Foreign Agent (FA)
 system in the current foreign network of the MN, typically a router
 forwards the tunneled datagrams to the MN, typically also the default
router for the MN
 Care-of Address (COA)
 address of the current tunnel end-point for the MN (at FA or MN)
 actual location of the MN from an IP point of view
 can be chosen, e.g., via DHCP
 Correspondent Node (CN)
 communication partner
10

10. Example network
mobile end-system
Internet
router
router
router
end-system
FA
HA
MN
home network
foreign
network
(physical home network
for the MN)
(current physical network
for the MN)
CN
11

11. Data transfer to the
mobile system
Internet
sender
FA
HA
MN
home network
foreign
network
receiver
1
2
3
1. Sender sends to the IP address of MN,
HA intercepts packet (proxy ARP)
2. HA tunnels packet to COA, here FA,
by encapsulation
3. FA forwards the packet
to the MN
CN
12

12. Data transfer from the
mobile system
Internet
receiver
FA
HA
MN
home network
foreign
network
sender
1
1. Sender sends to the IP address
of the receiver as usual,
FA works as default router
CN
13

13. Overview
CN
router
HA
router
FA
Internet
router
1.
2.
3.
home
network
MN
foreign
network
4.
CN
router
HA
router
FA
Internet
router
home
network
MN
foreign
network
COA
14

14. Network integration
 Agent Advertisement
 HA and FA periodically send advertisement messages into their physical
subnets
 MN listens to these messages and detects, if it is in the home or a foreign
network (standard case for home network)
 MN reads a COA from the FA advertisement messages
 Registration (always limited lifetime!)
 MN signals COA to the HA via the FA, HA acknowledges via FA to MN
 these actions have to be secured by authentication
 Advertisement
 HA advertises the IP address of the MN (as for fixed systems), i.e.
standard routing information
 routers adjust their entries, these are stable for a longer time (HA
responsible for a MN over a longer period of time)
 packets to the MN are sent to the HA,
 independent of changes in COA/FA
15

15. type = 16
length = 6 + 4 * #COAs
R: registration required
B: busy, no more registrations
H: home agent
F: foreign agent
M: minimal encapsulation
G: GRE encapsulation
r: =0, ignored (former Van Jacobson compression)
T: FA supports reverse tunneling
reserved: =0, ignored
Agent advertisement
preference level 1
router address 1
#addresses
type
addr. size lifetime
checksum
COA 1
COA 2
type = 16 sequence numberlength
0 7 8 15 16 312423
code
preference level 2
router address 2
. . .
registration lifetime
. . .
R B H F MG r reservedT
16

16. Registration
t
MN HA
t
MN FA HA
17

17. Mobile IP registration request
home agent
home address
type = 1 lifetime
0 7 8 15 16 312423
T x
identification
COA
extensions . . .
S B DMGr
S: simultaneous bindings
B: broadcast datagrams
D: decapsulation by MN
M mininal encapsulation
G: GRE encapsulation
r: =0, ignored
T: reverse tunneling requested
x: =0, ignored
18

18. Mobile IP registration reply
home agent
home address
type = 3 lifetime
0 7 8 15 16 31
code
identification
extensions . . .Example codes:
registration successful
0 registration accepted
1 registration accepted, but simultaneous mobility bindings unsupported
registration denied by FA
65 administratively prohibited
66 insufficient resources
67 mobile node failed authentication
68 home agent failed authentication
69 requested Lifetime too long
registration denied by HA
129 administratively prohibited
131 mobile node failed authentication
133 registration Identification mismatch
135 too many simultaneous mobility bindings
19

19. Tunneling
• This method of sending IP datagram's is called ‘tunneling’
• End-points of tunnel are called encapsulator & decapsulator
• Flow of packets :
src  encapsulator  decapsulator  destn
• Mobile node is attached to a foreign network
• Need to deliver packets addressed to mobile node, to an agent that can deliver
datagram's to mobile node at current location
• The datagram's are sent over the tunnel
• Multiple src - dest pairs can share the same tunnel
20

20. Tunneling & Encapsulation
• Communication between an IP node and a Mobile Node
• Delivery of data to mobile node’s COA via permanent home address
• Tunnelling is achieved by encapsulation
Home Agent
IP Host
Foreign Agent
Mobile Node
1
2
3
4
(triangular
routing)
IP tunnel
21

21. Encapsulation
original IP header original data
new datanew IP header
outer header inner header original data
Encapsulation of one packet into another as payload
- e.g. IPv6 in IPv4 , Multicast in Unicast
- e.g. IP-in-IP-encapsulation
IP-in-IP-encapsulation
- Tunnel between HA and COA
22

22. Encapsulation I
 Encapsulation of one packet into another as payload
 e.g. IPv6 in IPv4 (6Bone), Multicast in Unicast (Mbone)
 here: e.g. IP-in-IP-encapsulation, minimal encapsulation or GRE
(Generic Record Encapsulation)
 IP-in-IP-encapsulation (mandatory, RFC 2003)
 tunnel between HA and COA
Care-of address COA
IP address of HA
TTL
IP identification
IP-in-IP IP checksum
flags fragment offset
lengthDS (TOS)ver. IHL
IP address of MN
IP address of CN
TTL
IP identification
lay. 4 prot. IP checksum
flags fragment offset
lengthDS (TOS)ver. IHL
TCP/UDP/ ... payload
23

23. Encapsulation II
 Minimal encapsulation (optional)
 avoids repetition of identical fields
 e.g. TTL, IHL, version, DS (RFC 2474, old: TOS)
 only applicable for non fragmented packets, no space left for fragment
identification
care-of address COA
IP address of HA
TTL
IP identification
min. encap. IP checksum
flags fragment offset
lengthDS (TOS)ver. IHL
IP address of MN
original sender IP address (if S=1)
Slay. 4 protoc. IP checksum
TCP/UDP/ ... payload
reserved
24

24. Generic Routing
Encapsulation original
header
original data
new datanew header
outer header
GRE
header
original data
original
header
Care-of address COA
IP address of HA
TTL
IP identification
GRE IP checksum
flags fragment offset
lengthDS (TOS)ver. IHL
IP address of MN
IP address of CN
TTL
IP identification
lay. 4 prot. IP checksum
flags fragment offset
lengthDS (TOS)ver. IHL
TCP/UDP/ ... payload
routing (optional)
sequence number (optional)
key (optional)
offset (optional)checksum (optional)
protocolrec. rsv. ver.CRK S s
RFC 1701
RFC 2784 (updated by 2890)
reserved1 (=0)checksum (optional)
protocolreserved0 ver.C
25

25. Optimization of packet forwarding
 Problem: Triangular Routing
 sender sends all packets via HA to MN
 higher latency and network load
 “Solutions”
 sender learns the current location of MN
 direct tunneling to this location
 HA informs a sender about the location of MN
 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 now forwards
remaining packets to new FA
 this information also enables the old FA to release resources for the MN
26

26. Change of foreign agent
CN HA FAold FAnew MN
MN changes
location
t
Data Data Data
Update
ACK
Data Data
RegistrationUpdate
ACK
Data
Data Data
Warning
Request
Update
ACK
Data
Data
27

27. Reverse tunneling
Internet
receiver
FA
HA
MN
home network
foreign
network
sender
3
2
1
1. MN sends to FA
2. FA tunnels packets to HA
by encapsulation
3. HA forwards the packet to the
receiver (standard case)
CN
28

28. Mobile IP with reverse tunneling
 Router accept often only “topological correct“ addresses (firewall!)
 a packet from the MN encapsulated by the FA is now topological
correct
 furthermore multicast and TTL problems solved (TTL in the home network
correct, but MN is to far away from the receiver)
 Reverse tunneling does not solve
 problems with firewalls, the reverse tunnel can be abused to circumvent
security mechanisms (tunnel hijacking)
 optimization of data paths, i.e. packets will be forwarded through the
tunnel via the HA to a sender (double triangular routing)
 The standard is backwards compatible
 the extensions can be implemented easily and cooperate with current
implementations without these extensions
 Agent Advertisements can carry requests for reverse tunneling
29

29. Mobile IP and IPv6
 Mobile IP was developed for IPv4, but IPv6 simplifies the protocols
 security is integrated and not an add-on, authentication of registration is
included
 COA can be assigned via auto-configuration (DHCPv6 is one
candidate), every node has address auto-configuration
 no need for a separate FA, all routers perform router advertisement
which can be used instead of the special agent advertisement;
addresses are always co-located
 MN can signal a sender directly the COA, sending via HA not needed in
this case (automatic path optimization)
 „soft“ hand-over, i.e. without packet loss, between two subnets is
supported
 MN sends the new COA to its old router
 the old router encapsulates all incoming packets for the MN and
forwards them to the new COA
 authentication is always granted
30

30. Problems with mobile IP
 Security
 authentication with FA problematic, for the FA typically belongs to another
organization
 no protocol for key management and key distribution has been standardized in
the Internet
 patent and export restrictions
 Firewalls
 typically mobile IP cannot be used together with firewalls, special set-ups are
needed (such as reverse tunneling)
 QoS
 many new reservations in case of RSVP
 tunneling makes it hard to give a flow of packets a special treatment needed for
the QoS
 Security, firewalls, QoS etc. are topics of research and discussions
31

31. Security in Mobile IP
 Security requirements (Security Architecture for the Internet Protocol, RFC 4301, was:
1825, 2401)
 Integrity
any changes to data between sender and receiver can be detected by the
receiver
 Authentication
sender address is really the address of the sender and all data received is really
data sent by this sender
 Confidentiality
only sender and receiver can read the data
 Non-Repudiation
sender cannot deny sending of data
 Traffic Analysis
creation of traffic and user profiles should not be possible
 Replay Protection
receivers can detect replay of messages
32

32. not encrypted encrypted
IP security
architecture I
 Two or more partners have to negotiate security mechanisms to setup a security association
 typically, all partners choose the same parameters and mechanisms
 Two headers have been defined for securing IP packets:
 Authentication-Header
 guarantees integrity and authenticity of IP packets
 if asymmetric encryption schemes are used, non-repudiation can also be guaranteed
 Encapsulation Security Payload
 protects confidentiality between communication partners
Authentification-HeaderIP-Header UDP/TCP-Paketauthentication headerIP header UDP/TCP data
ESP headerIP header encrypted data
33

33.  Mobile Security Association for registrations
 parameters for the mobile host (MH), home agent (HA), and
foreign agent (FA)
 Extensions of the IP security architecture
 extended authentication of registration
 prevention of replays of registrations
 time stamps: 32 bit time stamps + 32 bit random number
 nonces: 32 bit random number (MH) + 32 bit random
number (HA)
registration reply
registration request
registration request
IP security architecture II
MH FA HA
registration reply
MH-HA authentication
MH-FA authentication FA-HA authentication
34

34. Key distribution
 Home agent distributes session keys
 foreign agent has a security association with the home agent
 mobile host registers a new binding at the home agent
 home agent answers with a new session key for foreign agent and
mobile node
FA MH
HA
response:
EHA-FA {session key}
EHA-MH {session key}
35

35. IP Micro-mobility support
 Micro-mobility support:
 Efficient local handover inside a foreign domain
without involving a home agent
 Reduces control traffic on backbone
 Especially needed in case of route optimization
 Example approaches (research, not products):
 Cellular IP
 HAWAII
 Hierarchical Mobile IP (HMIP)
 Important criteria:
Security Efficiency, Scalability, Transparency, Manageability
36

36. Mobile IP session
initiation protocol
 SIP is the core protocol for initiating, managing and terminating
sessions in the Internet
 These sessions may be text, voice, video or a combination of these
 SIP sessions involve one or more participants and can use unicast or
multicast communication.
 SIP entities
User Agent
User Agent Client
User Agent Server
Proxy Server
Redirect server
37

37. SIP Message Types
Requests – sent from client to server
 INVITE
 ACK
 BYE
 CANCEL
 OPTIONS
 REGISTER
 INFO
Responses – sent from server to the client
 Success
 Redirection
 Forwarding
 Request failure
 Server failure
 Global failure
38

38. SIP Role
SIP Proxy
MG MG
RTP
MGCMGC
SIP
PSTN PST
N
MEGACO/
MGCP
MEGACO/
MGCP
IP Network
39

39. SIP Headers
General-headers Entity-headers Request-headers Response-headers
Call-ID Content-Encoding Accept Allow
Contact Content-Length Accept-Encoding Proxy-
Authentication
Cseq Content-Type Accept-Language Unsupported
Date Authorization Warning
Encryption Hide
Expires Max-Forwards
From Organization
Record-Route Priority
To Proxy-Authentication
Via Proxy-Require
Require
Response-Key
Subject
User-Agent
40

40. SIP Session Establishment and
Call Termination
41

41. SIP Call Redirection 42

42. SIP Protocol Use 43

43. Hierarchical Mobile
IPv6
 Operation:
 Network contains mobility anchor
point (MAP)
 mapping of regional COA
(RCOA) to link COA (LCOA)
 Upon handover, MN informs
MAP only
 gets new LCOA, keeps RCOA
 HA is only contacted if MAP
changes
 Security provisions:
 no HMIP-specific
security provisions
 binding updates should be
authenticated
MAP
Internet
AR
MN
AR
MN
HA
binding
update
RCOA
LCOAoldLCOAnew

44. Hierarchical Mobile IP:
Security
 Advantages:
 Local COAs can be hidden,
which provides at least some location privacy
 Direct routing between CNs sharing the same link is possible (but might
be dangerous)
 Potential problems:
 Decentralized security-critical functionality
(handover processing) in mobility anchor points
 MNs can (must!) directly influence routing entries via binding updates
(authentication necessary)
45

45. Hierarchical Mobile IP:
Other issues
 Advantages:
 Handover requires minimum number
of overall changes to routing tables
 Integration with firewalls / private address support possible
 Potential problems:
 Not transparent to MNs
 Handover efficiency in wireless mobile scenarios:
 Complex MN operations
 All routing reconfiguration messages
sent over wireless link
46

46. MOBILE AD HOC
NETWORKS (MANET) Standard Mobile IP needs an infrastructure
 Home Agent/Foreign Agent in the fixed network
 DNS, routing etc. are not designed for mobility
 Sometimes there is no infrastructure!
 remote areas, ad-hoc meetings, disaster areas
 cost can also be an argument against an infrastructure!
 Main topic: routing
 no default router available
 every node should be able to forward
A B C
47

47. A plethora of ad hoc routing protocols
 Flat
 proactive
 FSLS – Fuzzy Sighted Link State
 FSR – Fisheye State Routing
 OLSR – Optimized Link State Routing Protocol (RFC 3626)
 TBRPF – Topology Broadcast Based on Reverse Path Forwarding
 reactive
 AODV – Ad hoc On demand Distance Vector (RFC 3561)
 DSR – Dynamic Source Routing (RFC 4728)
 DYMO – Dynamic MANET On-demand
 Hierarchical
 CGSR – Cluster head-Gateway Switch Routing
 HSR – Hierarchical State Routing
 LANMAR – Landmark Ad Hoc Routing
 ZRP – Zone Routing Protocol
 Geographic position assisted
 DREAM – Distance Routing Effect Algorithm for Mobility
 Geo Cast – Geographic Addressing and Routing
 GPSR – Greedy Perimeter Stateless Routing
 LAR – Location-Aided Routing
48

48. Solution: Wireless ad-
hoc networks
 Network without infrastructure
Use components of participants for
networking
 Examples
Single-hop: All partners max. one hop apart
 Bluetooth piconet, PDAs in a room,
gaming devices…
49

49. MANET: Mobile Ad-
hoc Networking
Fixed
Network
Mobile
Devices
Mobile
Router
Manet
Mobile IP,
DHCP
Router End system
50

50. Problem No. 1: Routing
 Highly dynamic network topology
 Device mobility plus varying channel quality
 Separation and merging of networks possible
 Asymmetric connections possible
good link
weak link
time = t1 time = t2
N1
N4
N2
N5
N3
N1
N4
N2
N5
N3
N6
N7
N6N7
51

51. Traditional routing algorithms
 Distance Vector
 periodic exchange of messages with all physical neighbors that contain information about who can be
reached at what distance
 selection of the shortest path if several paths available
 Link State
 periodic notification of all routers about the current state of all physical links
 router get a complete picture of the network
 Example
 ARPA packet radio network (1973), DV-Routing
 every 7.5s exchange of routing tables including link quality
 updating of tables also by reception of packets
 routing problems solved with limited flooding
52

52. Routing in ad-hoc networks
 THE big topic in many research projects
 Far more than 50 different proposals exist
 The most simplest one: Flooding!
 Reasons
 Classical approaches from fixed networks fail
 Very slow convergence, large overhead
 High dynamicity, low bandwidth, low computing power
 Metrics for routing
 Minimal
 Number of nodes, loss rate, delay, congestion, interference …
 Maximal
 Stability of the logical network, battery run-time, time of connectivity …
53

53. Problems of traditional routing
algorithms
 Dynamic of the topology
 frequent changes of connections, connection quality, participants
 Limited performance of mobile systems
 periodic updates of routing tables need energy without contributing to the transmission of
user data, sleep modes difficult to realize
 limited bandwidth of the system is reduced even more due to the exchange of routing
information
 links can be asymmetric, i.e., they can have a direction dependent transmission quality
54

54. DSDV (Destination Sequenced
Distance Vector, historical)
 Early work
on demand version: AODV
 Expansion of distance vector routing
 Sequence numbers for all routing updates
assures in-order execution of all updates
avoids loops and inconsistencies
 Decrease of update frequency
55

55. Dynamic source routing (DSR)
 Reactive routing protocol
 2 phases, operating both on demand:
Route discovery
 Used only when source S attempts to to send a packet to
destination D
 Based on flooding of Route Requests (RREQ)
Route maintenance
 makes S able to detect, while using a source route to D, if it can no
longer use its route (because a link along that route no longer works)
56

56. DSR: Route discovery (1)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
57

57. DSR: Route discovery (2)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
(S)
58

58. DSR: Route discovery (3)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
(S,A)
(S,E)
59

59. DSR: Route discovery (4)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
(S,E,G)
(S,B,C)
60

60. DSR: Route discovery (5)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
(S,E,G,J)
(S,A,F,H)
61

61. DSR: Route discovery (6)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
(S,A,F,H,K)
62

62. DSR: Route discovery (7)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
(S,A,F,H,K,P)
63

63. DSR: Route discovery (8)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
RREP(S,E,G,J,D)
64

64. DSR: Route Discovery (9)
 Route reply by reversing the route (as illustrated) works only if all the
links along the route are bidirectional
 If unidirectional links are allowed, then RREP may need a route
discovery from D to S
 Note: IEEE 802.11 assumes that links are bidirectional
65

65. DSR: Data delivery
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
DATA(S,E,G,J,D)
66

66. DSR: Route maintenance (1)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
DATA(S,E,G,J,D)
X
67

67. DSR: Route maintenance (2)
E G
M
H
R
F
A
B
C
I
DS
K
N
L
P
J
Q
X
RERR(G-J)
When receiving the Route Error message (RERR),
S removes the broken link from its cache.
It then tries another route stored in its cache; if none,
it initializes a new route discovery
68

68. DSR: Optimization of route
discovery: route caching
 Principle: each node caches a new route it learns by any means
 Examples
When node S finds route (S, E, G, J, D) to D, it
also learns route (S, E, G) to node G
In the same way, node E learns the route to D
Same phenomenon when transmitting route
replies
 Moreover, routes can be overheard by nodes in the neighbourhood
 However, route caching has its downside: stale caches can severely
hamper the performance of the network
69

69. DSR: Strengths
 Routes are set up and maintained only between nodes who need
to communicate
 Route caching can further reduce the effort of route discovery
 A single route discovery may provide several routes to the
destination
70

70. DSR: Weaknesses
 Route requests tend to flood the network and generally reach all
the nodes of the network
 Because of source routing, the packet header size grows with the
route lengh
 Risk of many collisions between route requests by neighboring
nodes  need for random delays before forwarding RREQ
 Similar problem for the RREP (Route Reply storm problem), in case
links are not bidirectional
Note: Location-aided routing may help reducing the number of useless
control messages
71

71. Ad Hoc On-Demand
Distance Vector Routing
(AODV)
 As it is based on source routing, DSR includes source routes in data
packet headers
 Large packet headers in DSR  risk of poor performance if the
number of hops is high
 AODV uses a route discovery mechanism similar to DSR, but it
maintains routing tables at the nodes
 AODV ages the routes and maintains a hop count
 AODV assumes that all links are bi-directional
72

72. Dynamic source routing I
 Split routing into discovering a path and maintaining a path
 Discover a path
only if a path for sending packets to a certain
destination is needed and no path is currently
available
 Maintaining a path
only while the path is in use one has to make
sure that it can be used continuously
73

73. Dynamic source routing II
 Path discovery
 broadcast a packet with destination address and unique ID
 if a station receives a broadcast packet
 if the station is the receiver (i.e., has the correct destination address) then
return the packet to the sender (path was collected in the packet)
 if the packet has already been received earlier (identified via ID) then
discard the packet
 otherwise, append own address and broadcast packet
 sender receives packet with the current path (address list)
 Optimizations
 limit broadcasting if maximum diameter of the network is known
 caching of address lists (i.e. paths) with help of passing packets
74

74. A plethora of ad hoc routing
protocols
 Flat
 proactive
 FSLS – Fuzzy Sighted Link State
 FSR – Fisheye State Routing
 OLSR – Optimized Link State Routing Protocol (RFC 3626)
 TBRPF – Topology Broadcast Based on Reverse Path Forwarding
 reactive
 AODV – Ad hoc On demand Distance Vector (RFC 3561)
 DSR – Dynamic Source Routing (RFC 4728)
 DYMO – Dynamic MANET On-demand
 Hierarchical
 CGSR – Clusterhead-Gateway Switch Routing
 HSR – Hierarchical State Routing
 LANMAR – Landmark Ad Hoc Routing
 ZRP – Zone Routing Protocol
 Geographic position assisted
 DREAM – Distance Routing Effect Algorithm for Mobility
 GeoCast – Geographic Addressing and Routing
 GPSR – Greedy Perimeter Stateless Routing
 LAR – Location-Aided Routing
Two promising
candidates:
OLSRv2 and
DYMO
75

75. Further difficulties and research
areas
 Auto-Configuration
 Assignment of addresses, function, profile, program, …
 Service discovery
 Discovery of services and service providers
 Multicast
 Transmission to a selected group of receivers
 Quality-of-Service
 Maintenance of a certain transmission quality
 Power control
 Minimizing interference, energy conservation mechanisms
 Security
 Data integrity, protection from attacks (e.g. Denial of Service)
 Scalability
 10 nodes? 100 nodes? 1000 nodes? 10000 nodes?
 Integration with fixed networks
76

76. Clustering of ad-hoc networks
Internet
Super cluster
Cluster
Base station
Cluster head
77

77. UNIT 5
WIRELESS MANS AND PANS
78

78. Wireless MANs – Physical and MAC layer details, Wireless PANs – Architecture of
Bluetooth Systems, Physical and MAC layer details, Standards.
Dharma Prakash Agrawal & Qing-An Zeng, “Introduction to Wireless and Mobile
Systems”, Thomson India Edition , 2nd Ed., 2007. Pages 439-465
79

79. WMANs using WiMAX
 IEEE 802.16 MAC Protocol
 Point to multi-point broadband wireless access
 0-3.5 MHz
 Supports packet based protocols
 Fundamental Tasks
 Allocating Bandwidth
 Transporting data
 Privacy sub layer - provides authentication of network access
 Avoids theft of service
 Provides key exchange
 Encryption for data Privacy
80

80.  IEEE 802.16a – WiMAX
 Supports lower frequency ranges
 Provides a MAC to support ARQ(Automatic Repeat Request)
81

81. MAC Layer Details
 Service- Specific Convergence Sub layers
 Common Part Sub layer
Generic Header for MAC PDU (Protocol Data Unit)
82
HT=0 (1) EC (1) Type (6) Rsv(1) CI(1) EKS(2
)
Rsv(1) LEN
msb
(3)
LEN lsb (8) CID msb (8)
CID lsb (8) HCS (8)

82. Physical Layer Details of WMANs
 10-66GHz band
 Physical layer is driven by line of sight (LOS)
 WMAN-SC (Single Carrier Modulation)
 Point-Point communication is enabled through TDM
 UL direction is by TDMA
 Allows both TDD and FDD
 2-11GHz band
 Physical layer is driven by non line of sight (NLOS)
 Consideration of Antenna design
83

83.  TC (Transmission Convergence) Sublayer
 Resides between PHY and MAC layer
 Transformation of variable length MAC PDUs into fixed length FEC block
TC sublayer PDU(Protocol Data Unit)
84
P MAC PDU that has started in
previous TC PDU
First MAC PDU,
then this TC PDU
Second MAC
PDU, then this
TC PDU

84. Wireless Mesh Network 85

85.  Radio nodes organized in a mesh topology
 Consists of mesh clients, mesh routers and
gateways
 Coverage area is called mesh cloud
 Wireless mesh network can self form and self
heal
 Used in U.S. military force
 One lap top per child program
 Dynamic routing is enabled
86

86. RICOCHET (RIK-ə-shay)
 Developed by Metricom Incorporated
 Link to the internet without phone lines
 Operates in license-free 902-928 MHz band
 Microcellular Data Network(MCDN)
 Based on frequency hopping and spread
spectrum technology
87

87. WPANs
 Bluetooth – IEEE 802.15.x
 IEEE 802.15.1 (medium rate)
 IEEE 802.15.3 (high rate)
 IEEE 802.15.4 (low rate)
 IEEE 802.15 working group is formed by four task group
 The IEEE 802.15 WPAN/Bluetooth TG1
 The IEEE 802.15 Coexistence TG2
 The IEEE 802.15 WPAN/High Rate TG3
 The IEEE 802.15 WPAN/Low Rate TG4
88