FakeTRX » History » Revision 18

Revision 17 (msuraev, 10/24/2018 01:59 PM) → Revision 18/44 (msuraev, 10/24/2018 02:01 PM)

h1. FakeTRX (Virtual Um-interface) 

 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! 

 h2. FAQ 

 h3. What is the difference from [[cellular-infrastructure:Virtual_Um|VIRT-PHY]]? 

 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. 

 h3. Python? 

 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. 

 h3. What about RSSI and ToA (Timing of Arrival)? 

 Since we are talking about the virtual interface, it's possible to emulate any values for both RSSI and ToA. 

 h3. Can I run multiple BTS and / or multiple MS instances? 

 Not yet. Related tickets: 

 h2. Running 

 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]]. 

 digraph G { 
     rankdir = LR; 
     subgraph cluster_M { 
         mobile1 [label="Mobile"]; 
         mobile2 [label="Mobile"]; 
         TRXcon1 [label="TRXcon"]; 
         TRXcon2 [label="TRXcon"]; 
         label = "Mobile side"; 
     subgraph cluster_N { 
         OsmoBTS1 [label="osmo-bts-trx"]; 
         OsmoBTS2 [label="osmo-bts-trx"]; 
         FakeTRX1 [label="FakeTRX"]; 
         FakeTRX2 [label="FakeTRX"]; 
         label = "Network side"; 
     FakeTRX1 -> OsmoBTS1 [label="TRX Interface"]; 
     FakeTRX2 -> OsmoBTS2 [label="TRX Interface"]; 
     OsmoBTS1 -> OsmoBSC; 
     OsmoBTS2 -> OsmoBSC; 
     mobile1 -> TRXcon1 [label="L1CTL"]; 
     mobile2 -> TRXcon2 [label="L1CTL"]; 
     TRXcon1 -> FakeTRX1 [label="TRX Interface"]; 
     TRXcon2 -> FakeTRX2 [label="TRX Interface"]; 

 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. 

 _Tip: feel free to use tmux or screen to avoid a mess with multiple windows_ 

 1. Run the network side stack you have. In this example we will use the [[osmonitb:|Network in the Box]]: 

 $ osmo-nitb -c ./openbsc.cfg -l ./hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM 

 2. Run the fake transceiver: 

 $ cd osmocom-bb/src/target/trx_toolkit/ 
 $ python ./ 

 3. Start [[OsmoBTS:]] (in case you want to [[cellular-infrastructure:build from source]], enable the TRX backend with @./configure --enable-trx=yes@). 

 $ osmo-bts-trx -c ./osmo-bts.cfg 

 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. 

 4. In order to make [[OsmocomBB:]] applications able to work with FakeTRX, you need to run [[TRX Interface#The-trxcon-application|trxcon]]: 

 $ cd osmocom-bb/src/host/trxcon/ 
 $ ./trxcon 

 5. Finally, run any L2&3 application, e.g. ccch_scan: 

 $ cd osmocom-bb/src/host/layer23/src/misc/ 
 $ ./ccch_scan -a ARFCN -i 

 Please note that ARFCN value should match the one your BTS configured to. 

 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. 

 h2. Running [[mobile]] application 

 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. 

   imsi 901700000000000 
   no barred-access 
   rplmn 901 70 

 Make sure you have the virtual network running, then run mobile the same way as in case of a Calypso based phone: 

 $ cd osmocom-bb/src/host/layer23/src/mobile/ 
 $ ./mobile -i 

 Now you can use mobile's telnet interface to manage your virtual phone: 

 $ telnet localhost 4247 
 $ ... 

 h3. Voice call example 



 h2. Demo 

 h2. Project status 


 * Simulation and randomization of both RSSI and ToA 
 * Burst capture to file (see 
 * Injection of bursts and commands 

 Further plans: 

 * Allow multiple BTS to work with multiple BB instances 
 * Distinguish debug messages (BTS / MS, ID)
Add picture from clipboard (Maximum size: 48.8 MB)