WP8 Pilot Design, Execution & Evaluation

WP8PilotDesign,Execution&EvaluationL EADER : B IOASSIST

INVOLVEDPARTNERS: CREATENET,IMINDS, ATOS, JOLOCOM,UNI PASSAU, SKYWATCH,MOB ISTAR , INR IA, EUROTECH

AGILEMEETING,14-15April2016,Athens

WP8– Timeline

Milestones:◦ MS1(M9)- AGILEInitialDesign&DraftFrameworkRelease◦ MS2(M18)- MS2AGILEFramework(SWandHW)release&InitialIntegration◦ MS5(M36)- FinalProjectOutcome&ExploitationReport

Deliverables:◦ D8.1PilotDesignandanalysisrequirementsandspecification(M9)◦ D8.2InitialPilotComponentsDevelopment&DeploymentReport(M18)◦ D8.3FinalPilotDeployment&EvaluationReport(M36)

14-15April2016 AGILEMEETING,ATHENS 2

• ScenarioOverview• BusinessView• ScenarioRationale• Storyline• Users,StakeholdersandRoles

Done

• HWSpecifications• DataAspects• CommunicationTechnologiesandProtocols

• ExternalCloudEndpoints/Services

• SecurityandPrivacy• Risks

Ongoing• UseCases• PilotArchitectureandComponentDescriptions

• RequirementsDefinition• Administrativeprocedures• KPIs

To-do

StatusDefinitionofthescenariosandIoT Testbed

5+1shareddocumentswhichwillbethebasisforD8.1


WP8NextStepsSynchronizerequirements’ specificationwiththeotherWPs

DefineofUseCases/Diagrams

Designthecomponentsandoverallarchitectureofeachpilot

IdentifyKPIs

Developmentofplanforpilotpreparation/operation/evaluation◦ UserRecruitment◦ Locations

DevelopmentoftheoverallmethodologyforWP8forthepilots


HardwareRequirementsMakersVersion

PilotA PilotD PilotB PilotE

BLE Weight /Volume/PowerWiFi WiFi /3G/4G 3G/4G

DisplayStatus GPSDataVisualization Compatiblewithsensors:

1)Stationarysensors(Libelium)*2)Eartag sensorsforanimals(Fastcom)

Swappablesensormodules forshields:1)multigas2)radiation

ConnectionwithHD/infraredcameraConnecttothecontrollerofthedroneproxyMAVLink messages.


HardwareRequirementsIndustrialversion

◦ Modularity forsensingandconnectivity.◦ Support formultipleWAN/LANconnectivityoptions.◦ Support forawiderangeofenvironmentalsensingmodules.◦ withpre-calibratedsensorconditioning.

◦ Timestampandoptionalgeo-localizationinformation.◦ Fanless thermaldesign.◦ Maximumpowerconsumption5W.◦ Extended temperaturerangesupport(target-20+70°C).◦ Small,highlyintegrated.◦ Maximumsize:board180x100x50mm(LxDxH).


PilotAQuantifiedSelf


RequirementsHardware◦ BLECommunication◦ Displaystatus/datavisualizationData◦ Handledifferenttypesofdataandsources◦ e.g.biosignal sensors/smartwatches

◦ Cloudplatforms/servicesfromapplicationprovidersaredatasources◦ e.g.Misfit,GoogleFit

◦ Basicprocessingonthegateway,advancedprocessingontheCloud◦ buildtheuserprofileandidentifytrends,risksetc.

◦ Datasharingofrawandprocesseddatawithotherusers◦ Friends,Relatives,Healthcareexperts

Security◦ Userincontrolof◦ whattoshare◦ withwho,◦ when(adhoc/automatically/periodically)


PilotA

OpenIssuesDatasharingprocess◦ Considerdatatypes/APIs◦ Specifications(OpenmHealth)◦ Sharetoapps/platforms

◦ OngoingdiscussionswithJolocom

Directcommunicationofsmartwatches/activitytrackerswiththegateway◦ Typicallydonethroughcloudservices

UseofTUGrazrecommenders?


PilotA

NextStepsDetailedanalysis,categorizationandspecificationofthepilotrequirements

DefineofUseCases/Diagrams

Designthepilotcomponentsandoverallarchitecture

IdentifyKPIs

Developmentofplanforpilotpreparation/operation/evaluation◦ UserRecruitment◦ Locations


PilotA

PilotBOpenField&CattleMonitoring

Dynamic IoT Sensor Use Case

Stationary IoT Sensor Use Case


UseCases:Win/Android

ExampleofUser-Interface DynamicIoT Sensorsonanimals StationaryIoT Sensorsontheground

PilotB


Requirements(1/2)Hardwarerequirements:◦ AgileGateway(Makers)

◦ Stationarysensors(Libelium)*◦ Eartagsensorsforanimals(Fastcom)

◦ OwnHardware◦ Cumulus◦ Huginn◦ Windowstablet

PilotB


Requirements(2/2)Softwarerequirements:◦ APIforDataPresentation(GUI)◦ VPNTunnelling

