Permission error
From its-wiki.no
Josef.Noll (Talk | contribs) |
Josef.Noll (Talk | contribs) (→TOC elements for Technology line reporting) |
||
Line 56: | Line 56: | ||
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. | 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 Building block #1 description | ||
:3.1 Building block main description & specification | :3.1 Building block main description & specification |
Revision as of 17:59, 31 January 2018
SCOTT-NO Jan 2018 | ||||||
---|---|---|---|---|---|---|
|
![]() |
You do not have permission to edit this page, for the following reason:
SCOTT-NO Jan 2018 | ||||||
---|---|---|---|---|---|---|
|
![]() |
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, Elahe Fazeldelkordi, Boning Feng |
related to Project | SCOTT |
Keywords |
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
Bruno - Christian: S-ABAC (Hamed and Christian) as input for WP21 (document for input/output), roadmap, demonstrator at M14, - will also applied to WP7 (Finland meeting)
SCOTT:WP8, SCOTT:WP11, SCOTT:WP12, SCOTT:WP13, SCOTT:WP14, SCOTT:WP15,
SCOTT:WP21 - is part of the core implementation
Privacy Labelling - status: 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
ActionItem: Toktam to ask SCOTT-NO partners for establishing a “reporting plan” for contribution in WPs 5G Network slicing - jan18 analysis of open source for network slicing - - feb18 - mar18 continuation of analysis work - apr18 detailed analysis of xxx technology
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…
ActionItem: xxxx WP13 - small contribution from SCOTT-NO, mainly following and commenting WP14 - NXP WP21 - Ewout - WP22… harmonised WP24, 26, WP28 trust framework applicability, see Jan Meeting with Netherlands WP29
OsloMet - Secure IoT lab established (Jan2018)
ActionItem: Thanh for a specific meeting at Network Slicing in the OisloMet lab - 7 Mar 2017
Deliverables
4 reports coming up D24.1 and D8.2 need harmonisation ActionItems: TOC for upcoming M12 deliverables D22.1 Assessment of technology M12 UiO Toktam Ramezani Public D8.2 Managed Wireless Framework - Year 1 M12 EyeNetworks Geir Arne Rimala Public D24.1 Distributed cloud computing building blocks - Iteration 1 M12 Telenor Do van Thanh Confidential D28.3 Use Case Vulnerabilities M12 Movation Josef Noll Confidential
Hand-written signature of book to Thanh
7 Jun 9-1430 SCOTT-NO meeting at Ifi
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 developmentVoWIFI - 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
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
Demonstration in Gdansk for
- remote configuration of devices, e.g. SSID update (new SSID, Firmware update, device inventory)
End of project demonstration
- guest network functionality for "Internet Lite for all"
- Telenor/Telia SSID in the home (5G@Home)
- API for registration of devices (batch processing)
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):- Final Review Graz Jun2020 (onThis property is a special property in this wiki. 28 September 2020)
- Privacy Labelling Workshop, 12Mar2020, Oslo (onThis property is a special property in this wiki. 12 March 2020)
- SCOTT-NO meeting Feb2020 (onThis property is a special property in this wiki. 4 February 2020)
- SCOTT-NO meeting Jan2020 (onThis property is a special property in this wiki. 17 January 2020)
- SCOTT-NO meeting Nov2019 (onThis property is a special property in this wiki. 13 November 2019)
- SCOTT Y2 Review (onThis property is a special property in this wiki. 9 October 2019)
- Consortium f2f Gdansk 2019 (onThis property is a special property in this wiki. 4 June 2019)
- SWITS annual meeting of Swedish security groups (onThis property is a special property in this wiki. 3 June 2019)
- EyeNetworks Fagdag Apr2019 (onThis property is a special property in this wiki. 29 April 2019)
- Elektrofagdag OsloMet 22Mar2019 (onThis property is a special property in this wiki. 22 March 2019)
- ... further results