Feature #2969
closedobtain and store subscriber identity
100%
Description
osmo-bsc doesn't per se get hold of the subscriber identity except during a Paging Command.
However, osmo-bsc passes through all the DTAP between BTS and MSC, and in fact we have a DTAP filter in place in osmo-bsc's code base, which does obtain the mobile identity from the passing DTAP.
Using that code, it is possible to obtain the subscriber's IMSI/TMSI identity for all connections, and note it in the subscriber_connection's bsc_subscr struct for all other code to benefit from.
This is mainly useful for analysis / logging; for example, a handover log currently shows only the MT subscriber's identity:
DHODEC DEBUG handover_decision_2.c:1129 (lchan 1.020 TCH/F) (subscr unknown) MEASUREMENT REPORT DHODEC DEBUG handover_decision_2.c:1134 (lchan 1.020 TCH/F) (subscr unknown) 0: arfcn=868 bsic=63 neigh_idx=0 rxlev=35 flags=0 DHODEC DEBUG handover_decision_2.c:1129 (lchan 1.030 TCH/F) (subscr IMSI:901700000014701) MEASUREMENT REPORT DHODEC DEBUG handover_decision_2.c:1134 (lchan 1.030 TCH/F) (subscr IMSI:901700000014701) 0: arfcn=868 bsic=63 neigh_idx=0 rxlev=60 flags=0
Another example is the meas_feed feature, which in its last working implementation discards measurement reports for unknown subscribers instead of sending them out. (That could be changed, but adding the subscriber identity would probably be better.)
Checklist
- BSC side CommonID
- MSC side CommonID
- TTCN3 test for BSC side
- TTCN3 test for MSC side
Related issues