Securityrequirements◦ Encrypteddatalink◦ Encryptedonboardstorage◦ Datashouldbeaccessible troughanauthenticatedcloudservice

PilotB


Pilot1:StationarySensor◦ Pilot2b– EyeintheSky◦ BasedonWater samplesdetectionofminingactivities intherainforest

PilotB


Pilot2:DynamicSensor◦ Pilot2a– Hofmansgave Gods◦ 7acres◦ 50+Cows

◦ Pilot2b– KarenBlixenCamp◦ 100+animals◦ Elephants,Rhinos,Cattle

◦ 30.000acrearea◦ Supportfromnationalconservatory◦ MaraNorth60.000animals

PilotB


OpenIssueso RegulationandFlightpermissions

o GroundBasedSensors

PilotB


NextStepso GetsignedLetterofIntentsfromPilotPartners

o MoredetailedprojectplanforavailabilityofGatewayforintegration

o RolloutplanforPilots

PilotB


PilotCAirqualityandpollutionmonitoring


Requirements(Preliminary)basedontheindustrialversionofthemodulargateway◦ Modularityforsensingandconnectivity.◦ SupportformultipleWAN/LANconnectivityoptions.◦ Supportforawiderangeofenvironmentalsensingmodules.◦ withpre-calibratedsensorconditioning.

◦ Timestampandoptionalgeo-localization information.◦ Fanless thermaldesign.◦ Maximumpowerconsumption5W.◦ Extendedtemperaturerangesupport(target-20+70°C).◦ Small,highlyintegrated.◦ Maximumsize:board180x100x50mm(LxDxH).

PilotC


SoftwareRequirements◦ Yocto Linux◦ Kura◦ KuraWires◦ Everyware Cloud◦ EclipseOSGi Equinox◦ EclipsePaho◦ RedHatJBoss◦ ApacheCamel◦ HyperSQL

Protocol:◦ MQTTS

PilotC


OpenIssuesandNextStepsOpenissues◦ Scenariostill tobeconfirmed.◦ Newmeetingplannedfor20ofApril.

Nextsteps◦ Consolidatethescenarios,◦ definetheusecasesand◦ …finalizethePilotdescription.

PilotC


PilotDEnhancedRetailServices


Requirements(1/3)Hardwarerequirements:◦ AgileGateway◦ RaspberryPi3modelBforBeaconsmartnetworkhttps://www.raspberrypi.org/products/raspberry-pi-3-model-b/

◦ Kontaktbeacons https://kontakt.io/◦ Wirelesssmartbuttonforfeedbackwithoutsmartphone https://flic.io/

◦ AndroidSamsungS6ornewersmartphone◦ CloudretailerservicesdeployedonAmazonAWS

PilotD


Requirements(2/3)Softwarerequirements:◦ Node.jsonRaspberryPinodes.◦ DockerwithsnappyforappsdeployedonAGILEGateway.◦ JEEfortheservicesdeployedonAmazonAWS.◦ AngularJSonBackoffice userinterface.◦ Ioniconsmartphone customerapplication.◦ MongoDBonretailerserverstorage.

PilotD


Requirements(3/3)Securityrequirements◦ Weonlymanage anonymousdatafromcustomersatourtrackingsystem.◦ Users’personalinformationcanonlybeaccessedthroughappsusingHTTPSandauthenticationandauthorizationmechanisms basedonOAuth2.

◦ Backoffice accesses datausingthesamesecuritysystemthanmobileappisusing.◦ NobodycanaccessdatainGateways.It’stheGatewayitselfwhosends itsdatatoexternalsystems.ItwillalsoperformpollinginconfigurationandnotificationtaskstoIoT devicesduringthePilot.

Protocolsandcommunications◦ SystemusesHTTPSforallcommunicationsbetweennodes.◦ Nodeswillusecertificates inordertocreateatrustnetworkbetweenserversandavoidingthiswayman-in-the-middle attacks.

PilotD


UseCase:SnappyFunctionalSnappyModules:◦ SmartiBeaconnetwork(mandatory).NetworkmanageriBeacons /Raspberriesthatmonitorsthestatusofallnodesandtheinformationtheygeneratewhentheydetectthebeaconsassociatedtocomponentssubjecttomonitoring

◦ Employeetracker. Identificationandmonitoringofemployees associated iBeacons.

◦ Customertracker.Identificationandmonitoringofshoppingcartsassociated iBeacons .

◦ CustomerQueues listener.ReceivertomeasurethewaitingtimefortheIbeaconsshoppingcarts.

◦ CustomerFeedbacklistener. ReceiverModuleofSmartbuttonsFeedback.◦ RetailerFeedbacknotification listener. Indoormoduletopushnotificationsfeedbacksreceivedbysmartbuttonsorexternalservers.

PilotD


