Implementing Eddystone™ Bluetooth® Smart ... - …

1 1 SWRA491A September2015 RevisedOctober2016 SubmitDocumentationFeedbackCopyright 2015 2016,TexasInstrumentsIncorporatedImpleme ntingEddystoneBluetoothSmartBeaconsUsing the TI BLE-StackApplicationReportSWRA491A September2015 RevisedOctober2016 ImplementingEddystone Bluetooth SmartBeaconsUsingthe TI BLE-Stack ChesterKimABSTRACTT hisapplicationnotedescribesthe basicconceptof Eddystone Beacon,howconnectablebeaconapplicationsc an be implementedon top of the existingsampleapplicationSimpleBLEP eripheral,and howthe compatibilityto Eddystonespecificationcab be ,callbacks,and usagesof hardwaredriversfor obtaininginformationto populatethe of of ,SimpleLinkare trademarksof a registeredtrademarkof a trademarkof Google, othertrademarksare the propertyof September2015 RevisedOctober2016 SubmitDocumentationFeedbackCopyright 2015 2016,TexasInstrumentsIncorporatedImpleme ntingEddystoneBluetoothSmartBeaconsUsing the TI BLE-Stack1 IntroductionAs describedin theBluetooth low energyBeaconsApplicationNote(SWRA475), a Bluetooth lowenergy(BLE)

2 Beaconis a devicebroadcastinga non-connectableadvertisingpacketcarrying smallpiecesof informationto the timingand the informationconveyedwithinthe packet,beaconscan enablea varietyof use cases,includingbut not limitedto proximityawareness,synchronization,ident ification,or just protocolor formatfor how the beaconis implementedin a example,Applehas definedthe iBeaconprotocol,availableunderan MFi license,for usewith iOS is an openbeaconprotocolspecificationfromGoogl eaimedat improvingproximity-basedexperiences,with supportfor bothAndroidand iOS specifyingvariousbeaconpayloadformats,de finedas frames-types,as well as acorrespondingset of APIsusedto accessthesepayloadsfromthe smartdevice(suchas an Androidsmartphone).

3 This applicationnotedescribeshow to implementan exampleEddystonebeacondeviceusingthe TI BLE-Stack the SimpleLink lowerpowerconsumptionand wideoperatingvoltagecapabilitymakethe CC2640an idealplatformfor , by definition,broadcast-onlydevices,the conceptof a connectablebeaconwill beaconentera connectablestate(technically,switchingfr omthe GAPbroadcasterto the peripheralrole)is desirablefor the purposesof provisioningand updatingthe metadataof Eddystoneprotocoldefinesa modethat allowsthe beacondatato be updatedby projectfiles and the sourcecodefiles createdor modifiedfor EddystoneBeacondeviceimplementationare availableas a GitHubrepository.

4 Whichcan be foundon the TI BLE energyCCSCodeComposerStudioIDIdentifierG APG eneralAccessProfileMCUM icrocontrollerOADO verthe Air DownloadSDKS oftwareDevelopmentKitTI-RTOST exasInstrumentsRealTimeOperatingSystemTL MT elemetryTXTransmissionUIDU niqueIdentityURLU niformResourceLocator3 ObjectiveThis applicationshowswhatmustbe implementedon top of the existingSimpleBLEP eripheralsampleapplicationto makea Prerequisites3 SWRA491A September2015 RevisedOctober2016 SubmitDocumentationFeedbackCopyright 2015 2016,TexasInstrumentsIncorporatedImpleme ntingEddystoneBluetoothSmartBeaconsUsing the TI BLE-Stack4 ProjectOverviewand PrerequisitesPriorto followingthe examplesdescribedin this applicationnote,the designershouldhavea detailedunderstandingof the TI BLE-StackSDKas describedin the SW Developer s Guide(SWRU393), theBluetoothlow energyBeaconsapplicationnote(SWRA475)

5 , and the GoogleEddystoneprotocolspecification,whi chcan be foundat sampleapplicationSimpleEddystoneBeaconre quiresTI IDEscan be usedto buildthe SimpleEddystoneBeaconprojectrunson the optionalsmartphoneand test applicationcan be usedto validatethe TI GitHubrepositoryble_examplesincludesthe minimumnumberof files necessaryto buildtheprojectwhenthey are put on top of the repositoryconsistsofprojectand workspacefiles for IAR/CCS,as well , whichare for the application, , installthe SimpleEddystoneBeaconproject,copythe followingfoldersinto the appropriatedirectoriesin the SDK.

