-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to decode constrained OCTET_STRING in F1AP SetupRequest #118
Comments
I have observed this as well. I believe your report identifies the issue with greater clarity, but for completeness I'll link what I documented in the stale vlm fork vlm#456 |
Thanks for reporting it. Any recommendation for a fix? |
@ruffyontheweb @grzegorzniemirowski any suggestion for a fix? Or where, in your opinion, the problem is? Scouring through the whole compiler is infeasible for me now. |
Sorry, none from me. |
I'm sorry, I can't help. |
In F1AP ASN there is such definition of information element:
The size of this OCTET STRING is not properly processed by asn1c. It is treated as unconstrained. Here is generated code:
There is no sign of size constrained to 3 octets. So when this IE is encountered in APER data, decoder expects length field which is not there and the decoding fails.
The example code:
F1SetupRequest.zip
PER encoded F1SetupRequest to be checked on https://www.marben-products.com/decoder-asn1-nr/
38.473-F1AP-16.7.0.asn.zip
The F1AP ASN file
The text was updated successfully, but these errors were encountered: