Partnerforasmarterfuture

LoRaOverview

CERN7/11-17,JorgenMortensen

ABOUTORBIWISE

C o n t r i b u t o r M em b e r

•  HeadquarteredinGeneva,Switzerland.

•  OfficesinIndia,Macedonia,USA–soonAsia.•  Extensiveexperienceinwirelesscommunication,especiallycellular.

•  IndustryleadingLoRaWANTMNetworkServerSoftware-OrbiWANTM.

•  Customers-anycompanywantingtodeployaLPWAnetwork,e.g.

•  ICondor/Yeap!:ArgentinianNationwideLoRaTMNW.

•  Eleven-X:CanadianNationwideLoRaTMNW.

•  TataCommunications:IndianNationwideLoRaTMNW.

•  PervasiveNation:IrishNationwideLoRaTMNW.

..

•  Privatenetworks/Enterprisesegment

C o n t r i b u t o r M e m b e r

C o n t r i b u t o r M em b e r

Overview•  LoRa™:PhysicalLayerforLOngRAngecommunication,definedby

Semtech.

•  LoRaWAN™:MACProtocolLayerontopofLoRa™,definedbytheLoRa-Alliance,forforLowPowerWideAreaNetworks(LPWAN).

•  LoRa-Alliance:Eco-systemaroundtheLoRa™Technology

•  500+companiesincluding:Applications&devicesmakers,Networkoperators,GWmanufacturers,CorenetworkSWproviders,etc

