re introducing e1 in osmobsc
play

Re-introducing E1 in OsmoBSC Harald Welte - PowerPoint PPT Presentation

Re-introducing E1 in OsmoBSC Harald Welte <laforge@gnumonks.org> Intro OpenBSC (later OsmoNITB) started with E1 BTS until NITB Split, E1 support remained present even old OsmoBSC (sccplite) never had E1 BTS suport new OsmoBSC also has no


  1. Re-introducing E1 in OsmoBSC Harald Welte <laforge@gnumonks.org>

  2. Intro OpenBSC (later OsmoNITB) started with E1 BTS until NITB Split, E1 support remained present even old OsmoBSC (sccplite) never had E1 BTS suport new OsmoBSC also has no E1 BTS support let’s change that!

  3. Classic OsmoNITB with E1-BTS + ext MNCC GSM_TCHF_FRAME SS0 SS1 MNCC subchan_demux trau_decode SS2 S PBX T SS3 1 E1/T1 e1_input BTS 64k Slots OsmoNITB Abis/E1 with 16k sub-slots in 64k slots E1 device offers 64k timeslots only 16k sub-channel mux/demux done in software TRAU frames in 16k sub-slots decoded (to FR/EFR codec frames) passed next to MNCC signaling over MNCC socket

  4. Classic OsmoNITB with E1-BTS + ext MNCC + RTP SS0 SS1 RTP subchan_demux RTP trau_decode SS2 S PBX T SS3 1 E1/T1 e1_input BTS 64k Slots OsmoNITB just like previous example, but we generate RTP from TRAU frames MNCC interface is signaling only user voice frames handled via RTP

  5. Classic OsmoNITB with IP-BTS + ext MNCC + RTP proxy RTP RTP PBX Abis/IP rtp_sock BTS RTP OsmoNITB Abis/IP BTS use RTP transport for speech frames OsmoNITB is asked to provide RTP proxy functionality

  6. Classic OsmoNITB with IP-BTS + ext MNCC + direct RTP MNCC PBX Abis/IP BTS OsmoNITB RTP P T R Abis/IP BTS use RTP transport for speech frames OsmoNITB rtp_proxy is disabled RTP data passes directly from BTS to external PBX and vice-versa

  7. IP-BTS User Plane in post-NITB When using IP-based BTS like OsmoBTS, this looks like this: RTP to/from the BTS is handled by the BSC-colocated OsmoMGW

  8. E1-BTS User Plane in post-NITB When using E1-based BTS, it should look like this: TRAU frames in 16k E1 sub-slots to/from the BTS are handled by the BSC-colocated OsmoMGW OsmoMGW needs real media gateway functionality from E1 sub-slots to RTP E1 driver needs to support single E1 span (line) that opens RSL/OML LAPDm signaling on one TS from OsmoBSC opens TRAU on other TS from OsmoMGW osmo-bsc.cfg states which Um TS maps to which E1 TS/SS osmo-bsc uses MGCP EP naming scheme like E1/Line1/TS4/SS2@mgw

  9. EOF End of File

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend