Project

General

Profile

OsmoTRX » History » Version 65

laforge, 10/21/2017 03:21 PM

1 41 ttsou
{{>toc}}
2 1 ttsou
3 41 ttsou
h1. [[OsmoTRX]]
4 1 ttsou
5
6 41 ttsou
[[OsmoTRX]] is a software-defined radio transceiver that implements the Layer 1 physical layer of a BTS comprising the following 3GPP specifications:
7
* TS 05.01 "Physical layer on the radio path"
8
* TS 05.02 "Multiplexing and Multiple Access on the Radio Path"
9
* TS 05.04 "Modulation"
10
* TS 05.10 "Radio subsystem synchronization"
11 1 ttsou
12 49 neels
[[OsmoTRX]] is based on the transceiver code from the [[OsmoBTS:OpenBTS]] project, but setup to operate independently with the purpose of using with non-OpenBTS software and projects, while still maintaining backwards compatibility with [[OsmoBTS:OpenBTS]]. Currently there are numerous features contained in [[OsmoTRX:]] that extend the functionality of the [[OsmoBTS:OpenBTS]] transceiver. These features include enhanced support for various embedded platforms - notably ARM - and dual channel diversity support for the Fairwaves [[umtrx:]].
13 41 ttsou
14 65 laforge
h2. OsmoTRX in the Osmocom GSM architecture (old OsmoNITB case)
15 46 laforge
16
{{graphviz_link()
17
digraph G {
18
    rankdir = LR;
19
    SDR -> OsmoTRX [label="Raw Samples"];
20
    OsmoTRX -> OsmoBTS [label="bursts over UDP"];
21 1 ttsou
    OsmoBTS -> OsmoNITB [label="Abis/IP"];
22 65 laforge
    OsmoBTS -> OsmoPCU [label="pcu_sock"];
23
    OsmoPCU -> OsmoSGSN [label="Gb/IP"];
24
    OsmoTRX [color=red];
25
}
26
}}
27
28
h2. OsmoTRX in the Osmocom GSM architecture (new OsmoBSC+OsmoMSC case)
29
30
{{graphviz_link()
31
digraph G {
32
    rankdir = LR;
33
    SDR -> OsmoTRX [label="Raw Samples"];
34
    OsmoTRX -> OsmoBTS [label="bursts over UDP"];
35
    OsmoBTS -> OsmoBSC [label="Abis/IP"];
36
    OsmoBSC -> OsmoMSC [label="AoIP"];
37 46 laforge
    OsmoBTS -> OsmoPCU [label="pcu_sock"];
38
    OsmoPCU -> OsmoSGSN [label="Gb/IP"];
39
    OsmoTRX [color=red];
40
}
41
}}
42 41 ttsou
43 62 laforge
h2. RF Hardware support
44 41 ttsou
45 1 ttsou
46 62 laforge
Multiple RF devices are currently supported. These include USRP family products from Ettus Research, and the [[UmTRX:]] from Fairwaves.
47
48
more details (e.g. signal levels) are provided in the hardware specific pages:
49
{{child_pages(HardwareSupport)}}
50
51
52
h2. Embedded Platform Support
53
54
[[OsmoTRX]] has been tested on the multiple embedded platforms representing a wide range of device types. Low cost ARM devices are generally limited by memory and I/O as much CPU utilization.
55
56
Running a full or near full ARFCN configuration (7 simultaneous TCH channels with Combination V) may require running the GSM stack remotely, which can be configured at runtime on the command line. This limitation appears to be scheduling related more so than lack of CPU resources, and may be resolved at a later time.
57
58
|_.Platform|_.SoC*|_.Processor|_.SIMD/FPU|_.Testing Notes|
59
|ArndaleBoard|Samsung Exynos 5250|ARM Cortex-A15|NEON-VFPv4|7 TCH|
60
|BeagleBoard-xM|Texas Instruments OMAP3|ARM Cortex-A8|NEON|7 TCH, remote [[osmobts:]] stack|
61
|Ettus E100|Texas Instruments OMAP3|ARM Cortex-A8|NEON|7 TCH, remote [[osmobts:]] stack|
62
|Raspberry Pi|Broadcom BCM2835|ARM11|VFP|2 TCH, remote [[osmobts:]] stack|
63
|Shuttle PC|NA|Intel Atom D2550|SSE3|Dual channel, 15 TCH|
64
65
All embedded plaforms were tested with low-phase error modulator disabled. Use of the more accurate modulator on embedded platforms has not been extensively tested.
66
67
68
h2. Features
69
70 41 ttsou
*Intel SSE Support*
71 6 ttsou
* SSE3
72
* SSE4.1
73 20 ttsou
74 41 ttsou
On Intel processors, [[OsmoTRX]] makes heavy use of the Streaming SIMD Extensions (SSE) instruction set. Accelerated operations include pulse shape filtering, resampling, sequence correlation, and many other signal processing operations. SSE3 is the minimum requirement for accelerated use.
75 1 ttsou
76 20 ttsou
SSE3 is present in the majority of Intel processors since later versions of the Pentium 4 architecture and is also present on low power Atom processors. Support is automatically detected at build time. For additional performance information, please see the performance and benchmarks section.
77 29 ttsou
78 41 ttsou
*ARM Support*
79 1 ttsou
* NEON
80
* NEON-VFPv4
81 20 ttsou
82 41 ttsou
[[OsmoTRX]] runs on a variety of ARM processors with and without NEON coprocessors. Like SSE on Intel processors, NEON provides acceleration with SIMD vectorized instructions.
83 20 ttsou
84 1 ttsou
Tested popular architectures include ARM11 (Raspberry Pi), Cortex-A8 (!BeagleBoard), and Cortex-A15 (!ArndaleBoard). Loosely speaking, these platforms are representative of low cost embedded devices, mid-level handsets, and high-end smartphones respectively. Similarly, in order, these platforms include no NEON coprocessor, standard NEON, and NEON-VFPv4. The latter NEON variation, VFPv4, provides additional fused-multiply-accumulate (FMA) instructions useful for many DSP operations.
85
86 26 ttsou
NEON support must be enabled by the user at build time. For additional information, please see the configuration and performance and benchmarks sections.
87 37 ttsou
88 41 ttsou
*Dual Channel (UmTRX and B210)*
89 7 ttsou
90 1 ttsou
Two dual channel modes are available: standard dual channel mode and diversity. In standard dual channel mode, each RF
91 28 ttsou
path of the dual channel device supports a different ARFCN. Each path operates independently a
92 1 ttsou
nd operates similarly to two separate devices. GSM channel capacity in this mode is doubled. This option can be configured at run time from the command line.
93
94 41 ttsou
*Dual Channel Diversity (UmTRX, experimental)*
95 1 ttsou
96 28 ttsou
Diversity mode is similar to the standard dual channel mode except each antenna supports both ARFCN channels. In this case, the receiver sample bandwidth is widened to handle both ARFCN's and subsequently converted and demultiplexed into separate sample streams. Each GSM receive path is fed dual signals, where antenna selection diversity is performed by taking the stronger signal on a burst-by-burst basis. This diversity setup improves uplink reception performance in multipath fading environments.
97 16 ttsou
98 28 ttsou
Limitations are increased CPU utilization and that ARFCN spacing is restricted (currently at 400 kHz) by the receiver sampling bandwidth. Setting the ARFCN spacing beyond the sampling limit will disable the diversity path and operate in standard dual channel mode. This options can be configured at run time from the command line.
99 58 ipse
100 1 ttsou
*Uplink Burst Detection*
101 41 ttsou
102 1 ttsou
[[OsmoTRX]] utilizes an updated receive burst detection algorithm that provides greater sensitivity and reliability than the original [[OsmoBTS:OpenBTS]] approach, which relied on energy detection for the initial stage of burst acquisition.
103
104 50 neels
The limitation of the previous approach was that it was slow to adapt to highly transient power levels and false burst detection in challenging situations such as receiver saturation, which may occur in close range lab testing. The other issue was that a high degree of level tuning was often necessary to operate reliably.
105 41 ttsou
106 1 ttsou
The current receiver code addressed those limitations for improved performance in a wider variety of environments.
107 60 laforge
108 59 roh
*Low Phase Error Modulator*
109 41 ttsou
110 1 ttsou
The default GSM downlink signal is configured for low distortion using a linearized GMSK modulator. The implementation is based on a two pulse Laurent approximation of continuous phase modulated (CPM) signals. The baseband output signal measures with very low phase error and is capable of passing industry spectrum mask requirements. Please note that actual performance will depend strongly on the particular device in use.
111 41 ttsou
112
Theoretical details can be found in the report on "GMSK":http://tsou.cc/gsm/report_gmsk.pdf. Octave / Matlab code for "pulse generation":http://tsou.cc/gsm/laurent.m is also available.
113
114 1 ttsou
This option can be enabled or disabled at run time from the command line.
115
116 43 laforge
Very Low Phase Error (Ettus Research N200)
117
118
!osmo-trx-phase.gif!
119
120
Spectrum Mask (Ettus Research N200)
121
122 1 ttsou
!osmo-trx-spectrum.gif!
123
124 19 ttsou
125 41 ttsou
h2. Mailing List
126 22 ttsou
127 41 ttsou
128 49 neels
For development purposes, [[OsmoTRX:]] is discussed on both [[OsmoBTS:OpenBTS]] and [[OpenBSC:]] mailing lists at openbts-discuss@lists.sourceforge.net and openbsc@lists.osmocom.org respectively.
129 41 ttsou
130 1 ttsou
Please direct questions and bug reports to the list appropriate for the GSM stack being used.
131 41 ttsou
132 47 laforge
Subscription information is available at "and [http://lists.osmocom.org/mailman/listinfo/openbsc/":https://lists.sourceforge.net/lists/listinfo/openbts-discuss].  Please make sure to read our [[cellular-infrastructure:MailingListRules]] before posting.
133 1 ttsou
134 41 ttsou
h2. GPRS support
135 1 ttsou
136 64 laforge
* [[OsmoTRX]] supports the GPRS (and EGPRS/EDGE) features of [[osmoPCU:]] and [[osmoBTS:]] as well as the remaining Osmocom stack, such as [[OsmoSGSN:]] and [[OpenGGSN:OsmoGGSN]]
137 61 laforge
* [[OsmoTRX]] does not support GPRS in combination with [[OsmoBTS:OpenBTS]].  For that, please use the transceiver supplied with [[OsmoBTS:OpenBTS]].
138 41 ttsou
139
h2. Source code
140
141
142 1 ttsou
The source code is available from git.osmocom.org (module osmo-trx).
143 18 ttsou
144
Public read-only access is available via
145 41 ttsou
<pre>
146 19 ttsou
$ git clone git://git.osmocom.org/osmo-trx
147 41 ttsou
</pre>
148 1 ttsou
You can browse it via cgit: http://cgit.osmocom.org/cgit/osmo-trx/
149
150 48 neels
h2. Dependencies
151 1 ttsou
152 48 neels
Install libusb-1.0 and libbost dev packages. On debian 8.4:
153 1 ttsou
154 48 neels
<pre>
155
sudo apt-get install --no-install-recommends libusb-1.0-0-dev libboost-dev
156
</pre>
157 41 ttsou
158 53 neels
h3. UHD
159 1 ttsou
160 48 neels
Unless using USRP1, you will need the Universal Hardware Driver (UHD),
161
which is available from Ettus Research or Fairwaves; the UHD implementation
162
must match your hardware:
163
164
* Ettus Research UHD for USRP devices
165 51 neels
* Fairwaves UHD with [[UmTRX:]]
166 48 neels
* USRP1 does not use the UHD driver, it is supported through the legacy libusrp driver provided in GNU Radio 3.4.2.
167
168 55 wirelesss
h3. UHD for Debian
169 48 neels
170 52 neels
When you are reading this, Debian packages for UHD may be sufficient for running osmo-trx and osmo-bts-trx.
171 48 neels
here are some of the packages that need to be installed:
172
173
<pre>
174 54 neels
sudo apt-get install libuhd-dev uhd-host
175 48 neels
</pre>
176 1 ttsou
177 55 wirelesss
*Troubleshooting:*
178
 
