Doc.: IEEE 15-13-0703-00-0010-lighting-use-cases Submission November 2013 Paul Chilton, NXP SemiconductorsSlide 1 Project: IEEE P802.15 Working Group for

doc.: IEEE 15-13-0703-00-0010-lighting-use-cases

Submission

November 2013

Paul Chilton, NXP SemiconductorsSlide 1

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Submission Title: Lighting Use Cases for L2R discussionDate Submitted: Nov 10, 2013Source: Paul Chilton, NXP SemiconductorsAddress: Furnival Street, Sheffield, S Yorks UK Voice:+44 114 281 2655, e-mail: [email protected]: Call for interest and applications in Layer 2 routing

Abstract: Description of some of the use cases and requirements for lighting applications in domestic and commercial buildings.

Purpose: Input to discussions on requirements and applications

Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.


Submission

November 2013


Use Cases in Lighting for Domestic and Commercial Buildings

Dallas, TX

November 12, 2013


Submission

November 2013


Smart Lighting Why make lighting Smart?

Enhanced control Improved user experience Different scenarios in domestic and commercial

Personal use vs Management

Energy saving Intelligent use of lighting when needed

Component of overall Smart Building strategy Buildings become more efficient and controllable through

synthesis of sensor and actuator information


Submission

November 2013


Domestic use cases (1) Personal Control

Control the lighting in a room with a custom controller or smart device (tablet or cellphone) On / Off / Level Colour (inc colour temperature) Effects (transition times, mood lighting) Groups Scenes


Submission

November 2013


Domestic (2) Management

Appropriate light levels Turn off lighting in unoccupied rooms Automatically maintain ambient level

Monitor usage / lifetime Burn time of lamps – power consumption,

reliability Warn for replacement

Installation Initial use Build-out of additional units


Submission

Use Cases, requirements and constraintsLatency

Reliability

Installation

Configuration

Robustness

Power Consumption

Capacity and Environment

Very Low power devices

Cost

November 2013



Submission

Latency• Lights visible to user must appear to operate

instantaneously• User expectation influenced by incandescent bulb behaviour

• Turn on or off in less than 0.5s (ideally 250 msecs or less)

• May depend on technology (eg CFL vs LEDs)

• But something has to happen when the button is pressed

• Lights in other rooms • User doesn’t care so long as the lights do the right thing

• Groups add further constraints• All visible members of a group should appear to act together

• Need to avoid the “popcorn” effect

• Also applies to Scenes since they use underlying Group function

November 2013



Submission

Reliability• Want the command to work when the

button is pressed• Rule of thumb – 99.9% reliability? (1 in a

thousand lost)

• Members of groups should all act together• Can’t have lights in a group missing an “On”

command and staying off

November 2013



Submission

Installation• Initial deployments as small one-room networks

• Eg blister pack 4 bulbs and a remote control

• Later build-out adding more bulbs

• “Islands” of activity (eg per room) which don’t communicate

• Then add external control

• Integrate Islands together

• Link to home network

• Must be easy to do

• Purchase through DIY stores

• Unskilled customer base• Your mother has to be able to do it with no help

• Lack of user interface

• Retailers don’t want returns

• Manufacturers can’t provide customer support on volumes expected

November 2013



Submission

Configuration• No “special” bulbs allowed

• Too difficult to explain to customers• Already difficult to explain that 6W LED is equivalent of 60W

incandescent, and bayonet vs Edison screw fittings

• Too costly to manufacture

• Integration with internet or local home network can use “gateway”

• But need to avoid proliferation of boxes

• Ideally low cost and transparent (border router)

• Some devices may need limited mobility

• Want to be able to use Remote Controls in different rooms when integrated

• Local control between eg switch and bulbs / group

• Binding of switch to group

November 2013



Submission

Robustness• Biggest impediment to smooth

operation• THE LIGHT SWITCH ON THE WALL

• Must be able to recover if a light gets switched off and back on

• Rest of lights must continue to operate while it is off

• Unless it is the sole path to other parts of the network

November 2013



Submission

Power Consumption

• Introducing new green technology – LEDs

• Big improvement over existing bulbs• Incandescent (x10)

• CFL (x2)

• So ON state is very good.

• Costs of adding intelligence• Standby power

• Need to ensure that the OFF state doesn’t contribute substantially to lifetime power figure

• BOM cost increase• Offset with extra functionality

November 2013



Submission

Power Consumption • LED bulbs projected at 15000-50000 hrs lifetime

• Take 30000 hrs lifetime as an example

• Assume this is spread over 5-6hrs per day – so actual installed lifetime of bulb is about 120000 – 150000 hrs (5000-6250 days, 13.5-17yrs)

• Factors affecting lifetime – temperature, electronics

• LED equiv for 60W tungsten is about 6-8W (EC specifies 806 lumens)

• Standby power – 150-300mw (or 500mW with scruffy psu) • 2.5-5% (8%) of power when bulb is ON

