Project

General

Profile

Configuration Guide » History » Version 19

neels, 11/09/2017 06:10 PM

1 1 neels
{{>toc}}
2
3
h1. Configuration Guide
4
5
The first challenge in setting up a cellular network is to actually know what you
6
want to setup and which components you need to achieve that.
7
8 2 neels
h1. 2G Networks
9 1 neels
10 2 neels
h2. Radio Equipment
11 1 neels
12
There is a multitude of BTS equipment that works with Osmocom to choose from.
13
14 14 laforge
Various BTS models actually run Osmocom's [[OsmoBTS:]] and [[OsmoPCU:]] software on the BTS itself:
15 1 neels
16 12 laforge
* [[OpenBSC:sysmoBTS]] models 1002, 1002OD, 1020, 1200, 1100 and 2050 (osmo-bts-sysmo)
17 8 ipse
* [[OsmoTRX:|SDR based BTSs]], e.g. using the Ettus B200 or Fairwaves' UmTRX (osmo-trx plus osmo-bts-trx)
18 2 neels
* Octasic [[OctBTS]] (osmo-bts-octphy)
19 11 laforge
* Nutaq [[Litecell 1.5]] / sysmoBTS 2100 (osmo-bts-lc15)
20 1 neels
21 14 laforge
Others are "closed" BTS that are nevertheless interoperable with Osmocom's BSC implementation:
22 1 neels
23 2 neels
* ip.access [[OpenBSC:NanoBTS]]
24
* Siemens [[OpenBSC:BS11]]
25 3 neels
* [[OpenBSC:Ericsson RBS]]
26 1 neels
27 2 neels
h2. Core Network
28 1 neels
29 9 neels
* Are you going to plug into a 3rd party MSC, e.g. the "voice" part of a mobile operator's core network? Then you will want to use the standalone [[OpenBSC:]] approach.
30 18 neels
** Since 2017, Osmocom offers a true *SCCP/M3UA based 3GPP A-over-IP interface*. This is available in the new "osmo-bsc.git":http://git.osmocom.org/osmo-bsc: look for @osmo-bsc@ in [[Binary_Packages]] or sysmocom OpenEmbedded feeds (starting from "201705").
31 13 laforge
** Originally, Osmocom supported only an *SCCPlite based A-interface*. This is still available in the old "openbsc.git":http://git.osmocom.org/openbsc; in [[Binary_Packages]] or sysmocom OpenEmbedded feeds (starting from "201705"), look for @osmo-bsc-sccplite@.
32 1 neels
33
* Are you looking for a self-contained complete core network?
34 13 laforge
** Since 2017, it is recommended to use [[OsmoHLR:]], [[OsmoMSC:]], [[OsmoSTP:]], [[OsmoBSC:]] and [[OsmoMGW:]]. See the [[Osmocom Network In The Box]] guide.
35 15 neels
** Historically, Osmocom offered the [[OsmoNITB:]] "Network-In-The-Box" approach. It is still available, but active development is now focused on the new separate programs, see [[Osmocom Network In The Box]]. To migrate from OsmoNITB to the new separate programs, see the [[OsmoNITB Migration Guide]].
36 1 neels
37 9 neels
* [[Miscellaneous Projects:osmo-sip-connector]] may connect your OsmoMSC or OsmoNITB to external VoIP services.
38 7 laforge
39 19 neels
* GPRS and EGPRS data services are provided by, for example, by [[OsmoSGSN:]] and [[OpenGGSN:OsmoGGSN]]. Operation with a 3rd party SGSN or GGSN are also possible. See [[Osmocom Network In The Box]].
40 1 neels
41 9 neels
* Osmocom also contains various tools to tunnel GTP, RTP/MGCP or A protocols through a NAT layer:
42 4 neels
** osmo-bsc_nat
43
** osmo-bsc_mgcp
44
** gtphub
45 1 neels
46
h1. 3G Networks
47
48
h2. Radio Equipment
49
50 14 laforge
You will need hNodeB hardware that is capable of talking the Iuh protocol over IP. This type of 3G cell is also known as small cell or femto-cell.
51 1 neels
52 14 laforge
[[sysmocom]] offers a professional small cell product for these purposes to customers.
53 2 neels
54 14 laforge
We're also working on a lowest-cost femtocell offering strictly limited to active contributors to the Osmocom projects.
55 1 neels
56
h2. Core Network
57 6 neels
58 14 laforge
As outlined in "this article":https://osmocom.org/news/59, the Osmocom 3G core network uses [[OsmoHNBGW:]] to connect to [[OsmoMSC:]] and [[OsmoSGSN:]]. Furthermore osmo-bsc_mgcp is used to relay RTP voice streams and OsmoGGSN may be used to provide data services.
59 5 neels
60 16 neels
See [[Osmocom Network In The Box]] and [[Getting Started with 3G]]
Add picture from clipboard (Maximum size: 48.8 MB)