STF 473 – Progress Report for ETSI
Presented to ETSI meeting
SESSatEC#25 Online
10-Jul-2014
10-Jul-2014
Doc ref
Author:
Date:
Version
Matteo Berioli
3-Jul-2014
1
page 1 of 2
STF
473
STF leader
Matteo Berioli
TB/WG
SES SatEC
TB responsible
Alice De Casanove
STF Assistant
Thierry Comont
STF title:
Alert Message Encapsulation
Milestone
Objective
Status
B
Covers the period
until (cut-off date)
03-Jul-2014
Progress Report#2 referring of completion of Tasks 1.1, 1.2 and 1.3 and progress of Tasks
1.4 and 1.5 approved by SatEC#25 (3 July 2014).
Achieved
Objective achieved
Remarks
Achieved dates
Template
Draft report
TB approval
ETSI approval
Sent to EC
EC approval
12-Jun-2014
3-Jul-2014
10-Jul-2014
n.a.
n.a.
n.a.
1
Executive summary
The main goals of this Milestone were to clarify the basic and fundamental features of the MAMES
encapsulation protocol, and to formally define a list of technical requirements that the protocol should fulfil
to achieve its design objectives. All these activities were, in the opinion of the STF, successfully
performed. The STF has also defined some operational scenarios of the protocol, together with some
implementation examples of practical interest, in order to facilitate the implementation and the
understanding of the protocol functional architecture.
The progress of the work reflects the foreseen Work Plan. So, in the opinion of the STF, the contractual
Milestone B has been achieved and its targets have been fully met:
- Task 1.1 and 1.2 had already been closed with the achievement of Milestone A;
- to prove the completion of Task 1.3, the STF has prepared and submitted to the SatEC Working
Group (WG) two documents that address all issues of this task;
- the progress of Tasks 1.4 and 1.5 (that have just started in June 2014) is considered satisfactory
with respect to the time schedule, the activities performed in these two tasks are described in two
additional documents submitted to the WG.
The progress of the work seems also satisfactory with respect to the current targets and future contractual
milestones; so there is no need to update the Work Plan and the milestone schedule, the current STF
Work Plan and schedule can be confirmed. The STF sees no need for additional resources to complete
the work or for shift of budget. There were no changes in the STF team, and there are no changes
planned in the future.
2
Introduction
The STF has performed an extensive analysis and finally defined a list of technical requirements for the
protocol. The STF has also clarified the important and fundamental features of the encapsulation protocol
by classifying all of its possible use cases in a set of operational scenarios; this allowed specifying the
protocol functional architecture. Some implementation examples of practical interest, one per operational
scenario, were also identified, in order to facilitate the understanding of the use of the protocol and its
future implementation.
3
Contractual milestone
Four draft documents, in addition to the present report, were distributed to the ETSI SES/SatEC WG in
preparation of its meeting. They represent the outcomes of the following three running tasks of the project:
 Task 1.3 – Functional Architecture (document SESSatEC(14)000017): This document describes
the MAMES functional architecture and highlights operational cases in which the MAMES protocol
is supposed to work; the terminology and the definitions used in the MAMES context are also
formalized here.
 Task 1.3 (document SESSatEC(14)000018): In this document high-level requirements, derived
from existing standards, on protocols operating for alert systems are listed, and their relevance for
MAMES is discussed and clarified; the objectives and the desired capabilities of the protocol are
identified; these objectives, capabilities and high-level requirements are analysed and combined
to arrive at a consistent and complete set of formal MAMES requirements; MAMES requirements
are divided into general functional requirements, requirements on the MAMES Alerter-Side Agent,
and requirements on the MAMES User-Side Agent.
 Task 1.4 (document SESSatEC(14)000019): This document presents a preliminary MAMES
message structure definition to be considered and discussed by the WG.
 Task 1.5 (document SESSatEC(14)000020): This document preliminarily discusses the scope of
