Feature Descriptions GSM 16

Nokia Networks

GSM/EDGE BSS, Rel. GSM 16, Operating Documentation, Issue 03, Change Delivery 01 GSM 16 Feature Descriptions and Instructions DN09217923 Issue 01D Approval Date 2016/04/21

GSM 16 Feature Descriptions and Instructions

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © 2016 Nokia Solutions and Networks. All rights reserved.

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for any additional information.

2

DN09217923

Issue: 01D


Table of Contents This document has 170 pages Summary of changes................................................................... 10 1 1.1 1.1.1 1.1.2 1.1.3 1.1.4

RG302531 benefits....................................................................... 11 RG302531 functional description................................................. 11 RG302531 system impact............................................................ 12 RG302531 reference data............................................................ 13

2 2.1

Transmission and transport features............................................ 15 Description of RG602394: TDM fallback for GSM Application.....15

3 3.1 3.1.1 3.1.1.1

Operability features...................................................................... 19 Description of BSS101909: Automat ed Certificate Management.... 19 Testing BSS101909: Automated Cer tificate Management........... 22 License Control of Automated Certifi cate Management...............22

3.1.1.2 3.1.1.3

New Alarm of feature license....................................................... 23 Manual BTS certification operations from BSC command........... 24

3.2

Description of RG302253: L3 data c ollection for GSM PS...........30

3.2.1 3.2.1.1 3.2.1.2 3.2.1.3

Testing RG302253: L3D Collection f or GSM PS..........................32 Starting and stopping PS data monit oring in Megamon...............32 TBF assignment and re-assignment monitoring.......................... 33 TLLI monitoring in Megamon....................................................... 34

3.2.1.4 3.2.1.5 3.3 3.4

TBF releases monitoring in Megamo n ........................................ 35 Assignment reject in Megamon.................................................... 36 Description of RG302362: GSM 16 Release Upgrade License... 37 Description of RG301831: Enhancement of Failure Reasons for the TRX Test................................................................................ 39 Description of RG602488: Single RAN Abis Support...................42 Description of RG302161: Improved Log Collection.................... 47

3.5 3.6 3.6.1 3.7 3.8 3.9

Issue: 01D

Packet switched data features...................................................... 11 RG302531: Multipoint Gb Functional ity Improvement .................11

Testing RG302161: Improved Log Collection...............................49 Description of RG602513: PAoTDM as transport connection for SBTS............................................................................................52 Description of RG302373: Flexi BTS and its Transport Parameter Categorization.............................................................................. 54

3.10

Description of RG602496: Energy efficiency Shut Down Mode with RF Sharing............................................................................56 Description of RG302360: BSC CS counter data for Traffica...... 58

3.11 3.11.1 3.11.2

RG602489: Category for Obsolete Parameters........................... 61 RG602489 benefits...................................................................... 61 RG602489 functional description................................................. 61

3.11.3

RG602489 system impact............................................................ 62

DN09217923

3


3.11.4 3.12 4 4.1

4.2.1 4.2.1.1

BSC and TCSM solution features................................................ 68 Description of RG302150: mcBSC to mcRNC HW reuse implementation procedures..........................................................68 RG302150: implementation procedur es...................................... 77 Description of RG302188: Integrated CS Data support in mcBSC.. 79 Testing RG302188: Integrated CSD s upport in mcBSC...............83 CSD call setup with data rate of 9,6kb ps .................................... 83

4.2.1.2 4.2.1.3 4.2.1.4 4.2.1.5 4.3 4.3.1 4.3.2 4.3.2.1

No calls are dropped when ETMA is moved to BL state..............84 Test CSD call when restarting ETMA with MML ZUSU................86 Intra-cell HO of CSD call.............................................................. 87 Inter-cell HO of CSD call.............................................................. 89 RG301939: Network Resiliency for m cBSC.................................90 RG301939 benefits...................................................................... 91 RG301939 functional description................................................. 91 RG301939 activity mode.............................................................. 96

4.1.1 4.2

4.3.2.2 4.3.2.3 4.3.2.3.1 4.3.2.3.2

RG301939 data synchronization.................................................. 98 RG301939 BSC switchover......................................................... 99 RG301939 prepared BSC switchover ........................................ 100 RG301939 unprepared BSC switchov er.................................... 103

4.3.2.3.3 4.3.2.3.4 4.3.2.4 4.3.2.5

RG301939 prepared BSC switchback ....................................... 104 RG301939 unprepared BSC switchba ck................................... 106 RG301939 BkBSC build managemen t.......................................106 RG301939 BSC pair O&M interface.......................................... 109

4.3.2.6 4.3.3 4.3.4

RG301939 IP mapping and IP conne ctivity test.........................110 RG301939 system impact.......................................................... 110 RG301939 reference data.......................................................... 111

4.3.5 4.3.5.1 4.3.5.2 4.3.6

Activating RG301939.................................................................. 115 Activating RG301939 in the PrBSC............................................ 117 Activating RG301939 in the BkBSC........................................... 119 Deactivating RG301939............................................................. 130

4.3.6.1 4.3.6.2 4.3.7 4.3.7.1

Deactivating RG301939 in the PrBSC....................................... 131 Deactivating RG301939 in the BkBSC.......................................132 Testing RG301939: Network resiliency for mcBSC....................132 Setting of scheduled synchronization.........................................132

4.3.7.2

Unprepared switchover/switchback with non-dual home BCF and

4.3.7.3

dual home BCF (BkBSC in backup mode).................................134 Prepared switchover/switchback with non-dual home BCF and dual home BCF (BkBSC in loaded mode)..................................136

5

BTS solution features.................................................................139

5.1

Description of RG302311: Support for Harmonized Mast Head Amplifier Family..........................................................................139 RG602339: Sync Hub Direct Forward........................................141

5.2

4

RG602489 reference data............................................................ 63 Testing BSS101711: Tracing with BT S Manager......................... 64

DN09217923

Issue: 01D


5.2.1 5.2.2 5.2.2.1 5.2.3 5.2.4 5.2.5 5.2.5.1 5.2.5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.5.1 5.4 5.4.1 5.4.2 5.4.3

Issue: 01D

RG602339 benefits.................................................................... 141 RG602339 functional description............................................... 141 Support of Multi BCF and Common BCCH with Sync Hub Direct Forward...................................................................................... 144 RG602339 system impact..........................................................146 RG602339 reference data..........................................................147 Testing RG602339: Sync Hub Direct Forward........................... 148 Case 1: Sync Hub Master is phase synchronized with GPS and provides accurate phase synchronization and time to slave......149 Case 2: Sync Hub Master is frequency synchronized with ToP and provides internal phase synchronization to slave.......................156 RG302198: BSS Support for FXED (6x60W RFM)....................160 RG302198 benefits.................................................................... 160 RG302198 functional description............................................... 161 RG302198 system impact..........................................................161 RG302198 reference data.......................................................... 162 Testing RG302198: BSS Support for FXED (6x60W RFM)....... 163 Test case: setup 888 configuration to verify FXED functionality...... 163 RG602550: FXEF Flexi RFM 3-pipe 1800 240W.......................165 RG602550 benefits.................................................................... 165 RG602550 functional description............................................... 165 RG602550 system impact.......................................................... 165

5.4.4

RG602550 reference data..........................................................166

5.4.5

Testing RG602550: FXEF Flexi RFM 3-pipe 1800 240W.......... 167

DN09217923

5


List of Figures

6

Figure 1

PDU routing to Multipoint Gb.............................................................. 12

Figure 2

Scenario of PS call re-routing in Multipoin t GB.................................. 12

Figure 3

RG602394 TDM fallback mechanism.................................................16

Figure 4

Feature state is ON observed from BSC MML output ZW7I.............. 23

Figure 5

Feature code 5496 shows activated in fet ched BTS SIR file..............23

Figure 6 Figure 7

Feature code 5496 shows inactivated in fetched BTS SIR file...........24 Alarm ‘7602 BCF NOTIFICATION’ and ‘7 665 BASE STATION TRANSMISSION ALARM’ with new added specific fault reason reported.............................................................................................. 24

Figure 8

Certificate Management in BTS..........................................................25

Figure 9

Command executed successful, MML pri nts out the result of operation with possible additional information....................................................27

Figure 10

After INIT/UP command executed, BTS Certificate files show/refrash in fetched BTS SIR file....................................................................... 28

Figure 11

After REM command executed, Root CA Certificate removed from BTS side in accordance......................................................................28

Figure 12

If BSS101909 feature’s licence state is no t ON, MML command shall be invisible..........................................................................................29

Figure 13

If operation was not successful, failure r eason and text field with additional information are output in MMLcommand execution printout. ............................................................................................................29

Figure 14 Figure 15

RG302253 L3 data collection scheme................................................ 31 RG301831 enchanced failure reason for the TRX test.......................40

Figure 16

RG602488 Single RAN system architecture...................................... 43

Figure 17

Data flow in RG302360...................................................................... 59

Figure 18

RG302150 multicontroller RNC capacity steps.................................. 69

Figure 19

RG302150 multicontroller BSC capacity steps...................................71

Figure 20

RG302150 mcBSC PS extension module necessary changes..........73

Figure 21

RG302150 mcBSC TRX extension module necessary changes........74

Figure 22

RG302150 mcBSC Spare module necessary changes......................75

Figure 23

RG302150 mcBSC main module necessary changes....................... 76

Figure 24

RG301939 N+1 redundancy of network resiliency for mcBSC...........93

Figure 25

RG301939 mcBSC resiliency concept............................................... 94

Figure 26

The activity mode of the BkBSC state transition diagram.................. 97

Figure 27 Figure 28

The activity mode of the PrBSC state transition diagram................... 98 RG302311 harmonized MHA selection............................................ 140

Figure 29

RG602339: Sync Hub Direct Forward chaining................................142

Figure 30

RG602339: Sync Hub Direct Forward RF sharing........................... 143

Figure 31

SHDF configuration with LTE as SyncHub Master........................... 144

Figure 32

Mixed SHDF and FN/FCLK chain.....................................................145

Figure 33

SHDF configuration with GSM as SyncHub Master......................... 146

DN09217923

Issue: 01D


Figure 34

Issue: 01D

Sync Hub Direct Forward output...................................................... 149

Figure 35

Configuring a BTS as Sync Hub Master (with BTS Site Manager)...150

Figure 36

Enabling Sync hub direct forward (master)and 1PPS clock output is holdover...................................................................................... 151

Figure 37

Selecting Priority List........................................................................ 152

Figure 38

Configuring BTS Sync Source and Cable propagation delay...........153

Figure 39

Configuring System module............................................................. 153

Figure 40 Figure 41

Selecting Priority List........................................................................ 154 Clock Control Settings......................................................................154

Figure 42

BCF Properties................................................................................. 155

Figure 43

Alarms raising...................................................................................156

Figure 44

Changing BSC defined as Sync Source...........................................157

Figure 45

Setting IP address of ToP server......................................................158

Figure 46

Clock Control Settings......................................................................159

Figure 47

Alarms raising...................................................................................160

Figure 48

6-pipe FXED front view.....................................................................163

Figure 49

3-pipe FXEF front view..................................................................... 169

DN09217923

7


List of Tables Table 1

8

RG302531 hardware and software requir ements...............................13

Table 2

RG302531 sales information.............................................................. 14

Table 3


Table 4


Table 5

BSS101909 hardware and software requirements.............................19

Table 6 Table 7

BSS101909 new alarms..................................................................... 20 BSS101909 modified alarms.............................................................. 21

Table 8

BSS101909 new MML commands..................................................... 21

Table 9

BSS101909 modified parameters.......................................................21

Table 10

BSS101909 sales information............................................................ 21

Table 11

RG302253 hardware and software requirements...............................30

Table 12


Table 13


Table 14

RG302362 new parameters............................................................... 38

Table 15


Table 16


Table 17


Table 18

RG602488 software and hardware requir ements...............................42

Table 19

RG602488 hardware requirements.................................................... 42

Table 20

RG602488 modified alarms................................................................45

Table 21

RG602488 modified MML commands................................................ 45

Table 22

RG602488 new parameters............................................................... 46

Table 23

RG602488 modified parameters........................................................ 46

Table 24


Table 25


Table 26


Table 27


Table 28


Table 29


Table 30


Table 31


Table 32


Table 33


Table 34

Existing key performance indicators related to RG302360................ 60

Table 35

PRFILE parameters related to RG302360......................................... 60

Table 36


Table 37


Table 38


DN09217923

Issue: 01D


Issue: 01D

Table 39


Table 40


Table 41

RG302188 software and hardware requirements...............................80

Table 42

RG302188 supported CS Data services............................................ 81

Table 43

RG302188 modified counters.............................................................82

Table 44


Table 45

RG301939 terms and definitions........................................................ 91

Table 46

RG301930 Default mcBSC internal VLAN IDs...................................95

Table 47

RG301939 Configuration completeness values and descriptions........................................................................................ 98

Table 48

RG301939 software requirements.................................................... 111

Table 49

RG301939 mcBSC hardware requirements..................................... 112

Table 50

RG301939 hardware configurations................................................. 112

Table 51

RG301939 new alarms..................................................................... 112

Table 52

RG301939 modified alarms.............................................................. 113

Table 53

RG301939 new MML commands..................................................... 113

Table 54

RG301939 modified MML commands.............................................. 114

Table 55

RG301939 new BSC parameters..................................................... 114

Table 56

RG301939 new Flexi Multiradio 10 para meters............................... 115

Table 57

RG602488 sales information............................................................ 115

Table 58

RG302311 hardware and software requirements.............................139

Table 59

RG302311 modified parameters.......................................................141

Table 60


Table 61

RG602339 hardware and software requi rements.............................147

Table 62

RG602339 parameters..................................................................... 148

Table 63


Table 64

RG302198 software and hardware requi rements.............................162

Table 65

RG302198 new alarms..................................................................... 162

