Brkiot 1291

#CLUS
LoRaWAN for IOT

Enterprises services
Patrick Grossetete (pgrosset@cisco.com)
Distinguished Engineer, Technical Marketing
Michael Harttree, (harttree@cisco.com)
IoT Architect, US Federal
Randy Benn (rbenn@cisco.com)
Architect, US Public Sector
BRKIOT-1291
#CLUS
Agenda
• LoRaWAN Use Cases
• LoRaWAN Technology Overview
• Cisco’s LoRaWAN Solution
• Cisco LoRaWAN Deployment Considerations
• Conclusion
#CLUS BRKIOT-1291 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Cisco Webex Teams
Questions?
Use Cisco Webex Teams to chat
with the speaker after the session
How
1 Find this session in the Cisco Live Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
Webex Teams will be moderated cs.co/ciscolivebot#BRKIOT-1291

by the speaker until June 16, 2019.
#CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
Licensed and Unlicensed LPWA Landscape
3GPP LTE Cat. M1 and NB-IOT LoRa Alliance 1.0.x and 1.1 specifications
Mobile Service Provider (SP) Enterprises and Services Providers
Public Infrastructure and Services Public & Private Infrastructure and Services
Ecosystem under development Ecosystem Ready Now
What is LoRaWAN?
A disruptive wireless technology for low data rate secure communication
RF unlicensed Long Distance Low Low Power

spectrum Connectivity Data Rate Solution
LoRaWAN Use Cases
Enable Innovations
Generate New Revenues
Decrease Operating Costs

Measure Report Track
Data Events Improve Customers Satisfaction
Increase Productivity and Operations

Gather Device Data Report a State Provide Asset Location
with or without GPS
Preserve existing Assets
Gas and Water Meters Smart Parking
Measure
Customer Satisfaction Survey Environmental monitoring
#CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Optimize Waste Collection Connected Mouse Trap
Report
Events
Optimize operations and reduce busy

Physical Security time to improve business efficiency
Waste Management
https://www.ferrovial.com/en/press-room/news/dynamic-municipal-waste-collection-project-granada-spain/
Prevent Copper Spool Thefts Track Cows Grazing
Track
Optimize Shuttle Buses Use geolocation to protect

and monitor assets
#CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Cisco is a Founding Member of the LoRa Alliance
 An open, nonprofit association of members that believes the Internet
