Actions
Feature #3613
closedFeature #2583: SGsAP Interface for LTE/ePC CSFB Support
SGsAP message encoding/decoding library
Start date:
10/02/2018
Due date:
% Done:
100%
Resolution:
Spec Reference:
Description
We need to develop a library for encoding/decoding of SGsAP protocol messages as per 3GPP TS 29.118 Section 8.
We can create unit tests using data encoded using the TITAN SGsAP encoder.
Updated by laforge over 5 years ago
- Status changed from New to In Progress
- Assignee set to laforge
- % Done changed from 0 to 30
Initial work for parsing/encoding SGsAP using the osmocom tlv parser as well as enums, value_strings, etc is in the laforge/sgsap branch of libosmocore.git, see http://git.osmocom.org/libosmocore/log/?h=laforge/sgsap, particularly
http://git.osmocom.org/libosmocore/commit/?h=laforge/sgsap&id=347a084fc4e03aecab4508bc34838989c80cf24e
Updated by laforge over 5 years ago
similarly, initial code for the osmo-msc side is at http://git.osmocom.org/osmo-msc/log/?h=laforge/sgsap
The completely untested code contains:- data structures for SGs connection, SGs MME, SGs per-UE context
- FSM for managing the VLR reset procedure to a given MME
- SGs server over SCTP using libosmo-netif, listening for MME connections
- per-UE FSM described in 3GPP spec
- message encoding/decoding helper functions
- VTY for configuring SGs interface related settings (ip/port, timers, vlr name, ...)
Updated by laforge over 5 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
implemented in 6721144c80c1160e28a2da86b0f33e050fe9adaf
Actions