Sie sind auf Seite 1von 17

MSS4.

0 Core Network Configuration Seminar


Agenda:
MSS4.0 CN Configuration Scope
MSC Server Configuration (R12)
MGW Configuration (R4)

MGW Configuration R4

MGW Configuration

MGW Configuration procedure


-Input:
Network Design Document
MGW MO Scripts User Guide
MGW MO Scripts template

-Output:
Mo Scripts for MGW node

-Procedure:

Following the MGW MO Scripts User guide and MGW HW configuration, select MO subfiles from MGW MO Scripts Template.
Following the Network Design Document. Modified the MO scripts template to satisfied the
network requirement.

MGW Configuration R4
Structure of MO Scripts of MGW R4
Modularity:
Subrack Level:
Example: BC3024 node has 6 subracks:
1 Central Processor Module (CPM)
4 M-MGw MODULEs
1 OPTIONAL ET MODULE.
Internal Subrack Level:
Different Subrack has different configuration. Please select the MGW HW
Configuration from MGW B-module.
Signalling Standard Level:
Correct Signalling Standard must be chosen.

System/Local Indication:
There are two kinds of MO script filename extended name:
SYS: The .sys files are standard for all nodes and all markets, which cant be changed.
LOC: The .loc files are dependent on the specified network configuration, which should
be changed according to the network design.

MGW Configuration R4
Description and Loading sequence of MO scripts:
File Name

Description

01_HW_Definition_SYS Describes the available board types (PIU Type)


02_..._HW_Configuration_LOC
Describes the HW configuration of the node
include all Switch-module, Subracks and all Slots
03_CPP5_SW_Definition_SYS
Lists all CPP5 loadmodules product No./Rev/Path
03_UPCF_SW_Definition_SYS
Lists all UPCF loadmodules product No./Rev/Path
04_..._SW_Allocation_SYS
Describes the way the loadmodules allocated on
each slots(GPB/SCB/SXB/MSB/ET-M4/ET-MFG/ETC41/ET-MC1) in all
subracks and loadmodules
reliable-state
05_SW_Roles_Definition_SYS
Lists the SW roles used by upgrade, LM match Board
06_..._SW_Roles_Allocation_SYS Allocates the SW roles to the all boards, SW will
control Boards
07_..._ISL_and_Alarm_...
Defines the Alarm, Inter-Subrack Links, Fans
08_..._ET_boards_definition_SYS Defines the ET-Boards MOs(ET-M4/ET-MFG/ETC41/ET-MC1) in all subracks
09_TUB_Definition_SYS Defines the general characteristics of the TUBs

MGW Configuration R4
File Name

Description

10_..._Resource_Accesses_MGw_SYS
Creates the MGW Application and Resource Access
11_Media_Stream_Services_SYS Defined the services for device in pools in MSB
12_..._DevicePools_SYS Defined the device pools for the MSB devices
13_..._MSB_ Lock_SYS Locks the MSBs
14__MSB_Device_Group_Definition
Defined a device group in each MSB board
15__MSB_Device_Set_Allocation_SYS
Allocates SW to MSB boards in MGW subracks
16_..._MSB_Unlock_SYS
Unlocks the MSBs
18_UPCF_MGw_Application_SYS
Defines MGWApplication
19_..._UPCF_Connection_Handlers_SYS
Defines the UPCF Connection Handler
20_..._UPCF_Media_Stream_Controllers_SYS
Creates UPCF Mesc in MGW subracks Slot 2/3
All HW&SW system configuration is finished.
5

MGW Configuration R4

File Name

Description

22_..._ET_Ports_ITU_LOC

Defines all ET Ports in ET boards

Board
ET-MC1
ET-C41
ET-M4
ET-MFG

Ports
8 E1PhysPathTerm
4 Os155SpiTtp
2 Os155SpiTtp
1 GigaBitEthernet

24_..._MSPG_Groups_LOC

Interface
63 Vc12Ttp
1 AtmPort

Description
E1-board
ET155-board
ATM-board
IP-board

Defines Multiplex Section Protection Group (MSPG)

Example: 2 Os155SpiTtp ports on ET-C41 boards could be defined as MSPG,


one ports should be Active; Another one should be Standby;
Muxmode 0 - standby
1 - Active for E1
2 Active for ATM

25_Network_Synchronization_LOC
Defines Network Synchronization

MGW Configuration R4
File Name

Description

26_ATM_Traffic_Descriptors_LOC Defines ATM traffic descriptors

27_..._Ds0Bundles_LOC Defines Remote-TDM Ds0Bundles for


signalling and traffic on ET-MC1 and ET-C41 boards

28_..._VP_VC_ITU_LOC Defines ATM VP/VC for each ATM board(ET-M4)

29..._Atm_Cross_Connect_LOC

Defines the ATM cross connections

30_NNISAAL_Profiles_LOC

Defines NNISAAL profiles

MGW Configuration R4

|--------------------------------------|
|ISUP |BICC& Q.2630&GCP|
|&TUP|
|
|--------------------------------------|
|MTP3 | MTP3b | M3UA |
|--------------------------------------|
| MTP2 | NNI-SAAL | SCTP |
|
| AAL5
|
|
|--------------------------------------|
| TDM | ATM
| IP
|
|(MTP1)|
|
|
|-------------------------------------- |
8

MGW Configuration R4
31_..._MTP3_Broadband_Signalling_LOC Defines MTP3b broadband signalling
Layer1(Physical):

VplTp (VPI)

VpcTp (interface between VPI and VCI)


VclTp (VCI)

Layer2:
Aal5TpVccTp

