NSN SGSN

STANDARD OPERATION And MAINTENACE PROCEDURE

NSN SGSN

PT. Nokia Siemens Networks Menara Mulia 27th Floor JL. Gatot Subroto Kav. 9-11 Jakarta

NSN SGSN

IuPS Integration
Creating Iu over ATM interface in SGSN
These instructions show the creation of the Iu over ATM interface. UBR unspecified bit rate, bit rate that does not specify traffic-related service guarantees CBR constant bit rate, bit rate that supports transport services that require rigorous timing control and performance parameters VCI virtual channel identifier, identifier which identifies a particular virtual channel link for a given virtual path connection VPI virtual path identifier, identifier which identifies a group of virtual channel links, at a given reference point, that share the same virtual path connection Before you start These instructions assume that:
. .

the point code for the SGSN has been created the IOCP-EA plug-in unit is in use.

ATM RAN
IOCP-EA

VPI: 3 VCI 51 VPI: 3 VCI 52 RNC Iu over ATM Control Plane VPI:0 VCI:60 Service Category:CBR Iu over ATM User Plane VPI: 0 VCI:61 Service Category UBR/CBR

3.2.1 Check the configuration of the ATM PAPU

The SGSN cannot perform switchover for ATM connections. This means that those units which have the ATM interface (ATM-PAPUs) cannot be N+1 replaceable redundant, but must be SN+ load sharing redundant instead. The ATM PAPU redundancy is achieved by connecting each RNC to a minimum of two PAPUs which belong to the same PAPU group. For more information, see Section Grouping ATM PAPUs.

Steps
1. Make sure PAPU is configured correctly (USI) ZUSI:PAPU; In the following example, PAPU-4 and PAPU-5 are configured for

NSN SGSN

ATM. Example
WORKING STATE OF UNITS UNIT PHYS STATE LOCATION INFO PAPU-0 0020 WO-EX PAPU-1 0021 WO-EX PAPU-2 0022 WO-EX PAPU-3 0023 SP-EX IDLE PAPU-4 0024 WO-EX GRNP PAPU-5 0025 WO-EX GRNP TOTAL OF 6 UNITS GROUP OF N+ COMPLEMENTARY 2 COMMAND EXECUTED

2. If needed, configure the ATM PAPU

Steps
a. Set the PAPU to the SE-NH state (USC) ZUSC:PAPU,2:TE; ZUSC:PAPU,2:SE; b. Set the state of the ATM PAPU to SN+ (UST) ZUST:PAPU,2:S-GRNP; c. Set the PAPU to the Active state (USC) ZUSC:PAPU,2:TE; ZUSC:PAPU,2:WO;

3.2.2 Creating ATM configuration Steps

1. Create Layer 1, SDH/Sonet (KLC) The following example shows how to create layer 1 from PAPU 2, port 0: ZKLC:PAPU,2,0:<SES BIP threshold>:<SD BER threshold>:<SF BER threshold>:DIA=OFF,LINE=OFF,LASER=ON,:<SDH protocol>,SET; The SES BIP treshold, SD BER treshold and SF BER threshold define the fault tolerance level of the physical interface before an alarm is set. The possible alarms are 3403 INCOMING SDHSIGNAL DEGRADED IN ATM INTERFACE and 3404 EXCESSIVE ERRORS IN INCOMING SDH SIGNAL IN ATM INTERFACE. <SDH protocol> SDH or SONET <synchronization source> EXT = No synchronisation SET = SDH exchange terminal is used as a synchronization source.
Further information

NSN SGSN

For more information, see KL - ATM Layer 1 Handling. 2. Create ATM interface (KCC) The following example shows how to create the ATM interface which is tied up to a physical layer trail termination point (phyTTP). In this example, the index of the ATM interface is 1. ZKCC:1:<max VPI bits>:<max VCI bits>:U:1;
Further information

For more information, see KC - ATM layer configuration handling. 3. Create termination points (KCN) This example shows how to create termination points as presented in Figure Iu over ATM, example configuration. Create a virtual path link termination point (VPLtp) and virtual channel link termination point (VCLtp) for both user plane and control plane. The virtual path must be created first. The CDVT parameter identifies the maximum cell delay variation and the PCRparameter defines the peak cell rate.

Steps
a. Create virtual path for control plane (KCN) The used service category for the control plane is constant bit rate. ZKCN:1:VP,<VP Number>:<OAM segment>:C:<CDVT>:<PCR>:U; b. Create virtual path for user plane (KCN) The used service category for the user plane is either a constant bit rate or an unspecified bit rate; in this example unspecified bit rate. ZKCN:1:VP, <VP Number>:<OAM segment>:U:<CDVT>:<PCR>:U; c. Create virtual channel for control plane (KCN) ZKCN:1:VC, <VP Number>,<VC Number>:<OAM segment>:C:<CDVT>:<PCR>:U; d. Create virtual channel for user plane (KCN) ZKCN:1:VC, <VP Number>,<VC Number>:<OAM segment>:U:<CDVT>:<PCR>:U;
Further information

