The summaries of the deliverables of the project are as follows:

D2.1Harmonized requirements for 5G-enabled
eHealth applications
WP2 produces the requirements and overall architecture specification for the Health5G project as well as manages its validation. The specifications will be produced based on the requirements and use case-specific architecture definitions, originating from the sub-projects. WP2 will harmonize the requirements and identify any commonalities among the technologies, required for implementing the different use cases. The overall solution envisioned as the result of WP2, includes the common enabling technologies and their configuration to meet the requirements of the different services and domains of use, including Hospital, Home, and Emergency. WP2 will also evaluate the overall architecture in the context of selected end-to-end scenarios, including multiple use cases (e.g. emergency and hospital), to verify the interplay between the different services and discover the full potential of the overall solution.

The eHealth issues that are primarily related to the hospitals consist of the use cases of sub-project 1 (SP1). These issues are mainly concerned with the communication and exchange of data with the hospitals. To satisfy the demands of the use cases from SP1, the requirements are higher connection speed, lower minimum latency, uninterrupted communication network, and maintaining privacy and security. The partners involved with SP1 (along with their use case titles) are Insung Information (Wireless Patient Monitoring Inside Hospitals), Inosens (Hospital & Clinical Rehabilitation Training System), RedZinc (Senior medical support with in-hospital wearable video), and Experis IT (Fall Detection and Monitoring Inside Hospitals).

The sub-project 2 (SP2) focuses on home care applications, preferably enabled by the 5G network. The different use cases under this SP2 may have varied paths to achieve a specific target of providing smooth communication between the homes and the caregiver facilities. However, they all need to fulfil the harmonized requirements of high bandwidth (at least 10 Mbps), low latency (< 100 ms), secure connection, and uptime of at least 99.5% of the time. The partners involved with SP2 (along with their use case titles) are Alkit (Home based rehabilitation training system), Alten (OnDosis hand-held oral medicine dosing device), Accellrate (Wireless Planner), Vestel (5G Patient diagnosis, care, treatment and monitoring at home), Semper-Tech (Smart Bike Trainer), CardioShirt (Home Monitoring), and Camanio (Camanio Smart Care and Giraff telepresence robot).

Finally, the last sub-project 3 (SP3) deals with the emergency use cases that may occur outside of home and hospital, in an outdoor environment. Example scenarios include, a traffic accident, transporting patient from an accident scene to the hospital, emergency during a sports event. The partners involved with SP3 (along with their use case titles) are TUB (Accident and emergency response) & (Medical Care at a Large Event), FH IIS (Patient Transport Monitoring), and RedZinc (Wearable Video from Paramedic to Emergency Department of Hospital).
D2.2Initial Overall System Architecture SpecificationsDay to day eHealth applications such as telemedicine, telemonitoring, remote training etc. are gaining high importance with thanks to developing communication technologies. 5G mobile cellular technology is one of the most enhanced communication technologies which provides high data rates, low latency, high reliability and availability that enable novel features of eHealth services. According to ETSI TR 103477 v.1.1 “eHealth; Standardization Use Cases for eHealth” document different eHealth objectives should be met via network technologies and 5G will be the most convenient technology that provides unique features such as enhanced Mobile Broadband(eMBB), ultra-Reliable Low Latency(uRLLC) and Massive Machine Type Communication(mMTC). All these features have unique attributes that utilized by eHealth use cases, 5G network will offer challenging and new Health5G use cases in different environments.

This document aims to specify an integrated architecture for 5G powered eHealth project. All architectures have been created for each domains such as hospital, home and emergency to be able to meet various requirements of use cases. Primarily each use case owner explained their use cases, motivation and added value of 5G of use cases related with sub-domain architectures.All architectures are created based on results of Task 2.1 in Health5G, and mainly these requirements specify how overall architectures should be to serve whole use cases. Main motivation of behind creating different architectures for each domain is that show how 5G capabilities will enhance sub-domain specific use cases. Differences and commonalities between 5G supported use cases for each sub-domains detailly investigated and outcomes are presented as architecture definitions. Finally, overall architecture is defined to show interplay between all sub-domains, especially aim to show full potential of 5G supported various eHealth applications.

