Birla Institute of Technology & Science, Pilani Work-Integrated Learning Programmes Division Second Semester 2010-2011 Mid-Semester Test

(EC-1 Regular) SOLUTION Course No. Course Title Nature of Exam Weightage Duration Date of Exam : SS ZG531 : PERVASIVE COMPUTING : Closed Book : 40% : 2 Hours : 06/02/2011 (FN)

1. How fully correct, incorrect or partially correct/incorrect are the following statements and why? a. AJAX includes Java Script and XML. b. OSGi enables interaction of multiple devices inside a moving vehicle to the entities in the external networked environment for the purpose of providing / using pre-defined set of services. 3+3=6 Solution: a. This statement is completely CORRECT. However, AJAX is no longer only the acroym for Asynchronous Java Script and XML. It is a cross-platform interactive web-application-programming technique used for developing a wide variety of rich Internet applications and over the time has evolved to represent a set of plat-form independent technologies. It is based on open standards such as JavaScript and the DOM. Note: AJAX is considered asynchronous since extra data is requested from the server and loaded in the background without interfering with the display and behaviour of the existing page. Like DHTML and LAMP, Ajax is not a technology in itself, but a term that refers to the use of a group of technologies. XHTML / HTML and CSS, for marking up and styling information. XML is sometimes used as the format for transferring data between the server and client, although any format will work, including preformatted HTML, plain text and JSON. These files may be created dynamically by some form of server-side scripting. The DOM accessed with a client-side scripting language, especially ECMAScript implementations such as JavaScript and JScript, to dynamically display and interact with the information presented. The XMLHttpRequest object is used to exchange data asynchronously with the web server. In some Ajax frameworks and in certain situations, an IFrame object is used instead of the XMLHttpRequest object to exchange data with the web server, and in other implementations, dynamically added <script> tags may be used. b. This statement is completely CORRECT. OSGi (formerly known as the Open Services Gateway initiative - <obsolete expansion>) in deed enables interaction of multiple devices inside a moving vehicle to the entities in the external networked environment for the purpose of providing / using pre-defined set of services.

The OSGi Alliance and its members have specified a Java-based service platform that can be remotely managed. The core part of the specifications is a framework that defines an application life cycle model and a service registry. Based on this framework, a large number of OSGi Layers, APIs, and Services have been defined. OSGi technology is Universal Middleware.OSGi technology provides a service-oriented, component-based environment for developers and offers standardized ways to manage the software lifecycle. These capabilities greatly increase the value of a wide range of computers and devices that use the Java platform. Note: The OSGi Alliance is an independent non-profit corporation comprised of technology innovators and developers and focused on the interoperability of applications and services based on its component integration platform. Integrating the OSGi gateway into a CIS (Car Information System) allows transmission / reception of data wirelessly to the outside world where a back-end system maybe known to exist. The OSGi , in such cases, acts as an interface between the CIS and the outside world / back-end system. This is due to the fact that the OSGi gateway has an ability to access information from the cars ECUs and disseminate it, as required, to the designated targets in the world outside the car. The cars driver / owner / passenger / manufacturer / maintenance-shop can benefit from such provisioning amongst others. The user can access a range of free / paid services including email, voice calls etc. as per need. Similarly, the car-manufacturer can make good use of the feedback by monitoring critical parameters obtained from car sensors periodically / upon occurrence of any specified event. This ultimately helps him to improve quality / safety / marketability of his cars subsequently as well as at times may allow to act proactively and help the driver / owner.

2. What shall be your off the shelf design choices with respect to hardware elements (computing, peripheral and network communication) and software elements (system, application and services) if? a. You have to quickly build a handheld device for supporting the IEEE 802.15.1 and IEEE 802.11b/g/n (when needed), 2.5 G Cellular and 3 G Cellular forms of communication systems (both of these simultaneously) apart from featuring always-on connectivity with IP-level support with multi-layer security provisions. b. You have to advise on a simple rudimentary solution that could provide for sensing dangerous tidal waves due to any under the sea / ocean volcanic eruption so as to warn the fishermen, naval / passenger / merchant ships as well as people living near the areas that may be affected by these giant waves in time to be able to minimize, if not eliminate, the risk of losing precious lives. 5x2=10 Solution: (a). Background note: General Design Guidelines for mobile / handheld devices user interfaces include: o o o o o Enable frequent users to use shortcuts Offer informative feedback Design dialogs to yield closure Support internal locus of control Design for multiple and dynamic contexts

