Project

General

Profile

Actions

Bug #1640

open

Missing release field/length in MS RA capability container

Added by prasadkg almost 6 years ago. Updated about 1 year ago.

Status:
Feedback
Priority:
Low
Assignee:
-
Target version:
-
Start date:
03/10/2016
Due date:
% Done:

10%

Spec Reference:

Description

Description
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

Proposal:
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.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)