MECwiki - User contributions [en]

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2018-02-26T12:52:35Z

Mullers: /* PoC Team */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

Advantech

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

Paul Stevens, Advantech [mailto:paul.stevens@advantech.eu paul.stevens@advantech.eu]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based or a Virtual Machine (VM) environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000663r1_PoC_10_Service-Aware_MEC_Platform_to_Enable_Bandwidth_Manage.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2018-02-26T12:52:13Z

Mullers: /* Abstract */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

Paul Stevens, Advantech [mailto:paul.stevens@advantech.eu paul.stevens@advantech.eu]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based or a Virtual Machine (VM) environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000663r1_PoC_10_Service-Aware_MEC_Platform_to_Enable_Bandwidth_Manage.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2018-02-26T12:51:09Z

Mullers: /* PoC Proposal */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

Paul Stevens, Advantech [mailto:paul.stevens@advantech.eu paul.stevens@advantech.eu]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000663r1_PoC_10_Service-Aware_MEC_Platform_to_Enable_Bandwidth_Manage.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2018-02-26T12:50:00Z

Mullers: /* PoC Topics */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

Paul Stevens, Advantech [mailto:paul.stevens@advantech.eu paul.stevens@advantech.eu]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2018-02-26T12:49:21Z

Mullers: /* Main Contact */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

Paul Stevens, Advantech [mailto:paul.stevens@advantech.eu paul.stevens@advantech.eu]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:08:54Z

Mullers: /* PoC Report */

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''Traffic coordination between MEC and vehicles with simulated vehicle transportation scenario'', Feb 2018, MWC 2018, Barcelona

PoC Demo 2 – ''Enhancement and quantitative analysis on the traffic coordination with dynamic vehicle transportation scenario'', Sep 2018, Edge Computing Congress 2018, Berlin

== Abstract ==
Connected vehicles generate various data with different priorities and the transportation road congestion may give lead to mobile network congestion, which interfere with urgent V2X communication. In the PoC, we will demonstrate how to harmonize and prioritize network traffic sent for vehicles with MEC system by using MEC services in order to control the mobile network congestion.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000673r2_PoC_Proposal_on_Traffic_Management_for_V2X.doc Communication Traffic Management for V2X]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

[[PT04 MEC enabled vertical segments applications]]

== PoC Report ==
PoC Report is expected by Q4 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:08:28Z

Mullers: /* PoC Topics */

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:05:40Z

Mullers: /* PoC Topics */

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''Traffic coordination between MEC and vehicles with simulated vehicle transportation scenario'', Feb 2018, MWC 2018, Barcelona

PoC Demo 2 – ''Enhancement and quantitative analysis on the traffic coordination with dynamic vehicle transportation scenario'', Sep 2018, Edge Computing Congress 2018, Berlin

== Abstract ==
Connected vehicles generate various data with different priorities and the transportation road congestion may give lead to mobile network congestion, which interfere with urgent V2X communication. In the PoC, we will demonstrate how to harmonize and prioritize network traffic sent for vehicles with MEC system by using MEC services in order to control the mobile network congestion.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000673r2_PoC_Proposal_on_Traffic_Management_for_V2X.doc Communication Traffic Management for V2X]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

[[PT04 - PT04 MEC enabled vertical segments applications]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:04:16Z

Mullers: /* PoC Topics */

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''Traffic coordination between MEC and vehicles with simulated vehicle transportation scenario'', Feb 2018, MWC 2018, Barcelona

PoC Demo 2 – ''Enhancement and quantitative analysis on the traffic coordination with dynamic vehicle transportation scenario'', Sep 2018, Edge Computing Congress 2018, Berlin

== Abstract ==
Connected vehicles generate various data with different priorities and the transportation road congestion may give lead to mobile network congestion, which interfere with urgent V2X communication. In the PoC, we will demonstrate how to harmonize and prioritize network traffic sent for vehicles with MEC system by using MEC services in order to control the mobile network congestion.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000673r2_PoC_Proposal_on_Traffic_Management_for_V2X.doc Communication Traffic Management for V2X]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

