Members Area
depend.jpg15 Oct 2005: To ensure a higher level of interoperability across the DVB-RCS market, SatLabs invited ESA to initiate a process of definition for an Interoperable Performance Enhancement Proxy (I-PEP) solution. The I-PEP specification is based on the SCPS protocol as defined within CCSDS.
PEP implementations have become an integral part of today’s “Fast Internet via Satellite” systems and include functions such as compression, encryption and access control.

Currently the option for end users to select a mixture of DVB-RCS terminal products from multiple vendors is complicated due to the fact that additional services and functions need to be integrated in the terminal. These additional functions include PEP implementations, which encompass a server side (in the hub) and a client side (in the terminal). Because current PEP implementations define which client and server should be used together, additional requirements are placed on interoperability.

 Therefore, the aim was to define a suitable I-PEP protocol which, very similar to the DVB-RCS standard itself, would define the “air interface” and thereby the communication between hub-side and client-side PEP instances.

Implementations conforming to the I-PEP definition will allow the use of different PEP implementations on the client-side as well as on the hub-side and even allow the use of a complete mixture of different clients with different PEP implementations.
 This will provide end users with the freedom to select DVB-RCS equipment according to their project needs.

 The icon_pdf.gif  I-PEP Specification document (pdf, 455 kb) contains the definition of an Interoperable PEP and defines the basic procedures and protocol messages exchanged over the air interface between the satellite terminal and hub station. The current specification has been published in order to support initial implementations of the I-PEP. Interoperability tests can then be held and the specification consequently updated.