Support for TDoA multiframe via COLLOS

Yash_Pahwa · December 17, 2018, 11:51am

I’ve updated my server and installed lora-geo-server (with Subscription keys from collos), along with it I’ve subscribed to Semtech LoRaWAN Localization in COLLOS (state is active now)

What to enter in the loraserver.toml, for the geolocation server ?
I’ve entered localhost:8005

Geolocation settings.
[geolocation_server]
server=“localhost:8005”

lora-geo-server.toml
[geo_server.backend]
name=“collos”
[geo_server.backend.collos]
subscription_key=“b01a45c56s710f5b64f45a12b10c48f7d4” (example key)

Is there any way that we can use the v2 endpoint that utilizes Tdoa Multiframe from Semtech Localization Algorithms?

Now, how to get the device location, is there any third party application for the collos APIs, or is the loraserver have some feature for the purpose?

brocaar · December 18, 2018, 1:14pm

The multiframe has not (yet) been implemented. The location will be published to MQTT or via HTTP by LoRa App Server.

Yash_Pahwa · December 19, 2018, 6:42am

As lora-geo-server is not sending any data to collos.

1)How to configure lora-geo-server to send data to collos?

OR

2)This means i have to send data to collos, manually(by mqtt or http)?

Yash_Pahwa · January 21, 2019, 6:02am

How the LoRa Server & LoRa Geo Server communicates with the COLLOS ? and how can the App Server get the location as the LoRa Geo Server is not providing any data to LoRa Server?

Please provide the proper configuration solution for getting the location.

Thanking you in advance

brocaar · January 21, 2019, 7:25am

LoRa Server sends a geolocation request to LoRa Geo Server which responds with the location. LoRa Server initiates the call, but does wait for a response from LoRa Geo Server.

sagarpatel · May 15, 2019, 10:57am

Hii @brocaar @Yash_Pahwa

i have created Collas account and subscribe 1 Semtech LoRaWAN Localization and subscriptions was active now i am seen 2 api keys Primary key and Secondary key

[geo_server.backend.collos]
  # Collos subscription key.
  #
  # This key can be retrieved after creating a Collos account at:
  # http://preview.collos.org/
  subscription_key=""

which key use to Configuration Lora Geo Server?
how can we get device location?

Thank you

sagarpatel · May 17, 2019, 10:07am

Hii,
please help me…!

brocaar · May 17, 2019, 11:32am

I think it doesn’t matter. You can use either the primary or secondary.

sagarpatel · May 17, 2019, 11:34am

but we cannot get any device location

any documentation related geo gRPC api call using c#?

Yash_Pahwa · May 18, 2019, 6:55pm

You should check the loraserver logs with debug messages “ON”, there you will find about the API calls for the Lora-geo-server.
Share the log details, it helps a lot in debugging the issues.

sagarpatel · May 20, 2019, 4:48am

Hii @Yash_Pahwa,

i got debug log of lora-geo-server

loraserver log

Thank you

Yash_Pahwa · May 20, 2019, 6:18am

You should make the log at the time, device is communicating with the server. there you will find the API calss for the location resolutions.

sagarpatel · May 20, 2019, 7:14am

Thanks @Yash_Pahwa

check below logs

currently we have only 1 gateway so it’s skipping geolocation meta-data
how many gateway we need for geolocation data?

Thank you

Yash_Pahwa · May 20, 2019, 8:10am

A Minimum of 3 gateways are required for the same (as per my knowledge)

brocaar · May 20, 2019, 9:09am

That is correct, you will need at least 3 gateways. Also make sure that you need gateways that provide an accurate timestamp / geolocation capabilities (e.g. Kerlink iBTS https://www.kerlink.com/product/wirnet-ibts/).

pooja.mittal · June 5, 2019, 12:59pm

Hi @brocaar!

It would be great if you could elaborate upon what exactly is a FineTimeStamp?

And in what format does the LoRa Server receive it and later on forwards it to LoRa Geo Server?

Thank you!

brocaar · June 5, 2019, 1:07pm

It is an accurate RX timestamp which can be used for triangulation. In general, this is implemented by “v2 gateways” like the Kerlink iBTS (which has a FPGA doing the timestamping). The timestamp of a “regular” gateway is not accurate enough for triangulation.

pooja.mittal · June 5, 2019, 1:15pm

Hello @brocaar, thank you so much for such a quick reply!

Currently, I don’t have Kerlink iBTS gateway but I’m using iC880A.

Could you kindly share Kerlink iBTS uplink frame, so that we can differentiate between both v1 and v2 gateways uplink frames (TimeStamp and FineTimeStamp) ?

Thank you!

brocaar · June 5, 2019, 1:39pm

It has an etime field (which contains an AES encrypted timestamp), see also:

github.com

brocaar/chirpstack-gateway-bridge/blob/master/internal/backend/semtechudp/packets/push_data.go#L277


	Time ExpandedTime `json:"time"` // UTC 'system' time of the gateway, ISO 8601 'expanded' format (e.g 2014-01-12 08:59:28 GMT)
	Lati float64      `json:"lati"` // GPS latitude of the gateway in degree (float, N is +)
	Long float64      `json:"long"` // GPS latitude of the gateway in degree (float, E is +)
	Alti int32        `json:"alti"` // GPS altitude of the gateway in meter RX (integer)
	RXNb uint32       `json:"rxnb"` // Number of radio packets received (unsigned integer)
	RXOK uint32       `json:"rxok"` // Number of radio packets received with a valid PHY CRC
	RXFW uint32       `json:"rxfw"` // Number of radio packets forwarded (unsigned integer)
	ACKR float64      `json:"ackr"` // Percentage of upstream datagrams that were acknowledged
	DWNb uint32       `json:"dwnb"` // Number of downlink datagrams received (unsigned integer)
	TXNb uint32       `json:"txnb"` // Number of packets emitted (unsigned integer)
}


// RXPK contain a RF packet and associated metadata.
type RXPK struct {
	Time *CompactTime `json:"time"` // UTC time of pkt RX, us precision, ISO 8601 'compact' format (e.g. 2013-03-31T16:21:17.528002Z)
	Tmms *int64       `json:"tmms"` // GPS time of pkt RX, number of milliseconds since 06.Jan.1980
	Tmst uint32       `json:"tmst"` // Internal timestamp of "RX finished" event (32b unsigned)
	AESK uint8        `json:"aesk"` //AES key index used for encrypting fine timestamps
	Chan uint8        `json:"chan"` // Concentrator "IF" channel used for RX (unsigned integer)
	RFCh uint8        `json:"rfch"` // Concentrator "RF chain" used for RX (unsigned integer)
	Stat int8         `json:"stat"` // CRC status: 1 = OK, -1 = fail, 0 = no CRC

pooja.mittal · June 6, 2019, 6:27am

Thanks for answering my queries @brocaar!