Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support of NIDD transport for Lora and 3GPP #1046

Open
sbernard31 opened this issue Jul 1, 2021 · 8 comments
Open

Add support of NIDD transport for Lora and 3GPP #1046

sbernard31 opened this issue Jul 1, 2021 · 8 comments
Labels
bsserver Impact LWM2M bootstrap server client Impact LWM2M client new feature New feature from LWM2M specification server Impact LWM2M server
Milestone

Comments

@sbernard31
Copy link
Contributor

This aims to centralize discussion about support of NIDD transport in Leshan.

LoRaWAN :

CIoT :

@sbernard31 sbernard31 added new feature New feature from LWM2M specification client Impact LWM2M client server Impact LWM2M server bsserver Impact LWM2M bootstrap server labels Jul 1, 2021
@sbernard31 sbernard31 added this to the 2.0.0 milestone Jul 1, 2021
@sbernard31
Copy link
Contributor Author

@Przem83, @MichalWadowskiOrange, I created a dedicated issue to talk about NIDD transport. (#1034 (comment))

@madhushreegc as you already have some code which seems to run Leshan with NIDD, you may be interested (or could help) about this topic.

I link some previous issue/work/talk about that :

@madhushreegc
Copy link

@sbernard31 , Sure . Connector we have implemented our own to integrate with the other channels .

@sbernard31
Copy link
Contributor Author

@Michal-Wadowski I see you start investigating on this.

I have no experience with this transport layer at all and one of my current concern about this feature is how this will be tested/testable ? (This is maybe a very naive question but does it needed any hardware or specific tool to do that ?)
Do you have some inputs about that ?

@Michal-Wadowski
Copy link
Contributor

I'm currently do a research with my team. At first step we want to make sure that we can just implement some kind of connector that would work with Leshan without specific IP dependencies. For now we don't know how should the final product looks like.

@boaks
Copy link

boaks commented Sep 9, 2021

AFAIK, there is still too much stuff depending on an IP-address (InetSocketAddress).
So, one of the most promising approaches is therefore mapping the "custom protocol" to something, which looks like IP.

  • message oriented transfer, then use the UDP flavor.
  • stream oriented transfer, then use the TCP flavor.

For both, map the "native address" into IPv4 or IPv6 addresses. Please omit multicast/broadcast addresses.
With that:

  • incoming messages must be converted into RawData and the "native address" is mapped into a ip-address:
  • outgoing messages are passed as RawData with a destination ip-address, which must be mapped to the "native address" and the bytes must be sent with that transfer.

@sbernard31
Copy link
Contributor Author

@Michal-Wadowski is it something Orange need ? or this is more to try to make Leshan 2.0 feature complete about LWM2M v1.1 ?

@sbernard31
Copy link
Contributor Author

@madhushreegc, I move forward about transport layer abstraction. #1025

If you want, you could try to implement to add a NIDD with this new abstraction maybe inspiring yourself by #1312
This could help to know if we go in the right direction.

@madhushreegc
Copy link

Sure, I will try this out. I am quite busy now , later next month mid I will try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bsserver Impact LWM2M bootstrap server client Impact LWM2M client new feature New feature from LWM2M specification server Impact LWM2M server
Projects
None yet
Development

No branches or pull requests

4 participants