Network planning

Siemens

Network planning

Contents
1 1.1 1.2 1.3 2 2.1 2.2 3 4 4.1 4.2 4.3 5 5.1 5.2 5.3 5.4 6 Network planning Overview SSS planning principles The planning process Network elements and network topology Network elements Network topology Traffic forecast Traffic models and traffic distribution Traffic and mobility data Obtaining the model parameters Traffic matrix Network structure, gateways and routing Network structure Gateways and routing Fixed Alternate Routing (FAR) with load sharing in the final route Optimized Dynamic Routing (ODR) Load check 3 4 6 8 11 12 14 17 21 22 26 28 31 32 34 38 40 43

MN1738EU02MN_0002
2004 Siemens AG

Siemens

Network planning

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Network planning

Fig. 1 Network planning

MN1738EU02MN_0002
2004 Siemens AG

Siemens

Network planning

1.1

Overview

The SSS planning is a functional block in the planning process for the entire GSM network. The requirements for the planning phase are determined in an initial planning step. A forecast is calculated for the next planning periods using a growth model based on the desired final configuration (maximum number of subscribers in the network). This data represents the initial requirements for network planning. The network is then implemented and installed. The following individual planning steps are performed: Specify the customer's requirements Determine demand; produce a forecast Plan the network Configure the network Install the network and take it into operation. This planning course deals with the calculation of the line network for user channels (voice, data, fax, etc.) and signaling links. Below are the other activities to be carried out as part of the network planning: Register all data for an existing network Infrastructure and civil works (buildings, power supply, antennae, cables, etc.) Project-specific planning rules (contractual agreements) Geographical information (maps, GPS survey) Technological selection of equipment for transport switching and TMN. Detailed planning of the individual components: Radio network planning Fixed network planning Transport planning Synchronization TMN concept Materials planning Negotiation of the interfaces to the PSTN and other networks Production of all planning documentation.

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Customer Request / Input

Demand and Service Forcast

Network Planning

Network Configuration

Order, Installation, Commisioning

Fig. 2 Basic planning steps

MN1738EU02MN_0002
2004 Siemens AG

Siemens

Network planning

1.2

SSS planning principles

A network operator requires precise knowledge of the geographical and economic structure of the country or region in which the GSM network is planned. The number of radio cells is derived from the subscriber density (number of mobile subscribers per square kilometer), which in turn yields the number of network elements (BSC's and MSC's) for the fixed network planning. A network is planned with the following steps: Produce the network topology Calculate the traffic matrix Plan interconnection and routing Dimension the network.

The trunk network planning team attempts using the SSS technology and by defining a suitable network structure with corresponding routing and dimensioning to satisfy all requirements for a network in the best way. The most crucial parameter in PSTN planning in the past was the minimization of investment costs while maintaining a specific grade of service for a given traffic matrix. Since the transport costs were the major cost factor for each connection, networks were designed using the shortest path principle. This led to increased intermeshing of the networks with increasing size of the individual network elements because more and more traffic relationships exceeded the minimum traffic value required for creating a high usage route. The result of this approach is highly intermeshed, complex networks with large, constantly rising overhead costs for monitoring, operation, maintenance and planning (operating costs). These networks are investment cost optimized for a particular traffic pattern. In the mobile communications sector, however, we need a network designed for alternating traffic patterns that offers a high degree of availability. In addition, today's networks are considerably more aligned towards optimization of the operating costs and greater flexibility to accommodate changes in traffic patterns or loads due to network element failures. It is accepted that investment costs for equipment may sometimes be greater than for PSTN but these costs can be quickly compensated by a reduction in operating costs.

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Investment Costs

Grade of Service

-Structure -Routing -Dimensioning

(Change in) Demand

Quality
Availibilty

Traffic
Traffic Distribution

Operating Costs
Network Evolution Interconnection PSTN / other PLMN

Fig. 3 Planning parameters

MN1738EU02MN_0002
2004 Siemens AG

Siemens

Network planning

1.3

The planning process

