#  Data summary

_The template is a set of questions that you should answer with a level of
detail appropriate to the project._

_**It is not required to provide detailed answers to all the questions in the
first version of the DMP that needs to be submitted by month 6 of the
project.** Rather, the DMP is intended to be a living document in which
information can be made available on a finer level of granularity through
updates as the implementation of the project progresses and when significant
changes occur. Therefore, **DMPs should have a clear version number and
include a timetable for updates.** As a minimum, the DMP should be updated in
the context of the periodic evaluation/assessment of the project. If there are
no other periodic reviews envisaged within the grant agreement, an update
needs to be made in time for the final review at the latest. _

The Data Management Plan (DMP) describes the management life cycle for the
data to be collected, processed and generated by this Horizon 2020 project,
5G-Xcast. This DMP represents a first version of the final document. It is
intended to be updated, making it available on a finer level of granularity
through updates as the implementation of the project progresses and when
significant changes occur. The DMP will be updated in the context of the
periodic evaluation of the project. The next updates are planned to be
submitted to the official project website:

_Table 1. Timetable for updates of the data management plan._  
  
<table>  
<tr>  
<th>

**Version**

</th>  
<th>

**Date**

</th> </tr>  
<tr>  
<td>

First version

</td>  
<td>

M3

</td> </tr>  
<tr>  
<td>

Revision for first periodic evaluation

</td>  
<td>

M12

</td> </tr>  
<tr>  
<td>

Revision for final evaluation

</td>  
<td>

M23

</td> </tr> </table>

##  Purpose of data collection

_What is the purpose of the data collection/generation and its relation to the
objectives of the project?_

Throughout the project, partners of the consortium will naturally generate
data in the form of results and presentations whilst carrying out research
activities related to respective project objectives. The collection and
sharing of this information within the project is essential to allow the
effective coordination of research tasks among the task contributors. Data
will be shared internally through an internal repository, accessible only to
project partners.

In addition to the internal data sharing activities, a series of public
deliverables and presentations are planned for open publication. This will
make the more key research discoveries available to the wider research
community and industry, including other 5GPPP phase-2 projects. 5G-Xcast will
coordinate with other 5G projects related to broadcast and media to maximize
the exploitation of findings. This includes sharing project deliverables and
exploring possible exchange of results with other projects; i.e. where
appropriate, 5G-Xcast results could be used in other projects and vice versa.

The sharing of and building upon knowledge is the foundation of research and
discovery. The project will ensure the technical and scientific relevance of
the results as well as promote the image of the consortium by supervision of
the look & feel quality of its output. The 5G-Xcast project aims at providing
its main results and ideas through the official website. This public website
will be also the central hub for the dissemination activities.

Open access to scientific publications will be ensured by publishing submitted
paper in compliance with IEEE rules. A periodic newsletter will include
information on the latest achievements of the project and links to recent
public deliverables and forthcoming events.

##  Types of data

_What types and formats of data will the project generate/collect?_

During the project, different types and formats of **open access** data will
be generated and collected to be shared in the public website of the project:

  * **Deliverables** : during the project, a series of confidential and public open Deliverables (D) will be developed related to specific tasks. All documents will be shared with 5G-PPP projects for inter-project cooperation. Public deliverables will be released to the open public. To monitor the work progress of the tasks, a first draft version will be released several months before the last and final version. 

  

  * **Presentations** : main presentations summarising global results of the different working packages (WP) will be shared as well through the official website of the project. Organisation of workshops will be proposed to relevant conferences. In order to have the maximum impact, the presentations made in these events will be also accessible to the open public. 

  

  * **Results:** during the project, specific results are expected to be shared. Examples of these results would be Matlab data files, coverage maps in terms of signal strength level, or some information about field trials such as Global Position System (GPS) position, signal level, interference, etc. 

  

  * **Standardization technical contributions** from project partners will be also shared in the official webpage. Examples of standardization forums are 3GPP or DVB. 

  

Currently, project members do not expect to make public any code related to
simulation platforms or specific tools. All types of data mentioned above will
be also shared internally among the members of the consortium throughout the
drafting phase. By making use of the EBU repository and email lists dedicated
to this purpose, project partners can collaborate, jointly building the
deliverables with shared access to all data. In addition, project partners
will share **privately** (allowing access to project partners) other types of
data, in order to ensure that the objectives of the project are fulfilled:

  * **Software:** during the project, some simulation platforms and software tools will be shared among the partners. Different repositories will be used, depending on the nature of the simulation tool. For instance, a common air interface simulator will be developed among several partners by making use of the Git system. Git is a free and open source distributed version control system designed to handle very large projects with speed and efficiency. 

  

  * **Preliminary results** in the form of presentations, spreadsheets, figures, etc., will be shared among partners through the internal repository. 

  

  * **Preliminary research ideas** presented in teleconferences will be shared among partners through the internal repository as well. 

  

  * **Standardization technical documents:** partners submitting contributions to standards developing organisations (SDOs) will make the contribution public if the SDOs documents are public (for example 3GPP). For others SDOs that have documents restricted to members (for examples DVB) partners will check with the chairman and aim to make the documents public whenever possible. 

  