[[PT04 - MEC enabled vertical segments applications]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:03:22Z

Mullers: /* PoC Proposal */

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:01:52Z

Mullers: /* Abstract */

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''Traffic coordination between MEC and vehicles with simulated vehicle transportation scenario'', Feb 2018, MWC 2018, Barcelona

PoC Demo 2 – ''Enhancement and quantitative analysis on the traffic coordination with dynamic vehicle transportation scenario'', Sep 2018, Edge Computing Congress 2018, Berlin

== Abstract ==
Connected vehicles generate various data with different priorities and the transportation road congestion may give lead to mobile network congestion, which interfere with urgent V2X communication. In the PoC, we will demonstrate how to harmonize and prioritize network traffic sent for vehicles with MEC system by using MEC services in order to control the mobile network congestion.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:00:50Z

Mullers: /* PoC Demo */

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''Traffic coordination between MEC and vehicles with simulated vehicle transportation scenario'', Feb 2018, MWC 2018, Barcelona

PoC Demo 2 – ''Enhancement and quantitative analysis on the traffic coordination with dynamic vehicle transportation scenario'', Sep 2018, Edge Computing Congress 2018, Berlin

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T09:00:01Z

Mullers:

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''PoC Demo1 - Traffic coordination between MEC and vehicles with simulated vehicle transportation scenario'', Feb 2018, MWC 2018, Barcelona

PoC Demo 2 – ''PoC Demo2 - Enhancement and quantitative analysis on the traffic coordination with dynamic vehicle transportation scenario'', Sep 2018, Edge Computing Congress 2018, Berlin

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 11 Communication Traffic Management for V2X

2018-02-09T08:57:35Z

Mullers: Created page with "== PoC Team == KDDI Corporation Saguna Networks Ltd. Hewlett Packard Enterprise == Main Contact == Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com] Lior Fite..."

== PoC Team ==
KDDI Corporation

Saguna Networks Ltd.

Hewlett Packard Enterprise

== Main Contact ==
Tomonobu Niwa, KDDI [mailto:to-niwa@kddi.com to-niwa@kddi.com]

Lior Fite, Saguna [mailto:lior@saguna.net lior@saguna.net]

Alex Reznik, HPE [mailto:alex.reznik@hpe.com alex.reznik@hpe.com]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

== PoC Report ==
PoC Report is expected by Q1 2018

Ongoing PoCs

2018-02-09T08:54:29Z

Mullers: /* List of PoCs */

==Overview of Reports==
<googlespreadsheet style="width:900px; height:400px" sheet="0" >1UUMWpAR6_elhU6DwoTqaDBgDNgV4hvtiSKkyHj4P-hM</googlespreadsheet>

==List of PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

'''[[PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN]]'''
Industry Technology Research Institute - Linker Network - FarEasTone

'''[[PoC 11 Communication Traffic Management for V2X]]'''
KDDI Corporation - Saguna Networks Ltd. - Hewlett Packard Enterprise

Ongoing PoCs

2018-02-09T08:53:54Z

Mullers: /* List of PoCs */

Main Page

2017-10-27T16:11:49Z

Mullers:

This Wiki is provided as a tool for the use of ISG MEC participants.
You may need to login to access some information

''' >>> ISG MEC participants can login with their ETSI OnLine (EOL) account <<<'''

If you are an ISG MEC participant and do not have an EOL account yet,
you can [http://webapp.etsi.org/createaccount apply for an EOL account], or send a request to [mailto:helpdesk@etsi.org ETSI helpdesk]

For any other wiki related request, please [mailto:CTI_support@etsi.org?Subject=ISG_MEC_WIKI_request contact ETSI CTI]



'''MEC API Activity:'''

''' [[OpenAPI development guidelines]] ''' How can I contribute to the API development?

'''MEC PoC Activity:'''

'''[[Ongoing PoCs]]''' Information about ongoing ISG MEC PoCs.

'''[[PoC Topics]]''' Information about ISG MEC PoC Topics.

'''[[PoC Framework]]''' Information about ISG MEC PoC Framework (process, criteria, templates....).

'''[[Logos and guidelines]]''' Information and guidelines on the use of ETSI and MEC PoC logo.

'''[[Q&A]]''' Usual questions (and answers) on ISG MEC PoCs.

----

''' [http://mecwiki.etsi.org/index.php?title=Special%3AUserLogin&returnto=Main+Page Login with your EOL account!]'''

Main Page

2017-10-27T16:11:04Z

Mullers:

This Wiki is provided as a tool for the use of ISG MEC participants.
You may need to login to access some information

''' >>> ISG MEC participants can login with their ETSI OnLine (EOL) account <<<'''

If you are an ISG MEC participant and do not have an EOL account yet,
you can [http://webapp.etsi.org/createaccount apply for an EOL account], or send a request to [mailto:helpdesk@etsi.org ETSI helpdesk]

For any other wiki related request, please [mailto:CTI_support@etsi.org?Subject=ISG_MEC_WIKI_request contact ETSI CTI]



''' OpenAPI development guidelines ''' How can I contribute to the API development?

'''MEC PoC Activity:'''

'''[[Ongoing PoCs]]''' Information about ongoing ISG MEC PoCs.

'''[[PoC Topics]]''' Information about ISG MEC PoC Topics.

'''[[PoC Framework]]''' Information about ISG MEC PoC Framework (process, criteria, templates....).

'''[[Logos and guidelines]]''' Information and guidelines on the use of ETSI and MEC PoC logo.

'''[[Q&A]]''' Usual questions (and answers) on ISG MEC PoCs.

----

''' [http://mecwiki.etsi.org/index.php?title=Special%3AUserLogin&returnto=Main+Page Login with your EOL account!]'''

MediaWiki:Sidebar

2017-10-27T16:09:08Z

Mullers:

PT04 MEC enabled vertical segments applications

2017-07-25T13:30:33Z

Mullers: /* Description */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:

• automotive and cooperative vehicles

• virtual reality / augmented reality

• IoT scenarios (with sensors, fog nodes, …)

• robotics and factories of the future

• eHealth and mHealth

• media and entertainment vertical

• applications for the energy industry

• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets

• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)?

• What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?

• Is the PoC identifying possible enhancements to the current MEC architecture?

• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:30:11Z

Mullers: /* Points to prove/refute */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets

• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)?

• What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?

• Is the PoC identifying possible enhancements to the current MEC architecture?

• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:29:37Z

Mullers: /* Points to prove/refute */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets

• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)?
What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?

