Network Planning Principles

7/27/2019 Network Planning Principles

1/42

Network Planning Principles

For discussion and adaptation !!!


2/42

Objective

The main objective of the this document is to lay downhigh level service, applications, technical and economicframeworks which have to be followed during thedevelopment of the network during the TEP period.

Much of the framework principles are the derivatives ofthe RFP, the national growth and transformation plan,accepted strategies in the industry and lessons learned inthe last vendor financing program.

All planners involved in the planning of the build up oftelecom infrastructure shall use this framework as a blueprint for detailed planning activities.


3/42

TEP Main Objectives (RFP)

Extending the GSM geographic coverage to

85% to reach coverage to the.

..(This has to be detailed from the RFP and

further discussion from further requirements)


4/42

Principles

Network planning activities should evolve with the properevolution of the network, the services, the technologies, themarket and the government requirement. These evolutionsimply a wider set of options to implement a network than in

the past and as a consequence, the importance of carefulplanning and analysis for alternatives have larger impact onthe network capabilities today in order to assure the neededcapacities, the associated quality of service and the requiredinvestments.

There shall be no costly over-investment nor bad utilization ofalready earlier made investments, and at the same timeensures fluent migration of the services for the considerableamount of existing subscribers.


5/42

Principles

The inherent layering structure of the network and relatedtechnologies together with the complexity of the overall networkimplies that the network planning has to be performed also bylayers, sub-networks and technologies.

By Layers in a vertical dimension following the client-server relation(one layer is supported in the layer below and provides resourcesfor the layer up) as indicated: Physical, Transmission,Routing/Switching, and Applications/Services/Control.

By Segments or splitting of the end to end communication into subareas as customer premises, access, core national, coreinternational

By Technologies or underlying technique as FO, DWDM, SDH, MetroEthernet, PTN, ATM, IP, GSM, 3G, etc.....


6/42

Network Architecture Principles

Layering and segmenting are the main principles for building thearchitecture of the new network.

The architecture defined in the last vendor financing project shallbe revised in light of the convergence and technologydevelopments.

Convergence has been tried to be fully applied in the bearerbackbone transmission network. The new network architectureshall as far as possible and wherever possible, advocateconvergence and infrastructure sharing in all layers.

The most feasible candidate for convergence is the new backhaul(aggregation) network in the new network architecture.

A new Infrastructure layer is added this time to be planned in anintegrated way.


7/42

Network Architecture (2007)

IP/MPLS Backbone Network

BSCBSC

MGW

MGWAGW

TGW

OSS

SERVICE

LAYER

CONTROL

LAYER

BEARER

LAYER

ACCESS

LAYER

CDMA GSM/WCDMA

MSAN

TGW

International

Network

Existing PSTN &

GSM

Network

Internet

NOC & BSS


8/42

Proposed Layers in the New Architecture

1. OSS/BSS Layer

2. Service Layer

3. Control Layer4. Backbone layer

5. Backhaul Layer

6. Access layer7. Infrastructure layer

Functions of Layers Reference points for planning

and design of the network

Boundaries for achieving the

convergence and infrastructuresharing issues

Framework for resource

planning

Framework for the organizationof project implementation

Framework for vendor

allocation.


9/42

Proposed Network Architecture

IP/MPLS Backbone Network

BSC BSC

OSS

SERVICE

LAYER

CONTROL

LAYER

BACKBONE

LAYER

ACCESS

LAYER

CDMA/EVDO GSM/WCDMA

MSAN/METRO

Existing

Legacy Network

Internet

NOC & BSS

BACKHAUL

LAYER

INFRASTRUCTURE

LAYER

Tower & Foundation

Backhaul (Aggregation) Network

IP/MPLS, SDH,DWDM, Metro Ethernet

MSTP/PTN/OTN

International

Network


10/42

OSS/BSS Layer

This layer is responsible for all end to endnetwork management functions irrespectiveof the layer, technology, network building

