<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SUPL-C license has been denied</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/87751/supl-c-license-has-been-denied</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Wed, 11 May 2022 12:37:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/87751/supl-c-license-has-been-denied" /><item><title>RE: SUPL-C license has been denied</title><link>https://test-devzone.nordicsemi.com/thread/367407?ContentTypeID=1</link><pubDate>Wed, 11 May 2022 12:37:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d82c565-a421-4104-bb71-4e1a318827a3</guid><dc:creator>user93921</dc:creator><description>&lt;p&gt;Hi Benedikt,&lt;/p&gt;
&lt;p&gt;Good to hear, you are welcome.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Charlie&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SUPL-C license has been denied</title><link>https://test-devzone.nordicsemi.com/thread/367290?ContentTypeID=1</link><pubDate>Wed, 11 May 2022 06:13:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52386bed-1bd0-4c42-bea8-ceffb9f68ada</guid><dc:creator>user115892</dc:creator><description>&lt;p&gt;Hello Charlie,&lt;/p&gt;
&lt;p&gt;thank your very much for your fast reply and the additional information.&lt;/p&gt;
&lt;p&gt;My application for the SUPL-C license has been granted.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Benedikt&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SUPL-C license has been denied</title><link>https://test-devzone.nordicsemi.com/thread/367106?ContentTypeID=1</link><pubDate>Tue, 10 May 2022 09:04:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9fcdb279-5275-4676-8a85-6a339321a3f4</guid><dc:creator>user93921</dc:creator><description>&lt;p&gt;Hi Benedikt,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;We apologize for the inconvenience. This&amp;nbsp;is&amp;nbsp;&lt;/span&gt;&lt;span&gt;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.&amp;nbsp;Let me know if you need further assistance.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On the other hand, I would&amp;nbsp;&lt;/span&gt;recommend you avoid using SUPL as a GNSS assistance solution until it is clear that nRF Cloud cannot work for your use case.&amp;nbsp;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;
&lt;p&gt;There are 3 ways to utilize nRF Cloud services. including A-GPS:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span&gt;direct to nRF Cloud via MQTT&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;direct to nRF Cloud via REST (HTTPS)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;indirectly using a cloud-to-cloud proxy via REST&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;Option 1 is appropriate for some&lt;span&gt;&amp;nbsp;&lt;/span&gt;developers&lt;span&gt;&amp;nbsp;&lt;/span&gt;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.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Option 2 is appropriate if&lt;span&gt;&amp;nbsp;&lt;/span&gt;your&lt;span&gt;&amp;nbsp;&lt;/span&gt;products only report data infrequently, such as when a rare event occurs. The LTE connection could be kept off until needed.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;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.&lt;span&gt;&amp;nbsp;&lt;/span&gt;Nordic has developed example AWS and Azure web projects customers can start with.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;You can also refer to&amp;nbsp;the documentation on both the nRF Connect SDK side (&lt;a title="https://developer.nordicsemi.com/nrf_connect_sdk/doc/latest/nrf/ug_nrf_cloud.html" href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf_cloud.html" rel="noopener noreferrer" target="_blank"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf_cloud.html&lt;/a&gt;) as well as on the nRF Cloud side (&lt;a title="https://docs.nrfcloud.com/" href="https://docs.nrfcloud.com/" rel="noopener noreferrer" target="_blank"&gt;https://docs.nrfcloud.com/&lt;/a&gt;).&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Best regards,&lt;/div&gt;
&lt;div&gt;Charlie&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>