Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models...

14
Slide 1 Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions From: Roxanne Gryder, Mark Yarvis, Jasmeet Chhabra May 11, 2004

Transcript of Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models...

Page 1: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 1

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Defining Usage Models for 802.11s ESS Mesh

W. Steven Conner

Intel Corp.

Contributions From:

Roxanne Gryder, Mark Yarvis, Jasmeet Chhabra

May 11, 2004

Page 2: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 2

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Outline Goals for Defining Usage Models

Examples: Home, Office, Hotzone

Driving Requirements and Evaluation with Usage Models

Recommended Next Steps

Page 3: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 3

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Defining Usage Models for 802.11s Exercise: Define and document expected use and behavior of Exercise: Define and document expected use and behavior of

ESS Mesh networksESS Mesh networks

Recent Example: TGn Usage Models (11-03/802)Recent Example: TGn Usage Models (11-03/802) ApplicationApplication: source or sink of wireless data : source or sink of wireless data

EnvironmentEnvironment: type of place where the WLAN deployed: type of place where the WLAN deployed

Use CaseUse Case: how an end-user uses a system that exercises the WLAN : how an end-user uses a system that exercises the WLAN (application in a deployment environment)(application in a deployment environment)

Usage ModelUsage Model: Collection of one or more Use Cases that specifies a : Collection of one or more Use Cases that specifies a realistic scenario to evaluaterealistic scenario to evaluate

Additional Items Useful to Capture in ESS Mesh Usage Models:Additional Items Useful to Capture in ESS Mesh Usage Models: Node mobility (mesh APs and clients)Node mobility (mesh APs and clients)

Security (mis)use cases and threatsSecurity (mis)use cases and threats

Connectivity to non-802.11 networksConnectivity to non-802.11 networks

Network management use casesNetwork management use cases

Page 4: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 4

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Why Define Usage Models? Drive functional requirementsDrive functional requirements

What are the functional components?What are the functional components? What are the requirements for each component?What are the requirements for each component?

Drive evaluation and comparison criteriaDrive evaluation and comparison criteria What are the performance evaluation metrics?What are the performance evaluation metrics? How to evaluate solutions against and security How to evaluate solutions against and security

threats? threats?

Page 5: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 5

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Home Network Usage Model Example

Office

Bedroom

Den

Internet

Mesh AP

Mesh SoftAP PCs Mesh AP CE Devices

Non-MeshClients

User Requirements:User Requirements: Reliable high-bandwidth coverage Reliable high-bandwidth coverage

throughout homethroughout home Internet access and high-bandwidth Internet access and high-bandwidth

peer-to-peer A/V streams and data peer-to-peer A/V streams and data transfer (e.g., MPEG content between transfer (e.g., MPEG content between PVR and HDTV)PVR and HDTV)

Self-managing and easy to install Self-managing and easy to install (non-technical consumers)(non-technical consumers)

Network and data are “secure”Network and data are “secure”

Deployment Characteristics:Deployment Characteristics: Densely interconnected wireless Densely interconnected wireless

topologiestopologies Usually one broadband Internet Usually one broadband Internet

connection out of homeconnection out of home Blurred lines between infrastructure Blurred lines between infrastructure

and clients:and clients: Many fixed or rarely moving devices Many fixed or rarely moving devices

such as Gateway/AP, PC, PVR (good such as Gateway/AP, PC, PVR (good candidates for Mesh APs)candidates for Mesh APs)

Battery-powered clients may be mobile Battery-powered clients may be mobile in the home (laptops, PDAs, cameras)in the home (laptops, PDAs, cameras)

Page 6: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 6

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Small/Medium Office Network Usage Model Example

Two ScenariosTwo Scenarios AP meshAP mesh

SoftAP PC meshSoftAP PC mesh

Non-meshclientsMesh

SoftAP

User Requirements:User Requirements: Reliable high-bandwidth network coverage Reliable high-bandwidth network coverage

anywhere in the office/campus anywhere in the office/campus Applications primarily require access to Intranet Applications primarily require access to Intranet

services, with limited peer-to-peer (e.g. services, with limited peer-to-peer (e.g. file/presentation sharing, printing)file/presentation sharing, printing)

Network administrator must be able to control Network administrator must be able to control and manage the ESS Mesh infrastructureand manage the ESS Mesh infrastructure

