Unit IV
Unit IV
Wireless Networks
Unit IV - WIRELESS
NETWORK APPLICATIONS
Dr.S.Kavi Priya
[email protected]
9842295563
Mobile Applications
and Mobile IP
Mobile Application Platforms
• limited computing power and do not run batch
programs
• interfaces (UIs) are typically vastly different -
include a touchscreen guided by touch or voice
command, and user
• mobile platforms typically run a core system
(such as Android or iOS) - allow third parties to
extend the platform with applications that run
on top of the framework (simply called “apps”)
Mobile Application Platforms
• Resource Constraints : powered almost
exclusively by batteries, have smaller amount of
RAM and internal memory, with limited computing
power for graphics and computation - provide user
interfaces to applications that interface to remote
cloud services
• The Interaction Layer : Along with input from
hardware buttons, users also typically interact with
a device by touch (gestures, for example) or voice
command
Mobile Application Platforms
• Two Example Hardware Stacks:
– Apple’s iOS (running on iPads and iPhones) : iOS
Apps written in Objective C and Swift, compiled using
Apple’s compiler, make use of iOS application framework,
through which they display GUI output, access sensory
(touch, location, voice) input, and communicate with
networks
– Google’s Android : widely installed, unique ROM to install
system apps, Android system allows programmers to write
in Java, but the Java bytecode (emitted by the Java
compiler) is translated to Dalvik virtual machine (DVM)
bytecode
Mobile App Development
• frameworks typically allow the programmer to access
– GUI interaction with the user
– Sensor data available (GPS, acceleration, etc.)
– Authentication and account access
– Interaction with remote servers
• Development Environments
– Google supports Java-Based Android Studio and Eclipse.
– iOS applications are written using XCode
Android System Architecture
Android Applications
• Each Android application consists of one or more instances of one or more of four
• Activities: An activity corresponds to a single screen visible as a user interface. For
example, an e-mail application might have one activity that shows a list of new e- mails,
another activity to compose an e- mail, and another activity for reading e- mails.
Activities can be exported/imported E.g. a camera application can start the activity in
the e- mail application that composes a new mail, in order for the user to share a
picture.
• Services: Services are typically used to perform background operations that take a
considerable amount of time to finish. This ensures faster responsiveness, for the main
thread (aka UI thread) of an application, with which the user is directly interacting. For
example, a service might create a thread or process to play music in the background
while the user is in a different application, or it might create a thread to fetch data over
the network without blocking user interaction with an activity. A service may be invoked
by an application. Additionally, there are system services that run for the entire lifetime
of the Android system, such as Power Manager, Battery, and Vibrator services.
Android Applications
• Content providers: A content provider acts as an interface
to application data that can be used by the application. One
category of managed data is private data, which is used only
by the application containing the content provider. For
example, the Notepad application uses a content provider to
save notes. The other category is shared data, accessible by
multiple applications. This category includes data stored in
file systems, an SQLite database, on the Web, or any other
persistent storage location your application can access
• Broadcast receivers: A broadcast receiver responds to
system- wide broadcast announcements. A broadcast can
originate from another application, such as to let other
applications know that some data has been downloaded to
the device and is available for them to use, or from the
system, for example a low- battery warning
The Activity Lifecycle
Mobile Application Deployment
• Deployment to Markets
• User Reviews and Marketing
• Quality Control
Mobile IP
Mobile IP
• When IP datagrams are exchanged over a connection between the mobile node and another
host the following operations occur:
1. Server X transmits an IP datagram destined for mobile node A, with A’s home address in the
IP header. The IP datagram is routed to A’s home network.
2. At the home network, the home agent intercepts the incoming IP datagram. The home agent
encapsulates the entire datagram inside a new IP datagram that has A’s care- of address in
the header, and retransmits the datagram. The use of an outer IP datagram with a different
destination IP address is known as tunneling. This IP datagram is routed to the foreign
agent.
3. The foreign agent strips off the outer IP header, encapsulates the original IP datagram in a
network-level PDU (e.g., a LAN LLC frame), and delivers the original datagram to A across
the foreign network.
4. When A sends IP traffic to X, it uses X’s IP address. In our example, this is a fixed address;
that is, X is not a mobile node. Each IP datagram is sent by A to a router on the foreign
network for routing to X. Typically, this router is also the foreign agent.
5. The IP datagram from A to X travels directly across the Internet to X, using X’s IP address.
Mobile IP
• To support the operations Mobile IP includes three basic capabilities:
• Discovery: A mobile node uses a discovery procedure to identify prospective
home agents and foreign agents.
• Registration: A mobile node uses an authenticated registration procedure to
inform its home agent of its care- of address.
• Tunneling: Tunneling is used to forward IP datagrams from a home address
to a care- of address.
Mobile IP - Discovery
• a router or other network node that can act as an agent periodically issues a
router advertisement ICMP message with an advertisement extension
• The router advertisement portion of the message includes the IP address of
the router.
• A mobile node listens for these agent advertisement messages. Because a
foreign agent could be on the mobile node’s home network (set up to serve
visiting mobile nodes), the arrival of an agent advertisement does not
necessarily tell the mobile node that it is on a foreign network.
• The mobile node must compare the network portion of the router’s IP address
with the network portion of its own home address. If these network portions do
not match, then the mobile node is on a foreign network.
Mobile IP - Discovery
• agent advertisement extension follows the ICMP router advertisement fields that includes the
following 1-bit flags:
R: Registration with this foreign agent is required (or another foreign agent on this network). Even
those mobile nodes that have already acquired a care-of address from this foreign agent must
reregister.
B: Busy. The foreign agent will not accept registrations from additional mobile nodes.
H: This agent offers services as a home agent on this network.
F: This agent offers services as a foreign agent on this network.
M: This agent can receive tunneled IP datagrams that use minimal encapsulation, explained
subsequently.
G: This agent can receive tunneled IP datagrams that use generic routing encapsulation (GRE)
encapsulation, explained subsequently.
r: reserved.
T: Foreign agent supports reverse tunneling.
Mobile IP - Agent Solicitation
• Foreign agents are expected to issue agent advertisement messages periodically. If a
mobile node needs agent information immediately, it c issue an ICMP router
solicitation message.
• Any agent receiving this message will then issue an agent advertisement
Mobile IP - Move Detection
• mobile node may move from one network to another due to some handoff mechanism,
without the IP level being aware of it. The agent discovery process is intended to enable the
agent to detect such a move. The agent may use one of two algorithms for this purpose:
• Use of lifetime field: When a mobile node receives an agent advertisement from a foreign
agent that it is currently using or that it is now going to register with, it records the lifetime
field as a timer. If the timer expires before the mobile node receives another agent
advertisement from the agent, then the node assumes that it has lost contact with that agent.
If, in the meantime, the mobile node has received an agent advertisement from another
agent and that advertisement has not yet expired, the mobile node can register with this
new agent. Otherwise, the mobile node should use agent solicitation to find an agent.
• Use of network prefix: The mobile node checks whether any newly received agent
advertisement is on the same network as the node’s current care- of address. If it is not, the
mobile node assumes that it has moved and may register with the agent whose
advertisement the mobile node has just received.
Mobile IP - Co-Located Addresses
• the care- of address is an IP address for the foreign agent. This foreign agent will
receive datagrams at this care-of address, intended for the mobile node, and then
forward them across the foreign network to the mobile node.
• However, in some cases a mobile node may move to a network that has no foreign
agents or on which all foreign agents are busy. As an alternative, the mobile node may
act as its own foreign agent by using a co-located care-of address.
• A co-located care-of address is an IP address obtained by the mobile node that is
associated with the mobile node’s current interface to a network.
• One means is to dynamically acquire a temporary IP address through an Internet
service such as Dynamic Host Configuration Protocol (DHCP).
• Another alternative is that the co-located ddress may be owned by the mobile node as a
long-term address for use only while visiting a given foreign network
Mobile IP - Registration
• Once a mobile node has recognized that it is on a foreign network and has acquired a
care-of address, it needs to alert a home agent on its home network and request that the
home agent forward its IP traffic. The registration process involves four steps:
1. The mobile node requests the forwarding service by sending a registration request to the
foreign agent that the mobile node wants to use.
2. The foreign agent relays this request to the mobile node’s home agent.
3. The home agent either accepts or denies the request and sends a registration reply to the
foreign agent.
4. The foreign agent relays this reply to the mobile node.
Mobile IP - Registration
• The registration request message consists of the following fields:
• Type: 1, indicates that this is a registration request.
• S: Simultaneous bindings. The mobile node is requesting that the home agent retain its prior mobility bindings. When simultaneous bindings are in effect, the
home agent will forward multiple copies of the IP datagram, one to each care-of address currently registered for this mobile node. Multiple simultaneous bindings
can be useful in wireless handoff situations, to improve reliability.
• B: Broadcast datagrams. Indicates that the mobile node would like to receive copies of broadcast datagrams that it would have received if it were attached to its
home network.
• D: Decapsulation by mobile node. The mobile node is using a co-located care-of address and will decapsulate its own tunneled IP datagrams.
• M: Indicates that the home agent should use minimal encapsulation, explained subsequently.
• G: Indicates that the home agent should use GRE encapsulation, explained subsequently.
• r: Reserved.
• T: Reverse tunneling requested.
• x: Reserved.
• Lifetime: The number of seconds before the registration is considered expired. A value of zero is a request for de-registration.
• Home Address: The home IP address of the mobile node. The home agent can expect to receive IP datagrams with this as a destination address, and must
forward those to the care- of address.
• Home Agent: The IP address of the mobile node’s home agent. This informs the foreign agent of the address to which this request should be relayed.
• Care-of Address: The IP address at this end of the tunnel. The home agent should forward IP datagrams that it receives with mobile node’s home address to this
destination address.
• Identification: A 64-bit number generated by the mobile node, used for matching registration requests to registration replies and for security purposes, as
explained subsequently.
• Extensions: The only extension so far defined is the authentication extension, explained subsequently.
Mobile IP - Registration
Mobile IP - Registration
• The registration reply message consists of the following fields:
• Type: 3, indicates that this is a registration reply.
• Code: Indicates result of the registration request
• Lifetime: If the code field indicates that the registration was accepted, the number of
seconds before the registration is considered expired. A value of zero indicates that the
mobile node has been de-registered.
• Home Address: The home IP address of the mobile node.
• Home Agent: The IP address of the mobile node’s home agent.
• Identification: A 64-bit number used for matching registration requests to registration
replies.
• Extensions: The only extension so far defined is the authentication extension,
explained subsequently.
Mobile IP - Securing the Registration Procedure
• Mobile IP is designed to resist two types of attacks:
– A node may pretend to be a foreign agent and send a registration request to a home
agent so as to divert traffic intended for a mobile node to itself.
– A malicious agent may replay old registration messages, effectively cutting the mobile
node from the network.
• For purposes of message authentication, each registration request and reply contains an
authentication extension which includes the following fields:
– Security Parameter Index (SPI): An index that identifies a security context between a pair of nodes.
This security context is configured so that the two nodes share a secret key and parameters relevant to this
association (e.g., authentication algorithm).
– Authenticator: A code used to authenticate the message. The sender inserts this code into the message
using a shared secret key. The receiver uses the code to ensure that the message has not been altered or
delayed. The authenticator protects the entire registration request or reply message, any extensions prior to
this extension, and the type and length fields of this extension.
Mobile IP - Securing the Registration Procedure
• Rich History
• Satellite
– Communications
– GPS
– Television
small cells
(spotbeams)
base station
or gateway
footprint
r3
(2 f )2
Prof. Dr.-Ing. Jochen Schiller, MC SS02 5.
http://www.jochenschiller.de/ 32
WAYS TO CATEGORIZE
COMMUNICATIONS SATELLITES
• Coverage area
– Global, regional, national
• Service type
– Fixed service satellite (FSS)
– Broadcast service satellite (BSS)
– Mobile service satellite (MSS)
• General usage
– Commercial, military, amateur,
experimental
minimal elevation:
elevation needed at least
to communicate with the satellite
satellite orbit
perigee
inclination
equatorial plane
24 satellite
velocity [ x1000 km/h] period [h]
20
16
12
4
synchronous distance
35,786 km
10 20 30 40 x106 m
radius
Van-Allen-Belts: 35768
km
ionized particles
2000 - 6000 km and
15000 - 30000 km
above earth surface
TENUATION 50
GHz
40 rain absorption
30
fog absorption
20
10
atmospheric
absorption
1 km
Cisco AIR-ANT3338
21dBi Parabolic Dish
Azimuth 3dB BW =12º
Elevation 3dB BW =12º
• Examples:
• Div =2º -> Gain(dBi) = 22,6 dBi (2x 22,6 if in both planes)
• Div =4º -> Gain(dBi) = 19,6 dBi
• Div =8º -> Gain(dBi) = 16,6 dBi
• Div=12º -> Gain(dBi) = 14,7 dBi (Vert and Hor: 14,7 x 2 = 29,4
dBi)
• Note: Cisco’s antenna with Div= 12º has a gain of 21 dBi (vs 29.4 dBi in theory) due to losses in other directions (side lobes).
• Pt = 40dBm (10W)
• Footprint = 471 716 Km2 (PI x 387.5km x 387.5km) (Iberian peninsula 582 860 km2)
• Aphy = 1m2 ; = 50%
• At = 10 dB
• Pr = 40 – 115.6 -10 = - 85.6 dBm
1.2º 775 Km
36000 Km