Introduction to GSM/UMTS Networking

This describes the networking of the global system for mobile communications/universal mobile telecommunications system (GSM/UMTS) solutions based on the softswitch architecture.

Networking of the GSM Solution

Figure 1 shows Huawei's GSM network solution based on the softswitch architecture.

Figure 1 Huawei's GSM network solution based on the softswitch architecture

MSC Server

BTS

BTS Other Network

BSC

UMG8900

MGW UMG (UMG8900 8900

BTS BSC

BTS: base transceiver station

BSC: base station controller

MGW: media gateway

MSC Server: mobile switching center server GSM: global system for mobile communications

WCDMA: wideband CDMA, namely, the UMTS PSTN: public switched telephone network

In the GSM network, the mobile switching center (MSC) in the core network can be classified into the VMSC, TMSC, and GMSC based on the network positions, and thus implementing network hierarchy. The UMG8900 can network with the MGC to serve as a VMSC, TMSC, or GMSC in the GSM network. The UMG8900 is based on the standard softswitch architecture. Thus, one UMG8900 can network with one MGC. At the same time, multiple UMG8900s can accept the management and control of one MGC to build a large local network. The UMG8900 and the MGC can be placed in one equipment room. They can also be placed in different equipment rooms and connect with each other through the IP bearer network. The UMG8900 is placed near the access network to reduce switching paths for service data of subscribers and improve service quality. The centralized network management system iManager M2000 of Huawei can manage and maintain all the network elements in the network in centralized mode.

Networking of the UMTS Solution

Figure 2 shows Huawei's R4 network solution.

Figure 2 Huawei's R4 network solution

RAN

CN

MSC Serv

NodeB

NodeB

RNC NodeB

MGW (UMG890

NodeB

RNC

SGSN

GGSN: gateway GPRS support HLR: home location register node MSC Server: mobile switching center server SGSN: serving GPRS support node CN: core network

MGW: media gateway

CS: circuit switched domain

PS: packet switched

PSTN: public switched telephone network RNC: radio network controller

UTRAN: UMTS terrestrial radio RAN: radio access network access network WCDMA: wideband CDMA, that is, the UMTS GSM: global system for mobile communications

The UMG8900 networks as an MGW in the circuit switched (CS) domain of the core network. The UMG8900 implements the bearer interworking on the service plane and provides service resources. Parent topic: Introduction Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

GSM/UMTS Network Evolution

This describes the global system for mobile communications (GSM)/universal mobile telecommunications system (UMTS) network evolution based on the orientation of the UMG8900.

Current Situation
The current GSM network adopts the traditional time division multiplexing (TDM) transmission technology. Network elements (NEs) connect with each other in the star topology, and NEs with different functions connect with each other in the hierarchical topology. The network topology is complex. In addition, because TDM transmission devices are relatively complex, the cost for network construction and maintenance is high. The development of the IP network makes it an inevitable choice for network evolution to provide integrated voice, data, and video services based on the IP packet technology. The packet transmission technology will be introduced gradually during the evolution from the GSM network to the UMTS network. The final aim is the all-IP network. The existing GSM network needs to introduce the IP-based packet transmission technology during evolution processes such as capacity expansion, upgrade, and device replacement. On one hand, it meets the trend of network evolution. On the other hand, because the IP network technology is simple and universal, it can effectively reduce the cost for network construction and operation. The UMG8900 is designed based on the softswitch separated architecture. The UMG8900 networks with the media gateway controller (MGC) of Huawei to completely support various narrowband voice and data services of the existing GSM network. In addition, the IP packet transmission technology is introduced to achieve smooth evolution from TDM to IP.

Network Evolution
The evolution process of the GSM network is GSM general packet radio service system (GPRS) R99 R4 R5 R6, and finally to an all-IP packet network where the core networks of mobile and fixed networks are integrated to achieve integrated service access.

Table 1 lists the typical characteristics at each phase. Table 1 GSM network evolution Phase in the GSM Characteristics The air interfaces adopt the frequency division multiple access (FDMA) and the time division multiple access (TDMA) modes. All the transport networks adopt the TDM mode and comply with GSM series of specifications. The core network adopts the hierarchical architecture. The network connections are complex, and the end-to-end delay is low. Two physical entities, namely, gateway GPRS support node (GGSN) and serving GPRS support node (SGSN), are overlaid on the existing GSM network to meet requirements of high-speed packet services. The air interfaces in the access network do not change. Packet service processing interfaces are added to base station controllers (BSCs). The air interfaces adopt the CDMA mode. The transmission between access networks and between access networks and the core network is based on the asynchronous transfer mode (ATM). The architecture of the core network has no change. The R99 network complies with relevant 3rd Generation Partnership Project (3GPP) R99 standards. The core network is divided into the circuit switched (CS) domain and the packet switched (PS) domain. The CS domain provides voice and narrowband data services. The PS domain provides high-speed packet services. The CS domain is based on the TDM mode, the same as that in the GSM network. The access network of R4 is the same as that of R99. The softswitch architecture is introduced to the CS domain of the core network. The original mobile switching center (MSC) is divided into two entities, MSC Server and media gateway (MGW). The core network supports TDM, ATM, and IP connections. The network evolves toward a flattened architecture, and the networking is more flexible. The PS domain of the core network of R4 is the same as that of R99. Based on R4, the IP multimedia subsystem (IMS) domain is introduced. The R5 network achieves the integrated access of voice, data, and video services and provides IP multimedia services. The R4 CS domain is retained to provide voice and narrowband data services. The IMS domain is enhanced to achieve the interworking with different networks and the interworking between different IMS domains.

GPRS

R99

R4

R5

R6

Figure 1 shows the applications of the UMG8900 at different network evolution phases.

Figure 1 Applications of the UMG8900 during the GSM network evolution

GSM

R99

MGC

MGC

UMG8900

UMG8900

VMSC/TMSC/

VMSC/TMSC/

The UMG8900 is based on the standard separated architecture. It can work with the softswitch to implement core switching applications at different network phases. In actual networking applications of different networks, the UMG8900 can support smooth network expansion and evolution through addition of related hardware boards and software upgrade. Parent topic: Introduction Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

GSM Networking Application

This describes the networking application of the UMG8900 in a global system for mobile communications (GSM) network. To realize smooth network upgrade without affecting the development of existing networks, the UMG8900 networks with the media gateway controller (MGC) to provide mobile switching center (MSC) functions in a GSM network. Figure 1 shows the GSM networking application. Figure 1 GSM networking application
TDM TDM TDM

MGC BSC BTS Mc

MGC

Mc

LE

BTS

UMG8900

UMG8900

PSTN

MSC

GMSC

When serving as an MSC in the GSM network, the UMG8900 and the MGC act as one device. They connect with each other through the internal interface or the standard Mc interface. Neither the UMG8900 nor the MGC can provide complete GSM service interfaces. In a GSM network, the MSCs in the core network, the MSC in the core network and the BSC in the access network, and the core network and the public switched telephone network (PSTN) all connect with each other through time division multiplexing (TDM). The UMG8900 accesses voice service streams from the access network to the core network through TDM. For voice service streams between devices in the core network, the existing TDM network or the voice over IP (VoIP) function of the UMG8900 can be used to realize the VoIP connection in the core network. The Base Station Subsystem Application Part (BSSAP) call control signaling from the access network can be sent to the MGC directly through the independent signaling trunks between the MGC and the base station controller (BSC). The signaling can also be transferred to the MGC through the signaling gateway (SG) embedded in the UMG8900 or the TDM semi-permanent connections of the UMG8900. The signaling between MSCs in the core network is exchanged based on ISDN User Part (ISUP) or Telephone User Part (TUP). The signaling can be transmitted over TDM links between MGCs or be transferred through TDM connections between UMG8900s by using the embedded SG and the semi-permanent connection of the UMG8900.

When the UMG8900 and the MGC work together as a GSM gateway exchange, the UMG8900 receives voice service streams from an external network such as the PSTN through the TDM interfaces. The signaling is sent to the MGC through an independent SG or through direct connections to the MGC. The signaling can also be transferred to the MGC through the SG embedded in the UMG8900. The UMG8900 supports complete SG functions. The UMG8900 can transfer the signaling of the access network or Signaling System No.7 (SS7) of the PSTN based on MTP2 User Adaptation Layer (M2UA)/MTP3 User Adaptation Layer (M3UA). Parent topic: Basic Networking Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

R99 Networking Application

This describes the networking application of the UMG8900 in an R99 network. After global system for mobile communications (GSM) networks evolve to R99 networks, the connection modes and service types in an access network change a lot, but the combination of the UMG8900 and the media gateway controller (MGC) is still used in circuit switched (CS) domains in core networks. The UMG8900 must work jointly with the media gateway controller (MGC) to serve as the mobile switching center (MSC). Figure 1 shows the networking application. Figure 1 R99 networking application
ATM TDM TDM

MGC RNC Mc

MGC

NodeB

Mc

LE

NodeB

UMG8900

UMG8900

PSTN

MSC

GMSC

In an R99 network, asynchronous transfer mode (ATM) connections function between CS domains in the access network and the core network. The Iu CS interface works. On the user plane (UP), voice and narrowband data is transmitted based on Iu UP. On the control plane (CP), call control messages are transmitted based on Iu CP. Time division multiplexing (TDM) connections exist between MSCs in the core network, and between the core network and the public switched telephone network (PSTN). The UMG8900 and the MGC function as one network entity. They can act as an MSC in the core network to achieve service switching and connection. The UMG8900 can communicate with the MGC through either internal interfaces or standard H.248 messages. In this networking mode, the UMG8900 accesses and processes service streams from the access network through Iu CS interfaces. The call control signaling from the access network can be directly transmitted to the MGC or be transparently transmitted to the MGC through the embedded signaling gateway (SG) function of the UMG8900 after signaling adaptation. Between MSCs in the core network or between the core network gateway MSC (GMSC) and the PSTN, voice services are carried by the UMG8900. Signaling is transferred by the embedded SG or the semi-permanent connection of the UMG8900.

The UMG8900 performs adaptation on the signaling of the access network based on Message Transfer Part layer 3 broadband (MTP3B), or performs IP packet adaptation based on MTP3 User Adaptation Layer (M3UA) and sends the signaling to the MGC for processing. The UMG8900 performs adaptation on the TDM narrowband signaling based on MTP2 User Adaptation Layer (M2UA) or M3UA, for signaling connection between MSCs in the core network or between the core network and the PSTN. The UMG8900 is in the Bearer Independent Call Control Protocol (BICC) architecture and supports TDM/IP/ATM bearers. Thus, the UMG8900 can help R99 networks to smoothly evolve into R4/R5/R6 networks and save investment of carriers. Parent topic: Basic Networking Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

R4 Networking Application
This describes the networking application of the UMG8900 in an R4 network. An R4 network is designed in the Bearer Independent Call Control Protocol (BICC) structure so that new services can be easily applied. The core network adopts packet bearer mode, which occupies less bandwidth. Figure 1 shows the R4 networking application.

Figure 1 R4 networking application

ATM

MGC RNC Mc

NodeB

N NodeB
UMG8900

MSC
Compared with R99 networks, the UMG8900 in the R4 access network is in the same application and the R4 core network adopts packet connections. The media gateway (MGW) in the R4 core network provides standard Mc, Iu CS, and Nb interfaces to connect with mobile switching center (MSC) Servers and other MGWs supporting 3rd Generation Partnership Project (3GPP) standards.

The UMG8900, an MGW in the R4 core network, provides the functions of service stream bearer and bearer control in circuit switched (CS) domains. The UMG8900 supports Iu CS, Mc, and Nb interfaces. The Iu CS interface applies to transmission of service streams between the radio network controller (RNC) and the UMG8900, with ATM bearer and Iu UP adopted. The Mc interface is between the UMG8900 and the media gateway controller (MGC). The MGC controls and manages the UMG8900 through H.248 and the Mc interface, with IP bearer adopted. The Nb interface is the transmission channel for bearer setup and service streams between adjacent UMG8900s, with IP/TDM bearer adopted. When IP bearer is in use, the application protocols are Real Time Protocol (RTP)/Real Time Control Protocol (RTCP), Nb UP, and IP Bear Control Protocol (IPBCP). MGCs connect with each other through Nc interfaces to complete call routing, control service interworking between devices, and provide channels for IPBCP negotiation. After the Iu interface evolves from ATM to IP, the UMG8900 supports IP-based Iu interface. The IP packet transmission technology is adopted in the radio access network (RAN) and the core network (CN), to build an all-IP network where the RAN and the CN may share the IP bearer network. The UMG8900 also provides the gateway MSC (GMSC) bearer networking function and acts as the gateway exchange in the 3G core network to connect with the public switched telephone network (PSTN). The interface between the UMG8900 and the PSTN switch is over TDM bearer. The embedded signaling gateway (SG) of the UMG8900 or an independent SG can implement signaling connection with the PSTN. Parent topic: Basic Networking Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

IM-MGW Networking Application

This describes the networking application where the UMG8900 serves as an IMS-media gateway (IM-MGW). Located on the edge access layer, the IM-MGW is the universal media gateway applied in the IP multimedia subsystem (IMS) domain. Through upgrade based on the 3rd Generation Partnership Project (3GPP) R4 MGW or next generation network (NGN) trunk gateway (TG)/access gateway (AG)/signaling gateway (SG), Huawei UMG8900 can support the IM-MGW functions. The IMMGW converts the traditional switching mode between the IMS domain and the public switched telephony network (PSTN) or the CS domain to the IP mode, and achieves the necessary codec conversion. In this way, the IP-based communication can be implemented in the whole network. As an IM-MGW, the UMG8900 works together with the media gateway control function (MGCF) in the IMS domain to interwork with the existing PSTN and public land mobile network (PLMN). Thus, the backward compatibility of networks can be ensured. Figure 1 shows the position of the IM-MGW in the IMS domain, and interfaces and protocols between network elements (NEs).

Figure 1 Typical networking application of the IM-MGW

BGCF Mj BICC/ISUP over SCTP/IP CSCF Mg Mn Mb (Note 3) User Plane Control Plane IM-MGW MGCF SGW BICC over SCTP/ IP CS channels e.g.PCM

BICC/ISUP over MTP

CS network

BGCF: breakout gateway control function MGCF: media gateway control function Note 3: other MGWs CS network: circuit switched network

CSCF: call session control function SGW: signaling gateway IM-MGW: IMS-media gateway

As the external interface NE in the IMS domain, the IM-MGW achieves broadband/narrowband bearer interworking on the user plane between the IMS, PSTN, and CS domain and necessary codec conversion. It features the following: Setup, release, and mapping of the time division multiplexing (TDM) trunk circuits and the Real-time Transport Protocol (RTP)/Internet Protocol (IP) connections based on the H.248 resource control commands from the MGCF Control of the special resource processing on the user plane, including transparent transmission of H.264 and MPEG4 video codes, audio codec conversion and echo cancellation (EC) control, based on the H.248 resource control commands from the MGCF Operation, administration, and maintenance (OAM) functions such as configuration management, fault management, alarm management, performance measurement, and security management Using the IM-MGW to implement interworking between the IMS domain and the universal mobile telecommunications system (UMTS) CS/PSTN domain brings the following advantages: Reduce the cost on network construction because some IM-MGWs can be built on the same platform with the CS-MGW Simplify network maintenance and management Ensure that subscribers can interwork with the existing CS/PSTN subscribers at the early stage of IMS network construction, and help carriers to hold and increase market shares Parent topic: Basic Networking Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

MGW Registration Flow

This describes the media gateway (MGW) registration flow.

MGW Registration Flow

When an MGW is in service for the first time or restarted, it must be registered with the related media gateway controller (MGC). Figure 1 shows the registration flow. Figure 1 MGW registration flow
MGW SVC_CHG_REQ MGC

SVC_CHG_REPLY

1. When an MGW is in service for the first time or restarted, it sends the ServiceChange message to the MGC to which it belongs to request registration. This message contains descriptors such as Method ("Restart", for example), ServiceChangeAddress (address message), and Reason. This message corresponds to the ROOT terminal, that is, the whole MGW. 2. The MGC authenticates the MGW and returns the ServiceChange_Reply message containing ServiceChangeAddress to accept the registration. If the MGC rejects the registration, for example, because the version is inconsistent or the MGW is not controlled by the MGC, the MGC sends the ServiceChange_Reply message containing Reason to the MGW to reject the registration. Parent topic: Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

MGW Deregistration Flow

This describes the media gateway (MGW) deregistration flow.

MGW Deregistration Flow

Before the MGW stops the service, it must be deregistered with the related media gateway controller (MGC). Figure 1 shows the deregistration flow. Figure 1 MGW deregistration flow
MGW SVC_CHG_REQ MGC

SVC_CHG_REPLY

1. When an MGW wants to stop services, it sends the ServiceChange message to the MGC to which it belongs to request deregistration. This message contains descriptors such as Method ("Forced", for example) and Reason (905{"Termination taken out of service"}, for example). This message corresponds to the ROOT terminal, that is, the whole MGW.

2. The MGC returns the ServiceChange_Reply message to accept the deregistration. Parent topic: Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

R4 Local Exchange networking

This describes the sample R4 local exchange networking. Figure 1 shows the R4 local exchange networking.

Figure 1 R4 local exchange networking

MGC RANAP (MO) RNC-A RANAP Iu UP term A MGW T1 (RAN in)

User plane

Parent topic: R4 Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Establishment Flow of the Bearer Plane on the Calling Side

This describes the establishment flow of the bearer plane on the calling side. Figure 1 shows the establishment flow of the bearer plane on the calling side. Figure 1 Establishment flow of the bearer plane on the calling side
RNC-A MGC MGW

(1) Initial UE (CM Service request)

(2) Auth and Secuirty procedure

(3) Setup

(Codec list , PLMN BC) Call Proceeding

(4) Callee analysis and routing

(5) MGW selection

( early )

(6) ADD.req($) (7) RAB-ASSIGMENT-REQ ( Rab,UP,BNC-id,Addr) ADD.rsp(C1,T1,BNC-id1,Addr)

(8) ERQ(Q.2630 for AAL2 with SUGR=BNC-id ) ECF(Q.2630 for AAL2 ) (9) IuUP-Init (RFCI,SDU size,IPTI,etc) IuUP-Init-Ack (10) Notify (Bearer established) RAB-ASSIGMENT-CMP

1. RNC-A sends the CM SERVICE REQUEST message to the media gateway controller (MGC). This message contains mobile identifications (including temporary mobile subscriber identifier (TMSI), international mobile subscriber identity (IMSI), and

international mobile equipment identity (IMEI)), classmark2, ciphering key sequence number (CKSN), connection management (CM) service type (including mobile originating call setup, emergency call setup, short message service, supplementary services, and location service). 2. The MGC may initiate authentication and ciphering, during which initiation of getting authentication set from the home location register (HLR)/authentication center (AUC) may be required. If the security management procedure is not required, turn to step 3. Security management includes authentication, encryption, temporary mobile station identity (TMSI) reallocation, and fetching identification. 3. Upon the receipt of the service acceptance message or the ciphering complete message, RNC-A sends the SETUP message to the MGC. After receiving the SETUP message, the MGC returns the CALL PROCEEDING message to the caller. 4. The MGC performs callee analysis and determines that the callee is a mobile subscriber. Then, the MGC gets the routing information of the callee from the HLR. 5. The MGC chooses an MGW based on the routing information.

6. The MGC sends the ADD command to the MGW to enable the MGW to set up a call. The MGW returns call C1, termination T1, BNC-id1, and Addr. 7. The MGC sends the RAB Assignment Req message to RNC-A, indicating BIEFAddress and BNC-ID of the MGW and instructing the RNC to start establishing the bearer channel. 8. 9. RNC-A and the MGW establish the signaling plane. RNC-A and the MGW establish the user plane.

10. The MGW sends the Notify message to notify the MGC that the bearer channel between RNC-A and the MGW is established. Parent topic: R4 Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Establishment Flow of the Bearer Plane on the Called Side

This describes the establishment flow of the bearer plane on the called side. Figure 1 shows the establishment flow of the bearer plane on the called side.

Figure 1 Establishment flow of the bearer plane on the called side

MGC

1. The media gateway controller (MGC) performs authentication, encryption, and temporary mobile station identity (TMSI) reallocation. In this procedure, the MGC must start getting the authentication set from the home location register (HLR)/authentication center (AUC). 2. The MGC sends the Setup message containing gsm bearer capability and bc speech to the called RNC-B. The called user equipment (UE) returns the CallConfirmed message containing call control cap and supported codecs(o). 3. The MGC sends the ADD command to the media gateway (MGW) to enable the MGW to add termination T2 in call C1. The MGW returns call C1, terminations T1 and T2, BNC-id2, and Addr. 4. The MGC sends the RAB Assignment Req message to RNC-B, indicating BIWFAddress and BNC-ID of the MGW and instructing the RNC to start establishing the bearer channel. 5. 6. RNC-B and the MGW establish the signaling plane. RNC-B and the MGW establish the user plane.

7. The MGW sends the Notify message to notify the MGC that the bearer channel between RNC-B and the MGW is established. Parent topic: R4 Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Call Setup Flow

This describes the call setup flow. Figure 1 shows the call setup flow. Figure 1 Call setup flow
RNC-A MGC (1)Alerting (2) MOD (RingTone to T1 ) MOD rsp (3) Connect (4) MOD (stopTone to T1 ,T1<->T2 ) MOD rsp (5) Connect Connect ack Connect ack RNC-B MGW

(6) Call in active

1. The media gateway controller (MGC) sends the Alerting message to RNC-B to enable RNC-B to instruct the handset to ring.

2. The MGC sends the MOD command to the MGW to enable the MGW to play the ring back tone to the handset on the RNC-A side. 3. The handset on the RNC-B side answers the call. RNC-B sends the Connect message to the MGC, indicating that the subscriber on the RNC-B side has answered the call. 4. The MGC sends the MOD command to the MGW to enable the MGW to stop playing the ring back tone to the handset on the RNC-A side. 5. The MGC sends the Connect message to RNC-A to connect RNC-A and RNC-B.

6. The call is set up. Parent topic: R4 Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Call Release Flow

This describes the call release flow. Figure 1 shows the call release flow. Figure 1 Call release flow
RNC-A MGC RNC-B MGW

Call in active

(1) Disconnect (2) Disconnect Release Release Release complete Release complete (3) Iu-Release-cmd (4) REL (Q.2630 for AAL2) RLC (Q.2630 for AAL2) Iu-Release-Complete (5) SUB.req(T1) SUB.rsp (6) Iu-Release-cmd (7) REL (Q.2630 for AAL2) RLC (Q.2630 for AAL2) Iu-Release-Complete (8) SUB.req(T2) SUB.rsp

1. The handset on the RNC-A side hangs up, and RNC-A sends the DISCONNECT message to the media gateway controller (MGC) to require release on initiative. 2. The MGC receives the release request from RNC-A and then sends the release command to RNC-B. 3. After the channel between NodeB and RNC-A is released, the MGC sends the IU RELEASE COMMAND message to RNC-A to start releasing the user plane between the media gateway (MGW) and RNC-A. 4. The MGC sends the REL(Q.2630 for AAL2) message to RNC-A to start releasing the signaling plane between the MGW and RNC-A. 5. The MGC sends the SUB command to the MGW to enable the MGW to delete termination T1, that is, the caller termination, from call C1. 6. After the channel between NodeB and RNC-B is released, the MGC sends the IU RELEASE COMMAND message to RNC-B to start releasing the user plane between the MGW and RNC-B. 7. The MGC sends the REL(Q.2630 for AAL2) message to RNC-B to start releasing the signaling plane between the MGW and RNC-B. 8. The MGC sends the SUB command to the MGW to enable the MGW to delete termination T2, that is, the callee termination, from call C1. Parent topic: R4 Call Flow Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Logical Fundamentals
This describes the logical fundamentals of the UMG8900. The logical architectures of SSM-256 frames and SSM-32 frames of the UMG8900 are different. Figure 1 shows the logical components of the SSM-256 frame.

Figure 1 Logical components of the SSM-256 frame

TDM pro mod GPS BITS 8k Hz

CLK

E1/

E32

Figure 2 shows the logical components of the SSM-32 frame.

Figure 2 Logical components of the SSM-32 frame

TDM m GPS BITS 8k Hz E1/ E32/ T32/S1L CLK

The UMG8900 accesses and processes IP/ATM/TDM bearer services, interacts with the media gateway controller (MGC), processes media resources, and adapts and transparently transmits signaling. The UMG8900 also provides auxiliary functions such as device management and maintenance, clock, and cascading. Based on the functions and the distributed modular architecture, the hardware system of the UMG8900 can be divided into the gateway control and management module, TDM processing module, service resource module, packet processing module, signaling adaptation module, and cascading module. Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Gateway Control and Management Module

This describes the functions and components of the gateway control and management module. The gateway control and management module provides the following functions: This module manages and maintains the UMG8900. The UMG8900 works in client/server mode. The LMT connects with the back administration module (BAM) of the UMG8900 to maintain and manage the UMG8900. Under the control of the media gateway controller (MGC), this module invokes bearer and service resources within the UMG8900, sets up service bearers, and converts service stream formats. The maintenance and management center of the UMG8900 can perform centralized management on the UMG8900 through the BAM embedded in the OMU or the OMB. Operation and maintenance messages are exchanged between frames through cascaded FE channels. The PPU/CMU provides the gateway control function. The OMU/MPU/TNC provides the management and maintenance function. The PPU and the CMU can work jointly to provide the gateway control function. You can flexibly configure this function through software. When the PPU and the CMU work jointly to provide the gateway control function, the PPU resolves and encapsulates the network layer and transport layer protocols, resolves the H.248 protocol stack, and sends the transaction messages to the specified CMU. The CMU invokes and manages resources within the UMG8900 based on the gateway control messages. The physical board of the PPU is the MPPB, the MCMF and the MCMB. The physical boards of the CMU are the MCMB and the MCMF. The physical boards of the OMU are the MOMU and the MOMB. The physical boards of the MPU are the MMPU and the MMPB. The MOMU/MMPU can be configured only in the SSM-256 frame. The MOMB can be configured only in the SSM-32 frame. NOTE: In the SSM-32 frame, the MMPB actually provides the packet switching function, and the MOMB and the MTNC provide the management and maintenance function. The MOMB/MMPB can be equipped with the SCMU subboard to improve the processing capability and implement the functions of the CMU/PPU. Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Packet Processing Module

This describes the functions and components of the packet processing module. The packet processing and interface module processes packet service bearers of the UMG8900 and provides hardware interfaces for packet services. The packet processing module consists of two parts. One is packet switching, and the other is packet processing and interface. The packet switching module switches packet services of the UMG8900. In the SSM-256 frame, the NET provides this function and the physical board of the NET is the MNET. In the SSM-32 frame, this function is embedded in the OMU/MPU in the gateway control and management module and the physical board of the OMU/MPU is the MOMB/MMPB. In the SSM-256 frame, the UG01MNET provides the 16 GE packet switching capability, and the UG02MNET provides the 24 GE packet switching capability. In the SSM-32 frame, the packet switching module provides the 12 GE packet switching capability. The packet processing and interface module processes packet service bearers of the UMG8900 and provides hardware interfaces for packet services. Packet service bearers provided by the UMG8900 are Internet Protocol (IP)/asynchronous transfer mode (ATM)/IP over E1 (IPoE1), corresponding to different hardware types of boards. The hardware of the IP packet processing and interface module mainly includes the HRB, E8T, E1G, P1H, and P4L. The corresponding physical boards are the MRPU, MHRU, MIOE, ME8T, MG1O, MP1H, MP4L, MHRD with the interface subboards, and MNET. The MIOE and the ME32 work jointly to provide the IP over E1 function. The hardware of the ATM packet processing and interface module mainly includes the ASU, A4L, EAC, and TAC. The corresponding physical boards are the MASU, MA4L, MEAC, and MTAC. The HRB accesses packet services through the back interface board and then resolves IP/IPoA packets. The jitter buffer caches voice packets. Then, under the control of the gateway control module, the jitter buffer forwards the packets to a specified board for processing. The packet processing module can forward H.248, Signaling Transport (SIGTRAN), and operation and maintenance center (OMC) packets at the same time. You can configure this function through software. The HRB provides external interfaces to send and receive these three types of packets. Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

TDM Processing Module

This describes the functions and components of the time division multiplexing (TDM) processing module. The TDM processing module consists of TDM interface, clock processing, and TDM switching. The TDM interface module provides TDM interfaces of the UMG8900 and supports extraction of line clocks as clock reference sources. The TDM interface module mainly includes the E32, T32, PIE, S2L, and S1L. The corresponding physical boards are the ME32, MESU, MT32, MTSU, MPIE, MS2L, MS1L, MS2E, and MS1E. The UG01S2L can be configured only in the SSM-256 frame. The UG02S2L can be configured in the SSM-256 frame. If the UG02S2L works with the UG02TNC, the UG02S2L can be configured in the SSM-32 frame. The S1L can be configured only in the SSM-32 frame. The clock processing module provides clock signals required by the UMG8900 and supports access of various clock reference sources. The CLK implements clock processing, and its physical board is the MCLK.

The UMG8900 supports two clock modes. One is to provide the clock through the CLK. The CLK can provide stratum-2A or stratum-3 clock signals. The other is to provide the clock through the TNU (MTNC). The TNU can provide only stratum-3 clock signals and can be configured only in the SSM-32 frame. The independent CLK board can provide 2 M/1.5M clock reference sources for the next level network devices. The TDM switching module mainly includes the TNU. In the SSM-256 frame, the corresponding physical boards are the MTNU, TCLU, and MTNB. In the SSM-32 frame, the corresponding physical board is the MTNC. Table 1 lists the four TDM switching cascading boards. Table 1 TDM switching cascading boards Board MTNB Frame SSM-256 Specification The MTNB provides 256 K TDM switching capability and offers 4 x 8 K TDM cascading channels between frames. If only the MTNB is used in multi-frame cascading, no restriction exists on frames. The MTNU provides 256 K TDM switching capability and offers 3 x 8 K TDM cascading channels between frames. In multi-frame cascading, the MTNU works with the TCLU. The MTNU is configured in the central switching frame, and the TCLU is configured in other frames. The TCLU provides 256 K TDM switching capability and offers 3 x 8 K TDM cascading channels between frames. In multi-frame cascading, the MTNU works with the TCLU. The MTNU is configured in the central switching frame, and the TCLU is configured in other frames. The UG01TNC provides 32 K TDM switching capability and offers 1 x 8 K/2 x 8 K TDM cascading channels between frames. The UG02TNC provides 96 K TDM switching capability and offers 1 x 8 K/2 x 8 K/4 x 8K TDM cascading channels between frames. In addition, the MTNC provides interfaces for FE cascading between frames.

MTNU

SSM-256

TCLU

SSM-256

MTNC

SSM-32

Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Service Resource Module

This describes the functions and components of the service resource module. The service resource module processes media stream formats and provides resources for service connection. It supports G.711/G.723/G.726/G.729/AMR/WB-AMR voice codecs, announcement playing, digit collecting, echo cancellation (EC), and audio mixing. The hardware of the service resource module mainly includes the VPU and the ECU. The ECU provides the EC function. The VPU provides the announcement playing, digit collecting, and

audio mixing functions. In addition, the VPU can provide all the functions of the ECU. The corresponding physical boards are the MVPB, MVPD, MTCB, MTCD, and MECU. The service resource board works in load-sharing mode and is composed of the mother board and the subboard. Based on different subboards configured, the number of subboards, and software loaded, the board can provide functions such as announcement playing, digit collecting, EC, audio mixing, and voice codec conversion. The MVPB and the MTCB can be configured only in the SSM-256 frame. The MVPD, and the MTCD can be in the SSM-256 frame and the SSM-32 frame. The MVPD is compatible with the subboard of the MVPB. The new subboards such as the VQE, VDD, and VDF can be configured. Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Signaling Adaptation Module

This describes the functions and components of the signaling adaptation module. The signaling adaptation module adapts the signaling of the access network and the public switched telephone network (PSTN) to the signaling of the IP packet network. This module works with the TDM processing module, packet processing module, and gateway control and management module to adapt and transfer signaling. The SPF implements the functions of the signaling adaptation module. The corresponding physical board is the MSPF. The TDM interface board accesses signaling on the TDM side and then transfers the signaling to the SPF through internal TDM switching. The interface between the signaling adaptation module and the media gateway controller (MGC) is the Signaling Transport (SIGTRAN) interface. In the case of single SSM-256 application, the MIR packet interface on the back NET is adopted. In the case of single SSM-32 application, the Mc interface in the main control frame is adopted. If the packet processing module is configured, the HRB provides the interface. In the case of SSM-256 multi-frame cascading or mixed cascading, the OMC interface on the NET in the central switching frame is used. In the cascading of multiple SSM-32 frames, the OMC interface on the TNC in the first service frame is used. Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Cascading Module
This describes the functions and components of the cascading module. The UMG8900 supports applications of different capacities through single-frame cascading and multi-frame cascading. The cascading module provides the cascading of packet, time division multiplexing (TDM), and control service streams in multi-frame cascading. The BLU and the FLU work with the packet processing module and the TDM processing module to perform the functions of the cascading module. The physical board of the BLU is the MBLU. The physical board of the FLU is the MFLU. The BLU and the FLU can be configured only in the SSM-256 frame. The FLU and the BLU provide 3 x 8 K TDM cascading and 4 x 8 K TDM cascading. For 4 x 8 K TDM cascading, the corresponding physical boards are the UG02FLU and the UG02BLU, and they must work with the TNB.

The SSM-32 frame also supports another cascading board, the NLU. Its physical board is the MNLU. The NLU is used for the GE cascading between SSM-32 frames, and between SSM-32 frames and SSM-256 frames. Parent topic: Logical Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Software Fundamentals
This describes the software fundamentals of the UMG8900. As a large-capacity universal media gateway, the UMG8900 supports the complete media gateway processing functions and the embedded signaling gateway (SG) functions. Figure 1 shows the software architecture of the UMG8900. Figure 1 Software architecture of the UMG8900

Host software BAM

The software of the UMG8900 consists of the host software and the LMT software. The host software achieves bearer related service processing, underlying support, and hardware management. The LMT software and the back administration module (BAM) of the host software are in the client/server mode. The LMT software completes routine maintenance and management on the host of the UMG8900. Parent topic: Software Architecture Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.