The following tasks have to be performed during SSS planning: Record the network data - Number of subscribers - Points of interconnection - Traffic forecast Produce a traffic model - Traffic value per mobile subscriber - Mobility of the subscribers - Usage of the services in the network (voice, data, text, fax, e-mail) Determine the network elements in the regions - Peak busy hour - Functionality of the network elements - Number of network elements Define the points of interconnection (gateways) - Gateway to the international PSTN - Gateway to the national PSTN - Gateway to other mobile networks Define the network architecture - Level 1: BSC MSC - Level 2: Transit and Gateway MSC's Calculate the traffic matrix - End-to-end traffic relationships - Service-specific traffic profiles Routing - Full intermeshing - Hierarchical routing Network dimensioning for - traffic channels - signaling links Configure the MSC internal components - SN, CP, (Loop-) LTG, DEC, IWU, OCANEQ, MTPY OMS configuration Evaluating Network costs -Investment costs - Operating costs

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Demand of Network Data Evaluation of Network Costs

Traffic Model

Configuration of OMS Number of Network Elements SSS Planing Network Dimensioning Points of Interconnection

Configuration of NEs

Traffic Routing

Network Architecture

End-To-End Traffic Matrix

Fig. 4 Planning steps

MN1738EU02MN_0002
2004 Siemens AG

Siemens

Network planning

10

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Network elements and network topology

System area

Location area Location area

SIEMENS SIEMENS

PLMN Country
MSC area
BSS

cell

cell

SIEMENS

SIEMENS

MSC area
cell BSS
SIEMENS SIEMENS

Location area
cell

BSS

MSC area

Location area

Location area
cell

Location area
SIEMENS SIEMENS

BSS cell

MSC area
BSS cell

cell

BSS cell
SIEMENS

cell
SIEMENS

cell

PLMN area 1
BSS cell cell

MSC area Location area

SIEMENS SIEMENS

BSS

MSC area

Location area

Location area
BSS cell cell cell BSS cell cell

PLMN area 2

Location area

Fig. 5 Network elements

MN1738EU02MN_0002
2004 Siemens AG

11

Siemens

Network planning

2.1

Network elements

We distinguish between the following subsystems: Radio Subsystem (RSS), divided into: - Base Station System (BSS) - Mobile Stations (MS) Switching Subsystem (SSS) Operation and Maintenance Subsystem (OMS) The specification of the number of necessary modules of network elements is the task of the hardware planning team. We will concentrate on the interface between the network elements and calculate the number of trunks for voice, data and signaling (control and short messages) along with other units for recorded announcements, interworking, etc. We divide these connections into three types: Traffic channels (voice and data for MS) Signaling links (CCS7) Operation and maintenance channels (X.25) Critical interfaces are often gateways to other networks because the timing of the planning process must be negotiated with the other network operators in these cases. The dimensioning and configuration of the signaling links are particularly important because the functionality of the overall network depends on the availability and loading capability of these control links. The data channels for the O&M system are used for operation and maintenance or for data transfer of charge and traffic measurement data. The terminals can be connected locally (for specific maintenance functions) or remotely via the packet network or PSTN / ISDN.

12

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Radio Subsystem RSS

Switching Subsystem SSS

MSC / VLR MS BTS BSC / TRAU BTS MSC / VLR MS BTS BSC / TRAU BTS HLR / AC

Service centers (SMS,VMS)

IN SCP

other networks WAP RAS

EIR

OMC-B / Radio-Commander

OMC-S / Switch-Commander

O&M Subsystem (OMS)

OMT-B

OMT-S

OMT-B

OMT-S

Fig. 6 Structure of D900 / D1800 PLMN

MN1738EU02MN_0002
2004 Siemens AG

13

Siemens

Network planning

2.2

Network topology

At the start of the network planning, the locations of the network elements and the possible transport paths between the nodes are selected. When defining the locations, network operators always first target the industrial centers, areas with the highest population densities or busy highway and road systems. They also attempt to achieve the greatest possible coverage (> 90%) if the economic conditions permit. The intermeshing of nodes (network structure, see chapter 5 for details) depends on the traffic flow between the locations and the distance between them. Full intermeshing makes sense only in small networks with about 4 MSC's as shown in Fig. 7. If the network is expanded (N MSC > 5), the introduction of a transit level is advisable because full intermeshing is not economical for the reasons already stated.

14

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

BSS PSTN MSC 3

PSTN MSC 4 BSS PSTN BSS

MSC 2 BSS

MSC 1 PSTN

Fig. 7 Network topology (non hierarchical)

