Roadmap » History » Version 3
laforge, 11/14/2016 12:34 PM
1 | 1 | laforge | h1. Overall Roadmap |
---|---|---|---|
2 | |||
3 | 3 | laforge | This is the general direction in which we would like the Osmocom |
4 | Cellular Infrastructure projects to move. None of this will of course |
||
5 | happen |
||
6 | 1 | laforge | without significant contribution and/or funding: |
7 | |||
8 | h2. BTS |
||
9 | |||
10 | 3 | laforge | * more systematic generation + reporting of alarms over Abis OML #1615 |
11 | * communication of BTS specific capabilities/features towards BSC (via |
||
12 | * Abis extension) to avoid BTS/BSC config mismatches #1614 |
||
13 | 1 | laforge | |
14 | h2. BSC |
||
15 | |||
16 | * BSC/MSC split: Real A interface with BSSAP/BSSMAP between MSC and BSC |
||
17 | 3 | laforge | * Support of 3GPP A-over-IP in addition to current non-standard IPA |
18 | * multiplex / SCCPlite |
||
19 | 1 | laforge | * Alarm handling |
20 | ** generation of Alarms inside the BSC |
||
21 | ** aggregation/forwarding of Alarms received from Abis |
||
22 | 3 | laforge | ** reporting of alarms via control interface· |
23 | ** control interface / SNMP proxy for alarm -> trap conversion #1590 |
||
24 | * Move all media processing (TRAU frames, RTP) to separate MGW daemon, |
||
25 | * controlled via MGCP |
||
26 | * late assignment instead of very early assignment #1778 |
||
27 | 1 | laforge | |
28 | h2. Core Network |
||
29 | |||
30 | * BSC/MSC split: Real A interface with BSSAP/BSSMAP between MSC and BSC |
||
31 | 3 | laforge | * #1594 |
32 | * externalize the HLR+AUC from the NITB (osmo-gsup-hlr) #1711, #1591, |
||
33 | * #1592, #30,· |
||
34 | * support for UMTS AKA over GERAN #1711 |
||
35 | * support of SMS delivery via GPRS #1587 |
||
36 | * support of combined CS/PS attach (2G and 3G) #1599 #1583 |
||
37 | * support of inter-BSC hand-over (after BSC/MSC split) #1609 |
||
38 | 1 | laforge | * support of inter-MSC hand-over (after HLR+AUC externalization) |
39 | * Real A interface (MTP2/MTP3/SCCP) |
||
40 | 3 | laforge | * Move all media processing (TRAU frames, RTP) to separate MGW daemon, |
41 | * controlled via MGCP |
||
42 | * Local Call, Local Switching #1602 |
||
43 | * External interface to HLR #1643 |
||
44 | * External interface for USSD #1597 |
||
45 | 1 | laforge | |
46 | 3 | laforge | h2. SIP Interface (osmo-sip-connector |
47 | |||
48 | * better VTY #1680 |
||
49 | * create user manual #1684 |
||
50 | * DTMF support |
||
51 | * call hold #1686 |
||
52 | * codec selection #1683 |
||
53 | |||
54 | 1 | laforge | h2. 3G/3.5G related |
55 | |||
56 | 3 | laforge | * Iu-CS and Iu-PS interface over M3UA (as specified in 3GPP), not just |
57 | * SUA (current implementation) #1595, #1589· |
||
58 | 1 | laforge | * test/validate mobility between multiple hNodeB/smallcells |
59 | * hand-over between multiple hNodeB/smallcells |
||
60 | * Iu-CS/Iu-PS validation against RNCs |
||
61 | * Iuh validation against more hNodeB/smallcell vendors |
||
62 | 3 | laforge | * inter-RAT mobility (2G <-> 3G) #1588 |
63 | 1 | laforge | * network with simultaneous 2G and 3G/3.5G cells |
64 | |||
65 | h2. PCU |
||
66 | |||
67 | * more complete EGPRS implementation for uplink and downlink |
||
68 | * multi-slot uplink support |
||
69 | 3 | laforge | * PTCCH support (TA loop for fast moving MS) #1526, #1545 |
70 | * closed loop power control #1546 |
||
71 | * EC-GSM-IoT support #1780 |
||
72 | 1 | laforge | |
73 | h2. Build and Test infrastructure |
||
74 | |||
75 | * more mature osmo-gsm-tester setup |
||
76 | 3 | laforge | ** have osmo-gsm-tester do full end-to-end regression testing on every |
77 | commit or every night |
||
78 | ** develop test cases for MO-Call, MT-Call, Hold/Retrieve, USSD, |
||
79 | SMS-in-Call, hand-over, etc. |
||
80 | ** not only functional testing, but performance testing (time to deliver |
||
81 | N SMS) |
||
82 | 1 | laforge | ** GPRS/EGPRS testing |
83 | 3 | laforge | *** (single-MS ul/dl throughput, multi-MS ul/dl throughput) #1544 |
84 | 1 | laforge | *** mobility between different BTS/PCUs |
85 | 3 | laforge | ** testing against different modems (different baseband processr, |
86 | protocol stack) |
||
87 | 1 | laforge | |
88 | h2. Libraries/Infrastructure |
||
89 | |||
90 | 3 | laforge | * VTYv2: Externalize VTY + config management #1601 |
91 | ** shared daemon that manages a MIB and offers VTY + control interface |
||
92 | to access that MIB |
||
93 | ** individual programs just access that config daemon via well-defined |
||
94 | API |
||
95 | 1 | laforge | ** preferably with transactions, roll-back |
96 | ** avoid hand-written code for parsing individual VTY commands |
||
97 | ** avoid duplicate code for VTY + Control interface |
||
98 | 3 | laforge | |
99 | h2. Documentation |
||
100 | |||
101 | * provide one conscise set of tutorials/howto's as opposed to fragmented |
||
102 | * and duplicated, outdated information in wiki #1719 |
||
103 | * regularly update user manuals and reference manuals |