ISG MEC Proposal September 1st 2014

page 1 of 11

From: Founding members of an ISG on Mobile-edge Computing (MEC) To: ETSI Director General Subject: Proposal to create ISG MEC (Mobile-Edge Computing)

1 Decision/action requested

The Director-General is requested to approve the creation, Terms of Reference, and Membership Agreement for an MEC ISG; and to appoint Nurit Sprecher (Nokia Networks) as

Convenor for the first two meetings.

2 References

TWP clause 3 Operation of Industry Specification Groups TWP clause 3.2 Creation and Termination of an Industry Specification Group TWP Annex D 3 Requirements for an Industry Specification Group

3 Rationale

Mobile-edge Computing provides IT and cloud-computing capabilities within the RAN (Radio Access Network) in close proximity to mobile subscribers. Located at the base station or at the Radio Network Controller (RNC), it also provides access to real-time radio and network information (such as subscriber location, cell load, etc.) that can be exploited by applications and services to offer context-related services; these services are capable of differentiating the mobile broadband experience. For application developers and content providers, the RAN edge offers a service environment with ultra-low latency and high-bandwidth as well as direct access to real-time radio network information. Mobile-edge computing allows content, services and applications to be accelerated, increasing responsiveness from the edge. The customer’s experience can be proactively maintained through efficient network and service operations, based on insight into the radio and network conditions.

Operators can open the radio network edge to third-party partners, allowing them to rapidly deploy innovative applications and services towards mobile subscribers, enterprises and other vertical segments. Proximity, context, agility and speed can be translated into value and can be exploited by mobile operators, service and content providers, Over the Top (OTT) players and Independent Software Vendors (ISVs), enabling them to play complementary and profitable roles within their respective business models and allowing them to monetize the mobile broadband experience.

This environment can create a new value chain and an energized ecosystem comprising application developers, content providers, OTT players, network equipment vendors and mobile operators. Based on innovation and business value, this value chain will allow all players to benefit from greater cooperation.

The intention is to foster dissemination of the deliverables produced by the ISG MEC in order to develop favorable market conditions which will create sustainable business for all players in the value chain, and to facilitate global market growth.

ISG MEC Proposal page 2 of 11

The goals of the ISG MEC are to:

Create a standardized, open environment which will allow the efficient and seamless integration of third-party applications across multi-vendor Mobile-edge Computing platforms. This will ensure that the vast majority of the customers of a mobile operator can be served.

Enable and accelerate the development of edge applications across the industry, increasing the market scale and improving the market economics.

Address regulatory and legal requirements.

4 Terms of Reference for ETSI ISG MEC [TWP D.3, Part Aa)]

4.1 Scope

The purpose of the ISG MEC is to produce (Standards Track Deliverables) interoperable and deployable Group Specifications that will allow the hosting of third-party applications in a multi-vendor Mobile-edge Computing environment.

