Networking

The present document identifies the requirements that should characterise an ontology for the semantic conceptualisation of information related to IP traffic measurements. The requirements are obtained through the analysis of use cases spanning across a variety of related application categories and domains of interest, as well as the consideration of additional qualitative needs, such as the protection of personal data. Additional inputs arise from user experience, as well as the 'GS/MOI-010' Work Item study, entitled "Report on information models for IP traffic measurement" . The general difficulty of setting limits to an ontology, taking concepts from outside is also dealt within the present document that states MOI focus on IP traffic measurement concepts and let's side ontologies dealing with other subjects, an easy way to link. Thus a rather practical approach to define MOI ontology will be laid so that further QoS, traffic monitoring and Internet governance issues can be built on top of it by means of semantic tools.

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 F5G Use Cases document ETSI GR F5G 002 has defined many use cases for F5G. To support these use cases, the network architecture will need to be simple, agile, optimized and intelligent. The present document defines the F5G E2E network architecture and related network node requirements, including Customer Premise Network (CPN), Access Network and Aggregation Network. F5G takes SDN/NFV into account for the network's control layer. The F5G architecture will explore new network features like a seamless connection between Optical Transport Network and Access Network, E2E full-stack slicing, etc. The F5G end-to-end management architecture is considered out of scope for the present document. The present document also specifies technical requirements for the network nodes and elements in the architecture. The focus will be on Telecommunication networks in particular.

This Recommendation describes the protocol for managing capability exposure APIs in IMT2020 network. It includes signalling architecture, API management functions, signalling flows and their message format, and definition for management APIs. It also describes gap analysis and use cases for API management. This protocol can be used by network operators and third parties to manage capability exposure APIs.

Link Aggregation allows parallel point-to-point links to be used as if they were a single link and also supports the use of multiple links as a resilient load-sharing interconnect between multiple nodes in two separately administered networks. This standard defines a MAC-independent Link Aggregation capability and provides general information relevant to specific MAC types.

How Uniform Resource Name (URN) values are allocated in IEEE 802(R) standards is described in this amendment to IEEE Std 802(R)-2014. 

The Recommendation X.1044 analyses security challenges and threats on Network Virtualization, and provides the security requirements on physical resources layer, virtual resources layer and LINP layer in Network Virtualization (NV).

ISO/IEC 20922:2016 is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.

The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:

Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
A messaging transport that is agnostic to the content of the payload.
Three qualities of service for message delivery:
"At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
"At least once", where messages are assured to arrive but duplicates can occur.
"Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied

ISO/IEC 19464:2014 defines the Advanced Message Queuing Protocol (AMQP), an open internet protocol for business messaging. It defines a binary wire-level protocol that allows for the reliable exchange of business messages between two parties. AMQP has a layered architecture and the specification is organized as a set of parts that reflects that architecture.

Part 1 defines the AMQP type system and encoding.
Part 2 defines the AMQP transport layer, an efficient, binary, peer-to-peer protocol for transporting messages between two processes over a network.
Part 3 defines the AMQP message format, with a concrete encoding.
Part 4 defines how interactions can be grouped within atomic transactions.
Part 5 defines the AMQP security layers.

IEC 61784-1:2019 defines a set of protocol specific communication profiles based primarily on the IEC 61158 series, to be used in the design of devices involved in communications in factory manufacturing and process control. This fifth edition cancels and replaces the fourth edition published in 2014 it constitutes a technical revision. The main changes are:
• update of the dated references to the IEC 61158 series, to IEC 61784 2, to the IEC 61784 3 series, to the IEC 61784-5 series and to IEC 61918 throughout the document;
• update of selection tables CPF 2, CPF 4 and CPF 8

IEC 61158-1:2019 specifies the generic concept of fieldbuses. This document presents an overview and guidance for the IEC 61158 series explaining the structure and content of the IEC 61158 series, relating the structure of the IEC 61158 series to the ISO/IEC 7498-1 OSI Basic Reference Model and showing how to use parts of the IEC 61158 series in combination with the IEC 61784 series. It also provides explanations of some aspects of the IEC 61158 series that are common to the type specific parts of the IEC 61158 5 including the application layer service description concepts and the generic fieldbus data types.