179 52 neels
At the time of writing this (2016-12), for Debian 8 aka jessie you need to use the jessie-backports packages:
180
181
<pre>
182
sudo -s
183
echo "deb http://ftp.de.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/uhd.list
184
apt-get update
185
apt-get -t jessie-backports install libuhd-dev uhd-host
186
</pre>
187
188
It may also be possible to use the pothos PPA instead:
189 48 neels
190
<pre>
191
sudo add-apt-repository ppa:guruofquality/pothos
192
sudo apt-get update
193
sudo apt install libboost-dev uhd
194
</pre>
195
196 53 neels
h3. Firmware
197 48 neels
198
You also need to download the firmware using a script provided by the UHD package.
199
Instructions suggest running the script as root, but this way is less dangerous:
200
201
<pre>
202
sudo mkdir /usr/share/uhd
203
sudo chown $USER: /usr/share/uhd
204
/usr/lib/uhd/utils/uhd_images_downloader.py
205
</pre>
206
207 63 pespin
You can flash the FPGA data you just downloaded with the following command, setting type and other parameters accordingly to your hw. For instance for an Ettus B200:
208
<pre>
209
uhd_image_loader --args="type=b200"
210
</pre>
211
212
The uhd_image_loader claims it can update the firmware too, but at least on some versions it does nothing when asked to update firmware. If you see no output of firwmare being flashed, you can use this other command line to flash the firmware, adapting it to the firmware file of your HW:
213
<pre>
214
/usr/lib/uhd/utils/b2xx_fx3_utils --load-fw /usr/share/uhd/images/usrp_b200_fw.hex
215
</pre>
216
217 53 neels
h3. Group
218 48 neels
219
You may need to add yourself to the usrp group:
220
221
<pre>
222
sudo gpasswd -a $USER usrp
223
# and re-login to acquire the group
224
</pre>
225
226 53 neels
h3. Verify
227 48 neels
228
run uhd_find_devices to make sure b200 is available:
229
230
<pre>
231
$ uhd_find_devices 
232
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown
233
234
--------------------------------------------------
235
-- UHD Device 0
236
--------------------------------------------------
237
Device Address:
238
    type: b200
