MULTICAST CAPACITY IN MANET WITH INFRASTRUCTURE SUPPORT

PROJECT REPORT

Submitted to the Department of Computer Science & Engineering in the FACULTY OF ENGINEERING & TECHNOLOGY

In partial fulfillment of the requirements for the award of the degree

MASTER OF TECHNOLOGY

COMPUTER SCIENCE & ENGINEERING

APRIL 2015

BONAFIDE CERTIFICATE

Certified that this project report titled “MULTICAST CAPACITY IN MANET WITH INFRASTRUCTURE SUPPORT” is the bonafide work of Mr. _____________Who carried out the research under my supervision Certified further, that to the best of my knowledge the work reported herein does not form part of any other project report or dissertation on the basis of which a degree or award was conferred on an earlier occasion on this or any other candidate.

Signature of the Guide Signature of the H.O.D

Name Name

CHAPTER1

1.1 ABSTRACT:

We study the multicast capacity under a network model featuring both node’s mobility and infrastructure support. Combinations between mobility and infrastructure, as well as multicast transmission and infrastructure, have already been showed effective ways to increase it. In this work, we jointly consider the impact of the above three factors on network capacity.

We assume that m static base stations and n mobile users are placed in an ad hoc network. A general mobility model is adopted, such that each user moves within a bounded distance from its home-point with an arbitrary pattern. In addition, each mobile node serves as a source of multicast transmission, which results in a total number of n multicast transmissions.

We focus on the situations in which base stations actually benefit the capacity improvement, and find that multicast capacity in a mobile hybrid network falls into several regimes. For each regime, reachable upper and lower bounds are derived. Our work contains theoretical analysis of multicast capacity in hybrid networks and provides guidelines for the design of real hybrid system combing cellular and ad hoc networks.

1.2 INTRODUCTION:

Recent years witness a rapid development in wireless ad hoc networks, in both academic and industrial fields. Kumar and Gupta have showed in their ground breaking work that, even with the optimal scheduling, routing and relaying of packets, the per-node capacity still decreases as when n approaches the infinity. Many studies try to improve this disappointing scalability of throughput capacity by introducing different characteristics into ad hoc networks, such as mobility of nodes, an infrastructure of the network: a multicast transmission scheme.

Mobility in ad hoc networks was considered firstly by Tse. A store-carry-forward relaying scheme was proposed and proven to sustain a per-node capacity, if each node can visit the whole network area with an uniformly ergodic mobility process. Garetto et al. generalize the mobility model through a restriction that each moving node is located within a circle of radius 1/f(n). By mapping the network to a generalized random geometric graph, they have proven that per-node capacity is achievable.

Infrastructure in an ad hoc network provides a more straightforward increase to the capacity. Liu et al. claim that infrastructure can offer a linear capacity increase in a hybrid network, when the number of base stations increases asymptotically faster than . In addition, Kozat and Tassiulas prove that if the number of users served by each BS is bounded above, a per-node capacity of can be achieved. In Agarwal and Kumar further extend this result to .

Multicast transmission refers to the transmission from a single node to other k _ 1 nodes, so as to generalize both unicast and broadcast transmissions. In Li proves that multicast transmission can obtain a per-flow capacity of , which is larger than that of k unicast transmissions. The gain of multicast transmission results from a merge of relay paths within a minimum spanning tree. In Li et al. extend the multicast transmission to a Gaussian channel model and show similar capacity improvement under the corresponding protocol.

Many existing studies focus on the combinations of the above characteristics. Some aim to further increase the network performance, while others try to present a more realistic scenario. In Li et al. explore the multicast capacity in a static hybrid network with infrastructure support. Establishing a multicast tree with the help of infrastructure and employing a hybrid routing scheme, they have showed that the achievable multicast capacity in a hybrid network with m BSs is .On the other hand, Huang, Wang et al. study the unicast capacity of mobile hybrid networks and jointly consider the influences of node’s mobility and infrastructure support on it. A pernode capacity is for strong mobility, and for weak and trivial mobility.

In this paper, we further study the multicast capacity scaling laws of a mobile hybrid network characterizing both mobility and infrastructure. In our model, each of the n users moves around a home-point within a bounded radius. m wire-connected base stations are placed in a wireless ad hoc network, of which the area scales with n as f2(n) There are totally nc clusters with radius r = and the number of destinations in the multicast scheme is assumed as k. A multicast path can be generated with an infrastructure routing and a pure ad hoc routing, as well as a combination of both. Intuitively, in our hybrid routing scheme, we hope to circumvent the bottleneck of backbone transmission or wireless access for cellular networks and take the advantage of them, thus the capacity can be improved.

1.3 LITRATURE SURVEY

MULTICAST CAPACITY OF WIRELESS AD HOC NETWORKS

PUBLICATION: X.-Y. Li, IEEE/ACM Trans. Netw., vol. 17, no. 3, pp. 950-961, June 2009.

