Topics created by MeneerJacco

@meneerjacco

3GPP and finding the right docs is always challenging and time consuming :-). But once you know the doc number it is well managed and organized to download it:

3GPP document download

I assume you looking for R13 information? The following TS may be interesting

TS36.331

However I have no clue at what power levels the MIBs and SIBs are broadcasted. (afaik you need to sync and collect some info before you can send out the RRC Connection Setup Request)

Maybe somebody else here has more radio experience and knows?

Take this information with a grain of salt until we can get an expert on NB IoT technology to answer this question, but the CE level should be set by the modem based on the measured downlink received signal power and increased automatically when the random access preamble retransmission limit set for the current CE level by the network has been reached.
How long it takes to reach this limit depends on the limit and the period between retries (waiting for the network’s random access response).

They are still running, so this seems to be the (temporary) solution.

Last comment …

This is valid only for non eDRX downlink messages. eDRX messages are sent directly into the network and will be buffered by the mobile network until the device is available.

Unfortunately I don’t know how long the downlink message is buffered by the mobile Telekom network 😞

Regards, Roland

Hi,

currently it is not possible to query the IMSI of a device via the API.

BUT
the IMSI is delivered along with the lifecycle event when the device registeres it self.
In this case you get forwarded to your configured application url a payload like this.

{ "reports": [ { "serialNumber": "IMEI:123456789012345", "timestamp": 1623278710492, "subscriptionId": "63b07b01-4c14-4bba-8bc4-f3a89b3c94ff", "resourcePath": "uplinkMsg/0/data", "value": "500a060800101a181", "customAttributes": {} } ], "registrations": [ { "deviceType": "device", "serialNumber": "IMEI:123456789012345", "timestamp": 1623278710457, "make": "Generic", "model": "Sensor", "groupName": "TMNL.PROFESSIONAL.CON_0000001204", "imsi": "N/A", "protocol": "HTTP", "tags": "N/A", "subscriptionId": "cc48f3fa-7147-4b6d-9fe7-fe5b108e50dc", "deviceProps": { "device/0/imsi": "IMSI:123456789012346", "device/0/model": "Sensor", "uplinkMsg/0/data": "500a060800101a181", "device/0/manufacturer": "Generic", "connectivity/0/port": "62509", "connectivity/0/mncmcc": "", "location/0/longitude": "", "connectivity/0/cellid": "", "connectivity/0/ip": "10.0.5.183", "location/0/radius": "", "connectivity/0/rat": "", "location/0/latitude": "", "connectivity/0/apn": "" }, "customAttributes": {} } ], "deregistrations": [], "updates": [], "expirations": [], "responses": [] }

You can see the IMEI in the IoT Creators portal because we did some implementation regarding this 🙂

Hope this helps a bit.

Regards, Roland

@afzal_m Yes of course, I’ve sent them via PM. Thanks for the quick response!

@Stefan-de-Lange , @Uta I am referring to the device’s RSSI and SNR. I want to be able to check signal quality, as I have some experimental asset trackers with GPS that I am currently testing with.

With LoRaWAN devices, I found it very convenient that all kinds of additional “network”-information was available in the MQTT response (JSON) from the API.

As roaming is more or less transparent for the device as well as backend-end server, this recommendation formulated here https://forum.iotcreators.com/topic/594/data-packet-size still applies.

Hi @MeneerJacco
please send me your ICCID or IMSI in a private message via the forum chat tool and I’m going to look at your tariff.
Thanks,
Uta

@MeneerJacco you might check this entry as well, which points to a small web page doing the calculation work reg. at+cpsms command.
https://forum.iotcreators.com/topic/642/psm-calculation-tool-t3412-t3324-value-decoding?_=1622307153602

Be aware, that entering the value via at+cpsms is only a request towards the network. The network decides if your values are committed. To check the network reply, use

at+cereg=4

and check the values via:

at+cereg?

You can paste the reply in the above mentioned web page as well to get the values ‘decoded’.
My recommendation: set the active time (T3324) to a minimum and use the ‘RAI’ - release assistance indicator after sending data to shorten the RRC connected mode to a minimum. Then your device will enter PSM faster.
BR,
Markus