Property:Baseline

This is a property of type Text.

Pages using the property "Baseline"

Showing 22 pages using this property.

(previous 25) (next 25)

B
BB24.H +	Deployed systems rely on pre-specified roles and schedules for use in order to grant access. Mobility prediction is a current research area, but is not yet linked to access control in deployed systems  +
BB24.I +	Attribute Based Access Control (ABAC) starts to penetrate the industry, and has been used especially in the health domain where fine grained access policies are needed. Industrial standards already exist, e.g., XACML and SAML, and industry standard implementations of ABAC also exist, e.g., Balana ... We plan to include in ABAC notions from Semantic Technologies, e.g. ontologies for the specific domains that SCOTT works on, and reasoning engines like Protege. Semantic technologies are widely used in industries for and specific domains, with the purpose to provide amore structures way of managing and querying data. We want to use the powerful tools of ST in conjunction with ABAC models, to improve the flexibility of ABAC and ease the adoption by industry.  +
BB24.J +	The baseline for this building block is a vehicle interface for OBD (On- Board Diagnostic), which has been developed in FEV, a low cost, fan- less, single board embedded ARM computer as a demonstrator including high resolution display. This demonstrator can manage tethered OBD/CAN bus data and transmit it via an available network to the end-user e.g. for the purpose of vehicle condition evaluation. This demonstrator will be prepared according to the requirements of a trustable passenger vehicle data exchange system for quantified car use cases.  +
BB24.K +	The baseline for this building block is a vehicle interface for OBD2 (On- Board Diagnostic), which has been developed in DEWI using a beagle bone black, a low cost, fan-less, single board computer as a demonstrator. This demonstrator can manage tethered CAN bus data and transmit it via a wireless mesh network (IEEE 802.11s) to the end-user, e.g. for the purpose of a wireless software update. This demonstrator will be elaborated to sufficient the requirements of a trustable passenger vehicle data logging system for quantified car use cases.  +
BB24.L +	Adaptable Network slicing requires a number of technologies to be in place such as SDN, NFV, cloud technologies and consumer device technologies. These technologies will be offered by the Telenor 5G testbed but additional functions will have to be implemented.  +
BB25.A +	Baseline for this Building Block is the current project status of the WSN demonstrator for automotive test-beds in DEWI.  +
BB25.B +	Ultra Wide-band (UWB) radio communications has been proposed in literature as a possible defense against relay attacks in passive keyless entry systems. Similarly, UWB radio communications has also been identified as a promising candidate for wireless in-vehicle networking. First commercial UWB products have become available, however, they generally do not meet power consumption requirements for target application in PKE systems and/or wireless IVN applications. In addition, the IEEE 802.15.4 standard behind these products leaves room of a number of improvements in terms of security and effective use of resources.  +
BB25.C +	Batteries and supercapacitors are popular choices of storage device, but neither represents the ideal solution, with, supercapacitors possessing low energy densities while batteries have low power density. When using a battery-only solution for storage, the runtime of a typical sensor node is typically reduced by the battery’s relatively high internal impedance and thermal loss. Supercapacitors can overcome some of these problems, but generally do not provide sufficient long-term energy to allow aircraft health monitoring applications to be operated over an extended period. A hybrid energy storage solution can provide both energy and power density to a wireless sensor node.  +
BB25.D +	The power demanded by track-side infrastructures is about tens of watts or even 100W. This makes the energy harvesting quite complex since many of harvesting technologies, like piezoelectric and electromagnetic, are in the area of miliwatt to watt range. Therefore, there is a real need of high power energy harvesting (100W) and the corresponding energy management and storage to really achieve an appropriate deployment of these infrastructures along the whole rail system. There are promising solutions in the state of the art based on an electromagnetic energy harvester with mechanical motion that recover energy from the vibration track deflections induced by passing trains. These techniques are able to provide tens of watts but only when trains are passing.  +
BB25.E +	The BB starts from ...  +
BB25.F +	Baseline for this Building Block is the current project status of the WSN demonstrator for automotive test-beds in DEWI.  +
BB25.G +	State-of-the-art is publisched in Papp & Exarchakos. It contains a proposal for the dependability tree. System level Fault Injection, however, is not part of it. This will be developed in SCOTT  +
BB26.A +	Existing trackside networks often rely on cables between wayside cabinets to deliver communications. This fragile cable can become a weak link in the trackside infrastructure, as it can be targeted by vandalism or damaged by the weather. Moreover, the valuable metal is a frequent target of thieves, and the many meters of cable needed to support a true trackside network represent a significant ongoing replacement and maintenance cost. Cabling communication systems can also be an arduous task, particularly in trains systems, which are compose of many moving parts. The proposal of a Reference Architecture for an autonomous wireless communication infrastructure that will provide connectivity to both ontrack and onboard elements with a cloud-based platform is aimed to free operators from the limitations and complications of cabling a communications system.  +
BB26.B +	During the design and implementation phase the hosting of the cloud computing platform (see figure) will be established on the company IT infrastructure of participating partners to ensure high flexibility. If required, the hosting of resulting demonstrators and services, e.g. in order to ensure high-performance functionality for evaluation, will be established using available (professional) online cloud hosting services (from project partners) to save hosting efforts. These cloud hosting services must support the hosting of use-case specific technical components developed in SCOTT. Cloud platforms for private and public purposes will be configured and developed, based on available libraries or web services, including: * a managed app development platform, * high performance object storage and databases * cloud interconnections * data warehousing, batch and stream processing, data exploration * machine learning algorithms * monitoring, logging, and diagnostics * control of access and visibility to resources  +
BB26.C +	The BB Background experience and expertise coming from previous projects, as: SMARCOS (ARTEMIS), SESAR P15.2.4 (EC) and SATCOM4RAIL (ESA), where multilink systems have been analysed and simulated. from  +
BB26.D +	Security in IoT applications has not been addressed in full extent. Current solutions are vendor specific and mainly target encryption at the application level. This gap will be filled by this building block, providing a complete assessment of potential vulnerabilities that will lead to convenient security enforcing mechanisms.  +
BB26.E +	In the literature there is no yet a complete solution fro cross-domain interaction and application development. There are multiple stakeholders and vendors with customized solutions, but there is no standard or technological tools that enables interoperability between different wireless technologies and applications. This is an important gap in the literature of IoT and industrial automated systems.  +
BB26.F +	The Multi-metrics methodology from SHIELD is suggested as a starting point, to convert application requirements into e.g. network resources. The flow is as follows: a) applications having b) security and privacy requirements in need of c) network resources (in terms of security, privacy, reliability, ++). Example: a) Health Care services might need a b) privacy level A+, thus have c) requirements for isolation (VPN) when it comes to network resources. We will build on and extend the work done in previous Artemis projects. We will extend theoretical and methodological concepts developed there, as well as tools that have been developed for manipulating metrics for security, privacy, and dependability.  +
BB26.G +	We would like to introduce privacy labels for applications and components, similar to the energy labels (A++, A+, A, B,...F), see [[IoTSec:Privacy_Label]]. Customers in Europe have an understanding of these labels for white goods, and thus we should use a similar technology to introduce "privacy" labeling. E.g. You would like to buy yourself a sports device (Fitbit, Google watch,...) or application (Endomondo, Strava,...). A potential difference between the tools might be expressed through the privacy label, e.g. a Polar device having an A-privacy, while a Garmin device having a B-privacy. - Our analysis can then show the relation between application goals and system capabilities (configuration of components) to achieve the required privacy level.  +
BB26.H +	Experience is coming from past measurement campaigns, a ray tracing software packages developed at AIT, a geometry based stochastic modelling technique developed at AIT, currently running projects on SDR prototyping (REALTIME) and single link emulation (ENABLE- S3).  +
BB26.I +	Currently there is no consensus or standard for security in the IoT. Semantics and ontology interoperability has been proposed but it is also in its infancy. There are many vendors nd standards in the industry for IoT interoperability. This is an important gap in the literature. Our building block attempts to bridge this ga providing convenient interoperability, protocol translation, and data representation for industrial automation, smart cities etc.  +
BB26.J +	Communication protocol coming from ESA project (Iris program) where Indra was leading the definition and design of the new standard (waveform) for ATM communications via satellite. Indra has a prototype (TRL-4) of the GES modem (HUB side) implementing a SIC receiver (Interference canceller). Indra aims to adapt this waveform to be used for M2M applications and develop the remote terminal to on- board on trains.  +

(previous 25) (next 25)