This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2006-09-14 16:38:18
Size: 2043
Editor: no-dns-yet
Comment: First content
Revision 4 as of 2007-08-24 23:13:14
Size: 2468
Editor: host81-151-5-222
Comment: typo + explanation of why removed from R8
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
These transport channel formats are described in R99, R4, R5, R6 and R7 releases of the above documents. These transport channel formats are described in R99, R4, R5, R6 and R7 releases of the above documents.  There appears to be no FP layer in R8 (aka LTE (Long Term Evolution )). Probably because the bearer will be IP.
[http://www.3gpp.org/ftp/Specs/html-info/36-series.htm Evolved UTRA aspects]
Line 20: Line 21:
The FP dissector is mostly functional, but can only be invoked at the moment while reading ["DCT2000"] format traces (these contain additional information needed in order to properly decode the frames). The FP dissector is mostly functional, but can only be invoked at the moment while reading Catapult ["DCT2000"] or Tektronix ["K12"] format traces (these contain additional information needed in order to properly decode the frames).
Line 49: Line 50:
I think the reason why there is no FP in LTE is that MAC/RLC/PDCP is no longer sent over a wired interface (they terminate in the eNODEB) whereas with IuB they would be send over ATM or IP/UDP - martinm

Frame Protocol (FP)

The Frame Protocol is the user plane protocol used in UTRAN IuB and IuR interfaces. It is described in 3GPP TS 25.427 (Dedicated transport channels) and 3GPP TS 25.435 (Common transport channels)

History

These transport channel formats are described in R99, R4, R5, R6 and R7 releases of the above documents. There appears to be no FP layer in R8 (aka LTE (Long Term Evolution )). Probably because the bearer will be IP. [http://www.3gpp.org/ftp/Specs/html-info/36-series.htm Evolved UTRA aspects]

Protocol dependencies

  • FP can be transported over AAL2, AAL0 or ["UDP"]

Example traffic

XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).

Wireshark

The FP dissector is mostly functional, but can only be invoked at the moment while reading Catapult ["DCT2000"] or Tektronix ["K12"] format traces (these contain additional information needed in order to properly decode the frames).

Preference Settings

There are currently no preference settings.

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

  • attachment:SampleCaptures/PROTO.pcap

Display Filter

A complete list of FP display filter fields can be found in the [http://www.wireshark.org/docs/dfref/f/fp.html display filter reference]

  • Show only the FP based traffic:

     fp 

Capture Filter

Because FP traces can only currently be read from existing trace files, there is no way to filter for FP frames while capturing.

Discussion

I think the reason why there is no FP in LTE is that MAC/RLC/PDCP is no longer sent over a wired interface (they terminate in the eNODEB) whereas with IuB they would be send over ATM or IP/UDP - martinm

FP (last edited 2009-05-20 06:50:53 by GuyHarris)