Big Data

Big data based on cloud computing provides the capabilities to collect, store, analyze, visualize and handle varieties of large volume datasets, which cannot be rapidly transferred and analyzed using traditional technologies. e.g. Big Data as a Service (as defined in [ITU-T Y.3600], big data as a service (BDaaS) is a cloud service category in which the capabilities provided to the cloud service customer are the ability to collect, store, analyse, visualize and manage data using big data.). Data storage, analysis, calculation and other data services based on the big data platform, are developing rapidly in recent years.

This recommendation aims to specify security protection measures of big data platform, regulate security protection measures in the construction and operation process of big data platform, and promote the development of big data services. These measures in the framework will take into account on the national legal and regulatory obligations in individual member states in which the big data platforms operate. The work will proceed using the methodology standardized in clause 10 of Recommendation ITU-T X.1601.

This Recommendation is security guidelines of lifecycle management for telecom Big Data. This recommendation covers as follows:

- Introduction the use cases in telecom Big Data;

- Analyze the security risks of lifecycle management for telecom Big Data;

- Specify the security guidelines of lifecycle management for telecom Big Data.

The standard defines specific methodologies to help users certify how they approach accessing, collecting, storing, utilizing, sharing, and destroying child and student data. The standard provides specific metrics and conformance criteria regarding these types of uses from trusted global partners and how vendors and educational institutions can meet them.
You can look here for a preview of the Standard Document

Development Status: Under development
 

The present document specifies the structure and format of a VNF package file and its constituents, fulfilling the requirements specified in ETSI GS NFV-IFA 011 [1] for a VNF package.

The present document specifies a data model for NFV descriptors, using the TOSCA Simple Profile in YAML, fulfilling the requirements specified in ETSI GS NFV-IFA 011 and ETSI GS NFV-IFA 014 for a Virtualised Network Function Descriptor (VNFD), a Network Service Descriptor (NSD) and a Physical Network Function Descriptor (PNFD). The present document also specifies requirements on the VNFM and NFVO specific to the handling of NFV descriptors based on the TOSCA Simple Profile in YAML specification.

The present document describes the Single Illumination System, which allows to deliver Parent Signals for direct reception by consumer receivers and, at the same time, for a deterministic generation of daughter streams for terrestrial retransmission. Parent Signals can be provided to the daughter site via all defined TS-based DVB means - be it satellite, cable or terrestrial. Metadata may be provided as part of the Parent Signal(s) (called "in-band" in the present document). Part of the metadata may also be provided "out-of-band".

The present document provides a contribution to the evolution of network performance testing towards a professional degree of transparency. This begins with a consistent framework of definitions and technical terms. The elements of the testing process are then described within this context.

Apart from the obvious direct parameters of throughput testing, such as time windows or transferred data volumes, there are numerous other elements which can have an impact on data values obtained. In this sense, methodology and definition of metrics cannot be decoupled from each other. The process starts with selecting the boundaries to the system under test, i.e. insertion or demarcation points. Next comes the way the system under test is accessed. For instance, if the test is run over a radio access network using a mobile device such as a smartphone, the type and degree of influence needs to be assessed. The type of stimulus is likewise important, such as the protocol type, the structure of data traffic (e.g. TCP or UDP based), and the number of parallel connections. Depending on these selections, other choices also become parameters for testing. An example would be to use some kind of real application to create a particular type of traffic, versus using synthetically generated traffic.

The present document's scope is to provide guidance on OTT video streaming testing approach with a set of minimum desired and most meaningful QoE centric QoS parameters along with recommendations to create a figure of merit quantifying the OTT video streaming session quality, where possible. In addition, the set of introduced QoE centric QoS parameters aim to help with the identification of the possible roots of video quality degradation. The present document also offers means to understand aspects related with network and services optimization and troubleshooting, such as the trade-off between bandwidth usage or controlled throttling and end-to-end video quality.

The present document provides a framework for concurrent tests of multiple services, using a top-level approach which is also modular and scalable with respect to new services. Also, the framework explicitly integrates measurement methodology, in particular reproducibility aspects.

The present document summarizes the results of an analysis of the impact of the upcoming 5G on existing QoS metrics, and the question if extensions or modifications of the portfolio of QoS parameters portfolio are required to capture respective properties of 5G.

The analysis starts with a summary of features and properties of 5G which can be expected to be relevant for QoS assessment.
The first question addressed is if there are features of the 5G roadmap - as far as technically stable as of the time of publication, or reasonably stable projections - which constitute new services which would then require new sets of QoS parameters. The second question is in what way projected 5G properties may require adaptations with respect to measurement methodologies, computation, or usage of existing QoS parameters.

The present document discusses Quality of Service (QoS) aspects of services related to the Internet of Things (IoT) ecosystem from an end-to-end perspective; a strict end-user, service-oriented point of view. Here, end-to-end is understood as "from a service user/terminal/provider to a service user/terminal/provider".

The discussion deals with two questions. The first question is if the existing framework for QoS parameter definitions and methodologies is sufficient to also include the IoT angle of view. The second question is if the existing portfolio of QoS parameters needs extensions or adaptations.

This draft Recommendation presents the high-level requirements and reference framework of Smart City Platform (SCP). The SCP is a fundamental platform supporting all the services and applications of a smart city, with the objective to improve quality of life, provide urban operation and services for the benefit of the citizens while ensuring city sustainability.