Project

General

Profile

Wiki » History » Version 11

laforge, 02/21/2016 02:51 PM

1 1 laforge
2 10 laforge
h1. [[OsmoBTS]]
3 4 ipse
4 4 ipse
5 10 laforge
[[OsmoBTS]] is a software implementation of Layer2/3 of a BTS. It implements the follwing protocols/interfaces:
6 10 laforge
* LAPDm (GSM 04.06)
7 10 laforge
* RTP
8 10 laforge
* A-bis/IP in IPA multiplex
9 10 laforge
* OML (GSM TS 12.21)
10 10 laforge
* RSL (GSM TS 08.58)
11 1 laforge
12 10 laforge
[[OsmoBTS]] is building up on work done previosuly for [[OpenBSC]] (RSL, OML, RTP) and "OsmocomBB":http://bb.osmocom.org (LAPDm).  The Abis/IP protocol staking is inspired by ip.access A-bis/IP, sometimes called IPA multiplex.
13 1 laforge
14 11 laforge
h2. OsmoBTS in the Osmocom architecture
15 11 laforge
16 11 laforge
{{graphviz_link()
17 11 laforge
digraph G {
18 11 laforge
    rankdir = LR;
19 11 laforge
    OsmoTRX -> OsmoBTS [label="bursts over UDP"];
20 11 laforge
    sysmoPHY -> OsmoBTS [label="/dev/msgq/"];
21 11 laforge
    octPHY -> OsmoBTS [label="Raw Ethernet"];
22 11 laforge
    OsmoBTS -> OsmoNITB [label="Abis/IP"];
23 11 laforge
    OsmoBTS -> OsmoPCU [label="pcu_sock"];
24 11 laforge
    OsmoPCU -> OsmoSGSN [label="Gb/IP"];
25 11 laforge
    OsmoBTS [color=red];
26 11 laforge
}
27 11 laforge
}}
28 1 laforge
29 10 laforge
h2. Backends / Hardware support
30 9 laforge
31 10 laforge
32 10 laforge
[[OsmoBTS]] is modular and has support for multiple back-ends.  A back-end talks to a specific L1/PHY implementation of the respective BTS hardware. Based on this architecture, it should be relatively easy to add a new back-end to support so-far unsupported GSM PHY/L1 and associated hardware.
33 10 laforge
34 10 laforge
So far [[OsmoBTS]] has been integrated with several different L1/PHY and hardware systems. The backends are:
35 10 laforge
* osmo-bts-sysmo
36 10 laforge
** Multiple indoor and outdoor BTS products  called "sysmoBTS":http://www.sysmocom.de/products/sysmobts which is sold by "sysmocom":http://sysmocom.de/
37 10 laforge
* osmo-bts-trx
38 10 laforge
** Wideband SDR transceiver hardware supported by [[OpenBTS]] transceiver or [OsmoTRX] PHY layer software, including the [[UmTRX]], the USRP family, etc.
39 10 laforge
** Multiple indoor and outdoor "fairwaves":https://fairwaves.co BTSs, like [[UmDESK]] and [[UmSITE]]
40 10 laforge
* osmo-bts-bb
41 10 laforge
** A pretty crazy experimental BTS hardware based on two [[OsmocomBB]] phones had originally been supported, but needs to be re-integrated with core code changes.
42 10 laforge
43 10 laforge
44 10 laforge
h2. Status
45 10 laforge
46 10 laforge
47 9 laforge
The source code includes a  http://cgit.osmocom.org/cgit/osmo-bts/tree/README file with current status information
48 9 laforge
49 9 laforge
50 10 laforge
h2. GPRS support
51 1 laforge
52 1 laforge
53 10 laforge
osmo-bts has recently been extended with a socket interface towards [[osmo-pcu]]. This adds GPRS (and later EDGE) support to it.
54 10 laforge
55 10 laforge
56 10 laforge
h2. Source code
57 10 laforge
58 10 laforge
59 1 laforge
The source code is available from git.osmocom.org (module osmo-bts).
60 6 ipse
61 6 ipse
Public read-only access is available via
62 6 ipse
 git clone git://git.osmocom.org/osmo-bts.git
63 6 ipse
You can browse it via cgit: http://cgit.osmocom.org/cgit/osmo-bts/
64 6 ipse
65 6 ipse
66 10 laforge
h2. Authors / Credits
67 10 laforge
68 10 laforge
69 10 laforge
[[OsmoBTS]] was originally developed in 2011 by Andreas Eversberg and Harald Welte.  
70 9 laforge
71 9 laforge
Today it is mostly maintained by Harald Welte and Holger Freyther at sysmocom.  Exception is the osmo-bts-trx back-end which is maintained by Fairwaves. 
Add picture from clipboard (Maximum size: 48.8 MB)