The architectural blueprint presented in the white paper ((ETSI/BOARD(14)99_xy) forms the basis for the work in the ISG and the scope of the first release. The scope of the first release is restricted and includes the following elements:

Application platform services and Application Programming Interfaces (APIs):

o Communication services that allow applications hosted on the same server to communicate with each other and with the platform services;

o Service registry which is used to define the services that are available on the platform. It is also used by applications to locate the end points for the services they require and to publish their own service end points for other applications to use.

o Radio network information API, providing low-level radio and network parameters that can be used by authorised applications hosted on the platform to calculate and present the following high-level and meaningful parameters: Cell-ID, location of the subscriber, cell load and throughput guidelines;

o Traffic offload service which is used to off-load selective, policy-based, user-data streams to an application hosted on the platform.

Virtual Machine (VM) Service Level Agreement (SLA): description and negotiation of cloud services based on a standard unit of measurement; supervision mechanisms for the availability and the integrity of the VMs, platform services and APIs; Mechanisms for trouble shooting

MEC application platform management interface

The ISG MEC will produce an (informational) ontology containing the terminology that will be used consistently by the set of MEC specifications, as well as a gap analysis, identifying critical functional elements and techniques that need to be standardized to provide greater value;

In addition, the following (normative) specifications will be developed:

Requirements;

Framework and reference architecture;

Specifications relating to the platform services and the APIs.

ISG MEC Proposal page 3 of 11

As a general guideline, the ISG MEC will use and refer to existing specifications (both ETSI and external specifications) where appropriate.

In addition to technical (normative) specifications, the ISG MEC will advance mobile-edge computing in the industry, accelerate the adoption of the concept and the standards and address legal and regulatory requirements. The group will produce (informative) reports in the form of white papers and tutorials and will arrange workshops and events.

4.2 Membership

Membership is restricted in accordance with Clause 3.4 of the ETSI Technical Working Procedures to ETSI Full/Associate members and applicants for Full/Associate membership, who have signed the ISG MEC agreement. Observers and non-members of ETSI may not become members of the ISG but may participate in the ISG according to the rules as described in the ISG MEC Participant Agreement (see clause 4.7.1 below). Participation of non-members of ETSI is subject to acceptance of the ISG Participant Agreement, and payment of a per-meeting participation fee as described in the ISG Participant Agreement. 4.3 Dues

Dues for membership and operation are fixed on an annual basis by the members, based on the costs the members anticipate to incur. Currently, no or minimal annual dues are anticipated. Observers and non-members of ETSI are required to pay a per-meeting participation fee as described in the ISG Participant Agreement. This per-meeting fee is set initially at €100 (excluding taxes) per person per meeting day. These fees may be modified by ETSI on consultation with the ISG MEC. 4.4 Duties and Rights of Members

Members and Participants have the duty to constructively cooperate on the development of ISG Group Specifications within the scope of the ISG MEC as described in clause 4.1.

Members have the right to cast their vote on the approval of a Group Specification when necessary, and in other instances when decisions by the members are required. Members have the right to appeal directly to the ETSI Board to challenge a Chairman's decision and shall inform the ISG Chairman and the ETSI Director General beforehand.

Voting is by weighted individual vote, and voting rights are dependent on regular participation in the ISG MEC: members are required to have been present in at least one of the three meetings (face-to-face or remote/conf call) preceding any vote in order to have the right to vote. 4.5 Preparation of Group Specifications

Group specifications are prepared within the ISG or working group. The working groups are chaired by working group chairs, who are appointed according to the rules of operation of the ISG. All draft specifications must be approved by the ISG members using the decision making process detailed in the rules of operation of the ISG. If a specification is prepared in a working group and fails to be approved by the members, it is referred back to the working group.

ISG MEC Proposal page 4 of 11

4.6 Detailed deviations from the ETSI Technical Working Procedures (TWP)

In the following, deviations from the applicable ETSI TWP as agreed by the members of ISG MEC, including deviations to the ETSI TWP made in the ISG MEC Membership Agreement, are stipulated. Section 4.6 is included in these Terms of Reference only for information as the prevailing document in respect of changes to the TWP is the ISG MEC Membership Agreement. 4.6.1 Participation in the work of the Industry Specification Group (extension of TWP 3.4)

Observers or non-members of ETSI must agree to the ISG MEC Participant Agreement in order to be authorized to participate. The Participant Agreement will be terminated if the participant has not participated in at least one meeting of the ISG in a 12 month period. A revocation notice under article 9.1 (c) of the ISG Participant Agreement is sent to the participant in this case. The ISG MEC Chairman will periodically review the participation record of authorized Participants.

In addition, access to meeting documents, mailing lists etc. will be removed from authorized Participants if they fail to participate in, or register and pay participation fees for two successive meetings. Such access will be restored upon registration for a subsequent meeting of the ISG MEC. 4.6.2 Convening an ISG meeting (TWP 3.5)

4.6.2.1 Invitation to an Industry Specification Group MEC meeting (TWP 1.5.1)

The invitation to an Industry Specification Group MEC meeting and the necessary logistical information shall be disseminated by the hosting organization at least 30 days before the meeting to all on the Industry Specification Group MEC membership list (see clause 1.5.5). The first meeting of the Industry Specification Group MEC will be announced in a Collective Letter, with at least 30 days notice, by the ETSI Secretariat. 4.6.2.2 Agenda for an Industry Specification Group MEC meeting (TWP 1.5.2)

The draft agenda shall be disseminated by the responsible Chairman to all on the Industry Specification Group MEC membership list at least 30 days before a meeting. The draft agenda shall include details of draft ETSI deliverables for approval and officials for appointment. Any other subject matters where voting may be required shall also be included and indicated in the draft agenda. 4.6.2.3 Documentation for an Industry Specification Group MEC meeting (TWP 1.5.3)

Meeting documents shall follow a consistent numbering system as shown in the following example: ETSI/MEC(nn)x_filename This numbering system has three logical elements: 1) ETSI: to indicate that it is an ETSI document; 2) MEC: the name of the ISG; 3) (nn): to indicate the year, e.g. (98); 4) x: a unique number of the document, appended with a revision number if applicable; 5) filename of the document

ISG MEC Proposal page 5 of 11

4.6.2.4 Registration for an Industry Specification Group MEC meeting (TWP 1.5.4)