##  Re-use of existing data

_Will you re-use any existing data and how? What is the origin of the existing
data?_

5G-Xcast will make use of existing data developed and validated by partners
outside the framework of this project. Public specifications coming from DTT
(Digital Terrestrial Television) committees such as DVB (Digital Video
Broadcasting) or ATSC (Advanced Television Systems Committee), as well as 3GPP
(3rd Generation Partnership Project ) technical specifications (TS) and
technical reports (TR), will be used as starting point for the further
development of required data.

5G-Xcast will not develop technologies entirely from scratch; partners will
build upon concepts already developed in 3GPP and 5G-PPP phase-1 projects, for
unicast PTP transmissions. Baseline data such as simulators and tools based on
current specifications will be considered as a benchmark for the 5G-Xcast
technology solutions developed within the project.

Likewise, scientific journal and conference publications, technical reports,
white papers and workshops will be also considered for calibration and cross-
checking of the technological data deployed.

##  Expected size

_What is the expected size of the project data?_

The size of the data will depend on the outcomes of the project research
tasks. The 5GXcast project is expected to provide:

  * At least one presentation per WP summarizing the main findings of the work. 

  

  * Specific results such as field trials, figures or data files. 

  

  * Several specification technical contributions. 

  

  * Eight confidential deliverables . 

  

  * Nineteen open deliverables. 

  

  * Several videos about demonstrations and showcases could be produced and release. This could be one or more of the following events: 

    * Demonstration in International Broadcasting Convention (IBC), in 2018 o Demonstration in either the Mobile World Congress (MWC) o Demonstration at the European Conference on Networks and Communications (EuCNC), in 2019. 

  

    * Showcase at the European Championships of 2018. 

  

  

  * Dissemination activities: 

    * 40 journal papers, whitepapers and conference papers. o 10 filed patents. o 15 standard contributions. o 10 keynotes and panels. 

  

    * 10 participations in 5G or broadcast events and forums. o 8 workshops in major IEEE conferences. o 4 summer schools/trainings. 

  

  

##  Data utility

_To whom might it be useful ('data utility')?_

5G-Xcast data will be available for the Research and Development industry, the
European creative media industry and the telecom industry. The project will
facilitate the exploitation of the outcomes into future products and services
and provides good knowledge for faster deployment of 5G networks in Europe. In
addition, the different types of data facilitated will be useful not only to
the industry, but also to universities, research institutes, scientific
magazines and specialised press. Concerning the press, contacts will be
established with the relevant trade press in order to extend the utility and
reach of communication activities.

#  Findable, accessible, interoperable and re-usable (FAIR) data

##  Making data findable, including provisions for metadata

_Are the data produced and/or used in the project discoverable with metadata,
identifiable and locatable by means of a standard identification mechanism
(e.g. persistent and unique identifiers such as Digital Object Identifiers)?_

Internally, documents (presentations, figures, deliverables, etc.) will use a
specific format for tracking all internal sharing per WP, within the project
internal repository.

Externally, several metadata tracking methods will be used, depending on the
type of data. Publications derived from the projects will follow the DOI
(Digital Object Identifiers) mechanisms already established in the scientific
research community. These publications will also include keyword metadata as
well as descriptive titling. As such, these will become indexed and searchable
by any academic or research search tool (including IEEEXplore, Research Gate,
as well as most public search engines such as Google, Bing, etc.).

Patents follow a well-established form of description via metadata as well as
possessing unique identifiers, which vary depending on country filed and
patent type. Once again searchable via patent indexing services and most
search engines.

_What naming conventions do you follow? Do you provide clear version numbers?_

The naming conventions are explained in deliverable D1.1[2] and are summarized
below. Deliverables have unique IDs and always are presented with their full
title. This will make them accessible via search engines and easily through
the project website.

