SGSN

GSM

Figure 3-1 Protocol interfaces provided by the MSOFTX3000 in a mobile network

BSC: Base Station Controller BC: Billing Center SG: Signaling Gateway MGW: Media Gateway

GMLC: Gateway Mobile Location Center SCP: Service Control Point SGSN: Serving GPRS Support Node PLMN: Public Land Mobile Network

HLR: Home Location Register SMC: Short Message Center RNC: Radio Network Controller

Table 3-5 Interfaces and protocols supported by the MSOFTX3000 in a mobile network

Connected Entities
MSC ServerMGW
MSC ServerRNC MSC ServerBSC (GSM) MSC ServerVLR MSC ServerHLR VLRHLR MSC ServerMSC Server MSCMSC (GSM) MSC ServerSMC VLRVLR MSC ServerGMLC SSPSCP GMSC ServerPSTN GMSC ServerPLMN MSC ServerSGSN MSC ServerNMS MSC ServerBC

Interface
Mc
lu-CS A B C D Nc E E G Lg Gs -

Protocol
H.248
RANAP BSSAP Internal protocol MAP MAP MAP, TUP/ISUP/BICC MAP, TUP/ISUP/BICC MAP MAP MAP CAP TUP/ISUP BSSAP+ MML FTP/FTAM

Figure 5-7 H.248 stack structure (H.248 over M3UA)

Figure 5-8 H.248 stack structure (H.248 over SCTP)

Figure 6-1 MSC networking

BSS: GSM Base station subsystem

UTRAN: UMTS terrestrial radio access network

GMSC: Gateway mobile switching center

BC: Billing center

GMLC: Gateway mobile location center PSTN: Public switched

HLR: Home location register

SCP: Service control point PLMN: Public land mobile

SMC: Short message center

SGSN: Serving GPRS support node

Figure 3-1 MA networking with multiple MSC numbers and multiple SPs

 MS

2.2.1 Signaling Flow Figure 2-2 shows the signaling flow of the GMSC NPI scheme. Figure 2-2 Signaling flow of the GMSC NPI scheme

Line type

It indicates the office to which the A-interface circuit belongs.

Trunk group name

Equipment type CIC status Uninstall

It indicates the trunk group to which the A-interface circuit belongs.

It indicates that the A-interface equipment type is BSSAP. It indicates the identifier of the A-interface circuit. It indicates that A interface circuits are not configured or A interface data configuration is incomplete. For example, A interface circuits are configured but the circuits are in the unavailable state, or the circuits are configured on dualhoming non-activated nodes. It indicates that A interface circuits are normal or can be used for calls. It indicates A interface circuits are abnormal. The reason is a transmission problem due to abnormal physical connection of E1.

Idle Fault Oam block

It indicates that A interface circuits are abnormal. When you run BLK AIETKC to block the circuits, the circuits in the free state are transferred to the blocked state When circuits are in this state, you cannot make calls through there circuits except circuits specified by an operator. It indicates that circuits on the BSC side are blocked. When circuits are in this state, you cannot make calls through the circuits. It indicates that A interface circuits are normal. When circuits are occupied for calls, the circuits are in this state. It indicates that A interface circuits on the BSC side and local maintenance console are blocked. It indicates that A interface circuits are both in the oam block and the fault state. l This occurs when you block A interface circuits in the fault state on the maintenance console. l This occurs when you block circuits in the free state on the maintenance console but the circuits lead to E1 failure due to circuit gateway failure. It indicates that A interface circuits are both in the peer block and the fault state. It indicates that A interface circuits are both in the oam peer block and the fault state.

Remotely blocking Busy Oam peer block Oam block fault

Peer block fault Oam peer block fault

nce number) BSN

tor bit) BIB

 vlr

Figure 3-9 Protocol stack processed by the WCCU/WCSU

Figure 3-19 Protocol stack processed by the WSGU