The project plans show that this deliverable has two version. In this first version, first architectures related with sub-domains and overall system defined and it is ready to be utilized by partners. Until end of project, first versions of architectures will be used for guiding the use case and subdomain specific integration and validation. Use case owners will evaluate performances of their use cases with these architectures when they integrate their end-to-end solutions with common technologies. Second version of this deliverable will be formulated based on performance of first architectures and further analyses of use cases. Towards the end of the Health5G project, final version of this deliverable shows validated architectures of end-to-end eHealth services over 5G network.
D2.3Pilot Site and Demonstrator DescriptionThis document is the Deliverable 2.3 – Pilot Site and Demonstrator Description. It contains information on what use-cases will be implemented in the pilot sites, how the demonstrators show the outcomes of the project, which technologies are already present and what planned features are to be developed and integrated to implement the demonstrators.

There are three pilot sites (Germany, Sweden, Turkey) in the project with close cooperation between partner of the same and across pilot sites (i.e., Korean demonstrator integration with German or Turkish pilot). The pilots’ goal is to create an environment of future enabling technologies, i.e., 5G communication, cloud and fog computing, IoT and security, to evaluate the project partners’ eHealth devices, services, and applications in different settings. To meet that goal, each pilot consortium includes mobile network operators, cloud service providers, IoT data platform providers, and eHealth service providers. It should be noted that the geographical distribution and diversity in expertise among project partners allow the demonstrators to be exhibited to broad international audiences. A mapping of pilot/country and the implemented demonstrators is first provided in Section 2.

The demonstrators highlight main technological and healthcare aspects of all Health-5G use cases specified in Deliverable 2.1 [1]. They cover a broad range of novel eHealth applications, i.e., at home, in the hospitals, and in smart cities. The demonstrators’ purpose is to showcase the activities and outcome of the project. The joined efforts in the development of demonstrators take advantage of availability of the medical partners availability for the pilots. Most demonstrators show the requirement for advanced capabilities of future 5G, cloud and IoT infrastructures and health instruments to deliver ubiquitous eHealth services. Each demonstrator is described in details in the respective sections with scenario flows showing interactions between eHealth services and infrastructure components. Subsequently, the evaluation criteria are analysed with respect to project objectives. Therefore, this deliverable serves as the basis for the cooperation among project partners during the implementation, deployment and evaluation of the demonstrators.

The deliverable contains a current and future state analysis based on the use cases descriptions and requirements in Deliverable 2.1 [1]. For each pilot site and demonstrator, the requirements for technologies to be developed in WP3-5 are specified. Validations of the demonstrators regarding performance and project objectives are being carried out, and the results will be reported in the later version of this deliverable.
D3.15G Elastic Communication NetworkThe challenge for Health5G is to qualify and validate 5G as core connectivity infrastructure for eHealth services, applications, and devices, that can address a diverse eHealth use-cases. The consortium has defined these use-cases and their communication requirements in WP2. The use-cases are grouped in three eHealth related scenarios: Hospital, Home, and Emergency. These challenging and beyond state-of-the-art use-cases are to be realized in pilot sites and demonstrators across different countries. Within WP3, communication and cloud technologies are to be defined and developed, to enable the Health5G partners to evaluate their solutions in 5G-enabled networks and modern infrastructure.

Deliverable 3.1 – 5G elastic Communication Network reports on the 5G communication infrastructures of various pilot sites in Health^5G project. The objectives of the communication infrastructures together with cloud and IoT infrastructure are to create trial environments to evaluate emerging enabling technologies and novel eHealth services. As such, all 5G service types are supported by the network infrastructure, e.g., eMBB, URLLC, mMTC and V2X. Details of the end-to-end infrastructure components is specified including heterogeneous radio access network, core network, multi-access edge computing, network slicing, and service centric management and orchestration platforms. The availability of 5G commercial deployments allows novel communication approaches and components developed in the project to be evaluated against current 5G capabilities and to target beyond 5G requirements for eHealth. As the results, beside scientific contributions, the works reported in this deliverable also contribute to current standard and industrial proof of concept development efforts, e.g., 3GPP 5G option 3.x roll-out, ONF O-RAN and ONAP projects.

