Networking

The document contains a description of scenarios, use cases, and definition of requirements for the autonomic/self-managing future internet. Scenarios and use cases selected in the present document reflect real-world problems which can benefit from the application of autonomic/self-management principles. Two types of high-level requirements are covered:

1. basic requirements that enable to derive an architectural reference model for introducing Autonomic Management & Control (AMC) of networks (resources, protocols, parameters) and services in various reference network architectures;
2. specific requirements pertaining to aspects requiring "automation" and "behaviour" in a particular network/service management problem.

The present document aims at providing recommendations for the introduction of autonomics (management and control intelligence) into the fixed broadband access and aggregation networks specified in the Broadband Forum (BBF) Architecture specifications. To this effect, it covers the instantiation of the reference model for Autonomic Networking, Cognition and Self-Management, called GANA (Generic Autonomic Networking Architecture), starting from the reference architecture defined in BBF TR 101, and considering also BBF TR 178 and BBF TR 317 reports. It superimposes GANA Decision Elements (DEs) into nodes/devices and the overall BBF network architecture, so that the DEs and their associated control-loops can be further designed to perform autonomic management and control of the specific resources (Managed Entities) in the target architecture. Based on this, the present document identifies the requirements for autonomic behaviours (Autonomics Functions/DEs) across the fixed broadband access and aggregation network segments of the BBF reference architecture and provides recommendations on where and how the GANA Functional Blocks (including DEs) should be instantiated. It further extends these recommendations to the virtualized manifestation of these segments considering their virtualized evolution in conjunction with SDN and NFV technologies. Finally, it also provides recommendations on the interworking and coordination between autonomic functions among GANA-BBF and GANA-3GPP (Core Network) domains, as well as recommendations on the Interworking and coordination between virtualized GANA-BBF and virtualized GANA-3GPP (Core Network) domains.

The Web of Things seeks to counter the fragmentation of the IoT through standard complementing building blocks (e.g., metadata and APIs) that enable easy integration across IoT platforms and application domains.
 
Thing Description:
 
Semantic vocabularies for describing the data and interaction models exposed to applications, the choice of communications patterns provided by protocols, and serialization formats suitable for processing on resource-constrained devices and transmission over constrained networks.
 
Scripting API:
 
Platform-independent application-facing API for Thing-to-Thing interaction and Thing lifecycle management.
 
Binding Templates:
 
Example mappings from the abstract messages to specific common platforms and protocols in collaboration with the corresponding organizations.
 
Security and Privacy:
 
Cross-cutting policies and mechanisms integrated into the other building blocks to describe and implement security and privacy policies to enable secure and safe interaction across different IoT platforms.
 
Of these, the first deliverable, the normative Thing Description standard, is central, with the other items playing supporting roles. The Scripting API is also normative but simply serves to provide a standardized and convenient way to access the functionality of the Thing Description from a programming language in order to build concrete applications. Binding Templates are informational and provide mappings to concrete protocols. This deliverable also provides templates for describing further protocol mappings through the Thing Description. The Security and Privacy deliverable is normative, but while considered separately, its implementation is integrated into the other deliverables.

CoRE provides a framework for resource-oriented applications intended to run on constrained IP networks. Such networks have limited packet sizes, may exhibit a high degree of packet loss, and may have a substantial number of devices that may be powered off at any point in time but periodically "wake up" for brief periods of time.

• The CoRE working group will define a framework for a limited class of applications: those that deal with the manipulation of simple resources on constrained networks.
• This includes applications to monitor simple sensors (e.g. temperature sensors, light switches, and power meters), to control actuators (e.g. light switches, heating controllers, and door locks), and to manage devices.

Interception techniques need to become more effective and fail-safe as endpoints become inherently more secure. The IETF Captive Portal Interaction (CAPPORT) Working Group will define secure mechanisms and protocols to:

• Allow endpoints to discover that they are in this sort of limited environment.
• Provide a URL to interact with the Captive Portal.
• Allow endpoints to learn about parameters of their confinement.
• Interact with the Captive Portal to obtain information such as status and remaining access time.
• Optionally, advertise a service whereby devices can enable or disable access to the Internet without human interaction. (RFC 7710 may be a full or partial solution to the first two bullets).

The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses, IPv6 prefixes, IP protocol stack and other parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132.
DHCPv6 is currently a Proposed Standard and is being updated. The WG plans to advance the DHCPv6 protocol to Internet standard. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are generally outside of scope for the DHC WG.

The ITU-T Focus Group on Machine Learning for Future Networks including 5G was established by ITU-T Study Group 13 at its meeting in Geneva, 6-17 November 2017. The Focus Group will draft technical reports and specifications for machine learning (ML) for future networks, including interfaces, network architectures, protocols, algorithms and data formats.

We are responsible for the identification of European regulatory requirements for cellular systems developed by the Third Generation Partnership Project (3GPP™), and for developing Harmonised Standards and related ETSI standards for GSM™, International Mobile Telecommunications (IMT) systems for cellular and technologies evolving from them (including IMT Advanced but excluding Digital Enhanced Cordless Telecommunications (DECT^TM)).

We provide the regulatory standards needed to support the deployment of GSM, Universal Mobile Telecommunications System (UMTS™) and LTE™ networks in Europe

We are responsible for standardization to support the development and implementation of Intelligent Transport Systems (ITS) service provision across the network, for transport networks, vehicles and transport users, including interface aspects, multiple modes of transport and interoperability between systems.

We are helping to accelerate the introduction of ITS services and applications and to maximize their benefits by developing common European standards and technical specifications to enable interoperability. TC ITS is leading the drive to achieve international standards.

We are responsible for a range of radio product and electromagnetic compatibility (EMC) standards and the overall co-ordination of radio spectrum matters.

For many years we have provided more than 75% of the Harmonised Standards required under the R&TTE Directive until the arrival of the Radio Equipment Directive in June 2016. The RED has implications for ETSI’s radio work, especially in relation to receivers, software defined radio and cognitive radio. After review and alignment, TC ERM is currently maintaining nearly 150 Harmonised Standards related to the RED.
Since the scope of the RED is broader than the R&TTE Directive, we develop new Harmonised Standards in areas such as radio and TV broadcast receivers, equipment below 9 kHz and radio determination equipment which were not addressed previously.

The EMTEL Special Committee is responsible for the capture of European requirements concerning emergency communication services, covering typically the four scenarios in case of an emergency e.g. communication of citizens with authorities, from authorities to citizens, between authorities and amongst citizens. In addition, EMTEL deals with topics like location (e.g. Advanced Mobile Location), NG112, communications involving IoT devices in emergency situations and alerting.

We are responsible for defining the equipment engineering, the bonding and grounding, the power supply interface and environmental aspects for telecommunication infrastructures and equipment.

We manage various engineering aspects of telecommunication equipment in different types of installations. These include:

• environmental conditions (climatic, thermal, active substances, acoustic, etc.);
• equipment practice (the physical requirements of racks, sub-racks and cabinets including thermal matters);
• power supply and grounding (power interface specifications, power and grounding distributions);
• eco-environmental matters (energy efficiency, environmental impact analysis, alternative energy sources);
• environmental matters associated with mobile Information and Communications Technologies (ICT) devices.

Much of our work on energy efficiency supports European Commission (EC) policies, regulation or legislation.
We also comprise representatives from the Telecommunication network operators and equipment suppliers of Europe, China, Japan and the US.