Adaptive Mechanism Model for the Prevention of SLA Violation in the Context of COPD Patient Monitoring

: In this paper, we introduce a new kind of Service Level Agreement(SLA) Template to better control dynamically quality of medical monitoring platform service. Our approach is based on Health care system and Health Information Technology (HIT) research area, speciﬁcally the ﬁeld of telemonitoring system for patients who su ﬀ er from chronic obstructive pulmonary disease (COPD). According to WHO statistics, COPD is the third leading cause of death worldwide. To this end, several solutions or platforms exist today to monitor COPD. Most of these platforms manage large volume of patient data. This can bring about quality and lost data problems. To address these issues, control mechanisms must be proposed and designed to improve the quality of service (QoS) on these platforms. A platform with continuously monitored QoS can save patients’ lives and reduce data quality risk. In this article, we propose an ontology that uses SLAs data from COPD monitoring platforms with dynamic data from a patient context. We dynamically calculate the number of patient data incidents and the number of service request incidents from two dynamic contexts: SLA and the patient context. If the number of incidents is higher than what is expected in the SLA, then alerts are sent to the interface parties in real time. Finally, the contribution of this article is the proposed virtual SLA template to better control SLA violation and improve quality of medical monitoring platforms services.


Introduction
During the last few decades, ubiquitous computing, particularly Health Care System and Health Information Technology (HIT), commonly referred to as pervasive/ubiquitous systems, has impacted the world of research. This revolution has materialized through many context-aware applications that have become important in different fields of research in general, and particularly in the medical field. Health Information Technology (HIT) is health technology, particularly information technology, applied to health and health care. It supports health information management across computerized systems and the secure exchange of health information between consumers, providers, payers, and quality monitors. Service level agreement (SLA) was introduced in the 1980. SLA has been used in various fields such as telecommunications, call centers, security, cloud computing and health systems. In effect, remote medical monitoring platforms manipulate large volumes [1] of patient data, and the risk of data loss or poor data quality is real. This situation can be dangerous for chronic obstructive pulmonary disease (COPD) patients in extremely exacerbated cases. Moreover, quality of service (QoS) is important in the field of monitoring systems because context-aware applications must constantly adapt their services

Related Works
Shah et al. [5] discuss the concept of QoS for the health care system. The authors explain that these systems manipulate large volumes of data and declare that quality control mechanisms are needed to improve the QoS. Shah et al. also [5] explain the importance of adapting the SLA approaches of the systems to patient monitoring. The quality of transmission for data collected from patients is a very promising area of research in the health field according to Khan et al. [4]. Besides, body area networks (BANs) are an emerging field with applications for monitoring vital signs in addition to other contextual information. Khan et al. [4] proposed a solution for the transmission of patient data. The QoS routing protocol for reliability sensitive data in hospital body area networks [4] is an approach that ensures the quality of the transmission of data collected from patients, but it does not guarantee transmission quality when there are a large number of patients to be monitored. Furthermore, this approach does not provide an agreement between the patient and the clinic about monitoring the QoS. The requirements of patients are not addressed in the definition of this approach. In the same concept of service quality approach, Kouame et al. [6] and Abawajy et al. [3] indicate that an SLA model is a document that defines negotiable service level objectives (SLOs) and constraints. Other research projects have used SLA to improve system QoS. This is the case of the SLA predictive monitoring Symmetry 2020, 12, 1575 3 of 16 project [7]. According to Comuzzi et al. [7], this research project presented a new definition of the reliability of SLA forecasts, which included terms related to the variability of the service provision scenario in which a prediction is made. The predictions were based on SLOs, but this later project was limited by the absence of dynamic control of the SLA. Another research project [7] proposed an SLA-based healthcare big data analysis and computing in cloud network by combining big data analysis techniques with data collected from patients. In addition, according to Sahoo [8], an algorithm is proposed to prioritize the patient emergency work. Despite the contribution of this research project to prioritizing patient emergency work, this project has limitations, such as non-dynamic SLA and absence of an SLA violation control mechanism. The research project name [9], Cloud SLA terms analysis based on ontology focused on the problem of SLA and QoS violation in the context of services offered by the cloud. In the context of service offered by providers, this project allows subscribing consumers to monitor SLA violation, however, the data for calculating the metrics were not extracted from a patient context and no adaptation mechanism was implemented. The authors even indicated the limitations of this approach [7] and declared: "For future work, we opt to enhance the process by automatically predicting SLA violation using context-aware systems". Finally, in the same vein, the AISel project [8] aimed to help emergency physicians or practitioners to have relevant information and knowledge about COPD patients to better monitor their health status. This project proposed a virtual organization (VOS) to share knowledge between patient and practitioner actors in compliance with data protection laws. The organization based on SLA, a multi-agent system, explained in [10] that: "Conceptual definitions of SLA parameters, metrics, and economic values, as well as resource characteristics, are given in an OWL-DL ontology W3C". The MORF project of Luke et al. [11], was a mobile patient monitoring system with two vital parameters: SAO2(Saturation Oxygen) and HR(Heart Rate). This monitoring system seamlessly integrated vital data from different health services' sensors to identify a patient's condition. The system could then take appropriate measures for timely support. It was an ontology-based system that generated alerts based on the values of vital parameters. This system used ontology-based reasoning, but the QoS aspect of the system was not addressed. Finally, Labidi et al. [12] worked on an ontology-based SLA project. The objective of this project was to help users to better understand the terms of the SLA as part of the monitoring of its violation. Labidi et al. [12] explained: "We describe the cloud SLA modelling and analyzing approach that assists consumers to automatically analyze the terms of various SLA documents". Their approach was based on static data. They [12] plan to integrate the SLA management process by automatically predicting SLA violation using context-aware systems. Table 1 describes relevant existing projects of SLA violation. [ [10][11][12] Ontology-based reasoning QoS aspects of the system are not addressed; absence of the dynamic aspect

SLA Concepts & Approach
Telemonitoring is an essential activity, not only to improve the quality of life of COPD patients, but also to help emergency physicians make monitoring decisions with real-time data. Today, we are experiencing the emergence of several remote monitoring systems for COPD patients. As these Symmetry 2020, 12, 1575 4 of 16 systems are extremely important to the health of COPD patients and the quality of care, QoS must be assessed [4,5]. Our proposal is based on a virtual dynamic SLA template that monitors the patient context and updates the violation control interface. According to [13], the SLA is the main document that guarantees the QoS provided by a computer system. It defines a service level agreement between the IT service provider and the consumer of these IT services. Kritikos et al. [14] argued that an SLA comprises a set of service levels (SLs) explicating the different performance behaviors that a service can exhibit. The different activities in the life cycle of an SLA are description, matchmaking, negotiating, monitoring, assessment, settlement, and archiving [15]. Different languages are used to design and implement the SLA. The structure of the SLA document in Web Service Agreement( WSA) format allows us to translate the SLA document into an XML file. In this XML file, we can easily extract the data with another XML-compatible language. Our approach, described in Figure 1, is based on a WSA format in an XML-compatible language. Figure 1 describes our approach to design dynamic control mechanisms for SLA in a COPD monitoring context. Indeed, our approach consists of the four steps described below.
Symmetry 2020, 12, x FOR PEER REVIEW 4 of 16 systems are extremely important to the health of COPD patients and the quality of care, QoS must be assessed [4,5]. Our proposal is based on a virtual dynamic SLA template that monitors the patient context and updates the violation control interface. According to [13], the SLA is the main document that guarantees the QoS provided by a computer system. It defines a service level agreement between the IT service provider and the consumer of these IT services. Kritikos et al. [14] argued that an SLA comprises a set of service levels (SLs) explicating the different performance behaviors that a service can exhibit. The different activities in the life cycle of an SLA are description, matchmaking, negotiating, monitoring, assessment, settlement, and archiving [15]. Different languages are used to design and implement the SLA. The structure of the SLA document in Web Service Agreement( WSA) format allows us to translate the SLA document into an XML file. In this XML file, we can easily extract the data with another XML-compatible language. Our approach, described in Figure 1, is based on a WSA format in an XML-compatible language. Figure 1 describes our approach to design dynamic control mechanisms for SLA in a COPD monitoring context. Indeed, our approach consists of the four steps described below. Data extraction consists of extracting information from the COPD patient context (vital patient parameters sign) and the SLA (metric or KPI-targets). On the SLA side, the information is the SLA items in WSA format and the rules. On the COPD side, the information source is the real-time database.
ii) Step 2: Semantic Analysis This step consists of analyzing the items, proposing rules based on information from the SLA side and on the context-aware system side. The information on the vital parameters data allows for populating in real time the COPDViolationSLA ontology model.  Steps of the Approach (i) Step 1: Extraction Data and Rules Data extraction consists of extracting information from the COPD patient context (vital patient parameters sign) and the SLA (metric or KPI-targets). On the SLA side, the information is the SLA items in WSA format and the rules. On the COPD side, the information source is the real-time database.
(ii) Step 2: Semantic Analysis This step consists of analyzing the items, proposing rules based on information from the SLA side and on the context-aware system side. The information on the vital parameters data allows for populating in real time the COPDViolationSLA ontology model.

(iii) Step 3: Semantic Reasoning
The COPD rules and patient data are used in the reasoning process to generate the dynamic control services and populate the adaptive and virtual template. Depending on the period chosen by the user, it is possible to control the SLA violation in real time. It is also possible for the user to set the control period, for example, every hour. Whenever the patient context changes, the control mechanisms based on COPD violation SLA ontology change the information in the template.

Dynamic Control Architecture for COPD Diseases Based on SLA
The architecture of COPD adaptive control is described in four layers. Figure 2 presents the architecture of the proposed model. The COPD rules and patient data are used in the reasoning process to generate the dynamic control services and populate the adaptive and virtual template.

iv) Step 4: Control Violation of SLA Service
Depending on the period chosen by the user, it is possible to control the SLA violation in real time. It is also possible for the user to set the control period, for example, every hour. Whenever the patient context changes, the control mechanisms based on COPD violation SLA ontology change the information in the template.

