Project

General

Profile

FakeTRX » History » Version 25

fixeria, 01/17/2019 01:58 PM

1 1 fixeria
h1. FakeTRX (Virtual Um-interface)
2 1 fixeria
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 24 msuraev
Normally trxcon [[TRX Interface]] would be used for GR-GSM to implement client (mobile) side of the transceiver. The OsmoTRX implements server (BTS) side of transceiver and is used by osmo-bts-trx. FakeTRX acts as a bridge between them altering Uplink/Downlink headers as necessary which removes the need for actual hardware.
6 24 msuraev
7 1 fixeria
h2. FAQ
8 1 fixeria
9 3 fixeria
h3. What is the difference from [[cellular-infrastructure:Virtual_Um|VIRT-PHY]]?
10 1 fixeria
11 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.
12 1 fixeria
13 20 msuraev
h4. Interoperability with [[cellular-infrastructure:Virtual_Um|VIRT-PHY]]
14 20 msuraev
15 20 msuraev
TBD.
16 20 msuraev
17 1 fixeria
h3. Python?
18 1 fixeria
19 1 fixeria
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.
20 1 fixeria
21 19 msuraev
Once multiple instances are supported, we can benchmark to see what's the preformance bottleneck.
22 19 msuraev
23 5 fixeria
h3. What about RSSI and ToA (Timing of Arrival)?
24 1 fixeria
25 5 fixeria
Since we are talking about the virtual interface, it's possible to emulate any values for both RSSI and ToA.
26 1 fixeria
27 1 fixeria
h3. Can I run multiple BTS and / or multiple MS instances?
28 1 fixeria
29 17 msuraev
Not yet. Related tickets: https://osmocom.org/issues/3666 https://osmocom.org/issues/3667
30 1 fixeria
31 1 fixeria
h2. Running
32 1 fixeria
33 1 fixeria
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]].
34 1 fixeria
35 13 msuraev
{{graphviz_link()
36 13 msuraev
digraph G {
37 13 msuraev
    rankdir = LR;
38 13 msuraev
    subgraph cluster_M {
39 13 msuraev
        mobile1 [label="Mobile"];
40 13 msuraev
        mobile2 [label="Mobile"];
41 13 msuraev
        TRXcon1 [label="TRXcon"];
42 13 msuraev
        TRXcon2 [label="TRXcon"];
43 13 msuraev
        label = "Mobile side";
44 13 msuraev
    }
45 13 msuraev
    subgraph cluster_N {
46 13 msuraev
        OsmoBSC;
47 13 msuraev
        OsmoBTS1 [label="osmo-bts-trx"];
48 13 msuraev
        OsmoBTS2 [label="osmo-bts-trx"];
49 13 msuraev
        FakeTRX1 [label="FakeTRX"];
50 13 msuraev
        FakeTRX2 [label="FakeTRX"];
51 13 msuraev
        label = "Network side";
52 13 msuraev
    }
53 15 msuraev
    FakeTRX1 -> OsmoBTS1 [label="TRX Interface"];
54 15 msuraev
    FakeTRX2 -> OsmoBTS2 [label="TRX Interface"];
55 13 msuraev
    OsmoBTS1 -> OsmoBSC;
56 13 msuraev
    OsmoBTS2 -> OsmoBSC;
57 14 msuraev
    mobile1 -> TRXcon1 [label="L1CTL"];
58 14 msuraev
    mobile2 -> TRXcon2 [label="L1CTL"];
59 13 msuraev
    TRXcon1 -> FakeTRX1 [label="TRX Interface"];
60 13 msuraev
    TRXcon2 -> FakeTRX2 [label="TRX Interface"];
61 13 msuraev
    }
62 13 msuraev
}
63 13 msuraev
}}
64 13 msuraev
65 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.
66 1 fixeria
67 1 fixeria
_Tip: feel free to use tmux or screen to avoid a mess with multiple windows_
68 1 fixeria
69 1 fixeria
1. Run the network side stack you have. In this example we will use the [[osmonitb:|Network in the Box]]:
70 1 fixeria
71 1 fixeria
<pre>
72 1 fixeria
$ osmo-nitb -c ./openbsc.cfg -l ./hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM
73 1 fixeria
</pre>
74 1 fixeria
75 1 fixeria
2. Run the fake transceiver:
76 1 fixeria
77 1 fixeria
<pre>
78 6 fixeria
$ cd osmocom-bb/src/target/trx_toolkit/
79 23 msuraev
$ python ./fake_trx.py -R 127.0.0.3 -r 127.0.0.23 -b 127.0.0.13
80 1 fixeria
</pre>
81 1 fixeria
82 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.
83 23 msuraev
84 11 osmith
3. Start [[OsmoBTS:]] (in case you want to [[cellular-infrastructure:build from source]], enable the TRX backend with @./configure --enable-trx=yes@).
85 1 fixeria
86 1 fixeria
<pre>
87 1 fixeria
$ osmo-bts-trx -c ./osmo-bts.cfg
88 1 fixeria
</pre>
89 1 fixeria
90 23 msuraev
If using explicit IP addresses as specified above, your osmo-bts.cfg should have following options set:
91 23 msuraev
<pre>
92 23 msuraev
phy 0
93 23 msuraev
 osmotrx ip local 127.0.0.3