MN1738EU02MN_0002
2004 Siemens AG

15

Siemens

Network planning

16

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Traffic forecast

MN1738EU02MN_0002
2004 Siemens AG

17

Siemens

Network planning

The growth of a network is influenced by different factors: Gross national product and economic growth of the regions Competitive conditions in the telecommunications market Technical configuration of the other network operators (fixed and mobile networks) Tariff structure in the fixed and mobile networks Introduction of new services and technologies. A traffic forecast is never fully correct but is still essential for long-term planning as otherwise the network planning can never be optimal. Rapid growth in the market may lead to bottleneck situations in telecommunication networks and therefore to customer complaints if appropriate network redesigns or expansions are not initiated in time. If the growth pattern is not too irregular there are reliable methods to estimate the number of subscribers in a telecommunications network. Suppose we have observed si subscribers in period ti, i = 1,,n. Our approach is to model the typical S-shape of the subscriber number graph by a function

s(t) =

s max 1 + e a + bt

where smax denotes the saturation limit (of subscribers) and a and b are model parameters. TIP To simplify the problem we assume that smax is known at this stage. Our goal is to estimate a and b such that the graph of s(t) fits well to our observed data (ti,si). To do this first notice that the transformed function

y(t) = ln(

s max 1) = a + bt s(t)

is linear and hence it makes sense to estimate a and b by performing a linear regression for the transformed data
(t i , ln( s max 1)) , i = 1,,n . si

With a tool like Excel the result is just a few clicks away The forecast must be continuously updated with the latest network values in order to respond promptly to the current market situation. Fig. 8 clearly shows that the growth rate quickly falls once the saturation limit of a network has been approached. These figures are particularly crucial for long-term planning of a network.

18

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Enter:
Existing

Calculated Forecast

INPUT: OUTPUT:
b

smax
3.000.000 a -0,5543323 1109,354324 s(t) = 1 / (1+exp(a+bt))

YEAR 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014

#subs

50.000 100.000 150.000 270.000 400.000 700.000 1.000.000 1.400.000 1.800.000

s(t) 368,44 641,32 1116,22 1942,56 3379,95 5878,83 10218,91 17744,08 30753,76 53132,00 91293,29 155417,84 260548,98 426141,61 671191,60 1002282,72 1398610,27 1809688,39 2177313,50 2464966,50 2667405,18 2799478,83 2881437,13 2930725,83 2959810,14 2976780,33 2986617,25 2992297,58 2995570,46 2997453,83

3.500.000

3.000.000

2.500.000

s(t)=
2.000.000

smax 1+ ea+bt

1.500.000

1.000.000

500.000

1985

1987

1989

1991

1993

1995

1997

1999

2001

2003

2005

2007

2009

2011

Year

Fig. 8 Subscriber forecast

2013

MN1738EU02MN_0002
2004 Siemens AG

19

Siemens

Network planning

20

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Traffic models and traffic distribution

MN1738EU02MN_0002
2004 Siemens AG

21

Siemens

Network planning

4.1

Traffic and mobility data

To calculate the network we need a set of planning parameters that are affected by the dynamic behavior of the mobile subscribers. When planning new networks and if no project-specific data exist we use a traffic model from a comparable region, keeping in mind that values from existing networks of course cannot fully represent the region to be planned. Once detailed measurement values from the network become available, a modified traffic model is always calculated for extensions to the network. The average values always refer to the busy hour i.e., an interval of 60 minutes with the highest traffic value is determined from the daily curve. This value is the basis for network dimensioning. Moreover the values of the reference model refer to the normal load situation, which identifies frequent busy operating conditions of the network for which user expectations should be met. High load condition on the other hand identifies not very frequently encountered operating conditions for which user service expectations would not necessarily be met, but for which the level of performance achieved should be high enough to avoid significant user dissatisfaction, spread of congestion, overload in the coordination processor (CP113) etc. For further details on this subject see ITU-T recommendation E.500 (11/98). The call behavior of the subscribers depends on many factors like tariff structure of the operator offered services e.g. Pre-paid service, WAP applications type of subscriber, i.e. business or private existence and quality of PSTN infrastructure law and order (e.g. in some countries it is forbidden to use mobile phones in public transportation) etc. In general two kind of models can be distinguished: traffic model and mobility model. In both models the figures refer to an average subscriber. The traffic model gives information about the call activity in a busy hour, the mean holding time per call, the call split of MTC, MOC, MMC and their success rate.

