FINCH12345678

Views:
 
     
 

Presentation Description

No description available.

Comments

By: aldifz (14 month(s) ago)

good information for me regarding the capabilities Wimax 802.16 standart to meet NG BB wireless, could you explain more detail about the roadmap to meet 4G requirement regards

Presentation Transcript

FINCH :

Fast Intra-Network and Cross-Layer Handover FINCH

1. INTRODUCTION :

1. INTRODUCTION mobility, there is no need to update MS’s care-of-address ( CoA ). THE IEEE 802.16 standard is a promising standard for next-generation broadband wireless access networks. It provides last mile solution and supports high-speed multimedia services. The IEEE 802.16e amendment enhances IEEE 802.16 with mobility support for users moving at vehicular speeds. Like other IEEE 802-series standards, 802.16 standardize physical (PHY) layer and Media Access Control (MAC) layer only. To build a complete system, higher layers are still necessary. One of the major objectives of WiMAX Forum, thus, is to promote conformance and interoperability of the IEEE 802.16 standards. The network reference model proposed by WiMAX Forum, The Access Service Network (ASN) provides radio access to WiMAX subscribers. It consists of one or more ASN Gateways (ASN GWs) and Base Stations (BSs). ASNs are connected by Connectivity Service Network (CSN), which provides Internet Protocol (IP) connectivity services. To support IP mobility, Mobile IP (MIP, IETF RFC 3344) is adopted by WiMAX Forum . The Home Agent (HA) of a Mobile Station (MS) is located in the CSN of the MS’s Home Network Service Provider (H-NSP). ASN GW supports the Foreign Agent (FA) functionality. For intra-ASN

2. Organization Profile :

2. Organization Profile COMPANY PROFILE At Axess Technologies (P) Ltd, We go beyond providing software solutions. We work with our client’s technologies and business changes that shape their competitive advantages. Founded in 2001, AXESS Technologies (P) Ltd. is a software and service provider that helps organizations deploy, manage, and support their business-critical software more effectively. Utilizing a combination of proprietary software, services and specialized expertise, AXESS Technologies (P) Ltd. helps mid-to-large enterprises, software companies and IT service providers improve consistency, speed, and transparency with service delivery at lower costs. AXESS Technologies (P) Ltd. helps companies avoid many of the delays, costs and risks associated with the distribution and support of software on desktops, servers and remote devices. Our automated solutions include rapid, touch-free deployments, ongoing software upgrades, fixes and security patches, technology asset inventory and tracking, software license optimization, application self-healing and policy management. At AXESS Technologies (P) Ltd, we go beyond providing software solutions. We work with our clients’ technologies and business processes that shape there competitive advantages.

.:

. About The People As a team we have the prowess to have a clear vision and realize it too. As a statistical evaluation, the team has more than 40,000 hours of expertise in providing real-time solutions in the fields of Embedded Systems, Control systems, Micro-Controllers, C Based Interfacing, Programmable Logic Controller, VLSI Design And Implementation, Networking With C, ++, java, client Server Technologies in Java,(J2EE\J2ME\EJB),VB & VC++, Oracle and operating system concepts with LINUX . Our Vision “ Dreaming a vision is possible and realizing it is our goal ”. Our Mission We have achieved this by creating and perfecting processes that are in par with the global standards and we deliver high quality, high value services, reliable and cost effective IT products to clients around the world.

3. SYSTEM ANALYSIS :

3. SYSTEM ANALYSIS Existing System: Real-time communication in a mobile wireless Internet environment it is essential to minimize the transient packet loss when the mobile is moving between different cells (subnets) within a domain. Network layer mobility management schemes have been proposed to provide optimized fast-handoff for multimedia streams during a client’s frequent movement within a domain. Application layer techniques to achieve fasthand off for real-time RTP/UDP based multimedia traffic in a SIP signaling environment. These techniques are based on standard SIP components such as user agent and proxy which usually participate to set up and tear down the multimedia sessions between the mobiles. Unlike network layer techniques, application layer techniques do not have to depend upon any additional components such as home agent and foreign agent. It thus provides a network access independent solution suitable for application service providers. Proposed System: The proposed FINCH is especially suitable for real-time services in frequent handover environment, which is important for future mobile WiMAX networks. In addition, FINCH is a generic protocol for other IEEE 802-series standards. This is especially beneficial for the integration of heterogeneous networks, for instance, the integration of WiMAX and WiFi networks.

4. SYSTEM STUDY :

4 . SYSTEM STUDY 4.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

. :

. 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. 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.

.:

. 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.

.:

.

.:

.

.:

.

6.Software Environment  :

6.Software Environment 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 tillustrates how his works

.:

. 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.

.:

. 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.

.:

. 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

.:

. 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. This encodes a network ID and more addressing. The network ID falls into various classes according to the size of the network 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.

7. SYSTEM TESTING   :

7. SYSTEM TESTING The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement. TYPES OF TESTS Unit testing Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.

.:

