Jayson Castro

Danilo J. Mercado
IT238

1. A user arrives at a bus station that they have never visited before, carrying a smart cellphone that is
capable of wireless networking. Suggest how the user could be provided with information about the
local services and amenities at that station without entering the station’s name or attributes. What
technical challenges must be overcome?

Answer:
The user can access a location-based service app that automatically determines the station's location
and delivers real-time information about nearby services and amenities by using the wireless
networking capabilities

The user can then choose which connection will allow them to log in without a code or password by
accessing a location-based service app in the area.

Through the use of a login portal without password or code that contains all of this information, we
may advise the client, customer, or user about the services and amenities we offer at that station,
including ticket booths, waiting places, restrooms, eateries, surrounding attractions, and transit
alternatives.

However, using this method could present some technical difficulties for the user. First off, there might
be restrictions for customers, clients, or users in some places with bad signal coverage or crowded
large areas. Additionally, the app's functionality is dependent on the accessibility of Wi-Fi networks or
the availability of an internet connection, neither of which are usually stable in train stations or while
traveling.
Additionally, some stations might not have an access point with a longer range for a stronger and
better connection.

Sources:
-https://systemzone.net/
-additional personal encounters and an overview of the problem

2. List the three main software components that may fail when a client process invokes a method in a
server object, giving an example of a failure in each case. Suggest how the components can be made
to tolerate one another’s failures.

Failure of software component includes

 Server may be crashed before receiving message.

 Channel/process in between may be corrupted due to improper function of OS or other
software.
  The client who placed the request may not be able to receive it. This may occur due to time
delay caused by the server.
There three different methods by which we can handle failure:

1. Detecting Failure: - For detecting failure checksum can be used to detect corrupted data in a
file. Checksum is a simple bit message which is combined with the header and checked at the
receiver side for the authentication.
2. Masking Failure: - Some errors which is detected can be made less severe. There are two
different ways for masking failure. One way to masking failure is retransmitting the message
which is failed to arrive at the receiver side. Second way is replication of data so if one is
corrupted then another one can be used.
3. Tolerating Failure: - Most of service on internet face different failure at the time of process. So,
client can be designed to tolerate the failure. If server is not able to provide response to web
browser, it simply must show error message to the user.
4. Recovering Failure: - Recovery depends on the design of software. Recovery of data can be
done by replicating data on multiple location. The system can rollback data and make
computation by using one of stored location.
Sources:
https://www.coursehero.com/
https://www.numerade.com/

3. Describe and illustrate the client-server architecture of Web-based email as it may be implemented on
the Internet. Explain the possible layering of protocols and software components.

The client-server architecture refers to a system that hosts, delivers, and manages most of the
resources and services that the client requests. In this model, all requests and services are delivered
over a network, and it is also referred to as the networking computing model or client server network.
Client-server architecture typically features multiple users’ workstations, PCs, or other devices,
connected to a central server via an Internet connection or other network. The client sends a request
for data, and the server accepts and accommodates the request, sending the data packets back to the
user who needs them.

To sum it up briefly:

 First, the client sends their request via a network-enabled device

 Then, the network server accepts and processes the user request

 Finally, the server delivers the reply to the client

 What’s the Purpose of Client-Server Architecture?

The client-server network model brings a higher level of processing that increases the effectiveness of
workstation power, workgroup empowerment, remote network management, market-driven business,
and the preservation of existing investments.

In summary, client-server architecture provides the exact framework that today’s organizations need to
meet the challenges of a rapidly evolving IT world.

The three-tier client-server architecture consists of a presentation tier known as the User Interface layer, an
application tier called the Service layer, and a data tier comprising the database server. Three-tier architecture
can be divided into three parts:

 Presentation layer (or Client Tier): This layer takes care of the User Interface.

 Application layer (or Business Tier): This layer handles the detailed processing.

 Database layer (or Data Tier): This layer stores the information.

The Client system controls the Presentation layer; the Application server looks after the Application layer, and
the Server system supervises the Database layer.
Sources

www.simplilearn.com

https://www.chegg.com

1. Outline the scheme design that uses message retransmissions with IP multicast to overcome the problem
of dropped messages. Your scheme should take the following points into account:
a. There may be multiple senders.
b. Generally, only a small proportion of messages are dropped.
c. Recipients may not necessarily send a message within any particular time limit.

Assume that messages that are not dropped arrive in sender order.

Answer :

1. The sender multicasts each message to all intended recipients using IP multicast.
This allows multiple senders to transmit messages simultaneously

2. The recipients receive the multicast messages and acknowledge the successful
receipt of each message to the sender. This acknowledgment can be sent
through a separate unicast message or by piggybacking the acknowledgment on
a subsequent multicast message.

3. If the sender does not receive an acknowledgment for a specific message within
a certain time limit, it assumes that the message was dropped. The sender then
retransmits the dropped message using IP multicast.

4. Recipients receive the retransmitted message and acknowledge its successful

receipt. If a recipient receives a duplicate message due to retransmissions, it can
simply discard the duplicate based on the message sequence number or other
identification mechanism.

5. Since only a small proportion of messages are generally dropped, retransmitting

the dropped messages ensures reliable delivery of most messages without
significantly increasing network traffic.

6. It's important to note that the scheme does not require recipients to send a
message within any particular time limit. The acknowledgment can be sent at the
 recipient's convenience, as long as it is received by the sender within a
reasonable time frame.

By using message retransmissions with IP multicast and acknowledgments, this

scheme provides a reliable and efficient way to overcome the problem of
dropped messages in a multicast environment.

possible design using message retransmissions with IP multicast to overcome the problem of dropped
messages:

1. The sender multicasts each message to all intended

recipients using IP multicast. This allows multiple senders
to transmit messages simultaneously.
2. 2. The recipients receive the multicast messages and keep
track of the received messages using sequence numbers or
other identification mechanisms.
3. If a recipient detects a gap in the received sequence
numbers, indicating a dropped message, it sends a request
to the sender for a retransmission of the missing message.