ISP Automation

Note: Please Scroll Down to See the Download Link.

ABSTRACT

An Internet Service provider, or ISP, is a company that provides its customers with access to the Internet. Customers may connect to their ISP through dialup (telephone), broadband (including DSL, ISDN and cable modem services), or wireless connections. There are countless national and regional ISPS.

The purpose of project ’ISP AUTOMATION” is to automate an interface where in all the complaints, which are encountered by the customers, are to be entered, and the entire project is based on the activities of ISP companies.

Basically for any ISP company they will be having DIAL-UP and WEB-HOSTING as two Departments. DIAL-UP dept of the ISP Company will totally concentrates on the DIAL-UP packages, which are requested by the customers, and WEB-HOSTING dept is for WebPages concept. After the websites is registered in the server of the ISP, the total maintenance of the websites will be taken care by that particular company itself.

So, as part of the maintenance of the websites if a tiny sort of errors is occurred while browsing the websites, the customers will launch complaints to the ISP companies.

So, in order to maintain and keep track of all complaints, which are raised by the customers, we (Developers) have to design an interface in which all the complaints pertaining to customer’s website will be entered.

Responsibilities of the ISP companies after designing the interface:

·Accepting the complaints from DIAL-UP customers and storing the actions taken towards solving the problem.

·Generating reports on the status of the complaint

INTRODUCTION:

The analysis of the Internet is not sufficient anymore if it is solely based on the link state between routes (i.e. internet topology analysis). There are two main reasons. First, the Internet is becoming an integrated service network. More and more services are being introduced that require a better-than-best-effort network service quality, that means, in addition to the connectivity analysis, the performance of routes through the network has to be checked and maintained. Second, the requirement of Internet business has to be considered. The Internet has proliferated to a network that is trading products and services, worth several billions of dollars. In order to expand such trade, it is Internet services.

As more and more corporations, small business, government and private organizations educational institutions, consumers, and individuals rely on the internet to conduct business, engage in commercial activities, and simply communicates, the pressure applied by these users on this network to meet their performance and reliability demands also increases. This pressure is exacerbated by the deployment of high-speed access technologies; this pressure is exacerbated by the deployment of high-speed access technologies, such as cable modems and ADSL. When these demands are coupled with observations that the Internet is emerging as critical infrastructure and its contribution to economic output id significant, it is clear that the performance of the Internet is a critical issue. The Internet continued viability is closely tied to its ability to support the application that uses it. If the performance degrades or reliability

becomes questionable, the user experience will suffer. When the degradation is server enough-although the specific ramifications will vary with the individual users and application- the end result will be the same: the application will not be used, and the benefits will be lost.

Collecting and analyzing measurement data can understand Internet performance. In XIWT, a measurement architecture, measurement methodology, and common set of metrics were proposed for assessing, monitoring negotiating, and testing compliance for service quality (between an internet service provider (is The remainder of this article is organized as fallows) and its customers). The members of the cross industry working team Internet performance working team have undertaken a measurement initiative, based in the proposed architecture to collect a comprehensive set of data.

The analysis of the Internet is not sufficient anymore if it is solely based in the link state between routes (i.e. internet topology analysis) there are two main reasons. First, the Internet is becoming an integrated service network, more and more services are being introduced that requite a better-than-best-effort network service quality. That means in addition to the connectivity analysis the performance of routes through the network has to be checked and maintained. Second, the requirements of Internet business have to be considered .the Internet has proliferated to a network that is trading products and services, worth several billion dollars. In order to expand such trade, it is necessary to have an infrastructure in place, which facilitates such business transactions, information

providers have to a mean to communicate their needs to network provides, which transmit the information on their networks to the consumer will be satisfied with the delivered service.

Examining the business relationships between some Internet companies, it becomes obvious that companies are already teaming out in order to deal with these problems. For example, exodus specializes in data center services and reliable backbone services, helping other Internet companies to lower the risk of downtimes of their online information services. Another example is akamai that supports content provender’s to speed up the content delivery to their consumers.

In order to address these business needs, an understanding of the business models of Internet companies is necessary. That means, beside the analysis of the Internet companies as well as the values proposition of services is essential.

Greenstein stated in his work that the value proposition chain for electrical commerce has not settled yet. Companies ate still using different strategies for approaching similar commercial opportunities. Greenstein illustrated this situation by looking at the ISP market. He classified the ISPs into four groups:                       

Access service,

Backbone service,

Communication service, and

Consulting service.

Lakelin, Martin, and Sherwood give another ISP classification. They classified ISPs according to the size (i.e. IT service, telecommunication service, new callable service). However, both approaches ate not detailed enough to express all the different ISP business models.

Therefore, we introduced a reference models that helps to describe business models and business relations between Internet service providers. Based in that reference model, the place of Internet companies can be used help to future business requirements