Dynamic Control Architecture for COPD Diseases Based on SLA
The architecture of COPD adaptive control is described in four layers. Figure 2 presents the architecture of the proposed model. The application layer presents the emergency doctor, the patient, emergency reception, and triage interface.

Application Layer
The application layer provides two categories of services (i) administrator service and (ii) functional services for the control of the SLA. The administrator service allows the emergency physician to create or delete vital sign parameters (FIEV, SAo2, HR, temperature) with their respective limits, triage agent profiles, and COPD patient profiles in the system. The functional services for SLA monitoring are available in the different interfaces described below. The control interfaces allow for the dynamic monitoring of the SLA according to the period chosen by the user.
i) Emergency Interface The application layer presents the emergency doctor, the patient, emergency reception, and triage interface.

Application Layer
The application layer provides two categories of services (i) administrator service and (ii) functional services for the control of the SLA. The administrator service allows the emergency physician to create or delete vital sign parameters (FIEV, SAo2, HR, temperature) with their respective limits, triage agent profiles, and COPD patient profiles in the system. The functional services for SLA monitoring are available in the different interfaces described below. The control interfaces allow for the dynamic monitoring of the SLA according to the period chosen by the user.

(i) Emergency Interface
The emergency physician's interface allows the SLA control by period. This interface can also receive alerts depending to the patient and SLA context. Only the emergency physician can cancel the SLA. The agent interface helps to perform triage activity by using triage dashboard at the emergency reception desk. This dashboard is dynamically updated.

(iii) Patient Interface
This interface can receive alerts depending to the patient and SLA context.

Reasoning Layer
The reasoning engine is mainly based on rules, the KPI_TARGET value extracted from the SLA, and the income data sensor. The reasoning process consists of four phases: the phase of identification of the metric items or KPI target, the detection incident phase result from the comparison of the vital data of the four parameters collected on COPD patients, the implementation phase of the SLA violation control algorithm, and the phase of populate the SLA virtual template. These rules are important for the SLA violation evaluation mechanism. The two metrics of the dynamic SLA violation monitoring mechanism in the context of COPD patient are: the number of incidents from patient data, numberIncidentData, and the number of incidents of unsuccessful patient request, NumBeRequestSend. In effect, if the number of incidents is greater than the metric defined in the KPI-Target, there is a violation of the SLA. The rules for the SLA evaluation mechanisms are important for dynamically triggering the control of the SLA according to the context-aware data and SLA document information in WSA format.

(i) Detection Incident Phase
The information extracted from the SLA can be grouped into two parts: Content items and KPI-TARGETs. The KPI-TARGETs participate in the dynamic control mechanisms of the SLA. The other content items populate the virtual adaptive SLA template. KPI_IncidentDataValue and KPI_IncidentRequestValue are important items for the mechanism of SLA control violations.
To design these rules, we consider that for every vital sign parameter, there is an interval with a minimum and a maximum value, in which the value of the sensor is a data incident. Table 2 describes these incident rules. If IncidentDataNumber > KPI_IncidentDataValue, then the data quality SLA violation alarm is triggered. There are two approaches to SLA violation control: the data incident approach and the request incident approach. For data incidents, the reasoning is performed as soon as the following data are entered into the dynamic database: FIEVSensorData, HearateSensorData, and TemperatureSensorData. For each piece of data of the parameters, the system checks through each rule to determine if it is an aberrant or erroneous value. If it is an aberrant or erroneous value, then it is classified as a data incident. The system increments the number of incident data and compares this number to the metric KPI_IncidentValue extracted from the SLA.
Concerning request incidents, the incident counter (IncidentRequestNumber) is calculated as the difference between the number of incidents (RequestSendNumber) sent to the emergency physician by patients and the number of requests (RequestReceiveNumber) confirmed or received by the emergency physician during period. The system then compares the KPI_IncidentRequestValue extracted from the SLA to the IncidentRequestNumber. If IncidentRequestNumber > KPI_IncidentRequestValue, then a QoS SLA violation alert is triggered. All these mechanisms are implemented in the SLA violation algorithm. This algorithm represents the core of the system's reasoning. Below, Figure 4 describes the algorithm of SLA violation mechanisms based on incident requests.  There are two approaches to SLA violation control: the data incident approach and the request incident approach. For data incidents, the reasoning is performed as soon as the following data are entered into the dynamic database: FIEVSensorData, HearateSensorData, and TemperatureSensorData. For each piece of data of the parameters, the system checks through each rule to determine if it is an aberrant or erroneous value. If it is an aberrant or erroneous value, then it is classified as a data incident. The system increments the number of incident data and compares this number to the metric KPI_IncidentValue extracted from the SLA.
Concerning request incidents, the incident counter (IncidentRequestNumber) is calculated as the difference between the number of incidents (RequestSendNumber) sent to the emergency physician by patients and the number of requests (RequestReceiveNumber) confirmed or received by the emergency physician during period. The system then compares the KPI_IncidentRequestValue extracted from the SLA to the IncidentRequestNumber. If IncidentRequestNumber > KPI_IncidentRequestValue, then a QoS SLA violation alert is triggered. All these mechanisms are implemented in the SLA violation algorithm. This algorithm represents the core of the system's reasoning. Below, Figure 4 describes the algorithm of SLA violation mechanisms based on incident requests.  There are two approaches to SLA violation control: the data incident approach and the request incident approach. For data incidents, the reasoning is performed as soon as the following data are entered into the dynamic database: FIEVSensorData, HearateSensorData, and TemperatureSensorData. For each piece of data of the parameters, the system checks through each rule to determine if it is an aberrant or erroneous value. If it is an aberrant or erroneous value, then it is classified as a data incident. The system increments the number of incident data and compares this number to the metric KPI_IncidentValue extracted from the SLA.
Concerning request incidents, the incident counter (IncidentRequestNumber) is calculated as the difference between the number of incidents (RequestSendNumber) sent to the emergency physician by patients and the number of requests (RequestReceiveNumber) confirmed or received by the emergency physician during period. The system then compares the KPI_IncidentRequestValue extracted from the SLA to the IncidentRequestNumber. If IncidentRequestNumber > KPI_IncidentRequestValue, then a QoS SLA violation alert is triggered. All these mechanisms are implemented in the SLA violation algorithm. This algorithm represents the core of the system's reasoning. Below, Figure 4 describes the algorithm of SLA violation mechanisms based on incident requests.  The populate phase consists of displaying the results of the evaluation algorithm for SLA violation to the virtual template. These results are therefore accessible from the interface in a dynamic mode.

