The scope of this standard is to define an access layer independent protocol for on-board weighing equipment based on the requirements defined in COMMISSION IMPLEMENTING REGULATION (EU) 2019/1213.
The document provides a glossary of terms relating to the conceptual, architectural and functional elements within the scope of work on Multi-access Edge Computing. The purpose of this glossary is to ensure that all terminology defined in the document is used in a consistent way by all ETSI MEC deliverables as well as in wider industry discussions on Multi-access Edge Computing.
The document focuses on the support of regulatory requirements for Lawful Interception (LI) and Retained Data (RD) when implementing MEC into the network. It describes the problems, constraints, interfaces and additional capabilities needed for the different deployment scenarios, to ensure full support of LI and RD regulatory requirements when implementing MEC.
The document focuses on the MEC Location 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. It is to be noted that the actual data model and data format which is functional for the present API re-uses the definitions in "RESTful Network API for Zonal Presence" and "RESTful Network API for Terminal Location" published by the Open Mobile Alliance.
The present document focuses on the UE Identity functionality. It describes the related application policy information (including authorization, access control and traffic rule pattern format), information flows, required information and service aggregation patterns. The present document specifies the necessary API, data model and data format, considering existing API(s) if applicable.
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.
The document provides a specification for end-to-end MEC application mobility support in a multi-access edge system. The document describes information flows, required information and operations. The document also specifies the necessary API with the data model and data format.
The document focuses on the WLAN Access Information MEC service. It describes the message flows and the required information. The document also specifies the RESTful API with the data model.
The document describes a MEC service on Fixed Access Information for Fibre (e.g. G-PON, XG-PON, NG-PON2, XGS-PON), Cable (DOCSIS 3.1), xDSL, and Point-to-Point Fibre Ethernet access networks. It describes the information flows, required information, and as applicable, specifies the necessary operations, data model and data format. The present document also specifies the RESTful API.
The present document specifies a conformance assessment methodology for consumer IoT devices, their relation to associated services and corresponding relevant processes against ETSI TS 103 645 / ETSI EN 303 645, addressing the mandatory and recommended provisions as well as conditions and complements ETSI TS 103 645 / ETSI EN 303 645 by defining test cases and assessment criteria for each provision.
The present document gives a survey of the security features in the open source management software relevant to NFV, in particular OpenStackTM as the first case study. It addresses the OpenStack modules that provide security services (such as authentication, authorization, confidentiality protection, integrity protection, and logging) together with the full graphs of their respective dependencies down to the ones that implement cryptographic protocols and algorithms. It also identifies a set of recommendations on the use of and enhancements to OpenStack as pertinent to NFV.