Table 66


Table 67

RG602550 hardware and software requirements.............................166

Table 68


DN09217923

9

Summary of changes


Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Changes between issues 01C (2016-03-07, GSM 16) and 01D (2016-04-21, GSM 16) Description of RG302188: n I tegrated CS Data support in mcBSC •

The supported CD Data services table has been updated.

RG301939 activity mode •

Chapter has been updated.

RG602339: Sync Hub Direct Forward •

Feature has been revamped.

Support of Multi BCF and Common BCCH with Sync Hub Direct Forward •

Chapter has been added.

Changes between issues 01B (2016-01-08, GSM 16) and 01C (2016-03-07, GSM 16) RG302531: Multipoint Gb Functionality Improvement •

Feature has been added.

RG301939: Network Resiliency for mcBSC •

Feature has be en added.

RG302198: BSS Support for FXED (6x60W RFM) •


RG602550: FXEF Flexi RFM 3-pipe 1800 240W •


RG602489: Category for Obsolete Parameters •


Changes between issues 01A (2015-11-05, GSM 16) and 01B (2016-01-08, GSM 16) RG602339: Sync Hub Direct Forward • RG602339: Sync Hub Direct Forward has been updated.

10

DN09217923

Issue: 01D


Packet switched data features

1 Packet switched data features 1.1 RG302531: Multipoint Gb Functionality Improvement Benefits, functionality, system impact, reference data of the feature. Introduction The RG302531: Multipoint Gb Functionality Improvementfeature improves BSC functioning, providing a much shorter data outage for PS calls. Re-routing of UL logical link control protocol data units (LLC PDUs) in Multipoint GB configuration is automated, enhancing end-user performance.

1.1.1

RG302531 benefits The RG302531: Multipoint Gb Functionality Improvementfeature provides the following benefits: •

•

•

The lost mobile station (MS) connections are re-established usinga new serving GPRS support node (SGSN). The packet control unit (PCU) is capable of supporting immediate packet data protocol (PDP) context re-establishment. The PCU re-routes UL logical linkcontrol protocol data units (LLCPDUs) to the available SGSN.

1.1.2

RG302531 functional description Prior to BSC16 release in multipoint Gb setup, the re-establishment of a serving GPRS support node (SGSN) link with Nokia Base Station Controllers (BSCs) takes too much time and involves the subscribers turning their mobile phones off and on again to resume a connection. When an active SGSN fails, the mobile station (MS) connections in the failed network service entity identifier (NSEI) are dropped. The Nokia BSC drops logical link control protocol data units (LLC PDUs) of a UE. The Data session resumes after the UE is switched on, or during the next routing area update (RAU). The MSs have to detach, and re-attach their packet switched (PS) connections to start a new packet data protocol (PDP) session over one of the other working NSEIs in the SGSN pool. The RG302531: Multipoint Gb Functionality Improvementfeature enhances the Packet Control Unit (PCU) software. The BSC detects that UE serving SGSN has failed, and selects another available SGSN from a Multipoint Gb to re-route the protocol data units (PDUs). There is need for an MS to detach and re-attach to make a new PDP session over one of the other working SGSNs in the SGSN pool.

Issue: 01D

DN09217923

11



Figure 1

PDU routing to Multipoint Gb SGSN1

MPGB OP:1 NRI-NSEI Map Entries: A/B/C (SGSN1) D/E/F (SGSN2) G/H/I ( SGSN3)

SGSN2

SGSN3

SGSN4 MPGB OP:2 NRI-NSEI Map Entries: R/S/T ( SGSN4) U/V/W (SGSN5) X/Y/Z ( SGSN6)

SGSN5

SGSN6 Figure 2

Scenario of PS call re-routing in Multipoint GB

MS

BSC-PCU

SGSN 1/2/3

UL TBF Establishment

UE LL PDU (ATTACH REQ)

GPRS ATTACH BEGIN to SGSN1, Authentication and Ciphering Procedure; ATTACH COMPLETE

UE LLC PDU (UNITDATA) BSSGP UNITDATA PDU (LLC PDU)

PS DATA Transfer

SGSN1 Link Unavailable UE LLC PDU

NRI_vs_NSEI Mapping found, SGSN1 is DOWN; Select SGSN using NRR (Normal Round Robin) // select SGSN2 or SGSN3

BSSGP UNITDATA PDU (LLC PDU) UE LLC PDU BSSGP UNITDATA PDU (LLC PDU) GPRS DETACH BEGIN followed by DETACH ACCEPT [SGSN2 or SGSN3] GPRS ATTACH BEGIN, Authentication and Ciphering Procedure; ATTACH COMPLETE [SGSN2/SGSN3]

1.1.3

RG302531 system impact RG302531: Multipoint Gb Functionality Improvement impact on features and system performance and capacity. Interdependencies between features

12

DN09217923

Issue: 01D



The BSS20086: Multipoint Gb feature must be activated before activating the RG302531: Multipoint Gb Functionality Improvementfeature. Impact on interfaces The RG302531: Multipoint Gb Functionality Improvementfeature has no impact on interfaces. Impact on network management tools The RG302531: Multipoint Gb Functionality Improvementfeature has no impact on network management tools. Impact on system performance and capacity The RG302531: Multipoint Gb Functionality Improvementfeature impacts system performance and capacity as follows: •

1.1.4

During an active PS call, the UE is able to re-attach without waiting for thenext routing area update (RAU) cycle if the serving SGSN link becomes unavailable.

RG302531 reference data RG302531: Multipoint Gb Functionality Improvement requirements and sales information. Requirements Table 1

RG302531 hardware and software requirements

System Release

Fl exi EDGE

Fl exi Multiradio BTS

Flexi BSC Multiradio 10 BTS

N e tA c t

GSM16

Support not required




BSC16

The RG302531: Multipoint Gb Functionality Improvementfeature requires: • •

Packet Control Unit (PCU-2D) and PCU-2E PIUs support in the Flexi BSC. Packet Control Unit for Multicontroller PCUM onBOC-A and BMPP2-B PIUs support in the mcBSC.

Alarms There are no alarms related to theRG302531: Multipoint Gb Functionality Improvement feature. Commands There are no commands related to theRG302531: Multipoint Gb Functionality Improvement feature. Measurements and counters There are no measurements or counters related to theRG302531: Multipoint Gb Functionality Improvement feature. Key performance indicators There are no key performance indicators related to theRG302531: Multipoint Gb Functionality Improvement feature. Parameters

Issue: 01D

DN09217923

13



There are no parameters related to theRG302531: Multipoint Gb Functionality Improvement feature. Sales information Table 2

RG302531 sales information

Pr od uc t s tr uc t u re c l as s

BasicSoftware(BSW)

14

Li c e n s e c o n tr ol

-

DN09217923

A ct i v ate d by d e f au l t

Yes

Issue: 01D


Transmission and transport features

2 Transmission and transport features 2.1 Description of RG602394: TDM fallback for GSM Application Introduction to the feature This feature provides a transport backup path for an SBTS operating a Packet Abis over an Ethernet. In this case the packet network becomes unavailable it is possible to use an existing time-division multiplexing (TDM) connection and operate the Packet Abis over an ML-PPP. Benefits End-user benefits. This feature does not affect the end-user experience. Operator benefits. This feature enables GSM service continuation in case the packet network is unavailable. Requirements Table 3 System release

GSM 16

g

RG602394 hardware and software requirements Flexi EDGE


Fl exi Multiradio 10 BTS


Flexi Multiradio BTS


BSC


NetAct


Note: This feature requires Flexi Multiradio 10 System Module (FSMF). Functional description The packet network is monitored by single or multiple Bidirectional Forwarding Detection (BFD) sessions. Depending on the use case, single hop or multi hop BFD sessions are applied. These sessions can be individually configured for use inside or outside of an IPSec tunnel. The status changes in the BFD session trigger to: • •

routing entries to transmit the traffic over TDM links. IPSec policies to disable theencryption of GSM traffic (if IPsec is appliedto Packet Abis traffic across the packet network).

The routing decision in downlink is made by the transport network, depending on the BFD status. The BSC receives a routing update via dynamic routing. No traffic with the exception of GSM traffic, is affected. The IP addresses remain unchanged, regardless of whether GSM function is available using packet backhaul during normal operation or using the TDM while fallback is active.

Issue: 01D

DN09217923

15



While fallback is active, the GSM BTS functions and the transport functions (fault monitoring, performance monitoring and selected status information) can be monitored using the GSM BSC O&M connection. The feature assumes that the TDM ML-PPP terminates in a dedicated media conversion router. This ensures that media conversion is not affected in case of an outage of the packet network due to broadcast or Address Resolution Protocol (ARP) storms. When the network recovers after a failure and the BFD sessions are up again, the SBTS delays the reinstallation of the bound static routes and IPsec policies for a configurable time. The changes to the routing table and the IPsec policies and thus the switching between the Packet Abis over IP/Ethernet and Packet Abis over TDM do not require a GSM reset. TDM links can be continuously supervised by an optional PPP echo to monitor the state of the backup path while not carrying GSM traffic.

g

Note: Alternatively, an additional BFD session can be used. This function is however not provided by this feature. Selection of the synchronization source is independent of the switchover and is based on the configured synchronization hierarchy. During TDM fallback the SBTS might select TDM as well as the synchronization source. Figure 3

RG602394 TDM fallback mechanism SecGW 20.20.10.1

Ethernet IF

10.10.10.10

Virtual IF 10.10.20.11WCDMA 10.10.20.12LTE 10.10.20.13GSM 10.10.20.14M-plane

PSec UDP/P Ethernet

10.10.10.1

40.40.30.2

40.40.30.1 AR

Access Network BFDMH1/2

40.40.10.2 Metric10 40.40.10.1

10.10.20.2PPP 10.10.20.1 2GUP/CP/MP IP ML-PPP E1/TDM

PE

Aggregation Network

40.40.20.1

No IPec via TDM for GSM Metric 100 MSR 40.40.20.2

BSC 40.40.20.9

Relationship to other redundancy mechanisms There are networks which support redundant packet network paths to the SBTS with respect to a single BSC and fast IP rerouting or any dynamic routing protocol that is applied. In this case, the customer needs to ensure by proper timer configuration that these mechanisms are used first and the other packet network path is used instead of the TDM. There are networks which support a backup IPsec gateway. In this case the operator needs to ensure that the backup IPsec tunnel is used first and the backup IPsec gateway is used instead of the TDM. In any case it needs to be ensured that the BFD session(s) which are selected as a trigger for TDM fallback are terminated at a location in the network that is common for both packet network paths to the SBTS and both IPsec gateways

16

DN09217923

Issue: 01D



In case BSC redundancy/pooling is applied, the TDM fallback provides only a backup path for the primary BSC. BTS solution details This feature introduces the SBTS capability to logically combine the status of multiple BFD sessions and install or uninstall static routes and IPsec policies based on the outcome: •

•

•

As long as the BFD session or logically combined BFD sessions areup, bound static routes are applied based on the given metric/preference values and longest prefix match rules. As long as the BFD session or all logically combined BFD sessions aredown, bound IPsec policy rules are applied. When the BFD session and all logically combined BFD sessions aredown, the TDM fallback path is used.

The configuration in the SBTS needs to ensure that these BFD session(s) are never carried using the TDM path. The feature builds on the following existing functionalities: •

•

The BFD session(s) can start at any configured virtual, alias, orBTS interface IP address. The GSM application can be bound to any configured virtual, alias, orBTS interface IP address, and can be separated from other applications.

For efficient configuration in case of a network layer backhaul, one virtual IP address is used to exclusively bind the GSM application to the BFD sessions. BSC/BSC site solution details The mcBSC L3 connectivity is applied. That means that routing is enabled on the basic mcBSC modules. In addition to the BSC site routers, a dedicated media conversion router is connected directly to the Ethernet backhaul interfaces of the two mcBSC basic modules. All routers including the mcBSC need to share the same open shortest path first (OSPF) domain. System impact RG602394: TDM fallback for GSM Applicationsystem impact. Interdependencies between features •

•

The BSS101431: L3 Connectivity for Multicontroller BSCfeature is a prerequisite for the RG602394: TDM fallback for GSM Applicationfeature. This feature is bundled together with the SR000650: TDM fallback for GSM Application feature.

Impact on interfaces This feature has no impact on any interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has an impact on system performance and capacity as beneath:

Issue: 01D

DN09217923

17


• • •


System performance and capacity are not degraded. The switchover time must be less than one second starting from the fault detection. The overall GSM radio application performance is limitedby the currently available bandwidth of the transport connections.

Management data Alarms There are no new alarms related to theRG602394: TDM fallback for GSM Application feature. Commands There are no commands related toRG602394: TDM fallback for GSM Application . Measurements and counters There are no measurements or counters related toRG602394: TDM fallback for GSM Application. Key performance indicators There are no KPIs related toRG602394: TDM fallback for GSM Application. Parameters There are no parameters related toRG602394: TDM fallback for GSM Application. Sales information Table 4



BSW

18

-

DN09217923



Yes

Issue: 01D


Operability features

3 Operability features 3.1 Description of BSS101909: Automated Certificate Management Introduction to the feature The BSS101909: Automated Certificate Managementfeature improves certification management of the Public Key Infrastructure (PKI) certificates via the Certificate Management Protocol (CMP). In 2G, certificates are used for IPsec only. The Flexi BTS supports a hierarchical PKI for enrolment and life cycle management of the operator's BTS X.509 certificates. A BTS operator certificate is a mandatory pre-condition for IPSec or TLS transport security provisioning. Benefits The BSS101909: Automated Certificate Managementfeature provides the following benefits: • • • •

BTS licensing using multilayer hierarchycertificates automated certificate enrollment and life cycle management enables the initiation of mass operations using the NetAct CERMA tool one common solution for certificate management in 2G,3G and LTE BTS

Requirements Table 5

BSS101909 hardware and software requirements

