0% found this document useful (0 votes)
6 views8 pages

Client Server Model

The document discusses various computing models in mobile environments, including the Client-Server Model, Mobile Agent Model, Thin Client Model, and Client/Proxy/Server (C/P/S) Model. Each model is defined, explained, and evaluated for its advantages and disadvantages, highlighting aspects such as data management, processing efficiency, network dependency, and security concerns. The C/P/S model introduces a proxy layer to enhance communication between mobile clients and fixed servers, addressing limitations of traditional models.

Uploaded by

akadvserver
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views8 pages

Client Server Model

The document discusses various computing models in mobile environments, including the Client-Server Model, Mobile Agent Model, Thin Client Model, and Client/Proxy/Server (C/P/S) Model. Each model is defined, explained, and evaluated for its advantages and disadvantages, highlighting aspects such as data management, processing efficiency, network dependency, and security concerns. The C/P/S model introduces a proxy layer to enhance communication between mobile clients and fixed servers, addressing limitations of traditional models.

Uploaded by

akadvserver
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Client-Server Model in Mobile Computing

Definition:​
The Client-Server Model is a fundamental architecture in mobile computing where a mobile
device (client) communicates with a powerful computer (server) to request and receive
services or data. The client depends on the server to perform processing and store data,
while the server manages resources and responds to client requests.

How the Client-Server Model Works:

1.​ Client Side (Mobile Device):​

○​ The mobile device acts as the client.​

○​ It initiates requests for services or data.​

○​ Examples include requesting web pages, sending emails, or accessing


databases.​

2.​ Server Side:​

○​ The server is a centralized computer or group of computers with high


processing power.​

○​ It stores data and applications.​

○​ The server processes the client’s requests and sends back the required
information.​

3.​ Communication:​

○​ Communication occurs over a network (Internet or mobile network).​

○​ The client sends a request; the server processes it and responds.​

Example Scenario:

●​ When using a mobile banking app, the mobile device (client) sends a request to the
bank’s server for account balance.​

●​ The server verifies the request, fetches the data, and sends the balance back to the
client device.​
Advantages of Client-Server Model:

1.​ Centralized Data Management:​

○​ All data is stored on the server, ensuring easier updates and backups.​

○​ Central control improves security and data integrity.​

2.​ Simplified Client Devices:​

○​ Mobile devices don’t require heavy processing power.​

○​ Clients only handle user interface and send requests.​

3.​ Scalability:​

○​ Servers can be upgraded independently to handle more clients.​

○​ Multiple clients can be served simultaneously.​

4.​ Security:​

○​ Servers can implement strong security measures like firewalls and


authentication.​

Disadvantages of Client-Server Model:

1.​ Dependency on Network Connection:​

○​ Continuous and stable network connection is required.​

○​ Network failure causes loss of service on the client side.​

2.​ Server Bottleneck:​

○​ If the server is overloaded or down, all clients are affected.​

○​ Server maintenance or crashes cause service interruptions.​

3.​ Latency Issues:​

○​ Delays may occur due to data transmission between client and server,
especially on mobile networks.​
Mobile Agent Model in Mobile Computing

Definition:​
The Mobile Agent Model is a distributed computing model where a special software program
called a mobile agent moves autonomously from one computer or server to another across
the network. This agent carries the user’s code, data, and execution state, performing tasks
on behalf of the user at different network locations.

How the Mobile Agent Model Works

1.​ Agent Creation:​


The mobile agent is created on the user’s device or a client computer. It contains the
user’s request or program logic.​

2.​ Migration:​
The mobile agent moves (or migrates) from the client device to other remote servers
or nodes in the network. It travels across the network independently without
continuous communication with the user’s device.​

3.​ Local Execution:​


Once it reaches a server, the mobile agent executes its tasks locally on that server,
such as data processing, searching, or resource management.​

4.​ Result Collection:​


After completing the task at each server, the mobile agent either collects results from
multiple servers or aggregates the data.​

5.​ Return:​
The agent returns to the user’s device with the final results after completing its
operations on all intended servers.​

Key Characteristics

●​ Autonomy: The agent operates independently once dispatched.​

●​ Mobility: The agent physically migrates between nodes.​

●​ Asynchronous: No need for constant connection with the user’s device.​

●​ Intelligence: Can decide where and how to move next based on results.​
Example Scenario

Imagine a travel booking app that wants to find the cheapest flight tickets. Instead of the
mobile device repeatedly querying multiple airline servers, it sends a mobile agent:

●​ The agent visits several airline servers.​

●​ It searches and compares flight prices locally on each server.​

●​ It aggregates all the cheapest options.​

●​ Finally, it returns to the user’s device with the best flight deals.​

Advantages of the Mobile Agent Model

●​ Bandwidth Efficiency: Reduces network traffic by processing data locally on


servers instead of sending all raw data back and forth.​

●​ Reduced Latency: Local execution on servers minimizes delays caused by network


communication.​

●​ Robustness: Works well even if the mobile device has a weak or intermittent
network connection because the agent executes remotely.​

●​ Flexibility: Agents can adapt their behavior based on conditions encountered during
their journey.​

Disadvantages of the Mobile Agent Model

●​ Security Risks: Mobile agents can carry malicious code or be tampered with while
traveling, causing security vulnerabilities.​

