project blog responsive ads

FREE DOWNLOAD MANAGEMENT SYSTEM PROJECT REPORT WITH SOURCE CODE IN ASP.NET JAVA AND PHP FOR IGNOU

Free download management system project documentation with JAVA, PHP AND ASP.NET source code. In all project report you will get introduction and objective of the project, system analysis, feasibility study, project planning, DFD diagram, system design, database design, complete project coding, and ER diagram of the project. These project reports and synopsis are useful for BCA, MCA BSC CS, MSC IT B.TECH, M.TECH and BE computer science last year students IGNOU, SMU university final year projects

Sponsored Links

Saturday, December 14, 2013

bca projects free download with documentation

BCA projects free download with documentation




BCA PROJECT # 2- Hospital Information System
FRONT END - VB6.0
BACK END - SQL SEVER 2000

FRONTEND - C # AND .NET FRAMEWORK 

BACKEND - SQL SERVER 2008

SYNOPSIS OF PROJECT  ONLINE AUCTION SYSTEM

FINAL REPORT WITH FULL DOCUMENTATION and SOURCE CODE  OF PROJECT  ONLINE AUCTION SYSTEM


Emerging wireless technology 

                                            ABSTRACT

 

New and increasingly advanced data services are driving up wireless traffic, which is being further boosted by growth in voice applications in advanced market segments as the migration from fixed to mobile voice continues. This is already putting pressure on some networks and may be leading to difficulties in maintaining acceptable levels of service to subscribers.

For the past few decades the lower band width applications are growing but the growth of broad band data applications is slow. Hence we require technology which helps in the growth of the broad band data applications. WiMAX is such a technology which helps in point-to-multipoint broadband wireless access with out the need of direct line of sight connectivity with base station.

This paper explains about the WiMAX technology, its additional features in physical layer and MAC layer and the benefits of each feature.

This paper focuses on the major technical comparisons (like QOS and coverage) between WiMAX and other technologies. It also explains about the ability of the WiMAX to provide efficient service in multipath environment.

   

 II. Introduction:

For the past couple decades, low-bandwidth applications such as downloading ring tones and SMS are experiencing sharp growth, but the growth of broadband data applications such as email and downloading/ uploading files with a laptop computer or PDA has been slow. The demand for broadband access continues to escalate worldwide and lower-bandwidth wire line methods have failed to satisfy the need for higher bandwidth integrated data and voice services. WiMAX is radio technology that promises two-way Internet access at several megabits per second with ranges of several miles. It is believed that the technology can challenge DSL (Digital Subscriber Line) and cable broadband services because it offers similar speeds but is less expensive to set up. The intention for WiMAX is to provide fixed, nomadic, portable and, eventually, Mobile wireless broadband connectivity without the need for Direct line-of-sight with a base station.

III.What is wimax?

WiMAX is an acronym that stands for “Worldwide Interoperability for Microwave Access”. IEEE 802.16 is working group number 16 of IEEE 802, specializing in point-to-multipoint broadband wireless access. It also is known as WiMAX. There are at least four 802.16 standards: 802.16, 802.16a, 802.16-2004 (802.16), and 802.16e.

WiMAX does not conflict with WiFi but actually complements it.  WiMAX is a wireless metropolitan area network (MAN) technology that will connect IEEE 802.11 (WiFi) hotspots to the Internet and provide a wireless extension to cable and DSL for last km broadband access. IEEE 802.16 provides up to 50 km of linear   service   area range and allows user’s connectivity without a direct line of sight to a base station. The technology also provides shared data rates up to 70 Mbit/s.

The portable version of WiMAX, IEEE 802.16 utilizes Orthogonal Frequency Division Multiplexing Access (OFDM/OFDMA) where the spectrum is divided into many sub-carriers. Each sub-carrier then uses QPSK or QAM for modulation. WiMAX standard relies mainly on spectrum in the 2 to 11 GHz range. The WiMAX specification improves upon many of the limitations of the WiFi standard by providing increased bandwidth and stronger encryption

For years, the wildly successful 802.11 x or WiFi wireless LAN technology has been used in BWA applications. When the WLAN technology was examined closely, it was evident that the overall design and feature set available was not well suited for outdoor Broadband wireless access (BWA) applications. WiMAX is suited for both indoor and outdoor BWA; hence it solves the major problem.


In reviewing the standard, the technical details and features that differentiate WiMAX certified equipment from WiFi or other technologies can best be illustrated by focusing on the two layers addressed in the standard, the physical (PHY) and the media access control (MAC) layer design.

   III. a) WIMAX PHY Layer

 The first version of the 802.16 standard released addressed Line-of-Sight (LOS) environments at high frequency bands operating in the 10-66 GHz range, whereas the recently adopted amendment, the 802.16a standard, is designed for systems operating in bands between 2 GHz and 11 GHz. The significant difference between these two frequency bands lies in the ability to support Non-Line -of-Sight (NLOS) operation in the lower frequencies, something that is not possible in higher bands. Consequently, the 802.16a amendment to the standard opened up the opportunity for major changes to the PHY layer specifications specifically to address the needs of the 2-11 GHz bands. This is achieved through the introduction of three new PHY-layer specifications (a new Single Carrier PHY, a 256 point FFT OFDM PHY, and a 2048 point FFT OFDMA PHY);

  Some of the other PHY layer features of 802.16a that are instrumental in giving this technology the power to deliver robust performance in a broad range of channel environments are; flexible channel widths, adaptive burst profiles, forward error correction with concatenated Reed-Solomon and convolutional encoding, optional AAS (advanced antenna systems) to improve range/capacity, DFS (dynamic frequency selection)-which helps in minimizing interference, and STC (space-time coding) to enhance performance in fading environments through spatial diversity. Table 1 gives a high level overview of some of the PHY layer features of the IEEE 802.16a standard.


 

  b) IEEE 802.16a MAC Layer

 