Project partners will also use an internal versioning following naming
convention. The nomenclature fixed throughout the 5G-Xcast project is as
follows:

  1. Working documents in the repository will have names _**5G-Xcast_DZ.T_ Draft_vX.Y.docx** for the draft version. Once the document is reviewed and ready to be released, the document will be made available to the EC and in the project website and the naming will be changed. _

  

  2. Final versions Deliverables have name _**5G-Xcast_DZ.T_Title_vX.Y.docx** _ , where _DZ.T_ denotes the deliverable number and _vX.Y_ is the version number. 

     * Version numbering shall only arrive at _v_ 1.0 once the document is ready to be sent to the EC. 

  

     * Different versions may be differentiated by using _v_ 0\. _Y_ with _Y_ being integer numbers between 0 and 9. 

  

     * The version being transmitted to the EC will be labelled _v_ 1\. If the EC requests modifications, the updated version will be labelled _v_ 2\. The intermediate versions will be labelled _v_ 1.1, _v_ 1.2, etc. 

  

  

  3. Internal documents will be stored in the repository and might be used as a basis for public deliverables. Internal documents of WP will also have the following names: **5G-Xcast_WPn_Title_VX.Y.ext** (the extension ext depends on the type of document) 

  

  4. For the case of the **Quarterly Reports (QR)** , the nomenclature will be: 

     * Partner QR will be named _**5G-Xcast_QRY_Partner.docx** _ where _Partner_ is the acronym of the project partner and Y is the quarter number (for example, _5GXcast_QR1_UPV.docx_ ). 

  

     * A WP quarterly report will be prepared by the WP leader and should be named 

  

  

  

_**5G-Xcast_WPX_QRY.docx** _ , where _X_ is the WP number ( _for example,
5GXcast_WP1_QR3.docx_ ).

  * Quarterly Management Reports (QMR) will be prepared by the project manager and should be named _**5G-Xcast_QMRY.docx** _ . 

  

  5. For journals, articles, conference papers, standard contributions the naming standard is as follows: _** <Event>_<yyyy>_<Authors>_<Title> ** _

     * _ <Event> _ : indicates the journal, conference, standardization body (e.g. VTC, IEEECommMag, 3GPP, etc.) 

  

     * _ <yyyy> _ : Year of the publication 

  

     * _ <Authors> _ : indicates the first three letters of the last name of the author(s). In case of several authors, only the first three letters of the last name of the main author will be indicated, appending ‘ _etal_ ’. 

  

     * _ <Title> _ : indicates the title of the document. Only two meaningful words indicating the contents of the document will be used. Titles will be kept shorter than 10 letters by using abbreviations. 

  

  

  

_Will search keywords be provided that optimize possibilities for re-use?_

Keywords are also provided in all public deliverables to optimize
possibilities for re-use.

##  Making data openly accessible

_Which data produced and/or used in the project will be made openly available
as the default? If certain datasets cannot be shared (or need to be shared
under restrictions), explain why, clearly separating legal and contractual
reasons from voluntary restrictions._ As a result of the 5G-Xcast project,
many results will be generated and produced in order to fulfil the objectives
and tasks planned. Some of the results produced will be shared (or shared
under certain restrictions) to the open public. Currently, particular data
results to be shared are not defined. The specific results to be released from
each project partner will be specified in future versions of this document.
Open deliverables produced and used within the project will be made openly
available as the default as well.

The closed data due to legal and contractual reasons will not be shared. This
specific type of data that may have a very sensitive commercial/technological
value to some partners will be shared only to the level and the number of
partners required for the execution of the specific project tasks, such as
demonstrations and showcases.

_How will the data be made accessible (e.g. by deposition in a repository)?_