A stakeholder on the Internet is defined as an abstract entity that could take on one or more roles and run them as a business.

The role of a stakeholder in the Internet can be classified according to different criteria. At the highest level of abstraction, the criterion is the position of the stakeholder in a business transaction. The business transaction is defined as the delivery of a service, which may or may not be free. Applying that, two roles of stakeholder can be identified:

Consumer: a consumer (also named customer) uses a set of services provided by one or more service providers. A consumer might be a person or a corporation.

Service provider: the stakeholder in this role will provide services for consumers. The type of service and the duration of the service might vary widely. The service may or may not necessarily use the Internet.’

According to this classification, a Consumer can also be in the service provider role, by reselling the service purchased. Similarly, a service provider can be in more than one role. It also might be that a stakeholder takes on a certain role in one business relationship and does not in another.

 In order to distinguish more details, we classify the stakeholders according to the type of service provide or consume. We suggest introducing two service layers reflection two main types of services: the Infrastructure layer and the Internet service layer.

Internet service layer

The stakeholders of the Internet service layer are characterized by providing and consuming Internet services. An Internet service is defined as a service can be providing on the Internet. At this level of abstraction, the Internet service can be a network service as well as an information service. According to the definition if this layer, we determine the roles that a stakeholder of the Internet service.

In order to be able to describe the business relationship between information service, connectivity service providers, and end-user, a definition of roles within each of these groups of stakeholder is necessary.

Connectivity service provider

The connectivity device can be classified according to the functionality of the IP network within the Internet. Therefore, we can distinguish four types of connectivity service providers:

End –user network provider:

The stakeholder in this role can be the end user itself or a corporation. The end-user is responsible for the network or uses the network of a corporation he belongs to

Access service provider:

An access service provider covers the ‘last mile’ between the end-user and the backbone, utilizing copper lines, fiber lines, or radio technologies. The DSL provider and the local telephone companies that provide the telephone line for connecting to the service providers are mobile service providers or wire-less service providers.

Backbone service provider:            

A backbone service provider connects access providers to its high network. Examples for backbone providers are AT&T, British Telecom. Etc.

Data center provider:

The role of this stakeholder is to provide a secure facility to information provider, guaranteeing high reliability and availability of their servers and high-

speed connectivity to backbone providers. Example of this king of service provider is Exodus and Akamai.

Information service provider

Information service providers can be classified according to the kind of information they deliver. We distinguish five different roles that a stakeholder can take on:

Application service provider:

The service of an application service provider comprises the lease of usage time of software applications service provider comprises the lease time of software applications they own. The application software provider takes care of maintenance and management of the software. Examples of such applications are SAP and File maker.

Provision the service they. The way stakeholders run their roles are indifferent to the reference model.

Internet protocols:

The Internet protocols are the world’s most popular open-system protocol suit because they can used to communicate across any set of interconnected for LAN and WAN communications. The Internet protocols consist of a suit of communication protocol; of which the best known is the Transmission control protocol (TCP) and the Internet protocol (IP). The Internet protocol suit not only

 includes lower-layer protocols, but it also specifies common applications such as electronic mail, terminal emulation, and file transfer.

Internet protocols were first developed in the mid -1970’s when the advanced research projects agency became interested in establishing a packet-switched network that would facilitate communication between dissimilar systems at research institutions.

TCP/IP later was included with Berkeley Software Distribution (BSD) UNIX and has since become the foundation on which the Internet and the World Wide Web (WWW) are based.

Fallowing are the Internet protocols packet fields.

  • Version – indicates the version of IP currently used.
  • IP Header Length (IHL) - indicates the data gram header in 32-bit words.
  • Type –of –service –specifies how an upper-layer protocol would like a current data gram to be handled, and assigns data gram various levels of importance.
  • Total Length-specifies the length, in bytes, of the entire IP packet, including the data and header.
  • Identification-contains an integer that identifies the current data gram. This field is used to help piece together data gram fragments.
  • Flags – consists of a 3-bit field of which the two low-order bits control fragmentation. The low-order bits specify whether the packet can be
  • fragmented. The middle bit specifies whether the packet is the last fragment in a series of fragmented packets. The third or high-order is not used.
  • Fragment offset-indicates the position of the fragment data relative to the beginning of the data in the original data gram, which allows the destination IP process to properly reconstruct the original data gram.
  • Time-to-Live- maintain counters that gradually decrement down to zero, at which Point the data gram is discarded. This packet after IP processing is complete.
  • Protocol – indicates which upper-layer protocol receives incoming packets after IP processing is complete.
  • Header Checksum-helps ensure IP header integrity.
  • Source Address-specifying the sending node.
  • Destination Address-specifies the receiving node.

Click here to download ISP Automation source code