Network and data are “secure”Network and data are “secure”

Deployment Characteristics:Deployment Characteristics: Relatively dense infrastructure topology to Relatively dense infrastructure topology to

support high client densitiessupport high client densities Potentially multiple gateways to wired Intranet Potentially multiple gateways to wired Intranet

and other networksand other networks Fixed Infrastructure may include Mesh APs and Fixed Infrastructure may include Mesh APs and

desktop Mesh SoftAP PCsdesktop Mesh SoftAP PCs Fixed and mobile clients (PCs, laptops, PDAs, Fixed and mobile clients (PCs, laptops, PDAs,

etc).etc).

Page 7: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 7

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Hotzone Network Usage Model

Wired Network

Wired Network

User Requirements:User Requirements: Reliable coverage anywhere in the Reliable coverage anywhere in the

hotzone), e.g., across airport or hotzone), e.g., across airport or shopping centershopping center

Client applications primarily require Client applications primarily require Internet accessInternet access

Network provider must be able to Network provider must be able to control and manage the ESS Mesh control and manage the ESS Mesh infrastructureinfrastructure

Network and data are “secure”Network and data are “secure”

Deployment Characteristics:Deployment Characteristics: Dedicated infrastructure of fixed-location Dedicated infrastructure of fixed-location

Mesh APs (relatively sparse topology)Mesh APs (relatively sparse topology) Potentially multiple gateways to Internet Potentially multiple gateways to Internet

and other wired networksand other wired networks Fixed and mobile clients (laptops, Fixed and mobile clients (laptops,

handhelds, etc.)handhelds, etc.)

Page 8: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 8

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Summary of Deployment Characteristics

Home Office HotZone

Scale (Number of Mesh APs) Small-Medium

Medium-Large

Medium-Large

Density of Mesh APs High Medium-

High

Low-Medium

Frequency of Physical Mesh AP Topology Change

Low Low Low

Frequency of Mesh Link Quality Changes

Medium-

High

Medium-High

Medium-High

Number of connections to other (e.g. wired) networks

Low (1-2) Medium-High

Low-Medium

Page 9: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 9

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Possible Process for Driving Requirements and Evaluation Criteria with Usage Models

Usage Models

FunctionalComponents

Evaluation / Comparison

Criteria

Evaluation / Comparison

Criteria

Evaluation / Comparison

Criteria

Evaluation / Comparison

Criteria

Evaluation / Comparison

CriteriaFunctional

Requirements

Iteration

Assumptions

Page 10: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 10

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Proposed Next Steps1.1. Create common usage model description Create common usage model description

documentdocument 11n Usage Model document is a reasonable starting point, 11n Usage Model document is a reasonable starting point,

but need to extend and prioritize for ESS Meshbut need to extend and prioritize for ESS Mesh

Include security (mis)use-cases and threat analysisInclude security (mis)use-cases and threat analysis

2.2. Define major functional components and begin Define major functional components and begin compiling requirements based on usage modelscompiling requirements based on usage models

Page 11: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 11

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Thank You!

Questions?

Page 12: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 12

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Backup

Page 13: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 13

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

What Problems Motivate the Use of ESS Mesh?

Limited WLAN range/coverageLimited WLAN range/coverage

ReliabilityReliability

PerformancePerformance

Deployment cost/effortDeployment cost/effort

Ease of useEase of use

Page 14: Doc.: IEEE 802.11-04/528r1 Submission May 2004 Conner (Intel Corp.) Slide 1 Defining Usage Models for 802.11s ESS Mesh W. Steven Conner Intel Corp. Contributions.

Slide 14

Doc.: IEEE 802.11-04/528r1

Submission

May 2004

Conner (Intel Corp.)

Example Traffic ClassesApplications Offered

Load Protocol Maximum

Packet Loss Rate

Maximum Delay

Internet File Transfer(email, web, chat)

1Mbps TCP

Local File Transfer(printing, backup, multimedia)

30Mbps

(bulk transfer)

TCP

Netmeeting application

500kbps TCP

Internet Streaming Video/Audio

100kbps-4Mbps

UDP 1% 200ms

VoIP 20-150kbps UDP 5% 30ms

SDTV 4-5Mbps UDP 5x10-7 200ms

HDTV 19.2-24Mbps UDP 10-7 200ms

Source: TGn Usage Models 11-03/802r16