the Transport and Message Enhancers, and some candidate solutions for these enhancers,
including techniques for acknowledging messages at MAMES level.
With the preparation of the documents above, Task 1.3 can be considered closed. The progress of Tasks
1.4 and 1.5 is considered satisfactory with respect to the time schedule. This reflects the foreseen Work
Plan. So, in the opinion of the STF, the contractual Milestone B has been achieved and its targets have
been fully met.
4
Progress of the work
The progress of the work seems satisfactory with respect to the current Work Plan targets and future
contractual milestones. There is no need to update the Work Plan and milestone schedule.
5
Assessment of technical risk, difficulties encountered/expected, unresolved
issues
The difficulties encountered by the STF are mainly of technical nature. The approach selected by the STF
to hold regular on-line meetings, every 1-2 weeks, is giving good results; these frequent short rendezvous
meetings allow frequent interactions among the experts and more iterations of the technical analysis. This
proved to be, so far, a good practice to face internal debates and to solve technical problems. The
distribution of the tasks among the three experts is not creating conflicts at the moment. Some of the
working days, originally planned for July and August 2014, have been anticipated to May and June, to
avoid delays due to the summer break. For this reason, the workload observed on the STF leader was still
a bit higher than expected, but within reasonable levels. No recovery action is proposed for the moment.
One critical issue that has been identified very early by the STF (already in the Preparatory Meeting) is the
collection of the In-Kind (IK) contribution. The amount of IK-days required by the European Commission
(300) seems quite high for the volume of this STF and if compared to the size of the SatEC WG. For this
reason, the STF has performed, from its first working day, a careful planning of the events to advertise its
activity, and has started immediately attending events to collect signatures for the IK contribution. At the
moment, it is not sure that the goal of the 300 IK days can be achieved, in spite of the effort dedicated by
the STF to this, so this remains a critical point. A possible solution to the problem is to organize a
dedicated workshop at ETSI premises, where selected stakeholders can be invited, to present them the
current standardization activity.
6
Proposed changes in the STF work plan
The current STF Work Plan and schedule can be confirmed.
7
Resources requirements
No need for additional resources to complete the work or for shift of budget is expected at the moment.
8
Changes in the STF Team
There were no changes in the STF team, and there are no changes expected in the future.
9
Meetings/events attended on behalf of the STF
The STF experts participated to four working meetings, as listed in the table below:
- the PSCE Forum Conference is one of the regular events organized by the PSCE Forum; during
this event a collaborative/interactive session was organized by the STF472 and two presentations
about the activities of the two STFs (472 and 473) were given; signatures for the in-kind
contribution were also collected (more information can be found in the table below).
- the Progress Meeting 2 (PM2) was an ad-hoc on-line meeting that was suggested and organized by
the STF to clarify with the WG some technical issues that were important for the progress of the
work; the STF presented to the steering committee the status the STF work, in particular with
respect to the definition of the MAMES technical requirements; a document was prepared by the
STF to prepare the meeting (see link in the table below) and important hints were received from
the WG, they are noted in the document pointed by the link in the table below.
- the HF Workshop was a public event, in the form of a 2-days small conference, organized by the
ETSI Human Factor technical body; an STF expert was invited to participate to the panel session
and to give a short presentation about accessibility issues in alerting systems (e.g. how to
efficiently reach, in emergency situations, foreigners, elderly, or impaired people with warning
messages).
- the EMTEL#30 meeting was a venue where the STF had the possibility to advertise its activity, and
to receive important feedback; the STF had already established a contact with the EMTEL group
at the EMTEL#29 meeting, and in this new meeting J. Rammer gave EMTEL an update on the
STF activity; two presentations were given, one for STF473 and one for STF472; signatures for
the in-kind contribution were also collected (see link in the table below); four delegates were
attending the EMTEL#30 meeting from remote (via telephone conference), so even if their time
cannot be accounted as in-kind contribution, this shows a high interest of EMTEL members for the
STF work.
Date
Place
Event description
20-21/05/2014
Gothenburg
SW
PSCE (Public Safety
Communication Europe)
Forum Conference
23/05/2014
On-line
Progress Meeting 2 with
the SatEC WG
03-04/06/2014
Sophia
Antipolis FR
Human Factor
Workshop
(HF)
Reason to attend and other
notes
Informative/Dissemination
Meeting
documents:
STF472 Workarea
Update to the WG
from
Cruickshank,
Bovim
(STF472)
All
Meeting document: here
Informative/Dissemination
Meeting
documents
Mission Report): here
Participants
Rammer
(incl.
04-05/06/2014
Sophia
Antipolis FR
EMTEL#30
Informative/Dissemination
Rammer
Meeting documents: on the
EMTEL portal and here
Two more events were also exploited for dissemination, even if the STF did not attend them with experts:
the EENA Conference and the Euroalarm General Assembly. More details about them are given in sec.
11.
10 Meetings/events planned to be attended
The following table provide the list of meetings/events that are planned to be attended on behalf of the
STF (date/place, description, reason to attend).
Date
Place
Event description
Participants
SatEC#26
Reason to attend
(and other notes)
Informative/Dissemination:
A special session is being
organized,
with
presentations both from
STF472 and STF473.
A paper on MAMES has
been prepared by the STF
and submitted to the
conference.
Report to WG
08-10/09/2014
Livorno IT
ASMS conference
11-12/09/2014
Florence IT
14-15/10/2014
Sopron HU
EMTEL#31
Informative/Dissemination
Rammer
25-26/11/2014
Paris FR
Informative/Dissemination
(attendance
to
be
coordinated with STF472)
tbc
16-18/12/2014
PSCE Conference:
http://www.psceurope.eu/index.php?id
=426
SES#86
Sophia
Antipolis FR
Kristiansand, ISCRAM2015:
Norway
http://iscram2015.uia.no/
Informative/Dissemination
tbc
Informative/Dissemination;
The possibility to organize
a conference track could be
taken
into
account
(deadline for proposal Aug.
1st, see here).
tbc
24-27/05/2015
Berioli
all
11 STF communications, presentations, promotion, inside and outside ETSI,
WEB pages etc
The STF473 webpage (see http://portal.etsi.org/STFs/STF_HomePages/STF473/STF473.asp) was
published on the ETSI website.
In addition to the events listed above in sec. 9, the STF had the possibility to advertise its activity at two
important international events: the EENA Conference and the Euroalarm General Assembly.
EENA (http://www.eena.org/) is the European Emergency Number Association, an NGO set up in 1999 to
promote high-quality emergency services reached by the number 112 throughout the EU. EENA serves as
a discussion platform to improve the emergency response and to support the establishment of an efficient
system for alerting citizens. EENA Conference takes place every year. The EENA Conference 2014 was
held on 2-4 April 2014, in Warsaw (Poland); it brought together over 400 key stakeholders (emergency
services, public authorities and industry representatives), who showcased best practices. This year
conference outcomes, presentations, videos and pictures, were published on the EENA website (see
here). On day 2, Track 2, Peter Sanders (vice-chair of ETSI EMTEL) gave an interesting talk on “Next
Generation Public Warning from a standardization point of view”, he also mentioned the activities of the
ETSI SatEC STF473 and STF472 (the presentation can be found at the link above). Although the STF
was not physically present with an expert and didn’t collect in-kind contribution signatures, this was for
sure a very important dissemination event to key players in the field.
Euralarm represents the electronic fire and security industry at European and worldwide fora, providing
technical and market expertise for policy making and standardization work. The main fields of activity are:
fire detection and alarms, intrusion detection and alarm systems, access control, video surveillance, alarm
transmission and alarm receiving centers. Founded in 1970 it represents over 2500 companies having a
total turnover of appr. 16.4 Billion Euro, 70% of the total European Fire Safety & Security market.
Members include national associations in 17 countries as well as individual companies. Euralarm held its
annual General Assembly on May 13th 2014 in Juan les Pins (France) (see press release here). During
this event, DLR was invited to give a talk about the recently closed EU project Alert4All
(http://www.alert4all.eu/). The Alert4All project was also working on an encapsulation protocol for alerting
systems, and its outcomes are planned to be carefully considered in MAMES. In the presentation given to
Euroalarm (see here, esp. slide 11), DLR advertised the activity of the ETSI STF473 and promoted the
participation of Euroalarm members to ETSI. So, although the STF was not physically attending the
Euroalarm General Assembly 2014, this can also be considered a very important dissemination event for
the STF.
12 Technical advice required from the reference Technical Body
During Task 1.3 several technical issues were discussed, also with the WG, on the MAMES scope and
capabilities; these aspects were fundamental for the requirement definition of the protocol. The WG
should check that the outcomes of this discussion reflect the original expectations and design objectives
of the WG; anyway on this part no major deviations are expected.
The STF has also proceeded with Tasks 1.4 and 1.5, proposing some approaches to translate the
technical requirements into design principles for the MAMES header and message format. The WG is
asked to have a look at the preliminary results produced in these two tasks and provide feedback to the
STF.
13 Status of the deliverables
The Work Plan did not foresee the preparation of any draft Deliverable. According to the Terms of
Reference, parts of the documents prepared by the STF (see sec. 3 above) will be used later in the ETSI
TS (Technical Specification) and in the ETSI TR (Technical Recommendation); for this reason all material
produced by the STF has been prepared according to ETSI document templates, so that future integration
of this material into the deliverables should be easier. These documents can be also found here:
http://docbox.etsi.org/STF/STF473_SatEC_MAMES/STFworkarea/DraftDeliverables/.
14 Next report
The next report (Milestone C, Interim Report #3) is scheduled for: September 12th, 2014.
15 Any other business
None.