Semantic Layer: Development of COPDViolationSLAOntology Domain
Ajami and Mcheick [16] explain that the semantic approach is a formalism often used to interpret complex information. With the protégé Semantic Web Reasoning Language( SWRL) tool, it is possible to perform queries based on concepts or classes [16]. Ajami and Mcheick [16] declared that: "Ontology is considered to be one of the richest semantic structures for facilitating the representation, integration, and reasoning of knowledge." (i) Structure of COPDViolationSLAOntology Module Figure 4 shows the core of the COPDViolationSlaOntology structure. Each component of this structure is an ontology that participates in the implementation of the dynamic evaluation mechanisms of SLA. Each component can be reused to enrich other SLA ontologies. The structure is modular. Each module is described in detail in the following sections. This structure can be linked to the standard COPD ontology, i.e., COPD ontology from the patient COPD Ontology component. COPDViolationSLa Ontology is therefore not an independent ontology. It is a modular ontology that is reusable and extensible with the SLA Ontology Standard. Figure 5 shows an overview of the core structure of COPDViolationSLaOntology.  ii) Populate Phase The populate phase consists of displaying the results of the evaluation algorithm for SLA violation to the virtual template. These results are therefore accessible from the interface in a dynamic mode.

Semantic Layer: Development of COPDViolationSLAOntology Domain
Ajami and Mcheick [16] explain that the semantic approach is a formalism often used to interpret complex information. With the protégé Semantic Web Reasoning Language( SWRL) tool, it is possible to perform queries based on concepts or classes [16]. Ajami and Mcheick [16] declared that: "Ontology is considered to be one of the richest semantic structures for facilitating the representation, integration, and reasoning of knowledge." i) Structure of COPDViolationSLAOntology Module Figure 4 shows the core of the COPDViolationSlaOntology structure. Each component of this structure is an ontology that participates in the implementation of the dynamic evaluation mechanisms of SLA. Each component can be reused to enrich other SLA ontologies. The structure is modular. Each module is described in detail in the following sections. This structure can be linked to the standard COPD ontology, i.e., COPD ontology from the patient COPD Ontology component. COPDViolationSLa Ontology is therefore not an independent ontology. It is a modular ontology that is reusable and extensible with the SLA Ontology Standard. Figure 5 shows an overview of the core structure of COPDViolationSLaOntology. ii) COPDPatientOntology Module The objective of this ontology in the design of SLA control mechanisms is the dynamic collection of COPD patient data. The data come from the vital signal parameters: Fiev, Heartrate, Sao2, and Temperature. The Object Property and Datatype relationships of this ontology are described in Figure  4. Only the main relationships that participate in the dynamic control mechanisms of the SLA are described in Figure 4.
The object property relationships that participate in the SLA violation evaluation mechanisms are hasTemperatureSensorData, hasHeartRateSenSorData, hasSAO2SensorData, and hasFIEVSensorData. Indeed, these relationships allow for the collection of temperature, heart rate, (ii) COPDPatientOntology Module The objective of this ontology in the design of SLA control mechanisms is the dynamic collection of COPD patient data. The data come from the vital signal parameters: Fiev, Heartrate, Sao2, and Temperature. The Object Property and Datatype relationships of this ontology are described in Figure 4. Only the main relationships that participate in the dynamic control mechanisms of the SLA are described in Figure 4.
The object property relationships that participate in the SLA violation evaluation mechanisms are hasTemperatureSensorData, hasHeartRateSenSorData, hasSAO2SensorData, and hasFIEVSensorData. Indeed, these relationships allow for the collection of temperature, heart rate, oxygen saturation, and FIEV data, respectively, from a sensor installed on each COPD patient. The collected data are evaluated according to the rules defined in the reasoning. During this period, if the collected data do not satisfy the rules policies, then the reasoning engine increments the SLA violation incident counter. When the counter reaches the threshold defined in the KPI-Target Data incident, then the inference engine allows the SLA violation alert to be triggered.
Our solution approach is based on an adaptation mechanism. In effect, the type of alert sent to the parties for the SLA monitoring changes according to the nature of the incident detected by the patient context, for example by time period, if the patient context provides erroneous data, the alert system will generate a data incident.
In another period, if it is the service incidents that are identified, the alert will generate service incidents and not data incidents. Finally, depending on the nature of the incident, the system will propose dynamically the appropriate alert and services. Table 3 presents some properties of the ontology patient module. Figure 6 describes COPD Patient Ontology Module  Figure 6 described patient ontology.
Symmetry 2020, 12, x FOR PEER REVIEW 9 of 16 oxygen saturation, and FIEV data, respectively, from a sensor installed on each COPD patient. The collected data are evaluated according to the rules defined in the reasoning . During this period, if the collected data do not satisfy the rules policies, then the reasoning engine increments the SLA violation incident counter. When the counter reaches the threshold defined in the KPI-Target Data incident, then the inference engine allows the SLA violation alert to be triggered. Our solution approach is based on an adaptation mechanism. In effect, the type of alert sent to the parties for the SLA monitoring changes according to the nature of the incident detected by the patient context, for example by time period, if the patient context provides erroneous data, the alert system will generate a data incident.
In another period, if it is the service incidents that are identified, the alert will generate service incidents and not data incidents. Finally, depending on the nature of the incident, the system will propose dynamically the appropriate alert and services. Table 3 presents some properties of the ontology patient module. Figure 6 describes COPD Patient Ontology Module   Patient ontology module is structured into two main branches: vital parameters, psychological profile parameters, and patient personal information. The vital parameter sign represents the core of the evaluation mechanism. The SLA control rules are mainly based on the values of these parameters. For example, if the current value of the temperature does not belong to minimum and maximum temperature value, then there is a data incident. The SLA control counter is then incremented. If the counter value is beyond the KPI-TARGET limits, then the SLA control mechanism triggers the SLA violation alert according to the period chosen by the user. All signatory actors are automatically informed.

