The Lothians consist of the three former counties of East Lothian, Midlothian and West Lothian. The land is generally low-lying to the north, rising to moorland and hills in the south, with are...
Japanese Pronunciation & GrammarFull description
Tabletop RPG gamemaster resource
Descrição: Tabletop RPG gamemaster resource
Tabletop RPG gamemaster resource
D&D 3.5 edition Guide to to Were\Rats within dungeon and dragons rpg.Descripción completa
Design and Maintenance Guide Pdf fileFull description
Full description
GPS navegador Go to Fic uniDescripción completa
to go beyond
Intermediate EFL Textbook
Language To Go students bookDescripción completa
Technical Challenges & Design Features LNG TankFull description
You want to make a living creating content but you do not have enough fans. So you go viral. To go viral you need to create a piece of content full of emotion. Then find an influencer to aim their ...
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Product Name
Confidentiality Level
GSM BSC6910
Internal Public
Product Version
Total 258 pages
V900R017C00
Technical Guide to SRAN Network Design (GO Applicable to SRAN10.0 & GBSS17.0 & BSC6910) (For internal use only) Prepared By
fuqiang (employee ID:00283077)
Date
2014-07-18
Reviewed By
lishuanghua (employee ID: 00101863)
Date
2014-07-28
Date
2014-09-03
Li Yongqing (employee ID: 00141602) chenyin (employee ID: 00179448) Hu Chunhua (employee ID: 00257638) Approved By
hepeng (employee ID: 00110002)
Huawei Technologies Co., Ltd. All rights reserved
CONFIDENTIAL
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Change History Version
Prepared/Revie wed By
Date
Description
Approved By
V0.1
Li Bo
2012-11-30
Initial draft
Mei Weifeng, Huang Yanzhong
V0.2
Li Bo
2012-12-07
The document is modified according to comments of the delivery department.
Mei Weifeng
V0.3
Li Bo
2012-12-15
The document is modified according to comments of the network information service (NIS) department.
Mei Weifeng
V0.4
Li Bo
2012-12-22
The document is modified according to review comments.
Mei Weifeng
V0.5
Li Bo
2013-2-4
Section 18.2.2"Design Examples" is modified.
Songruining
V0.6
Li Bo
2013-5-7
Add a note about the relationship between traffic model and BSC specification in the contract:
Songruining
Specifications and capacity configuration of the BSC must be based on a certain traffic model, all contracts must be established on a given traffic model to ensure the accuracy of the contract. If you are
2015-11-13
Huawei Confidential
Page 2 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Version
Prepared/Revie wed By
Date
Description
Approved By
unable to obtain accurate traffic model, we recommend using the default Huawei traffic model for the contract traffic model. V0.7
Tang Xiaoli
2013-06-19
Deleted eGSM and used the eGBTS to replace independent NE.
Songruining
V0.8
Tang Xiaoli
2013-07-30
Added section 19.3"A Interface Design (TDM)" and section 19.6"Abis Interface Design (IP over E1)."
Songruining
V0.9
Tang Xiaoli
2013-11-22
Updated the document to adapt to the GBSS16.0 version.
Songruining
V1.0
Tang Xiaoli
2014-03-03
Revised the document based on TR5 review comments.
Songruining
V1.1
Liuqi
2014-05-06
Add 22.5.2 Constraints
Songruining
V1.2
付强
2014.07.18
Add VAMOS FR
Songruining
Add 16.4 source IP route
2015-11-13
Huawei Confidential
Page 3 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
2 Overview of Network Design........................................................21 3 Overall Guidance Principles.........................................................22 4 Overview of Key NEs...................................................................23 5 Overview of the Network Design Tool...........................................24 6 Important Reference Document...................................................25 7 Product Specifications.................................................................26 7.1 BSC Specifications.......................................................................................................................................................26 7.1.1 Hardware Capacity....................................................................................................................................................26 7.1.2 Estimation of BSC Configuration Capacity..............................................................................................................27 7.2 Board Specifications.....................................................................................................................................................28 7.2.1 BSC6910 Board Specifications.................................................................................................................................28 7.2.2 Service Processing Modules......................................................................................................................................28 7.2.3 Interface Modules......................................................................................................................................................31
8 BOQ Review Guide......................................................................34 8.1 Design Overview..........................................................................................................................................................34 8.1.1 Purpose of the Design................................................................................................................................................34 8.1.2 Input of the Design....................................................................................................................................................34 8.1.3 Contents of the Design..............................................................................................................................................34 8.1.4 Design Reference.......................................................................................................................................................34 8.2 Overview of Pre-sales Network Design.......................................................................................................................34 8.3 BOQ Review Principles...............................................................................................................................................35 8.4 CS Traffic Models........................................................................................................................................................36 8.5 PS Traffic Models.........................................................................................................................................................38 8.6 Relationship Between Traffic Model and Traffic Statistics..........................................................................................40
2015-11-13
Huawei Confidential
Page 4 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
9 Parameters for Capacity Calculation.............................................42 10 Capacity Calculation..................................................................42 11 Design of Resource Allocation....................................................44 11.1 Design Overview........................................................................................................................................................44 11.1.1 Purpose of the Design..............................................................................................................................................44 11.1.2 Input of the Design..................................................................................................................................................45 11.2 BSC Load Allocation..................................................................................................................................................45 11.2.1 Signaling Storm.......................................................................................................................................................46 11.3 BSC Board Layout Design.........................................................................................................................................52 11.3.1 Design Guide...........................................................................................................................................................52
12 Naming Rules Design.................................................................58 12.1 Design Overview........................................................................................................................................................58 12.1.1 Purpose of the Design..............................................................................................................................................58 12.1.2 Input of the Design..................................................................................................................................................58 12.2 NE Naming Rules.......................................................................................................................................................58 12.2.1 Naming Rules of Areas............................................................................................................................................58 12.2.2 Naming Rules of Offices.........................................................................................................................................59 12.2.3 Naming Rules of Manufacturers.............................................................................................................................59 12.2.4 Naming Rules of NEs..............................................................................................................................................60 12.2.5 Naming Rules of Signaling Points..........................................................................................................................61 12.3 NE Numbering Rules.................................................................................................................................................61 12.3.1 Numbering Rules of Entity IDs...............................................................................................................................61 12.3.2 Numbering Rules of BTS IDs.................................................................................................................................62 12.3.3 Numbering Rules of Cell IDs..................................................................................................................................62 12.3.4 Numbering Rules of LACs......................................................................................................................................62 12.3.5 Numbering Rules of MCCs and MNCs...................................................................................................................62 12.3.6 Numbering Rules of SPXs and DPXs.....................................................................................................................62
15 Detection Mechanism................................................................80 15.1 Restrictions of the Design..........................................................................................................................................80 15.2 BFD Detection............................................................................................................................................................82 15.3 ARP Detection............................................................................................................................................................84 15.4 IP PM Detection.........................................................................................................................................................84
16 IP Interworking Design..............................................................86 16.1 IP Planning on the BSC Side......................................................................................................................................86 16.2 IP Planning on the BTS Side......................................................................................................................................87 16.3 Routing Design on the BSC Side...............................................................................................................................88 16.4 Routing Design on the BTS Side................................................................................................................................88 16.5 VLAN Design.............................................................................................................................................................88 16.6 QoS Design.................................................................................................................................................................89
17 Network Topology Design...........................................................91 17.1 Design Overview........................................................................................................................................................91 17.1.1 Purpose of the Design..............................................................................................................................................91 17.1.2 Input of the Design..................................................................................................................................................91 17.2 Network Structure Design..........................................................................................................................................91 17.2.1 Design Guide...........................................................................................................................................................91 17.2.2 Typical Networking.................................................................................................................................................92
18 Reliability Design....................................................................102 18.1 Design Overview......................................................................................................................................................102 18.1.1 Purpose of the Design............................................................................................................................................102 18.1.2 Input of the Design................................................................................................................................................102 18.2 Network Reliability Design......................................................................................................................................102 18.2.1 Design Guide.........................................................................................................................................................102 18.2.2 Design Examples...................................................................................................................................................103
19 Transmission Interface Design..................................................118 19.1 Design Overview......................................................................................................................................................118 19.1.1 Purpose of the Design............................................................................................................................................118 19.1.2 Input of the Design................................................................................................................................................118 19.2 A Interface Design....................................................................................................................................................118 19.2.1 Interface Description.............................................................................................................................................118 19.2.2 Networking Design................................................................................................................................................119 19.2.3 SCTP Multi-Homing Design.................................................................................................................................129 19.2.4 Signaling Bandwidth Calculation..........................................................................................................................135 19.2.5 Signaling Configuration Principles.......................................................................................................................135 19.2.6 Traffic Bandwidth Calculation..............................................................................................................................135 19.2.7 IP Address Planning (A over IP)............................................................................................................................136 19.2.8 Routing Planning (A over IP)................................................................................................................................138
2015-11-13
Huawei Confidential
Page 6 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
20 Clock Synchronization Design...................................................201 20.1 Design Overview......................................................................................................................................................201 20.1.1 Purpose of the Design............................................................................................................................................201 20.1.2 Input of the Design................................................................................................................................................201 20.2 Clock Description.....................................................................................................................................................201 20.2.1 Definition of Synchronization...............................................................................................................................201 20.2.2 SyncE.....................................................................................................................................................................201 20.2.3 IEEE 1588 V2........................................................................................................................................................202 20.2.4 Advantages and Disadvantages of Clock Protocols..............................................................................................202 20.2.5 QoS Requirements of Clock Protocols..................................................................................................................205 20.3 Clock Source Selection.............................................................................................................................................205 20.4 Clock Design in Abis over TDM Mode...................................................................................................................206 20.5 Clock Design in Abis over IP Mode.........................................................................................................................207 20.6 Design of the IP Clock Server..................................................................................................................................209
21 Time Synchronization Design...................................................214 21.1 Design Overview......................................................................................................................................................214 21.1.1 Purpose of the Design............................................................................................................................................214 21.1.2 Input of the Design................................................................................................................................................214 21.2 Description of Time Synchronization.......................................................................................................................214 21.3 NTP...........................................................................................................................................................................214 21.4 Selection of a Time Synchronization Source............................................................................................................215 21.5 Transmission Mode..................................................................................................................................................215 21.6 Typical Networking..................................................................................................................................................215 21.7 Typical Application...................................................................................................................................................216
22 Function Design......................................................................217 22.1 Design of Broadcast Solutions for Cells..................................................................................................................217 22.1.1 Standard Broadcast................................................................................................................................................217 22.1.2 Simple Cell Broadcast...........................................................................................................................................222 22.2 Design of Radio Measurement Data Interface for Navigation (TOM-TOM)..........................................................223 22.2.1 Overview...............................................................................................................................................................223 22.2.2 Reference Document.............................................................................................................................................224 22.2.3 Limitations on Specifications................................................................................................................................224 22.2.4 Software and Hardware Configuration..................................................................................................................224 22.2.5 Networking Design................................................................................................................................................224 22.2.6 Bandwidth Design.................................................................................................................................................227 22.2.7 Time Synchronization............................................................................................................................................227 22.3 MOCN II Design......................................................................................................................................................227 22.3.1 Overview...............................................................................................................................................................227 22.3.2 Networking Design................................................................................................................................................228 22.3.3 Capacity Planning..................................................................................................................................................228
2015-11-13
Huawei Confidential
Page 8 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
23 BTS Design.............................................................................. 243 23.1 BTS Cable Design....................................................................................................................................................243 23.1.1 Purpose of the Design............................................................................................................................................243 23.1.2 Input of the Design................................................................................................................................................243 23.2 Design Tool of the BTS Cable Diagram...................................................................................................................243 23.3 BTS Transmission Design........................................................................................................................................243 23.3.1 Purpose of the Design............................................................................................................................................243 23.3.2 BTS Transmission.................................................................................................................................................243 23.3.3 eGBTS Networking...............................................................................................................................................246
24 OM Networking Design............................................................248 24.1 Design Overview......................................................................................................................................................248 24.1.1 Input of the Design................................................................................................................................................248 24.1.2 Design Content......................................................................................................................................................248 24.1.3 Reference...............................................................................................................................................................248 24.2 Introduction to OMU................................................................................................................................................248 24.2.1 Standalone OMU...................................................................................................................................................248 24.2.2 Dual OMU.............................................................................................................................................................249 24.3 OM Networking Design...........................................................................................................................................250 24.3.1 Networking for Part of E1/T1 Timeslots...............................................................................................................250 24.3.2 Entire E1/T1 Networking......................................................................................................................................252 24.3.3 IP Networking........................................................................................................................................................253 24.3.4 Networking Instances............................................................................................................................................254 24.4 OM IP Address Planning..........................................................................................................................................255 24.5 Route Planning.........................................................................................................................................................256 24.6 Impact of eGBTS on the O&M................................................................................................................................256
2015-11-13
Huawei Confidential
Page 9 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
Figures Figure 2-1 Position of the BSS network design in the entire network construction process................................21 Figure 11-1 Average service duration...................................................................................................................51 Figure 13-1 Port switchover..................................................................................................................................71 Figure 13-2 Board switchover...............................................................................................................................72 Figure 15-1 Diagram of the promoted commercial solution.................................................................................86 Figure 17-1 Networking of the BSC connected to a single MGW.......................................................................96 Figure 17-2 BSC/MGW multi-homing networking..............................................................................................97 Figure 17-3 MSC Pool networking mode 1..........................................................................................................98 Figure 17-4 MSC Pool networking mode 2..........................................................................................................99 Figure 17-5 Typical networking of the SGSN pool............................................................................................100 Figure 17-6 All-IP networking............................................................................................................................101 Figure 17-7 Typical IP-based networking...........................................................................................................101 Figure 17-8 Hybrid networking..........................................................................................................................102 Figure 17-9 Logical networking of the transmission resource pool...................................................................103 Figure 17-10 Physical networking of the transmission pool with active/standby boards...................................103 Figure 17-11 Physical networking of the transmission pool with independent boards......................................104 Figure 18-1 Improving reliability by active/standby links on ports....................................................................106 Figure 18-2 Reliability design of the Gb interface.............................................................................................107 Figure 18-3 Reliability design of IP transmission routes....................................................................................108 Figure 18-4 Reliability design of IP transmission routes....................................................................................108 Figure 18-5 BSC/MGW multi-homing networking............................................................................................109 Figure 18-6 MSC Pool networking mode 1........................................................................................................110 Figure 18-7 MSC Pool networking mode 2........................................................................................................111 Figure 18-8 Typical networking diagram of the SGSN pool..............................................................................112 Figure 18-9 IP networking topology of A interface boards based on the dynamic loading balancing...............112 Figure 18-10 Standalone EOMU........................................................................................................................113
2015-11-13
Huawei Confidential
Page 10 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
Figure 18-11 Dual EOMUs.................................................................................................................................114 Figure 18-12 Clock subsystem of the BSC6910.................................................................................................115 Figure 18-13 BSC belonging to two layer-2 transmission devices in the dual-homing mode............................117 Figure 18-14 BSC belonging to one layer-2 transmission device in the single-homing mode...........................117 Figure 18-15 Inter-board link aggregation in the inter-board pool networking scenario....................................118 Figure 18-16 Manual active/standby LAGs on the BSC side+router adopting the VRRP networking mode....119 Figure 18-17 LAG of the active/standby board+router adopting the VRRP networking mode.........................120 Figure 19-1 Reference protocol model on the control plane of the A interface..................................................122 Figure 19-2 Reference protocol model on the user plane of the A interface......................................................122 Figure 19-3 BSC/MGW multi-homing networking............................................................................................123 Figure 19-4 Typical A over IP networking mode (pool of standalone boards)...................................................124 Figure 19-5 Typical A over IP networking mode (pool of standalone boards)...................................................126 Figure 19-6 Typical A over IP networking mode (pool of active/standby interface boards+dual-active ports). 128 Figure 19-7 Typical A over IP networking mode (pool of active/standby boards+manual active/standby LAGs) .............................................................................................................................................................................129 Figure 19-8 SCTP four-homing between the BSC and the MSC server.............................................................133 Figure 19-9 Two M3UA links and SCTP four-homing between the BSC and the MSC server.........................134 Figure 19-10 SCTP dual-homing on the MSC server side and SCTP single-homing on the BSC side (1)........135 Figure 19-11 SCTP dual-homing on the MSC server side and SCTP single-homing on the BSC side (2)........136 Figure 19-12 SCTP single-homing on the MSC server side and SCTP dual-homing on the BSC side.............137 Figure 19-13 IP network topology of the BSC...................................................................................................141 Figure 19-14 Promoted detection mode in active/standby mode........................................................................143 Figure 19-15 Reference protocol model on the control plane of the A interface................................................148 Figure 19-16 Gb over IP protocol stack..............................................................................................................155 Figure 19-17 Embedded PCU networking..........................................................................................................156 Figure 19-18 Direction connection (Gb over IP)................................................................................................156 Figure 19-19 IP transmission network connection (Gb over IP)........................................................................157 Figure 19-20 Typical Gb over IP networking mode (active/standby boards+manual active/standby LAGs)....158 Figure 19-21 Typical Gb over IP networking mode (active/standby boards+dual-active ports)........................161 Figure 19-22 Logical connection between the NS layer and the SSGP layer.....................................................169 Figure 19-23 Abis over HDLC interface protocol..............................................................................................175 Figure 19-24 TDM networking when the Abis interface adopts STM-1 transmission.......................................177 Figure 19-25 IP networking when the Abis adopts MSTP transmission............................................................177 Figure 19-26 IP networking when the Abis adopts data network transmission..................................................177
2015-11-13
Huawei Confidential
Page 11 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
Figure 19-27 BTS networking diagram..............................................................................................................178 Figure 19-28 Two E1s connected to different interface boards..........................................................................181 Figure 19-29 Two E1s connected to different ports on the same interface board...............................................181 Figure 19-30 Typical A over IP networking mode (pool of active/standby boards+manual active/standby LAGs+single IP address).....................................................................................................................................182 Figure 19-31 Typical A over IP networking mode (pool of active/standby boards+dual-active ports+single IP address)................................................................................................................................................................184 Figure 19-32 SMLC-based network topology for the Lb interface....................................................................203 Figure 19-33 Direct connection between the BSC and the SMLC.....................................................................204 Figure 19-34 Connection through STP...............................................................................................................204 Figure 20-1 Clock networking instance 1...........................................................................................................213 Figure 20-2 Clock networking instance 2...........................................................................................................213 Figure 20-3 MSTP-based GSM IP solution........................................................................................................216 Figure 20-4 IP Clock synchronization networking.............................................................................................217 Figure 21-1 Typical networking for time synchronization.................................................................................222 Figure 22-1 Network topology of the cell broadcast..........................................................................................225 Figure 22-2 Cable connection diagram between the interface board and the CBC............................................226 Figure 22-3 Topology of the simple cell broadcast system................................................................................230 Figure 22-4 Logical networking for the TOM-TOM..........................................................................................232 Figure 22-5 Physical networking on the VNP interface.....................................................................................233 Figure 22-6 Networking of the active/standby OMUs with a single port and directly connected routers.........233 Figure 22-7 Networking for time synchronization.............................................................................................234 Figure 22-8 Logical structure of the LCS system on the GSM network............................................................235 Figure 22-9 Logical structure of the NSS-based SMLC.....................................................................................237 Figure 22-10 Logical structure of the BSS-based SMLC...................................................................................237 Figure 22-11 LCS flow initiated by an external LCS client...............................................................................238 Figure 23-1 Networking topology change of the eGBTS...................................................................................243 Figure 23-2 Change of northbound and southbound interfaces of the eGBTS...................................................243 Figure 24-1 Standalone OMU.............................................................................................................................245 Figure 24-2 Dual OMUs.....................................................................................................................................246 Figure 24-3 25-pin D model interface.................................................................................................................247 Figure 24-4 Networking for part of E1/T1 timeslots..........................................................................................248 Figure 24-5 Entire E1/T1 Networking................................................................................................................249 Figure 24-6 OM network topology.....................................................................................................................249
2015-11-13
Huawei Confidential
Page 12 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
Figure 24-7 IP networking in dual OMU mode..................................................................................................250 Figure 24-8 OM E1 networking instance 1.........................................................................................................250 Figure 24-9 OM E1 networking instance 2.........................................................................................................251 Figure 24-10 Change of the OM structure..........................................................................................................252
2015-11-13
Huawei Confidential
Page 13 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
Tables Table 7-1 Typical maximum configuration of HW69 R13 boards in BSC6900 GSM where the BM and TC are integrated...............................................................................................................................................................21 Table 7-2 Typical maximum configuration of HW69 R13 boards in BSC6900 GSM where the BM and TC are separated................................................................................................................................................................22 Table 7-3 Typical maximum configuration of HW69 R13 boards in BSC6900 GSM where the Abis over TDM or A over IP is adopted...........................................................................................................................................22 Table 7-4 Typical maximum configuration of HW69 R13 boards in BSC6900 GSM where the Abis over IP or A over IP is adopted...................................................................................................................................................22 Table 7-5 Board specifications..............................................................................................................................24 Table 8-1 Basic PS traffic model (new in the R13)...............................................................................................31 Table 8-2 PS user model........................................................................................................................................31 Table 8-3 PS coding ratio and average rate...........................................................................................................32 Table 8-4 Performance counters corresponding to basic procedures....................................................................32 Table 9-1 BSC capacity planning table.................................................................................................................35 Table 10-1 Manufacturer short names...................................................................................................................43 Table 10-2 NE short names...................................................................................................................................44 Table 12-1 MSP advantages and disadvantages....................................................................................................53 Table 12-2 MSP support capabilities of the boards of the controller....................................................................56 Table 12-3 Framing mode comparison..................................................................................................................69 Table 12-4 Optical interface interworking parameters..........................................................................................70 Table 13-1 Restrictions of the fault detection mechanism of the controller.........................................................73 Table 13-2 Restrictions of the fault detection mechanism of the base station......................................................74 Table 17-1 Calculation result of A interface bandwidth in TDM transmission mode.........................................121 Table 17-2 Calculation result of A interface bandwidth in IP transmission mode..............................................121 Table 17-3 A interface interworking parameters.................................................................................................129 Table 17-4 Design principles of A interface networking.....................................................................................133 Table 17-5 Configuration of O&M links for the Ater interface..........................................................................136 Table 17-6 Configuration of signaling links for the Ater interface.....................................................................136
2015-11-13
Huawei Confidential
Page 14 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
Table 17-7 Gb over IP interworking parameters.................................................................................................151 Table 17-8 Gb over IP interworking parameters.................................................................................................153 Table 17-9 Performance test results of parameters a, b, c, and d........................................................................170 Table 17-10 Estimates of data related to parameters a, b, c, and d.....................................................................170 Table 18-1 Support for 2G-based 1588v2 clocks................................................................................................189
2015-11-13
Huawei Confidential
Page 15 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Technical Guide to SRAN Network Design (GO Applicable to SRAN10.0&GBSS17.0&BSC6910)
Keywords: network design Abstract: The BSC6910 is introduced in the GBSS15.0. The BSC6910 R15 has less networking scenarios than the BSC6900. In GBSS17.0, the networking is enhanced. Specifically, the BSC6910 (configured with the POUc) supports A over TDM networking. The following describes the networking scenarios of the BSC6910:
The BSC6910 does not support an external PCU, without any Pb interface.
The BSC6910 does not support TC, remote TC subracks, or local independent TC subracks, without any Ater interface.
The BSC6910 does not support Abis over HDLC.
The A interface does not support IP over E1/T1.
Calculation of the BSC6910 capacity does not require calculation of Ater or HDLC transmission. Contents considering the deleted networking scenarios are removed from this document, for example, TC Pool and local switching. For details, see this document. The following table lists the differences in network design between the GBSS17.0 BSC6900 and BSC6910:
2015-11-13
Item
BSC6900
BSC6910
Resource allocation
Not supports the EXOUa in 10 GE or EGPUa. Supports TDM exchange, TNU boards, EIUa, EIUb, OIUa, OIUb, FG2a, FG2c, FG2d, PEUa, PEUc, GOUa, GOUc, GOUd, GOUe, XPUa, XPUb, and DPUa/c/d/e/f/g.
Supports the EXOUa in 10 GE and EGPUa, FG2c, GOUc, POUc, GOUd, GOUe, and FG2d boards. Not supports TDM exchange, TNU boards, and TC subracks.
Capacity
Supports the calculation of the CS traffic volume, the number of BSC subscribers, the BSC CS BHCA, the CIC of A interface and Ater interface, the number of PDCH, IWF resources, the TDM&IP and IP&IP using the IWF, and the Gb interface throughput.
Supports the calculation of the CS traffic volume, the number of BSC subscribers, the BSC CS BHCA, the CIC of A interface, the number of PDCH, IWF resources, the TDM&IP and IP&IP using the IWF, and the Gb interface throughput. Not supports the CIC calculation of Ater interface.
Overall capacity calculati on of the BSC
Huawei Confidential
Page 16 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
2015-11-13
Bandwid th calculati on of Abis interface
Supports the bandwidth calculation of Abis over TDM over E1, Abis over TDM over STM1, Abis over IP over E1, Abis over IP over STM1, Abis over IP over FE/GE(electrical)/GE(optical), and Abis over HDLC over E1. Not supports the bandwidth calculation of 10GE(optical) interface.
Supports bandwidth calculation of Abis over TDM over STM1 and Abis over IP over FE/GE(electrical)/GE(optical)/1 0GE(optical).
Bandwid th calculati on of A interface
Supports the bandwidth calculation of A over TDM over E1, A over TDM over STM1, A over IP over E1, A over IP over STM1, and A over IP over FE/GE(electrical)/GE(optical). Supports the calculation of the number of M3UA links over IP. Not supports the bandwidth calculation of A over IP over 10 GE(optical).
Supports bandwidth calculation of A over IP over FE/GE(electrical)/GE(optical)/1 0GE(optical), and the calculation of the number of M3UA links over IP.
Ater interface
Supports the bandwidth calculation of Ater over TDM over E1, Ater over TDM over STM1, and Ater over IP over STM1.
Not supports this interface.
Pb interface
Supports the bandwidth calculation of Pb interface circuits and the calculation of the bandwidth occupied by Pb interface links.
Not supports this interface.
Gb interface
Supports the bandwidth calculation of GB over FR over TDM E1, GB over FR over TDM STM1, and Gb over IP over FE/GE(electrical)/GE(optical). Not supports the bandwidth calculation of Gb over IP over 10 GE(optical).
Not supports Gb over FR over TDM E1 or Gb over FR over TDM STM1. Supports Gb over IP over FE/GE(electrical)/GE(optical)/1 0GE(optical).
Naming rules
The value of both BTS ID and CELL ID ranges from 0 to 2047. The value of DPX (integer) ranges from 0 to 186.
The value of both BTS ID and CELL ID ranges from 0 to 7999. The value of DPX (integer) ranges from 0 to 427.
IP networking
Supports the IP design on the BSC and BTS sides, the route design on the BSC and BTS sides, the VLAN design, and the QoS design.
Supports the IP design on the BSC and BTS sides, the route design on the BSC and BTS sides, the VLAN design, and the QoS design. Not supports the IP path design.
Huawei Confidential
Page 17 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Network topology
Supports the TDM networking, the BSC and MGW singlehoming networking, the BSC and MGW multi-homing networking, the MSC Pool networking, the SGSN pool networking, all-IP networking, hybrid networking, and the transmission resource pool networking.
Not supports the TDM networking or TC subracks. Therefore, networking in the BM and TC separated mode does not exist. Supports the BSC and MGW single-homing networking, the BSC and MGW multi-homing networking, the MSC Pool networking, the SGSN pool networking, all-IP networking, hybrid networking, and the transmission resource pool networking.
Reliability
Supports the reliability design of active/standby port links, loadbalancing, data configuration, multiple transmission channels, the VRRP in IP networking, the SCTP multi-homing, the BSC multi-homing MGWs, the MSC pool, the SGSN pool, the transmission resource pool over A interface, the OM, clock, and Ethernet link aggregation.
Supports the reliability design of active/standby port links, loadbalancing, data configuration, multiple transmission channels, the VRRP in IP networking, the SCTP multi-homing, the BSC multi-homing MGWs, the MSC pool, the SGSN pool, the transmission resource pool over A interface, the OM, clock, and Ethernet link aggregation. Not supports the reliability design of the TC pool.
A interface
Supports A over TDM, A over IP over FE/GE(electrical)/GE(optical), and A over IP over E1.
Not supports A over IP over E1. Supports A over IP over FE/GE(electrical)/GE(optical)/1 0GE(optical).
Abis Interface
Supports Abis over TDM over STM1, Abis over TDM over E1, Abis over IP, and Abis over HDLC.
Supports Abis over TDM over STM1 and Abis over IP over EF/GE(electrical)/10GE(Optical ).
Gb interface
Supports Gb over FR and Gb over IP.
Supports Gb over IP. Not supports Gb over FR.
Transmis sion interface
2015-11-13
Huawei Confidential
Page 18 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Ater interface
Supported
Not supported
Pb interface
Supported
Not supported
Supports line clock, GPS, BITS clock, and external clock.
Not supports line clock. Supports GPS, BITS clock, and external clock.
Clock synchronization
Foreword 1.1 Objectives This document guides global system for mobile communications (GSM) base station subsystem (BSS) network design engineers through the network design and delivery of GSM BSS establishment, migration, expansion, and optimization. With the help of this document, a GSM BSS network design engineer can use high-level design (HLD) and low-level design (LLD) templates for GSM BSS network design to work out a final GSM BSS network design report for a customer. A network design report consists of the HLD and LLD. The HLD provides the customer with the design of the network topology, networking, transmission, interfaces, resource capacity, function services, operation and maintenance (O&M), clock, and time synchronization. This document covers all the guidance principles. The LLD is intended for engineering guidance, and provides the design of the device board layout, cable connections, and key data configuration. You can use the network equipment planning (NEP) tool to generate the LLD.
2015-11-13
Huawei Confidential
Page 19 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
1.2 Scope This document describes the design principles, design methods, and output formats of the BSS networking, transmission, interfaces, services, and O&M. The core network elements (NEs) involved in BSS network design are the base station controller (BSC), packet control unit (PCU), and BTS, and the involved interface NEs are the mobile switching center (MSC) server, media gateway (MGW), M2000, serving GPRS support node (SGSN), and local maintenance terminal (LMT).
1.3 Constraints This document is developed based on GBSS17.0 BSC6910 and is applicable to the GSM Only mode of the BSC6910. Network design of the BSC6900 is described in Technical Guide to Single RAN Network Design V100R003 (GO applicable to SRAN10.0&GBSS17.0&BSC6910). The GU mode is described in the Single RAN network design guide.
1.4 Dependency
Before the network design, you must collect the required data based on the information collection template for network design. During the network design, you need to effectively communicate with the operator and core network engineers to ensure that the required information is accurate and the change causes and change results are recorded.
The network design personnel must be global technical service (GTS) engineers who are familiar with the BSC6910 and are engaged in engineering or maintenance for more than one year.
The network design guide is updated based on changes in the BSC and application scenarios and is available at http://support.huawei.com. You can obtain the latest version of the guide from the following path: Documentation > Wireless > Wireless Public > Wireless Professional Services Product > Technical Guides
2015-11-13
Huawei Confidential
Page 20 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
2
Overview of Network Design
The BSS network design service is provided in the engineering preparation and delivery stage. The network planning (NP) provided by the network design department of Sales & Services, the network development planning provided by the operator, and the radio network plan provided by the network planner are the input of the HLD and LLD. The BSS network design guides the follow-up network deployment design and engineering. Figure 1.1 shows the position of the BSS network design in the entire network construction process: Figure 1.1 Position of the BSS network design in the entire network construction process
The GSM BSS network design service involves the overall designs of the networking, transmission, interfaces, resource capacity, functional services, O&M, and clock of the network. Focusing on the security, balance, and extensibility of the network, the GSM BSS network design provides guidance for engineering and construction and guarantees highquality network operation for operators.
2015-11-13
Huawei Confidential
Page 21 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
3
CONFIDENTIAL
Overall Guidance Principles
Generally, the scale of GSM BSS network construction is large, numerous NEs are involved, and the interface interworking is complicated. The BSS network design principles are as follows:
Principle of area-based design The BSS network design is implemented based on the network construction plan of the operator, areas, and stages in engineering. Generally, design is implemented in a "cakecutting" manner with an MSC and all the BSCs mounted to the MSC as a cluster. In this way, the design work can be simplified, and the design process is lengthened so that the design workload can be distributed properly based on the engineering schedule.
Principle of interworking The BSS network design and core network design are closely related. Therefore, during the BSS network design, designers must effectively communicate with core network designers on issues, such as NE homing, interface interworking, and device capacity.
Principle of security in network design The purpose of network design is to provide the customer with an available and reliable network that can handle burst traffic and can recover quickly in the event of network faults.
Principle of proper utilization of resources The design principle of resources on a network varies with the development stage of the network. For example, if the number of users on a network rapidly increases, the resource usage cannot be designed too high. Otherwise, after the network is constructed, new BSCs may be required, and then the new BTSs result in hybrid networking and require re-homing, or new TRXs cannot be added for capacity expansion due to capacity limitation of the BSC after resources are used up.
Principle of interface independence The A, Gb, and Abis interfaces are physically independent. That is, a physical board can be configured with only one type of logical interfaces. Do not configure the A, Abis, and Gb interfaces on the same interface board because of the inconvenience for follow-up maintenance and expansion and the greater impact from board faults.
2015-11-13
Huawei Confidential
Page 22 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
4
Overview of Key NEs
BSC The BSC connects to the MSC and BTS through the A interface and Abis interface respectively. A PCU is embedded to implement radio resource management, BTS management, power control, handover control, radio network configuration, and radio network performance measurement.
BTS The BTS/eGBTS connects to the BSC through the Abis interface and communicates with mobile stations (MSs) through the radio interface. The BTS/eGBTS provides radio functions in the BSS. For example, the BTS transmits and receives radio signals, measures the quality of the radio network, controls power, and implements channel coding, interleaving, and encrypting for radio channels.
PCU The built-in PCU connects to the SGSN through the Gb interface. The PCU is introduced in the BSS so that the BSS supports the general packet radio service (GPRS) packet service. The PCU manages packet radio resources, controls packet calls, and transmits data packets on the radio interface and Gb interface
MSC server The MSC server provides switching functions and implements call switching between the public land mobile network (PLMN) and the public switched telephony network (PSTN). The MSC server provides telecom services, bearer services, and supplementary services for mobile subscribers.
SGSN The SGSN is a core network device in the GSM packet switched (PS) domain. It implements functions, such as mobility management, session management, data packet routing and forwarding, charging, SMS, customized applications for mobile network enhanced logic (CAMEL), and quality of service (QoS) management.
2015-11-13
Huawei Confidential
Page 23 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
5
CONFIDENTIAL
Overview of the Network Design Tool The NEP tool is developed to improve the efficiency of network design delivery. This tool can complete most network designs automatically. If you use the NEP tool in network design, the efficiency can be greatly improved. For detailed information, contact Li Yongqing (employee ID: 00141602), network design delivery representative of Network Integration Service (NIS).
2015-11-13
Huawei Confidential
Page 24 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
6
Important Reference Document The Transmission Configuration Specifications describes the specifications of IP planning, QoS parameters, and VLAN planning used for IP transmission. Related links are available at http://support.huawei.com:
A&GB Interface Configuration Specification_IP(GBSS17.0) Wireless > Wireless Public > Wireless Professional Services Product > Technical Guides http://support.huawei.com/support/pages/navigation/gotoKBNavi.do? actionFlag=getAllJsonData&colID=ROOTWEB|CO0000000064&level=4&itemId=20300051453&itemId0=29-7&itemId1=3-154&itemId2=1-632&itemId3=20200051452&itemId4=20300051453&itemId5=&itemId6=&itemId7=&itemId8=&itemId9=&materialType=1232&isHedexDocType=&pageSize=20
2015-11-13
Huawei Confidential
Page 25 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
7
Product Specifications
The specifications vary with the product version. For details about the capacity specifications of the BSC of a certain version, see the officially released documents of that version. Specifications and capacity configuration of the BSC must be based on a certain traffic model, all contracts must be established on a given traffic model to ensure the accuracy of the contract. If you are unable to obtain accurate traffic.
7.1 BSC Specifications For details about BSC specifications, see BSC6910 GU Product Description in the Hedex BSC6910 GU product documentation. Specifications of a BSC adopting an all-IP network change as follows: The number of TRXs increases from 8192 in the BSC6900 to 24000 in the BSC6910.
7.1.1 Hardware Capacity Table 1.1 lists the typical maximum configuration of R16 boards in BSC6910 GSM. The GBSS17.0 BSC6910 has a maximum configuration of one cabinet and three subracks in the GO mode and supports A over TDM, but it cannot be configured in BM/TC separated mode. The GBSS15.0 does not support A over TDM. Table 1.1 Typical maximum configuration of R16 boards in BSC6910 GSM (Abis over TDM and A over IP are adopted.)
2015-11-13
Specification and Subrack Name
1 MPS+2 EPS
Number of cabinets
1
Maximum BHCA (M)
15
Traffic volume (Erlang)
43750
Number of TRXs
7000
Number of PDCHs that can be activated (MCS-9)
28000
Huawei Confidential
Page 26 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Gb throughput (G)
2.688
Table 1.2 lists the typical maximum configuration of traffic volume of R16 boards in BSC6900 GSM where the BM and TC are separated. Table 1.2 Typical maximum configuration traffic volume of R16 boards in BSC6900 GSM (all-IP mode used) Specification and Subrack Name
1 MPS+2 EPS (Number of Subracks Can Be Changed)
Number of cabinets
1
Maximum BHCA (M)
52
Traffic volume (Erlang)
150000
Number of TRXs
24000
Number of PDCHs that can be activated (MCS-9)
96000
Gb throughput (G)
8
7.1.2 Estimation of BSC Configuration Capacity BSC configuration capacity is estimated based on two key BSC counters: Busy Hour Call Attempts (BHCA) and traffic volume. The actual configuration capacity is related to the number of interface boards and the number of service processing boards and is the minimum capacity calculated based on each board. The estimation of the configuration capacity conducted currently, however, is based on the number of EGPUa(GCUP) boards. This section describes a simple method for estimating BSC configuration capacity based on the number of EGPUa(GCUP) boards. The following describes how to calculate the maximum number of BHCA and maximum traffic volume:
2015-11-13
The method for calculating the maximum number of BHCA allowed by the current configuration is as follows: −
If all interfaces adopt the IP transmission mode, the maximum number of BHCA allowed by the current configuration is calculated as follows: Maximum number of BHCA = MIN ((Number of EGPUa(GCUP) pairs on the current BSC x Number of BHCA supported by a pair of EGPUa(GCUP)s x 80%, 52,000,000)
−
If all Abis interfaces adopt the TDM transmission mode, the maximum number of BHCA allowed by the current configuration is calculated as follows: Maximum number of BHCA = MIN ((Number of EGPUa(GCUP) pairs on the current BSC x Number of BHCA supported by a pair of EGPUa(GCUP)s x 80%, 21,000,000)
−
If the Abis interfaces adopt the TDM/IP hybrid transmission mode, the maximum number of BHCA allowed by the current configuration is calculated as follows: Maximum number of BHCA = MIN ((Number of EGPUa(GCUP) pairs on the current BSC x Number of BHCA supported by a pair of EGPUa(GCUP)s x 80%, 52,000,000)
Huawei Confidential
Page 27 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
The simplified method for calculating traffic (expressed in Erlang) is as follows: −
If all interfaces adopt the IP transmission mode, the maximum traffic volume allowed by the current configuration is calculated as follows: Maximum traffic volume = MIN ((Number of EGPUa(GCUP) pairs on the current BSC x Traffic volume supported by a pair of EGPUa(GCUP)s, 150,000)
−
If all Abis interfaces adopt the TDM transmission mode, the maximum traffic volume allowed by the current configuration is calculated as follows: Maximum traffic volume = MIN ((Number of EGPUa(GCUP) pairs on the current BSC x Traffic volume supported by a pair of EGPUa(GCUP)s, 62,500)
−
If the Abis interfaces adopt the TDM/IP hybrid transmission mode, the maximum traffic volume allowed by the current configuration is calculated as follows: Maximum traffic volume = MIN ((Number of EGPUa(GCUP) pairs on the current BSC x Traffic volume supported by a pair of EGPUa(GCUP)s, 150,000)
7.2 Board Specifications 7.2.1 BSC6910 Board Specifications For details about board specifications, see Boards in BSC6910 GSM Hardware Description in the BSC6910 documentation package. This document is officially issued to customers. Hardw are Versio n
In the BSC6910, only the POUc boards support Abis over TDM and A over TDM. The POUc supports 1024 TRXs (without extra license control). In the BSC6900, the POUc supports 512 TRXs and can be used in the BSC6910. In the BSC6910, POUc boards support TDM and IP over E1 transmission. In A over TDM transmission mode, DPUf boards must be configured to process user-plane CS data. The number of configured DPUf boards is determined according to the number of CICs. The DPUf supports N+1 backup mode. Number of Configured DPUf = RoundUp(MaxACICPerBSCTDM/ TCNoPerDPUf,0) where MaxACICPerBSCTDM indicates the maximum number of required A CICs on a BSC and is calculated based on the traffic model.
2015-11-13
Huawei Confidential
Page 28 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
7.2.2 Service Processing Modules Table 1.1 lists the specifications of service processing boards. Table 1.1 Specifications of service processing boards Boar d
Logical Functi on
Full Name of Logical Function
Descriptio n
Specificati ons
Condition
EGPUa
RMP
Resource management
Resource management processing
This board is for resource management of the system.
A BSC is configured with a pair of EGPUa boards.
This board (GCUP) processes services of control plane and user plane integration. In addition, it supports CS and PS services of the standard TRX.
This board processes services of control plane and user plane integration. The specification is: 1000 TRXs
The BHCA is based on Huawei default traffic model.
processing
GCUP
2015-11-13
GSM BSC control plane and user plane processing
600 BTSs 600 CELLs 3000 PDCHs.
GMCP
GSM BSC mathematics calculation processing
If the board is used for GSM BSC mathematics calculation processing, it can calculate using the Interference Based Channel Allocation (IBCA) algorithm.
None
The GMCP needs to be configured if the IBCA feature is enabled.
NASP
Network assisted service process
Network assisted service processing unit
None
The NASP needs to be configured if Intelligent WiFi Detection and Selection is enabled.
Huawei Confidential
Page 29 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
EXPUa
RMP
Resource management processing
Resource management processing board.
This board is for resource management of the system.
A BSC is configured with a pair of EXPUa boards.
GCUP
GSM BSC control plane and user plane processing
This board (GCUP) processes services of control plane and user plane integration. In addition, it supports CS and PS services of the standard TRX.
This board processes services of control plane and user plane integration. The specification is:
The BHCA is based on Huawei default traffic model.
If the board is used for GSM BSC mathematics calculation processing, it can calculate using the IBCA algorithm
None
The GMCP needs to be configured if the IBCA feature is enabled.
GMCP
GSM BSC mathematics calculation processing
1000 TRXs 600 BTSs 600 CELLs 3000 PDCHs.
ENIUa
NIU
Evolved network intelligence unit
Evolved network intelligence unit
An ENIUa board has a capacity of 8000 M PS throughput in the RAN15.0.
The ENIUa needs to be configured if the Evolved Deep Packet Inspection function is enabled.
ESAUa
SAU
Evolved service aware unit
Evolved service aware unit
The SAU board is for collecting, filtering, and gathering data of the service board, and periodically sending it to Nastar.
The SAU needs to be configured on the BSC, if a user purchases Nastar. A BSC is configured with only one ESAUa board.
2015-11-13
Huawei Confidential
Page 30 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
DPUf
DPU
CS Data Processing Unit (1920 CICs)
This board provides the TC function to process CS data and works in N+1 backup mode.
This board provides the TC function (supporting 1920 CICs) in A over TDM mode.
If common AMR is used, the DPUf supports 1920 CICs. If WB AMR is used, the number of supported CICs is halved. That is, the board capability required by WB AMR calls is two times greater than that required by common calls.
7.2.3 Interface Modules Table 1.1 lists the interfaces applicable to the boards. Table 1.1 Interfaces applicable to the boards Board Name
Description
Applicable Interface
FG2c
IP Interface Unit (12 FE/4 GE, Electric)
IP: A/Abis/Lb/Gb/Iur-g
GOUc
IP Interface Unit(4 GE, Optical)
IP: A/Abis/Lb/Gb/Iur-g
EXOUa
Evolved 10GE Optical interface Unit
IP: A/Abis/Lb/Gb/Iur-g
POUc
TDM Interface Unit(4 STM1, channelized)
TDM: Abis
Table 1.2 lists the specifications of interface boards over different interfaces. Table 1.2 Specifications of interface boards over different interfaces
2015-11-13
Huawei Confidential
Page 31 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Model
Trans missi on Mode
Port Type
Port No.
TRX
A CIC (64 kbit/s)
Ater CIC (16 kbit/s)
Gb Through put(Mbit /s)
WP1D000FG201 (FG2c)
IP
FE/GE electrical port
12/4
2048
23040
N/A
2000
WP1D000GOU01 (GOUc)
IP
GE optical port
4
2048
23040
N/A
2000
QM1D00EXOU00 (EXOUa)
IP
10 GE optical port
2
8000
75000
N/A
8000
WP1D000GOU03 (GOUe)
IP
GE optical port
4
2048
23040
N/A
2000
WP1D000POU01 (POUc)
TDM
CSTM-1 port
4
1024
7680
N/A
488
IP
IP CSTM-1
4
2048
N/A
N/A
N/A
The total number of required interface boards is the sum of interface boards over all interfaces. Interface boards work in 1+1 backup mode. The BSC does not support BM/TC separated mode and is not configured with the Ater interface. The A, Gb, and Abis interfaces must be configured on the BM subrack side. On a GSM network, it is not recommended that the A, Abis, and Gb share an interface board. Interface boards are configured over different interfaces.
Calculation of the number of Abis interface boards
Select appropriate transmission ports based on the network plan. Calculate the number of required Abis interface boards based on the service capability (TRX support capability) and port requirements, and then select the maximum value. Number of Abis interface boards = 2 x RoundUp(MAX(Number of TRXs in the transmission mode/Number of TRXs supported by the interface board, number of ports in the transmission mode/number of ports supported by the interface board),0) When configuring Abis interface boards, concern the following aspects: 2.
In Abis over TDM transmission mode, the BSC6910 only supports the POUc and does not support the TDM over E1/T1 interface board. If the Abis uses TDM over E1/T1 transmission on the BSC side, optical or electrical switching devices, such as Huawei OSN device, are required to perform switching between E1/T1 and STM-1.
3.
The BSC6910 cannot be configured with a 10GE EXOUa interface board. Instead, it can only be configured with the FG2 or GOUc working as the GE interface board when both of the following conditions are met: −
The BTS uses IP over E1 transmission.
−
The BSC uses IP transmission.
4.
Only the POUc board of the BSC6910 supports IP over E1 transmission.
Calculation of the number of A interface boards Select appropriate transmission ports based on the network plan. Calculate the number of required A interface boards based on the service capability (CIC support capability).
2015-11-13
Huawei Confidential
Page 32 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Number of A interface boards = 2 x RoundUp(A CIC Number/Support capability of the A interface board,0) When configuring A interface boards, concern the following aspects: In A over TDM transmission mode, the BSC6910 only supports the POUc interface board (TDM over STM-1) and does not support the TDM over E1/T1 interface board. If the Abis uses incoming TDM over E1/T1 transmission, optical or electrical switching devices, such as Huawei OSN device, are required to perform switching between E1/T1 and STM-1.
Calculation of the number of Gb interface boards Select appropriate transmission ports based on the network plan. Calculate the number of required Gb interface boards based on the service capability (bandwidth support capability). Number of Gb interface boards = 2 x RoundUp(Gb throughput/Support capability of the Gb interface board,0)
Calculation of the total number of required interface boards The total number of required interface boards is calculated as follows: Total number of interface boards = Number of Abis interface boards + Number of A interface boards + Number of Gb interface boards
2015-11-13
Huawei Confidential
Page 33 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
8
BOQ Review Guide
8.1 Design Overview 8.1.1 Purpose of the Design Review the pre-sales bill of quantities (BOQ) configuration based on accurate network planning information to ensure that the BOQ meets network construction requirements.
8.1.2 Input of the Design
Device BOQ
Network planning information (obtain the information, including the BSC coverage, traffic, location area code (LAC) partitioning, and BTS homing from the on-site network planning department.)
Information about the equipment room, power supply, or transmission of the customer, and special requirements of the customer
8.2 Overview of Pre-sales Network Design This section describes the pre-sales network planning and design as well as BOQ principles and process to guide network design personnel through BOQ review. In the network deployment scenario, the pre-sales network design procedures are as follows: 1.
2015-11-13
The pre-sales network planner plans the number of TRXs and the number of BTSs in the areas based on the capacity, coverage, and information, such as coverage, predicted number of subscribers, and traffic per subscriber, provided by the customer.
Huawei Confidential
Page 34 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
2.
The pre-sales network designer confirms the BSC locations and network topology based on the transmission conditions, equipment room resources, and core network of the customer.
3.
The pre-sales network designer uses the design tool to calculate the subrack and board BOQ configuration of each BSC based on the number of TRXs of each BSC, number of BTSs, half-rate ratio, transmission type, and number of BSCs.
In the network expansion scenario, the pre-sales network design procedures are as follows: 1.
The pre-sales network planner plans the number of sites and carriers to be added based on the congestion rate, coverage, and frequency planning of the live network.
2.
The pre-sales network designer calculates the number of pieces of BSC hardware required based on the number of sites, number of TRXs, half-rate ratio, and transmission type, deducts the number of pieces of existing hardware from the number of pieces of BSC hardware required to obtain the number of pieces of hardware to be added, and then generates the BSC device BOQ. The pre-sales planning of the core network is different from that of the BSS. The BOQ and interface bandwidth data of the core network are obtained directly based on the number of subscribers, traffic per subscriber, and certain redundancy. Therefore, interface bandwidth inconsistency may occur. Generally, the calculation result of the core network is smaller, and this causes the interface bandwidth inconsistency. The BSS planning does not involve bandwidth bottleneck and facilitates follow-up network development.
8.3 BOQ Review Principles Use the GSM NEP tool for BOQ review. In BOQ review, the number of pre-sales configured boards, especially the number of Abis interface boards, is reviewed. If spare BOQ hardware is configured, the review is successful. If the BOQ hardware is insufficient, check with marketing personnel whether to change the delivery. In the new network construction and migration scenarios, use the GSM NEP tool to calculate the required BSC hardware based on the number of BTSs, number of TRXs, and traffic model, and check the requirements against the pre-sales BOQ. In the expansion scenario, use the GSM NEP tool to calculate the required BSC hardware based on the number of BTSs, number of TRXs, and traffic model after expansion, deduct the existing BSC hardware to obtain the number of pieces of hardware to be added, and check the number against the pre-sales expansion BOQ. To meet the special requirements of some operators, the actual number of pieces of hardware in BOQ delivery is far greater than the actual required number of pieces of hardware. In terms of BTS distribution, the following principles are recommended (you communicate with the operator to learn the follow-up expansion plan): BTSs are evenly distributed to subracks and Abis interface boards based on a certain redundancy ratio. This facilitates follow-up TRX expansion or BTS addition. Traffic model parameters The following content is quoted from the GBSS15.0 BSC6910 system capacity calculation manual. Ensure that the following content is for internal use only.
2015-11-13
Huawei Confidential
Page 35 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
In this document, parameters are described in tables. Different colors in tables convey different meanings as follows: Parameter
Title
TRX Number
Parameter name
0.02
It is an input parameter, which is entered based on the network planning and design result. You can use the default value (if available) of an input parameter if the entered value cannot be obtained. The calculation result based on the default value is different from the actual situation. Generally, the result calculated based on the default value is larger. That is, more device resources are required.
300
It is an advanced parameter. You can enter a value or directly use the default value.
98%
Automatically calculated result. Do not change this value unless you are absolutely confident of the new value. If you can provide the dimension result, you can use it, but you must ensure that the modification is correct.
8.4 CS Traffic Models The circuit switched (CS) traffic model affects the BSC system capacity in the following aspects:
CS traffic on the control plane in the system. It is measured by the BHCA. If the traffic on the air interface in the system is specified, the traffic model affects the BHCA traffic on the control plane in the system.
CS traffic on the user plane in the system. It is measured in Erlang. If the number of subscribers on the network is specified, the traffic model affects the traffic on the user plane in the system.
Table 1.1 CS traffic model parameters Parameter
2015-11-13
Name
Defau lt Value
Description
Average voice traffic CSErlPerSub per subscriber@BH(Erlang)
0.02
Average busy-hour CS traffic per subscriber
Average Call Duration(Second)
CSCallDuration
60
Average busy-hour conversation duration per subscriber
Percent of Mobile originated calls
CSMOCRatio
50%
Average busy-hour MOC ratio
Percent of Mobile terminated calls
CSMTCRatio
50%
Average busy-hour MTC ratio
Huawei Confidential
Page 36 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Parameter
Name
Defau lt Value
Description
Average LUs/sub/BH
CSLUPerSubinBH
1.2
Number of busy-hour location updates per subscriber
Average IMSI Attach/sub/BH
CSAttachPerSubinBH
0.15
Average busy-hour IMSI attachments per subscriber
Average IMSI Detach/sub/BH
CSDetachPerSubinBH
0.15
Average busy-hour IMSI detachments per subscriber
Average MO-SMSs /sub/BH
CSMOSMSPerSubinB H
0.6
Average busy-hour sent SMSs per subscriber
Average MT-SMSs /sub/BH
CSMTSMSPerSubinB H
1
Average busy-hour received SMSs per subscriber
Average intra-BSC HOs CSIntraHOPerSubinB /sub/BH H
1.1
Average busy-hour intraBSC handovers per subscriber
Average inter-BSC HOs /sub/BH
CSInterHOPerSubinB H
0.1
Average busy-hour interBSC handovers per subscriber
Paging Retransfer Ratio
PagingRetransferRatio
35%
Ratio of paging retries on the A interface in busy hours
Table 1.2 CS signaling load parameters Parameter
Name
Defau lt Value
Description
64k SS7 signaling links load
64kSS7SigLinkLoad
0.2
Busy-hour 64K signaling load
2M SS7 signaling links load
2MSS7SigLinkLoad
0.2
Busy-hour 2M signaling load
Table 1.3 GoS-related parameters
2015-11-13
Parameter
Name
Defau lt Value
Description
Grade of Service (GoS) on Um interface
UmBlockRatio
0.02
Um interface block ratio
Huawei Confidential
Page 37 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Grade of Service (GoS) on A interface
ABlockRatio
0.001
Device block ratio
Table 1.4 Other related parameters Parameter
Name
Defau lt Value
Description
Average MOCs/sub/BH
CSMOCPerSubinBH
0.6
Number of busy-hour calling times per subscriber = CSErlPerSub x 3600/CSCallDuration x CSMOCRatio
Average MTCs/sub/BH
CSMTCPerSubinBH
0.6
Number of busy-hour called times per subscriber = CSErlPerSub x 3600/CSCallDuration x CSMTCRatio
MR report/sub/BH
CSMRPerSubinBH
144
Average number of MRs reported by each subscriber in busy hours. Its weight in BHCA is zero. It is used only for reference.
Paging retransfer /sub/BH
CSRetransferPagingPe rSubinBH
0.56
Average number of paging retransmission times per subscriber in busy hours on the A interface.
Parameter relationship in the CS traffic model 2.
Relationship between CSMTCRatio and CSMOCRatio: CSMTCRatio = 1 – CSMOCRatio
3.
Relationship between CSErlPerSub, CSCallDuration, CSMOCPerSubinBH, CSMOCPerSubinBH, and CSMTCPerSubinBH: CSMOCPerSubinBH = (CSErlPerSub x 3600/CSCallDuration) x CSMOCRatio CSMTCPerSubinBH = (CSErlPerSub x 3600/CSCallDuration) x CSMTCRatio
4.
Calculation of CSMRPerSubinBH: CSMRPerSubinBH = (CSMTCPerSubinBH + CSMOCPerSubinBH) x CSCallDuration x2 In the preceding formula, the MRs that are not reported in the call stage. For example, the MRs reported in the short message service (SMS) and signaling connection stages, are not included.
5.
Relationship between CSRetransferPagingPerSubinBH and PagingRetransferRatio: CSRetransferPagingPerSubinBH = (CSMTCPerSubinBH + CSMTSMSPerSubinBH) x PagingRetransferRatio
2015-11-13
Huawei Confidential
Page 38 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
8.5 PS Traffic Models The packet switched (PS) traffic model affects the BSC system capacity in the following aspects: If the number of subscribers in the system is specified, the PS traffic model determines the total traffic of PS services in the BSC. The PS traffic model consists of the following:
Basic PS traffic model (This model is new in the R13. In R12 and earlier versions, only the PS user model is available.)
PS user model (For details about this model, see Table 1.2.)
Table 1.1 Basic PS traffic model Parameter
Name
Value
Description
Uplink TBF Est & Rel / Second/TRX
TBFUpPerSec PerTRX
1.75
It indicates the average number of uplink TBFs per second for each TRX in peak hours. Its default value is 1.75 for common networks and is 3.5 for PS networks with heavy traffic.
Downlink TBD Est & Rel / Second/TRX
TBFDownPerS ecPerTRX
0.9
It indicates the average number of downlink TBFs per second for each TRX in peak hours. Its default value is 0.9 for common networks and is 1.8 for PS networks with heavy traffic.
PS Paging / Sub/BH
PSPagingPerS ub
1.25
It indicates the number of received peak-hour pagings for each PS subscriber. Its default value is 1.25 for common networks and is 2.5 for PS networks with heavy traffic.
Table 1.2 PS user model
2015-11-13
Parameter
Name
Valu e
Description
GPRS Active Sub
PSSubAct
10000
Number of online GPRS/EGPRS subscribers
average traffic per sub in busy hour (bit/s)
PSTrafficPerSubinBH
300
Average GPRS/EGPRS traffic per online subscriber in busy hours (application layer)
PS Traffic Peak Ratio
PSPeakRatio
25%
Ratio of the difference between the PS peak traffic and the average traffic to the average traffic. Do not use this parameter if it is not required.
Huawei Confidential
Page 39 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
average IP packet data length in Gb (Bytes)
PayloadLenGb
300
Average packet length on the Gb interface. Do not use this parameter if it is not required.
Table 1.3 PS coding ratio and average rate code scheme
Ratio
CS1
0%
CS2
0%
CS3
0%
CS4
0%
MCS1
0%
MCS2
0%
MCS3
0%
MCS4
0%
MCS5
0%
MCS6
100%
MCS7
0%
MCS8
0%
MCS9
0%
The sum of the preceding coding rate ratios must be 100%. Generally, the customer cannot provide the ratios of coding rates during calculation. You can use the customer-expected average rate to replace the inputs. For example, the customerexpected average rate is about 30 kbit/s. According to the preceding table, this average rate is within the rate range of the MCS6 coding mode. In this case, you can simply enter 100% as the ratio of the MCS6 coding mode.
8.6 Relationship Between Traffic Model and Traffic Statistics Traffic model indicates the average number of typical subscriber behaviors for a subscriber. The total number of these subscriber behaviors can be obtained from the traffic statistics. The traffic model for a subscriber equals the total number divided by the number of subscribers. The number of subscribers (SubPerBSC) served by a BSC must be available and accurate in the calculation of the traffic model. Table 1.1 lists the performance counters corresponding to basic procedures.
2015-11-13
Huawei Confidential
Page 40 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Table 1.1 Performance counters corresponding to basic procedures
2015-11-13
Basic Procedure (Subscriber Operation)
Performance Counters (Sum of Cell Performance)
CS LUs (Location Update)
A300F: Channel Requests (Location Updating)
Average IMSI Attachs (IMSI Attachs)
From MSC
Average IMSI Detachs (IMSI Detachs)
From MSC
CS calls
A300A: Channel Requests (MOC) + A300C: Channel Requests (MTC) – CA334A: Total Uplink Point-to-Point Short Messages – CA334B: Total Downlink Point-to-Point Short Messages
MR Reports
S329: Number of Power Control Messages per Cell
CS SMS (sending and receiving)
CA334A: Total Uplink Point-to-Point Short Messages + CA334B: Total Downlink Point-to-Point Short Messages
Intra-Hos (intra BSC)
CH310: Number of Outgoing Internal Inter-Cell Handover Requests
A9201: Number of Uplink EGPRS TBF Establishment Attempts + A9001: Number of Uplink GPRS TBF Establishment Attempts
Downlink TBF Est
A9301: Number of Downlink EGPRS TBF Establishment Attempts + A9101: Number of Downlink GPRS TBF Establishment Attempts
PS Paging
A331: Delivered Paging Messages for PS Service
Huawei Confidential
Page 41 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
9
Parameters for Capacity Calculation
Please refer to the latest BSC6900 Capacity Calculation Manual which you can download from http://3ms.huawei.com. http://3ms.huawei.com/mm/docMaintain/mmMaintain.do? method=showMMDetail&f_id=GSM14040308540024
10
Capacity Calculation
Please refer to the latest BSC6900 Capacity Calculation Manual which you can download from http://3ms.huawei.com. http://3ms.huawei.com/mm/docMaintain/mmMaintain.do? method=showMMDetail&f_id=GSM14040308540024
Reference: Impact on Interface Transmission Bandwidth After VLAN Is Deployed VLAN is a data exchange technology derived from traditional LAN. VLAN allows LAN devices to be logically grouped into multiple network segments (that is, smaller LANs) to implement virtual workgroups. The hosts in the same VLAN communicate
2015-11-13
Huawei Confidential
Page 42 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
with each other through VLAN switches. The hosts in different VLANs are separated from each other and they only communicate with each other through routers. A VLAN is a broadcast domain, that is, a host in a VLAN can receive broadcast packets from the other hosts in the same VLAN but cannot receive any broadcast packets from other VLANs. The advantages of VLAN are as follows:
Suppresses broadcast storm
Improves transmission security
Provides differentiated services
VLAN Frame Format The VLAN frame format is defined in IEEE 802.1Q. Compared with a standard Ethernet frame, the VLAN frame is added with a four-byte VLAN tag in its header, as shown below.
The fields of the VLAN tag are described as follows:
TPID: specifies the VLAN tag protocol identifier defined by IEEE. If a VLAN frame complies with IEEE 802.1Q, TPID is permanently set to 0x8100.
VLAN priority: specifies the priority of a VLAN frame. The priority ranges from 0 to 7. Ethernet provides differentiated services based on the VLAN priority.
Canonical Format Indicator (CFI): specifies the format of a frame that is exchanged between the bus Ethernet and a Fiber Distributed Data Interface (FDDI) or between the bus Ethernet and the token ring network.
VLAN ID: specifies the VLAN to which a frame is to be sent. Each VLAN is identified by a VLAN ID.
Application scenario: Only Ethernet IP networks. The related BSC6910 parameters are as follows:
VLANID: This parameter specifies the identifier of a VLAN. The VLAN ID mapping should be preconfigured in the BSC6910. According to the VLAN ID mapping, the BSC6910 determines the VLAN ID to send a VLAN frame. The BSC6910 supports two VLAN configuration modes: −
Configuring VLAN by next hop: The VLAN ID is determined according to the preconfigured mapping between the next-hop IP address and the VLAN ID. The related parameters are IPADDR and VLANID.
2015-11-13
Huawei Confidential
Page 43 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
−
Configuring VLAN by data flow The VLAN ID is determined according to the preconfigured mapping between the SCTP link, IP path, and VLAN ID. The parameters related to SCTP link are SCTPLNKN, PATHID, and VLANID.
VLANPRI: This parameter specifies the priority of a VLAN frame.
VLAN configuration modes supported by different interfaces on the BSC6910 on the GSM networks are as follows:
The A and Abis interfaces support configuring VLAN by next hop or data flow.
The Gb interface supports configuring VLAN by next hop.
The Ater interface supports configuring VLAN by next hop or data flow when IP over E1 is not in use.
Impact assessment: With the increasing deployment of IP networking, in particular, with the increasing deployment of VLAN networking on IP networks, VLAN tags have certain impact on IP transmission bandwidth over the Abis interface. The actual impact varies according to different compresses and transmission rate, and the average impact is about 3.5%. Detailed calculation method: If IP multiplexing (MUX) is not in use, a four-byte (32-bit) VLAN tag is added to a 20-ms voice (data) frame.
If MUX is in use, a four-byte (32-bit) VLAN tag is added to voice (data) frames that are transmitted at an interval of 20 ms. Therefore, VLAN tag resources are saved if MUX is in use.
2015-11-13
Huawei Confidential
Page 44 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
11
Design of Resource Allocation
11.1 Design Overview 11.1.1 Purpose of the Design
Review the traffic and BHCA load of each device based on accurate network planning information. If a load risk exists or the traffic exceeds the specifications, adjust the BTS homing. If the BTS homing cannot be adjusted, negotiate with the customer and marketing personnel to purchase more devices (under the guidance of marketing personnel).
Configure BSC boards in proper slots based on the BSC traffic and BHCA to balance the BSC load, improve the device resource usage, and improve the anti-attack capability.
Review the specifications information about the MSC, MGW, and SGSN to check whether the capacities are enough and assess the risk.
11.1.2 Input of the Design
Device BOQ
Network planning information (Obtain the information, including the BSC coverage, traffic, LAC partitioning, and BTS homing from the on-site network planning department.)
Information about the equipment room, power supply, or transmission of the customer, and special requirements of the customer
11.2 BSC Load Allocation This section assesses the BSC load risks, including the current traffic model and target traffic model based on the current device processing capability, and lists the percentages of the BHCA and traffic load of each BSC in the design specifications.
11.2.1.1 Design Principles
2015-11-13
The predicted BSC traffic load does not exceed 70% of the design specifications.
The predicted BHCA load does not exceed 70% of the design specifications.
TRXs are allocated to subracks evenly to balance the load and reduce signaling transfer between subracks.
The number of TRXs configured in each subrack needs to be less than 70% (it is for flexible follow-up adjustment and expansion but is
Huawei Confidential
Page 45 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
not mandatory) of the specifications to facilitate follow-up site adjustment and expansion. If the preceding principles conflict with the marketing BOQ, follow the marketing BOQ, and improve the overall system capacity by optimizing capacity resource allocation. If the traffic load or BHCA load exceeds 60%, experts in the Huawei headquarters assess the risk.
Confirm the BSC traffic capacity and BHCA specifications in the current configuration based on the configuration in the marketing BOQ. Assess whether the BSC resource load meets the requirements based on the traffic model, traffic capacity, and BTS homing. The BSC traffic calculated by the GSM NEP is the traffic capacity of the BSC. It is obtained based on the number of TRXs, number of BTSs, congestion rate, and erlang_B table. The actual traffic can be obtained from the customer or network planner. The calculation formula is as follows:
Actual BSC traffic = Predicted number of subscribers x Busy-hour traffic per subscriber
Actual BSC BHCA = Predicted number of subscribers x Busy-hour BHCA per subscriber
Actual BSC traffic load = Actual BSC traffic/BSC traffic specifications
Actual BSC BHCA load = Actual BSC BHCA/BSC BHCA specifications
Huawei's recommended expansion standards are as follows:
The number of TRXs configured for the BSC reaches 70% of the capacity specifications.
The busy-hour traffic exceeds 70% of the specifications.
The busy-hour BHCA exceeds 70% of the specifications.
The busy-hour central processing unit (CPU) usage exceeds 70%.
The SS7 link load exceeds 40%.
The CIC traffic per line exceeds 0.7 ERL.
Output of the design Table 1.1 BSC capacity planning table BSC Name
BTS Numbe r
Traffic
BHCA
Foreca st
Foreca st
TRX Numbe r
TRX
TRX
Traffic
BHCA
Capacit y
Perce nt
Perce nt
Percen t
For BHCA calculation note, see section Error: Reference source not found.
9.1.1 Signaling Storm 11.2.1.2 Concept of Signaling Storm Signaling storms first rose on the 3G network. Under the impact of a large number of signaling messages, major signaling processing channels become the bottleneck of the
2015-11-13
Huawei Confidential
Page 46 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
network, and CPU usage on the control plane of both the radio network controller (RNC) and NodeB increases sharply. Moreover, a smart terminal attempts to access the network at an increasingly short interval, once some signaling messages are discarded. Consequently, the already heavy signaling traffic becomes even heavier, which causes a signaling storm. The signaling storm threatens equipment security of both the RNC and NodeB, and seriously decreases the processing capacity of the system. A typical phenomenon is that the serving capacity of the system decreases. That is, high RRC and radio access bearer (RAB) rejection rates occur when the data traffic is low.
11.2.1.3 Current State of Signaling Storm As the penetration rate of smart terminals increases, the feature of high signaling traffic on smart terminals stands out. Statistics shows that smart terminals have seen an increase in signaling traffic, which is 15 times that in traditional terminals. Part of the UMTS network has been affected by signaling storms. For example, some subscribers of China Unicom in Beijing failed to access the network after the congestion rate increases in the core network (CN) of the X office in Beijing in 2010. Some subscribers of StarHub in Singapore had the same problem in 2011. Moreover, some subscribers of TELUS in Canada failed to access the network after many signaling messages were discarded by the CN of the X office. Some subscriber of NTT DoCoMo in Japan failed to access the network, and performance and reliability of the network were affected for the same reason.
11.2.1.4 Causes of Signaling Storm A signaling storm rises from too many signaling messages, which are caused by the following factors: Smart phone penetration rate increases year on year. After smart phones were introduced, services, including low-traffic services, have been diversified. Smart terminals and mobile network services are increasingly popular. To provide better user experience, smart terminals periodically send heartbeat packages to the network server to synchronize the information at the request of such applications as QQ and MSN Messenger. Heartbeat packages are small data packages of hundreds or thousands of bytes sent every dozen seconds or tens of seconds. The heartbeats of different applications and the system result in frequent PS calling. According to the 3rd Generation Partnership Program (3GPP), a terminal in the connected state can send a signaling connection release indication (SCRI) to the RNC in some scenarios. An SCRI carries different cause values in different scenarios. For example, a smart terminal sends an SCRI with the cause value being "UE Requested PS Data session end." to indicate the end of a PS data session. The greatest bottleneck of an MS lies in the battery. To save power, a smart terminal automatically sends an SCRI to the RNC at the end of a data session to release the RRC signaling connection and returns to the idle state. However, some applications on the terminal need to periodically send heartbeat packages to the application server. As a result, a connection to the RRC is re-established, and the UE returns to the connected state. After a small-size heartbeat package is sent, the RRC connection is released again, and the cycle goes on and on. As many as 30 pieces of signaling over the Uu interface and Iub interface are required in every PS data transmission, which makes the traffic model change significantly and the packet calling attempts exceed the voice calling attempts.
11.2.1.5 Impact of Smart Phones on the 2G Networks Signaling storms in the UMTS network rise from too many signaling messages caused by a large number of smart phones and low-traffic services. Whether signaling storms are likely to
2015-11-13
Huawei Confidential
Page 47 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
raise in the 2G networks as the penetration rate of smart phones rapidly increases? An analysis is made in multiple dimensions.
Impact of the heartbeat service model of smart phones over the average service model in the GSM Use the live network in Hangzhou city of China Mobile Group Zhejiang Company Ltd as an example. As shown in Figure 1.1, the heartbeat service model of smart phones is the same as the average service model in the GSM.
Figure 1.1 Average service duration
Impact of access to the GSM over the core network −
When uplink data exists on the MS, the MS is switched to the Ready state and directly sends the data. No authorization or encryption is required.
−
The state changes from Ready to Standby, if the time when no signaling message exists over the Gb interface exceeds a time prescribed by a timer on the SGSN side.
−
When downlink data exists on the network side, the Gb interface sends a paging message. In response, the MS returns a correct logical link control (LLC) frame.
−
Frequent service triggering does not increase signaling messages other than paging messages over the Gb interface.
To sum up, signaling interworking does not exist between the GSM service access and the core network.
2015-11-13
Huawei Confidential
Page 48 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Signaling in each access to the GSM When the GSM network is accessed, the number of signaling messages is less than three on the wireless network side, much less than the 25 signaling messages in the UMTS network (not considering interworking with the core network).
2015-11-13
Signaling load on the common control channel (CCCH) −
Based on the loading capacity of the base station subsystem (BSS), the loading efficiency of the packet data channel (PDCH) is 9 kbit/s when a cell uses a maximum of 64 PDCHs. Two CCCHs can meet the requirements of the PS signaling load when the cell enables the multi-CCCH function.
−
The CCCH resource usage efficiency can be further improved by multi-layered paging.
−
Channel management by layer improves signaling resource usage efficiency, gives priority to access of voice services, and prevents the heavy PS load from affecting the CS services.
−
The CCCH resources can bear the signaling load and do not form a bottleneck.
Huawei Confidential
Page 49 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Signaling load on the LAPD resources The load on the LAPD link mainly comes from the load on the B RSL link, which affects the CS paging messages, CS immediate assignment messages, PS paging messages, and PS immediate assignment messages. The LAPD resources can bear the signaling load and do not form a bottleneck.
−
The number of LAPD links required by the PS service is calculated according to the following specifications: On a 16 kbit/s timeslot, the maximum signaling load has 2000 Bytes/s.
−
Number of bytes in paging messages: 21 Bytes
−
Number of bytes in PS immediate assignment messages: 27 Bytes
The eXtensible processing unit (XPU) resources The following figure describes the subsequent networking planning requirements of China Mobile Group. Huawei's XPU design specifications can meet the BHCA requirements and do not form a bottleneck. In all-IP mode, the latest product BSC6910 has a BHCA specification of 52,000 K, which is much higher than the specification of the BSC6900.
2015-11-13
Huawei Confidential
Page 50 of 258
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
CONFIDENTIAL
−
Flow control on the XPU of the BSC ensures that the PS paging times in a period and the channel requests by the PS services in a period are controllable.
−
The increase in signaling services caused by the increase in the traffic of the current data services does not have an impact over the XPU of the BSC. In event of sudden increase in signaling messages, the flow control on the XPU guarantees the loading security on the XPU and deals with the impact of the PS services over the CS services.
−
The BSC BHCA specification of the BSC6910 is 52000 K (all-IP networking mode).
The data processing unit (DPU) resources As the version is updated, the DPU supports an increasing large number of PDCHs. The DPU resources can bear the signaling load and do not form a bottleneck.
The BSC6910 does not use the XPU and DPU boards separately. Functions of both XPU and DPU boards are integrated in EGPUa boards. An EGPUa (GCUP) board supports 1000 TRXs and 3000 PDCHs, almost twice the number of TRXs (512) and PDCHs (1024) supported by the original XPU and DPU boards. Based on the above analysis, the BSC6910 does not have a bottleneck in processing capability of the XPU and DPU boards.
2015-11-13
Impact of smart phones over the 2G network (based on the data of China Mobile Group Zhejiang Company Ltd) −
The 2G network subscriber base remains unchanged. However, traffic of smart phone users is 2.9 times that of non-smart phone users.
−
Market penetration rate of small phones reached 19% in 2011. The total traffic increases to 2.35 times that of the current traffic, if non-smart phones are substituted by smart phones.
−
The average loading efficiency of the PDCH is 4 kbit/s on the live network. When the loading efficiency of the PDCH increases to 9 kbit/s and the specification of equipment is improved to support more channels, the traffic in the 2G network can increase to 2.35 times the current traffic.
Huawei Confidential
Page 51 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Heartbeat duration of application services is adjusted to reduce the impact over the network −
Tencent increases the heartbeat duration of its program QQ (30 to 180s) to reduce the impact over the network.
−
Apple launched APNS, a server to send notification messages to such terminals as iPhone in a secure and timely manner, to manage heartbeats and increase heartbeat duration.
Development trend View of the operator (VF): The GSM network will evolve to be a low-cost and low-traffic network for the following reasons: −
The spectrum resources of the GSM will decrease because part of the resources is given to the UMTS and LTE in spectrum refarming. As a result, configuration for the BTS degrades in the GSM.
−
The legacy UE evolves towards smart phones and the traffic becomes increasingly low.
11.2.1.6 Conclusion of Impact of Smart Phones over the 2G Network Based on the analysis above, signaling storms do not occur on the 2G network. The conclusion may be updated depending on the future development.
11.3 BSC Board Layout Design 11.3.1 Design Guide Design board layout between subracks for the BSC based on the BOQ for load balancing and work out the board configuration figure. Purpose of board layout design:
2015-11-13
Decrease the number of messages forwarded between subracks to improve the BSC performance.
Balance the load between subracks to improve the anti-attack capability.
Huawei Confidential
Page 52 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Reserve certain port redundancy to facilitate site adjustment and expansion.
Deploy logical boards of the same type in a centralized manner to reduce interleaving with boards of different types.
Deploy electrical interface boards on one side and optical interface boards on the other side to facilitate cable connection.
Use different boards to provide 2G and 3G services to reduce the impact of software upgrade and board adjustment on services.
Allocate slots properly to maximize the board processing capability (the switching capability of the slots on the backplane differs).
In an office where traffic is heavy, board layout is important. Proper board resource allocation can maximize the processing capability of the device, balance the load, and improve the antiattack capability of the device.
11.3.1.1 BSC6910 Design Principles Design Principles (Use the NEP Tool to automatically generate the board layout figure, and the following principles are only for your reference)
Reduce inter-subrack signaling transfer. Ensure that the processing capabilities of the Abis interface board, A interface board, and embedded packet control unit (PCU) in the same subrack match each other.
Balance the load between the subracks of the BSC. The GMPS needs to process data, such as operation and maintenance (O&M), traffic measurement, and alarms. The XPU load is relatively high. The number of TRXs configured in the GMPS subrack is relatively small. Therefore, in the case of Abis interface board imbalance between BM subracks, the number of Abis interface boards configured for the GMPS is small.
Install interface boards in rear slots and service processing boards in non-fixed slots. Therefore, preferentially install service processing boards in front slots. Deploy the A interface board, Abis interface board, and Gb interface board separately, and deploy logical interface boards of the same type (A interface board, Abis interface board, and Gb interface board) together.
Deploy boards of the same type (physical boards or logical boards) from the middle to sides in the subrack to facilitate follow-up board expansion.
Deploy optical interface boards and electrical interface boards on different sides in the subrack. Do not deploy them on the same side.
The ENIU board (data service identification board with a specification of 1000 Mbit/s over the Gb interface) can be inserted in slots that do not hold the OMU and GGCU of the BM subrack. The recommended slots are slots 2 and 3, and the priorities of slots are 2 to 7. ENIU boards are preferably configured with the same subracks of the Gb interface board (to reduce traffic between subracks). The system can be configured with a maximum of 15 ENIUa boards. The ENIUa board can only be configured in 10 G slot.
When a customer purchases and uses Huawei's Nastar, the ESAUa boards need to be inserted in the BSC6910. The ESAUa board may be inserted in other idle slots other than the fixed slots. An ESAUa board occupies two slots. Configure the ESAUa board in the active subrack.
Deployment of 10G Slots in the BSC6910
2015-11-13
Huawei Confidential
Page 53 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
The following describes a method for configuring a main subrack: Every BSC6910 must be configured with only one PCS main subrack.
Assign EOMUa switch boards to slot 10 to 13. SCUb boards are assigned to slot 20 and 21, and EGPUa boards for resource management are assigned to slot 8 and 9.
Configure the BSC6910 with two PCS GCUa boards, when a GPS clock is required. Configure the BSC6910 with two PCS GCGa boards, when a GPS clock is not required. Assign GCUa/GCGa boards to slot 14 and 15.
When a customer purchases Huawei's Nastar, ESAUa boards are required in the BSC6910.
EGPUa/ESAUa boards can be inserted in other idle slots other than the fixed slots. The following assignment is recommended:
2015-11-13
−
Assign ESAUa boards to slot 0 and 1.
−
Preferred slots for EGPUa boards are slot 2 to 7.
The following assignment is recommended for GOUc/FG2c/EXOUa/POUc boards: −
EXOUa boards can only be assigned to slot 16 to 19 and slot 22 to 25.
−
Preferred slots for GOUc/FG2c/POUc boards are slot 16 to 19 and slot 22 to 25. When these slots are inadequate, they are assigned to slot 26 to 27.
Huawei Confidential
Page 54 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
The following describes a method for configuring an extended processing sub rack:
SCUb switch boards are assigned to slot 20 and 21.
If a customer purchases Huawei's Nastar, ESAUa boards are required. Configure ESAUa boards in the main subrack.
EGPUa boards can be assigned to other idle slots other than slot 20 and 21. The recommended slots are slot 0 to 13.
GOUc/FG2c/EXOUa/POUc boards are interface boards.
EXOUa/POUc boards can only be assigned to slot 16 to 19 and slot 22 to 25.
Preferred slots for GOUc/FG2c boards are slot 16 to 19 and slot 22 to 25. When these slots are inadequate, assign GOUc/FG2c boards to slot 26 and 27.
Principles of EGPUa/EXPUa configuration
2015-11-13
Huawei Confidential
Page 55 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Service processing boards used by the BSC6910 include EGPUa and EXPUa boards. EXPUa boards are used in the GSM other than the Universal Mobile Telecommunications System (UMTS). Logical types of service processing boards are RMP, GCUP, GMCP, or NASP.
EXPUa and EGPUa boards can be configured in both GO and GU mode. By default, EXPUa boards are configured in GO mode and EXPUa in GU mode.
In the UO mode, only EGPUa boards can be configured, instead of EXPUa boards.
Principles of EGPUa/EXPUa configuration for the RMP: In the GO mode, the RMP can use EXPUa or EGPUa boards. By default, the RMP uses the same board as the GCUP. In the GU/UO mode, the RMP can only use EGPUa boards.
Principles of EGPUa/EXPUa configuration for GMCP: In the GO/GU mode, the GMCP can use XPUa or EGPUa boards. By default, the GMCP uses the same board as the GCUP.
Principles of EGPUa/EXPUa configuration for the NASP: The NASP can only use EGPUa boards, instead of EXPUa boars.
Principles of RMP configuration The system is configured with only one RMP pair in the MSP subrack, one active and one standby board.
Principles of GCUP configuration Service processing boards are configured according to the BSC capacity planning. Different calculation methods are applied for the BSC6910 and BSC6900. In the BSC6900, numbers of XPUa/XPUb boards on the control plane, DPUd/DPUg boards on the PS user plane, and DPUc/DPUf boards on the CS user plane are calculated differently. For boards on the control plane, the number is the larger value calculated based on the planned TRX number and the comprehensive BHCA. For boards on the PS user plane, the number is calculated based on the number of PDCHs. For boards on the CS user plane, the number is calculated based on the predicated traffic volume. In the BSC6910, the EGPUa boards are used. Each GCUP board has the following specifications: BTS number, cell number, TRX number, comprehensive BHCA, number of PDCHs, and traffic volume. Divide the site-planned overall specification by the basic specifications above respectively, to obtain several board numbers. The greatest of these numbers is the number of boards to be configured. Table 1.1 describes the specifications of the EGPUa boards.
2015-11-13
Huawei Confidential
Page 56 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
Table 1.1 Specifications of the EGPUa board TRX
1000
Cell
600
BTS
600
Traffic volume
6250
6.25 Erlang per TRX on average
PDCH
3000
3 PDCHs per TRX on average
PS throug hput
300 Mbit/s
3000 × 100 kbit/s, EGRPS2A
Compre hensive BHCA
2200 K
The value is based on the actual benchmark weights and considers the PS BHCA. The PS BHCA is based on the comprehensive BHCA of Huawei's default traffic model.
GCUP boards do not support the active/standby mode. The number of redundant boards can be manually specified in the redundancy configuration. By default, if the number of GCUP boards required is X in capacity calculation, another GCUP board is configured. Each BSC is configured with at least two redundant boards.
Principles of GMCP configuration GMCP boards are configured according to the IBCA deployment requirements. If the IBCA function is enabled, one GMCP board supports 2048 TRXs. GMCP boards do not support the active/standby mode.
Principles of NASP configuration NASP boards are configured according to the deployment requirement of network assisted WLAN identification. If this feature is enabled, a BSC is configured with only once NASP board.
Principles of ENIUa configuration If the feature of intelligent service identification is enabled, ENIUa boards are required. A BSC is configured with only one ENIUa board.
Principles of ESAUa configuration If a customer purchases the Nastar, the ESAUa board needs to be configured in the BSC. A BSC is configured with only one ESAUa board.
2015-11-13
Huawei Confidential
Page 57 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
12
Naming Rules Design
12.1 Design Overview 12.1.1 Purpose of the Design
This section designs the numbering and naming rules for all the NEs on the network to make network topology clear and facilitate network management.
Standard numbering and naming facilitate maintenance. Directly locate faults by using alarm information to improve maintenance efficiency.
12.1.2 Input of the Design
Information, such as geographical distribution and the number of NEs, area names, office names, and NE types
NE naming specifications and requirements of the customer. In the high-level design (HLD), naming rules of NEs are determined based on naming conventions and planning requirements of the customer, and Huawei's naming rules. This document describes the naming and numbering rules recommended by Huawei. However, most customers use their own NE naming rules. In actual applications, communicate with the customer and then determine the naming and numbering rules based on the customer requirements and the rules recommended in this document.
12.2 NE Naming Rules 12.2.1 Naming Rules of Areas Network design is performed based on areas. Therefore, it is necessary to name the areas. Use the short name of the geographical name of an area to name the area. For a geographical name in China, use the capital letters in the full pinyin name. For example, the publicly known short name of Lagos, Nigeria is LOS. Use LOS as the name of Lagos.
2015-11-13
Huawei Confidential
Page 58 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
For example, the capital letters of the full pinyin name of Guangzhou is GZ. Use GZ as the name of Guangzhou.
12.2.2 Naming Rules of Offices Devices are installed in offices. Therefore, office naming is part of NE naming, and it is important for locating NEs quickly. Use the first three letters in the full English geographical name of an office. For a geographical name in China, use the capital letters in the full pinyin name. For example, a BSC office is located in Adekula in Nigeria. Use ADE as the name of the Adekula office. For example, a BSC office is located in Dian Xin Guang Chang in Xi'an. Use DXGC as the name of the Dian Xin Guang Chang office. If the short names of two are the same, lengthen the short name of one office to distinguish them. For example, two BSC offices are located in Okuno and Okuani in Nigeria. Use OKUN and OKUA as the names of the offices in Okuno and Okuani respectively.
12.2.3 Naming Rules of Manufacturers The network of an operator may use the devices of multiple manufacturers. Naming the manufacturers and using the manufacturer names in NE naming can help quickly distinguish the manufacturer of an NE. Use the commonly used manufacturer short names in the telecom field. Table 1.1 Manufacturer short names Manufacturer
Short Name
Huawei
HW
Ericsson
ERI
ZTE
ZTE
Nortel
NOR
Motorola
MOT
Samsung
SAM
Alcatel-Lucent
AL
UTSTARCOMM UT
UT
Nokia-Siemens
NSN
Cisco
CIS
There are numerous manufacturers, and this document lists only the commonly known ones.
2015-11-13
Huawei Confidential
Page 59 of 258
CONFIDENTIAL
Technical Guide to SRAN Network Design (GO Applicable to the SRAN10.0 & GBSS17.0 & BSC6910)
12.2.4 Naming Rules of NEs This document describes the naming rules only of the NEs on the radio side and the NEs closely related to the radio side. The short names of the NEs are as follows: Table 1.1 NE short names Network Element Type