The 802.16a standard uses a slotted TDMA protocol scheduled by the base station to allocate capacity to subscribers in a point-to-multipoint network topology. By tarting with a TDMA approach with intelligent scheduling, WiMAX systems will be able to deliver not only high speed data with SLAs, but latency sensitive services such as voice and video or database access are also supported. The standard delivers QoS beyond mere prioritization, a technique that is very limited in effectiveness as traffic load and the number of subscriber’s increases. The MAC layer in WiMAX certified systems has also been designed to address the harsh physical layer environment where interference, fast fading and other phenomena are prevalent in outdoor operation.

IV.WiMAX Scalability:

At the PHY layer the standard supports flexible RF channel bandwidths and reuse of these channels (frequency reuse) as a way to increase cell capacity as the network grows. The standard also specifies support for automatic transmit power control and channel quality measurements as additional PHY layer tools to support cell planning/deployment and efficient spectrum use. Operators can re-allocate spectrum through sectorization and cell splitting as the number of subscribers grows.

In the MAC layer, the CSMA/CA foundation of 802.11, basically a wireless Ethernet protocol, scales about as well as does Ethernet. That is to say - poorly. Just as in an Ethernet LAN, more users results in a geometric reduction of throughput, so does the CSMA/CA MAC for WLANs. In contrast the MAC layer in the 802.16 standard has been designed to scale from one up to 100's of users within one RF channel, a feat the 802.11 MAC was never designed for and is incapable of supporting.

a) Coverage:

The BWA standard is designed for optimal performance in all types of propagation environments, including LOS, near LOS and NLOS environments, and delivers reliable robust performance even in cases where extreme link pathologies have been introduced. The robust OFDM waveform supports high spectral efficiency over ranges from 2 to 40 kilometers with up to 70 Mbps in a single RF channel. Advanced topologies (mesh networks) and antenna techniques (beam-forming, STC, antenna diversity) can be employed to improve coverage even further. These advanced techniques can also be used to increase spectral efficiency, capacity, reuse, and average and peak throughput per RF channel. In addition, not all OFDM is the same. The OFDM designed for BWA has in it the ability to support longer range transmissions and the multi-path or reflections encountered. In contrast, WLANs and 802.11 systems have at their core either a basic CDMA approach or use OFDM with a much different design, and have as a requirement low power consumption limiting the range. OFDM in the WLAN was created with the vision of the systems covering tens and maybe a few hundreds of meters versus 802.16 which is designed for higher power and an OFDM approach that supports deployments in the tens of kilometers.

b) Quality of service:

The 802.16a MAC relies on a Grant/Request protocol for access to the medium and it supports differentiated service The protocol employs TDM data streams on the DL (downlink) and TDMA on the UL (uplink), with the hooks for a centralized scheduler to support delay-sensitive services like voice and video. By assuring collision-free data access to the channel, the 16a MAC improves total system throughput and bandwidth efficiency, in comparison with contention-based access techniques like the CSMA-CA protocol used in WLANs. The 16a MAC also assures bounded delay on the data. The TDM/TDMA access technique also ensures easier support for multicast and broadcast services. With a CSMA/CA approach at its core, WLANs in their current implementation will never be able to deliver the QoS of a BWA, 802.16 systems.

 

V. ROLE OF ‘OFDMA’ IN MULTIPATH ENIRONMENT:

Technologies using DSSS (802.11b, CDMA) and other wide band technologies are very susceptible to multipath fading, since the delay time can easily exceed the symbol duration, which causes the symbols to completely overlap (ISI). The use of several parallel sub-carriers for OFDMA enables much longer symbol duration, which makes the signal more robust to multipath time dispersion

a). Multipath: Frequency Selective Fading

                   This type of fading affects certain frequencies of a transmission and can result in deep fading at certain frequencies. One reason this occurs is because of the wide band nature of the signals. When a signal is reflected off a surface, different frequencies will reflect in different ways. In Figure below, both CDMA (left) and OFDMA (right) experience selective fading near the center of the band. With optimal channel coding and interleaving, these errors can be corrected. CDMA tries to overcome this by spreading the signal out and then equalizing the whole signal. OFDMA is therefore much more resilient to frequency selective fading when compared to CDMA.


VI. OFDMA with Adaptive Modulation and Coding (AMC):

