LoRaWAN Support

[thommck]

The LoRaWAN protocol is a very common solution for edge devices, thanks to it's capability to connect across large distances. For example there are already 881 public LoRaWAN gateways connected all around the United Kingdom (source). The issue is these LoRa devices usually communicate with the public Things Network, rather than a private network. This makes it more complex and have a higher risk than connecting via Akri on a locally deployed solution and then on to a cloud provider like Azure.

Describe the solution you'd like Enable LoRa devices to be able to connect to Akri straight out of the box

Describe alternatives you've considered IoT Edge Starter kit is a custom method but doesn't follow the same CNCF standards based approach as Akri

[agracey]

Hey, this would be a great thing to build!

Before we do, it's likely worth a having a more general conversation about if we want the core project maintainers to also maintain all of the discovery handlers or should we maintain a library of 3rd party options instead.

[lilustga]

@thommck how can we support you here? Are you looking to contribute changes to enable this? Or is this a feature request?

[thommck]

It's a feature request. I don't have the skills to contribute to the development

On Tue, 5 Dec 2023 at 16:54, Lior Lustgarten @.***> wrote:

@thommck https://github.com/thommck how can we support you here? Are you looking to contribute changes to enable this? Or is this a feature request?

— Reply to this email directly, view it on GitHub https://github.com/project-akri/akri/issues/677#issuecomment-1841222289 or unsubscribe https://github.com/notifications/unsubscribe-auth/AHC7URT4GWWV57P2JPETHO3YH5GS5BFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVEZTAMRXGAZTKNZWQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRRHE3DOOJUGAZDGNNHORZGSZ3HMVZKMY3SMVQXIZI . You are receiving this email because you were mentioned.

Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

-- Thom McKiernan *07988228438 | @.** http://twitter.com/thommck | thommck.wordpress.com http://thommck.wordpress.com/

[kate-goldenring]

Before we can more this to backlog of Discovery Handlers to put on the roadmap, we should do some investigation into how open LoRaWAN licensing is and whether it is permissible within a CNCF project. If that investigation shows that the licensing is not open enough, an individual/third party could still create the discovery handler and we could point to it in documentation

[yujinkim-msft]

@EthanChangAED

[EthanChangAED]

LoRaWan has a device certification program. Other than that, I believe there is no restriction on building join server, application server based on the LoRaWan specification and the lorawan-stack. There are already many application/solution in the market, including open-source or free ones. However, I think the LoRaWan has a complete design of network and connection topology, as well as a provision process. A LoRaWan device is not a typical "leaf device". I think we would need some dev assessment (if it hasn't been done) on whether there is a place for Akri to fit in before moving this to our backlog.

@thommck , it would be great if you can share your thought about how Akri integrate with or enhance the LoRaWan architecture.

[EthanChangAED]

The investigation for business/licensing perspective is done. Change the status to triage needed as we need some more triage from implementation point of view.