239
    name: MyB210
240
    serial: 1C0FFEE
241
    product: B210
242
</pre>
243
244
h2. Configuration and Build
245
246 41 ttsou
First, run autoreconf to remake the build system files.
247 1 ttsou
<pre>
248 18 ttsou
$ autoreconf -i
249 41 ttsou
...
250 18 ttsou
</pre>
251 41 ttsou
252 18 ttsou
*Intel Platforms (All)*
253 1 ttsou
254 41 ttsou
Intel SSE support is automatically detected on Intel x86 platforms. No user intervention is necessary. The general configuration defaults to the low phase error modulator. Atom users may wish to use the low-CPU utilization modulator, which can be later enabled from the command line at runtime.
255 18 ttsou
<pre>
256 1 ttsou
$ ./configure
257
...
258 19 ttsou
checking whether mmx is supported... yes
259 18 ttsou
checking whether sse is supported... yes
260
checking whether sse2 is supported... yes
261
checking whether sse3 is supported... yes
262
checking whether ssse3 is supported... yes
263
checking whether sse4.1 is supported... yes
264
checking whether sse4.2 is supported... yes
265 41 ttsou
...
266 18 ttsou
</pre>
267 41 ttsou
268 18 ttsou
*ARM Platforms with NEON*
269 41 ttsou
270
Many popular ARM development boards fall under this category including BeagleBoard, PandaBoard, and Ettus E100 USRP. This option will disable the low phase error modulator, which can be re-enabled at runtime. NEON support must be manually enabled.
271 24 ttsou
<pre>
272 41 ttsou
$ ./configure --with-neon
273 1 ttsou
</pre>
274 41 ttsou
275 1 ttsou
*ARM Platforms with NEON-VFPv4*
276 41 ttsou
277
Currently very few development platforms support this instruction set, which is seen mainly in high end smartphones and tablets. Available development boards are ArndaleBoard and ODROID-XU. This option will disable the low phase error modulator, which can be re-enabled at runtime. NEON-VFPv4 support must be manually enabled.
278 1 ttsou
<pre>
279 41 ttsou
$ ./configure --with-neon-vfpv4
280 1 ttsou
</pre>
281 41 ttsou
282 1 ttsou
*ARM Platforms without NEON*
283 41 ttsou
284 1 ttsou
This configuration mainly targets the Raspberry Pi. ARM platforms without NEON vector units are almost always very slow processors, and generally not very suitable for running [[OsmoTRX]]. Running [[OsmoTRX]] on a Raspberry Pi, however, is possible along with limited TCH (voice) channel support. Currently this configuration requires minor code changes.
285
286
Coming soon...
287 41 ttsou
288 1 ttsou
*Build and Install*
289 16 ttsou
290
After configuration, installation is simple.
291 41 ttsou
292 16 ttsou
<pre>
293
$ make
294 41 ttsou
$ sudo make install
295 16 ttsou
</pre>
296
297 41 ttsou
h2. Running
298 16 ttsou
299 56 wirelesss
Normally simply start osmo-trx.
300 41 ttsou
301 56 wirelesss
<pre>
302
$ osmo-trx
303
linux; GNU C++ version 5.3.1 20151219; Boost_105800; UHD_003.009.002-0-unknown
304
305
opening configuration table from path :memory:
306
Config Settings
307
   Log Level............... NOTICE
