MC – “MOBILE COMPUTING” ?!!!!

“Mobile computing can be defined as a computing

environment over physical mobility.”

i.e. The user of the mobile computing environment will be able to

access data(Text, Voice, Image etc) from any device in any network while on move.
MOBILE COMPUTING DEVICES
MOBILE COMPUTING – BASED ON CONTEXT ALSO KNOWN
AS...
1) Anytime, Anywhere Information:

2) Virtual Home Environment:

3) Pervasive Computing:

4) Ubiquitous Computing:

5) Wearable Computing:

6) Global Service Portability:

7) Nomadic Computing:
MOBILE COMPUTING - FUNCTIONS/CHARECTORSTICS

A computing environment is defined as “MOBILE” if it supports one or more of these characteristics:

1) User mobility:
• User should be able to move from one physical location to another location and use same service.
2) Network mobility:
• User should be able to move from one network to another network and use same service.
3) Device mobility:
• User should be able to move from one device to another and use same service.
4) Session mobility:
• A user session should be able to move from one user-agent environment to another.
5) Service mobility:
• User should be able to move from one service to another.
6) Host mobility:
• The user should be either a client or server.
MOBILE COMPUTING– FUNCTIONAL BLOCK
DIAGRAM

1) User with device: The user device, this could be fixed device like desktop computer in office
or a portable device like mobile phone. E.g Laptop Computers, Desktop Computers, Fixed Telephones,
Mobile Phones, Digital TV with set top box, palmtop computers,two way pagers, handheld terminals etc.

2) Network : Whenever a user is mobile, he will be using different networks at different places
at different time eg GSM, CDMA, iMode, Ethernet, Wireless LAN, and Bluetooth. etc.
MOBILE COMPUTING
3) Gateways: This is required to interface different transport bearers.
Eg: From a fixed phone (with voice interface) we access a service by pressing different keys on
the telephone.
These keys generate DTMF (Dual Tone Multi Frequency) signals.
These analogue signals are converted into digital data by Interactive Voice Response(IVR)
gateway to interface with a computer application.

Other Examples will be WAP Gateway, SMS Gateway etc.

●

4) Middle Ware: This is more of a function rather than a separate visible node.
In the present context middleware handles the presentation and rendering of the context
on a particular device. It will also handle the security and personalization for different users.

5) Content: This is the domain where the origin server and content is This could be an application,
system or even an aggregation of systems. The content can be mass market, personal or
corporate content. Origin Server will have some means to accessing the database and the
storage devices.
MC - NETWORKS
Mobile Computing networks can be:-
❖ Fixed telephone n/w
❖ GSM
❖ GPRS
❖ ATM(Asynchronous Transfer Mode)
❖ Frame Relay
❖ ISDN(Integrated Service Digital Network)
❖ CDMA
❖ CDPD (Cellular Digital Packet Data )
❖ DSL (Digital Subscriber Loop)
❖ Dial-up, Wi-Fi (Wireless Fidelty) , 802.11 , Bluetooth, Ethernet ,Broadband etc.
MC - NETWORKS
1) Wireline Networks:-
• - Networks over physical wires/ tangible conductors.
- Generally Public networks covers wide area.
- Eg. Landline, Optical Fibre, Wired Broadband etc.
2) Wireless Networks:-
- No Physical medium
- GSM, GPRS, CDMA etc.
3) Ad Hoc Networks:-
- No Static Infrastructures , On demand networks.
- Connection between wireless enabled devices in the “range” of each other.
- Bluetooth , Wi-Fi(802.11) etc.
4)Bearers :-
- Different types of Networks there are different types of transport bearers.
- For GSM - SMS,USSD,WAP etc | For Landline - Voice
MC – MIDDLEWARE AND GATEWAYS
Middleware & Gateways
“Any software layered between User application and Operating system called a middleware” .
1)Communication middleware
- Communicates between different nodes and services over MC Network.
Eg: IBM Mainframe services, Java mail connector for IMAP or POP3.
2)Transaction processing middleware
- Session Oriented Dialog (SOD)
- Session Less Dialog (SLD)
3) Behaviour management middleware
- We can have applications which are developed specially to deliver certain manner.
Eg: Device specific rendering of Apps and Websites.
4)Communication gateways:
- Gateways are deployed when there are different transport bearers or networks with
dissimilar protocols.
Eg: IVR for Voice to Computer , WAP for access internet over mobile phone
MC – INTENET THE UBIQUITOUS NETWORK

Internet -
- Packet Switched.
- Delay Possible.
- Working based on TCP/IP

Telecommunication Network -
- Circuit Switched.
- No Delay
- Working based on SS7

- Data can be Audio , Video , Text etc.

Ubiquitous Network – Network of internet , Telecommunication etc.

MC – INTERNET AND UBIQUITOUS NETWORKS
MC – INTENET THE UBIQUITOUS NETWORK

Ubiquitous Network has three parts.

