CST476 Mobile Computing 1
CST476 Mobile Computing 1
4.Device Mobility: The user should be able to move from one device
to another and use the same service. An example could be sales
representatives using their desktop computer in their home office.
During the day while they are on the street they would like to use
their Palmtop to access the application.
5. Session Mobility: A user session should be able to move from one
user-agent environment to another. A user watching a video on their
smartphone during a train ride can seamlessly switch to their laptop
upon reaching their office. The paused video session transitions from
the smartphone to the laptop, enabling the user to resume watching
the video uninterrupted.
CST476 Mobile Computing 7
6.Agent Mobility: The user-agent or the applications should be able to
move from one node to another In various computing contexts like
Cloud Computing, software entities such as aglets, crawler software,
and even malicious software like worms or viruses move freely
between different nodes, while in Cloud Computing, applications
seamlessly transition between platforms and infrastructures based
on temporal and economic factors, without being fixed to any specific
host.
7.Host Mobility: The user device can be either a client or server.
When it is a server or host, some of the complexities change. In case
of host mobility, mobility of the IP needs to be taken care of.
Core
The Data Tier is used to store data needed by the application and acts
as a repository for both temporary and permanent data.
The data can be stored in any form of datastore or database. These
can range from sophisticated relational database, legacy hierarchical
database, to even simple text files.
Database Middleware
Database middleware allows the business logic to be independent and
transparent of the database technology and the database vendor.
Database middleware runs between the application program and the
database. These are sometimes called database connectors as well.
Examples of such middleware will be ODBC,JDBC, etc. Using these
middleware, the application will be able to access data. from any data
source.
Data sources can be text files, flat files, spreadsheets, or a network,
relational, indexed, hierarchical, XML database, object database, erc.,
from vendors like Oracle, SQL, Sybase, etc.
Service Requester:
Function: Requests Web service execution.
Responsibilities: Initiates communication with service providers.
Service Provider:
Function: Processes requests for Web services.
Responsibilities: Executes requested services and provides necessary functionality
or data.
Discovery Agency (Broker):
• Function: Facilitates publication and discovery of Web service descriptions.
• Responsibilities: Acts as intermediary, ensuring service descriptions are
published and discoverable.