sszg531 introduction to communication technologies

8/6/2019 SSZG531 Introduction to Communication Technologies

http://slidepdf.com/reader/full/sszg531-introduction-to-communication-technologies 1/34

Communication Technologies in

Pervasive Computing

Dr. Rahul BanerjeeComputer Science & Information Systems Group

Birla Institute of Technology & Science, PilaniRajasthan – 333 031, INDIA

Home: http://www.bits-pilani.ac.in/~rahul/

Email: [email protected] / [email protected]

08/01/08 1(c) Dr. Rahul Banerjee, BITS-Pilani, INDIA

Lecture-set: 3B



Interaction Points• Significance of Communication in Pervasive Computing

• Identifying the requirements of communication in PervasiveComputing applications

• Select Communication Technologies, their respective reach and

consequent implications

• Communication elements for building Pervasive Computingsolutions

• Some Real-life Example technologies, their features, merits,

demerits and possible applications

• Operating System Requirements, Design-approaches and Related

Issues in Pervasive Computing

• Summary of Concepts learnt

• Q & A Session08/01/08 2(c) Dr. Rahul Banerjee, BITS-Pilani, INDIA



Significance of Communication in

Pervasive Computing

• Pervasive Computing Infrastructure has to allow controllablecommunication between various computing elements, sensors,actuators, and interface devices.

• Intermittent connectivity has to be a supported feature due to

physical limitations pertaining to power, cost, bandwidth andnetwork congestion.

• The infrastructure has to offer seamless connectivity to thedevices / entities / services.

• It has to support placement and location of uniquely identifiable“information tags / trackable tags” to all devices / entities in thePervasive Computing environment.

• Monitoring and controlling capabilities have to be embedded inthe solution, preferably.



Communication & Associated Elements

for Building Pervasive Computing

Solutions Mobile computing devices Fixed computing devices Multimode Mobile communication infrastructure

Cellular / WPAN / WLAN / WMAN / WWAN <terrestrialand satellite-based communication systems included>

Fixed-to-Mobile and Mobile-to-Fixed communication systeminterfaces

Fixed Wireline Networks / internetworks

Fixed Wireless Networks / internetworks <terrestrialcommunication systems only>

Trust system (security and privacy) Protocol stacks & Personalized service framework

(c) Rahul Banerjee, BITS, Pilani (India) 4



Device Connectivity aspects of

Pervasive Computing

(c) Dr. Rahul Banerjee, BITS-Pilani, India 5

• Design Aspects:• Communication aspect

• Networking Aspect

• Services Aspect

• Protocol Aspect

• Security Aspect

• Performance Aspect

• Usability Aspects

• Crash-resistance and Recovery Aspects

• Economy Aspects• Implementation Aspects

• Choice of programming languages, tools and paradigms

• Choice / Design of Algorithms and Data Structures



Why is device connectivity needed?

• Primary reason: – Getting / provisioning various kinds of services, often in a distributed way

• How can one get such services?

– By using some form of connectivity between various devices

– By discovering the services on offer

– By requesting the services (with / without registration / payment)

• How can one provide such services?

– By using some form of connectivity between various devices

– By making the services on offer preferably discoverable

– By configuring and maintaining the services (with / without registration /

payment)




What makes such a connectivity possible?• Some kind of interconnection between the involved devices must

be provided, preferably transparently to the user but notnecessarily so

– often implemented as regular or ad-hoc networks and their

interconnections leading to internetworks

– Always requires several sets of rules and conventions for different forms of meaningful communication

• Each such set leads to design and implementation of a protocol and

there may exist several protocols in a live system

– At the same or different levels

– Sometimes complementing one-another

– Sometimes competing with one-another

– Each protocol contributes towards providing a set of closely related

services

– Protocols may be grouped as Stacks or Families / Suites

(c) Dr. Rahul Banerjee, BITS-Pilani, India7



Identifying Requirements of Communication

Systems for Pervasive Computing Systems

• Identify classes of applications to require communication support.

• Estimate the exact set of corresponding functionalities to be

supported at the lower levels

• Identify additional performance and security-specific constraintsthat may be required to be satisfied

• Identify the hardware architectures over which the solution is

expected to be built

• Identify the availability of ready-to-use device drivers for thedevices expected to be supported

• Weigh the effects of various trade-offs at the OS-level to affect

the targeted class / classes of applications



How Do We Design Communication

Networking Systems for Pervasive

Computing?• Step-1: Need analysis

• Step-2: Evolving requirement specification and runningit through some appropriate sessions of brainstorming

• Step-3: Carrying out Architectural Design and itsvalidation

• Step-4: Carrying out Structural Design and its validation

• Step-5: Simulation / Prototyping

• Step-6: Field-testing involving likely users

• Step-5: Large-scale Production

• Step-6: Large-scale Deployment




Communication Networking Trends

• Networking technologies for home networking – Phone line networking technology

– Wireless radio frequency-based

– Power line networking technology• Some real-life cases

– Networked automobiles / airliners / trains / sealiners

– Surveillance cameras with built-in Web servers – Smart Homes

(c) Rahul Banerjee, BITS, Pilani (India) 10



Case-Study-1

i-Charak: A Healthcare Research

Grid being designed and deployed at

BITS-Pilani

11(c) Dr. Rahul Banerjee, BITS-Pilani, India

August 22, 2006, IEEE Health Grid



• Even though India does have a functional system in place for a verylarge set of public health care services, it is not efficient and easy toscale.

• Also, it does not necessarily support enough the semi- urban and rural population.

• These semi- urban and rural areas have actually lost out in enjoying most

of the benefits of recent technological and scientific breakthroughs in theworld of medicine and health-care.

• An overlay grid specifically designed for collaborative health-careinvolving the entire health-care chain could become an enablinginfrastructure for cost-effective handling of the non-surgical elementsof the health-care.

• The design can be done in a way that allows the very presence of theGrid to its users.

• Incidentally, such collaborative grids need to be QoS-aware and secure for a range of their services to be effective and therefore, such overlaygrids shall require such support available with the underlying Grid.




• Project Grid-One, is a two-part experimental

research project.

• The first phase involves building of a medium-sized

campus-wide IPv6 native support-based grid

involving several Server-class systems, large

number of PCs class systems and select mobile

computing devices.• The second phase aims to involve connecting the

resultant grid to initially a nation-wide and later a

world-wide collaboration Grid.13(c) Dr. Rahul Banerjee, BITS-Pilani, India



• "i-Charak" is a Grid enabled Health-care SupportSystem designed to run atop the Grid-Onearchitecture.

• Thus the iCharak architecture is an overlay gridarchitecture focusing on the non-surgical aspectsof the e-Health-care.

• We intend to focus on the base architecture,

involved thought process, perceived barriers andapproaches considered towards crossing thesebarriers in a phase-wise manner over a period of time.




• Overlay Grid:

–Focus is on Functionality based Abstraction andassociated Provisioning <ease of use, information-

collection / transmission / storage / retrieval,privacy, reliability, traceability, non-repudiationand maintainability aspects included>

• Underlying Actual Grid:

–Focus is on handling heterogeneity, availability,robustness, IPv6-QoS-capability, IP-level security,resource-allocation transparency, load-balancing,security and automatic recovery etc.




• The system can be structured into following

units, based on respective locations of

functions involved: – The Village Level Units (maintained by Health

worker)

– Regional Level units (District Hospital / NGO) – Central Grid Unit (at BITS Pilani campuses)




• The Village Level Unit shall use a Mobile Device or a Full System

with Audio/Video-capturing hardware (Video Resolution, Sound

quality and format depending on the hardware).

• The system after recording the data shall send the same to Regional

Servers (in compressed form).

• The patient data shall be also stored locally (Complete data

recorded may be sent to the doctor only when so required).

• Devices at Unit Level may have either limited or always-on kinds of

connectivity.

• These devices, in the former case, may come online as per the

requirement and synchronize the data with Regional Server and

receive the doctor’s feedback on the patient data sent.




• Regional Servers shall be connected to one-another with high

speed links are connected with the Central Grid.

• Each such server shall need to be online so that the Village

Units could synchronize the data with it.• The Grid Management System will:

– Distribute the work according to Hospital/Doctor’s availability.

– Send the data for analysis

– Collect the prescription and send the data to Regional Servers.

• If a doctor does not responds within a fixed time interval then

data may be sent to some other as per the case may be.




• Application-space partitioning of functionalities shall be

grouped into functionalities

– For the Village Units

– For the Independent Doctors and doctors at Regional Hospitals

– For the Regional Server Units

– For the application(s) running over the Central Grid Unit at BITS

Pilani

• The iCharak application architecture shall make use of

the underlying IPv6-QoS-aware grid and shall remain

transparent to the above layers.

• All data is sent over a secure channel.




• We have planned the research and development in a way that could allow

different groups of researchers to work in parallel on the following

aspects of iCharak .

• Group-I· Design of the Rural Healthcare Support System involving all

related aspects including:

– Mobile infrastructure-based test-bed design and development

– Integration planning and testing of Fixed-and-Mobile elements

– Design of the Security Provisioning System

• Group-II:· IPv6-QoS-aware Grid supporting the services required by the

System.

• ·Group-III: Integrating the development done for Grid-one like Network

layer QoS.




• We have already analyzed needs for the grid

middleware that could suit our purpose and

– can work atop multiple operating systems,

– provide IPv6 support,

– Flow label support for implementing Quality of Service

architecture.

• As none existed that could fit the bill, we are trying

to evolve one.




• Two mini-grids and multiple island clusters havebeen tested independently with and without theIPv6 QoS support

• Grid Management System is functional and allows job-submissions, monitoring etc.

• Bottlenecks related to Globus and Condorinteroperability are gradually being resolved

• Security architecture is only partly functional

• Inputs from medical, social, pharmaceutical,marketing and other allied fields have been onlypartially analyzed and documented.




• To evolve the current grid to involve 3000+ nodes <of 5000+

nodes>on Pilani campus

• To hook up nodes from other campuses of BITS-Pilani

