Building an Access Network for Triple-Play Services

This final project was made for the Broadband department of TeliaSonera. This project gives an overview on how internet service provider might build an access network so that they can offer triple-play services. It also gives information on what equipment is needed and what is required from the access, aggregation and edge networks. The project starts by describing the triple-play service. Then it moves on to optical fiber cables, the network technology and network architecture. At the end of the project there is an example of the process and construction of the access network. It will give an overview of the total process and problems that a network planner might face during the planning phase of the project. It will give some indication on how one area is built from the start to finish. The conclusion of the project presents some points that must be taken into consideration when building an access network. The building of an access network has to be divided to a time span of eight to ten years, where one year is one phase in the project. One phase is divided into three parts; Selecting the areas and targets, Planning the areas and targets, and Documentation. The example area gives indication on the planning of an area. It is almost impossible to connect all targets at the same time. This means that the service provider has to complete the construction in two or three parts. The area is considered to be complete when more than 80% of the real estates have fiber.

Building distributed high availability system

Today’s commercial web sites are under heavy user load and they are expected to be operational and available at all times. Distributed system architectures have been developed to provide a scalable and failure tolerant high availability platform for these web based services. The focus on this thesis was to specify and implement resilient and scalable locally distributed high availability system architecture for a web based service. Theory part concentrates on the fundamental characteristics of distributed systems and presents common scalable high availability server architectures that are used in web based services. In the practical part of the thesis the implemented new system architecture is explained. Practical part also includes two different test cases that were done to test the system's performance capacity.

Benefits and Limitations of Service Oriented Architecture

In this thesis I examine Service Oriented Architecture (SOA) considering both its positive and negative qualities for business organizations and IT. In SOA, services are loosely coupled and invoked through standard interfaces to enable business process independence from the underlying technology. As an architecture, SOA brings the key benefit of service reuse that may mean anything from simple application reuse to taking advantage of entire business processes across enterprises. SOA also promises interoperability especially by the Web services standards that enable platform independency. Cost efficiency is mainly a result of the savings in IT maintenance and reduced development costs. The most severe limitations of SOA are performance implications and security issues, but the applicability of SOA is also limited. Additional disadvantages of a service oriented approach include problems in data management and complexity questions, and the lack of agreement about SOA and its twofold nature as a business as well as technology approach leads to problematic interpretation of the available information. In this thesis I find the benefits and limitations of SOA for the purpose described above and propose that companies need to consider the decision to implement SOA carefully to determine whether the benefits will outdo the costs in the individual case.