Embed Size (px)
Citation preview
1
The Architecture and The Architecture and Protocol Design for Protocol Design for
Underwater NetworkUnderwater Network
Presented by JamesPresented by James
2
Original PapersOriginal Papers
• Mandar Chitre, Lee Freitag, Ethem Sozer, Shiraz Shahabudeen, Milica Stojanovic, John Potter, "An Architecture for Underwater Networks", OCEANS'06 IEEE ASIA PACIFIC
• S. Shahabudeen and M. Chitre, "Design of networking protocols for shallow water peer-to-peer acoustic networks," in Proceedings of IEEE Oceans'05 Europe, Brest, France, 2005.
3
Presentation OutlinePresentation Outline
• Underwater Network Architecture
• Design of Networking Protocols
• Discussions
4
Underwater Network ArchitectUnderwater Network Architecture (UNA)ure (UNA)
5
OverviewOverview• Guidelines:
– Underwater networking;
– Easy integration;
– Flexible;
– Simple.
6
Layered ModelLayered Model
LogicallyLogically
7
AddressingAddressing
• Unique
• Network ID + Node ID
• Broadcast Address: FFFF
• No DHCP
8
Transport LayerTransport Layer• Services:
– Connection Oriented– Datagram
• Messages:– Open REQ– Close REQ– Write REQ– Connection Established NTF– Connection Lost NTF– Incoming Data NTF
9
Network LayerNetwork Layer• Services:
– Routing– Reliability (optional)
• Messages:– Send Packet REQ– Incoming Packet NTF– Get Route REQ– No Route NTF
10
Data Link LayerData Link Layer• Services:
– Single hop data transmission– Error detection– MAC (for shared media)
• Messages:– Send Packet REQ– Incoming Packet NTF
11
Physical LayerPhysical Layer• Services:
– Framing– Modulation– Error correction– Parameter negotiation– Carrier sensing
• Messages:– Send Packet REQ– Incoming Packet NTF– Recommend Parameters REQ
12
Extension FrameworkExtension Framework
• Cross layer optimization
• Exists across all layers
• Services:– Check capabilities– Generic data query
13
UNA Framework APIUNA Framework API• An abstract of hardware and OS• Follows standard C language• Supports message queue• Services:
– Layer registration– Message queue– Timer
14
Quick SummaryQuick Summary
• A common framework
• A layered architecture
• Some extended features
15
Presentation OutlinePresentation Outline
• Underwater Network Architecture
• Design of Networking Protocols
• Discussions
16
Design of Networking ProtocolDesign of Networking Protocolss
• Goals– Present some results– Looking for proper protocols
• Target layers– Data link layer– Physical layer
17
ProtocolsProtocols• MAC0
– ALOHA based half duplex protocol• MAC1
– ALOHA based half duplex protocol with ACKs and retries
• MAC2– MACA based half duplex protocol using RTS/
CTS handshaking
18
Simulation ScenariosSimulation Scenarios
• 4~25 Nodes:
• Randomly distributed
• Random traffic (Poisson Arrival)
19
/
/
/
/
AverageSent SimulationTimeOfferedLoad
BitRate PacketLength
AverageReceived SimulationTimeThroughput
BitRate PacketLength
• Orthogonal channel– Bandwidth divided channel
• Non-Orthogonal Channel– Shared channel
20
Simulation 1Simulation 1• Throughput v/s Offered load for various
packet sizes
– Bit rate: 2400bps– Constant packet length
21
22
23
24
Simulation 2Simulation 2• For fixed offered load, compare the throughpu
t for various bit rate rates and packet lengths
25
Simulation 3Simulation 3• For fixed offered load, study throughput
variation with respect to number of nodes– Packet size: 4000 bits– Bit rate: 2400 bps
26
Simulation 4Simulation 4• For fixed offered load, study the throughput with resp
ect to the node separation– Packet size: 4000 bits– Bit rate: 2400 bps
27
Conclusions Conclusions • Non-orthogonal schemes are good
candidates– Lower system complexity– Could conserve power – Good performance
28
Presentation OutlinePresentation Outline
• Underwater Network Architecture
• Design of Networking Protocols
• Discussions
29
DiscussionsDiscussions
30
Is Five-layered Model Is Five-layered Model Suitable?Suitable?
• Redundancy:– Fragmentation
• Is performed through out transport layer, network layer, and datalink layer!
– Checksum• Is calculated in MAC layer (32-bit CRC), IP layer and transp
ort layer (16 bits). Can we just combine the later two together?
– Address• Can we use one address instead of assigning every layer a
n address?
31
Thanks!Thanks!
Questions?Comments?