●​ Complexity: Developing, managing, and debugging mobile agents is more


complicated than traditional client-server models.​

●​ Resource Usage: Servers must provide an environment to host agents, which may
increase resource consumption.​

●​ Trust Issues: Servers need to trust incoming agents, and users must trust the
servers on which agents run.​
Thin client model:

●​ The Thin Client Computing Model moves most application processing and data
storage from mobile devices to powerful, stationary servers.​

●​ The client devices, called thin clients, mainly handle input and output (display and
user actions).​

●​ Thin clients do very little processing themselves.​

●​ This model is ideal for devices with limited processing power, like dumb terminals
and small PDAs.

How the Thin Client Model Works

Application Execution on Server

●​ All applications run completely on a central, powerful server.​

●​ The mobile client device does not run applications; it only shows the results.​

●​ User inputs like mouse clicks and keyboard strokes are sent from the client to the
server.​

●​ This keeps the client device simple and saves its processing power.​

Virtual Desktop Display

●​ The MetaFrame server on the server side and ICA client on the client side work
together.​

●​ They show the user’s virtual desktop on the thin client’s screen.​

●​ This makes it look like the applications are running on the client device, even though
they are running remotely.​

●​ The user interacts with the remote desktop just as if it was local.​

Communication Protocol

●​ The client and server keep communicating constantly during the session.​

●​ Screen updates (what to display) are sent from the server to the client.​
●​ User actions (mouse and keyboard events) are sent from the client to the server.​

●​ CITRIX uses the Independent Computing Architecture (ICA) protocol to handle this
communication efficiently.​

●​ The server runs MetaFrame software on Windows NT to manage these interactions.​

Example: CITRIX Thin Client Architecture

●​ Server runs Windows NT with MetaFrame software to manage apps and user
sessions.​

●​ Client devices can be any platform and use ICA protocol to connect to the server.​

●​ All programs and data processing happen on the server, not on the client.​

●​ The thin client acts like a window to the server’s desktop, showing the virtual
desktop.​

Advantages of Thin Client Model

●​ Thin client devices can be simple and low-cost since they don’t run apps locally.​

●​ Centralized management makes updating software and securing data easier.​

●​ Works on different client platforms, so many types of devices can connect.​

●​ Uses less network bandwidth by sending only screen updates and user inputs.​

Challenges and Considerations

●​ Network latency (delays) affects user experience more than bandwidth limits.​

●​ Requires a stable and continuous network connection to work properly.​

●​ No offline use possible because all processing is on the server.​

●​ Network problems can cause lag or loss of connection.


📄 Client/Proxy/Server (C/P/S) Model
🟩 1. Introduction
●​ The Client/Proxy/Server (C/P/S) Model is an improved version of the traditional
Client/Server model.​

●​ It introduces a middle layer (called Proxy) that is mobility-aware and sits between the
client and the server.​

●​ This model helps to overcome the limitations of the traditional Client/Server model
when dealing with mobile clients.​

🟩 2. Basic Concept
●​ In the C/P/S model, the communication path between the client and the server is split
into two parts.​

●​ A "store-and-forward" component (Proxy) is used in the middle to manage data flow


between client and server.​

●​ This concept was first introduced in the Mowgli architecture.​

🟩 3. Role of the Proxy


●​ The proxy acts as a mediator between the mobile client and the fixed server.​

●​ It assumes the client is mobile and the server is part of the fixed (wired) network.​

●​ The server sends results to the proxy, and the proxy modifies these results based on
mobile client limitations.​

●​ The proxy may also store the results until the client is reconnected
(store-and-forward technique).​

🟩 4. Data Filtering by Proxy


●​ The proxy filters data before sending it to the client to match mobile device
capabilities and network conditions.​

●​ Common examples of data filtering:​


✔ Reducing image color and resolution​
✔ Removing audio files if the device does not support sound​
✔ Reducing file size to save bandwidth​
●​ Filtering decisions depend on:​
✔ Mobile device hardware features (e.g., screen size, audio support)​
✔ User preferences (e.g., turn off images, disable colors)​

🟩 5. Mowgli Architecture and Support


●​ The C/P/S model is supported by the Mowgli Architecture, which was specially
designed for mobile environments.​

●​ Mowgli introduces a service called Mowgli Data Channel Service (MCDS) that
ensures reliable data communication.​

●​ MCDS provides flow-controlled and prioritized data channels between base stations
and fixed hosts.​

●​ This allows protocol software in the fixed network to remain unchanged, simplifying
deployment.​

🟩 6. Specialized Components in Mowgli


●​ Two special components, the Mowgli Agent and the Mowgli Proxy, are used at both
ends of the wireless link.​

●​ These components offer similar functions as TCP and UDP protocols but are
optimized for mobile environments.​

●​ They manage data transmission reliability and reduce the effects of poor wireless
connections.​

🟩 7. Advantages of the C/P/S Model


●​ Allows mobile clients and fixed servers to function without needing special mobility
features.​

●​ Reduces communication problems caused by limited wireless bandwidth and mobile


device limitations.​

●​ Improves reliability and efficiency in mobile environments using filtering and smart
data handling.​

●​ Supports disconnected operation by storing data at the proxy when the client is
offline.​

You might also like