For more information, see KC - ATM layer configuration handling.

3.2.3 Creating user plane for the Iu interface - Iu over ATM

Figure 5. Iu over ATM user plane in SGSN

Steps
1. Create network interface (QRN and Q6N) This example shows how to create a point-to-point connection to the RNC. ZQRN:PAPU,2:IOCPEA,2:AA0,:10.102.152.202,

NSN SGSN

L:30:10.102.152.201:1500; Use the ZQ6N MML command for the IPv6 network. 2. Create loopback address for ATM (QRN and Q6N) Use the loopback address for all ATM traffic. The netmask length must be 32. ZQRN:PAPU,2:IOCPEA,2:LO0:10.102.152.132,L:32:; Use the ZQ6N MML command for the IPv6 network. 3. Create IP over ATM (KCA)
Iu over ATM user plane User data UDP IP ATM (I.361) LLC encp (RFC 1483) AAL5 (I.363) SDH/SONET (STM-1/STS-3c) GTP-U

This example shows how to create IP over ATM for the user plane, when the VPI is 0 and VCI is 61. ZKCA:1,0,61:AA0:<RNC index>:<usage>; The possible values for the usage parameter are IPOAUD, which means IP over ATM user data and IPOART, hich means IP over ATM real time user data. 4. Associate the source IP address for the Iu user plane (KAC) ZKAC:PAPU,0:APP=IUU:ADDRESS="10.102.152.132"; where the IP address is the loopback address of the ATM. 5. Ping the RNC user plane IP addresses to make sure the connection works (QRX) ZQRX:PAPU,0:IOCPEA,2:IP=<IP address>; where the IP address is the GTP-U endpoint IP address which the RNC has allocated to the SGSN.

3.2.4 Creating control plane for the Iu interface - Iu over ATM

Figure 6. Iu over ATM control plane in SGSN

Steps
1. Configure ATM-based signalling link, link set and route set
SAAL-NNI Iu over ATM control plane MTP-3b (Q.2210) NNI SSCF (Q.2140)

NSN SGSN

AAL5 (I.363) ATM (I.361) RANAP SCCP (Q.711-Q.716) SSCOP (Q.2110) SDH/SONET (STM-1/STS-3c) Layer 3 GMM/SM

Steps
a. Create ATM-based signalling link (NCS) ZNCS:<signalling link number>:<external interface number>,<external VPI-VCI>:PAPU,2:0; Example ZNCS:65:1,0-60:PAPU,2:0:; b. Create signalling link set (NSC) ZNSC:<signalling network>,<signalling point code>,<signalling link set name>:<signalling link number>,<signalling link code>; Example ZNSC:NA0,2950,RN655:65,0:; c. Create signalling route set (NRC) ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter setnumber>,<load route priority>; Example ZNRC:NA0,2950,RN655,0,,:,,,0::::; 2. Configure the signalling SCCP subsystem sharing status>,<restrictionstatus>:<signalling transfer point network>,<signalling transfer point code>,< signaling transfer point name>,<signalling

Steps
a. Create remote SCCP signalling point (NFD) ZNFD:<signalling network>,<signalling point code>,<signalling point parameter set set number>:<subsystem number>,<subsystem name>,<subsystemparameter

number>,<subsystem status test>; Example ZNFD:NA0,2950,2:; b. Create SCCP subsystem RANAP to remote signalling point (NFB)

NSN SGSN

ZNFB:<signalling network>,<signalling point codes>:<subsystem number>,<subsystem name>,<sub system parameter set number>,<subsystem status test>; Example ZNFB:NA0,2950:8E,RANAP,0,Y:; c. Create SCCP subsystem RANAP to own signalling point (NFB) ZNFB:<signalling network>,<signalling point codes>:<subsystem number>,<subsystem name>, <subsystem arameter set number>,<subsystemstatus test>; Example ZNFB:NA0,3BE:8E,RANAP,0,Y:; 3. Configure and activate the SS7 signalling components

Steps
a. Allow activation of signalling link (NLA) ZNLA:<signalling link numbers>; Example ZNLA:65:; b. Activate signalling link (NLC) ZNLC:<signalling link number>,<state change>; Example ZNLC:65,ACT:; c. Allow activation of signalling route set (NVA) ZNVA:<signalling Example ZNVA:NA0,2950::; d. Activate signalling route set (NVC) ZNVC:<signalling network>,<signalling point code>:[<signalling transfer point network>], [<signallingtransfer point code>]:<statechange>; Example ZNVC:NA0,2950::ACT:; e. Activate remote SCCP signalling point (NGC) ZNGC:<signalling network>,<signalling point codes>:ACT; Example ZNGC:NA0,2950:ACT; f. Activate SCCP subsystem of remote signalling point network>,<signalling point code>:<signalling transfer point network>,<signalling transfer oint code>;

NSN SGSN

