Ok, a single channel gateway is not compliant to the LoRaWAN standard.
The lack of having full compliant gateways has stood in the way of deploying them for a long time.
Also TTN not delivering their gateways encouraged the development of the SCG for those who invested in the kickstarter. To a certain extend TTN contributed to the existance of so many SCG and helped to created the “issue” that is topic of this thread. .
In my opinion SCG have a purpose and they satisfy the need for a simple solution that is cost effective. The nature of SCG fits the pioneering attitude of TTN particpants. Therefore rejecting SCG it not an option in my opinion.
I do acknowledge that having SCG that are non compliant in a compliant network is undesirable.
A workaround could be to have a separate (extra) channel, as suggested, for non complaint end devices and SCG that only operate one frequency. I do not see a solution (yet) for seamless integration of SCG in the existing channel plan.
With respect to the suggested options:
- Adding downlink to SCG is simple. RX1 window is implemeted many times. RX2 seems not. (I have not investigated all SCG versions.
- Having a separate channelplan for SCG seems feaseable as long as seamless integration with the compliant part of the network is not the objective.
I think these suggestions allow small deployments of nodes and gateways in micro or nano cell level. It will contribute to the handoff of traffic of the “big” network.
In my opinion a ecosystem like the LoRaWAN deriviation for SCG micro and nano networks can coexist besides the LoRaWAN compliant network while sharing the same back-end infrastructure. A win-win?
I am looking forward to the implementation.