![]() ![]() What I can say is that the use case was covering a typical smart metering deployment, with meter reads every 30mn, plus daily, weekly and monthly data collected. Regarding the tested case, the customer prevents us from publicly communicating detailed results as they are still unclear regarding which technology they want to deploy in the end, but we would be happy to discuss the context we were operating if this of interest for you. ![]() Traffic size is anticipated to ensure that ToA will enable us to effectively deploy the use case. On a new project, we observe, analyse and take into account those parameters to define the suitability and performance we can expect from the LoRaWAN network and context. Regarding TTN, you are right regarding the downlink and I now remember that one of our engineers highlighted that point when relating to TTN.Įach case will be different, as it is a combination of available spectrum/local regulation and regional parameters, combined with the LNS capabilities and metering data to collect, at a given periodicity. The use case we have tested with metering was involving another LNS but this showed that beyond the restriction of each LNS features, particularly in term of multicast or Firmware upgrade or Community Edition vs On Premise full featured deployment, LoRaWAN is able to support DLMS/COSEM. ![]() ![]() Regarding TTN compatibility, this is indeed to adjust to both the use case expectations/metering requirements and TTN specificities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |