Lietuvos Respublikos Ryšių reguliavimo tarnyba - …old.rrt.lt/download/17686/bu_lraic model manual final.docx · Web viewThese parts are distinguished by different page colors:

The Communications Regulatory Authority Mobile BU-LRAIC model documentationDecember 2012

Contents

1. Model user instructions..................................................................................................51.1 Model structure........................................................................................................51.2 “Intro” page.............................................................................................................51.3 Input parameter pages.............................................................................................6

1.3.1 Page “D1 Service Volumes“..................................................................................61.3.2 Page “D2 Service Statistics“.................................................................................71.3.3 Page “D3 Headroom Allowance”...........................................................................71.3.4 Page “D4 Network Statistics“...............................................................................7

1.3.4.1 Field “Coverage parameters”........................................................................81.3.4.2 Field “Traffic split between networks”...........................................................81.3.4.3 Field “LTE traffic“...........................................................................................81.3.4.4 Field “LTE sites configuration“.......................................................................81.3.4.5 Field “UMTS traffic“.......................................................................................81.3.4.6 Field “GSM traffic “........................................................................................91.3.4.7 Field “UMTS cell parameters“........................................................................91.3.4.8 Field “UMTS sites configuration“...................................................................91.3.4.9 Field “BTS capacity“......................................................................................91.3.4.10 Field “GSM sites configuration“.....................................................................91.3.4.11 Field “Transmission”......................................................................................91.3.4.12 Field “Other“.................................................................................................9

1.3.5 Page “D5 HCC data“.............................................................................................91.3.6 Page “D6 Mark-ups“...........................................................................................101.3.7 Page “D7 Service Matrix”...................................................................................101.3.8 Page “C3 UMTS pre-Design”...............................................................................101.3.9 Page “C4 LTE pre-Design”...................................................................................11

1.4 Calculation pages...................................................................................................111.4.1 Page “C1 Demand“.............................................................................................11

1.4.1.1 Field “Service conversion and service volumes“.........................................111.4.1.2 Field “Service and network elements matrixes”..........................................12

1.4.2 Page “C2 Projection“...........................................................................................121.4.2.1 Table “Traffic Projection”.............................................................................121.4.2.2 Table “Service demand growth”..................................................................12

1.4.3 Page “C3 UMTS pre-Design“...............................................................................121.4.3.1 Channel to Erlang conversion factor...........................................................131.4.3.2 NodeB calculation.......................................................................................13

1.4.4 Page “C4 LTE pre-Design“...................................................................................131.4.5 Page “C5 Network Design“.................................................................................14

1.4.5.1 Field “eNodeB calculations“........................................................................141.4.5.2 Field “NodeB calculations“..........................................................................161.4.5.3 Field “BTS Calculations”..............................................................................171.4.5.4 Field “Sectors”............................................................................................181.4.5.5 Field “Transceiver (TRX)“............................................................................181.4.5.6 Field “Transmission network“......................................................................191.4.5.7 Field “Base station controller (BSC)“...........................................................201.4.5.8 Field “Transcoder Controller (TRC)“.............................................................201.4.5.9 Field “Radio Network Controller (RNC)“.......................................................201.4.5.10 Field “MSC server (MSS) and media gateway (MGW)“.................................201.4.5.11 Field “IMS“..................................................................................................211.4.5.12 Field “Mobile switching center (MSC)“.........................................................211.4.5.13 Field “Intelligent network (IN)“....................................................................221.4.5.14 Field “Billing IC hardware and software“.....................................................221.4.5.15 Field “Number portability system harware and software“...........................22

The Communications Regulatory Authority Mobile BU-LRAIC model documentation November 2012

1.4.5.16 Field “Voice messaging service (VMS)“.......................................................221.4.5.17 Field “Home location registry (HLR)“...........................................................221.4.5.18 Field “Centralized User Database (CUD)“....................................................231.4.5.19 Field “Short message service center (SMSC)“.............................................231.4.5.20 Field “Multimedia messaging service center (MMSC)“................................231.4.5.21 Field “Packet control unit (PCU) and serving GPRS support node (SGSN)“. .231.4.5.22 Field “Evolved Packet Core network“..........................................................241.4.5.23 Field “Core ETH transmission“.....................................................................24

1.4.6 Page “C6 Revaluation“........................................................................................241.4.7 Page “C7 Mark-ups”............................................................................................241.4.8 Page „C8 HCC – NC“...........................................................................................25

1.4.8.1 Field “Allocation on Network Components “................................................251.4.8.2 Field “Cost of Network Components “.........................................................251.4.8.3 Field “Cost of Network Components - Service increment “..........................26

1.4.9 Page „ C9 NC-Services“......................................................................................271.4.10 Page „C10 Erlang“..............................................................................................27

Appendix A Entry data updating methodology......................................................................28

UAB „Ernst & Young Baltic” | 3


1. Model user instructionsBU-LRAIC model is prepared using the MS Excel 2007 application (part of MS Office Professional software package). In order to be able to see all the functionalities described in these user instructions, the user should have software version not lower than MS Excel 2007. If a lower version than MS Excel 2007 is used, a part of BU-LRAIC model may not be functioning.

The description of BU-LRAIC model is presented below.

1.1 Model structureBU-LRAIC model consists of three main parts:

► Intro page;► Input parameter pages;► Calculation pages.

These parts are distinguished by different page colors: intro – blue, input parameters – beige and calculations – green. Please note that C3 and C4 pages contain input data as well. The diagram presented below illustrates the model structure and interconnection between the model pages.

Diagram 2. BU-LRAIC model structure and interfaces

Note. Nodes from D2 to C8 and from D2 to C5 are not specified in this diagram.

The arrow that connects pages indicates the use of the input parameters or calculation results of one page (where the arrow starts) in another page (where the arrow ends). For instance, calculations on the page “C1 Demand” are performed by using data from the pages “D1 Service Volumes“ and “D2 Service Statistics“.



1.2 “Intro” pageThe purpose of “Intro“ page is a management of model pages. ”Intro“ consists of

2 two blocks of buttons – input parameters and calculations (see Diagram 2) – and drop down lists indicating:► Language;► Year of projection;► Annualization method;► Usage of IMS;► Inclusion of POI costs.

To calculate services’ rates choose year and press “Refresh” button in the “Intro” worksheet. The results of the calculation will be presented in the “C8 NC-Services” worksheet. Before pressing “Refresh” button, please make sure the parameters in “Intro” sheet are selected in the correct language.

By pressing the button in the upper left corner of the model page “Intro”, one can go back to the “Intro” page – „Intro“ page opens.

1.3 Input parameter pagesThe model has the following parameter pages:

1. “D1 Service Volumes” page 2. “D2 Service Statistics ” page3. “D3 Headroom Allowance” page4. “D4 Network Statistics” page5. “D5 HCC Data” page6. “D6 Mark-ups” page 7. “D7 Service matrix” page 8. “C3 UMTS pre-Design” page9. “C4 LTE pre-Design” page

As specified in Diagram 2, the data of each page is used in the specific calculation or other input parameters pages. Input parameter pages contain input data of different types:

Data provided by Operators from Questionnaires;

Data, which was presented as assumptions in MRP;

Benchmark data, which has been provided by EY;

Data taken from the previous mobile BU-LRAIC model;

Data taken from current fixed BU-LRAIC model

1.3.1 Page “D1 Service Volumes“ This page contains data of the subscribers’ quantity, service volumes and service statistics from 2010 to 2022 (inclusive). This table of data consists of the following columns: data type



(column B), unit (column D) and volumes in the years 2010-2022 (columns F-R). A list of the basic services and service statistics is presented below:► Actual and forecasted number of mobile subscribers (lines 9-11)► Actual and forecasted voice traffic for different types of mobile calls (minutes of use)

(lines 12-19)► Actual and forecasted video traffic for different types of mobile calls (minutes of use)

(lines 20-23)► Actual and forecasted SMS traffic for different types of mobile SMS (units of use) (lines

24-27)► Actual and forecasted MMS traffic for different types of mobile MMS (units of use) (lines

28-31)► Actual and forecasted Packet data traffic for different types of mobile traffic (Mbytes)

(lines 32-38)► Actual and forecasted GSM coverage (geographical) (lines 39-42)► Actual and forecasted UMTS coverage (geographical) (lines 43-46)► Actual and forecasted LTE coverage (geographical) (lines 47-50)► Actual and forecasted traffic split between radio networks as % of total traffic (excl.

packet data traffic) (lines 51-54)► Traffic split between radio networks as % of total voice CS traffic (excl. packet data

traffic) (lines 55-57)Detailed definitions of services and statistics types are presented in the survey questionnaire (hereinafter, the questionnaire) description.The data on servies in this page is used in “C2 Projection” calculation page, data use in the particular calculations is described in section 1.4.2 Projection, and statistics data is used in “D1 Service Volumes” sheet in order to gather Network statistics data for the 2010-2022 time period and further is used in “D4 Network Statistics” page wtich is described in section 1.3.4 Network Statistics.1.3.2 Page “D2 Service Statistics“

This input parameter page consists of two tables:► Routing factors matrix (lines 9-35)► Service conversion factors table. This table consists of the following columns:

“Parameters” (column B), “Unit” (column D) and “Values per total network “ (column E-L). The following parts are also specified in the table:► Call and call set-up durations (lines 42-45)► Completion rates (lines 46-47)► De-averaging factors (lines 48-52)► SMS/MMS conversion factors (lines 53-56)► Data conversion factors (lines 57-70)► Video conversion factors (lines 71-73)► Network parameters (lines 74-76)► Peak to off-peak tariff diferentiation (lines 77-80)► Priority factors (lines 81-83)► VoIP assumptions (lines 84-109)► Interconnection ports – voice (lines 111-120)

Use of the above data in the calculations is described in the following sections: 1.3.7 Page “Service matrix”, 1.4.1 Page “Service demand”, 1.4.5 Page “Network Design” and 1.4.8 Page “HCC – NC”.1.3.3 Page “D3 Headroom Allowance”

This input parameter page is a table of network elements and their capacity parameters. The table consists of the following columns:► Network element type (column B)► Measurement unit (column D)



► Base unit capacity if applicable (column F)► Extension unit capacity if applicable (column G)► Maximal technical capacity (including possible expansion) (column H)► Design utilisation factor at planning stage if applicable (column I)► Planning horizon (column J)► Planning horizon 2 (column K, necessary for functionality purposes)► Network demand group (column L)► Network demand group 2 (column M, necessary for functionality purposes)► Headroom allowance (column N)► Operational allowance (column O)► Base unit operational capacity (column Q)► Extension unit operational capacity (column R)► Maximal operational capacity (column S)

The data in the columns F to J was collected in the questionnaires or by other means. In the Column K (Network demand group) one of the three possible network demand groups is determined by the type of a specific network element planning.1.3.4 Page “D4 Network Statistics“

This input parameter page consists of the following basic fields:► Coverage parameters (lines 8-46)► Traffic split between networks (lines 48-57)► LTE traffic (lines 59-89)► LTE sites configuration (lines 91-110)► UMTS traffic (lines 112-142)► GSM traffic (lines 144-163)► UMTS cell parameters (lines 165-195)► UMTS sites configuration (lines 197-216)► BTS capacity (lines 218-237)► GSM sites configuration (lines 239-261)► Transmission (lines 263-286)► Other (lines 288-291)

1.3.4.1 Field “Coverage parameters” The field of coverage parameters can be divided in two parts. Part one specifies what total area of the Republic of Lithuania is covered by the

network modelled (line 10), by what geographical areas proportions this total area is split (lines 12-14) and what part is covered by LTE (lines 16-19), UMTS (lines 21-24) and GSM (lines 26-29) networks according to the respective geographical areas. This data is used in the model to calculate the number of basic stations to meet coverage requirements.

Part two determines presence of a certain mobile communications technology or attribute in the network (lines 32-46). For instance, if there is HSDPA technology in the modelled UMTS network, “1” is entered in the respective cell, if the technology does not exist, “0” is entered.

1.3.4.2 Field “Traffic split between networks” The field of traffic split between networks determines distribution of the service

traffic (excluding the packet data traffic) between the LTE, UMTS and GSM radio networks (lines 50-53). Sum of proportions (the percentages) between the LTE, UMTS and GSM radio networks has to be equal to 100% (50 line). It also determines the distribution of the same service traffic in the core networks; what part of the traffic is serviced at the mobile switching center (MSC, 2G architecture, line 56) and what in MSC server and media gateway



(MSS+MGW, 3G architecture, line 57). These 2G and 3G proportion sum has to be equal to 100% (55 line).

1.3.4.3 Field “LTE traffic“The traffic in busy hour is estimated in the first (61-64) lines of the field LTE

traffic:► Voice and video service traffic in Erlangs. It equals to the total LTE network traffic

without the packet data part.► Packet data traffic, BHMB. This value is estimated by selecting the bigger BHMB LTE

traffic from the up-link data traffic and the down-link data traffic.► Uplink and downlink ratio. This value is estimated by dividing the total uplink traffic

by the downlink traffic. The results should be expressed in percentages.

The other five parts of this field (lines 66-89) provide the LTE traffic distribution by geographical areas and cell types.

This data is further used to calculate the LTE network elements quantity on the page “C5 Network Design“.

1.3.4.4 Field “LTE sites configuration“This field presents the proportions between the macro cells quantities by sector

and geographical areas (lines 93-106) and the average number of micro (line 109) and pico (line 110) cells per site. These parameters are used further in the model to calculate eNodeB quantities.

1.3.4.5 Field “UMTS traffic“The traffic in busy hour is estimated in the first (114-117) lines of the field UMTS

traffic:► Voice and video service traffic in Erlangs. It equals to the total UMTS network traffic

without the packet data part.► Packet data traffic, BHMB. This value is estimated by selecting the bigger BHMB

UMTS traffic from the up-link data traffic and the down-link data traffic.► Uplink and downlink ratio. This value is estimated by dividing the total uplink traffic

by the downlink traffic. The results should be expressed in percentages.

The other five parts of this field (lines 119-142) provide the UMTS traffic distribution by geographical areas and cell types.

This data is further used to calculate the UMTS network elements quantity on the page “C5 Network Design“.

1.3.4.6 Field “GSM traffic “ The traffic in busy hour is estimated in the first (147 and 148) lines of the GSM

traffic field: ► Voice, SMS and MMS service traffic in Erlangs. It equals to the total GSM network

traffic without the packet data traffic part.► Packet data traffic in Erlangs. This value is calculated by adding up up-link and

down-link GSM data traffic (already converted to minutes).

The other three parts of this field (lines 150-163) present the GSM traffic distribution by geographical areas and cell types.

This data is further used in the model to calculate GSM network elements quantities in the page “C5 Network Design“.



1.3.4.7 Field “UMTS cell parameters“ In this field the the assumptions of NodeB cell range (lines 167-170) and sector

capacity by cell types and geographical areas are presented (lines 172-195). This data is further used in the model to calculate NodeB quantities.

1.3.4.8 Field “UMTS sites configuration“This field presents the proportions between the macro cells quantities by sector

and geographical areas (lines 199-212) and the average number of micro (line 215) and pico (line 216) cells per site. These parameters are used further in the model to calculate NodeB quantities.

1.3.4.9 Field “BTS capacity“ In the beginning of this field 900 MHz (GSM and EGSM) and 1800 MHz (DCS)

amount of spectrum (2x MHz) (lines 221 and 222) is calculated according to the GSM communications frequencies used by the operator. Also, sector reuse factors (lines 224 and 225) are provided for the frequencies of 900 MHz and 1800 MHz. Further, the assumptions for bandwidth of transceiver (line 227), cell range (lines 229-232) and physical sector capacity (lines 234-237) by cell types and geographical areas are presented. This data is further used in the model to calculate BTS quantities.

1.3.4.10 Field “GSM sites configuration“ This field presents the proportions of macro cell quantities by sectors and

geographical areas (lines 243-256) as well as the average number of micro (line 260) and pico (line 261) cells per site. These parameters are further used in the model to calculate BTS quantities.

1.3.4.11 Field “Transmission” In the beginning of this field the proportion of stand-alone ETH radiolink sites in

backhaul transmission as a ratio of stand-alone ETH radiolink sites to total number of sites in a network (line 265) and proportion of stand-alone ETH radiolink sites in core transmission as a ratio of stand-alone ETH radiolink sites to total number of sites in a network (line 268) are presented.

Further, BTS/NodeB-BSC/RNC logical layer proportions by ETH radiolinks capacities are provided, which are used in transmission network design calculations (lines 273-276).

The average number of BTS/Node B sites per link (ETH radiolinks) is provided in the line 278.

The last part in this field defines BSC/RNC-MGW logical layer proportions by capacity: what part of the traffic falls on microwave links and leased lines (lines 283-284). The average number of BSC/RNC sites per link is specified in line 286.

This data is further used in the model to calculate ETH radiolinks quantities in the network.

1.3.4.12 Field “Other“This field presents an assumption regarding the average IN transaction number

per call of pre-paid subscriber (origination, on-net) (line 291). This parameter is used to calculate the quantities of the service control point (SCP).1.3.5 Page “D5 HCC data“

This input parameter page presents the financial data of homogeneous cost categories:



► Current network equipment price (column D)► Currency, EUR or LT (column E)► Total current network equipment price, LTL (column F)► Useful lifetime (column G)► Average price index of the recent years (column H)► Net book value (NBV) and gross book value (GBV) ratio (column I)

Detailed definitions of HCC data presented above are provided in the BU-LRAIC questionnaire description. HCC financial data is further used on the calculation page “C6 Revaluation“.

This input parameter page also provides the LT/EUR exchange rate (cell C9) which is used to exchange EUR values to LT for column F - “Total current network equipment price, LTL” . This page also provides the average weighted capital cost (WACC) (cell C10). The last parameter is used in the calculations page “C6 Revaluation”.1.3.6 Page “D6 Mark-ups“

This input parameter page presents the values of mark-ups. The mark-ups used in BU-LRAIC model were calculated by using the data provided by the (network operating costs, network management system costs, administration and support operating costs, administration and support capital costs), modelled GRC values and Operators’ financial statements. OPEX mark-up was calculated dividing network operating expenses by GRC, OPEX (administration and support) was calculated dividing administration and support operating expenses by OPEX mark-up, Network management system mark-up was calculated dividing network management system costs by GRC, CAPEX (administration and support) was calculated dividing administration and support capital expenses by OPEX mark-up.

The following mark-ups groups are used in BU-LRAIC model and presented on this input parameter page:► Mark-ups of operational costs on network cost (cell B10)

► Site infrastructure► Base stations system (BSS) infrastructure► Transmission► MSC/MGW and other network elements

► Mark-ups of network management system on network cost (cell B16)► BSS infrastructure► Transmission► MSC/MGW and other network elements

► Mark-ups of administration and support operational cost (cell B23)► Total network infrastructure

► Mark-ups of administration and support capital cost (cell B26)► Total network infrastructure

Mark-ups are expressed in percent and are further used on the calculation page “C7 Mark-ups”, where absolute mark-ups values are calculated. 1.3.7 Page “D7 Service Matrix”

This input parameter page establishes the average service usage factors in order to calculate the service costs per each network component later.

Column B “Service type” presents modelled network services, cells C5:P5 – network components, cells C9:P19 – service usage factors.



For the calculation of average service usage factors, data is taken from the input parameter page “D4 Network Statistics” and calculation page “C1 Demand“. Calculations are based on the principles presented in the Reference paper. 1.3.8 Page “C3 UMTS pre-Design”

This page consists of two parts: input parameter part (lines 7-48) and calculations part (lines 55-135).

In the input parameter part, consists the following input parameters realated to NodeB dimensioning:

Spectrum assumptions.► Amount of spectrum (2 x 5 MHz) (cell F10). This parameter represents the number of

UMTS FDD duplex channels used by operator to provide UMTS voice and data services (excluding HSDPA)

Section A. Downlink values.► Maximal UMTS cell ranges assuming minimal capacity consumption (lines 15-17). This

parameter is estimated based on link budget simulations assuming minimal number of users and minimal interferences from other sectors/users

► Minimal site capacity volume (single data channel) (cell F19). This parameter presents minimal site capacity in kbps per one carrier

► Maximal UMTS cell ranges assuming full capacity consumption (lines 22-24). This parameter is estimated based on link budget simulations assuming maximal number of users and maximal interferences from other sectors/users.

► Maximal site capacity volume (single data channel) (lines 27-29). This parameter presents maximal site capacity in kbps per one carrier for each cell type.

Section B. Uplink values.► This section has the same structure as section A.

1.3.9 Page “C4 LTE pre-Design”This page consists of two parts: input parameter part (lines 7-48) and calculations

part (lines 51-131).Input parameter section has the same structure as in the page “C3 UMTS pre-

Design”. Therefore please refer to the section 1.3.8 Page “C3 UMTS pre-Design” for manual.

1.4 Calculation pagesThe description of input parameter pages and model pages defines data sources,

gives a general indication of further utilisation of the results received. This part contains a description of the operating principles of the model and constituent parts of the calculation pages. The model consists of the following calculation pages:1. “C1 Demand” page2. “C2 Projection” page3. “C3 UMTS pre-Design” page4. “C4 LTE pre-Design” page5. “C5 Network Design” page6. “C6 Revaluation” page7. “C7 Mark-ups “ page8. “C8 HCC – NC” page9. “C9 NC-Services” page



10. “C10 Erlang” pageIn the calculation pages, calculations are performed in each cell (they have formulas); therefore, they cannot be deleted or otherwise changed. If this requirement is not followed, the model may function only partially or may fail to produce any results.1.4.1 Page “C1 Demand“ Three main fields are specified on this calculation page:► Service conversion and service volumes (preparatory part of demand calculations)► Service and network elements matrixes (hereinafter, Matrix)

1.4.1.1 Field “Service conversion and service volumes“ In this field preparatory calculations for service and network elements matrixes are performed. Service volumes that are not measured in minutes are converted to equivalent minutes. Conversions are performed according to the formulas described in the Reference paper section 9.1. Service demand conversion and the data presented on the input parameter page “D2 Service Statistics“. The following service volumes are converted to equivalent minutes:► SMS message (unit)► MMS message (unit)► GPRS data (MB)► EDGE data (MB)► GSM data (MB)► UMTS data (MB)► HSDPA (MB)► UMTS (MB)► LTE (MB)► Video call minutes (min)

Then the waiting time per one successful call minute is calculated (line 46) and the volumes of the year (lines 47-76), which is set on the “Intro” page, are assigned.

1.4.1.2 Field “Service and network elements matrixes” The calculations of this field are performed according to the formulas described in

the Reference paper section 9.1. Service demand conversion and the data presented on the input parameter page “D2 Service Statistics”.

Service and network elements matrix is the same routing factors matrix defined on the page “D2 Service Statistics”, just extended with the lines of the quantities of voice and video calls attempts.

The First Matrix of weighted service scope assesses the weighted service volumes, i.e. the annual service volumes are multiplied by the respective service and networks elements routing factors from the page “D2 Service Statistics“. When performing weighted traffic calculations, the calculations of the quantities of voice and video calls attempts are performed too (lines 83-115). The results of Second Matrix, matrix of weighted services in equivalent minutes, are calculated the results of First Matrix multiplying by the respective service conversion factors.

The Third Matrix, matrix of busy hour traffic, represents the service traffic in busy hour, i.e. the quantities of Erlangs and busy hour megabytes are calculated. The results of this Matrix are received by multiplying the results of the second Matrix and the de-averaging factors (page “D2 Service Statistics”, lines 49-52).The results of the Second Matrix are further used in the model on page “C8 HCC-NC”, the results of the Third Matrix – on page “C5 Network Design“. More detailed use of these results is described in the respective sections.



1.4.2 Page “C2 Projection“ This page consists of two tables:

► Traffic Projection► Service demand growth

Projection of services (in equivalent minutes) is performed by demand groups, which are defined in the Reference paper, section 10.4.1. Base and extension units.

1.4.2.1 Table “Traffic Projection” This table consists of the columns “Demand group” (column B), “Current time”

(column D) and “Volumes” (columns F-R). The values of demand groups of the analysed year (the year set on the “Intro” page) are calculated in lines 13-15 by using the results of the page “D1 Service Volumes”. The demand group values of the respective year are calculated in the same lines of the column group “Volumes” using the data from pages “C1 Demand” and “D1 Service Volumes”. The projections for the years 2010-2022 stating from the year analysed of the demand group values are calculated in lines 9-11 in the columns group “Volumes”, i.e. the ratio between the value of a specific year and the analysed year is estimated.

1.4.2.2 Table “Service demand growth” This table consists of the “Demand group” (column B) and columns of planning

periods (columns D-J). Line 19 provides a calculation of the part of a year that the specific planning period in line 20 covers in one year (for the planning period 1 and 2 years ahead, this part equals to 1). Lines 21-23 show the estimation of the total service projection and planning period effect, i.e. the service demand growth ratio is calculated (marked in Reference paper as rSDG).The service demand growth ratio (for a certain demand group and planning period) is used on the page „D3 Headroom Allowance” to calculate the headroom allowance values. 1.4.3 Page “C3 UMTS pre-Design“

The first part of this page consists of the input data (lines 7 – 48) which has been described in the section 1.3.8 Page “C3 UMTS pre-Design”. The second part of this page contains channel to Erlang conversion factor calculation (lines 50- 53) and NodeB calculations (lines 55 – 135). In the following sections these calculations will be detailed.1.4.3.1 Channel to Erlang conversion factor

This parameter presents average number of Erlangs per one voice channel for UMTS radio network (lines 50 – 53). It is estimated as arithmetical average of number of Erlangs per one voice channel for minimal and maximal cell capacities. Number of Erlangs for each capacity is read from Erlang tables. 1.4.3.2 NodeB calculation

In this worksheet the optimal UMTS macrocell range and sector capacity is calculated (lines 55 – 135). The optimal UMTS macrocell range and sector capacity are calculated separately for different area types. In UMTS system the cell range is dependent on current traffic, the footprint of CDMA cell is dynamically expanding and contradicts according to the number of users. This feature of UMTS is called “cell breathing”. Implemented algorithm calculates optimal UMTS cell range regarding to the cell required capacity (demand). It is calculated in four steps:

Section A. Required UMTS network capacity by cell typesIn this section the required UMTS network capacity for uplink and downlink

channel is calculated based on voice and data traffic demand (lines 59-61). The UMTS network capacity is calculated separately for different area type.



Section B. Traffic BH density per 1km2In this section Traffic BH density per 1km2 is calculated based on required UMTS

network capacity and required coverage of UMTS network (lines 65-67). The UMTS traffic BH density per 1km2 is calculated separately for uplink and downlink channel for each area type.

Section C. Downlink and uplink calculation In this section implemented algorithm finds the relationship (function) between

cell area and cell capacity, separately for uplink and downlink channel and different area type (lines 71-100). To find relationship (function) formula algorithm uses two function extremums:

1. x: Maximal UMTS cell range assuming minimal capacity consumptiony: Minimal site capacity volume (single data channel)

2. x: Maximal UMTS cell range assuming full capacity consumptiony: Maximal site capacity volume

Then according to traffic BH density per 1km2 and found relationship (function) formula, the optimal cell area and sector capacity is calculated, separately for different area type (lines 102-120).

Section D. TotalIn this section the optimal UMTS macrocell range and sector capacity is calculated, separately for uplink and downlink channel and different area type (lines 125-135). 1.4.4 Page “C4 LTE pre-Design“

In lines 51-131 of this worksheet the optimal LTE macrocell range and sector capacity is calculated. The optimal LTE macrocell range and sector capacity are calculated separately for different area types. Implemented algorithm calculates optimal LTE cell range regarding to the cell required capacity (demand). It is calculated in four steps:

Section A. Required LTE network capacity by cell typesIn this section the required LTE network capacity for uplink and downlink channel

is calculated based on voice and data traffic demand (lines 55-57). The LTE network capacity is calculated separately for different area type.

