Talk:Generic Stream Encapsulation/Temp

From Wikipedia, the free encyclopedia
Jump to: navigation, search


Generic Stream Encapsulation, or GSE for short, is a Data link layer protocol defined by DVB. GSE provides means to carry packet oriented protocols, like for example IP, on top of uni-directional physical layers like e.g. DVB-S2, DVB-T2, DVB-C2, DVB-NGH.

GSE provides additional features beyond the pure carriage of IP datagrams that increase the protocol flexibility and applicability. Some key GSE functions/characteristics are:

Protocol Outline[edit]

Diagram of GSE encapsulation and fragmentation
How GSE carries datagrams and is carried in the physical layer

The protocol specification has been published as DVB BlueBook A116-1[1]. A logical link control protocol specification has been published as DVB BlueBook A116-2[2]. A robust header compression specification has been published as DVB BlueBook A116-3[3]. An accompanying implementation guidelines document has been published as ETSI TS 102 771.[4]

IP datagrams, Ethernet Frames, or other network layer packets are encapsulated in one or more GSE Packets. The encapsulation process adds control information such as the network protocol type and address label, and provides an overall integrity check when needed.

The payload frame may be encapsulated in a single GSE Packet or sliced into fragments and encapsulated in several GSE Packets. GSE Packets have in general variable length, in order to match the input IP traffic with minimum overhead.

GSE Packets may be sent in different Base Band frames, not necessarily consecutive or with the same transmission parameters (modulation format, coding rate). No constraint on the GSE Packet position within the Base Band frame is assumed. However, GSE Packets may not be reordered between the encapsulator and the de-encapsulator. In general, a Base Band frame can contain more than a single GSE Packet. Base Band frames may have fixed, or variable length.

GSE does not provide a mechanism for integrity check of single GSE Packet. A CRC-32 is only appended to the last fragment of a fragmented payload to verify the correctness of the reassembly operation. GSE relies on the physical layer being able to ensure the required error detection and/or correction probability.[5]

GSE Header[edit]

The GSE Packet header is highly dynamic and provides for many options. The minimum header is two bytes, comprising three flags fields, and a 12-bit payload length field. The diagram below shows all possible fields.

Unrolled GSE Header
bit offset 0 1 2-3 4–7 8-15 16-23 24-31
0 Start End Label Type GSE Length Fragment ID Total Length
32 Total Length Protocol Type Label (3 Byte)
64 Label (3 Byte) Label (6 Byte)
96 Label (6 Byte) ULE Extension Headers (Optional)
... ... Data
...  
Data
 

Fragmentation and Reassembly[edit]

The basic mechanism of GSE payload fragmentation uses the Start and End Flags, where the Start flag indicates the beginning of a payload frame, and the End flag indicates its end. This is shown in the diagram below.

Fragmentation Principle
Start End GSE Packet Content
1 0 Total payload size / Protocol type / Payload start
0 0 Payload continuation
0 1 Payload end / CRC-32

On DVB-S2, DVB-T2, DVB-C2, and DVB-NGH the ACM/VCM modes may cause the Base Band frames to vary in size depending on the transmission conditions. Hence there may be situations where the first fragments of a payload frame have been sent, but the encapsulator is forced to set aside the current payload frame, and start working on a new one. This may e.g. occur when large fragments have been prepared while transmission conditions were fine, but suddenly the conditions deteriorate, and only small Base Band frames are available.

This is when the Fragment ID field becomes important. It is a short-term identification of the payload frame. Whenever the encapsulator needs to move on to the next payload frame, without having finished transmitting the previous one, it uses the next available Fragment ID. That way, up to 256 payload frames can be "kept open" at any time. The decapsulator uses the Fragment ID to pick the reassembly buffer in which to store the fragment.

GSE Addresses[edit]

The "Label Type" (LT) bits determine how the GSE packet address is encoded according to the following table:

Addressing Mode
LT bits Addressing mode
00 Indicates that a 6 bytes label is present and shall be used for filtering.
01 Indicates that a 3 bytes label is present and shall be used for filtering.
10 No label present. All receivers shall process this packet.
11 Label re-use: no label is present; the label is the same as the previous GSE packet in the same base band frame. LT=11 shall not be used for the first GSE packet in a base band frame.

GSE Packet Types[edit]

Since the not all combinations of the Start and End Flags, and the Label Type yield useful GSE packets, the GSE protocol specification[1] defines five distinct GSE packet types. These are the only packet types allowed in GSE streams.

GSE Packet Types
Packet type Start End Label type
Padding 0 0 00
Intermediate 0 0 11
Start 1 0 see Addressing Mode
End 0 1 11
Complete 1 1 see Addressing Mode

CRC-32 Trailer[edit]

Each GSE Packet containing the last fragment for a payload frame, carries a CRC-32 checksum over the payload frame. The checksum is used to detect loss of intermediate fragments.