• Is the PoC identifying possible enhancements to the current MEC architecture?

• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:29:10Z

Mullers: /* Points to prove/refute */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets

• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current
limitations? What has been made in the PoC(s) to overcome those limitations?

• Is the PoC identifying possible enhancements to the current MEC architecture?

• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:28:46Z

Mullers: /* Criterion of success */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets?
• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?
• Is the PoC identifying possible enhancements to the current MEC architecture?
• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:28:35Z

Mullers: /* Coordinator */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets?
• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?
• Is the PoC identifying possible enhancements to the current MEC architecture?
• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
• Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:28:28Z

Mullers: /* Concerned WGs/WI */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets?
• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?
• Is the PoC identifying possible enhancements to the current MEC architecture?
• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
• Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
RGS/MEC-0021TechReq

=Coordinator=
• Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:28:17Z

Mullers: /* Technical information to be provided by the PoC Team */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets?
• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?
• Is the PoC identifying possible enhancements to the current MEC architecture?
• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
• Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=

• New identified technical requirements and specific use case description

• Technical details on the issues faced

• Technical details on the solutions provided

• Technical details on the lessons learned

When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
• RGS/MEC-0021TechReq

=Coordinator=
• Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:27:50Z

Mullers: /* Coordinator */

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets?
• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?
• Is the PoC identifying possible enhancements to the current MEC architecture?
• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
• Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=
• New identified technical requirements and specific use case description
• Technical details on the issues faced
• Technical details on the solutions provided
• Technical details on the lessons learned
When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
• RGS/MEC-0021TechReq

=Coordinator=
• Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:27:25Z

Mullers:

= Description =
Demonstration of application scenarios specifically targeted on vertical markets of the 5G era, in order to show the usage of MEC system as enabler for different use cases and business objectives, helping all stakeholders to develop a diverse, open, MEC ecosystem. The goal is to emphasize the transversal role of MEC by MEC POC demonstrations of some use cases of vertical business area.
Description of these scenarios, possibly identifying new use cases (or enhancements of the existing ones) that could generate requirements for MEC Phase 2 work.
Examples of MEC-enabled Vertical Segments applications include specific services for:
• automotive and cooperative vehicles
• virtual reality / augmented reality
• IoT scenarios (with sensors, fog nodes, …)
• robotics and factories of the future
• eHealth and mHealth
• media and entertainment vertical
• applications for the energy industry
• etc …

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• What are the main use cases and requirements derived from the demonstrated applications of vertical segments markets?
• What are the different deployment options the identified applications? What is the one deployed / recommended by the PoC(s)? What are the main current limitations? What has been made in the PoC(s) to overcome those limitations?
• Is the PoC identifying possible enhancements to the current MEC architecture?
• What is missing, if any, in the MEC specifications to enable the showcased application to be implemented in a live network

==Criterion of success==
• Documentation of how the MEC-enabled Vertical Segments applications have been implemented and deployed, and which use cases (and/or requirements) have been identified for submission to the ISG MEC.