Section B. Traffic BH density per 1km2In this section Traffic BH density per 1km2 is calculated based on required LTE

network capacity and required coverage of LTE network (lines 61-63). The LTE traffic BH density per 1km2 is calculated separately for uplink and downlink channel for each area type.

Section C. Downlink and uplink calculation In this section implemented algorithm finds the relationship (function) between

cell area and cell capacity, separately for uplink and downlink channel and different area type (lines 67-96). To find relationship (function) formula algorithm uses two function extremums:

3. x: Maximal LTE cell range assuming minimal capacity consumptiony: Minimal site capacity volume (single data channel)

4. x: Maximal LTE cell range assuming full capacity consumptiony: Maximal site capacity volume



Then according to traffic BH density per 1km2 and found relationship (function) formula, the optimal cell area and sector capacity is calculated, separately for different area type (lines 98-116).

Section D. TotalIn this section the optimal LTE macrocell range and sector capacity is calculated, separately for uplink and downlink channel and different area type (lines 121-131). 1.4.5 Page “C5 Network Design“Calculations of network element quantities are made on this page. The main parts of the page are as follows:► Field “eNodeB calculations“► Field “NodeB calculations“► Field “BTS calculations“► Field “Sectors“► Field “Transceiver (TRX)“► Field “Backhaul transmission network“► Field “Base station controller (BSC)“► Field “Transcoder controller (TRC)“► Field “Radio network controller (RNC)“► Field “MSC server (MSS) and media gateway (MGW)“► Field “IP multimedia sub-system (IMS)“► Field “Mobile switching center (MSC)“► Field “Intelligent network (IN)“► Field “Billing IC hardware and software”► Field “Number portability system harware and software”► Field “Voice messaging service (VMS)“► Field “Home location registry (HLR)“► Field “Centralized User Database (CUD)”► Field ”Short messaging service centre (SMSC)“► Field “Multimedia message service centre (MMSC)“► Field “Packet control unit (PCU) and Serving GPRS support node (SGSN)“► Field “Evolved Packet Core network”► Field “Core transmission network“

1.4.5.1 Field “eNodeB calculations“eNodeB calculations are the modelling part of elements of LTE radio network. These calculations are classified into five parts described below. 1. Cells to meet voice capacity requirements

A. Total voice traffic capacity to be handled by LTE network by geographical areas is first calculated in this part. Here total BH traffic in Erlangs is split into different area types. The traffic split is calculated by multiplying the total BH traffic in Erlangs (“D4 Network Statistics“, line 62) by the traffic proportion for each area type (“D4 Network Statistics“, lines 67-69).

B. Secondly, capacity to be handled by cell types is calculated. The capacity by geographical areas described in part A is multiplied by the respective LTE network proportions by cell types (“D4 Network Statistics“, lines 71-79).

C. Thirdly, the results received in part B are multiplied by the VoIP codec (“D2 Service Statistics, cell E97) in order to calculate capacity of voice traffic to be handled by cell types in kbps. Moreover, total data traffic capacity to be handled by LTE network by geographical areas is calculated by multiplying total BH Mbytes (“D4 Network Statistics“, line 63) by the traffic proportion for each area type (“D4



Network Statistics“, lines 67-69). Finaly BH Mbytes, to be handled by each geopraphical area, are converted into kbps (lines 45-47)

D. Here, total data traffic capacity to be handled by LTE network in kbps is splitted for each cell in each geographical areas by multiplying results in section C lines 45-47 by the respective LTE network proportions by cell types (“D4 Network Statistics“, lines 82-89).

E. In this section, capacity to be handled by cell types of voice and data downlink and uplink traffic in LTE network is estimated. Estimations are done by summing the results of sections C and D while correcting data traffic by the upload/download ratio (“D4 Network Statistics“, line 64).

F. Finally, the number of sectors to meet capacity requirements is calculated by dividing the results received in part E by the optimal LTE macrocell sector capacity (“C4 LTE pre-Design“, lines 129-131) and rounding the result to the higher integer number.

Calculations provided in the first part are performed coherently, next calculation is performed only when the previous is finished.2. Sites to meet capacity requirements

A. Firstly, the number of sites to meet capacity requirements in urban area is calculated. It is calculated by multiplying the final results in point 1.F of this Documentation by the respective sectorization statistics provided in D4 “Network statistics” lines 93-110.

B. Secondly, the number of sites to meet capacity requirements in suburban area is calculated. It is calculated by multiplying the final results in point 1.F of this Documentation by the respective sectorization statistics provided in D4 “Network statistics” lines 93-110.

C. Thirdly, the number of sites to meet capacity requirements in rural area is calculated. It is calculated by multiplying the final results in point 1.F of this Documentation by the respective sectorization statistics provided in D4 “Network statistics” lines 93-110.

D. Finally, the site quantities are summed up by a certain cut and the total number of sites to meet capacity requirements is received.

Calculations provided in the second part are performed coherently, next calculation is performed only when the previous is finished.3. Adjustment to number of sites due to coverage requirements

A. First, the area to be covered by LTE network is calculated by multiplying the total territory (page “D4 Network Statistics”, line 10), proportion of the LTE coverage and the proportion of the geographical area.

B. Second, the values of optimal eNodeB cell range according to geographical regions are transferred (C4 “LTE pre-Design”, lines 123-125).

C. Third, the coverage of a cell by geographic areas is calculated according to the hexagon area formula.

D. Finally, adjustment to the number of sites by geographical area is calculated by dividing areas described in point A by the coverage of cell (results of point C).

Calculations provided in the third part are performed coherently, next calculation is performed only when the previous is finished.4. Total number of sites



In this section the total number of eNodeB sites is calculated in accordance to the types of cells and geographical areas.5. Total number of sectors

A. First, a section of the number of sites in an urban area is prepared according to cell types and levels of sectorization.

B. Second, a section of the number of sites in suburban area is prepared according to cell types and levels of sectorization.

C. Third, a section of the number of sites in rural area is prepared according to cell types and levels of sectorization.

D. In this section an average number of sectors per site (macro cells) is calculated according to geographical areas. Assumptions on average number of sectors per site are transferred for microcells and picocells from the page “D4 Network Statistics”.

E. Finally, total number of sectors is calculated by cell types.Calculations provided in the fifth part are performed coherently, next calculation is performed only when the previous is finished.

1.4.5.2 Field “NodeB calculations“NodeB calculations are the modelling part of elements of UMTS radio network. These calculations are classified into six parts described below. 1. Cells to meet voice capacity requirements

A. Total capacity to be handled by UMTS network by geographical areas is first calculated in this part. It is calculated by multiplying the UMTS coverage proportion (“D4 Network Statistics“, lines 120-122) of a specific geographical area by the voice and video service traffic in Erlangs (total UMTS network traffic without packet data traffic, “D4 Network Statistics“, line 115).

B. Secondly, capacity to be handled by cell types is calculated. The capacity by geographical areas described in part A is multiplied by the respective UMTS network proportions by cell types (“D4 Network Statistics“, lines 124-132).

C. Thirdly, the results received in part B are multiplied by the NodeB sector operational allowance in BHT accordingly by cell types (“D3 Headroom allowance“, lines 9-15).

D. The values of assumptions on sector capacity in UMTS network by cell types are transferred in this part.

E. Finally, the number of sectors to meet capacity requirements is calculated by dividing the results received in part C by the respective part D results and rounding the result to the higher integer number.

Calculations provided in the first part are performed coherently, next calculation is performed only when the previous is finished.2. Cells to meet data capacity requirements

A. Firstly, total capacity to be handled by UMTS network (BHMB) is calculated by geographical areas. It is calculated by multiplying UMTS coverage proportion of a specific geographical area (“D4 Network Statistics”, lines 120-122), packet data traffic in BH megabytes in UMTS network (“D4 Network Statistics”, line 116) and adjusting the data with upload/download ratio, HSDPA presence and operational allowance statistics.

B. Secondly, capacity to be handled by cell types is calculated. The capacity by geographical areas described in part A is multiplied by the respective UMTS network proportions by cell types (“D4 Network Statistics“, lines 135-142).



C. Thirdly, the results received in part B are recalculated to the number of kbps.D. The values of assumptions on sector capacity in UMTS network by cell types are

transferred in this part.E. Finally, the number of sectors to meet capacity requirements is calculated by

dividing the results received in part C by the respective part D results and rounding the result to the higher integer number.

Calculations provided in the second part are performed coherently, next calculation is performed only when the previous is finished.3. Sites to meet capacity requirements

A. Firstly, the number of sites to meet capacity requirements in urban area is calculated. It is calculated by adding up the respective results described in points II.1.E and II.2.E of field “NodeB calculations”. Macro cell quantities are distinguished by different sectorization levels.

B. Secondly, the number of sites to meet capacity requirements in suburban area is calculated. It is calculated by adding up the respective results described in points II.1.E and II.2.E of field “NodeB calculations”. Macro cell quantities are distinguished by different sectorization levels.

C. Thirdly, the number of sites to meet capacity requirements in rural area is calculated. It is calculated by adding up the respective results described in points II.1.E and II.2.E of field “NodeB calculations”. Macro cell quantities are distinguished by different sectorization levels.

D. Finally, the site quantities are summed up by a certain cut and the total number of sites to meet capacity requirements is received.

Calculations provided in the third part are performed coherently, next calculation is performed only when the previous is finished.4. Adjustment to number of sites due to coverage requirements

A. First, the area to be covered by UMTS network is calculated by multiplying the total territory (page “D4 Network Statistics”, line 10), proportion of the UMTS coverage and the proportion of the geographical area.

B. Second, the values of assumptions on NodeB cell range according to geographical regions are transferred.

C. Third, the coverage of a cell by geographic areas is calculated according to the hexagon area formula.

D. Finally, adjustment to the number of sites by geographical area is calculated by dividing areas described in point A by the coverage of cell (results of point C).

Calculations provided in the forth part are performed coherently, next calculation is performed only when the previous is finished.5. Total number of sites

In this section the total number of NodeB sites is calculated in accordance to the types of cells and geographical areas.6. Total number of sectors

A. First, a section of the number of sites in an urban area is prepared according to cell types and levels of sectorization.

B. Second, a section of the number of sites in suburban area is prepared according to cell types and levels of sectorization.



C. Third, a section of the number of sites in rural area is prepared according to cell types and levels of sectorization.

D. In this section an average number of sectors per site (macro cells) is calculated according to geographical areas. Assumptions on average number of sectors per site are transferred for microcells and picocells from the page “D4 Network Statistics”.

E. Finally, total number of sectors is calculated by cell types.Calculations provided in the sixth part are performed coherently, next calculation is performed only when the previous is finished.

1.4.5.3 Field “BTS Calculations”BTS calculations are treated as the modelling of radio elements of GSM network. This field is subdivided into the following 11 points:1. Area covered by GSM cell

In this section the coverage of a cell area by geographic areas is calculated according to the hexagon area formula.2. Area to be covered by GSM network by typeIn this section the area covered by GSM network is calculated by geographical areas.3. Number of sites required to cover different area typesThe number of macro sites required to meet coverage requirements is calculated by dividing the results of point 2 by the respective results of point 1. The amount of microcells and picocells to meet the coverage requirements is equalled to zero, because the amount of such cells is driven by the traffic in the Network.4. Sector capacity calculationsCalculations in this section are made for single band – 900 MHz (H column) and for dual band – 1800 MHz (column I).

A. The spectrum capacity of a single band logical sector (amount of transceivers) is calculated based on the formula No. 27, defined in Reference paper, dual band – based on the formula No. 28, defined in Reference paper.

B. Physical capacity of single band logical sector (amount of transceivers) in macro cells is calculated by withdrawing 0.5 from an assumption of physical capacity sector, described in line 235 of the page “D4 Network Statistics”. For micro and pico cells the respective assumptions on physical capacity of spectrum are transferred.The physical capacity of dual band logical sector (amount of transceivers) for macro cells is calculated by adding the difference between an assumption of physical capacity sector, described in line 235 of the page “D4 Network Statistics” and 0.5 to a single band logical sector physical capacity. Respective assumptions of physical capacity are in ordinary manner transferred for microcells and picocells.

C. Effective sector capacity (amount of transceivers) is evaluated by choosing a lower value from the values of spectrum capacity of a logical sector (result of point III.4.A) and the physical capacity of a logical sector (result of point III.4.B).

D. Capacity of the sector is calculated according to the table of Erlangs. 5. Total busy hour trafficIn this section the total traffic in GSM network is calculated (in Erlangs) and its distribution according to geographical areas is calculated by multiplying the total traffic by the proportion of GSM coverage in a specific geographical area (lines 151-153 of a “D4 Network Statistics” page).6. Detailed traffic by cell types and geographical areas



In this section the traffic in GSM network is presented by different cell types and geographical areas.7. Number of sectors required to service the trafficIn this section the number of sectors is evaluated according to cell types and geographical areas. These amounts are calculated by dividing the traffic, defined in point 6, by sector capacity, which is calculated in section III.4.D and by a operational allowance of a respective cell equipment (lines 10-11 of the page “D3 Headroom Allowance”). For pico cells calculations there are used the parameters of micro cells from page „D3 Headroom Allowance“.8. Number of base transceivers stations per number of sectors usedIn this section number of base stations of macro cells is evaluated according to geographical areas and levels of sectorization. It is calculated by multiplying the results of this section’s point 7 by respective cells proportions according to sectors and geographical areas, and by dividing the result by a certain amount of sectors (depending on the level of sectorization).9. Final number of base transceivers stationsSingle/dual band filter is a table of single and dual bands presence in a certain geographical region. The amount of final base stations is produced by multiplying respective values of filter table by the amount of base stations calculated in this section’s point 8.10. Number of base transceivers stations by number of sectorsIn this section amounts of base stations are presented in more detail by additionally segregating them by levels of sectorization.11. Number of sites by typeIn this section a number of total BTS stations is provided according to cell type and geographical area. Amounts sorted in this manner are further used in this model for calculation of page “C4 Revaluation”.

1.4.5.4 Field “Sectors”In this field amounts of sectors are analysed in detail. These are preliminary tables of TRX amount calculation.1. Average number of sectors per BTS In this section an average number of sectors is calculated in macro cells according to geographical areas. Assumptions of average number of sectors per site are transferred for microcells and picocells from the page “D4 Network Statistics”.2. Number of sectorsIn this section a total number of sectors is calculated by multiplying III.9 results by an average number of sectors per site (results of this section’s point 1).

1.4.5.5 Field “Transceiver (TRX)“In this field the number of transceivers required to service the traffic is calculated. Calculations are performed step-by-step as defined below:1. Average traffic per sector (Erl) is calculated by dividing the values, defined in point 6 of

the field “BTS Calculations”, by the number of sectors according to respective types of cells.

2. TRX per sector required to service the trafficA. The number of TRX per sector required to service the traffic is calculated by dividing

the average traffic per sector (Erl) by the proportion of TRX cards operational allowance (M9 cell of page “D3 Headroom Allowance”), and by recalculating the results received to the number of TRX, based on the table of Erlangs.



B. If respective sector amounts (lines 618-622) exceeds zero value, a minimal number of TRX per sector according to cell types is equal to 1, otherwise the minimal number of TRX per sector according to cell types is equal to 0.

C. The number of TRX per sector required to service the traffic is evaluated by selecting a higher value from TRX number per sector required to service the traffic (result of point A) and a minimal amount of TRX per sector (result of point B) .

3. Total number of TRX according to cell types and geographical areas is equal to the product of the number of TRX per sector required to service the traffic (result of V.2.C) and the number of sectors (respective cell value, calculated in lines 618-620).1.4.5.6 Field “Backhaul transmission network“

Lines 674–907 define the proportions of ETH types and amounts in a backhaul transmission network. Calculations are divided into three parts:► Backhaul (eNodeB–GGSN transmission) (lines 676-715)► Backhaul (NodeB–RNC transmission) (lines 717-804)► Backhaul (BTS–BSC transmission) (lines 806-846)► Backhaul combined transmission (lines 848-907)

1. One main parameter is calculated in section eNodeB–GGSN: the number of LTE sites according to separate types of territories, cells and sectors (cells F688 – F699). The data received is used in calculating the total LTE sites throughput, which is used in defining the parameter of average throughput per site (cell F867).

Throughput per LTE sector according to separate types of territories, cells and sectors (cells F680 – F684), is taken from “C4 LTE pre-Design” sheet and number of sites with microwave backhaul transmission, according to separate types of territories, cells and sectors, are taken from eNodeB calculations part of the field “C5 Network design” part I.5.

2. Two main parameters are calculated in section NodeB–RNC: the throughput per UMTS site according to separate types of territories, cells, sectors is calculated to meet voice and data demands as well as overall demand (cells F721 – F727, F746 - F750, F769 - F773), and the number of UMTS sites according to separate types of territories, cells and sectors is calculated to meet voice and data demands as well as overall demand (cells F731 – F742, F754 – F765, F777- F788). The data received is used in calculating the total UMTS sites throughput, which is used in defining the parameter of average throughput per site (cell F868).

Number of sites with microwave backhaul transmission, according to separate types of territories, cells and sectors, are taken from NodeB calculations part of the fields“C5 Network design”, part II.6.3. Two main parameters are calculated in section BTS–BSC: the throughput of GSM site according to separate types of territories, cells and sectors (cells F809- F815), and the number of GSM sites according to separate types of territories, cells and sectors (cells F819 – F830). The data received is used in calculating the total GSM sites throughput, which is used in defining the parameter of average throughput per site (cell F869).Number of sites with microwave backhaul transmission, according to separate types of territories, cells and sectors, are taken from BTS calculations part of the fields“C5 Network design”, part III.10.4. In the third section (Backhaul combined transmission) primarily the total (LTE, GSM and UMTS) amount of sites is calculated (cell F864). The total amount of sites is calculated by summing numbers of sites, according to separate types of territories, cells and sectors (cells F853 – F863). The total amount of sites, laid down in cells F853 – F863, according to separate types of territories, cells and sectors are settled by the higher value between LTE sites (cells F704 - F714), UMTS sites (cells F793 - F803) and GSM sites (cells F835 – F845).



When all necessary parameters are known, the average throughput per site is calculated (cell F866).In cells F877 – F880 the link capacity of all types of microwaves is calculated, presuming that the basic capacity of a microwave 2 Mbit/s is equal to 2048 kbit/s (cell F875).According to the average throughput per site (cell F866) and the link capacity of all types of microwaves (cells F877 - F880), in cells F884 – F887 the maximum amount of sections is calculated which might be connected to respective ETH microwave type in a transmission network link.In cells F889 – F892 the amount of sections, which might be connected to a respective ETH microwave type in a transmission network link, is settled. The number of sections is settled by choosing lower value from cells F884 – F887 and from average number of sites per link (cell F871). According to the parameters calculated the proportions and amounts of ETH types in backhaul transmission network are settled in cells F897 – F900 and F902 – F905.In cell F907 an amount of stand-alone microwaves sites is calculated by multiplying the proportion of additional ETH microwaves (data input page D4 Network Statistics, cell F265) by the total amount of ETH microwaves (by summing up values of cells F902 – F905).

1.4.5.7 Field “Base station controller (BSC)“The calculation of the number of base station controllers is made up of four lines:► The number of TRXs (calculations are defined in section 1.4.5.5 Field “Transceiver

(TRX)“)► BSC capacity (amount of TRXs) is calculated in cell Q21 of the page “D3 Headroom

Allowance”.► The number of BSC basic units is calculated dividing the number of TRX by BSC

maximal operational capacity and rounding the number received to the higher number.► The number of BSC extension units is calculated according to the algorithm, defined

in the Reference paper formula No. 65 if the operational capacity of BSC extension unit and the number of BSC extension units is not equal to zero, otherwise there are no BSC extension units.1.4.5.8 Field “Transcoder Controller (TRC)“

The calculation of the number of transcoder controller is made up of seven lines:► TRC A interface capacity (E1) is calculated in cell Q22 of the page “D3 Headroom

Allowance”.► BSC total number of interfaces (E1) is calculated dividing total throughput by the

basic 2 Mb/s link capacity (line 875).► BSC Asub interface (E1) here a number of Asub interfaces (E1) is calculated.► TRC compression rate is an assumption presented in the Reference paper.► BSC A interface (E1) is equal to the multiplication of TRC compression rate and a total

BSC Asub interfaces (E1).► The number of TRC basic units is calculated dividing total amount of BSC Asub

interfaces (E1) by maximal TRC operational capacity and rounding the received number to the higher number.

► The number of TRC extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of TRC extension units and the number of TRC basic units is not equal to zero, otherwise there are no TRC extension units.



1.4.5.9 Field “Radio Network Controller (RNC)“The number of radio network controller depends on the capacity of Iub interface

(Mbit/s), an amount of sectors in UMTS network and an amount of NodeB sites. A table of RNC number calculation is divided into the following three parts:► Maximal operational capacity of RNC components (cells Q27 - Q29 of page “D3

Headroom Allowance“)► Demand of RNC components in a modelled network:

► Iu-CS link throughput is calculated by multiplying cells 731-741 by cells 793-803 and dividing it by Basic 2 Mb/s link capacity in [kbit/s].

► Iub link throughput is calculated by multiplying cells 777-787 by cells 793-803 and dividing it by Basic 2 Mb/s link capacity in [kbit/s].

► Total number of sectors in UMTS network is calculated in line 408 and defined under section 1.4.5.2 Field “NodeB calculations“.

► Total number of sites is calculated in line 371 and defined under section 1.4.5.2 Field “NodeB calculations“.

► The number of RNC basic and extension units ► The number of RNC basic units is calculated dividing number of RNC component

demand by respective maximal operational capacities and choosing the highest number and rounding it to the higher number.

► The number of RNC extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of RNC extension units and the number of RNC basic units is not equal to zero, otherwise there are no RNC extension units.

1.4.5.10 Field “MSC server (MSS) and media gateway (MGW)“This table consists of calculation tables of MCS server (lines 951-959) and media

gateways (lines 962-987).

MSC server

In lines 951-956 there are model assumptions and preparation calculations laid down. In lines 958 and 959 calculations are made as follows:► Number of MSS is evaluated based on minimal network requirements (assumption

provided in Reference paper) and traffic requirements. The number of MSS basic units, needed to handle specific amount of busy hours call attempts (BHCA) in 3G core network is calculated by dividing BHCA amount by maximal amount of MSS processor capacity (product of CPU in one MSS and cell Q31 of the page “D3 Headroom Allowance”). Thus, the number of MSS basic units equals to a higher number from the minimal MSS number and number of MSS, which is required to process BHCA (traffic requirements).

► Number of MSS extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of MSS extension units and the number of MSS basic units is not equal to zero, otherwise there are no MSS extension units .

MGW

In lines 962-981 there are model assumptions and preparation calculations laid down. In lines 983-987 MGWs amount calculations are done, which are described down below.

As defined in Reference paper section 10.5.3 Media Gateway, the number of MGW depends on minimal network requirements (it is assumed that there should be at least one MGW), traffic and ports requirements. The calculations of MGWs, made to meet traffic requirements, are adequate to those of MSS by incorporating respective values of MGW elements.



In the process of modelling MGW number to meet ports requirements, quantities of three types of ports are calculated:► RNC-facing ports. Their number is calculated by multiplying the BSC A interfaces (E1)

by the proportion of traffic in the MSS/MGW core network and adding Iu-CS links (E1) (cell F937).

► Interconnect-facing ports (line 974). This amount is calculated by dividing interconnect traffic in Erlangs by 0.7 and 31.

► Interswitch-facing ports (line 977). This number is calculated by dividing the traffic of interswitch facing ports by 0.7 and 31.

Summing up the numbers of ports the number of total required MGW ports is received. The number of MGW to meet ports requirements is calculated dividing the above mentioned number by maximal operational capacity of ports (cell Q32 of the page “D3 Headroom Allowance”) and rounding it to the higher number.Number of MGW ports extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of MGW extension units and the number of MGW basic units is not equal to zero, otherwise there are no MGW extension units.In conclusion, the number of MGW basic units in all the network is evaluated by choosing the highest number from MGW number as an assumption of minimal network requirements, MGW number to meet traffic requirements and MGW number to meet port requirements (results are in line 987).

1.4.5.11 Field “IMS“As defined in Reference paper section 10.5.6 IP multimedia sub-system the IP multimedia sub-system is used to provide services for LTE subscribers. Therefore the amount of IMS depends on LTE subscribers traffic and if in “Intro” sheet IMS dimensioning is selected. IMS elements (lines 992-1015) are dimensioned to handle the amount of BHE, BHCA and subscribers of LTE network. Detailed descriptions and formulas, according to which the elements of IMS system is dimensioned are described in Reference paper section 10.5.6 IP multimedia sub-system

1.4.5.12 Field “Mobile switching center (MSC)“As defined in Reference paper section 10.5.1 Mobile Switching Center the amount of MSC depends on minimal network requirements (it is assumed that there should be at least two MSCs, line 1022), CPU, ports and VLR part requirements.MSC number of CPU part is calculated adequately to the previously mentioned MSS by using respective values of MSC values. In the process of modelling MSC number to meet ports requirements, quantities of three types of ports are calculated:► BSC-facing ports. Their number is equal to total 2Mbit/s link capacity (E1 A interface),

calculated in a TRC table (line 926).► Interconnect-facing ports (line 1038). This number is calculated by dividing

interconnect traffic in MSC in Erlangs by 0.7 and 31. ► Interswitch-facing ports (line 1042). This number is calculated by dividing the traffic

of MGW/tandem-facing ports by 0.7 and 31.Summing up the numbers of ports the number of total required MSC ports is received. The number of MSC to meet ports requirements is calculated dividing the above mentioned number of ports by maximal operational capacity of slots (cell Q26 of the page “D3 Headroom Allowance”) and by rounding it to the higher number.Number of MSC ports extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of MSC extension units and the number of MSC basic units is not equal to zero, otherwise there are no MSC extension units.



Number of SS7 links in a MSC is calculated by dividing the number of inter-switch (line 1042) and interconnection facing ports (line 1038) by the number of trunks per SS7 link (line 1055).Number of SS7 extension units (line 1058) is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of SS7 extension units and the number of SS7 basic units is not equal to zero, otherwise there are no SS7 extension units.MSC number of VLR part (lines 1060-1063) is calculated by dividing the number of GSM users by maximal operational capacity of VLR (cell Q24 of the page “D3 Headroom Allowance”) and by rounding the result number to the higher number.Number of VLR extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of VLR extension units and the number of VLR basic units is not equal to zero, otherwise there are no VLR extension units. Results are presented in line 1067.In conclusion, the total number of MSC basic units (line 1069) in all the network is evaluated by choosing the highest number from MSC number as an assumption of minimal network requirements, CPU part, ports part and the number of VLR part.

1.4.5.13 Field “Intelligent network (IN)“In this section number of Service Control Point (SCP), an intelligent network part,

is calculated. It depends on the number of pre-paid subscribers and on the busy hour transactions number per second. The calculations of such amounts are defined below:► Number of SCP to meet subscribers demand (line 1077) is calculated by dividing

the number of pre-paid subscribers by maximal operational capacity of SCP (cell Q48 of the page “D3 Headroom Allowance”).

► Number of SCP extension units to meet subscribers demand (line 1088) is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of SCP extension units to meet subscribers demand and the number of SCP basic units is not equal to zero, otherwise there are no SCP extension units to meet subscribers demand.

► Number of SCP to meet traffic demand (line 1084) is calculated by dividing the amount of BH transactions per second by maximal SCP operational capacity for the traffic demand (cell Q49 of the page “D3 Headroom Allowance”).

► Number of SCP extension units to meet traffic demand (line 1090) is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of SCP extension units to meet traffic demand and the number of SCP basic units is not equal to zero, otherwise there are no SCP extension units to meet traffic demand.