Both W-CDMA (HSDPA) and OFDM utilize Quadrature Phase Shift Keying (QPSK) and Quadrature Amplitude Modulation (QAM). It should be noted here that for WCDMA, AMC is only used on the downlink, since the uplink still relies on WCDMA which uses QPSK but not QAM. Modulation and coding rates can be changed to achieve higher throughput, but higher order modulation will require better Signal to Noise Ratio. Figure illustrates how higher order modulations like QAM 64 are used closer to the base station, while lower order modulations like QPSK are used to extend the range of the base station . Performance results conducted for one of the 3GPP Working Groups [2], show that while OFDM is able to achieve the maximum throughput of 9.6 Mbps (16QAM), WCDMA does not exceed 3 Mbps. From these results, it appears that even higher discrepancy may be found when utilizing higher modulation and code rates to yield even higher throughput for OFDM.

                   Adaptive Modulation and Coding (AMC) in a multipath environment may give OFDMA further advantages since the flexibility to change the modulation for specific sub-channels allows you to optimize at the frequency level. Another alternative would be to assign those sub channels to a different user who may have better channel conditions for that particular sub-channel. This could allow users to concentrate transmit power on specific sub-channels, resulting in improvements to the uplink budget and providing greater range. This technique is known as Space Division Multiple Access (SDMA).

In Figure below, you can see how sub-channels could be chosen depending on the received signal strength. The sub-channels on which the user is experiencing significant fading are avoided and power is concentrated on channels with better channel conditions. The signals on the top indicate the received signal strength, while the bottom part of the figure indicates which sub-carriers are then chosen for each signal.

With OFDMA, the client device could choose sub channels based on geographical locations with the potential of eliminating the impact of deep fades. CDMA-based technologies utilize the same frequency band regardless of where the user is.

 

VII.ADVANCED RADIO TECHNIQUES:

a) Transmit and receive diversity schemes:

Transmit and Receive Diversity schemes are used to take advantage of multipath and reflected signals that occur in NLOS environments. By utilizing multiple antennas (transmit and/or receive), fading, interference and path loss can be reduced. The OFDMA transmit diversity option uses space time coding. For receive diversity, techniques such as maximum ratio combining (MRC) take advantage of two separate receive paths.


   b)  Smart Antenna Technology:

Adaptive antenna systems (AAS) are an optional part of the 802.16 standard. AAS equipped base stations can create beams that can be steered, focusing the transmit energy to achieve greater range as shown in the figure. When receiving, they can focus in the particular direction of the receiver. This helps eliminate unwanted interference from other locations.

  VIII. Conclusion:

Thus WiMAX systems for portable/nomadic use will have better performance, interference rejection, multipath tolerance, high data quality of service support (data oriented MAC, symmetric link) and lower future equipment costs i.e., low chipset complexity, high spectral efficiencies. And hence WiMAX can complement existing and emerging 3G mobile and wireline networks, and play a significant role in helping service provides deliver converged service offerings

IX. BIBLIOGRAPHY:

Ø Understanding “WiMAX”- Joe Laslo & Michael gartenberg

Ø  www.intel.com/ebusiness/pdf/wireless/intel

Ø  www.intel.com/netcomms/technologies/wimax

Ø  P. S. Henry, “Wi-Fi: What’s next?” IEEE Communications Magazine

Ø  WWW.WiMaxeed.COM.

Ø  WiMAX Handbook –Frank ohrtman 


You can download BCA, MCA and BSC computer science project from given below links

INSURANCE MANAGEMENT SYSTEM PROJECT REPORT


UNIVERSITY MANAGEMENT SYSTEM PROJECT REPORT


TRANSPORT MANAGEMENT SYSTEM PROJECT REPORT


EMPLOYEE MANAGEMENT SYSTEM PROJECT REPORT


SCHOOL MANAGEMENT SYSTEM PROJECT REPORT


AIRLINE RESERVATION SYSTEM PROJECT REPORT

AUTOMOBILE INVENTORY MANAGEMENT SYSTEM PROJECT

GENERAL STORE BILLING SYSTEM PROJECT

CUSTOMER CARE MANAGEMENT SYSTEM PROJECT IN ASP NET

HOSPITAL MANAGEMENT SYSTEM PROJECT

COURSE MANAGEMENT SYSTEMS PROJECT

KNOWLEDGE OUTSOURCING SYSTEM PROJECT REPORT

RECRUITMENT MANAGEMENT SYSTEM PROJECT

PASSPORT AUTOMATION AND MONITORING SYSTEM PROJECT REPORT

WEBINAR WEB BASED SEMINAR SYSTEM PROJECT REPORT

MCA Project  4# BCA MCA Bsc B tech CS information technology final year project




COURIER SERVICE MANAGEMENT SYSTEM PROJECT REPORT

Synopsis- Available- Click on the Project link above to review
Final report- Available - Click on the Project link to review
BCA Project Can be submitted by - BE, BCA, MCA, B TECH Computer Science Final Year students. IGNOU BCA, IGNOU MCA, SMU BCA, SMU MCA, B.Tech / B.E in Computer Science or Information technology, MTech, MS, BSC-IT as final year project.