We study the multicast capacity of large-scale random extended multihop wireless networks, where a number of wireless nodes are randomly located in a square region with side length a = √n, by use of Poisson distribution with density 1. All nodes transmit at a constant power P , and the power decays with attenuation exponent α > 2. The data rate of a transmission is determined by the SINR as Blog(1+ SINR), where B is the bandwidth. There are ns randomly and independently chosen multicast sessions. Each multicast session has k randomly chosen terminals. We show that when k ≤ θ₁[(n)/((logn)^2α+
6)] and ns ≥ θ₂n^1/2+β, the capacity that each multicast session can achieve, with high probability, is at leastc₈[(√n)/(ns√k)], where θ₁, θ₂, and c₈ are some special constants and β > 0 is any positive real number. We also show that for k = O( [(n)/(log²n)]) , the per-flow multicast capacity under Gaussian channel is at most O([(√n)/(ns √k)]) when we have at least ns = Ω(logn) random multicast flows. Our result generalizes the unicast capacity for random networks using percolation theory.

MULTICAST CAPACITY OF WIRELESS AD HOC NETWORKS UNDER GAUSSIAN CHANNEL MODEL

PUBLICATION: X.-Y. Li, Y. Liu, S. Li, and S. Tang, IEEE/ACM Trans. Netw., vol. 18, no. 4, pp. 1145-1157, Aug. 2010.

MULTICAST CAPACITY FOR HYBRID WIRELESS NETWORKS

PUBLICATION: X. Mao, X.-Y. Li, and S. Tang, in Proc. ACM MobiHoc, Hong Kong, 2008, pp. 189-198.

We study the multicast capacity for hybrid wireless networks consisting of ordinary wireless nodes and base stations under Gaussian channel model, which generalizes both the unicast capacity and broadcast capacity for hybrid wireless networks. We simply consider the hybrid extended network, where the ordinary wireless nodes are placed in the square region A(n) with side-length radicn according to a Poisson point process with unit intensity. In addition, m additional base stations (BSs) serving as the relay gateway are placed regularly in the region A(n) and they are connected by a high-bandwidth wired network. Three broad categories of multicast strategies are proposed in this paper. According to the different scenarios in terms of m, n and n_d, we select the optimal scheme from the three categories of strategies, and derive the achievable multicast throughput based on the optimal decision.

CLOSING THE GAP OF MULTICAST CAPACITY FOR HYBRID WIRELESS NETWORKS

[4] S. Tang, X. Mao, T. Jung, J. Han, X.-Y. Li, B. Xu, and C. Ma, in Proc. ACM MobiHoc, Hilton Head, Italy, 2012,

pp. 135-144.

We study the multicast capacity of a random hybrid wireless network consisting of wireless terminals and base stations. Assume that n wireless terminals (nodes) are randomly deployed in a square region and all nodes have the uniform transmission range r and uniform interference range R = Θ(r); each wireless node can transmit/receive at Wa-bps. In addition, there are m base stations (neither source nodes nor receiver nodes) that are placed uniformly in this square region; each base station can communicate with adjacent base stations directly with a data rate WB-bps and the transmission rate between a base station and a wireless node is Wc-bps. Assume that there is a set of ns randomly selected nodes that will serve as the source nodes of ns multicast flows (each flow has randomly selected k−1 receivers). We found that the multicast capacity for hybrid networks has three regimes and for each of regimes, we derive the matching asymptotic upper and lower bounds of multicast capacity. Index Terms—Hybrid networks, capacity, multicast, broadcast. I.

CHAPTER 2

2.0 SYSTEM ANALYSIS

2.1 EXISTING SYSTEM:

Many existing studies focus on the combinations of the above characteristics. Some aim to further increase the network performance, while others try to present a more realistic scenario. In, Liet al. explores the multicast capacity in a static hybrid network with infrastructure support. Establishing a multicast tree with the help of infrastructure and employing a hybrid routing scheme, they have showed that the achievable multicast capacity in a hybrid network. On the other hand, Huang, Wanget al. study the unicast capacity of mobile hybrid networks and jointly consider the influences of node’s mobility and infrastructure support on it. A per-node capacity is for strong mobility, and for weak and trivial mobility.

2.1.1 DISADVANTAGES:

In a many existing systems the scalability is failure of throughput capacity and some of the failures in the mobility nodes, and in networks infrastructure.

2.2 PROPOSED SYSTEM:

In this paper, we further study the multicast capacity scaling laws of a mobile hybrid network characterizing both mobility and infrastructure. In our model, each of the n users moves around a home-point within a bounded radius. An m wire-connected base station is placed in a wireless ad hoc network, of which the area scales with n. There are totally n_c clusters with radius r and the number of destinations in the multicast scheme is assumed as k. A multicast path can be generated with an infrastructure routing and a pure ad hoc routing, as well as a combination of both. Intuitively, in our hybrid routing scheme, we hope to circumvent the bottleneck of backbone transmission or wireless access for cellular networks and take the advantage of them, thus the capacity can be improved.

2.2.1 ADVANTAGES:

Our work is the first one to consider the effect of a general mobility on multicast transmission. Furthermore, we study multicast capacity in a more realistic network model featuring both mobility and infrastructure support. As a result, our work generalizes both unicast and broadcast capacity results in MANETs and hybrid networks.
We can prove that mobility is trivial and the network acts as a static one.

2.3 HARDWARE & SOFTWARE REQUIREMENTS:

2.3.1 HARDWARE REQUIREMENT:

v Processor – Pentium –IV

