SCOTT:SCOTT-NO Jan 2018

From its-wiki.no

Jump to: navigation, search


SCOTT:SCOTT-NO Jan 2018

Title SCOTT:SCOTT-NO January 2018
Place HiOA, Oslo, Pilestredet 46 - PA357
Date, Time 2018/01/31, 10:00-15:00
Contact Person Boning Feng
Participants Øivind Berg, Do van Thuan, Josef Noll, Christian Johansen, Toktam Ramezanifarkhani, Heidi Tuiskula, Maghsoud Morshedi, Bruno Dzogovic, Hamed Arshad, Boning Feng, Elahe Fazeldehkordi
related to Project SCOTT
this page was created by Special:FormEdit/Meeting, and can be edited by Special:FormEdit/Meeting/SCOTT:SCOTT-NO Jan 2018
Category:Meeting


 

Participants

  • Note that the Google forms take some time (many minutes and refreshes) before you can see your name listed.

     

Logistics

Meeting takes place at OsloMet - Oslo Metropolitan University (former HiOA) in Oslo, Building Pilestredet 46 (P46), Meeting Room PA357.  

Agenda

10:00 Welcome - table round
10:10 Status Contract (Josef)
10:20 Status Work Packages - an update since our last meeting in Halden
what are the real contributions, what do you want to do
11:00 Status Demonstrations
11:30 Status BBs, how we can improve the integration of the Building blocks
see presentation Media:SCOTT_UseCase_BB_Methodology.pdf
12:00 Lunch
12:45 Status BBs, integration (continued)
13:15 Deliverables, publications
14:00 SCOTT meeting in Tromsø in May (status, action items)
14:15 AOB, Action Items, next meetings
15:00 End of Meeting

 

Minutes

Discussion on Technology line reporting

Reporting of Technology lines and building blocks is due on M12. The following deliverables are planned. D23.1, D24.1, D25.1, and D26.1. SP2 and others ask for template for building block description. Shall be used as master for description, with basic information. Feel free to adopt the own approach for the building block.

TOC elements for Technology line reporting

Josef and Thanh suggest that the BB description in D23.1-D26.1 at M12 contain the following structure. Josef will ask the WP23-WP26 leaders (Thanh, Silke, Ramiro, Raffael) for feedback, before sending out a Word template.

1. Executive Summary
2. Introduction
3 Building block #1 description
3.1 Building block main description & specification
- objective
- state of technology
-envisaged advances
3.2 Detailed description of the building block
- sub-items… roadmap…
3.2 Proof of concept, contribution to Use Cases (overview)
- high level description (1 page)
3.4 Specific contribution to use case (WP7, WP8, WP9,…)
- specific to every use case
- core, extended, future - see SCOTT:Abbreviations
- open issues
4 Building block #2 description
4.1 Building block main description & specification
...
5 Building block #3 description
5.1 Building block main description & specification
...
6 Building block #4 description
6.1 Building block main description & specification
...
7 Summary

Relation between Use Cases and Building Blocks

Based on presentation from SP1 and SCOTT-NO suggestion for relation between use cases and building blocks: Media:SCOTT_UseCase_BB_Methodology.pdf

Abbreviations

see: SCOTT:Abbreviations used for all description.

Discussion of meaning of "use case". According to DoW, a use case is an area of building block implementation in a specific domain. A better understandable meaning would be a use case is the demonstration of technologies in a specific domain. Other abbreviations used:

  • spot-light = lead use cases
  • has a “core” for demonstration and market opportunities
  • has extended technology options for additional services
  • has future vision for envisaged services in the future vision

SCOTT-NO discussions

The internal discussions in the SCOTT team were set up to gain a clearer understanding of the contribution from each partner, and a common understanding of where we contribute else in the project.

S-ABAC (Hamed and Christian) as input for WP21 (document for input/output), roadmap, demonstrator at M14,

  • part of core implementation in WP21, with foreseen extensions of the building blocks
  • will also applied to WP7 (to be discussed in upcoming Finland meeting)
  • other WPs where S-ABAC is applied WP8WP11WP12WP13WP14WP15 
  • need for clarification meeting with Hamed, Christian and Josef on "trustworthy IoT

Privacy Labelling is going to be applied in Air Quality (Core?, Extended?) and Health (Core)

WP7 - 14Feb - physical meeting to define the details of the demonstration

WP8 - more details required for inputs from partners for the progress report

  • 5G network slicing: core: WP21, extended/future: WP08
  • home network with operator 5G network slice (ownership of infrastructure, mangement of infrastructure)
  • Dual core home router (increase reliability, …)

