blob: 124c03fda1f05e9ae2954d4a82b520443dde6bad [file] [log] [blame]
Harald Weltef1d42512017-05-31 21:22:42 +02001= OsmoBSC A / SCCPlite / 3GPP AoIP Options
2
3== Introduction
4
5This document serves as a paper to illustrate the different
6configurations of OsmoBSC in terms of integration with BTSs and MSCs.
7
8The document should accompany us in the 2017 development cycle which
9includes the _death of the NITB_, i.e. the move away from OsmoNITB to
10having OsmoBSC in all configurations, whether with a
11proprietary/external MSC or with OsmoMSC.
12
13Particular attention is spent on the user plane, including aspects
14such as
15
16* user plane transport address handling
17* use of MGCP (Media Gateway Control Protocol)
18* the (required) evolution of `osmo-bsc_mgcp`
19* not loosing classic TDM (E1/T1) BTS support when moving from
20 OsmoNITB to split OsmoBSC + OsmoMSC setup
21
22
23== Overview
24
25=== Classic GSM RAN with E1 based Abis and E1 A
26
27This configuration was actually never supported by OpenBSC, as E1 BTS
28support was so far for NITB only, but not for OsmoBSC.
29
30[mscgen]
31----
Oliver Smith686deaf2018-11-14 10:47:01 +010032include::{srcdir}/mgw/classic-bsc.msc[]
Harald Weltef1d42512017-05-31 21:22:42 +020033----
34
35=== OsmoBSC 2010-2017: IPA-style A over SCCPlite
36
37This configuration was introduced as early as 2010 in OpenBSC. It
38allowed the use of IP based BTSs (ip.access nanoBTS as well as all the
39OsmoBTS supported BTS models) in combination with third-party MSCs
40implementing a pre-standard, proprietary way of transporting the A
41interface over IP at a time where the 3GPP specifications only allowed
42classic TDM transport.
43
44[mscgen]
45----
Oliver Smith686deaf2018-11-14 10:47:01 +010046include::{srcdir}/mgw/osmo-bsc-old-sccplite.msc[]
Harald Weltef1d42512017-05-31 21:22:42 +020047----
48
49
50=== OsmoBSC 2017+: 3GPP AoIP + Abis/IP
51
52Release 7 of 3GPP included an official specification on how an
53interoperable A-over-IP (AoIP) interface shall look like.
54
55As more modern MSCs at operators tend to favor implementing 3GPP AoIP
56rather than the proprietary SCCPlite based A interface, it becomes
Martin Haukea29affd2019-11-13 22:10:41 +010057necessary for OsmoBSC to support this.
Harald Weltef1d42512017-05-31 21:22:42 +020058
59At the same time, for compatibility reasons, the classic SCCPlite
60support shall be kept, if possible with reasonable effort.
61
62[mscgen]
63----
Oliver Smith686deaf2018-11-14 10:47:01 +010064include::{srcdir}/mgw/osmo-bsc-new-mgw.msc[]
Harald Weltef1d42512017-05-31 21:22:42 +020065----
66
67
68=== OsmoBSC 2017+: 3GPP AoIP + Abis/E1
69
70Since OsmoNITB will soon be deprecated, we will use OsmoBSC in all
71Osmocom GSM ntework setups, requiring the support for classic E1/T1
72based BTSs from OsmoBSC.
73
74[mscgen]
75----
Oliver Smith686deaf2018-11-14 10:47:01 +010076include::{srcdir}/mgw/osmo-bsc-new-mgw-e1.msc[]
Harald Weltef1d42512017-05-31 21:22:42 +020077----