Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Performance Parameters

DTS/SES-00290

General Information

Status
Published
Publication Date
26-Nov-2009
Current Stage
12 - Completion
Due Date
04-Dec-2009
Completion Date
27-Nov-2009
Ref Project

Buy Standard

Standard
ETSI TS 102 673 V1.1.1 (2009-11) - Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Performance Parameters
English language
23 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 102 673 V1.1.1 (2009-11)
Technical Specification


Satellite Earth Stations and Systems (SES);
Broadband Satellite Multimedia (BSM);
Performance Parameters

---------------------- Page: 1 ----------------------
2 ETSI TS 102 673 V1.1.1 (2009-11)



Reference
DTS/SES-00290
Keywords
architecture, broadband, management
multimedia, performance, satellite
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 102 673 V1.1.1 (2009-11)
Contents
Intellectual Property Rights . 4
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Overview . . 9
5 BSM Performance Parameters Context . 9
5.1 BSM SI-SAP performance parameters . 10
5.2 BSM IP performance parameters . 11
6 BSM SI-SAP Performance Parameters . 12
6.1 Introduction . 12
6.2 Number of active QIDs [N ] . 13
QID
6.3 List of QIDs [QID ] . 13
i
6.4 Available Data Rate [R ] . 13
ava
6.5 List of IP flows associated to a QID [IP(QID )] . 14
i
6.6 List of SD queues associated to a QID [SD(QID )] . 14
i
6.7 Time [t ] and type [m ] of last QID modification . 14
mod QID
6.8 Transmission Delay [D ] . 14
T
6.9 Maximum Hardware Delay [D ] . 15
hw
6.10 Rate [R] . 16
6.11 Slack Term [S] . 16
6.12 Traffic Pattern [r, b, p, m, M] . 16
7 BSM IP Performance Parameters . 17
7.1 Measuring BSM IP Performance Parameters . 17
7.2 IP packet metrics . 19
7.2.1 IP Packet Transfer Delay (IPTD) . 19
7.2.1.1 Mean IP Packet Transfer Delay . 19
7.2.2 IP Packet Delay Variation (IPDV) . 19
7.2.3 IP Packet Loss Ratio (IPLR) . 19
7.2.4 IP Packet Error Ratio (IPER) . 19
7.2.5 Spurious IP Packet Rate (SIPR) . 20
7.2.6 IP Packet Reordered Ratio (IPRR) . 20
7.3 IP Flow Metrics . 20
7.3.1 IP Packet Throughput (IPPT). 20
7.3.2 IP Packet Goodput (IPPG) . 20
7.4 IP Service Availability (IPSA) . 20
7.5 Summary . 21
Annex A (informative): BSM IP performance objectives . 22
History . 23

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 673 V1.1.1 (2009-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and
Systems (SES).
Introduction
The present document is a consequence of the ETSI BSM report and recommendations on performance, availability and
quality of service detailed in [i.1]. It was deemed to be important to have an own document about performance
parameters even if this was not foreseen in [i.1].
BSM networks may be stand-alone domains, serving IP end-hosts located behind satellite terminals, but may often be
connected to external terrestrial segments. Users of BSM networks require their applications to run satisfactorily over
the whole end-to-end path, and thus over the satellite links, as well as over the traversed terrestrial segments. The
performance of the user applications can be derived by the network performance levels provided by the underlying
networks traversed by the end-to-end path, and since the terrestrial segments connected to the BSM networks, often
provide measurable network performance levels, it is fundamental to specify network performance levels for the BSM
systems in the same way as for terrestrial networks. In addition a network whose performance is not measurable cannot
sell its services, thus the performance levels required from BSM networks need to be formalized in a set of performance
parameters that can be used to check fulfilment of contractual agreements.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 673 V1.1.1 (2009-11)
1 Scope
The present document defines performance parameters which will be used in BSM networks for the four functions
mentioned below, i.e. for measuring performance, monitoring, controlling and analysing BSM systems.
Performance management is meant by ITU as one of the five network management categories, FCAPS, as specified by
the ITU-T Recommendation M.3400 [i.4]. So, adopting the ITU terminology, the present document focuses on
"Performance Parameters" as meant by the ITU and so all parameters relevant for the four remaining network
management categories (Fault management, Configuration management, Accounting management and Security
management) will not be considered here. ITU-T Recommendation M.3400 [i.4] also defines performance management
as consisting of the following functions:
• Performance Quality Assurance.
• Performance Monitoring.
• Performance Management Control.
• Performance Analysis.
These parameters can be used, for example, by a BSM network manager to establish QoS levels for a given service, and
monitor the "health" of the BSM, or to "present" the performance of the BSM network in order to assess compliancy to
some contractual agreements. The parameters could be used as a basis for one or more MIBs.
According to TR 121 905 [i.23], "Network performance parameter values are usually derived from Quality of Service
(QoS) parameter values". Therefore BSM performance parameters will be derived from all QoS parameters relevant to
BSM networks, namely from the classical parameters for IP-based services, e.g. proposed by ITU [i.4], as well as from
more BSM-specific ones, coming from the definition of the BSM QoS architecture [1],[2] and [3].
Network performance parameters may be used for different purposes: they can be used only inside the BSM network or
can be exposed to BSM external interfaces; this will be also clarified in the present document. In the former case they
will refer to SI-SAP properties (e.g. related to Queue Identifier (QID)) and thus they are meant for BSM-internal use
only; in the latter case they can be presented by the satellite network operator to the outside world (e.g. external
terrestrial network operators connected to the BSM), e.g. to prove fulfilment of contractual agreements.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
For a specific reference, subsequent revisions do not apply.
Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 673 V1.1.1 (2009-11)
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 102 462: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia
(BSM); QoS Functional Architecture".
[2] ETSI TS 102 463: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia
(BSM); Interworking with IntServ QoS".
[3] ETSI TS 102 464: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia
(BSM); Interworking with DiffServ QoS".
[4] ETSI TS 102 672: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia
(BSM); Management Functional Architecture".
2.2 Informative references
The following referenced documents are not essential to the use of the ETSI deliverable but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TR 102 157: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia;
IP Interworking over satellite; Performance, Availability and Quality of Service".
[i.2] ITU-T Recommendation Y.1540 (former I.380): "Internet protocol data communication service -
IP Packet Transfer and Availability Performance Parameters", November 2007.
[i.3] ETSI TS 102 295: "Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia
(BSM) services and architectures; BSM Traffic Classes".
[i.4] ITU-T Recommendation. M.3400: "TMN management functions".
[i.5] ITU-T Recommendation Y.1541 (former I.381): "IP Performance and Availability Objectives and
Allocations", January 2001.
[i.6] ITU-T Recommendation M.2301: "Performance objectives and procedures for provisioning and
maintenance of IP-based networks", July 2002.
[i.7] IETF RFC 2330: "Framework for IP Performance Metrics".
[i.8] IETF RFC 2678: "IPPM Metrics for Measuring Connectivity".
[i.9] IETF RFC 2679: "A One-way Delay Metric for IPPM".
[i.10] IETF RFC 2680: "A One-way Packet Loss Metric for IPPM".
[i.11] IETF RFC 2681: "A Round-trip Delay Metric for IPPM".
[i.12] IETF RFC 3148: "A Framework for Defining Empirical Bulk Transfer Capacity Metrics".
[i.13] IETF RFC 3357: "One-way Loss Pattern Sample Metrics".
[i.14] IETF RFC 3393: "IP Packet Delay Variation Metric for IPPM".
[i.15] IETF RFC 4656: "A One-way Active Measurement Protocol (OWAMP)".
[i.16] IETF RFC 4737: "Packet Reordering Metrics".
[i.17] IETF RFC 5136: "Defining Network Capacity".
[i.18] IETF RFC 3418: "Management Information Base (MIB) for the Simple Network Management
Protocol (SNMP)".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 673 V1.1.1 (2009-11)
[i.19] IETF RFC 3917: "Requirements for IP Flow Information Export (IPFIX)".
[i.20] IETF RFC 5101: "Specification of the IP Flow Information Export (IPFIX) Protocol for the
Exchange of IP Traffic Flow Information".
[i.21] IETF RFC 5102: "Information Model for IP Flow Information Export".
[i.22] IETF RFC 5153: "IPFIX Implementation Guidelines".
[i.23] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR
21.905)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Destination host (DST): host and a complete IP address where end-to-end IP packets are terminated
NOTE: In general a host may have more than one IP address; however, a destination host is a unique association
with a single IP address. Destination hosts also terminate higher layer protocols (e.g. TCP) when such
protocols are implemented (taken from [i.2]).
link: point-to-point (physical or virtual) connection used for transporting IP packets between a pair of hosts. It does not
include any parts of the hosts or any other hosts; it operates below the IP layer
NOTE: For example, a link could be a leased line, or it could be implemented as a logical connection over an
Ethernet, a frame relay network, an ATM network, or any other network technology that functions below
the IP layer (taken from [i.2]); in the BSM case the whole satellite connection from the ingress ST to the
egress ST can be defined as a link, if the satellite or the hub, connecting the two STs, do not implement
the IP layer.
host: computer that communicates using the Internet protocols
NOTE: A host implements routing functions (i.e. it operates at the IP layer) and may implement additional
functions including higher layer protocols (e.g. TCP in a source or destination host) and lower layer
protocols (e.g. Ethernet) (taken from [i.2]). An ST is a particular host which does not implement higher
layer protocols.
Measurement Point (MP): boundary between a host and an adjacent link at which performance reference events can
be observed and measured (taken from [i.2])
NOTE: In general one Measurement Point (MP) for the performance parameters considered in a BSM network
(also defined BSM MP) always coincides with one unique unicast IP address; so, where the SI-SAP is
implemented (e.g. in an ST or in the hub), it also coincides with the unicast BSM_ID. Standard IP
properties can be observed at BSM MPs, as well as SI-SAP specific properties, which are more related to
SD events.
Network Control Centre (NCC): equipment at OSI Layer 2 that controls the access of terminals to a satellite network,
including element management and resource management functionality
Network Performance (NP): ability of a network or network portion to provide the functions related to
communications between users; it contributes to service accessibility, service retainability and service integrity
NOTE: Network performance parameter values are usually derived from quality of service (QoS) parameter
values (taken from TR 121 905 [i.23]).
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 673 V1.1.1 (2009-11)
Network Section (NS): set of hosts together with all of their interconnecting links that together provide a part of the IP
service between a SRC and a DST, and are under a single (or collaborative) jurisdictional responsibility
NOTE: These hosts typically have the same network identifier in their IP addresses. Typically, they have their
own rules for internal routing. Global processes and local policies dictate the routing choices to
destinations outside of this network section. These network sections are typically bounded by routers that
implement the IP exterior gateway protocols (taken from [i.2]). The BSM network is a particular Network
Section.
population of interest: total set of packets transmitted between one (or more) ingress ST(s) and one (or more) egress
ST(s), which are object of measurement
NOTE: The description of the population of interest, in any statement about measured performance, should
normally include associated QoS information, namely which packet type(s) are included in the
population, since performance will differ by packet type.
packet transfer reference event: event occurring when a packet crosses a measurement point (MP), so when it enters
or leaves an IP level, normally crossing the SI-SAP
router: host that enables communication between other hosts by forwarding IP packets based on the content of their IP
destination address field (taken from [i.2])
NOTE: In a BSM network the hub or the satellite may act as routers.
Source host (SRC): host and a complete IP address where end-to-end IP packets originate
NOTE: In general a host may have more than one IP address; however, a source host is a unique association with
a single IP address. Source hosts also originate higher layer protocols (e.g. TCP) when such protocols are
implemented (taken from [i.2]).
3.2 Abbreviations
For the purposes of the present document the following abbreviations apply:
BSM MP Measurement Point for the performance parameters considered in a BSM networks
BSM Broadband Satellite Multimedia
CRA Constant Rate Assignment
CRA Constant Rate Assignment
DST Destination host
DVB-RCS Digital Video Broadcasting Return Channel via Satellite
FCA Free Capacity Assignment
FCA Free Capacity Assignment
GPS Global Positioning System
ICMP Internet Control Message Protocol
IETF Internet Engineering Task Force
IP Internet Protocol
IPDV IP Packet Delay Variation
IPER IP Packet Error Ratio
IPFIX IP Flow Information Export
IPLR IP Packet Loss Ratio
IPPG IP Packet Goodput
IPPM IP Performance Metrics
IPPT IP Packet Throughput
IPRR IP Packet Reordered Ratio
IPSA IP Service Availability
IPTD IP Packet Transfer Delay
MIB Management Information Base
MP Measurement Point
NCC Network Control Centre
NMC Network Management Centre
NP Network Performance
NS Network Section
OSI Open Standards Institute
OWAMP One-Way Active Measurement Protocol
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 673 V1.1.1 (2009-11)
QID Queue IDentifier
QoS Quality of Service
RFC Request For Comments
RSCT DVB-RSC Terminal
RSCT DVB-RSC Terminal
RTT Round Trip Time
SD Satellite Dependent
SIPR Spurious IP Packet Rate
SI-SAP Satellite Independent-Service Access Point
SLA Service Level Agreement
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
SNR Signal-to-Noise Ratio
SRC Source host
ST Satellite Terminal
4 Overview
There are similarities between the ETSI, ITU and IETF definitions which allow us to decide that BSM performance
parameters will be derived mainly from QoS parameters, and in addition from other aspects needed to establish and
maintain BSM network operation.
The network layer (i.e. IP layer) parameters are considered to be independent of the BSM and to be well-known for
typical IP hosts. These are the parameters that may have to be presented by the BSM network operator to external
parties, they can be specified following ITU recommendation (e.g. [i.2]).
Instead there are other parameters, which will be specific to the BSM, they will be available at the SI-SAP and relate to
lower protocol layers; they will be used for BSM-internal use.
The parameters presented in the present document represent real-time measured properties of a selected BSM entity (an
ST or a QID); specification of numerical objectives or monitoring thresholds for these BSM performance parameters is
left to implementers and operators.
5 BSM Performance Parameters Context
The BSM performance parameters always refer to BSM elements (e.g. STs) or to portions of the BSM network.
Measurement Points (MPs) for these performance parameters (the BSM MPs) are in general associated to unique
unicast IP addresses: A BSM MP can be defined at every layer-2 service access point in an IP host belonging to a BSM
network (e.g. an ST, a hub, or even the satellite if it implements on-board routing). As a consequence BSM MPs
coincide with SI-SAPs, in the hosts where the SI-SAP is implemented. This means that standard IP properties can be
observed at BSM MPs, as well as SI-SAP specific properties, which are more related to SD events.
More formally a BSM MP is the boundary between a host and an adjacent satellite link at which performance reference
events can be observed and measured (taken from [i.2]). In general a BSM MP always coincides with one unique
unicast IP address; so, where the SI-SAP is implemented (e.g. in an ST or in the hub), it also coincides with the unicast
BSM_ID. Standard IP properties can be observed at BSM MPs, as well as SI-SAP specific properties, which are more
related to SD events.
Figure 5.1 shows the terminology to be used for BSM performance parameters according to the definitions given in
clause 3.1.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 673 V1.1.1 (2009-11)
BSM network section network section
SRC host ST Gateway Router DST host
(host) (host) (host)
TCP / UDP / TCP / UDP /
higher layers higher layers
IP IP interworking IP interworking IP IP
SI-SAP SI-SAP
OSI OSI SLC & SLC & OSI OSI
OSI OSI
SMAC
SMAC SMAC
Layers Layers Layers Layers Layers Layers
1-2 1-2 1-2 1-2
1-2 1-2
SPHY SPHY SPHY
link link
BSM link
BSM BSM MP
Measurement
Point (MP)

