How panigrahip/3gppdecoder works
Project type and purpose
• This is a desktop GUI application written in C++ using the Qt framework.
• Its purpose is to decode 3GPP wireless messages (LTE, UMTS, GSM) and RLC PDU headers on Windows.
File structure
• Top‑level files:
• 3GPP Decoder.pro: Qt project file, defines build targets, source files, resources.
• README.md: project description and build instructions.
• Source files:
• main.cpp: application entry‑point, initializes QApplication and loads MainWindow.
• mainwindow.* (.cpp/.h/.ui): main UI container, menu actions, slots.
• aboutdialog.*, preferencedialog.*: modal dialogs for “About” and “Preferences.”
• Decoder modules:
• tsharkdecoder.*: wraps TShark-based decoding logic.
• umtsrlcdecoder.*: RLC PDU header decoding routines.
• Resources:
Key insights from README
• Built with Qt Creator, uses Qt widgets and signals/slots.
• Decoding feature set covers RRC, NAS messages and RLC headers.
Components
a. UI Layer
• QApplication / MainWindow
• AboutDialog, PreferenceDialog
• UI forms (*.ui) rendered by Qt Widgets
b. Business Logic / Decoder Layer
• TSharkDecoder module
• UMTSRLCDecoder module
• (Potentially future GSM / LTE-specific decoders)
c. Resource Layer
• Configuration storage (preferences)
d. External Dependencies
• Qt Framework (QtCore, QtWidgets)
• TShark (external binary/library invoked by TSharkDecoder)
Relationships and interactions
• On startup: main.cpp → QApplication → MainWindow
• User actions in MainWindow (e.g., “Open PDU,” “Decode”) → signal/slot to Business Logic
• Business Logic modules parse input data → return decoded structures/strings
• MainWindow (or dialogs) display results
• Preferences dialog reads/writes configuration → influences decoder behavior (e.g., paths)
• About dialog shows static metadata (version, links)
Architectural patterns and design principles
• MVC-ish separation: Qt UI forms and controllers distinct from decoder classes.
• Single responsibility: each decoder class handles one protocol.
• Resource bundling: images.qrc centralizes UI assets.
• Plugin‑ready design: new decoder modules can be added alongside existing ones.
Essential elements
• Class names and UI form names matching the codebase.
• Build file (.pro) indicating the overall project boundary.
• Notes on configuration and resource loading.