Integration Activity
CONTENTS
Mod 1- Integration Activity Basic review of Telecom Architecture Integration activity Briefing about Signaling link, Signaling link set, Route set, Trunk Group (CGR), GT Analysis,
SCCP, Tree Analysis Mod 2- MGW Integration
Integration of MGW with MSS Sigtran link configuration Integration with BSC
Mod 3- MSS Integration Sigtran link creation in MSS Signaling link & CGR creation towards BSC TDM link creation with other NEs.
MOD 4- Configuration for First call in MSS & MGW Data base definition for Voice & Data call Other system data base creation Definition for Location update & SMS
Network Architecture
Integration activity
Integration of MSS with HLR a) Location Update. b) Authentication & Ciphering c) TDM connectivity
Integration of MSS with MSS/MSC a) For Traffic Handling. b) For Handover c) Enhanced Network Coverage in a PLMN. d) TDM and IP connectivity.
Integration of MSS with GMSC/GCS a) For Traffic Handling. b) For POI and Gateways Connectivity c) Efficient Routing. d) TDM and IP connectivity.
Integration of MSS with SMSC a) SMS services. b) TDM connectivity
Integration activity
Integration of MSS with MGW a) Connectivity to BSC’s
b) Connectivity to other POIs.
c) Connectivityto other NE
Integration of MSS with CDS a) Data Call & Fax Call. b) IP connectivity.
Integration of MSS with SRBT/CRBT a) Caller tune service
b) TDM connectivity
Integration of MSS with BSC via MGW a) BTS and BSC handling
b) TDM & IP connectivity.
Signalling Link
Two Signalling nodes represented by their point codes can be connected using Signalling Link.
In European Standard links between nodes are full-duplex 64kbps within an E1 facility.
Signalling Link can be TDM or IP based. ZNCC
ZNCC:36:258-1,64,1,1:CCSU,6:0:;
Signalling link no.
Term id and TSL
Speed in Bit rate
Time slot
MTP 2 req.
Signalling link parameter set no.
Signalling Link
Adding signalling link to Signalling Link Set
ZNSA:NA1,D’191,X3H02:36,0;
signalling point code
signalling link set name
Signalling link no.
signalling link code
Signalling Link Set
In SS7 one or more signaling links can be connected to the same two endpoints that together form a signaling link set
Signaling links are added to link sets to increase the signaling capacity of the link set.
ZNSC ZNSC:NA1,D'191,X3H02:36,0:,:::;
Signalling Link Set
Activation of Signalling link set ZNLA:102:; ------- Activation Allowed
ZNLC:102,ACT:; ------- Changing Activation state
Signalling Route Set
Signalling Route - Chain of signalling link sets and signalling transfer points which can be used as a path by the signalling point when routing a message towards a specific signalling point
Signalling Route Set - Combination of all permitted signalling routes that may be used to pass signalling messages from a signalling point to a specific destination
Each Signalling Route Set are associated with a Signalling Route Set Parameter set that defines its own signalling function.
In general, the predefined parameters are the most suitable ones to be used.
ZNRC
ZNRC:NA1,D‘3022,MSS5,0,D,N:NA1,D'15006,M7GW2,7::::; ZNRC:NA1,D'15006,M7GW2,6,D,N:NA1,D'15006,M7GW2,7::::;
Signalling Route Set
Activation of Signalling Route Set
ZNVA:NA0,D’333:NA0,2810:; ------------- Activation allowed
ZNVC:NA0,D’333:NA0,2810:ACT; ------------- Change Activation status
GT Analysis
GT Analysis - Analysis in which the numbering plan, nature of address, and translation type determine an analysis tree from which the analysis result is derived, based on the digit sequence included in the address or translation type
GT Translation - Analysis of the global title in order to find out the signalling connection control part (SCCP) routing address
ZNAC - Global Title Results
ZNAC:NET=NA1,DPC=D'192,RI=GT,::GTR=4,:;
GT Analysis
ZNBC – Global Title Analysis ZNBC:ITU=4,:NP=7,NAI=4:919732:2;
ZNBC:ITU=4,:NP=1,NAI=4:919839000013:4:;
SCCP
The SCCP layer can use a Signalling Point Code (SPC) as the destination SCCP address even when the functional application and the MAP layer uses a GT
That there must be a route set on the MTP level to all Signalling Points (SP) known by the SCCP.
Applications that use SCCP services are defined as subsystems which are identified by a Subsystem Number (SSN).
SCCP
The subsystems can be SCCP management (SCMG), MSC MAP, VLR MAP, HLR MAP, INAP, OMAP, and possibly some network-specific subsystems, like Base Station System Application Part (BSSAP).
ZNFD ZNFD:NA1,D'192,0:6,MAPH,0,Y:8,MAPM,0,Y::::;
SCCP
Activation of SCCP Signalling point ZNGC:NA1,D'3030:ACT:;
Activation of SCCP Subsystem ZNHC:NA1,D'3030:6:ACT;
ZNHC:NA1,D'3030:7:ACT;
Trunk Group (CGR)
Circuits - Transmission channels permitting bidirectional transmission of signals between two points, to support a single communication.
Circuit Group - Group of circuits that have the same purpose and are traffic-engineered as a unit.
Trunk Group (CGR)
External circuit groups are created to connect circuits between two exchanges.
These circuits are used for carrying speech or data between these network elements. The circuit group identifies the direction and register signalling.
Trunk Group (CGR)
ZRCC - Creating CGR
ZRCC:TYPE=ECCS,NCGR=S22G06,CGR=2001:DIR=BI,NET=NA1,SPC=D'9395,LSI=IU5NI,IFAC=5,UPART=4:METHOD=1,INR=INIK4,TREE=80,NCCP=BASICINPSTNPBX,MGW=M2G2V17:;
Trunk Group (CGR)
ZRCA - Adding circuits to CGR
ZRCA:NCGR=S22G06:TERMID=1287-1&&-15,:CIC=1,CICDIR=0,:UNIT=ISU,:;
Trunk Group (CGR)
ZCRM - Activation of CGR
ZCRM:NCGR=S22G06:WO;
Trunk Group (CGR)
ZCEC – Activation Of Circuits
ZCEC:NAT=NA1,SPC=D'9395,CIC=0&&254,:WO:;
Tree Analysis
Digit analysis - It is the Analysis done in CM for Identifying dialed digits and routing it to respective Destinations.
Analysis tree - A chain of records in an analysis file, used for analysing different types of digits.
1. Circuit group (TOCs and PBX calls)2. General Parameter file PRFILE (in MOCs)3. End-of-Selection analysis (forwarding and roaming
calls)4. MSISDN digit analysis (some roaming calls)5. CM (if the digit analysis is sent back for reanalysis)
ANALYSIS TREE
ANALYSIS RESULT FILE
CHARGING ORIGIN
TYPE OF NUMBER
DIALLING (after preanalysis)
CM
ANALYSIS FILES
ANALYSIS RESULT FILES HLR INQUIRY
GSM-TERMINATING CALL
HANDOVER BETWEEN TWO EXCHANGES
CALL TO DDA
NUMBER MODIFICATION
IN CALL
OUTGOING CALL TO TRUNK CIRCUIT
ANNOUNCEMENT
1. OUTGOING ROUTE
2. SPECIAL ROUTE
To find the destination according to the dialled number
Tree Analysis
Tree Analysis
ZRDE – Creation of Destinations and Sub- destinations (Assumed SPR or routes are already created)
ZRDE:NSDEST=PREPCC:SPR=13,CT=SC,SP=3,MNL=0,:;
ZRDE:NDEST=PREPCC,ALT=0:NSDEST=PREPCC,:NCHA=CHARGE,:;
Tree Analysis
ZRDC – Digit Analysis
ZRDC:DIG=1909,TREE=93,TON=SUB,:NDEST=PREPCC,:;
Tree Analysis
`
2
50
48
30
20
70
Digit Analysis
MOC
Service number
Announcement number
Call forwarding
TOC / Inter MSC
MSRN (from HLRENQ)
/ HON (from HO_REQ)
Tree analysis
List of commonly used trees
Call Case Number Tree TON Source
MOC B-number - national 2 NAT PRFILE
B-number - International 2 INT
B-number - Local 2 SUB
Call forwarding C-Nbr. – national 20 NAT EOS-analysis, cause code
C-Nbr.-International 20 INT 100E (CFU) and 100F (conditional CFW)
Service call Service Numbers 30 NAT area serv. numb.handling
Announcement Announcement number 48 UNK PRFILE
Automatic callredirection
Automatic call redirection number 49 NAT PRFILE
Roaming MSRN-National/Handover nbr. 50 NAT EOS, cause code 1009
MSRN-International 50 INT
TOC TOC-number - National 70 >> NAT circuit group (can be
TOC-number –International 70 >> INT changed easily)
MGW Integration
Configuring IP connectivity for MSC Server SIGTRAN H.248 (or MEGACO) Configuring TDM resources for integrated
MSS
Configuring IP connectivity for MSC Server Configuring IP version 4 interface ZQRN:ISU,1::EL0:10.48.32.40,L,:1500:UP:;
Create default static route ZQKC:ISU,1:10.48.32.128,25:10.48.73.65:LOG;
Configuring IP connectivity for MSC Server
Configuring SCTP multihoming ZOYN:ISU,1:IPV4:"10.48.68.100","10.48.76.100";
Configuring IP connectivity for MSC Server
SIGTRAN
Configuration of SIGTRAN consists of an SCTP part and an M3UA part.
SIGTRAN(SCTP) SCTP is a reliable transport protocol
operating on top of a potentially unreliable connectionless packet service such as IP.
It offers acknowledged error-free non-duplicated transfer of messages
SIGTRAN(SCTP) ZOYC - Creation of Association set
ZOYC:MSS1:C:M3UA:;
ZOYA – Adding Association to Association set
ZOYA:MSS1:ISU,1:SCTP:;
SIGTRAN(SCTP)
SIGTRAN(SCTP)
ZOYP – Configuring Association
ZOYP:M3UA:MSS1,0:"10.48.72.164","10.48.80.164",:"10.48.21.4",25,"10.48.25.4",25,:;
SIGTRAN(SCTP)
ZOYS – Activating Associations
ZOYS:M3UA:MSS1,0:ACT:;
SIGTRAN(M3UA) The M3UA in SIGTRAN (SS7 MTP3-User
Adaptation Layer) provides the applications with the same services as the MTP3
It routes the MTP layer 3 messages from the applications to the correct SCTP associations.
The M3UA Signalling channel acts as a link to the logical SCTP association set which leads to the next network element
SIGTRAN(M3UA) ZNSP - Create the IP signalling
link together with the signalling link set
(used to exchange MTP signalling messages.)
ZNSP:NA1,D‘9395,MSS01:0:MSS1:;
SIGTRAN(M3UA) ZNRC – Creating Signalling
Route& attaching IP Signalling Link to it.
ZNRC:NA1,D'9395,MSS01,0,D,N:NA1,D'9395,MSS01,7:;
SIGTRAN(M3UA) Activate Signalling Link and
Signalling Route Set by ZNLA, ZNLC , ZNVA & ZNVC
H.248
H.248 or MEGACO is the interface between MSS and MGW to control user - plane resources.
This interface is implemented by establishing control connection between signalling unit (CCSU / SIGU) in MSS to signalling unit (ISU) in MGW.
In MSS, this is implemented by creating MGW and in MGW it is implemented by creating virtual MGW.
User plane resources for MSC server can be created only after H.248 interface is created between MSS and virtual MGW.
H.248
To configure H.248 control interface for MSC Server 1. Add new MGW - Select the signalling unit at MSS side, which communicates
with the MGW. 2. Configure MGW
a. Add MGW to MSS's MGW database.b. Select the signalling unit in MSS side, which communicates with the MGW.c. Configure H.248 –specific data.d. Configure E.164 address of the MGW.e. Configure each virtual MGW 's domain name and IP address.f. Configure peer MSS's IP addresses and domain names of each virtual MGW.
3. Register MGWa. Check that registration is enabled from the MGW at MSS side.b. Activate registration process in the MGW.
H.248
H.248(Multimedia Gateway in MSS) ZJGC - Create MGWs in MSS
ZJGC:MGWID=0,ADDR="172.23.71.36",PORT=8009,NAME=RNMG280,MGWTYP=GEN:UTYP=SIGU,UINX=0,UADDR="172.23.6.132",AESA="E-919934129052",
LBCU=2800,REGA=Y,TTY=SCTP,NBR=3,:USEPARS=0,DEFPARS=0,:;
H.248(Multimedia Gateway in MSS)
ZJGR – Registering MGWs in MSS
ZJGR:MGWID=17:METD=1,REGA=Y,:;
( Registration should be done at both MGW and MSS side simultaneously)
ZJVC – Create VMGW’s in MGW ZJVC:VMN=M5G1V11,UINX=11,:OIP="10.237.1.78",OPN=8009,:A2T=,::;
H.248(Multimedia Gateway in MGW)
ZJVA – Adding control data in VMGW
ZJVA:VMN=M5G1V11,:CNT=0,:PIP="10.236.1.17",:SIP="10.236.9.17",::;
H.248(Multimedia Gateway in MGW)
ZJVR – Registering VMGW’s in MGW
ZJVR:VID=10,:REGA=1,:;
H.248(Multimedia Gateway in MGW)
Check connected functions of used ET with ZWTI.
Configuring TDM resources for integrated MSS
ZRCC - Create CGR
ZRCC:TYPE=ECCS,NCGR=S22G06,CGR=2001:DIR=BI,NET=N,SPC=D'9395,LSI=IU5NI,IFAC=5,UPART=4:METHOD=1,INR=INIK4,
TREE=80,NCCP=BASICINPSTNPBX,MGW=M2G2V17:; ` ZRCC:TYPE=SPE,NCGR=S22G06,CGR=2001:USE=VMGW:;
MSS side
MGW side
Configuring TDM resources for integrated MSS
ZRCA – Adding Circuits to CGR
ZRCA:NCGR=S22G06:TERMID=1287-1&&-15,:CIC=1,CICDIR=0,:UNIT=SIGU,:;
ZRCA:NCGR=S22G06:CRCT=32-0&&-10;
MSS side
MGW side
Configuring TDM resources for integrated MSS
ZRRC – Creating Route
ZRRC:INT,ROU=2000,NCGR=S22G06,OUTR=ONIK5,NCCP=BASICOUTPSTNPBX,,,:;
Configuring TDM resources for integrated MSS
ZJVM – Attach CGR to VMGW
ZJVM:VMN=M5G1V11:NCGR=S22G06; (VMGWs should be de-registered before
attaching and should be registered after attaching CGR)
Configuring TDM resources for integrated MSS
ZCEC – Change state of Circuits in MSS
ZCEC:CRCT=3-2&&-15:SE;
ZCEC:CRCT=3-2&&-15:WO;
Configuring TDM resources for integrated MSS
ZCIM – Change state of Circuits in MGW
ZCIM:CRCT=49-1&&-31:WO;
Configuring TDM resources for integrated MSS
Change State of CGR , circuits in MSS
ZCRM:NCGR=TEST1:WO;
Configuring TDM resources for integrated MSS
BSC Integration
MGW END ATER INTERFACE CONFIGURATION: 1. ZR2S:ET=239:NBR=2:; 2. ZR2C:ET=239:TCPCM=1,CPOOL=23,APCM=11184,:; 3. ZR2C:ET=239:TCPCM=2,CPOOL=23,APCM=11185,:;4. ZR2C:ET=239:TCPCM=3,CPOOL=23,APCM=11186,:;5. ZR2C:ET=239:TCPCM=4,CPOOL=23,APCM=11187,:;
CREATE SIGNALLING LINK1. ZNCN:92:239-31,64:ISU,3:0:;
BSC Integration
CREATE LINKSET & ADD LINKS TO LINKSET:
1. ZNSC:NA1,D'304,Z3BN4:92,0:;
2. ZNSA:NA1,D'304,Z3BN4:93,1:;
BSC Integration
CREATE ROUTESET AND ADD AOPC(MSS POINT CODE)1. ZNRC:NA1,D'304,Z3BN4,1,D,N:,,,7:;
2. ZNRB:NA1,D'304:AOPC=D'7151:;
BSC Integration
ACTIVATION 1. ZNLA:92&93;
2. ZNLC:92,ACT;
3. ZNVA:NA1,D'304::;
4. ZNVC:NA1,D'304::ACT:;
BSC Integration
CIRCUIT GROUP AND CIRCUITS1. ZRCC:TYPE=SPE,CGR=340,NCGR=BNI004:US
E=VMGW:;
2. ZRCA:CGR=340:CRCT=11184-1&&-31:;
3. ZRCA:CGR=340:CRCT=11185-1&&-31:;
BSC Integration
ADD CIRCUIT GROUP TO VMGW1. ZJVE:VMN=MG1SHLV08,:CGR=340,:;
BSC Integration
STATE OF CIRCUIT GROUP AND CIRCUITS
1. ZCIM:CGR=340:WO;
2. ZCIM:CRCT=11184-1&&-31:WO;
3. ZCIM:CRCT=11185-1&&-31:WO;
BSC Integration
MSS END CREATE ROUTE SET VIA
MGW:
ZNRC:NA1,D'306,Z3BN6,1,D,N:NA1,D'1100,MG1SH,7:;
BSC Integration
ACTIVATION OF ROUTE SET
ZNVA:NA1,D'306:NA1,D'1100:;
ZNVC:NA1,D'306:NA1,D'1100:ACT:;
BSC Integration
CIRCUIT GROUP AND CIRCUITS
ZRCC:TYPE=ECCS,CGR=340,NCGR=BNI004:DIR=OUT,NET=NA1,SPC=D'304,LSI=AIF02,IFAC=25,UPART=5:MGW=MG1SHLV08:;
ZRCA:CGR=340:TERMID=11184-1&&31,:
CIC=1,CICDIR=0,::UNIT=BSU,INDEX=1:;
ZRCA:CGR=340:TERMID=11186-1&&-31,: CIC=65,CICDIR=0,::UNIT=BSU,INDEX=3:;
BSC Integration
SCCP & SUBSYSTEMS :1. ZNFD:NA1,D'304,1:FE,BSSAP,1,Y:;
2. ZNGC:NA1,D'306:ACT:
3. ZNHC:NA1,D'306:FE:ACT:;
BSC Integration
CREATE ROUTE:1. ZRRC:EXT:ROU=318,OUTR=OMCG0,NCC
P=BASICOUTPSTNPBX,STP=1,TON=UNK,NCGR=BNI004,:;
BSC Integration
CIRCUIT GROUP AND CIRCUITS:
1. ZCRM:NCGR=BNI004:WO;
2. ZCEC:MGW=MG1SHLV08,TERMID=11184-
1&&-31,:BA; 3. ZCEC:MGW=MG1SHLV08,TERMID=11184-
1&&-31,:WO;
BSC Integration
ZEDC – Create BSC
ZEDC:TYPE=BSC,NAME=DHARAM,NO=3:::;
BSC Integration
ZELC - CREATE LAC AND ROUTES
ZELC:NAME=DHARAM,LAC=3000:RNAME=BHADDI;
ZEDL:NO=3:NA1,D'304:; ZEDR:NO=7:23,318,:;
BSC Integration
CREATE AND ADD BTS 1. ZEPC:NAME=JUDIKURDS1,NO=12011:LAC=3000,CI=12011,MCC=405,MNC=754:;
2. ZEPB:NO=12011:BSCNO=3:LAC=3000,:;
3. ZEPS:NO=12011,:U:;
BSC Integration
MSS – MSS/GCS Integration
Configuring IP network in MSC Server
Configuring C7 Signalling in MSC Server
Configuring User Plane Routing and Topology
Creating circuit groups for control plane routing
Creation of digit analysis towards other MSSs
Creation of UPD analysis towards other MSSs
Configuring IP version 4 interface
ZQRN:ISU,1::EL0:10.48.32.40,L,:1500:UP:;
MSS – MSS/GCS Integration
Create default static route
ZQKC:ISU,1:10.48.32.128,25:10.48.73.65:LOG;
MSS – MSS/GCS Integration
Configuring SCTP multihoming
ZOYN:ISU,1:IPV4:"10.48.68.100","10.48.76.100";
MSS – MSS/GCS Integration
ZWOI - Check DSCP value in PR File
ZWOI: 53, 9,:;
MSS – MSS/GCS Integration
ZNRP - Configure own signalling of MSC Server.
MSS – MSS/GCS Integration
ZNPI – Check if BICC service is defined.
Necessary Process Family of BICC is 5C9.
MSS – MSS/GCS Integration
ZOYC - Creation of Association set ZOYC:MSS2:C:M3UA:;
MSS – MSS/GCS Integration
ZOYA – Adding Association to Association set
ZOYA:MSS2:SIGU,1:SCTP:;
MSS – MSS/GCS Integration
ZOYP – Configuring Association ZOYP:M3UA:MSS2,0:"10.48.72.164","10.48.80.164",:"10.48.21.4",25,"10.48.25.4",25,:;
MSS – MSS/GCS Integration
ZOYS – Activating Associations ZOYS:M3UA:MSS2,0:ACT:;
MSS – MSS/GCS Integration
ZNSP - Create the IP signalling link together with the signalling link set
(used to exchange MTP signalling messages.)
ZNSP:NA1,D‘9395,MSS01:0:MSS1:;
MSS – MSS/GCS Integration
ZNRC – Creating Signalling Route& attaching IP Signalling Link to it.
ZNRC:NA1,D'9395,MSS01,0,D,N:NA1,D'9395,MSS01,7:;
MSS – MSS/GCS Integration
Activate Signalling Link and Signalling Route Set by ZNLA, ZNLC , ZNVA & ZNVC
MSS – MSS/GCS Integration
Configuring User Plane Routing and Topology Integrate SS7 configuration. Create UPDs. Attach MGWs to UPDs.
SS7 configuration. Create BICC user part and C7
signalling configuration.
Configuring User Plane Routing and Topology
ZJGI – Interrogate created VMGWs
Configuring User Plane Routing and Topology
UPD Analysis
ZJFC – Creation of UPD
ZJFC:NUPD=UPDIPBB:BNCC=IPV4:NORM=PREP,EMERG=PREP:STOM=DC,TRUNK=Y,ACHM=0,:DCODEC=EFR:;
ZJFC:NUPD=UPDAAL2:BNCC=AAL2:NORM=PREP,EMERG=PREP:STOM=DC,TRUNK=Y,ACHM=0,:DCODEC=EFR:;
UPD Analysis
ZJFA – Add VMGWs to UPDZJFA:UPD=0:MGW=0&&28:LDSH=50:RACC=N,RORIG=Y:;
ZJFA:UPD=1:MGW=0&&28:LDSH=50:RACC=N,RORIG=Y:;
Circuit groups for control plane routing ZRCC - Create a BICC Circuit group
ZRCC:TYPE=BICC,NCGR=BICC1,CGR=2000:DIR=BI,NET=NA1,SPC=3F9,LSI=BICC01:METHOD=1,INR=IBIC0,TREE=81,NCCP=INCCPARIMCG0;
ZRCA – Adding CIC to BICC CGR
ZRCA:NCGR=BICC1:CIC=0&&254:UNIT=SIGU,INDEX=1:;
Circuit groups for control plane routing
Route for control plane routingZRRC – Create Route for
CP routing ZRRC:EXT:ROU=1001,OUTR=OBIC0,STP=1,TON=NAT,NCCP=BASICOUTPSTNPBX,NCGR=BICC1,:;
Digit Analysis Towards MSS
PUPD - This phase is executed only if the incoming signalling is BICC
SBNC - This phase is needed to figure out bearer technology used towards the succeeding MGW. This phase is executed only if the outgoing signalling is BICC
Digit Analysis Towards MSS
CMN - This phase is used to detect whether an MSS should act as a CMN node. This phase is executed only if both the incoming and the outgoing signalling are the same.
SUPD - This phase is executed only if the outgoing signalling is BICC
Digit Analysis Towards MSS
SAI - This phase is executed only if the outgoing signalling is BICC.It controls the used BICC bearer establishment method.
ICBNC - This phase is executed when there are two MGWs involved in the call in one MSS area and an interconnection is needed between the MGWs.
Digit Analysis Towards MSS
ZJUR – Create Final Result ZJUR:PUPDMSS1,PUPD,CONT:PUPD=0;
ZJUR:PUPDDEF,PUPD,STOP:;
ZJUR:PUPDUNK,PUPD,STOP;
ZJUR:SBNCMSS1,SBNC,CONT:SBNC=IPV4;
ZJUR:SBNCDEF,SBNC,STOP:;
ZJUR:SBNCUNK,SBNC,STOP:;
ZJUR:CMNACT,CMN,CONT:CMNI=ACTIVE:;
ZJUR:CMNDEF,CMN,STOP:;
ZJUR:CMNUNK,CMN,STOP:;
Digit Analysis Towards MSS
ZJUR ZJUR:SUPDMSS1,SUPD,CONT:SUPD=0;
ZJUR:SUPDDEF,SUPD,STOP:;
ZJUR:SUPDUNK,SUPD,STOP;
ZJUR:SAIFORW,SAI,CONT:SAI=FORW;
ZJUR:SAIDEF,SAI,STOP:;
ZJUR:SAIUNK,SAI,STOP;
ZJUR:ICBNCIPB,ICBNC,CONT:ICBNC=IPV4;
ZJUR:ICBNCDEF,ICBNC,STOP:;
ZJUR:ICBNCUNK,ICBNC,STOP;
Digit Analysis Towards MSS
ZJUC - CREATE SUB ANALYSIS
ZJUC:PUPDANA,START,PUPD:PUPDR=3001:RES=PUPDMSS1,DEFRES=PUPDDEF:UNKRES=PUPDUNK:; ZJUC:SBNCANA,START,SBNC:SUPDR=3001:RES=SBNCMSS1,DEFRES=SBNCDEF:UNKRES=SBNCUNK:; ZJUC:CMNANA,START,CMN:PUPDR=3001:RES=CMNACT,DEFRES=CMNDEF:UNKRES=CMNUNK:; ZJUC:SUPDANA,START,SUPD:SUPDR=3001:RES=SUPDMSS1,DEFRES=SUPDDEF:UNKRES=SUPDUNK:; ZJUC:SAIANA,START,SAI:SBNC=IPV4:RES=SAIFORW,DEFRES=SAIDEF:UNKRES=SAIUNK:; ZJUC:ICBNCANA,CONT,ICBNC:PSIGT=TRUNK:RES=ICBNCIPB,DEFRES=ICBNDEF:UNKRES=ICBNUNK;
Digit Analysis Towards MSS
ZJUN - Change State of Sub–Analysis
ZJUN:MTN,SAIANA:;
ZJUN:MTN,SUPDANA:;
ZJUN:MTN,CMNANA:;
ZJUN:MTN,SBNCANA:;
ZJUN:MTN,PUPDANA:;
ZJUN:MTN,ICBNCANA:;
Digit Analysis Towards MSS
ZRRM - To bring the control plane direction component to the user plane analysis.
ZRRM:ROU=1001,UPDR=3001:;
Route for control plane routing
ZRCM – Modifying / Add UPDR data to circuit group.
ZRCM:CGR=2000::UPDR=3001;
Circuit groups for control plane routing
ZCRM – Change state of the CGR.ZCRM:NCGR=BICC1:WO;
Circuit groups for control plane routing
ZCEC – Change of state of CICsZCEC:NAT=NA1,SPC=3F9,CIC=0&&254,:WO:;
Circuit groups for control plane routing
Route for control plane routing ZCRC – Change State of Route
ZCRC:ROU=1001:WO;
This Route can then be further used in the existent sub-destination or a New sub-destination for further digit analysis and tree routing.
TDM connectivity with HLR
ZYEF – Check if PCM is OK
ZYEF:ET,258;
ZYEC – Change the frame alignment mode of ET
ZYEC:ET,258:NORM, CRC4;
TDM connectivity with HLR
ZNCC – Create TDM Signalling Link
ZNCC:36:258-1,64,1,1:CCSU,6:0:;
TDM connectivity with HLR
ZNSC – Attach Signalling link to Signalling Link Set
ZNSC:NA1,D'191,X3H02:36,0:,:::;
TDM connectivity with HLR
TDM connectivity with HLR
ZNRC – Create Signalling Route Set
ZNRC:NA1,D'191,X3H02,0,D,N:NA1,D'191,X3H02,7::::;
TDM connectivity with HLR
ZNFD – Create SCCP Signalling point and Subsystems
ZNFD:NA1,D'191,0:6,MAPH,0,Y:8,MAPM,0,Y::::;
TDM connectivity with HLR
ZNAC – Create GT translation Result
ZNAC:NET=NA1,DPC=D'191,RI=GT;
TDM connectivity with HLR
ZNBC – Create GT Analysis
ZNBC:::919839000004:3:;
Activation
ZNLA:36:;
ZNLC:36,ACT:;
Activation
ZNVA:NA1,D'191::;
ZNVC:NA1,D'191::ACT:;
Activation
ZNGC:NA1,D'191:ACT:;
ZNHC:NA1,D'191:6:ACT:;
ZNHC:NA1,D'191:8:ACT:;
Configuration of POI
MGW END: CHANGE ET MODE TO DBLF: ZYEC:ET,227:NORM,DBLF:; ZYEC:ET,261:NORM,DBLF:;
Configuration of POI
CREATE LINK: ZNCN:6:227-16,64:ISU,7:0:; ZNCN:6:228-16,64:ISU,8:0:;
Configuration of POI
CREATE LINKSET: ZNSC:NA0,D'9544,ZCM00:6,0:7,1:::;
Configuration of POI
CREATE ROUTESET: ZNRC:NA0,D'9544,ZCM00,0,D,N:,,,7::::;
Configuration of POI
ADD AOPC(MSS POINT CODE) ZNRB:NA0,D'9544:AOPC=D'5244:;
Configuration of POI
ALLOW LINK & ROUTESET,THEN ACTIVATE:
ZNLA:6:; ZNLC:6,ACT:; ZNVA:NA0,D'9544:NA0,D'9544:; ZNVC:NA0,D'9544:NA0,D'9544:ACT:;
Configuration of POI
CRAETE CIRCUIT GROUP: ZRCC:TYPE=SPE,CGR=1801,NCGR=ICCI0
0:USE=VMGW:;
Configuration of POI
ADD CIRCUITS TO CIRCUIT GROUP: ZRCA:CGR=1801:CRCT=227-1&&-15&-
17&&-31:; ZRCA:CGR=1801:CRCT=261-1&&-15&-
17&&-31:;
Configuration of POI
ADD CRICUIT GROUP TO VIRTUAL MGW: ZJVE:VMN=MG1SHLV07,:CGR=1801,:;
Configuration of POI
UNBLOCK CIRCUIT GROUP & CIRCUITS: ZCIM:CGR=1801:WO; ZCIM:CRCT=227-1&&-15&-17&&-31:WO; ZCIM:CRCT=227-1&&-15&-17&&-31:WO;
Configuration of POI
MSS END: CREATE ROUTESET VIA MGW: ZNRC:NA0,D'9544,ZCM00:NA0,D'1100,MG1
SH,7:;
Configuration of POI
ALLOW & ACTIVATE ROUTESET: ZNVA:NA0,D'9544:NA0,D'1100:; ZNVC:NA0,D'9544:NA0,D'1100:ACT:;
Configuration of POI
CREATE CIRCUIT GROUP: ZRCC:TYPE=ECCS,NCGR=ICCI00,CGR=18
01:DIR=BI,NET=NA0,SPC=D'9544,LSI=IU4NI,IFAC=5,
UPART=4:METHOD=1,INR=INIK4,TREE=70,NCCP=BASICINPSTNPBX,MGW=MG1SHLV07:;
Configuration of POI
CHANGE STATE OF CIRCUIT GROUP: ZCRM:NCGR=ICCI00:WO;
Configuration of POI
ADD CIRCUITS TO CIRCUIT GROUP: ZRCA:CGR=1801:TERMID=227-1&&-
15,:CIC=1,CICDIR=0,::UNIT=SIGU,INDEX=5:; ZRCA:CGR=1801:TERMID=227-17&&-
31,:CIC=17,CICDIR=0,::UNIT=SIGU,INDEX=5:; ZRCA:CGR=1801:TERMID=261-1&&-
15,:CIC=33,CICDIR=0,::UNIT=SIGU,INDEX=6:; ZRCA:CGR=1801:TERMID=261-17&&-
31,:CIC=49,CICDIR=0,::UNIT=SIGU,INDEX=6:;
Configuration of POI
CHANGE STATE OF CIRCUITS: ZCEC:TERMID=227-1&&-15&-17&&-
31,MGW=MG1SHLV07,:SE; ZCEC:TERMID=227-1&&-15&-17&&-
31,MGW=MG1SHLV07,:WO; ZCEC:TERMID=261-1&&-15&-17&&-
31,MGW=MG1SHLV07,:SE; ZCEC:TERMID=261-1&&-15&-17&&-
31,MGW=MG1SHLV07,:WO;
Configuration of POI
CREATE ROUTE: ZRRC:EXT:ROU=2002,OUTR=ONIK5,NCCP
=BASICOUTPSTNPBX,STP=1,TON=NOE,NCGR=ICCI00,:;
Configuration of POI
CREATE SUBDESTINATION AND DESTINATION:
ZRDE:NSDEST=NSHARC00:ROU=2002,SP=10,CT=NC,:;
ZRDE:NDEST=DAIRCSH0,:NSDEST=NSHARC00,:NCHA=CHARGE,:;
Configuration of POI
NUMBER DEFINATION: ZRDC:DIG=98570&&-4,TREE=2,
TON=NAT,:NDEST=DAIRCSH0,:;
IP configuration SCTP Multi-homing (not mandatory for 1st Call)
Own Signalling Point Data. License Installation & Feature Activation Default Parameters
PR File
FI File
Configuration for 1st Call
Configuration for First Call
Signalling Parameters
SS7 Signalling Link Set Parameter
SS7 Signalling Route Set Parameters
SCCP Parameter Set
SS7 Level 3 Parameters
MAP Parameters
Configuration for First Call
Network Element Specific Parameter
VLR Parameters
PLMN Parameters
MSC Number Range
Network & NE Specific Numbers
MSC Specific Numbers
Configuration for First Call
SS7 services SCTP Parameter set Pre-analysis Routing Attribute Sub-Analysis & Final Result End of Selection BSSAP Parameters
Configuration for First Call
Call Control Parameters SPRs
GSMEND
HLRENQ
HANDOVER (not mandatory for 1st Call) IMSI analysis
Configuration in MGW
IP configuration Own Signalling Point Data. Default Parameters
PR File
FI File SS7 services
Configuration in MGW
Signalling Parameters
SS7 Signalling Link Set Parameter
SS7 Signalling Route Set Parameters
SCCP Parameter Set
SS7 Level 3 Parameters
SCTP Parameters
Configuration in MGW
License Installation & Feature activation MGW Specific Default Parameter DSP parameter & Capacity handling
Integration of MGW with MSS.
Integration of HLR with MSS.
Integration of BSC with MSS & MGW.
Digit Analysis
IP Configuration
IP configuration – Configuring MSS for its connectivity with other IP based network elements. ESB configuration : Define Ethernet interfaces. ZQRN : Define IP addresses for all the required
signalling units from which coonectivity is required ZQRT : define TCP/IP parameters for signalling
IP Configuration
ZQKC : Define Static Route. It is required for all different networks in order to correctly route outgoing IP packets to the configured destination.
SCTP Multi-homing ZOYN : The SCTP multi-homing should be used
to increase the redundancy of the M3UA and H.248 protocols that use the SCTP.
Defining Own specific Data
Own Signalling Point
The own signalling point has to be defined before we can create the other objects of the signalling network.
ZNRP:NA1,D’11563,MSS81,STP:ITU-T::;
ZNRP:NA1,D’9588,MSS80,STP:ITU-T::;
PR FILE
PR File - General Parameter File
The parameters are organized into parameter classes each of which represents a specific functional area.
ZWOC:3,009,5E;
FE FILE
FI file – Feature Information Control File
The featured parameter is not visible if feature for respective parameter is not activated for the customer.
ZWOA:1,98,A;
MTP implementation Signalling Link Parameters SS7 Signalling Link Set Parameter
The parameters in the signalling link parameter set define the function of the signalling link. Each signalling link uses the signalling link parameter set attached to it.
ZNOI;
MTP implementationRoute set Parameters SS7 Signalling Route Set Parameters
The parameters in the signalling route set parameter set define the signalling route set signalling functions. Each signalling route set uses a signalling route set parameter set attached to it.
ZNNI;
Defining SCCP
SCCP Parameter Set SCCP signalling point parameter set define the SCCP signalling parameters for certain timers that are used in monitoring the signalling connections, and for managing the subsystems of the own SCCP signalling point and the SCCP signalling functions towards remote SCCP signalling points.
ZOCI;ZOCJ;
Defining SS7 parameters
SS7 Level 3 ParametersMTP level 3 signalling parameters define the
functions of the whole MTP of the network element. Some of the parameter values are related to monitoring the functions, while others define various limits and timers.
ZNMI;
Defining MAP parameters
MAP Parameters
It defines the SCCP return option, the overload control, the standard of the TCAP, SCCP address, object identifier and the number of authentication sets used in different MAP versions.
ZOPM:TCAP=ANSI,OBID=ANSI,ADDR=ANSI;
ZOPH:MODIFY:AC=5,AMWL=NO:VER=3;
Defining VLR parameters
VLR Parameter - The VLR parameters are used to control certain functionality in the VLR like
General VLR operations (VLR cleaning, triplet/quintet record and deregistration)
Security operations (The use of authentication and IMEI checking)
The use of TMSI paging and searching
Defining VLR parameters
The support of supplementary services, teleservices, and bearer services
Network Identity & Time Zone parameters
Default access right reject cause codes
The VLR-specific parameters are general parameters of the VLR, meaning that they do not depend on the subscriber's HPLMN
Defining PLMN parameters
The PLMN-specific parameters control VLR functions which depend on the subscriber's HPLMN.
Roaming status
IMEI checking parameters
TMSI allocation parameters
Authentication and ciphering parameters
Advice of Charge parameters
Defining PLMN parameters
Equal Access parametersIntelligent Network parametersNITZ parametersInter-PLMN handover agreement listEquivalent PLMN listDefault access right reject cause codesAccess rights to GSM/UMTS radio
network
Defining MSRN & Handover Number range (MSC specific) MSC Number Range
We need to define number range for MSRN allocation and Inter MSC Handover. These number ranges are unique for every MSS.ZWVC:MSRN=919732898000&&919732898999:RNGP=0:;
ZWVC:HON=9733298400&&9733298599:TON=NAT;
Network & NE Specific Numbers
Network & NE Specific Numbers – Define numbers that specify a particular network or network element.
Own network code : numbering plan International prefix : type of prefix National prefix : type of prefix
ZWWS:CC=91:NP=E164;ZWWS:NDC=9732:NP=E164;ZWWS:IPRE=00;
MSC Specific Numbers
MSC Specific Numbers – Define Network and MSC specific numbers important for proper identification globally.ZWVS:MCC=405;
ZWVS:MNC=67;
ZWVS:MSC=919733000009:NP=E164,TON=NAT;
Defining SS7 services
SS7 services – To create user parts for MTP which uses services of MTP in SS7 for example BICC , SCCP etc
ZNPC:NA0,03,SCCP:Y:Y,10E,10F:;
Defining SCTP parameters
SCTP Parameter Sets –It control how the SCTP association is working And should be uniform at both ends of the SCTP association. If the SCTP parameters are different between peers, the value of the SCTP parameters should be harmonized in both ends
ZOYO;
Digit Analysis - Preanalysis
Preanalysis – To examine the numbers being dialled in
order to establish the type of call being made. To identify a service, service group or
emergency call. To send dialled digits modification
instructions on how to remove or add dialled digits.
Digit Analysis - Preanalysis
To analyse the nature of the dialled digits and change it to the “characteristics of number”.
Identify local calls (add local area code). Recognise a certain dialling pattern (prefix) from the
MS in order to proceed routing based on calling line identity (CLI).
Recognise prefixes for CLI presentation (whether the CLI is presented to Subscriber B or not)
Number of removed digit
Characteristic of number
Numbering Plan
Call Characteristic
Result Identifier
Numbering Plan
Type Of Number
Dialled Digits
011 2345678
UNKNOWN
E.164(ISDN/Telephony
Continue call setup
Normal call
E.164 (ISDN/Telephony)
National
1
Digit after pre-analysis = 11 2345678
Dialling Preanalysis
Number Dialled:
050 1234567
Example of Dialling Pre-analysis Input and Output Parameters
Routing Attribute Sub-Analysis & Final Result
Routing attribute analysis – Tree to be used for different calls depending
on the attributes associated with them. Intermediate announcement to calling (or
redirecting) subscriber with a Chargeable / free announcement indication.
Routing Attribute Sub-Analysis & Final Result Routing attribute analyses are made before the CM
digit analysis at points where the called or redirected number is brought to the digit analysis
They are not made for roaming or handover numbers and after number modification has been done.
The default result is that the analysis does not change the digit analysis tree and There is no announcement for the subscriber
Routing Attribute Sub-Analysis & Final Result
TypeUnitOrDepartmentHereTypeYourNameHere
Digitanalysis tree
Intermediateannoucement
Attributes
Digitanalysis
Routing Attributeanalysis
Destination
Hello
End Of Selection (EOS)
End Of Analysis – Examines the clear code, after which the call
may be disconnected, reanalysed, or lead to an alternative destination, depending on the incoming signalling and the given control codes.
End Of Selection (EOS)
It is used when the call attempt fails before the conversation state is achieved.
The EOS analysis contains the control information for giving the right response to each individual clear code.
ZRXI:RESGR=0;
BSSAP Parameter
BSSAP Parameter – An MSC contains 50 pre-packaged BSSAP
service profile descriptions, which define the data combinations of BSS functions and values of A-interface timers and parameters.
BSSAP Parameter
ZEDT – To modify BSSAP parameters
ZEDT:VER=9:F,3,1;
Call Control Parameter
Call Control Parameters
We define circuit group and route-specific data used by call control programs. One outgoing parameter set and one incoming set must be defined per each route/circuit group. IN Call Parameters OUT Call Parameters
Call Control Parameter
Call Control Parameters Handling - Define parameters concerning messages, call forwarding, announcements, handling of free calls, handling of CLI ,handling of PSTN related calls ,Voice Processing System calls ,etc
Call Control Parameter
To create a parameter set which is used for routing administration on the incoming circuits.
ZCPC:EXTIP:RESGR=3::ASKCLI=Y;
Call Control Parameter
To create a parameter set which is used for routing administration on the out going circuits.
ZCPJ:HANDOVER:IIDCLI=Y;
SPRs
SPR - SPR instructs the exchange to retain the call in the MSC because some other actions need to be done to the call before it can be routed out
SPRs
The SPRs used are:· HLRENQ SPR· GSMEND SPR· SPR with inter-MSC handover· Number modification SPR· Announcement SPR· SPR with data call; the call must pass through the modem pool before being routed out of the exchange· SPR with an IN call
SPR - HLRENQ
During every MTC, an HLRENQ must be performed to find out the MSC where the subscriber is located at the moment.
SPR - HLRENQ
Signalling messages from the MSC to the HLR can be routed using the two main principles:
· routing on label
· routing on Global Title (SCCP routing).
SPR - HLRENQ
HLRENQ routed on label
The definition for the SPR HLRENQ must contain the signalling point code from the HLR
HLRENQ routed on Global Title
It is the most flexible and elegant way of routing HLRENQs to the HLRs. Only one SPR for HLRENQ,
SPR - HLRENQ
ZRPR:STP=1,SPR=3,DIG=919732000007,TON=INT,NP=E164,:;
ZRPR:STP=1,SPR=4,DIG=919733000007,TON=INT,NP=E164,:;
ZRPR:STP=1,SPR=5,DIG=919732000017,TON=INT,NP=E164,:;
SPR - GSMEND
GSMEND SPR – Mobile Terminating Call
For a mobile-terminated call, the MSC receives its own MSRN back from the Trunk / HLR after HLRENQ which is then further analyzed in respective tree and the call is routed and terminated using GSMEND.
SPR - GSMEND
ZRPE
ZRPE:OUTR=OMCG0,STP=1,SPR=1:;
IMSI Analysis
IMSI Analysis – It is defined in all VMSCs in the visited PLMN area.
The MCC and MNC parts of IMSI are used to derive the correct PLMN.
Usually the first two digits of the Mobile Subscriber Identification Number (MSIN) are used to indicate the HLR within the subscriber's PLMN.
IMSI Analysis
ZCFC – Create IMSI Analysis
ZCFC:IMSI=405750,IMSIINDIC=120,PLMN=VODAFONE_JK,TOA=GT,:TON=INT,NP=E214,SRD=1,NRD=5,SAD=1,DIA=919796;
Configuration for DATA call
ZQKC - Create Static route for CDS
ZQKC:ISU,3:10.40.20.0,25:10.48.89.1:LOG:;
Configuration for DATA call
ZQRX – After creation of static route do check if used ISU is able to ping the network IP of CDS.
Until and unless the units doesn’t ping IWF resources created won’t get registered.
Configuration for DATA call
ZRCC – Creation of CGR for CDS
ZRCC:TYPE=SPE,NCGR=MZWB71,CGR=810:USE=VMGW:;
Configuration for DATA call
ZRCA – Adding circuits to CGR
ZRCA:CGR=810:CRCT=1774-1&&-31:;
Configuration for DATA call
ZJCH – To define own ISU specific IP address for TCP/IP and the current IWF/CDS resources hunting method.
ZJCH:UINX=3,OIP="10.48.73.6",HUNT=1:;
MGW IPA2800 2009-09-15 15:50:25UNIT DATA:
ISU UNIT ID : 3 OWN ADDRESS : 010.048.073.006HUNTING METHOD : PRIORITY
=========================================
COMMAND EXECUTED
Configuration for DATA call
ZJCA - To add an IWF priority entry.
ZJCA:UINX=3,PRIO=1:TTY=1:PIP="10.48.20.5",PPORT=8014,NENAME=M7G1V05,:;
Configuration for DATA call
ZJCI:UINX=3,;MGW IPA2800 2009-09-15 16:53:44IWF PRIORITY LIST:
ISU UNIT ID : 3 OWN ADDRESS : 010.048.073.006HUNTING METHOD : PRIORITY=========================================PRIORITY : 1 NE NAME : M7G1V05 TRANSPORT TYPE : TCPPRIM IWF ADDR : 010.048.020.005PRIM IWF PORT : 8014 SEC IWF ADDR : -SEC IWF PORT : -PARAMETER SET : -REG STATUS : REGISTEREDUSED ADDR : 010.048.020.005--------------------------------AVAIL CONG USED IWF RESOURCES------ ---- ------------------YES NO 50
COMMAND EXECUTED
Configuration for DATA call
ZJCM – To modify IWF connection status
ZJCM:UINX=3,PRIO=1,CONN=0:;
Configuration for DATA call
ZJVE – Adding CGR to VMGW
ZJVE:VID=4,:CGR=810,:;
Configuration for DATA call
ZCIM – Activating CGR
ZCIM:CGR=810:WO:;
Configuration for DATA call
ZCIM – Activating Circuits towards CDS
ZCIM:CRCT=1774-1&&-31:WO:;
Configuration for Location Update
The following configurations are required to be done in MSS for Location Update
SS7 services IMSI analysis MAP Parameters Home PLMN Parameters Integration with HLR Integration with BSC/BTS.