If it do not contain “additional R99 extensions” cause it’s optional ? and
the last 5 octet “38 03 f5 02 eb” is for other bssmap element ?
Looks to me likeInterRATHandoverInfo has been cut short, does the
decoding look right up to
accessStratumReleaseIndicator: rel-5 (1) ?
If so I think somethingh is missing in the message.
InterRATHandoverInfo ::= SEQUENCE {
-- This structure is defined for historical reasons, backward
compatibility with 44.018
predefinedConfigStatusList CHOICE {
absent NULL,
present PredefinedConfigStatusList
},
uE-SecurityInformation CHOICE {
absent NULL,
present UE-SecurityInformation
},
ue-CapabilityContainer CHOICE {
absent NULL,
-- present is an octet aligned string containing IE
UE-RadioAccessCapabilityInfo
present OCTET STRING (SIZE
(0..63))
},
-- Non critical extensions
v390NonCriticalExtensions CHOICE {
absent NULL,
present SEQUENCE {
interRATHandoverInfo-v390ext InterRATHandoverInfo-v390ext-IEs,
v3a0NonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v3a0ext InterRATHandoverInfo-v3a0ext-IEs,
laterNonCriticalExtensions SEQUENCE {
interRATHandoverInfo-v3d0ext
InterRATHandoverInfo-v3d0ext-IEs,
-- Container for additional R99 extensions
interRATHandoverInfo-r3-add-ext BIT
STRING
(CONTAINING
InterRATHandoverInfo-r3-add-ext-IEs) OPTIONAL,
v3g0NonCriticalExtensions SEQUENCE
{
interRATHandoverInfo-v3g0ext InterRATHandoverInfo-v3g0ext-IEs,
v4b0NonCriticalExtensions SEQUENCE
{
interRATHandoverInfo-v4b0ext InterRATHandoverInfo-v4b0ext-IEs,
v4d0NonCriticalExtensions SEQUENCE
{
interRATHandoverInfo-v4d0ext InterRATHandoverInfo-v4d0ext-IEs,
-- Reserved for future non
critical extension
v590NonCriticalExtensions SEQUENCE
{
interRATHandoverInfo-v590ext
InterRATHandoverInfo-v590ext-IEs,
v690NonCriticalExtensions SEQUENCE
{
interRATHandoverInfo-v690ext
InterRATHandoverInfo-v690ext-IEs,
v6b0NonCriticalExtensions
InterRATHandoverInfo-NonCriticalExtension-v6b0-IEs OPTIONAL
} OPTIONAL
} OPTIONAL
} OPTIONAL
} OPTIONAL
} OPTIONAL
} OPTIONAL
} OPTIONAL
}
}
}
From:
wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx]
On Behalf Of damker
Sent: den 13 september 2010 12:31
To: 'Community support list for Wireshark'
Subject: [Wireshark-users] bssmap malformed packet
Hi all
Attachment file is bssmap malformed
packet , might be because of element coding not updated.