Dynamic Quality Management of Emergency Systems Via Rich Explicit Constraints

Conference on Web and Information Technologies
May 9 12, 2013
Dynamic Quality Management of Emergency Systems via Rich Explicit Constraints
A. Alti, H. Reffad
UFAS, University of Stif Algeria Email : altiadel2002@yahoo.fr
P.Roose, S. Laborie
LIUPPA / IUT Bayonne, Anglet - France Email : Prenom.Nom@univ-pau.fr
Outlines
Introduction Context and Limitations Semantic Generic Context Model Context Situation aware Framework Demo Conclusion
May 9 12, 2013
Context and Limitations
Device heterogeneity
Execution Context
Document heterogeneity
Limitations : Adaptation implicit No portability No genericity No explicit constraints
SEMANTIC GENERIC CONTEXT MODEL
May 9 12, 2013
Services, Facet and Constraints

Context Facet Document Facet Hardware Facet
User Services
Temperature Services
Temporal Services
Situation Services
Audio Services
Image Services
Device Services
Software Services
User Location Services
SetSituation (Very Hot)
BatteryServices
GetTime () ="Winter Period"
SetAudio (Exclude) GetTemperature () ="High"

Constraint 1 Constraint 2
SetImage (Include)
GetUserLocation () = "close" office

AND AND
GetBatteryLevel () = Low
GetUserLocation () = "close" office
May 9 12, 2013
Hirerachical context model

Level 1 Level 2 Car Close Office Conference After Level 3 Level n-1 Level n Longitude 12 GPS Latitude 25 Altitude 41
...
qualitative
quantitative
Level 1 : The qualitative term that one may want to use in a context model. Level 2: This level corresponds to the potential services which are associated to the qualitative terms Level i: Subdomains may be defined in order to associate a qualitative term to more specific application domains Level n: This is the lower level and it refers to the corresponding quantitative values which are associated to the qualitative term for a specific context.
May 9 12, 2013
OWL semantic context model
Services
May 9 12, 2013
Context Situation aware Framework

Temperature CO2 Door
COLLECTOR1
DATA AGREGATION
COLLECTOR2
Syntaxic Data
COLLECTOR3
Server Situation identification

Conference on Web and Information Technologies Semantic Data
Inference Engine
May 9 12, 2013

CPU Load Battery Level
COLLECTOR1
DATA AGREGATION
Free Memory
COLLECTOR2
Syntaxic Data
COLLECTOR3
Server Reconfiguration Quality Deployement

Situation identification
Inference Engine
Semantic Data
May 9 12, 2013

Context Situation aware Framework in Android Platform Context Situation aware Framework in Windows Platform
9
Conference on Web and Information Technologies May 9 12, 2013

Generic Interface
Generic Interface
services Service
memory
Service
Battery
Service
Cpu
Service
memory
Sensors
Sematic Context Model
Service Cpu
Service Battery
Service Screen
Sensors
May 9 12, 2013
Demo
Zone 1 Device .. Zone N Conference Room
Mobile Email
Co2 Temperature
Conference
Effector
Fire Theft
Door
PC ( Inference Engine + Collecteor)
May 9 12, 2013
Demo
Situation Conference Rule IF GetSoundLevel() = high AND GetUserLocation() =CloseConferenceRoom THEN SetSituation(Conference) IF GetDoorState () = open AND GetUserLocation() =CloseMesum AND GetPeriodHour () =after work THEN SetSituation (Theft)
Theft
Fire
IF GetTemperatureLevel() =High AND GetUserLocation() = CloseConferenceRoom AND GetSeasonHour() = 'duringWinter' THEN SetSituation(Very_Hot).
IF GetSituation()=Very_Hot AND GetCO2Level() =High THEN SetSituation(Fire).

IF GetSituation()=Fire THEN SetSituation(Alarm)
May 9 12, 2013
Demo
May 9 12, 2013
Demo
User Constraint : IF Battery Level is Low Then Exclude Video and Include Images
A First Simple Scenario

The application is first of all deployed in a favorable context, where neither the stations nor the network are saturated.
The context is sufficient to provide both video and audio. If we receive a video stream packaged with RealVideo in a 120 x120 window at 10 frames / second with Pocket PC audio quality, rate of 56Kbits is sufficient
A Second Scenario Eemergency Situation Incident of Fire Situation Context : Battery level = 30 % (low) and Temperature sensor provides temperature data in Celsius unit every 10 min
The current context is not sufficient to provide video and we must react to new emergency situation: Fire We adapt services in consequences : coloured map service or black and white map service of the environment.
Context : Battery level = 10 % (very low) and temperature sensor provides temperature data is become in failure State
The application must continue to operate even with another temperature sensor which measure temperature data in Kelvin unit. The battery level is very low, we must deploy black and white map of the environment.
May 9 12, 2013
Demo
Tempertaure meseaured in C
May 9 12, 2013
Conclusion
Our Goals: Describe multiple context informations Model real-life user constraint A multi-platform model Our proposition: Facets : Device, document, context Explicit constraints Service-based
GENERIC EXPRESSIVE PORTABLE
May 9 12, 2013

May 9 12, 2013
Questions

Dynamic Quality Management of Emergency Systems Via Rich Explicit Constraints

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Dynamic Quality Management of Emergency Systems Via Rich Explicit Constraints

Hochgeladen von

Copyright:

Verfügbare Formate

Conference on Web and Information Technologies

May 9 12, 2013