22

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Traffic Data I Traffic per MS Number of BHCA per MS and BH MHT per call (successful and unsuccessful) CAs MORTR (including MMCs) thereof successful thereof unsuccessful no traffic channel / engaged thereof unsuccessful no answer CAs MICTR (including MMCs) thereof successful thereof unsuccessful detached / no paging response thereof unsuccessful no answer CAs MTM (originating at the MSC under consideration) thereof MSC internal thereof to other MSCs 10% 50% 50% 40% 55% 31.5% 13.5% 20 mErl 1.2 60s 60% 65% 21% 14%

Fig. 9 Example traffic data I

Traffic Data II Fax/Data calls (with IWF) SCI per MS and BH SMS (originating and terminating) per MS and BH Call Forwarding of MTC and MMC thereof conditional to PSTN thereof conditional to VMSc thereof conditional to PLMN thereof unconditional to PSTN thereof unconditional to VMSc thereof unconditional to PLMN 1% (of total traffic) 0.1 0.2 10% 2.5% 40% 7.5% 5% 40% 5%

Fig. 10 Example traffic data II

MN1738EU02MN_0002
2004 Siemens AG

23

Siemens

Network planning

The mobility model describes the behavior of a subscriber with respect to inherent actions. These actions are usually pure signaling related. The traffic and the mobility model is the essential input for the network planning. In general the operator provides information about the call behavior of the subscriber. If this is not the case the network planner has to make reasonable assumptions. The basis of such an assumption could be a comparison of other -already existingnetworks of the same or neighboring countries. WARNING It is not reasonable to give general GSM traffic/mobility model as a reference. There are huge differences in the figures when comparing one country with others. Some operators even distinguish between several regions within the country (e.g. metropolitan and rural area).

24

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Mobility Data Handover per MS and BH thereof inter MSC thereof inter BSC (intra MSC) thereof intra BSC (intra MSC and BSC) Attach/Detach per MS and BH Location Update per MS and BH thereof inter VLR (interworking with HLR) thereof intra VLR
Fig. 11 Example mobility data

0.8 15% 21.25% 63.75% 0.2 2.0 20% 80%

MN1738EU02MN_0002
2004 Siemens AG

25

Siemens

Network planning

4.2

Obtaining the model parameters

We use the planning parameters of a model network when planning a new network. These parameters are estimations based on data of comparable networks. They are used solely for initial planning of a network. Once the network is up and running and network extensions can be made, we can begin to add project-specific measurement data for the planning in order to precisely consider the corresponding load relationships and traffic distribution of the individual regions. The presentation on the opposite page shows an example with measurement data from active operation. The distribution of the call types is obtained from the measurement counters. The traffic value, A, can be calculated as follows with the number of call attempts, CA, and mean holding time, tm .: Traffic value A = CA * tm / 3600 [Erl] Example: Traffic: CA = 31 836 PLMN tm PSTN = 60 sec. A = 530 Erl

WARNING In order to conclude the share of incoming MMCs as well as the share of MTCs without MMCs from observed data of a single MSC, we have to make an assumption regarding the incoming Inter-MSC-MMCs.

26

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

N VLR Subscribers CA (MORTR)

70 113

BSS

CALL_INT_MS_OWN_MSC for MORTR

CA (MTER)

54 816

MMC =

9 810

55 729

BSS

MMC =

5 358

Other BSS / CA (MOUT_ VMSc PLMN)

5 358

CALL_INT_MS_OWN_MSC for MICTR

MTC =
PSTN

MTC/MMC = 45 912 without interrogation

CA (MICTR) MICTR

47 148

MOC =

31 836

31 836
CA MOUT_ NOT_PLMN) PSTN

with interrogation MTRAN =

MSC

24

CA (MTRAN)

86 MTRAN = 62 without interrogation

CA (total)

MSC/ PSTN

CA (in progress)

101 964

93 009

Fig. 12 Call distribution measurement

MN1738EU02MN_0002
2004 Siemens AG

27

Siemens

Network planning

4.3
4.3.1

Traffic matrix
End-to-end