o o o

o o

Allow users to configure output to their needs and preferences (e.g., text size, brightness) Allow for single- or no-handed operation Have the application adapt itself automatically to the users current environment Design for small devices Provide word selection instead of requiring text input Design for limited and split attention Provide sound and tactile output options Design for speed and recovery Allow applications to be stopped, started, and resumed with little or no effort Application should be up and running quickly Design for top-down interaction Present high levels of information and let users decide whether or not to retrieve details Allow for personalization Provide users the ability to change settings to their needs or liking Design for enjoyment Applications should be visually pleasing and fun as well as usable

Speech input is a viable alternative for devices too small for buttons. Sound can also be used for output, taking the place of text or graphics. For mobile devices and applications, time constraints need to be taken into account in initial application availability and recovery speed. When time is critical, waiting a few minutes for an application to start may not be in the users best interest. Given the different contexts under which mobile devices are used, users may need to quickly change or access functions or applications. When such situations rise, a user would need to quickly and securely save any work already performed and resume it later without any loss. Different users have different usage patterns, preferences, and skill levels. So it is important to allow for variations among users.

To do: To suggest an approach to quickly build a handheld system having support for: IEEE 802.15.1 and IEEE 802.11b/g (when needed), 2.5 G and 3 G (both of these simultaneously) always-on connectivity IP-level support Provision for multi-layer security Explicit Constraints: Using mostly off-the-shelf components Approach must allow least possible time for building the device Implicit constraints: Cannot consider designing new hardware and software devices / elements / components even if that could have provided more costeffective solution Support for Mobile IPv6 is implied

Assumptions: <one-line justification is to be added in each case> Device to be designed is a Dual-mode GSM/CDMA Smartphone with support for Bluetooth and WLAN Device is expected to be capable of handing XHTML and Mobile AJAX Device has to support IPv4 and IPv6 both using the Dual-Stack Transition mechanism Device has to support GPRS / EDGE over GSM for one of its two modes Device shall use SIM for the GSM/UMTS part and USIM for the WCDMA part Device must be capable of handling secure transactions over the air Device must be able to be securely synchronized with another paired device duly configured by the user The Host Operating System of the handheld is expected to have support for internationalization and Unicode.

One possible solution approach may look like: <one-line justification is to be added in each case> Processor choice: Radio transceiver choices: Wi-Fi radios Display device choices: inches Audio device choices: Ployphonic sound support, Intel X-scale family processor GSM Quad-band, WCDMA, Bluetooth,

Touchscreen, Resolution: , Size: 4/4.3

Microphone, Dual-mode Speaker,

Keypad choices: Vertical Slider type Regular 12-key mini-keypad with three multifunctional keys (totaling 15-keys leading to 18 different unique press-patterns) Smartcard choices: Location-awareness choices: grained SIM, USIM GPS fine-grained / Cellular coarse-

Power-provisioning choices: Li-Ion batteries Other hardware choices: Sockets and ports for: Power adapter connectivity, USB data cable connectivity, IEEE 1394 port; Power adapter/charger, USB Data cable Protocol Stack choices: DHCPv6, HTTP, IMAP, POP, SMTP, SSL/TLS, WTLS, WAP, TCP/IPv6 with MIPv6, TCP/IPv4, IEEE 802.11 b/g, IEEE 802.15.1, IEEE 1394 Operating System choice: Googles Android 2.3 Multi-layer-security choices: L2 (through IEEE 802.1x, Bluetooth passphrase, PKCS), L3 (IPv6: ESP+AH, IPv4+IPSec), L4 (SSL/TLS atop

TCP, WTLS: PKCS), L5 (Conventional and PKCS based) + OS support through Crypto API utilized by select applications Language choices: Java (as in J2ME) XHTML, Java Script, WML, WML Script,

Other Application and Codec Support choices: MP3 support, MPEG-4 support, MMS, SMS, Email editors and readers, Overall remarks: The following diagram shows select elements in the handset.

(b). To do: To work out a a simple rudimentary solution that could to be able to minimize / eliminate loss of lives This soulution has to o provide for sensing dangerous tidal waves caused due to any under the sea / ocean volcanic eruption o and, consequently warn the fishermen, naval / passenger / merchant ships people living near the likely coastal areas

