Simon

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • Simon
    Participant

    Hi Jason,
    thank you for your help!

    Could you use different APP EUI/KEY per customer for each set of Conduits?

    Unfortunatly not, i have no access to devices.

    LENS could be used although there would be additional cost involved.

    What are the costs and how can i get into LENS?

    When using the Network Server on Conduit a device should join and get a session to only one Conduit. Without LENS multiple Conduits that know the DevEUI/AppKey could respond to the Join Request.

    This is happening, but this is not a problem. At the moment the Device sends the Join Request and all gateways will answer this request. The device will get the Keys from the “fastest” response and saves this AppSKey and NetSKey on its local storage. If the device sends a Payload afterwards only one gateway has the corresponding Session keys.

    Is it possible with LENS to assign Device EUIs to Gateways? Otherwise i would have the Problem, that every Gateway fetches the correct Session Keys from the LENS Server and i will receive duplicate Uplinks.
    I hope you understand my Problem.

    Antoher Solution would be if i could move the NetworkServer from the Gateway to the Cloud. Do you know wich Network Server is used on the Conduits and if it can be ported to the Cloud?

    Thank you so much for your support

    in reply to: Packetforwarder to Loraserver Setup over LTE missing packets #32246
    Simon
    Participant

    Hi Steve,

    i would like to understand this a little bit better.

    For uplink i the the follwoing data flow:

    PF<====LTE=====>Loraserver<=========>Applicaiton

    even if there is a high latency the packet should still arrive at the loraserver and should be relayed to the application.

    For the downlink i want to investigate where the downlink packet gets stuck

    Application<============LTE====>Loraserver<======LTE=====>Packetforwarder

    The application queues the downlink in the loraserver. When the Class A Device sends its uplink to the Loraserver the Loraserver will immediatly use its two windows to set the downlink. I have more than one second time. if the packetforwader pings the loraserver i hava a ping of 56ms.
    Is there anything i am missing?

    My Problem is, that i have a big installation with multiple sensors (>500). Since the builing has 8 levels i need to use multiple gateways that can only use LTE. If i set every gateway to be a loraserver, than the devices can only use one gateway for up and downlink, since the inital join request was handled by one gateway. If i could use the Loraserver Packetforwader setup one sensor will be recieved by all gateways which will increase the performance and the stability of the network dramatically.

    If you have any idea what will be a solution for this case i am more than happy.

    Thank you for your support

Viewing 2 posts - 1 through 2 (of 2 total)