The traffic matrix contains the traffic relationships from all origins to all destinations and therefore provides the input information for network dimensioning. To calculate the traffic matrix we consider the end nodes (BSS and PSTN) as the originating and destination points of the traffic. Another share of the traffic goes to the mailbox service or to other special services such as recorded announcements or call centers. The distribution of traffic cannot be accurately calculated when planning a new network. For this reason, empirical values derived from experience with other networks are used. The best values are those from a neighboring region with comparable economic and population structures. Corrections are made during operation when up-to-date traffic measurement data is available. In our example (Fig. 6) we consider a section of a matrix with BSS 1 as the traffic source and the other network elements as destinations. The table below shows the breakdown of the originating traffic of BSS 1.

A full traffic matrix contains the traffic values of all origin/destination relationships. We still need to define the routing rules in order to calculate the line network. This results in the traffic components in the individual path sections required for trunk group calculation.

28

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

PSTN

MSC 2
A = 1000 Erl

BSS 3
A = 150 Erl

A. = 50 Erl

Other PLMN BSS 2

A = 150 Erl

BSS 1
A = 1500 Erl

MSC 1

BSS 2

BSS 3 150 Erl 10%

PSTN 1 000 Erl 66.6%

Other PLMN 50 Erl 3.3%

Voice Mail Serv. 150 Erl 10%

A = 150 Erl

BSS 1

150 Erl 10%

Voice Mail

Fig. 13 Traffic distribution for mobile originating traffic

MN1738EU02MN_0002
2004 Siemens AG

29

Siemens

Network planning

30

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Network structure, gateways and routing

MN1738EU02MN_0002
2004 Siemens AG

31

Siemens

Network planning

5.1

Network structure

The most important aspect of network design is the creation of simple, clear structures with little overhead for monitoring, operation, maintenance and planning. This must be achieved by a limited, regional intermeshing and by the use of simple routing principles or automatic routing functions such as dynamic routing methods like Optimized Dynamic Routing (ODR) from Siemens. The network has to satisfy strict requirements in order to survive the high level of dynamism of telephone traffic in a deregulated market. This means that new MSC's or an expansion of existing MSC's must be able to be introduced quickly without impairing other network components. Points in the network must be illustrated that provide distinct, concentrated gateways to the increasing numbers of other networks. The design must guarantee a high level of availability of all services in the network and provide robust structures that can react to failures of trunk groups and network elements or to shifts in the traffic patterns. Finally, the network and its routing should be designed to utilize the installed equipment as much as possible and for all traffic flows. An additional aspect is the so-called robustness of the network. Unexpected loads occur regularly, particularly in the case of mobile communication networks reserves of about 20% should be allowed during planning for such contingencies. A flexible traffic management function can help to prevent or alleviate network overloads so that a grade of service can be guaranteed up to extreme loads. Practical experience has demonstrated that the introduction of a transit level at an early stage is of benefit because it makes it much easier to expand the network with new elements. Simple network structures are clearer for monitoring and planning. The choice of intermeshing depends on the traffic volume and the geographical or cost relationships. The star network has the disadvantage that there are no alternative routes. Intermeshing is often not feasible in mountainous terrain for cost reasons. Full intermeshing is recommended in densely populated areas (region III) because the traffic is routed during local overloads to the destination over alternative routes, thereby significantly increasing the level of availability. Traffic from the PLMN to the PSTN is generally routed directly from the originating MSC to the fixed network. The Mobile Terminating Traffic (MTC) is routed from the view of the PSTN through the nearest transit MSC. Likewise, the mobile traffic between the individual regions is transported only via the transit MSC's. We avoid the use of full intermeshing by introducing the transit level. The planning, operation and maintenance of the network are therefore clearer, and produce less costs. The special services such as recorded announcements, voice mail service or the Short Message Service are partially created locally in each MSC, and for low traffic volumes, also centrally in the transit MSC's. These units are not shown in the figure in order to preserve clarity.

32

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Region Region I I (partially (partially intermeshed) intermeshed)

Region Region IIII (star (star- shaped) shaped)

PSTN

Region III Region III (fully (fully intermeshed) intermeshed)

BSS

MSC

Transit/Gateway MSC

Fig. 14 Planning regions

MN1738EU02MN_0002
2004 Siemens AG

33

Siemens

Network planning

5.2
5.2.1