block, vendor involved; Standardization is achieved through the north

bound interface visible to all layers;

Convergence ofIT platforms, OS anddatabases is required at this layer.

There shall be one system vendor in this layer.


11/42

Service Layer

This layer involve all applications and services related issues of the NextGeneration Networks. The abstract representation of the functional grouping

in the service layer include:

the service control functions including service user profile functions;

and

the application support functions and service support functions.Service layer functions and networks include:

Billing and Customer Care

SMS gateway

VMS gateway

One vendor is recommended for each application service in this layer

Convergence ofIT platforms, OS and databases is required at this layer.


12/42

Control Layer

The control


13/42


14/42

Core Network Planning Principles

GSM/UMTS networks are built in a hierarchical manner withindependent regional areas with access networks, each onecontrolled by an MSC.

In small PLMNs the MSCs are connected in a meshed network.However, as PLMN grow large the backbone network is divided into

a transit layer and a regional MSC layer. In order to simplify routing and traffic prediction, a ring topology

can be implemented in the transit layer. It is also recommendedthat all incoming and out going traffic be in the transit layer. Thisenables the operator to choose the most cost-effective solution interms of far-end drop or near-end drop.

Each regional MSC should be connected to at least two transit layernodes. This is called dual homing and it enables them to have fullprotection or to have load sharing. The most common option issomething in between.


15/42

Node Determination Factors

Capacity factor, i.e. when will their capacity run out ? Where should smallnodes be located in the network?

O&M factor, i.e. does it cost more to have many small-capacity nodescompared to having a few large ones?

Network robustness, i.e. would the network be more robust with manymore nodes rather than a few large ones?

Transmission efficiency, i.e. is it more efficient to have concentrated largenodes rather than many smaller ones?

Spare parts handling, the practical issues with holding spare parts indifferent places and the management of spare parts.

Other costs, such as the cost of new sites against co-location. Placing

many small nodes in the network would entail more site costs, especially ifthey are to be spread out geographically. Co-location must be considered.

Would the network topology of one, which consists of a few large nodes orone, that has many small nodes be more flexible for expansion?


16/42

Network Planning Process (1)Network Planning is one of the sub-processes that are included in the

Network Design for the Mobile Systems.

Scope of the Network Planning is determined during the Start-Up andInformation Gathering sub-process. The approved SolutionSpecification is the main output from Network Planning and is theinput to next activity in the Network Design, that is Detailed NetworkDesign


17/42

Network Planning Process (2)The Network Planning sub-process serves the following purposes:

Identify, at a high level, the network equipment requiredto

carry the required services.

Define topology and architecture of the network.

Anticipate network securityissues.

Define the roadmap for network evolution.

Provide key network elements for budgeting purposes and a

preliminary equipment list.

Identifies high-level impacts on existing / future network

systems.

Provides an input to help identify impact of business systems.

Provides an input to the Detailed Network Design sub-process.


18/42

Network Planning Process (Inputs)

Each work package included in the NetworkPlanning sub-process requires different types ofinputs at various stages of the network planning

process. However, high-level inputs are: Customers business plan

Network information

Subscriber information

Detailed inputs will be discussed in the relevantsub-process.


19/42


20/42

Network Planning Work Packages

The Network Planning sub-process consists of a number of workpackages. Each work package has its own inputs, outputs and

dependencies.

Outputs from one work

package may be used as

input to another work

package, or be used as

output to the Network

Planning sub-processprocess itself.


21/42

Network Planning Work PackagesFollowing work packages are included in the Network Planning:

Network Baseline/Review and evaluation Services and Traffic Planning

Security Solution

Migration/Expansion Planning

Core Network Architecture Solution

Circuit-Switched Network Solution

Packet-Switched Network Solution

Signaling Network Solution

Interconnection Planning

Transport Planes Solutions (IP and TDM Networks)

Synchronization Network Solution

