RG 10(BSS) for Network Planners Customer training material 1 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
RG 10 for Network Planners Site Solution Hardware Support • Flexi BSC(3 i 3000) and Double Capacity AS 7 Unit_BSS 21149 • Integrated IP card for BSC 3 i and TCSM 3 i_BSS 21157 • PCU 2 HW Evolution and Asymmetrical PCU HW configuration_BSS 21226 Radio Network Performance • AMR Handover Signaling Optimization_BSS 20916 • Unpacking AMR_BSS 21120 • Wideband AMR_BSS 20960 • Tandem Free Operation (TFO) for AMR_BSS 21118 • SDCCH and PS Data Channels on DFCA TRX_BSS 21161 • Downlink Dual Carrier_BSS 21228 Improvement in Operability • Energy Saving Mode For BCCH TRX_BSS 20958 • Flexi EDGE Dual TRX Automatic Power Down_BSS 20984 2 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Site Solution Hardware Support Flexi BSC and Double Capacity AS 7 Unit • Benefits • Architecture • Configuration steps • PCU capacity • Dimensioning rules (BSC, BCSU, PCU, ET) 3 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Site Solution Hardware Support Flexi BSC benefits Flexi BSC reduces OPEX • Circuit-switched capacity for voice 18000 Flexi BSC PDFU Erlangs GTIC ETC • 3000 TRXs and 3000 BTS sectors/sites in one GSW 2 KB GTIC ETC CLS • Packet data capacity for EDGE evolution up to GSW 2 KB 30720 Abis links (16 kbit/s) • New support of IP/Ethernet for all interfaces • Flexible transmission types (E 1/T 1, STM-1/OC 3, IP/Ethernet) © Nokia Siemens Networks RN 20092 EN 14 GLN 0 BCSU 2 FTRB BCSU 4 • Very high footprint efficiency • Excellent power consumption efficiency 4 BCSU 1 MCMU 500 TRX to 3000 TRX, license step one TRX LANU BCSU 7 OMU BCSU 3 FTRB LANU • Scalable in 6 HW capacity steps (BCSUs) from FTRB MCMU FTRB BCSU 5 BCSU 6 CLS cabinet
Site Solution Hardware Support Flexi BSC architecture Marker and Cellular Management Unit (MCMU) Base Station Controlling and Signalling Unit (BCSU) • Supervising of GSWB, executing RRM functions, internal traffic handling by Ethernet Message Bus (EMB) and LAN Switching Units (SWUs) • Handling of signalling traffic (LAPD, SS 7) incl. PCU Exchange Terminal (ET) • Connecting of transmission systems (E 1/T 1, STM 1/OC 3, PWE 3) to GSWB; several ET types are possible within Flexi BSC: ET 16, ETS 2, ETIP 5 © Nokia Siemens Networks Bit-oriented Group Switch (GSWB) • Switching CS/PS traffic, connecting signalling circuits RN 20092 EN 14 GLN 0 Operation and Maintenance Unit (OMU) • Supporting O&M for Flexi BSC incl. storage devices (interfaces to user/OMC/transmission/peripherals, alarm collection and indications, system configuration/management, BSC 3 i maintenance/administration, LAN topology management) Clock and Synchronization Unit (CLS) • Generating clock signals for BSC 3 i
Site Solution Hardware Support Flexi BSC Configuration Steps • Overview on Flexi BSC capacity – The following table presents the main capacity figures of the Flexi BSC #TRX per BSC 1… 500 501… 1000 1001… 1500 1501… 2000 2001… 2500 2501… 3000 #active BCSU 1 2 3 4 5 6 500 1000 1500 2000 2500 3000 5 10 15 20 25 30 max #PS Abis chan@16 5120 10240 15360 20480 25600 30720 max #RTSL 4000 8000 12000 16000 20000 24000 max #SS 7 links: 64 kbps 128 kbps 256 kbps 512 kbps 1024 kbps HSL 0 8 4 2 2 1 2 0 16 8 4 4 2 4 0 16 12 6 6 3 6 0 16 16 8 8 4 8 0 16 16 10 10 5 10 0 16 16 12 12 6 12 max #LAPD (*1) 992 1984 2976 3968 4960 5952 50 16 8 50 16 8 max #BTS / #BCF max #logical PCU 2 -E #PCM (*2): ET 16 SET ETIP (*1): #LAPD links achievable with “low capacity” SS 7 links. Therefore in 3000 TRX conf. SS 7 over IP (SIGTRAN) is recommended. (*2): #controllable PCM lines does not depend on #BCSU 6 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU capacity in Flexi BSC Site Solution Hardware Support • PCU functionality in Flexi BSC can be realized by both: - PCU 2 -E, a new plug in unit offering significant capacity enhancements - PCU 2 -D, • The following PCU configurations are feasible in Flexi BSC : - Each BCSU can be equipped with up to 5 PCU - BCSU can have a mixture of PCU 2 -D/PCU 2 -E - With Asymmetric PCU configuration feature all BCSUs within one BSC do not need identical PCU configurations - PCU 2 -D comprises 2 logical PCU, each logical PCU can handle up to 256 Abis PS channels@16 - PCU 2 -E comprises 1 logical PCU, it can handle up to 1024 Abis PS channels@16. 7 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Dimensioning Flexi BSC • Dimensioning concept same as with BSC 3 i: Site Solution Hardware Support - All static and dynamic limits are checked against the corresponding values determined per planning area - The basic formula is used to calculate the number of BSCs in a given area - The initial BSC utilization level is considered to leave capacity for future extensions and traffic growth • Flexi BSC offers high scalability and configuration variety: - In a given BSC the following items are calculated - The number required of BCSUs - The number of required PCUs - The number and types of the interface units/ports 8 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Dimensioning BCSU Site Solution Hardware Support • Working BCSU is needed for each 500 TRXs • Every BCSU is equipped with the number of AS 7 -D units sufficient to handle signalling traffic produced by 500 TRX • Also other units (power supply, CPU, memory) are always installed and do not need to be computed • Apart from this, BCSU can be equipped with up to 5 PCUs • The number of working BCSU per Flexi BSC can be computed by formula below: • Regardless of the amount of working BCSU an extra spare one is always needed for redundancy – N+1 redundancy principle applies for the BCSUs 9 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Dimensioning PCU 2 -E Site Solution Hardware Support • PCU 2 -E has several static limits (#Abis channels, #TRX, #BTS, #segments, #EDAPs, …) (For details about PCU 2 -E static limits please refer to product documentation) • Usually the most critical parameter in PCU dimensioning is the number of Abis channels that can be managed by PCU – PCU 2 -E serves 1024 Abis channels@16 kbps – PCU 2 -D serves 256 Abis channels@16 kbps • The number of PCU can be computed by means of the formula below: 10 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Dimensioning ET Site Solution Hardware Support • The number of Exchange Terminals (of given type) depend on how many PCM lines is terminated in Flexi BSC and what connectivity configuration has been chosen • The number of PCM lines can be computed by means of the formula below: • The next step is to decide which PCM lines will be connected to ET 16, ETS 2 and ETIP and to compute the required amount of PIU and cartridges to be installed 11 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Dimensioning ET Site Solution Hardware Support • Then the number of particular PIU can be computed as follows (ETSI standard): • Please note that the actual number of ETS 2 PIU depends on the number of required SET and number of optical interfaces activated per ETS 2 (1 or 2 optical interfaces may be active): - 1 optical interface per ETS 2 active: - 2 optical interfaces per ETS 2 active: 12 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Integrated IP card for BSC 3 i and TCSM 3 i • Benefits • Hardware Requirements • Functionality • Planning and dimensioning aspect 13 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Integrated IP card for BSC 3 i and TCSM 3 i Benefits • Ethernet based transmission networks are cheaper that E 1/T 1 networks comparing the same bandwidths • At the same time, more and more transport resources are expected to be needed due to: − Availability of services which leads to increase in data rates and in the amount of transport resources − Collaboration on the same site base station operating in different technologies (e. g. GERAN, UTRAN ) • Exchange Terminal for IP (ETIP) is fully integrated with the existing HW platform − ETIP (ETIP 1 -A) is designed in such a way that allows to be used instead of ETS 2 or ET 16, − Extends BSC 3 i/TCSM 3 i products flexibility and gives operator many new configuration possibilities − Any mixture of all S 14 compatible Exchange Terminals is fully allowed • All these reasons cause that IP over Ethernet BSS interfaces are supposed to be the most efficient realization of transport network in GERAN 14 © Nokia Siemens Networks RN 20092 EN 14 GLN 0 Integrated IP card for BSC 3 i and TCSM 3 i
Integrated IP card for BSC 3 i and TCSM 3 i ETIP 1 -A plug in unit ETIP 1 -A characteristics • • • 15 8+8 ETIP can be installed in Flexi BSC 8+8 ETIP can be installed in BSC 3 i 1000/2000 4+4 ETIP can be installed in TCSM 3 i (stand-alone) 126 E 1 / 168 T 1 per ETIP 1 -A (in BSC 3 i) 128 E 1/T 1 per ETIP 1 -A (in TCSM 3 i) 512 different WS (Pseudo Wires) 512 different PSN tunnels Fast Ethernet / Gigabit Ethernet external connectors Fast. E: mainly to be used for local O&M interface Gig. E: mainly to be used for PSN interface © Nokia Siemens Networks RN 20092 EN 14 GLN 0 Integrated IP card for BSC 3 i and TCSM 3 i
Integrated IP card for BSC 3 i and TCSM 3 i Functionality Integrated IP card for BSC 3 i and TCSM 3 i • TDM links can be replaced by IP over Ethernet links • Mapping of TDM traffic into IP packets possible thanks to PWE 3 (Pseudo Wire Emulation) − PWE 3 is a standardized mechanism which emulates the essential attributes of a service into Packet Switched Network (PSN). § Different services can be emulated by PWE 3 with CESo. PSN functionality (i. e. PWE 3 of TDM traffic ) • IP solution is applicable for Flexi BSC, BSC 3 i, TCSM 3 i and Flexi. EDGE BTS products − PWE for other elements can be implemented by additional products e. g. hi. D 3105/3140 HD. 16 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Integrated IP card for BSC 3 i and TCSM 3 i PWE 3 realization in BSS: CESo. PSN • CESo. PSN functionality – Circuit Emulation Service over PSN performs the following activities: § The TDM bit stream is segmented according to the user specified Time Slot Set (TSS) • bits transmitted by indicated PCM TS in subsequent TDM frames § Headers are added to each segment to form a manageable packet (encapsulation) § Packets are forwarded to the PSN tunnel and transmitted to its destination over Ethernet network § At destination, the original bit stream is reconstructed by removing headers, concatenating frames and regenerating the timing an E 1 line a resulting PW (also called CESo. PSN packet) TDM frame #1 Ch 24 TS 31 … TDM frame #2 Ch 24 TS 31 … TS 1 Ch 2 Ch 1 TS 0 TDM frame #3 Ch 24 TS 31 … TS 1 Ch 2 - 3 TDM frames mapped - PW composed of 31 TS Ch 1 TS 0 TS 1 Ch 2 Ch 1 TS 0 TS 31 Ch 24 … TS 2 Ch 1 TS 31 TS 1 Ch 24 … Ch 2 TS 2 payload TSS composed of 31 TS 17 © Nokia Siemens Networks RN 20092 EN 14 GLN 0 Ch 1 Ch 24 TS 1 TS 31 … TS 2 Ch 2 TS 1 Ch 1 CESo. PSN Header header Ref. P. Spennemann, Internal Ethernet/IP Interfaces for BSS Feature Request Sheet, FRS 94060, version 2. 0, May 2007
Integrated IP card for BSC 3 i and TCSM 3 i Planning and dimensioning aspects Integrated IP card for BSC 3 i and TCSM 3 i • Number of ETIP are needed to map the desired TDM traffic into a PSN using Ethernet links with chosen bandwidth (FE vs. GE). The following dimensioning aspects are: – Decide/choose which particular lines shall be mapped to a PSN – Define PWs (from TSS) for each PCM line to be mapped to a PSN – Define how many TDM frames shall be multiplexed within particular CESo. PSN packets – Compute a bandwidth required by each and every PW – Compute the number of required ETIP 1 -A • BSC 3 i can have mixture of traditional TDM lines (ET 16, ETS 2) and PW lines (ETIP) 18 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Integrated IP card for BSC 3 i and TCSM 3 i Planning and dimensioning aspects Parameters • The number of consecutive TDM frames per CESo. PSN packet (Nf) • The time slot set i. e. the number of TSL from the original E 1/T 1 (TSS) • Use of VLAN (CESo. PSN header 74 octets with VLAN and 70 octets without VLAN) Required Ethernet bandwidth: Illustration: 19 © Nokia Siemens Networks RN 20092 EN 14 GLN 0 TS 4 TS 5 TS 6 TS 29 TS 3 TS 4 Packet Header TS 5 TS 4 TS 3 TS 2 TS 1 TS 0 TS 31 TS 30 TS 29 TS 6 TS 5 TS 4 TS 2 TS 3 TS 1 =2 TS 29 TS 6 TS 5 TS 4 TS 3 TS 2 TS 1 TS 29 TS 6 TS 5 TS 3 TS 4 TS 1 TS 29 TS 6 TS 5 TS 4 TS 3 TS 2 TS 1 2 frames multiplexed, packetization time of 2*125 μs = 250 μs Packet TS 3 TS 0 TS 1 TS 31 TS 29 TS 30 TS 31 TS 6 TS 27 TS 28 TS 29 TS 5 TS 4 TS 3 TS 25 TS 26 TS 2 TS 1 bundle 1 - 29 (CESo. PSN) multiplier Header Timeslot allocated for Abis Timeslot unused TSx bundle 1 - 29 (CESo. PSN) TS 29 TS 5 TS 6 TS 4 TS 3 TS 2 TS 1 TS 24 TS 0 TS 1 TS 23 TS 31 TS 29 TS 30 TS 18 TS 6 TS 19 TS 17 TS 5 TS 20 TS 15 TS 16 TS 4 µs bundle 1 - 29 (CESo. PSN) TS 29 TS 6 TS 5 TS 4 TS 3 TS 2 TS 1 bundle 1 - 29 (CESo. PSN) TS 3 TS 14 TS 12 TS 0 TS 2 TS 11 TS 31 TS 9 TS 6 TS 10 TS 5 TS 30 TS 4 TS 8 TS 3 TS 29 TS 2 TS 7 TS 0 TS 1 TS 31 TS 30 TS 29 TS 0 TDM frame (E 1) 32 timeslots 125
Planning and dimensioning aspects Dimensioning aspects • Calculation example – Given: - 126 E 1 lines to be mapped 1 PW per E 1 line (each TSS composed of 31 TSs) 8 TDM frames per packet CESo. PSN header length of 74 bytes (VLAN is enabled) Gigabit Ethernet and Fast Ethernet links shall be checked – Calculations: - 20 packetization latency = 125 · Nf = 1000 μs (cf. eq. 2) => will be needed for time budget payload = 8 * TSS * Nf = 1984 bits (cf. eq. 2) => 248 bytes; payload size acceptable header = 8 * header_length = 592 bits (cf. eq. 2) BW / PW = (1984 + 592) / 1000 = 2. 576 Mbit/s (cf. eq. 1) OHF = (1984 + 592) / 1984 = 1. 29 29% (cf. eq. 4) BW / PSN = 2. 576 * 126 = 324. 58 Mbit/s (cf. eq. 7) GE link load = 324. 58 / 1000 = 32. 5% => all 126 E 1 can be served by 1 ETIP FE link load = 324. 58 / 100 = 324. 6 % => not possible!!! - With FE, 5 ETIP would be needed to handle 126 E 1 - 126 E 1 can be handled by 1 ETS 2 (with 2 optical interfaces) © Nokia Siemens Networks RN 20092 EN 14 GLN 0 Integrated IP card for BSC 3 i and TCSM 3 i
Planning and dimensioning aspects Integrated IP card for BSC 3 i and TCSM 3 i Impact on implementation planning • TCSM aspects – Stand-alone TCSM 3 i has the following characteristics ▪ Comprises of 1… 6 TC 2 C cartridges in a single Transcoder Cabinet ▪ Each TC 2 C houses 2 TR 3 E/TR 3 A PIUs • One TC 2 C cartridge can house two extension steps • One TC 2 C cartridge consist of up to 16 TR 3 E/TR 3 A units each up to 120 channels plus selected interface cards ▪ Each TR 3 x has the following transcoding capacity: • TR 3 E: 960 TCH ETSI (8 E 1 Ater lines) • TR 3 A: 768 TCH ANSI (8 T 1 Ater lines) ▪ Fully equipped TCSM 3 i can support: • 6 TC 2 C × 2 TR 3 E × 960 = 11520 TCH ETSI • 6 TC 2 C × 2 TR 3 A × 768 = 9216 TCH ANSI • 6 TC 2 C × 2 TR 3 E × 8 Ater lines = 96 E 1/T 1 Ater 384 E 1/T 1 A-IF • up to 24 BSC can be connected to a single TCSM 3 i cabinet – Implementation of CESo. PSN in TCSM 3 i ▪ 4 (active + spare) ETIP 1 -A can be installed in TCSM 3 i: Ref. P. Koski, M. Saukko, H. Tervonen, J. Toivinen, • 1 ETIP is used to handle Ater interface PWE Transport Support in BSC 3 i and TCSM 3 i, Requirements Specification, BSS 21157, version 1. 1. 0, January 2008 • 3 ETIP are used to handle A interface, one ETIP can serve 2 (adjacent) TC 2 C ▪ If the whole Ater is over IP the Ater ETIP in TCSM 3 i has to be configured as a synch master and an ETIP in the BSC as a synch slave. 21 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Planning and dimensioning aspects Integrated IP card for BSC 3 i and TCSM 3 i Impact on implementation planning • Redundancy aspects – ETIP 1 -A PIU is represented by functional unit ETIP – Redundancy implementation concept are: ▪ HW protection (N+N, active PIU has its own spare one) ▪ Line protection (each board has two individual Ethernet interfaces while only one of them is active at the time) • IP addressing – IP addresses of the devices installed in Flexi. BTS, BSC 3 i, TCSM 3 i are used during creation of PSN tunnel and its PWs: any mismatch is to be avoided 22 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
BSS 14 for Network Planners PCU 2 HW Evolution and Asymmetrical … Hardware Support • Flexi BSC and Double Capacity AS 7 Unit. • Integrated IP card for BSC 3 i and TCSM 3 i • PCU 2 HW Evolution and Asymmetrical PCU HW configuration 23 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU 2 HW Evolution and Asymmetrical … PCU 2 HW Evolution and Asymmetrical PCU HW configuration • Benefits • Configuration and capacity • Dimensioning rules (connectivity and asymmetrical setup) • Modified parameters, new alarms 24 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU 2 HW Evolution and Asym. PCU HW config. Benefits PCU 2 HW Evolution and Asymmetrical … PCU related S 14 features are expected to bring the following benefits • PCU 2 -E − − Allows to increase packet data capacity within the same space Optimized for Flexi BSC Supports higher user peak rates Better Gb link utilization. More cells per PCU gives better multiplexing gain in Gb. • Asymmetrical PCU HW configuration − Optimizes and simplifies PCU usage in different BCSU − Less PCU plug in units needed with the feature − Its benefit can be immediately seen in the scenarios like: § PCU capacity extension (in a single BCSU): user needs to add only 1 single PCU to the BCSU where insufficient PCU capacity is observed § TRX capacity extension: user needs to add another BCSU (without or with minimum PCU configuration) § Various amount of PCUs in different BCSU 25 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Benefits of PCU 2 -E PCU 2 HW Evolution and Asymmetrical … • PCU 2 -E can also be used in the BSC 3 i 660 and BSC 3 i 1000/2000 − Performance improvement is a prime reason to install PCU 2 -E in BSC 3 i types § Mixture of PCU 2 -E and PCU 2 -D is possible within BSC 3 i − Due to different internal structure in BSC 3 i and Flexi BSC the PCU 2 -E can reach half of its max possible capacity in when used in BSC 3 i 660/1000/2000 § PCU 2 -E can handle up to 512 Abis channels in BSC 3 i 660/1000/2000 26 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU 2 HW Evolution and Asymmetrical … Characteristics of PCU 2 -E capacity • PCU 2 -E capacity is collected in the table below together with the respective values of PCU 2 -D for comparison • The capacities below are achievable per logical PCU in Flexi BSC Parameter PCU 2 -E PCU 2 -D #logical PCU 1 2 #Abis channels 1024 256 #BTS objects 384 128 #EGPRS cells 256 64 #GPRS/EGPRS TRX 1024 / 720 256 / 192 #EDAP 60 16 #BCF 384 128 Note: PCU 2 -D capacity figures are maintained in RG 10 in comparison to S 13 ones 27 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU 2 HW Evolution and Asymmetrical … Gb interface capacity for PCU 2 -E and PCU 2 -D Parameter # max Gb throughput per logical PCU )* # of bearer channels per logical PCU capacity per FR link Total rate of FRLs / logical PCU 2 -E 8 Mbps (128 TSL x 64 kbps) 16 FRL/NS-VC 1… 31 TSL (1984 kbps) 128 x 64 kbps PCU 2 -D 2 Mbps (32 TSL x 64 kbps) 4 FRL/NS-VC 1… 31 TSL (1984 kbps) 32 x 64 kbps *) incl. both user traffic and overheads • Overall, applicable for both PCU 2 -E / PCU 2 -D − Max Gb throughput can be reached with more than 1 FRL − Gb over FR: capacity of the Frame Relay links may limit the PCU throughput − Gb over IP: Gb connectivity does not limit the PCU throughput 28 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Possible configuration of PCU 2 -E PCU 2 HW Evolution and Asymmetrical … • PCU 2 -E can be installed in Flexi BSC and any BSC 3 i but certain additional rules exist Abis bw in max conf BSC type max #PCU 2 -E per BCSU #Abis channels per PCU 2 -E #active BCSU per BSC / #logical PCU per BSC 3 i 660 1 (not 2) 512 6/6 ~ 98 Mbps BSC 3 i 1000 3 (not 5) 512 5 / 15 ~204 Mbps BSC 3 i 2000 3 (not 5) 512 10 / 30 ~ 409 Mbps Flexi BSC 5 1024 6 / 30 ~ 491 Mbps • PCU 2 -E can be installed neither in BSCi nor in BSC 2 i • There are 2 rules to be considered when using PCU 2 -E in BSC 3 i 660/1000/2000 − Limited number of PCU slots in BCSU can host PCU 2 -E due to limitations of power supply and cooling systems − 512 Abis channels can be reached due to connectivity implementation in BSC 3 i 660/1000/2000 29 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Mixed PCU configuration PCU 2 HW Evolution and Asymmetrical … • Different amount of PCUs in different BCSUs of the same BSC or different PCU HW variants in the same slots of different BCSUs • ‘mixed PCU configuration’ is possible however some restrictions exist, i. e. the following mixtures are allowed within the same BCSU track of different BCSU − PCU, PCU-S, PCU-T, PCU 2 -U, empty slot − PCU-B, PCU 2 -D, empty slot − PCU 2 -E, empty slot • Mixed PCU configuration in such context is a new functionality that leads to “asymmetrical” PCU configuration 30 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Asymmetrical PCU configuration PCU 2 HW Evolution and Asymmetrical … • Asymmetrical PCU configuration is available as a separate RG 10 feature • Before the feature: - Each BCSU in the BSC is equipped with the same PCU configuration (number of PCUs and their type) § For e. g. let’s assume a BSC 3 i 2000 equipped with 10 (active) BCSUs and 1 PCU in each BCSU § Let’s say that 1 out of 10 BCSUs needs another PCU to be installed (due to PS traffic) § To do so, each and every BCSU would need to have second PCU installed § 10 extra PCUs are needed in case of fully equipped BSC 3 i 2000 to add 1 PCU in 1 BCSU 31 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Asymmetrical PCU configuration • With the feature: - PCU can be installed and activated according to actual traffic needs with granularity 1 in every BCSU separately - Each active BCSU can have different number of PCUs (depending on actual traffic requirements), i. e. it may happen that some BCSU have no PCU units while the other ones have some PCU installed - Different PCU types can be mixed in the same BSC/BCSU (restrictions concerning the same BCSU track exist -> see previous slide) - BCSU which is marked as primary spare must be equipped with the number of PCU sufficient to replace any of the active BCSU 32 © Nokia Siemens Networks RN 20092 EN 14 GLN 0 PCU 2 HW Evolution and Asymmetrical …
PCU 2 HW Evolution and Asymmetrical … PCU 2 HW and SW Activation in S 14 For E. g. with Flexi BSC and with Asymmetrical PCU HW Configuration • Example : • Minimum configuration for 1 BSC => • 1 + 1 PCU 2 -E HW units + one PCU 2 BSW license PCU 2 BSW OPTIONAL – activated according traffic requirements • for spare BCSU In maximum four PCU 2 BSW licenses per one PCU 2 -E HW plug-in unit One PCU 2 BSW license = 256 Abis channels (16 kbit/s) PCU 2 -E HW PCU 2 BSW PCU 2 -E HW OPTIONAL – activated according traffic requirements • PCU 2 -E HW is installed according traffic requirements • PCU 2 -E SW is activated according traffic requirements • In minimum one PCU 2 -E HW unit + one PCU 2 -E HW unit PCU 2 -E HW PCU 2 BSW PCU 2 BSW Spare BCSU PCU 2 -E HW 33 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU 2 -E Dimensioning PCU 2 HW Evolution and Asymmetrical … • Impact of PCU 2 -E introduction on PCU dimensioning/planning – Overall PCU HW requirements for BSS 14 § All existing PCU units (PCU 1, PCU 2) could still be used with the basic S 14 SW release § All new packet data related application SW features would require PCU 2 – Impact of introduction of PCU 2 -E on PCU dimensioning - Dimensioning concept does not need to be modified - All static limits must be checked against the corresponding values determined per BSC (planning area) - Utilization rate should be additionally taken into account - The basic formula used for PCU dimensioning is 34 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
PCU 2 HW Evolution and Asymmetrical … Parameters • No new parameters • Modified parameters: only ranges of those parameters that are explicitly dependent on modified static limits should be subject to modification, e. g. new PCU variant (PCU 2 -E) must be configurable in addition to former types Parameter name (abbreviation) Range and step, default value Description Object name Plug-in Unit Type (piu. Type) Range: 276 (pcu_c), 365 (pcu_s_c), 379 (pcu_t_c), 398 (pcu 2_u_c), 979 (pcu_b_c), 985 (pcu 2_d_c), 995 (pcu 2_e_c), 1023 (no_piu_type_info_c) Default: 1023 PCU plug-in unit type. The attribute describes the PCU HW variant. PCU Bearer Channel Identifier (fr. Bearer. Channel. Id) Range: 0… 479 Step: 1 Default: - Bearer channel identifier. The attribute allows to define the bearer channel ID. NSVC, FRBC 35 © Nokia Siemens Networks RN 20092 EN 14 GLN 0 Note! Range: 0. . 95 for BSC 3 i 660 0. . 399 for BSC 3 i 2000 0. . 479 for BSC 3 i 3000 (6 BCSU/BSC × 5 PCU 2 -E/BSCU × 16 FRLor. NSVC/PCU) 0. . 63 for other BSCs
Counters and alarms PCU 2 HW Evolution and Asymmetrical … • PCU 2 -E requires no new counters nor measurements (apart from FRL measurement), it does not affect functional triggering points either) - only the amount of FRL measurements is extended due to increase in the number of FRL supported • No new alarms are introduced due to PCU 2 -E - only the amount of alarms (since the alarm count parameter is generally scaled according to the number of object instances raising the alarm) is to be extended (e. g. EGPRS DYNAMIC ABIS POOL FAILURE from 16 to 60 objects) • New alarms related to ‘Asymmetrical PCU configuration’ - primary_spare_bcsu_missing_a: PCU configuration of BSC is asymmetrical and primary spare BCSU unit definition is missing - primary_spare_bcsu_invalid_a: Primary spare BCSU unit PCU configuration is invalid. Primary spare BCSU unit can not replace all BCSUs 36 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Thank you for your attention! 37 © Nokia Siemens Networks RN 20092 EN 14 GLN 0
Скачать презентацию RG 10 BSS for Network Planners Customer training material
f13d1d8a15984b14074c5513f1afca59.ppt