Explicit Constraints: Solution MUST be able to work in terms of hard real-time constraints so as to be able to be of any real help Only under the sea/ocean volcanic eruptions are to be considered, if estimated to cause major tidal urbulence Implicit Constraints: Vastness of the oceans and seas Need to limit the number of the locations to be considered causes of major relevant concern Sensory system has to be able to survive the likely adverse conditions while placed deep inside the sea / ocean Need for a highly available and failsafe real-time communication infrastructure Inherent complexity of the estimation process High computational processing and storage capacity required Multi-locale / multi-lingual support Support for Human Intervention in case of early detection of false positives Need to make the system trustworthy and secure so as to disallow abuse of the associated warning system and the connected NIIs (National Information Infrastructure or equivalent body, if any, of each related nation) One possible solution: <one-line justification is to be added in each case> Processor choices: Intel range of processors for Server-class applications, Intel range of CISC / RISC processors for workstations,

Intel mobile family of RISC processors for mobile handhelds <preferably dual-core, quad-core or higher at the workstation and server ends> Sensor choices: Temperature, Pressure, Vibration, Ultrasound, Oxigen-level-detection sensors with and without compute nodes associated lococally but with associated signal amplifiers, converters, modulators and transmitters tec. as per need). (WSN class of sensor-compute nodes with some of these sensory capabilities shall be preferable in many a situations) Radio transceiver choices: GSM Tri-band, WCDMA, ZigBee, Wi-Fi radios, FM and AM transceivers for broadcasting support, Display device choices: LCD, Plasma, Touchscreen, Soft-surface, LEP displats as per need in different locations Audio device choices: Microphones, Hi-Fi Speakers Sensitive and Noise-cancelling

Smartcard choices: SIM and USIM for cellular phones and associated services, Contactless processor-based Smartcards for access control and services Location-awareness choices: GPS for fine-grained and coarse-grained needs Power-provisioning choices: Flexible polymer and Li-Ion batteries for dry miniature devices, hermatically sealed plolymer batteries and tidalenergy-driven miniature energy-conversion devices for under-water placements, regular electrical power to be provisioned for normal server-class and workstation class systems Other hardware choices: Sockets and ports for: Power adapter connectivity, USB data cable connectivity, IEEE 1394 port; Power adaptesr/chargers, Data cable, Secondary storage devices, interconnected secure SANs Protocol Stack choices: DHCPv6/v4, HTTP, IMAP, POP, SMTP, SSL/TLS, WTLS, WAP, TCP/Ipv6 with MIPv6, TCP/Ipv4, IEEE 802.11 a/b/g, IEEE 802.3x, IEEE 802.15.4, IEEE 1394, IEEE 802.16 Operating System choice: Ports of the Microsoft Windows CE 5/6 and Symbian OS7/8/9 for mobile phones, Ports of Linux, SUN Solaris, IBM AIX, HP-UX and Microsoft Windows Servers 2000/2003 or later for Server Class systems and Ports of Linux, MacOS IX/X, Microsoft Windows 2000/XP/ME/XPE/Vista for regular workstations Multi-layer-security choices: L2 (through IEEE 802.1x, Bluetooth passphrase, PKCS), L3 (Ipv6: ESP+AH, Ipv4+IPSec), L4 (SSL/TLS atop TCP, WTLS: PKCS), L5 (Conventional and PKCS based) + OS support through Crypto API utilized by select applications

Language choices: XML, HTML, XHTML, Java Script, WML, WML Script, Java (as in J2ME/J2SE/J2EE), C (variants like ANSI C, GNU C, NesC included) Other Application and Codec Support choices: MP3 support, MPEG-4 support, MMS, SMS, Email editors and readers, provision for MATLAB or Mathematica compliance for easy data modeling and visualization support Overall remarks: In such situations, a diagram showing the functional blocks involved could help us explain the whole scheme in a nutshell.

3. What shall be your pervasive computing solution if? a. Temporary but recurrent Repetitive Stress Injuries in the fingers, wrist and shoulder areas force an individual computer user to seek help from you as an engineer consequent to advice by his / her physiotherapist to correct his / her posture, adjust level of chair-arms and use low-force key-pads. b. You have to use a single multi-core processor-based computing platform for supporting a small set of hard real-time applications as well as several timeinsensitive applications specifically designed for variants of Linux environment. 3+3=6 Solution: (a). To do: To work out a pervasive computing device which shall assist in avoidance of recurrence of the listed RSIs to the patient while allowing most of the required functionalities of regular systems used by him / her