(AAL5)

NniSaalProfile
NniSaalTp (NNI-SAAL)

Layer3:
Mtp3bSpItu

(OWN SP ITU )

Mtp3bSpChina
(OWN SP China )
Mtp3bSrs (MTP3b Signalling Route Set to other NODE,SP)
Mtp3bAp (remote Access point code)
Mtp3bSls (SS7 signalling link set ,LS)
Mtp3bSr (MTP3b Signalling Route ,DEST)
Mtp3bSlItu (signalling link code ,SLC)
Mtp3bSlChina
(signalling link code ,SLC)
9

MGW Configuration R4
32_..._MTP3_Narrowband_Signalling_LOC Defines MTP3 narrowband signalling
Layer1(Physical):

DS0Bundle

Layer2:
Mtp2ProfileChina
Mtp2ProfileItu
Mtp2TpChina
(on signalling DS0Bundle)
Mtp2TpItu (on signalling DS0Bundle)

Layer3:

Mtp3bSpItu

Mtp3bSpChina
(OWN SP China ,same with broad band )
Mtp3bSrs
(MTP3b Signalling Route Set to other NODE,SP)
Mtp3bSls
(SS7 signalling link set,LS)
Mtp3bSr (MTP3b Signalling Route,DEST)
Mtp3bSlItu
(the termination of the signalling link,SLC)
Mtp3bSlChina
(the termination of the signalling link,SLC)

(OWN SP ITU ,same with broad band)

10

MGW Configuration R4
35_..._Sigtran_Signalling_LOC

Defined IP Access Host GPB

Defined SCTP(SCTP end point)

Defines signalling over IP

IpAccessHostGpb (Ip Access Host used for signalling, executes on a GPB board )
IpInterface

(IP address definition)

SCTP (SCTP is designed to transport signaling messages over IP networks)

Defined M3u Association

This Exist common Managed Object for MTP Layer 3(MTP3/MTP3b/M3UA):


Mtp3bSpItu
(OWN SP ITU ,same with broad band)
Mtp3bSpChina
(OWN SP China ,same with broad band )
Mtp3bSrs (MTP3b Signalling point to other NODE,SP)
Mtp3bAp (remote Access point code)
M3uAssociation
Mtp3bSr (MTP3b Signalling Route ,DEST)

11

MGW Configuration R4
File Name

Description

38_.._AAL2paths_LOC
39_.._AAL2_Signalling_LOC
40_.._TdmGrp_Creation_LOC

Defines the AAL2 paths


Defines the AAL2 signalling links
Defines the TDM termination groups on
ET-MC1 and ET-C41 boards
41_.._GCP_Profiles_LOCDefines the GCP profile
42_1_VMGw_LOC
Defines the Virtual MGWs
43_Interactive_Messages.LOC
Defines the interactive messages
44_Tones_ITU_R4_LOC
Defines the tones for the market

12

MGW Configuration R4
Interactive Messaging Messages, Structures and
Files

A message is a spoken word or phrase, which can be played to a user. A message file is
a stand alone file which provides data for the playing of a message. Message files are
data files for basic messages (audio files) and configuration and algorithm files for
variable messages.
The file names and the file paths of the associated message files are specified at
message creation. The message files themselves are downloaded to the node
separately by using FTP.
Basic Message - Each basic message has one associated message file, that is the data
file containing the audio data.
Variable message The contents of a Variable Message depend on input data from the
IM system like date, time or phone number. This is defined in the associated
configuration and algorithm files. There is a configuration and algorithm file associated
to each variable message.
Composite message - A message composition consists of a sequence of messages,
which can be basic messages, variable messages or other message compositions.
Same message elements, like basic messages, can be used in several message
compositions, or several times in one message composition.

13

MGW Configuration R4
Interactive Messaging Messages, Structures and
Files

Configuration files (.map) in the package directory


For M-MGw R3 and R4.0: /c/im_algorithms/algconfigfiles/
For M-MGw R4.1: /c/im_variable_messages/algconfigfiles/
Algorithm files (.logic) in the package directory
For M-MGw R3 and R4.0: /c/im_algorithms/algsourcefiles/
For M-MGw R4.1: /c/im_variable_messages/algsourcefiles/

14

MGW Configuration R4
Interactive Messaging Messages, Structures and
Files

For M-MGw R3 and R4.0:

For M-MGw GMPv2.x


/p001000/phrases/ and /p001100/phrases/
For M-MGw GMPv3.0
/p001200/phrases/ and /p001300/phrases/

For M-MGw R4.1:

For M-MGw GMPv2.x


/p001000/im_basic_messages/phrases/ and /p001100/im_basic_messages/phrases/
For M-MGw GMPv3.0
/p001200/im_basic_messages/phrases/ and /p001300/im_basic_messages/phrases/

15

MGW Configuration R4
Interactive Message Streamer

The IM Streamer is responsible for streaming the message towards the IM players
(devices). There can be a master Streamer and a backup IM Streamer to provide
redundant speech store. The basic messages are thus loaded on both IM Streamers
and in case of failure of one of the IM Streamers the other one takes over. The IM
Streamer runs on a GPB. Note that when an IM Streamer GPB is replaced, also the
message files must be downloaded to the new GPB.

An IM Streamer must be created before the first basic message is created. The IM
Streamer can then be associated to all basic messages, when they are created.

For M-MGw GMPv2.x, GPB 001000 is the active ImStreamer and 001100 is the standby.
For M-MGw GMPv3.0, GPB 001300 is the active ImStreamer and 001200 is the
standby.

16

17