WP3 D.3.2 Technical specification of scenarios · D.3.2 ‐ Technical specification of scenarios ... Diego Bonini ALU‐I diego.bonini@alcatel‐lucent.com ... Blue Prints should

WP3

D.3.2 ‐ Technical specification of scenarios

Document Number: CONNECT‐CIP‐325094/SPECIFI/WP3/D3‐2/300613

Contractual Date of Delivery: 30/06/2013

Authors: Diego Bonini, Giorgio Parladori, WP3 Partners

Workpackage: WP3

Distribution / Type: CO

Version: 1.0

Total Number of Pages: 101

File: SPECIFI‐WP3‐D3.2

Abstract

D3.2 aims to collect technical requirements form Pilots in view of next WP3 activity, target to define the European Creative Ring (ECR) Architecture definition and realizations. Data collection will be mainly target on infrastructural aspects thinking that they are fundamental for defining future Pilot convergence towards ECR.

SPECIFI WP3 D.3.2 2/27

Executive Summary

Within WP3, D3.2 has the objective to specify the technical requirements with regard to ICT infrastructure and services needed to design the European Creative Ring architecture. Referring to the use cases defined in WP2, the relevant KPIs have to be identified and quantified. Furthermore additional KPI should be identified in order to guarantee the needed interworking between the platforms present in the three cities and possible new application that may be envisaged.

It is worth to know that similar activity is running in WP8 with the aim to use these technical requirements to manage the use case extension to other locations. In particular D8.1, together with D3.2 will be taken as input for the European Creative Ring architecture addressed in D3.1a/b.

In order to identify the ICT infrastructure requirements, a reference framework has to be identified, gathering existing requirements from WP2 (user requirements), WP4, 5, and 6 (pilot requirements), WP8 (requirements related to components exchange) and compose overarching requirements aiming at outlining the overall system architecture that will be addressed in T3.1.

First, we will describe the framework used for identifying the different sub‐elements that are subject to the definition of requirements. This framework describes how the end‐to‐end service can be decomposed into smaller dedicated parts that each have specific requirements.

Second, this framework will be applied to the sub‐elements defined in order to describe the different technical requirements, but also the performance parameters that are linked to it.

Further, we will apply this framework and requirements at use case level.

Finally, the same framework and requirements will be extended to the Creative Ring level.


Document Revision History

Date Version Author Summary of changes

27/5/2013 0.1 Diego Bonini First draft

03/6/2013 0.1 Giorgio Parladori Adding introduction and reference to templates

22/08/2013 0.1 Dirk Osstyn Updated structure and strategy to line up with DOW

22/08/2013 0.1 Makis Stamatelatos Comment added

30/08/2013 0.3 Giorgio Parladori Extend and consolidate Dirk proposal also including Makis comments

30/08/2013 0.4 Giorgio Parladori Further progress based on conf call decisions

20/09/2013 0.5 Giorgio Parladori, Dirk Osstyn

Further progress based on conf call decisions and Pilot Feedback

26/09/2013 1.0 Giorgio Parladori Update to start revision process

16/10/2013 1.0 Dirk Osstyn Document revision and comments

18/10/2013 1.0 Tim Wauters Document revision and comments

21/10/2013 1.0 Giorgio Parladori Integration of previous comments


Contributors

First Name Last Name Company Email

Diego Bonini ALU‐I diego.bonini@alcatel‐lucent.com

Giorgio Parladori ALU‐I giorgio. parladori@alcatel‐lucent.com

Dirk Osstyn ALU‐B Dirk.osstyn@alcatel‐lucent.com

Makis Stamatelatos NKUA [email protected]

