nrf_cloud_agps_process buffer format

[ibiglari]

Hi,

What is the expected format to pass to nrf_cloud_agps_process()? I am working on an LwM2M server and want to be able to respond to /50001/0/{0,1} request coming from asset_tracker_v2 to improve TTFF.

Cheers,
Iman

[Øyvind]

Hello Iman, 

What is the expected format to pass to nrf_cloud_agps_process()?

I'm not sure what you are asking for here. Do you mean the API documentation for nrf_cloud_agps_process() in the nRF Cloud A-GPS library?

Asset Tracker v2 does not support an LwM2M client, only the LwM2M carrier library that facilitates an nRF91 device to connect to the device management servers, regardless of the other actions of the user application. It is mandatory to include the LwM2M carrier library in any AT&T, T-Mobile, or Verizon certified products as per the Mobile network operator certifications

Kind regards,
Øyvind

[ibiglari]

Hi,

Thanks for your reply. I managed to use LwM2M client with Asset Tracker v2, and it is communicating with my own LwM2M server (running a copy of Leshan demo server at the moment). I was hoping to be able to integrate SUPL binary into Asset Tracker v2 as well for AGPS, but enabling it would make the HEX file too large and west aborts the linking process. Then I decided to connect to Google SUPL server on my LwM2M server, and send the data back to Thingy91. My question is, what is the format of data nrf_cloud_agps_process() expects to receive in its first parameter?

[Øyvind]

Sorry for the delayed answer on this. Did you find a solution?

The nRF Cloud A-GPS schema can be found here
https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/net/lib/nrf_cloud/include/nrf_cloud_agps_schema_v1.h

Kind regards,
Øyvind