Osmocom Base Transceiver Station (BTS) https://osmocom.org/projects/osmobts
Go to file
Holger Hans Peter Freyther 4513d561eb sysmobts: Add a manual ms power level control
Currently the DSP is instructed to achieve a given uplink
power target but there are circumstances (e.g. EMV testing)
where we need more control over it. The "manual/software/osmo"
power control can only be implemented per TRX and not per
lchan. Add a very very basic control that checks the MS Power
used by the phone, the actual receive level and then adjust
the power.

The code doesn't take the history into account, if the phone
can not reach the requested power level the code will be stuck
(e.g. no timeout based on multiframes). It has a mode for a
fixed power control but no way to set it yet.
2014-12-11 14:35:05 +01:00
contrib sysmobts: Add VTY support to the sysmobts-mgr 2014-08-21 15:49:06 +02:00
doc add information on unit (milli-dB) to control interface doc 2014-08-25 08:42:08 +02:00
include sysmobts: Add a manual ms power level control 2014-12-11 14:35:05 +01:00
src sysmobts: Add a manual ms power level control 2014-12-11 14:35:05 +01:00
tests sysmobts: Add a manual ms power level control 2014-12-11 14:35:05 +01:00
.gitignore common: Ignore "si.valid" outside of _MAX_SYSINFO_TYPE 2014-05-22 21:17:49 +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.