ETSI

The present document provides reference test material and test results for improved usability of technologies in 3GPP TS 26.118: Virtual Reality (VR) profiles for streaming applications. The specification 3GPP TS 26.118 includes several VR media profiles for video and a single media profile for audio with different configuration options. The specification focuses primarily on interoperability requirements for VR360 applications, but does not address performance characterization of the solutions. In order for content providers and the rest of the ecosystem to be able to select and configure the technologies defined in 3GPP TS 26.118 and to generate content for streaming applications, collecting such information would be most valuable.

The present document provides an overview of delivery of 3D graphics of games that are running on a high-performance server to client devices that would otherwise not have the resources to run these games natively. The present document describes the use cases, high level requirements and different solution approaches, and identifies the main area(s) where standardization work would be needed. Exploring the nature and content of what is going to be exchanged between servers and clients constitutes the main topic of the present document The primary aim for this technology is to enable casual gaming scenarios, and it is not the primary aim to try to satisfy hardcore gamers, since we have to be realistic about what can be achieved with the current state of networking and server technology. Because of the nature of the content and in order to focus on feasible solutions, we may exclude certain type of network connections to be used, such as using "unreliable" or high-latency wireless connections such as 802.11b/g. We expect to have a broadband connection between the client and the server, without too many intermediate hops. In the present document we do not address deployment issues, such as integration into a Content on demand infrastructure (e.g. user registration, pricing, purchasing), or integration into a QoS framework (e.g. prioritization of gaming streams compared to other types of streams). Also, use cases and synchronization issues related to multi-player gaming, whereby different connection speeds/types could result in different response times, are out of scope of the present document.

The Use Cases Document shall provide an overview of possible application scenarios in which Quantum Key Distribution (QKD) systems ([i.1]) can be used as building blocks for high security Information and communication technology (ICT) systems.

The present document is intended to specify an Application Programming Interface (API) between a QKD key manager and applications. The function of a QKD key manager is to manage the secure keys produced by an implementation of a QKD protocol and to deliver the identical set of keys, via this API, to the associated applications at the communication end points.

The present document gives specifications and procedures for the characterization of optical components for use in QKD systems. Examples of specific tests and procedures for performing such tests are given. Due to their importance in the security of a QKD system, particular attention is given to active optical components such as optical sources and single photon detectors.

The present document describes the main communication resources involved in a QKD system and the possible architectures that can be adopted when performing a QKD deployment over an optical network infrastructure. The scope of the present document is restricted to QKD deployments over fibre optical networks. Architectural options are also restricted to point-to-point communication.

The present document specifies a communication protocol and data format for a quantum key distribution (QKD) network to supply cryptographic keys to an application.

The present document provides a definition of management interfaces for the integration of QKD in disaggregated network control plane architectures, in particular with Software-Defined Networking (SDN). It defines abstraction models and workflows between a SDN-enabled QKD node and the SDN controller, including resource discovery, capabilities dissemination and system configuration operations. Application layer interfaces and quantum-channel interfaces are out of scope.

SAREF4CITY is an extension of SAREF for the Smart Cities domain. This extension has been created by investigating resources from potential stakeholders of the ontology, such as standardization bodies, associations, IoT platforms and European projects and initiatives. Taking into account ontologies, data models, standards and datasets provided by the identified stakeholders, a set of requirements were identified and grouped in the following categories: Topology, Administrative Area, City Object, Event, Measurement, Key Performance Indicator, and Public Service.

SAREF4INMA focuses on extending SAREF for the industry and manufacturing domain to solve the lack of interoperability between various types of production equipment that produce items in a factory and, once outside the factory, between different organizations in the value chain to uniquely track back the produced items to the corresponding production equipment, batches, material and precise time in which they were manufactured.

SAREF4SYST defines Systems, Connections between systems, and Connection Points at which systems may be connected.

The Smart Applications REFerence ontology (SAREF) is intended to enable interoperability between solutions from different providers and among various activity sectors in the Internet of Things (IoT), thus contributing to the development of the global digital market.