System release

F l e xi E D G E


GSM 16


EX16

BTS Flexi B S C Multiradio 10


BSC16

NetAct

NetAct16.2

Functional description The certificate life cycle management between the BTS and the operator PKI is done with the Certificate Management Protocol CMPv2 for initial key assignment and key update according to the CMP profiling specified in 3GPP TS 33.310. With the BSS101909: Automated Certificate Managementfeature BTS is able to verify a certificate along a chain of trust, which comprises of up to 5 certificates, for example: the device certificate, up to 3 sub-ordinated CA certificates, and the self-signed root CA certificate as a trust anchor. The time before the BTS updates a BTS certificate, which is close to expiry, is configurable in the range of 1 to 4999 days with the granularity days and the default 90 days. Configuration is possible via local or remote EM. Feature can be managed by: • • •

Issue: 01D

Certificate Management tool in NetAct (CERMA) BSC using MML commands BTS using 2G Element Manager

DN09217923

19



For more information on IPSec configuration seeSecurity and User Management in mcBSC and mcTC document.

g

When the new BTS certificate is installed, the old BTS certificate is automatically removed, but the root certificate is not deleted. Options to delete the root certificate are provided via CERMA and the Site Element Manager. However, these are intended for old and un-used root certificates. If a trust-chain associated with the root certificate exists on the BTS, these deletion options would lead to the removal of complete trust chain. These options to delete root certificates must be used with caution. If the Root Certificate being removed was used for the existing IPSEC tunnel setup, but new certificates are not installed on the BTS, this will lead to a system outage and only recovery mechanism will initiate a HW Reset from the Site Element Manager. System impact Interdependencies between features The BSS101909: Automated Certificate Managementfeature requires activating the GSM 16 Release Upgrade Licensefeature. Other features that introduce the Certificate Management Protocol (CMP) in 3G and LTE: • • •

RAN1899: Factory and Customer’s PKI RAN2268: Multi-Layer Certificate Authorities LTE665: LTE Certificate Management

•

LTE685:Infrastructures forCertification Authority (CA) and Registration Authority (RA) Impact on interfaces New Abis O&M messages: • •

BTS_CERTIFICATE_ REQ with operation code BTS_CERTIFICATE_ ACK with with status code OK/NOK

Impact on network management tools NetAct CERMA tool enables mass operations on certificates. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms Table 6

BSS101909 new alarms A l arm ID

20

A l ar m n ame

7665

BASE STATION TRANSMISSION ALARM

8316

TRUST CHAIN CERTIFICATE STATUS NOTIFICATION

DN09217923

Issue: 01D


Table 7


BSS101909 modified alarms A l arm ID

A l arm n ame

7602

BCF NOTIFICATION

Commands Table 8

BSS101909 new MML commands Command name

EFF - certificate management

Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 9

BSS101909 modified parameters

F ul l n ame BSC Options

A b b r e v i a t e d n a me bscOptions

M an ag e d o bj e c t

BSC

P are n t s t ru c tu r e

BSC

Sales information Table 10

BSS101909 sales information

So f tw ar et y p e

ASW

L i c e n s e co n tr ol

-

A ct i v at ed b yd e f au l t

No

Activation •

•

The RG302362 GSM16 Release Upgrade Licencefeature must be installed and in 'ON' state in the BSC before changing theBSS101909: Automated Certificate Management feature license to 'ON' state. Make sure that the BSS101909: Automated Certificate Managementfeature license is installed on the BSC.

1. Check that the license covering theBSS101909: Automated Certificate Management feature is installed (W7I). ZW7I:LIC,FULL:LIC=; For more information on licenses, see License Management in BSC. 2. Check that the BSS101909: Automated Certificate Managementfeature is activated (W7I). ZW7I:FEA,FULL:FEA=; Example: ZW7I:FEA,FULL:FEA=5496; 3. Change the state of theBSS101909: Automated Certificate Management feature to 'ON' (W7M). ZW7M:FEA=5496:ON;

Issue: 01D

DN09217923

21



Deactivation 1. Change the state of theBSS101909: Automated Certificate Management feature to 'OFF' (W7M). ZW7M:FEA=5496:OFF;

3.1.1

Testing BSS101909: Automated Certificate Management Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks.

g 3.1.1.1

License Control of Automated Certificate Management Purpose The purpose of this test case is to verify the functionality of the new added feature license, to check if the feature can be successfully installed and activated on BCF, or if relevant alarm can be reported from BCF when the license is not properly used. Test environment • • •

BSC BTS EM

Before you start Preconditions: • • • •

Running BSC16 and BTS16 with Supervisory status License for GSM 16 Release Upgrade Licence is installed in BSC(feature code 5423) License for feature BSS101909 isinstalled but not active in BCF EM is running on a connected laptop

Procedure

1

Set Automated Certificate Management feature state to ON in BSC fo r feature code 5496. ZW7M:FEA=5496:ON;

2

Enable feature via SCF file, perform BTS commissioning

3

Check SiteInfoReport file fetched from EM after site comes up

Expected outcome •

22

Site comes to WO status successfully without anyunexpected alarms

DN09217923

Issue: 01D


• •

3.1.1.2


Feature state is ON observed from BSC MML output ZW7I Feature code 5496 shows activated in fetched BTS SIR file

Figure 4

Feature state is ON observed from BSC MML output ZW7I

Figure 5

Feature code 5496 shows activated in fetched BTS SIR file

New Alarm of feature license Purpose The purpose of this test case is to verify the new added alarm for Automated Certificate license check, and to check if the alarm is successfully triggered when the license is not properly used. Test environment • •

BSC BTS

Before you start Preconditions: •

Issue: 01D

Running BSC16 and BTS16 with Supervisory status

DN09217923

23



•

License for feature BSS101909 isnot installed and not active in BCF

Procedure

1

Enable Automated Certificate Management feature via SCF file or BTS site manager, perform BTS commissioning

2

Check current alarm status on EM or BSC via command ZEOL


•

3.1.1.3

Alarm ‘7665 BASE STATION TRANSMISSION ALARM’ with specific fault reason “Licence for Automated Certificate Management is not available.” reported after BCF restart. Alarm ‘7602 BCF NOTIFICATION’ with new added specific fault reason reported.

Figure 6

Feature code 5496 shows inactivated in fetched BTS SIR file

Figure 7

Alarm ‘7602 BCF NOTIFICATION’ and ‘7665 BASE STATION TRANSMISSION ALARM’ with new added specific fault reason reported

Manual BTS certification operations from BSC command The purpose of this test case is to verify the functionality of the new introduced BSC MML command. Actual ‘Automated certificate management’ with Certificate Management Protocol version 2 (CMPv2) was implemented already in earlier releases for BTS. This feature BSS1010909 in GSM 16 adds functionality for mass operations. Test environment • • • • •

24

BSC O&M BTS EM LDAP server CA server

DN09217923

Issue: 01D


•


DNS server

Before you start Preconditions: • • •

Running BSC and BTS with Supervisory status Feature BSS101909 is activated using licence in BSC and SCF parameters in BTS IPSec with Packet Abis over Ethernet feature is running on BTS

• •

CMP server IPalready address/LDAP server address configured onBTS CMP services configured andIP running onalready CA server

Figure 8

Certificate Management in BTS Initial certificate enrollment and update, CMP

CA

Alarms, update trigger

NetAct

BSC

BTS Revocation list check for remote

CRL

peers, LDAP

Procedure

1

Execute each new added command via BSC MML, reference shows below: Sub-steps

a) ‘Initilialize Operator Certificate’ operation: ZEFF::INIT;

b) ‘Update Operator Certificate’ operation: ZEFF::UPD;

c) ‘Download Revocation List’ operation: ZEFF::DL;

d) ‘Remove Root Certificate’ operation: ZEFF::REM:SN=”076cf7”,ISSUER=”TA_Demo”;

Issue: 01D

DN09217923

25



2

Check executed result from BTS EM


26

Command executed successful, MMLprints out the result of operation with possible additional information.

DN09217923

Issue: 01D


Figure 9

•

Issue: 01D


Command executed successful, MML prints out the result of operation with possible additional information.

Certificate operation is completed successfully for the BCF. After INIT/UP command executed, BTS Certificate files show/refrash in fetched BTS SIR file.

DN09217923

27



Figure 10

After INIT/UP command executed, BTS Certificate files show/refrash in fetched BTS SIR file

After REM command executed, Root CA Certificate removed from BTS side in accordance. Figure 11

• •

28

After REM command executed, Root CA Certificate removed from BTS side in accordance.

If BCF is in SRAN mode, MML execution fails with informative errorcode and message If BSS101909 feature’s licence state isnot ON, MML command shall be invisible.

DN09217923

Issue: 01D


Figure 12

•

If BSS101909 feature’s licence stateis not ON, MML command shall be invisible.

If operation was not successful, failure reason and text field with additional information are output in MML command execution printout. Figure 13

Issue: 01D


If operation was not successful, failure reason and text field with additional information are output in MML command execution printout.

DN09217923

29



•

If BSC O&M does not get answer message in time, MML execution fails with informative error code and message

3.2 Description of RG302253: L3 data collection for GSM PS Introduction to the feature The RG302253: L3 data collection for GSM PSfeature introduces BSC PCU2 and PCUM support for Layer 3 Data (L3D) collection and Packet Switched (PS) data traffic. Benefits The RG302253: L3 data collection for GSM PSfeature provides the following benefits: • • •

improved DX200 message log collection solution continuous tracing ofPacket Switched (PS) data traffic that can help to improve network optimization improved Call LocationAnalysis (CLA) and smart phone usage (packet data connection) data analysis that enables incidents reduction in network performance



System release

F Lexi EDGE



NetAct

GSM 16




NetAct 16.2


The RG302253: L3 data collection for GSM PSfeature requires the following software: • •

L3 Data Collector (Megamon) L3 Data Analyzer (Emil)

Functional description Packet Switched (PS) data resources of GSM are allocated and processed by the PCU in the Flexi BSC and PCUM in mcBSC. TheRG302253: L3 data collection for GSM PS feature introduces BSC PCU2 and PCUM support for Layer 3 Data (L3D) collection and PS data traffic. This functionality is supported by the L3 Data Collector (Megamon) and monitoring analysis is done by the L3 Data Analyzer (Emil) tool. Megamon and Emil can be downloaded from the Nokia Networks Online Services (NOLS) portal. Browse: Care -> Software Supply Tool -> Radio Access Network Tools and choose software to download.

30

DN09217923

Issue: 01D


Figure 14


RG302253 L3 data collection scheme

System impact Interdependencies between features There are no interdependencies between theRG302253: L3 data collection for GSM PS feature and any other feature. Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature introduces L3 Data Collector (Megamon) and L3 Data Analyzer (Emil) tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information

Issue: 01D

DN09217923

31



Table 12


So f tw ar et y p e

ASW

Li c e n s ec o n tr ol

-


No

Activation The RG302253: L3 data collection for GSM PSfeature is activated when the Megamon PC is configured and connects to the PCU. For detailed instructions on the L3 Data Collector (Megamon) seeNokia from L3 Data Megamon Installation Instructions document.configuration It can be downloaded the Collector NOLS / SW Supply Tool (SWD) along with the MegaMon software.

3.2.1

Testing RG302253: L3D Collection for GSM PS

g 3.2.1.1

Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks.

Starting and stopping PS data monitoring in Megamon Purpose The purpose of this test case is to verify PS data monitoring starting and stopping in Megamon. Test environment • • • • •

BSC HW(at least one PCU2-D/PCU2-E), or in case of mcBSC several PCUMs with Gb over IP configured BSC SW (BSC16) Real GPRS network with EGPRS capable BTSs PC installed MegaMonSW with PCU monitoring license, andMegamon version supports PS monitoring MSs are available for PS call

Before you start Preconditions: • • • • •

32

Transmission between the PCUs and Megamon-PC has been implemented. Configure Ethernet IP(VLAN) interfaces forthe PCUs to be monitored. (ZQRA, ZQRN) Set shared key for BSC. (ZQ4A:GIVAXIPSK,S:K:H;) TCP port (GIVAXI_PORT) activation for BSC. (ZWOC:2,2093,FF;) Install L3 Data see Collector(Megamon) onPC. For detailedInstallation instructionsInstructions onMegaMon configuration, Nokia L3 Data Collector Megamon document. It can be downloaded from NOLS/SW Supply Tool (SWD) along with the MegaMon software.

DN09217923

Issue: 01D



Procedure

1

In Megamon select "get units" button.

2

Select the PCUs to be monitored from the list and set all monitoring conditions on (“TBF procedure”).

3

In Megamon start monitoring and generate some PS traffic, such as FTP data transfer on BTSs connected to the PCUs under monitoring. Verify if PCUs are sending monitoring data to Megamon.

4

In Megamon stop the monitoring and generate some PS traffic on the same BTS. Verify if PCUs are no longer sending monitoring data to Megamon.

Expected outcome • • • •

3.2.1.2

Megamon shows all computer units and all PCUs having an IP address created. Monitoring conditions are set correctly. Monitoring is started successfully and it can be verified that PCUs are sending monitoring data to Megamon. Monitoring is stoppedsuccessfully and PCUs are no longer sending monitoring data to Megamon.

TBF assignment and re-assignment monitoring Purpose The purpose of this test case is to verify that TBF assignment and re-assignment related messages are sent correctly to Megamon when TBF procedure monitoring is set on. Test environment • • • • • •

BSC HW(at least one PCU2-D/PCU2-E), or in case of mcBSC several PCUMs with Gb over IP configured BSC SW (BSC16) Real GPRS network with EGPRS capable BTSs PC installed MegaMonSW with PCU monitoring license, andMegamon version supports PS monitoring MSs are available for PS call Nethawk monitoring

Before you start Preconditions: • •

Issue: 01D

Transmission between the PCUs and Megamon-PC has been implemented IP addresses have been defined for the PCUs to be monitored