iii) SLAItemsOntology Module
This ontology aims to provide information about the SLA context. For this purpose, it only addresses the description of the different items of the SLA. The items that are mainly involved in the mechanisms of control SLA are KPI-TARGET, Services and SLO. The Object Property and Datatype Patient ontology module is structured into two main branches: vital parameters, psychological profile parameters, and patient personal information. The vital parameter sign represents the core of the evaluation mechanism. The SLA control rules are mainly based on the values of these parameters. For example, if the current value of the temperature does not belong to minimum and maximum temperature value, then there is a data incident. The SLA control counter is then incremented. If the counter value is beyond the KPI-TARGET limits, then the SLA control mechanism triggers the SLA violation alert according to the period chosen by the user. All signatory actors are automatically informed.

(iii) SLAItemsOntology Module
This ontology aims to provide information about the SLA context. For this purpose, it only addresses the description of the different items of the SLA. The items that are mainly involved in the mechanisms of control SLA are KPI-TARGET, Services and SLO. The Object Property and Datatype Property that characterize them are represented in the main table. The hasKPI_Expression_IncidentRequest and hasKPI_Expression_IncidentData relationships identify the incident levels discussed with the various parties signing the SLA. Indeed, the value of the data incident counter is compared with the KPI-TARGET defined in the SLO expression related to the data: KPI_Expression_IncidentData. The same approach is true for the request incident counter value, which is also compared with the SLO expression related to the incident requests: KPI_Expression_IncidentRequest. Table 4 presents some properties of SLA items ontology. The details of the SLAItemsOntology module are described in Figure 7 below. The hasKPI_Expression_IncidentRequest and hasKPI_Expression_IncidentData relationships identify the incident levels discussed with the various parties signing the SLA. Indeed, the value of the data incident counter is compared with the KPI-TARGET defined in the SLO expression related to the data: KPI_Expression_IncidentData. The same approach is true for the request incident counter value, which is also compared with the SLO expression related to the incident requests : KPI_Expression_IncidentRequest. Table 4 presents some properties of SLA items ontology. The details of the SLAItemsOntology module are described in Figure 7 below.

iv) Violation Data Concepts and Alarm Management module
The purpose of this ontology is to record violations information and then populates the information to the template dynamically. The items or concepts that mainly participate in the SLA control mechanisms are patient and violation Sla Data Concepts. The hasAlarmViolationSlaManagementProfile and IncrementAlarmLevel links respectively associate the incident to the patient concerned and increment the incident counter to compare it to the KPI-TARGET extracted from the SLA. The hasAcquisitionRate relationship allows the emergency physician to define data collection periods. This approach makes the SLA control system more flexible. Below, Table 5 describes some properties of violation data concepts and alarm managements.

(iv) Violation Data Concepts and Alarm Management module
The purpose of this ontology is to record violations information and then populates the information to the template dynamically. The items or concepts that mainly participate in the SLA control mechanisms are patient and violation Sla Data Concepts. The hasAlarmViolationSlaManagementProfile and IncrementAlarmLevel links respectively associate the incident to the patient concerned and increment the incident counter to compare it to the KPI-TARGET extracted from the SLA. The hasAcquisitionRate relationship allows the emergency physician to define data collection periods. This approach makes the SLA control system more flexible. Below, Table 5 describes some properties of violation data concepts and alarm managements.