The project plan defines a 2-step timeline for this deliverable. This final iteration consolidates and amends the previous version with further analysis and reports on the final development and evaluation of eHealth 5G components.
D3.2Distributed CloudDeliverable 3.2 focuses on the resources and functions of virtualization solutions needed by the eHealth^5G services as well as their management. It specifies and implements the cloud infrastructure and its interface components. The cloud infrastructure encompasses the backend cloud, and the capability to deploy and run applications and services closer to the end users in the network edge and beyond. The technologies for distributed cloud computing, including -for example, ETSI MEC and fog computing- and its management are studied and developed in the scope of this deliverable.
The distributed cloud solution is based on the requirements originating from the use cases defined in WP2. It is envisioned to facilitate scalability, flexibility and lower delays for the eHealth services and their enabling virtualized network functions developed in D3.1. The security of deploying services of multiple parties and trust levels into the cloud is considered by applying relevant technologies developed in D5.1. The result of this deliverable is a cloud infrastructure for the eHealth^5G services integration in WP5. This deliverable also interacts with D2.1 for requirements of eHealth^5G services and D2.2 for defining the architectural components regarding the cloud infrastructure as well as the different functionalities to be supported.

Technology and feature development of the distributed cloud are coordinated by this deliverable as planned at the beginning of the project with the respective tasks in the pilot sites. This deliverable also includes information on how technologies are used and integrated into pilot sites.

Task 3.2 – Distributed Cloud will have two different versions. In this version (D3.2v1) of the deliverable 3.2, the architecture design -such as IoT multi-tenant architecture, distributed multi-cloud architecture, etc. – is documented by partners. Furthermore, the gait monitoring framework, MANO-based security monitoring framework, and the STB gateway which are based on common cloud architecture are also documented in this deliverable. Detailed documentation of all components developed in the scope of this deliverable will be documented in the next version of this task (D3.2v2).
D3.3Heterogeneous IoT NetworksThis deliverable focuses on the IoT component of the different use cases of the Health5G project. In the first version of this document, as a starting point, the main characteristics of heterogeneous IoT networks are analyzed, in order to have a better idea of what challenges must be overcome. In WSN, or wide sensor networks, different systems must be interconnected. This is usually achieved at network level through network management, which, in WSNs has been implemented as a distributed and autonomous process through Routing Protocol for Lossy Low-power Network (RPL). The IP protocol is used in homogeneous systems, like data center or core networks, while other unregulated wireless communication standards, such as Wi-Fi, BLE, IEEE 802.15.4 and ZigBee coexist in the same 2.4 GHz Industrial Scientific Medicine (ISM) band during operation.

Regarding the architecture and functions of a network, its changes can be dynamically managed using several methods which can include Inter-Domain Routing (IDR), vertical handovers, network slicing and network virtualization. The usage of wide body area networks (WBAN) enables communication with 5G networks through gateways or border routers at the network edge.

Taking this information into account, and the requirements elicited in work package 2, a common IoT architecture is proposed. This architecture must support different protocols, such as BLE or ANT+, for the communication of the devices, and their integration with both private and public networks. A way to analyze and access this information by users and professionals must also be supported.
This common architecture has been particularized for the different use cases, to cover their more precise needs, and the first steps of their implementation have been documented. In the context of the hospital scenarios, the IoT components are focused on supporting clinical devices, such as heart rate sensors, but also more niche components, such as movement or kinetic sensors. Attention has also been given to the integration with private hospital networks. Protocols such as BLE, Wifi, 5G, and OCC will be used for the communications amongst the devices.

Within the home environment, the interconnection with public networks to make the data gathered available from other locations becomes more important. Devices have to consume low power in order to last for several days, for which protocols like Zigbee, BLE or Zwave will be used. Other devices that must be supported in the home scenarios are smart watches, balances or monitoring shirts.

Lastly, some of the emergency use cases share many of its characteristics with the home use cases from an IoT point of view. The gateways used in the home scenarios will be deployed in the test road for the emergency pilots, while 5G infrastructure will provide connectivity for the IoT components. On the other hand, an emergency use cases for paramedics must support live video sent from a camera worn by the paramedic to the hospital.

