GCI search & multiple cell location

Hello,

since location accuracy is not enough for us with single cell, we are trying to use multiple cell location.

We tries with %NCELLMEAS = 2 but we don't get multiple cells. Maybe the serving cell has good signal?

Then we tried with GCI search and fw 1.3.4.

%NCELLMEAS = 3,3

and we got those 3 cells (I added newlines for easiness of reading):

%NCELLMEAS: 0,

"0AAE62A2","22201","92B9",65535,0,6254,243,62,19,178936,0,0,

"0319AFA2","22201","92B8",65535,0,6254,295,62,18,178936,0,0,

"0094586F","22210","69D9",65535,0,6354,105,77,29,178973,0,0

so we tried to inject this data into the nrfCloud API:

{
  "lte": [
    {
      "mcc": 222,
      "mnc": 1,
      "eci": 179200674,
      "tac": 37561,
      "earfcn": 6254,
      "adv": 65535,
      "rsrp": -78,
      "rsrq": -10,
      "nmr": [
        {
          "earfcn": 6254,
          "pci": 295,
          "eci": 52015010,
          "rsrp": -78,
          "rsrq": -10.5
        },{
          "earfcn": 6354,
          "pci": 105,
          "eci": 9721967,
          "rsrp": -63,
          "rsrq": -5
        }
      ]
    }
  ]
}

and this is the response:

{
	"lat": 45.39999247,
	"lon": 11.90999508,
	"uncertainty": 2472,
	"fulfilledWith": "MCELL"
}

which does not give any improvement on the original location with SCELL.

Can you help us? Are we formatting the data the wrong way?

Marco

Parents Reply Children
  • Hi Marco,

    I can reproduce the issue. I see that it makes no difference whether the neighbor cells are included. This could be due to available cell towers in the area or that your SIM is locked down to one carrier with only access to certain towers. Do you have a different SIM that you could try? That may get you higher accuracy. 

    Cole

  • Dear Cole,

    I tried with other SIMs form other providers. But the cells that can be seen do not change much. I managed to add one more cell to the list:

    {
    	"lte": [
    		{
    			"mcc": 222,
    			"mnc": 1,
    			"eci": 52015010,
    			"tac": 37560,
    			"earfcn": 6254,
    			"adv": 65535,
    			"rsrp": -78,
    			"rsrq": -10
    		},
    		{
    			"mcc": 222,
    			"mnc": 1,
    			"eci": 179200674,
    			"tac": 37560,
    			"earfcn": 6254,
    			"adv": 65535,
    			"rsrp": -78,
    			"rsrq": -10
    		},
    		{
    			"mcc": 222,
    			"mnc": 1,
    			"eci": 179200673,
    			"tac": 37560,
    			"earfcn": 6254,
    			"adv": 65535,
    			"rsrp": -78,
    			"rsrq": -10
    		},
    		{
    			"mcc": 222,
    			"mnc": 10,
    			"eci": 9721967,
    			"tac": 37560,
    			"earfcn": 6354,
    			"adv": 64,
    			"rsrp": -78,
    			"rsrq": -10
    		}
    	]
    }

    However, no improvement on the response.

    NOTE: I am using Nb-IoT.

    I cannot really understand if this is working as expected. The cells in the nearby are actually in a range of 400m (red line on the map)

    So I don't understand:

    • why single cell location give only 2500m accuracy (if the device was 2500 metres away, it would receive other cells)
    • why multiple cell location does not give any improvement.

    Thanks & best

    Marco

    on 

  • Hi Marco,

    This is very odd indeed. I am passing your findings onto our vendors and will get back to you.

    Cole

  • Hi Cole,

    did you get any news from the vendors?

    thanks

    Marco

  • Hi everyone,

    We actually ran into the exact same issue.

    We use Soracom in Alberta, Canada and when using the GCI search types and mfw_v1.3.4 we do get additional cells as expected. However, when injecting these additional cells into the "nmr" section of the a location request to the nRF Cloud we don't see any improvement on the location either.

    Currently we are only evaluating the recent improvements on multicell, so we send the requests directly from the device using a service key.

    Thanks
    Alex

Related