MEC(18)000003r1

Title*: Way Forward On Terminology Acronyms

from Source*: Virtuosys Limited Contact: Mark Cannon input for Committee*: MEC

Contribution For*: Decision X Discussion Information

Submission date*: 2018-01-09

Meeting & Allocation: MEC#88-Tech - Relevant WI(s), or RGS/MEC-0001v211Terms deliverable(s):

Decision/action requested: Please approve

ABSTRACT: This contribution discusses some alternative approaches for defining MEC acronyms in the Phase 2 specification documents. Some specific proposals are made that are intended to promote a consistent approach.

1/7 MEC(18)000003r1

1 Introduction

There was some discussion at the last face-to-face meeting in Chandler (MEC#12) about the best approach for defining MEC acronyms in the specification documents. This document describes some alternative approaches that could be adopted and makes some specific proposals that are intended to promote a consistent approach across all the Phase 2 specifications and to reduce the burden on anyone making a change to the documents.

The MEC-specific and non-MEC specific acronyms are treated separately in clauses 2 and 3.

A summary of all the acronyms from all the currently active specifications is shown in the Annex.

The changes in Revision r1 reflect the decisions agreed during MEC#88-Tech.

2 MEC-specific acronyms

The most problematic definitions are those that MEC is defining for its own use. Some MEC acronyms are defined identically in multiple Phase 1 documents and this is potentially causing inconsistency and could cause maintenance problems if the same approach is used in Phase 2. Hence the first proposal is that all MEC-specific acronyms are only defined in one place.

Proposal 1: All MEC-specific acronyms used in the Phase 2 documents should only be defined in MEC001, the Terminology specification document.

The definitions which are causing an issue are where “Mobile Edge” is changing to “MEC”. For example, “Mobile Edge Platform Manager” is changing to “MEC Platform Manager”.

Two approaches have been suggested so far as follows:

Approach 1 MECP MEC Platform MECPM MEC Platform Manager MECO MEC Orchestrator

Approach 2 MEP MEC Platform MEPM MEC Platform Manager MEO MEC Orchestrator

Note that it is not absolutely necessary to consider what definitions are currently used in MEC014 or MEC017 as these are Phase 1 documents. The Phase 2 versions (when/if they are created) can then be made consistent with the remaining Phase 2 documents.

It is not desirable to change the existing acronyms that are already defined in the Phase 1 documents MEC014 and MEC017 and it is proposed that these remain as they are.

It was agreed at MEC#88-Tech to follow Approach 2. Note that this means that MEC10-2 and MEC011 will have to be edited.

Proposal 2: The following acronyms should be defined in the Phase 2 MEC001 specification and removed from any other Phase 2 documents: MEP MEC Platform MEPM MEC Platform Manager MEO MEC Orchestrator Once a Phase 2 version of MEC017 is created then the following definitions can be added to MEC001. MEAO MEC Application Orchestrator MEPM-V MEC Platform Manager - NFV

2/7 MEC(18)000003r1

3 Repeated acronyms in Phase 2 documents

The following (non-MEC specific) acronyms are defined in multiple documents in the Phase 2 specifications:

3GPP 3rd Generation Partnership Project API Application Programming Interface DNS FQDN Fully Qualified Domain Name GRE Generic Routing Encapsulation GTP-U GPRS -User plane GTP GPRS Tunnelling Protocol HTTP Hyper Text Transfer Protocol IP JSON Javascript Object Notation MAC Media Access Control NTP PTP QCI Quality Class Indicator REST Representational State Transfer RFC Request For Comments RNI Radio Network Information RNIS Radio Network Information Service TEID Tunnel End Point Identifier TLS Security UE User Equipment URI Uniform Resource Identifier URL Uniform Resource Locator UTC Coordinated Universal Time

There are a couple of approaches to deal with this issue:

Approach 1 Move these definitions to MEC001 and remove the definitions in the other Phase 2 documents. This would ensure that the definitions are consistent across all the MEC documentation. However, the disadvantage is that more work is needed initially, and this will be very inconvenient in the future as well. For example, if a new acronym is needed in any Phase 2 document then it would be necessary to search through all the active documents to check if it is already defined anywhere. If it is already defined, then both that document and MEC001 would have to be edited in addition to the specification where the change is really targeted. This seems like a burden that CR creators are not likely to remember or apply consistently. There is also the problem that a Phase 2 specification may already have been published, and so it would not be possible to remove the definition without a maintenance change.

Approach 2 Accept that these non-MEC specific acronyms can be defined in multiple documents. However, they should at least be defined consistently.

Proposal 3: It is accepted that acronyms can be defined identically in multiple MEC Phase 2 documents. Note that this applies only to non-MEC terminology which is already well known and is defined in standards elsewhere or is in common usage. .

4 Conclusion

Some alternative approaches to defining the acronyms for the Phase 2 MEC specification documents have been described. The three proposals above are suggested as a way forward.

3/7 MEC(18)000003r1

Annex A: Acronyms used in the currently active MEC specs

Acronyms used in the currently active MEC draft specifications.

Phase 2 (14 docs)

MEC001 3GPP 3rd Generation Partnership Project DNS Domain Name System IP Internet Protocol MEC Multi-access Edge Computing NFV Network Functions Virtualisation RAN Radio Access Network UE User Equipment VM Virtual Machine

MEC002 API Application Programming Interface BYO Bring Your Own DSRC Digital Short-Range Communications EAB Edge Accelerated Browser GNSS Global Navigation Satellite System GPRS General Packet Radio Service GPS Global Positioning System GTP GPRS Tunnelling Protocol HTTP Hyper Text Transfer Protocol IM Instant Messaging LAN Local Area Network NTP Network Time Protocol PBX Private Branch Exchange PTP Precision Time Protocol QCI Quality Class Indicator QoE Quality of Experience RAT Radio Access Technology SLA Service Level Agreement SMS Short Message Service SPID Subscriber Profile ID TCP Transmission Control Protocol TEID Tunnel Endpoint ID VNF Virtualised Network Function

MEC003 CFS Customer Facing Service NFVI-PoP Network Functions Virtualisation Infrastructure Point of Presence OSS Operations Support System

MEC010-2 CPD Connection Point Descriptor DNS Domain Name System FQDN Fully Qualified Domain Name FTP GRE Generic Routing Encapsulation GTP GPRS Tunnelling Protocol GTP-U GPRS Tunnelling Protocol for User plane IP Internet Protocol MAC Media Access Control MECO MEC Orchestrator MECPM MEC Platform Manager QCI QoS Class Identifier RNIS Radio Network Information Service URL Uniform Resource Locator

4/7 MEC(18)000003r1

MEC011 API Application Programming Interface DSCP Differentiated Services Code Point FQDN Fully Qualified Domain Name GRE Generic Routing Encapsulation GTP GPRS Tunnelling Protocol HTTP HyperText Transfer Protocol IETF Internet Engineering Task Force JSON Javascript Object Notation MAC Media Access Control MECPM MEC Platform Manager MQTT Message Queue Telemetry Transport NTP Network Time Protocol PTP Precision Time Protocol QCI Quality Class Indicator REST Representational State Transfer RFC Request For Comments RNI Radio Network Information RPC Remote Procedure Call TC Traffic Class TLS TOD Time of Day URI Uniform Resource Indicator UTC Coordinated Universal Time XML eXtensible Markup Language

MEC012 3GPP 3rd Generation Partnership Project API Application Programming Interface ECGI E-UTRAN Cell Global Identifier E-RAB E-UTRAN Radio Access Bearer E-UTRAN Evolved Universal Terrestrial Radio Access Network GTP GPRS Tunnelling Protocol GTP-U GPRS Tunneling Protocol-User plane GW Gateway HTTP Hypertext Transfer Protocol HTTPS HTTP over TLS IE Information Element IP Internet Protocol JSON Javascript Object Notation MCC Mobile Country Code MMEC MME Code MNC Mobile Network Code OAI Open API Initiative PLMN Public Land Mobile Network QCI Quality Class Indicator QoS RAB Radio Access Bearer REST Representational State Transfer RFC Request For Comments RNI Radio Network Information RNIS Radio Network Information Service RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality SGW Serving Gateway TEID Tunnel End Point Identifier TLS Transport Layer Security TMSI Temporary Mobile Subscriber Entity UE User Equipment URI Uniform Resource Indicator UTC Coordinated Universal Time

5/7 MEC(18)000003r1

MEC013 ACR Anonymous Customer Reference API Application Programming Interface E-SMLC Evolved Serving Mobile Location Centre ID Identifier LS Location Service OMA Open Mobile Alliance REST Representational State Transfer SCF Small Cell Forum UE User Equipment URI Uniform Resource Identifier URL Uniform Resource Locator

MEC016 None

MEC021 None

MEC022 None

MEC024 None

MEC025 None

MEC027 None

MEC028 None

************************************************

Phase 1 (2 docs)

MEC014 API Application Programming Interface HTTP Hypertext Transfer Protocol IETF Internet Engineering Task Force UE User Equipment

MEC017 DNS Domain Name System DOPFR Dynamic Optimisation of Packet Flow Routing EM Element Manager ETSI European Telecommunications Standards Institute GS Group Specification GTP GPRS Tunnelling Protocol HOT Heat Orchestration Template IP Internet Protocol LCM Life Cycle Management MANO Management and Orchestration ME Mobile Edge MEAO Mobile Edge Application Orchestrator MEC Mobile Edge Computing MEO Mobile Edge Orchestrator MEPM Mobile Edge Platform Manager MEPM-V Mobile Edge Platform Manager - NFV 6/7 MEC(18)000003r1

NFP Network Forwarding Path NFV Network Functions Virtualisation NFVI Network Functions Virtualisation Infrastructure NFVO Network Functions Virtualisation Orchestrator NS Network Service NSD Network Service Descriptor OASIS Organisation for the Advancement of Structured Information Standards OSS Operations Support System PM Performance Management PNF Physical Network Function PNFD Physical Network Function Descriptor SFC Service Function Chaining TOSCA Topology and Orchestration Specification for Cloud Applications UE User Equipment VIM Virtualised Infrastructure Manager VL Virtual Link VM Virtual Machine VNF Virtualised Network Function VNFC VNF Component VNFD VNF Descriptor VNFFG VNF Forwarding Graph VNFM Virtual Network Function Manager YAML YAML Ain't Markup Language

References

[MEC-specs] ETSI MEC website, http://www.etsi.org/deliver/etsi_gs/MEC/001_099

7/7