W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g
description
Transcript of W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g
![Page 1: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/1.jpg)
Wireless Communication & Mobile Programming
1
UNIT- 1 – MOBILE COMPUTING INTRODUCTION
Blog: aforajayshahnirma.wordpress.com
![Page 2: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/2.jpg)
Reference Book
2
“Mobile Computing” By Asoke K Telukder, Roopa RYavagal, TMH
Chapters – 2
Blog: aforajayshahnirma.wordpress.com
![Page 3: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/3.jpg)
Mobile Computing - Architecture Introduction/Evolution
Architecture
3Blog: aforajayshahnirma.wordpress.com
![Page 4: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/4.jpg)
Mobile Computing - Architecture Introduction/Evolution
Architecture
First Tier/Layer
4
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 DBmanagement & access.
Blog: aforajayshahnirma.wordpress.com
![Page 5: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/5.jpg)
Three-Tier ArchitectureDIY
5Blog: aforajayshahnirma.wordpress.com
![Page 6: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/6.jpg)
Design considerations for Mobile Computing
6
Mobile computing environment needs to be context-independent 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
![Page 7: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/7.jpg)
Design considerations for Mobile Computing• Client Context Manager
• Composite Capabilities/CC orPreference Profiles/PP
• Policy Manager
• Semantic Web
• Security Manager
• Platform for PrivacyPreference Project
• Adaptability Manager
• Content Adaptation & Transcoding
• Content Rating & Filtering
7Blog: aforajayshahnirma.wordpress.com
![Page 8: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/8.jpg)
Design considerations for Mobile Computing• Client Context Manager
• Composite Capabilities/CC orPreference Profiles/PP
• Policy Manager
• Semantic Web
• Security Manager
• Platform for PrivacyPreference Project
• Adaptability Manager
• Content Adaptation & Transcoding
• Content Rating & Filtering
8Blog: aforajayshahnirma.wordpress.com
![Page 9: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/9.jpg)
Design considerations for Mobile Computing• Client Context Manager
• Composite Capabilities/CC orPreference Profiles/PP
• Policy Manager
• Semantic Web
• Security Manager
• Platform for PrivacyPreference Project
• Adaptability Manager
• Content Adaptation & Transcoding
• Content Rating & Filtering
109Blog: aforajayshahnirma.wordpress.com
![Page 10: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/10.jpg)
Design considerations for Mobile Computing• Client Context Manager
• Composite Capabilities/CC orPreference Profiles/PP
• Policy Manager
• Semantic Web
• Security Manager
• Platform for PrivacyPreference Project
• Adaptability Manager
• Content Adaptation & Transcoding
• Content Rating & Filtering
10Blog: aforajayshahnirma.wordpress.com
![Page 11: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/11.jpg)
WAPArchitecture
11Blog: aforajayshahnirma.wordpress.com
![Page 12: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/12.jpg)
WAPArchitecture
12Blog: aforajayshahnirma.wordpress.com
![Page 13: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/13.jpg)
WAP – ProtocolLayers
13Blog: aforajayshahnirma.wordpress.com
![Page 14: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/14.jpg)
WAP – Protocol Layers
14Blog: aforajayshahnirma.wordpress.com
![Page 15: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/15.jpg)
SOC & AOC Clients
15
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/SOCto mobile devices or Always On Connectivity/AOC. SOC and AOC terminology effectively describe to our clients
thecommunications frequency and performance: capabilities of alternativesformobile 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.wordpress.com
![Page 16: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/16.jpg)
SOC Clients
20
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 WinCE 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.
16
Blog: aforajayshahnirma.wordpress.com
![Page 17: W i r e l e s s C o mm un i c a t i o n & M o b il e P r o g r a mm i n g](https://reader033.fdocuments.in/reader033/viewer/2022051416/568130dc550346895d96ed9e/html5/thumbnails/17.jpg)
AOC Clients
17
AOC clients require a wireless connection that is always on to be able to accessdata 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.wordpress.com