7.7.4 Creating a run configuration:
The bca projects free download with documentation run configuration specifies the project to run, the Activity to start, the emulator options to use, and so on. When you first run a project as an Android Application, ADT will automatically create a run configuration. The bca projects free download with documentation default run configuration will launch the default project Activity and use automatic target mode for device selection (with no preferred AVD). If the default settings don't suit your project, you can customize the launch configuration or even create a new.
To create or modify a launch configuration, follow these steps as appropriate for your Eclipse version:
Open The bca projects free download with documentation run configuration manager.
In Eclipse 3.3 (Europa), select Run > Open Run Dialog (or Open Debug Dialog)
In Eclipse 3.4 (Ganymede), select Run > Run Configurations (or Debug Configurations)
Expand the Android Application item and create a new configuration or open an existing one.
To create a new configuration:
Select Android Application and click the New launch configuration icon above the list (or, right-click Android Application and click New).
Enter a Name for your configuration.

bca projects free download with documentation

In the Android tab, browse and select The bca projects free download with documentation project you'd like to run with the configuration.
To open an existing configuration, select the configuration name from The bca projects free download with documentation list nested below Android Application.
Adjust your desired launch configuration settings.
In the Target tab, consider whether you'd like to use Manual or Automatic mode when selecting an AVD to run your application. See the following section on Computer Science Final Project
You can specify any emulator options to The bca projects free download with documentation Additional Emulator Command Line Options field. For example, you could add -scale 96dpi to scale the AVD's screen to an accurate size, based on the dpi of your computer monitor. For a full list of emulator options, see the   Free download MCA projects in asp.net document.
7.8 Designing:

 Designing for performance:  Free download MCA projects in vb.net

An Android application should be fast. Well, it's probably more accurate to say that it should be efficient. That is, it should execute as efficiently as possible in The bca projects free download with documentation mobile device environment, with its limited computing power and data storage, smaller screen, and constrained battery life.
As you develop your application, keep in mind that, while the application may perform well enough in your emulator, running on your dual-core development computer, it will not perform that well when run a mobile device — even the most powerful mobile device can't match the capabilities of a typical desktop system. For that reason, you should strive to write efficient code, to ensure The bca projects free download with documentation best possible performance on a variety of mobile devices.
Generally speaking, writing fast or efficient code means keeping memory allocations to a minimum, writing tight code, and avoiding certain language and programming idioms that can subtly cripple performance. In object-oriented terms, most of this work takes place at the method level, on the order of actual lines of code, loops, and so on.

bca projects free download with documentation


Introduction:
There are two basic rules for resource-constrained systems:
Don't do work that you don't need to do.
Don't allocate memory if you can avoid it.
All the tips below follow from these two basic tenets.
Some would argue that much of The bca projects free download with documentation advice on this page amounts to "premature optimization." While it's true that  Free download MCA projects in C#.net micro-optimizations sometimes make it harder to develop efficient data structures and algorithms, on embedded devices like handsets you often simply have no choice. For instance, if you bring your assumptions about VM performance on desktop machines to Android, you're quite likely to write code that exhausts system memory. This will bring your application to a crawl — let alone what it will do to other programs running on the system!
That's why these guidelines are important. Android's success depends on the user experience that your applications provide, and that user experience depends in part on whether your code is responsive and snappy, or slow and aggravating. Since all our Free download MCA projects in java applications will run on The bca projects free download with documentation same devices, we're all in this together, in a way. Think of this document as like the rules of the road you had to learn when you got your driver's license: things run smoothly when everybody follows them, but when you don't, you get your car smashed up.
Before we get down to brass tacks, a brief observation: nearly all issues described below are valid whether or not the VM features a JIT compiler. If I have two methods that accomplish The bca projects free download with documentation same thing, and the interpreted execution of foo() is faster than bar(), then the compiled version of foo() will probably be as fast or faster than compiled bar(). It is unwise to rely on a compiler to "save" you and make your code fast enough.

Avoid creating objects:  Free download MCA projects in PHP

Object creation is never free. A generational GC with per-thread allocation pools for temporary objects can make allocation cheaper, but allocating memory is always more expensive than not allocating memory.
If you allocate objects in a user interface loop, you will force a periodic garbage collection, creating little "hiccups" in the user experience.
Thus, you should avoid creating object instances you don't need to. Some examples of things that can help:
When extracting strings from a set of input data, try to return a substring of The bca projects free download with documentation original data, instead of creating a copy. You will create a new String object, but it will share the char[] with the data.
If you have a method returning a string, and you know that its result will always be appended to a StringBuffer anyway, change your signature and implementation so that the function does The bca projects free download with documentation append directly, instead of creating a short-lived temporary object.
A somewhat more radical idea is to slice up multidimensional arrays into parallel single one-dimension arrays:

bca projects free download with documentation free download MCA projects in ASP.NET with complete source code

