path: root/asn1/ranap
AgeCommit message (Collapse)AuthorFilesLines
2015-12-27RANAP-PDU-Contents: fix syntax error regarding InitialUE-MessageHarald Welte1-1/+1
With that syntax error, the RAC was not treated as a possible IE in the InitialUE-Message, causing decoder failure.
2015-12-24RANAP: Replace the last remainng TBCD-STRING with OCTET STRINGHarald Welte1-1/+1
in order to work around a bug in asn1c. When we keep the original TBCD-STRING, the APER-encoded PLMNidentity always has an extra leading length byte that the decoder doesn't expect.
2015-12-22Remove obsolete ffasn1c files.Neels Hofmeyr2-47803/+0
The ffasn1c files from early trials are obsolete, we're using asn1c now.
2015-12-19ranap ASN.1: Define IMSI as OCTET STRING to work around asn1c bugHarald Welte1-1/+1
When IMSI is a TBCD-STRING type, and TBCD-STRING is defined as OCTET STRING, we end up encoding the IMSI the wrong way. I don't knwo why that is, but changing it fixed the problem, as described below: before this commit: 00 17 PeranentNAS-UE-ID 40 criticality ignore 0a (length) 00 presence = IMSI 08 BUG: why the additional length field? 46 23 91 34 70 77 80 f3 IMSI (643219430777083) after this commit: 00 17 PeranentNAS-UE-ID 40 criticality ignore 09 (length) 50 presence = IMSI 46 23 91 34 70 77 80 f3 IMSI (643219430777083)
2015-12-19ranap: Don't forget ProtocolIE-CointainerPair around ProtocolIE-FieldPairHarald Welte1-1/+1
2015-12-18RANAP: Split FormatInformationParameter / SDUParameterItemHarald Welte1-2/+4
The definition of the above data types as per 3GPP specs results in a SEQUENCE_OF() an anonymous structure, which is slightly inconvenient to use. So let's split the SEQUENCE OF part and the actual definition of the item in separate types.
2015-12-16One further RANAP hacking sessionHarald Welte2-75/+145
This is not development, it is random trial and error hacking. I really hate the fact that we have no useful asn.1 code generator and need to work with hacks like asn1tostruct.py and asn1c without information object classes :/ This commit is a one-day-long iteration of trial+error, manually editing and adding the .asn source of RANAP until we get something that in the end at least compiles and links. Do I trust the resulting code? No. But we have no alternative :(
2015-12-16RANAP: Add more types/IEs to RANAP-PDU.asn and re-generate CHarald Welte1-1/+363
As asn1c cannot understand information object classes, we cannot compile RANAP-PDU-Contents.asn but instead need to manually add the respective infrmation elements to RANAP-PDU.asn.
2015-09-11remove obsolete asn1c makefiles in the asn1c/ hierarchyHarald Welte1-6/+0
we are generating the code locally in src/{ranap,rua,hnbap}
2015-09-10ranap: Add more manual definitions to RANAP-PDUsHarald Welte1-0/+121
It seems that individual IEs contain nested containers, and asn1c is not generating code for that unless we help it by some hand-crafted additional definitions. *sigh*
2015-08-30generate ASN.1 structures for each message withotu iformation object classHarald Welte1-1/+417
this is done semi-automatically using the asn1msgs.pl script.
2015-08-30asn1 syntax fixup for ffasn1cHarald Welte1-5/+1
2015-08-30Add Procedure Codes and IEI constants to CommonDataTypesHarald Welte1-2/+323
... this is what's required for asn1c to generate nice C language enums for it. Conversion was performed semi-automatically by use of asn1enum.pl
2015-08-30RANAP: Further qualify Constants. They're not just integerHarald Welte1-319/+325
2015-08-30RANAP ASN.1 Rewrite to avoid information object classesHarald Welte3-566/+159
If we avoid using Information Object Classes in the IE definitions (which are only used for Extension Containers), then we can compile the ASN.1 source using Lev Walkin's asn1c.
2015-08-30fixup ffasn1Harald Welte1-1/+1
2015-08-30give asn1c generated files more useful namesHarald Welte2-0/+0
2015-08-29add ffasn1c generated code for HNBAP, RANAP and RUAHarald Welte2-0/+47803
2015-08-29Import RANAP from 3GPP TS 25.413 V12.4.0 (2015-03)Harald Welte6-0/+7514