v) ViolationSLARequestconcepts and Alarmanagement Module
The purpose of this ontology is to record violations informations. Then, it provides the information to the template dynamically. The items that mainly participate in the SLA control mechanisms are ViolationRequest_Concepts and Request. The parameters hasNumbeRequestSent and hasNumberRequest are the data properties. Their values are calculated at the end of each AcquisitionRate collection period with the request incident control algorithm. If there is an incident request, then an alarm is generated with the hasGenerateAlarmRequest relationship. The incident request counter is then incremented with the relation hasIncrementAlarmLevelRequest. Figure 9 describes the different relations between concepts. The main branch of the ontology related to SLA control mechanisms is Request, ViolationRequest_Concepts. An incident request occurs if the sent request has not been received by the emergency physician, i.e., the status of the request is not confirmed. The difference between the number of requests sent and the number of confirmed requests in a period determines the number of request incidents. The concept or class allows the recording of these incidents and to populate the virtual template dynamically according to the period. vi) Subscription to Service Monitoring COPD Ontology Module

(v) ViolationSLARequestconcepts and Alarmanagement Module
The purpose of this ontology is to record violations informations. Then, it provides the information to the template dynamically. The items that mainly participate in the SLA control mechanisms are ViolationRequest_Concepts and Request. The parameters hasNumbeRequestSent and hasNumberRequest are the data properties. Their values are calculated at the end of each AcquisitionRate collection period with the request incident control algorithm. If there is an incident request, then an alarm is generated with the hasGenerateAlarmRequest relationship. The incident request counter is then incremented with the relation hasIncrementAlarmLevelRequest. Figure 9 describes the different relations between concepts.

v) ViolationSLARequestconcepts and Alarmanagement Module
The purpose of this ontology is to record violations informations. Then, it provides the information to the template dynamically. The items that mainly participate in the SLA control mechanisms are ViolationRequest_Concepts and Request. The parameters hasNumbeRequestSent and hasNumberRequest are the data properties. Their values are calculated at the end of each AcquisitionRate collection period with the request incident control algorithm. If there is an incident request, then an alarm is generated with the hasGenerateAlarmRequest relationship. The incident request counter is then incremented with the relation hasIncrementAlarmLevelRequest. Figure 9 describes the different relations between concepts. The main branch of the ontology related to SLA control mechanisms is Request, ViolationRequest_Concepts. An incident request occurs if the sent request has not been received by the emergency physician, i.e., the status of the request is not confirmed. The difference between the number of requests sent and the number of confirmed requests in a period determines the number of request incidents. The concept or class allows the recording of these incidents and to populate the virtual template dynamically according to the period. vi) Subscription to Service Monitoring COPD Ontology Module The main branch of the ontology related to SLA control mechanisms is Request, ViolationRequest _Concepts. An incident request occurs if the sent request has not been received by the emergency physician, i.e., the status of the request is not confirmed. The difference between the number of requests sent and the number of confirmed requests in a period determines the number of request incidents. The concept or class allows the recording of these incidents and to populate the virtual template dynamically according to the period.

(vi) Subscription to Service Monitoring COPD Ontology Module
This ontology is not directly involved in the control mechanisms of the SLA. However, it provides important information to enable the control mechanisms to work correctly and above all, to adapt the interfaces to the context. Indeed, it provides information about the connected patient and the services affected by the SLA. The items that mainly participate in the SLA control mechanisms are: patients, services, and SLA actors. The hasSubscribeSystemCpodMonitoring relationship allows the subscription of the COPD patient, the emergency physician and the triage agent. For each contract with the COPD monitoring system, a service or services are assigned to the subscribed patient. Table 6 describes the relations between the concept service components. This ontology is not directly involved in the control mechanisms of the SLA. However, it provides important information to enable the control mechanisms to work correctly and above all, to adapt the interfaces to the context. Indeed, it provides information about the connected patient and the services affected by the SLA. The items that mainly participate in the SLA control mechanisms are: patients, services, and SLA actors. The hasSubscribeSystemCpodMonitoring relationship allows the subscription of the COPD patient, the emergency physician and the triage agent. For each contract with the COPD monitoring system, a service or services are assigned to the subscribed patient. Table  6 describes the relations between the concept service components.

Acquisition Layer
The collected data refer to the parameters presented in the table below but for the evaluation of the SLA, we focused on vital parameters only. Table 7 describes the information of the patient parameters. There are two categories of data. In first category, there are the static data: age, BMI, gender, and medical history. These data are available in the patient's medical records and only the emergency physician can consult them. In the other category, there are the dynamic data collected from the sensors: vital parameters and symptom parameters. The decisions in a monitoring system are fundamentally based on the quality of the data. Incorrect data can influence the emergency physician's decision-making process. A wrong decision can hurt the patient's health. Evaluating the data aspects of the SLA is intended to improve the QoS. The other aspect of the SLA assessment