The collection and sharing of information within the project is essential to
allow the effective coordination of research tasks among the task
contributors. Data will be shared internally through a workspace powered by
the European Broadcasting Union (EBU), current partner of the project
consortium. Data will be only accessible to project partners. The 5G-Xcast
project will also provide its main results, thoughts and ideas by making use
of the official project website (  _http://5g-xcast.eu/_ )  . The website is
open and accessible to the general public.

In order to ensure the largest possible exposure of the project, different
social media and networking tools are used (LinkedIn and Twitter). A YouTube
channel is used as well to capture presentations from e.g. industry forum
demonstrations, workshops, and test-bed trials.

_What methods or software tools are needed to access the data?_

Specific software tools will be required for the correct access to the data
generated. Open deliverables and presentations (dissemination activities,
workshops, WP summaries, etc.) will be uploaded using the Portable Document
Format (PDF). Microsoft Office or equivalents will also be required as a basic
tool to open DOC, XLS and PPT documents.

_Is documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?_

Currently, there is no information about software to be shared or published in
the website. The same applies to documentation related to tests and field
trials. In the future as field trials become more specific partners may wish
to share some of the data. This will be updated in upcoming version.

_Where will the data and associated metadata, documentation and code be
deposited? Preference should be given to certified repositories which support
open access where possible._

Open access data, associated metadata and documentation will be deposited in
the File Download Area of the official project website (
_http://5g-xcast.eu/documents/_ )  . Internally, all data and associated
metadata will be deposited in the repository folder created for the associated
work package.

_Have you explored appropriate arrangements with the identified repository?_

All project partners and contributors fulfil the appropriate arrangements with
the internal repository. Note that this repository is implemented within a
workspace that belongs to a consortium member, i.e. the European Broadcasting
Union. This repository is a customised implementation of the Atlassian
Confluence software. For more information, please see
_https://www.atlassian.com/software/confluence_ .

_If there are restrictions on use, how will access be provided? How will the
identity of the person accessing the data be ascertained?_

Individual member registration is required to access the internal repository
and ascertain the identity of the person accessing the data. Although anyone
can sign up as new user, specific content such as the 5G-Xcast project
repository is restricted to member organizations and individual partners.

On the other hand, no registration is required to visit the different tags or
access the data provided in the project webpage. Documents are open and
accessible to the general public without any restriction.

##  Making data interoperable

_Are the data produced in the project interoperable, that is allowing data
exchange and re-use between researchers, institutions, organisations,
countries, etc. (i.e. adhering to standards for formats, as much as possible
compliant with available (open) software applications, and in particular
facilitating re-combinations with different datasets from different origins)?_

Data produced in the project will be interoperable. The project will allow to
the extent possible data exchange and re-use of published results between open
public i.e. individual researchers, institutions, organisations, etc.

All reports, deliverables and public presentations will be presented (or where
not able, translations provided) in English. Final versions of such documents
will also be provided in PDF format, offering wide support and readability on
a wide range of devices and platforms with many free and open source readers
available. Where this is not possible, the project will endeavour to provide
data in formats which are open, widely accepted and are accessible to the
wider public through open source utilities.

##  Increase data re-use

_How will the data be licensed to permit the widest re-use possible?_

Public project outputs such as public deliverables, papers, presentations and
project results will be available on the project website and can be reused by
other projects.

Some of the contributions of the project will also be available in different
standard developing organisations (SDOs). Some of these organisations allow
open access to the general public (such 3GPP) while some other allow access
only to members (Such DVB, IEEE). An indirect access to some of project
results will be possible via these standard and technical organisations.
However, specific rules apply for each organisation (E.g. 3GPP allows access
to results but they cannot be reproduced / used without permission) Specific
confidential material will require direct licensing from the originating
company.

_How long is it intended that the data remains re-usable?_

Data produced within the 5G-Xcast framework and openly published in the
website will be useable by third parties, during and after the end of the
project. On use, there is a requirement for appropriate attribution back to
the 5G-Xcast project. Any modifications to the original data or results must
be indicated clearly. Data will remain accessible for as long as the project
website is kept open. Data obtained will remain useable indefinitely.

_When will the data be made available for re-use? If an embargo is sought to
give time to publish or seek patents, specify why and how long this will
apply, bearing in mind that research data should be made available as soon as
possible._

Note that this DMP represents a first version of the document, released on M3
of the project. Therefore, information about embargos or when the data will be
available for reuse is still unknown. This information will be specified in
future versions of the deliverable.

_Are data quality assurance processes described?_

The data quality including all the review process and risk mitigation for all
project outputs is described in the project proposal [1] and project
guidelines [2] documents.

#  Allocation of resources

_What are the costs for making data FAIR in your project?_

The project has as entire Work Package, WP7, dedicated to dissemination,
standardisation and exploitation of the data and research produced within the
project. This acts as a focused resource in which a key responsibility is
ensuring data is findable, accessible, interoperable and reusable.

WP7 Objectives:

  1. Promote the project, its objectives, results and the concepts developed. 

  

  2. Influence standardisation bodies to adopt the concepts developed in 5G-Xcast. 

  

  3. Coordinate with other 5G European projects for maximum synergy. 

  

  4. Build awareness on the use of broadcast with its different applications and how 5G-Xcast helps in this regards. 

  

  5. Maximize the exploitation of the project results by consortium members. 

  

  6. Maximize the innovation impact of the project. 

  

  

To best achieve this, WP7 will work closely with all other WP leaders to
ensure key research output and accompanying insights are shared to a wider
audience, promoting the project, expanding knowledge in the field and
promoting further research in the field of 5G broadcast.

WP7 has resources dedicated throughout the project, starting in month 1 and
ending in month 24. In total this forms 69 Person Months of the total project
budget and a minimum of 1 person months have been assigned to each project
partner (with most partners getting 2 or more). The full breakdown is provided
in Table 2. This allows for time by each partner to be dedicated to
interfacing with the external world and making their research available to the
wider academic, scientific and industrial community. This encourages
establishing and continuation of communication with different parties, making
data available through the public project website, maximising scientific
visibility through publication in major conferences and high impact journals
(IEEE etc).

_Table 2. WP7 Resource Allocation per Participant_  
  
<table>  
<tr>  
<th>

**Participant number**

</th>  
<th>

1

</th>  
<th>

2/3

</th>  
<th>

4

</th>  
<th>

5

</th>  
<th>

6

</th>  
<th>

7

</th>  
<th>

8

</th>  
<th>

9

</th>  
<th>

10

</th>  
<th>

11

</th>  
<th>

12

</th>  
<th>

13

</th>  
<th>

14

</th>  
<th>

15

</th>  
<th>

16

</th>  
<th>

17

</th>  
<th>

18

</th> </tr>  
<tr>  
<td>

**Short name of participant**

</td>  
<td>

UPV

</td>  
<td>

NOK

</td>  
<td>

BBC

</td>  
<td>

BT

</td>  
<td>

BPK

</td>  
<td>

BLB

</td>  
<td>

EXP

</td>  
<td>

FS

</td>  
<td>

IRT

</td>  
<td>

LU

</td>  
<td>

NOM

</td>  
<td>

O2M

</td>  
<td>

SEUK

</td>  
<td>

TIM

</td>  
<td>

TUAS

</td>  
<td>

EBU

</td>  
<td>

UNIS

</td> </tr>  
<tr>  
<td>

**Person months per participant:**

</td>  
<td>

12

</td>  
<td>

8

</td>  
<td>

1

</td>  
<td>

2

</td>  
<td>

2

</td>  
<td>

2

</td>  
<td>

3

</td>  
<td>

4

</td>  
<td>

2

</td>  
<td>

3

</td>  
<td>

4

</td>  
<td>

1

</td>  
<td>

13

</td>  
<td>

2

</td>  
<td>

2

</td>  
<td>

6

</td>  
<td>

2

</td> </tr> </table>

Note that apart from this, some additional costs may be covered in this WP,
e.g. website costs. However, additional costs will depend on the data and
results shared during and after the project.

_Who will be responsible for data management in your project?_

The person responsible for data management within the 5G-Xcast project will be
Dr Belkacem Mouhouche, from Samsung Electronics R&D UK (SEUK). Dr Mouhouche is
the Innovation Manager of the project, and leader of this WP7.

_Are the resources for long term preservation discussed (costs and potential
value, who decides and how what data will be kept and for how long)?_

Data is intended to be long-term preserved, after the end of the project.
Internal and confidential reports, as well as results, presentations and all
types of data are expected to be available in the EBU internal repository in a
static copy for at least 5 years.. UPV could keep the public website open for
a minimum of two years following the end date of the project. Note that this
is an early version of the DMP, and no commitment has been done in this
regard. More information will be given in future versions of this deliverable.

#  Data security

_What provisions are in place for data security (including data recovery as
well as secure storage and transfer of sensitive data)?_

##  Shared project data

The sharing of all non-public data within the project is carried out through a
team collaboration platform provided by the EBU. Access to the platform
requires each individual to generate a personal username and password.
Passwords are encrypted and only known to the individual herself/himself, i.e.
neither the EBU nor the platform provider has access to passwords. Each
individual must then be associated to the project space by the EBU
administrators in agreement with the project management team. Only once this
association has been made is access to the project space enabled to the user.
The platform provided by the EBU is part of the company information
infrastructure and is protected by the state-of-the-art security systems. It
employs enterprise strength encryption and an enterprise level backup plan
implemented in the event of system failure (i.e. daily back-up on the entire
content of the repository).

##  Data within each partner institution

The consortium is comprised of established and respected institutions, each of
which is expected to have measures in place to protect and preserve data, as
well as relevant policies to ensure compliance. Furthermore, each partner has
agreed to comply with the consortium agreement, requiring observation of
obligations under the EU data Protection Directive 95/46/EC [1]. For the
duration of the project, the data generated by each partner whilst carrying
out their respective research activities is subject to their own internal
measures of safety and security. Partners are requires to provide updates and
share the outcomes of this research on a regular basis through the project, at
which point documentation will be uploaded to the EBU collaboration platform
and be subject to the storage and security levels outlines above.