Collaborative Development – An HAE* Use Case * Home Appliances & Entertainment Inhwan Choi, LG Electronics Project Maintainer October 20, 2015 20 October 2015 AllSeen Alliance 1
Agenda 1. Overview of HAE Service Framework 2. Participation 3. Collaboration 4. Theory of Operation 5. Interface Definitions 6. Project Milestones 7. Lessons Learned 8. Resources 20 October 2015 AllSeen Alliance 2 2
Overview of HAE Service Framework The HAE service framework project develops the common way of controlling and monitoring Home Appliances & Entertainment (HAE) category devices, regardless of device manufacturers. Use Cases Benefits • Cross-Vendor Interoperability HAE Controller HAE Device – Interoperate between devices and controllers from different vendors Control • Machine-to-Machine Interaction Monitor – No need for human’s intervention. – Background interactions between devices 20 October 2015 AllSeen Alliance 3
Participation Major HAE device manufacturers and a leading smart home service provider are actively participating to contribute their expertise. 20 October 2015 AllSeen Alliance 4
Collaboration Members have been making consistent efforts to deliver AllJoyn interface definitions for flexible representation of HAE devices while complying with IRB guidelines. 1 st F2F 2 nd F2F 3 rd F2F @ Italy @ Korea @ China 20 October 2015 AllSeen Alliance 5
Theory of Operation – Device Model Following the AllJoyn bus object structure, a real HAE device will expose its interaction capabilities via implemented AllJoyn interfaces. Names for bus object paths are not candidates for standardization and can be arbitrarily chosen. 20 October 2015 AllSeen Alliance 6
Theory of Operation – Device Model Depending on its actual complexity, the entire physical device Root might have one or more children devices in its AllJoyn representation. Names for bus object paths are not candidates for standardization and can be arbitrarily chosen. 20 October 2015 AllSeen Alliance 7
Theory of Operation – Device Types The initial version of HAE service framework defines 23 device types. ※ For more detailed information, refer to the its Theory of Operation document. 20 October 2015 AllSeen Alliance 8
Theory of Operation – Discovery Before joining a session, discovery of HAE service framework and the implemented HAE device types should be enabled. For this, the service framework's own custom field, org.alljoyn.SmartSpaces.DeviceDescription will be appended to About metadata. • Examples – DeviceDescription = { <"/A", 0>, <"/A", 5> } for Example Air Conditioner – DeviceDescription = { <"/HAE", 0>, <"/HAE/Alpha", 2>, <"/HAE/Beta", 3>, <"/HAE/Gamma", 4> } for Example Refrigerator 20 October 2015 AllSeen Alliance 9
Interface Definitions – under IRB Review Namespace Interfaces org.alljoyn.SmartSpaces Theory of Operation document org.alljoyn.SmartSpaces. AirRecirculationMode, Alerts, AudioVideoInput, AudioVolume, Operation (26) BatteryStatus, Channel, ClimateControlMode, ClosedStatus, CycleControl, DishWashingCycle, EnergyUsage, FilterStatus, HeatingZone, HvacFanMode, InsertionStatus, LaundryCycle, OnOff, OvenCycle, RapidMode, RapidModeTimed, RemoteControllability, RepeatMode, ResourceSaving, RobotCleaningCycle, Timer, UserInput org.alljoyn.SmartSpaces. CurrentAirQuality, CurrentAirQualityLevel, CurrentHumidity, Environment (13) CurrentTemperature, MoistureOutputRate, TargetHumidity, TargetSoilLevel, TargetSpinSpeedLevel, TargetTemperature, TargetTemperatureLevel, WaterLevel, WindDirection, WindStrength org.alljoyn.SmartSpaces. LanguageDisplay, TemperatureDisplay, TimeDisplay UserInterfaceSettings (3) 20 October 2015 AllSeen Alliance 10
Project Milestones Milestone Date Notes Draft Interface Definitions Jul. 24, 2015 Done Before the AllSeen Summit IRB Approval of Interface Definitions Oct. 16, 2015 High-Level Design (HLD) Document Nov. 13, 2015 Draft will be available before the summit and discussed during the summit. Service Framework Source Release Feb. 26, 2016 v15.04 Core will be the base. - C for Thin Client (Controllee) After release, request IP review for - C++ for Standard Client inclusion into base implementations. (Controllee/Controller) Sample Mobile App. Release (Android) Apr. 29, 2016 30-day IP review ends before this Device Emulators Development milestone. Test Suite Development Certification Launch May. 27, 2016 C&C Review and Validation of Test Suite Assumptions 1) Initial release and certification program supports only a subset of defined device types. The initial list of device types : Air Conditioner, Clothes Washer, Clothes Dryer, Clothes Washer-Dryer, Refrigerator, Freezer, IceMaker, Oven, Cooktop, Cooker Hood, Dish Washer, Robot Cleaner, Television The rest of device types to be supported at the next release : Thermostat, Humidifier, Dehumidifier, Air Purifier, Electric Fan, Air Quality Monitor, Food Probe, Set Top Box 2) Source codes for sample mobile application and device emulators are not candidates for IP review. 20 October 2015 AllSeen Alliance 11
Lessons Learned • Ask questions early and often ! – Especially before you request an official review of interfaces you designed. – Different experts might have different opinions. Try to get consultations from a broader membership, if available. • Participate and contribute your expertise ! – Every work is done by voluntary contributions. – To move fast or deliver higher quality of work, contribute your expertise. • F2F meeting makes a real progress ! – Especially in case of multi-vendor collaboration from different countries. 20 October 2015 AllSeen Alliance 12
Resources • Wiki page https://wiki.allseenalliance.org/hae • Mailing list Subscribe allseen-hae@lists.allseenalliance.org • Jira https://jira.allseenalliance.org/projects/ASAHAE • Weekly technical meeting Oct. 28 Nov. 5 20 October 2015 AllSeen Alliance 13
Thank you Follow us on For more information on AllSeen Alliance, visit us at: allseenalliance.org & allseenalliance.org/news/blogs 20 October 2015 AllSeen Alliance 14
Recommend
More recommend