DN09217923

33



Procedure

1

In Megamon, configure “TBF procedure” as the only monitoring condition and start monitoring. Simultaneously, start Abis Nethawk monitoring.

2

Start downlink data transfer and lock all TSLs except for one during the data transfer. Compare Megamon and Nethawk logs.

3

Start uplink data transfer and lock all TSLs except for one during the data transfer. Compare Megamon and Nethawk logs.

Expected outcome • • •

3.2.1.3

Both monitorings are started successfully. In both logs, downlink assignment andre-assignment related messages canbe found similarly. In both logs, uplink assignment andreconfigure re-assignment messages canbe found similarly.

TLLI monitoring in Megamon Purpose The purpose of this test case is to verify TLLI monitoring during PDP context activation and routing area update. Test environment • • • • • •


Before you start Preconditions:

34

•

Transmission between the PCUs and Megamon-PC has been implemented

•

IP addresses have been defined for the PCUs to be monitored

DN09217923

Issue: 01D



Procedure

1

In Megamon configure the “TBF procedure” as the only monitoring condition and start monitoring . Simultaneously, start Abis Nethawk monitoring.

2

Perform PDP context activation and ping an IP address in the network. Compare Megamon and Nethawk logs.

3

During downlink data transfer, trigger a routing area update. Compare Megamon and Nethawk logs.

Expected outcome • •

•

3.2.1.4

Both monitorings are started successfully. PCU sends BTS id, TRX id, RTSL information, TLLI anduplink TFI to Megamon, when PDP context activation has succeeded. The related messages can be found similarly in Nethawk log. PCU sends both current and old TLLI to Megamon, when TLLI of mobile station changes. The related messages can be found similarly in Nethawk log.

TBF releases monitoring in Megamon Purpose The purpose of this test case is to verify the monitoring of UL and DL TBF releases as well as abnormal TBF releases. Test environment • • • • • •



Issue: 01D


DN09217923

35



Procedure

1

In Megamon configure the “TBF procedure” as the only monitoring condition and start monitoring. Simultaneously start Abis Nethawk monitoring.

2

Start downlink data transfer and wait until the transfer is completed. Compare Megamon and Nethawk logs.

3

Start uplink data transfer and wait until the transfer is completed. Compare Megamon and Nethawk logs.

4

Start downlink FTP data transfer and remove the battery from the mobile during the data transfer. Repeat the same with uplink FTP data transfer. Compare Megamon and Nethawk logs.

Expected outcome • • • • •

3.2.1.5

Both monitorings are started successfully. In both logs, downlink TBF normal release can be found similarly. In both logs, uplink TBF normal release can be found similarly. In both logs, DL and UL TBF abnormal release canbe found similarly. In both logs, DL and UL TBF abnormal release canbe found similarly.

Assignment reject in Megamon Purpose The purpose of this test case is to verify that the Megamon log correctly shows assignment rejects. Test environment • • • • • •

BSC HW(at least one PCU2-D/PCU2-E). Or in case of mcBSC several PCUMs with Gb over IP configured BSC SW (BSC16) Real GPRS network with EGPRS capable BTSs PC installed MegaMonSW with PCU monitoring license, andMegamon version supports PS monitoring MSs are available for PS call Nethawk monitoring


36


DN09217923

Issue: 01D



Procedure

1

Lock all but one GPRS TSL, and set MNDL and MNUL parameters to one so that only one TBF can occupy a TSL at a time.

2

In Megamon, configure the “TBF procedure”as the only monitoring conditionand start monitoring. Simultaneously, start Abis Nethawk monitoring.

3

Try to start uplink data transfer with two mobiles at the same time.

Expected outcome • • •

Configuration changes done successfully. Both monitorings are started successfully. Uplink data transfer is started successfully only forone mobile. In both logs Assignment reject message for the other mobile can be found similarly.

3.3 Description of RG302362: GSM 16 Release Upgrade License Introduction to the feature The RG302362: GSM 16 Release Upgrade Licensefeature introduces the operator to the GSM 16 features and functionality. It is an umbrella license that must be installed and activated before using any of the GSM16 level Basic Software (BSW) or Application software (ASW) features. The license is TRX capacity based and it is required for all unlocked TRXs of the BSC. Benefits The RG302362: GSM16 Release Upgrade Licensefeature provides the following benefits: • •

easier access to the new GSM16 features employment of the most recent corrections provided inthe latest software versions before purchasing the GSM16 release



System release

F l e xi E D G E

B TS F l e x i Multiradio

BTS Flexi B S C Multiradio 10

NetAct

GSM 16





S16_3

Functional description

Issue: 01D

DN09217923

37



When RG302362: GSM16 Release Upgrade Licensefeature is installed and in 'ON' state in the BSC, plus sufficient TRX capacity is available, the Operator can use all of the features that are covered with this one upgrade license. This feature must be installed and activated before using any of the GSM16 features. The individual License Key controlled features still require their own License Keys. System impact Interdependencies between features The RG302362: GSM16 Release Upgrade Licensefeature impacts the following features: • • • •

BSS101909: Automated Certificate Management RG302094: Packet Abis IPSec for GF RG302188: Integrated CS Data support in mcBSC RG602488: SingleRAN Abis Support

Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters Table 14

RG302362 new parameters

F ul l n ame BSC Options

A b b r e v i a t e d n am e bscOptions

M an ag e d o bj e c t

BSC

P ar e n t s t r u c t u r e

-



So f tw ar et y p e

ASW

38


-

DN09217923


No

Issue: 01D



3.4 Description of RG301831: Enhancement of Failure Reasons for the TRX Test Introduction to the feature The RG301831: Enhancement of Failure Reasons for the TRX Testfeature enchances troubleshooting TRX failures from BSC level, while performing TRX Loop Tests.

Issue: 01D

DN09217923

39



Figure 15

RG301831 enchanced failure reason for the TRX test

Benefits The RG301831: Enhancement of Failure Reasons for the TRX Testfeature provides the following benefits: •

40

more information onTRX failuers is avaliable from the BSC level

DN09217923

Issue: 01D



group command can be used from the BSC level

•

Requirements Table 16 System release

RG30 1)

RG301831 hardware and software requirements F l e xi E D G E

EX5


EX5


GF161)

S16

NetAct

NetAct16.2

- supported from GF16 onwards

Functional description The RG301831: Enhancement of Failure Reasons for the TRX Testfeature enchances troubleshooting the TRX failures from BSC level, while performing TRX Loop Tests. Failed TRX test results information is displayed in the BSC in the same way as in the 2G Element Manager. This feature will enchance test execution from the BSC level, providing the same amount of information as is avaliable in the 2G Element Manager. System impact Interdependencies between features There are no interdependencies between theRG301831: Enhancement of Failure Reasons for the TRX Testfeature and any of the other features. Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms There are no alarms related to this feature. Measurements and counters There are no measurements or counters related to this feature. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information

Issue: 01D

DN09217923

41



Table 17


So f tw ar et y p e


ASW

-


No

3.5 Description of RG602488: Single RAN Abis Support Introduction to the feature This document concentrates on BSC support for the Single RAN system. For more information on the Single RAN documentation, see the documents in the Single RAN Operating Documentation set. Benefits The RG602488: Single RAN Abis Supportfeature provides the following benefits: • •

improves the use of network elements in the Single RAN technology. enables managing Single RAN and GSM BTS units by BSC.


RG602488 software and hardware requirements

System release

F l ex i E D G E



GSM 16



SRAN16.2

Table 19

BSC16

NetAct

NetAct16.2

RG602488 hardware requirements BTS hardware requirements

Flexi Multiradio 10 System Module FSMF

Functional description The main difference between the Single RAN (SRAN) system architecture and the Single RAT LTE, WCDMA and GSM BTS system architecture is in the radio network's O&M architecture. While an SRAT base station represents one radio technology, the Single RAN base station (SBTS) can host several radio access technologies simultaneously. SBTS can also be configured for one technology only. Regardless of the radio configuration, SBTS has one common transport and one common M-plane connection for all the radio technologies. In the GSM system, Abis O&M between BSC and SBTS is kept in the SRAN architecture, but the O&M functionalities are restricted. SRAN and SRAT base stations can be connected to the same RNC and BSC. The following picture illustrates the SRAN system architecture in comparison with the SRAT LTE, WCDMA and GSM system architectures.

42

DN09217923

Issue: 01D


Figure 16


RG602488 Single RAN system architecture

The NE3S interface is the main M-plane interface for the SBTS management. The BCF Outputs, External alarms, and BCF SW handling of Single RAN BTS must be performed through the NE3S interface. Abis O&M interface remains for the direct O&M communication between the BSC and the BCF, and it is required for the tightly-coupled recovery services for BCF and BSC. The process of creating Single RAN BTS into BSC is the same process as creating Flexi Multiradio 10 BTS, and requires to use Packet Abis as the Abis transmission. The BSC controller identifies the Single RAN BTS as any other Flexi Multiradio 10 BTS until the Single RAN BTS indicates (using the SBTSID parameter) that it is the Single RAN BTS. After that, BSC: removes mapping of the BCF to IO texts from the database sets all IO texts, and the EAC related parameters to default values

• •

The BSC performs the above steps for the Single RAN BSC into its own database.

g

•

•

• •

•

Issue: 01D

Only GSM specific configuration is delivered throughthe Abis O&M interface by the BSC. BTS SW management, SCF delivery,BCF Outputs and EAC configurations are no longer through the Abis O&M interface by the BSC. Q1 channel protection is not neededin the Single RAN technology. The BSC does not receive all alarms that may be relevant to analyze thestatus of the SBTS. Alarms shall be analyzed in NetAct, because NetAct enables to see the whole status of the alarm(s). In addition to the backup functionality,the Packet Abis over TDM (PAoTDM)can be used also as the only connection type in GSM dedicated (Single RAT) mode.

DN09217923

43



System impact Interdependencies between features The RG302362: GSM16 Release Upgrade Licensefeature is a prerequisite for the RG602488: Single RAN Abis Supportfeature.

g

Note: When the license is missing, the alarm 7730 appears. The RG602488: Single RAN Abis Support feature is impacted by the following features: •

•

w

BSS11052: Dynamic Frequency and Channel Allocation and BSS Synchronisation BSC does not manage nor configure synchronisation for Single RAN BTS. However, if BSS Synchronisation is in use, the clock source's parameter value should be set to BSSTOP at the BSC. This setting enables the DFCA recovery to work smoothly and correctly. RG602394: TDM fallback for GSM Application The RG602394: TDM fallback for GSM Applicationfeature gives backup coverage by using the 2G network over the TDM when primary connection is lost. As a result of losing Ethernet connection to the Single RAN BTS, WCDMA and LTE become unreachable, and GSM traffic continues to secure basic coverage. The BTS supervises Ethernet and TDM paths and takes care switching to the TDM fallback path and back again. The role of the mcBSC role is to only show the alarm from the BTS that informs the operator about fallback. The site router of the mcBSC acts as a media converter. It means that the mcBSC connects to the router over the Ethernet interface and the router connects to Abis over the ML PPP/TDM interface. The RG602394 TDM fallback for GSM Applicationfeature is supported only by the mcBSC.

Impact on interfaces The RG602488: Single RAN Abis Supportfeature impacts interfaces as follows: •

•

•

44

Abis O&M interface The BSC does not send following messages to the Single RAN BTS: –

BTS_CLOCK_REQ

–

BTS_OUTPUT_CONTROL

–

BTS_TRE_POLL_LIST

–

BTS_PABIS_MEAS_REQ with Measurement type = 151 BSS ToP Measurement

The BTS denotes to be a Single RAN BTS by adding an SBTS ID into BTS_OMU_STARTED message. This message contains valid A5 ciphering and GSM release level information. A Single RAN BTS ID must be present if the BTS is configured as a Single RAN BTS. BSC – NMS (NetAct) XML interface NetAct does not allow SCF handling for the Single RAN BTS. Q1 interface The Single RAN BTS does not support the Q1 interface.

DN09217923

Issue: 01D


g


Note: The NE3S interface, directly from NetAct, is used for SBTS BTS SW management, SCF delivery, BCF Outputs and EAC configurations. No need to configure separately for GSM in the BSC. Impact on system performance and capacity This feature does not affect system performance or capacity. Management data Alarms Table 20

RG602488 modified alarms

A l ar m ID

A l ar m n a me

7600

BCF FAULTY

7602

BCF NOTIFICATION

7606

TRX FAULTY

7607

TRX OPERATION

7730

CONFIGURATION OF BCF FAILED

For alarm descriptions, see: • •

Base Station Alarms (7600-7699) BSC Alarms Excel Document

Commands Table 21

RG602488 modified MML commands Command name

ZEEI ZEFO

For command descriptions, see: •

EE - Base Station Controller Parameter Handlingin BSC

•

EF - Base Control Function Handling

Measurements and counters There are no measurements or counters related to theRG602488: Single RAN Abis Support feature. Key performance indicators There are no key performance indicators related to theRG602488: Single RAN Abis Support feature. Parameters

Issue: 01D

DN09217923

45



Table 22

RG602488 new parameters

F u l ln am e

A b b r e v i a t e dn a m e

SBTS ID

Table 23

M a n a g e do b j e c t

BCF

sBTSId

RG602488 modified parameters

F u l ln am e


Clock Source

clockSource


BCF

BSS ToP Phase Sync Timing Limit

bssTopSyncLimit

BCF

Output Definition

outputDefinition

BCF

Text ID Of The Output 1...6

textId

BCF

External Alarm Definition

externalAlarmDefinition

BCF

External Input Number

inputId

BCF

Text ID

inputTextId

BCF

Polarity

polarity

BCF

Severity

severity

BCF

External Outputs

bcfOutputInUse

BCF

External 1PPS Sync

ext1ppsSyncSource

BCF

Uplink Traffic Shaping

uplinkTrafficShaping