• To interconnect this with one or more national and international

experimental grids <preferably with IPv6 native support>

• Interlink with projects like the Project SHARE of Europe etc.

• Evolve a privacy and confidentiality framework for controlled use of

collected data and its purposeful analysis

• Large-scale field-testing of the target system before seeking its

actual nation-wide deployment <and subsequently initiate the

outreach program to help others around the world with focus on

the economically weaker nations>




Reference

Preliminary Research Reports of the Project <on-line> at:

• http://discovery.bits-pilani.ac.in/GridOne/




Case-Study-2

Project NetFirst at BITS-Pilani An Innovative Research Architecture atop the

MIT’s iLabs Framework




A Brief Background on the BITS-

MIT Collaboration on the MIT’s

iCampus Initiative• What led us to conceptualize the iCampus India Initiative and renew

our MIT links of foundational years? – Expansion of BITS through establishment of Multiple campuses in India and

Abroad – Work-Integrated Learning Programmes of BITS

– Availability of required infrastructural facilities and domain expertise in keyengineering disciplines at BITS

– Past experience with select web-based laboratory development projects in thelate 90s

– Scalability and Sharing Needs

• Flagging off the iCampus India Initiative with BITS-Pilani becoming thefirst MIT iCampus Hub Institution in India

• Project Home Page: http://discovery.bits-pilani.ac.in/iCampus/




A Brief Background on the Project

NetFirst at BITS ....

• What led us to the Project NetFirst? <in addition to

those of previous slide>

– Networking research at BITS-Pilani

– The I2L Architecture of the BITS-VU

– Ready support from researchers <faculty,

students>

– Experience of the Web-based Remote Instruction

using synchronous as well as asynchronous

learning methods




About Project NetFirst at BITS-

Pilani

• What is the basic idea?

• Steps involved

• Progress made so far• Work in progress

• Next Steps

• Project Website has information on

– Vision Document and Roadmap

– How to join the project?28(c) Dr. Rahul Banerjee, BITS-Pilani, India



What is the Basic Idea Behind the

Project NetFirst ?

• Making the physical research and experimentation infrastructure infixed and mobile networking at BITS accessible to interested facultyand students <both on-campus as well as off-campus> as if it was local<except for the physical touch and feel factor!>

• Complementing the regular lecture material produced over the yearsthrough the anytime-anywhere model of experimental learning

• Enabling like-minded researchers and teachers interested in sharedlearning resources in the area who may not have access to suchexperimental infrastructure or domain expertise

• Evolving an architecture that could allow more advanced forms of experimentation which may prove useful to those who may requirefar more user-configurable forms of safe experimentation thatotherwise may require simulations




Phases of Project NetFirst

• Phase-I

– Experiments that may aid the 4th level introductory networking coursefocussed on design and basic concepts, design methods andimplementation strategies <CS C 461 / IS C 461 / BITS C 481 / BITS ZC 481 /EA C 451 / EA ZC 451 courses at BITS-Pilani>

• Phase-II – More advanced experiments to aid the 5th and 6th level networking

courses like those including, Network Security, Mobile Computing,Pervasive Computing <CS G 513 / SS G 513 / SS ZG 513 / CS G 541 / SS G531 / SS ZG 531 and related courses>

• Phase-III – Research experiments in fixed and mobile networking

• Phase-IV

– Research experiments in high-performance network and distributedcomputing




Issues involved• How to identify the best candidate areas and experiments?

• How to estimate the costs involved?

• Which kind of equipments, connectivity and software shall suit

the best?

•How to optimize the resources?

• Perceived Barriers:

– Initial Research, Developmental & Deployment Costs at the research

university’s end <end users have practically no cost except for that of

Internet Connectivity as chargeable by their respective ISPs, a bit of staff/

student-volunteer-training and at least of one good computing system>

– Lack of awareness amongst the likely beneficiaries




Concluding Remarks• Gradually, all the BITS-Pilani campuses shall also join the project but at

present it is limited to the main campus at Pilani.

• Willing to know more or readily interested in joining hands with BITS?

– Just visit the website: http://discovery.bits-pilani.ac.in/iCampus/ and read the

details related to eligibility, commitments, benefits, FAQs, procedure to join

<including the draft MoUs>, contact details etc.. OR

– Simply send an Email to the Project Leader (PI) at the Email address: [email protected]

• AFTER completing this course, at a later point of time, you may also wish to

– Consider speaking to the Project Leader (PI) at +91-9414082475 <cell> or

+91-1596-245073 Ext. 335 for an initial expression of interest <after you have

taken your employer’s written permission so as to avoid any IPR and related issueslater>




Summary of Concept Learnt

• Definition

• Reach

• Elements involved – Hardware

– Software

– Communication

• Applications & Services




Any questions?

That’s all for the day!

Thank you for your time and interest!

Home: http://www.bits-pilani.ac.in/~rahul/

Email: [email protected] / [email protected]

08/01/08 34(c) Dr Rahul Banerjee BITS-Pilani INDIA

sszg531 introduction to communication technologies

Documents