The second version of this deliverable has been updated with the final details of the implementation of the different use cases. Besides, it presents the evaluation of the IoT part of the use cases, which includes the description and results of the testing, as well as a a comparison of those results to the ones obtained using 4G technology. This comparison has shown improvements in terms of better delay (lower latency) in the communications amongst devices, less packet loss and higher bandwidth, which translates, for instance in a more consistent video quality in videoconferences, or an improved detection rate in gesture recognition. 5G also offers much better transfer rates and QoS (Quality of Service), which, in some cases, directly enables use cases that would be otherwise impossible, for example, the medicine dosing use case.
D4.1Final report on connectivity in IoT networks description for eHealth scenariosWP4 focuses on designing and developing the IoT infrastructure, which is considered as the key enabler for the eHealth and 5G environment. Deliverable 4.1 focuses mainly on IoT connectivity issue as one of the key challenges in IoT networks. This document provides a background on possible sensing devices, radio technologies (e.g., IEEE 802.15.4, IEEE 802.15.6, WiFi, Bluetooth, BLE, UWB and OCC) and communication protocols (RPL routing, 6LoWPAN, CoAP) for IoT networks. It then addresses different technologies that were employed by Health5G partners. Examples have been provided by MDH, NETAS, Accellrate, Camanio, Alten, Kookmin University, Experis, Insung and Vestel. These technologies were then further analyzed in terms of connectivity challenges. Reliability and timeliness were considered as two major performance metrics for evaluating Connectivity. The integration of IoT with 5G has been addressed as the next step that requires tight collaboration with WP3.

Academic and industrial partners have considered different types of radio technologies for indoor and outdoor environment to enable IoT connectivity for eHealth applications. MDH has focused on IEEE 802.15.4 as an alternative IoT radio with long history of standardization and academic development. Unreliable wireless links and lack of a centralized network management strategy were considered as the main challenges of this technology. NETAS compared different messaging protocols, such as HTTP, CoAP, AMQP and MQTT, where the end-to-end orchestration of IoT services was described as a challenging issue. Accellrate evaluated WiFi and 5G technologies and identified network quality in different wireless networks. Camanio studied the use of cellular (4G and 5G) and WiFi technologies for Giraff and smart care, where connectivity has been recognized as their main challenging issue. Alten is working on integration of BLE and 5G technology for dosing machine. Kookmin University is working on the integration of OCC and 5G for indoor environments, where the lack of a standard gateway has been identified as their main challenge. Experis is building a gait monitoring tool using BLE and ANT+ for communication, where battery lifetime, limited channel bandwidth, real-time support, and resource virtualization are main challenges of their system. Insung is working on patient monitoring in hospitals using BLE, OCC and 5G, where reliability and latency are key challenges. Vestel is designing a middleware platform on gateways, where using multiple communication protocols is considered a challenge in their system model.

In summary, deliverable D4.1 has collected different examples of systems employing IoT technologies for eHealth applications. Main connectivity issues and challenges were addressed by different partners. Some of the challenges are defined as unreliable links, low battery lifetime, limited channel bandwidth and low processing capabilities. Moreover, partners focused on devising solutions and techniques to cope with connectivity challenges, and integration of IoT networks within 5G networks. Then, the proposed solutions were evaluated in different forms, either testbed or simulation, and the final results compared to the baselines as much as possible by different individual partners.
D4.2IoT Resource Management Description for eHealth ScenariosWP4 focuses on designing and developing the IoT infrastructure, which is considered as the key enabler for the e-Health and 5G environment. This document is the first version of deliveable 4.2, which details project partners’ objectives and progress on designing and evaluating IoT resource management approaches for 5G enabled eHealth services. The deliverable first detail ralated 3GPP standard to IoT resource management in 5G network. Subsequently, the project contributions described in this deliverable specified an end to end system for emerging eHealth services including multiple layers, i.e., device, sensor network radio and protocols, IoT gateway, 5G communication, and cloud based IoT platforms. At the device layer, low profile wareable healh sensors are the main focus of Insung application. Heterogeneous sensor networks, e.g., optical camera communication (OCC), low power radio, WiFi, are the focus of Kookmin University, Insung, NETAS and TUB. 5G D2D is studied by Insung and TUB for 5G integration. IoT data platforms are the focus of TUB, NETAS, Enforma, Experis.

