Encapsulation requirements for return links and mesh systems over satellite

F Hobaya, C Baudoin, E Dubois, P Gélard, E Chaput, A L Beylot, G Fairhurst

Research output: Chapter in Book/Report/Conference proceedingPublished conference contribution

1 Citation (Scopus)

Abstract

Initially designed for TV broadcasting, DVB standard families have become mature technologies for Internet communications via satellite access networks. A generic encapsulation protocol is therefore required for the forward link, the return link, and for mesh satellite systems. Moreover, because of the cost and the scarcity of resources, this should be as efficient and light as possible. The GSE (Generic Stream Encapsulation) protocol enables efficient transport of any protocol, originally designed for DVB-S2, that is to say on Quasi Error Free (QEF) forward links of satellite systems. This paper addresses limitations in GSE for the return link context and examines the requirements for an encapsulation mechanism for satellite systems using multiple access. This includes the return link but also mesh satellite systems and any satellite systems that uses multiple access. This paper also analyses approaches to derive requirements and provides a first analysis of these requirements.
Original languageEnglish
Title of host publicationVehicular Technology Conference Fall (VTC 2010-Fall), 2010 IEEE 72nd
PublisherInstitute of Electrical and Electronics Engineers (IEEE)
Pages1-5
Number of pages5
ISBN (Electronic)978-1-4244-3574-6
ISBN (Print)978-1-4244-3573-9
DOIs
Publication statusPublished - 4 Oct 2010
EventVTC - Mobile Satellite and Positioning Systems Conference - Ottawa, Canada
Duration: 6 Sept 201010 Sept 2010

Conference

ConferenceVTC - Mobile Satellite and Positioning Systems Conference
Country/TerritoryCanada
CityOttawa
Period6/09/1010/09/10

Keywords

  • RLE
  • DVB-RCS
  • mesh VSAT

Fingerprint

Dive into the research topics of 'Encapsulation requirements for return links and mesh systems over satellite'. Together they form a unique fingerprint.

Cite this