• State Not Answered
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 143 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288812
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

SUPL-C license has been denied

user115892

I keep receiving the email stating the following, even after having all the points taken care of :-

1. I am using a active / approved DevZone Account.

2. I am using the same email address.

3. The account I requested from is the same account I sent this question from.

Am not sure if there is something that I am doing wrong, or if there is an issue with the backend as stated in the previous similar instances.

Parents
  • 0

    Hi Benedikt,

    We apologize for the inconvenience. This is a known bug with the SUPL licenses, as there are some issues with this process. I contacted the person in charge of the licenses, and you will get a mail with access soon, as we added your application manually. Let me know if you need further assistance.

    On the other hand, I would recommend you avoid using SUPL as a GNSS assistance solution until it is clear that nRF Cloud cannot work for your use case. 

    There are 3 ways to utilize nRF Cloud services. including A-GPS:

    1. direct to nRF Cloud via MQTT
    2. direct to nRF Cloud via REST (HTTPS)
    3. indirectly using a cloud-to-cloud proxy via REST
    Option 1 is appropriate for some developers whose products report data to the cloud frequently, such as asset tracking or reporting weather conditions, and for whom low power consumption is not a major requirement. The MQTT connection should be kept open and functional long-term to avoid TLS connection negotiation costs.
    Option 2 is appropriate if your products only report data infrequently, such as when a rare event occurs. The LTE connection could be kept off until needed.
    Option 3 allows the developer to run their own cloud solution, which can leverage the best balance of reliability, security, and complexity for their use case (e.g., maybe LWM2M, maybe CoAP / UDP, etc.), but still consume nRF Cloud services such as A-GPS, P-GPS, cellular positioning, or FOTA, in a cloud-to-cloud proxy arrangement. Asset Tracker v2 supports such an arrangement. Nordic has developed example AWS and Azure web projects customers can start with.
    You can also refer to the documentation on both the nRF Connect SDK side (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf_cloud.html) as well as on the nRF Cloud side (https://docs.nrfcloud.com/).
    Best regards,
    Charlie
Reply
  • 0

    Hi Benedikt,

    We apologize for the inconvenience. This is a known bug with the SUPL licenses, as there are some issues with this process. I contacted the person in charge of the licenses, and you will get a mail with access soon, as we added your application manually. Let me know if you need further assistance.

    On the other hand, I would recommend you avoid using SUPL as a GNSS assistance solution until it is clear that nRF Cloud cannot work for your use case. 

    There are 3 ways to utilize nRF Cloud services. including A-GPS:

    1. direct to nRF Cloud via MQTT
    2. direct to nRF Cloud via REST (HTTPS)
    3. indirectly using a cloud-to-cloud proxy via REST
    Option 1 is appropriate for some developers whose products report data to the cloud frequently, such as asset tracking or reporting weather conditions, and for whom low power consumption is not a major requirement. The MQTT connection should be kept open and functional long-term to avoid TLS connection negotiation costs.
    Option 2 is appropriate if your products only report data infrequently, such as when a rare event occurs. The LTE connection could be kept off until needed.
    Option 3 allows the developer to run their own cloud solution, which can leverage the best balance of reliability, security, and complexity for their use case (e.g., maybe LWM2M, maybe CoAP / UDP, etc.), but still consume nRF Cloud services such as A-GPS, P-GPS, cellular positioning, or FOTA, in a cloud-to-cloud proxy arrangement. Asset Tracker v2 supports such an arrangement. Nordic has developed example AWS and Azure web projects customers can start with.
    You can also refer to the documentation on both the nRF Connect SDK side (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf_cloud.html) as well as on the nRF Cloud side (https://docs.nrfcloud.com/).
    Best regards,
    Charlie
Children
No Data
Related
Terms of service