Basic of TMSC Networking

TMSC Networking

The MSOFTX3000 supports various protocols such as the H.248, ISUP, and BICC. When deployed with UMG8900, it provides TDM trunks or IP bearer channels of large capacity. It can function as the tandem mobile switching center (TMSC) in the hierarchical network.

TMSC Networking

The networking as shown is suitable for the GSM and 3GPP R99 hierarchical network structure, in which, the call signaling and bearer connection are connected through the TMSC hierarchically. The MSOFTX3000 realizes the call connection and route selection functions in the PLMN. It also controls the bearer terminal (IP) at the core network side in the UMG8900.

In the 3GPP R4 all-IP network, the MSOFTX3000 realizes the end-to-end bearer connection between the originating end and the terminating end through the BICC signaling. That is, the call signaling messages are transferred hierarchically through the TMSC, but the bearer does not require hierarchical processing. In this case, the media gateway (MGW, such as UMG8900) is not required in the networking depicted.

Read more...

Basic of GMSC Networking

GMSC Networking

The MSOFTX3000 supports various protocols such as the H.248, MAP, CAP, ISUP, and TUP. It provides abundant functions, such as:

• Black and white list
• Call authentication
• Call intercept
• Mass storage of CDRs

When deployed with UMG8900, the MSOFTX3000 can function as the GMSC in the network.

GMSC Networking

MSC: Mobile Switching Center

VLR: Visitor Location Register

BC: Billing Center

HLR: Home Location Register

SCP: Service Control Point

PSTN: Public Switched Telephone Network

PLMN: Public Land Mobile Network

The MSOFTX3000 terminates the signaling (such as the BICC) on the Nc interface with the other MSCs, and the call control ISUP/TUP signaling with the traditional external network (PSTN/PLMN). It realizes the route search for the called mobile subscriber and the number change between the mobile network and fixed network. Through the Mc interface, the MSOFTX3000 controls the bearer terminal (IP) at the core network side in the UMG8900 and the bearer terminal (TDM trunk) at the traditional fixed network side. In the GMSC networking, the MSOFTX3000provides the following interfaces:

• MSOFTX3000 <-> UMG8900: Mc interface. It is the standard interface of the control layer and bearer layer in the core network. It adopts the extended H.248 protocol defined by the ITU-T. Through the Mc interface, the MSOFTX3000 controls the bearer resources at the trunk side. The interface is an IP-based interface added in the R4 stage.
• MSOFTX3000 <-> MSC/MSC server: The MSOFTX3000 adopts the ISUP/BICC protocol for interworking with the MSC. When theMSOFTX3000 interworks with the MSC server, the interface is called the Nc interface. The Nc interface is the inter-office signaling interface in the control layer of the CS domain. It is an IP-based or TDM-based interface that adopts the ISUP or BICC protocol. It is added in the R4 stage.
• MSOFTX3000 <-> PSTN/PLMN: It adopts the TUP or ISUP protocol. It sends and receives the call control messages between the mobile network of the local CS domain and the PSTN/PLMN. It is a TDM-based (MTP3) interface directly inherited from the R99 stage.
• MSOFTX3000 <-> HLR: C/D interface. It adopts the MAP protocol, and is used to obtain the routing information for the called mobile subscriber from the PSTN/PLMN. It is a TDM-based or IP-based interface directly inherited from the R99 stage.
• MSOFTX3000 <-> SCP: The interface adopts the CAP protocol, and provides the following functions:
  Realizing the standard connection between the SSP and SCP in the CS domain integrated in the MSOFTX3000
  Reporting the T-BCSM call state event, and executing commands of the SCP
  Thus, in the R4 stage, the intelligent services in the R99 and GSM stage can be realized in transparent mode. The interface is a TDM-based or IP-based interface directly inherited from the R99 stage.
• MSOFTX3000<->BC: The interface adopts the FTP/FTAM protocol and enables the BC to automatically fetch the CDRs from the iGWB of theMSOFTX3000.
• MSOFTX3000<->M2000: The interface adopts the MML protocol and supports the MSOFTX3000 to access the iManager M2000network management system.

