μPnP: Plug-‐and-‐Play Peripherals for the Internet-‐of-‐Things Fan Yang, Nelson MaIhys, Rafael Bachiller, Sam Michiels, Wouter Joosen, Danny Hughes iMinds-‐DistriNet, KU Leuven, Leuven, B-‐3001, Belgium [email protected] MOTIVATION Conven5onal Plug-‐and-‐Play peripheral integra5on is infeasible for resource-‐ constrained Internet-‐of-‐Things devices: § Mainstream approaches like USB are power-‐hungry and have too much soYware overhead § Peripheral drivers are mostly pla;orm-‐specific import uart; § Tradi5onal discovery protocols are heavyweight uint8_t idx, rfid[12]; bool busy; OUR APPROACH event init(): # 9600 baud, no parity, 1 stop bit, 8 data bits signal uart.init(9600, USART_PARITY_NONE, USART_STOP_BITS_1, USART_DATA_BITS_8); idx = 0; busy = false; 1. Low-‐cost, low-‐power peripheral iden5fica5on based on on passive electrical characteris5cs event destroy(): # restore uart to platform defaults signal uart.reset(); 2. Pla;orm-‐independent, compact and over-‐the-‐air deployable drivers event read(): if !busy: busy = true; signal uart.read(); # initiate read operation 3. Remote peripheral discovery and usage via standard IPv6 mul5cast Example driver code of a UART-based RFID networking card reader. CURRENT PROTOTYPE AND PERFORMANCE § Ultra-‐low power consump5on (6 orders of magnitude lower than USB) § Easy driver language (-‐50% Code, -‐90% RAM) § IPv6 Mul5cast discovery (in 2KB of ROM) § Extremely low cost (< 1¢ per peripheral) § Tiny memory footprint (< 10% of AVR/ATMega128) NEXT STEPS § New testbed with 100 nodes § Global ID management § Secure driver deployment § Smaller and cheaper hardware Funded by: Visit us at: http://www.micropnp.com/
© Copyright 2024