308
   Device args............. 
309
   TRX Base Port........... 5700
310
   TRX Address............. 127.0.0.1
311
   Channels................ 1
312
   Tx Samples-per-Symbol... 4
313
   Rx Samples-per-Symbol... 1
314
   EDGE support............ Disabled
315
   Reference............... Internal
316
   C0 Filler Table......... Disabled
317
   Multi-Carrier........... Disabled
318
   Diversity............... Disabled
319
   Tuning offset........... 0
320
   RSSI to dBm offset...... 0
321
   Swap channels........... 0
322
323
-- Detected Device: B200
324
-- Loading FPGA image: /usr/share/uhd/images/usrp_b200_fpga.bin... done
325
-- Operating over USB 2.
326
-- Detecting internal GPSDO.... No GPSDO found
327
-- Initialize CODEC control...
328
-- Initialize Radio control...
329
-- Performing register loopback test... pass
330
-- Performing CODEC loopback test... pass
331
-- Asking for clock rate 16.000000 MHz... 
332
-- Actually got clock rate 16.000000 MHz.
333
-- Performing timer loopback test... pass
334
-- Setting master clock rate selection to 'automatic'.
335
-- Asking for clock rate 26.000000 MHz... 
336
-- Actually got clock rate 26.000000 MHz.
337
-- Performing timer loopback test... pass
338
-- Setting B200 4/1 Tx/Rx SPS
339
-- Transceiver active with 1 channel(s)
340
</pre>
341
342 41 ttsou
[[OsmoTRX]] can be configured with a variety of options on the command line. In most cases, the default settings will suffice. Notable options include UHD device argument passing, which is often useful for using network based devices with firewalls, and external 10 MHz reference support.
343
344 16 ttsou
<pre>
345
$ osmo-trx -h
346
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.005.004-140-gfb32ed16
347
348
Options:
349 1 ttsou
  -h    This text
350 16 ttsou
  -a    UHD device args
351
  -l    Logging level (EMERG, ALERT, CRT, ERR, WARNING, NOTICE, INFO, DEBUG)
352 1 ttsou
  -i    IP address of GSM core
353
  -p    Base port number
354 16 ttsou
  -d    Enable dual channel diversity receiver
355
  -x    Enable external 10 MHz reference
356 38 ttsou
  -s    Samples-per-symbol (1 or 4)
357
  -c    Number of ARFCN channels (default=1)
358 16 ttsou
  -f    Enable C0 filler table
359 41 ttsou
  -o    Set baseband frequency offset (default=auto)
360 16 ttsou
</pre>
361 41 ttsou
362 1 ttsou
<pre>
363 16 ttsou
$ osmo-trx -a "addr=192.168.10.2"
364
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.004.000-b14cde5
365
366
Config Settings
367 1 ttsou
   Log Level............... INFO
368 16 ttsou
   Device args............. addr=192.168.10.2
369 1 ttsou
   TRX Base Port........... 5700
370 16 ttsou
   TRX Address............. 127.0.0.1
371
   Channels................ 1
372
   Samples-per-Symbol...... 4
373
   External Reference...... Disabled
374
   Diversity............... Disabled
375 41 ttsou
376 13 ttsou
-- Opening a [[UmTRX]] device...
377 38 ttsou
-- Current recv frame size: 1472 bytes
378 41 ttsou
-- Current send frame size: 1472 bytes
379 38 ttsou
-- Setting [[UmTRX]] 4 SPS
380 41 ttsou
-- Transceiver active with 1 channel(s)
381 38 ttsou
</pre>
382 1 ttsou
383 49 neels
h2. [[OsmoTRX]] with [[OsmoBTS:OpenBTS]]
384 38 ttsou
385
386 49 neels
[[OsmoTRX]] is fully compatible with [[OsmoBTS:OpenBTS]] for voice and SMS services. Due to differences in handing of GPRS, [[OsmoTRX]] does not support GPRS when used with [[OsmoBTS:OpenBTS]], however, GPRS with the Osmocom stack is supported.
387 41 ttsou
388 49 neels
For use with [[OsmoBTS:OpenBTS]], enable the filler table option "Enable C0 filler table", which enables [[OsmoBTS:OpenBTS]] style idle bursts and retransmissions.
389 41 ttsou
390
<pre>
391 1 ttsou
$ osmo-trx -f
392 41 ttsou
</pre>
393 17 ttsou
394 49 neels
The [[OsmoTRX]] transceiver should be started before running [[OsmoBTS:OpenBTS]]. No symbolic link to './transceiver' should exist in the [[OsmoBTS:OpenBTS]] directory. This prevents [[OsmoBTS:OpenBTS]] from starting its own transceiver instance.
395 35 ttsou
396 1 ttsou
h2. Authors
397 41 ttsou
398 1 ttsou
399 57 ttsou
[[OsmoTRX]] is currently maintained by Tom Tsou and Alexander Chemeris among others. The code is derived from the [[OsmoBTS:OpenBTS]] project, which was originally developed by David Burgess and Harvind Samra at Range Networks.
Add picture from clipboard (Maximum size: 48.8 MB)