Speed – 1.1 GHz
- RAM – 256 MB (min)
- Hard Disk – 20 GB
- Floppy Drive – 1.44 MB
- Key Board – Standard Windows Keyboard
- Mouse – Two or Three Button Mouse
- Monitor – SVGA

2.3.2 SOFTWARE REQUIREMENTS:

Operating System : Windows XP or Win7
Front End : Microsoft Visual Studio .NET 2008
Document : MS-Office 2007

CHAPTER 3

3.0 SYSTEM DESIGN:

Data Flow Diagram / Use Case Diagram / Flow Diagram:

The DFD is also called as bubble chart. It is a simple graphical formalism that can be used to represent a system in terms of the input data to the system, various processing carried out on these data, and the output data is generated by the system

The data flow diagram (DFD) is one of the most important modeling tools. It is used to model the system components. These components are the system process, the data used by the process, an external entity that interacts with the system and the information flows in the system.

DFD shows how the information moves through the system and how it is modified by a series of transformations. It is a graphical technique that depicts information flow and the transformations that are applied as data moves from input to output.

DFD is also known as bubble chart. A DFD may be used to represent a system at any level of abstraction. DFD may be partitioned into levels that represent increasing information flow and functional detail.

NOTATION:

SOURCE OR DESTINATION OF DATA:

External sources or destinations, which may be people or organizations or other entities

DATA SOURCE:

Here the data referenced by a process is stored and retrieved.

PROCESS:

People, procedures or devices that produce data. The physical component is not identified.

DATA FLOW:

Data moves in a specific direction from an origin to a destination. The data flow is a “packet” of data.

MODELING RULES:

There are several common modeling rules when creating DFDs:

All processes must have at least one data flow in and one data flow out.
All processes should modify the incoming data, producing new forms of outgoing data.
Each data store must be involved with at least one data flow.
Each external entity must be involved with at least one data flow.
A data flow must be attached to at least one process.

SYSTEM ARCHITECTURE:

DATAFLOW DIAGRAM

UML DIAGRAMS:

USECASE DIAGRAM:

CLASS DIAGRAM:

SEQUENCE DIAGRAM:

ACTIVITY DIAGRAM:

CHAPTER 4

4.0 IMPLEMENTATION:

In this section, we firstly provide a definition of a uniformly dense network, as well as some characteristics in such network. We show that when a network falls into strong mobility regime, it is equivalent to classify it as a uniformly dense network. Then reachable upper and lower bounds are presented in both pure ad hoc routing and cellular routing for uniformly dense networks. For pure ad hoc routing, we map the mobile network into a random geometric graph, and derive reachable capacity bounds. For cellular routing, we divide the routing scheme into three phases and achieve reachable upper and lower bounds in each phase, as well.

In the following part of this section, we will derive asymptotically reachable lower bound on multicast capacity in uniformly dense networks by ad hoc routing. We have already mapped a mobile network into a static graph, which makes the establishment of a multicast routing possible and realistic. We employ the next algorithm from to set up the multicast routing in graph. We consider the impact of infrastructure in multicast capacity of a mobile network. Multicast flows will be routed through BSs. We divide the bandwidth in air channels into uplink bandwidth WA and downlink bandwidth WC.

We further assume that the bandwidth of optical fibers connecting BSs is WB. Cellular routing RC consists of three phases. In the first phase, a multicast source node routes the packets to a BS. In the second phase, the packets are routed to the cells that contain destinations. In the last phase, BSs of these cells broadcast packets to the destinations. It is worth pointing out that such a routing cannot be established directly in mobile networks. However, with the help of the mapping scheme presented in the previous section, it is possible to generate a cellular multicast route in a random geometric graph.

4.1 ALGORITHM

4.2 MODULES:

MULTICAST CAPACITY:

SCHEDULING POLICIES:

HYBRID NETWORKS MOBILITY:

TRANSMISSION INFRASTRUCTURE:

COMMUNICATION AND INTERFERENCE:

4.3 MODULE DESCRIPTION:

MULTICAST CAPACITY:

Multicast capacity under a network model featuring both node’s mobility and infrastructure support between mobility and infrastructure, as well as multicast transmission and infrastructure, have already been shown effective ways to increase capacity. In this work, we jointly consider the impact of the above three factors on network capacity. We assume that m static base stations and n mobile users are placed in an ad hoc network, of which the area scales with n as f²(n). A general mobility model is adopted, such that each user moves within a bounded distance from its home point with an arbitrary pattern. In addition, each mobile node serves as the source of a multicast transmission, which results in a total number of n multicast transmissions. We focus on the situations that base stations actually benefit the capacity, and prove that multicast capacity of mobile hybrid network falls into three regimes. For each regime, matching upper and lower bounds are derived.

SCHEDULING POLICIES:

Scheduling is the method by which threads, processes or data flows are given access to system resources (e.g. processor time, communications bandwidth). This is usually done to load balance and share system resources effectively or achieve a target quality of service. The need for a scheduling algorithm arises from the requirement for most modern systems to perform multitasking (executing more than one process at a time) and multiplexing (transmit multiple data streams simultaneously across a single physical channel). A multicast path can be generated with an infrastructure routing and a pure ad hoc routing, as well as a combination of both. Intuitively, in our hybrid routing scheme, we hope to circumvent the bottleneck of backbone transmission or wireless access for cellular networks and take the advantage of them, thus the capacity can be improved.

