SCOTT-NO Partner contribution

From its-wiki.no

Jump to: navigation, search

SCOTT Partner contribution

Jump directly to EyeSaaS, OsloMet, Movation, SmartIO, UiO, Telenor, TellU, Wolffia,

Responsibles for the various WPs in SCOTT-NO

use [[has SCOTT-NO contact::Christian Johansen, Toktam Ramezani]] in the description of the WPs


Details of Partner contribution

use [[UiO contribution::text of contribution here]] and SmartIO, EyeSaaS, HiOA, Wolffia, TellU in the respective WPs. Using Template SCOTT_lead
Testing of [[has contribution::UiO;5;lead development of xxx]] is at SCOTT:Testing_contribution

EyeSaaS (40 PM)

EyeSaaS leadership in WPs, Building Blocks, Deliverables and Tasks

 Page TitleLeaderSCOTT-NO:
WP08WP8 Managed WirelessMaghsoud MorshediMaghsoud Morshedi
BB24.ABB24.A Remote Configuration of InfrastructureLinda Firveld
T8.1Managed Wireless for Smart InfrastructuresMaghsoud Morshedi
T8.3Pilot implementations of novel servicesGeir Arne Rimala
EyeSaaS is editor of Deliverable:
 TitleEditor
D8.1Managed Wireless FrameworkGeir Arne Rimala
D8.2Managed Wireless Framework - Year 1Geir Arne Rimala
D8.4Managed Wireless Framework - Year 2Geir Arne Rimala
D8.5Managed Wireless Framework - DemonstratorGeir Arne Rimala

EyeSaaS participates in:

EyeSaaS participates in WPs: EyeSaaS participates in Building Blocks:

Details of contribution
WP3 - Requirements on Distributed Cloud Integration (WP03)
EyeSaaS (1 PM)

  • Requirements from use cases
o Contribution to the specification of requirements on security for NFV (network function virtualization), SDN (software-defined networking) and orchestration