Figure 5.1: Terminology for BSM performance parameters
The BSM parameters can be classified in two groups, which are more clearly described in the next two clauses and
listed in detail in clauses 6 and 7 respectively:
• BSM SI-SAP parameters: They are specific to the BSM, i.e. will be available at the SI-SAP and relate to
lower protocol layers; they do not refer to IP-level performance, but to more specific properties of one
terminal, or of one service class being provided on one particular link.
• BSM IP parameters: They are the typical IP-layer parameters, defined in a way similar to ITU [i.2], but with
respect to a specific BSM section or a BSM link between two given devices (e.g. between two STs).
Considering this classification, each BSM MP may be interpreted as two virtual measurement points, one for QIDs (at
the SI-SAP), which is to be considered for BSM SI-SAP parameters, and which does not exist is the SI-SAP is not
implemented, and one for IP (immediately above the SI-SAP), which is to be considered for BSM IP parameters, and
which always exists. Anyway, since physically these two virtual MPs are co-located at the ST layer-2 service access
point, this distinction will not be done in the following.
5.1 BSM SI-SAP performance parameters
The BSM SI-SAP parameters are referred to a single MP, and can only be defined where the ingress (or transmitting)
SI-SAP is implemented, so they are referred to a single ingress SI-SAP (and thus equivalently to a single unicast
BSM_ID, being the source BSM_ID always the unicast BSM_ID of the ST). These parameters are not measured on a
network section but on an MP at the uplink ST.
These performance parameters describe some SD characteristics of the ST, so they are very BSM specific. They are
used for BSM internal purposes, in particular for the management of the QoS and of the QIDs [2] and [3], since in BSM
networks performance is usually directly linked to the characteristics of the satellite transmission (physical and link
layer) that directly affect the BSM capabilities to operate.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 673 V1.1.1 (2009-11)
For all parameters in this group the MP is any point in the BSM network where the SI-SAP interface is implemented,
so, in principle, at every ST. For this reason it is likely that they will be physically stored next to the "managed
element", and that in order to get th
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.