Presentation Template - OLSR Interop

Various reporting features. ... (link layer notification, medium power, high mobility). 0%. 20%. 40% ... development of ad hoc networks, and OLSR in particular.
328KB taille 1 téléchargements 300 vues
OLSR Simulation and Implementation Christopher Dearlove [email protected]

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 1

Overview Requirements. Design Decisions. Software Organisation. Compliance, Limitations and Extensions. Simulation Example. Ground Sensor Network Demonstration. Additional Requirements.

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 2

OLSR Simulation and Implementation Requirements • A framework for a generic AHRP. • An implementation of OLSR within this framework. • To be usable to simulate AHRP, e.g. in OPNET. • To be usable to implement AHRP in real time on e.g. Linux platform. (Laptop or PDA using IEEE 802.11b WLAN.) • To include IPv4 and IPv6 options. • To be able to interwork with other implementations of OLSR. • To add some compliant proprietary extensions to OLSR. • To allow extension to modified versions of OLSR. • To support dynamic ©parameters. BAE SYSTEMS 2004. All rights reserved.

Advanced Technology Centre

Slide 3

Software Design Decisions Code to be written in standard C++. To use object oriented design. OLSR code to be independent of OPNET and Linux. OPNET and Linux specific “wrappers” for code. Separate compilation for IPv4 and IPv6. Various reporting features.

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 4

AHRP and OLSR Classes and Creation Ahrp packet_received() routing_failure() link_layer_notification() timeout()

Aodv

Classes in black exist Classes in red are hypothetical

Olsr packet_received() routing_failure() link_layer_notification() timeout()

«registration» «creation»

Ahrp_Factory

1

register_creation() create()

«creation» Secure_Olsr

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Wrapper

Slide 5

AHRP and OLSR Class Usage

Routing_Table add() replace() remove()

Packet_Handler

Olsr 1

1

1

1

allocate() send()

Ahrp Linux_Routing_Table add() replace() remove()

Linux_Packet_Handler 1 1

1

allocate() send()

1 1

Advanced Technology Centre

Linux_Wrapper

1

© BAE SYSTEMS 2004. All rights reserved.

Slide 6

OLSR Software (1) Initial implementation of OLSRv5, then converted to OLSRv7, then finally to OLSRv11 (RFC 3626). Some observations from use provided to OLSR authors. Designed to be fully compliant with OLSR 3626, including • Multiple interfaces. • Host and network associations (including dynamic changes). • Link layer notification and link quality. • All parameters are configurable (including dynamically). • IPv4 and IPv6 (separate compilation).

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 7

OLSR Software (2) Current limitations • Does not piggyback messages, but will process received piggybacked messages. • No packet size control or message fragmentation, but will handle fragmented messages. Extensions (all optional) • Minimum message intervals. • MPR Set reuse. • Link layer notification details. • Use HELLO messages to update Interface Association Set and MID messages to change Two Hop Neighbour Set. Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 8

OLSR Simulation Example Minimum intervals as proportion of normal message interval (link layer notification, medium power, high mobility) zero (fully reactive)

quarter interval

half interval

zero (fully reactive)

quarter interval

half interval

Receive overhead per node

100%

50

80%

40

60%

30

40%

20

20%

10

0%

mean overhead (kbyte/s)

proportion of data received

Delivery performance

0 10

30

50

number of nodes

Advanced Technology Centre

10

30

50

numbe r of nodes

© BAE SYSTEMS 2004. All rights reserved.

Slide 9

OLSR Implementation Current wrapper is for Linux. Demonstrated on small mobile networks of laptops and PDAs. Particular current interest in sensor networks • Initially stationary. • Later to add mobile autonomous platform nodes. Used in • Operational trials of a BAE SYSTEMS First Generation Unattended Ground Sensor Network in both open terrain and urban environments. • Collaborative B2NCW (Building Blocks for Network Centric Warfare) programme. (Also looking at reactive protocols.) Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 10

First Generation Unattended Ground Sensor Network Avionics Group Sensor Systems Division

Ground sensor node (low power ARM based processor with WLAN, acoustic interface, geo-phone sensor and GPS)

Tactical Network access Advanced Technology Centre

Universal camera node

Demonstration network integrated with an in-service sounding ranging system © BAE SYSTEMS 2004. All rights reserved.

Slide 11

Sensor Network Trial Results S4

S3

GW1 S2 Example of network topology, as seen from S0

Mean hop counts from S0

S0 C0

S1 M1

Packet receptions at S0 during demonstration 1.2

Sensor 1 (S1) Sensor 2 (S2) Sensor 3 (S3) Sensor 4 (S4) Controller 0 (C0) Gateway 1 (GW1) Monitor 1 (M1)

1.74 1.07 1.01 2.75 1.01 1.54 1.02

The non-integer values demonstrate OLSR network reconfiguration during demonstration

1 0.8 0.6 0.4 0.2 0 00:00:00

01:12:00

Advanced Technology Centre

02:24:00

03:36:00

© BAE SYSTEMS 2004. All rights reserved.

Slide 12

Additional Requirements The following have been identified as of interest in the development of ad hoc networks, and OLSR in particular • Security. • Low power operation (including power control). • Covertness (possibly including reactive capability). • Multicast. • Addressing issues (including IPv6). • External gateway issues (aggregation, dynamism).

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 13

Conclusions Key points • Generic ad hoc routing protocol framework. • Flexible implementation of OLSR. • Minimum interval extension for highly mobile network. • Field trials of ad hoc sensor network. • Additional requirements, especially security.

Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 14

Contact and Acknowledgements Christopher Dearlove BAE SYSTEMS Advanced Technology Centre Great Baddow, Chelmsford, Essex, CM2 8HN, UK. +44 1245 242194 [email protected]

The author gratefully acknowledges the support of his colleagues in BAE SYSTEMS plc, Ericsson Microwave Systems AB and Ericsson Telebit A/S, and the support from the UK, Swedish and Danish MoDs under the EUCLID/Eurofinder programme, Project RTP6.22 (B2NCW).

The First Generation Unattended Ground Sensor Network Concept Demonstration was undertaken on behalf of BAE SYSTEMS Avionics Group Sensor Systems Division. Advanced Technology Centre

© BAE SYSTEMS 2004. All rights reserved.

Slide 15