cellular-infrastructure
/
osmo-bsc
mirror of https://gerrit.osmocom.org/osmo-bsc
9
0
Fork 0
Code Issues Releases Wiki Activity

doc: overview: replace section TRAU mapper / E1 sub-channel muxer 

The manual contains a section about a TRAU mapper / E1 sub-channel
muxer. This section seems to be copied from the OsmoNITB manual. In
OsmoNITB everything was integrated in one binary, now dealing with TRAU
frames is the task of the MGW. Let's remove the section but still leave
a word about how Speech traffic is handled/relayed by OsmoBSC.

Change-Id: If33589feb80e1b29b4f841b678fe5329b8c06a76
This commit is contained in:
Philipp Maier 2023-03-21 15:09:38 +01:00
parent 563652890c
commit 64c0e6e11c
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/manuals/chapters/overview.adoc
View File

@ -135,11 +135,13 @@ Station Controller, i.e.
For more information, see <<net>>, <<bts>> and <<bts-examples>>.
==== TRAU mapper / E1 sub-channel muxer
==== Speech traffic
Unlike classic GSM networks, OsmoBSC does not perform any transcoding.
Rather, a compatible codec is selected for both legs of a call, and
codec frames are passed through transparently. In order to achieve this
with E1 based BTS, OsmoBSC contains a E1 sub-channel de- and
re-multiplexer as well as a TRAU mapper that can map uplink to downlink
frames and vice versa.
OsmoBSC, by itself, does not perform any transcoding or relaying of user plane
speech traffic. This task is handled entirely by a BSC co-located media gateway,
such as OsmoMGW, which will take care of relaying the RTP traffic from the BTS
into the core network.
In case classic E1 based BTSs are used, OsmoBSC will instruct the MGW to
convert between TRAU frames on the E1 side and RTP frames on the IP based core
network side.