Data format translation from SUPL to NRF Cloud AGPS Schema V1

[Anirudh Agarkhed]

Hello,

          Using the nRF Connect SDK 1.9.1 for nRF9160 location. Found the "location" library quite simple and scalable to use. So was looking into it. We do not plan to use nRF Cloud for AGPS, and selected the corresponding option to go with External AGPS data, and picked the SUPL lib to inject AGPS data. In the GNSS Sample with SUPL Assistance, the SUPL server data received is injected to the GNSS socket, which is fine. Now in case of "location" library, there is a handler "LOCATION_EVT_GNSS_ASSISTANCE_REQUEST" is received. Here it is mentioned to push the AGPS data formatted to nRF Cloud AGPS Schema V1 into function "location_agps_data_process".

1. Is there a way to translate this received SUPL data into the desired schema?

2. Can the data be injected to GNSS Socket and inform the "location" library to use this SUPL's AGPS data?

[Håkon Alseth]

Hi,

 

Using the nRF Connect SDK 1.9.1 for nRF9160 location. Found the "location" library quite simple and scalable to use. So was looking into it. We do not plan to use nRF Cloud for AGPS, and selected the corresponding option to go with External AGPS data, and picked the SUPL lib to inject AGPS data. In the GNSS Sample with SUPL Assistance, the SUPL server data received is injected to the GNSS socket, which is fine. Now in case of "location" library, there is a handler "LOCATION_EVT_GNSS_ASSISTANCE_REQUEST" is received. Here it is mentioned to push the AGPS data formatted to nRF Cloud AGPS Schema V1 into function "location_agps_data_process".

1. Is there a way to translate this received SUPL data into the desired schema?

I am not sure I understand the question properly.

AGPS SUPL data, regardless of where it comes from (ie. google supl server or nrf cloud), is injected in the same way to the gnss.

2. Can the data be injected to GNSS Socket and inform the "location" library to use this SUPL's AGPS data?

Location is a look up based on the MNC/MCC of your currently connected network, and if there's a problem to look up the specific Cell ID, it will give a default location based on the country code.

 

Kind regards,

Håkon

[Anirudh Agarkhed]

If it is indeed injected the same way to the gnss, why is there an error when "location_agps_data_process()" is invoked?

[Håkon Alseth]

Hi,

 

My apologies for misunderstanding your question. I thought you were talking about the data that goes into the GNSS socket.

The "location" library uses nrf cloud as a backend for PGPS/AGPS operations, as explained in the documentation:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/modem/location.html#implementation

This library can not be used with the SUPL server implementation.

 

Kind regards,

Håkon

[Anirudh Agarkhed]

Hello,

Kindly help me understand why provide the option for configuring of feeding external AGPS and PGPS data specified as "CONFIG_LOCATION_METHOD_GNSS_AGPS_EXTERNAL" in

developer.nordicsemi.com/.../location.html

[Håkon Alseth]

Hi,

 

Anirudh Agarkhed said:

Kindly help me understand why provide the option for configuring of feeding external AGPS and PGPS data specified as "CONFIG_LOCATION_METHOD_GNSS_AGPS_EXTERNAL" in

developer.nordicsemi.com/.../location.html

If you enable this config, you have to implement the handler manually, as stated in the documentation.

If you want to use AGPS with a generic supl server, like google's, you should have a look at the gnss sample, and add these two configurations:

CONFIG_GNSS_SAMPLE_ASSISTANCE_SUPL=y
CONFIG_GNSS_SAMPLE_SUPL_HOSTNAME="supl.google.com"

 

This requires that you have the libsupl library present in your local checkout of the SDK.

You can request libsupl from this page: https://www.nordicsemi.com/Products/nRF9160/Download?lang=en#infotabs

 

Kind regards,

Håkon