The checksum is a 32 bit value calculated according to the generator polynomial represented by 0x104C11DB7:

If the last fragment of a paylod frame is lost, the decapsulator can not directly detect that fact. It never sees the GSE frame with the End flag set and containing the CRC-32. For this situation, the decapsulator must choose a suitable time-out based on the data-rate and application.

Logical Link Control[edit]

With the protocol specification[1] alone, GSE only provides a transparent pipe which delivers higher layer protocol frames. The protocol type field in the GSE header provides some basic information about those frames. It may convey either an EtherType[6] value, or an ULE next header[7] value.

From the protocol type field, a receiving host can infer which higher layer protocol is used (for example IPv4 or IPv6), but it does not yet know which services are available on this link. On a traditional data network, a host would use some sort of service discovery mechanism, like for example DNS Service Discovery (DNS-SD) a component of Zero Configuration Networking, Dynamic Host Configuration Protocol (DHCP), or Simple Service Discovery Protocol (SSDP) a component of Universal Plug and Play (UPnP).

DVB-GSE was however conceived for use over uni-directional broadcast bearers. In such an environment, the host operates the GSE link in a receive-only mode, and can hence not actively request any further information. Instead, it has to wait for any such information being multicast or broadcast on the link. Since the receiving host does not even know which service discovery mechanisms are supported on each GSE link, it has to listen on all potential Service Access Points (SAP) for all the service discovery mechanisms on all available GSE links. As every RF channel can carry one or more GSE streams, hundreds of GSE links can potentially available to a receiving host. Retuning the radio receiver unit to each of them in turn, and listening to all possible service announcements is not practical. Therefore, DVB have defined a logical link control protocol.

Processing flow of GSE streams in an OS kernel

The GSE LLC logical link control protocol uses a protocol type value registered in the IANA ULE Next-Header Registry[7] as DVB-GSE_LLC. The stream of LLC packets can therefore easily be filtered out from the arriving packets, before the remaining packets are forwarded to other kernel modules or user space.

This enables virtual network interfaces to be instantiated, each representing one of the potentially receivable GSE streams. This allows application developers to simply connect to the transport service access points they wish to, and the underlying operating system and platform will be able to choose the correct interface, and configure the hardware accordingly.

As the GSE LLC protocol also conveys modulation information about the RF channels (frequencies, etc.), and network information about the protocols (IP addresses, etc.) transported over GSE, sets of RF and network parameters can be associated with transport service access points, and upon receiving a request for a particular transport service access point from user space, the device driver and IP stack can directly be provided with the correct RF and network parameters for the connection.


Network Control Data[edit]

Link Control Data[edit]

Robust Header Compression for IP[edit]

robust header compression

[8]

[9]

[10]

[11]

Bidirectional Interface Emulation[edit]

[12]

GSE Implementations[edit]

Products Supporting GSE[edit]

Since GSE packets are directly inserted into base-band frames of the modulation scheme, GSE products come in the form of "GSE Routers" or "GSE Modems", which - from the outside - act very much like a DSL Router or DSL Modem used by consumers. More generically these devices are also referred to as "GSE Encapsulators". These products have a standard IP network interface (most often Ethernet or a similar LAN interface) to collect IP traffic which is to be forwarded over the uni-directional link on the other end. To optimise the packaging into base-band frames, these devices typically generate complete base-band frames with the GSE packets as payload, which are then transferred to the DVB-S2, DVB-T2, DVB-C2, or DVB-NGH modulator through a second interface.

Here is a (very likely incomplete) list of GSE en- and decapsulators:

GSE-based IP Service Offerings[edit]

There are many IP-over-satellite service offerings, including for instance ASTRA2Connect from SES or Tooway from Eutelsat. Little detail is however known about the protocols used since the receivers are provided as part of the service by the operators and very little technical detail is disclosed.

References[edit]

  1. ^ a b c DVB BlueBook A116-1: "Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE); Part 1: Protocol"
  2. ^ DVB BlueBook A116-2: "Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE); Part 2: Logical Link Control (LLC)"
  3. ^ DVB BlueBook A116-3: "Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE); Part 3: Robust Header Compression (ROHC) for IP"
  4. ^ ETSI TS 102 771: "Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) implementation guidelines"
  5. ^ IETF RFC 3819: "Advice for Internet Subnetwork Designers"
  6. ^ IEEE EtherType registry
  7. ^ a b IANA Unidirectional Lightweight Encapsulation (ULE) Next-Header Registry
  8. ^ IETF RFC 5795: "The RObust Header Compression (ROHC) Framework"
  9. ^ IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed"
  10. ^ IETF RFC 4815: "RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095"
  11. ^ IETF RFC 3843: "RObust Header Compression (ROHC): A Compression Profile for IP"
  12. ^ IETF RFC 3077: "A Link-Layer Tunneling Mechanism for Unidirectional Links"

External links[edit]

Category:Link protocols