BCF

UL Committed Information Rate

ulCommittedInformationRate

BCF

UL Committed Burst Size

ulCommittedBurstSize

BCF

BU1 Abis Throughput Threshold

bu1AbisThroughputThreshold

BCF

BU2 Abis Throughput Threshold

bu2AbisThroughputThreshold

BCF

DL Committed Information Rate

dlCommittedInformationRate

BCF

Packet Loss on DL Abis PL1 Threshold

pl1ThresholdPacketLoss

BCF

Packet Loss on DL Abis PL2 Threshold

pl2ThresholdPacketLoss

BCF

Packet Abis Congestion Control

packetAbisCongestionControl

BCF

Maximum BTS Multiplexing Wait Time

maxBtsMultiplexingWaitTime

BCF

Maximum Multiplexing Packet Size

maximumMultiplexingPacketSize

BCF

Source

46

DN09217923

Issue: 01D


Table 23


RG602488 modified parameters (Cont.)

F u l ln a me



BTS IPv4 Subnet Mask btsIpv4SubnetMasklengthCUplane BCF Length for C/U-plane Packet Delay Variation

packetDelayVariation

BCF

BTS C/U-plane IP

btsCuPlaneIpAddress

BCF

Address

For parameter descriptions, see theBSS Radio Network Parametersdocument. Sales information Table 24


Pr od uc t s tr u ct u re c l as s


BSW

A ct i v at ed b y d e f au l t

-

Yes

3.6 Description of RG302161: Improved Log Collection Introduction to the feature The current log collection mechanism in the BTS Manager is complicated and requires multiple applications to run multiple times. This makes it difficult to manage and timeconsuming in the event of, for example, an investigation concerning a complicated log collection. The RG302161: Improved Log Collectionfeature enhances log collection by streamlining the procedure, reducing the log size and improving the time of solving field problems. Benefits End-user benefits. This feature does not affect the end-user experience. Operator benefits. The RG302161: Improved Log Collectionfeature introduces an enhanced log collection mechanism. This mechanism reduces the fault processing time and improves the testability and serviceability of all the Flexi BTS units and also improves the diagnostics embedded in the BTS SW. In addition, the feature improves the understanding of the field conditions during fault situations. This leads to reduction in the time used for failure root cause analysis. It also decreases the number of faulty units that are re-sent to the field after failed fault detection. Requirements Table 25 System release

GSM 16


EX 5_2.1


GF1_2.1


EX 5_2.1

BSC


NetAct


Functional description

Issue: 01D

DN09217923

47



Currently, the snapshot collection procedure in BTS obtains the following items for the snapshot: 1. 2. 3. 4. 5. 6.

Site Information Report (SIR) UKPT logs Baseband memory Dump HW unit logs Element Manager Logs and EMGCS Logs Alarms

7. Events 8. Test Reports The RG302161: Improved Log Collectionfeature adds the following new logs to the list: 1. SM blackbox File 2. System Stats (contains CPU, Overall Memory, and Process Information) The Element Manager after the introduction of the new logs allows the user to select/deselect the needed logs. This also allows collecting the logs faster over a slower TDM link. The log selection/deselection option concerns the following logs: 1. 2. 3. 4. 5.

Ukpt Logs Baseband Memory Dump HW Unit Logs SM blackbox file System Stats

The following logs are mandatory and included in every snapshot: 1. 2. 3. 4. 5.

Site Information Report (SIR) EM and EMGSCL logs Alarms Events Test Reports

The feature changes the BTS EM Graphical User Interface to provide the check-box based selection of logs. This allows the user to deselect the unnecessary logs, which significantly speeds up log collection, particularly when collecting logs over the remote TDM links. System impact RG302161: Improved Log Collection system impact. Interdependencies between features There are no interdependencies between theRG302161: Improved Log Collection feature and any other feature. Impact on interfaces This feature has no impact on any interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity

48

DN09217923

Issue: 01D



This information is to be provided in a further delivery. Management data Alarms There are no new alarms related to theRG302161: Improved Log Collectionfeature. Measurements and counters There are no measurements or counters related toRG302161: Improved Log Collection. Key performance indicators There are no KPIs related toRG302161: Improved Log Collection. Parameters There are no parameters related toRG302161: Improved Log Collection. Sales information Table 26



BSW

3.6.1

-



Yes

Testing RG302161: Improved Log Collection Purpose

g

Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks. The purpose of this test case is to verify that Improved Log Collection works properly. Test environment •

Windows OS Laptop


Issue: 01D

Install GSM version 16 site manager on Windows OS Laptop BCF is working on GSM 16 load

DN09217923

49



Procedure

50

1

Connect BTS manger remotely/locally on si te

2

Go to File option

3

Choose Save as option

4

There will be a snapshot option to select as below: EM will change the snapshot GUI to allow users to select / deselect logs. By default everything will be checked and selected

DN09217923

Issue: 01D



Expected output HW unit logs are not saved into snapshot's Zip files.

Issue: 01D

DN09217923

51



3.7 Description of RG602513: PAoTDM as transport connection for SBTS Introduction to the feature The Packet Abis of the TDM transport connection can be used with the SBTS when running the SBTS in GSM dedicated mode. In this case the O&M traffic is routed to the SBTS through the mcBSC. Benefits End-user benefits. This feature does not affect the end-user experience. Operator benefits. Possibility to utilize existing transport network in SRAN. Requirements Table 27 System release

GSM 16







BSC

BSC16

NetAct

NetAct16.2

Functional description The Packet Abis of the TDM transport connection can be used with the SBTS when running the SBTS in GSM dedicated mode. In this case the O&M traffic is routed to the SBTS through the mcBSC. The SBTS and the mcBSC site's router will take care of interface load balancing.

52

DN09217923

Issue: 01D



The M-plane traffic is protected with the IPSec on the TDM. Other traffic is not crypted on the Abis interface. • •

•

using the mcBSC as a router towards NetAct the mscBSC allows configuring Abis type"PAoMC" when creating a BCF into an mscBSC (PAoMC refers to Abis with MediaConversion from mcBSC Eth to Abis TDM) flow control for the M-plane traffic is sent over the TDM.

System impact RG602513: PAoTDM as transport connection for SBTSsystem impact. Interdependencies between features •

This feature is bundled together with the SR001027: SBTS PAoTDM for GSM dedicated mode with mcBSC feature.

Impact on interfaces This feature has no impact on any interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms There are no new alarms related to theRG602513: PAoTDM as transport connection for SBTS feature. Commands There are no commands related toRG602513: PAoTDM as transport connection for SBTS. Measurements and counters There are no measurements or counters related toRG602513: PAoTDM as transport connection for SBTS. Key performance indicators There are no KPIs related toRG602513: PAoTDM as transport connection for SBTS . Parameters There are no parameters related toRG602513: PAoTDM as transport connection for SBTS. Sales information Table 28



BSW

Issue: 01D

-

DN09217923



Yes

53



3.8 Description of RG302373: Flexi BTS and its Transport Paramete r Categorization Introduction to the feature This feature introduces the concept of CM (configuration management) parameter categorization. Benefits End-user benefits. This feature does not affect the end-user experience. Operator benefits. Operators can reduce their operating expenses (OPEX) by simplifying of the plan file and limiting the number of basic parameters managed via NetAct CM tools: • • •

simplified network parametrization faster product roll outs and less effort for competence development reduces human effort needed for the daily BTS maintenance tasks


GSM 16


EX16




EX6.0

BSC

BSC16

NetAct

NetAct 8 SP1

Functional description This feature introduces the concept of CM (configuration management) parameter categorization for: • • • • • •

each existing GSM Flexi BTS CM parameter each existing GSM BTS Transport CM parameter each existing WCDMA Flexi BTS CM parameter each existing WCDMA Flexi BTS Transport CM parameter each new SRAN, GSM and WCDMA BTS CM parameter common Flexi BTS Transport CM parameters

Basic parameters category is meant for parameters used during cell deployment that are adjusted to a particular scenario. The advanced parameters category holds the network optimization and fine tuning parameters (including those related to advanced or complex features). NetAct CM Editor and NetAct Plan Editor allows the user to select and use any of the following UI filtering options for CM parameters: • • •

54

all parameters (all parameters are visible) basic parameters (parameters belongingto the basic category arevisible) advances parameters (parameters belongingto advanced category are visible)

DN09217923

Issue: 01D



System impact system impact. RG302373: Flexi BTS and its Transport Parameter Categorization Interdependencies between features •

This feature is connected with the SR000832 Flexi BTS and its Transport Parameter Categorization feature.

Impact on interfaces This feature has no impact on any interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms There are no new alarms related to theRG302373: Flexi BTS and its Transport Parameter Categorizationfeature. Commands There are no commands related toRG302373: Flexi BTS and its Transport Parameter Categorization. Measurements and counters There are no measurements or counters related toRG302373: Flexi BTS and its Transport Parameter Categorization. Key performance indicators There are no KPIs related toRG302373: Flexi BTS and its Transport Parameter Categorization. Parameters There are no parameters related toRG302373: Flexi BTS and its Transport Parameter Categorization. Sales information Table 30



BSW

-



Yes

Activating RG302373 Preconditions: •

• • •

Issue: 01D

The license for the RG301936: Intelligent MCPA TRX shutdownfeature has to be installed. BSS20984: 2G TRX Automatic Power Down feature has to be activated. Flexi Multiradio licencehas to be installed and enabled. BSC release S16.1 or greater.

DN09217923

55



• • •

Flexi Multiradio BTS with EX 5.1 release or greater. Flexi Multiradio 10 with BTS GF1 1.0.0 release or greater. Flexi Compact BTS with GFC1 1.0.0 release or greater.

Procedure: 1. Change the value of2G TRX Automatic Power Downfeature state to ON using the W7M command. ZW7M:FEA=1236:ON;

2. Change the value of Intelligent MCPA TRX shutdownfeature state to ON using the W7M command. ZW7M:FEA=4438:ON;

3. Ensure that the feature state waschanged successfully using the W7I command. ZW7I:FEA,FULL:FEA=4438;

3.9 Description of RG602496: Energy efficiency Shut Down Mode with RF Sharing Introduction to the feature The RG602496: Energy efficiency Shut Down Mode with RF Sharingintroduces a power saving mode for RF sharing configurations by automatically shutting down the resources inside the RF module based on low traffic conditions, time of the day or operator defined profile. Benefits End-user benefits. This feature does not affect the end-user experience. Operator benefits. This feature helps to reduce OPEX due to energy savings provided by a power saving mode for RF sharing configurations. Requirements Table 31 System release

GSM 16







BSC


NetAct


Functional description The RG602496: Energy efficiency Shut Down Mode with RF Sharingfeature releases RAT resources from the RF module during low traffic conditions or when required by the operator-defined profile. The Power Amplifier automatically goes into stand-by mode when both conditions are met: •

Depending on RF sharing configuration, at least twoRAT specific features are activated: –

56

RG301936: Intelligent MCPA TRX Shutdown

DN09217923

Issue: 01D


– – •


RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks

There are no radio resources reserved.

System impact RG602496: Energy efficiency Shut Down Mode with RF Sharingsystem impact. Interdependencies between features •

Depending on RF sharing configuration, at least twoof the following features must be activated before starting up theRG602496: Energy efficiency Shut Down Mode with RF Sharing feature: – – –

•

g

RG301936: Intelligent MCPA TRX Shutdown RAN955: Power Saving Mode for BTS LTE1103: Load based Power Saving for multi-layer networks

This feature is connected with the RAN3247/LTE2507/RG602496: Energy Efficiency Shut Down Mode with RF Sharingfeature. Note: RG602496 works under the terms of RG301936, RAN955, and LTE1103 licenses.

Impact on interfaces This feature has no impact on any interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity This feature has no impact on system performance or capacity. Management data Alarms There are no new alarms related to theRG302373: Flexi BTS and its Transport Parameter Categorizationfeature. Commands There are no commands related toRG302373: Flexi BTS and its Transport Parameter Categorization. Measurements and counters There are no measurements or counters related toRG302373: Flexi BTS and its Transport Parameter Categorization. Key performance indicators There are no KPIs related toRG302373: Flexi BTS and its Transport Parameter Categorization. Parameters There are no parameters related toRG302373: Flexi BTS and its Transport Parameter Categorization.

Issue: 01D

DN09217923

57






ASW


-


Yes

Activating RG302373 Before you start: •

• • • • • •

The license for the RG301936: Intelligent MCPA TRX shutdownfeature has to be installed. The BSS20984: 2G TRX Automatic Power Downfeature has to be activated. The Flexi Multiradio licencehas to be installed and enabled. The BSC release S16.1 or greater. Flexi Multiradio BTS with EX 5.1 release or greater. The Flexi Multiradio 10with BTS GF1 1.0.0 release or greater. The Flexi Compact BTS with GFC1 1.0.0 release or greater.

1. Change value of the 2G TRX Automatic Power Downfeature state to ON using the W7M command. ZW7M:FEA=1236:ON;

2. Change value of the Intelligent MCPA TRX shutdownfeature state to ON using the W7M command. ZW7M:FEA=4438:ON;

3. Ensure that the feature state waschanged successfully using the W7I command. ZW7I:FEA,FULL:FEA=4438;

3.10 Description of RG302360: BSC CS counter data for Traffica Introduction to the feature The RG302360: BSC CS counter data for Trafficafeature enhances the statistical information provided to Traffica via Traffica interface for 2G. L3DC (Layer 3 Data Collector - MegaMon) is able to capture more counters and deliver them to L3DA (Layer 3 Data Analyzer - Emil) for further processing and to be delivered to Traffica. Benefits The RG302360: BSC CS counter data for Trafficafeature provides the following benefits: •

Increased number of counters that can be provided to Traffica

• •

