Roadmap » History » Revision 2
Revision 1 (laforge, 11/14/2016 12:11 PM) → Revision 2/12 (neels, 11/14/2016 12:15 PM)
h1. Overall Roadmap This is the general direction in which we would like the Osmocom Cellular Infrastructure projects to move. None of this will of course happen without significant contribution and/or funding: h2. BTS * more systematic generation genration + reporting of alarms over Abis OML * communication of BTS specific capabilities/features towards BSC (via Abis extension) to avoid BTS/BSC config mismatches h2. BSC * BSC/MSC split: Real A interface with BSSAP/BSSMAP between MSC and BSC * Support of 3GPP A-over-IP in addition to current non-standard IPA multiplex / SCCPlite * Alarm handling ** generation of Alarms inside the BSC ** aggregation/forwarding of Alarms received from Abis ** reporting of alarms via control interface ** control interface / SNMP proxy for alarm -> trap conversion * Move all media processing (TRAU frames, RTP) to separate MGW daemon, controlled via MGCP h2. Core Network * BSC/MSC split: Real A interface with BSSAP/BSSMAP between MSC and BSC * externalize the HLR+AUC from the NITB (osmo-gsup-hlr) * support for UMTS AKA over GERAN * support of SMS delivery via GPRS * support of combined CS/PS attach (2G and 3G) * support of inter-BSC hand-over (after BSC/MSC split) * support of inter-MSC hand-over (after HLR+AUC externalization) * Real A interface (MTP2/MTP3/SCCP) * Move all media processing (TRAU frames, RTP) to separate MGW daemon, controlled via MGCP h2. 3G/3.5G related * Iu-CS and Iu-PS interface over M3UA (as specified in 3GPP), not just SUA (current implementation) * test/validate mobility between multiple hNodeB/smallcells * hand-over between bewtween multiple hNodeB/smallcells * Iu-CS/Iu-PS validation against RNCs * Iuh validation against more hNodeB/smallcell vendors * inter-RAT mobility (2G <-> 3G) * network with simultaneous simultaenous 2G and 3G/3.5G cells h2. PCU * more complete EGPRS implementation for uplink and downlink * multi-slot uplink support * PTCCH support (TA loop for fast moving MS) h2. Build and Test infrastructure * more mature osmo-gsm-tester setup ** have osmo-gsm-tester do full end-to-end regression testing on every commit or every night ** develop test cases for MO-Call, MT-Call, Hold/Retrieve, USSD, SMS-in-Call, hand-over, etc. ** not only functional testing, but performance testing (time to deliver N SMS) ** GPRS/EGPRS testing *** (single-MS ul/dl throughput, multi-MS ul/dl throughput) *** mobility between different BTS/PCUs ** testing against different modems (different baseband processr, protocol stack) h2. Libraries/Infrastructure * VTYv2: Externalize VTY + config management ** shared daemon that manages a MIB and offers VTY + control interface to access that MIB ** individual programs just access that config daemon via well-defined API ** preferably preferrably with transactions, roll-back ** avoid hand-written code for parsing individual idividual VTY commands ** avoid duplicate code for VTY + Control interface
