Project

General

Profile

OsmoTRX » History » Version 25

ttsou, 02/19/2016 10:47 PM

1 1 ttsou
= OsmoTRX =
2
3
OsmoTRX is a software-defined radio transceiver that implements the Layer 1 physical layer of a BTS comprising the following 3GPP specifications:
4
 * TS 05.01 "Physical layer on the radio path"
5
 * TS 05.02 "Multiplexing and Multiple Access on the Radio Path"
6
 * TS 05.04 "Modulation"
7
 * TS 05.10 "Radio subsystem synchronization"
8
9 6 ttsou
OsmoTRX is based on the OpenBTS transceiver, but setup to operate independently with the purpose of using with non-OpenBTS software and projects. Currently there are numerous features contained in OsmoTRX that extend the functionality of the OpenBTS transceiver. These features include enhanced support for embedded platforms - notably ARM - and dual channel diversity support for the Fairwaves UmTRX. Most of these features will eventually be merged into mainline OpenBTS, but primary development will occur on OsmoTRX.
10
11
== Features ==
12
13 16 ttsou
'''Intel SSE Support'''
14 6 ttsou
* SSE3
15
* SSE4.1
16
17 20 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.
18 1 ttsou
19 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. For additional performance information, please see the performance and benchmarks section.
20
21 16 ttsou
'''ARM NEON Support'''
22 6 ttsou
* NEON
23 1 ttsou
* NEON-VFPv4
24 6 ttsou
25 20 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.
26 1 ttsou
27 20 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.
28
29
For additional performance information, please see the performance and benchmarks section.
30
31 6 ttsou
'''Dual Channel (UmTRX only)'''
32 7 ttsou
33
Two dual channel modes are available: standard dual channel mode and diversity. In standard dual channel mode, each RF
34
path of the dual channel device - currently only UmTRX - supports a different ARFCN. Each path operates independently a
35
nd operates similarly to two separate devices. GSM channel capacity in this mode is doubled.
36 1 ttsou
37 8 ttsou
'''Dual Channel Diversity (UmTRX only)'''
38 1 ttsou
39 20 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.
40 16 ttsou
41 20 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.
42
43 16 ttsou
'''Low Phase Error Modulator'''
44
45 20 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.
46 16 ttsou
47 20 ttsou
Very Low Phase Error (Ettus Research N200)
48 1 ttsou
49
[[Image(http://tsou.cc/gsm/osmo-trx-phase75.gif)]]
50
51 21 ttsou
Spectrum Mask (Ettus Research N200)
52 1 ttsou
53
[[Image(http://tsou.cc/gsm/osmo-trx-spectrum75.gif)]]
54
55 20 ttsou
== RF Hardware support ==
56 1 ttsou
57 20 ttsou
Multiple RF devices are currently supported. These include USRP family products from Ettus Research, and the UmTRX from Fairwaves.
58 1 ttsou
59 20 ttsou
||'''Fairwaves'''||'''Notes'''||
60
||UmTRX||Dual channel||
61
62
All Ettus Research devices are supported.
63
64
||'''Ettus Research'''||'''Notes'''||
65
||USRP1||Requires legacy libusrp driver and clocking modification||
66
||USRP2||10 MHz external reference required||
67 1 ttsou
||B100||
68
||B110||
69 20 ttsou
||B200||10 MHz external reference recommended||
70
||B210||* Dual channel, 10 MHz external reference recommended||
71 1 ttsou
||N200||
72
||N210||
73
||E100||
74
||E110||
75
76 20 ttsou
* Ettus B210 dual channel support with OsmoTRX is currently unavailable, but is expected to be added at a later time.
77
78 1 ttsou
== Embedded Platform Support ==
79
80 20 ttsou
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.
81 1 ttsou
82 20 ttsou
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.
83
84
||'''Platform'''||'''SoC'''||'''Processor'''||'''SIMD/FPU'''||'''Testing Notes'''
85
||!ArndaleBoard||Samsung Exynos 5250||ARM Cortex-A15||NEON-VFPv4||7 TCH||
86 21 ttsou
||!BeagleBoard-xM||Texas Instruments OMAP3||ARM Cortex-A8||NEON||7 TCH, remote OsmoBTS stack||
87
||Ettus E100||Texas Instruments OMAP3||ARM Cortex-A8||NEON||7 TCH, remote OsmoBTS stack||
88
||Raspberry Pi||Broadcom BCM2835||ARM11||VFP||2 TCH, remote OsmoBTS stack||
89 1 ttsou
||Shuttle PC||NA||Intel Atom D2550||SSE3||Dual channel, 15 TCH||
90 20 ttsou
91 25 ttsou
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.
92 19 ttsou
93
== Mailing List ==
94 18 ttsou
95 1 ttsou
For development purposes, OsmoTRX is discussed on both OpenBTS and OpenBSC mailing lists at openbts-discuss@lists.sourceforge.net and openbsc@lists.osmocom.org respectively.
96
97 22 ttsou
Please direct questions and bug reports to the list appropriate for the GSM stack being used.
98 19 ttsou
99 16 ttsou
Subscription information is available at [https://lists.sourceforge.net/lists/listinfo/openbts-discuss] and [http://lists.osmocom.org/mailman/listinfo/openbsc/].
100 19 ttsou
101
== GPRS support ==
102 16 ttsou
103 1 ttsou
OsmoTRX supports GPRS through OsmoBTS.
104 16 ttsou
105 1 ttsou
For GPRS support with OpenBTS, please use the transceiver supplied with OpenBTS.
106
107
== Source code ==
108 16 ttsou
109 1 ttsou
The source code is available from git.osmocom.org (module osmo-trx).
110
111
Public read-only access is available via
112 18 ttsou
 git clone git://git.osmocom.org/osmo-trx
113 1 ttsou
You can browse it via cgit: http://cgit.osmocom.org/cgit/osmo-trx/
114 18 ttsou
115
== Configuration and Build ==
116 19 ttsou
117 1 ttsou
The only package dependency is the Universal Hardware Driver (UHD), which is available from Ettus Research or Fairwaves depending on the device. Please note that the UHD implementation must match hardware (i.e. Ettus Research UHD for USRP devices and Fairwaves UHD with UmTRX). The one device that does not use the UHD driver is the USRP1, which is supported through the legacy libusrp driver provided in GNU Radio 3.4.2.
118
119 18 ttsou
'''Intel Platforms (All)'''
120
121
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.
122
{{{
123
$ ./configure
124
...
125 1 ttsou
checking whether mmx is supported... yes
126 18 ttsou
checking whether sse is supported... yes
127
checking whether sse2 is supported... yes
128
checking whether sse3 is supported... yes
129
checking whether ssse3 is supported... yes
130
checking whether sse4.1 is supported... yes
131 1 ttsou
checking whether sse4.2 is supported... yes
132 19 ttsou
...
133 18 ttsou
}}}
134
135
'''ARM Platforms with NEON'''
136
137
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.
138
{{{
139 19 ttsou
$ ./configure --with-neon
140 18 ttsou
}}}
141
142
'''ARM Platforms with NEON-VFPv4'''
143
144
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.
145
{{{
146
$ ./configure --with-neon-vfpv4
147
}}}
148
149
'''ARM Platforms without NEON'''
150
151
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.
152 1 ttsou
153 24 ttsou
Coming soon...
154 18 ttsou
155 16 ttsou
'''Build and Install'''
156
157
After configuration, installation is simple.
158
159
{{{
160 18 ttsou
$ make
161 19 ttsou
$ sudo make install
162 16 ttsou
}}}
163
164
== Running ==
165
166
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.
167
168
{{{
169
$ osmo-trx -h
170
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.005.004-140-gfb32ed16
171
172
Options:
173
  -h    This text
174
  -a    UHD device args
175
  -l    Logging level (EMERG, ALERT, CRT, ERR, WARNING, NOTICE, INFO, DEBUG)
176
  -i    IP address of GSM core
177
  -p    Base port number
178
  -d    Enable dual channel diversity receiver
179
  -x    Enable external 10 MHz reference
180
  -s    Samples-per-symbol (1 or 4)
181
  -c    Number of ARFCN channels (default=1)
182
}}}
183
184
{{{
185
$ osmo-trx -a "addr=192.168.10.2"
186
linux; GNU C++ version 4.8.1 20130603 (Red Hat 4.8.1-1); Boost_105300; UHD_003.004.000-b14cde5
187
188
Config Settings
189
   Log Level............... INFO
190
   Device args............. addr=192.168.10.2
191
   TRX Base Port........... 5700
192 1 ttsou
   TRX Address............. 127.0.0.1
193 16 ttsou
   Channels................ 1
194 1 ttsou
   Samples-per-Symbol...... 4
195
   External Reference...... Disabled
196 16 ttsou
   Diversity............... Disabled
197
198
-- Opening a UmTRX device...
199
-- Current recv frame size: 1472 bytes
200
-- Current send frame size: 1472 bytes
201
-- Setting UmTRX 4 SPS
202 19 ttsou
-- Transceiver active with 1 channel(s)
203 13 ttsou
}}}
204 19 ttsou
205
== Benchmarks ==
206 17 ttsou
207 13 ttsou
A variety of performance benchmarks are available for various code optimizations. These include floating point - integer conversions, convolution, and convolutional decoding. Note that convolutional decoding does not take place in OsmoTRX, but one stop higher in the Layer 1 stack - either in OsmoBTS or OpenBTS core.
208
209 1 ttsou
Selected benchmark results are provided below. All tests are run on a single core only.
210 24 ttsou
211
The benchmark code repository is coming soon...
212 13 ttsou
213
'''Intel Haswell (i7 4770K 3.5 GHz)'''
214
215
{{{
216 10 ttsou
--- Floating point to integer conversions
217
-- Testing 40000 iterations of 3120 values
218 1 ttsou
- Measuring conversion time
219
- Elapsed time base...                  0.065508 secs
220
- Validating SIMD conversion results... PASS
221
- Measuring conversion time
222
- Elapsed time SIMD ...                 0.011424 secs
223
- Speedup...                            5.734244
224
}}}
225
226
{{{
227
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
228
[.] Input length  : ret = 165  exp = 165 -> OK
229
[.] Output length : ret = 448  exp = 448 -> OK
230 3 ttsou
[.] Pre computed vector checks:
231
[..] Encoding: OK
232
[..] Decoding base: 
233
[..] Decoding SIMD: 
234
[..] Code N 3
235
[..] Code K 7
236
OK
237
[.] Random vector checks:
238
[.] Testing baseline:
239
[..] Encoding / Decoding 10000 cycles:
240
[.] Elapsed time........................ 1.435066 secs
241
[.] Rate................................ 3.121808 Mbps
242 1 ttsou
[.] Testing SIMD:
243
[..] Encoding / Decoding 10000 cycles:
244 17 ttsou
[.] Elapsed time........................ 0.073524 secs
245 1 ttsou
[.] Rate................................ 60.932485 Mbps
246
[.] Speedup............................. 19.518334
247
}}}
248
249 17 ttsou
'''Intel Atom (D2500 1.86 GHz)'''
250
{{{
251
--- Floating point to integer conversions
252
-- Testing 40000 iterations of 3120 values
253
- Measuring conversion time
254
- Elapsed time base...                 1.147449 secs
255
- Validating SSE conversion results... PASS
256
- Measuring conversion time
257
- Elapsed time SSE ...                 0.347838 secs
258
- Quotient...                          3.298803
259
}}}
260
261
{{{
262
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
263
[.] Input length  : ret = 165  exp = 165 -> OK
264
[.] Output length : ret = 448  exp = 448 -> OK
265
[.] Pre computed vector checks:
266
[..] Encoding: OK
267
[..] Decoding base: 
268
[..] Decoding SIMD: 
269
[..] Code N 3
270 1 ttsou
[..] Code K 7
271
OK
272
[.] Random vector checks:
273 17 ttsou
[.] Testing baseline:
274
[..] Encoding / Decoding 10000 cycles:
275
[.] Elapsed time........................ 11.822688 secs
276
[.] Rate................................ 0.378932 Mbps
277
[.] Testing SIMD:
278
[..] Encoding / Decoding 10000 cycles:
279
[.] Elapsed time........................ 0.550423 secs
280 19 ttsou
[.] Rate................................ 8.139195 Mbps
281
[.] Speedup............................. 21.479277
282
}}}
283 17 ttsou
284
'''!ArndaleBoard (ARM Cortex-A15 1.7 GHz)'''
285
286
Please note that the Viterbi implementations on ARM is largely C based with speedup generated primarily through algorithm changes. In comparison, vector optimization on Intel platforms with SSE is currently much more aggressive, which explains the disparity on decoding performance.
287
288
{{{
289
--- Floating point to integer conversions
290
-- Testing 40000 iterations of 3120 values
291
- Measuring conversion time
292
- Elapsed time base...                 0.384097 secs
293
- Validating SSE conversion results... PASS
294
- Measuring conversion time
295
- Elapsed time SSE ...                 0.100877 secs
296
- Quotient...                          3.807578
297
}}}
298
299
{{{
300
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
301
[.] Input length  : ret = 165  exp = 165 -> OK
302
[.] Output length : ret = 448  exp = 448 -> OK
303
[.] Pre computed vector checks:
304
[..] Encoding: OK
305
[..] Decoding base: 
306
[..] Decoding SIMD: 
307
[..] Code N 3
308
[..] Code K 7
309
OK
310
[.] Random vector checks:
311
[.] Testing baseline:
312
[..] Encoding / Decoding 10000 cycles:
313
[.] Elapsed time........................ 5.371288 secs
314
[.] Rate................................ 0.834064 Mbps
315
[.] Testing SIMD:
316
[..] Encoding / Decoding 10000 cycles:
317
[.] Elapsed time........................ 1.016621 secs
318
[.] Rate................................ 4.406755 Mbps
319
[.] Speedup............................. 5.283471
320
}}}
321
322 3 ttsou
'''!BeagleBoard-xM (ARM Cortex-A8 800 MHz)'''
323
{{{
324
--- Floating point to integer conversions
325
-- Testing 40000 iterations of 3120 values
326
- Measuring conversion time
327
- Elapsed time base...                  6.292542 secs
328
- Validating SIMD conversion results... PASS
329
- Measuring conversion time
330
- Elapsed time SIMD ...                 0.839081 secs
331 5 ttsou
- Quotient...                           7.499326
332 3 ttsou
}}}
333
334
{{{
335 4 ttsou
[+] Testing: GSM TCH/AFS 7.95 (recursive, flushed, punctured)
336 3 ttsou
[.] Input length  : ret = 165  exp = 165 -> OK
337
[.] Output length : ret = 448  exp = 448 -> OK
338
[.] Pre computed vector checks:
339
[..] Encoding: OK
340
[..] Decoding base: 
341
[..] Decoding SIMD: 
342
[..] Code N 3
343
[..] Code K 7
344
OK
345
[.] Random vector checks:
346 1 ttsou
[.] Testing baseline:
347 3 ttsou
[..] Encoding / Decoding 10000 cycles:
348
[.] Elapsed time........................ 21.963257 secs
349
[.] Rate................................ 0.203977 Mbps
350
[.] Testing SIMD:
351
[..] Encoding / Decoding 10000 cycles:
352 1 ttsou
[.] Elapsed time........................ 3.083282 secs
353
[.] Rate................................ 1.452997 Mbps
354 17 ttsou
[.] Speedup............................. 7.123337
355 1 ttsou
}}}
356
357
== Authors ==
358
359 23 ttsou
OsmoTRX is currently developed and maintained by Thomas Tsou with support from Fairwaves, the Open Technology Institute, and Ettus Research. The code is derived from the OpenBTS project, which was originally developed by David Burgess and Harvind Samra at Range Networks.
Add picture from clipboard (Maximum size: 48.8 MB)