IoT debugging
0 likes1,369 views
The document provides an overview of IoT and its integration with iOS, including experience from various professionals in related fields. It covers crucial debugging techniques, case studies of IoT applications, and highlights the importance of understanding the hardware and software interplay in IoT solutions. Additionally, it emphasizes the necessity of having a defined debugging strategy prior to implementation.
IoT debugging
- 1. IoT Debugging Su Pingchen LINE Fukuoka 1
- 2. Experience • AVer Information Section Chief Sphere2 - Flip classroom with wireless camera • Noodoe Assistant Manager KYMCO Noodoe • LINE iOS Engineer 2
- 3. Experience 10% 20% 20% 50% iOS dev MFi dev macOS dev Others 3
- 4. Interests 30% 20% 20% 30% World of Warcraft PS4 NS Switch Movie/Drama 4
- 5. Outline • What is IoT • IoT & iOS • Logging on iOS • Debugging IoT 5
- 6. –Wikipedia “The Internet of things (IoT) is the network of physical devices, vehicles, home appliances, and other items embedded with electronics, software, sensors, actuators, and connectivity which enables these things to connect, collect and exchange data, creating opportunities for more direct integration of the physical world into computer-based systems, resulting in efficiency improvements, economic benefits, and reduced human exertions.” 6
- 7. IoT Solutions • Amazon AWS IoT • Google Cloud IoT • Microsoft Azure IoT Image from https://pixabay.com/zh/users/Tumisu-148124/ 7
- 8. IoT x iOS • Apple HomeKit • Google Assistant • Amazon Alexa • LINE Clova Image from https://pixabay.com/zh/users/tagechos-9643195/ 8
- 9. 9
- 10. Mature IoT dev team Hardware Team Firmware(OS) Team Driver(framework) Team App Team Operation Team Backend Team FrontEnd Team 10
- 12. Understanding fundamentals bluetooth / BLE / Wi-Fi 12
- 13. Understanding fundamentals Wi-Fi / Cellular Network 13
- 16. 16
- 17. 17
- 18. 18
- 19. 19
- 20. 20
- 21. 21
- 22. 22
- 23. Unified Logging System (os.log, os.activity) • Event with categories • Built-in extra debug info • Debug with system framework • Debug with other process • Live activity debug • Performance measure 23
- 24. 24
- 25. Understanding fundamentals • btmanager • bluetoothd • accessoryd 25
- 26. Understanding fundamentals • wifid • baseband(3G/4G) 26
- 28. Case Study 28
- 29. Case Study • An app interacts with radio. • We use custom protocol. • We will adopt MFi. 29
- 30. Case Study • iOS ask to connect • Device accept connection • iOS notify new connection • App open stream • Device confirm stream open • Start communication 30
- 31. Case Study ExternalAccessory.framework Radio Controller <Controller Protocol> Radio Session Radio Manager Radio Device System IPC 31
- 32. Case Study ExternalAccessory.framework Radio Controller <Controller Protocol> Radio Session Radio Manager Radio Device System IPC Radio Device Radio Controller <Controller Protocol> Radio Session 32
- 33. Case Study func asyncOpenControlSession() { let session = EASession(accessory: accessory, forProtocol: “com.myService.ctrlSession”) session.inputStream?.open() session.outputStream?.open() } func asyncOpenMediaSession() { let session = EASession(accessory: accessory, forProtocol: “com.myService.mediaSession”) session.outputStream?.open() } func initialize() { asyncOpenControlSession() asyncOpenMediaSession() } import ExternalAccessory 33
- 34. Case Study • iOS ask to connect • Device accept connection • iOS notify new connection • App open stream • Device confirm stream open • Start communication 34
- 36. Case Study ExternalAccessory.framework Radio Controller <Controller Protocol> Radio Ctrl Session Radio Manager Radio Device System IPC Radio Med Session 36
- 37. Debug with performance • Understand your app (platform / service / framework) • Understand server (protocol) • Understand firmware (protocol / data structure) • Understand hardware (capability / limitations) 37
- 38. Debug with performance 38 Hardware Firmware(OS) App Team Operation Backend FrontEnd
- 39. Conclusion • App is the interface of your service • Define debug strategy before implementation • Debug your spec before it is on the table 39
- 40. Thank you 40