= Technical information to be provided by the PoC Team=
• New identified technical requirements and specific use case description
• Technical details on the issues faced
• Technical details on the solutions provided
• Technical details on the lessons learned
When applicable, submission of contributions to MEC technical requirements (GS MEC 002) for the MEC Phase 2 work.

=Concerned WGs/WI=
• RGS/MEC-0021TechReq

=Coordinator=
• Dario Sabella (POC support team) ([mailto:dario.sabella@intel.com dario.sabella@intel.com])

CTI Support: [mailto:cti_support@etsi.org cti_support@etsi.org]

=Contributions (feedback) deadline=
Q2 2018

PT04 MEC enabled vertical segments applications

2017-07-25T13:23:52Z

Mullers: Created page with "= Description = Identify valuable and measurable MEC metrics that demonstrate the technical and business benefits of the MEC solutions in some use cases. Demonstrate the ident..."

= Description =
Identify valuable and measurable MEC metrics that demonstrate the technical and business benefits of the MEC solutions in some use cases.
Demonstrate the identified MEC Metrics as drafted within the current DGS MEC-IEG006.

[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2015//MEC(15)000272r2_Hot_PoC_Topic_Proposal.docx MEC PoC Topic Proposal - MEC Metrics]

= Status =
'''ACTIVE'''

= What is expected to be learnt from the PoCs =

==Points to prove/refute==
• Valuable and measureable additional MEC Metrics that demonstrate the benefits of MEC in some use cases

• Demonstrate that the identified MEC Metrics are measurable

==Criterion of success==
• KPI/Metrics that are contributed to the draft GS MEC-IEG006

==Other information==
• Proposed measured metric value ranges with additional detailed description under what conditions they have been measured

= Technical information to be provided by the PoC Team=
The identified MEC Metrics are either described by the current draft or will be provided by the PoC Team as input contributions to the IEG WG meetings.

= Template for the PoC Feedback Contribution =
No specific template. POC Teams are expected to submit a Technical Report covering the points mentioned above.

=Concerned WGs/WI=
• GS MEC-IEG006 Mobile Edge Computing (MEC); MEC Metrics ([https://portal.etsi.org/tb.aspx?tbid=835&SubTB=835 See latest draft])

=Coordinator=
MEC-IEG006 Rapporteur: Milan Patel, Huawei ([mailto:milan.patel@huawei.com milan.patel@huawei.com])

CTI Support: [mailto:cti_support@etsi.org cti_support@etsi.org]

=Contributions (feedback) deadline=
Q4 2016

PoC Topics

2017-07-25T13:16:58Z

Mullers: /* MEC PoC Topics */

PoC Topics

2017-07-25T13:16:46Z

Mullers: /* MEC PoC Topics */

PoC Topics

2017-07-25T13:15:53Z

Mullers: /* MEC PoC Topics */

= Rationale =
MEC PoC Topics are specific areas, often linked to a Work Item, where input or feedback from the MEC Proofs of Concept is needed. MEC PoC Topics help to focus PoC Projects on the most relevant topics for the ISG MEC, and to increase the relevance of their contributions.

MEC PoC Topics are identified and documented by ISG MEC. MEC PoC Topics may include templates for the PoC Contributions and deadlines to ensure that the PoC Contributions arrive on-time to be taken into account by the targeted WIs.

= MEC PoC Topics =

{| class="wikitable"
! PoC Topic
! Status
! WI(s)
! PoC Feedback
! Deadline
|-
| '''[[PT01 - Demonstration of MEC Service Scenarios]]'''
| '''Active'''
| [https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=46047 MEC-IEG004]
| Technical Report
| Q4 2016
|-
| '''[[PT02 - MEC Metrics]]'''
| '''Active'''
| [https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=47908 MEC-IEG006]
| Technical Report
| Q4 2016
|-
| '''[[PT03 - MEC Architecture]]'''
| '''Active'''
| [https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=46046 MEC003]
| Technical Report
| Q4 2016
|}

<googlespreadsheet style="width:900px; height:400px" sheet="990838750" >1UUMWpAR6_elhU6DwoTqaDBgDNgV4hvtiSKkyHj4P-hM</googlespreadsheet>

= Addressing a PoC Topic in a PoC Project =
PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected input or feedback in the requested format (template, if applicable) in a timely manner.

= Feeding back the results =
As soon as experimental results relevant for a given MEC PoC Topic are available (no need to wait for the PoC Project to be completed), the PoC Team creates a contribution and informs the ISG MEC by email (if the PoC Topic had a specific template for feedback contributions, it should be used). PoC Teams are also encouraged to contribute additional results and lessons learned during the PoC Project to the ISG MEC.

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2017-06-07T14:34:34Z

Mullers: /* PoC Topics */

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2017-06-07T14:32:48Z

Mullers: /* PoC Proposal */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017/MEC(17)000254r1_PoC_Proposal-Service-Aware_MEC_Platform_to_Enable_Bandwidth_.doc Service Aware MEC Platform to Enable Bandwidth]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

PoC Contribution to PT01 and PT03 (Technical Report) is expected by Q3 2017

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2017-06-07T14:30:51Z

Mullers: /* Abstract */

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC utilizes two application contexts including Enterprise Video Call/VoIP and Tele-Drone to demonstrate the feature BandwidthManager of ETSI MEC FEATUREs defined in Mobile Edge Computing (MEC); Technical Requirements (ETSI GS MEC 002 V1.1.1). The PoC will be verified on multi-vendor EPCs which contain our team member FarEasTone (FET)’s EPC and the multi-vendor EPCs in ITRI’s 4G+/5G testbed. The MEC platform of our PoC executes as a Virtual Network Function (VNF) in a container-based a Virtual Machine (VM) environment environment and provides an interface for installing the service application (APP) into a container or a VM and configuring a set of parameters for bandwidth management of a mobile network.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000003r1_PoC_Proposal__Platform_to_enable_low-latency_Industrial_IoT.docx MEC_Platform_to_enable_low-latency_Industrial_IoT]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

PoC Contribution to PT01 and PT03 (Technical Report) is expected by Q3 2017

== PoC Report ==
PoC Report is expected by Q1 2018

PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN

2017-06-07T14:24:05Z

Mullers: Created page with "== PoC Team == Industry Technology Research Institute Linker Network FarEasTone == Main Contact == Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw] Wil..."

== PoC Team ==
Industry Technology Research Institute

Linker Network

FarEasTone

== Main Contact ==
Kuo-Wei Wen, ITRI [mailto:JimmyWen@itri.org.tw JimmyWen@itri.org.tw]

Willy Kuo, Linker Networks [mailto:wguo@linkernetworks.com wguo@linkernetworks.com]

Ming Lin, FarEasTone [mailto:mijlin@fareastone.com.tw mijlin@fareastone.com.tw]

== PoC Demo ==
PoC Demo 1 – ''Service-Aware MEC Platform for Service Offload with Enterprise Video Call/VoIP'', Jun 2017, Small Cell Forum Plugfest & 5G Workshop, NTUH Internal Convention Center, Taipei City, Taiwan

Poc Demo 2 – ''Service-Aware MEC Platform for Traffic Offload and Static Bandwidth Management with Enterprise Video Call/VoIP'', Sep 2017, MEC Congress 2017, Berlin

Poc Demo 3 – ''Service-Aware MEC Platform for Traffic Offload and Dynamic Bandwidth Management with Enterprise Video Call/VoIP or Tele-Drone'', Feb 2018, MWC 2018, Barcelona

== Abstract ==
This PoC considers a typical Industry 4.0 (RAMI 4.0 - Platform 4.0 Industrie)* IoT use-case for latency, mobility and location sensitive applications, wherein a MEC host with local RAN breakout can enable massively scalable real-time duplex trusted transit delivery of data between IoT devices (sensors, actuators, control systems etc.) and cloud based industrial applications that leverage low-latency transactions with real-time meta-data on localized usage, security and QoS. The PoC will simulate a real-world Industry 4.0* use case and demonstrate several value drivers for stakeholders driving IoT.

This PoC will leverage Xaptum’s distributed Peering IP-Overlay Network for IoT and extend their peering Xaptum ENF (Edge Network Fabric) Run-Time Architecture to the mobile edge for low latency and secure communication in Industrial IoT devices and applications. By combining Xaptum ENF with Oberthur’s embedded cryptographic authentication SE (Secure Element) offering and vendor neutral TPM 2.0 (Trusted Platform Module) and DAA (Direct Anonymous Attestation) to both IoT device and application end-points, we shall be able to demonstrate several use-cases that meet stringent requirements for industrial applications as defined by leading Industry 4.0 standards.

The entirety of the PoC will be deployed over an NFV infrastructure to highlight the benefits of COTS hardware and to reap the benefits of orchestration and automation. The PoC will leverage RIFT.io RIFT.ware, a commercially supported offering of the ETSI Open Source MANO (OSM).

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000003r1_PoC_Proposal__Platform_to_enable_low-latency_Industrial_IoT.docx MEC_Platform_to_enable_low-latency_Industrial_IoT]

