1 / 10

Design and Application Space for 6LoWPAN

Design and Application Space for 6LoWPAN. Draft-ekim-6lowpan-scenarios-00 Eunsook Kim, Nicolas Chevrollier, Dominik Kaspar. Goal of design and application spaces draft. To List Scenario and Market domains To define design parameters To provide detailed scenarios To list the benefit of IP

jwaldrop
Download Presentation

Design and Application Space for 6LoWPAN

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. Design and Application Space for 6LoWPAN Draft-ekim-6lowpan-scenarios-00 Eunsook Kim, Nicolas Chevrollier, Dominik Kaspar

  2. Goal of design and application spaces draft • To List Scenario and Market domains • To define design parameters • To provide detailed scenarios • To list the benefit of IP • To Provide a base to discuss 6lowpan requirements with specific industries

  3. Scenario parameters • Major parameters currently in the draft • Deployment (Manual vs. Automatic, Addressing Mechanism dynamic configuration, battery/mains power) • Network Size (10, 100, 1000, …) • Routing (Topology, Single-hop, Multi-hop, data centric, event driven, address centric, localization based) • Mobility (fixed vs. moving) • Connectivity (always connected, intermittent, sporadic) • Security/ Threat model

  4. Scenario 1: structure monitoring • A 1000m long bridge with 10 pillars. Each pillar contains 5 sensors to measure the water level, and 5 vibration sensors to monitor its structural health. On the top part of each pillar, an "infrastructure" FFD sink node is placed to collect the sensor data. The FFD is the LoWPAN coordinator of the sensors for each pillar which can be FFD or RFD. • Main characteristics • static deployment • star topology networks • All nodes are static and pre-configured • Low numbers of nodes • Several star networks may be managed in a hierarchy • Routing occurs only from leaf nodes to the PAN coordinator • Event-driven data

  5. Scenario 2: Healthcare(at home/Hospitals) • A small number (e.g, less than 10) of sensors are deployed on a patient body for medical surveillance. They monitor vital signs such as heart beats or blood pressure, and provide localization information. The patient is able to move in his room or within the hospital. The collected data is sent to sinks placed onto hospital's walls. • Main characteristics • Single, low- to medium-sized star networks • Moving in an infrastructure of sink nodes • Automatic configuration for mobility support • Periodic data gathering

  6. Scenario 3: Vehicular networks • Scattered sensors are included in roads during their construction for motion monitoring. When a car passes on top of these sensors, the possibility is then given to track the trajectory and velocity of the car for safety purpose. A rough estimate of 4 sensors per square meter is needed. • Main Characteristics • Mobility support • Multi-hop mesh networks • Possibly dense node populations • Highly mobile networks • Car to Car (TBD)

  7. Scenario 4: Home and Industrial deployment • TBD

  8. Scenario 5: agricultural monitoring • In a 20-acres vineyard, 8 parcels of land are equipped with 10 sensors each to provide readings on temperature and soil moisture. Each of the 8 parcels contains 1 FFD sink to collect the sensor data. 10 intermediate FFD "routers" are used to connect the sinks to the main gateway. • Main Characteristics • static deployment • multi-hop mesh networks • All nodes are located statically • Medium to large numbers of nodes • Can be manually configured • Within mesh networks, auto-configuration and dynamic routing is needed • Data may be gathered both periodically or driven by event

  9. Scenarios out of scope? • Scenarios where • No motivation to use IEEE 802.15.4 • Regional/national wide networks

  10. Questions and Future work • Which scenarios do we need to add? • Did we capture the important dimensions? • Are there scenarios that are close, but definitely are *not* in scope for 6lowpan? • Further improvements of the scenarios • Feed back from industrial partners

More Related