Explicit Constraints: Repetitive Stress Injuries in the fingers, wrist and shoulder areas have to be carefully avoided in future Implicit constraints: No new RSIs should preferably crop up as a consequence of the proposed solution Assumptions: <one-line justification is to be added in each case> The person-in-question is a regular computer user <since RSIs are common only in such cases> One possible solution approach may look like: <one-line justification is to be added in each case> Consider providing a good-resolution-based medium-/large screen-sized touch-screen I/O interface with handwriting recognition support. If the person can afford it, even a TabletPC or a similar device may be of great help.

(b). To do: To suggest an approach that would use a single multi-core processorbased computing platform for supporting a small set of hard real-time applications as well as several time-insensitive applications specifically designed for variants of Linux environment Explicit Constraints: <one-line justification is to be added in each case> multi-core processor-based computing supporting a small set of hard real-time applications supporting several time-insensitive applications designed for variants of Linux environment Implicit constraints: <one-line justification is to be added in each case> Hosting virtualized OSes atop a non-real-time OS is not an option here.

Assumptions: <one-line justification is to be added in each case> Primitive needed to virtualize all the referred OSes are made available to the design team o Any cost-effective extension of an existing solution may be preferable in oder to save development and training costs One possible solution approach may look like: <one-line justification is to be added in each case> o Processor choice: As required by respective OS. Nothing specific here! Display device choices: As required by respective OS. Nothing specific here! Audio device choices: As required by respective OS. Nothing specific here! Input device choices: As required by respective OS. Nothing specific here! Smartcard choices: Such a situation does not require a Smart Card except for use as a peripheral / associate device. Support for Smartcard per se is an OS-specific provision and does not concern virtualization of the OS per se Location-awareness choices: Not an OS issue this! Irrelevant here. Power-provisioning choices: As usual. Nothing specific here. Other hardware choices: NoneProtocol Stack choices: As supported by different respective OSes + the virtualization protocol that would allow Inter-OS communication Operating System choice: All the listed variants of non-real-time Linux and one variant of real-time Linux OS (provided with their virtualization primitives) Language choices: As required by respective OS. Nothing specific here Approach prefereable: Independent hypervisor-based approach of virtualization may be preferred here since it would allow all the required flexibilities.

4. Which of the following are true and to which extent, in the context of an ideal Wearable Computing system, and why? a. Users context is more significant than the context of the environment in which the user operates along with his acquaintances. b. Body-safety and power-provisioning issues outweigh form-factor and weight specific issues particularly if the usage-duration is prolonged. 2x3=6 Solution: (a). It is TRUE that in the context of an ideal Wearable Computing system, Users context is more significant than the context of the environment in which the user operates along with his acquaintances. This true since although a wearable computing system may be assisted by exchanging information with its surroundings, it has to primarily focus on being aware of the wearers personal context since that is its primary purpose of use. Ther term Users Context here pertains to collection of information of specific relevance to the wearer with respect to the intended use of the wearable computer and may hence vary from system to system. Some of these contexts are formed by collecting sensory data and structuring the resultant information in a specified manner so as to assist the rest of the wearable computing system to make use of this information to visualize it as part of the overall context of the user-in-question and could therefore be used for taking the actual expected actions, as per design and deployment objectives.

(b). It is TRUE that in the context of an ideal Wearable Computing system, Bodysafety and power-provisioning issues outweigh form-factor and weight specific issues particularly if the usage-duration is prolonged. This true since although a wearable computing system should be as smalland lightweight as possible and it may help further if its shape suits the eye, it has to primarily focus on the wearers personal needs without compromising on users body-safety and since without proper power-provisioning, it may not work either appropriately or for long enough to fulfil it very purpose of deployment. Body-safety,comfort and convenience of use are very important but the body-safety gets the first priority. Aspects that may require specific attention in this case do include safety from EM radiations, Electrical current / voltage, Thermal Heat or prolonged contact with any chemical substance (gel / powder etc. included). This means that processor-choice, communication-system design, power-unit design, choice of material for batteries (if any), choice of fabric, connection methods, electrodes (if any), sensors etc. need a lot of careful consideration so as to be able to ensure body-safe design and deployment of a wearble computer. It often helps to have a a verifiable framework that could be used to ensure that the overall system in its entirety or any individual sub-system / element of which does not pose any threat to the physical security or mental comfort level of the user. IT has to be ensured that a built-in self-test be executed on the wearable computer as well as on the vehicles computer at appropriate intervals in order to determine if the system continues to conform to the specified safety norms.