6 Ble_examples/examples/cc2650lp/simple_ed dystone ble_examples/src/examples/simple_eddysto ne/cc26xx ble_examples/src/profiles/EddystoneURLCf g5 Designand Eddystoneprotocoldefinesthreeframe-typef ormats(referredto as frames ), whichare transmittedby the beacondeviceas describedin EddystoneFrameFormatsFrame-typeDescripti onUIDU niqueidentifierthat can identifya URL,suchas , that canbe launchedby the ,suchas batteryvoltageand temperatureof the describedin moredetailin the advertisingpacket,up to the maximum31-bytepayloaddefinedby the EddystoneBeacondefinestwo modesof operation.

7 Regularadvertisingmodeand an relatedby five regularadvertisingmode,the beaconoperatesas a traditionalbroadcastersendingnon-connect ableadvertisementsconsistingof UID,URL,or URLconfigurationmode,the beacontransmitsconnectableadvertisements to allowa clientto connect,and if authorized,updatethe URLcontentandthe systemparametersthroughthe operatingstatetransitionsfor thesemodesof operationare depictedin Figure1, alongwith thecorrespondingactionsusedto transitionstatesin the a greycirclerepresentURLconfigurationmode, whilethe Eddystoneprotocoldoesnot specifythe type,when,or how oftena particularframeis transmitted,orthe actionsthat triggera ,for example,transmitonly URLframes,or a combinationof all UID FrameAdvertising URL FrameConfig Mode AdvertisingAdvertising TLM FrameConnectedStartRIGHT btn pressRIGHT btn pressLEFT btn pressLEFT btn pressConnection EstablishedConnection TerminatedPacket Cnt % 10 == 0 Packet Cnt % 10 == 0 Return to last stateReturn to last stateDesignand September2015 RevisedOctober2016 SubmitDocumentationFeedbackCopyright 2015 2016.

8 TexasInstrumentsIncorporatedImplementing EddystoneBluetoothSmartBeaconsUsingthe TI BLE-StackFigure1. SimpleEddystoneBeaconOperationModeTransi tionsIn this design,the beacondevicesendseitherUID framesor URLframesregularly,and TLMframesintermittently,whilein statetransitionsbetweenUID and URLare toggledby a practicalreasons,TLMframesare expectedto be observedless frequentlythanUID or URLframes,so in this design,they are sent only every10thadvertiseof UID or be enteredby enteringthe configmodeadvertisingstatein this istriggeredby a be causedby a LEFT buttonpress,orany type of terminationof the.

9 The centralterminatesthe connectionwhenthebeaconis finishedupdating,to let the use a buttonpressto triggersomeof the transitions,the key eventhandlermustbe implementedslightlydifferentlyby this implementation, usedfor the any case,SimpleEddystoneBeacon_keyChangeHand ler()is registeredas the callbackand eventuallythe key eventSEB_KEY_CHANGE_EVTis handledbySimpleEddystoneBeacon_handleKey s().For the CC2650 LaunchPad,all RIGHTbtn pressescorrespondto BTN-2,and all LEFT buttonpressescorrespondto usedfor four differentpurposes,regardlessof the eachtypeof the ADVsusedin this implementationare summarizedin Propertiesof AdvertisingPacketsUID/URL/TLMF rameURLC onfigurationModeADVADVE ventTypeADV_NONCONN_INDADV_INDADVTypeFla gsBREDR_NOT_SUPPORTEDBREDR_NOT_SUPPORTED |GENERAL_DISCOVERABLEADVI ntervalFromURLCfg for UID/URL.

10 10 timeslongerfor TLMD efaultIntervalTX Implementation5 SWRA491A September2015 RevisedOctober2016 SubmitDocumentationFeedbackCopyright 2015 2016,TexasInstrumentsIncorporatedImpleme ntingEddystoneBluetoothSmartBeaconsUsing the TI BLE-StackAs switchingfromone advertisingpacketto anotherat run time is required,how to set the parameterstochangethe propertiesfor regularadvertisingmodeis describedin this get the informationto populatethe payloadof eachpacketis also shownin Table2, thereare five propertiesto be changedwhentogglingbetweenregularadverti singmodeand be configuredusingGAPRole_SetParameter()