How to have an equivalent AT+COPS=<mode>,<format>,<opName>,<rat> using qapi API functions? | Thales IoT Developer Community

I mean, when we use the qapi functions to start a data call, we would follow these steps:

qapi_DSS_Set_Data_Call_Param(..., QAPI_DSS_CALL_INFO_TECH_PREF_E,...);
qapi_DSS_Set_Data_Call_Param(..., QAPI_DSS_CALL_INFO_APN_NAME_E,...);
qapi_DSS_Set_Data_Call_Param(..., QAPI_DSS_CALL_INFO_APN_USERNAME_E,...);
qapi_DSS_Set_Data_Call_Param(..., QAPI_DSS_CALL_INFO_APN_PASSWORD_E,...);
qapi_DSS_Set_Data_Call_Param(..., QAPI_DSS_CALL_INFO_IP_VERSION_E,...);
qapi_DSS_Set_Data_Call_Param(..., QAPI_DSS_CALL_INFO_UMTS_PROFILE_IDX_E,...);

/* Then after set the parameters, we start the data call */
qapi_DSS_Start_Data_Call(netctrl_dss_handle);

In the above snippet, I took it (simplified) from the examples/coap.c file in SDK examples folder.

So, following the snippet, what I would like to do is to explicitly tell via qapi that I want to connect to a NB.1 Network, and not in a Cat.M1 for example. This is required for my app so we can implement a fallback where if NB is not available, then we try to connect in Cat.M1, and so on.

In other words, I would expect to have something like this to set connection type:

/* example 
 * HERE IS A PARAMETER I MADE UP TO EXAMPLIFY */
qapi_DSS_Set_Data_Call_Param(..., CONNECTION_CAT_M1, ...);

/* then after configuring params, connect */
qapi_DSS_Start_Data_Call();

/* then verify that I am really connected in Cat.M1 
 * HERE IS A FUNC I MADE UP */
conn = qapi_DSS_Get_Data_Call_Param(..., GET_CONNECTION_TECHNOLOGY, ...);

if (conn != CONNECTION_CAT_M1)
{
  /* we are not connected in tech we expected, log something */
}