1 / 18

CentMesh

CentMesh. Centennial Wireless Mesh Testbed. Original Vision.

titus
Télécharger la présentation

CentMesh

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CentMesh Centennial Wireless Mesh Testbed

  2. Original Vision The Centennial Mesh project aims to build a highly programmable, extensible, open, outdoor wireless testbed to support research and education on the design of wireless mesh networks, as well as IT systems and applications enabled by wireless mesh networks, using open source code built by NCSU students and faculty, and re-using other open source code • Part of original SOSI proposal • Also funded by DURIP grant from ARO • In planning and design/development (and permissions!) for two years • Equipment ordering now mostly complete • Close to deployment – ITng (OSCAR Labs) overseeing • Internetwork Engineering as wireless survey/contractor

  3. Two Networks

  4. Motivation • Many emerging security and network research areas in network availability, reliability etc. • Solutions are often through routing, opportunistic MAC, etc. research areas i.e. low down and across stack • Availability of testbed a plus for enabling more successful and more practically useful research • Need a testbed that allows separation of experimental concerns • Data transport, E2E control • Signaling and control • Management algorithms, “knowledge plane” • Also host of application (IT and other) research enabled • Some originally conceived research projects, envisioned continued use beyond

  5. Experimental Network Phases • Phase 1: Laboratory testbench • Purpose: Develop initial software architecture, create initial common codebase • Phase 2: Pushcart nodes • Purpose: Benchmark wireless conditions, prove developed software and envisaged hardware strategies in outdoor settings, survey multiple locations for permanent installation • Phase 3: Poletop installations • Purpose: Provide a (semi-)permanent testbed installation for researcher-users of CentMesh

  6. Design Goals and Plan • No wired backbone, 802.11 link based • Use simple commodity hardware for platform • Standard PCs, Atheros cards (2 / 4 per node) • Use open source software, develop open source software • MadWiFi driver, Linux • Modularize and cleanly separate functionality whenever possible • Separate data, control, management planes • Allow plugging in/out specific software modules

  7. Software Architecture • Central control/management node • All control/signaling traffic is channeled through the communicator module • Embeds control plane policies such as spectrum usage • Uses TCP connections between mgmt and mesh nodes • Uses automatic pub/sub mechanism locally, manual/programmatic pub/sub across nodes (planned extension to complete automatic pub/sub in future)

  8. Software Architecture • Mgmt node contains a data repository (MySQL) • Acts as decoupling intermediary between various data collection/dissemination procedures • Management software modules implemented in general as paired managers and agents • Managers and agents are clients to communicator • Managers interact with data repository

  9. Software Architecture • Servers for typical OAM tasks also attaches to data repository • Clients may run on control node or elsewhere on Internet • Visualization currently implemented this way • Scripting planned to work this way (will adapt from past existing testbed implementation)

  10. Software Architecture • Some enabling mgmt modules included as system modules • Can be replaced but not eliminated • Neighbor discovery • Agent collects and sends information to manager • Manager enters into database • Bootstrap routing • Manager computes connected topology and distributes to agents for actuation • Can be computed from database, currently manual • Other core mgmt modules • Routing • Channel/radio control • Power control • Scheduling (coarse-grain) • Separate recovery partition with only system modules

  11. Production Wireless Mesh • Extension of NCSU network • Comtech managed • A portion for research as needed • >=5 year lifespan

  12. Experimental Wireless Mesh Network • For testing, development, and innovation of wireless networking technology and applications. • Run/managed by ITng • All activity coordinated with Comtech • 3rd phase of development (lab, cart, poles) • >=3 year lifespan

  13. Planning/Deployment Milestones • Development of experimental mesh nodes • OIT/Comtech approval • Initial walkthrough to determine location candidates • University Architect approval • Electrical design • RF survey • Equipment Purchase • Installation • Network configuration

  14. Node Locations

  15. Location Types • Building • Root Nodes • Textiles, Keystone, RedHat Parking Deck, EB2 • Pole • Mesh nodes • Majority of locations • Arbor • Mesh nodes • South of EB1 and EB3 • Similar to pole locations

  16. Pole Installation Details

  17. Pole Mock-up

  18. centmesh.csc.ncsu.edu centmesh.itng.ncsu.edu Building Mock-up

More Related