Background note: Wearable computing has Computers/sensors on people whereas in the Pervasive computing, Computer/sensors are embedded in the environment. Wearable systems know more about people whereas the Pervasive Computing Systems know more about environment.

5. A large multi-lingual republic comprising of several states is surrounded by large aquatic bodies on three sides and a mountain-range on the fourth side. Economy of this republic depends mostly upon agriculture, tourism (regular and medical types), knowledgeservices and manufacturing industries. Although increasing progressive, this nation is also characterized by its low literacy rate, inadequate transport infrastructure and poor health services in the rural and semi-rural areas. This makes it increasingly difficult for allowing quality health-services to reach the rural semi-literate / illiterate population. If you are asked to formulate a cost-effective solution that could allow an early diagnosis of the most common medical problems of this rural population using a proper combination of several devices and services, without usually requiring it to go to hospitals far away from their locale, what would you advise and why? (Hint: Please redefine the given problem more precisely by limiting its scope, making simplifying assumptions and identifying the candidate features before working out the rest of the solution in terms of hardware, software and services). 12 Solution: Given Hints: Please redefine the given problem more precisely by limiting its scope, making simplifying assumptions and identifying the candidate features This is to be done before working out the rest of the solution in terms of : hardware, software and services Limiting Scope of the problem: <one-line justification is to be added in each case> Each state has its own native language but does have people from other states as well whose needs are to be taken into account There is ONE major language out of these spoken languages that is expected to be understood by all its citizens which has been identified as Language X. This is the primary language of communication across the country. Each state brings out its official communication in its native language as well as this language X (if the two are different). Roads, waterways and air all form the modes of transport but our solution has to focus only on roadways. Problem is to be considered limited to the rural areas alone. Simplifying Assumptions: <one-line justification is to be added in each case> Number of states in this large republic are N All state governments and the federal government at the centre follow an India-like method of governance Since the country is having a flourishing Medical Tourism boom, it can be safely assumed that capable medical specialists are available in the country in good numbers although in urban areas.

Country is well connected through optical fibre backbones and has a high mobile telephony penetration even in the rural areas. Each village has at least one literate trained volunteer or an appointed Primary Health Worker. Each village is accessible through some mobile telephony system.

Identification of Candidate Features: <one-line justification is to be added in each case> Voice and icon-assisted but multimediat-capable gadgets with mobile telephony and datat-transfer capability to be made available in the villages (at least one per ten houses) Existing mobile phonesowned by somepeople in the village could also join the pool referred above or independedntly participate in the program, if compatible. User interface at the rural end has a friendly UI that supports voicerecognition, Gesture recognition, icon-based operation as well as the regular GUI/Text based operations. Devices are either Smartphones / PocketPC Phones with integrated medium/high-resolution cameras or the village is provided with at least one such camera that could be attached to one of the existing / provided devices. Rural centres connect wirelessly to the block headquarters that connect over the fibre to district headquarters and through them to the state capital. All state capitals are connected to the National Capital via highspeed redundancy-based backbone links. The system is supported by a secure middleware-based architecture which in turn capitalizes on a system of distributed pool of Server Farms spread in different parts of the country as per need. Overall architecture resembles the traditional three-tier architecture. User need not be aware of the architecture involved. Each hospital, trauma centre, medical / pharmaceutical store, registered paramedical support agency and ambulance service in the country has an obligation to pledge some percentage of its resources / services (on guarantee of payment by the National Health Scheme or equivalent) to assist the rural-initiated request for diagnosis/treatment/advice/transportation/delivery as may be relevant on demand. All these agencies are therefore expected to have an always-on kind of connectivity at their end. These systems are directly / indirectly connected to the Internet. Explicit Constraints: <one-line justification is to be added in each case> Lower literacy rate in the rural areas Very little availability of medical experts in rural areas Implicit Constraints: <one-line justification is to be added in each case> Lower literacy rate in the rural areas means even lower computer awareness and lower level of awareness of whom to approach for a particular type of a health problem A possible solution approach: <brief justification is to be added in each case>

We may thus conceive a Grid enabled Pervasive Healthcare Support System, which will be set atop an IPv6/IPv4 dual-mode-enabled Grid.

