Project

General

Profile

OsmoDevCon2012 » History » Version 19

laforge, 02/19/2016 10:47 PM

1 7 laforge
[[PageOutline]]
2 1 laforge
3
This page is used to plan and coordinate regarding the intended Osmocom Developer Conference 2012
4
5 7 laforge
= Osmocom Developer Conference 2012 =
6 1 laforge
7 7 laforge
Ths Osmocom Developer Conference 2012 ([wiki:OsmoDevCon2012]) is a event '''by project members for project members'''.
8
As such, the primary audience is people who have been contributing to the project.
9 1 laforge
10 10 laforge
It is '''not''' an event '''targetted at users'''.
11 1 laforge
12 7 laforge
Attendance requires registration (see below) and notification of acceptance.  There number of participants
13
is limited to about 10 to 15.
14 1 laforge
15 7 laforge
== When ==
16 1 laforge
17 7 laforge
March 23rd through 26th, 2012. This is Friday through Monday, to ensure people with regular day jobs
18
don't have to take off four but only two days.
19 1 laforge
20 7 laforge
== Where ==
21 1 laforge
22 7 laforge
In the conference room ("Seminarraum") of [http://www.c-base.org/ c-base], Berlin, Germany, the Universe.
23 1 laforge
24 7 laforge
The meeting / seminar / conference room at c-base is located on ground floor and has windows facing a courtyard,
25
i.e. it may be possible to set up some (GPS, Thuraya, etc.) antennas in that courtyard, if required.
26 1 laforge
27 7 laforge
== Format ==
28
29
The format of this workshop is not formal lectures/talks.  It's more like "guided discussions", i.e. there are
30
topics and each topic will get an "owner" who should introduce the topic and lead the discussion related to it.
31
32
== Who ==
33
34
(if you want to attend, please add your name below ASAP, no later than December 24th):
35
36
 * laforge
37
 * zecke
38
 * jolly
39
 * tnt
40
 * dieter?
41
 * pablo
42 8 ahuemer
 * ahuemer
43 9 laforge
 * dburgess00
44 12 horiz0n
 * horizon
45 13 khorben
 * khorben?
46 14 laforge
 * vogelchr
47 15 steve-m
 * steve-m
48 16 laforge
 * peter
49 17 laforge
 * jan
50
 * daniel (/stefan)
51 18 laforge
 * chemeris
52 1 laforge
53
54 18 laforge
== Presentations ==
55 1 laforge
56 18 laforge
=== Introduction to GSM/3G Core network protocols (!LaForge) ===
57
 * Core network protocols / architecture / transactions
58
 * The internet-hosted Osmocom internal SS7 network
59
  * what do you need to connect to it via M3UA, SUA or M2PA
60
  * connecting your BTS+BSC to it
61
  * what can you do with it?
62
63
=== Core Network protocol implementation (!LaForge) ===
64
 * Status of implementation in Erlang (osmo_ss7, osmo_sccp, osmo_map, signerl)
65
 * Status of Erlang HLR/AUC and possibly MSC/VLR based on that code
66
  * osmo-codegen (for auto-generated parser/generator of 04.08)
67
 * Status of currently bit-rotting C language (libosmo-asn1-tcap, libosmo-asn1-map, libosmo-tcap)
68
69
=== Towards running your own 3G network (Dieter) ===
70
 * How to talk Iu-over-IP with Ericsson and NSN NodeBs
71
72
=== UMTS/WCDMA phone-side (steve-m, Dieter) ===
73
 * UMTS/WCDMA telephone under our control
74
  * TBD
75
76
=== Femtocell architectures (Nion, Kevin, Dieter) ===
77
 * Vodafone / Alcatel-Lucent (RANAP)
78
 * SFR / Sercomm / Ubiquisys (UMA/GAN)
79
 * AT&T / Cisco / ip.access (URSL)
80
 * possible ways to support them
81 1 laforge
  * UMA gateway as BSC "replacement"
82
  * RANAP implementation in Erlang
83 18 laforge
84
=== osmo-bts and sysmoBTS (!LaForge, Andreas) ===
85 19 laforge
 * osmo-bts software architecture / code
86
  * back-ends for sysmoBTS, OpenBTS and maybe more (OsmocomBB)
87
 * sysmoBTS hardware / firmware
88
  * quick tour through high-level architecture
89
  * availability and pricing of sysmoBTS for Osmocom developers
90 18 laforge
91
=== osmo-msc (Holger) ===
92
 * having one BSC that can talk to multiple MSC
93
 * local call routing in osmo-bsc
94
95
=== cellmgr_ng (Holger) ===
96
 * what is cellmgr_ng / osmo-stp ?
97
98
== Working Group / Discussion ==
99
100
=== OpenBSC important TODOs items ===
101
 * externalize the database process
102
  * make transactions asynchronous
103
  * prepare for talking to MAP stack and real HLR later
104
 * not only build osmo-bsc, osmo-nitb, but also osmo-msc (just the MSC code)
105
 * use intra-bsc hand-over code from osmo-bsc, not only osmo-nitb
106
 * more interfactive configuration changes
107
 * externalize the RTP proxy / TRAU processing
108
  * build a new media gateway that deals with the user plane
109
 * externalize the SMSC
110
 * support for CSD
111
112
=== GPRS for OpenBTS + OsmoBTS (Ivan, Alexander, !LaForge) ===
113 1 laforge
  * PCU development (for public OpenBTS and osmo-bts)
114
  * SGSN completion and improvement
115 18 laforge
116
=== VTY improvements (?) ===
117
  * Incremental updates from VTY code
118 1 laforge
  * can we do something in common/shared code to facilitate this?
119 18 laforge
120
=== GMR-1 / Thuraya (Sylvain, Dimitri) ===
121 1 laforge
  * C-band signal intelligence
122
  * TBD
123 18 laforge
124
=== TETRA (?) ===
125
  * do we actaully have a need to talk about tetra?
126
127
=== Motorola Mo-bis support for OpenBSC (Dieter, !LaForge) ===
128
  * report from field trip to University of Brno
129
  * who wants some Horizon macro BTS?
130
131
=== libosmo-netif (pablo) ===
132
133 7 laforge
 * libosmo-netif as unified API for signalling + voice
134 18 laforge
135
136
=== OsmocomBB status + round table (Andreas, Sylvain, !LaForge) ===
137
  * we should try to continue the MTK port
138
  * porting of L2 or even L3 into phone
139
  * port of code into NuttX
140
  * user interface
141
  * "transactional" L1
142
143
=== Wireshark patches / problems (!LaForge, Pablo) ===
144
  * how can we accelerate the process of inclusion?
145
  * should we provide binary builds of our git branch?
146
  * should we move new code to plugins instead of built-in dissectors?
147
148
=== OpenBSC regression testing setup ===
149
  * !LaForge has been building a remote-controlled setup with Ericsson, Siemens, Nokia and ip.access BTS that should be used for regular regression tests
150 1 laforge
  * how to automatize this?  jenkins integration? who wants access to the system?
151
152 19 laforge
=== misc ===
153
 * OsmoSDR ?
154
 * SIMtrace ?
155
 * UmTRX ?
156
 * OpenBTS developments?
157 13 khorben
158 1 laforge
== Travel ==
159 6 laforge
160 13 khorben
=== Airports ===
161 1 laforge
Berlin has two active airports during OsmoDevCon2012: Tegel (TXL) and Schoenefeld (SXF).  Neither of the two
162 6 laforge
is exactly close to the venue, so pick whatever works best for you.
163
164 13 khorben
From SXF you can take local trains (S-Bahn), switch at Ostkreuz into another train and exit at Jannowitzbrücke.
165 6 laforge
You will need a "Berlin ABC" ticket.
166
167
From TXL, you can take the bus 128 to Osloer Straße, and then change for the U8 and exit at Jannowitzbrücke. Alternatively, the TXL bus can drop you at Alexanderplatz, one S-Bahn stop away from Jannowitzbrücke. You will need a "Berlin AB" ticket either way.
168 13 khorben
169 6 laforge
=== Train ===
170
171
You can take long distance trains to ''Berlin Ostbahnhof'', which is only one S-Bahn stop away from Jannowitzbrücke, where C-Base is located
172
173
=== Public Transport ===
174
175
Check http://www.bvg.de/ for maps, fares, etc.
176
177
=== Car ===
178
179
There is some public parking in Rungestrasse where c-base is located, but it is always very crowded.  Parking your car there is thus not recommended.
180
181
== Accomodation ==
182
183 11 laforge
Berlin has tons of options, from very cheap to plush and expensive.  Pick your favourite.
184
185
The closest low-end option in walking distance is the A&O Hostel Berlin Mitte, which has both a hotel as well as a hostel:
186
 * Hotel: http://www.aohostels.com/en/berlin/hotel-mitte/ (from 32 EUR per person per night in single room, 18 EUR per person in two bed room)
187 1 laforge
 * Hostel: http://www.aohostels.com/en/berlin/hostel-mitte/hostel/info/ (from 12 EUR per night in a dorm)
188
189
There's also Hotel Alameda a few more steps from the venue: http://www.hotel-alameda-berlin.de/index.php?article_id=1&clang=1
190
191
== Spectrum License ==
192
193
We will apply for a regulatory permit to use 2 GSM 1800 ARFCN for test + development.
Add picture from clipboard (Maximum size: 48.8 MB)