Read more...

Basic of MSC Networking

MSC Networking

The MSOFTX3000 supports various protocols, such as the H.248, BSSAP, RANAP, MAP, CAP, ISUP, TUP, and BSSAP+. It can work as the mobile switching center (MSC) server and the VLR in the network. When deployed with UMG8900 and the Shared InterWorking Function (SIWF), theMSOFTX3000 supports the BSS, UTRAN and SBC access and can function as the 2G VMSC, 3G VMSC, or 2G/3G integrated VMSC in the network.

Typical MSC networking

BSS: GSM Base Station Subsystem

UTRAN: UMTS Terrestrial Radio Access Network

SBC: Session Border Controller

GMSC: Gateway Mobile Switching Center

BC: Billing Center

HLR: Home Location Register

HSS: Home Subscriber Server

SMC: Short Message Center

GMLC: Gateway Mobile Location Center

SCP: Service Control Point

SGSN: Serving GPRS Support Node

PSTN: Public Switched Telephone Network

PLMN: Public Land Mobile Network

The MSOFTX3000 terminates the mobile subscriber/network signaling defined by the R99 24.008 and R98 04.08 specifications. It converts the signaling to the inter-office signaling transferred on the Nc interface. In addition, the MSOFTX3000 stores the subscription data of mobile subscribers and the related CAMEL data in its embedded VLR. The GMSC realizes the interworking between the MSOFTX3000 and the PSTN/PLMN. Through the Mc interface, the MSOFTX3000 controls the bearer terminal and media stream at the access network and backbone network side in the UMG8900. The interface, protocol and physical interface modes between the MSOFTX3000 and other network elements are as follows:

• MSOFTX3000 <-> UMG8900: Mc interface. It is the standard interface of the control layer and bearer layer in the core network. It adopts the extended H.248 protocol defined by the ITU-T. Through the Mc interface, the MSOFTX3000 controls the bearer resources at the radio access side and trunk side. The interface is an IP-based interface added in the R4 stage.
• MSOFTX3000 <-> BSC: A interface. It is the standard interface in the control layer between the core network and the BSS radio access network, based on the GSM. It adopts the BSSAP protocol, and realizes the termination of the controlling signaling messages for the service access in the circuit switched (CS) domain for the 2G mobile subscribers. The A interface provides the following functions:
• Mobility management
• Call control
• Circuit allocation
• Circuit reset
• Handover
• Short message processing
• It is a TDM-based interface that adopts the BSSAP protocol for the GSM MSC. It can also be connected through the UMG8900 with the SIGTRAN function. In this case, it adopts the M2UA protocol.
• MSOFTX3000 <-> RNC: Iu interface. It is the standard interface in the control layer between the core network and the UTRAN based on the WCDMA. It adopts the RANAP protocol, and realizes termination of the controlling signaling messages for the service access in the CS domain for the 3G mobile subscribers. The Iu interface provides the following functions:
• Mobility management
• Call control
• RAB allocation
• Reset and overload control
• RNC re-allocation
• Short message processing
• This interface inherits the functions in the R99 stage. It can be an IP-based (M3UA) interface. When a direct interface does not exist between the MSOFTX3000 and the RNC, the Iu interface can be connected through the UMG8900.
• MSOFTX3000<->SBC: The interface adopts the SIP protocol. The VoBB subscribers interact with the MSOFTX3000 through the SBC. The SBC processes the service messages of the VoBB subscribers, such as the location update message, and forwards the subscriber messages.
• MSOFTX3000 <-> GMSC/GMSC server: The MSOFTX3000 adopts the ISUP/TUP protocol for interworking with the GMSC. When theMSOFTX3000 interworks with the GMSC server, the interface is called the Nc interface. The Nc interface is the inter-office signaling interface in the control layer of the CS domain. It is an IP-based or TDM-based interface that adopts the ISUP/TUP or BICC protocol. It is added in the R4 stage.
• MSOFTX3000 <-> MSC: E/G interface. It is adopted only between the neighboring MSCs (not shown in the figure). It is a TDM-based or IP-based interface that adopts the MAP protocol, used for inter-office handover and location update.
• MSOFTX3000 <-> HLR: C/D interface. It adopts the MAP protocol; is used for the location update of network level in the CS domain, and the management of routing data and subscription data. It is a TDM-based or IP-based interface directly inherited from the R99 stage.
• MSOFTX3000 <-> HSS: Sh/Cx interface. It adopts the Diameter protocol. The MSOFTX3000 communicates the VoBB subscription data with the HSS through the Sh interface and communicates the VoBB authentication data with the HSS through the Cx interface.
• MSOFTX3000 <-> SCP: The interface adopts the CAP protocol. It provides the following functions:
• Realizing the standard connection between the SSP and SCP in the CS domain integrated in the MSOFTX3000
• Reporting the O/T-BCSM call state event, and executing the commands from the SCP
• Thus, in the R4 stage, the intelligent services in the R99 and GSM stage can be realized in the transparent subscriber mode. The interface is a TDM-based or IP-based interface directly inherited from the R99 stage.
• MSOFTX3000<->SMC: E interface. It adopts the MAP protocol, and transfers the mobile originated and mobile terminated short messages between the SMC and the MSOFTX3000.
• MSOFTX3000<->GMLC: Lg interface. It adopts the MAP protocol. The Lg interface between the MSOFTX3000 and the GMLC supports the location application outside the PLMN to exchange the subscriber authentication data required by the location service and the data (such as the IMSI) required by the network resource allocation with the MSC, through the GMLC, and locate the QoS.
• MSOFTX3000<->SGSN: Gs interface. It adopts the BSSAP+ protocol. The Gs interface between the MSOFTX3000 and the SGSN integrates certain functions of the packet switched (PS) domain and the CS domain (such as the united location update) to save the wireless resources.
• MSOFTX3000<->BC: The interface adopts the FTP/FTAM protocol and enables the BC to automatically fetch the CDRs from the iGWB of theMSOFTX3000.
• MSOFTX3000<->M2000: The interface adopts the MML protocol and supports the MSOFTX3000 to access the iManager M2000network management system.

