Hi,
I'm reading the book "Die GSM-Dm-Kanäle im Dialog" by Joachim Göller, and I learned, that a mobile phone sends, about every second, a MEASUREMENT REPORT to the station, where it is logged. In this report the mobile sends the signal power of the cell, where it is logged, and of other neighborhood cells. With these signals, I can measure the distance of the mobile from my cell(s).
But I don't understand how can I get this values using OpenBSC.
It only does that when in an active dedicated channel (either a call or a sms or some other transaction). If you enable the debug for the DMEAS (either in the console or with the -d option), you should see those reports.
Also, it sends reports only for neighbor cell of your network (as specified in the BCCH SI messages).
Cheers,
Sylvain
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am Wed, 23 Jun 2010 10:06:26 +0200 schrieb Sylvain Munaut 246tnt@gmail.com:
It only does that when in an active dedicated channel (either a call or a sms or some other transaction). If you enable the debug for the DMEAS (either in the console or with the -d option), you should see those reports.
Also, it sends reports only for neighbor cell of your network (as specified in the BCCH SI messages).
Hi, Sylvain!
Thanks a lot for your answer! Now I see the measurement. I'll make some experiments... :D
Greetings - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello@netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag@netzing.de _______________________________________________________________________
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am Wed, 23 Jun 2010 10:06:26 +0200 schrieb Sylvain Munaut 246tnt@gmail.com:
It only does that when in an active dedicated channel (either a call or a sms or some other transaction). If you enable the debug for the DMEAS (either in the console or with the -d option), you should see those reports.
Also, it sends reports only for neighbor cell of your network (as specified in the BCCH SI messages).
Hi, again!
I tried to activate the DMEAS ("logging level meas everything" on Telnet), and to call a mobile phone. Now I have the problem, that I get TWO measurement reports... How can I filter the reports of just ONE mobile?
Thanks a lot - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello@netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag@netzing.de _______________________________________________________________________
On 06/23/2010 04:43 PM, Luca Bertoncello wrote:
I tried to activate the DMEAS ("logging level meas everything" on Telnet), and to call a mobile phone. Now I have the problem, that I get TWO measurement reports... How can I filter the reports of just ONE mobile?
You can try to set an imsi filter on the log:
"logging filter imsi IMSI"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am Wed, 23 Jun 2010 17:02:53 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
You can try to set an imsi filter on the log:
"logging filter imsi IMSI"
Unfortunately it does not work... If I just give "logging filter imsi XXX" OpenBSC logs nothing. I have to give "logging filter all 1", too, and then both measurements will be sent.
These looks like this:
========================== <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=0 RXL-FULL-ul=-110dBm RXL-SUB-ul=-110dBm RXQ-FULL-ul=5 RXQ-SUB-ul=0 BS_POWER=0 NOT VALID NUM_NEIGH=0 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=1 RXL-FULL-ul=-62dBm RXL-SUB-ul=-63dBm RXQ-FULL-ul=6 RXQ-SUB-ul=7 BS_POWER=0 NOT VALID NUM_NEIGH=0 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=2 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=3 RXQ-SUB-ul=2 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 NOT VALID NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=3 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=4 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=5 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=6 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=7 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=8 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=0 RXL-FULL-ul=-88dBm RXL-SUB-ul=-102dBm RXQ-FULL-ul=6 RXQ-SUB-ul=0 BS_POWER=0 NOT VALID NUM_NEIGH=0 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=9 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=1 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=2 RXQ-SUB-ul=2 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 DTXu NOT VALID NUM_NEIGH=7 <0009> abis_rsl.c:881 MEASUREMENT RESULT NR=10 RXL-FULL-ul=-47dBm RXL-SUB-ul=-47dBm RXQ-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 5dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dBm RXQ-FULL-dl=4 RXQ-SUB-dl=0 NUM_NEIGH=7 ==========================
If it is possible to filter (using an external program) which measurements come from a mobile, it is not a problem for me, but here I can't see any useful pattern...
Any idea? - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello@netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag@netzing.de _______________________________________________________________________
On 06/23/2010 05:31 PM, Luca Bertoncello wrote:
Am Wed, 23 Jun 2010 17:02:53 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
You can try to set an imsi filter on the log:
"logging filter imsi IMSI"
Unfortunately it does not work... If I just give "logging filter imsi XXX" OpenBSC logs nothing. I have to give "logging filter all 1", too, and then both measurements will be sent.
Well, look at src/debug.c and figure out why the imsi comparison is failing?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am Wed, 23 Jun 2010 17:50:19 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
Unfortunately it does not work... If I just give "logging filter imsi XXX" OpenBSC logs nothing. I have to give "logging filter all 1", too, and then both measurements will be sent.
Well, look at src/debug.c and figure out why the imsi comparison is failing?
I'm looking now this code. But I can't understand the reason... I can only suppose, that in this Measurement Report the IMSI will not be sent.
Thanks - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello@netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag@netzing.de _______________________________________________________________________
On 06/23/2010 06:01 PM, Luca Bertoncello wrote:
Am Wed, 23 Jun 2010 17:50:19 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
Unfortunately it does not work... If I just give "logging filter imsi XXX" OpenBSC logs nothing. I have to give "logging filter all 1", too, and then both measurements will be sent.
Well, look at src/debug.c and figure out why the imsi comparison is failing?
I'm looking now this code. But I can't understand the reason... I can only suppose, that in this Measurement Report the IMSI will not be sent.
if ((tar->filter_map & (1 << FLT_IMSI)) != 0 && subscr && strcmp(subscr->imsi, tar->filter_data[FLT_IMSI]) == 0) return 1;
the above does not evaluate to true... this can be:
a) because the filter function is not called at all.. b) tar->filter_map & .. is == 0 c) subscr is NULL d) the imsi's do not match..
Okay, after wanting to explain how the filtering is working, I remembered that I did this: 69e8f8285bf080ad2050fbc20f861bc8621e5c75 (git show that-number). You could git revert that-number and then try again.
So in the case of the measurement report the subscr is not set as context as the measurement debug is still in the abis_rsl context before it is hitting the BSC side...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am Wed, 23 Jun 2010 18:13:44 +0800 schrieb Holger Hans Peter Freyther holger@freyther.de:
if ((tar->filter_map & (1 << FLT_IMSI)) != 0 && subscr && strcmp(subscr->imsi, tar->filter_data[FLT_IMSI]) == 0) return 1;
the above does not evaluate to true... this can be:
a) because the filter function is not called at all.. b) tar->filter_map & .. is == 0 c) subscr is NULL d) the imsi's do not match..
Okay, after wanting to explain how the filtering is working, I remembered that I did this: 69e8f8285bf080ad2050fbc20f861bc8621e5c75 (git show that-number). You could git revert that-number and then try again.
So in the case of the measurement report the subscr is not set as context as the measurement debug is still in the abis_rsl context before it is hitting the BSC side...
Hi, Holger!
After I revert your changes, I can filter the measurements using IMSI. I suggest, your changes will committed back in the source tree...
Thanks a lot! - -- _______________________________________________________________________ Luca Bertoncello Entwicklung Mail: bertoncello@netzing.de
NETZING Solutions AG Tel.: 0351/41381 - 0 Kesselsdorfer Str. 216, 01169 Dresden Fax: 0351/41381 - 12 HRB 18926 / Ust.ID DE211326547 Mail: netzing.ag@netzing.de _______________________________________________________________________
On 06/23/2010 07:35 PM, Luca Bertoncello wrote:
Hi, Holger!
After I revert your changes, I can filter the measurements using IMSI. I suggest, your changes will committed back in the source tree...
Well,
the printing should move up to the MSC side of OpenBSC.. specially as the conn will become a pointer that may be null. Nevertheless I will revert the change for now.
-
Holger Hans Peter Freyther -
Luca Bertoncello -
Sylvain Munaut