OsmoCon2017 Programme » History » Version 4

laforge, 02/17/2017 05:18 PM

1 1 laforge
h1. OsmoCon2017 Programme
2 2 laforge
3 3 laforge
Below is a list of the individual talks/topics that we will cover as part of the schedule of [[OsmoCon2017]].
4 3 laforge
5 4 laforge
h2. Welcome / Introduction / Osmocom Project 101
6 4 laforge
7 4 laforge
This is a short introduction that will introduce you to the Osmocom project.  It will give a short introduction to many of its member projects, as well as some background on the motivations and the people behind the project.  Wile OsmoCon2017 covers only the cellular infrastructure projects (GSM/GRPS/EDGE/UMTS/HSPA), Osmocom in reality is much more than that.
8 4 laforge
9 2 laforge
h2. Running a basic circuit-switched Osmocom GSM network
10 2 laforge
11 2 laforge
This is an introductory talk running you through everything that's required to run a minimal small/private circuit-switched GSM network using the Osmocom stack and its various components.  The focus will be very practical / hands-on.  Target audience is to entrry-level users with limited experience in using OpenBSC & co. so far.
12 2 laforge
13 2 laforge
h2. Configuring + running GPRS/EDGE data services with OsmoPCU, OsmoSGSN and OpenGGSN
14 2 laforge
15 2 laforge
Based on the previous talk about a circuit-switched GSM network, it will describe what is required to extend the network with GPRS and EDGE/EGRPS features.  It will cover the required configuration changes as well as the related OsmoPCU, OsmoSGSN and OpenGGSN software.
16 2 laforge
17 2 laforge
h2. Interfacing with VoIP using osmo-sip-connector
18 2 laforge
19 2 laforge
Having a private stand-alone GSM network is great, but most often people want to interface this network somehow to other networks, whether private or public.  In the past, many people did so using lcr (Linux Call Router).  LCR is a very powerful soft-PBX for Linux.  However, in many cases a thin gateway to SIP is all that's required.  So in order to reduce the complexity and to avoid having to understand and configure yet another program, osmo-sip-connector has been developed.  This talk explains the MNCC interface of OsmoNITB and shows you how to add osmo-sip-connector to interface to external SIP PBXs or SIP providers using SIP trunking.
20 2 laforge
21 2 laforge
h2. Setting up a 3G network using osmo-iuh and a femto/small cell
22 2 laforge
23 2 laforge
GSM is a robust system with maximum interoperability and minimal spectrum requirements.  However, the GPRS/EGPRS data speets are prohibitive for anything beyond very basic telematics usage these days.  This talk will show you how to run a 3G network by using a femtocell and OsmoHNBGW in combination with your trusted Osmocom cellular core network components.
24 2 laforge
25 4 laforge
Speaker: Neels Hofmeyr
26 2 laforge
27 2 laforge
h2. Using the Osmocom control interface
28 2 laforge
29 2 laforge
Everyone who has used Osmocom will have used its command line interface, the VTY.  The VTY is a humand interface, designed for interaction of human system administrators with the system.  However, there is also a much-underused CTRL (control) interface.  It is a machine-parseable interface intended for interactions of external programs with the Osmocom software components.
30 2 laforge
31 2 laforge
h2. Osmocom Roadmap
32 2 laforge
33 2 laforge
This talk will provide you with up-to-date information on current developments and the future of the Osmocom cellular infrastructure projects.  A lot has been going on in the development community during 2016 and early 2017.  The most fundamental changes in Osmocom are about to be merged to "master" and officially released: The split of the NITB (Network In the Box) into separate components.  Stay tuned!
34 1 laforge
35 4 laforge
Speaker: Harald Welte
36 4 laforge
37 4 laforge
38 2 laforge
h2. Reporting and investigating issues in Osmocom
39 2 laforge
40 2 laforge
No software is perfect, particularly not when it has to interoperate with mobile device from many different manufacturers, all of whom may have a slightly different interpretation of what the GSM specifications say.  This talk will show you what you can do to investigate any issues you may encounter.  It covers topics like the comprehensive Osmocom logging infrastructure, taking protocol traces of the various interfaces and GSMTAP. It also informs you how to report your findings to the development team in a way that provides them all they need for hopefully fixing the issue.
41 2 laforge
42 2 laforge
43 2 laforge
h2. Osmocom Project Infrastructure (redmine, mailman, git, gerrit, jenkins, ...)
44 2 laforge
45 2 laforge
People with strong background in Free/Open Source Software projects are mostly familiar with various tools like redmine, mailman, git, gerrit, jenkins.  However, if you're not from a development background, particulraly not one from the FOSS world, they will be quite new to you.  This talk is covering the various different tools the Osmocom projects use for communication, project management, revision control and continuous integration.
46 2 laforge
47 2 laforge
h2. Fundamental GSM radio frequency planning
48 2 laforge
49 2 laforge
Operating a GSM network not only requires the hardware and software, but also requires some understanding of radio frequency propagation and radio frequency planning.  Only with good planning, you will get the optimum network coverage and capacity.  This talk cannot turn you into an expert in the field, but at least provides you with the fundamental concepts, such as path loss, link budget.  It will also present some example calculations and tools (to be) released within Osmocom to help you with basic RF planning.
50 2 laforge
51 1 laforge
The talk also covers an introduction into the RF electronics after your BTS, i.e. coaxial cables, connectors, duplexers, filters, attenuators, terminators, antennas, etc.
52 4 laforge
53 4 laforge
Speaker: Harald Welte
Add picture from clipboard (Maximum size: 48.8 MB)