Read more...

MSC Networking Evolution

Networking Evolution

The MSOFTX3000 supports the application of the 3GPP R4 CS CN and is compatible with the GSM and 3GPP R99 networking. It enables the R4 networking to evolve smoothly to the 3GPP R5/R6.

Figure 1 Evolution strategy of mobile core network

The previous sections describe the applications of the MSOFTX3000 in the GSM, 3GPP R99, and 3GPP R4. The following paragraphs describe the evolution solution of theMSOFTX3000 towards the IP multimedia subsystem (IMS) of 3GPP R5/R6.

Figure 2 Solution of R5

In the 3GPP R5 solution, the IMS for long is networked with the CS CN of 3GPP R4 as a service control network built on top of the PS domain. The two networks can supplement each other. It also converges mobile networks with fixed networks.

Due to continuous improvement in real-time IP service QoS mechanism of the PS air interface, increasing enhancement to the IP processing capability of wireless terminals, and mature end-to-end session-based QoS mechanism of the IMS bearer network, the IMS will gradually replace the CS R4 in the 3G access domain. The MSOFTX3000 can be expanded smoothly into the equipment with the MGCF, and the UMG8900 can be upgraded to the IM MGW. This ensures investment protection.

Read more...

Functions of the elements in the WCDMA network

 Functions of the elements in the WCDMA network