Possibility to calculate KPIs in real time by Traffica Indication of service impacting problems quickly (SDCCH, TCH, Handover failures). Possibility to easily find congested BTSs in the network (e.g. calls blocked due to congestion, admission control). Real time visibility to voice calls, accessibility, retainability and failure reasons at cell level.

• •

Requirements

58

DN09217923

Issue: 01D


Table 33



System release

F l e xi E D G E



NetAct

GSM 16





BSC16

This feature requires the following software: • • •

L3D Collector L3D Analyzer Traffica interface set as active

Functional description BSC SW gathers value changes of selected counters from existing CS measurements. L3DC collects these changes and forwards them to L3DA for further processing. After the processing, L3DA forwards these processed counter changes to Traffica using Traffica interface. Figure 17

Data flow in RG302360

Traffica

Values of pre-selected BSC CS PM counters visible in data collected by L3DC

Traffica specific interface

Flexi BSC

L3D Collector RAID Disks

mcBSC

N.B. Interfaces

Traffica Network Element Server

For more information on the content refer to theTraffica Reference Guide for BSC document. System impact Interdependencies between features There are no interdependencies between theRG302360: BSC CS counter data for Traffica feature and any other feature. Impact on interfaces The RG302360: BSC CS counter data for Trafficafeature has no impact on interfaces. Impact on network management tools

Issue: 01D

DN09217923

59



The RG302360: BSC CS counter data for Trafficafeature has no impact on network management tools. Impact on system performance and capacity The RG302360: BSC CS counter data for Trafficafeaturehas a low impact to BSC performance and capacity. Management data Alarms There are no alarms related to theRG302360: BSC CS counter data for Trafficafeature. Measurements and counters There are no measurements or counters related to theRG302360: BSC CS counter data for Traffica feature. Key performance indicators Table 34

Existing key performance indicators related to RG302360

KIP DI

KnPaIme

blck_8i

TCH call blocking, DR compensated

csf_1

SDCCH access probability, before FCS

hfr_55c

HO failure ratio due to radio interface blocking

sdr_4 dcr_8i

SDCCH drop ratio without timer T3101 expiry TCH drop call ratio, after TCH assignment, without RE

hfr_2b

Total HO failure ratio, area level

hfr_68c

HO drop ratio

Parameters Table 35

PRFILE parameters related to RG302360 P a r a m e t e rI D

P a r a me t e rn a me

002:2341

COUNTER_TRIGG_TRAFFICA



So f tw ar et y p e

BSW


-


No

Activation The RG302360: BSC CS counter data for Trafficafeature is activated by the parameter COUNTER_TRIGG_TRAFFICA. Additionally Traffica interface for 2G needs to be active. For detailed instructions on the L3D Collector and L3D Analyser configuration see Traffica interface for 2Gdocument. It can be downloaded from the NOLS / SW Supply Tool (SWD) along with the L3D Collector software.

60

DN09217923

Issue: 01D



3.11 RG602489: Category for Obsolete Parameters Benefits, functionality, system impact, reference data of the feature. Introduction The RG602489: Category for Obsolete Parametersfeature enhances the current parameter categorization in the NetAct application. The feature introduces a new parameter category Obsolete, and improves the Advanced category by displaying both the basic and advanced parameters.

3.11.1

RG602489 benefits Benefits of the RG602489: Category forObsolete parameters feature. The RG602489: Category for Obsolete parametersfeature provides the following benefits: •

Operating expenses (OPEX)is reduced because of the simplified plan file, and limitation of the number of parameters to be displayed in NetAct configuration management (CM) tools.

•

The categorization of the parameters prevents the occurrence of mistake, which leads to a faster search of the needed parameter.

•

The operators are allowed to modify the categorized obsolete parameters ifthe parameters are still in use and to give feedback before the parameters are completely removed.

3.11.2

RG602489 functional description Functional description of the RG602489: Category for Obsolete parameters feature. The RG602489: Category for Obsolete parametersfeature improves the parameter categorization in NetAct CM Editor and NetAct CM Plan Editor. The feature introduces a new parameter categoryObsolete. This feature makes the NetAct parameter categorization to have four category views: • • • •

All Basic Advanced Obsolete

The child parameters are also supported to be categorized as Basic, Advanced, or Obsolete. The child parameters can be categorized differently from the parent parameter. And if the child parameter is uncategorized, it is displayed in the view corresponding to the category of the parent parameter. Parameter category views The following are the definition of each category view:

Issue: 01D

DN09217923

61



•

g

The All view displays all the parameters.This view displays the Basic, Advanced, Obsolete, and the uncategorized parameters. Note: Uncategorized parameters may be found in network elements that can no longer be modified. This feature targets only the operator configurable RNW and IP parameters. The RNC ATM configuration parameters are not categorized.

•

•

•

There might be some cases where a parameter has been categorized differently than the category expected by the operator. In such cases,All view provides an efficient way for the operator to find such parameters. The Basic view displays the parameters that are essential for RNC or BTS integration and deployment and parameters that are used regularly to manage the network. As a default view, the NetAct Configurator displays the parameters under Basic view. The Advanced view displays both the basic and advanced parameters. Advanced parameters are used in network optimization or for fine-tuning functionalities that are related to complex features. Operators often depend on basic parameters, the reason why basic and advanced parameters are combined. The Obsolete view displays only the obsolete parameters that are intended to be removed in the future release.

These obsolete parameters are still modifiable and visible in the NetAct Configurator display but will soon be removed. The operators can modify the parameters categorized asObsolete. If they assessed that a certain parameter in theObsolete category is still used in their networks, then they can modify the category and justify the reason why they need to keep the parameter to Nokia Networks customer support. Operators can also create their own user-defined view if they are not satisfied with the pre-defined categorization. This leads to an efficient means for parameter configuration administration and ease the possibility of error or mistake by removing parameters that are not frequently used in the NetAct Configurator display. When the obsolete parameter is in the user-defined view, then it is displayed differently than other parameters to alert the operator that the parameter is a candidate for removal.

3.11.3

RG602489 system impact RG602489: Category for Obsolete parameters impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features There are no interdependencies between theRG602489: Category for Obsolete parameters feature and any other feature. The feature is related to the following features: • •

LTE2506: Category for Obsolete Parameters RAN3242: Category for Obsolete Parameters

Impact on interfaces

62

DN09217923

Issue: 01D



The RG602489: Category for Obsolete parametersfeature has no impact on interfaces. Impact on network management tools The RG602489: Category for Obsolete parametersfeature impacts NetAct as follows: • • •

•

A new parameter category view Obsolete is introduced. The default view is changed from All to Basic. NetAct displays differentparameter category values for different parameters in the same structure. NetAct displays the obsoleteparameters that arein the user-defined view ina visually different way that alerts the operator that the parameter is intended to be removed.

Impact on system performance and capacity The RG602489: Category for Obsolete parametersfeature has no impact on system performance or capacity.

3.11.4

RG602489 reference data RG602489: Category for Obsolete parameters requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 37 System release

GSM 16





Flexi Multiradio 10 BTS


BSC


NetAct

NetAct 16

Alarms There are no alarms related to theRG602489: Category for Obsolete parameters feature. BTS faults and reported alarms There are no faults related to theRG602489: Category for Obsolete parametersfeature. Commands There are no commands related to theRG602489: Category for Obsolete parameters feature. Measurements and counters There are no measurements or counters related to theRG602489: Category for Obsolete parameters feature. Key performance indicators There are no key performance indicators related to theRG602489: Category for Obsolete parameters feature. Parameters To check a category of parameter, see the follwoing documents:

Issue: 01D

DN09217923

63



• • •

BSC BSS Radio Network Parameters Flexi Multiradio BTS GSM Parameters Flexi Multiradio 10 BTS GSM Parameters




BasicSoftware(BSW)


-


Yes

3.12 Testing BSS101711: Tracing with BTS Manager Purpose

g

Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks. The purpose of this test case is to verify that Tracing with BTS Manager works properly. The user of the BTS Element Manager shall be able to select the following top level parameters: • • • • • •

RSSI VSWR TRX low Power Alarm MHA Module Temperature DAC and Antenna Boosting

Test environment •

Windows OS Laptop


64

Install GSM version 16 site manager on Windows OS Laptop BCF is working on GSM 16 load

DN09217923

Issue: 01D



Procedure

1

Connect BT S manager remotely/locally on s ite

2

Go to supervision-bts performance

3

The Trace tool will provide the options of selecting individual items for tracing. The display will be presented in textual as well as in graphical format

Expected output By selecting each of the tracing items, there will be a tracing result shown on the screen.

Issue: 01D

DN09217923

65


66


DN09217923

Issue: 01D


Issue: 01D


DN09217923

67

BSC and TCSM solution features


4 BSC and TCSM solution features 4.1 Description of RG302150: mcBSC to mcRNC HW reuse implementation procedures Introduction to the feature The huge growth of traffic expected has brought new chalenges to the radio network elements. To satisfy current and future needs, Nokia has developed a novel, compact and highly scalable Multicontroller Platform which enables operators to provide the needed capacity in an unrivaled footprint. The hardware of both the mcBSC and the mcRNC are based on the Multicontroller HW Platform. This platform enables the sharing of most of the hardware between the mcBSC and the mcRNC. When the network changes and more capacity is required for the mcRNC, then the mcBSC modules can be transformed to mcRNC modules by making minor HW changes in the module and/or by installing the corresponding SW. Benefits The RG302150: mcBSC to mcRNC HW reuse implementation proceduresfeature provides the following benefits: •

•

This feature enablesfast and smooth HW reuse implementation betweenthe mcBSC and the mcRNC. This feature enables touse of a common BCN HW platform in GSM and WCDMA technologies.


GSM 16





Flexi Multiradio 10 BTS


BSC

BSC16

NetAct


Functional description mcRNC introduction

68

DN09217923

Issue: 01D


•


8x BMPP2-B, OcteonII Card

Basic mcRNC configuration with Rel2 HW consists of two mc01B modules. The supported mcRNC Rel2 hardware capacity expansion is to add two mc02B modules to the mc01B basic modules for S3-B2, then add four more of the mc02B modules to S3-B2 for S7- B2. For more information, seeMulticontroller RNC Product Description. mcBSC introduction

70

DN09217923

Issue: 01D


Figure 19


RG302150 multicontroller BSC capacity steps

Step 7

Step 6

Step 5

Step 4

Step 3

Step 2

Step 1

The mcBSC is fully compliant with any core network supporting an IP based GSM access network and it is fully optimized to most modern and efficient IP only transmission solutions. Depending on the capacity needs, one mcBSC consists of two to several modules. Seven reference capacity steps are used in the current mcBSC. They differ in the number of BCN modules used, from two (step 1) to eight (step 7). The mcBSC with Rel2 hardware is built with four module types. Typically, the hardware combination consists of a BCN-B box and BMPP2 add-in cards.

Issue: 01D

DN09217923

71



Each module type of the mcBSC with Rel.2 hardware consists of the below add-in cards: Main module: • • • •

4x BJC-A, Jasper Forest Card 4x BMPP2-B, Octeon II Card HDS30-A, 300GB HDD optional BSAC-A, Synchronization AMC card

Spare module: • 3x BJC-A, Jasper Forest Card • 5x BMPP2-B, Octeon II Card • HDS30-A, 300GB HDD • optional BSAC-A, Synchronization AMC card TRX extension module: •

2x BJC-A, Jasper Forest Card

•

6x BMPP2-B, Octeon II Card

PS extension module: •

8x BMPP2-B, Octeon II Card

The basic standalone mcBSC configuration consists of two modules (mcBSC basic modules). Additional capacity steps are available by steps of one mcBSC TRX extension module to increase TRX and PS data connectivity. Maximum TRX connectivity can be reached with capacity step 4 containing 5 modules, and on top of that, even higher PS data connectivity can be reached with additional mcBSC PS data extension modules. Maximum configuration with BCN-B hardware consists of 8 modules. For more information, seeMulticontroller BSC and Multicontroller TC Product Description. Hardware reuse according to network evolution Implementation of HW reuse becomes relevant, when network and traffic evolves over time. Network evolution is supported by efficient and ready made procedures for smooth HW reuse implementation between the mcBSC and the mcRNC. Hardware modification from the mcBSC module to the mcRNC module

72

DN09217923

Issue: 01D


•

Figure 20

RG302150 mcBSC PS extension module necessary changes

BJC-A

BMPP2-B

Issue: 01D


to be replaced with the BMPP2-B card

PCU

Packet Control Unit

ETP

Exchange Terminal for Packet

no need to replace

DN09217923

73


•

Figure 21


RG302150 mcBSC TRX extension module necessary changes

BJC-A

BMPP2-B

74


no need to replace

DN09217923

PCU

Packet Control Unit

ETP


BCXU

Base Station Controller Signalling Unit

Issue: 01D


•

Issue: 01D

Figure 22


RG302150 mcBSC Spare module necessary changes

BJC-A


PTU

to be replaced with a cover

BMPP2-B

no need to replace

HDD AMC/ SYNC AMC

no need to replace

DN09217923

PCU

Packet Control Unit

ETP


BCXU


MCMU

Marker and Cellular Management Unit

PTU

Packet Timing Unit

HDU

Hard Disk Unit

75


•

Figure 23


RG302150 mcBSC main module necessary changes

BJC-A

PTU

BMPP2-B

HDD AMC/ SYNC AMC


PCU

Packet Control Unit

ETP


to be replaced with a cover

BCXU


MCMU

Marker and Cellular Management Unit

no need to replace

PTU

Packet Timing Unit

HDU

Hard Disk Unit

OMU

Operation and Maintenance Unit

no need to replace

System impact Interdependencies between features This feature is bundled together with theRAN2671: Upgrading of mcBSC to mcRNC feature. Impact on interfaces The feature has no impact on interfaces. Impact on system performance and capacity This feature does not impact on system performance or capacity. Management data

76

DN09217923

Issue: 01D



