Project

General

Profile

FakeTRX » History » Version 23

msuraev, 11/15/2018 11:56 AM

1 1 fixeria
h1. FakeTRX (Virtual Um-interface)
2
3 8 fixeria
FakeTRX is a virtual Um-interface implementation written in Python, which allows you to connect [[OsmocomBB:]] and [[OsmoBTS:]] without actual RF hardware. The main purpose of this software is to facilitate and simplify the development and testing process. In other words, you don't need to physically run your GSM network nor use any kind of special hardware - just run a few scripts and do anything you want / need in your virtual GSM network!
4 1 fixeria
5
h2. FAQ
6
7 3 fixeria
h3. What is the difference from [[cellular-infrastructure:Virtual_Um|VIRT-PHY]]?
8 1 fixeria
9 3 fixeria
The main difference is that FakeTRX actually works on GSM L1, while [[cellular-infrastructure:Virtual_Um|VIRT-PHY]] works on higher levels, using GSMTAP and multicast sockets to exchange the data. It means that FakeTRX provides the [[TRX Interface]] for both [[OsmocomBB:]] and [[OsmoBTS:]], and forwards GSM bursts between both sides. So, no need to do any modifications in the [[OsmoBTS:]] source code, just use osmo-bts-trx.
10 1 fixeria
11 20 msuraev
h4. Interoperability with [[cellular-infrastructure:Virtual_Um|VIRT-PHY]]
12
13
TBD.
14
15 1 fixeria
h3. Python?
16
17
Of course, Python is slower than C, for example. But it's more than enough for exchanging UDP messages between [[OsmocomBB:]] and [[OsmoBTS:]], and vice versa. Moreover, it can be easily reimplemented in C, if someone interested in better performance.
18
19 19 msuraev
Once multiple instances are supported, we can benchmark to see what's the preformance bottleneck.
20
21 5 fixeria
h3. What about RSSI and ToA (Timing of Arrival)?
22 1 fixeria
23 5 fixeria
Since we are talking about the virtual interface, it's possible to emulate any values for both RSSI and ToA.
24 1 fixeria
25
h3. Can I run multiple BTS and / or multiple MS instances?
26
27 17 msuraev
Not yet. Related tickets: https://osmocom.org/issues/3666 https://osmocom.org/issues/3667
28 1 fixeria
29
h2. Running
30
31
This guide assumes that you already have the Osmocom GSM [[cellular-infrastructure:|network side stack]] compiled and installed. If not, the simplest way is to use the [[osmonitb:|Network in the Box]].
32
33 13 msuraev
{{graphviz_link()
34
digraph G {
35
    rankdir = LR;
36
    subgraph cluster_M {
37
        mobile1 [label="Mobile"];
38
        mobile2 [label="Mobile"];
39
        TRXcon1 [label="TRXcon"];
40
        TRXcon2 [label="TRXcon"];
41
        label = "Mobile side";
42
    }
43
    subgraph cluster_N {
44
        OsmoBSC;
45
        OsmoBTS1 [label="osmo-bts-trx"];
46
        OsmoBTS2 [label="osmo-bts-trx"];
47
        FakeTRX1 [label="FakeTRX"];
48
        FakeTRX2 [label="FakeTRX"];
49
        label = "Network side";
50
    }
51 15 msuraev
    FakeTRX1 -> OsmoBTS1 [label="TRX Interface"];
52
    FakeTRX2 -> OsmoBTS2 [label="TRX Interface"];
53 13 msuraev
    OsmoBTS1 -> OsmoBSC;
54
    OsmoBTS2 -> OsmoBSC;
55 14 msuraev
    mobile1 -> TRXcon1 [label="L1CTL"];
56
    mobile2 -> TRXcon2 [label="L1CTL"];
57 13 msuraev
    TRXcon1 -> FakeTRX1 [label="TRX Interface"];
58
    TRXcon2 -> FakeTRX2 [label="TRX Interface"];
59
    }
60
}
61
}}
62
63 6 fixeria
Since [[OsmocomBB:]] was extended with [[TRX Interface]] support, follow the corresponding instructions and compile OsmocomBB with [[TRX Interface#The-trxcon-application|trxcon]] application. After that, you may find the FakeTRX toolkit located in 'src/target/trx_toolkit/'. See README for more details.
64 1 fixeria
65
_Tip: feel free to use tmux or screen to avoid a mess with multiple windows_
66
67
1. Run the network side stack you have. In this example we will use the [[osmonitb:|Network in the Box]]:
68
69
<pre>
70
$ osmo-nitb -c ./openbsc.cfg -l ./hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM
71
</pre>
72
73
2. Run the fake transceiver:
74
75
<pre>
76 6 fixeria
$ cd osmocom-bb/src/target/trx_toolkit/
77 23 msuraev
$ python ./fake_trx.py -R 127.0.0.3 -r 127.0.0.23 -b 127.0.0.13
78 1 fixeria
</pre>
79
80 23 msuraev
Here we assume that osmo-bts-trx is available on 127.0.0.3, osmocom-bb (mobile or other program) is available on 127.0.0.23 and we use 127.0.0.13 as our own address. This allow us to run multiple transceivers (and mobiles) in parallel. In simple setups with only single fake_trx all IP-related parameters can be omitted.
81
82 11 osmith
3. Start [[OsmoBTS:]] (in case you want to [[cellular-infrastructure:build from source]], enable the TRX backend with @./configure --enable-trx=yes@).
83 1 fixeria
84
<pre>
85
$ osmo-bts-trx -c ./osmo-bts.cfg
86
</pre>
87
88 23 msuraev
If using explicit IP addresses as specified above, your osmo-bts.cfg should have following options set:
89
<pre>
90
phy 0
91
 osmotrx ip local 127.0.0.3
92
 osmotrx ip remote 127.0.0.13
93
</pre>
94
95 1 fixeria
Congratulations! Now you have a virtual GSM network running. As you can see, the virtual transceiver emulates the clock source, as this is required for [[OsmoBTS:]]. Also, it handles only a few important commands, such as RXTUNE and TXTUNE, but ignores other irrelevant ones.
96
97
4. In order to make [[OsmocomBB:]] applications able to work with FakeTRX, you need to run [[TRX Interface#The-trxcon-application|trxcon]]:
98
99
<pre>
100
$ cd osmocom-bb/src/host/trxcon/
101 23 msuraev
$ ./trxcon --trx-remote 127.0.0.13 --trx-bind 127.0.0.23
102 1 fixeria
</pre>
103 23 msuraev
104
Here we assume that trxcon is available on 127.0.0.13 and we use 127.0.0.23 as our own address. This allow us to run multiple transceivers (and mobiles) in parallel. In simple setups with only single fake_trx/trxcon all IP-related parameters can be omitted.
105 1 fixeria
106
5. Finally, run any L2&3 application, e.g. ccch_scan:
107
108
<pre>
109
$ cd osmocom-bb/src/host/layer23/src/misc/
110
$ ./ccch_scan -a ARFCN -i 127.0.0.1
111
</pre>
112
113
Please note that ARFCN value should match the one your BTS configured to.
114
115
Since this step, you should see the broadcast messages coming from the virtual network, like in case of a real one. You can use Wireshark to analyze them.
116
117
h2. Running [[mobile]] application
118
119 12 osmith
As you should already know, [[mobile]] applications implements a simple mobile phone with SMS, USSD and voice calls. In the virtual network we can benefit from using a virtual SIM card. Just configure one according to your network configuration, see the example below. If you are starting with the default config from the source tree (@osmocom-bb/doc/examples/mobile/default.cfg@), make sure to change @sim reader@ to @sim test@ in the @ms 1@ section.
120 1 fixeria
121
<pre>
122
test-sim
123
  imsi 901700000000000
124
  no barred-access
125
  rplmn 901 70
126
</pre>
127
128
Make sure you have the virtual network running, then run mobile the same way as in case of a Calypso based phone:
129
130
<pre>
131
$ cd osmocom-bb/src/host/layer23/src/mobile/
132
$ ./mobile -i 127.0.0.1
133
</pre>
134
135
Now you can use mobile's telnet interface to manage your virtual phone:
136
137
<pre>
138
$ telnet localhost 4247
139
$ ...
140
</pre>
141
142 18 msuraev
h3. Voice call example
143
144
TBD.
145
146
147 1 fixeria
h2. Demo
148
149
https://www.youtube.com/watch?v=Uxdaui8EkjY
150
151
h2. Project status
152
153 10 fixeria
Supported:
154
155
* Simulation and randomization of both RSSI and ToA
156
* Burst capture to file (see data_dump.py)
157
* Injection of bursts and commands
158
159 1 fixeria
Further plans:
160
161 21 msuraev
* Allow multiple BTS to work with multiple BB instances: https://osmocom.org/issues/3666 https://osmocom.org/issues/3667
162 22 msuraev
* Distinguish between various debug messages (BTS / MS, ID)
Add picture from clipboard (Maximum size: 48.8 MB)