► Number of SCP basic units is calculated by choosing the highest number from the amount of SCP to meet subscribers demand and the amount of SCP to meet traffic demand. Calculation presented in line 1086.1.4.5.14 Field “Billing IC hardware and software“

It is assumed that one Billing IC hardware and software is enough to support the services. Therefore, the only relevant calculation made in lines 1094-1100 is calculation of the overall Busy hour call attempts in the network. Later in the model, this amount of BHCA is used to add the cost of billing system proportionally to the service depending of the BHCA driven by the service.

1.4.5.15 Field “Number portability system harware and software“It is assumed that one number portability system harware and software is enough to support the services. Therefore, the only relevant calculation made in lines 1102-1110 is calculation of the busy hour call attempts in MSC/MGW or SMSC or MMSC or SGSN network elements. Later in the model, this amount of BHCA is used to add the cost of number portability system proportionally to the service depending of the BHCA driven by the service.



1.4.5.16 Field “Voice messaging service (VMS)“The calculation of voice messaging service units consists of four lines:► Number of subscribers (here is placed for additional required data for calculation)► Capacity of the VMS (mailboxes) is calculated in cell Q50 of the page “D3 Headroom

Allowance”.► Number of VMS basic units is calculated dividing the number of subscribers by VMS

maximal operational capacity (mailboxes) and rounding the number received to the higher number.

► Number of extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of VMS extension units and the number of VMS basic units is not equal to zero, otherwise there are no VMS extension units.1.4.5.17 Field “Home location registry (HLR)“

The calculation of the number of home location registry consists of four lines:► Number of subscribers (here is placed for additional required data for calculation)► Capacity of the HLR (subscribers) is calculated in cell Q51 of the page “D3

Headroom Allowance”.► Number of HLR basic units is calculated dividing the number of subscribers by HLR

maximal operational capacity and by rounding the number received to the higher number.

► Number of extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of HLR extension units and the number of HLR basic units is not equal to zero, otherwise there are no HLR extension units.1.4.5.18 Field “Centralized User Database (CUD)“

The calculation of the number of centralized user database consists of four lines:► Number of subscribers (here is placed for additional required data for calculation)► Capacity of the CUD (subscribers) is calculated in cell Q52 of the page “D3

Headroom Allowance”.► Number of CUD basic units is calculated dividing the number of subscribers by CUD

maximal operational capacity and by rounding the number received to the higher number.

► Number of extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of CUD extension units and the number of CUD basic units is not equal to zero, otherwise there are no CUD extension units.1.4.5.19 Field “Short message service center (SMSC)“

The calculation of the number of short message service center consists of five lines:► Number of BH SMS per minute is calculated by dividing the number of Erlangs of

SMS in SMSC by SMS to minute conversion factor.► Number of BH SMS per second is calculated by dividing the number of BH SMS per

minute by 60.► Capacity of the SMSC (BH SMS per second) is calculated in cell Q55 of the page

“D3 Headroom Allowance”.► Number of SMSC basic units is calculated dividing the number of BH SMS per second

by SMSC maximal operational capacity and rounding the number received to the higher number.

► Number of extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of SMSC extension units and



the number of SMSC basic units is not equal to zero, otherwise there are no SMSC extension units.1.4.5.20 Field “Multimedia messaging service center (MMSC)“

The calculation of the number of multimedia messaging service center consists of five lines:► Number of BH MMS per minute is calculated by dividing the number of Erlangs of

MMS in MMSC by MMS to minute conversion factor.► Number of BH MMS per second is calculated by dividing the number of BH MMS per

minute by 60.► Capacity of the MMSC (BH MMS per second) is calculated in cell Q56 of the page

“D3 Headroom Allowance”.► Number of MMSC basic units is calculated dividing the number of BH MMS per

second by MMSC maximal operational capacity and rounding the number received to the higher number.

► Number of MMSC extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of MMSC extension units and the number of MMSC basic units is not equal to zero, otherwise there are no MMSC extension units.1.4.5.21 Field “Packet control unit (PCU) and serving GPRS

support node (SGSN)“This table consists of the tables of CPU and SGSN calculations.In calculation of the number of PCU the Gb link throughput (Mbit/s) should be

evaluated first, where busy hour data traffic in GSM and UMTS networks and MMS traffic is recalculated into Mbit/s (line 1166). Then this throughput is divided by maximal operational capacity of PCU, rounded to a higher number and thus the number of PCU basic units (line 1171) is received.

Number of PCU extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of PCU extension units and the number of PCU basic units is not equal to zero, otherwise there are no PCU extension units.

In calculation of the number of SGSN the Gb link throughput (BH packets / sec) should be evaluated first, where Gb link throughput (Mbit/s) is divided by average number of bytes per packet (line 75 in sheet “D2 Service Statistics”) and converted into busy hour packets per second (line 1167). Then this throughput is divided by maximal operational capacity of SGSN, rounded to a higher number and thus the number of SGSN basic units (line 1177) is received.

Number of SGSN extension units is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of SGSN extension units and the number of SGSN basic units is not equal to zero, otherwise there are no SGSN extension units.

1.4.5.22 Field “Evolved Packet Core network“This table consists of the tables of MME and PGW calculations.In calculation of the number of MME the Gb link throughput (Mbit/s) should be

evaluated first, where busy hour data and voice traffic in LTE network is recalculated into Mbit/s (line 1183). Then this throughput is divided by maximal operational capacity of MME and average data session length, rounded to a higher number and thus the number of MME basic units (line 1188) is received.

Number of MME extension units (line 1190) is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of MME extension units and the number of MME basic units is not equal to zero, otherwise there are no MME extension units.



In calculation of the number of PGW the Gb link throughput (BH packets / sec) should be evaluated first, where Gb link throughput (Mbit/s) is divided by average number of bytes per packet (line 75 in sheet “D2 Service Statistics”) and converted into busy hour packets per second (line 1184). Then this throughput is divided by maximal operational capacity of PGW, rounded to a higher number and thus the number of PGW basic units (line 1194) is received.

Number of PGW extension units (line 1196) is calculated according to the algorithm, defined in the Reference paper formula No. 65 if the operational capacity of PGW extension units and the number of PGW basic units is not equal to zero, otherwise there are no PGW extension units.

1.4.5.23 Field “Core ETH transmission“In this section an algorithm and the result of the number of ETH microwave in

core network is presented. The total number of EPC, BSC and RNC is presented in a cell F1200 and the number of MSC/MGW/PGW – in a cell F1201. These numbers are calculated in previous sections.

In cells F1206 - F1207 the distribution of the total demand for capacity of BSC/RNC/EPC – MGW/EPC ETH radiolinks and leased lines is settled. This is defined by the proportions of transmission network (input parameters page – D4 Network Statistics, F283 – F284), provided by Operators.

In cells F1219 and F1220 the number of radiolinks and leased lines for BSC/RNC/EPC – MGW/EPC section, in order to meet the required capacity demand, is calculated based on the settled parameters.

In cell F1222 the amount of additional stand-alone microwave sites is calculated by multiplying the additional proportion of ETH (page of data input D4 Network Statistics, cell F268) by the total amount of ETH radiolinks (cell F1219).

In cell F1226 the total demand for capacity of MGW/MSC – MGW/MSC transmission is estimated and in cell F1232 the number of GE leased lines is determined to meet the estimated demand.1.4.6 Page “C6 Revaluation“

In this calculations’ page the current value of the network is established and investments received are converted to annual values.

Column B “HCC name” contains HCC groups and their components. Column D “Volumes” contains amounts of network elements, which are settled in calculations’ page C5 Network Design. Column E “Unit costs, total (LTL)” contains values of network elements, their values are taken from the page of input parameters “D5 HCC data”. Column F (Total GRC (LTL)) contains the result of multiplication of columns D and E, i.e. gross replacement cost (GRC). Column G (Total GRC (LTL) + NMS) contains the total GRC value with network management system mark-up added to it.

As previously mentioned, the investments are converted to annual values. This calculations’ page includes three methodologies of investments conversion to annual values. Column H “Annuity” contains annuity method, column I “Tilted annuity” – method of tilted annuity, column J “Straight-line” – straight line depreciation method. All three methods are described in Reference paper. Column K (Method chosen) contains annual values, which are calculated by the method selected in the “Intro” sheet, line 13.1.4.7 Page “C7 Mark-ups”

In this page of calculations, mark-ups to cover common costs are added to annual network investment values, defined in the page of calculations “C4 Revaluation”.

Column B (HCC name) contains HCC groups and their components. Column C “Total GRC+NMS (LTL)” contains respective GRC values of network elements from the page of calculations “C4 Revaluation”, column G “Total GRC+NMS (LTL)”. Column D “Yearly cost



before mark-ups” contains annual values of network investment, calculated in column K of the calculations’ page “C4 Revaluation”.

Columns E, F and G settles mark-ups, defined in section 11.2 in the Reference paper, to cover common costs: ► Column E (OPEX) include the values of mark-ups to cover common costs, which are

calculated by multiplying the respective GRC value (column C) by a respective mark-up to cover common costs (page of input parameters “D6 Mark-ups”, cells D11-D14).

► Column F (OPEX administration and support) contain the values of mark-ups to cover administration and maintenance operating costs, which are calculated by multiplying the value of operational costs (column E) by mark-up to cover operating costs for administration and maintenance (page of input parameters “D6 Mark-ups”, cell D24).

► Column G (CAPEX administration and support) contain values of mark-up to cover costs of capital for administration and maintenance, which is calculated by multiplying respective values of operating costs (column E) by mark-up to cover costs of capital for administration and maintenance (page of input parameters “D6 Mark-ups”, cell D27).

In column I (Yearly costs after mark-ups) annual network investments with mark-ups to cover common costs are calculated by adding up the values of columns D, E, F and G.1.4.8 Page „C8 HCC – NC“

In this calculation page consists of three parts:► Allocation on Network Components;► Cost of Network Components;► Cost of Network Components - Service increment.

1.4.8.1 Field “Allocation on Network Components “Here HCC annual cost allocation to network components and network service unit

costs assigned to particular network component is provided. In column B “HCC name” HCC groups and its components are provided. In column

C “Yearly cost” network elements’ annual cost are provided from calculation page “C7 Mark - ups” column H. These costs are distributed to network components. Network components are provided in F5 – S5 cells. Annual costs for network components are distributed in this calculation page’s cells, indicating percentage of costs to particular network component.

1.4.8.2 Field “Cost of Network Components “In this section, total network costs as well as network costs of different scenarios are calculated in order to estimate incremental costs and common costs.

In line 130 total network component costs are calculated, summing assigned annual costs to a particular network component. This cost represents cost of a fully functioning network.

The results presented in lines 132 - 136 of worksheet C8 HCC-NC are calculated by Visual Basic subroutines. Such approach simplifies the model and allows to replace the number of manual operations by automatized function.

Operations made by automatized function are used to recalculated the model several times in row with different input parameters and save the results of calculation in appropriate lines. In general function copies the result from line 130 and paste it the one of the lines 132 – 136. ► Line 132 – presents cost of NC when providing all group of services.

Values presented in this line are copied from line 130, assuming that network is providing all groups of services i.e. data, voice and access. The provision of a particular



group of service can be set in cells C130 – E130, where cell C130 presents data services, cell D130 presents voice services and cell E130 present access services. Value 100% set in one of the listed cells mean that the group of services is provide and value 0% mean that services is not provided. In this case all cells C130 – E130 are set to 100%.

► Line 133 – presents cost of NC when providing only access services;Values presented in this line are copied from line 130, assuming that network is providing only access services and data and voice services are not provided. In this case all cells C130 – D130 are set to 0% and cell E130 is set to 100%.

► Line 134 – cost of NC when providing only voice and data services; Values presented in this line are copied from line 130, assuming than network is providing data and voice services and access services are not provided. In this case all cells C130 – D130 are set to 100% and cell E130 is set to 0%.

► Line 135 - cost of NC when not providing voice services; Values presented in this line are copied from line 130, assuming than network is providing data and access services and voice services are not provided. In this case all cells C130 and E130 are set to 100% and cell D130 is set to 0%.

► Line 136 - cost of NC when not providing data services; Values presented in this line are copied from line 130, assuming than network is providing voice and access services and data services are not provided. In this case all cells D130 and E130 are set to 100% and cell C130 is set to 0%.

In lines 138 – 141, estimation of incremental costs related to traffic, access, voice traffic and data traffic are estimated by subtracting appropriate total network costs estimated in lines 132 – 136 by VBA subroutines. Using these incremental cost estimations, common costs of the network are estimated in lines 143 – 149

Finally, in line 153 network component unit costs according to LRAIC+ are estimated by calculating the network component voice incremental costs and dividing the costs by the total network demand.

And in line 157 network component unit costs according to LRAIC++ are estimated by calculating the network component voice traffic incremental costs and adding the voice traffic common costs and further dividing the result by the total network demand.

1.4.8.3 Field “Cost of Network Components - Service increment “In this section the network component costs according to Pure LRAIC are

estimated.The results presented in lines 161 - 165 of worksheet C8 HCC-NC are calculated

by Visual Basic subroutines. Such approach simplifies the model and allows to replace the number of manual operations by automatized function.

Operations made by automatized function are used to recalculated the model several times in row with different input parameters and save the results of calculation in appropriate lines. In general function copies the result from line 130 and paste it the one of the lines 161 - 165. ► Line 161 - cost of NC when not providing off-net services;

Values presented in this line are copied from line 130, assuming than network is not providing off-net services and all other services are provided. In this case volume of off-net minutes in worksheet “C1 Demand” is set to zero, by changing the values in line 124 to “0”.



► Line 162 - cost of NC when not providing voice termination services; Values presented in this line are copied from line 130, assuming than network is not providing voice termination services and all other services are provided. In this case volume of incoming minutes in worksheet “C1 Demand” is set to zero, by changing the values in line 125 to “0”.

► Line 163 - cost of NC when not providing voice transit services; Values presented in this line are copied from line 130, assuming than network is not providing voice transit services and all other services are provided. In this case volume of transit minutes in worksheet “C1 Demand” is set to zero, by changing the values in line 126 to “0”.

► Line 164 - cost of NC when not providing SMS services; Values presented in this line are copied from line 130, assuming than network is not providing SMS services and all other services are provided. In this case volume of SMS minute equivalents in worksheet “C1 Demand” are set to zero, by changing the values in lines 132 - 134 to “0”.

► Line 165 - cost of NC when not providing MMS services; Values presented in this line are copied from line 130, assuming than network is not providing MMS services and all other services are provided. In this case volume of MMS minute equivalents in worksheet “C1 Demand” are set to zero, by changing the values in lines 136 - 138 to “0”.

In lines 167 – 171 the demand of each service is trasfered. Lastly, in lines 173 – 177 network component unit costs according to Pure LRAIC.

Here apporiate service traffic is calculated and divided by the service demand.1.4.9 Page „ C9 NC-Services“

The final results are calculated in this calculation page – LRAIC++ unit cost (cells D10 – D21), LRAIC+ unit costs (cells D25 – D36) and Pure LRAIC unit costs (cells D40 – D51). Also, allocation of joint costs of termination are allocated to origination in line 55 for LRAIC++ and in line 59 for LRAIC+.

In column B “Service type” modelled network services are provided and in cells H6 – U6 – network components.

In column E service costs in peak hours are calculated. In column F - off-peak .In cells H10:U51 network service units costs, depending on each approach, are

assigned to network components (calculation page „C6 HCC – NC“, lines 161, 156 and 181 - 185) are multiplied by services usage factors ( input parameter page „ D7 Service Matrix“, cells C9:P19). 1.4.10 Page „C10 Erlang“

This page consist of single and dual band erlang tables. Each table has these columns: “Number of channels” (columns B, K ), „Number of TRX“ (columns C, L) and „ Blocking probability “ (columns D-G, M-P).

Erlang table results with specific blocking probability is used to convert number of TRX to number of channels and on contrary.



Appendix A Entry data updating methodologyPage Data Cells Periodicity Data revaluation sourceD1 Service Volumes

Service statistics F10 – R57 Data is updated 1 time in a year

Information is updated according to the data on sold services provided by Operators

D2 Service Statistics

Routing factors F10 – L35 Data is updated 1 time in 2 years

Information is updated by consulting Operators and telecommunication industry experts


Call and call set-up durations

E43 - E45 Data is updated 1 time in a year

Information is updated according to the information provided by Operators and telecommunication industry experts


Completion rates E47 Data is updated 1 time in a year



De-averaging factors E49 – E51 Data is updated 1 time in a year



De-averaging factors F52 – L52 Data is updated 1 time in 2 years

Information is updated according to telecommunication industry experts


SMS/MMS conversion factors

E54 – E56 Data is updated 1 time in a year



Data conversion factors




Video and voice calls conversion factors

E72 – E73 Data is updated 1 time in 2 years

Information is updated according to telecommunication industry experts


Network parameters E75 – E76 Data is updated 1 time in a year




Page Data Cells Periodicity Data revaluation sourceD2 Service Statistics

Peak to off-peak tariff diferentiation


Information is updated according to the information provided by Operators


Priority factors E82 – E83 Data is updated 1 time in a year



VoIP assumptions E86 – E91 Data is updated 1 time in a year



VoIP assumptions - Codec & Bit Rate (Kbps)

E100 – F109

Data is updated 1 time in 2 years



Interconnection ports - voice

E113 – E115

Data is updated 1 time in a year



Interconnection ports – voice IC ports capacity

E118 – E120



D3 Headroom Allowance

Network elements headroom allowance data

F9 – J58 Data is updated 1 time in a year


D4 Network Statistics

Coverage parameters

F10 – F46 Data is updated 1 time in a year



LTE traffic F67 – F89 Data is updated 1 time in a year



LTE sites configuration

F94 – F110





Page Data Cells Periodicity Data revaluation sourceD4 Network Statistics

UMTS traffic F120 – F142




GMS traffic F151 – F163




UMTS cell parameters

F191 – F195




UMTS sites configuration

F200 – F216




BTS capacity F221 – F237




GSM sites configuration

F244 – F261




Transmission F265 – F286




IN transactions number

F291 Data is updated 1 time in 2 years


D5 HCC Data

Current network equipment price

D14 – D133



D5 HCC Data

Useful lifetime G14 – G133





Page Data Cells Periodicity Data revaluation sourceD5 HCC Data

Last five years price index average

H14 – H133



D5 HCC Data

NBV and GBV ratio I14 – I133 Data is updated 1 time in a year


D6 Mark ups

Mark-ups D11 - D27 Data is updated 1 time in 2 years



Documents

Lietuvos Respublikos Ryšių reguliavimo tarnyba - …old.rrt.lt/download/17686/bu_lraic model manual final.docx · Web viewThese parts are distinguished by different page colors: