Circuit nanoBSC design

A Interface Connections - Signalling

The nanoBSC is connected to only one R99 MSC or R4 MGW

according to the technical note of nanoBSC. The interface towards
MGW is a standard A interface over TDM (E1 or T1 depending on
the configuration). The circuit BSC uses an internal Signalling Gateway
to convert the A-Interface SCCP/MTP3 message transport from
MTP2/MTP1 on E1/T1 to M2UA/SCTP and vice versa. This Signalling
Gateway, also called as Media Gateway is integral part of the BSC and
different to R4 MGW.

nanoBSC interface towards legacy MSC

nanoBSC interface towards R4 MGW

A interface connection for Speech Calls and Transcoding

The Circuit BSC Media Gateway (Signalling Gateway in the above
picture) provides the transcoding function for speech calls. The GSM FR,
EFR, or AMR speech frames are transcoded to/from 64kbit/s u-law or A-
law PCM (dependant upon configuration option). Thus no legacy Trans
Coder is required between BSC and MSC or MSS/MGW

Signalling Requirement between R4 MGW and ip.access

nanoBSC

The NanoBSC is R99 compliant BSC, however it can be

connected to R4 Core Network, by using the backward
compatibility of the Core Network.

To integrate the NanoBSC into the Ericsson R4 Core, it can only

be connected to one MGW because it does not support load
sharing and quasi associated signalling. The NanoBSC supports
only Associated Signalling and from its perspective only the point
code of the MSC-S is visible, even though it is physically
connected to the MGW.

Therefore the R4 MGW needs to be set up to forward SS7

messages back and forth the between BSC and MSC-S in
transparent way for the BSC.

The NanoBSC can only be controlled by one MSC-S server

because it does not support MSC in Pool Functionality.