This solution can be implemented to help in the acquisition, validation and use of this information independent of any platformspecific considerations. This character of the Grid makes it a sort of medium to port with various types of devices and/or sub-grids.In this scenario we assume that even though most of the rural areas lacks specialist medical healthcare support but they do have some elementary amenities. Therefore, our technology can utilize required resources often available in metropolitan / urban areas by collecting data from semi-urban and rural areas and make use of Grid for collaborative decision- making / diagnosis / processed etc. and thereby provide initial breakthrough to medical facilities in rural areas.
The system can be structured into following units, based on respective locations of functions involved: a. The Village Level Grid-Access Units (used by the trained Health worker) b. Regional Level Grid-Member units (District Hospital / NGO) c. Central- level Grid Management Unit (at the National capital) The Village Level Unit is expected to use a Mobile Device or a customdesigned workstation with Audio/Video capturing hardware (Video Resolution, Sound quality and format shall depend upon the need of the situation and availability of the hardware). The latter system, when needed, will have the ability to send the recorded data about the patient to Regional and major Nationwide set of Servers (in compressed format). This data is to be stored locally as well where appropriate storage maintenance is possible. (Note: Complete data recorded may be sent to the doctor as and when the doctor / specialist consultant as and when required). The devices at Unit Level may have regular or intermittent. These end-user units can go online as per the need and synchronize the data with Regional and National Servers apart from receiving the doctors feedback on the patient data sent earlier or even during a session of the live kind where so needed based on the criticality of the situation on hand. The Regional Servers (connected to one-another preferably with high speed WAN links) are to be connected to the Central Grid which shall be hereafter called as Nationwide Grid. It needs to be always available so that the Village Units can synchronize the data with it. The Nation-wide Grid will analyze the work to be done by the Grid continuously and would have the responsibility to ensure balanced timely distribut ion of the work according to several parameters of operation including Hospital/Doctor availability. It is also expected to collate and send the data for analysis to machines / experts, collect the prescriptions / advice from specialists if any and send the entire processed data of relevance to Regional Servers. (If a doctor / specialist does not respond within a fixed time interval, system shall be able to take care of it and send the job to another specialist. Application-space partitioning of functionalities For the Village Units For the Independent Doctors and doctors at Regional Hospitals For the Regional Server Units And the application running over the Nation-wide Grid The application shall make uses of the underlying IPv6-QoS-aware network and is transparent to the above layers. All data is sent over a secure channel.

Background note: Pervasive Computing Infrastructure has to comprise of computing elements, communicating elements, sensors, actuators, and interface devices. This means Computation should be available widely and freely (not free of cost). Intermittent connectivity has to be a supported feature due to physical limitations pertaining to power, cost, bandwidth and network congestion.The infrastructure has to offer seamless connectivity to the devices / entities / services. It has to support placement and location of uniquely identifiable information tags / trackable tags to all devices / entities in the Pervasive Computing environment. Also, the users environment must be able to be aware of the users context. Display elements do have a range of different requirements in terms of Display-size, Display-shape, Display-resolution, Display-colour richness, Display viewing angles to be supported, Display power provisioning constraints and Display refresh rates etc. The pervasive computing system needs at least two basic elements to be pervading everywhere they are required to pervade: (a)- Computing elements to take care of computational needs; (b)- Communication elements to interconnect these computing elements either through wires or wirelessly (with / without mobility). For identifying Requirements of Operating Systems for Pervasive Computing Systems we need to first identify classes of applications to be run atop the target OS, estimate the exact set of corresponding functionalities to be supported at the lower levels, identify additional performance and security-specific constraints that 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 the devices expected to be supported and at the same time weigh the effects of various trade-offs at the OS-level to affect the targeted class / classes of applications. Principal issues related to design of Pervasive Computing Systems are Featurespecific issues, Form-factor-(size)-specific issues, Power-provisioning issues, Weightspecific issues, Shape-specific issues, Cooling-specific issues, Connectivity-specific issues, User Interface-specific issues, Body-safety-specific issues <not for all devices>, Security-specific issues, Processor-choice-specific issues, Operating System-specific issues, Development and execution-environment-specific issues, Costspecific issues and of course Regulatory issues. The principal issues related to the Biometric Authentication-based device security systems are FAR and FRR. This is because just as False acceptance may invite disaster, False rejection may prevent valid use (sometimes critical in nature). Please keep in mind that Design blunder of ignoring possible problems due to accident / disease / temporary physical irregularities, possible misuse of photographic scanning technology, associated cost and complexity has to be avoided.