94 23 msuraev
 osmotrx ip remote 127.0.0.13
95 23 msuraev
</pre>
96 23 msuraev
97 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.
98 1 fixeria
99 1 fixeria
4. In order to make [[OsmocomBB:]] applications able to work with FakeTRX, you need to run [[TRX Interface#The-trxcon-application|trxcon]]:
100 1 fixeria
101 1 fixeria
<pre>
102 1 fixeria
$ cd osmocom-bb/src/host/trxcon/
103 23 msuraev
$ ./trxcon --trx-remote 127.0.0.13 --trx-bind 127.0.0.23
104 1 fixeria
</pre>
105 23 msuraev
106 23 msuraev
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.
107 1 fixeria
108 1 fixeria
5. Finally, run any L2&3 application, e.g. ccch_scan:
109 1 fixeria
110 1 fixeria
<pre>
111 1 fixeria
$ cd osmocom-bb/src/host/layer23/src/misc/
112 1 fixeria
$ ./ccch_scan -a ARFCN -i 127.0.0.1
113 1 fixeria
</pre>
114 1 fixeria
115 1 fixeria
Please note that ARFCN value should match the one your BTS configured to.
116 1 fixeria
117 1 fixeria
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.
118 1 fixeria
119 1 fixeria
h2. Running [[mobile]] application
120 1 fixeria
121 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.
122 1 fixeria
123 1 fixeria
<pre>
124 1 fixeria
test-sim
125 1 fixeria
  imsi 901700000000000
126 1 fixeria
  no barred-access
127 1 fixeria
  rplmn 901 70
128 1 fixeria
</pre>
129 1 fixeria
130 1 fixeria
Make sure you have the virtual network running, then run mobile the same way as in case of a Calypso based phone:
131 1 fixeria
132 1 fixeria
<pre>
133 1 fixeria
$ cd osmocom-bb/src/host/layer23/src/mobile/
134 1 fixeria
$ ./mobile -i 127.0.0.1
135 1 fixeria
</pre>
136 1 fixeria
137 1 fixeria
Now you can use mobile's telnet interface to manage your virtual phone:
138 1 fixeria
139 1 fixeria
<pre>
140 1 fixeria
$ telnet localhost 4247
141 1 fixeria
$ ...
142 1 fixeria
</pre>
143 1 fixeria
144 1 fixeria
h2. Demo
145 1 fixeria
146 1 fixeria
https://www.youtube.com/watch?v=Uxdaui8EkjY
147 1 fixeria
148 1 fixeria
h2. Project status
149 1 fixeria
150 10 fixeria
Supported:
151 10 fixeria
152 10 fixeria
* Simulation and randomization of both RSSI and ToA
153 10 fixeria
* Burst capture to file (see data_dump.py)
154 10 fixeria
* Injection of bursts and commands
155 10 fixeria
156 1 fixeria
Further plans:
157 1 fixeria
158 21 msuraev
* Allow multiple BTS to work with multiple BB instances: https://osmocom.org/issues/3666 https://osmocom.org/issues/3667
159 22 msuraev
* Distinguish between various debug messages (BTS / MS, ID)
Add picture from clipboard (Maximum size: 48.8 MB)