HYBRID NETWORKS MOBILITY:

Further increase the network performance, while others try to present a more realistic scenario in the multicast capacity in a static hybrid network with infrastructure support. Establishing a multicast tree with the help of infrastructure and employing a hybrid routing scheme, they have showed that the achievable multicast capacity in a hybrid network with m BSs is

We further study the multicast capacity scaling laws of a mobile hybrid network characterizing both mobility and infrastructure. In our model, each of the n users moves around a home-point within a bounded radius. M wire-connected base stations are placed in a wireless ad hoc network, of which the area scales with n as f2n.

TRANSMISSION INFRASTRUCTURE:

We consider the effects of mobility and infrastructure in multicast capacity of a wireless mobile ad hoc network. We divide mobility into three regimes, and present reachable upper bounds and lower bounds for each regime. We assume that bandwidth is W for wireless channel, and WB for wired connections. In cellular routing, we further divide wireless frequency resource W into uplink bandwidth WA and downlink bandwidth WC.

COMMUNICATION AND INTERFERENCE:

Base stations communicate with each other through optical fiber with bandwidth WB. This kind of communication will not cause interference to themselves or wireless communications. We assume that the available bandwidth in all the wireless channels is W. In ad hoc routing, transmissions fully occupy the wireless bandwidth W. In cellular routing, bandwidth is further divided into uplink bandwidth WA and downlink bandwidth WC. All the communications in wireless channels are characterized by Protocol Model, which is defined as followed.

CHAPTER 5

5.0 SYSTEM STUDY:

5.1 FEASIBILITY STUDY:

The feasibility of the project is analyzed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY
TECHNICAL FEASIBILITY
SOCIAL FEASIBILITY

5.1.1 ECONOMICAL FEASIBILITY:

This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.

5.1.2 TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.

5.1.3 SOCIAL FEASIBILITY:

The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system.

5.2 SYSTEM TESTING:

Testing is a process of checking whether the developed system is working according to the original objectives and requirements. It is a set of activities that can be planned in advance and conducted systematically. Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the global will be successfully achieved. In adequate testing if not testing leads to errors that may not appear even many months.

This creates two problems, the time lag between the cause and the appearance of the problem and the effect of the system errors on the files and records within the system. A small system error can conceivably explode into a much larger Problem. Effective testing early in the purpose translates directly into long term cost savings from a reduced number of errors. Another reason for system testing is its utility, as a user-oriented vehicle before implementation. The best programs are worthless if it produces the correct outputs.

5.2.1 UNIT TESTING:

Description	Expected result
Test for application window properties.	All the properties of the windows are to be properly aligned and displayed.
Test for mouse operations.	All the mouse operations like click, drag, etc. must perform the necessary operations without any exceptions.

A program represents the logical elements of a system. For a program to run satisfactorily, it must compile and test data correctly and tie in properly with other programs. Achieving an error free program is the responsibility of the programmer. Program testing checks for two types of errors: syntax and logical. Syntax error is a program statement that violates one or more rules of the language in which it is written. An improperly defined field dimension or omitted keywords are common syntax errors. These errors are shown through error message generated by the computer. For Logic errors the programmer must examine the output carefully.

5.1.2 FUNCTIONAL TESTING:

Functional testing of an application is used to prove the application delivers correct results, using enough inputs to give an adequate level of confidence that will work correctly for all sets of inputs. The functional testing will need to prove that the application works for each client type and that personalization function work correctly.When a program is tested, the actual output is compared with the expected output. When there is a discrepancy the sequence of instructions must be traced to determine the problem. The process is facilitated by breaking the program into self-contained portions, each of which can be checked at certain key points. The idea is to compare program values against desk-calculated values to isolate the problems.

Description	Expected result
Test for all modules.	All peers should communicate in the group.
Test for various peer in a distributed network framework as it display all users available in the group.	The result after execution should give the accurate result.

5.1. 3 NON-FUNCTIONAL TESTING:

The Non Functional software testing encompasses a rich spectrum of testing strategies, describing the expected results for every test case. It uses symbolic analysis techniques. This testing used to check that an application will work in the operational environment. Non-functional testing includes:

Load testing
Performance testing
Usability testing
Reliability testing
Security testing

5.1.4 LOAD TESTING:

An important tool for implementing system tests is a Load generator. A Load generator is essential for testing quality requirements such as performance and stress. A load can be a real load, that is, the system can be put under test to real usage by having actual telephone users connected to it. They will generate test input data for system test.

Description	Expected result
It is necessary to ascertain that the application behaves correctly under loads when ‘Server busy’ response is received.	Should designate another active node as a Server.

5.1.5 PERFORMANCE TESTING:

Performance tests are utilized in order to determine the widely defined performance of the software system such as execution time associated with various parts of the code, response time and device utilization. The intent of this testing is to identify weak points of the software system and quantify its shortcomings.

Description	Expected result
This is required to assure that an application perforce adequately, having the capability to handle many peers, delivering its results in expected time and using an acceptable level of resource and it is an aspect of operational management.	Should handle large input values, and produce accurate result in a expected time.

