Project

General

Profile

OsmoTRX » History » Version 20

ttsou, 02/19/2016 10:47 PM

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