Alarms There are no alarms related to this feature. Commands There are no commands related to this featurte. Measurements and counters There are no measurements or counters related to theRG302150: mcBSC to mcRNC HW reuse implementation proceduresfeature. Key performance indicators There are no key performance indicators related to theRG302150: mcBSC to mcRNC HW reuse implementation proceduresfeature. Parameters There are no existing parameters reated to this feature. Sales information Table 40



BSW

4.1.1

-



Yes

RG302150: implementation procedures Reuse of mcBSC modules in existing or new mcRNC configuration Purpose 1. mcBSC is running in commercial network operation. 2. Customer sees lower GSM TRX coverage and / or PS data traffic capacity requirements in the mcBSC. 3. Customer scales down mcBSC RNW configuration according lower capacity requirerements. Implementation procedure for removing modules from mcBSC configuration

Issue: 01D

DN09217923

77



Procedure

78

1

mcBSC PS or TRX extension modules are configured to idle module by module.

2

mcBSC functional units in the idle module are separated from active HW configuration.

3

Idle mcBSC modules are shut down and physically removed from existing mcBSC installation.

DN09217923

Issue: 01D


g


Note: Procedures provided by theRG301250 feature apply to removal of mcBSC extension modules and assumes that mcBSC remains functional. If also mcBSC basic modules are reused in mcRNC, whole mcBSC is taken out from service and shut down.

Reuse of mcRNC modules in existing mcBSC configuration Purpose 1. is running in commercial network operation. 2. mcBSC Customer sees need for higher PS data capacity requirements in the mcBSC. 3. HW modules previously used in mcRNC are available to be reused in existing mcBSC configuration. Implementation procedure for preparing mcRNC modules for mcBSC usage Procedure

1

mcRNC module is prepared to be used as a PS d ata capacity extension module in mcBSC.

2

mcRNC definitions are removed, embedded SW is updated according mcBSC requirements.

4.2 Description of RG302188: Integrated CS Data support in mcBSC Introduction to the feature

Issue: 01D

DN09217923

79



The RG302188: Integrated CS Data support in mcBSCfeature introduces integrated CS Data support in mcBSC. Benefits The RG302188: Integrated CS Data support in mcBSCfeature: • •

reduces the IP planning reduces additional HW expenses


RG302188 software and hardware requirements

System release

F l ex i E D G E



NetAct

GSM 16




NetAct16.2

BSC16

CS data call in FSMF does not work in following configuration: •

PAoPSN abis mode with A over IP configuration with Flexi BSCand mcBSC.

CS data call in FSMF works in following configuration: •

Legacy Abis with A over TDM interface.

Functional description This feature specifies CS Data Rate Adaptation function requirements in DX application. The CS Data services are critical for Government regulatory reasons. To support legacy CS Data services, mcBSC requires mcTC controller. To mitigate the problem with maintaining boxes for CS Data application, Nokia introduces the RG302188: Integrated CS Data support in mcBSCfeature. This feature widens the mcBSC's functionality to integrate the CS Data support. Thanks to this solution no additional IP planning and backbone is needed. The RG302188: Integrated CS Data support in mcBSCfeature is implemented by enabling the Rate Adaptation (RA) functionality in ETMA units. It means that the functionality of this feature is primarily implemented in ETMA.

g

Note: 1. The usage of this feature is controlled by a separate license. 2. The CS Data includes several features and only those which are implemented in earlier Nokia BSS releases are valid for AoIP, except: • •

In Call Modification between speech and data HSCSD, multi-slot allocations and 14.4 kbit/s data rate

The following table presents supported CS Data services.

80

DN09217923

Issue: 01D


Table 42


RG302188 supported CS Data services

CS Data non transparent single slot 9.6 kbit/s CS Data transparent single slot 300 bit/s, 600 bit/s, 1.2 kbit/s, 2.4 kbit/s, 4.8 kbit/s, 9.6 kbit/s Automatic Facsimile group 3

Supported mcBSC configurations for AoIP with TC in MGW CS Data AoIP with Rate Adaptation in ETMA and Packet Abis for mcBSC: • •

g

ETMA functional unit with BOC-A plug-in unit ETMA functional unit with BMPP2-B plug-in unit Note: CS Data Rate Adaptation is not supported in configuration where Rate Adaptaion function is in both mcTC and ETMA in the same mcBSC. If the license for this feature is enabled (ON), then mcTC will not be used for Rate Adaptation, even if it is configured.

System impact Interdependencies between features The BSS21341: A over IP feature is a prerequisite for using theRG302188: Integrated CS Data support in mcBSC feature. The RG302188: Integrated CS Data support in mcBSCfeature enables the usage of ETMA for CS Data calls in mcBSC, therefore the A over IP license shall be enabled in mcBSC Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity When RA is implemented in ETMA, theRG302188: Integrated CS Data support in mcBSC feature impacts the capacity effects in ETMA and mcBSC, One CS Data call takes capacity of 6 speech calls from ETMA Octeon. Management data Alarms There are no alarms related to this feature. Measurements and counters

Issue: 01D

DN09217923

81



Table 43

RG302188 modified counters C o u n t e rI D

C o un t erN ame

M e a s u r e m e n t I Da n d N a me

130005

RTP PACKETS RECEIVED TOO LATE

130: AoIP Traffic BSC

130006

RTP PACKETS RECEIVED TOO EARLY


130007

RTP PACKETS RECEIVED


ON TIME

For more information, seeGSM Measurement Counters and KPIs. Key performance indicators There are no key performance indicators related to this feature. Parameters There are no parameters related to this feature. Sales information Table 44


So f tw ar et y p e


ASW

-


No

RG302188 - activation of the feature Before you start The following licenses, in ON state, are required in mcBSC: •

GSM 16 Release Upgrade license

•

A over IP

Activation of the RG302188 feature 1. To activate the RG302188 feature, use the following command: ZW7M:FEA=5454:ON:;

g

Note: •

All WO-EX ETMA functional unitsshall have BOC-A or BMPP2-B plug-in units to use this feature.

•

It is not possible to use CS Data calls using mcTC after activation this feature.

RG302188 - deactivation of the feature There are three possibilities to deactivate this feature: • • •

82

automatic deactivation when the license expires set the feature state to: OFF set the feature state to: CONF

DN09217923

Issue: 01D


4.2.1

Testing RG302188: Integrated CSD support in mcBSC

g 4.2.1.1


Note: This is an example of verification; do not use it for the feature as such in a live network. The configuration and parameter settings described are only examples and they can vary in different networks.

CSD call setup with data rate of 9,6kbps Purpose The purpose of this test case is to verify CSD call setup with transparent data at a rate of 9.6kbps or verify with non-transparent data depending on MS capability. Test environment • • • • •

mcBSC with GSM16 or later SW package supporting RG302188 feature. AoIP interface with ETMA is configured. TC residesin MGW. OMU, MCMU, BCXU, ETME and ETMA units are in working state. Packet Abis interface is configured forthe 2 BTS's which are in WO-EX state. 2 MSs are available and support CSD calls.

Before you start Preconditions • • • •

Issue: 01D

GSM 16 Release Upgrade license feature code(5423) is active on BSC. Integrated CS data support feature code (5454)is in conf state on BSC. An over IP (TC in MGW) feature code(1753) isactive on BSC. CSD AT Commands: refer to CSD AT commands for CSD establishment.

DN09217923

83



Procedure

1

Initiate a CSD call with transparent data at a rate of 9.6kbps, between MS1 and MS2 connected on the COM1 and COM2 ports in Hyper terminal through AT command.

2

Answer the call through AT command ATA.

3

Check the data rate on MO and MT.

4

Start data transfer from MS1 to MS2.

5

Check the ongoing call details through detpcs csd ST commands in ETMA unit.

6

Disconnect the call.


Data call is established successfully.

• •

MS displays CONNECT 9600. Data is transferred successfully. Call details are displayed properly on ETMA. Call is released successfully. No unexpected alarms are present on the BSC/ETMA. No unexpected error logs are present in the ETMA logs.

• • • •

g 4.2.1.2

Note: Log in to each individual computer unit and check if there are no error logs in the outputs of ZGD/ZGSC and ZSLE command.

No calls are dropped when ETMA is moved to BL state Purpose The purpose of this test case is to verify that no calls are dropped when ETMA moves to BL state and subsequently no further calls can be established. Test environment • • •

• •

84

mcBSC with GSM16 or later SW package supporting RG302188 feature. AoIP interface with ETMA is configured. TC residesin MGW. OMU, MCMU, BCXU, ETMEand ETMA units are in working state. If morethan one of the ETMA units are present then put one into WO-EX and the others into BL state. Packet Abis interface is configured forthe 2 BTS's which are in WO-EX state. 2 MSs are available and support CSD calls.

DN09217923

Issue: 01D



Before you start Preconditions GSM 16 Release Upgrade license feature code(5423) is active on BSC. Integrated CS data support feature code (5454)is in conf state on BSC. An over IP (TC in MGW) feature code(1753) isactive on BSC

• • •

Procedure

1


2


3


4


5


6

Move ETMA to BL state.

7

Verify that no calls are dropped.

8

Initiate a CSD call between MS3 and MS4 and it is rejected.

Expected outcome • • • • • •

g

Issue: 01D

Data call is established successfully. MSdisplays CONNECT 9600. Data is transferred successfully. Calldetails are displayed properly on ETMA. All ongoing calls are still running on ETMA. Data call is rejected when ETMA is in BL state. No unexpected alarms are present on the BSC/ETMA. No unexpected error logs are present in the ETMA logs. Note: Log in to each individual computer unit and check if there are no error logs in the outputs of ZGD/ZGSC and ZSLE command.

DN09217923

85


4.2.1.3


Test CSD call when restarting ETMA with MML ZUSU Purpose The purpose of this test case is to verify all calls that are released on ETMA when it is restarted using MML command ZUSU and subsequently new calls which are established successfully after ETMA comes to working state. Test environment • • • • •

mcBSC with GSM16 or later SW package supporting RG302188 feature. AoIP interface with ETMA is configured. TC residesin MGW. OMU, MCMU, BCXU, ETME and ETMA units are in working state. Packet Abis interface isconfigured for 2 BTS which are in WO-EX state. 2 MSs are available and support CSD calls.

Before you start Preconditions • • •

86

GSM 16 Release Upgrade license feature code(5423) is active on BSC. Integrated CS data support feature code (5454)is in conf state on BSC. An over IP (TC in MGW) feature code(1753) isactive on BSC.

DN09217923

Issue: 01D



Procedure

1


2


3


4


5


6

Restart the active ETMA using the MML command ZUSU.

7

Verify that the running call is dropped.

8

Verify that the ETMA comes up to WO-EX state again.

9

Initiate a CSD call between MS3 and MS4.

Expected outcome • • • • • •

g 4.2.1.4

Data call is established successfully. MSdisplays CONNECT 9600. Data is transferred successfully. Calldetails are displayed properly on ETMA. ETMA is restarted successfully andall ongoing calls are dropped. Call is established successfully after ETMA returns to working state. No unexpected alarms are present on the BSC/ETMA. No unexpected error logs are present in the ETMA logs. Note: Log in to each individual computer unit and check if there are no error logs in the outputs of ZGD/ZGSC and ZSLE command.

Intra-cell HO of CSD call Purpose The purpose of this test case is to verify the intra-cell HO of CSD call with transparent data at a rate of 9.6kbps. Test environment •

Issue: 01D

mcBSC with GSM16 or later SW package supporting RG302188 feature.

DN09217923

87



•

AoIP interface with ETMA is configured. TC residesin MGW. OMU, MCMU, BCXU, ETME and ETMA units are in working state. Packet Abis interface isconfigured for 2 BTS which are in WO-EX state.

•

2 MSs are available and support CSD calls.

• •



Procedure

1


2


3


4


5

Check the ongoing call details through detpcs csd ST commands in ETMA unit, verify the BCF info from ST commands:dbcfinfo < bcf_id >.

6

Lock the TRX carrying the call using ZERS (with FHO) command to achieve intra-cell HO.

7

Check the ongoing call details through detpcs csd ST commands in ETMA unit, verify the BCF info from ST commands:dbcfinfo < bcf_id >.

8



88

Data call is established successfully. MS displays CONNECT 9600. Data is transferred successfully. Calldetails are displayed properly on ETMA. Call is successfully handed over to another TRX in the same BTS. No unexpected alarms are present on the BSC/ETMA. No unexpected error logs are present in the ETMA logs.

DN09217923

Issue: 01D


g 4.2.1.5


Note: Log in to each individual computer unit and check if there are no error logs in the outputs of ZGD/ZGSC and ZSLE command.

Inter-cell HO of CSD call Purpose The purpose of this test case is to verify the inter-cell HO of CSD call with transparent data at a rate of 9.6kbps. Test environment

•

mcBSC with GSM16 or later SW package supporting RG302188 feature. AoIP interface with ETMA is configured. TC residesin MGW. OMU, MCMU, BCXU, ETME and ETMA units are in working state. Packet Abis interface isconfigured for 2 BTS which are in WO-EX state.

•

2 MSs are available and support CSD calls.

• • •


Issue: 01D


DN09217923

89



Procedure

1


2


3


4


5


6

Trigger inter-cell handover from BTS1 to BTS2 b y making RF power variations.

7

Verify if the cal l is successfully established on new c ell and verify the new cell configurations using MML command:ZERO.

8



g

Data call is established successfully. MS displays CONNECT 9600. Data is transferred successfully. Calldetails are displayed properly on ETMA. Call is successfully handed over to new BTS. No unexpected alarms are present on the BSC/ETMA. No unexpected error logs are present in the ETMA logs. Note: Log in to each individual computer unit and check if there are no error logs in the outputs of ZGD/ZGSC and ZSLE command.

4.3 RG301939: Network Resiliency for mcBSC Introduction The RG301939: Network Resiliency for mcBSCfeature allows RAN network recovery from fatal HW failure of a single mcBSC. When one physical mcBSC fails, the operator is able to command the earlier configured and synchronized backup physical mcBSC to take over the responsibility of the failed mcBSC.