5.1.6 RELIABILITY TESTING:

The software reliability is the ability of a system or component to perform its required functions under stated conditions for a specified period of time and it is being ensured in this testing. Reliability can be expressed as the ability of the software to reveal defects under testing conditions, according to the specified requirements. It the portability that a software system will operate without failure under given conditions for a given time interval and it focuses on the behavior of the software element. It forms a part of the software quality control team.

Description	Expected result
This is to check that the server is rugged and reliable and can handle the failure of any of the components involved in provide the application.	In case of failure of the server an alternate server should take over the job.

5.1.7 SECURITY TESTING:

Security testing evaluates system characteristics that relate to the availability, integrity and confidentiality of the system data and services. Users/Clients should be encouraged to make sure their security needs are very clearly known at requirements time, so that the security issues can be addressed by the designers and testers.

Description	Expected result
Checking that the user identification is authenticated.	In case failure it should not be connected in the framework.
Check whether group keys in a tree are shared by all peers.	The peers should know group key in the same group.

5.1.8 WHITE BOX TESTING:

White box testing, sometimes called glass-box testing is a test case design method that uses the control structure of the procedural design to derive test cases. Using white box testing method, the software engineer can derive test cases. The White box testing focuses on the inner structure of the software structure to be tested.

Description	Expected result
Exercise all logical decisions on their true and false sides.	All the logical decisions must be valid.
Execute all loops at their boundaries and within their operational bounds.	All the loops must be finite.
Exercise internal data structures to ensure their validity.	All the data structures must be valid.

5.1.9 BLACK BOX TESTING:

Black box testing, also called behavioral testing, focuses on the functional requirements of the software. That is, black testing enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a program. Black box testing is not alternative to white box techniques. Rather it is a complementary approach that is likely to uncover a different class of errors than white box methods. Black box testing attempts to find errors which focuses on inputs, outputs, and principle function of a software module. The starting point of the black box testing is either a specification or code. The contents of the box are hidden and the stimulated software should produce the desired results.

Description	Expected result
To check for incorrect or missing functions.	All the functions must be valid.
To check for interface errors.	The entire interface must function normally.
To check for errors in a data structures or external data base access.	The database updation and retrieval must be done.
To check for initialization and termination errors.	All the functions and data structures must be initialized properly and terminated normally.

All the above system testing strategies are carried out in as the development, documentation and institutionalization of the proposed goals and related policies is essential.

CHAPTER 6

6.0 SOFTWARE DESCRIPTION:

6.1 JAVA TECHNOLOGY:

Java technology is both a programming language and a platform.

The Java Programming Language

The Java programming language is a high-level language that can be characterized by all of the following buzzwords:

Simple
- Architecture neutral
- Object oriented
- Portable
- Distributed
- High performance
- Interpreted
- Multithreaded
- Robust
- Dynamic
- Secure

With most programming languages, you either compile or interpret a program so that you can run it on your computer. The Java programming language is unusual in that a program is both compiled and interpreted. With the compiler, first you translate a program into an intermediate language called Java byte codes —the platform-independent codes interpreted by the interpreter on the Java platform. The interpreter parses and runs each Java byte code instruction on the computer. Compilation happens just once; interpretation occurs each time the program is executed. The following figure illustrates how this works.

You can think of Java byte codes as the machine code instructions for the Java Virtual Machine (Java VM). Every Java interpreter, whether it’s a development tool or a Web browser that can run applets, is an implementation of the Java VM. Java byte codes help make “write once, run anywhere” possible. You can compile your program into byte codes on any platform that has a Java compiler. The byte codes can then be run on any implementation of the Java VM. That means that as long as a computer has a Java VM, the same program written in the Java programming language can run on Windows 2000, a Solaris workstation, or on an iMac.

6.2 THE JAVA PLATFORM:

A platform is the hardware or software environment in which a program runs. We’ve already mentioned some of the most popular platforms like Windows 2000, Linux, Solaris, and MacOS. Most platforms can be described as a combination of the operating system and hardware. The Java platform differs from most other platforms in that it’s a software-only platform that runs on top of other hardware-based platforms.

The Java platform has two components:

The Java Virtual Machine (Java VM)
The Java Application Programming Interface (Java API)

You’ve already been introduced to the Java VM. It’s the base for the Java platform and is ported onto various hardware-based platforms.

The Java API is a large collection of ready-made software components that provide many useful capabilities, such as graphical user interface (GUI) widgets. The Java API is grouped into libraries of related classes and interfaces; these libraries are known as packages. The next section, What Can Java Technology Do? Highlights what functionality some of the packages in the Java API provide.

The following figure depicts a program that’s running on the Java platform. As the figure shows, the Java API and the virtual machine insulate the program from the hardware.

Native code is code that after you compile it, the compiled code runs on a specific hardware platform. As a platform-independent environment, the Java platform can be a bit slower than native code. However, smart compilers, well-tuned interpreters, and just-in-time byte code compilers can bring performance close to that of native code without threatening portability.

6.3 WHAT CAN JAVA TECHNOLOGY DO?

The most common types of programs written in the Java programming language are applets and applications. If you’ve surfed the Web, you’re probably already familiar with applets. An applet is a program that adheres to certain conventions that allow it to run within a Java-enabled browser.

