A Comparison of Context-Aware Application Development Infrastructures and Context Representation .


52 views
Uploaded on:
Description
A Comparison of Context-Aware Application Development Infrastructures and Context Representation. Dev Oliver, Nikhil Yadav CISE Department, University of Florida, Gainesville, Florida, USA . Outline. Introduction Problems and proposed solutions in Pervasive Computing Infrastructures
Transcripts
Slide 1

A Comparison of Context-Aware Application Development Infrastructures and Context Representation Dev Oliver, Nikhil Yadav CISE Department, University of Florida, Gainesville, Florida, USA

Slide 2

Outline Introduction Problems and proposed arrangements in Pervasive Computing Infrastructures Middleware Goals Middleware Architectures GAIA Meta-working System Service-situated Context Aware Middleware (SOCAM) Context-Aware Middleware Utilizing Asynchronous Communication Middleware in view of Application Packages and the Kernel Runner Comparisons Conclusions

Slide 3

Introduction Problems and proposed arrangements in Pervasive Computing Infrastructures Middleware Goals Middleware Architectures GAIA Meta-working System Service-arranged Context Aware Middleware (SOCAM) Context-Aware Middleware Utilizing Asynchronous Communication Middleware in light of Application Packages and the Kernel Runner Comparisons Conclusions

Slide 4

Introduction Numerous middleware frameworks and model frameworks for creating setting mindful applications Need for Middleware and Standards for decoupling programming and application improvement from physical space development and mix TCP/IP, customer server models, appropriated OS for organized PCs. Comparative ideas required for Pervasive registering situations

Slide 5

Introduction Problems and proposed arrangements in Pervasive Computing Infrastructures Middleware Goals Middleware Architectures GAIA Meta-working System Service-situated Context Aware Middleware (SOCAM) Context-Aware Middleware Utilizing Asynchronous Communication Middleware in view of Application Packages and the Kernel Runner Comparisons Conclusions

Slide 6

Problems and Proposed arrangements Problem: Non-adaptable combination Low level data on sensors and actuators required. Tedious to incorporate and test for clashes. Arrangement: Self Integration Allow programmed mix inside the space; desirable over perspective components as programming administrations and space as runtime environment Problem: Closed world Assumption New innovations from 3 rd Party merchants can\'t be included that effectively as innovation advances after some time. Arrangement: Standard Adoption of benchmarks like OSGi and UPnP by most extreme number of sellers, so expansion of outsider components turns out to be simple

Slide 7

Problem: Obsolete Concepts get to be out of date after some time… e.g. setting mindfulness and administration entryways Solution: Semantic Exploitation and Intelligent Middleware outline Allow added administrations to publicize their nearness and register administrations. Administration definition + incorporation are included. Middleware for machines e.g. keen attachments. Joining these, usefulness can create after some time.

Slide 8

Introduction Problems and proposed arrangements in Pervasive Computing Infrastructures Middleware Goals Middleware Architectures GAIA Meta-working System Service-situated Context Aware Middleware (SOCAM) Context-Aware Middleware Utilizing Asynchronous Communication Middleware taking into account Application Packages and the Kernel Runner Comparisons Conclusions

Slide 9

Middleware Goals Presenting sensors and actuators as programming administrations in a runtime domain (Smart space) Faster prototyping utilizing administration perspectives and element libraries Browsing and learning backing… to help in full Semantic Exploitation (amassing connection for occurrence) (Middleware Infrastructures take after next)

Slide 10

Introduction Problems and proposed arrangements in Pervasive Computing Infrastructures Middleware Goals Middleware Architectures GAIA Meta-working System Service-arranged Context Aware Middleware (SOCAM) Context-Aware Middleware Utilizing Asynchronous Communication Middleware in light of Application Packages and the Kernel Runner Comparisons Conclusions

Slide 11

The GAIA Meta-working System Features Include: Distributed OS/segments Decoupled correspondence model Context Registry and Query administrations Component nearness recognition Browsing offices Virtual Directory Hierarchy for records Application Partitioning among Devices

Slide 12

The GAIA Architecture

Slide 13

Distributed OS/Components GAIA depends on dispersed segments (sensors and actuators) and applications CMC in charge of dealing with these i.e. stacking, emptying, exchanging and making all GAIA segments

Slide 14

Decoupled Communication Model Event Manager gives this. In view of suppliers, buyers and channels Forwarding of supplier\'s occasions to purchasers enrolled with the channel Fault tolerant: Supplier supplanted with imitation if there should arise an occurrence of disappointment

Slide 15

Context Registry and Querying administrations Applications permitted to enlist and inquiry a specific setting administration Allows application adaption Context registry can be gazed upward by applications to discover what administration they require

Slide 16

Component Presence Detection Presence Service in charge of this. Keeps up redesigned data about dynamic space parts i.e. gadgets, applications and administrations Digital Entity Presence subsystem: applications and administrations send heartbeats… no pulse got => Entity has left the dynamic space Physical Entity nearness subsystem goes about as an intermediary executing a beaconing instrument. Open Infrastructure, can utilize distinctive gadget drivers and calculations

Slide 17

Browsing Facilities The space storehouse stores all HW and SW substance data e.g. by name, sort, proprietor Applications permitted to skim and recover an element taking into account particular traits Applications can find out about substances entering and leaving the dynamic space through the nearness administration channels

Slide 18

Virtual Directory Hierarchy for Files Context File framework in charge of this. Clients offered access to connection at whatever point they require it Makes individual information accessible to applications; sorts out information to encourage finding pertinent material for applications and clients; recover information in light of client inclinations or gadget qualities CFS Aware of various sorts of setting characterized and permits mounting of various connections into one fundamental application space Virtual Directory Hierarchy: e.g. /area:/RM2401/circumstance:/meeting Architecture made out of mount and File servers

Slide 19

Application Partitioning among gadgets Application system in charge of this Allows clients to adjust how to information/yield information to and from the application. gives clients a chance to build, run or adjust existing applications to dynamic spaces.

Slide 20

Introduction Problems and proposed arrangements in Pervasive Computing Infrastructures Middleware Goals Middleware Architectures GAIA Meta-working System Service-situated Context Aware Middleware (SOCAM) Context-Aware Middleware Utilizing Asynchronous Communication Middleware in view of Application Packages and the Kernel Runner Comparisons Conclusions

Slide 21

Service Oriented Context-Aware Middleware (SOCAM) Features Include: OSGi based; utilizes JVM => stage freedom Context Registry and Query administrations Service Location (segment recognition) Ontology based Context thinking Support for numerous home systems administration advances Hosting of Multiple administrations from various suppliers on a solitary entryway stage Various levels of framework security, computerized marking of downloaded administrations and article access control.

Slide 22

SOCAM Architecture

Slide 23

OSGi construct SOCAM is proposed in light of top of administration arranged OSGi open standard. OSGi characterizes a lightweight system for conveying and executing administration arranged applications. Administration functionalities include: introducing, actuating, deactivating, overhauling and expelling administrations. Can give a hearty and possibly interoperable base for building, provisioning and overseeing setting mindful administrations in keen homes and past.

Slide 24

Context Registry and Query administrations SLS, permits promotion of administrations by CP and CI for simple area Context Providers registers with SLS to be found by others. They can be either outer or inward in view of where connection is acquired from Context Interpreters are made out of a setting reasoner and a connection learning base. Reasoner utilizes preloaded induction rules and so on to decide. Connection Knowledge base uses Tbox, Abox, predefined cases stacked amid framework start and detected setting occasions stacked amid runtime. Occasion activating instrument used to redesign specific setting examples.

Slide 25

Context-mindful administrations: Applications utilizing distinctive levels of setting data, adjusting their conduct as indicated by the present connection. Questions SLS to discover setting it requires. A typical method for creating setting mindful applications is to indicate activities in light of connection changes. Application designers can indicate administers and determine strategy to conjure when the condition turns out to be valid.

Slide 26

Service Location (segment recognition) SLS...wide range revelation of setting suppliers is took into consideration. Tracks and adjusts to changes initiated when including/expelling sensors or reconfiguring connections. Multi. coordinating component permitting commercial of connection in different structures. (locatedIn John ?x) is a question case. The administration will first load the setting ontologies put away in the database and the connection occurrences promoted by various connection suppliers, and afterward apply semantic coordinating to discover which connection supplier gives this data. On the off chance that a match is discovered, it sends the application the reference to the CP.

Slide 27

Ontology based Context thinking Supports philosophy and standard based thinking. The OWL thinking framework bolsters builds for depicting properties and classes, including connections between classes. RDF mapping rules required to perform RDF blueprint thinking for instance. Client characterized principle based thinking. Forward + in reverse tying + crossover execution mode to perform thinking is utilized.

Slide 28

Support for various home systems administration advancements OSGi

Recommended
View more...