Wireless Communication Mobile Programming UNIT 1 MOBILE COMPUTING

Wireless Communication & Mobile Programming UNIT- 1 – MOBILE COMPUTING INTRODUCTION Blog: aforajayshahnirma. wordpress. com 1

Reference Book “Mobile Computing” By Asoke K Telukder, Roopa R Yavagal, TMH Chapters – 2 Blog: aforajayshahnirma. wordpress. com 2

Mobile Computing Architecture Introduction/Evolution Architecture Blog: aforajayshahnirma. wordpress. com 3

First Tier/Layer Mobile Computing Architecture Introduction/Evolution Architecture User Interface/Presentation Layer – deals with the user facing device handling & rendering. This tier includes a user interfacing components like Textbox, Labels, Checkboxes, etc. Second Tier/Layer Process Management/application Layer – deals with Business logic & Rules. It is capable of accommodating hundreds users. Thired Tier/Layer Database Management/Data Tier – deals with DB management & access. Blog: aforajayshahnirma. wordpress. com 4

Three-Tier Architecture DIY Blog: aforajayshahnirma. wordpress. com 5

Design considerations for Mobile Computing Mobile computing environment needs to be contextindependent as well as context-sensitive. Here “Context” means all information that help determine the state of object. The object can be person/device/place/physical or computational object/any other entity that is being tracked by the system. Mobility implies the service is associated with the user/device will change constantly. So the change in the content & behavior of the applications should be adopted to suit the current situation. There are many ways in which contexts can be adapted, • Content with Context Awareness • Content switch on Context • Content Transcoding on Context Blog: aforajayshahnirma. wordpress. com 6

Design considerations for Mobile Computing • Client Context Manager • Composite Capabilities/CC or Preference Profiles/PP • Policy Manager • Semantic Web • Security Manager • Platform for Privacy Preference Project • Adaptability Manager • Content Adaptation & Transcoding • Content Rating & Filtering Blog: aforajayshahnirma. wordpress. com 7

Design considerations for Mobile Computing • Client Context Manager • Composite Capabilities/CC or Preference Profiles/PP • Policy Manager • Semantic Web • Security Manager • Platform for Privacy Preference Project • Adaptability Manager • Content Adaptation & Transcoding • Content Rating & Filtering Blog: aforajayshahnirma. wordpress. com 8

Design considerations for Mobile Computing • Client Context Manager • Composite Capabilities/CC or Preference Profiles/PP • Policy Manager • Semantic Web • Security Manager • Platform for Privacy Preference Project • Adaptability Manager • Content Adaptation & Transcoding • Content Rating & Filtering Blog: aforajayshahnirma. wordpress. com 10 9

Design considerations for Mobile Computing • Client Context Manager • Composite Capabilities/CC or Preference Profiles/PP • Policy Manager • Semantic Web • Security Manager • Platform for Privacy Preference Project • Adaptability Manager • Content Adaptation & Transcoding • Content Rating & Filtering Blog: aforajayshahnirma. wordpress. com 10

WAP Architecture Blog: aforajayshahnirma. wordpress. com 11

WAP Architecture Blog: aforajayshahnirma. wordpress. com 12

WAP – Protocol Layers Blog: aforajayshahnirma. 13

WAP – Protocol Layers Blog: aforajayshahnirma. 14

SOC & AOC Clients Mobile users need solutions that can be used effectively at any time during their work day and used wherever their works takes them. Mobile technology can be implemented with Sometimes On Connectivity/SOC to mobile devices or Always On Connectivity/AOC. SOC and AOC terminology effectively describe to our clients the communications frequency and performance: capabilities of alternatives for mobile computing solutions. SOC clients can work effectively in a disconnected mode and take advantage of wireless or wired connections when they are available while AOC clients must be connected all or most of the time to be effective. Blog: aforajayshahnirma. 15

SOC Clients SOC clients have the ability to store large amounts of data on the mobile device and provide the user with a complete application solution even when the user does not have a wireless or wired data connection. Data updates can occur when wireless, Internet dialup, network or desktop synchronization connections are available. Regardless of connectivity, productive work can proceed. Data updates, when they do occur, can be fast bursts of small amounts of data rather than entire screen images that AOC clients employ. SOC client technology typically requires a Pocket PC or Win. CE device in order to have sufficient processing power and data storage capability. AOC clients have small amounts of data or no data on board the device. Blog: aforajayshahnirma. 20 1 6

AOC Clients AOC clients require a wireless connection that is always on to be able to access data and the user interface, or screen image. AOC clients typically use a browser for application interactions. Internet-like HTML or WAP is employed by the browser to view web pages that are especially designed for the smaller screens of mobile devices. AOC clients require transmission of the data and screen image for each user action. Consequently, mobile workers need a wireless connection constantly available in order to effectively use AOC client mobile devices. Blog: aforajayshahnirma. 17