osmo-bts

Osmocom Base Transceiver Station (BTS) https://osmocom.org/projects/osmobts

Go to file

Harald Welte 54cbbb1450 Have osmo-bts request OML routes for all its MOs at startup During OML link start-up, osmo-bts now requests a OML route for each of the managed objects that it currently implements. This is done via the 'ORC' (OML Router Control) protocol, which is encapsulated in the extended IPA_PROTO_OSMO multiplex. The responses (ACK/NACK) are not yet processed inside osmo-bts.		2014-08-24 17:29:16 +02:00
contrib	sysmobts: Add VTY support to the sysmobts-mgr	2014-08-21 15:49:06 +02:00
doc	add a small document describing the use of the control interface	2014-08-24 17:19:59 +02:00
include	Have osmo-bts request OML routes for all its MOs at startup	2014-08-24 17:29:16 +02:00
src	Have osmo-bts request OML routes for all its MOs at startup	2014-08-24 17:29:16 +02:00
tests	sysmobts: Add a unit test that checks of the behavior	2014-08-09 09:42:56 +02:00
.gitignore	A dedicated OML router program (osmobts-omlrouter)	2014-08-24 17:28:47 +02:00
COPYING	re-work original osmo-bts with support for sysmocom femtobts	2011-06-27 11:25:35 +02:00
Makefile.am	sysmobts: Add VTY support to the sysmobts-mgr	2014-08-21 15:49:06 +02:00
README	misc: Please ignore the commit. It is done to test a jenkins trigger	2013-06-20 17:24:32 +02:00
configure.ac	fix build problem introduced with control interface	2014-08-24 17:04:54 +02:00
git-version-gen	auto-generate a version	2011-09-07 21:28:27 +02:00

README

Repository for new the Osmocom BTS implementation.

This code implementes the Layer 2 and higher of a more or less
conventional GSM BTS (Base Transceiver Station) - however, using an
Abis/IP interface, rather than the old-fashioned E1/T1.

Specificallt, this includes
 * BTS-Side implementation of TS 08.58 (RSL) and TS 12.21 (OML)
 * BTS-Side implementation of LAPDm (using libosmocore/libosmogsm)
 * A somewhat separated interface between those higher layer parts
   and the Layer1 interface.

Right now, only one hardware and Layer1 are supported:  The sysmocom
sysmoBTS.

There is some experimental and way incomplete code to use a couple of
OsmocomBB phones and run them in the BTS.  However, the required code
for the Calypso DSP code have not been written yet.  This would still
require a lot of work.

Some additional work is being done in using some parts of the OpenBTS
L1FEC and glue it against omso-bts.  However, this is also still in an
early, experimental stage.

== Known Limitations ==

As of June 3, 2012, the following known limitations exist in this
implementation:

=== Common Core ===
 * No Extended BCCH support
 * System Information limited to 1,2,2bis,2ter,2quater,3,4,5,6,9,13
 * No RATSCCH in AMR
 * No OML (TS 12.21) alarms yet (temperature, ...)
 * Only single-TRX BTS at this point
 * Will reject TS 12.21 STARTING TIME in SET BTS ATTR / SET CHAN ATTR
 * No support for frequency hopping
 * No reporting of interference levels as part of TS 08.58 RF RES IND
 * No error reporting in case PAGING COMMAND fails due to queue overflow
 * No hand-over support (planned)
 * No use of TS 08.58 BS Power and MS Power parameters
 * No support of TS 08.58 MultiRate Control
 * No support of TS 08.58 Supported Codec Types
 * No support of Bter frame / ENHANCED MEASUREMENT REPORT

=== osmo-bts-sysmo ===
 * No CSD / ECSD support (not planned)
 * No GPRS/EDGE support (planned)
 * GSM-R frequency band supported, but no NCH/ASCI/SoLSA
 * All timeslots on one TRX have to use same training sequence (TSC)
 * No multi-TRX support yet, though hardware+L1 support stacking
 * Makes no use of 12.21 Intave Parameters and Interference
   Level Boundaries
 * Makes no use of TS 12.21 T3105
 * Doesn't yet include MAC address in Abis/IP Identity message
 * MphConfig.CNF can be returned to the wrong callback. E.g. with Tx Power
   and ciphering. The dispatch should take a look at the hLayer3.