html5
1 / 9

Design and Application Spaces for 6LoWPAN

Design and Application Spaces for 6LoWPAN. (draft-ekim-6lowpan-scenarios-01) IETF-70 Vancouver Wednesday, December 5th 2007 1300 – 1500 Afternoon Session I Eunsook Kim, Nicolas Chevrollier, Dominik Kaspar, JP Vasseur. Goal of design and application spaces draft. Goal:

schaffee
Download Presentation

Design and Application Spaces 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 Spaces for 6LoWPAN (draft-ekim-6lowpan-scenarios-01) IETF-70 Vancouver Wednesday, December 5th 2007 1300 – 1500 Afternoon Session I Eunsook Kim, Nicolas Chevrollier, Dominik Kaspar, JP Vasseur

  2. Goal of design and application spaces draft • Goal: • This is an Recommendation for 6LoWPAN applications • Documents how 6LoWPAN networks deploy and list *main* characteristics (e.g. topology, security, traffic pattern, …) • Non Goal: • We are not trying to provide an EXHAUSTIVE description of the all possible deployments

  3. In the last meeting • Major parameters • 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 • Scenarios • Structure Monitoring • Healthcare • Vehicular Networks • Agricultural Monitoring

  4. Update (-01) • Four Parameters are added • Security Level • Power Source • QoS • Traffic Pattern

  5. Update (-01) • Four Scenarios are updated based on the added parameters • Two scenarios are added • Industrial Monitoring • Connected Home

  6. Industrial Monitoring (1/2) • Application fields • Process Monitoring and Control • Machine Surveillance • Supply Chain Management and Asset Tracking • Storage Monitoring • Ex: • Various sensor measurements together with controllers and actuators • gas pressure • the flow of liquids and gases • room temperature and humidity • tank charging levels • to improve a plant's productivity in a continuous self-controlling loop

  7. Industrial Monitoring (2/2) • Dominant Parameters • Deployment: pre-planned, manually attached • Mobility: no (except Asset Tracking) • Network size: medium to large • Power source: battery-operated • Security level: high • Routing: multi-hop, highly event-driven • Connectivity: always on for crucial case, otherwise intermitted • QoS: important • Traffic pattern: P2P (actuator control), MP2P (data collection)

  8. Connected Home • Application fields • Home safety/security • Home automation and control • Healthcare • Smart appliances • Dominant Parameters • Deployment: multi-hop topologies • Mobility: small degree of mobility • Network size: medium number of nodes, potentially high density • Power Source: mix of battery and AC powered • Security level: authentication and encryption required • Routing: no requirement for multi-topology or QoS routing • Connectivity: intermittent (usage-dependent sleep modes) • QoS: support of limited QoS (small number of Class of Service) • Traffic Pattern: P2P (inter-device), P2MP and MP2P (polling)

  9. Questions and Future work • WG feed-back on the document very much welcome • Does the WG agree that such a document is useful? • If so, what can be the next step for the ID? (more scenarios? More detail description? etc.)

More Related