WP9 - plans for demonstration in place…

WP13 - small contribution from SCOTT-NO, mainly following and commenting
WP14 - NXP has taken responsibility, UiO is only commenting
WP21 - Ewout has full control
WP22 - was discussed today, see early notes on harmonisation
WP24, 26,
WP28 trust framework applicability, see SCOTT:SCOTT-Netherlands_exchange_certification on security certification and interesting perspective on a European level
WP29 - jobb for each partner to disseminate

OsloMet - Secure IoT lab established (Jan2018), more info will come

Upcoming meetings

  • 7Mar2018: Thanh will invite for a specific meeting at Network Slicing in the OsloMet lab - 7 Mar 2017 at 11:00h
  • 23-25May2018: Tromsø meeting
  • 7Jun2018: SCOTT-NO meeting at UiO from 9-14:30 - Toktam to organise


Open issues

Gap in understanding of what is Cyber Security for the various areas: explanation and potential impact
Critical Infrastructure - common collaboration(?)

  • Deliverable 28.1 on vulnerabilities in use cases.
  • Sharing of knowledge for the Smart-Grid Security Centre


Deliverables

The SHIELD Methodology by CRC Press
  • 4 reports coming up in M12
 TitleDue monthLead partnerEditorDissemination level
D8.2Managed Wireless Framework - Year 1M12EyeNetworksGeir Arne RimalaPublic
D22.1Assessment of technologyM12UiOToktam RamezaniPublic
D24.1Distributed cloud computing building blocks - Iteration 1M12TelenorDo van ThanhConfidential
D28.3Use Case VulnerabilitiesM12MovationConfidential


ActionItems: TOC for upcoming M12 deliverables from authors

  • lot's of overlap between deliverables, thus we are using the TOC for harmonisation

Contract Issues

NFR will send the contract. Josef will send out the "Egenerklæring (own declaration regarding company type). Each partner is asked to sign and return the form to Josef

Contract Ammendment

The following contract ammendments were accepted by SCOTT and are going to be sent to the commission:
UiO: consolidation to increase efficiency and effectiveness for the contribution in SCOTT

  • Move 2 PM from WP13 to WP26 as the required PM for measurable security and privacy labeling.
  • Move 2 PM from WP14 to WP26
  • Move 2 PM from WP15 to WP26

SmartIO: Missmatch between expectations of contributions

  • Move 3 PM from WP15 to WP8


Potential demonstrations by SCOTT-NO partners

SCOTT-NO envisaged demonstrations, depending on technology development

VoWIFI - integration of Telecom services in the future home

1. TelCo service not using the mobile network, but using the home WIFI network

  • Future Mobile services will come: URLL, LPW …
  • using EyeSaaS network for monitoring the Wifi

https://eyenetworks.no/files/788045/1474598/1/1462867929000/Erik+Taraldsen+-+Telenor+-+VoWiFi+-+fagdag2016.pdf

Network slicing

by Telenor (Thanh), EyeNetwork (Maghsoud), OsloMet (Boning, Bruno), Basic Internet Foundation

  • Network slicing (build own OpenAir mobile SDN network) - own SIM
  • Own Network connected to Internet
  • network slice for “Internet light for all” - meaning: free access to information
  • collecting data from network and perform anomaly detection, using AI and machine learning for counteracting on e.g. APT attacks. (APT - “collecting information”)

Future vision: Emergency/Police network as network slice in Telecom

Managed Wireless

  • EyeSaaS platform, give ISP the opportunity to see the quality of te delivered WiFi - 75% of all calls to ISP are related to Wifi, 90% of boxes returned to ISPs were fully operational
  • security monitoring (F-Secure)
  • Pilot interworking
  • SmartHome - SmartCity - energy, critical infrastructures (electricity)
  • EMPOWER: Valer functioning MicroGrid - summer cottages (own apps), control system (End of April implementation)
  • consumer site: privacy labelling applicability in App)
  • Monitoring of the home/city: what is controlled in the App, consumer and energy aggregator.
  • privacy, trust and security in apps and remote monitoring for SCOTT



Trust-enhancement using S-ABAC

  • discussion of trust enhancement
  • will be demonstrated in WP21 as "extension" during 2nd iteration

Other opportunities

WP21 health - Philips & Telenor - Emergency case

  • network slice
  • trust delegation, access control (open doors)

DDoS counter-act

counter-act on a DDoS attack by switching off devices in the home (business attribute)  


 

SCOTT Meetings

SCOTT related Meeting(s):

 

Open Action Items