Acquisition Layer
The collected data refer to the parameters presented in the table below but for the evaluation of the SLA, we focused on vital parameters only. Table 7 describes the information of the patient parameters. There are two categories of data. In first category, there are the static data: age, BMI, gender, and medical history. These data are available in the patient's medical records and only the emergency physician can consult them. In the other category, there are the dynamic data collected from the sensors: vital parameters and symptom parameters. The decisions in a monitoring system are fundamentally based on the quality of the data. Incorrect data can influence the emergency physician's decision-making process. A wrong decision can hurt the patient's health. Evaluating the data aspects of the SLA is intended to improve the QoS. The other aspect of the SLA assessment concerns the requests transmitted to the emergency physician by the patient. An request incident triggered when a request sent by the patient is not received by the emergency physician for any reason.

Design of Virtual Adaptive Template SLA
The purpose of a virtual SLA is to dynamically monitor the QoS guarantees of the SLA in a COPD patient monitoring context. This template has two parts. Part 1 represents the offered service that has been validated by the parties. If the data of Part 1 is changed, the virtual template will also be modified in real time. In addition, part 2 presents the dynamic control elements of the SLA. This part adapts dynamically according to the data of the patient context and the context-aware ubiquitous system. Finally, the information described in these two parts is extracted from the ontology presented in the previous sections. To allow a better understanding of the virtual SLA template, important concepts are presented. According to reference [17], the SLA template must have important information: SLO, KPI-TARGETs, Condition, and Constraints. Figure 11 describes the virtual SLA template. concerns the requests transmitted to the emergency physician by the patient. An request incident triggered when a request sent by the patient is not received by the emergency physician for any reason.

Design of Virtual Adaptive Template SLA
The purpose of a virtual SLA is to dynamically monitor the QoS guarantees of the SLA in a COPD patient monitoring context. This template has two parts. Part 1 represents the offered service that has been validated by the parties. If the data of Part 1 is changed, the virtual template will also be modified in real time. In addition, part 2 presents the dynamic control elements of the SLA. This part adapts dynamically according to the data of the patient context and the context-aware ubiquitous system. Finally, the information described in these two parts is extracted from the ontology presented in the previous sections. To allow a better understanding of the virtual SLA template, important concepts are presented. According to reference [17], the SLA template must have important information: SLO, KPI-TARGETs, Condition, and Constraints. Figure 11 describes the virtual SLA template. Figure 11. Virtual SLA template.
Concerning the SLO, Labidi et al. [17] explained: "The Service Level Objective element in a guarantee term is also expressed as an assertion over service attributes and/or external factors such as date, time. However, most often a Service Level Objective is expressed as a target for a Key Performance Indicator (KPI) such as average response time, completion time". Concerning KPI-Targets, Labidi et al. [17] concluded: "A KPI Target expresses a service level objective by specifying a target for a key performance indicator (KPI) such as average response time, availability, etc. associated with a service. The definition of a KPI is outside the scope of the current specification".

Implementation
We used the Ontopy platform to implement our prototype. According to [14] Ontopy is a free software Python module (GNU LGPL v3 license) for ontology-oriented programming and agile ontology-based application development. The Python 3.4 language was chosen because it is a dynamic object language with multiple inheritance. Concerning the SLO, Labidi et al. [17] explained: "The Service Level Objective element in a guarantee term is also expressed as an assertion over service attributes and/or external factors such as date, time. However, most often a Service Level Objective is expressed as a target for a Key Performance Indicator (KPI) such as average response time, completion time". Concerning KPI-Targets, Labidi et al. [17] concluded: "A KPI Target expresses a service level objective by specifying a target for a key performance indicator (KPI) such as average response time, availability, etc. associated with a service. The definition of a KPI is outside the scope of the current specification".

