ETSI

The document focuses on mobility support provided by Mobile Edge Computing. It documents mobility use cases and end to end information flows to support UE and Application mobility for Mobile Edge Computing. When necessary, the document describes new mobile edge services or interfaces, as well as changes to existing mobile edge services or interfaces, data models, application rules and requirements. The document identifies gaps to support mobility that are not covered by existing WIs, documents these gaps and recommends the necessary normative work to close these gaps.

The document focuses on identifying the MEC features to support V2X applications. It collects and analyses the relevant V2X use cases (including the findings from external organizations), evaluates the gaps from the defined MEC features and functions, and identifies the new requirements including new features and functions. When necessary, this may include identifying new multi-access edge services or interfaces, as well as changes to existing MEC services or interfaces, data models, application rules and requirements. It will also recommend the necessary normative work to close these gaps if identified.

The document focuses on identifying the MEC functionalities to support network slicing. It first analyses the relevant network slicing concepts as defined by external organizations. Next, it collects relevant use cases based on the identified network slicing concepts when applied in the context of MEC and it evaluates the gaps from the defined MEC functional elements. When necessary, the document identifies new MEC functionalities or interfaces as well as changes to existing MEC functional elements, interfaces and requirements. It will also recommend the necessary normative work to close these gaps if identified.

The document focuses on identifying the additional support that needs to be provided by MEC when MEC applications run on alternative virtualization technologies, such as containers. The document collects and analyses the use cases relating to the deployment of such alternative virtualization technologies, evaluates the gaps from the currently defined MEC functionalities, and identifies new recommendations. As ETSI NFV is also working on alternative virtualization technologies, the MEC work should be aligned with NFV where applicable. The document also recommends the necessary normative work to close any identified gaps.

The document describes the key issues, solution proposals and recommendations for MEC integration into 3GPP 5G system. The following aspects are addressed: MEC System interactions with the 5G System, including the correspondence of the current MEC procedures to procedures available in 3GPP 5G system specification, options for the functional split between MEC and 5G Common API framework, realization of MEC as 5G Application Function(s). In addition the document addresses the scope and the preferred way of proceeding with the identified future technical work, as well as the identification of any missing 5G system functionality for MEC integration.

The document focuses on the Traffic Management multi-access edge service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The document specifies the necessary API with the data model and data format.

The document contains the API definition for the lifecycle management of user applications over the Mx2 reference point between the device application and the User Application LifeCycle Management Proxy (UALCMP) in the MEC system. The document covers the following lifecycle management operations: user application look-up, instantiation and termination. In addition, a mechanism is specified for the exchange of lifecycle management related information between the MEC system and the device application. The intended key audience of the present document are the application developers for the MEC system, since this API provides them with a method to manage their applications.

To investigate security and privacy issues for On-board Weighing Equipment.

To prepare a Threat, Vulnerability and Risk Assessment for On-board Weighing Equipment