•  Anopen,non-profitassociationofmembers(http://lora-alliance.org/)

•  DefinestheLoRaWANspecifications

•  DefinesDevicecertificationprogram

•  Organizeseventsandpromotionoftheeco-system

LoRa™

C o n t r i b u t o r M em b e r

•  57 Announced Public Network Operators

•  49 Alliance Member Operators

•  Over 100 Countries

•  350+ on-going trials & city deployments

•  500+ members in the Alliance

November 2017

All information contained herein is current at time of publishing – LoRa Alliance is not responsible for the accuracy of information presented

LoRaWAN™NetworkCoverage

C o n t r i b u t o r M em b e r

IoTuse-cases,Howtogenerate“data”

AdvancedRadio

q Adaptive Radio q Multiple Device

Classes q Roaming q Geo-location q Multicast

LoRaWANTM Network Features

LongRange MaxLifetime

q Greater than cellular q Deep indoor coverage

q Low-power q >10yr on AA cell q >10x vs cellular M2M

LowCost

q Minimal infrastructure q Low-cost end-devices q ISM RF band

C o n t r i b u t o r M em b e r

LoRaWANnetwork

C o n t r i b u t o r M em b e r

Modulation:ChirpSpreadSpectrum(&FSK).

•  Constantenvelope

•  Relative“Wide-band”,lesssensitivetomultipathfading

•  LesssensitivetofrequencyerrorandDopplereffect

Spreadingfactors:SF7-SF12

•  2SFchirps/symbol

•  Chirprate=BW

•  demodulationpossibledownto-20dBbelownoisefloor(<-143dBm)

MultipleBandwidth:

•  125KHz,250KHzand500KHz(notusedEU)

ForwarderrorcorrectionandCRC

LoRaAirInterface

(Imagesource:LinkLabs

C o n t r i b u t o r M em b e r

Rangebetweengatewaysanddevices

•  3-5kminurbanareasonaverage,dependinggatewayposition.

•  typical>10kminruralareas.

Exampleofmessagetransmissiontime(UL)for20bytepayload(includingheader,FEC,CRC,etc)

•  SF7=>Transmissiontime=57mSec.

•  SF12=>Transmissiontime=1.3Sec.

Maximumpayloadsizepermessage(EU):

•  59bytes–250bytesdependingonSpreadingFactorused.

LongRange–andlowdata-rates.

C o n t r i b u t o r M em b e r

DeviceAdaptiveData-Ratetooptimizebatterylife&radioresource

•  SF,TXpower,TXrepetition

•  Controlledbythenetworkserver

Encryption(AES)

•  EndtoEndPayloadencryption

•  NetworkProtocolCommunicationauthentication/encryption

ISMBand(i.e.regiondependent),ForEUregion:

-  ISMband:863-870MHz(433-434MHz)

-  MaximumTXpower-  14dBm,

-  27dBmfor869.525MHz27dBm(usedforDLonly)

-  Duty-cyclelimitations0.1%-10%dependingonchannel

LoRa

11

Q3-2017Confidential

Optimizing transmission with Adaptive Data-Rate

Ba?eryusagecoefficientSF

7 8 9 10 11 12

TxPow

er[d

Bm] 2 1.0 1.8 3.2 5.6 11.2 22.4

5 1.0 1.8 3.2 5.6 11.2 22.48 1.1 2.0 3.5 6.1 12.3 24.611 1.3 2.4 4.2 7.3 14.7 29.414 1.6 3.0 5.3 9.2 18.4 36.917 2.2 4.0 7.2 12.6 25.1 50.2

FromIMSTdatasheetforcurrentconsumption&LoRa™calculatorfortimeonair

C o n t r i b u t o r M em b e r

EndDeviceclasses:

•  A:Deviceinitiatedcommunication.Downlink(todevice)onlypossibleafterUplink.Lowestpowerdevices.(Aloha)

•  B:Devicetime-synchronizedtoacommonbeacon.Additionaldownlinkpossibleinscheduled`ping-slots`.

•  C:Downlinkalwayspossible.Nodownlinklatency.

MulticastispossbleforclassB&Cdevices

Deviceclasses–forlowpower

LoRa-Based Geo-location

Confidential

AnyLoRadevicecanbegeolocated.NoneedforadditionalHWorSWindevice.

Lowestpowerconsumption.Devicescansurviveonsmallbatteryforyears.

LocationserverusingTDOA,RSSIandotherdatatolocatedevicesviaadvancedalgorithms.

Spatialdiversityand�high�GWpositionimportant

forgoodresults.

Zero-Cost Geolocation

Cloud-basedNetworkServer&

LocationServer

Batterylife(givenbattery)

Accuracy

LoRaGeoLoc

GPSA-GPS

LoRa Network Server 14

Q3-2017

Confidential

Application Servers

Application Enablement

platforms

ControlledwithDASSWEB-UIorRESTAPI

ControlledwithO&MWEB-UIorRESTAPI

Radio Network Sub-system Data Access Sub-system

OrbiWANExt.Join Servers (HSM)

(Optional)

IP

Cellular Ethernet

Wifi

OW-API MQTT Kafka Etc.

Other NW

orbiwan™

World-Class,Carrier-GradeLoRaWAN™

NetworkServerSolution

ORBIWAN LORASERVERFEATURES

SupportforallLoRaWAN™v1.0.2features

-LoRaWAN™v1.1soon!

SupportfordeviceallClassesA,BandC

Monitoring&ManagementofDevices,Gateways,

Servers,Application/AEP

Interfaces

AdditionalSecurityandSoftware(JS,AEPs,

Billing)Partner

Solutionsavailable.

Gatewayconnectionviacellular(e.g.LTE/

3G/2G)orEthernet

LoRa™-basedLocalization/

Geolocationfully

supported!

FullMulti-tenancysupport ComprehensiveTrace&Reportingsystem

C o n t r i b u t o r M em b e r

LoRaishere•  AprovenviablesolutionforLPWANIoTsolutions

•  Devices,Gateways,Networkservers,Applicationsareavaliable

•  VeryActiveEco-system

•  Networksrollingout

Use-casesinnovate!!

FORASMARTERFUTURE

PARTNERWITH

Copyright © 2017 OrbiWise SA - Geneva, Switzerland - All rights reserved.

PHY layer definition •  Europeanregulation:ETSI[EN300.220]

•  Frequencybandsfrom863to870MHzwithoutlicensebutwithlimitationonthedutycycle(averagetransmittimeperunitoftime)•  10%dutycycle/500mWfrom869,4to869,7MHz

•  1%dutycycle/25mWfrom868to868.6MHz

•  0.1%ducycycle/10mWfrom863to870MHz

•  Defaultfrequencychannels:868.1868.3868.5MHz

•  DefaultRx2Window:869.525MHzwithSF12

•  Otherbandssupportedforotherregions(US,Asia,…)

Types of messages & commands •  Uplink/downlinkmessages

•  Uplinkmessagesaresentbyend-devicestothenetworkserver

•  Downlinkmessagesaresentbythenetworkservertotheend-devices.

•  Messagetypes:Confirmed/unconfirmed/proprietary•  Datamessages(bothdownlink&uplink)canbeconfirmedorunconfirmed.Aconfirmed

messagehastobeacknowledgedbythereceiver.

•  Proprietarymessagestypecanbeusedtoimplementno-standardmessageformats.

•  MACcommands•  Networkcommandsaddedtoamessageorsentinaseparateframe,basedonrequest/answer

betweenend-deviceandnetworkserver

LinkCheckReq/LinkCheckAnsLinkADRReq/LinkADRAnsDutyCycleReq/DutyCycleAnsRXParamSetupReq/RXParamSetupAnsDevStatusReq/DevStatusAnsNewChannelReq/NewChannelAnsRXTimingSetupReq/RXTimingSetupAnsTxParamSetupReq/TxParamSetupAnsDlChannelReq/DlChannelAns

ClassBDedicatedcommandsPingSlotInfoReq/PingSlotInfoAnsPingSlotChannelReq/PingSlotFreqAnsBeaconTimingReq/BeaconTimingAnsBeaconFreqReq/BeaconFreqAns

Q3-2017Confidential

LoRaWan Message Format 20

Note:Maxsizeofapplicationpayloaddatadependsonspreadingfactorusedandregionalrestrictions.IftheapplicationusepayloadslargerthanthemaxsizeforcurrentSF(orMAXSF),theapplicationandthedevicemusthandlethepacketsegmentationandassembly.

*Onlyinuplink

MessageIntegrityCode

Fport0(zero)usedforMACpayload

Preamble PHDR PHDR_CRC PHYPayload CRC*

MHDR1 Byte

Mtype | RFU | Major

MACPayload

MIC4 Bytes

FHDR7 to 22 Bytes

Fport1 Byte

FRMPayloadApplication Data*

DevAddr Short address 4 Bytes

FCtrl 1 Byte

ADR | ADRACKReq | ACK | Fpending | FOptsLen

FCnt 2 Bytes Seq #

Fopts 0 – 15 Bytes

Optional MAC commands

Q3-2017Confidential

MAC commands in Messages 21

•  MACcommandscanbetransportedeitherin:

•  FopsfieldoftheFrameHeader

•  ThisisthecaseiftheMACcommandissmallerorequalto15bytes

•  TheframepayloadandencryptedwithNwkSKey

•  ThisisthecaseiftheMACcommandislargerthan15bytes

Q3-2017Confidential

Device identification & authentication •  DevEUI–UniqueEnd-DeviceIdentifier

Uniqueidentifieroftheend-device–format:IEEEEUI64

•  AppKey–ApplicationKeyAES-128applicationkeyspecificfortheend-deviceusedtoderivethesessionkeys:AppSKey&NwkSKey

•  AppEUI–“Application"identifier(JoinEUIinv1.1)PointingtoanoptionalexternalJoinServer(standardizedinLoRaWan1.1)

KindofMACaddress

JoinServerIdentifier,currentlynotused

Q3-2017Confidential

Device identification & authentication •  DevAddr–End-DeviceAddress

Identificationofthedeviceonthecurrentnetwork,usedineachframetoandfromtheend-device,generatedbyOrbiWANduringthejoinprocess.

•  NwkSKey–NetworkSessionKeyDevicespecifickeyformessagecalculatingtheintegritycode(MIC)andforencryptionMACpayloadmessages.GeneratedfromAppKeyandtworandomnumbers(renewedateveryjoinsession).

•  AppSKey–ApplicationSessionKeyDevicespecificencryptionkeyforapplicationpayloadmessages.GeneratedfromAppKeyandtworandomnumbers(renewedateveryjoinsession).

•  MIC–MessageIntegrityCodeSignaturecalculatedoverthe“NW”partofthemessageusingtheNwkSKey,DevAddr,FCNT,etc

KindoflocalIPaddress

Q3-2017Confidential

Device activation on the network

•  OverTheAirActivation(OTAA)•  End-devicefollowsajoinprocedurepriorexchangingdatawiththenetworkserver.

•  Pros:devicecanattachanyLoRanetwork,securitykeyscanbeupdatedfromtimetotime(sessionbased).Devicerebooteasilydetected.

•  Cons:applicationserverhastoanswertojoinrequestseachtimeadevice(re)starts,generatingmoredownlinktraffic.

•  ActivationByPersonalization(ABP)•  Theend-deviceisalreadypre-registeredonthenetwork.DevAddr,NwkSKey&AppSKeyarestored

intheend-deviceandNetworkServer.

•  Pros:simplerfromapplicationserverpointofview

•  Cons:nodetiedtoaparticularnetworkormustberegisteredwithexactlythesamekeys.

Q3-2017Confidential

Device „Join“ by ABP, class A, B & C 25

Q3-2017

26Join procedure, Application, OTAA

Q3-2017