WP5 - Requirements Reference Architecture (WP05)
EyeSaaS (1 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains
WP6 - Industrial Use Cases (WP06)
EyeSaaS (2 PM) will maintain the consistency with WP8 of which it is the leader and make sure the development matches the goals and endeavours from the other WPs.
WP8 Managed Wireless (WP08)
EyeSaaS (13 PM) will lead this work package, and contribute with wireless infrastructure design, standards and methods for the Home Bubble as well as standardized APIs for information exchange between systems.
WP9 - Secure Connected Facilities Management (WP09)
EyeSaaS (13 PM) will contribute with network insight and monitoring solutions of home infrastructure. EyeSaas will use their framework for network management in the context of the applications developed here.
WP13 - Trustable Wireless In-vehicle Communication Network (WP13)
EyeSaas (4 PM) Contribute with wireless infrastructure design, standards and methods for the smart sensors
WP28 - Building Trusted Systems (WP28)
EyeSaaS (5 PM) will refine the use case “Managed Wireless for Smart Infrastructure” to describe the operational and environmental characteristics of use. An appropriate trust manager will be appointed to implement the SCOTT framework with, as needed, the help of computer interaction designers, human factors, and psychologists to contextualize the trust factors and help derive trust objectives and trust requirements that will enable the actual building of trust for this use case. EyeSaas will monitor these trust requirements throughout the implementation phase. EyeSaas will develop assurance cases that allow to demonstrate trustworthiness of the technologies and document them through analytical and/or empirical means.
WP29 - Dissemination and Exploitation (WP29)
EyeSaaS (1 PM) will organize customer workshops to enhance the capabilities of the industry on measurable and configurable wireless networks.


in addition, have an Eye on WP7 Air Quality, WP9 Facility Monitoring and WP21 Health Care

OsloMet (38 PM)

HiOA leadership in WPs, Building Blocks, Deliverables and Tasks



HiOA participates in:

HiOA participates in WPs: HiOA participates in Building Blocks:

Details of contribution
WP3 - Requirements on Distributed Cloud Integration (WP03)
HiOA (1 PM)

  • Requirements from use cases
  • Requirement on security for roaming and cloud integration


WP5 - Requirements Reference Architecture (WP05)
HiOA (1 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains
WP8 Managed Wireless (WP08)
deploy, host and manage the management platform for connections between the Home bubble and the distributed cloud which is based on the Building Block 3.2.L Adaptable Network Slicing., HiOA (8 PM) will deploy, host and manage the management platform for connections between the Home bubble and the distributed cloud which is based on the Building Block 3.2.L Adaptable Network Slicing.
WP15 - Vehicle-as-a-Sensor within Smart Infrastructure (WP15)
HiOA (8 PM) will deploy, host and manage the management platform for connections between the vehicle and the infrastructure which is based on the Building Block 3.2.L Adaptable Network Slicing. moved to WP21
WP21 Assisted living and community care (WP21)
HiOA (8 PM) will deploy, host and manage the management platform for connections between the use case Assisted Living and the infrastructure which is based on the Building Block 3.2.L Adaptable Network Slicing. (moved from WP15)
WP24 - Distributed Cloud Integration (WP24)
HiOA (14 PM)

  • Remote Configuration of Infrastructure (2 PM)
  • Semantic Attribute Based Access Control (S-ABAC) (2 PM)
  • Adaptable Network Slicing (10 PM)


WP26 - Reference Architecture / Reference Implementations (WP26)
HiOA (5 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains.
WP29 - Dissemination and Exploitation (WP29)
HiOA (1 PM) will in addition to scientific dissemination through papers and conferences disseminate results and seek for exploitation possibilities through the SmartIO industry cluster and towards our collaboration partners around Europe.


Movation (9 PM)

Movation leadership in WPs, Building Blocks, Deliverables and Tasks

 Page TitleLeaderSCOTT-NO:
WP22WP22 - Technology Lines - Development and ImplementationJosef NollJosef Noll
T22.1Technology LinesJosef Noll
Movation is editor of Deliverable:
 TitleEditor
D22.2Market Roadmap - initialJosef Noll
D22.4Market roadmap - advancesJosef Noll
D28.3Use Case Vulnerabilities

Movation participates in:

Movation participates in WPs:


Details of contribution
WP22 - Technology Lines - Development and Implementation (WP22)
Movation (8 PM) will lead SP3 with focus on roadmaps, lessons learned and commonalities from developments and implementation work.
WP28 - Building Trusted Systems (WP28)
Movation (0 PM) lead the work on Deliverable D28.3. Note: neither contribution nor manpower defined
WP29 - Dissemination and Exploitation (WP29)
Movation (1 PM) ??


UiO (46 PM)

UiO leadership in WPs, Building Blocks, Deliverables and Tasks

BB24.IBB24.I Semantic Attribute Based Access Control (S-ABAC)Christian Johansen
BB26.FBB26.F Measurable security and privacyToktam Ramezani
BB26.GBB26.G Privacy labels (A-F)Christian Johansen
T30.3Implement an open innovation approach in SCOTTToktam Ramezani
UiO is editor of Deliverable:
 TitleEditor
D22.1Assessment of technologyToktam Ramezani
D22.3Trust technologies advancesToktam Ramezani
D30.3Documentation of open innovation activitiesToktam Ramezani

UiO participates in:

UiO participates in WPs: UiO participates in Building Blocks:

Details of contribution
WP1 - Requirements Management (WP01)

  • Contribution to the definition of guidelines and best practices (Task 1).
  • Contribution to the overall harmonization of requirements (Task 2).
  • Contribution to the assessment of project objectives (Task 4).


WP2 - Requirements on Security & Safety (WP02)
UiO (1 PM)

  • Requirements from Use Cases
  • Harmonization of requirements

  • Requirements on management of measurable security and privacy


WP3 - Requirements on Distributed Cloud Integration (WP03)
UiO (1 PM)

  • Requirements from use cases
  • Requirements for future of distributed cloud logic, addressed as fog- or edge-computing
  • Requirements from high-level objectives and general business needs
  • Harmonization of requirements for Remote Configuration of Infrastructure
  • Harmonization of requirements for Semantic Attribute Based Access Control


WP5 - Requirements Reference Architecture (WP05)
UiO (0 PM) will contribute with requirements for distributed access control, distributed logic and measurable security to the reference architecture.
WP6 - Industrial Use Cases (WP06)
UiO (2 PM) will analyse the commonalities between the use cases and use these for roadmapping in SP3.
WP7 - Air Quality Monitoring (WP07)
UiO (2 PM) Work on privacy aspects for mobile measurements and develop techniques for air quality visualisation. We expect to adopt the Citi-Sense-MOB toolbox of mobile air-quality measuring adapted to indoor measurements.
o Work on real-time status for Air Quality sensors, which is a vital aspect for obtaining reliable well-spread measurements. We will apply the Privacy Labels building block in conjunction with the Multi-metrics for privacy building block.
o We will use our experience from analysing Smart Grid electricity measurements to minimize energy consumption and apply it to air quality measurements.
o The work will also look into methods for predicting IAQ hazards and making virtual alarm services for alerting the occupants
WP8 Managed Wireless (WP08)
with measurable security and privacy of applications in the home domain, and will involve pilot users., UiO (4 PM) will contribute with measurable security and privacy of applications in the home domain, and will involve pilot users.
WP9 - Secure Connected Facilities Management (WP09)
UiO (4 PM) will contribute with attribute-based access control technologies to allow for a more fine-grained and dynamic access control solution. UiO will also work on defining the space of attributes needed in this use case along with their semantics and the structure of their inter-relationships. Attributes, with semantics and measurable values, and the flexible architecture behind the standard ABAC (e.g., using XACML and SAML based technologies and implementations), are a very good approach to obtaining a more virtual access control architecture. Attributes can include various aspects, like about the context, type of network and profiles. UiO’s work here is also related to the building block S-ABAC from the technology line of WP24. UiO will contribute with applying the Privacy Labels building block to the various technologies from this WP, like those for user localization. , In WP9(2 PM) and WP15 (1PM) we have already used our PMs in:

  • We have defined a master thesis on "Light-weight Authentication to Prevent Relay Attacks in RFID Environments".
  • We have attended a meeting regarding these WPs in Porto, and had several contributions for the WPs.
  • And have discussed 20 operational scenarios in WP9, and 9 scenarios in WP15.
  • We have defined a "new scenario” for dynamic access control related to applying BB24.I SABAC.


WP13 - Trustable Wireless In-vehicle Communication Network (WP13)
UiO (2 PM 0 PM, moved to WP26 Jan2018) Provide the measures for trusted authentication mechanisms of smart sensors as part of the real-time applications. Core of the work will be the focus on light-weight semantics for real-time decision making. For this we will make use of building block 3.4.F (Multi-metrics building block).
o Contribute with application-specific security and privacy profile, to enable software-enabled communication configurations for the in-vehicle communication. This will be one application of building block 3.2.I (Semantic ABAC building block).
WP14 - Secure Car Access Solution (WP14)
UiO (0 PM) reduced from 2 to 0 PM in Jan2018

  • Contribute with the security and privacy measures of communication channels to ensure a secure-enough car access, using the ongoing research finding from the National Smart Grid Security Centre. Moreover, the access control will be enhanced with a semantic model, to allow the definition of more fine-grained policies. This will also use the Semantic ABAC building block of WP24.
* Support the analysis of attack scenarios and contribute to proposal for related countermeasures. This will also use the Multi-metrics building block of WP26.
* Support final evaluation with a focus on security aspects. We will also use here the Privacy Labels building block of WP26.


WP15 - Vehicle-as-a-Sensor within Smart Infrastructure (WP15)
UiO (3 PM 1 PM, rest moved Jan2018 to WP26) will establish measurable security metrics for the sensor communication from the vehicle. This will make use of the Multi-metrics building block from WP26. UiO will point out privacy aspects related to the collection and distribution of sensed data from the vehicle. Investigate how these aspects are related to other privacy concerns raised in other use cases. This will also make use of the Privacy Labels building block from WP26. UiO will work on describing and modelling the semantics of the various privacy concepts present in the vehicle-as-a-sensor concept. The end result is a privacy aware solution from this work package. This will make use of the Semantic ABAC building block from WP24.
In WP15 (1PM) we have already used our PMs for defining 9 scenarios in WP15, mainly related to dynamic access control related to applying BB24.I SABAC.
WP21 Assisted living and community care (WP21)
will contribute to ease the introduction of the S-ABAC Building Block to help enable trust-based delegation in the assisted living and community care use case., UiO (2 PM) will contribute to ease the introduction of the S-ABAC Building Block to help enable trust-based delegation in the assisted living and community care use case.
WP22 - Technology Lines - Development and Implementation (WP22)
UiO (4 PM) will lead task 1 and establish the scientific background for the roadmap. UiO will establish the comparison to the state-of-science
WP23 - Security and Safety (WP23)
UiO (2 PM) has Focus on Privacy labelling
WP24 - Distributed Cloud Integration (WP24)
UiO (5 PM)

  • Establish models for semantic models on distributed logic, according to security and privacy needs

  • Remote Configuration of Infrastructure


* Semantic Attribute Based Access Control
WP26 - Reference Architecture / Reference Implementations (WP26)
UiO (6 PM) will contribute for distributed access control, distributed logic and measurable security to the reference architecture and also address compatibility with the FiWare platform. UiO will also drive standardization activities for the ‘privacy labelling’ developed in WP22.
WP29 - Dissemination and Exploitation (WP29)
UiO (1 PM) will contribute to security conferences and journals, and will identity sector-specific key players to foster application-specific.
WP30 - Open Innovation and Stakeholder Engagement (WP30)
UiO (4 PM) is leader of Implement an open innovation approach in SCOTT

  • Judge Open Innovation event submissions from a general technical point of view


* Support the winners of the Open Innovation Contest during their further implementation based on SCOTT results


SmartIO (27 PM)

SmartIO leadership in WPs, Building Blocks, Deliverables and Tasks



SmartIO participates in:

SmartIO participates in WPs: SmartIO participates in Building Blocks:

Details of contribution
WP1 - Requirements Management (WP01)

  • Contribution to the definition of guidelines and best practices (Task 1).

  • Contribution to the assessment of project objectives (Task 4).


WP3 - Requirements on Distributed Cloud Integration (WP03)
SmartIO (1 PM)

  • Requirements from use cases
  • Requirements for cloud technologies


WP5 - Requirements Reference Architecture (WP05)
SmartIO (1 PM) will contribute to collection of requirements from the Managed Wireless for Smart Infrastructures.
WP7 - Air Quality Monitoring (WP07)
SmartIO (3 PM) o Work on demonstrating this use case in ongoing work on smart home and smart grid.
o SmartIO will derive business opportunities for this use case.
WP8 Managed Wireless (WP08)
with the Smart Grid Security Centre Infrastructure. SmartIO will further develop the existing platform to fit SCOTT requirements., SmartIO (11 PM) will contribute with the Smart Grid Security Centre Infrastructure. SmartIO will further develop the existing platform to fit SCOTT requirements.
WP9 - Secure Connected Facilities Management (WP09)


WP15 - Vehicle-as-a-Sensor within Smart Infrastructure (WP15)
SmartIO (3 PM) SmartIO will investigate and test the Vehicle-as-a-Sensor use case towards the smart grid/home/building, with main focus on energy management by using the smart grid security centre infrastructure. In countries with high penetration of electrical vehicles, cars are seen as flexibility asset for the load balancing in the distribution grid. SmartIO will participate in all tasks in the UC in order to investigate and improve the compatibility of vehicle-as-a-sensor technology developed in the WP with the Smart Grid solutions. Work conducted by SmartIO is especially exploiting Building Blocks 3.2A Remote Configuration of Infrastructure and 3.2I Semantic Attribute Based Access Control (S-ABAC) moved to WP8
WP24 - Distributed Cloud Integration (WP24)
SmartIO (2 PM)

  • Remote Configuration of Infrastructure


* Semantic Attribute Based Access Control (S-ABAC)
WP26 - Reference Architecture / Reference Implementations (WP26)
SmartIO (2 PM) will contribute to Task 8 Multi level security metrics and privacy labelling for architecture definition
WP29 - Dissemination and Exploitation (WP29)
SmartIO (1 PM)  ??
WP30 - Open Innovation and Stakeholder Engagement (WP30)
SmartIO (2 PM) is mainly involved in Stakeholder engagement. 
Continuous SCOTT results promotion through SmartIOs extended industrial cluster and business incubator Recruitment of SMEs and incubator companies to be involved in a SCOTT open innovation initiative


Tellu (12 PM)

TellU leadership in WPs, Building Blocks, Deliverables and Tasks



TellU participates in:

TellU participates in WPs:


Details of contribution
WP3 - Requirements on Distributed Cloud Integration (WP03)
TellU (1 PM)

  • Requirements from assisted living use case


WP21 Assisted living and community care (WP21)
will contribute its cloud service and connected devices, and work on integration and trust in the SCOTT context. Its cloud service could/would be one of the cloud services with connected devices depicted in Figure 79. TellU may also be able to provide a Norwegian implementation of the use case.
In task 1, TellU will work on defining the architecture for their part of the system; integration, demonstration and validation. In task 3, TellU will work on introducing Role- Based Access Control to the TelluCloud system (i.e. S-ABAC integration)., TellU (9 PM) will contribute its cloud service and connected devices, and work on integration and trust in the SCOTT context. Its cloud service could/would be one of the cloud services with connected devices depicted in Figure 79. TellU may also be able to provide a Norwegian implementation of the use case. In task 1, TellU will work on defining the architecture for their part of the system; integration, demonstration and validation. In task 3, TellU will work on introducing Role- Based Access Control to the TelluCloud system (i.e. S-ABAC integration).
WP24 - Distributed Cloud Integration (WP24)
TellU (1 PM)

  • Semantic Attribute Based Access Control for assisted living scenario


WP29 - Dissemination and Exploitation (WP29)
TellU (1 PM) ??


Telenor (38 PM)

Telenor leadership in WPs, Building Blocks, Deliverables and Tasks

 Page TitleLeaderSCOTT-NO:
WP03WP3 - Requirements on Distributed Cloud IntegrationDo van ThanhDo van Thanh
WP24WP24 - Distributed Cloud IntegrationDo van ThanhDo van Thanh
BB24.LBB24.L Adaptable network slicingDo van Thanh
T24.1Cloud Integration
T3.1Requirements Cloud Integration
T8.2Service enabling through SW routingDo van Thanh
Telenor is editor of Deliverable:
 TitleEditor
D24.1Distributed cloud computing building blocks - Iteration 1Do van Thanh
D24.2Distributed cloud computing building blocks - Iteration 2Do van Thanh
D24.3Distributed cloud computing building blocks - Iteration 3Do van Thanh
D24.4Summary of selected SCOTT building blocks for distributed cloud computingDo van Thanh
D3.1Requirements on distributed cloud integration - Iteration 1Do van Thanh
D3.2Requirements on distributed cloud integration - Iteration 2Do van Thanh
D3.3Requirements on distributed cloud integration - Iteration 3Do van Thanh
D8.3Service Enabling Software RoutingDo van Thanh

Telenor participates in:

Telenor participates in WPs: Telenor participates in Building Blocks:

Details of contribution
WP1 - Requirements Management (WP01)
(also WP3 lead; link to TL Roaming & Cloud Integration)

  • Contribution to the definition of guidelines and best practices (Task 1).
  • Contribution to the overall harmonization of requirements (Task 2).

  • Contribution to the requirements tracking (Task 3).


WP3 - Requirements on Distributed Cloud Integration (WP03)
Telenor (3 PM)

  • Leader of this work package
  • Requirements from use cases
  • Requirement on security for roaming and cloud integration
  • Harmonization of requirements for mobile edge computing


WP5 - Requirements Reference Architecture (WP05)
Telenor (1 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains
WP8 Managed Wireless (WP08)
specify and design the connection between the Home Bubble and the distributed cloud according to the requirements of the Home Bubble by making use of he Building Block 3.2.L Adaptable Network Slicing., Telenor (6 PM) will specify and design the connection between the Home Bubble and the distributed cloud according to the requirements of the Home Bubble by making use of he Building Block 3.2.L Adaptable Network Slicing.
WP9 - Secure Connected Facilities Management (WP09)
Telenor .
WP15 - Vehicle-as-a-Sensor within Smart Infrastructure (WP15)
Telenor (6 PM) will specify and design the connection between the vehicle and the infrastructure according to specific requirements on security, reliability, latency, mobility, roaming, etc. by making use of the Building Block 3.2.L Adaptable Network Slicing. moved to WP21
WP21 Assisted living and community care (WP21)
Telenor (6 PM) will specify and design the connection between the use case Assisted Living and the infrastructure according to specific requirements on security, reliability, latency, mobility, roaming, etc. by making use of the Building Block 3.2.L Adaptable Network Slicing. (moved from WP15)
WP24 - Distributed Cloud Integration (WP24)
Telenor (14 PM)

  • Work package lead

  • Adaptable Network Slicing (8 PM)

  • Big Data Analytics (6 PM)


* Mobile Edge Computing (1 PM)
WP26 - Reference Architecture / Reference Implementations (WP26)
Telenor (4 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains.
WP29 - Dissemination and Exploitation (WP29)
Telenor (1 PM) will contribute to the Dissemination and Exploitation activities of the project.
WP30 - Open Innovation and Stakeholder Engagement (WP30)
Telenor (2 PM)

  • Judge Open Innovation event submissions from a Distributed Cloud Integration point of view

  • Support the winners of the Open Innovation Contest during their further implementation based on SCOTT results



Wolffia (30 PM)

Wolffia leadership in WPs, Building Blocks, Deliverables and Tasks



Wolffia participates in:

Wolffia participates in WPs: Wolffia participates in Building Blocks:

Details of contribution
WP3 - Requirements on Distributed Cloud Integration (WP03)
Wolffia (1 PM)

  • Requirements from use cases
  • Requirement on security for roaming and cloud integration


WP5 - Requirements Reference Architecture (WP05)
Wolffia (1 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains
WP8 Managed Wireless (WP08)
Wolffia will will carry out the implementation and testing of the connection between the Home bubble and the distributed cloud according to specific requirements on security, reliability, latency, mobility, roaming, etc. by making use of the Building Block 3.2.L Adaptable Network Slicing., Woffia (6 PM) will carry out the implementation and testing of the connection between the Home bubble and the distributed cloud according to specific requirements on security, reliability, latency, mobility, roaming, etc. by making use of the Building Block 3.2.L Adaptable Network Slicing.
WP15 - Vehicle-as-a-Sensor within Smart Infrastructure (WP15)
Wolffia (3 PM) will carry out the implementation and testing of the connection between the vehicle and the infrastructure according to specific requirements on security, reliability, latency, mobility, roaming, etc. by making use of the Building Block 3.2.L Adaptable Network Slicing.moved to WP21
WP21 Assisted living and community care (WP21)
Wolffia (3 PM) will specify and design the connection between the vehicle and the infrastructure according to specific requirements on security, reliability, latency, mobility, roaming, etc. by making use of the Building Block 3.2.L Adaptable Network Slicing. (moved from WP15)
WP24 - Distributed Cloud Integration (WP24)
Wolffia (14 PM)

  • Remote Configuration of Infrastructure (2 PM)

  • Semantic Attribute Based Access Control (S-ABAC) (2 PM)


* Adaptable Network Slicing (10 PM)
WP26 - Reference Architecture / Reference Implementations (WP26)
Wolffia (4 PM) will contribute with requirements for configuration architectures, starting from the home bubble and extending towards other domains.
WP29 - Dissemination and Exploitation (WP29)
Wolffia (1 PM) will contribute to the Dissemination and Exploitation activities of the project.



Reponsibilities of people

are in SCOTT:Authors, testing of graphical relations in SCOTT:Semantic_Relations