An array of ints is a much better than an array of Integers, but this also generalizes to the fact that two parallel arrays of ints are also a lot more efficient than an array of (int,int) objects. The same goes for any combination of primitive types.
If you need to implement a container that stores tuples of (Foo,Bar) objects, try to remember that two parallel Foo[] and Bar[] arrays are generally much better than a single array of custom (Foo,Bar) objects. (The exception to this, of course, is when you're designing an API for other code to access; in those cases, it's usually better to trade correct API design for a small hit in speed. But in your own internal code, you should try and be as efficient as possible.)
Generally speaking, avoid creating short-term temporary objects if you can. Fewer objects created mean less-frequent garbage collection, which has a direct impact on user experience.

bca project documentation

bca project documentation



BCA PROJECT # 2- Hospital Information System
FRONT END - VB6.0
BACK END - SQL SEVER 2000

FRONTEND - C # AND .NET FRAMEWORK 

BACKEND - SQL SERVER 2008

SYNOPSIS OF PROJECT  ONLINE AUCTION SYSTEM

FINAL REPORT WITH FULL DOCUMENTATION and SOURCE CODE  OF PROJECT  ONLINE AUCTION SYSTEM


Abstract

                                 

                                      This paper describes an architecture for differentiation of Quality of Service in heterogeneous wireless-wired networks. This architecture applies an “all-IP” paradigm, with embedded mobility of users. The architecture allows for multiple types of access networks, and enables user roaming between different operator domains. The overall 4G architecture discussed in this paper is IPv6-based, supporting seamless mobility between different access technologies. Mobility is a substantial problem in such environment, because inter-technology handovers have to be supported. In our case, we targeted Ethernet (802.3) for wired access; Wi-Fi (802.11b) for wireless LAN access; and W-CDMA - the radio interface of UMTS - for cellular access.The architecture is able to provide quality of service per-user and per-service An integrated service and resource management approach is presented based on the cooperative association between Quality of Service Brokers and Authentication, Authorisation, Accounting and Charging systems. The different phases of QoS-operation are discussed. The overall QoS concepts are presented with some relevant enhancements that address specifically voice services. In particular, EF simulations results are discussed in this context.

  

CONTENTS

1:INTRODUCTION

             1.1:WIRELESS COMMUNICATION

            

             1.2: GENERATIONS OF WIRELESS COMMUNICATION

 

2: AN ALL-IP 4G NETWORK ARCHITECTURE

 

3:PROVIDING QUALITY OF SERVICE

                         

           3.1: Service and Network Management in Mobile Networks

          

           3.2 :Implicit "Session" Signalling

 

4:END-TO-END QOS SUPPORT

                  

           4.1 :Registration and Authorisation

          

           4.2: Handover with QoS guarantees

         

           4.3: EF PHB resource provisioning

 

5:CONCLUSION

 

1:INTRODUCTION

 

             1.1 WIRELESS COMMUNICATION:

 

A wireless network is an infrastructure for communication “through the air”, in other words, no cables are needed to connect from one point to another. These connections can be used for speech, e-mail, surfing on the Web and transmission of audio and video. The most widespread use is mobile telephones. Wireless networks are also used for communication between computers. This note focuses on ways to set up wireless connections between computers. It gives a basic overview without becoming too technical. It will help to determine whether a wireless network might be a suitable solution. It also is a guide to more resources. Many links are to a document by Mike Jensen. The links used are examples; they are not preferred products.

 

           1.2 GENERATIONS OF WIRELESS COMMUNICATION:

 

1G: These first generation mobile systems were designed to offer a single service     that is speech.

 

2G: These second generation mobile systems were also designed primarily to offer speech with a limited capability to offer data at low rates.

 

3G: These third generation mobile systems are expected to offer high quality multimedia services and operative different environments. These systems are referred to as universal mobile telecommunication systems (UMTS) in Europe and international mobile telecommunication systems 2000(IMT2000) worldwide.

 

4G: This is user-driven, user controlled services and context aware applications. Compared to 3G ,4G has higher data rates and it has QOS which is the main criteria in 4G wireless commuication.

 

Availability of the network services anywhere, at anytime, can be one of the key factors that attract individuals and institutions to the new network infrastructures, stimulate the development of telecommunications, and propel economies. This bold idea has already made its way into the telecommunication community bringing new requirements for network design, and envisioning a change of the current model of providing services to customers. The emerging new communications paradigm assumes a user to be able to access services independently of her or his location, in an almost transparent way, with the terminal being able to pick the preferred access technology at current location (ad-hoc, wired, wireless LAN, or cellular), and move between technologies seamlessly i.e. without noticeable disruption. Unified, secure, multi-service, and multiple-operator network architectures are now being developed in a context commonly referenced to as networks Beyond-3G or, alternatively, 4G networks .

 

2 AN ALL-IP 4G NETWORK ARCHITECTURE:

 

The overall 4G architecture discussed in this paper is IPv6-based, supporting seamless mobility between different access technologies. Mobility is a substantial problem in such environment, because inter-technology handovers have to be supported. In our case, we targeted Ethernet (802.3) for wired access; Wi-Fi (802.11b) for wireless LAN access; and W-CDMA - the radio interface of UMTS - for cellular access (Fig. 1). With this diversity, mobility cannot be simply handled by the lower layers, but needs to be implemented at the network layer. An "IPv6-based" mechanism has to be used for interworking, and no technology-internal mechanisms for handover, neither on the wireless LAN nor on other technology, can be used. So, in fact no mobility mechanisms are supported in the W-CDMA cells, but instead the same IP protocol supports the movement between cells. Similarly, the 802.11 nodes are only in BSS modes, and will not create an ESS: IPv6 mobility will handle handover between cells. 1 The concepts that are presented in this paper have been developed and tested in controlled environments in the IST project Moby Dick [2] and are currently being refined.



 