Gateways and routing

Overview

Generally speaking, a large portion (50 80%) of traffic is directed to the fixed network (PSTN) or comes from there and ends in the mobile network. There are also traffic components to other mobile network operators. These points of interconnection must be defined in conjunction with the relevant network operators. The routing options depend on the regulatory controls imposed by the corresponding state. The transition to the fixed network can take place in the originating MSC, in a transit MSC or in the called party's region. In the presentation shown on the opposite page the setup of a call from a calling party (MSC 1) to a called party (MSC 1 / 2 / 3) is controlled by routing in the PLMN in such a way that the transfer to the PSTN does not take place until in the destination area. Example: A Sub. MSC 1 MSC 2 MSC 3 PSTN (South) B Sub.3

Routing is taken to mean the selection of different paths available for switching a call. Electronically controlled switching systems, such as MSC, permit different routing functions. The following are the objectives of routing: Provision of an alternative path if the preferred path is under heavy load Sharing of load among as many possible alternative paths Optimum utilization of all available network resources. The use of a suitable routing method depends on the network structure and the availability of the corresponding routing function in the network element. Depending on the routing definitions, the trunk group dimensioning can then be calculated. The routing in Fig. 16 shows two alternative routes over MSC 2 and MSC 3 for calls in the direction MSC1 MSC 4. In this way, we can access free routes if congestion occurs, thereby significantly increasing availability.

34

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

A-Sub.

PLMN

MOC Transition in called partys region

MSC 1 MSC 2 MSC 3

PSTN

PSTN Central

PSTN

B-Sub.1

B-Sub.2

B-Sub.3

Fig. 15 MOC routing example

MSC 2

Route 2 MSC 4

MSC 1 Route 3

Route 1

Route 2

MSC 3

Route 1

PSTN

Fig. 16 Routing and interconnection

MN1738EU02MN_0002
2004 Siemens AG

35

Siemens

Network planning

5.2.2

Fixed Alternate Routing (FAR)

The most common method of routing is so-called fixed alternate routing (FAR). The order of the alternate paths in the database of individual network elements is fixed. Fig. 17 shows an example of a "single overflow configuration". In this overflow configuration, the preferred path is under very high load and only the traffic peaks are routed over the final route. The availability is increased in that, should the transmission equipment for the preferred path fail, the final route has a certain overload reserve available to all direct routes. The end-to-end blocking rate (GOS = Grade of Service) is significantly reduced as shown in the following calculation: Example: Blocking B: Node1 B: Node1 B: TRX EEB Node1 EEB Node1 Dest 1 = 0.2 % Dest 1 TRX Dest 1 = 10% = 1% = 1%