90

DN09217923

Issue: 01D


4.3.1


RG301939 benefits Benefits of the RG301939: Network Resiliency for mcBSC. The RG301939: Network Resiliency for mcBSCfeature provides the following benefits:

•

shortens the controller's outage timein the radio network enables quick recovery ofthe GSM service after a disastrous failure of aBSC site

• •

enables the semiautomatic and fast BSC switchover to the backup BSC enables to use the minimal amount of additional equipment

•

4.3.2

RG301939 functional description Functional description of the RG302939: Network Resiliency for mcBSC feature. The RG301939: Network Resiliency for mcBSCfeature improves the network availabilty. The network is defined as connectivity between BTS and BSC and the resiliency means the ability to re-establish the network conection using alternate BSC in case the connectivity between BTS and BSC is broken. The following table presents the most important terms and definitions used in the feature description: Table 45

RG301939 terms and definitions Te r m

BSC redundancy pair

D e f i n i ti o n

It is the pair that consists of two BSCs. The BSC redundancy pair is visible as one BSC to the core network, and BSCs of the redundancy pair can be geographically separated. One BSC in the redundancy pair is the protected BSC (PrBSC), and the other is the backup BSC (BkBSC).

Protected BSC (PrBSC)

The BSC with running network services protected by the BkBSC.

Backup BSC (BkBSC)

The BSC configured to back up the BSC services. It does not have its own radio access network under control.

It applies only when the PrBSC is active.

The backup BSC stores data SW builds of all protected BSCs in fallback SW builds (there are two SW builds per PrBSC). It applies only when the BkBSC is inactive. Active BSC

The BSC in the BSC redundancy pair, which runs the BSC service. It means, that the BCFs are controlled by the active BSC, and traffic goes to the active BSC.

Issue: 01D

Inactive BSC

The BSC in the BSC redundancy pair, which does not run the BSC service.

BTS switchover

It means that the BTS changes the BSC connection from the PrBSC to the BkBSC or other way around.

DN09217923

91


Table 45


RG301939 terms and definitions (Cont.) Te r m

D ef i n i ti o n

BTS switchover happens in two possible ways:

Automatic BTS switchover

•

automatic BTS switchover

•

manual BTS switchover

Automatic BTS switchover happens when the connection between BTSs and PrBSC (or BkBSC) is lost. The BTS triggers the configurable timer (switchover_start_timer; default value is set to twenty minutes). By the time the timer will expire the BkBSC should be up and running. If the connection between BTS and BkBSC is successful, BTS will resume all services using the BkBSC.

Manual BTS switchover Manual BTS switchover is triggered 1) by the operator. Once the BTS receives the switchover request, it checks the availability of the BkBSC. If the BkBSC is available and configured, then BTS will disconnect the PrBSC and will try to connect to the BkBSC. Similar steps can be done with the BTSs connected to the BkBSC. The BTS switchover request can be triggered from the BkBSC and the same sequence of steps will happen. The BTS will disconnect from the BkBSC and will try to connect to the PrBSC. BSC switchover

BSC switchover (also called BSC activity mode change) means switch over from the PrBSC to the BkBSC.

g

Note: • •

BSC switchback

BTS SW download is not proceeding during the BSC switchover. The BSC switchover happens when the RG302939: Network Resiliency for mcBSC feature is in use.

The BSC switchback is switch over from the BkBSC to the PrBSC. From SW point of view BSC switchback and BSC switchover are the same.

g

Note: The BSC switchback happens when the RG302939: Network Resiliency for mcBSC feature is in use.

Service status

It is a parameter that indicates ongoing network resiliency operation.

3GPP interfaces

This term refers to the interfaces of the BSC other than O&M interfaces. Example: packet Abis, AoIP, GboIP.

Configuration committing

A command which tells to the system that the user configuration is done and is ready for configuration adaptation and integrity check. For more information, see Activating RG301939 in the BkBSC.

1)

92

Trigger means BSC inactivation command.

DN09217923

Issue: 01D


Table 45


RG301939 terms and definitions (Cont.) Te r m

Dual homed BCF

D e f i n i ti o n

This is a parameter that describes if BCF is allowed of carrying out a BSC switchover to BkBSC. If value of this parameter is enabled, the BTS is rehomed during the BSC switchover. The operator is unable to modify the value of this parameter, but it is received from BTS. For more information, see BSC_BSS_Radio_Network_Parameters.

The RG301939: Network Resiliency for mcBSCfeature enables to define a pair of mcBSCs where one of controller is the BkBSC, and the other is the PrBSC. In case of a failure of the PrBSC or because of maintenance, the BkBSC takes over the RAN and interfaces, and runs the PrBSC’s services. The operator is able to switch over the traffic from PrBSC to BkBSC via MML commands. During PrBSC inactivation and BkBSC activation, Packet Abis connections of dual homed BTSs switch over from the PrBSC to the BkBSC. After resolution a switchback from the BkBSC to the PrBSC can be done. During switchback dual homed BTSs switch back from BkBSC to PrBSC. A switchback from the BkBSC to the PrBSC restores the active SW build from backup media and executes a System Restart in the PrBSC. It is a model example of N+1 redundancy where the BkBSC is the independent backup component (+1). Figure 24

RG301939 N+1 redundancy of network resiliency for mcBSC Backup BSC

CS Core

Backup BSC can serve one primary BSC at a time

AoIP and Gb IP connectivity to both primary and backup BSC

PS Core

BSC1

EDGE

BSC2

EDGE

BSC3

EDGE

BSC4

EDGE

BSC Cluster O&M interface Packet Abis

Issue: 01D

DN09217923

93



Configurations of all PrBSCs are synchronized to the BkBSC. It means that all configuration data (/LFILES directory) is copied (in data SW Build) to the BkBSC. Also, the /ASWDIR directory is copied. The following figure shows, in general, the resiliency idea and introduces an example network concept. Figure 25

RG301939 mcBSC resiliency concept 1.

Backup BSC

NetAct 4.

Packet Abis

EDGE

AoIP 2.

AoIP

5. Gb/IP

CS Core

3. Packet Abis

Gb/IP

BSC out of service

PS Core

Numbers presented in the figure above are explainedbelow: 1. After the BSC switchover, the BkBSC restarts with the configuration of the failed PrBSC. 2. The BSC pair O&M interface enables to copy the configuration from the PrBSC to the BkBSC periodically or manually. 3. The BTSs switched over tothe backup BSC after Abis connection lost. Cells have the same common gateway interface (CGI) and other parameters in the backup BSC. 4. The NetAct has updated information for the operator. 5. AoIP and Gb/IP connectivity to both BSCs.

g

Note: • • • • • •

•

94

The BkBSC can be the backup BSC for 16 PrBSCs in maximum, but it serves only 1 PrBSC at a time. In normal situation, BkBSC doesnot carry any traffic. File Based Plan Provisioning operationsare not allowed in BkBSC. The PrBSC and the BkBSC can be in the same physical site or in different sites. When there is an active BSC service in the BkBSC, it does not synchronize data with other PrBSCs. The BSC redundancy pairis visible as one BSCin the core network andruns BSC services. From the NetAct point of view, the PrBSC and the BkBSC are two separate BSCs. It is not recommended to modify the RNW configuration in the BkBSC.

DN09217923

Issue: 01D



Only one of the following tasks can be ongoing simultaneously in the BkBSC when activating or deactivating the RG301939: Network Resiliency for mcBSCfeature: • • • • •

PBSC creation PBSC deletion BSC switchover data synchronization BPS fallback

RG301939 Internal VLAN requirements All PrBSCs and BkBSC(s) should have the same internal VLAN IDs without network element prefix. VLAN IDs recommended in theBSC Site IP Connectivity Guidelines document should be used. The following table presents default mcBSC internal VLAN IDs. Table 46

RG301930 Default mcBSC internal VLAN IDs

V L A NN a m e

EMB-0

V L A NI D

5

Un its

MCMU

P ur p o se

Ethernet Message Bus 0.

BCXU OMU EMB-1

6

MCMU

Ethernet Message Bus 1.

BCXU OMU O&M

10

Signalling

20

OMU BCXU MCMU ETMA ETME

Operations&Maintenancetraffic in OMU. DHCP and software downloading for Octeon cards. Control and Management of PCUM and ETME/A cards. PCUM Diagnostic.

PCUM EEP

23

ETMA ETME

PEP

24

PCUM ETME

SIGTRAN-1

32

BCXU MCMU

SIGTRAN-2

33

BCXU MCMU

CS traffic between ETME and ETMA cards.

PS traffic between ETME and PCUM cards.

SS7 over IP (SIGTRAN) traffic for A, BBI, Lb and VNP interfaces.

SS7 over IP (SIGTRAN) traffic for A, BBI, Lb and VNP interfaces. Needed when Multihoming used.

Issue: 01D

DN09217923

95


Table 46


RG301930 Default mcBSC internal VLAN IDs (Cont.)

V L A NN a m e

V L A NI D

Un its

P ur p o se

OMUSIG

44

BCXU

O&MtrafficofBTS.

BCXU

ControltrafficofTRXsinBTS.

TRXSIG

45

AoIP

46

PAbis

48

ETME

UserplaneonPacketAbis interface.

GbIP

49

PCUM

GbandInterPCULAN.

MC-MGMT

800

ETMA

LMP

CS user plane on AoIP interface.

O&M of Multicontroller platform.

OMU MCMU PTUM Cluster O&M

4.3.2.1

11

OMU

Additional IP subnet for mcBSC pair O&M traffic.

RG301939 activity mode The activity mode parameter refers to two new objects implemented by this feature: • •

PBSC object, BBSC object.

The activity mode of the PBSC object The activity mode parameter of PBSC object in BkBSC indicates if BkBSC is actively serving network or if it is in backup mode. Available states are presented in the following table: St at e

D e s cr i p t i o n

Active

BSC service of PBSC is active and operational in BkBSC.

Backup

When activity mode of PBSC in the BkBSC is Backup, data is being synchronized. BkBSC is restarted to operate with base data SW build - no BSC service has been selected for operation. Base data SW build includes a RNW configuration database where only BSC and PBSC objects are created

Loaded

Data of BSC service is pre-configured in BkBSC but BSC switchover has not been requested - BkBSC is inactivated. IP addresses of IP mapping table and SS7 configurations are updated for configuration commit, done

Wait For Sync

BSC service is created in the BkBSC but data is not synchronized (synchronization data is missing).

in Loaded state.

BSC updates activity mode parameter of PBSC to value Backup after completed first data synchronisation

Following figure and table present posible transitions and transition descriptions.

96

DN09217923

Issue: 01D


Figure 26


The activity mode of the BkBSC state transition diagram

loaded Unload Activate

Load Activate Inactivate

active

backup

Data Synced Sync waitForSync

Tr an s i t i o n Backup → Loaded

Descr ip ti on Loaded happens Transition from Backup to when operator loads selected PBSC for preconfiguration and configuration commit.

Backup → Active

Direct transition from Backup to Active happens when operator initiates the resiliency switchover When operator initiates the redundancy switchover.

Loaded → Active Loaded → Backup

When operator unloads selected PBSC from pre-configuration and returns to backup operation

Active → Backup

When operator initiates the redundancy switchback operation. Dual homed BTSs are moved back to PrBSC.

Wait For Sync → Backup

When first data synchronisation is completed.

The activity mode of the BBSC object The activity mode parameter of BBSC object in PrBSC indicates if PrBSC is actively serving network or if it is inactivated. Available states are presented in the following table: S tat e

Descri p ti o n

Active

BSC service is active in the PrBSC.

Loaded

Data of BSC service is preconfigured in PrBSC but 3GPP interfaces are inactivated (PrBSC is inactivated).

Following figure and table present posible transitions and transition descriptions.

Issue: 01D

DN09217923

97


Figure 27


The activity mode of the PrBSC state transition diagram Inactivate

active

loaded Activate

Tr a n s i t i o n

Descr ip ti on

Active → Loaded

4.3.2.2

BSC service in PrBSC is active – PrBSC is operational.

RG301939 data synchronization Data synchronization takes place before BSC switchover and it is used when creating the backup SW build in the BkBSC. Data and configuration of PrBSC are collected, transferred and adapted to the BkBSC. Data synchronization is executed when the PrBSC and the BkBSC are on the same SW levels. It is possible to trigger data synchronization by MML command or by a schedule which is defined by operator. When the PrBSC and the BkBSC are on different SW levels, BSC switchover is allowable, and the BkBSC uses the latest synchronized data SW build. The latest synchronized data SW build is compatible with the SW version of the the BkBSC. The Configuration completeness parameter indicates if configuration is ready to be activated. During data synchronization and configuration commit operations system checks if IP addresses are correctly mapped and if configuration is ready for activation. Based on that, the value ofConfiguration completeness parameter is updated. Table 47

RG301939 Configuration completeness values and descriptions

Configuration completeness value

Description

Fully completed

Value Fully completed means that the configuration committing didn’t find any unmapped or invalid IP mappings and the adaptation was done successfully.

Partially completed

Value Partially completed means that configuration committing found some unmapped and/or invalid IP mappings, the adaptation was done successfully with the existing IP mapping for the configuration files. It is needed to verify the impact of unmapped or invalid configuration entries.

g Not completed

Note: This status is needed before attempting any state changes of the BSC.

Value Not completed means that configuration committing or adaptation has not been executed or it has failed due to error or missing IP mapping. The recover scenario looks like below:

1. Check IP mappings and reconfigure.

98

DN09217923

Issue: 01D


Table 47


RG301939 Configuration completeness values and descriptions (Cont.)

Configuration completeness value

Description

To check IP mappings, use theD6P - PRINT IP MAPPINGS

Feature Descriptions GSM 16

Recommend Documents