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:

BTS¶

• communication of BTS specific capabilities/features towards BSC (via Abis extension) to avoid BTS/BSC config mismatches #1614

BSC¶

• 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 #1590
• Move all media processing (TRAU frames, RTP) to separate MGW daemon, controlled via MGCP #61
• 3GPP Local Call Local Switch #1602

Core Network¶

• support of SMS delivery via GPRS #1587
• support of combined CS/PS attach (2G and 3G) #1599 #1583
• support of inter-BSC hand-over (after BSC/MSC split) #1609
• support of inter-MSC hand-over (after HLR+AUC externalization)
• Local Call, Local Switching #2487
• External interface to HLR #1643
• External interface for USSD #1597
• Generation of accounting/billing data #1596
• LTE-GSM integration
  • CSFB
  • SMS-via-Gs
  • GSUP-to-Diameter Interworking Function
• External USSD interface
• Externalize SMS from OsmoMSC

SIP Interface (osmo-sip-connector¶

• better VTY #1680
• create user manual #1684
• DTMF support
• call hold #1686
• codec selection #1683

3G/3.5G related¶

• test/validate mobility between multiple hNodeB/smallcells
• hand-over between multiple hNodeB/smallcells
• Iu-CS/Iu-PS validation against RNCs
• Iuh validation against more hNodeB/smallcell vendors
• inter-RAT mobility (2G <-> 3G) #1588
• IuUP implementation in OsmoMGW to have 2G <-> 3G calls

PCU¶

• more complete EGPRS implementation for uplink and downlink
• multi-slot uplink support
• PTCCH support (TA loop for fast moving MS) #1526, #1545
• closed loop power control #1546
• EC-GSM-IoT support #1780

Build and Test infrastructure¶

• more mature osmo-gsm-tester setup
  • develop more end-to-end 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) #1544
    • mobility between different BTS/PCUs
  • testing against different modems (different baseband processor, protocol stack)
• extend the coverage of our TTCN3_Testsuites

Libraries/Infrastructure¶

• VTYv2: Externalize VTY + config management #1601 #1613 #1600
  • 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 with transactions, roll-back
  • avoid hand-written code for parsing individual VTY commands
  • avoid duplicate code for VTY + Control interface

STP¶

• Global Title Routing
• Global Title Translation
• Load-Sharing / Fail-Over

Documentation¶

• provide one conscise set of tutorials/howto's as opposed to fragmented and duplicated, outdated information in wiki #1719
• regularly update user manuals and reference manuals