Tim Wauters iMinds [[email protected]


Acronyms

Acronym Meaning

3G Third Generation

AV Audio Video

BGP Border Gateway Protocol

CBR Constant Bit Rate

CDN Content Delivery Network

CIM Common Information Model

CPU Central Processing Unit

ETSI European Telecommunications Standards Institute

FTTH Fibre To The Home

HD High Definition

HDMI High‐Definition Multimedia Interface

HD‐SDI High‐Definition Serial Digital Interface

HLS HTTP Live Streaming

HTML HyperText Markup Language

HTTP HyperText Transfer Protocol

IP Internet Protocol

IP‐TV Internet Protocol TeleVision

IT Information Technologies

LAN Local Area Network

MCU Multipoint Control Unit

MJPEG Motion JPEG (Joint Photographic Experts Group)

MPEG Moving Picture Experts Group

OMA Open Mobile Alliance

OS Operating System

OSPF Open Shortest Path First

QoS Quality of Service

RTP Realtime Transport Protocol

RTSP Real Time Streaming Protocol


Acronym Meaning

SIP Session Initiation Protocol

SNMP Simple Network Management Protocol

SOTA State of the Art

SSH Secure Shell

TCP Transmission Control Protocol

TMF TeleManagement Forum

UDP User Datagram Protocol

URI Uniform Resource Identifier

URL Uniform Resource Locator

USIM Universal Subscriber Identity Module

VGA Video Graphics Array

VIPS Video Manager over IP System

VLAN Virtual Local Area Network

VPN Virtual Private Network

WAN Wide Area Network

WiMAX Worldwide Interoperability for Microwave Access


Table of Contents

1. Introduction .............................................................................................................................. 10 2. General Framework .................................................................................................................. 11 2.1 Existing templates as an input ........................................................................................................ 13

2.1.1 Use‐case template 1 based on Logical Framework Approach (LFA): ................................... 14 2.1.2 Use case Template 2: description in laymen terms ............................................................. 14 2.1.3 Template 3: LFA Visualisation Template .............................................................................. 15 2.1.4 TechCards based Template .................................................................................................. 15 2.1.5 Template Identified in D8.1 ................................................................................................. 16

3. Requirements for Front‐end, Infrastructure and Back‐end......................................................... 17 3.1 Front‐End requirements ................................................................................................................. 18

3.1.1 Front‐End Technical requirements. ..................................................................................... 18 3.1.2 Front‐End Performance requirements. ................................................................................ 18 3.1.3 Front‐End Requirements Template. .................................................................................... 18

3.2 Back‐End requirements ................................................................................................................... 19 3.2.1 Back‐End Technical requirements. ....................................................................................... 19 3.2.2 Back‐End Performance requirements. ................................................................................. 19 3.2.3 Back‐End Requirements Template. ...................................................................................... 19

3.3 Infrastructure requirements ........................................................................................................... 19 3.3.1 Infrastructure Technical Requirements ............................................................................... 19 3.3.2 Infrastructure Performance Requirements ......................................................................... 19 3.3.3 Infrastructure Requirements template ................................................................................ 20

3.4 Consolidated Requirements Template ........................................................................................... 20 4. Use Cases .................................................................................................................................. 24 5. Towards a European Creative Ring ............................................................................................ 25 6. ANNEX ...................................................................................................................................... 26 7. References ................................................................................................................................ 27


List of Figures

Figure 1 – General Framework.............................................................................................................. 11 Figure 2 ‐ Generic Network scheme...................................................................................................... 17 Figure 3 – Generic Network scheme ..................................................................................................... 18 Figure 4 – Process for technical requirements collection ..................................................................... 24


List of Tables

Table 1: Use‐case template 1 based on LFA ......................................................................................... 14 Table 2: Technical Requirements: Front‐end Template ....................................................................... 21 Table 3: Technical Requirements: Infrastructure Template ................................................................. 22 Table 4: Technical Requirements: Back‐end Template ......................................................................... 22


1. Introduction Within WP3, D3.2 has the objective to specify the technical requirements with regard to ICT infrastructure and services needed to design the European Creative Ring architecture. Referring to the use cases defined in WP2, the relevant KPIs have to be identified and quantified. Furthermore additional KPI should be identified in order to guarantee the needed interworking between the platforms present in the three cities and possible new application that may be envisaged.

It is worth to know that similar activity is running in WP8 with the aim to use these technical requirements to manage the use case extension to other locations. In particular D8.1, together with D3.2 will be taken as input for the European Creative Ring architecture addressed in D3.1a/b.

First, we will describe the framework used for identifying the different sub‐elements that are subject to the definition of requirements. This framework describes how the end‐to‐end service can be decomposed into smaller dedicated parts that each have specific requirements.

Second, this framework will be applied to the sub‐elements defined in order to describe the different technical requirements, but also the performance parameters that are linked to it.

Further, we will apply this framework and requirements at use case level.

Finally, the same framework and requirements will be extended to the Creative Ring level.


2. General Framework In order to identify the ICT infrastructure requirements, a reference framework has to be identified, gathering existing requirements from WP2 (user requirements), WP4, 5, and 6 (pilot requirements), WP8 (requirements related to components exchange) and compose overarching requirements aiming at outlining the overall system architecture that will be addressed in T3.1.

The purpose of defining a reference framework is to create a unique reference point for the Creative Ring architecture, gathering user requirement, pilot requirement and all the requirement related to geographical extension of them (both in terms of remote usage and components exchange).

Figure 1 – General Framework

Considering a generic application, one can distinguish three main components:

The Front‐End: these are the direct interface with the end‐user. Examples of Front‐Ends may be SmartPhones, TV sets, sensors, public touch screens or even a theater room.

The Back‐End: these are all requirements that ensure the service itself. Typically these are IT infrastructure like servers, platforms and storage locations and their respective management systems to enable, update, activate,… the services.

Infrastructure: The infrastructure is the (ICT) network that connects the Front End to the Back End.

While defining the requirements for each of these 3 elements, we need to take into account both the local (pilot specific) requirements that apply to a small scale deployment as well as the

Access Infrastructure

Metro/Aggregation Network

•Service Platform•Service Creation•Service delivery•Service management

IT Resources

Layering

Terminal & Sensors

end users

• OS• (Virtualization layer)• #CPU

• #Memory• #Storage• #others…

CORE Network

L3• IP• DHCP• NAT

L2• VLAN

L1• DWDM• OTH• SDH

Network Technology

Front‐end

Back‐end

Infrastructure


internationalization possibilities. As an example, it is possible to describe the bandwidth usage required to run a service in a city context, but when extending the service towards other pilots, a larger audience will require a definitions like “bandwidth per user” as this identifies the scalability but also delay limitations on larger distances.

Figure 1 depicts a generic reference network model. It will be important to draw a per‐use‐case blue print model that provides more details on what is required. Blue prints allow assessing the ease of replication and/or extension in other regions and providing a clear overview to define the technical and infrastructural requirement.

Typical requirements are:

Front End

We refer to devices used to access the service. We may distinguish between specialized terminal vs dedicated terminal (e.g. dedicated set‐to‐box vs. general purpose PC). In general we need to take into account Scalability aspects, i.e. possible range of terminal e.g. from mobile device display to high‐end TV set.

Infrastructure:

Blue Prints should be identified, taking into account different alternative technologies (from DWDM to IP) that influence the service behavior and performances. Furthermore the role of access, metro and core networks in the identified scenarios should be considered.

Access bandwidth – this is associated to the terminal and may range from… to...

Allocated network bandwidth – this can be evaluated having in mind a specific service model that should be parameterized with respect to total user population, partitioning with respect to the terminal type if necessary, expected contemporary users, possibility to manage QoS over the network, bandwidth needed for infrastructure functioning (in case of distributed platform)

Back End

Service platform, typically requiring IT resources (i.e. CPU, Memory, storage) that could be concentrated, distributed or even virtualized. According to possible different choices, additional network resource may be needed to interconnect distributed elements and/or possible additional sources of information like sensors.

In a second dimension, we define requirement into two subsets of requirements:

Technical requirements: These requirements determine the tangible requirements that are typically very measurable. Technical requirements may be exact (example Operating system Windows 7) or provide range or minimum level (example: minimum 300 GB disk storage).

Non‐exhaustive list of technical requirements:

Operating systems supported (and version)

Screen sizes supported (expressed in HxV resolution)

Memory requirements


Storage requirements

Sensor type and interfaces

Etc…

Performance requirements: These requirements are typically linked to requirements of other parts of the network. A typical example could be connectivity (type of network access, minimum bandwidth requirements, etc)

Non‐exhaustive list of performance requirements:

Bandwidth requirements (preferably per end‐user for scalability assessment)

Jitter restrictions

Delay restrictions

Connectivity requirements: 3G/4G – WIFI type n– Gigabit Ethernet, etc…

We will apply the sub‐requirements to each of the three framework base components, leading to following overview:

Component Technical requirements Performance Requirements (KPI)

Front End

Infrastructure

Back End

In the next section, each of these will be worked out in more detail, leading to a generic requirements template.

2.1 Existing templates as an input Looking at the general framework, previously described, we need to identify the technical requirements of the identified applications. Furthermore we need to identify a general way to describe first and to collect later on those requirements.

Different templates have been already defined in the other project WP’s.

In D2.1 we identify three template formats, but unfortunately they mainly reflect the user perspective and the technical contents are very limited. An alternative is to use a kind of TechCards defining a template where to put the technical requirements from a network level (Interface & performance cards?).

Furthermore in WP8 additional templates were use to acquire additional information.

Unfortunately it will be difficult to manage the technical requirements within the existing templates, mainly because their structure is not well shaped tor technical detail collection. For that reason we are going to define a new template (excel based) later on.


However some technical requirements can be extracted from the existing template. In the following paragraph we identified the relevant fields of the already defined template highlighting (in yellow) the part that could be used to extract relevant information related to this deliverable.

2.1.1 Use‐case template 1 based on Logical Framework Approach (LFA):

1. Long‐term goal / social & economic impact (outcome)

the general goal of the use case

the expected socio –economic impact

2. Direct purpose of the use case

products and or services

target group and customer segments

3. Services and revenues (output) the applications (one‐pager describing the when, what, where, how for the pilots in layman's terms)

the used content

the expected (future) revenue streams

other user preferences

opportunities to expand to other cities (up‐scaling possibilities)

4. Activities preparing and during the trials (throughput)

developing apps and platforms

trials

selecting users and defining target groups

communication & dissemination

5. Assets/costs (input) Equipment, and hardware

software platforms

other technical facilities

content

IPR & capital

Use TechCards, an example of a techcard can be found in section 4.

Table 1: Use‐case template 1 based on LFA

Only entry list #5 can be used to identify the dedicated infrastructure elements even if those are listed with the purpose to evaluate the use case cost.

2.1.2 Use case Template 2: description in laymen terms

Brief Description: (max. 2 sentences),

Actors: (max. 1 sentence per actor),

Preconditions: (max. 1 sentence per Precond.),

Basic Flow of Events: (List the sequence of actions with short and clear sentences),

Alternative Flows: (List the sequence of actions with short and clear sentences),

Special Requirements: (List the requirements for a successful execution),

Description of limitations & opportunities to expand to other cities/regions,

Technological components that can be ‘exported’ and ‘imported’.

According to D2.1 almost all the bullets may include useful information regarding the technical requirements even if the data collection is not homogeneous


2.1.3 Template 3: LFA Visualisation Template

Only “Input/Key resources” section contain relevant information about infrastructure even if very often are generic end apparently not including for instance network requirement

2.1.4 TechCards based Template

A tech‐card is a two‐sided card (see Figure 2), which contains the following information:

(1) Title and name of the platform/technology;

(2) Metaphorical image;

(3) Short description of the technology;

(4) Maturity level,

(5) Ownership;

(6) Technical characteristics;

(7) Communication interfaces;

(8) Location & contact and;

(9) Importance of being used in the project.

According to D2.1 only few bullets may include useful information regarding the technical requirements even if the data collection is not homogeneous


2.1.5 Template Identified in D8.1 Additional tables have been proposed in the D8.1 which will be very helpful to identify the technical requirement both from general perspective and also related to specific pilot applications. In particular for:

Network or networking infrastructure,

Platform,

End Devices,

Application,

Service,

User (including also non technical aspects, such as language etc). a model has been proposed highlighting possible associated attributes. The analysis done within D8 start from use case overview:

Name

Content

Context

Network Technology

Platforms

Applications

Events

Living Labs Then analyze the platform

Platform: <>, Use Case: <>

Functionality

Input

Quality

Process

Output

Portability The analysis continues with the purpose to assess the “portability” of the use‐cases following the WP8 objectives.


3. Requirements for Front‐end, Infrastructure and Back‐end.

In this chapter the relevant technical and performance requirements will be identified and a general template to be used for specific use cases will be proposed. In particular a list of relevant KPI will be associated to the performance indicators.

Given a generic service we need also to deal with some additional consideration that may influence the analysis:

Quality of service – depending on many possible factors (business model, location, resource availability, etc.) a specific service could have different level of quality. For example video can be displayed on different devices from a small smartphone to a high end tv set at different resolution

Requirement inter‐dependency ‐ in service deployment we need to take into consideration possible constraints that may influence the requirements. For instance bandwidth availability may limit the number of user or may influence the quality of service. In this case we need to set priority in the requirements

Scalability – we need to identify possible requirement parameterization. As example, depending on user base requirements related to infrastructure or back‐end may vary significantly.

Figure 2 ‐ Model & Architecture

Taking into account the above consideration we need to identify a kind of process to actually set end‐to‐end service requirements, considering dependencies, scalability and QoS target. For a green fields service we should target mainly the desired QoS and, according to the target population, it is possible to define infrastructure requirements and back‐end requirement. If we would like to develop a new service over an existing infrastructure we need to consider the constraint that will influence QoS and possible target population.

End Users

Front‐end

Infrastructure

Back‐end

SERVICE Model & Architecture

Business MODEL

• # of user• User localization

• Terminal, Sensors• SW Platform

(Android, IoS, Win)

• Network layer • IT technologiesTechnical Requirements

Performance requirements

• Expected QoS • Terminal, Sensors• SW Platform

(Android, IoS, Win)

• Bandwidth• Delay• Jitter

• MIPS• Memory size

Requirement dependencies


Referring to Figure 3, in the following paragraphs more details on technical requirement of Front‐end, Back‐end and infrastructure will be given. Some example will be also presented. In the final paragraph the consolidated template should be capture the entire technical requirement consolidated up to now.

Figure 3 – Generic Architecture Scheme scheme

3.1 Front‐End requirements

3.1.1 Front‐End Technical requirements.

As the front‐end can be identified as the end‐user interface and related HW/SW support, we need to identify the set of resources that can guarantee the usability of the service. In particular the type of terminal and the platform technology should be identified.

3.1.2 Front‐End Performance requirements.

We need also to deal with the level of quality of the service. As an example video information can be seen on a smartphone or on high resolution display. This will influence the performance requirement of the front‐end platform.

3.1.3 Front‐End Requirements Template.

The above leads to below Front‐End Requirements template.

Component Technical requirements Performance Requirements

Front‐End Bulleted list Bulleted list

Kortrijk

Barcelona

Trento

INFRASTRUCTURE (GEANT / NRENS)

Access Infrastructure

Metro Network

Service Connection

Local users


IT Resources

IT Resources

IT Resources

IT Resources


Front‐end

Back‐end

Infrastructure


3.2 Back‐End requirements

3.2.1 Back‐End Technical requirements.

We should identify the physical resources needed to support the identified services mainly in terms of Platform technology. In general we should consider the underlying SW platform (i.e. basic Operating System like Linux/windows, etc…). It is also important to identify the way that those resources will be available. More and more we are speaking about virtualization and cloud services, but quantification of the actual physical resources is still essential for the dimensioning.

Additional service requirements could be considered part of the general infrastructure such as, for example, security management, IPR management that can be tough as part of the general infrastructure, instead to be specifically implemented by the single application/service.

3.2.2 Back‐End Performance requirements.

We should identify the IT performances needed to support the identified services mainly in terms of computational power (CPU) and storage capacity.

3.2.3 Back‐End Requirements Template.

The above leads to below Back‐End Requirements template.


Back‐End Bulleted list Bulleted list

3.3 Infrastructure requirements

3.3.1 Infrastructure Technical Requirements

Technical Infrastructure requirements are linked to the actual network architecture supporting the specific service. We need to consider both network layers and network topology.

Network layers define the different protocols applied. It typically determines the type of connectivity that is required or the alternatives that are provided. For some applications where mobility is involved, this will be 3G or 4G, but WIFI might be a cheaper alternative that is also supported.

The network topology defines how the different infrastructure elements are connected together and how they interoperate. At a high level it describes how access is provided to the end‐user and how the access nodes are connected to a bigger network and to the back‐end. But the topology also describes for instance if NAT is used, what routing protocols are required, which security levels are build in, etc – just to name a few.

3.3.2 Infrastructure Performance Requirements

According to the generic architecture presented in Figure 3Error! Reference source not found., the physical layer is mainly characterized by bandwidth and availability figures. We need to consider local users, served by a suitable access network and service and management platform, very likely attached to metro‐core network.

In general we need to keep under control the latency and jitter characteristics and the service layer agreement (SLA) needed by the identified services, in particular guaranteed rate vs. best effort rate and the associated packet loss probability.


In general the identified parameters assume values that are linked to the specific network solution / configuration and that scale with respect the number of user and the “dimension” of the offered services (e.g. for video distribution, the dimension on video data base, the size and the location of the storage capacity). Furthermore we need to consider that Network Infrastructures are normally shared by many applications.

3.3.3 Infrastructure Requirements template

The above leads to below Infrastructure Requirements template. This template consists of 2 elements: a drawing that outlines the infrastructure elements (ICT network overview). This drawing includes all elements up to the connectivity with the Front‐end and the Back‐End. A table of requirements, outlined here below.


Infrastructure Bulleted list Bulleted list

3.4 Consolidated Requirements Template The consolidated Requirements Template can be found here below (reference excel file D3.2‐Annex.xls). For better readability it is split in the tree man sections Front‐end, Infrastructure and Back‐end.


Table 2: Technical Requirements: Front‐end Template

Front-end

Sum

mar

yP

latfo

rm A

BC

Pla

tform

CD

E

Pla

tform

…

Bas ic Types Technical requirements Performance requirements General Comment(input devices, incl. sensors)

keybordtouchscreenmicrophonevideo cameraGPSproximitylighttemperaturecontacts (open/closed)

(output devices)video displayloudspeakersheadphonescontacts (open/closed)

(processing device)CPUmemoryOS Platform

(storage device)diskflash

(networking)copper pair (xDSL)fiberwi-fiethernetIP LayerMobile

(security)Resource availabilityIntegrityConfidentiality


Table 3: Technical Requirements: Infrastructure Template

Table 4: Technical Requirements: Back‐end Template

Infrastructure

Sum

mar

yP

latfo

rm A

BC

Pla

tform

CD

E

Pla

tform

…

Basic Types Technical requirements Performance requirements General Comment(Access Network)

Physical TechnologyTranmission characteristicsNetwork equipmentsNetwork managementSecurity

(Aggregation Network)TechnologyTranmission characteristicsNetwork equipmentsNetwork managementsecurity

(Core Network)TechnologyTranmission characteristicsNetwork equipmentsNetwork managementsecurity

(end-to-end characteristics)Resource availabilityTranmission characteristicsSecurity

Back-end

Sum

mar

yP

latfo

rm A

BC

Pla

tform

CD

E

Pla

tform

…

Bas ic Types Technical requirements Performance requirements General Comment(processing device)

CPU

memory

OS Platform

(storage device)

disk

(networking)

copper pair (xDSL)

fiber

router/switch

ethernet

IP Layer

(security)

Resource availability

Integrity

Confidentiality


With the purpose to collect data we suggest the following procedure.

1. Identify the architecture – A picture should represent the basic architectural components grouped in “front‐end”, “Infrastructure” and “back‐end” sections. This picture does not make part of the overall template described above, but will be used as a blue print for later extension and/or replication to other pilots or under different circumstances. Moreover, it allows to have a clear view on the components that are involved (Back‐end and Front‐end) and the infrastructure required to connect these components.

2. Identify the actors – It is expected that users, provider of the service, provider of the network, as an example, will be identified. By doing so, these actors will further identify the different “instances” of each component shown in the blue print. As an example: different types of users may exist that have different types of end‐user devices and therefore also have different requirements.

3. Identify the elementary components (the actual technical requirement) – what is needed to guarantee the usability of the service. The blue print, in combination with the different instances created by the diversity of users will provide a clear insight of the elementary components that are involved and that are required to set up the service.

4. Identify the list of attributes (the actual performance requirements) ‐ For each component and identify the performances and the actual value range or specific value that guarantee the desired quality of service/experience

The template is built up in a layered way.

In a first layer, Front‐end, Infrastructure and Back‐end form the three main building blocks as outlined above.

In a second layer, each of these 3 main building blocks are broken down into main types of components, such as input devices, output devices, etc…

In the third and final layer, each device will be described by its characteristics (e.g. input devices keyboard, microphone, etc…).

This layered methodology allows to easily browsing which components are required for the use case, then clearly describing the details of each of these components up to the level required to unambiguously identify what is needed.

Mainly in the case of Front End and Back End, there may be different co‐existing platforms. These platforms may be resulting from the instances created through different stakeholders, alternatively due to platforms composed by multiple components (example: a multimedia platform that consists of a processing unit and a storage unit). To accommodate for this requirement, it is possible to extend the template with additional columns. An empty template will contain “Platform ABC” and “Platform CDE” as initial input fields only.


4. Use Cases Based on current defined use cases form D2.1, this chapter has the objective to capture the key technical requirements, validating the template structure from one side and collect the relevant information in view of e‐ring architecture definition and setup.

The following picture shows the process identified for data collection, taking into account the envisaged evolution of Pilots.

Figure 4 – Process for technical requirements collection

In particular, we derive the current technical requirement from the current use cases identified in the three Pilots. Part of this activity has been already done by WP2 and information is available within Pilot WP4‐6, further inputs are also available from D8.1. We need then to take into account three main evolution axes:

Evolution of the use case within the same Pilot, increasing performance, adding new feature, enhancing the quality of the service, etc, eventually leading to new technical requirements in view of D2.5.

Geographical evolution of the services within Creative Ring architecture set in D3.1, this mainly refers to the possibility to access a particular service within Creative Ring platform and the consequent adaptation/scaling addressed in D3.3/D3.4

Service Interchange, which has been currently addresses in WP8 (D.8.1)

Refer to Annex for the detailed list of technical requirements associated to each use case and related platforms.

PILOTS

GeneralRequirements (WP2)

End Users

Front‐end

Infras tructure

Back‐end

Use Cases

Local Evolution

Additional Requirements (WP2, WP4‐6)

Geographical Evolution

towards Creative Ring Architecture

Interchange evolutionPILOTS

PILOTS

Additional technical Requirements (WP3)

+

Consolidated technical Requirements (Annex of D3.2)

+


Annex – 2nd step +

Annex – 3rd step +


Annex – 4th step


5. Towards a European Creative Ring This section has the purpose to draw a synthesis of technical requirement based on data collection coming from the Pilots. This will be the starting point to capture additional technical requirements needed to address the evolution of local service to geographical extension, significantly increasing end‐user population.

By analyzing the collected data it is possible to derive some general consideration that will be reported hereinafter.

Front‐end

The majority of use‐cases and related platforms are based on standard terminal, ranging from basic smartphone device up to PC platform. Only in few cases we detect the usage of high end computer device or tv set where the relevant aspects are mainly related to the computational power and display performances.

It is worth to highlight that the connection bandwidth, today based on standard available connections, need to be better analyzed in view of scaling the service to a wider population. In particular the needed performances are currently achieved by using best effort networking with low level of load, rather than managing QoS in the network. For the next evolution step we need to estimate the actual bandwidth per user, being ideally able to model it.

Infrastructure

Infrastructure is correctly perceived from the Pilot as the access network. However, end‐to‐end network requirements should be assessed to allocate the proper network resources. Per user traffic model need to be identified and QoS requirements need to be clearly defined.

Back‐end

As for the front end, the back end platforms are based on standard IT technology. A variety of IT resourced are used starting form standard server/WS up to “virtualized” resources in the cloud. Also in this case the local network infrastructure and the access network are used without specific requirements.

In general:

security aspects seem not addressed at the moment

Scalability issue need to be better addressed having a clear per user / per service bandwidth profile

Actual QoS requirements need to be better identified and used for a real network design


6. ANNEX The following pages show the data collection performed by the Barcelona, Kortrijk and Trento Pilots in terms of Technical and Performance requirements.

D3.2‐AnnexV4.xls Page 1

USE CASE: Barcelona Live Media UHD Capture, Transmission and Visualisation.

Front-end

smar

tpho

ne

tabl

et

PC … Sum

mar

y

Basic Types Technical requirements Performance requirements x value value (input devices, incl. sensors)

keybord required xtype standard…

touchscreen not requiredcharacteristics

…microphone required x

bandwidth [50 , 20.000] Hzsensitivity [-55 , -45] dBconnector XLR or jack output

echo cancellation…

video camera required xBW/Col Automatic or manual

Resolution < 3840x2160 up to 4K…

GPS not requiredperformance

…proximity not required

active area…

light not requiredsensitivity

…temperature not required

range…

contacts (open/closed) not requiredrules

…

(output devices) xvideo display required x

size 24" or moreresolution < 3840x2160 up to 4Kframe-rate >20 25 - 50 fps

3D…

loudspeakers required x# of 1 or more

Power 30 W or moreheadphones required x

performance [53 , 22.000] Hz…


…


(processing device) xCPU required

type dual core quad coreclock > 2.5 GHz

…memory required

size 4 GB or more…

OS Platform requiredWindows XP or new ver.

Linux Ubuntu > v12,04Android

IOS…

(storage device) xdisk required x

size > 320 GBperformance > 5400 rpm

…flash not required

sizeperformance

…

(networking) xcopper pair (xDSL)

bandwidth upstreambandwidth downstream

…fiber required x

bandwidth upstream > 100 Mb/s > 1000bandwidth downstream > 100 Mb/s > 1000

…wi-fi required x

ref. standard IEEE 802.11n

bandwidth upstream > 100 Mb/sbandwidth downstream > 100 Mb/s

…Mobile not required

ref. standardbandwidth upstream

bandwidth downstream…

ethernet required xbandwidth > 100 Mb/s

…IP Layer required x

version IPv4 or IPv6DHCP manual prefered

NAT Traversal

…

(security)Resource availability

device reliabilityredundancy

…Integrity

backup procedure…

Confidentialitypassword rules

…



Front-end

Sum

mar

y

Plat

form

1: L

ow-la

tenc

y AV

Pla

tform

Basic Types Technical requirements Performance requirements

Technical requirements


Comment

(input devices, incl. sensors)keybord required Required

type standard…


…microphone required Required



video camera required RequiredBW/Col Automatic or manual




active area…



range…


…

(output devices)video display required required

size > 24"resolution < 3840x2160 up to 4Kframe-rate >20 usually 25 - 50 fps

3D…

loudspeakers required required# of > 1

Power > 30 Wheadphones required required



…


(processing device)CPU required required Intel

type > dual core P2 requires > quad core CPUclock > 2.5 GHz

…memory required required

size > 4 GB…

OS Platform required requiredWindows >XP


IOS…

required

(storage device)disk required required



sizeperformance

…

(networking)copper pair (xDSL)


…fiber required required

bandwidth upstream > 100 Mb/s > 1000 (P2)bandwidth downstream > 100 Mb/s > 1000 (P2)

…wi-fi required required






ethernet required requiredbandwidth > 100 Mb/s > 1000 (P2)

…IP Layer required required


NAT Traversal

…



…Integrity

backup procedure…


…



Front-end

Sum

mar

y

Plat

form

1: L

ow-la

tenc

y AV

Pla

tform

Plat

form

2: U

HD

Vis

ualis

atio

n




Comment

(input devices, incl. sensors)keybord required Required

type standard…


…microphone required Required



video camera requiredBW/Col Automatic or manual




active area…



range…


…


size > 24"resolution < 3840x2160 up to 4Kframe-rate >20 usually 25 - 50 fps

3D…

loudspeakers required required# of > 1

Power > 30 Wheadphones required required



…

(processing device)CPU required required Intel

type > dual core P2 requires > quad core CPUclock > 2.5 GHz



size > 4 GB…

OS Platform required requiredWindows >XP


IOS…

required

(storage device)disk required required



sizeperformance

…



…fiber required required

bandwidth upstream > 100 Mb/s > 1000 (P2)bandwidth downstream > 100 Mb/s > 1000 (P2)

…wi-fi required required






ethernet required requiredbandwidth > 100 Mb/s > 1000 (P2)

…IP Layer required required


NAT Traversal

…



…Integrity

backup procedure…


…



Infrastructure

Sum

mar

y


value value

(Access Network)Physical Technology required

Copper (xDSL)Fiber 10 Gb/s or more

Wireless IEEE 802.11n >100Mb/s3G/4G

Public WI-FIEthernet

Coax…

Tranmission characteristic requiredbandwidth [1 , 10] Gb/s

delay < 250 msjitter < 1 ms…

Network equipments requiredThroughtput 100 Mb/s 10000 Mb/s

# of ports# of users

…Network management N/A

ArchitectureTechnology

…Security N/A

link redundancy…

(Aggregation Network)

(Core Network)

(end-to-end characteristics)



Infrastructure

Sum

mar

y

Low

-late

ncy

AV P

latfo

rm




Comment


Copper (xDSL)Fiber >10 Gb/s


Public WI-FIEthernet >1Gb/s

Coax…



Network equipments requiredThroughtput 100 > x > 10000 Mb/s




…Security N/A

link redundancy…


(Core Network)




Infrastructure

Sum

mar

y

Low

-late

ncy

AV P

latfo

rm

UH

D V

isua

lisat

ion




Comment


Copper (xDSL)Fiber >10 Gb/s


Public WI-FIEthernet >1Gb/s

Coax…



Network equipments requiredThroughtput 100 > x > 10000 Mb/s




…Security N/A

link redundancy…


(Core Network)




Back-end

Sum

mar

y

Low

-late

ncy

AV P

latfo

rm

UH

D V

isua

lisat

ion

Plat

form

…

see front-end section


USE CASE: Barcelona Multi-conferencing Service

Front-end

smar

tpho

ne

tabl

et

PC UH

D V

ideo

Wal

l

Sum

mar

y


value value

(input devices, incl. sensors)keybord required x x x

type standard…

touchscreen required x xcharacteristics any technology

…microphone x x x

bandwidthsensitivityconnector


video camera requiredBW/Col Col

Resolution CIF or higher (1Mb/s)

…GPS not required

performance…

proximity not requiredactive area

…light not required

sensitivity…

temperature not requiredrange

…contacts (open/closed) not required

rules…

(output devices)video display required x x x x

size any sizeresolution or lower 4k resolution frame-rate or lower 30 fps

3D…

loudspeakers required x x x x

headphones required x x xperformance

…



…

(processing device)CPU required x x x x

type dual core or higherclock 2500 Mhz or higher

…memory required x x x x

size 4 Gb or higher…

OS Platform requiredWindows x supported

Linux x x supported

Android x x supported

IOS x x x supported

…

(storage device)disk x x x x required

size 50 Gb or higher

performance 5200 rpm or higher

…flash

sizeperformance

…

(networking)copper pair (xDSL) required

bandwidth upstream x x 2 Mbps or higher

bandwidth downstream x x 10 Mbps or higher

…fiber required



…wi-fi required

ref. standard x x xbandwidth upstream 2 Mbps or higher

bandwidth downstream 10 Mbps or higher

…Mobile required



ethernet requiredbandwidth 10 Mbps or higher

30 Mbps or higher

…IP Layer required

version TCP/IPv4

DHCP DHCP or Fixed IPNAT Traversal STUN Server or ICE Server

…

(security)



Front-end

Sum

mar

y

Plat

form

Vid

eo M

ixer


Technical requirements Performance requirements

Comment

(input devices, incl. sensors)keybord required required

type standard…

touchscreen required requiredcharacteristics any technology

…microphone



video camera required requiredBW/Col Col


…GPS not required

performance…



sensitivity…



rules…


size any sizeresolution 4k resolution or lowerframe-rate 30 fps or lower

3D…

loudspeakers required required

headphones requiredperformance



rules…

(processing device)CPU required required

type dual core or higher

clock 2500 Mhz or higher


size 4 Gb or higher

…OS Platform required required

WindowsLinux supported

AndroidIOS…

(storage device)disk required



…flash

sizeperformance

…


bandwidth upstream 2 Mbps or higher


…fiber



…wi-fi

ref. standardbandwidth upstream 2 Mbps or higher


…Mobile



ethernetbandwidth 10 Mbps or higher

30 Mbps or higher

…IP Layer

version TCP/IPv4

DHCP DHCP or Fixed IPNAT Traversal

…

(security)



Front-end

Sum

mar

y

Plat

form

Vid

eo M

ixer

Plat

form

Mul

ticon

fere

nce

syst

em


Technical requirements Performance requirements Comment


type standard…


…microphone required





…GPS not required

performance…



sensitivity…



rules…


size any sizeresolution full HD or lowerframe-rate 30 fps or lower

3D…

loudspeakers required required

headphones required requiredperformance


rules…

(processing device)


CPU required requiredtype dual core or higher



size 4 Gb or higher


Windows supported

Linux supported

Android supported

IOS supported

…




…flash

sizeperformance

…




…fiber



…wi-fi



…Mobile



ethernetbandwidth 10 Mbps or higher

30 Mbps or higher

…IP Layer

version TCP/IPv4

DHCP DHCP or Fixed IPNAT Traversal STUN Server or ICE Server

…

(security)



Infrastructure

smar

tpho

ne

tabl

et

PC UH

D V

ideo

Wal

l

Sum

mar

y

Plat

form

Vid

eo M

ixer

Plat

form

Mul

ticon

fere

nce

syst

em


value value


Copper (xDSL) x x 5‐10 Mbps

Fiber x x 5‐10 Mbps

Wireless x x x x 5‐10 Mbps

3G/4G x x 2‐10 Mbps

Public WI-FI x x x x 5‐10 Mbps

EthernetCoax

…Tranmission characteristic N/A

bandwidth 2‐10 Mbps

delayjitter…

Network equipments N/AThroughtput




…Security N/A

link redundancy…

N/A


(Core Network)




Back-end

PC/W

S

Dat

a C

ente

r

Clo

ud In

frast

ruct

ure

…

Sum

mar

y


value value

(processing device)

CPU required

# of cores x 4 or higher

CPU x x86 or x64

clock x 2800 MHz or higher

…

memory required

size 4GB or higher

…

OS Platform required

Windows

Linux x ubuntu

Android

IOS

…

(storage device)

disk required

# of disks x

size x

performance x

technology

architecture (raid)

external storage

…

(networking)

copper pair (xDSL) required

bandwidth upstream x 20 Mbps or higher

bandwidth downstream x 20 Mbps or higher

…

fiber required



…

router/switch

capacity

# of ports

…

ethernet required



…

IP Layer required

version x N/A

DHCP x N/A

Proxy N/A

VPN N/A

Firewall N/A

NAT Transversal x STUN Server or ICE Server

…

(security)



Back-end

Sum

mar

y

Plat

form

Vid

eo M

ixer


Platform ABC

(processing device)

CPU required required

# of cores 4 or higher

CPU x86 or x64

clock 2800 MHz or higher

…

memory required required

size 4GB or higher

…

OS Platform required required

Windows

Linux ubuntu

Android

IOS

…

(storage device)

disk required required

# of disks 1

size 50 GB

performance any

technology

architecture (raid)

external storage

…

(networking)




…

fiber required



…

router/switch

capacity

# of ports

…

ethernet required



…

IP Layer required

version

DHCP

Proxy

VPN

Firewall

NAT Transversal

…

(security)



Back-end

Sum

mar

y

Plat

form

Vid

eo M

ixer

Plat

form

Mul

ticon

fere

nce

syst

em


Platform CDE

(processing device)



CPU x86 or x64


…


size 4GB or higher

…


Windows

Linux ubuntu

Android

IOS

…

(storage device)


# of disks 1

size 50 GB

performance any

technology

architecture (raid)

external storage

…

(networking)




…

fiber required



…

router/switch

capacity

# of ports

…

ethernet required



…

IP Layer required

version

DHCP

Proxy

VPN

Firewall

NAT Transversal STUN Server or ICE Server

…

(security)


USE CASE: Barcelona Multiscreen Management System

Front-end

smar

tpho

ne

tabl

et

PC Sum

mar

y

Basic Types Technical requirements Performance requirements value value


type standard…


…microphone



video camera requiredBW/Col Col

Resolution CIF (1Mb/s) or higher…



active area…



range…


…

(output devices)video display required x x x

sizeresolutionframe-rate

3D…

loudspeakers not required# of

Powerheadphones not required

performance…


…

(processing device)


CPU required x x xtype dual core or higher

clock…

memory required x x xsize 1 Gb or higher

…OS Platform required

Windows x supported

Linux x supported


IOS x x supported

…

(storage device)disk not required x x x

sizeperformance


sizeperformance

…




…fiber required



…wi-fi required

ref. standardbandwidth upstream x x x 2 Mbps or higher

bandwidth downstream x x x 10 Mbps or higher




ethernet requiredbandwidth upstream 10 Mbps or higher



versionDHCP TCP/IPv4

NAT Traversal DHCP or Fixed IP…

(security)



Front-end

Sum

mar

y

Vide

o IP

Sys

tem

Basic Types Technical requirements Performance requirements Technical requirements


Comment


type standard…


…microphone





…GPS not required

performance…



sensitivity…



rules…


size any sizeresolutionframe-rate

3D…

loudspeakers not required# of

Powerheadphones not required

performance…


…

(processing device)CPU required required


clock



size 1 Gb or higher


Windows supported

Linux supported

Android supported

IOS supported

…

(storage device)disk not required not required

sizeperformance


sizeperformance

…




…fiber required



…wi-fi required









version TCP/IPv4


…

(security)



Infrastructure

Sum

mar

yS



Copper (xDSL) x 5‐10 Mbps

Fiber x 5‐10 Mbps

Wireless x x 5‐10 Mbps

3G/4G 2 10 Mb3G/4G x 2‐10 Mbps

Public WI-FI x x 5‐10 Mbps

EthernetCoax

…Tranmission characteristic required

bandwidth 2‐10 Mbps

delayjitter…





…Security N/A

link redundancy…


(Core Network)




Back-end

PC/W

S

Dat

a C

ente

r

oud

Infra

stru

ctu

Sum

mar

y

D

Clo


(processing device)

CPU required

# of cores x 1 or higher

CPU x arm

clock x 1 GHz or higher

…

memory requiredmemory required

size 512MB or higher

…


Windows

Linux x x ubuntu/debian

Android

IOS

…

(storage device)

disk required

# of disks x 1

size x 50GB or higher

performance x any

technology

architecture (raid) any redundant architecture

external storage

…

(networking)




…

fiber required


bandwidth downstream x 20 Mbps or higherbandwidth downstream x 20 Mbps or higher

…

router/switch not required

capacity

# of ports

…

ethernet required



…

IP Layer requiredIP Layer required

version x TCP/IPv4

DHCP x DHCP or Fixed IP

Proxy

VPN

Firewall

NAT Transversal x

…

(security)(security)



Back-end

Sum

mar

y

eo IP

Sys

tem

Vide



Comment

(processing device)



CPU arm

clock 1 GHz or higher

…

memory required requiredmemory required required

size 512MB or higher

…


Windows

Linux ubuntu/debian

Android

IOS

…

(storage device)


# of disks 1

size 50GB or higher

performance any

technology


external storage

…

(networking)




…

fiber required



…

router/switch not requiredrouter/switch not required

capacity

# of ports

…

ethernet required



…

IP Layer required

version TCP/IPv4

DHCP DHCP or Fixed IP

Proxy

VPN

Firewall

NAT Transversal

…

(security)


USE CASE: Barcelona Media Content Adaptation System as a Service

Front-end

smar

tpho

ne

tabl

et

PC Sum

mar

y



type standard…


…microphonevideo camera required x x x

BW/Col IP RTSP camera

Resolution…

GPS not requiredproximity not requiredlight not requiredtemperature not requiredcontacts (open/closed) not required

(output devices)video display x x x required

sizeresolutionframe-rate

3D…

loudspeakers x x x not requiredheadphones x x x not requiredcontacts (open/closed) not required

(processing device)CPU x x x required

type arm/x86/x64 ‐ dual core or higherclock

…memory x x x required


OS Platform requiredWindows x supported

Linux x supported


IOS x x supported

…

(storage device)disk x x x not requiredflash not required





…fiber required



…wi-fi required x x x

ref. standard 802.11b or faster

bandwidth upstream x x x 2 Mbps or higher

bandwidth downstream x x x 5 Mbps or higher

…Mobile required

ref. standard 3G/4Gbandwidth upstream 2Mbps or higher

bandwidth downstream 5Mbps or higher

…ethernet required




version TCP/IPv4


…

(security)



Front-end

Sum

mar

y

MC

AS



Comment


type standard…


…microphonevideo camera required Optional

BW/Col IP RTSP camera

Resolution…

GPSproximitylighttemperaturecontacts (open/closed)

(output devices)video display required

size any sizeresolutionframe-rate

3D…

loudspeakersheadphonescontacts (open/closed)

(processing device)CPU required

type arm/x86/x64 ‐ dual core or higher

clock…

memory requiredsize 1 Gb or higher


Windows supported

Linux supported

Android supported

IOS supported

…

(storage device)disk not requiredflash




…fiber required




…wi-fi required

ref. standard 802.11b or faster



…Mobile required

ref. standard 3G/4Gbandwidth upstream 2Mbps or higher

bandwidth downstream 5Mbps or higher…




version TCP/IPv4


…

(security)



Infrastructure

Sum

mar

y


(Access Network)Physical Technology required any technology

Copper (xDSL)Fiber

Wireless3G/4G


Coax…

Tranmission characteristics requiredbandwidth 2 Mbp/s 50 Mb/s

delayjitter…

Network equipments N/ANetwork management N/ASecurity N/A

(Aggregation Network)Technology N/ATranmission characteristics N/ANetwork equipments N/ANetwork management N/Asecurity N/A

(Core Network)Technology N/ATranmission characteristics N/ANetwork equipments N/ANetwork management N/Asecurity N/A

(end-to-end characteristics)Resource availability N/ATranmission characteristics N/ASecurity N/A



Back-end

PC/W

S

Dat

a C

ente

r

Clo

ud In

frast

ruct

u

Sum

mar

y


(processing device)

CPU required x x


CPU x64


…

memory required x x

size 4GB or higher

…


Windows x x

Linux x x ubuntu/debian

Android

IOS

…

(storage device)

disk required x x

# of disks 1

size 100Gb or more

performance any

technology


external storage

…

(networking)


bandwidth upstream x 5Mbps or higher

bandwidth downstream x 5Mbps or higher

…

fiber required



…

router/switch required

capacity

# of ports

…

ethernet required



…

IP Layer required

version x TCP/IPv4

DHCP x Static IP

Proxy

VPN

Firewall

NAT Transversal x

…

(security)



Back-end

Sum

mar

y

MC

AS

Basic Types Technical requirements Performance requirements Platform ABC

(processing device)



CPU x64

clock 1600MHz or higher

…


size 4GB or higher

…


Windows

Linux ubuntu/debian

Android

IOS

…

(storage device)


# of disks 1

size 100Gb or more

performance any

technology


external storage

…

(networking)


bandwidth upstream 5Mbps or higher


…

fiber required



…


capacity

# of ports

…

ethernet required



…

IP Layer required

version TCP/IPv4

DHCP Static IP

Proxy

VPN

Firewall

NAT Transversal

…

(security)

Page 1 D3.2‐AnnexV4.xls

USE CASE: Kortrijk City App

Front-end

smar

tpho

ne

tabl

et

PC …

Sum

mar

y

Basic Types Technical requirements


x x x value range

(input devices, incl. sensors) x x xkeybord x x x required

Type on-screen kb…

touchscreen x x requiredcharacteristics any touch-technology

…microphone x x x required



video camera x x x requiredBW/Col Color

Resolution HD ready or hihger…

GPS x x requiredperformance Assisted GPS - low/smart energy

…proximity sensor x x required

active area iBeakon/BT4 detection…

light sensor not requiredsensitivity

…temperature sensor not required

range…


…

(output devices) x x xvideo display required x x x required

size any sizeresolution 320x480 1024*768 or higherframe-rate any framerate any framerate

3D 2D 2D…

loudspeakers x x x required# of

Powerheadphones x x optional

performance…

contacts (open/closed)rules

…

(processing device)CPU x x x required


…


memory x x x requiredsize 4 Gb or higher…

OS Platform x x x requiredWindows

Linux supported (version > x.y)Android supported (version > x.y)

IOS…

(storage device)disk x x x required

size 50 Gb or higherperformance 5200 rpm or higher

…flash x x x required

size 50 Gb or higherperformance

…



…fiber


…wi-fi x x required

ref. standard B or fasterbandwidth upstream any bandwith up

bandwidth downstream 5 Mb/s or faster…

Mobileref. standard


…ethernet

bandwidth…

IP Layer x x x requiredversion TCP/IP v4DHCP yes/optional fixed ip

NAT Traversal STUN Server or ICE Server…



…Integrity

backup procedure…


…



Front-end

Sum

mar

y

iPoi

nts





Comment

(input devices, incl. sensors)keybord required

Type…

touchscreen requiredcharacteristics any touch-technology

…microphone not required



video camera requiredBW/Col Color

Resolution HD ready or hihger…

GPS requiredperformance

…proximity sensor required

active area…



range…


…


size any sizeresolution 1024*768 or higherframe-rate any framerate

3D 2D…

loudspeakers required# of

Powerheadphones

performance…


…



…memory required



OS Platform requiredWindows

LinuxAndroid supported (version > x.y)

IOS supported (version > x.y)…


size 50 Gb or higherperformance 5200 rpm

…flash required

size 50 Gb or higherperformance

…



…fiber


…wi-fi required

ref. standard B or fasterbandwidth upstream any bandwith up

bandwidth downstream 5 Mbit downstream…

Mobileref. standard


…ethernet

bandwidth…

IP Layer requiredversion TCP/IP v4DHCP DHCP or fixed ip

NAT Traversal…



…Integrity

backup procedure…


…



Front-end

Sum

mar

y

iPoi

nts

App

hand

held





Type on-screen kb…

touchscreen requiredcharacteristics




video camera requiredBW/Col Color

Resolution…

GPS required Assisted GPSperformance low/smart energy

…proximity sensor required

active area iBeakon/BT4 detection…



range…


…


sizeresolution 320x480 or greaterframe-rate any framerate

3D 2D…

loudspeakers required# of

Powerheadphones

performance…


…


typeclock

…memory required

size…

OS Platform requiredWindows

LinuxAndroid

IOS…



sizeperformance

…flash required

sizeperformance

…



…fiber


…wi-fi



Mobileref. standard


…ethernet

bandwidth…

IP LayerversionDHCP

NAT Traversal STUN Server or ICE Server…



…Integrity

backup procedure…


…



Infrastructure …

Sum

mar

y

Basic Types Technical requirements rformance requirements value range


Copper (xDSL)Fiber yes for kiosk

Wireless yes for tablet/smartphone3G/4G


Coax…

Tranmission characteristics requiredbandwidth <1Mb/s (smartph. only) 10Mb/s

delay N/Ajitter N/A…





…Security N/A

link redundancy…


(Core Network)




Infrastructure

Sum

mar

y

Kortr

jik

Basic Types Technical requirementsrformance requirements Technical requirementserformance requirement Comment


Copper (xDSL)Fiber yes for kiosk

Wireless yes for tablet/smartphone3G/4G


Coax ?…

Tranmission characteristics requiredbandwidth 1-10 Mbps <1Mb/s for Tablet/smartph.

delay N/Ajitter N/A…

Network equipmentsThroughtput


…Network management


…Security

link redundancy…


(Core Network)




Back-end

PC/W

S

Dat

a C

ente

r

Clo

ud In

frast

ruct

ure

…

Sum

mar

y



value range

(processing device)CPU x x required

# of cores 1 4 or moreCPU X64clock 2400 MHz or more

…memory x x required

size 4GB 8GB or more…

OS Platform x x requiredWindows VMWARE 2008RC2

Linux Debian Debian Virtual hostAndroid

IOS…

(storage device)disk x x required

# of disks 1 32size 50GB 2000GB

performance anytechnology trasitiona HD

architecture (raid) RAID 5External storage required

…



…fiber x x required

bandwidth upstream 10 Mbpsbandwidth downstream 10 Mbps

…router/switch x x required

capacity 100 M# of ports 10 …more

…ethernet x x optional

bandwidth upstream 10 Mbp/s 100Mb/sbandwidth downstream

…IP Layer x x

version IPv4DHCPProxyVPN

FirewallNAT Transversal

…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form





Comment


# of cores 1 or 2 CPUclock 2500

…memory

size 4GB…

OS Platform Virtual machineWindows VMWARE 2008RC2

LinuxAndroid

IOS…


# of disks 1size 50GB

performance anytechnology

architecture (raid) any host dependentExternal storage

…



…fiber


…router/switch

capacity 100 M# of ports

…ethernet

bandwidth upstream

bandwidth downstream

…IP Layer

version 4DHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held





Comment

(processing device)CPU PC/WS, Data Center

# of coresCPUclock

…memory

size 4GB or more…

OS PlatformWindows

Linux Linuix x.yAndroid

IOS…

(storage device)disk

# of diskssize

performancetechnology

architecture (raid)External storage

…



…fiber required

bandwidth upstream 10 Mbpsbandwidth downstream 10 Mbps

…router/switch

capacity# of ports

…ethernet optional if not fiber

bandwidth upstream 10 Mbpsbandwidth downstream

…IP Layer

versionDHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held

Dat

abas

e &

Sear

ch s

erve

r Med

iaH

aven




(processing device)CPU

# of cores 4CPU X64clock

…memory

size 8GB…

OS PlatformWindows

Linux DebianAndroid

IOS…


# of disks 1size 50 GB



…



…fiber


…router/switch

capacity# of ports

…ethernet

bandwidth upstream


…IP Layer

versionDHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held

Dat

abas

e &

Sear

ch s

erve

r Med

iaH

aven

Web

& A

ppilc

atio

n se

rver

Med

iaH

aven






…memory

size 8GB…

OS PlatformWindows

Linux DebianAndroid

IOS…





…



…fiber


…router/switch

capacity# of ports

…ethernet

bandwidth upstream


…IP Layer

versionDHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held

Dat

abas

e &

Sear

ch s

erve

r Med

iaH

aven

Web

& A

ppilc

atio

n se

rver

Med

iaH

aven

Tran

scod

er s

erve

r Med

iaH

aven






…memory

size 8GB…

OS PlatformWindows

Linux DebianAndroid

IOS…


# of disks 1size 50 GB + 500 GB temp space



…



…fiber


…router/switch

capacity# of ports 10+

…ethernet

bandwidth upstream 1-10Gb/sbandwidth downstream

…IP Layer

versionDHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held

Dat

abas

e &

Sear

ch s

erve

r Med

iaH

aven

Web

& A

ppilc

atio

n se

rver

Med

iaH

aven

Tran

scod

er s

erve

r Med

iaH

aven

Stor

age

and

expo

rt se

rver





# of cores 4CPU x64clock

…memory

size 8GB…

OS PlatformWindows

Linux DebianAndroid

IOS…




architecture (raid)External storage external storage required

…



…fiber


…router/switch

capacity# of ports

…ethernet

bandwidth upstream


…IP Layer

versionDHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held

Dat

abas

e &

Sear

ch s

erve

r Med

iaH

aven

Web

& A

ppilc

atio

n se

rver

Med

iaH

aven

Tran

scod

er s

erve

r Med

iaH

aven

Stor

age

and

expo

rt se

rver

Zetic

on S

tora

ge A

pplia

nce





# of coresCPU X64 architectureclock

…memory

size…

OS PlatformWindows

LinuxAndroid

IOS…


# of disks 32size 2TB


architecture (raid) RAID 5External storage

…



…fiber


…router/switch

capacity# of ports

…ethernet

bandwidth upstream


…IP Layer

versionDHCPProxyVPN


…

(security)



Back-end

Sum

mar

y

iPoi

nts

plat

form

App

hand

held

Dat

abas

e &

Sear

ch s

erve

r Med

iaH

aven

Web

& A

ppilc

atio

n se

rver

Med

iaH

aven

Tran

scod

er s

erve

r Med

iaH

aven

Stor

age

and

expo

rt se

rver

Zetic

on S

tora

ge A

pplia

nce

Max

/Sen

seta

le C

reat

ion

envi

ronm

ent





# of cores more is betterCPU X64 architectureclock

…memory

size 4GB or more…

OS PlatformWindows

Linux DebianAndroid

IOS…

(storage device)disk No dedicated

# of disks 32size 2TB


architecture (raid) RAID 5External storage

…



…fiber


…router/switch

capacity# of ports

…ethernet

bandwidth upstream 100Mb/sbandwidth downstream

…IP Layer

versionDHCPProxyVPN


…

(security)


USE CASE: TRENTO Informative Video Services

Front-end

smar

tpho

ne

tabl

et

PC

Kios

k co

mpu

ter

Sum

mar

y


value value

(input devices, incl. sensors)keybord required x x required

type 30 45…

touchscreen required x x requiredcharacteristics x Both built-in or external infrared… Capacitive film Visual Planet

microphone Currently not provided xbandwidthecho cancellationsensitivityconnector…

video camera Currently not provided xBW/ColResolution…

GPS Currently not provided xperformance…

proximity not requiredactive area…

light not requiredsensitivity…

temperature not requiredrange…

contacts (open/closed) not requiredrules…

(output devices)video display required x x

size x x 46" 55"resolution x x 1136x640 1080x1920frame-rate 56 853Dbrightness 1500cd…

loudspeakers required x# of 1 2Power 1W or more

headphonesperformance…

contacts (open/closed)rules…



type AMD Quad-coreclock 2,5 Ghz…

memory requiredsize 4 GB…

OS Platform requiredWindows Embedded Standard 7LinuxAndroid Ver. > 4IOS Ver. > 5…

power requiredpower consumption 6 75…


size 32GB or moreperformance SSD…

flashsizeperformance…


bandwidth upstreambandwidth downstream…

fiberbandwidth upstreambandwidth downstream…

wi-firef. standardbandwidth upstreambandwidth downstream…

Mobileref. standardbandwidth upstreambandwidth downstream…

ethernet required x GbE Ethernet (RJ-45)bandwidth 2Mbps or more…

IP LayerversionDHCPNAT Traversal…

(security)



Front-end

Sum

mar

y

Dig

ital S

igna

ge (U

C1)



Performance requirements Comment


type on screen keybord (45keys)…

touchscreen required required Windows7 driver compatibilitycharacteristics Both built-in or external infrared… Capacitive film Visual Planet

microphone Currently not provided Currently not providedbandwidthecho cancellationsensitivityconnector…

video camera Currently not provided Currently not providedBW/ColResolution…

GPS Currently not provided Currently not providedperformance…

proximity not requiredactive area…

light not requiredsensitivity…

temperature not requiredrange…

contacts (open/closed) not requiredrules…


size 46 – 55”resolution 1080x1980frame-rate 56-85Hz3Dbrightness 1500cd (outdoor totem)…

loudspeakers required# of 1-2Power >1W

headphonesperformance…

contacts (open/closed)rules…


type AMD Quad-coreclock


…memory

size 4GB (DDR3 SO-DIMM 2GB x 2)…

OS PlatformWindows Windows Embedded Standard 7LinuxAndroid Ver. > 4IOS Ver. > 5…

powerpower consumption 70W (Max)…


size SSD 32GBperformance…

flashsizeperformance…




wi-firef. standardbandwidth upstreambandwidth downstream…

Mobileref. standardbandwidth upstreambandwidth downstream…

ethernet required GbE Ethernet (RJ-45)bandwidth…

IP LayerversionDHCPNAT Traversal…

(security)



Infrastructure

…

Sum

mar

y


value value

(Access Network)Physical Technology

Copper (xDSL)FiberWireless 2Mb/s3G/4GPublic WI-FIEthernetCoax…

Tranmission characteristicsNetwork equipmentsNetwork managementSecurity


(Core Network)




Back-end PC/W

S

Dat

a C

ente

r

Clo

ud In

frast

ruct

…

Sum

mar

y

Basic Types Technical requirements Performance requirements value value (processing device)

CPU required x# of cores 4CPUclock 2,2 Ghz…

memory required xsize 2-4 GB…

OS Platform required xWindows Windows 7 – 32bitLinuxAndroidIOS…

(storage device)disk required x

# of diskssize 500 GBperformancetechnologyarchitecture (raid) needed tbdexternal storage…




router/switchcapacity# of ports…

ethernet requiredbandwidth upstream 1 GBbandwidth downstream 1 GB…

IP Layer N/AversionDHCPProxyVPNFirewallNAT Transversal…

(security)



Back-end Sum

mar

y

Dig

ital S

igna

ge (U

Basic Types Technical requirements Performance requirements(processing device)

CPU required# of cores 4CPU XEON 4 core 5606 EMU Virtual CPUclock 2,13 Ghz…

memory requiredsize 2 GB…

OS Platform requiredWindows Windows 7 – 32bitLinuxAndroidIOS…


# of diskssize 400 GBperformancetechnologyarchitecture (raid)external storage…




router/switchcapacity# of ports…

ethernet requiredbandwidth upstream 1 GBbandwidth downstream 1 GB…

IP Layer N/AversionDHCPProxyVPNFirewallNAT Transversal…

(security)


USE CASE: TRENTO IPTV Services

Front-end

smar

tpho

ne

tabl

et

PC

set t

op b

ox

Sum

mar

y


value value

(input devices, incl. sensors)keybord required x x x x requiredtouchscreen required x xmicrophone Currently not provided x x xvideo camera Currently not provided x xGPS Currently not provided x xproximity not requiredlight not requiredtemperature not requiredcontacts (open/closed) not required

(output devices)video display required x x x x requiredloudspeakers required x x x x requiredheadphones optionalcontacts (open/closed)

(processing device)CPU requiredmemory requiredOS Platform requiredpower required

(storage device)diskflash


bandwidth upstreambandwidth downstream 2Mb/s…

fiberwi-fiMobileethernet required x GbE Ethernet (RJ-45)

bandwidth 2Mbps or more…

IP Layer

(security)



Infrastructure

…

Sum

mar

y

DIS

I/IPT

V

Mul

timed

ia C

onte

nt M

anag

emen

t


value value

(Access Network)Physical Technology

Copper (xDSL) 2Mb/sFiberWireless 2Mb/s3G/4GPublic WI-FIEthernet 2Mb/sCoax…

Tranmission characteristicsNetwork equipmentsNetwork managementSecurity


(Core Network)




Back-end

PC/W

S

Dat

a C

ente

r

Clo

ud In

frast

ruct

ure

…

Sum

mar

y


value value

(processing device)CPU required x

# of cores 4CPU 2clock 2,2 Ghz…

memory required xsize 16 GB…

OS Platform required x

Windows Redhat Enterprise Linux (RHEL)

LinuxAndroidIOS…

(storage device)disk required x

# of diskssize >2TBperformancetechnologyarchitecture (raid) needed tbdexternal storage…

(networking)

(security)


USE CASE: TRENTO Augmented Reality Video Services.

Front-end

smar

tpho

ne

tabl

et

PC

Kios

k co

mpu

ter

Sum

mar

y

Basic Types Technical requirementsPerformance requirements

value value


type 30 keys 45keys…

touchscreen required x x xcharacteristics any touch technology

…microphone required x x

bandwidthecho cancellation

sensitivityconnector

…video camera Currently not provided x

BW/ColResolution

…GPS Currently not provided x

performance…



sensitivity…



rules…

(output devices)video display required x x x

size 4" 55"resolution 1024*768 1080x1920frame-rate any framerate 58

3Dbrightness 1500

…loudspeakers required x x x

# of 1‐2

Power >1W

headphones optionalperformance


rules…


(processing device)CPU required x x x


…memory required

size 4GB


Windows Supported

Linux Supported

Android Supported

IOS Supported

…power required x

power consumption 70W (Max)

…

(storage device)disk required x x


performance 5400 rpm


sizeperformance

…

(networking)copper pair (xDSL) required x

bandwidth upstream 1 Mbits/s > 2‐3 Mbits/s

bandwidth downstream 10 Mbits/s

…fiber


…wi-fi required x x x

ref. standard B or faster

bandwidth upstream any bandwith up

bandwidth downstream 5 Mbit downstream

…Mobile required x x

ref. standard 3G/4Gbandwidth upstream


ethernet required x x x GbE Ethernet (RJ-45)bandwidth > 2Mbps


versionDHCP

NAT Traversal STUN Server or ICE Server is required…

(security)



Front-end

Sum

mar

y

Plat

form

Poi

Cen

tral




type…





…video camera Currently not provided Currently not provided

BW/ColResolution

…GPS Currently not provided Currently not provided

performance…



sensitivity…



rules…


size any size

resolution 1024*768 or higher

frame-rate any framerate

3D 2D

brightness 1500cd (outdoor totem)

…loudspeakers required

# of 1‐2

Power >1W

headphones optionalperformance


rules…





…memory required

size 4GB


WindowsLinux Supported

AndroidIOS…

power requiredpower consumption 70W (Max)

…





sizeperformance

…

(networking)copper pair (xDSL) required Required


…fiber


…wi-fi required



Mobile requiredref. standard


…ethernet required GbE Ethernet (RJ-45)

bandwidth…

IP Layer requiredversionDHCP

NAT Traversal

…

(security)



Front-end

Sum

mar

y

Plat

form

Poi

Cen

tral

Plat

form

Stre

etVi

deo




type on screen keybord …

touchscreen required requiredcharacteristics any touch tecnology

…microphone required required



…video camera Currently not provided required

BW/Col Color

Resolution smartphone‐tablet camera

…GPS Currently not provided required Assisted GPS

performance low/smart energy…



sensitivity…



rules…


sizeresolution 960x640 or higher

frame-rate3D

brightness…

loudspeakers required required# of

Powerheadphones optional

performance…


…





… tablet and smartphone core

memory requiredsize 4GB


Windows Supported

Linux Supported

Android Supported

IOS Supported

…power required

power consumption

…


size 50 GB multimedia



sizeperformance

…



…fiber


…wi-fi required Required



Mobile required required

ref. standard 3G/4Gbandwidth upstream


ethernet requiredbandwidth


versionDHCP

NAT Traversal STUN Server or ICE Server is required…

(security)



Front-end

Sum

mar

y

Plat

form

Poi

Cen

tral

Plat

form

Stre

etVi

deo

Plat

form

Raz

una


Technical requirementsPerformance requirements

Comment


type…





…video camera Currently not provided

BW/ColResolution

…GPS Currently not provided

performance…

proximity not requiredlight not requiredtemperature not requiredcontacts (open/closed) not required


size any size

resolution 1024*768 or higher

frame-rate any framerate

3D 2D

brightness…

loudspeakers required required# of 1‐2

Power >1W

headphones optionalcontacts (open/closed) not required


typeclock

…memory required

size 4GB (DDR3 SO‐DIMM 2GB x 2)


WindowsLinux Supported

AndroidIOS…

power requiredpower consumption 70W (Max)


…


size 50 GB multimedia




bandwidth upstream upstream > 2‐3 Mbits/s


fiberwi-fi required



Mobile requiredref. standard


…ethernet required GbE Ethernet (RJ‐45)

bandwidth…

IP Layer requiredversionDHCP

NAT Traversal

…

(security)



Infrastructure …

Sum

mar

y

Basic Types Technical requirements Performance requirements value value (Access Network)

Physical TechnologyCopper (xDSL) x

Fiber xWireless x3G/4G


Coax…

Tranmission characteristicsbandwidth 10‐100 Mbps

delayjitter…

Network equipmentsNetwork managementSecurity

(Aggregation Network)TechnologyTranmission characteristics required

bandwidth > 2Mbps

delayjitter…

Network equipmentsNetwork managementsecurity

(Core Network)

(end-to-end characteristics)Resource availabilityTranmission characteristicsSecurity



Back-end

PC/W

S

Dat

a C

ente

r

Clo

ud In

frast

ruct

ure

…

Sum

mar

y


value value

(processing device)

CPU required x x x

# of cores 4

CPU X64 QEMU Virtual CPU

clock 2500 or higher

…

memory required x

size 8 GB 16GB

…

OS Platform required x

Windows

Linux Ubuntu/centos

Android

IOS

…

(storage device)

disk required x

# of disks 1

size 50 GB + 500 GB temp space

performance any

technology

architecture (raid) x

external storage

…

(networking)

copper pair (xDSL) N/A

fiber N/A


capacity 100 Mbps

# of ports

…

ethernet N/A

IP Layer required

version 4

DHCP

Proxy

VPN

Firewall

NAT Transversal

…

(security)



Back-end

Sum

mar

y

Plat

form

Poi

Cen

tral


(processing device)

CPU required

# of cores 4



…

memory required

size 8 GB

…


Windows

Linux Ubuntu/centos

Android

IOS

…

(storage device)

disk required

# of disks 1

size 100 GB

performance any

technology

architecture (raid)

external storage

…

(networking)


fiber N/A


capacity 100 Mbps

# of ports

…

ethernet N/A

IP Layer required

version 4

DHCP

Proxy

VPN

Firewall

NAT Transversal

…

(security)



Back-end

Sum

mar

y

Plat

form

Poi

Cen

tral

Plat

form

Stre

etVi

deo


Platform CDE

(processing device)

CPU required

# of cores 4

CPU X64


…

memory required

size 16 GB

…


Windows

Linux Ubuntu/centos

Android

IOS

…

(storage device)

disk required

# of disks 1


performance any

technology

architecture (raid)

external storage

…

(networking)


fiber N/A


capacity 100 Mbps

# of ports

…

ethernet N/A

IP Layer required

version 4

DHCP

Proxy

VPN

Firewall

NAT Transversal

…

(security)



Back-end

Sum

mar

y

Plat

form

Poi

Cen

tral

Plat

form

Stre

etVi

deo

Plat

form

Raz

una


(processing device)

CPU required

# of cores 4



…

memory required

size 16 GB

…


Windows

Linux Ubuntu/centos

Android

IOS

…

(storage device)

disk required

# of disks 1


performance any

technology

architecture (raid)

external storage

…

(networking)


fiber N/A


capacity 100 Mbps

# of ports

…

ethernet N/A

IP Layer required

version 4

DHCP

Proxy

VPN

Firewall

NAT Transversal

…

(security)


7. References [1] SPECIFI web‐site

[2] Deliverable D2.1, “Scenarios, Use Cases and Requirements”

[3] Deliverable D8.1, “Service Customisation and Adaptation Framework”

[4] ...

Documents

WP3 D.3.2 Technical specification of scenarios · D.3.2 ‐ Technical specification of scenarios ... Diego Bonini ALU‐I diego.bonini@alcatel‐lucent.com ... Blue Prints should