== PoC Topics ==
This PoC is WORKING on:

[[PT01 - Demonstration of MEC Service Scenarios]]

[[PT03 - MEC Architecture]]

PoC Contribution to PT01 and PT03 (Technical Report) is expected by Q3 2017

== PoC Report ==
PoC Report is expected by Q1 2018

Ongoing PoCs

2017-06-07T14:16:36Z

Mullers: /* List of PoCs */

Ongoing PoCs

2017-06-07T14:16:07Z

Mullers: /* List of PoCs */

PoC 3 Radio aware video optimization in a fully virtualized network

2017-05-17T07:32:50Z

Mullers: /* Main Contact */

== PoC Team ==
Telecom Italia

Intel UK Corporation

Eurecom

Politecnico di Torino

== Main Contact ==
Dario Sabella, Intel [mailto:dario.sabella@intel.com dario.sabella@intel.com]

Navid Nikaein, Telecom Italia [mailto:navid.nikaein@eurecom.fr navid.nikaein@eurecom.fr]

== PoC Demo ==
PoC Demo 1 - ETSI MEC plenary #7b, Sophia Antipolis (FR), 27-30 June, 2016

PoC Demo 2 - MEC congress 2016, Munich (GE), 20-22 September 2016

PoC Demo 3 - MWC 2017, Barcelona (SP), February 2017