(NHC) ZNHC:<signalling network>,<signalling point codes>:<subsystem>:ACT; Example ZNHC:NA0,2950:8E:ACT:; g. Activate SCCP subsystem of own signalling point (NHC) ZNHC:<signalling network>,<signalling point codes>:<subsystem>:ACT; Example ZNHC:NA0,3BE:8E:ACT:; h. Activate the broadcast status of local SCCP subsystem (OBC) ZOBC:<network Example ZOBC:::Y; i. Activate the broadcast status of remote signalling point (OBM) ZOBM:<network of affected subsystem>,<signalling number>:<network point code of affected signalling subsystem>,<affected Example ZOBM:::Y; subsystem ofconcerned of affected subsystem>,<signalling point code of affected subsystem>,<affected subsystem umber>:<network of local subsystem>,Y;

point>,<concerned signalling point code>:Y;

3.2.5 Creating RNC Steps

1. Create RNC (E6C) The following example shows how to create RNC and simultaneously a RAC and LAC association for the default PLMN identity (MCC and MCN). New associations can be added to any RAC, LAC or PLMN identity later using the E6M MML command. ZE6C:RNCID=100,RNCNAME=RNC1,:TOA=DPC,LAC=1,RACL=8,PAPU=0,:NI=IN0,SPC=99:; Syntax and parameters of the command example: ZE6C:RNCID=<RNC identification>,[MCC=<mobile country code>,MNC=<mobile network code>|own MCC and MNC def],RNCNAME=<RNC name>:[TOA=<type of address>|GT def],LAC=<location area code>,

NSN SGSN

[LAMCC=<mobilecountry code of LA>,LAMNC=<mobile network code of LA>|own MCC and MNC def],RACL=<routing area code list>...,[PSET=<RNC parameter set>|0 def],[PGI=<PAPU groupidentifier><option>|PAPU=<PAPU unit index>]:[TYPE=<type of rnc><option>|RNC def]:(DIG=<RNCglobal code>]); 2. Connect RNC to the correct interface (E6G) ZE6G:ADD:RNCNAME=RNC1:PAPU=0,IPNAME=AA0; 3. Activate RNC (E6S) ZE6S:RNCNAME=RNC1:STATE=U; 4. Verify the RNC creation (E6I) ZE6I:RNCNAME=RNC1:RT=ALL; Example
RNC IN RADIO NETWORK =========================================== RNC IDENTIFICATION: MOBILE COUNTRY CODE............ (MCC)..... : 240 MOBILE NETWORK CODE............ (MNC)..... : 08 RNC IDENTIFICATION............. (RNCID)... : 0100 RNC NAME....................... (RNCNAME). : RNC1 MULTIPLE PLMN IN RNC: PLMN1 (MCC,MNC)........................... : 240, 08 RNC PARAMETERS: RNC ADMINISTRATIVE STATE....... (STATE)... : UNLOCKED RNC OPERATIONAL STATE.......... (OPSTATE). : OUT OF SERVICE RNC PARAMETER SET.............. (PSET).... : 0 RNC PARAMETER SET NAME......... (PNAME)... : DEFAULT PAPU GROUP IDENTIFIER.......... (PGI)..... : PAPU UNIT INDEX................ (PAPU).... : 0 RNC GLOBAL TITLE ADDRESS....... (DIG)..... : NUMBERING PLAN................. (NP)...... : TYPE OF NUMBER................. (TON)..... : NETWORK INDICATOR.............. (NI)...... : IN0 SIGNALLING POINT CODE.......... (SPC)..... : 99 TYPE OF RNC.................... (TYPE).... : RNC

title

address>|[NI=<network

indicator>,SPC=<signalling

point

Creating Iu interface
ROUTING AREA IDENTITY LIST: MCC MNC LAC RAC ==================== 240 08 00001 008 COMMAND EXECUTED

3.2.6 Restarting PAPU after the Iu interface is configured

After you have created the Iu Interface, restart PAPU since the parameters must be updated in the working unit.

Steps

NSN SGSN

1. Restat PAPU (USU) ZUSU:PAPU,0;

3.2.7 Grouping ATM PAPUs

To achieve redundancy for the ATM PAPUs, you need to group PAPUs in the group of at least two PAPUs. For further information, see Section Redundancy in Description of Feature

SG01114: Iu over ATM, Feature Description.

In the following example, PAPU 0 and PAPU 1 are added to group 1 named IuOverATM. Before you start It is assumed all the ATM PAPUs to be grouped are configured as presented in Section Creating Iu over ATM interface in SGSN.

Steps
1. Create PAPU group (FWG) This example shows how to create PAPU group 1. The name of the group is IuOverATM. The group contains PAPUs 0 and 1 and the used PAPU group configuration model in this example is 1. The configuration model affects the distribution of the 2G cells, therefore, if you are using the same PAPU group for the 2G and 3G traffic,select the configuration model according to the 2G traffic. ZFWG:PGI=1,PGN=IUOVERATM:PAPU=0&1:PGM=1;
Refference Nokia Electronic Documentation