wireshark-dev August 2010 archive
Main Archive Page > Month Archives  > wireshark-dev archives
wireshark-dev: Re: [Wireshark-dev] Wireshark-dev Digest, Vol 51,

Re: [Wireshark-dev] Wireshark-dev Digest, Vol 51, Issue 39

From: 燠饑 <olinalee_at_nospam>
Date: Tue Aug 31 2010 - 08:34:50 GMT
To: wireshark-dev@wireshark.org

Hello,
Thanks for your reply quickly.
I mean that I want to known every bit of feature group indicators of packet-lte-rrc.c file, but the fuction called dissect_per_bit_string(),and dissecte the all bits of data feild not each of them.
For example,When the UE is queried for it*s capabilities, it responds with the following feature group indicator.
The ans.1 encode ueCapabilityRAT-container is set to
80:9f:f0:03:00:00:8f:06:88:40:00
Here is the non-asn encoded bytes sent by the controller to the mdmApp.
1e 0d 10 80 (the wireshark capture and display)
1e = 0001 1110
0d = 0000 1101
10 = 0001 0000
80 = 1000 0000

 

Index of indicator(bit number)

Definition

(description of the supported functionality, if indicator set to one&true*)

Notes

1 (leftmost bit)

 

 

off

- Intra-subframe frequency hopping for PUSCH scheduled by UL grant

- Extended cyclic prefix with 忖f = 7.5kHz for DL resource block

- DCI format 3a (TPC commands for PUCCH and PUSCH with single bit power adjustments)

- Multi-user MIMO for PDSCH

- Aperiodic CQI/PMI/RI reporting on PUSCH: Mode 2-0 每 UE selected subband CQI without PMI

- Aperiodic CQI/PMI/RI reporting on PUSCH: Mode 2-2 每 UE selected subband CQI with multiple PMI

 

2

 

 

off

- Simultaneous CQI and ACK/NACK on PUCCH, i.e. PUCCH format 2a and 2b

- Absolute TPC command for PUSCH

- Resource allocation type 1 for PDSCH

- Periodic CQI/PMI/RI reporting on PUCCH: Mode 2-0 每 UE selected subband CQI without PMI

- Periodic CQI/PMI/RI reporting on PUCCH: Mode 2-1 每 UE selected subband CQI with single PMI

 

3

 

off

- Semi-persistent scheduling

- TTI bundling

- 5bit RLC UM SN

- 7bit PDCP SN

 

4

 

on

- Short DRX cycle

 

5

 

on

- Long DRX cycle

- DRX command MAC control element

 

6

on

- Piroritized bit rate

 

7

on

- RLC UM

- can only be set as &false* if the UE does not support voice

8

 

off

- EUTRA RRC_CONNECTED to UTRA CELL_DCH PS handover

- can only be set to &true* if the UE has set bit number 22 to &true*

9

 

off

- EUTRA RRC_CONNECTED to GERAN GSM_Dedicated handover

- related to SR-VCC

- can only be set to &true* if the UE has set bit number 23 to &true*

10

 

off

- EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order

- EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order with NACC (Network Assisted Cell Change)

 

11

off

- EUTRA RRC_CONNECTED to 1xRTT CS Active handover

- can only be set to &true* if the UE has sets bit number 24 to &true*

12

off

- EUTRA RRC_CONNECTED to HRPD Active handover

- can only be set to &true* if the UE has set bit number 24 to &true*

13

 

on

- Inter-frequency handover

- can only be set to &true* if the UE has set bit number 24 to &true*

14

 

on

- Measurement reporting event: Event A4 每 Neighbour > threshold

- Measurement reporting event: Event A5 每 Serving < threshold1 & Neighbour > threshold2

 

15

 

off

- Measurement reporting event: Event B1 每 Neighbour > threshold

 

16

 

on

- Periodical measurement reporting for non-ANR related measurements

 

17

 

Off

- Periodical measurement reporting for SON / ANR

- ANR related intra-frequency measurement reporting events

 

18

 

Off

- ANR related inter-frequency measurement reporting events

 

19

 

Off

- ANR related inter-RAT measurement reporting events

 

20

 

On

- RB combination: SRB1 and SRB2 for DCCH + 1x AM DRB + 1x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 2x AM DRB + 1x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 2x AM DRB + 2x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 3x AM DRB + 1x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 3x AM DRB + 2x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 4x AM DRB + 1x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 4x AM DRB + 2x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 5x AM DRB + 3x UM DRB

- RB combination: SRB1 and SRB2 for DCCH + 8x AM DRB

- RB combination: SRB1 and SRB2 for DCCH + 1x AM DRB + 1x UM DRB must be supported/tested if the UE supports voice

21

Off

- Predefined intra-subframe frequency hopping for PUSCH with N_sb > 1

- Predefined inter-subframe frequency hopping for PUSCH with N_sb > 1

 

22

 

Off

- UTRAN measurements and reporting in E-UTRA connected mode

 

23

Off

- GERAN measurements and reporting in E-UTRA connected mode

 

24

 

Off

- cdma2000 measurements and reporting in E-UTRA connected mode

 

25

On

- Inter-frequency measurements and reporting in E-UTRA connected mode

 

26

Off

Undefined

 

27

Off

Undefined

 

28

Off

Undefined

 

29

Off

Undefined

 

30

Off

Undefined

 

31

Off

Undefined

 

32

off

Undefined

 

-- Thanks & Best Regards Olina Lee At 2010-08-29 03:00:02ㄛwireshark-dev-request@wireshark.org wrote: >Send Wireshark-dev mailing list submissions to > wireshark-dev@wireshark.org > >To subscribe or unsubscribe via the World Wide Web, visit > https://wireshark.org/mailman/listinfo/wireshark-dev >or, via email, send a message with subject or body 'help' to > wireshark-dev-request@wireshark.org > >You can reach the person managing the list at > wireshark-dev-owner@wireshark.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Wireshark-dev digest..." > > >Today's Topics: > > 1. buildbot failure in Wireshark 1.2 on Windows-XP-x86 > (buildbot-no-reply@wireshark.org) > 2. wireshark dissect (??) > 3. Re: wireshark dissect (Anders Broman) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Fri, 27 Aug 2010 17:32:58 -0700 >From: buildbot-no-reply@wireshark.org >Subject: [Wireshark-dev] buildbot failure in Wireshark 1.2 on > Windows-XP-x86 >To: wireshark-dev@wireshark.org >Message-ID: <20100828003258.935FB544B6@thump.wireshark.org> >Content-Type: text/plain > >The Buildbot has detected a new failure of Windows-XP-x86 on Wireshark 1.2. >Full details are available at: > http://buildbot.wireshark.org/trunk-1.2/builders/Windows-XP-x86/builds/37 > >Buildbot URL: http://buildbot.wireshark.org/trunk-1.2/ > >Buildslave for this Build: windows-xp-x86 > >Build Reason: >Build Source Stamp: 33975 >Blamelist: gerald > >BUILD FAILED: failed nmake setup > >sincerely, > -The Buildbot > > > >------------------------------ > >Message: 2 >Date: Sat, 28 Aug 2010 17:47:45 +0800 (CST) >From: ?? <olinalee@126.com> >Subject: [Wireshark-dev] wireshark dissect >To: wireshark-dev@wireshark.org >Message-ID: <154df0c.ec99.12ab8187989.Coremail.olinalee@126.com> >Content-Type: text/plain; charset="gbk" > > >hello, >I need to dissect every bit of feature group indicator of packet-. But the dissect_per_bit_string can't disset this feild. Can you tell me how to dissect this? > > >-- > > >Thanks & Best Regards > > > >Olina Lee > > >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: http://www.wireshark.org/lists/wireshark-dev/attachments/20100828/b31fd7a9/attachment.html > >------------------------------ > >Message: 3 >Date: Sat, 28 Aug 2010 15:04:27 +0200 >From: Anders Broman <a.broman@telia.com> >Subject: Re: [Wireshark-dev] wireshark dissect >To: Developer support list for Wireshark <wireshark-dev@wireshark.org> >Message-ID: <4C79095B.4090405@telia.com> >Content-Type: text/plain; charset="x-gbk" > > ???? skrev 2010-08-28 11:47: >> >> hello, >> I need to dissect every bit of feature group indicator of packet-. But >> the dissect_per_bit_string can't disset this feild. Can you tell me >> how to dissect this? >> >You need to be a bit more verbose :-) >Which protocol? what protocol entity(IE)? From the brief description >above I'm assuming that something in the protocol ASN1description is >defined as a PER bitstring then there is some verbal >description or a reference on how this bitstring should be interpreted. >If that's the case you would have to add code in the .cnf file (assuming >this is a protocol dissector generated by asn2wrs) >to extract the bitstring and to dissect it. Adding a feature request to >bugzilla describing the problem and with a example trace might get some >one to pick it up and implement it. >Regards >Anders >> -- >> >> Thanks & Best Regards >> >> * * >> >> */Olina Lee/* >> >> >> >> ------------------------------------------------------------------------ >> ?????????????????????????????? <http://mail.163.com/?from=fe1> >> >> >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list<wireshark-dev@wireshark.org> >> Archives: http://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe > >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: http://www.wireshark.org/lists/wireshark-dev/attachments/20100828/42ddc0a0/attachment.htm > >------------------------------ > >_______________________________________________ >Wireshark-dev mailing list >Wireshark-dev@wireshark.org >https://wireshark.org/mailman/listinfo/wireshark-dev > > >End of Wireshark-dev Digest, Vol 51, Issue 39 >*********************************************

___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe