Presented by

Mr. Abhishek Kumar Mr. Piyush Nayak Student IES IPS Academy

ABSTRACT
The big challenge related to the contemporary research on

ubiquitous and pervasive computing is that of seamless integration. In this paper, we present middleware-level resource management service for situated displays in public smart spaces, acting as a scheduler and an arbiter for mobile clients. We have implemented the discovery service and subjected it for alpha testing in an indoor setting. We report a proofof-concept implementation of the Screen Spot system and we demonstrate an approach of visualizing the discovery results to the user.

INTRODUCTION
A typical usage scenario in this research field involves a mobile user with a smart phone, PDA or other similar networked terminal, utilizing services from the ambient surroundings. STEPS 1) the user issues a discovery request including certain discrete keywords to the service repository. 2) which in turn performs static matchmaking to return a set of matching service descriptions from the directory.

3) the mobile client utilizes this proxy to control and exchange data with the remote service. In the case of distributed and non-directory-based discovery protocol, two operational modes are possible. 1) The pull-based model. 2) The push-based model.

The Pull based model & The Push based model

client issues service requests as multicast messages to the network in order to discover suitable service candidates.

model, the service implementations publish advertisements of their presence to the network, and clients can tap to this traffic to perform discovery.

Usage Scenario
These hotspots in conjunction with the personal mobile devices allow the deployment of distributed application structures that realize multimodal user interfaces towards the users.

Overview
The mobile terminals connect as pub/sub clients to the

routing subsystem through the IEEE 802.11b panOulu WLAN access network. Individual Resource Manager contain terminal computation entities that act as containers for the respective RM instances and interface the pub/sub routers through IEEE 802.3 Ethernet links.

 In addition to the aforementioned connectivity, the mobile

terminals also engage ad-hoc communications with the ambient RM instances through Bluetooth.
Through this short-range ad-hoc connectivity, we want to

physically enforce the aspect of spatial proximity to the computation.

hot-spot around the situated display, and we utilize this coverage area as a virtual watchdog for monitoring the proximity between user and the display.

 Through this functionality, the leasing for the display can be monitored in a way that user can terminate the leasing session merely by walking away from the display thus we inhibit an implicit interaction session termination through the Bluetooth watchdog beacons.

High-level architecture of Screen Spot.

Component structure on a situated display

IEEE 802.11b WLAN

networking transmission methods. 802.11b has a maximum raw data rate of 11 Mbit/s and uses the CSMA/CA media access method defined in the original standard. Due to the CSMA/CA protocol overhead, in practice the maximum 802.11b throughput that an application can achieve is about 5.9 Mbit/s using TCP and 7.1 Mbit/s using UDP.

IEEE802.3 Ethernet
IEEE 802.3 is a working group and a collection

of IEEE standards produced by the working group defining the physical layer and data link layer's media access control (MAC) of wired Ethernet. This is generally a local area network technology with some wide area network applications. Physical connections are made between nodes and/or infrastructure devices (hubs, switches, routers) by various types of copper or fiber cable.

Resource Manager
This instance resides within each situated display, and

is responsible for the allocation and scheduling of the resource instance, as well as the execution of service instances residing on the resource. This design reflects the tight coupling of the resource with the associated services, which is essential in the case of stateful distributed applications. During the execution, it may be necessary to inject the application-related data from the client side to the respective ambient resource to reflect the state of the distributed application.

 The Resource Manager component forms the core of

the RM instance and coordinates the other components. It realizes the discovery interface towards the mobile clients, and controls the execution of the discovery procedure.

Policy Manager
Policy Manager acts as a container and controller for

the usage policies set for this resource. A single usage policy is an aggregation of resource utilization rules for a single user group. These include an access control list with usernames of the group, the renewal policies allowed for the group, as well as the role that the group has in the smart space, i.e. employee vs. guest.

Fuego pub/sub client

towards the publish/subscribe routing system. The subscription semantics utilized in the discovery service are hybrid in nature. First, the routing system realizes a separate subscription channel for the discovery traffic. Secondly, the RM instance on each ambient resource subscribes only to the messages targeted to this group of instances.

 This decoupled routing scheme allows a flexible

maintenance of the smart space, which isnt difficult and sometimes impossible to perform through a complete shutdown and restart. A discovery request sent to the network is only received by running resource managers that have an active and subscription, and thus are ready for resource utilization and service deployment.

Lease Queue
Lease Queue maintains the queuing of the leases set

for the resource. Instance by mobile clients. The basic queuing scheme is FIFO. It should be noted that pre-emptive scheduling of users in this setting is highly counterproductive, especially when considering stateful applications.

Service Proxy
Service Proxy acts as a singleton interface towards the

core, and allows the execution of the service binaries residing within this resource object. The service binaries are tightly coupled with the resource instance and the users issue utilization requests to the resource by setting leases to the associated lease queue. Each lease must be associatively connected to a deployable service binary.

BT Server
BT Server implements the physical Bluetooth

connectivity around the ambient hotspot. This spatial connectivity has two distinct roles in our system. First, users residing within the Bluetooth coverage area of a single hotspot can perform discovery requests to the rest of the system through the local hotspot. Secondly, during the resource deployment, the Bluetooth coverage area acts as a virtual spatial watchdog.

Functionality
The main functionality of the system is to perform

discovery requests within a physical smart space domain and return multidimensional resource information back to the user. The attachment points for end users in the system are Bluetooth coverage areas around the ambient hotspots that provide resources and deployable services.

Virtual spatial ranges from the seed instance

 As the user is residing within an ambient hotspot when the

discovery is initiated, the RM instance managing this hotspot becomes the seed for the discovery request. From this seed, other RM instances within the smart space domain appear on different virtual spatial ranges, denoting relative physical distances between the hotspots.

 Range zero consists of the local hotspot, and the successive

ranges are dependent on the location model configured to the system. Range 1 can for example denote hotspots within the same floor as the seed instance. Range 2 denotes instances within the next floor up. Outer ranges denote other areas within the smart space physical domain.

THANK YOU