. Integration testing Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components . Functional test Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items: Valid Input : identified classes of valid input must be accepted. Invalid Input : identified classes of invalid input must be rejected. Functions : identified functions must be exercised. Output : identified classes of application outputs must be exercised. Systems/Procedures: interfacing systems or procedures must processes , and successive processes must be considered for be invoked. Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined

.:

. System Test System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points. White Box Testing White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level. Black Box Testing Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot “see” into it. The test provides inputs and responds to outputs without considering how the software works.

.:

. 7.1 Unit Testing: Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases. Test strategy and approach Field testing will be performed manually and functional tests will be written in detail. Test objectives All field entries must work properly. Pages must be activated from the identified link. The entry screen, messages and responses must not be delayed. Features to be tested Verify that the entries are of the correct format No duplicate entries should be allowed All links should take the user to the correct page.

.:

. 7.2 Integration Testing Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or – one step up – software applications at the company level – interact without error. Test Results: All the test cases mentioned above passed successfully. No defects encountered . 7.3 Acceptance Testing User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements . Test Results: All the test cases mentioned above passed successfully. No defects encountered.

8. HARDWARE SPECIFICATION :

8. HARDWARE SPECIFICATION Processor : Any Processor above 500 MHz. RAM : 128Mb. Hard Disk : 10 GB. Compact Disk : 650 Mb. Input device : Standard Keyboard and Mouse. Output device : VGA and High Resolution Monitor.

SOFTWARE SPECIFICATION :

SOFTWARE SPECIFICATION Operating System : Windows 2000 server Family. Techniques : JDK 1.5.

9.IMPLEMENTATION:

9.IMPLEMENTATION Implementation is the stage of the project when the theoretical design is turned out into a working system. Thus it can be considered to be the most critical stage in achieving a successful new system and in giving the user, confidence that the new system will work and be effective . The implementation stage involves careful planning, investigation of the existing system and it’s constraints on implementation, designing of methods to achieve changeover and evaluation of changeover methods . Modules : 1 . Networking module. 2 . Intradomain mobility management module 3 . cross-layer design module. 4 . Packet forwarding module. 5 . Location update module Module description : Networking module .

.:

. Client-server computing or networking is a distributed application architecture that partitions tasks or work loads between service providers (servers) and service requesters, called clients. Often clients and servers operate over a computer network on separate hardware. A server machine is a high-performance host that is running one or more server programs which share its resources with clients. A client does not share any of its resources, but requests a server's content or service function. Clients therefore initiate communication sessions with servers which await ( listen to) incoming requests.The client-server characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services . Intradomain mobility management module Network architecture for inter-domain mobility and intradomain mobility, in which a domain may be configured in many different ways, such as a bus network, a ring network, a star network, a tree network, and so forth. There are different network components including routers, and bridges. The functionality of the network components can be either like an L3 router or an L2 bridge. The mobility management and packet routing within the domain are done by replacing the necessary routing table and bridging table with a Forwarding Table (FT ).

.:

. Cross-layer design module Fast Intra-Network and Cross-layer Handover (FINCH), for intradomain mobility, which can achieve fast HO, especially for real-time services. FINCH limits frequent HOs within CSN. It cooperates with MIP, which serves as the inter-domain mobility management protocol. FINCH intends to localize location update to reduce the HO latency in MIP. It also reduces end-to-end latency because packets are delivered in a shorter path than that in MIP. In addition, FINCH is a cross-layer protocol, which also considers link layer. Thus, FINCH can further improve the performance. The proposed FINCH is especially suitable for real-time services in frequent HO environment. In addition, paging extension is designed to conserve the energy of MS and reduce the signaling overhead for location update . Packet forwarding module They are capable of processing IP packets. If a BS does not support IP routing, we assume that there is an Access Router (AR) behind the BS to handle IP packet routing. Remember that Table 1 represents the FT in BS 1 depicts that any IP packet arriving at BS 1 and bound for MS 1, as identified by its IP address is not forwarded to any other node. The IP packet is transmitted directly over a port . Location update module we derive the location update cost of the proposed FINCH. When an MS enters a new CSN, it should perform intradomain registration, which is combined with the MIP registration. Therefore, when traversing i cells from the _ th cell, the MS will perform registrations. Moreover, the location update of intradomain mobility traverses from the new BS to the original BS.

10. CONCLUSION :

10. CONCLUSION The problem is even exaggerated for real-time services, which require very fast HOs in mobile WiMAX networks. In this paper, we propose to use MIP in mobile WiMAX for interdomain (inter-CSN) mobility management only. We propose a fast HO protocol, FINCH, for intradomain (intra-CSN) mobility management. The protocol is discussed with examples. The analytical models and extensive simulations show that the proposed FINCH can support fast and efficient link layer and intradomain HOs. Because of the cross-layered design, comparing with other intradomain mobility management protocols, the proposed FINCH reduces location update cost and overall cost.

11. BIBLIOGRAPHY :

11. BIBLIOGRAPHY Good Teachers are worth more than thousand books, we have them in Our Department References Made From: 1. Professional Java Network Programming 2. Java Complete Reference Sites Referred: http://java.sun.com http://www.sourcefordgde.com http://www.networkcomputing.com/