Hackathon Framework

From MECwiki
Revision as of 13:09, 18 December 2017 by Carignani (talk | contribs) (Created page with "= Introduction = This contribution discusses the background assumptions for the organization of MEC Hackathons. The document describes guidelines, general framework for propo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

This contribution discusses the background assumptions for the organization of MEC Hackathons. The document describes guidelines, general framework for proposers and hosts, by clarifying also the role of ETSI MEC ISG and ETSI CTI.

Motivation

In order to increase and accelerate the adoption of MEC, in Phase 2 ETSI ISG MEC still continues engaging the ecosystem, and encourage all stakeholders to use MEC work to develop edge applications. One of the means to reach this goal is the organization of MEC Hackathons.

Definition

Terminology

For MEC Hackathons, the following entities are defined:

Theme means generic theme in area of technical theme e.g. in case of Health, it could be Future Hospitals.

Technical Theme usually refers to vertical area e.g. AR/VR, Health, V2X, Industry, but can also refer to a technical focus area defined by ETSI ISG MEC e.g. CRAN.

Target Venue Venue for which the application or service is created. This could be museum, airport, stadium etc.

Technology Vendor Partner a party that provides the target platform for the development.

Service Provider Partner a party that provides the connectivity & networking services e.g. operator, enterprise.

Target Venue Partner a party that aims to host the service or application developed in the hackathon e.g. in case of museum, this could be a specific and well-known museum.

Organization Partner the hackathon can be sponsored by number of organizations. These can be ETSI, other SDO or any regional, government or global other organization.

Host host of the event selected by agreement of the attending parties.