https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13721

            Bug ID: 13721
           Summary: x2ap dissector dissects eUTRANcellIdentifier wrongly
                    as 8 hex number (32 bit)
           Product: Wireshark
           Version: 2.3.x (Experimental)
          Hardware: x86
                OS: Windows 7
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: xiaoc...@foxmail.com
  Target Milestone: ---

Created attachment 15559
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15559&action=edit
x2ap

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
  x2ap dissector dissects eUTRANcellIdentifier wrongly as 8 hex number (32
bit). The eUTRANcellIdentifier field is 28 bit, so 7 hex number. The binary and
decimal value are correct. I attached one pcap file which has the
eUTRANcellIdentifier field.
  I found the is comprised of  eNB ID (20 bit) and Cell ID (8 bit). Could we
dissect eNB ID and Cell ID further although they are not standard x2ap field?

0002e000 = 188416
0002e00 = 11776  (aligned with decimal part)

 pLMN-Identity: 64f033
                                            Mobile Country Code (MCC): China
(460)
                                            Mobile Network Code (MNC): Unknown
(33)
                                        eUTRANcellIdentifier: 0002e000 [bit
length 28, 4 LSB pad bits, 0000 0000  0000 0010  1110 0000  0000 .... decimal
value 11776]

http://www.sharetechnote.com/html/Handbook_LTE_IDs_in_LTE.html
##################################
ECI
E-UTRAN Cell Identifier
To identify a Cell within a PLMN
ECI (28 Bits) = eNB ID + Cell ID

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to