Various architectural aspects and challenges for future 5G based eHealth services are discussed. With diverse expertise and close cooperation among the project partners, resource efficiency issues at each system layer are tackled with novel method and techniques to optimize the usage of power, compute, and storage resource of IoT devices, communication backends, and on device software. Kookmin University provides an approach for sensor connection using OCC and future performance improvement. Insung develop a custom protocol and gateway to integrate low profile sensor devices based on indirect 5G communication model. Resource efficient approaches at platform level are studied by Experis focusing on service orchestration, NETAS focusing on mMTC protocols, TUB focusing on semantic model and human process integration, among others. Notably, the works described also contribute to ongoing standardization efforts, e.g., IEEE standards for Optical Camera Communication 802.15.7m and 802.15.7a, 3GPP C-V2X.

The work carried out within this task is inspired by the activities and results obtained in WP2. Furthermore, it envisage interactions with two other WPs on Cloud computing and 5G (WP3), and privacy and security (WP5). This final version of the deliverable covers additional details of the specified system and results of the approaches evaluation.
D4.3Design and evaluate data collection, data management and data processing for IoT networksWP4 focuses on designing and developing the IoT infrastructure, which is considered as the key enabler for the e-Health and 5G environment. The main target of Deliverable 4.3 is data collection, data management, and data processing issues as the IoT network will generate a tremendous amount of data that needs to be stored and processed for eHealth applications. This deliverable also focuses on designing and evaluating the data collection, management, and processing methods on the IoT networks, which is one of the important parts of the Health^5G project. Efficient data collection processes need to be studied in static and dynamic topologies. It is common to experience data collection from multiple people or multiple objects in a dynamic environment, where sensors are affected by other wireless radios. Interference and mobility impose unique challenges to IoT networks that require enhancing communication protocols for efficient data collection. The concurrent data collection technique is an alternative approach to facilitate data collection in large IoT networks. Channel hopping techniques are utilized to overcome environmental interference. Data fusion and data aggregation approaches are applied to sensors and gateways to reduce the amount of data and to enhance network performance. Thus, designing novel data processing approaches for data forwarding is another issue that will be considered in this task.
In the scope of this deliverable, the detailed information is documented for data collection methods from sensors, sensor networks, IoT gateways, edge nodes, and cloud platforms by Inosens, Inova+, Insung Information, Semper-Tech, Enforma, Kookmin University, and TUB. New architectures -OCC data collection based eHealth solution, architecture of Chariot IoT Middleware, etc. – for data collection also reported by partners. Data management and processing methods and solutions – architecture of MIMO-COOK data processing, Broker (eg. RabbitMQ, Kafka), Elasticsearch, and data detection and correction techniques – are introduced in this deliverable.
The work carried out within this deliverable will be coordinated by the activities and results obtained in WP2 for requirements and architecture. Solutions of security and privacy on WP5 will be used for the methods of data collection, data management, and data processing on IoT networks by partners to provide secure and private data. This deliverable also interacts with WP3 on 5G connectivity and cloud component requirements
Task 4.3 – Design and evaluate data collection, data management and data processing for IoT networks will have two different versions. In this version (D4.3v1) of the deliverable 4.3, the architecture design, methods and solutions are documented by partners. Detailed documentation of all components/solutions developed in the scope of this deliverable will be documented in the next version of this task (D4.3v2).
D5.1Harmonized requirements for 5G-enabled eHealth applications – Design specifications of security and privacy toolsThe security and privacy on 5G enabled solutions are the objective of WP5. In this document, the requirements of the security and privacy on the infrastructure that conforms the different IoT devices and IT equipment of the use cases will be collected. Since the infrastructure may have wireless and physical connections, it is needed to understand all the configurations and risks for these connections, consequently in the document we can find general security recommendations for increase the security in the different connections and devices that conforms the project ecosystem.
The schemes and tables with information about the devices and networks in project make easy the effort to understand the security requirements and the next recommendations to implement in each case. This recommendations are focused in connections between devices with wire or with wireless protocols.
On the other hand, the data of patient that cross in the network should be protected like sensible health data to carry out the normative compliance. For this reason in the document we can find information about the patient data used in the device storage and communication between them in the use cases. With this information Nunsys has created Risk Analysis with the risks, threats and vulnerabilities that can affect components of project.
D5.2Harmonized requirements for 5G-enabled eHealth applications – Development and evaluation of security and privacy toolsWP5 focuses on the security and privacy of the project, which an integral part of the project due to the importance of protecting patients’ data in IoT, when dealing with sensitive medical data. Deliverable 5.2 focuses mainly on the development of security and privacy tools and their evaluation. For this purpose based on requirements and specifications which are defined in D5.1, two solutions are provided to respond to the requirements. This document describes these solutions which are namely Cybernate and Sirena and have been developing by Semper-Tech and Nunsys respectively.