== Abstract ==
This PoC is demonstrating a video optimisation application aware of the Radio conditions in the cell, where MEC application is co-located with eNB and communicating with video content server, and quality of video streams are adjusted according to radio conditions of the users. As a result, video streams and the quality perceived by users will be improved thanks to the usage of MEC video optimization application.

== PoC Proposal ==
[https://docbox.etsi.org/ISG/MEC/Closed_WGs/IEG/05-CONTRIBUTIONS/2015/MECIEG(15)000064r1_Radio_aware_video_optimization_in_a_fully_virtualized_networ.docx Radio_aware_video_optimization_in_a_fully_virtualized_network]

== PoC Topics ==
This PoC is WORKING on: [[PT01 - Demonstration of MEC Service Scenarios]]

PoC Contribution to PT01 (Technical Report) is expected by July 2016

This PoC is also working and will be providing feedback to ISG MEC on:

* MEC APIs

* MEC metrics and baseline results (MEC-IEG-006)

PoC Contributions on these areas are expected by July 2016

== PoC Report ==
PoC Report is expected by Q1 2017

Ongoing PoCs

2017-04-26T13:46:55Z

Mullers:

Ongoing PoCs

2017-04-26T13:44:45Z

Mullers: /* Overview of Reports */

==Overview of Reports==
<googlespreadsheet style="width:900px; height:300px" sheet="0" >1UUMWpAR6_elhU6DwoTqaDBgDNgV4hvtiSKkyHj4P-hM</googlespreadsheet>

==List of PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

Ongoing PoCs

2017-04-26T13:32:21Z

Mullers: /* Overview of Reports */

==Overview of Reports==
<googlespreadsheet style="width:800px; height:300px" sheet="0" >1UUMWpAR6_elhU6DwoTqaDBgDNgV4hvtiSKkyHj4P-hM</googlespreadsheet>

==List of PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

Ongoing PoCs

2017-04-26T13:31:48Z

Mullers: /* Overview of Reports */

==Overview of Reports==
<googlespreadsheet style="width:600px; height:400px" sheet="0" >1UUMWpAR6_elhU6DwoTqaDBgDNgV4hvtiSKkyHj4P-hM</googlespreadsheet>

==List of PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

Ongoing PoCs

2017-04-26T13:30:57Z

Mullers: /* Overview of Reports */

==Overview of Reports==
<googlespreadsheet style="width:600px; height:400px" >1UUMWpAR6_elhU6DwoTqaDBgDNgV4hvtiSKkyHj4P-hM</googlespreadsheet>

==List of PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

Ongoing PoCs

2017-04-26T13:29:17Z

Mullers:

==Overview of Reports==

==List of PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

Ongoing PoCs

2017-04-26T13:28:47Z

Mullers:

==Overview of Reports==

==Ongoing PoCs==
This page provides the list of on-going ISG MEC PoCs. Click on them to learn further details.

The following MEC Proofs of Concept are developed according to the ETSI ISG MEC Proof of Concept Framework. MEC Proofs of Concept are intended to demonstrate MEC as a viable technology. Results are fed back to the Industry Specification Group on Mobile Edge Computing.

Neither ETSI, the ISG MEC, nor their members make any endorsement of any product or implementation claiming to demonstrate or conform to MEC. No verification or test has been performed by ETSI on any part of these MEC Proofs of Concept.

'''[[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]]'''
Intel - China Mobile - iQiYi

'''[[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]]'''
Nokia - EE - Smart Mobile Labs

'''[[PoC 3 Radio aware video optimization in a fully virtualized network]]'''
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino

'''[[PoC 4 FLIPS – Flexible IP-based Services]]'''
InterDigital - Bristol is Open - Intracom - CVTC - Essex University

'''[[PoC 5 Enterprise Services]]'''
Saguna - Adva Optical Networking - Bezeq International

'''[[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]]'''
Quortus Ltd - Argela - Turk Telecom

'''[[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]]'''
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone

'''[[PoC 8 Video Analytics]]'''
Nokia - Vodafone Hutchison Australia - SeeTec

'''[[PoC 9 MEC platform to enable low-latency Industrial IoT]]'''
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone

PoC Framework

2017-04-12T12:56:06Z

Mullers: /* MEC PoC Framework Document */

__TOC__

= MEC PoC Framework Document =
The MEC Proof of Concept (PoC) Framework GS describes the full ISG MEC PoC activity process, roles, responsibilities, acceptance criteria, etc...

The latest version of this document can be downloaded here: [[Media: Gs_MEC-IEG005v010102.pdf | MEC PoC Framework]].

For convenience of the PoC Teams, direct links to the PoC Proposal/PoC Report Templates, PoC Topics and a summary of the PoC Proposal acceptance criteria are provided below.

= Templates =

[[Media:MEC_PoC_proposal_template v2.doc | MEC PoC Proposal Template (word)]]

[[Media:MEC_PoC_report_template v2.doc | MEC PoC Report Template (word)]]

= PoC Topics =

PoC Projects are expected to be scoped arround PoC Topics identified and agreed by ISG MEC. [[PoC Topics|See details and current list of PoC Topics]].

= Submitting a PoC Proposal =
# The PoC Team fills in the PoC Proposal template
# The PoC Team uploads the completed proposal to the ETSI portal as a contribution to MEC
# The PoC Team sends an email to the [mailto:ISG_MEC@list.etsi.org MEC mailing list] containing the link to the proposal

= Acceptance Criteria =
The PoC Proposals shall fulfill the following acceptance criteria:
* The PoC Proposal will follow the PoC Proposal Template
* The PoC Team will have at a minimum 3 different organizations:
** at least one network operator;
** at least one infrastructure provider;
** at least one content/application provider.
* The PoC Point of Contact will be an ISG MEC Member or ISG MEC Participant.
* The PoC Proposal will address at least one of the PoC topics listed on the MEC Wiki.
* The PoC Proposal will commit for a demonstration of the PoC at a public event, e.g. Public Exhibition, ISG MEC meeting, a related conference, or other events

= CTI support =
The ETSI Center for Testing and Interoperability (CTI) can assist the PoC teams with test expertise, administration and project management.

MEC PoC Teams may request CTI assistance by [mailto:CTI_Support@etsi.org?Subject=MEC_PoC-Support_Request contacting ETSI CTI].

= About ISG MEC =
ISG MEC is creating a standardized, open environment which will allow the efficient and seamless integration of applications from vendors, service providers, and third-parties across multi-vendor Mobile-edge Computing platforms.

ISG MEC has developed a MEC PoC Framework to coordinate and promote multi-vendor Proofs of Concept illustrating key aspects of the ISG MEC work.

[http://www.etsi.org/technologies-clusters/technologies/mec Learn more about ISG MEC]

PoC Framework

2017-04-12T12:55:49Z

Mullers: /* MEC PoC Framework Document */

__TOC__

= MEC PoC Framework Document =
The MEC Proof of Concept (PoC) Framework GS describes the full ISG MEC PoC activity process, roles, responsibilities, acceptance criteria, etc...

The latest version of this document can be downloaded from:

[[Media: Gs_MEC-IEG005v010102.pdf | MEC PoC Framework]].

For convenience of the PoC Teams, direct links to the PoC Proposal/PoC Report Templates, PoC Topics and a summary of the PoC Proposal acceptance criteria are provided below.

= Templates =

[[Media:MEC_PoC_proposal_template v2.doc | MEC PoC Proposal Template (word)]]

[[Media:MEC_PoC_report_template v2.doc | MEC PoC Report Template (word)]]

= PoC Topics =

PoC Projects are expected to be scoped arround PoC Topics identified and agreed by ISG MEC. [[PoC Topics|See details and current list of PoC Topics]].

= Submitting a PoC Proposal =
# The PoC Team fills in the PoC Proposal template
# The PoC Team uploads the completed proposal to the ETSI portal as a contribution to MEC
# The PoC Team sends an email to the [mailto:ISG_MEC@list.etsi.org MEC mailing list] containing the link to the proposal

= Acceptance Criteria =
The PoC Proposals shall fulfill the following acceptance criteria:
* The PoC Proposal will follow the PoC Proposal Template
* The PoC Team will have at a minimum 3 different organizations:
** at least one network operator;
** at least one infrastructure provider;
** at least one content/application provider.
* The PoC Point of Contact will be an ISG MEC Member or ISG MEC Participant.
* The PoC Proposal will address at least one of the PoC topics listed on the MEC Wiki.
* The PoC Proposal will commit for a demonstration of the PoC at a public event, e.g. Public Exhibition, ISG MEC meeting, a related conference, or other events

= CTI support =
The ETSI Center for Testing and Interoperability (CTI) can assist the PoC teams with test expertise, administration and project management.

MEC PoC Teams may request CTI assistance by [mailto:CTI_Support@etsi.org?Subject=MEC_PoC-Support_Request contacting ETSI CTI].

= About ISG MEC =
ISG MEC is creating a standardized, open environment which will allow the efficient and seamless integration of applications from vendors, service providers, and third-parties across multi-vendor Mobile-edge Computing platforms.

ISG MEC has developed a MEC PoC Framework to coordinate and promote multi-vendor Proofs of Concept illustrating key aspects of the ISG MEC work.

[http://www.etsi.org/technologies-clusters/technologies/mec Learn more about ISG MEC]

PoC Framework

2017-04-12T12:55:16Z

Mullers: /* MEC PoC Framework Document */

__TOC__

= MEC PoC Framework Document =
The MEC Proof of Concept (PoC) Framework GS describes the full ISG MEC PoC activity process, roles, responsibilities, acceptance criteria, etc... The latest version of this document can be downloaded from:

[[Media: Gs_MEC-IEG005v010102.pdf | MEC PoC Framework]].

For convenience of the PoC Teams, direct links to the PoC Proposal/PoC Report Templates, PoC Topics and a summary of the PoC Proposal acceptance criteria are provided below.

= Templates =

[[Media:MEC_PoC_proposal_template v2.doc | MEC PoC Proposal Template (word)]]

[[Media:MEC_PoC_report_template v2.doc | MEC PoC Report Template (word)]]

= PoC Topics =

PoC Projects are expected to be scoped arround PoC Topics identified and agreed by ISG MEC. [[PoC Topics|See details and current list of PoC Topics]].

= Submitting a PoC Proposal =
# The PoC Team fills in the PoC Proposal template
# The PoC Team uploads the completed proposal to the ETSI portal as a contribution to MEC
# The PoC Team sends an email to the [mailto:ISG_MEC@list.etsi.org MEC mailing list] containing the link to the proposal

= Acceptance Criteria =
The PoC Proposals shall fulfill the following acceptance criteria:
* The PoC Proposal will follow the PoC Proposal Template
* The PoC Team will have at a minimum 3 different organizations:
** at least one network operator;
** at least one infrastructure provider;
** at least one content/application provider.
* The PoC Point of Contact will be an ISG MEC Member or ISG MEC Participant.
* The PoC Proposal will address at least one of the PoC topics listed on the MEC Wiki.
* The PoC Proposal will commit for a demonstration of the PoC at a public event, e.g. Public Exhibition, ISG MEC meeting, a related conference, or other events

= CTI support =
The ETSI Center for Testing and Interoperability (CTI) can assist the PoC teams with test expertise, administration and project management.

MEC PoC Teams may request CTI assistance by [mailto:CTI_Support@etsi.org?Subject=MEC_PoC-Support_Request contacting ETSI CTI].

= About ISG MEC =
ISG MEC is creating a standardized, open environment which will allow the efficient and seamless integration of applications from vendors, service providers, and third-parties across multi-vendor Mobile-edge Computing platforms.

ISG MEC has developed a MEC PoC Framework to coordinate and promote multi-vendor Proofs of Concept illustrating key aspects of the ISG MEC work.

[http://www.etsi.org/technologies-clusters/technologies/mec Learn more about ISG MEC]