Requirements on transmission

Transmission Network Solution

Node Dimensioning

Verification Audit

Network Evolution Planning


22/42

Network Baseline/Review/EvaluationIf the network requires expansion, it is necessary to understand thecurrent network capability and capacity.For an established 2G operator, it is vital that the existing network befully understood by the network planner. Obviously, equally vital is afull understanding of the short and medium term plans, which are inplace for the introduction of new services and network infrastructure.

To this end, a network baseline study is necessary.Depending on the requirements, the network will be studied in termsof:

Network architecture and topology

Network capacity

Network traffic Node configuration and performance

In addition customer-specific network design rules and guidelinesshould be captured and understood.


23/42

Services and Traffic PlanningServices Modeling

The objective of services modeling is to calculate the payload requirements,

upon which network dimensioning is based. It requires the following inputs:

Applications (web browsing, email, voice, FTP, etc.)

Services (voicemail, internet banking, web surfing, horoscope, etc.)

User profiles per service type

Quality of service Busy hours for each type of service

Service distribution and penetration

Service areas

Service profiles for each service area

Customer profiles

The services model will be used for services demand forecasting, and sensitivity

analysis. Changes in marketing plans to the number of services offered, or the

number of customers forecast, can be quickly re-calculated so that the network

plan can be updated, and impacts on the existing network can be determined.


24/42

Services and Traffic PlanningTraffic Modeling

The purpose of traffic modeling is to forecast traffic demand in order to

establish network requirements. The process consists of:

Traffic analysis (distribution and dispersion)

Network traffic modeling

Network traffic forecasting

Traffic distribution / dispersion

Traffic analysis involves the determination of user behavior, call MHT, BHCA,

busy hours in the day, user mobility related procedures such as handover per

subscriber and location update frequency, SMS events, and so on. Traffic

origin and destination(dispersion) for each type of call case or service must

also be determined. It allows the traffic planner to establish traffic flow in

the network, and is used for traffic forecasting. Traffic volume distribution is

estimated for the purpose of network topology and connectivity network

planning. The traffic model is especially useful for traffic sensitivity analysis.


25/42

Services and Traffic Planning (Inputs)

The modeling above shows processes with respect to both internal and external

inputs.Internal

Internal inputs are those that can be obtained from studies, outputs from

calculations and network statistics. Examples of internal inputs are:

Default parameters from applications and mobility models

Customer profiles

Number of RNCs as dimensioned

Traffic at each RNC

External

External inputs are those coming from the operator. These are: Service Application profile

Customer forecast and distribution

Customer profiles

Services offered

.


26/42

Traffic Planning (Detailed Inputs)The objectives of the Traffic Planning work package are to determine traffic

volume and flows across the network. Traffic planning generally starts withInformation gathering and can extends into network planning, if assumptionsneed to be made. Some of the inputs are:

Business Plan (list of services)

Services plan, profiles and penetration

Subscribers forecast & distribution

Subscriber profile

Network coverage information and Radio Network evolution

Traffic growth forecast and distribution

Traffic profiles

Signaling capacity towards other nodes

Number of nodes to interface RAN requirements

O&M, Billing requirements

Requirements Specification


27/42

Services and Traffic Planning (Outputs)

The output from this process also feeds into the next process along the chain

as seen in Figure of the planning overview process. The main outputs are: Services payload matrix

Traffic distribution

Solution Specification containing Traffic Plan

Services PayloadThe services payload allows the planner to arrive at the total data payload

requirements in each region and areas (sub-regions) in the network.

It also gives the planner the design criteria to apply in network design such

as quality and bandwidth. The criteria can be classified as types of services,

such as Real Time, or Non Real Time.Traffic Distribution

Traffic distribution is an important criterion for dimensioning nodes, links

and transmission requirements.


28/42

Security Solutions

Inputs

Traffic and Services Plan

Traffic forecast from otherexternal networks (data, voice)

