
)*+,,*
-./
!
))0+)01++,
=!
)(+
42!
**0
STLF-NA-TRD-REQ-1050 Each set of QoS parameters shall be described through:
Uplink: Guaranteed minimum Data Rate in kb/s for permanent connections
Uplink: Guaranteed minimum on-demand Data Rate in kb/s
Uplink: No guaranteed maximum on-demand Data Rate in kb/s
Security parameters
T
STLF_IF_NONREG_MESH
STLF_IF_NONREG_STAR
STLF_IF_MGMT_RCSTNEW
STLF_IF_RCST_QOS
-
STLF-NA-TRD-REQ-1060 The SatLife System shall support up to 7 different traffic classes. T NERA: by design
STLF_IF_NONREG_MESH
STLF_IF_MGMT_RCSTNEW
STLF_IF_NONREG_STAR
STLF_IF_RCST_QOS (there up to 20
flow type entries, and a maximum of 3
priority levels)
-
STLF-NA-TRD-REQ-1070 The RCST shall be able to classify the incoming IP packets into different
classes of services depending on several criteria, as indicated in the RCST
MIB:
IP packet header parameters (IP source and destination address,
DSCP/TOS, protocol type, TCP/UDP source and destination ports number)
Transport layer protocol parameters
Application layer protocol parameters
T NERA:Test 1.2.19 QoS filter
configuration via SNMP
NERA: Test 1.2.20 Qos filter
configuration via CLI
STLF_IF_RCST_QOS (there up to 20
flow type entries, and a maximum of 3
priority levels)
-
STLF-NA-TRD-REQ-1080 The SatLife system shall implement a Satellite Adaptation Layer (SAL) to
map the IP flows onto access layer. The layer should include the following
functionality:
Queueing
Traffic policing / shaping
Congestion control
Marking
Traffic engineering
T NERA: Test_1.2.15 Terminal packet
dropping. Masking connections. Traffic
engineering.
STLF_IF_RCST_QOS
-
STLF-NA-TRD-REQ-1090 The SatLife system shall be able to modify the DSCP field of incoming IP
packets headers which are already marked with a valid DSCP value (as
defined in the Service Level Agreement).
NA DSCP marking not supported -
Komentarze do niniejszej Instrukcji