opensand team mailing list archive

[Dubois Emmanuel <Emmanuel.Dubois@xxxxxxx>]

Hello,
I have updated the wiki to work on definition of each probes and events.
               http://opensand.org/support/wiki/doku.php?id=design:probes_and_events
I have added some columns that can be useful to precise each element.

I have added some questions in the wiki

People who know the historic and precise meaning of the probe can update the wiki.
It can be useful

Thanks and good we.

Emmanuel

--------------------------------
Emmanuel DUBOIS
CNES Network and Telecom Engineer
Batiment Lagrange Bureau S28
Tel (33) 5 61 28 19 81 - Fax : (33) 5 61 28 26 13 - mail : emmanuel.dubois@xxxxxxx<mailto:emmanuel.dubois@xxxxxxx>

De : opensand-bounces+emmanuel.dubois=cnes.fr@xxxxxxxxxxxxxxxxxxx [mailto:opensand-bounces+emmanuel.dubois=cnes.fr@xxxxxxxxxxxxxxxxxxx] De la part de Fabrice HOBAYA
Envoyé : mardi 11 septembre 2012 18:15
À : Vincent DUVERT; opensand@xxxxxxxxxxxxxxxxxxx
Objet : Re: [Opensand] New environment plane: Defined probes and events

Le 11/09/2012 12:03, Vincent Duvert a écrit :


Hello all,





Thus, we are requesting feedback on which probes and events should go

into the OpenSAND platform alongside with the new environment plane.



Regards,

Vincent Duvert



Hi all,

   As a user of the OpenSAND platform, here are few comments.

*** Regarding GW probes

- CRA_st_allocation: since it is specific to a terminal, I think it should be classified in the ST probes.
- RBDC_st_allocation: same thing.
- RBDC_MAX_st_allocation: same thing.

- I think the VBDC allocation per terminal (VBDC_st_allocation) could be useful and should be classified in the ST probes.
- I think the FCA allocation per terminal (FCA_st_allocation) could be useful and should be classified in the ST probes.

- I think the VBDC max (VBDC_MAX_allocation) allocation and the VBDC max allocation per terminal (VBDC_MAX_st_allocation) could be useful.

__________________________
*** Regarding SAT probes

- In the case of a regenerative system, it could be useful to have the total uplink rate, the per terminal uplink rates, the total downlink rate and the per terminal downlink rate.

________________________
*** Regarding ST probes

- The outcoming/incoming throughputs should be renamed with more explicit names. I suggest the generic naming:
direction_layer_throughput
with direction={reception/emission}
with layer={L3, L2, L1}
that means:
emission_L3_throughput: throughput for traffic transmitted by the ST on the satellite link including layer 3 header and data (that is upper layer headers and data).
emission_L2_throughput: throughput for traffic transmitted by the ST on the satellite link including layer 2 header and data (that is upper layer headers and data).
emission_L1_throughput: throughput for traffic transmitted by the ST on the satellite link including layer 1 header and data (that is upper layer headers and data).
reception_L3_throughput: throughput for traffic received by the ST from the satellite link including layer 3 header and data (that is upper layer headers and data).
reception_L2_throughput: throughput for traffic received by the ST from the satellite link including layer 2 header and data (that is upper layer headers and data).
reception_L1_throughput: throughput for traffic received by the ST from the satellite link including layer 1 header and data (that is upper layer headers and data).

- CRA: is this one redundant with CRA_st_allocation ?

Regards,
Fabrice.


--

Fabrice HOBAYA

PhD - Réseaux, Télécommunications, Systèmes et Architectures

Ingénieur d'études Viveris Technologies

1 Avenue de l'Europe - Parc technologique du Canal -

Bat C - 1er étage - 31400 Toulouse - France

fabrice.hobaya@xxxxxxxxxxxxxxxxxxxx<mailto:fabrice.hobaya@xxxxxxxxxxxxxxxxxxxx>