nrf9160 throughput

 I'm trying to build a proof of concept for a BLE gateway that captures data from BLE sensors and sends it to the cloud via LTE-M connection. I'm hoping that the gateway can support 20 concurrent BLE connections for the proof of concept. However, I'm concerned on nRF91's data rate. I am afraid it leave the throughput on the cellular side lacking compared to what it receives from the BLE peripheral. Is there anyway to get around this? Or should I use a third party GSM like sim7600?

My idea is to connect two NRF9160 together to handle the throughput. Or I can connect nrf52840 with a LTE CAT4 module like Maduino Zero 4G LTE. Both options need to be battery backed and runs without connecting to PC eventually.

Would that work?

Best,

Ben Li

  • Hello Ben Li, 

    My idea is to connect two NRF9160 together to handle the throughput. Or I can connect nrf52840 with a LTE CAT4 module like Maduino Zero 4G LTE. Both options need to be battery backed and runs without connecting to PC eventually.

    Would that work?

    I’m honestly not quite sure what your approach is here. Can you elaborate? 

    However, I'm concerned on nRF91's data rate. I am afraid it leave the throughput on the cellular side lacking compared to what it receives from the BLE peripheral. Is there anyway to get around this? Or should I use a third party GSM like sim7600?

    Why are you concerned about the nRF91 data rate and what do you mean by ‘throughput on the cellular side lacking’? 

    Regards, 

    Markus 

  • I’m honestly not quite sure what your approach is here. Can you elaborate? 

    My first approach is to use nRF52 that scans and initiate connections, and I will need another nrf52 as a peripheral to advertise 20 BLE signals in total using blood pressure profile, heart rate profile... etc. To send the data to the cloud, I will connect the central with another third party cellular module such as the madrino board via SPI or UART so that I can foward the data to the cloud via 4G/5G cellular

    My second approach is just using two NRF9160 together. Since there are on board nrf52480 SOC and cellular modem. It will serves as a central. I will still use another nrf52 to serve as peripheral. 

    Why are you concerned about the nRF91 data rate and what do you mean by ‘throughput on the cellular side lacking’? 

    My concern is that I'm not sure if there is going to be latency issue  since nRF9160 seems to be designed for low throughput use cases. As I'm having 20 concurrent BLE signals. I am afraid the network core will runs out of memory. Therefore I'm wondering if it is necessary to connect two nRF9160 together to solve this issue.

  • Ben Li said:
    My first approach is to use nRF52 that scans and initiate connections, and I will need another nrf52 as a peripheral to advertise 20 BLE signals in total using blood pressure profile, heart rate profile... etc. To send the data to the cloud, I will connect the central with another third party cellular module such as the madrino board via SPI or UART so that I can foward the data to the cloud via 4G/5G cellular

    Thanks a lot for the detailed input, Ben Li! 

    Ben Li said:
    My second approach is just using two NRF9160 together. Since there are on board nrf52480 SOC and cellular modem.

    In this case, you mean two nRF9160 DKs, right? Because the nRF9160 SiP itself has no nRF52840 SoC included. Please be advised, that on the nRF9160 DK the nRF52840 SoC is flashed with a firmware called the Board Controller. You can of course flash other firmware to it, but you will then loose some of the functionality that comes along with the DK. 

    Ben Li said:
    My concern is that I'm not sure if there is going to be latency issue 

    I’m still not sure if I understand what you mean by 'latency issues'. Could you think of a specific example or use case here? 

    Ben Li said:
    since nRF9160 seems to be designed for low throughput use cases.

    What gives you the impression that the nRF9160 'seems to be designed for low throughput use cases'? Could you point me to the source mentioning that? 

    Ben Li said:
    I am afraid the network core will runs out of memory.

    The nRF9160 has no network core. It includes an application and a modem core which, except of a shared RAM memory area, are completely separated from each other. Along with the nRF5340, the nRF9160 is our most powerful product. Having the application core out of memory will require quite some coding. The modem core on the other hand is designed as a black box which cannot be accessed from the outside, except via the mentioned shared RAM memory area.

    Regards,

    Markus

  • Hello Markus, 

    Thank you so much for your input. 

    I’m still not sure if I understand what you mean by 'latency issues'. Could you think of a specific example or use case here? 

    I think what I'm trying to say is that the throughput of the modem on nrf9160 seems to be very low. Just like what other people said  nRF9160 DK maximum throughput I'm not sure the UL rate of 50kbps is going to be enough for my case (20 concurrent BLE connections). I am afriad that when the application sends more data than how much the modem can transmit, I will experience the some issues with the data trasmission. (like it´s waiting to send the buffer to the cellular tower or the socket disconnects.) 

    What gives you the impression that the nRF9160 'seems to be designed for low throughput use cases'?

    I've been told by Simon about this issue on my last ticket  nRF6943 or nRF9160 DK (BLE Cellular gateway) but I still want to consider using nRF9160DK because I'm not sure how to connect nRF52 with SIMCOM GSM. So I'm wondering if nRF9160 cellular modem is capable of supporting high throughput. I have also been told by my supervisor that LTE-CAT M1 doesn't have enough UL and DL rate, what's why I'm considering using LTE CAT4. What do you think about that?

    Thank you,

    Ben Li

  • Hello Ben Li, 

    Ben Li said:
    I think what I'm trying to say is that the throughput of the modem on nrf9160 seems to be very low. Just like what other people said  nRF9160 DK maximum throughput I'm not sure the UL rate of 50kbps is going to be enough for my case (20 concurrent BLE connections). I am afriad that when the application sends more data than how much the modem can transmit, I will experience the some issues with the data trasmission. (like it´s waiting to send the buffer to the cellular tower or the socket disconnects.) 

    The above-mentioned data rates are not nRF9160 specific, we are talking about designed limits according to the specifications of the LTE-M / NB-IoT protocol. In LTE-M, data rates up to 4 Mbps can be achieved while NB-IoT is specified for 127 kbps up to this point. The nRF9160 acts according to those standards, which it is designed for. And I guess this what my colleague Simon means with “The nRF9160 isn't really designed for high throughput use cases, but rather low power solutions.” 

    However, if one would consider those data rates as low or high throughput depends on how you look at it and what you compare it to. 

    Ben Li said:
    I've been told by Simon about this issue on my last ticket  nRF6943 or nRF9160 DK (BLE Cellular gateway) but I still want to consider using nRF9160DK because I'm not sure how to connect nRF52 with SIMCOM GSM. So I'm wondering if nRF9160 cellular modem is capable of supporting high throughput. I have also been told by my supervisor that LTE-CAT M1 doesn't have enough UL and DL rate, what's why I'm considering using LTE CAT4. What do you think about that?

    The nRF9160 does not support LTE protocols, no.  

    One challenge that I see from what you are describing here is that the gateway has to buffer lots of data, filter and transfer it within certain time frames. Since the nRF9160 has a shared memory for data exchange between the application and modem core, this can be handled quite fast. On the other hand, if an external modem is used, the data rates of the interface that communicates with this modem might limit the throughput. Additionally, how fast an external modem will act on certain requests might have to be considered as well. 

    I might not have an universal answer for you here, Ben Li. At a certain point you should test and compare the devices you are considering for your project and see which ones give you the most promising results.

    Cheers, 

    Markus 

Related