1) Core –
- Backbone of networks
- Primary task is to deliver traffic efficiently.
- See in bitstream point of view
2) Edge -
- Managed/owned by service providers(ISPs)
- See is Service point of view.
- Responsible to distribution of traffic.
3) Access -
- Services the devices/users at the end point
- Last mile of transmission
- Wireline/wireless

.
MC - THREE TIER ARCHITECTURE

• Mobile Networks needs to work on any network, bearer, agent and dev
• For universal access Ubiquitous network like internet is preferred.
• For accessing from any device, Web browsers are desirable.
• Three tiers:-
1)User Interface/Presentation tier
2)Application tier
3)Data Layer tier
MC – THREE TIER ARCHITECTURE
MC – THREE TIER ARCHITECTURE
THREE TIER ARCHITECTURE – PRESENTATION (TIER -1)

● Responsible for presenting information to the user.

● Output - Text, Audio, Visual etc
● Input – Keypress , touch , audio etc.
● Web browsers (Mozilla , Google chrome, IE, Safari etc)
● Agent software will
be installed/loaded in the user’s device.
THREE TIER ARCHITECTURE – APPLICATION (TIER -2)

● Middle tier or “Engine” of Ubiquitous network.

● Deals with business logic of application based on user inputs
● CGI, Java, JSP, Servlet .NET Services, PhP, Apache etc.
● Other functions are decision on rendering, network managem
security, data store access etc.
● Middleware are handling different tasks in this tier.
THREE TIER ARCHITECTURE – APPLICATION (TIER -2)

Middleware- major categories

1)Message Oriented middleware(MOM)
2)Transaction Processing middleware(TP)
3)Database Middleware
4)Communication Middleware
5)Distributed object and components
6)Transcoding Middleware
THREE TIER ARCHITECTURE – APPLICATION (TIER -2)
Middleware- major categories
1) Message Oriented middleware(MOM)
● Exchange of messages(asynchronous) between different applications
● Message contain formatted data, request for action, unsolicited response.
● Generally Asynchronous, Peer to Peer, publish/subscribe fashion.
● Message queues are used for temporary storage of messages.
● Eg: IBM- MQ Series, Java-JMS.
2) Transaction Processing middleware(TP)
● Provides and Manages Service to many clients
● (1000s in numbers)
● Used in Airline / Train Reservation,
● Banking Application etc.
THREE TIER ARCHITECTURE – APPLICATION (TIER -2)

Middleware- major categories

3) Communication Middleware
● Connection between applications
● Telnet , ssh etc
● Internet to mobile calling.
4) Distributed object and components

● Managing distributed objects over network

● Net-centric application devolopment

● Eg: CORBA(Common Object Request Broker Architecture)

THREE TIER ARCHITECTURE – APPLICATION (TIER -2)

• Middleware- major categories

• 5) Transcoding Middleware
● Transcode data from one format to another based on the compatibility of client.
● Content adaptation for meeting the client requirements,
● Eg 1: HTML page to WML page for mobile compatibility
● Eg 2: Viewing maps in Mobile/Tab/Laptop.
● Eg 3: Dropping frames based on bandwidth in video streaming.
● Internet Content Adaptation Protocol (ICAP) is the standard.
THREE TIER ARCHITECTURE – APPLICATION (TIER -2)
Internet Content Adaptation Protocol (ICAP) -
● Works in the “edge” of network, HTTP based protocol.
● Object based content vectoring of HTTP services.

ICAP Steps: -

1)User agent(end device) makes a request to ICAP -capable surrogate(ICAP Client).

2)The Surrogate sends the request to ICAP Server

3)The server executes the ICAP Resource’s service, and sends the modified

4) request/response to ICAP Client.

5)Surrogate sends the “modified request” to original server

6)The Original server responds the request.

7)The Surrogate (ICAP Client) sends(forward) the response to the client.

THREE TIER ARCHITECTURE – DATA (TIER - 3)

Data Tier is used to store data needed by applications and act as repository for both temporary an
data.
● Database middleware will be responsible for “data” exchange across tiers.
● Database middleware sometimes called as “data connectors”.
● Eg: JDBC , ODBC
● The databases can be Oracle, MySql, XML database etc.
SyncML -
● Protocol for synchronization of data access from different nodes.
● Caching and syncing of DB.
● Updating of emails, calendar, task lists etc. Between server and “mobile” device.
● SyncML supports – HTTP, WSP (Wireless Session Protocol), SMTP,POP3 and IMAP etc.
DESIGN CONSIDERATIONS OF MOBILE COMPUTING

1)Context Awareness .

1) Content with context awareness.

● www.abc.com/pc.html, www.abc.com/mob.html

2) Content switch on context.

● www.abc.com - server responds by “intelligently” aware of context.

3) Content transcoding on context:

● www.abc.com - middleware(like ICAP) analyse the context and transcode the response
from server.
DESIGN CONSIDERATIONS OF MOBILE COMPUTING

1)Type of user devices need to support the app.

2)Decide whether building a rich client(like whatsapp) or a thin web client(web
internet application(cloud services)
3)Mode of connection occasional, Realtime ,limited-bandwidth etc.