Implementation
We used the Ontopy platform to implement our prototype. According to [14] Ontopy is a free software Python module (GNU LGPL v3 license) for ontology-oriented programming and agile ontology-based application development. The Python 3.4 language was chosen because it is a dynamic object language with multiple inheritance. Figure 12 describes the architecture of the Ontopy platform.
Symmetry 2020, 12, x FOR PEER REVIEW 14 of 16 Figure 12 describes the architecture of the Ontopy platform.
We designed the ontology with Protégé, a tool for Ontology Web Language, Decidable Language(OWL/DL) projects. We exported classes, instances, and relations into the Ontopy platform. We used Python 3.4 to implement a simple application prototype. Our implementation scenario checks the feasibility of the SLA evaluation virtual model. To this end, we defined three incidents of data and two incidents of service request acceptable per month as the SLA KPI_TARGET value. We simulated the data for the patient context with four files containing the temperature parameter. The temperature values in the files f1, f2, f3, and f4 are erroneous or aberrant values. The structure of the files is f (idpatient, temperature): f1(1,20), f2(2,55), f3(3,60), and f4(4,100). The program reads these files and calculates the number of incidents, which is 4, and checks that 4(IncidentDataNumber) > 3(KPI_TARGET value of the SLA). Then, the prototype triggers the SLA violation alert and the virtual template publishes all the SLA violation information. Figure 13 describes the results of this test with Python 3.4. Figure 13. Violation incident data test.
For request incidents, we created two files, A1 and A2. Both files contain, respectively, the number of requests sent by the COPD patient to the emergency physician and the number of requests received by the emergency physician. The structure of the files is A (id, NumberRequest): A1(1,6); A2 (2,3). The program reads the files and calculates the difference between the sent and received requests. Then the program compares this result to KPI-TARGET value extracted from the SLA. The system triggers the SLA violation alert and the dynamic model publishes these results.
The Figure 14 presents a simple example of an incident request test.
We designed the ontology with Protégé, a tool for Ontology Web Language, Decidable Language(OWL/DL) projects. We exported classes, instances, and relations into the Ontopy platform. We used Python 3.4 to implement a simple application prototype. Our implementation scenario checks the feasibility of the SLA evaluation virtual model. To this end, we defined three incidents of data and two incidents of service request acceptable per month as the SLA KPI_TARGET value. We simulated the data for the patient context with four files containing the temperature parameter. The temperature values in the files f1, f2, f3, and f4 are erroneous or aberrant values. The structure of the files is f (idpatient, temperature): f1(1,20), f2(2,55), f3(3,60), and f4(4,100). The program reads these files and calculates the number of incidents, which is 4, and checks that 4(IncidentDataNumber) > 3(KPI_TARGET value of the SLA). Then, the prototype triggers the SLA violation alert and the virtual template publishes all the SLA violation information. Figure 13 describes the results of this test with Python 3.4.
Symmetry 2020, 12, x FOR PEER REVIEW 14 of 16 Figure 12 describes the architecture of the Ontopy platform.
We designed the ontology with Protégé, a tool for Ontology Web Language, Decidable Language(OWL/DL) projects. We exported classes, instances, and relations into the Ontopy platform. We used Python 3.4 to implement a simple application prototype. Our implementation scenario checks the feasibility of the SLA evaluation virtual model. To this end, we defined three incidents of data and two incidents of service request acceptable per month as the SLA KPI_TARGET value. We simulated the data for the patient context with four files containing the temperature parameter. The temperature values in the files f1, f2, f3, and f4 are erroneous or aberrant values. The structure of the files is f (idpatient, temperature): f1(1,20), f2(2,55), f3 (3,60), and f4(4,100). The program reads these files and calculates the number of incidents, which is 4, and checks that 4(IncidentDataNumber) > 3(KPI_TARGET value of the SLA). Then, the prototype triggers the SLA violation alert and the virtual template publishes all the SLA violation information. Figure 13 describes the results of this test with Python 3.4. Figure 13. Violation incident data test.
For request incidents, we created two files, A1 and A2. Both files contain, respectively, the number of requests sent by the COPD patient to the emergency physician and the number of requests received by the emergency physician. The structure of the files is A (id, NumberRequest): A1(1,6); A2 (2,3). The program reads the files and calculates the difference between the sent and received requests. Then the program compares this result to KPI-TARGET value extracted from the SLA. The system triggers the SLA violation alert and the dynamic model publishes these results.
The Figure 14 presents a simple example of an incident request test.

Methods
OWL/X ML parser Figure 13. Violation incident data test.
For request incidents, we created two files, A1 and A2. Both files contain, respectively, the number of requests sent by the COPD patient to the emergency physician and the number of requests received by the emergency physician. The structure of the files is A (id, NumberRequest): A1(1,6); A2(2,3). The program reads the files and calculates the difference between the sent and received requests. Then the program compares this result to KPI-TARGET value extracted from the SLA. The system triggers the SLA violation alert and the dynamic model publishes these results.
The Figure 14 presents a simple example of an incident request test.

Conclusions and Future Works
Several contributions of this study can be noted. One of the major contributions is that, however large or small the volume of data manipulated by the COPD monitoring platforms, our SLA violation control mechanism allows us to monitor the quality of the data. Firstly, our solution realizes the dynamic evaluation of the SLA by extracting relevant data from the SLA documents and extracting dynamic data from the COPD patient to populate an SLA violation control ontology. Secondly, our solution provides virtual and adaptive SLA template for SLA violation prevention. Thirdly, virtual SLA template is accessible to all SLA parties from their context-aware application interface. Finally, the implementation of the SLA approach to better control quality of medical monitoring platform service is a relevant step for Health Care System and Health Information Technology (HIT) research area. In our future research projects, we will investigate if patient data collection periods influence the SLA violation.

Conclusions and Future Works
Several contributions of this study can be noted. One of the major contributions is that, however large or small the volume of data manipulated by the COPD monitoring platforms, our SLA violation control mechanism allows us to monitor the quality of the data. Firstly, our solution realizes the dynamic evaluation of the SLA by extracting relevant data from the SLA documents and extracting dynamic data from the COPD patient to populate an SLA violation control ontology. Secondly, our solution provides virtual and adaptive SLA template for SLA violation prevention. Thirdly, virtual SLA template is accessible to all SLA parties from their context-aware application interface. Finally, the implementation of the SLA approach to better control quality of medical monitoring platform service is a relevant step for Health Care System and Health Information Technology (HIT) research area. In our future research projects, we will investigate if patient data collection periods influence the SLA violation.