MOP For BSC Addition (GB over IP)

TABLE OF CONTENTS

1. BSC Creation Description

1.1 Overview
1.2 BSC Creation Scenario
1.2.1 Signaling Networking
1.3 General Office Creation
1.3.1 Checking Alarm and Notification
1.3.2 Preparing People
1.3.3 Checking BSC Status

2. BSC Creation Procedure

2.1 Configuration Data
2.2 Service Test
2.3 Charging Verification

3.After Creation Observation

3.1 Observation Principle
3.2 Alarm and Notification
3.3 Performance Statistics
3.4 Failure Observation

1 BSC Creation Description

1.1 Overview
With growing network building demands, Addition of wireless access NEs in various scenarios is
required. Common scenarios include:

 BSC (or the Gb interface) Integrate

 RNC (or the Iu interface) Integrate

1.2 BSC Creation Scenarios

1.2.1 Signaling Networking

Figure 1-1 Gb Interface Signaling Interconnection

IPGB

IPGB
RPU

RPU
IT Network
(one or more
iBSC switch/router) SGSN

Lan cable Internal circuit

1.3 General Creation Procedure

No. Step Sub-step
1 Create BSC LAC Add the data of Location area configuration
2 Create the BSC RAC Add the data of Routing area configuration
3 Create the NSE Create Network service Entity
4 Create Local End point Add the IP of Local End.
Create Remote End Add the IP of remote End. (For Static
5
point Configuration)
Configuration for IP NSVC (For Static
6 Create IP NSVC
Configuration)
7 SYN Save the Changes Done
8 Check IP NSVC state Checking Status of Respective NSVC.

1.3.1 Checking Alarms and Notifications

Purpose

To verify that there is no abnormal alarm on the SGSN.

Operations

Operation path: Fault management > Current Alarm Real-time Monitoring

 Criteria

There is no abnormal cutover-related alarm on each NE.

1.3.2 Preparing People

The customer and ZTE’s test personnel are ready.

1.3.3 Checking BSC Status

Purpose

To verify that the target SGSN is reachable from BSC. All IP LINK is normal

2 BSC Creation Procedure

2.1 Configuration data

ADD LAI

Example Format : ADD LAI:NAME="BSC",MCC="404",MNC="59",LAC="0E8A";

Add RAI

Example Format: ADD RAI:NAME="BSC",LAI="BSC",RAC="3E";

Add NSE

Format:
ADD NSE :NSEI=2101,BEARMODE="IP",NSVCMODE="Static",VPNID=20,T10TIMER=6,NAME="BSC";

Add Remote End Point

Format:
ADD REMOTE ENDPOINT:NSEI=2101,IPADDR=10.69.XXX.XXX,PORT=32768,SIGWEIGHT=10,
DATAWEIGHT=10,ENDPOINTID=9;

Add IP NSVC

Example Format: ADD IP NSVC:NSEI=2101,LIPPORTID=1,RIPPORTID=9;

NOTE: For LOCAL ENDPOINT ID , use SHOW LOCAL ENDPOINT command.

To Save the Changes Done:

After the Completion of all Configuration Part the Data have to be saved for that use below
Command:

SYN;

Checking BSC Status:

SHOW IPNSVC INFO:NSEI:2101,NSVCMODE=”STATIC”;

2.2 Service Tests

The Node B cutover will affect all the services of all the subscribers under the related Node B.
Therefore, you must perform comprehensive service tests that cover all the services
commissioned in the existing network.

2.3 Charging Verifications

After completing the all-service tests, perform charging verifications according to the test form.
Verify that all the test records have their corresponding charging records and the charging is
normal.

3 After-Creation Observation

3.1 Observation Principles

 In Performance Statistics, observe basic traffic and office traffic, compare the traffic
data with that collected before the operation, evaluate the overall system operation
condition, and verify that all the offices are still normal after the cutover.

 In Performance Statistics, observe resource usage, compare it with the usage before
the operation, and evaluate whether the operation has any impact during busy hours.

 In Performance Statistics, analyze the performance of each module, compare it with

the performance before the cutover, and verify that each module is affected by the
cutover only in a reasonable way.
  In Performance Statistics, analyze the statistical data that may be affected by the
operation, and compare it with the data before the cutover.

 In Performance Statistics, observe the information about the SGSN.

 Analyze the alarms and notifications after the operation; compare them with the
alarms and notifications produced before the cutover. Pay attention to abnormal
alarms and notifications, analyze the reasons, and handle them immediately.

 Observe the operational status of each board, and check whether it is abnormal. If a
board is abnormal, replace it to eliminate the potential risks.

 If the cutover operation involves charging changes or affects CDR generation, ask the
charging side for assistance before performing the operation. After the operation,
check immediately whether CDR generation and sorting is still normal.

 If the cutover operation involves the superior network management system’s data
gathering or reporting, ask the superior network management side for assistance
before performing the operation. After the operation, ask the superior network
management side to verify that it is still normal.

 After the operation, analyze the signaling traced in the service tests and failure
observation information, and handle abnormal cases immediately.

3.2 Alarms and Notifications

In Alarm Management, check current and real-time notifications. Ensure that there is no new
abnormal alarm or notification.

Verify that the operational status of each NE is consistent with the status shown in the rack
chart.

3.3 Performance Statistics

In Performance Management, query performance statistics. Pay attention to A/Iu interface
cutover related indexes. Compare the statistics with those indexes collected in the same period
before the cutover, and see whether they are basically the same.

3.4 Failure Observation

Check failure observation information of the SGSN and verify that there are no new abnormal
failures and lots of failures.