Project

General

Profile

Roadmap » History » Version 1

laforge, 11/14/2016 12:11 PM

1 1 laforge
h1. Overall Roadmap
2
3
This is the general direction in which we would like the Osmocom Cellular Infrastructure projects to move.  None of this will of course happen
4
without significant contribution and/or funding:
5
6
h2. BTS
7
8
* more systematic genration + reporting of alarms over Abis OML
9
* communication of BTS specific capabilities/features towards BSC (via Abis extension) to avoid BTS/BSC config mismatches
10
11
h2. BSC
12
13
* BSC/MSC split: Real A interface with BSSAP/BSSMAP between MSC and BSC
14
* Support of 3GPP A-over-IP in addition to current non-standard IPA multiplex / SCCPlite
15
* 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
** control interface / SNMP proxy for alarm -> trap conversion
20
* Move all media processing (TRAU frames, RTP) to separate MGW daemon, controlled via MGCP
21
22
h2. Core Network
23
24
* BSC/MSC split: Real A interface with BSSAP/BSSMAP between MSC and BSC
25
* externalize the HLR+AUC from the NITB (osmo-gsup-hlr)
26
* support for UMTS AKA over GERAN
27
* support of SMS delivery via GPRS
28
* support of combined CS/PS attach (2G and 3G)
29
* support of inter-BSC hand-over (after BSC/MSC split)
30
* support of inter-MSC hand-over (after HLR+AUC externalization)
31
* Real A interface (MTP2/MTP3/SCCP)
32
* Move all media processing (TRAU frames, RTP) to separate MGW daemon, controlled via MGCP
33
34
h2. 3G/3.5G related
35
36
* Iu-CS and Iu-PS interface over M3UA (as specified in 3GPP), not just SUA (current implementation)
37
* test/validate mobility between multiple hNodeB/smallcells
38
* hand-over bewtween multiple hNodeB/smallcells
39
* Iu-CS/Iu-PS validation against RNCs
40
* Iuh validation against more hNodeB/smallcell vendors
41
* inter-RAT mobility (2G <-> 3G)
42
* network with simultaenous 2G and 3G/3.5G cells
43
44
h2. PCU
45
46
* more complete EGPRS implementation for uplink and downlink
47
* multi-slot uplink support
48
* PTCCH support (TA loop for fast moving MS)
49
50
h2. Build and Test infrastructure
51
52
* more mature osmo-gsm-tester setup
53
** have osmo-gsm-tester do full end-to-end regression testing on every commit or every night
54
** develop test cases for MO-Call, MT-Call, Hold/Retrieve, USSD, SMS-in-Call, hand-over, etc.
55
** not only functional testing, but performance testing (time to deliver N SMS)
56
** GPRS/EGPRS testing
57
*** (single-MS ul/dl throughput, multi-MS ul/dl throughput)
58
*** mobility between different BTS/PCUs
59
** testing against different modems (different baseband processr, protocol stack)
60
61
h2. Libraries/Infrastructure
62
63
* VTYv2: Externalize VTY + config management
64
** shared daemon that manages a MIB and offers VTY + control interface to access that MIB
65
** individual programs just access that config daemon via well-defined API
66
** preferrably with transactions, roll-back
67
** avoid hand-written code for parsing idividual VTY commands
68
** avoid duplicate code for VTY + Control interface
Add picture from clipboard (Maximum size: 48.8 MB)