This Figure depicts the conceptual network architecture, illustrating some of the handover possibilities in such network with a moving user. Four administrative domains are shown in the figure with different types of access technologies. Each administrative domain is managed by an AAAC system. At least one network access control entity, the QoS Broker, is required per domain. Due to the requirements of full service control by the provider, all the handovers are explicitly handled by the management infrastructure through IP-based protocols, even when they are intratechnology, such as between two different Access Points in 802.11, or between two different Radio Network Controllers in WCDMA. All network resources are managed by the network provider, while the user only controls its local network, terminal, and applications.

 

In Figure 1, the key entities are:

ü  A user - a person or company with a service level agreement (SLA) contracted with an operator for a specific set of services. Our architecture is concerned with user mobility, meaning that access is granted to users, not to specific terminals.

ü  A MT (Mobile Terminal) - a terminal from where the user accesses services. Our network concept supports terminal portability, which means that a terminal may be shared among several users, although not at the same time.

ü  AR (Access Router) - the point of attachment to the network, which takes the name of RG (Radio Gateway) - for wireless access (WCDMA or 802.11).

ü  PA (Paging Agent) - entity responsible for locating the MT when it is in "idle mode" while there are packets to be delivered to it [4].

 

ü  QoS Broker - entity responsible of managing one or more ARs/AGs, controlling user access and access rights according to the information provided by the AAAC System.

ü  AAAC System - the Authentication, Authorization, Accounting and Charging System, responsible for service level management (including accounting and charging). In this paper, for simplicity, metering entities are considered an integral part of this AAAC system.

ü  NMS (Network Management System) - the entity responsible for managing and guaranteeing availability of resources in the Core Network, and overall network management and control. This network is capable of supporting multiple functions:

ü  inter-operator information interchange for multiple-operator scenarios;

ü  confidentiality both of user traffic and of the network control information;

ü  mobility of users across multiple terminals;

ü  mobility of terminals across multiple technologies;

ü  QoS levels guaranties to traffic flows (aggregates), using, e.g. the EF Per Hop Behaviour (PHB);

ü  monitoring and measurement functions, to collect information about network and service usage;

 

3: PROVIDING QUALITY OF SERVICE

 

The design principle for QoS architecture was to have a structure which allows for a potentially scalable system that can maintain contracted levels of QoS. Eventually, especially if able to provide an equivalent to the Universal Telephone Service, it could possibly replace today's telecommunications networks. Therefore, no specific network services should be presumed nor precluded, though the architecture should be optimised for a representative set of network services. Also, no special charging models should be imposed by the AAAC system, and the overall architecture must be able to support very restrictive network resource usage. In terms of services, applications that use VoIP, video streaming, web, e-mail access and file transfer have completely different prerequisites, and the network should be able to differentiate their service. The scalability concerns favour a differentiated services (DiffServ) approach [5]. This approach is laid on theassumption to control the requests at the borders of the network, and that end-to-end QoS assurance is achieved by a concatenation of multiple managed entities. With such requirements, network resource control must be under the control of the network service provider. It has to be able to control every resource, and to grant or deny user and service access. This requirement calls for flexible and robust explicit connections admission control (CAC) mechanisms at the network edge, able to take fast decisionson user requests.

 

 

         3.1 Service and Network Management in Mobile Networks

 

Our approach for 4G networks and to service provisioning is based on the separation of service and network management entities. In our proposal we define a service layer, which has its own interoperation mechanisms across different administrative domains (and can be mapped to the service provider concept), and a network layer, which has its own interoperation mechanism between network domains. An administrative domain may be composed of one or more technology domains. Service definitions are handled inside administrative domains and service translation is done between administrative domains [6]. Each domain has an entity responsible for handling user service aspects (the AAAC system), and at least one entity handling the network resource management aspects at the access level (the QoS Broker). The AAAC system is the central point for Authentication, Authorization and Accounting. When a mobile user enters the network, the AAAC is supposed to authenticate him. Upon successful authentication, the AAAC sends to the QoS Broker the relevant QoS policy information based on the SLA of the user, derived from his profile. From then, it is assumed that the AAAC has delegated resource-related management tied to a particular user to the QoS Broker. However, two different network types have to be considered in terms of QoS:

     

    3.2 :Implicit "Session" Signalling

 

