Project

General

Profile

OpenBSC » History » Version 21

laforge, 02/19/2016 10:47 PM

1 13 laforge
[[PageOutline]]
2 1 laforge
'''OpenBSC''' is the current name for a software program that started with the name bs11-abis.
3
4
== What is OpenBSC ==
5 2 laforge
It is a [wiki:BSC] (Base Station Controller) side implementation of the A-bis protocol, as implemented in the GSM Technical Specification 08.5x and 12.21.  It implements a minimal subset of the [wiki:BSC], [wiki:MSC] and [wiki:HLR].  It does not implement ant of the interfaces (like the A and B interfaces) between the higher-order GSM network components.
6 1 laforge
7
The goal of the project is to
8
 * provide a basis for experimentation and security research with GSM from the network side
9
 * document, publicized and point out any security related issues that we find as part of that
10
 * learn more about GSM networks on a lower level, particularly the practical aspects with real-world equipment
11
12 17 laforge
We '''are not primarily interested''' in
13 14 laforge
 * building a stable/reliable BSC/MSC for deployment in networks requiring high-9 (99.999....) availability
14 1 laforge
 * building something that follows the GSM spec to the last detail
15
 * disrupting actual commercial GSM network
16
17
== Requirements ==
18 13 laforge
19 17 laforge
While OpenBSC is mainly written in portable C99 code, there are is one non-portable parts: The E1 input driver requires a Linux kernel with mISDN support and an [wiki:E1] interface card compatible with [wiki:mISDN].  You only need this if you have an E1 based BTS.
20 1 laforge
21 13 laforge
To opertate a GSM network, you not only need OpenBSC but of course also some kind of GSM [wiki:BTS].  The only currently tested configurations are with a
22 21 laforge
 * sysmocom [http://www.sysmocom.de/products/sysmobts sysmoBTS] (by means of [wiki:OsmoBTS])
23 1 laforge
 * Siemens [wiki:BS11 BS-11] microBTS
24
 * [wiki:nanoBTS ip.access nanoBTS]
25
26 17 laforge
== Configurations / Modes ==
27
28
=== OpenBSC network-in-the-box (NITB) mode ===
29
30
This is ''very different'' from a classic GSM network in which the BSC is only one minor element in the distributed network consisting
31
of many different elements like BSC, MSC, HLR, etc.  Nonetheless, it is the ''classic'' mode to operate OpenBSC.  In this configuration, you only need (at least) one BTS and OpenBSC.  There is no need for a MSC, HLR, VLR, AuC or any other traditional GSM network components.
32
33
{{{
34
#!graphviz
35
digraph G {
36
rankdir=LR 
37
bs11->OpenBSC    [ label="Abis/E1" ]
38
nanobts->OpenBSC [ label="Abis/IP" ]
39
bs11    [ label = "Siemens\nBS-11" ]
40
nanobts [ label = "ip.access\nnanoBTS" ]
41
OpenBSC [ label = "OpenBSC\nNITB" ]
42
}
43
}}}
44
45 19 laforge
In order to use the NITB mode, you will use the [wiki:osmo-nitb] program.
46 1 laforge
47 18 laforge
==== Interconnecting OpenBSC with a PBX ====
48
If you want to connect calls outside of your OpenBSC based GSM network, you can have [wiki:lrc (Linux Call Router] and OpenBSC
49
work together to create a setup like this:
50
51
{{{
52
#!graphviz
53
digraph G {
54
rankdir=LR 
55
bs11->OpenBSC    [ label="Abis/E1" ]
56
nanobts->OpenBSC [ label="Abis/IP" ]
57
OpenBSC->LCR     [ label="MNCC Socket" ]
58
LCR->ISDN        [ label="E1/PRI/BRI" ]
59
bs11    [ label = "Siemens\nBS-11" ]
60
nanobts [ label = "ip.access\nnanoBTS" ]
61
OpenBSC [ label = "OpenBSC\nNITB" ]
62
}
63
}}}
64
65 17 laforge
=== OpenBSC in BSC-only mode ===
66 1 laforge
67 17 laforge
If you want to use OpenBSC as a classic GSM BSC, you can do that as well.  However, you will need all other parts of the GSM
68 18 laforge
network and a MSC that can provide an A-over-IP interface using SCCP-lite
69 17 laforge
70
{{{
71
#!graphviz
72
digraph G {
73
rankdir=LR;
74
bs11->OpenBSC    [ label="Abis/E1" ];
75
nanobts->OpenBSC [ label="Abis/IP" ];
76
OpenBSC->MSC     [ label="A/SCCP-Lite/IP" ];
77 1 laforge
subgraph core {
78
  MSC->VLR;
79 17 laforge
  MSC->HLR;
80
  HLR->AUC;
81 18 laforge
  label = "not included";
82
  color = blue;
83 17 laforge
}
84
bs11    [ label = "Siemens\nBS-11" ];
85 1 laforge
nanobts [ label = "ip.access\nnanoBTS" ];
86
OpenBSC [ label = "OpenBSC\nosmo-bsc" ];
87
}
88 17 laforge
}}}
89 18 laforge
90
In order to use the BSC-only mode, you will use the [wiki:osmo-bsc] program.
91
92 12 laforge
== Source code ==
93 13 laforge
94 1 laforge
=== Releases ===
95
As we're a mostly research oriented project, we don't really have any releases yet.  This will likely change soon.
96
97
=== Development Version ===
98
You can check out the source code via
99 15 laforge
{{{
100 1 laforge
git clone git://git.osmocom.org/openbsc.git
101
}}}
102 18 laforge
or browse it at http://cgit.osmocom.org/cgit/openbsc/
103 1 laforge
104 3 laforge
== Mailing list ==
105 16 laforge
106 18 laforge
There's a '''developer''' mailing list called openbsc@lists.osmocom.org
107 1 laforge
Subscription is available at [http://lists.osmocom.org/mailman/listinfo/openbsc/]
108
109
== IRC (Internet Relay Chat) ==
110 13 laforge
111 1 laforge
We have an IRC channel where some developers and users hang out.  You can find it at:
112
irc.freenode.net/#openbsc
113
114
== Project status ==
115
116 13 laforge
=== Things that work ===
117 1 laforge
 * Housekeeping
118
  * [wiki:OML] Initialization of the BTS
119 14 laforge
  * Support for frequency hopping channels on BTS equipment that supports it (like BS-11)
120 13 laforge
  * [wiki:RSL] bringup, channel allocation, Channel required / Immediate Assign
121
 * Mobility Management
122
  * Very simplistic [wiki:HLR] implemented as sqlite database
123
  * Non-secure Authentication using [wiki:IMEI]/[wiki:IMSI] and regular SIM cards.
124 18 laforge
  * Authentication using COMP128v1 if you have SIM cards with known Ki
125 1 laforge
  * [wiki:IMEI]/[wiki:IMSI] skimming of all phones that try to register with OpenBSC
126 13 laforge
  * Transmission of MM INFO packets with operator name and local time / timezone
127
  * paging of mobiles that are registered to the BTS
128
  * keeping track of which location area a phone has last performed location updating
129
  * in-call handover between multiple cells inside one BSC
130
 * SMS Support
131
  * [wiki:SMS] reception and [wiki:SMS] sending, including routing between subscribers
132 18 laforge
  * Sending of SMS from OpenBSC command line
133 13 laforge
  * Sending of SMS from external applications by writing to the SQL tables
134
 * Voice Call Support
135
  * MO (Mobile Originated) and MT (Mobile Terminated) calls
136
  * TCH/F support with FR and EFR codec
137
  * TCH/H support with AMR codec (in BSC-only configuration)
138
 * E1 support
139
  * demultiplex of the four 16k sub-channels with voice data contained in one [wiki:E1] timeslot
140
  * support for multiple [wiki:TRX] in one [wiki:BTS]
141
  * support for multiple [wiki:BTS] connected to the same E1 link (multi-loop configuration)
142 1 laforge
 * Abis/IP support
143 13 laforge
  * Abis/IP protocol for nanoBTS
144
  * RTP gateway to interoperate E1 based BTS and nanoBTS on one BSC and switch calls between them
145
 * GPRS/EDGE support
146
  * configuring the nanoBTS OML objects/attributes for GPRS and EDGE
147
  * setting SYSTEM INFORMATION 13 via RSL
148
  * configurable RAID/CGI/NSVCI/NSEI/BVCI
149 1 laforge
  * have the BTS interoperate a SGSN with Gb (NS-over-IP) interface
150 18 laforge
  * beta state [wiki:OsmoSGSN] included along OpenBSC
151 1 laforge
152 11 laforge
=== Things that are implemented but don't work yet or aren't tested yet ===
153 20 laforge
 * dynamic PDCH / TCH switching
154 7 laforge
155
=== Things being worked at ===
156 1 laforge
 *  GPS/DCF77 disciplined quartz reference for the HFC-E1 card (via HS-Esslingen, Student Research Project)
157
158 20 laforge
=== Things that are not implemented ===
159 2 laforge
 * Cell Broadcast
160 20 laforge
 * Any type of transcoding of voice data
161
 * TCH/H voice calls (they work in [wiki:osmo-bsc], but not in [wiki:osmo-nitb])
162 2 laforge
 * [wiki:CSD] calls
163 20 laforge
 * emergency call handling (works in [wiki:osmo-bsc], but not in [wiki:osmo-nitb])
164 4 laforge
 * Discontinuous TX and RX ([wiki:DTX] / [wiki:DRX]) support
165 2 laforge
166 1 laforge
== Authors ==
167
168 19 laforge
OpenBSC was mainly developed by [http://laforge.gnumonks.org/ Harald Welte] and Holger Freyther. Contributions by Dieter Spaar, Stefan Schmidt, Daniel Willmann, Jan Luebbe, Thomas Seiler and Andreas Eversberg.
169 1 laforge
170 11 laforge
Special thanks to Dieter Spaar for [wiki:BS11-Init] and tons of feedback and comments, without which we would not have been able to make progress as quickly as we did.
Add picture from clipboard (Maximum size: 48.8 MB)