MECwiki - User contributions [en]

Ongoing PoCs

2024-09-18T08:15:11Z

Featherston1: Change status of PoC 15 & 16 to completed and added report link

__TOC__

<big>'''Overview of Reports'''</big>

<big>
{| class="wikitable center"
! PoC Num
! Description
! Final Report
|-
| PoC 16
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_16_MEC_based_Smart_production_and_scheduling MEC based Smart production and scheduling]
| [//docbox.etsi.org/ISG/MEC/05-Contributions/2024/MEC(24)000353r1_MEC_24_000353_report_for_MEC_PoC__16.doc PoC16_Final_Report]
|-
Distributed MEC based AR remote maintenance for logistics transportation
| PoC 15
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_15_Distributed_MEC_based_AR_remote_maintenance_for_logistics_transportation Distributed MEC based AR remote maintenance for logistics transportation]
| [//docbox.etsi.org/ISG/MEC/05-Contributions/2024/MEC(24)000352r1_MEC_24_000352_report_for_MEC_PoC__15.doc PoC15_Final_Report]
|-
| PoC 14
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_14_Network_resource_allocation Network resource allocation for Gaming using MEC BandWidth Management service and TeraFlowSDN]
| Ongoing
|-
| PoC 13
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_13_MEC_infotainment_for_smart_roads_and_city_hot_spots MEC infotainment for smart roads and city hot spots]
| Completed
|-
| PoC 12
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_12_MEC_enabled_Over-The-Top_business MEC enabled OTT business]
| Completed
|-
| PoC 11
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_11_Communication_Traffic_Management_for_V2X Communication Traffic Management for V2X]
| [//docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2019//MEC(19)000243r2_MEC_PoC11_report.zip PoC11_Final_Report]
|-
| PoC 10
| style="text-align:left;" | [//mecwiki.etsi.org/index.php?title=PoC_10_Service-Aware_MEC_Platform_to_Enable_Bandwidth_Management_of_RAN Service-Aware MEC Platform to Enable Bandwidth Management of RAN]
| Completed
|-
| PoC 9
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_9_MEC_platform_to_enable_low-latency_Industrial_IoT MEC platform to enable low-latency Industrial IoT]
| Completed
|-
| PoC 8
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_8_Video_Analytics Video Analytics]
| [//docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000194_PoC_8_Final_Report.zip PoC8_Final_Report]
|-
| PoC 7
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_7_Multi-Service_MEC_Platform_for_Advanced_Service_Delivery Multi-Service MEC Platform for Advanced Service Delivery]
| Completed
|-
| PoC 6
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_6_Healthcare_%E2%80%93_Dynamic_Hospital_User,_IoT_and_Alert_Status_management Healthcare – Dynamic Hospital User, IoT and Alert Status management]
| Completed
|-
| PoC 5
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_5_Enterprise_Services Enterprise Services]
| Completed
|-
| PoC 4
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_4_FLIPS_%E2%80%93_Flexible_IP-based_Services FLIPS – Flexible IP-based Services]
| Completed
|-
| PoC 3
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_3_Radio_aware_video_optimization_in_a_fully_virtualized_network Radio aware video optimization in a fully virtualized network]
| [//docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2021/MEC(21)000338_MEC_PoC_3_Final_Report.zip PoC3_Final_Report]
|-
| PoC 2
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_2_Edge_Video_Orchestration_and_Video_Clip_Replay_via_MEC Edge Video Orchestration and Video Clip Replay via MEC]
| [//docbox.etsi.org/ISG/MEC/05-CONTRIBUTIONS/2017//MEC(17)000193_PoC_2_Final_Report.zip PoC2_Final_Report]
|-
| PoC 1
| style="text-align:left;" | [http://mecwiki.etsi.org/index.php?title=PoC_1_Video_User_Experience_Optimization_via_MEC_-_A_Service_Aware_RAN_PoC Video User Experience Optimization via MEC - A Service Aware RAN PoC]
| Completed
|}
</big>

<big>'''List of PoCs'''</big>

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.

To request a ETSI MEC PoC, please contact [mailto:CTI_Support@etsi.org CTI_Support@etsi.org].


== [[PoC 1 Video User Experience Optimization via MEC - A Service Aware RAN PoC]] ==
Intel - China Mobile - iQiYi
Through the Video UE Optimization application running on the MEC server, the MEC application is able to recognize which are the paid video streams from the content provider. From there, the MEC application will assign higher priority to those video streams by ensuring higher bit rate. As a result, the paid subscribers will have a more guaranteed user experience when streaming video from the designated content provider.
[[File:Poc1.png|center|800x600px|link=PoC_1_Video_User_Experience_Optimization_via_MEC_-_A_Service_Aware_RAN_PoC]]
<br>

== [[PoC 2 Edge Video Orchestration and Video Clip Replay via MEC]] ==
Nokia - EE - Smart Mobile Labs
Through the Edge Video Orchestration application running on the MEC server, the end user is able to receive live video streams from professional stadium cameras in real time. The user can choose the camera angle and view video replays provided locally. All media is produced, injected and played out locally, without the need to modify core network elements. Backhaul and core capacity is not impacted.
[[File:Poc2.png|center|800x800px|link=PoC_2_Edge_Video_Orchestration_and_Video_Clip_Replay_via_MEC]]
<br>

== [[PoC 3 Radio aware video optimization in a fully virtualized network]] ==
InterDigital - Bristol is Open - Intracom - CVTC - Essex University
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.
[[File:Poc3.png|center|600x600px|link=PoC_3_Radio_aware_video_optimization_in_a_fully_virtualized_network]]
<br>

== [[PoC 4 FLIPS – Flexible IP-based Services]] ==
Telecom Italia - Intel UK Corporation - Eurecom - Politecnico di Torino
An operator-based MEC Application is designed to transparently accelerate delivery of IP-based content and streaming media. This Application additionally allows exposure of in-network surrogate server to allow operators to offer Surrogate-as-a-Service for web-based media delivery
[[File:Poc4.png|center|600x600px|link=PoC_4_FLIPS_–_Flexible_IP-based_Services]]
<br>

== [[PoC 5 Enterprise Services]] ==
Saguna - Adva Optical Networking - Bezeq International
se of MEC for Enterprise by implementation of a local breakout for the enterprise users
[[File:PoC5.png|center|600x600px|link=PoC_5_Enterprise_Services]]
<br>

== [[PoC 6 Healthcare – Dynamic Hospital User, IoT and Alert Status management]] ==
Brocade - Gigaspaces - Advantech - Saguna - Vasona - Vodafone
This POC considers a typical ‘Healthcare’ use-case where a Hospital is able to assign a cellular access hierarchy (using network slicing) and open access (at the edge) to local systems depending on managed access rights. It also demonstrates dynamic network slicing based on Hospital ‘alert’ status
[[File:Poc6.png|center|500x500px|link=PoC_6_Healthcare_–_Dynamic_Hospital_User,_IoT_and_Alert_Status_management]]
<br>

== [[PoC 7 Multi-Service MEC Platform for Advanced Service Delivery]] ==
Quortus Ltd - Argela - Turk Telecom
Through a single, unified infrastructure, NFV-O, and cloud orchestration system, this MEC PoC demonstrates the ability to support multiple MEC platforms and applications residing on shared and common computing infrastructure, each providing a unique value-add on the traffic traversing platform.
[[File:Poc7.png|center|600x600px|link=http://mecwiki.etsi.org/index.php?title=PoC_7_Multi-Service_MEC_Platform_for_Advanced_Service_Delivery Multi-Service]]
<br>

== [[PoC 8 Video Analytics]] ==
Nokia - Vodafone Hutchison Australia - SeeTec
This MEC PoC submission is about a video analytics solution that leverages MEC for analyzing raw video streams of LTE-connected surveillance cameras and forwarding of relevant incidents to the local control room,
[[File:Poc8.png|center|600x600px|link=PoC_8_Video_Analytics]]
<br>

== [[PoC 9 MEC platform to enable low-latency Industrial IoT]] ==
Vasona Networks - RIFT.io - Xaptum - Oberthur Technologies - Intel Corporation - Vodafone
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.
[[File:Poc9.png|center|600x600px|link=PoC_9_MEC_platform_to_enable_low-latency_Industrial_IoT]]
<br>
== [[PoC 10 Service-Aware MEC Platform to Enable Bandwidth Management of RAN]] ==
Industry Technology Research Institute - Linker Network - FarEasTone
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)
[[File:Poc10.png|center|600x600px|link=PoC_10_Service-Aware_MEC_Platform_to_Enable_Bandwidth_Management_of_RAN]]
<br>
== [[PoC 11 Communication Traffic Management for V2X]] ==
KDDI Corporation - Saguna Networks Ltd. - Hewlett Packard Enterprise
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, it is demonstrated 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.
[[File:Poc11.png|center|600x600px|link=PoC_11_Communication_Traffic_Management_for_V2X]]
<br>
== [[PoC 12 MEC enabled Over-The-Top business]] ==
China Unicom - ZTE - Intel - Tencent - Wo video - UnitedStack
This ETSI MEC PoC is about enabling OTT business on MEC platform: distributing OTT’s CDN to the MEC platform in the network of China Unicom. The combination of CDN and MEC can reduce the RTT and increase the HTTP download rate.
[[File:Poc12.png|center|800x700px|link=PoC_12_MEC_enabled_Over-The-Top_business]]
<br>
== [[PoC 13 MEC infotainment for smart roads and city hot spots]] ==
TIM - Intel - Vivida - ISMB - City of Turin
The use case aims at demonstrating innovative 4G/5G infotainment services for both pedestrians and car drivers/passengers in smart roads and city hot spots.
[[File:Poc13.png|center|600x600px|link=PoC_13_MEC_infotainment_for_smart_roads_and_city_hot_spots]]

== [//mecwiki.etsi.org/index.php?title=PoC_14_Network_resource_allocation PoC 14 Network resource allocation for Gaming using MEC BandWidth Management service and TeraFlowSDN] ==
CTTC - xFlow Research - Telefónica

MEC BandWidth Management (BWM) service and TeraFlowSDN can be used to provide dedicated resources for network resource allocation for Gaming. BWM allows applications to allocate specific amounts of bandwidth to gaming applications, while TeraFlowSDN provides a way to manage and control traffic flows.

This can help to ensure that gaming traffic has priority over other traffic, which can improve the gaming experience for users. The tests of this compute-network interface can also be interesting for upcoming 6G networks.
[[File:Poc14.png|center|600x600px|link=PoC_14_Network_resource_allocation]]

== [//mecwiki.etsi.org/index.php?title=PoC_15_Distributed_MEC_based_AR_remote_maintenance_for_logistics_transportation PoC 15 Distributed MEC based AR remote maintenance for logistics transportation] ==
China Telecom - China Telecom Intelligent NETWORK Technology - Huawei

This PoC proposal describes the 5G distributed MEC solution to support remote maintenance of AR in logistics transportation. This solution can effectively improve the efficiency of logistics transportation and reduce the maintenance cost.
<br>
[[File:Poc15.png|center|600x600px|link=PoC_15_Distributed_MEC_based_AR_remote_maintenance_for_logistics_transportation]]

== [//mecwiki.etsi.org/index.php?title=PoC_16_MEC_based_Smart_production_and_scheduling PoC 16 MEC based Smart production and scheduling] ==
China Telecom - China Telecom Intelligent NETWORK Technology - Huawei

This PoC proposal describes the 5G MEC solution supporting industrial manufacturing for industrial production, detection, scheduling used in Park. With this solution, industrial production efficiency will be greatly improved.
<br>
[[File:Poc16.png|center|800x800px|link=PoC_16_MEC_based_Smart_production_and_scheduling]]

MEC URN namespace

2024-03-25T15:00:27Z

Featherston1: Changed https to http to avoid a "lock icon" being presented

<h3> Introduction</h3>
ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [http://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx [1]]. The MEC URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

The following sections describe the basic structure of the sub-tree and how an entry in the registry can be requested.

<h3>MEC sub-tree</h3>
{| class="wikitable"
|+
!MEC sub-tree
!Full Namespace
!Type
!Description
|-
|coord
|<nowiki>urn:etsi:mec:coord</nowiki>
|string
|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[http://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>
</ul>
|-
|capifext
|<nowiki>urn:etsi:mec:capifext</nowiki>
|string
|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:

* ETSI GS MEC 011 v3.2.1 (published at [[http://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]])
|}

<h3>Type definitions</h3>
<pre>
string = 1*(ALPHANUMERIC/-/_)
# a string should contain one or more upper- or lower-case letters, integer numbers, hyphens or underscores

ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by the ETSI MEC ISG and its working groups, by making a contribution to ETSI ISG MEC DECODE.

<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).

MEC URN namespace

2024-03-25T11:31:08Z

Featherston1: Added "onwards" to indicate that versions later than 010-2 V2.2.1 are valid too

<h3> Introduction</h3>
ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx [1]]. The MEC URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

The following sections describe the basic structure of the sub-tree and how an entry in the registry can be requested.

<h3>MEC sub-tree</h3>
{| class="wikitable"
|+
!MEC sub-tree
!Full Namespace
!Type
!Description
|-
|coord
|<nowiki>urn:etsi:mec:coord</nowiki>
|string
|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>
</ul>
|-
|capifext
|<nowiki>urn:etsi:mec:capifext</nowiki>
|string
|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:

* ETSI GS MEC 011 v3.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]])
|}

<h3>Type definitions</h3>
<pre>
string = 1*(ALPHANUMERIC/-/_)
# a string should contain one or more upper- or lower-case letters, integer numbers, hyphens or underscores

ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by the ETSI MEC ISG and its working groups, by making a contribution to ETSI ISG MEC DECODE.

<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).

MEC URN namespace

2024-03-23T03:13:58Z

Featherston1: Implementation of MECDECODE(24)000007

<h3> Introduction</h3>
ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The MEC URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

The following sections describe the basic structure of the sub-tree and how an entry in the registry can be requested.

<h3>MEC sub-tree</h3>
{| class="wikitable"
|+
!MEC sub-tree
!Full Namespace
!Type
!Description
|-
|coord
|<nowiki>urn:etsi:mec:coord</nowiki>
|string
|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>
</ul>
|-
|capifext
|<nowiki>urn:etsi:mec:capifext</nowiki>
|string
|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:

* ETSI GS MEC 011 v3.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]])
|}

<h3>Type definitions</h3>
<pre>
string = 1*(ALPHANUMERIC/-/_)
# a string should contain one or more upper- or lower-case letters, integer numbers, hyphens or underscores

ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by the ETSI MEC ISG and its working groups, by making a contribution to ETSI ISG MEC DECODE.

<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).