In this architecture, each network service being offered in the network is associated to a different DSCP code. This way, every packet has the information needed to the network entities to correctly forward, account, and differentiate service delivered to different packets. After registering (with the AAAC system) a user application can “signal” the intention of using a service by sending packets marked with appropriate DSCP. These packets are sent in a regular way in wired access networks, or over a shared uplink channel used for signalling in W-CDMA. This way of requesting services corresponds to implicit signalling, user-dependent, as the QoS Broker will be aware of the semantics of each DSCP code per each user (although typically there will be no variation on the meaning of DSCP codes between users). Thus QoS Broker has the relevant information for mapping user-service requests into network resources requirements and based on this information configures an access router.A novel concept of “session” is implemented: the concept of a “session” is here associated with the usage of specific network resources, and not explicitly with specific traffic micro-flows. This process is further detailed in section 4.

 



 

           3.3 Network services offer

 

Services will be ofered a the network operator independently on the user applications, but will be flexible enough to support user applications Each offered network service will be implemented with one of the three basic DiffServ per-hop behaviours (EF, AF, or BE), with associated bandwidth characteristics. Table 1 lists the network services used in the tests. The network services include support for voice communications (e.g. via S1) and data transfer services. Delay, delay jitter and packet loss rate are among the possible parameters to include in the future, but no specific control mechanisms for these parameters are currently used. The services may also be unidirectional or bi-directional. In fact, the QoS architecture can support any type of network service, where the only limit is the level of management complexity expressed in terms of complexity of interaction between the QoS Brokers, the AAAC systems and the AR that the network provider is willing to support.

4: END-TO-END QOS SUPPORT

 

Given the concepts described in section 3, the entities developed in the project can support end-to-end QoS, without explicit reservations at the setup time. Three distinct situations arise in the QoS architecture: i) registration, when a user may only use network resources after authentication and authorization, ii) service authorisation, when the user has to be authorised to use specific services; and iii) handover – when there is a need to re-allocate resources from one AR to another.



         4.1 :Registration and Authorisation

 

The Registration process (Figure 2) is initiated after a Care of Address (CoA) is acquired by the MT via stateless auto-configuration, avoiding Duplicate Address Detection (DAD) by using unique layer-2 identifiers [7] to create the Interface Identifier part of the IPv6 address. However, getting a CoA does not entitle the user to use resources, besides registration messages and emergency calls. The MT has to start the authentication process by exchanging the authentication information with the AAAC through the AR. Upon a successful authentication, the AAAC System will push the NVUP (network view of the User Profile) to both the QoS Broker and the MT, via the AR. Messages 1 to 4 on Figure 2 detail this process. The same picture shows how each network service is authorized (messages 5 to 8). The packets sent from the MT with a specific DSCP implicit signal the request of a particular service, such as a voice call (supported by network service S1, as in Table 1). If the requested service does not match any policy already set in the AR (that is, the user has not established a voice call before, e.g.), the QoS attendant/manager at the AR interacts with the QoS Broker that analyses the request and authorises the service or not, based on the User NVUP (Network View of the User Profile) and on the availability of resources. This authorisation corresponds to a configuration of the AR (via COPS [10]) with the appropriate policy for that user and that service (e.g. allowing the packets marked as “belonging” to voice call to go through, and

configuring the proper scheduler parameters, as we will see in section 4.3). After that, packets with authorised profile will be let into the network and non-conformant packets will restart the authorization process once more, or will be discarded.

 

          4.2: Handover with QoS guarantees

 

One of the difficult problems of IP mobility is assuring a constant level of QoS. User mobility is assured in our network by means of fast handover techniques in conjunction with context transfer between network elements (ARs - old and new – and QoS Brokers).

When the quality of the radio signal in the MT to the current AR (called “old AR”, AR1) drops, the terminal will start a handover procedure to a neighbouring AR (called “new AR”, AR2) with better signal and from which it has received a beacon signal with the network prefix advertisement. This handover has to be completed without user perception, when making a voice call, e.g.. For achieving this, the MT will build its new care-of-address and will start the handover negotiation through the current AR, while still maintaining its current traffic. This AR will forward the handover request to both the new AR and to the QoS Broker.



              

  4.3: EF PHB resource provisioning

 

Building an all-IP architecture based on a Differentiated Services introduces a problem of how to create per-domain services for transport of traffic aggregates with a given QoS. Per-domain services support data exchange by mixing traffic of different applications, therefore different aggregates are required to support delay-sensitive traffic, delay tolerant traffic, inelastic, elastic, as well as network maintenance traffic (e.g. SNMP, DNS, COPS, AAAC etc.). As applications generate traffic of different characteristics in terms of data rates, level of burstiness, packet size distribution and because the operator needs to protect the infrastructure against congestion, it is very important that aggregate scheduling will be accompanied by:

ü  per-user rate limitation performed in the ingress routers (ARs) based on user profile,

ü  dimensioning and configuration of network resources to allow for a wide range of user needs and services,

ü  resource management for edge-to-edge QoS.

                                



The basic evaluation criteria was the queuing delay and the delay jitter of EF PDB for flow S1. The SFQ algorithm exhibits the worst performance of all schedulers, especially for medium and high traffic loads on a link. A better performance exhibits the SFQ algorithm at a very low load, but it applies to average delays only. PRI, PRIs and WFQ algorithms produce comparable results. For the Moby Dick architecture we are now considering to recommend PRIs, due to its simplicity when compared to WFQ.