Every Attendee shall register on arrival at each meeting. Each Attendee who represents an ISG MEC member or ISG MEC Participant organization shall declare the precise name of that organization. An Attendee may only represent one ISG MEC member or one ISG MEC Participant. 4.6.2.5 Maintaining an Industry Specification Group MEC membership list (TWP 1.5.5)

The ISG shall maintain a membership list within an email exploder list established specifically for that purpose. Any individual may join this email exploder list if he/she is a representative of an ETSI member that has signed the ISG MEC Member Agreement or the ISG MEC Participant Agreement and has an ETSI server user account, and those who join this email exploder list will be considered as being on the ISG MEC membership list. Failure to reconfirm the intention to remain on the email exploder list at regular intervals will result in removal from this email exploder list and thus from the ISG membership list. Note that lists are normally reviewed every six months. The ISG membership list shall be used for the dissemination of information and for the decision making within the ISG. 4.6.3 Decision making (TWP 3.7)

4.6.3.1 Principles of decision making (TWP 1.7.1)

The Industry Specification Group MEC shall endeavour to reach Consensus on all issues, including the approval of draft ETSI deliverables and the adoption of Group Specifications. If Consensus cannot be achieved, the Chairman can decide to take a vote which may be performed by a secret ballot. A vote may be conducted during an Industry Specification Group MEC meeting or by correspondence.

Where voting is used, vote results shall be evaluated by the Chairman on the basis of a weighted individual vote as described in Article 11 of the Rules of Procedure. ISG Participants do not have the right to vote.

Decisions concerning (i) the ISG Budget under Article 3.1(b) of the ISG MEC Agreement, (ii) Additional Costs under Article 3.1(c) of the ISG MEC Agreement, and (iii) the allocation of costs among members of the ISG MEC under Article 3.2 of the ISG MEC Agreement, require unanimous support of the ISG MEC members who are present and are eligible to vote, as defined below.

For all other decisions, except for the appointment of officials of the ISG MEC for which clause 3.3 of ETSI Technical Working Procedures applies, a proposal shall be deemed to be approved if 71 % of the votes cast are in favour. Abstentions or failure to submit a vote shall not be included in determining the number of votes cast.

For interpreting the result of an election for an ISG official, a simple majority of the votes cast shall be used (see the procedure in clause 4.6.3.1.3). 4.6.3.1.1 Voting during an Industry Specification Group MEC meeting

The following procedures apply for voting during an ISG or ISG working group meeting:

o before voting, a clear definition of the issues shall be provided by the chairman;

o voting members shall only be entitled to one vote per member;

o if a voting member has more than one representative present, only one representative may vote;

ISG MEC Proposal page 6 of 11

o if manual voting procedures are used, each voting member may only cast the vote once; if electronic voting procedures are used, votes may be changed prior to the closure of the vote;

o ISG members are only eligible to vote (voting members) if they have participated in at least one of the three meetings preceding any vote (working group and ISG plenary meetings combined);

o founding members of the ISG as identified in the ISG Agreement shall be eligible to vote during and up to the end of the first three meetings following the creation of the ISG. Thereafter they are subject to the above participation requirements as for all other members;

o voting by proxy is not permitted;

o there are no quorum requirements;

o voting shall be on the basis of a weighted individual vote;

o the result of the vote shall be recorded in the meeting report. 4.6.3.1.2 Voting by correspondence

The following procedures apply for voting by correspondence:

o before voting, a clear definition of the issues shall be provided by the Chairman and disseminated to all on the ISG membership list;

o the voting period shall be a minimum of 14 days, or a longer period defined by the ISG Chairman. The voting period or closing date shall be communicated to all on the Industry Specification Group membership list before the start of each vote;

o voting shall be on the basis of a weighted individual vote;

o ISG members are only eligible to vote (voting members) if they have participated in at least one of the three meetings preceding any vote (working group and ISG plenary meetings combined);

o founding members of the ISG as identified in the ISG Agreement shall be eligible to vote during and up to the end of the first three meetings following the creation of the ISG. Thereafter they are subject to the above participation requirements as for all other members;

o electronic voting only, shall be used for voting by correspondence;

o votes may be changed prior to the closure of the vote;

o there are no quorum requirements;

o at the end of the voting period the Chairman shall count the votes as described in clause .4.6.3.1 above;

o The result of the vote should be disseminated to everybody on the ISG membership list within 15 days.

4.6.3.1.3 Voting for the election of an ISG MEC official

For the purpose of electing any ISG MEC official the procedures given in clauses 4.6.3.1, 4.6.3.1.1 and 4.6.3.1.2 shall apply.