UseCase:AndroidAppMainusecases:◦ Welcomenotification.◦ Indoorlocationshoppinglist.◦ IndoorlocationPromotionorsuggestions.◦ WhereIam?◦ Informationpoints(Nearorabsolutelocation.◦ Cashierstatus.◦ Feedback.

PilotD


OpenIssuesoSetupandtestthedevicenetwork

oToconfirmtheRetailertooperatethepilot.Eroski?http://www.eroski.es/

PilotD


NextStepso DefineindeepdetailtheUsecasesfortheAgileGateway

o DefineindeepdetailtheBusinessUseCasesoftheRetailerfunctionality

oDefinetheobjectivesandKPI’stoassess thePilotimpact

oTechnologyassessmentofthepilotscenario(SetupandTestaprototype)

oFollowupAgileGatewayevolution(capabilities,functionality…)

oConfirmtheRetailer

oDefineaprojecttimelineandprojectplanforthePilot

PilotD


PilotEPortAreaMonitoring forPublicSafety• Sensorsonthedronewillcapturetheinformationandsenditover4Gtowardstheapplicationviathegateway.

• Userscanviewthedataviatheapplication.

• Withtheapplicationuserscansendrequeststothedroneover4Gviathegateway


PilotE

RequirementsHardwarerequirementsagilegateway

• Communicationshouldbedonevia3G/4G.• Sensormodulesshouldbeswappable(wirelessorconnectionbay).• ConnecttothecontrollerofthedroneproxyMAVLinkmessages.• ConnectionwithHDcamera.• Connectionwithinfraredcamera.• Connectiontothemultigas sensorshield• Connectiontotheradiationshield

PilotE


RequirementsHardwarerequirementsdronesfinalproduct

• Carriageload:•Minimumsafeflighttime:• Speed:•Maxrange:

>1kg35min>60km/h20km

PilotE


RequirementsDatamanagement

• Storecameraimagesandsensordataongatewaywhen4Gisnotavailable.• Nouserdataistransmittedviathegateway.• Datacannotbeaccessedbyusersdirectlyonthegateway.• DataonlyavailableviaAPI’s forinstanceswhichareallowedtoconsultthedata.

PilotE


RequirementsSecurityrequirements

• DatawillonlybeavailablethroughRESTful API’s foraselectednumberofapplications.• Userscanonlyaccessdataviatheapplication,andonlydatawhichtheyhaveaccessto.

PilotE


OpenIssues• Dronerequirementsdonotmatchdronespecifications.• Itisgoodenoughforaproofofconcept,butnotforafinalproduct.• NotyetclearwhereBelgianlegislationstandsatthemoment.• Notclearwhichbudgettouseforthehardware.

PilotE


NextSteps• Describethedifferentusecasesindetail• DefinetheobjectivesandKPI’s.• Determinetestsite.• Discussthedronerequirements.

PilotE


IoTTestbed§ HWandSWInfrastructurealreadyinplaceforremote,bare-metalaccessto2700+IoT-devices.

§ OnlinetoolsforIoTnodefirmwareupload,experimentconfiguration,experimentresultsdownload.


PlannedTestbed ExtensionUSBplugged-inAGILEgatewayhardwareonIoT-LABhostA8-M3nodes

Blue:userlandYellow:adminGreen:userland extension

IoTTestbed


RequirementsSW:thetestbedoffersbare-metalaccesstoIoTdevices,sothereisnoSWrequirementsonIoTdevices.Nospecificreq.onAGILEgatewaySWeither(except:mustbeabletorunonAGILEhardwaree.g.RasPi)HW:IoTdevicesarecurrentlyIEEE802.15.4onlyonthetargetedIoT-LABsite=>AGILEgatewayshouldhaveaIEEE802.15.4communicationmodule(whichmaybeaUSB-connectedboardrunningRIOT).Securityrequirements:◦ sshtunnel toAGILEgateway,whereAGILEinterfacescanbeused(andcorresponding securityconsiderationsapply).

◦ Bare-metalaccesstoIoT-devices:e.g.RIOTfirmwarerunning onIoT-LABM3nodes,withIPv6/6LoWPAN/RPL/UDPstack(andcorresponding securityconsiderationsapply).

Datamanagement,post-processingandvisualization:uptothetestbedusers.Outofscopeforthetestbedtools.Pre-processingpossibleontheIoT-devices(programmableinthefirmwareuploadedonIoTdevicese.g.RIOT)


IoTTestbed

OpenIssuesFrameworktoavoid user-initiated file-system«bricking» onthegateway◦ BasedonNFSboot?

Finaldecisionbetweenseveralpossiblelevelsofintegration:◦ Level 1:adding newIoTdevices toIoT-LAB(connecting them through USBtooneoftheA8-M3nodes)

◦ Level 2:adding newgateways toIoT-LAB(e.g.AGILEgateway)◦ connecting viaanexisting OpenA8- maybeUSB-Ethernet◦ connecting totheprivate EthernetofIoT-LABlocalserve◦ alternative:connect viaanadditional private server,with anadminVMdedicated toAGILE.

◦ Level 3:modifying SW(currently acustomized OpenEmbedded - Yocto Daisy)onIoT-Lab A8nodes so that they become anAGILEGateway,e.g.usingSnappy


IoTTestbed

NextSteps§ PluginAGILEhardware(makerversion):RasPi +802.15.4module

§ Auto-configurationofglobalIPv6addressesonAGILEgateway

IoTTestbed


Thankyou!
