Project

General

Profile

Roadmap » History » Version 10

laforge, 08/19/2017 10:16 AM

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