However, the Java programming language is not just for writing cute, entertaining applets for the Web. The general-purpose, high-level Java programming language is also a powerful software platform. Using the generous API, you can write many types of programs.

An application is a standalone program that runs directly on the Java platform. A special kind of application known as a server serves and supports clients on a network. Examples of servers are Web servers, proxy servers, mail servers, and print servers. Another specialized program is a servlet.

A servlet can almost be thought of as an applet that runs on the server side. Java Servlets are a popular choice for building interactive web applications, replacing the use of CGI scripts. Servlets are similar to applets in that they are runtime extensions of applications. Instead of working in browsers, though, servlets run within Java Web servers, configuring or tailoring the server.

How does the API support all these kinds of programs? It does so with packages of software components that provides a wide range of functionality. Every full implementation of the Java platform gives you the following features:

The essentials: Objects, strings, threads, numbers, input and output, data structures, system properties, date and time, and so on.
Applets: The set of conventions used by applets.
Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram Protocol) sockets, and IP (Internet Protocol) addresses.
Internationalization: Help for writing programs that can be localized for users worldwide. Programs can automatically adapt to specific locales and be displayed in the appropriate language.
Security: Both low level and high level, including electronic signatures, public and private key management, access control, and certificates.
Software components: Known as JavaBeans^TM, can plug into existing component architectures.
Object serialization: Allows lightweight persistence and communication via Remote Method Invocation (RMI).
Java Database Connectivity (JDBC^TM): Provides uniform access to a wide range of relational databases.

The Java platform also has APIs for 2D and 3D graphics, accessibility, servers, collaboration, telephony, speech, animation, and more. The following figure depicts what is included in the Java 2 SDK.

6.4 HOW WILL JAVA TECHNOLOGY CHANGE MY LIFE?

We can’t promise you fame, fortune, or even a job if you learn the Java programming language. Still, it is likely to make your programs better and requires less effort than other languages. We believe that Java technology will help you do the following:

Get started quickly: Although the Java programming language is a powerful object-oriented language, it’s easy to learn, especially for programmers already familiar with C or C++.
Write less code: Comparisons of program metrics (class counts, method counts, and so on) suggest that a program written in the Java programming language can be four times smaller than the same program in C++.
Write better code: The Java programming language encourages good coding practices, and its garbage collection helps you avoid memory leaks. Its object orientation, its JavaBeans component architecture, and its wide-ranging, easily extendible API let you reuse other people’s tested code and introduce fewer bugs.
Develop programs more quickly: Your development time may be as much as twice as fast versus writing the same program in C++. Why? You write fewer lines of code and it is a simpler programming language than C++.
Avoid platform dependencies with 100% Pure Java: You can keep your program portable by avoiding the use of libraries written in other languages. The 100% Pure Java^TMProduct Certification Program has a repository of historical process manuals, white papers, brochures, and similar materials online.
Write once, run anywhere: Because 100% Pure Java programs are compiled into machine-independent byte codes, they run consistently on any Java platform.
Distribute software more easily: You can upgrade applets easily from a central server. Applets take advantage of the feature of allowing new classes to be loaded “on the fly,” without recompiling the entire program.

6.5 ODBC:

Microsoft Open Database Connectivity (ODBC) is a standard programming interface for application developers and database systems providers. Before ODBC became a de facto standard for Windows programs to interface with database systems, programmers had to use proprietary languages for each database they wanted to connect to. Now, ODBC has made the choice of the database system almost irrelevant from a coding perspective, which is as it should be. Application developers have much more important things to worry about than the syntax that is needed to port their program from one database to another when business needs suddenly change.

Through the ODBC Administrator in Control Panel, you can specify the particular database that is associated with a data source that an ODBC application program is written to use. Think of an ODBC data source as a door with a name on it. Each door will lead you to a particular database. For example, the data source named Sales Figures might be a SQL Server database, whereas the Accounts Payable data source could refer to an Access database. The physical database referred to by a data source can reside anywhere on the LAN.

The ODBC system files are not installed on your system by Windows 95. Rather, they are installed when you setup a separate database application, such as SQL Server Client or Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a file called ODBCINST.DLL. It is also possible to administer your ODBC data sources through a stand-alone program called ODBCADM.EXE. There is a 16-bit and a 32-bit version of this program and each maintains a separate list of ODBC data sources.

From a programming perspective, the beauty of ODBC is that the application can be written to use the same set of function calls to interface with any data source, regardless of the database vendor. The source code of the application doesn’t change whether it talks to Oracle or SQL Server. We only mention these two as an example. There are ODBC drivers available for several dozen popular database systems. Even Excel spreadsheets and plain text files can be turned into data sources. The operating system uses the Registry information written by ODBC Administrator to determine which low-level ODBC drivers are needed to talk to the data source (such as the interface to Oracle or SQL Server). The loading of the ODBC drivers is transparent to the ODBC application program. In a client/server environment, the ODBC API even handles many of the network issues for the application programmer.