Element	Function
MSC	The MSC is the softswitch center in a WCDMA network. It incorporates the VLR database. Its functions include: Call control Access control of MGW Resource allocation Signaling processing Routing Authorization Charging The MSC is used to provide basic services,  mobility management, and multimedia services for subscribers.
MGW	The MGW incorporates the MRFP to convert the format of media streams,  play announcement, and provide conference resources and other media resources. UMG8900 incorporates SG functions and can realize signaling  interworking between the IP bear and the SS7 signaling network.
HLR	The HLR is a database for mobile subscriber management. It stores the following information: Subscription information Subscriber states MS location information MDN IMSI (MIN)
GGSN	The interface between the GPRS (General Packet Radio Service) network and external IP networks. The location register function in the GGSN stores subscription information and routing information (needed to tunnel packet data traffic destined for a GPRS MS to the SGSN where the MS is registered) for each subscriber for which the GGSN has at lest one PDP context active.
SGSN	The SGSN is an NE that provides the GPRS services. The SGSN forwards the input and output IP packets to the MSs in its service area. The SGSN provides the following functions: Routing and forwarding of subscriber packets Encryption and authentication Session management Mobility management Logical link management Charging information generation and output
BSS	In GSM, the BSS is composed of the BSC (Base Station Controller) and the BTS (Base Transceiver Station) associated with it. It is controlled by MSC, and used to give radio coverage to a determined geographical zone called a cell.
UTRAN	In UMTS, the UTRAN is composed of the NodeB and the RNC (Radio Network Controller) associated with it. It is controlled by MSC, and used to give radio coverage to a determined geographical zone called a cell.

Based on the evolution strategy of the CS domain of the mobile CN and the requirement for constructing an all IP networking, the MSC in the GSM and 3GPP R99 is divided into two parts: the MSC server and the MGW in the 3GPP R4 and later versions.

• MSC Server connects with the BSS and the UTRAN, and performs the following control functions of the CS domain:
  

  • Mobility management
  • Security management
  • Handover processing
  • Signaling processing
  • Call processing
  • Subscriber data management (function of the VLR)

  The MSOFTX3000 provided serves as an MSC server.
• MGW is the transmission endpoint of the PSTN or the PLMN that is connected to the MSC server. It performs the following functions:
  

  • Media transformation
  • Bearer control
  • Coding/Decoding of digital signals
  • Echo cancellation
  • Conference bridging

  The UMG8900 provided serves as an MGW

Read more...

MSC Networking Structure

Networking Structure

By separating the bearer from the control, a networking model, with the softswitch technology as the core, can use bearer networks such as the IP and TDM. This is a key feature of the softswitch technology. At present, most carriers choose the softswitch technology to build mobile core networks (CNs). By using the distributed networking mode and IP bearers, mobile softswitches provide carriers with the following benefits:

• Reducing operation costs by improving the efficiency of network transmission
• Protecting the carrier investment by providing a smooth evolution from one model to another as the subscriber base and traffic increases

The mobile softswitch solution provides a 2G and 3G convergence networking scheme that is easy to operate and maintain to address the networking requirements and network features of carriers. The solution supports the networking schemes of the GSM, 3GPP R99, 3GPP R4, and 3GPP R5. Typical networking model of the mobile softswitch solution for 3GPP R4.

Mobile softswitch solution

BSS: Base Station Subsystem

UTRAN: UMTS Terrestrial Radio Access Networkr

SBC: Session Border Controlle

MSC Server: Mobile Switching Center Server

CN: Core Network

MGW: Media Gateway

CS: Circuit Switched domain

PS: Packet Switched domain

HLR: Home Location Register

IMS: IP Multimedia Subsystem

SGSN: Serving GPRS Support Node

GGSN: Gateway GPRS Support Node

HSS: Home Subscriber Server

PSTN: Public Switched Telephone Network  

Read more...

Structure of the scheduling center

 Structure of the scheduling center

• MO process
  In the MO process, after a mobile subscriber submits an SM to the SMCAPP, the BillCreater generates an MO bill, and the SMCAPP determines whether SMs to be delivered to the called party are stored in the FDB. If yes, the SMCAPP saves the SM to the FDB. Otherwise, the SMCAPP attempts to deliver the SM.
• MT process
  In the MT process, the SMCAPP attempts to deliver an SM to a mobile subscriber, and the BillCreater generates an MT bill. If the SM fails to be delivered and is pending redelivery, or is successfully delivered but requires a status report, the SMCAPP saves the SM to the FDB. If the SM is deleted after the final delivery attempt fails, or is successfully delivered but requires no status report, the BillCreater generates a charging bill and history bill, and the DBDaemon saves the SM to the history database.

Read more...