Provides insights on ETSI GANA Knowledge Planes (KPs) Driven Networking in Autonomic/Autonomous Networking (ANs) for Networks that exhibit features such as self-* operations such as self-adaptation, self-optimization, self-monitoring, self-protection and self-defense objectives for the network and services; Establishes relationships between Autonomics, Cognition and Autonomous Network Behaviour; Standardization in this area of ANs.
The present document allows application developers to describe the status of devices as resources on oneM2M-based platform in various ways. Thus different application developers can create different resource trees even when they build the same kinds of applications. Moreover when handling the same kinds of devices from different vendors on M2M platforms, application developers may create disunited resource trees without common information model.
This work item will analyse and define the type of OAM functions for VNFs that can be generalized and be provided as a “generic function” supporting the provisioning, connectivity, configuration and monitoring of VNFs on a virtualized platform. The work item will also determine possible solutions to realize such generic OAM functions, e.g., by leveraging PaaS capabilities. The result report will include, if necessary, recommendations for requirements and architectural enhancements. The resulting deliverable will be informative.
This work item will study multi-tenancy related use cases for NFV to remove the gap between the existing IFA010 general functional requirements on multitenancy management and the missing requirement details regarding NFV elements consumed by different tenants. It will also take into consideration possible relation with Release 3 features like multi-domain NS provisioning, security orchestration. Key issues on multi-tenancy in NFV (e.g. tenant-dependent LCM, tenant dependent resource management, traffic separation, ..) will be identified and analyzed for concluding the recommendations.
The Pan-European Mobile Emergency Application (PEMEA) architecture provides the requirements and architecture for a solution to provide emergency application interconnection. It specifies the protocols and procedures enabling interoperable implementations of the architecture and provides extension points to enable new communication mechanisms as they evolve.
The present document addresses the requirements for communications between the authorized representatives who can be involved in the responses and actions when handling an emergency. It describes the functional requirements for communications between the authorized representatives involved in the responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the specific local, regional or national organizations and diagrams of relations between authorized representatives. It follows from this that adaptations will have to be done when implementing the present document at a local level. Furthermore, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices that support communications between authorities during emergencies.
A standardized framework for the Smart Appliances Reference Ontology based on the results of a European Commission Study Group on Smart Appliances ontologies and of a Specialist Task Force on the maintenance and evolution of the Reference Ontology taking into account all the interest of the relevant stakeholders.
The present document is a study of interworking between oneM2M Architecture and 3GPP Rel-13 architecture for Service Capability Exposure as defined in the release 13 version of ETSI TS 123 682 [i.5]. The key objective and value is analyzed and described. The document also investigates the potential solution in oneM2M by evaluating the existing technical solutions.
The present document outlines the motivation for the deployment of IPv6 in enterprises, the objectives, the benefits, the risks, the challenges, the technology guidelines, the different choices that arise when designing IPv6-only or dual-stack enterprise network, step-by-step process, the addressing plan, and the milestones.
The document aims to define the protocols and interfaces of LTN systems. It goes along with the document GS LTN 002 [5] on LTN functional architecture.
The scope of the present document is to specify the minimum set of key scenarios for the Next Generation Protocols (NGP), Industry Specific Group (ISG).