In the case where there is more than one candidate, a secret ballot shall be used. When, in the first ballot, no candidate has obtained more than 50% of the votes cast, a second ballot shall be held. The second ballot shall be held among the two candidates who have obtained the highest number of votes

ISG MEC Proposal page 7 of 11

in the first ballot. The candidate obtaining the higher number of votes in the second ballot is then elected.

The ISG MEC Chairman shall be responsible for the voting process and shall ensure that confidentiality is maintained.

If the vote is conducted during an ISG meeting only the final result shall be recorded in the meeting report.

If the vote is conducted by correspondence only the final result of the vote shall be disseminated.

4.6.3.2 Appealing against a Chairman's decision

Any member of the ISG who is against the Chairman's ruling on a vote may submit its case to the Board for decision. In such cases the member shall also inform the ISG MEC Chairman.

When the ISG MEC Chairman has made a ruling, his decision shall be taken as the basis for future operations, unless overturned by the Board.

5 ETSI field of interest [TWP D.3, Part Ab)]

ETSI plays an active role in the development and implementation of telecommunication standards. ETSI has developed open mobile communication standards, such as GSM, UMTS and LTE, independently and with partners in other regions. These specifications have been successfully adopted worldwide.

In addition, ETSI is currently working on the development of standards relating to cloud and internet technologies as well as end-to-end network architecture (which, among other aspects, also addresses Content Delivery Networks (CDN)).

The work of ETSI MEC aims to unite the telco and IT cloud worlds, providing IT and cloud-computing capabilities within the RAN (Radio Access Network). Creating this ISG and specifying the elements presented in clause 4.1 will enable third-party applications to be hosted in a multi-vendor Mobile-edge Computing environment. Proximity, context, agility and speed can be translated into value and exploited by mobile operators, service and content providers, OTT players and ISVs. These parties can play complementary and profitable roles within their respective business models, since they can monetize the mobile broadband experience.

Moreover, ETSI has an active ISG working on Network Function Virtualization (NFV) which is tasked with leveraging the standardized IT virtualization technology to consolidate multiple types of network equipment into standards-based, high-volume servers, switches and storage which could be located in data centres, network nodes and on the end user’s premises. With NFV, entire classes of network node functions can be virtualized into building blocks that may be connected or chained together to create communication services. The work on MEC will complement the work on NFV and the scope will be highly focused. MEC will enable third-party applications and services (Layer 4 and above) to be hosted ‘on top’ of a RAN element, i.e. above the network layer. These applications and services can benefit from being in close proximity to the customer and from receiving radio-network contextual information. For details on the scope, see clause 4.1 above.

The MEC specifications will amongst others refer to and reuse the NFV specifications when appropriate.

ISG MEC Proposal page 8 of 11

6 Reasons why overlapping or complementary elements (with reference to existing work or Terms of Reference of any existing Technical Committee or Project) are regarded as desirable [TWP D.3, Part Ac)]

The work of the ISG MEC complements current projects in ETSI and in other organizations, such as the 3rd Generation Partnership Project (3GPP), OpenStack, the LINUX Foundation, Distributed Management Task Force (DMTF), OASIS (Advancing Open Standards for the Information Society), Cloud Security Alliance (CSA), and Open Networking Foundation (ONF). The ISG MEC will align and liaise with the ETSI ISG NFV and with other related initiatives, reusing existing specifications where appropriate.

7 Timeline [TWP D.3, Part Ad)]

The lifetime of the ISG MEC is expected to be 18-24 months from setup.

The ISG MEC intends to hold an initial meeting within 30 days of formation. ISG MEC meetings and conference calls will be planned in order to generate ISG MEC Group Specifications and reports.

It is expected that meetings will take place about 4 times a year; each meeting may last 3 days.

After 18 months, the ISG MEC will issue a proposal regarding its future activities (maintenance of the specifications covered by the first release, work items for the second release, etc.).

The ISG MEC may extend its period of activity in order to maintain the specifications and to work on future releases, or it may be absorbed into an ETSI Technical Body. The options are to:

o Continue the ISG MEC for an extended period with revised Terms of Reference (ToR), or

o Absorb the work into a new Technical Body (new WG in a TC, new TC, new EP or new EPP). This would mean that all ISG participants would be required to become ETSI members, if they desire to continue working in such new Technical Body.

8 Chairmanship [TWP D.3, Part Ae)]

Nurit Sprecher (Nokia Networks) has accepted to stand as convenor for the first meetings. The Collective Letter announcing the first meeting will include a call for candidates for the Chairmanship. If it is not possible to appoint a permanent Chairman at the first meeting then the meeting shall appoint a convenor for the second meeting. The chairman, vice-chairmen and working group chairmen of ISG MEC are appointed for a period of maximum 2 years.