The advantages of this scheme are so numerous that you are probably thinking there must be some catch. The only disadvantage of ODBC is that it isn’t as efficient as talking directly to the native database interface. ODBC has had many detractors make the charge that it is too slow. Microsoft has always claimed that the critical factor in performance is the quality of the driver software that is used. In our humble opinion, this is true. The availability of good ODBC drivers has improved a great deal recently. And anyway, the criticism about performance is somewhat analogous to those who said that compilers would never match the speed of pure assembly language. Maybe not, but the compiler (or ODBC) gives you the opportunity to write cleaner programs, which means you finish sooner. Meanwhile, computers get faster every year.

6.6 JDBC:

In an effort to set an independent database standard API for Java; Sun Microsystems developed Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access mechanism that provides a consistent interface to a variety of RDBMSs. This consistent interface is achieved through the use of “plug-in” database connectivity modules, or drivers. If a database vendor wishes to have JDBC support, he or she must provide the driver for each platform that the database and Java run on.

To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC. As you discovered earlier in this chapter, ODBC has widespread support on a variety of platforms. Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market much faster than developing a completely new connectivity solution.

JDBC was announced in March of 1996. It was released for a 90 day public review that ended June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon after.

The remainder of this section will cover enough information about JDBC for you to know what it is about and how to use it effectively. This is by no means a complete overview of JDBC. That would fill an entire book.

6.7 JDBC Goals:

Few software packages are designed without goals in mind. JDBC is one that, because of its many goals, drove the development of the API. These goals, in conjunction with early reviewer feedback, have finalized the JDBC class library into a solid framework for building database applications in Java.

The goals that were set for JDBC are important. They will give you some insight as to why certain classes and functionalities behave the way they do. The eight design goals for JDBC are as follows:

SQL Level API

The designers felt that their main goal was to define a SQL interface for Java. Although not the lowest database interface level possible, it is at a low enough level for higher-level tools and APIs to be created. Conversely, it is at a high enough level for application programmers to use it confidently. Attaining this goal allows for future tool vendors to “generate” JDBC code and to hide many of JDBC’s complexities from the end user.

SQL Conformance

SQL syntax varies as you move from database vendor to database vendor. In an effort to support a wide variety of vendors, JDBC will allow any query statement to be passed through it to the underlying database driver. This allows the connectivity module to handle non-standard functionality in a manner that is suitable for its users.

JDBC must be implemental on top of common database interfaces

The JDBC SQL API must “sit” on top of other common SQL level APIs. This goal allows JDBC to use existing ODBC level drivers by the use of a software interface. This interface would translate JDBC calls to ODBC and vice versa.

Provide a Java interface that is consistent with the rest of the Java system

Because of Java’s acceptance in the user community thus far, the designers feel that they should not stray from the current design of the core Java system.

Keep it simple

This goal probably appears in all software design goal listings. JDBC is no exception. Sun felt that the design of JDBC should be very simple, allowing for only one method of completing a task per mechanism. Allowing duplicate functionality only serves to confuse the users of the API.

Use strong, static typing wherever possible

Strong typing allows for more error checking to be done at compile time; also, less error appear at runtime.

Keep the common cases simple

Because more often than not, the usual SQL calls used by the programmer are simple SELECT’s, INSERT’s, DELETE’s and UPDATE’s, these queries should be simple to perform with JDBC. However, more complex SQL statements should also be possible.

Finally we decided to precede the implementation using Java Networking.

And for dynamically updating the cache table we go for MS Access database.

Java ha two things: a programming language and a platform.

Java is a high-level programming language that is all of the following

Simple Architecture-neutral

Object-oriented Portable

Distributed High-performance

Interpreted Multithreaded

Robust Dynamic Secure

Java is also unusual in that each Java program is both compiled and interpreted. With a compile you translate a Java program into an intermediate language called Java byte codes the platform-independent code instruction is passed and run on the computer.

Compilation happens just once; interpretation occurs each time the program is executed. The figure illustrates how this works.

6.7 NETWORKING TCP/IP STACK:

The TCP/IP stack is shorter than the OSI one:

TCP is a connection-oriented protocol; UDP (User Datagram Protocol) is a connectionless protocol.

IP datagram’s:

The IP layer provides a connectionless and unreliable delivery system. It considers each datagram independently of the others. Any association between datagram must be supplied by the higher layers. The IP layer supplies a checksum that includes its own header. The header includes the source and destination addresses. The IP layer handles routing through an Internet. It is also responsible for breaking up large datagram into smaller ones for transmission and reassembling them at the other end.

UDP:

UDP is also connectionless and unreliable. What it adds to IP is a checksum for the contents of the datagram and port numbers. These are used to give a client/server model – see later.

TCP:

TCP supplies logic to give a reliable connection-oriented protocol above IP. It provides a virtual circuit that two processes can use to communicate.

Internet addresses

In order to use a service, you must be able to find it. The Internet uses an address scheme for machines so that they can be located. The address is a 32 bit integer which gives the IP address.

Network address:

Class A uses 8 bits for the network address with 24 bits left over for other addressing. Class B uses 16 bit network addressing. Class C uses 24 bit network addressing and class D uses all 32.

Subnet address:

Internally, the UNIX network is divided into sub networks. Building 11 is currently on one sub network and uses 10-bit addressing, allowing 1024 different hosts.

Host address:

8 bits are finally used for host addresses within our subnet. This places a limit of 256 machines that can be on the subnet.

