Roadmap » History » Version 11
laforge, 03/05/2018 07:25 PM
remove roadmap items thar are done, add some new
| 1 | 1 | laforge | h1. Overall Roadmap |
|---|---|---|---|
| 2 | |||
| 3 | 10 | laforge | 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: |
| 4 | 1 | laforge | |
| 5 | h2. BTS |
||
| 6 | |||
| 7 | 4 | laforge | * communication of BTS specific capabilities/features towards BSC (via Abis extension) to avoid BTS/BSC config mismatches #1614 |
| 8 | 1 | laforge | |
| 9 | h2. BSC |
||
| 10 | |||
| 11 | 3 | laforge | * Alarm handling |
| 12 | 1 | laforge | ** generation of Alarms inside the BSC |
| 13 | ** aggregation/forwarding of Alarms received from Abis |
||
| 14 | 11 | laforge | ** reporting of alarms via control interface |
| 15 | 1 | laforge | ** control interface / SNMP proxy for alarm -> trap conversion #1590 |
| 16 | * Move all media processing (TRAU frames, RTP) to separate MGW daemon, controlled via MGCP #61 |
||
| 17 | 11 | laforge | * 3GPP Local Call Local Switch #1602 |
| 18 | 1 | laforge | |
| 19 | h2. Core Network |
||
| 20 | |||
| 21 | * support of SMS delivery via GPRS #1587 |
||
| 22 | * support of combined CS/PS attach (2G and 3G) #1599 #1583 |
||
| 23 | 4 | laforge | * support of inter-BSC hand-over (after BSC/MSC split) #1609 |
| 24 | 3 | laforge | * support of inter-MSC hand-over (after HLR+AUC externalization) |
| 25 | 11 | laforge | * Local Call, Local Switching #2487 |
| 26 | 3 | laforge | * External interface to HLR #1643 |
| 27 | * External interface for USSD #1597 |
||
| 28 | 1 | laforge | * Generation of accounting/billing data #1596 |
| 29 | 11 | laforge | * LTE-GSM integration |
| 30 | ** CSFB |
||
| 31 | ** SMS-via-Gs |
||
| 32 | ** GSUP-to-Diameter Interworking Function |
||
| 33 | * External USSD interface |
||
| 34 | * Externalize SMS from OsmoMSC |
||
| 35 | 1 | laforge | |
| 36 | 3 | laforge | h2. SIP Interface (osmo-sip-connector |
| 37 | 1 | laforge | |
| 38 | 3 | laforge | * better VTY #1680 |
| 39 | * create user manual #1684 |
||
| 40 | * DTMF support |
||
| 41 | * call hold #1686 |
||
| 42 | * codec selection #1683 |
||
| 43 | 1 | laforge | |
| 44 | h2. 3G/3.5G related |
||
| 45 | 7 | msuraev | |
| 46 | 1 | laforge | * test/validate mobility between multiple hNodeB/smallcells |
| 47 | * hand-over between multiple hNodeB/smallcells |
||
| 48 | * Iu-CS/Iu-PS validation against RNCs |
||
| 49 | * Iuh validation against more hNodeB/smallcell vendors |
||
| 50 | * inter-RAT mobility (2G <-> 3G) #1588 |
||
| 51 | 11 | laforge | * IuUP implementation in OsmoMGW to have 2G <-> 3G calls |
| 52 | 3 | laforge | |
| 53 | 1 | laforge | h2. PCU |
| 54 | |||
| 55 | 3 | laforge | * more complete EGPRS implementation for uplink and downlink |
| 56 | * multi-slot uplink support |
||
| 57 | 1 | laforge | * PTCCH support (TA loop for fast moving MS) #1526, #1545 |
| 58 | * closed loop power control #1546 |
||
| 59 | * EC-GSM-IoT support #1780 |
||
| 60 | |||
| 61 | h2. Build and Test infrastructure |
||
| 62 | |||
| 63 | * more mature osmo-gsm-tester setup |
||
| 64 | 11 | laforge | ** develop more end-to-end test cases for MO-Call, MT-Call, Hold/Retrieve, USSD, SMS-in-Call, hand-over, etc. |
| 65 | ** not only functional testing, but performance testing (time to deliver N SMS) |
||
| 66 | 3 | laforge | ** GPRS/EGPRS testing |
| 67 | *** (single-MS ul/dl throughput, multi-MS ul/dl throughput) #1544 |
||
| 68 | *** mobility between different BTS/PCUs |
||
| 69 | 11 | laforge | ** testing against different modems (different baseband processor, protocol stack) |
| 70 | * extend the coverage of our [[cellular-infrastructure:TTCN3_Testsuites]] |
||
| 71 | 3 | laforge | |
| 72 | 1 | laforge | h2. Libraries/Infrastructure |
| 73 | 3 | laforge | |
| 74 | 1 | laforge | * VTYv2: Externalize VTY + config management #1601 #1613 #1600 |
| 75 | 3 | laforge | ** shared daemon that manages a MIB and offers VTY + control interface |
| 76 | to access that MIB |
||
| 77 | 1 | laforge | ** individual programs just access that config daemon via well-defined |
| 78 | API |
||
| 79 | ** preferably with transactions, roll-back |
||
| 80 | 5 | laforge | ** avoid hand-written code for parsing individual VTY commands |
| 81 | 3 | laforge | ** avoid duplicate code for VTY + Control interface |
| 82 | 11 | laforge | |
| 83 | h2. STP |
||
| 84 | |||
| 85 | * Global Title Routing |
||
| 86 | * Global Title Translation |
||
| 87 | * Load-Sharing / Fail-Over |
||
| 88 | 3 | laforge | |
| 89 | h2. Documentation |
||
| 90 | |||
| 91 | 8 | msuraev | * provide one conscise set of tutorials/howto's as opposed to fragmented and duplicated, outdated information in wiki #1719 |
| 92 | 3 | laforge | * regularly update user manuals and reference manuals |
