initial commit to training-materials.git
This commit is contained in:
commit
a8c42ad586
|
@ -0,0 +1,8 @@
|
|||
Osmocom Training Materials
|
||||
==========================
|
||||
|
||||
This repository is a collection of training materials realated to
|
||||
Osmocom projects, particularly regarding the Osmocom CNI (Cellular
|
||||
Network Infrastructure).
|
||||
|
||||
It is very much under construction.
|
|
@ -0,0 +1,27 @@
|
|||
The training will cover the following topics
|
||||
• General GSM topics (not strictly Osmocom related, but pointing out Osmocom choices whenever 3GPP leaves implementation choices)
|
||||
◦ GSM architecture
|
||||
◦ GSM signaling (CS + PS)
|
||||
◦ 2G Call flow overview
|
||||
◦ Signaling Flow
|
||||
• Osmocom specifics
|
||||
◦ OsmoBSC, OsmoBTS and OsmoMGW introduction
|
||||
◦ OsmoBSC, OsmoBTS and OsmoMGW architecture, roadmap
|
||||
◦ OsmoBSC, OsmoBTS and OsmoMGW software architecture – processes, daemons
|
||||
◦ OsmoBSC, OsmoBTS and OsmoMGW supported features
|
||||
◦ Channel configuration
|
||||
◦ All interfaces & hardware of BSC
|
||||
◦ Installation and commissioning with hardware requirements
|
||||
◦ A/Abis/Um/Gb interfaces
|
||||
▪ interface configuration & commissioning
|
||||
◦ Software Upgrades
|
||||
• Configuration of Osmocom RAN components, specifically
|
||||
◦ BTS configuration
|
||||
◦ TRX configuration
|
||||
◦ BSC configuration
|
||||
◦ Hardware knowledge (interface level & processing level)
|
||||
◦ Operation and Maintenance
|
||||
◦ documentation (deployment scenarios – Test cases – Acceptance test procedure)
|
||||
• Troubleshooting
|
||||
◦ logging, trace, events/alarms,
|
||||
◦ recovery, common issues, workarounds, tips, utilities
|
|
@ -0,0 +1,46 @@
|
|||
1. GSM system architecture, interfaces, functional split between components; Osmocom specific design/implementation choices or deviations.
|
||||
|
||||
* Network elements (MS, BTS, BSC, MSC, HLR, PCU, SGSN, GGSN) and their role
|
||||
* Interfaces (Um, Abis, A, Gb, Gn, Gi, ...) and their protocol stacks
|
||||
* Transport Network Evolution (E1/SS7 to IP/SIGTRAN)
|
||||
* Osmocom Implementation Choices/Differences, such as
|
||||
** Abis-over-IP
|
||||
** TRX protocol betwen OsmoTRX and OsmoBTS; different BTS back-ends
|
||||
** 3GPP AoIP
|
||||
** BTS-located PCU
|
||||
** GSUP as CN protocol instead of TCAP/MAP
|
||||
** MGCP instead of Megaco between MSC(Server) and MGW
|
||||
|
||||
2. GSM call flows on Um/Abis/A interface for Voice and SMS with focus on Osmocom specifics
|
||||
* Scenarios
|
||||
** Location Update
|
||||
** MO-SMS, MT-SMS
|
||||
** MO Voice Call, MT Voice Call
|
||||
* Interfaces
|
||||
** Um (standard)
|
||||
** Abis/IP (IPA multiplex, TS 12.21 based OML, standard TS 08.58 RSL)
|
||||
** AoIP (3GPP standard, no legacy A-over-E1; SCCPlite support)
|
||||
** MGCP and GSUP messages in call flows
|
||||
|
||||
3. Introduction into Osmocom software + system architecture. Configuration + VTY Interface.
|
||||
|
||||
* one Linux process per network element; typically spawned by systemd
|
||||
* VTY interface for state introspection, configuration
|
||||
** VIEW / ENABLE / CONFIG node; VTY reference manuals
|
||||
* Osmocom logging sub-system; log sub-sytems, levels, targets (file, syslog, stderr, vty)
|
||||
* CTRL interface for programmatic access
|
||||
* TRX, BTS and BSC configuration with examples
|
||||
|
||||
4. Understanding of Osmocom development, testing, releases and packaging.
|
||||
|
||||
* Collaborative FOSS development process; Who writes code? why?
|
||||
* patch submission and review process (git, gerrit)
|
||||
* build testing before merge to master
|
||||
* continuous integration using Jenkins
|
||||
* autoamtic testing
|
||||
** unit tests (C)
|
||||
** integration tests (TTCN3)
|
||||
** end-to-end tests (osmo-gsm-tester)
|
||||
* Debian/Ubuntu packages
|
||||
** network:osmocom:nightly feed
|
||||
** network:osmocom:latest feed
|
Binary file not shown.
Binary file not shown.
Loading…
Reference in New Issue