Bug #1640

Missing release field/length in MS RA capability container

Added by prasadkg almost 2 years ago. Updated 7 days ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Spec Reference:


In case of MS RA Capability container "Content_t", there is no dedicated field to denote the existence of 3GPP release in the message. The encoder goes out of max length allowed for release supported and encodes incorrectly.
Example vector with failure:
vector1 = 40165e000000268ca2a050740440000000300b2b2b2b2b
vector2 = 40165e00000026d0a2a0507400000220000000180b2b2b
vector1 == vector2 : FALSE

For this, we shall have precomputed value of length to terminate the container encoding before calling Content_Dissector in csn1.cpp file. The pre computing length logic routine shall consider the presence of different 3GPP releases.

For example in case of release 5 RA capability message , encoder should be able to code only till release 5 fields . In case of release 6 RA capability, encoder must be able to code till release 6. This release information must be available to the encoder to calculate length. Decoder will set the release field based on the fields present in the message.


#1 Updated by laforge about 1 year ago

the proposal seems fine to me. will your team be working on this?

#2 Updated by arvind.sirsikar about 1 year ago

  • Status changed from New to Stalled

Currently no impact on the test scenarios. Hence low priority.

#3 Updated by laforge 5 months ago

  • Assignee set to sysmocom

#4 Updated by laforge 3 months ago

  • Status changed from Stalled to New
  • Assignee changed from sysmocom to msuraev

#5 Updated by laforge 3 months ago

  • Priority changed from Normal to High

#6 Updated by msuraev 7 days ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

Also available in: Atom PDF