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 2 and 5 (spanning 3 versions)
Revision 2 as of 2007-08-20 15:33:07
Size: 2123
Editor: no-dns-yet
Comment: Mention K12 support
Revision 5 as of 2007-09-11 12:10:46
Size: 2482
Comment: Move Discussion item into History section
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
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) The Frame Protocol is the lowest-layer 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).
Line 8: Line 8:
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). These transport channel formats are described in R99, R4, R5, R6 and R7 releases of the above documents. There is no FP layer in R8 (aka LTE (Long Term Evolution )) because the MAC/RLC/PDCP entities now terminate in the eNodeB (see [http://www.3gpp.org/ftp/Specs/html-info/36-series.htm Evolved UTRA aspects]).
Line 20: Line 20:
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). The FP dissector is mostly functional, but can currently only be invoked while reading Catapult ["DCT2000"] or Tektronix ["K12"] format traces (these contain the additional information needed in order to properly decode the frames).  It would be possible, but challenging, to decode the RRC messages describing the configuration of the lower layers, and use this information to infer how each FP frame should be decoded.
Line 40: Line 40:
Because FP traces can only currently be read from existing trace files, there is no way to filter for FP frames while capturing. Because FP traces can currently only be read from existing trace files, there is no way to filter for FP frames while capturing.

Frame Protocol (FP)

The Frame Protocol is the lowest-layer 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 is no FP layer in R8 (aka LTE (Long Term Evolution )) because the MAC/RLC/PDCP entities now terminate in the eNodeB (see [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 currently only be invoked while reading Catapult ["DCT2000"] or Tektronix ["K12"] format traces (these contain the additional information needed in order to properly decode the frames). It would be possible, but challenging, to decode the RRC messages describing the configuration of the lower layers, and use this information to infer how each FP frame should be decoded.

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 currently only be read from existing trace files, there is no way to filter for FP frames while capturing.

Discussion

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