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 4 and 10 (spanning 6 versions)
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
Revision 10 as of 2009-05-20 06:50:53
Size: 2702
Editor: GuyHarris
Comment: Link to the 3GPP page on the first reference. Clean up 3GPP external links.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:

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 [[http://www.3gpp.org/ftp/Specs/html-info/25427.htm|3GPP TS 25.427]] (Dedicated transport channels) and [[http://www.3gpp.org/ftp/Specs/html-info/25435.htm|3GPP TS 25.435]] (Common transport channels).
Line 7: Line 6:

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]
These transport channel formats are described in R99, R4, R5, R6 and R7 releases of the above documents. There is no FP layer in 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]]). There is what looks like a place-holder specification for the dedicated channels shown for R8.
Line 12: Line 9:

* FP can be transported over AAL2, AAL0 or ["UDP"]
 * FP can be transported over AAL2, AAL0 or [[UDP]]
Line 16: Line 12:
Here is an example of HSDPA (type 2, introduced in R7) traffic.
Line 17: Line 14:
XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot). {{attachment:fp-example.jpg}}
Line 20: Line 17:

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 24: Line 20:
Line 28: Line 23:
Line 31: Line 25:
 * attachment:SampleCaptures/PROTO.pcap  * [[attachment:SampleCaptures/PROTO.pcap]]
Line 34: Line 28:
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] 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]]
Line 36: Line 30:
 Show only the FP based traffic: {{{
 fp }}}
 . Show only the FP based traffic:
{{{
 fp
}}}
Line 40: Line 36:

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.
Line 44: Line 39:

* [http://www.3gpp.org/ftp/Specs/html-info/25427.htm] ''3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub/Iur interface user plane protocol for DCH data streams''
 * [http://www.3gpp.org/ftp/Specs/html-info/25435.htm] ''3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub Interface User Plane Protocols for Common Transport Channel data streams''
 * [[http://www.3gpp.org/ftp/Specs/html-info/25427.htm|3GPP TS 25.427]] ''3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub/Iur interface user plane protocol for DCH data streams''
 * [[http://www.3gpp.org/ftp/Specs/html-info/25435.htm|3GPP TS 25.435]] ''3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub Interface User Plane Protocols for Common Transport Channel data streams''
Line 50: Line 43:
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 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 LTE (Long Term Evolution) because the MAC/RLC/PDCP entities now terminate in the eNodeB (see Evolved UTRA aspects). There is what looks like a place-holder specification for the dedicated channels shown for R8.

Protocol dependencies

  • FP can be transported over AAL2, AAL0 or UDP

Example traffic

Here is an example of HSDPA (type 2, introduced in R7) traffic.

fp-example.jpg

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.

Display Filter

A complete list of FP display filter fields can be found in the 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.

  • 3GPP TS 25.427 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub/Iur interface user plane protocol for DCH data streams

  • 3GPP TS 25.435 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iub Interface User Plane Protocols for Common Transport Channel data streams

Discussion

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