room 5 - a deep dive into iot design challenges webinar
TRANSCRIPT
October 2014
A deep dive into IoT design challenges: power management, security and engineering for
delivery
moderated by
Erik Ljung
QuesAons? post in quesAon panel tweet to #room5iot [email protected]
Welcome to part 2 of our technical webinar series
Warren Fox Principle Engineer Power Management Expert
Rickard Eneqvist Principle Engineer Security Architect
Room 5 early IoT pioneers
Dr. Rocky Sherriff, PhD Principle Engineer SoluAons Architect
Erik Ljung CTO
3
• Embedded development • Kernel (Power/GFX) • Middleware and frameworks • Cloud and Web 2.0 • Mobile application development • 3D graphics rendering • Software Architect • Technical Lead • Engineering Management
• Sony Ericsson • Qualcomm • Amazon • DARPA • L3 - Photonics
Erik Ljung – CTO
Warren Fox – Principal Engineer, Power Management Expert
• 25+ years architect & developer of power opAmizaAon, unaXended and embedded devices specialist
• Architected long lifeAme requirements for ultra-‐low power sensing systems
• designed, programmed, and deployed embedded, distributed, and real-‐Ame systems
• Evaluates hardware requirements for custom embedded plaZorms, system architecture design and use case development (hw and sw), programming, tesAng, deployment and client acceptance test
• Authored mulAmillion dollar award winning proposals • Clients: DARPA, Hughes Aircra^ Company and University of
California, San Diego, Bielet Inc (Goji Smart Locks)
Rickard Eneqvist – Principal Engineer, Security Architect
• 20+ years architect & developer of mobile networks/mobile devices with a focus on new technologies, technical advancements and applicaAons
• Architect and principle engineer for distributed Cybersecurity project and designed for heavy parallelism using pthreads and supported atomic funcAons
• Architecture and implementaAon of SDK for applicaAon development targeAng military devices and distribuAon of mesh network distributed informaAon
• Clients: Sony Ericsson, Samsung, Nokia, Qualcomm, Toshiba, Ericsson, L3 Photonics, DARPA and Bielet Inc (Goji Smart Locks)
Dr. Rocky Sherriff, PhD – Principle Engineer, IOT SoluAons Architect
• 15+ years in embedded firmware and mobile, experAse in every technical discipline of IoT systems from firmware to mobile app development, cloud and connecAvity interacAons. Responsible for everything ranging from the physical-‐layer digital signal processing (DSP) assembly code for cell phone handsets and embedded firmware development on resource-‐constrained hardware to the development of base staAon implementaAons on cuing-‐edge SIMD DSP cores. Worked with iOS, Android app and framework development.
• Research physicist with the AirForce Research Laboratory for 9+ years and contributed to research in state of the art ultrafast lasers, epitaxial crystal characterizaAon and verAcal-‐cavity surface-‐emiing laser (VCSEL) design
• Clients: Bielet Inc (Goji Smart Locks), DARPA, Amazon, Freescale semiconductor etc
Materials
Aesthetics
Basic FunctionMaterials
AestheticsBasic Function
Wireless ConnectivityCloud Architecture
Network CommunicationPower Management
Video ProcessingSecurity
Exploding Complexity
Explosive Complexity
If building a lock is a line drawing Building a “smart” lock is a mulA-‐dimensional sphere
Smart connected products and applicaAons
Typical issues facing an IoT soluAon architect • No master reference architecture • MulAple technical disciplines, with various
development life-‐cycles • MulAple integraAon points
The Complex Puzzle
Smart connected products and applicaAons
October 2014
Power management consideraAons • Power opAmizaAons from use-‐case(s); device responsiveness, compute power,
security implicaAons, local interface • Why spin your on hardware; size, volume cost, power draw, peripherals, dev-‐
kits general purpose • Demo to product; picking components, power budget, balance connecAvity and
responsiveness, power states • Maximize baXery life with virtual connecAvity
Warren Fox – Principal Engineer, Power Management Expert
October 2014
When is power management a limiAng factor 1. The more baXery powered IoT devices in the
homes/business and having to change baXeries all the Ame.
2. UnaXended sensors in remote areas that need persistent connecAvity? Addressed with virtual connecAvity. These devices are mostly off and transmiing and receiving infrequently. Turning on and off is the biggest energy draw. In the industrial space, there are proprietary soluAons available for very low power beyond Zigbee.
Warren Fox -‐ Power Management, Embedded Architect
October 2014
IoT power opAmizaAon • ConnecAvity • Responsiveness • Local compute power • Security
Warren Fox -‐ Power Management, Embedded Architect
October 2014
Why spin HW & not use off the shelf dev kits • Size • Dev kits are general purpose • Mass volume cost • Power draw
Warren Fox -‐ Power Management, Embedded Architect
October 2014
From demo to producAon • Power budget • Picking components • OpAmizaAons connecAvity based on use
cases • Power states
Warren Fox -‐ Power Management, Embedded Architect
October 2014
Security consideraAons • Security is not an add-‐on; design security from day one • The use-‐case(s) will tell you about aXack vectors and security risks • What’s our security architectures impact on power management? • Security is not a one-‐off, plan for upgrades and exploits • What can you do to protect against reverse engineering? • Why not always end-‐to-‐end security; complexity of the system and cost
Rickard Eneqvist – Principle Engineer, Security Architect
October 2014
Security • AXack vectors and risks idenAfied early from use-‐cases
End to end security compromises • Cost • Complexity of System
Rickard Eneqvist – Security Architect
October 2014
How Security relates to power • Local CPU computaAon • Hardware support for encrypAon
Rickard Eneqvist – Security Architect
October 2014
Engineering for delivery -‐ ConsideraAons • Design one system and have one clearly idenAfied owner, project trade-‐
offs always exists • Always iterate on a working system based of the primary-‐use case(s) • Design system wide debug funcAonality early and for the life-‐cycle of the
product development • Test-‐driven development for parts and/or the system • Cross-‐disciplinary technologies (applicaAon, cloud/server, firmware,
connecAvity, security, power) mandate a dynamic team structure
Dr. Rocky Sherriff – Principle Engineer, SoluAons Architect
October 2014
Engineering for delivery – Common PiZalls • A demo or POC is not a product • Usually in a funcAonal demo, major technical discipline like power and
security are . Common misconcepAon is that these can be layered on later
• Hardware iteraAons are not as simple as fixing a so^ware bug. In a typical IoT project development life-‐cycles differ – plan for it!
Dr. Rocky Sherriff – Principle Engineer, SoluAons Architect
October 2014
Engineering for delivery Techniques for effecAve cross-‐discipline teams • Early integraAon • Working system • Design for system debug throughout the lifecycle • Test-‐driven development across parts and the
system • Use agile approach where possible but understand
different rhythmns
Rocky Sherriff – IOT SoluAons Architect
October 2014
Engineering for delivery 1. Design one system 2. Always iterate on working system 3. Primary use cases 4. Early integraAon 5. Demo != ProducAon 6. Design debug for the life-‐cycle of the product
development 7. Test driven development for parts and/or system
where applicable 8. Use agile approach to align with rapid emerging IoT
technologies 9. Plan for various so^ware life-‐cycles in a IoT project 10. Project Tradeoffs
Rocky Sherriff – IOT SoluAons Architect
Warren Fox Principle Engineer Power Management Expert
Rickard Eneqvist Principle Engineer Security Architect
Room 5 early IoT pioneers
Rocky Sherriff Principle Engineer SoluAons Architect
Erik Ljung CTO
24
Q&A
25
• Feedback via survey • Next technical webinar will be about edge computing in the Industrial IoT • Questions or schedule a 1:1 discovery or strategy session with our IoT
experts? contact Karen Mills: [email protected], 760-585 9562
Next steps
26
Our Clients
27
embedded & wireless
graphics UX/UI
Tactel AB founded in Malmo, Sweden
1995
Tactel opens first US office in San Diego
20072005
Tactel AB acquires Southend Studios
2009
Tactel receives first external capital
Tactel US becomes independent subsidiary
2011 2013
Tactel US becomes Room 5 Incorporated
multimedia
android
IoT
Smart connected products
smart phones
iOS
windows phones
About Room 5