SSIGNMENT WORD
SSIGNMENT WORD
University
Collage of Computing
Department of
Computer Science
3rd year second semester
2024
Wireless and Mobile Computing
individual assignment
Wireless Communication: is the transfer of information over a distance without the use of
electrical conductors or wire.
Medium: the space or frequency through which the signals travel, such as air or vacuum.
Advantages:
Limitations:
Range: limited distance over which wireless signals can be effectively transmitted.
Q 2: Cellular network architecture
Cellular network: A network of distributed land areas called cells, each served by a
fixed location transceiver known as a Base transceiver station (BTS).
3G:
- Technology: W-CDMA
- Speed: Up to 2 Mbps
4G:
- Technology: LTE
- Speed: Up to 1 Gbps
- Features: HD streaming, faster data rates, less delay, and better voice over internet.
5G:
- Speed: Up to 10 Gbps
- Features: Super low delay, speedy data transfer, supports lots of IoT devices, and self-driving
cars.
1. Role of MAC: MAC is a part of the data link layer. It helps manage access to the network.
It makes sure data can be sent without clashes. It also keeps track of data frames that go in and
out of the network.
- CSMA/CD: Detects collisions after they happen. It allows devices to listen before sending data
but only finds out if there's a problem when two devices send data at the same time.
How it works: It looks for collisions. If there’s a crash, devices wait for a bit before
sending again.
- CSMA/CA: Avoids collisions before they happen. It also has devices listen but takes steps to
prevent conflicts before sending data.
How it works: It waits for an open channel before sending. It gets confirmation
that the data was sent successfully.
Q4: Mobile Computing Overview
Mobile computing means using devices that you can carry around, like
smartphones or tablets. These devices connect to wireless networks,
which lets you do things on the go. You can check your emails, browse
the internet, or use your favorite apps without being tied to a desk.
- Mobile Hardware: This is all about the devices you use, such as
smartphones, tablets, and laptops. These are lightweight and made to
travel with you.
Here are some of the problems we face and how we tackle them today:
- Battery Life: Keeping a device running all day can be tough. Luckily,
both hardware and software have gotten smarter about saving energy.
New techniques help devices use less power.
- Wi-Fi (IEEE 802.11): This is what lets you connect to the internet
without wires. It’s great for getting high-speed internet in your home or
at public places like cafes.
- ZigBee (IEEE 802.15.4): This one is often used in smart homes. It’s
designed for low power and works well for devices that don’t need to
send a lot of data.
They make sure devices from different brands can work together without
a hitch. This compatibility is key for a smooth user experience. When
everything plays nice, it not only helps users, but it also encourages
growth in the industry. We can mix and match devices easily, and it
keeps our connections secure.
Part B: Practical/Research-Based Questions
- Real-world uses like managing traffic, smart power grids, and safety in public areas.
Introduction
Smart cities use new technology to make life better for people living there. They
aim to be more sustainable and to make city services work smoother. Wireless
communication is vital because it lets different devices and systems talk to each
other easily. In this report, we’ll look at how Internet of Things (IoT) devices work
and the wireless protocols they use. We'll also explore their applications, like
traffic management, smart power grids, and public safety, as well as the challenges
that come with using wireless tech in smart cities.
IoT devices are a big part of what makes smart cities run. They connect things like
sensors, actuators, and communication networks. These devices send data using
wireless protocols, which help them stay efficient. Here are some common
protocols:
- Wi-Fi: Great for high-speed data transfer, making it perfect for tasks that need a
lot of information quickly.
- Bluetooth and BLE (Bluetooth Low Energy): Perfect for short distances with
low power use. Popular in gadgets you wear and smart home devices.
- Zigbee and Z-Wave: Made for low power and lower data needs, often used in
smart homes and sensor networks.
- NB-IoT (Narrowband IoT): Offers wide coverage and strong signal even in
tough spots. Useful for reliable connections in large areas.
-Smart Grids: We can combine renewable energy sources and keep tabs on
energy use thanks to wireless communication. Smart meters and sensors share data
with electric companies, allowing them to balance demand and cut down on energy
waste.
-Public Safety: Thanks to wireless networks, safety gets a boost. Cameras and
sensors can communicate quickly, supporting emergency responses and disaster
management. This gives first responders real-time updates and better awareness of
what’s going on.
While there are many upsides, smart cities face a few bumps when rolling out
wireless tech:
- Interference Issues: With lots of devices and networks, interference can mess
with signals and hurt the quality of communication.
- Security Risks: Wireless systems can be targets for cyber attacks. This means we
need strong security to protect important data and keep communications safe.
- Energy Use: Many IoT devices rely on batteries, making energy efficiency
crucial. There's a need for low-power protocols and ways to gather energy from the
environment.
- Lack of Standards: Different devices and systems often don’t play well
together. The absence of unified protocols can make communication and
integration difficult.
Conclusion
1. Throughput
Throughput is all about how much data gets successfully sent over the network.
Think of it like the speed of traffic in a city. We usually talk about throughput in
bits per second or packets per second.
For example, if you received 100 packets during your test, you would calculate it
like this:
2. Delay
Delay is the time it takes for a packet to get from where it starts to where it needs
to go. This time includes several parts like how long it takes to process, queue up,
actually send, and travel through the network.
- Start by recording the time each packet is sent and the time it is received.
- Then, find the time difference for each packet.
- Finally, add these differences together and divide by how many packets you
measured.
For example, if you had three packets with delay times of 0.1 seconds, 0.2
seconds, and 0.15 seconds, the math would look like this:
3. Packet Loss
Packet loss happens when some packets don’t make it to their destination. This
may be due to congestion, weak signals, or other issues. To figure out the packet
loss rate, do the following:
For example, if 150 packets were sent, but only 130 were received, you would do
the calculation like this:
Introduction
This report looks into how a basic wireless communication network works using
Network Simulator 2, or NS-2. We have three nodes in our network. Each node
can handle different streams of traffic. The main goal of running this simulation is
to see how well the network performs. We will check three things: how fast data
moves through it (throughput), how long it takes for a message to get from one
point to another (delay), and how many packets don't make it to their destination
(packet loss).
Simulation Setup
We set up our simulation in a small area measuring 500 by 500 units. We placed
our four nodes at specific spots within this space. The nodes follow a particular set
of rules known as the DSDV routing protocol. We also use some fixed settings for
network features like the type of link layer, the MAC type, and what kind of
antenna is used. To keep track of everything happening in the network, we use
something called the Global Object for Dynamics (God).
For performance testing, we created three different UDP traffic flows between the
nodes. Each flow was set with different packet intervals. We ran the simulation for
10 seconds, and we saved the results to files so we could look at them later.
Here we would include screenshots showing how our three-node wireless network
looked during the simulation.
Performance Metrics
1. Throughput: This is a key measure of how much data the network can send.
We calculate it by counting the total packets that reached the sink nodes and
multiplying that by the packet size, which is 512 bytes. Then, we divide that
number by the time the simulation was running 10 seconds. This gives us the
throughput in bytes per second.
2. Delay: Delay is the time it takes for a packet to go from where it started to
where it’s supposed to end up. This includes all sorts of times: how long it takes to
process the packet, how long it waits in line, how long it takes to send, and how
long it takes to travel through the air. We find the average delay by looking at
when each packet was sent and received and then calculating the average time
difference.
3. Packet Loss: Packet loss tells us how many packets didn’t make it to the end.
This could happen for several reasons, like if the network is busy, if there’s
interference, or if there are errors in sending. To find the packet loss rate, we
compare the total number of packets sent with how many were received and
express that as a percentage.
Our simulation showed a throughput of about 5120 bytes per second. This means
that the network is pretty good at sending data, given how we set things up. This
number tells us that the network can handle data efficiently.
Delay:
The average delay we recorded was 0.15 seconds. This low number shows that the
network is quick at sending out and receiving data. It indicates that all the delays,
like processing time and waiting time, are under control.
Packet Loss:
We saw a packet loss rate of around 13.33%. This number shows both the
strengths and weaknesses of the network. It indicates that some packets didn’t
reach their destinations, possibly due to congestion or interference. Figuring out
how to fix these problems could help the network perform better.
Conclusion
The simulation of our basic wireless communication network helped us learn a lot
about how well it works. We found out that the throughput is 5120 bytes per
second, the average delay is 0.15 seconds, and the packet loss rate is 13.33%.
These numbers are really important for understanding how to improve and design
better networks.