Total address:

The 32 bit address is usually written as 4 integers separated by dots.

Port addresses

A service exists on a host, and is identified by its port. This is a 16 bit number. To send a message to a server, you send it to the port for that service of the host that it is running on. This is not location transparency! Certain of these ports are “well known”.

Sockets:

A socket is a data structure maintained by the system to handle network connections. A socket is created using the call socket. It returns an integer that is like a file descriptor. In fact, under Windows, this handle can be used with Read File and Write File functions.

#include <sys/types.h>

#include <sys/socket.h>

int socket(int family, int type, int protocol);

Here “family” will be AF_INET for IP communications, protocol will be zero, and type will depend on whether TCP or UDP is used. Two processes wishing to communicate over a network create a socket each. These are similar to two ends of a pipe – but the actual pipe does not yet exist.

6.8 JFREE CHART:

JFreeChart is a free 100% Java chart library that makes it easy for developers to display professional quality charts in their applications. JFreeChart’s extensive feature set includes:

A consistent and well-documented API, supporting a wide range of chart types;

A flexible design that is easy to extend, and targets both server-side and client-side applications;

Support for many output types, including Swing components, image files (including PNG and JPEG), and vector graphics file formats (including PDF, EPS and SVG);

JFreeChart is “open source” or, more specifically, free software. It is distributed under the terms of the GNU Lesser General Public Licence (LGPL), which permits use in proprietary applications.

6.8.1. Map Visualizations:

Charts showing values that relate to geographical areas. Some examples include: (a) population density in each state of the United States, (b) income per capita for each country in Europe, (c) life expectancy in each country of the world. The tasks in this project include: Sourcing freely redistributable vector outlines for the countries of the world, states/provinces in particular countries (USA in particular, but also other areas);

Creating an appropriate dataset interface (plus default implementation), a rendered, and integrating this with the existing XYPlot class in JFreeChart; Testing, documenting, testing some more, documenting some more.

6.8.2. Time Series Chart Interactivity

Implement a new (to JFreeChart) feature for interactive time series charts — to display a separate control that shows a small version of ALL the time series data, with a sliding “view” rectangle that allows you to select the subset of the time series data to display in the main chart.

6.8.3. Dashboards

There is currently a lot of interest in dashboard displays. Create a flexible dashboard mechanism that supports a subset of JFreeChart chart types (dials, pies, thermometers, bars, and lines/time series) that can be delivered easily via both Java Web Start and an applet.

6.8.4. Property Editors

The property editor mechanism in JFreeChart only handles a small subset of the properties that can be set for charts. Extend (or reimplement) this mechanism to provide greater end-user control over the appearance of the charts.

CHAPTER 7

APPENDIX

7.1 SAMPLE SOURCE CODE

7.2 SAMPLE OUTPUT

CHAPTER 8

8.0 CONCLUSION:

This paper analyzes the multicast capacity in mobile ad hoc networks with infrastructure support. Hybrid routing schemes are proposed to achieve reachable upper and lower bounds in each of the regimes. It is worth pointing out that our work generalizes results in previous works on hybrid networks, impact of mobility and multicast transmissions, as well as any combinations of the above. Our results are instructive in the design of real hybrid system combining cellular and ad hoc networks.

CHAPTER 9

9.0 REFERENCES:

[1] X.-Y. Li, ‘‘Multicast Capacity of Wireless Ad Hoc Networks,’’IEEE/ACM Trans. Netw., vol. 17, no. 3, pp. 950-961, June 2009.

[2] X.-Y. Li, Y. Liu, S. Li, and S. Tang, ‘‘Multicast Capacity of Wireless Ad Hoc Networks under Gaussian Channel Model,’’ IEEE/ACM Trans. Netw., vol. 18, no. 4, pp. 1145-1157, Aug. 2010.

[3] X. Mao, X.-Y. Li, and S. Tang, ‘‘Multicast Capacity for Hybrid Wireless Networks,’’ in Proc. ACM MobiHoc, Hong Kong, 2008, pp. 189-198.

[4] S. Tang, X. Mao, T. Jung, J. Han, X.-Y. Li, B. Xu, and C. Ma,‘‘Closing the Gap of Multicast Capacity for Hybrid Wireless Networks,’’ in Proc. ACM MobiHoc, Hilton Head, Italy, 2012,

pp. 135-144.

[5] W. Huang, X. Wang, and Q. Zhang, ‘‘Capacity Scaling in Mobile Wireless Ad Hoc Network with Infrastructure Support,’’ in Proc. IEEE ICDCS, Genoa, Italy, 2010, pp. 848-857.

[6] Y. Guo, F. Hong, Z. Jin, Y. He, Y. Feng, and Y. Liu,‘‘Perpendicular Intersection: Locating Wireless Sensors with Mobile Beacon,’’ IEEE Trans. Veh. Technol., vol. 59, no. 7, pp. 3501-

3509, Sept. 2010.

[7] C. Wang, X.-Y. Li, S. Tang, C. Jiang, and Y. Liu, ‘‘Capacity and Delay in Mobile Ad Hoc Networks under Gaussian Channel Model,’’ SIGMOBILEMobile Comput. Commun. Rev., vol. 14, no. 3, pp. 22-24, July 2010.