• Guess which PSU the manufacturers will want to use

• Over installed lifetime, additional 30-60kWh(100kWh) bulb consumes 300kWh

• Target less than 100mw - will need Duty cycling/sleeping

November 2013



Submission

Capacity and EnvironmentNumbers for a smart home (US 2010)

About 200 nodes, with half of them lighting

So network sizing needs to be able to cope with at least this number to be safe

Apartments vs HousesAbove numbers are for detached housing

Probably no neighbour networks in range

Apartments

Smaller numbers per unit (20-30 lights, 50 total?)

Denser in terms of networks and nodes

Semi-detached housing

Neighbouring networks in range

Smaller number of devices (100-150?)

November 2013



Submission

Very Low Power devices• A useful class of sensors and control inputs

• Low cost of (semi permanent) installation• Need to be self contained

• No mains supply wiring

• No control connections

• Long lifetime or v low maintenance• Self powered (coin cell) or energy harvesting

• Examples• light switches (mechanical or piezo scavenging)

• Thermostats / Temp sensors

• Occupancy or light sensors (PV cell)

The “Peel and stick” approach

November 2013



Submission

Duty cycling issues• Duty-cycling increases latency

• Can’t send until intended receiver is awake

• May need to tune duty cycles to achieve latency targets • in different classes of device

• Different locations in the network

• Synchronisation of group actions• Implications for sleep schedule, or higher layer sync?

• How to perform broadcast/multicast

• VLP devices may require “always on” proxies• Typically just launch transmissions

• May not have enough energy to synchronise with another device

November 2013



Submission

Cost Cost of adding intelligence/connectivity

Must be a small portion of overall BOM to be viable

CFLs retail at $5 – probably charge a premium for added functionality, but not much

Determined by several factors

Packaging costProbably needs to be integrated transceiver – 1 package cheaper

than 2

Silicon die size

Radio and memory are two biggest components

Can’t do much about radio size

Therefore memory size is criticalROM:Flash:RAM:EEPROM roughly ratio of 1:2:6:12 area

per bit in most technologies

RAM is most critical – may have effect on routing

Operating Environment

November 2013



Submission

Security

May be more severe when networks are in close proximity

Don’t want other people to change your lighting

Don’t allow unauthorised devices on network, but must have mechanism to allow devices to attempt to join

November 2013



Submission

Summary

Easy to use and install

Low latency

Reliable transmission

Low power consumption

Small memory footprint

Low cost adder

Very low power devices

Control locally and over internet

November 2013



Submission

Commercial Building

• Differences from Domestic lighting use cases• Architecture• Installation and commissioning• Size

November 2013



Submission

ArchitectureFunctional Silos

HVAC, Fire, Security, Lighting, Elevators

Sensors and actuators

Components at the edge of the network

Area Controllers

Small area, eg room or open space

Provide localised control and use local sensor data – usually for one functional silo

Eg lighting control in a room

Zone Controllers

Similar to Area controller but cover larger area eg floor

Take inputs from area controllers

May still take inputs from sensors

Building Management System synthesises higher functionality

November 2013



Submission

CB InstallationUnskilled installer

May only install one type of equipment

Several visits by different installers required for full fit-out

Needs to test installation standalone eg per room

Similar to domestic installation

Skilled commissioning engineerFor system level commissioning

Ties together equipment in one or more functions

System Integration To make complete BMS after different systems commissioned.

BMS may be less flexible if devices are only addressable by functional area

November 2013



Submission

Installation SizesArea Controller (room)

Small meeting room 5-10 devices

Conference room 30+ devices (lights, occupancy sensors, switches, shade actuators, HVAC)

Open office area

Lighting

Placement every 3m typically on a grid

Independent areas (20mx20m) may have 50 luminaires

multiple lights in each

HVAC zones

15mx15m area with control dampers, temp sensor, flow sensors (6 devices?)

Fire detection

Smoke detectors every 15m, grid layout, plus manual alarms

Security - more difficult to predict - Ground floor doors & windows, internal access control

Zone per floor, many area controllers handling 60mx20m may have 500 devices present

Lighting dominates, but need to provision for other control and sensor functions

November 2013



Submission

HotelRemote control per room controlling lights in that room

Similar to apartment Many networks or groups of devices in close proximity

PAN per room or per floor?

Link back to central control over building Ethernet wiring?

Extra features Alarm call - raise light level gently as wakeup

Hotel maintenance team can monitor state of bulbs

Turn off lights when customer not in the room

November 2013



Submission

Street LightingNeed to be able to support long thin network

structure

Reliable rather than low latency

Comms between eg nearest neighbour and next nearest neighbour for redundancy of links

Probably needs higher security since it is out in the openCould be hacking target

Could use as backbone for urban sensors

November 2013


Documents

Doc.: IEEE 15-13-0703-00-0010-lighting-use-cases Submission November 2013 Paul Chilton, NXP SemiconductorsSlide 1 Project: IEEE P802.15 Working Group for