The PRIs limitation has yet another advantage – rate limitation does not have influence on traffic characteristics when traffic level remains within limits, and the limits can be dynamically changed without inducing abrupt delay shift. For WFQ and SFQ algorithms dynamic change of bandwidth assigned for service class changes the service rate for this class, and can cause a transient increase of delay jitter.

5 CONCLUSION:

We presented an architecture for supporting end-to-end QoS. This QoS architecture is able to support multi-service, multi-operator environments, handling complex multimedia services, with per user and per service differentiation, and integrating mobility and AAAC aspects. The main elements in our architecture are the MT, the AR and the QoS Brokers. We discussed the simple interoperation between these elements and depicted the overall QoS concept. With our approach, very little restrictions are imposed on the service offering. This architecture is currently being evolved for large testing in field trials across Madrid and Stuttgart. Being an architecture specially targeted to support real time communications over packet networks, the network elements configuration must be well dissected. The simulation study summarized in the paper was a valuable input to the QoS Broker implementation and policies design, providing simple heuristics to properly configure the access routers to achieve the best possible performance. The schedulers configuration on the core routers was also determined through the results of this simulation study. This architecture still has some shortcomings, though, mostly due to its diffserv orientation. Each domain has to implement its own plan for mapping between network service and a DSCP, and thus, for inter domain service provision, it is essential a service/DSCP mapping between neighbouring domains. Furthermore, an adequate middleware function is required in the MT, to optimally mark the packets generated by the applications and issue the proper service requests, which requires extensions in current protocol stacks.

BIBLIOGRAPHY

 

IEEE NETWORKS (NOV-DEC 2004)

 

1.      www.indiainfo.com

 

2.      www.mobyclick.org

 

3.      www.draft-ietf-mobileip.txt

 

4.      IEEE SPECIAL ISSUE ON IP BASED MOBILE TELECOMMUNICATIONS NETWORK (AUG 2000)

 

5.      www.cgarcia/articulos/artQOS

 

6.      delson.org/4g mobile/docs/4g_intro.htm

 

BCA MCA Bsc B tech CS information technology final year project




BCA Project Can be submitted by - BE, BCA, MCA, B TECH Computer Science Final Year students. IGNOU BCA, IGNOU MCA, SMU BCA, SMU MCA, B.Tech / B.E in Computer Science or Information technology, MTech, MS, BSC-IT as final year project.


7.7.1 Running your application:
Before you can run your application on the Android Emulator, you must create an Android Virtual Device (AVD). An AVD is a configuration that specifies the Android platform to be used on the emulator. You can read more in The bca project documentation  Free download MCA projects in VB,NET with complete source code document, but if you just want to get started, follow the simple guide below to create an AVD.
If you will be running your applications only on actual device hardware, you do not need an AVD — see Developing On a Device for information on running your applicaiton.



bca project documentation

7.7.2 Creating an AVD:
With ADT 0.9.3 and above, the Android SDK and AVD Manager provides a simple graphical interface for creating and managing AVDs. (If you're using ADT version 0.9.1 or older, you must use the android tool to create your AVDs—read The bca project documentation  AVD guide to Free download MCA MSc projects in C#.net with complete source codeTo create an AVD with the AVD Manager:
Select Window > Android SDK and AVD Manager, or click the Android SDK and AVD Manager icon (a black device) in the Eclipse toolbar.
In The bca project documentation  Virtual Devices panel, you'll see a list of existing AVDs. Click New to create a new AVD.
Fill in the details for the AVD.
Give it a name, a platform target, an SD card image (optional), and a skin (HVGA is default).
Click Create AVD.
Your AVD is now ready and you can close the AVD Manager. In The bca project documentation  next section, you'll see how the AVD is used when launching your application on an emulator.
For more information about AVDs, read the Free download MCA projects in JAVA with complete source code documentation.

bca project documentation  Free download MCA projects in PHP with  Complete source code,

7.7.3 Running your application:
Note: Before you can run your application, be sure that you have created an AVD with a target that satisfies your application's Build Target. If an AVD cannot be found that meets The bca project documentation  requirements of your Build Target, you will see a console error telling you so and the launch will be aborted.
To run (or debug) your application, select Run > Run (or Run > Debug) from the Eclipse main menu. The bca project documentation  ADT plugin will automatically create a default launch configuration for the project.
When you choose to run or debug your application, Eclipse will perform the following:
Compile The bca project documentation  project (if there have been changes since the last build).
Create a default launch configuration (if one does not already exist for the project).
Install and start The bca project documentation  application on an emulator or device (based on the Deployment Target defined by the run configuration).
By default, Android application run configurations use an "automatic target" mode for selecting a device target. For information on how automatic target mode selects a deployment target, see  Free download BSc CS IT projects in PHP,JAVA, ASP.NET with  source code  below.
If debugging, the application will start in The bca project documentation  "Waiting For Debugger" mode. Once the debugger is attached, Eclipse will open the Debug perspective.
To set or change the launch configuration used for your project, use The bca project documentation  launch configuration manager. See Free download MCA projects in ASP.NET with documentation for more projects


G+

Pages