## 3 Proposed Model
### Dynamic Control Architecture for COPD Diseases Based on SLA
#### 3.2.3 Semantic Layer: Development of COPDViolationSLAOntology Domain  
[PERSON] and [PERSON] [16] explain that the semantic approach is a formalism often used to interpret complex information. With the protege Semantic Web Reasoning Language(SWRL) tool, it is possible to perform queries based on concepts or classes [16]. [PERSON] and [PERSON] [16] declared that: _\"Ontology is considered to be one of the richest semantic structures for facilitating the representation, integration, and reasoning of knowledge.\"_  
* 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. * 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: Five, 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, hasSAO2 SensorData, and hasFIEVSensorData. Indeed, these relationships allow for the collection of temperature, heart rate, oxygen saturation, and FIFV 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. Figure 5: Core structure of COPDViolationSlaOntology. 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. * SLAItemsOntology Module  
This ontology aims to provide information about the SLA context.