1 november 11, 2015 iot: rapid prototyping for fun and profit avi baum texas instruments inc. nov,...
TRANSCRIPT
1November 11, 2015
IoT: Rapid Prototyping for Fun and Profit
Avi BaumTexas Instruments Inc.
Nov, 2015
November 11, 2015
2November 11, 2015
Developer :: Who are you?
USER?
HOBBYIST
STRATEGIST
ARCHITECT
SALES
DEVELOPER
MARKETING
3November 11, 2015
CPU ’Brain’ power
Sensor / Actuator:
Physical world interactionElectrical, Mechanical, Chemical…
Power Energy sourceLine, Battery, Harvesting..
Connectivity CommunicationWired (ETH, HART..)Wireless (S1G, BLE,..)
The Product
PRODUCT
CPU
ACT / SENSE
POWER
CONNECT
4November 11, 2015
Source: GE Estim
ates, Oct 2013
The Business Source: Harvard Buisness Review, Oct 2015
HUGE opportunity in the Industrial sector
HUGE traction in the Consumer & Personal sector
..YET..
5November 11, 2015
USER Human interaction
SERVICE Data-driven entity )Source, Sink or Pipe(
THING Machine interaction
The Ecosystem
IoTUSER
THING
SERVICE
6November 11, 2015
Developer :: The Need
✓SIMPLE
✓SMART
✓SECUREPROPERTIES
SMART
SIMPLE
SECURE
7November 11, 2015
Developer :: The Need :: Simple
▶Making ‘Simplicity’ Quantifiable
▶Overcome multi-discipline knowhow
▶Focus on product, minimize unnecessary
8November 11, 2015
Developer :: The Need :: Simple
A. Absolute
B. Scaled
Simplified to the level an operation is avoided, seamless or, trivial and unnoticeable
Complexity is scaled to the capabilities of the typical target user; Overall good experience
C. Relative Lower compared to expectation. Either in comparison to same type of product, former generation of same product or similar task
D. Full Proof Though complex, a complete decision tree ensures no option uncovered; Troubleshooting
F. ComplexHigh complexity ; limited information ; many steps ; hard to follow procedure etc .
9November 11, 2015
Developer :: The Need :: Simple
▶Standard adherence APIs (where applicable, e.g. networking)
▶Standard resembling APIs (e.g. file system, applications)
▶No APIs for uncommon or complex tasks (e.g. TLS, PHY)
9
L8 IoT
L7 Application
L6 Presentation
L5 Session
L4 Transport
L3 Network
L2 Data Link
L1 Physical
10November 11, 2015
Developer :: The Need :: Smart ▷Handling large scale
‣Of devices ‣Of connections ‣Of interactions
▷Sparse nature of traffic ▷Protocol overheads
▷Localization ▷Energetic efficiency
11November 11, 2015
Developer :: The Need :: Secure
▶Design for security
▶Safety net for developer mistakes
▶Inherent and unavoidable
▶Standard Adherence & Certification
12November 11, 2015
OEM :: The Landscape
Source: Harvard Buisness Review, Oct 2015
▶OEMs shifting core competency
▶Moving out of traditional comfort zone
▶Products changings nature
▶New use cases
▶New capabilities
13November 11, 2015
OEM :: The Need
✓Quality
✓Robustness
✓ScalablePROPERTIES
ROBUST
QUALITY
SCALE
14November 11, 2015
Case Study
▶Is switch client? server?
▶Is communication IP based?
▶Is it local? Cloud-based?
▶Optimization goal
Optimize energy of the switch to allow battery
operated switch while guaranteeing latency
constraint.
Case 1
Optimize overall system energy under given latency constraint for a network with N switch + bulb pairs.
Case 2
Optimize overall system energy under given
latency constraint for a network with N switch
+ bulb pairs.
Case 3
15November 11, 2015
Two Examples
15
Connected Toy Cars
Connected Sticky Note
..For Fun
..And profit
16November 11, 2015
I ndefiniteOpportunitiesT erritory