Cybernate is a solution that aims to automate various network security analysis activities for Health^5G. Among the automated activities are risk analysis, network security monitoring, and detecting intrusion in the network and preventing that. The product utilizes the software defined network and (SDN) and network function virtualization (NFV) which are two important enablers in the 5G network. The architecture and overview of using these technologies in health^5G project were determined in WP3. Some of the Cyberante features which are provided in the cloud environment as a virtual function are included but are not limited to: Network topology scanning, visualizing and monitoring network topology, detecting an anomaly in the network, and log analysis. For this purpose, several technologies such as Openstack, SDN Opendaylight controller, Kubernetes, Cloudify, etc have been used.

On the other hand, Sirena is a cybersecurity tool that aims to collect the data in IT (Information Infrastructure) and OT ( Operative Infrastructure ) networks. The tools is composed by SIEM ( Guardian of Nozomi, focused in IoT and OT networks) and Risk Management tool (GConsulting, focused in Security Governance). The aim is discovering the assets in the network (according to IP/MAC) and tag automatically the devices with rules created by the technicians: This tags are created in human readable language to make more easy the compression by non-technical staff. Other functionalities are; prepare a list of vulnerabilities associated with assets, detecting the alarm when some vulnerabilities attack occurred in the network, perform comprehensive risk analysis in the network and control the threats.

In the document we can find research about idea of device WSensor, embryonic idea based on WIDS (Wireless Intrusion Detection), device used to monitor and control the IoT connections in all use case scenarios. The sensor could control the most known wireless connections and the correct link between 2 devices, like wearable device and patient smartphone, to check if the connection between them use strong protocol cipher or the smartphone used is the trust device.
D5.3Harmonized requirements for 5G-enabled eHealth applications – Summary report of security and privacy toolsThe document content a summary report of security and privacy tools performing will be issued together with a compendium of enhancements to be carried out in future projects.
The tools of Security and Privacy developed in the project, Cybernate and Sirena, expose here the conclusions and tests with a realistic environments similar to environments of the use case in project.
In the other hand, in the document include the conclusions and test of the security and privacy measures described in the first deliberable.
D6.1Publication, standardisation and exploitation plan (v1)This document outlines the dissemination, exploitation and standardisation plans for industrial use cases (Hospital, Home and Emergency) which were agreed upon by the Health5G project partners. The intention of these use cases is to build upon the goals of the project proposal to better define the scope of the project and pave the way for the final demonstrators and assessment results. Industry-or even company-specific difficulties that will form the basis for collaboration within the project.
D6.2Publication, standardisation and exploitation plan (v2)The objective of this deliverable to provide a latest update on the dissemination, standardisation, and exploitation plans and activities of the project.

The leader of the work package is Enforma. The deliverable is co-led by Enforma and Sempertech. Within the deliverable, the dissemination task is led by MDH, the standardisation task is led by Sempertech and the exploitation task is led by Inosens.

The consortium is composed of 26 partners from 6 different countries. Immediately observable is the presence of universities and research & technology organisations, as the project heavily relies on their performance for a successful dissemination. Next, there is a variety of pilots and partners who are in the business of either wireless communications, health IoT or smart e-health applications, meaning that there is also high expectations as far as project results’s exploitation is concerned. Finally, thanks to the presence of telecommunication operators & vendors, medical device manufacturers, and cybersecurity firms, the understanding of wireless, medical device and privacy and security standards was made possible during the project.