bca project documentation
BACK END - SQL SEVER 2007
MCA FINAL YEAR PROJECT Project SYNOPSIS OF ONLINE EXAMINATION SYSTEM
Final Report Of Online Examination System with full Documentation
SYNOPSIS of Project Sanatorium (Hospital Information System)
Click here to download Final report of project Hospital Information System
BCA Project 3# ONLINE AUCTION SYSTEM
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
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
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 (
ü 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
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
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
BIBLIOGRAPHY
IEEE NETWORKS (NOV-DEC 2004)
3.
www.draft-ietf-mobileip.txt
4.
IEEE SPECIAL ISSUE ON IP BASED
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.
bca project documentation
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 code) To
create an AVD with the AVD Manager:
19 comments:
For free Dot Net Projects, VB.NET Projects, ASP.Net Projects, MCA Projects, MBA Projects Download from Free Projects Download
we have provide the best ppc service.
ppc company in gurgaon
website designing company in Gurgaon
PPC company in Noida
seo company in gurgaon
PPC company in Mumbai
PPC company in Chandigarh
==============================================================================================
putlocker Nidhi Company Software is very user friendly & the system has a simple graphic user interface & features a logical distribution of functions. It is User-friendly ness which ensures hassle free usage at reasonable cost.
123movies Welcome to best Canadian Escort Directory. Find independent escorts girls and escorts agencies to fulfill your sexual desire.
This is really helpful for me, Now I am going to try to make IGNOU MCA Project.
asked about accounting software is Tally.
Download Real Driving 3D Mod
Management of EAS, having 2 decades of experience in the field of ISO certification and ISO training is delivered. ISO 9001 Lead Auditor Training is designed and delivered by EAS real time experienced auditors. IRCA ISO 9001 Auditor Certification | Virtual Online Lead Auditor Training | 5days | Online Exam | 95% success | Contact +91 9962590571 or visit our blog https://www.eascertification.com/iso-training/iso-9001-irca-lead-auditor-training/
digitechtricks.com
Find independent escorts girls and escorts
Thanks for sharing nice content, its really good for readers.
nmims mba project
Very nice information, Thanks for sharing
we are Best Hospital Software in India
Launch your own online food delivery application with our highly recommended script for Swiggy Clone that’s highly scalable and end-to-end customizable. The Swiggy Clone script is having great features and trustworthy backend platform for huge per sec transaction
zomato clone is a front-edge food delivery solution
that allows restaurants to start online services and achieve higher revenues.
Summer Training In Gurgaon
With easier and quicker corporate bookings, it improves the experience of business travel. We hope to offer an optimized corporate travel business process through the use of the Corporate Self Booking Tool, from the first search through the actual booking.
Excellent Blog, A must read.
backup and disaster recovery
Thank You for Posting such a great Post.
cloud computing services
Excellent Piece of Information. Thanks server migration to cloud
Thank you so much for sharing this article. Here is good information about IGNOU project assignment which very useful for all ignou students. Thanks for sharing this wonderful article.
NMIMS project
NMIMS Assignment
I wanted to express my gratitude for your insightful post. Also check the wyoming hunting laws
Post a Comment