Dest 1 = 0.1 * [ 1 ( 1 0.01) * (1 0.01) = 0.002

36

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Transit TRX

Final Route

DEST 1

DEST 2

DEST 3

Orig 1 Orig 2

Offered Traffic A

DEST 4

First Choice Route

DEST 5 Node 1

Alternate routing Node 1 ==> Dest 1 . . . 5

Orig n
Fig. 17 Alternate routing

MN1738EU02MN_0002
2004 Siemens AG

37

Siemens

Network planning

5.3

Fixed Alternate Routing (FAR) with load sharing in the final route

The security and cost-effectiveness of a network can be further increased by duplicating the final route i.e., each MSC is connected with two or more transit nodes. As a result, the likelihood of a total failure of the final route is very small because two nodes very rarely fail at the same time. In small networks it is more cost-effective to connect to the PSTN or to foreign PLMN's via the gateway MSC because larger trunk groups result from concentrating the traffic, thereby reducing the costs per traffic channel. A network planner must also decide whether a high usage route is to be created or not. Small trunk groups with N < 90 traffic channels are often not economic because the costs for administration, maintenance and planning may be higher than the savings obtained by shorter distances. The traffic is then always first routed along the direct route (if available) and overflows using the load sharing principle to the gateway MSC's. The load sharing ratio is variable but is generally set to 50:50 in the case of equivalently used transit MSC's. If the new planning indicates that the network will grow rapidly, the early introduction of gateway MSC's is to be recommended because a network expansion is significantly easier to implement. A new MSC (7) is connected in the first step only to the gateway MSCs and therefore has immediate access to all other network elements. Destination load measurements show whether a high usage route to other MSC's is required or not. The modification work in the existing network elements is minimized with this expansion strategy. However, the trunk groups must be adapted to the new traffic load. Examination of the utilization of the trunk group capacities is in any case a permanent task of the network analysis function.

38

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

PSTN

other PLMN

Gateway MSC 1

Gateway MSC 2

50%

50%

MSC 3

50% Final Route

50%

MSC 7

First Route

MSC 4

MSC 5

MSC 6

Fig. 18 Gateway MSC with load sharing

MN1738EU02MN_0002
2004 Siemens AG

39

Siemens

Network planning

5.4

Optimized Dynamic Routing (ODR)

Yet another routing function is provided by the MSC with the method called Optimized Dynamic Routing (ODR). Optimum utilization of the trunks is possible for fully intermeshed networks i.e., up to 10% fewer trunks than for conventional routing methods (FAR) are needed for the same blocking rate (B<1%). The basic principle is that the greatest share of the traffic (about 90 95% depending on the trunk group concentration) is processed over the direct route from the origin to the destination. If the high usage route is blocked, the overflow traffic is evenly shared between the available alternate routes. This is achieved as follows: the first five overflow connections are routed over the first free alternate route, the next five over the second alternate route, etc. If the second section for an alternate route (transit destination MSC) is blocked, the connection back to the origin is released ("crank back") and a second attempt (rerouting) is started. This procedure only takes place once however because otherwise the switching processors would be placed under undue load. Moreover, further attempts made during congestion of the destination area would also be rejected. We assume a non-hierarchical network for the ODR method i.e., all MSC's are at the same network level. Like in an hierarchical network, traffic to the PSTN or to other external networks can also be routed via two gateway MSC's. For this scenario we use a mixture of Fixed Alternate Routing (FAR) and Optimized Dynamic Routing (ODR): In the first step the traffic is distributed among the gateway MSC's via a trunk group cluster (FAR) In the second step the overflow traffic is routed over the alternate routes using the ODR method to the gateway MSC's and then to the PSTN. This routing method is particularly useful in mobile communication networks because the traffic distribution changes dramatically over the day. This problem can be solved in part using scheduled routing tables. The dynamic routing method ODR solves the problem with great efficiency because all unused network resources can be accessed. ODR greatly improves the stability of a network i.e., the blocking rate increases much more slowly than for conventional routing methods during overload or partial failure of the transmission paths.

40

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

T3 T2 T1

Uniform traffic distribution over all active alternative routes

Destination B

Origin A

T4 T5

1. Distribute traffic overflows to sets of active alternative routes (1 ... n)

T6

Possible alternative routes: inactive active 2. Remove route from active route set if first or second section of the alternative route is blocked
unsuccessful

3. Reinitialize active route set

6 3 1

1 2 3

6 5 4

1 2 3 4

6 5

1 3 3

active alternate routes

Fig. 19 Optimized dynamic routing (ODR)

active

inactive alternate routes

active alternate routes

MN1738EU02MN_0002
2004 Siemens AG

41

Siemens

Network planning

42

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Load check

MN1738EU02MN_0002
2004 Siemens AG

43

Siemens

Network planning

After completing the previous planning stages (end-to-end traffic matrix calculation and routing decisions) the resulting link and system loads can be calculated which in turn save as input parameters for dimensioning the interfaces and internal components (see the chapter on Dimensioning for details). Calculating the system load is a complex computational process and is conducted during the planning phase by experts using a the traffic and mobility models stated before. Moreover, the HW and SW variants and capacity stage of the system must be taken into account. The result of these calculations is the maximum number of MSC / VLR subscribers that can be served by a Mobile Switching Center (MSC). The system load is mainly governed by the following parameters: Call rate taking the Call Split into account Handover rate of successful calls Location update rate (differentiated according to Intra / Inter VLR) Use of the supplementary services. This calculation is extremely vital to the planning phase because the usage of the CP113 is critical in the performance of the overall network.

44

MN1738EU02MN_0002
2004 Siemens AG

Network planning

Siemens

Fig. 20 Screenshot of the SIEMENS CP load tool

MN1738EU02MN_0002
2004 Siemens AG

45

Siemens

Network planning

46

MN1738EU02MN_0002
2004 Siemens AG