Traffic distribution matrix (2G -3G, 3G - external networks)

Points of Interconnect

Interface requirements

Roaming requirements

Customer security requirementsand business objectives

Security recommendations from3GPP, 3GPP2 and GSMA

Outputs

Zone definitions

Inter-zone connections and policy

decision points

Filter and firewall criteria

Equipment access security issues

Management access

Boarder elements

The objectives of the Security Solution work package are to produce a clear

strategy for the implementation of a secure network.


29/42

Migration/Expansion Planning

Inputs

Current network topology and

architecture Operational constraints

Business plan

Product roadmaps and plans

Core Network architecture

solution

Outputs

Core Network architecture

solution

CS user plane solution

PS user plane solution

Signaling Network solution

Interconnection planning

Transport plane solutions

Synchronization Network solution

The objective of Migration/Expansion Planning work package is to cover all

aspects of Network planning for the successful migration from an operators

current network architecture and topology to that planned architecture andtopology.


30/42


31/42


32/42

Circuit Switched Network Solution

Inputs

Requirement Specification

Traffic plan

Target network baseline

Call cases and expected signaling

load

Current network baseline

Customer forecast and service

penetration

Network architecture and

topology

Outputs

The outputs of this work package are

Solution Specification containing

Circuit-Switched Network Solution

and Input to preliminary equipment

list

Circuit-Switched Network Solution includes CS User plane and CS Call Control

& Mobility Management of the Control Layer.


33/42


34/42

Signaling Network Solution

Inputs

Traffic plan

Target signaling network baseline(capacity and configuration)

Signaling Point Code allocation

and naming policy

Call cases (for each service

introduced) and expectedsignaling load

Customer forecast and service

penetration


Outputs

Signaling network plan

Signaling network Architecture and topology

Signaling network requirements

(capacity, interface requirements,

etc) specification

The objectives of Signaling Network Solution work package are to produce a

signaling network architecture and topology that will form the basis forsignaling network development and subsequent design

l


35/42

Interconnection Planning

Inputs

Traffic plan

Traffic forecast from otherexternal networks (data, voice)

Traffic distribution matrix (2G -

3G, 3G - external networks)

Points of Interconnect


Roaming requirements


Outputs

Interconnect plan

Interconnect traffic forecast(internal and external)


Interconnect network diagram

Interconnect Requirements

Specification

The objectives of the Interconnection Planning work package are to produce a

high level Interconnection plan that will allow a design to be specified thatwill satisfy the interconnection arrangements between carriers.


36/42


37/42

R i T i i


38/42

Requirement on Transmission

Inputs

Requirement Specification

Network baseline

Existing transmission network

CS network solution

PS network solution

TDM network solution

IP network solution

ATM network solution

FR network solution

Outputs

Output of this work package is

Solution Specification containing

Requirements on transmission

The objective of Requirements on Transmission work package is to identify

the requirements placed on the transmission network by the transport planes

of the Core Network.

T i i N k S l i


39/42

Transmission Network Solution

Inputs

Core Network design overview

Radio Network design report

Traffic forecast

Existing transmission network

Topology plan

Requirements specification

Outputs

Equipment list

Node configuration layout Network design layout

Solution Specification

Transmission Network Solution work package involves determination of the

physical layer design, including the architecture, topology, link capacity, and

protection and investment cost of the network..


40/42


41/42

N t k E l ti Pl i


42/42

Network Evolution Planning

Inputs

High-level network plans

(Convergence of other network,e.g. GPRS, PBN/PCN, GSM)

Product roadmap

Customer forecast and future

requirements

Services and traffic forecast Network baseline


Upgrade plan

Outputs

Network evolution phases with

timeframe

Network capacity

Capability and technical/network

proposals

The objectives of Network Evolution Planning work package are to develop a

plan to evolve the target network to future technologies within a suitable

timeframe.

Network Planning Principles

Documents

Transcript of Network Planning Principles