1. 26 August 2015 AllSeen Alliance 1 C&C Working Group Meeting 11 JUNE 2014

2. 26 August 2015 AllSeen Alliance 2 Antitrust Compliance Notice AllSeen Alliance meetings involve participation by industry competitors, and it is the intention of AllSeen Alliance to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at AllSeen Alliance meetings and in connection with AllSeen Alliance activities are described in the AllSeen Alliance Antitrust Policy. If you have questions about these matters, please contact your company counsel, or if you are a member of AllSeen Alliance, feel free to contact Lee Gesmer or Andrew Updegrove, of the firm of Gesmer Updegrove LLP, which provides legal counsel to AllSeen Alliance.

3. 26 August 2015 AllSeen Alliance 3 Guidelines This is a reminder that all AllSeen Alliance activities are subject to strict compliance with the AllSeen Alliance By-laws. Each individual participant and attendee at this meeting is responsible for knowing the contents of the AllSeen Alliance By-laws, and for complying with the AllSeen Alliance By-laws. Copies of the AllSeen Alliance By- laws are available at: https://allseenalliance.org/allseen/bylaws Reminder: This call is being recorded

4. 26 August 2015 AllSeen Alliance 4 4 1. Getting Validation tool built and tested 2... Goals for Today’s Discussion

5. 26 August 2015 AllSeen Alliance 5 Example: Self Validation Test Setup and Executing Test Cases 1. Configure a Nexus Tablet (Android test device) to connect to Personal Access Point. Nexus 7 Tablet is the device on which the tests are executed 2. Onboard Device Under Test (DUT) to Personal Access Point. DUT is the device against which tests will be executed 3. Connect Nexus 7 Tablet to a PC/Laptop (Win 7) via USB cable 4. Download test code from GIT repository onto PC/Laptop 5. Compile test code and build test app on the PC/laptop 6. Deploy the test app to the Nexus 7 Tablet 7. Execute command on the PC/Laptop to start the execution of tests on Nexus 7 Tablet against the Device Under Test 8. View and analyze the test results produced on the PC/Laptop GIT 8 8 5 5 1 1 4 4 2 2 6 6 7 7 3 3 DUT

6. 26 August 2015 AllSeen Alliance 6 Feedback on Homework from May 7th Using the example on previous slide, setup and execute Self Validation Test Cases: 1.Acquire/configure an Android device (preferably Nexus 7) 2.Setup the Test Environment as per Validation Test User Guide 3.Compile the test cases as per Validation Test User Guide 4.Execute the test cases as per Validation Test User Guide 5.Provide feedback on process Validation Test User Guidehttps://wiki.allseenalliance.org/_media/compliance/alljoyn_validation_te st_user_guide.pdfhttps://wiki.allseenalliance.org/_media/compliance/alljoyn_validation_te st_user_guide.pdf Test Code https://git.allseenalliance.org/cgit/compliance/tests.git/https://git.allseenalliance.org/cgit/compliance/tests.git/

7. 26 August 2015 AllSeen Alliance 7 Validation – how to collaborate and get help? 1. Best: fastest way to get a response is to submit it via Jira for C&C project > v14.02 > "Create Issue", component: frameworkhttps://jira.allseenalliance.org/browse/ASACOMP/fixforversion/10101https://jira.allseenalliance.org/browse/ASACOMP/fixforversion/10101 2. Better: Use Ask. Add tag “validation” to your questionhttps://ask.allseenalliance.org/questions/query:validation/https://ask.allseenalliance.org/questions/query:validation/ 3. Good: email allseen-cc@allseenalliance.org ?allseen-cc@allseenalliance.org Feedback: docs are too self-referential. Needs to give links, paths, etc. Mike Young will provide a specific list as he runs into these issues dependency/libs folder to build the tool, readme that lists jars but there are no jars, etc. Presumes everyone has knowledge of where everything is, already knows project User Guide on Wiki is open source just like the code. Fix the doc, Fix the code! Thanks in advance https://wiki.allseenalliance.org/compliance/overviewhttps://wiki.allseenalliance.org/compliance/overview

8. 26 August 2015 AllSeen Alliance 8 How can members test the test tool? 1. To try the test tool, you need something that it can run against, a Device Under Test (DUT). Right? 2. What if someone does not yet have an AllJoyn enabled prototype or product they can use as a DUT? 3. Should they use Arduino Yun as the DUT while developing & testing the validation tool? Or is there something else? 4. What source code / samples should someone use for DUT so they can run the validation tool against something? Is there code already used that could be shared for use as DUT? Mike Quon mquon@qce.qualcomm.com runs hackathons, will help with Arduino Yun AllJoyn code to create a DUT though Yun is not powerful enough to run all services. Probably better to make this DUT app a Raspberry Pi or desktop app, using the Linux “standard client”. If members create Linux DUT app, then LF can build the binary for download from allseenalliance.orgmquon@qce.qualcomm.com Ideal would be get a download image for SD card or flash the device. See what Mike Quon has. Brian Spencer too. Change User Guide to Wiki content (longer term it should be HTML web content?)

9. 26 August 2015 AllSeen Alliance 9 Extending our “homework” ask to all members For Phase 0 before going live with Phase 1 1. Need LF to build the Android app self-validation test. Please help ryan@linuxfoundation.org ryan@linuxfoundation.org 2. It is not realistic to expect every members to build their own Android validation app. Right? And could introduce errors into the process? 3. Plan is to email all members (or everyone on mail list?) asking them to do “homework” as a dry run before launching Phase 1. –If serious bugs / gaps are encountered, can QCE fix them? 4. Send test results and feedback to allseen-cc@lists.allseenalliance.orgallseen-cc@lists.allseenalliance.org 5. Use “Ask” forum for technical support https://ask.allseenalliance.org/questions/ https://ask.allseenalliance.org/questions/

10. 26 August 2015 AllSeen Alliance 10 Your Feedback on self-validation test “homework” 1. What your result? 2. What was good about the process? 3. What should be improved? 4. Do you think the validation tool is ready to ask our members to try it? Note: feedback from LF developer was difficulty building this Android app

11. 26 August 2015 AllSeen Alliance 11 Validation Tool sample output log

12. 26 August 2015 AllSeen Alliance 12 Sample output log from Validation Tool from the PC and from Nexus 7 of running a test case. Towards the end the Logcat file indicates if the test case passed –05-19 12:33:26.570: I/TestRunner(4663): passed: testAbout_v1_01_AboutAnnouncement

13. 26 August 2015 AllSeen Alliance 13 C&C Working Group Information To access the wiki page please go to https://wiki.allseenalliance.org/compliance/overviewhttps://wiki.allseenalliance.org/compliance/overview To contact the Certification and Compliance Work Group, send an email to the allseen-cc@lists.allseenalliance.org allseen-cc@lists.allseenalliance.org To join the Certification and Compliance Work Group Mailing List, please self-subscribe at https://lists.allseenalliance.org/mailman/listinfo/allseen-cc. C&C WG meetings every week –The meeting will be held on: –Wednesdays 20:00PM - 21:00PM Eastern Time –Wednesdays 17:00PM - 18:00PM Pacific Time –Thursdays 9:00AM - 10:00 AM Korea/Japan –Thursdays 1:00AM - 2:00 AM France

14. 26 August 2015 AllSeen Alliance 14 Thank you Follow us on For more information on AllSeen Alliance, visit us at: allseenalliance.org & allseenalliance.org/news/blogs