9 Resource requirements [TWP D.3, Part Af)]

No resource requirements, beyond the "basic administrative support" provided by the ETSI Secretariat to ISGs, have been identified. Further resource requirements may be identified from time to time by the ISG members, who will decide on the funding arrangements as required.

10 ETSI Secretariat resources [TWP D.3, Part Ag)]

“Basic administrative support” will be provided by the ETSI Secretariat, e.g.:

ISG MEC Proposal page 9 of 11

o info/meeting/document handling area on the ETSI Portal;

o document storage area on the ETSI DOCBOX server;

o e-mail lists provision

o entry of the Work Items into the WPM database (provided by ESP);

o processing/publication of ETSI Deliverables (providing they have respected the ETSI Drafting Rules);

o a support officer will be allocated to provide guidance and assistance to the ISG. Support for meetings will be provided when the meeting is held at the ETSI Headquarters, e.g.:

o meeting rooms in ETSI premises;

o meeting support for invitations, badges, etc in ETSI premises;

o tea/coffee in ETSI premises. Meetings held outside of the ETSI Headquarters shall be supported by the hosting member organization. In addition the secretary will support the ISG MEC in organizing workshops and possible interoperability events.

11 ISG Membership Agreement [TWP D.3, Part Ah)]

See the Annex of this document.

12 ETSI full and/or associate members having declared their willingness to provide resources [TWP D.3, Part Ba)]

The following members have indicated that they are willing to support the ISG (at least four required) and are considered to be the founding members of the ISG: DOCOMO Communications Laboratories Europe GmbH Huawei Technologies (UK) IBM Europe Intel Corporation (UK) Ltd Nokia Networks VODAFONE Group Plc

ISG MEC Proposal page 10 of 11

13 Planned deliverables and their delivery dates shall be identified [TWP D.3, Part Bb)]

The ISG MEC will provide an (informational) ontology containing the terminology that will be used consistently by the set of MEC specifications, and the following normative deliverables:

o Requirements

o Framework and reference architecture

o Specifications of the platform services and the APIs

The target delivery dates (completion) of the ISG MEC deliverables will be agreed in the first ISG meetings.

In addition, the ISG MEC will deliver an (informational) ontology presenting the critical functional elements and techniques that need to be standardized to provide greater value as was identified in the gap analysis task.

Based on the results of the gap analysis, the ISG MEC will liaise with the relevant organizations and ask them to develop the critical functional elements and techniques that need to be standardized in order to provide greater value. It is expected that the specifications for the supporting standards will be drawn up during 2016 and 2017. In addition to the specifications listed above, the ISG MEC will produce informative reports in the form of white papers and tutorials that will be used to advance Mobile-edge Computing in the industry, accelerate the adoption of the concept and the standards, and create a favourable legal and regulatory environment.

14 Internal organization [TWP D.3, Part Bc)]

The ISG MEC will be responsible for producing the ontology and the technical specifications;

An industry-enabling working group that will be tasked with advancing Mobile-edge Computing in the industry, accelerating the adoption of the concept and the standards, and creating a favourable legal and regulatory environment. The group will produce (informative) reports in the form of white papers and tutorials and will arrange workshops and events.

The ISG vice-chair will serve as the industry-enabling working group chairman and will report to the ISG.

15 Any committee/project-external ETSI resources required (i.e. outside those provided by the Industry Specification Group participants) shall be specified [TWP D.3, Part Bd)]

No additional resources such as experts or Special Task Forces have been identified. This will depend on the results of the initial work of the ISG MEC.

16 Maintenance arrangements for deliverables shall be specified [TWP D.3, Part Be)]

The maintenance of any deliverables will be assured by the ISG MEC. At the end of the work the ISG MEC will define the follow-on responsibility for any required maintenance.

ISG MEC Proposal page 11 of 11

17 The relationship with the ETSI Technical Organisation shall be specified (i.e. list the interfaces between the ISG and ETSI TBs) [TWP D.3, Part Bf)]

The ISG MEC intends to establish a liaison relationship with the following ETSI TBs and Partnership Project:

o EP E2NA/TC NTECH

o ETSI ISG NFV

o 3GPP

Depending on the way in which the work progresses, the ISG MEC may establish a liaison relationship with the following organizations:

o OpenStack,

o LINUX Foundation,

o Distributed Management Task Force (DMTF),

o OASIS (Advancing Open Standards for the Information Society),

o Cloud Security Alliance (CSA), and

o Open Networking Foundation (ONF).

If required, the ISG MEC may decide to establish additional liaison relationships.