of Things era is now (https://www.lora-alliance.org)
 Mission: To standardize LPWA networks being deployed around the
world to enable Internet of Things (IoT), Machine-to-Machine (M2M),
Smart City, and industrial applications
 Cisco is a founding member and serves on the Board of Directors as
well as in the Technical Committee
 LoRa Alliance specifies the LoRaWAN protocol above the physical
layer and network architecture, and assures interoperability between
devices and operators in one open global standard
 LoRa Alliance specifications: v.1.0.2, including 1.0.2 regional RF
parameters in separate document. 1.0.3 published with additional
clean-up
 New published release (10/2017) – 1.1 Core specifications, 1.0
backend interfaces, 1.1 regional RF parameters
LoRa Alliance Update
 17 Sponsors
 64 Contributors
 339 Adopters
 16 Institutional
LoRaWAN Layered Architecture
Applications or IOT Broker (eg. Kinetic EFM, CKC,…)
SCHC
Raw others
(IETF LPWA WG)
™
LoRaWAN MAC
Class A Class B Class C
(default, batteries powered) (Beacon, batteries powered) (Continuous, powered)
LoRa PHY Modulation (developed by Semtech)
EU868 US915 AS923 India 865 AU915 RU864
LoRaWAN Adaptive Data Rate (ADR)
14km 2km 2km 14km
Spreading SF12 SF11 SF10 SF9 SF8 SF7

Factor
5496bps
Time in Air
958ms
479ms 3125bps
1758bps
240ms
120ms 977bps
60 537bps
Bitrate 293bps
30ms
• ADR maximises battery life overall & network capacity

• ADR manages the data rate and RF output for each device
Acknowledgement: Actility for diagrammatic representation #CLUS BRKIOT-1291 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
ADR, Spreading Factor and Payload
Spreading Factor Data Rate (bit/s) Time on Air (ms) Maximum Payload End-device
Size sensitivity (dBm)
SF10 980 370 59 bytes -133
SF9 1760 200 123 bytes -130
SF8 3125 100 250 bytes -127
SF7 5470 28 250 bytes -124
US915 Frequency band, @125kHz channels Upstream
US915 LoRaWAN Channels Line Up
• Upstream – 64 channels (0-63) @125 kHz BW DR0 to DR3, at 902,3+i*0,2MHz
• Upstream – 8 channels (64-71) @500 kHz BW DR4, at 903,0+j*1,6MHz
• Downstream – 8 channels (0-7) @500 kHz BW DR8 to DR13, at 923,3+k*0,6MHz
• 915-923 MHz range is not used and not defined
• Applicable to North-America and FCC aligned South-America countries
64 + 8 uplink channels 8x downlink channels
…. ….
902.3 903.0 904.6 914.2 923.3 923.9 927.5
EU863-870 LoRaWAN Channels Line Up
3 mandatory channels that all devices should implement and all gateways
should constantly receive: 868.10, 868.30 and 868.50 MHz
AS923 LoRaWAN Channels Line Up
915Mhz 916Mhz 917Mhz 918Mhz 919Mhz 920Mhz 921Mhz 922Mhz 923Mhz 924Mhz 925Mhz 926Mhz 927Mhz 928Mhz
Vietnam 920 - 925
Thailand 920 - 925
Taiwan 922 - 928
KT920-923 Plan (JoinFreq 922.10, 922.30, 922.50) South Korea 917 - 923.5
Singapore 920 - 925
NZ 915 - 928
Malaysia 919 - 923 JoinFreq 923.2

JoinFreq 923.4
Laos 923 - 925
Japan 920.6 – 928.8 (LBT support)

Indonesia 923 -
925
Hong Kong 920 - 925
Cambodia 923 - 925

Brunei 923 -
AU915-928 Band Plan (Join on any UL frequency) 925
Australia 915 - 928
LoRaWAN Class A Devices
Packet device sleeps device sleeps
Class A 1 second ± 20µS RX1 1 second ± 20µS RX2
Dependent from 923.3MHz / DR8
Tx channel/SF
Packet received by all

LoRaWAN Network Server selects
LoRaWAN GW in range
best LoRaWAN GW for downstream
traffic (if any)
Class A: bi-directional (default: must be supported by all devices)

• Most energy efficient communication class
• Class A must initiate a Tx before listening on Rx windows
• Can switch to Class B or C
LoRaWAN Class C Devices
Packet
Class A RX1
RX2 RX2
RX1 delay Up to next uplink
RX2 delay
Class C: bi-directional with “Continuous Rx”

• Powered devices which can afford to listen continuously.
• No latency for downlink communication.
• Implements Class A RX1 window plus…Continually listens on RX2 channel, only closed when
Transmitting
LoRaWAN Class B Devices
Beacon Beaconing is performed on the same channel that normal Beacon
downstream traffic as defined in the Class A specification. I.e. the
1st beacon will be transmitted on 923.3Mhz , 2nd on 923.9MHz, the
9th beacon will be on 923.3Mhz
GW with Class B (GPS)
R R R R R R R
Class B
X X X X X X X
Rx slot: 3 to 160ms depending on SF

Class B Bi-directional with scheduled receive slots (Beacons)
• Energy efficient communication class for latency controlled downlink.
• Slotted communication synchronized with a network beacon (from gateways).
• Network may send downlink packet to node at any Rx slot
• Node may implements Class A, then switch to Class B, if application firmware supports it
LoRaWAN End-to-End Architecture Application Servers
IOT broker or
LoRaWAN Network Server(s) dedicated applications
Gateways
P Semtech HW Next LoRaWAN MAC decaps,
Gen. reference Encrypt/Decrypt
design Network/Radio management Measure
Message scheduling, etc… Data
Roaming (1.1 specs)

Join Server
provisioning, keys management
Report
etc… Events
Geo-location solver
LoRaWAN™
Devices
Certification IP Backhaul API
program by LoRa Track
Alliance
LoRaWAN™ LoRaWAN™ IP
App Data IP Transport App Data
Radio PHY MAC Tunnel
MAC Layer encryption (NwkSKey)
App Layer encryption (AppSKey)
LoRaWAN Over-The-Air Activation (OTAA)
Global Dev ID
EUI64
(DevEUI)
JoinServer checks if the
Vendors’ provisioned on Global Join ID Provisioned by NS manager device was provisioned,
EUI64
devices (JoinEUI) on Join (NS) server then derives keys using
device’s AppKey and join
AES128
Application Key request content, and
(AppKey) generates the encrypted
Join Accept Join Accept
Home
DevNonce DevEUI JoinEUI JoinNonce DevAddr DLSettings RXDelay CFList
NetID
Join Request
Device derives AppSkey and NwkSKey Application

from content of Join Accept and AppKey Encrypted AppSKey or Server
SessionKeyID
Thingpark Enterprise Device Provisioning OTAA
Thingpark Wireless Endpoint Provisioning OTAA
• Example for LoRaWAN 1.0.2, with AppEUI (will be
JoinEUI, + NwkKey in 1.1)
LoRaWAN Activation-By-Personalisation (ABP)
Global Dev ID
EUI64
(DevEUI)
Vendors’ provisioned on Global Join ID Provisioned by NS manager
EUI64
devices (JoinEUI) on Join (NS) server
ABP devices use the same session
AES128 AES128
Network Session Key
NwkSKey keys throughout their lifetime (i.e.,
no rekeying is possible. Therefore,
App Session Key it is recommended that OTAA
(AppSKey) devices are used for higher
security applications.
End Device Addr
32bits
(DevAddr)
Application
Encrypted AppSKey or Server
SessionKeyID
Thingpark Wireless Endpoint Provisioning ABP
• Example for LoRaWAN 1.0.2, with

NwkSKey (will be FNwkSIntKey,
SNwkSIntKey, NetSEncKey in 1.1)
Thingpark
Enterprise
Thingpark Enterprise Components
Application Servers
IOT broker or
Cisco IXM LoRaWAN Thingpark Enterprise dedicated applications
P Gateways’ license Small, medium or large license
Macro or Nano package
Standard or premium connector Measure
Data
license
Cisco UCS (optional) or existing
server API
Report
Events
LoRaWAN™
Devices
Certification IP Backhaul
program by LoRa Track
Alliance
App Data
MAC
IP Transport App Data
Radio PHY Tunnel
Thingpark Enterprise Overview
• On-Prem or NaaS Cloud LoRaWAN Network Server for Enterprises
• Unified GUI, single tenant,
Dashboards Base Stations Device Application Platform

Monitor the LoRaWAN Management Management Management Management
network components Provision and operate Provision and monitor Choose to route Monitor platform, licenses
using charts LoRaWAN™ gateways LoRaWAN™ devices, your data to your and data frames of
including where data will application servers LoRaWAN™ devices
be forwarded or to IoT cloud (Wireles Logger)
platform
Thingpark Enterprise Components Installation
Dashboard Base Stations Device Management Application Portal

Management Management Management
TPE Portal
TPE Cockpit
CentOS
TPE Mini Technical Preview
• Cisco IC 3000 Thingpark Enterprise
• 4 core 1.2GHz Intel Rangeley CPU
• 8 GB of 1333MHz DDR3 memory
• 100GB mSATA drive (internal)
• 2 x 10/100/1000Base-T/SFP
• Thingpark Enterprise (TPE Mini)

• TPE Mini as a VM – Local Manager or IOT FND
• up to 3 IXM LoRaWAN
• up to 500 LoRaWAN endpoints Internet/Intranet
Thingpark Enterprise vs Thingpark Wireless
Thingpark Enterprise (TPE) Thingpark Wireless (TPW)
Tenancy Single tenant only, On-Prem & SaaS Single and multi tenants, On-Prem &
SaaS
Management Unfified GUI, single role Multiple roles Operator, vendor,
supplier, subscriber
Scale limitations Up to 100 GWs, 40K endpoints None
Devices/Gateways profiles Standard definitions Customizable
RF region multiple multiple
API for provisioning & service activation DX API DX API, OSS API, BSS API
Endpoints provisioning OTAA OTAA, ABP
User Data Record No Yes
LoRaWAN geo-location support Under review Yes
LoRaWAN roaming Roadmap Yes, Thingpark eXchange
Connectivity plans No Yes
Cisco IXM
LoRaWAN
Cisco LoRaWAN Gateway
Key Features and Capabilities
Ruggedized Dual Power

Inputs
IP67
TDOA Geolocation Globally

(GPS-free) ISM band
Cisco IXM LoRaWAN Gateway Software Components
 Cisco LoRaWAN Gateway firmware and Management: performs hardware/software management and monitors status
 Thingpark LRR: LoRaWAN radio management and traffic forwarding through LoRaWAN Gateway Ethernet backhaul
LoRaWAN Interface LoRaWAN

Mgmt. Subsystem
LXC
Thingpark LRR App App
LoRaWAN™ Connector Connector
• LoRaWAN packet Management
forwarder • Ethernet backhaul only LoRaWAN™
• RF channel • IPv4/ stack • No advanced IOS services App Router
management • IPsec to secure
• OSS RF stats communications • VPN service - up to 2 active LoRaWAN™
• Downlink Routing • Semtech HAL tunnels Network Server
Management driver
RX1/RX2 • Firmware GW MGMT Subsystem
• IEC 104 WAN management
Connectivity
Field
Linux-based
Network AAA/CA
firmware Director
FastEthernet 0/1 VPN VPN Connectivity

aggregation
Standalone LoRaWAN Gateway Site Installation
LoRaWAN Interface Omni
LoRaWAN Gateway Antenna x 2
Main and Diversity
Antenna Feeder RF Cable x 2
Lightning arrestor x 2
LoRaWAN Interface GPS

• Ethernet backhaul – typically LAN Antenna and cable
switch port with PoE+ option
• If no PoE+ support on the
Ethernet PoE+ cable
Ethernet backhaul device, either
PoE+ injector or DC power can be
used Ethernet 10kV surge protector –
if required
IP backhaul
Cisco IOS Mode LoRaWAN Gateway Software Components
 Cisco IOS mode LoRaWAN Gateway Management: performs hardware/software management and monitors status
 Thingpark LRR: LoRaWAN radio management and traffic forwarding through intelligent Cisco
IOS Software Layer-3 forwarding
LoRaWAN Gateway • Ethernet, Cellular or Wi-Fi LoRaWAN

LXC
(IR829) backhaul Mgmt. Subsystem
Thingpark LRR LoRaWAN™ • IOS ACL, QoS, FlexVPN, VRF, App App
Management SLA… for LoRaWAN services Connector Connector
• LoRaWAN packet
forwarder LoRaWAN™
• IPv4/IPv6 stack Cisco IOS App Router
• RF channel • IPsec to secure
management LoRaWAN™
communications Software LoRaWAN™
• OSS RF stats Management
with IR800 Network Server
• Downlink Routing • Semtech HAL
Management Intelligent
driver
RX1/RX2 • Firmware Cisco IOS Layer 3 GW MGMT Subsystem
• IEC 104 WAN management Forwarding
Software CLI
Connectivity
Field
Linux-based
Virtual-LPWA x Network AAA/CA
firmware Director
GI x (IR809)
10/100Mbs RJ-45 VPN Connectivity
VLAN x (IR829)
Link can be encrypted

Cisco IOT Gateway Portfolio
RUGGEDIZED
2x
GPS OPERATIONS LTE LTE WiFi
EDGE
COMPUTE Virtual-LPWA AVAILABILITY
60º
Global
-25º
CGR1000
U.S and
60º
Europe
-40º only
IR 807
60º
-40º
IR 809 Globally
60º
-40º
IR 829 Single LTE Globally
North
60º America
-40º & Europe
IR 829 Dual LTE only
2.0.30 release for CGR 1000/IR807

IR807/809 LoRaWAN Gateway Site Installation
LoRaWAN Gateway Omni
LoRaWAN Gateway Antenna x 2
Main and Diversity
Antenna Feeder RF Cable x 2
Lightning arrestor x 2
LoRaWAN Gateway GPS

IR809 GPS IR809 4G antennas
antenna (optional) (if cellular backhaul)
Antenna and cable
Ethernet PoE+ cable

Ethernet 10kV surge protector –
if required
Power source required for IR807/809 and LoRaWAN

IP backhaul
Gateway 48VDC source available from site –
LoRaWAN PoE+ DC injector
Cisco IR809 in enclosure • AC source: AC/DC adapter for IR807/809 and
or ground cabinet PoE+ AC injector for LoRaWAN Gateway
Cisco LoRaWAN Common Packet Forwarder
 Actility is Cisco LoRaWAN solution primary business partner
for LoRa Network Server
3rd party Network Server support requires the vendor to
develop and support its own LoRaWAN packet forwarder
LoRaWAN Forwarder for v2 GW is not available from Github Other Network Server Vendors engaged
as open source
IXM LoRaWAN 2.0.32 embeds Semtech packet forwarder,
which is unsupported by Semtech (and Cisco), see
Devnet community
https://communities.cisco.com/community/developer/in
ternet-of-things/cisco-lorawan-v2-gateway
To offer production level interworking with 3rd party Network
Server, Cisco is planning to build a Common Packet
Forwarder (CPF) based on Semtech latest Basic Station
LNS protocol. CPF is a licensed feature in IXM release
2.0.35 with target FCS date at Dec, 2019.
https://doc.sm.tc/station/tcproto.html
LoRaWAN
Deployment
Considerations
LoRaWAN Deployment Considerations
Application Servers
Cisco IXM LoRaWAN
Gateways
P
Measure
Data
Network Server
API
Report
Events
LoRaWAN™
Devices
IP Backhaul
Track
App Data
MAC
Radio PHY Tunnel
LoRaWAN Deployment Considerations - Sensors
Cisco IXM
LoRaWAN Application Servers
Gateways
P
Measure
Data
API
Network Server
Report
Events
LoRaWAN™
Devices
IP Backhaul
Track
App Data
MAC
Radio PHY Tunnel
Selecting the Right Sensors
Choosing sensors can be complicated
• Not all sensors are approved for local market (FCC approval)
• There is a dizzying array of hardware and software features
• For Logistics, GPS vs No GPS is a big issue for battery and cost
Different levels of “Out of Boxness”

• Documentation Levels
• Config Utility
• Support Resources
• Do they have integration into a Network Server or Application Server
• https://market.thingpark.com/iot-devices.html?p=1
Selecting the Right Sensors
Different levels of Network Server and Application Server
support
• More features are readily available with Network Server support
Digital Matter Sensors
Digital Matter Guppy Configuration
Default values used, except where highlighted.
Digital Matter Guppy Configuration (cont.)
Regional Considerations for Global Deployments
Source: https://www.thethingsnetwork.org/docs/lorawan/frequencies-by-country.html
Battery Considerations for Sensors
Source: Digital Matter

LoRaWAN Deployment Considerations - Gateways
Cisco IXM
Gateways
P
Measure
Data
API
Network Server
Report
Events
LoRaWAN™
Devices
IP Backhaul
Track
App Data
MAC
Radio PHY Tunnel
Considerations for Outdoor Deployments
Roof-top deployment of a Cisco

LoRaWAN gateway utilizing Cisco LoRaWAN gateways placed at the apex of
autonomous power and LTE uplink. tents used to house the MDM 2018 expo.
Rooftop Deployment Considerations
Antenna “array”:
• g -Pre-assembled to minimize mount points
-2 x IXM antennas
-GPS antenna
-grounding connection
Antenna cables:
-Minimize antenna cable lengths
-Drip loops
Mounting points:
-Use fixed infrastructure when possible
-3 band clamps for entire installation
Network backhaul:
-Weather-proof enclosure for IR800
Power requirements
View LoRaWAN Radio Traffic on IXM Gateway
1. Verify LRR trace level in packet forwarder configuration:
IXM# request shell container-console
bash-3.2# cd $ROOTACT/usr/etc/lrr/
bash-3.2# more lrr.ini
• Verify trace level is set to ‘1’; edit with vi if necessary:
[trace]
level=1
• If the trace level is changed, the packet forwarded must be restarted
2. View LoRaWAN RF packets in real-time:

bash-3.2# cd $ROOTACT/var/log/lrr/
bash-3.2# tail –f TRACE.log
Sample Capture:
Join Request (DM Guppy)
22:15:06.131 (00234) [../lgw_x8.c:1303] PKT RECV board0 tms=970734286 tus=081976108 status=CRCOK
sz=23 freq=904100000 delay=80 mod=0x01 bdw=BW125 spf=SF10 ecc=CC4/5 channel=9 nam='LC9' G20
22:15:06.131 (00234) [../lgw_x8.c:1324] rf0: valid=1 finetime=0 finetimestamp=000000000 chip=1 chan=1

snr=11.250000 rssi_chan=-102.000000 rssi_sig=0.000000 rssi_sig_std=0 antennaid=0
snr=0.000000 rssi_chan=0.000000 rssi_sig=0.000000 rssi_sig_std=0 antennaid=0
22:15:06.131 (00234) [../lgw_x8.c:1349] PKT RECV

data='000100005070d5b3709e04005070d5b3701a12fa79d2b7' seq=46037 devaddr=50000001
22:15:06.131 (00201) [../main.c:4026] packet sent to LRC=0 lrrid=6706bc41 by order rssi=-102.000000

snr=11.250000
Sample Capture:
Data Upload (DM Guppy)
22:58:50.846 (00234) [../lgw_x8.c:1303] PKT RECV board0 tms=973358968 tus=2706668684 status=CRCOK
snr=12.500000 rssi_chan=-89.000000 rssi_sig=0.000000 rssi_sig_std=0 antennaid=0
22:58:50.846 (00234) [../lgw_x8.c:1349] PKT RECV data='40ae03330480010001756435437dbc' seq=1
devaddr=043303ae
22:58:50.846 (00201) [../networkfilter.c:403] NWF addr=043303ae 00000100001100110000001110101110
check
22:58:50.846 (00201) [../networkfilter.c:407] NWF addr=043303ae no mask -+ defined
22:58:50.846 (00201) [../main.c:6110] NWF devaddr=043303ae forwarded
22:58:50.846 (00201) [../main.c:4026] packet sent to LRC=0 lrrid=6706bc41 by order rssi=-89.000000
snr=12.500000
Sample Capture:
Packet Received from Unregistered Device
22:10:54.729 (00234) [../lgw_x8.c:1303] PKT RECV board0 tms=970482887 tus=4125515419 status=CRCERR


snr=-11.750000 rssi_chan=-121.000000 rssi_sig=0.000000 rssi_sig_std=0 antennaid=0

LoRaWAN Deployment Considerations – Network
Server
Cisco IXM
Gateways
P
Measure
Data
API
Network Server
Report
Events
LoRaWAN™
Devices
IP Backhaul
Track
App Data
MAC
Radio PHY Tunnel
TPE Installation Requirements
Local NTP server
Local SMTP server
Internet
connectivity
required for initial
install
DNS (or local host

file)
LoRaWAN Deployment Considerations –
Application Server
Cisco IXM
Gateways
P
Measure
Data
API
Network Server
Report
Events
LoRaWAN™
Devices
IP Backhaul
Track
App Data
MAC
Radio PHY Tunnel
Application Server: Digital Matter – Telematics Guru
Web Client
Mobile
Client
Application Server Considerations
WMW - the Application Server we used
• Multiple Sensor types supported
• Multiple Data Types (i.e., text message inputs)
• Customer Premise and Cloud options
WMW can be your primary tool for visualization, or

• Text message
• Email
• API integration to other platforms
Application Server: WMW
WMW Chain of Custody/History Report
Arrival
Departure
Handover
WMW Application Server – API availability
WebEx Teams API integration with WMW and
LoRaWAN
h/t: David Siezemore

LoRaWAN Use Case for Logistics, for example
This protocol solves major problems in the Logistics space
• Our experience has been in the DoD space
• A combination of distance, battery and cost makes this outcome possible, no
SIM
• We can find not only the location of goods, but of people, machines, vehicles,
and warehouses that handle the goods
• All this data can be presented simultaneously in different ways
We can draw conclusions with actionable insights

• Servers can give us maps with current or historical information
• Applications can notify us when goods, people, vehicles are out of compliance
The concept of “Presence”

• We don’t need to GPS locate everything to make that data valuable
• These are all the goods that I have now in the warehouse
Precision GPS Tracking:
Oyster GPS Tag Reporting to Single IXM Gateway
Asset Tracking:
Non-GPS LoRaWAN Sensor with Single GW per Location
Telematics Guru screen capture showing real-time location of buses at MDM main expo area and Marine Corps museum parking
location.
WMW screen capture showing buses at overnight parking area in front of base lodging.
WMW screen capture showing real-time location of buses at MDM main expo area and Marine Corps museum parking location.
WMW screen capture showing real-time location of buses at MDM main expo area and Marine Corps museum parking location.
Also shows historical position & speed data at bottom of screen.
Real-Time Location with GPS LoRaWAN Sensor:
History Report with Check-in & Check-out
Real-Time Location with GPS LoRaWAN Tag:
History Report with Check-in & Check-out
References
Additional Resources
• LoRa Alliance https://www.lora-alliance.org/
• Cisco LoRaWAN solution:
http://www.cisco.com/c/en/us/solutions/internet-of-things/lorawan-
solution.html
• Cisco LoRaWAN interface:
http://www.cisco.com/c/en/us/products/routers/interface-module-
lorawan/index.html
• Cisco LoRaWAN HW:
http://www.cisco.com/c/en/us/support/routers/interface-module-
lorawan/tsd-products-support-install-and-upgrade.html
• Cisco LoRaWAN SW:
http://www.cisco.com/c/en/us/support/routers/interface-module-
lorawan/tsd-products-support-configure.html
Complete your
online session • Please complete your session survey
evaluation after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live water bottle.
• All surveys can be taken in the Cisco Live
Mobile App or by logging in to the Session
Catalog on ciscolive.cisco.com/us.
Cisco Live sessions will be available for viewing
on demand after the event at ciscolive.cisco.com.
Continue your education
Demos in the
Walk-in labs
Cisco campus
Meet the engineer

Related sessions
1:1 meetings
Thank you
#CLUS
#CLUS

Brkiot 1291

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brkiot 1291

Uploaded by

Copyright:

Available Formats

#CLUS

LoRaWAN for IOT

Webex Teams will be moderated cs.co/ciscolivebot#BRKIOT-1291

Mobile Service Provider (SP) Enterprises and Services Providers

Ecosystem under development Ecosystem Ready Now

RF unlicensed Long Distance Low Low Power

Generate New Revenues

Decrease Operating Costs

Increase Productivity and Operations

Customer Satisfaction Survey Environmental monitoring

Optimize operations and reduce busy

Optimize Shuttle Buses Use geolocation to protect

LoRa PHY Modulation (developed by Semtech)

EU868 US915 AS923 India 865 AU915 RU864

Spreading SF12 SF11 SF10 SF9 SF8 SF7

• ADR maximises battery life overall & network capacity

SF10 980 370 59 bytes -133

SF9 1760 200 123 bytes -130

SF8 3125 100 250 bytes -127

SF7 5470 28 250 bytes -124

US915 Frequency band, @125kHz channels Upstream

64 + 8 uplink channels 8x downlink channels

902.3 903.0 904.6 914.2 923.3 923.9 927.5

Thailand 920 - 925

Taiwan 922 - 928

Singapore 920 - 925

Malaysia 919 - 923 JoinFreq 923.2

Japan 920.6 – 928.8 (LBT support)

Cambodia 923 - 925

Packet received by all

Class A: bi-directional (default: must be supported by all devices)

RX1 delay Up to next uplink

Class C: bi-directional with “Continuous Rx”

GW with Class B (GPS)

Rx slot: 3 to 160ms depending on SF

Roaming (1.1 specs)

App Layer encryption (AppSKey)

Device derives AppSkey and NwkSKey Application

App Layer encryption (AppSKey)

ABP devices use the same session

App Layer encryption (AppSKey)

• Example for LoRaWAN 1.0.2, with

Dashboards Base Stations Device Application Platform

Dashboard Base Stations Device Management Application Portal

• Thingpark Enterprise (TPE Mini)

Ruggedized Dual Power

TDOA Geolocation Globally

LoRaWAN Interface LoRaWAN

FastEthernet 0/1 VPN VPN Connectivity

LoRaWAN Interface GPS

LoRaWAN Gateway • Ethernet, Cellular or Wi-Fi LoRaWAN

Link can be encrypted

2.0.30 release for CGR 1000/IR807

LoRaWAN Gateway GPS

Ethernet PoE+ cable

Power source required for IR807/809 and LoRaWAN

Different levels of “Out of Boxness”

Source: Digital Matter

Roof-top deployment of a Cisco

2. View LoRaWAN RF packets in real-time:

22:15:06.131 (00234) [../lgw_x8.c:1324] rf0: valid=1 finetime=0 finetimestamp=000000000 chip=1 chan=1

22:15:06.131 (00234) [../lgw_x8.c:1349] PKT RECV

22:15:06.131 (00201) [../main.c:4026] packet sent to LRC=0 lrrid=6706bc41 by order rssi=-102.000000