Mswitch R6.0 Overview E SZ v1.0

mSwitch
System Overview
Release 6.0
Doc. Code L3 H010 6000 03 100 01
Copyright 2006-2008 UTStarcom, Inc. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without prior, express and written permission from UTStarcom, Inc. UTStarcom, Inc. reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of UTStarcom, Inc. to provide notification of such revision or changes. UTStarcom, Inc. provides this documentation without warranty of any kind, implied or expressed, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. UTStarcom may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. UNITED STATES GOVERNMENT LEGENDS: If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following: United States Government Legend: All technical data and computer software is commercial in nature and developed solely at private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995) or as a commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in UTStarcom's standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this User Guide. UTStarcom, the UTStarcom logo, !-Volution, AccessGuard 500, AIRSTAR, AN-2000, AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell, Internode, Intranode, iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now, NGDLC, PAS, PAS Wireless, Seamless World, Softexchange, Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, Sonata WLL, Telos, Total Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are registered trademarks or trademarks of UTStarcom, Inc. and its subsidiaries. Other brand and product names may be registered trademarks or trademarks of their respective holders. Any rights not expressly granted herein are firmly reserved.
Contents
About This Guide ........................................................................................................1
Introduction ........................................................................................................................1 Audience............................................................................................................................2 Conventions.......................................................................................................................2 Notices...........................................................................................................................2 Text................................................................................................................................2 Figures and Screen Captures .......................................................................................3
Overview .............................................................................................................5
Typical Networking Architecture........................................................................................5 System Characteristics......................................................................................................8 System Features .............................................................................................................10 System-Level Features ...............................................................................................10 Carrier-Level Features ................................................................................................11 Subscriber-Level Features ..........................................................................................12 NGN Applications ............................................................................................................29 Basic C4/C5 Service ...................................................................................................29 Multiple Signaling Protocols ........................................................................................30 Routing and Digit Analysis ..........................................................................................31 Supplementary Services .............................................................................................31 IP Centrex/Host IP Centrex (applicable to UTSmart terminal)....................................32 Value-added Service and Intelligent Service ..............................................................34 UTSmart Softphone.....................................................................................................34 Fixed-Mobile Convergence .........................................................................................34 mBOSS........................................................................................................................35 Operation and Maintenance ........................................................................................37 Regulatory ...................................................................................................................38 System Redundancy and Reliability............................................................................39 New Features in mSwitch R5.4 .......................................................................................39 New Features in mSwitch R5.4.1 ....................................................................................39 New Features in mSwitch R5.5 .......................................................................................40 New Features in mSwitch R5.6 .......................................................................................41 New Features in mSwitch R6.0 .......................................................................................44
Typical Applications ........................................................................................49

Tandem-Level Networking Solution ................................................................................49 Access of Multiple Terminal Types..................................................................................50 Typical Solution to PHS Network ....................................................................................51
mSwitch
System Overview
ii
Interconnection between PHS Terminals ....................................................................51 Interconnection between PHS Terminals and PSTN Terminals .................................52 Typical Solution to VoIP Network ....................................................................................52 Interconnection between VoIP Terminals....................................................................53 Interconnection between VoIP Terminals and PSTN Terminals .................................53
Typical Service Solutions ............................................................................... 55

Q-Box Service Solution....................................................................................................55 Centrex Service Solution .................................................................................................57 iNumber Service Solution ................................................................................................62 CRBT Service Solution ....................................................................................................64 PBMS Solution.................................................................................................................68 FMC Solution ...................................................................................................................70 SIM Card Roaming Service Solution ...............................................................................72 Networking Model ........................................................................................................72 Service Logic ...............................................................................................................75 Call Flow ......................................................................................................................78 SIM-Based IP Terminal Subscriber Solution (release to PLDT only)..............................86 iWeSee Service ...............................................................................................................87
System Functional Components.................................................................... 91

Introduction to mSwitch Platform.....................................................................................91 Components in Service/application Layer .......................................................................93 Parlay GW ...................................................................................................................94 Parlay APP ..................................................................................................................95 Feature Server.............................................................................................................95 Components in Control Layer ..........................................................................................98 iCS-P ...........................................................................................................................98 Transaction Server ................................................................................................... 101 HLR........................................................................................................................... 104 VLR........................................................................................................................... 105 SAU .......................................................................................................................... 106 CPS2100 .................................................................................................................. 110 Components in Access Layer ....................................................................................... 113 iUMG......................................................................................................................... 113 iSG3200.................................................................................................................... 114 iSG5.6....................................................................................................................... 116 iMS............................................................................................................................ 121 iAN-8000................................................................................................................... 122 Components in Operation Support Layer ..................................................................... 129
System Overview
mSwitch
iii
CN SNMS ..................................................................................................................129 SAM ...........................................................................................................................131 OBS ...........................................................................................................................133 PSC ...........................................................................................................................137 CG .............................................................................................................................137 CSS ...........................................................................................................................137 ESS ...........................................................................................................................141 VSP Management System ........................................................................................142 IVR-1000 ...................................................................................................................146 VAS ...........................................................................................................................147 RADIUS Server .........................................................................................................148
5 6 A
System Disaster Tolerance Solution............................................................149 Performance Specifications..........................................................................151 Compliant Specifications and Standards ....................................................153
China Standards............................................................................................................153 China Telecom Standards .............................................................................................153 ITU-T Recommendations ..............................................................................................153 IETF Standards .............................................................................................................154 North America BELLCORE Standards..........................................................................156 NTT Standards ..............................................................................................................156 ANSI Standards.............................................................................................................156 India TEC Standards .....................................................................................................156 Chile Standards .............................................................................................................157
Acronyms........................................................................................................159
mSwitch
System Overview
iv
List of Tables
Table 1 Supplementary Services Available to PHS Subscribers ..............................................12 Table 2 Supplementary Services Available to IP Terminal Subscribers / V5 POTS Subscribers ...........................................................................................................................................14 Table 3 ANSI Standard-Compatible Supplementary Services..................................................16 Table 4 VAS Provided by mSwitch System...............................................................................17 Table 5 IN Services Supported in the mSwitch System ............................................................23 Table 6 iCS-P Performance Specifications ............................................................................ 101 Table 7 Usage of CPS-Provided Standard Protocol Stack by NEs in mSwitch Network....... 112 Table 8 Optical Interface Specifications ................................................................................. 114 Table 9 Electrical Interface Specifications.............................................................................. 114 Table 10 iSG5.6 Performance Specifications......................................................................... 118 Table 11 iSG5.6 External Interfaces and Protocol Specifications.......................................... 119 Table 12 iSG5.6 Physical Specifications................................................................................ 119 Table 13 Power Consumptions of the iSG5.6 Key Boards .................................................... 120 Table 14 Environmental Specifications .................................................................................. 120 Table 15 Power Module Specifications .................................................................................. 121 Table 16 Performance Specifications..................................................................................... 122 Table 17 Reliability Specifications .......................................................................................... 122 Table 18 System Performance ............................................................................................... 151 Table 19 Interface and Protocols............................................................................................ 151 Table 20 NE Specifications .................................................................................................... 151
System Overview
mSwitch
List of Figures
Figure 1 mSwitch System Architecture.......................................................................................6 Figure 2 Class 4 Solution Provided by the mSwitch .................................................................49 Figure 3 Class 5 Solution..........................................................................................................50 Figure 4 Interconnection between PHS Terminals in mSwitch Network ..................................51 Figure 5 Interconnection between PHS Terminals in mSwitch Network and Terminals in PSTN ...........................................................................................................................................52 Figure 6 Interconnection between VoIP Terminals in mSwitch Network ..................................53 Figure 7 Interconnection between VoIP Terminals in mSwitch Network and Terminals in PSTN ...........................................................................................................................................54 Figure 8 Solution to Q-Box Service .........................................................................................57 Figure 9 Solution to iNumber Service .......................................................................................64 Figure 10 Solution to CRBT Service .........................................................................................67 Figure 11 Solution to Phone Bar Management System............................................................69 Figure 12 SIM Card Roaming Service Solution ........................................................................73 Figure 13 Call Flow for a SIM Card Roaming Service Subscribers Request for Registration in Visited Network and Location Information Update ............................................................78 Figure 14 Call Flow for SIM Card Roaming Service Subscribers Request for Activating Follow Me to Home Logic and registering a New Follow Me to Home Number at the Visited Site ...........................................................................................................................................79 Figure 15 Call Flow for IDD Calls Made by SIM Card Roaming Service Subscriber from the Visited Site.........................................................................................................................81 Figure 16 Call Flow for Calls Originated from a Hunt Me Number to a SIM Card Roaming Service Subscriber at the Visited Country.........................................................................83 Figure 17 Call Flow for SIM Card Roaming Service Subscribers VMS Request.....................84 Figure 18 SIM-Based IP Terminal Subscriber Solution ............................................................86 Figure 19 External Interfaces of mSwitch Network Elements...................................................86 Figure 20 iWeSee Service Implementation Architecture ..........................................................90 Figure 21 4U Chassis (Front View)...........................................................................................92 Figure 22 4U Chassis (Front View)...........................................................................................93 Figure 23 4U Chassis (Rear View) ...........................................................................................93 Figure 24 Parlay API Structure .................................................................................................94 Figure 25 Location of the FS in mSwitch Network....................................................................96 Figure 26 Position of FS Acting as USSD Server in mSwitch Network ....................................97 Figure 27 External Interfaces of the iCS-P ...............................................................................99 Figure 28 TS External Interfaces and Protocols .....................................................................103 Figure 29 Protocol Conversion through HLR..........................................................................105 Figure 30 Protocol Conversion through VLR ..........................................................................106 Figure 31 SAU Architecture ....................................................................................................106
mSwitch System Overview
vi
Figure 32 FS + SAU Functioning as SCP .............................................................................. 107 Figure 33 GHLR and GVLR Deployed in WiFi/GSM FMC Solution....................................... 108 Figure 34 CHLR and CVLR Deployed in WiFi/CDMA FMC Solution..................................... 109 Figure 35 HLR Deployed in SIM Card Roaming Service Solution......................................... 110 Figure 36 Position of CPS2100 in Network............................................................................ 111 Figure 37 iUMG External Interfaces....................................................................................... 113 Figure 38 Signaling Conversion between mSwitch and PSTN/IN enabled by iSG ............... 115 Figure 39 iSG External Interfaces .......................................................................................... 116 Figure 40 Position of iSG5.6 in mSwitch Network ................................................................. 117 Figure 41 iAN-8000 Network Topology.................................................................................. 123 Figure 42 NGN Migration ....................................................................................................... 128 Figure 43 Architecture Conformance between mSwitch O/M Modules and TMN Layers ..... 129 Figure 44 Three- layer Structure of CN SNMS ...................................................................... 130 Figure 45 NEs Managed by CN SNMS.................................................................................. 131 Figure 46 NEs communicating with SAM............................................................................... 132 Figure 47 OBS Architecture and External Interfaces............................................................. 134 Figure 48 OBS Background Administration Flow................................................................... 135 Figure 49 Reseller Management System Structure ............................................................... 136 Figure 50 System Billing Data Paths ..................................................................................... 137 Figure 51 CSS Architecture ................................................................................................... 138 Figure 52 An Exemplary CSS Website Main Page................................................................ 139 Figure 53 Administration Center Login Page ......................................................................... 140 Figure 54 CSS Supports C-mode Service ............................................................................. 140 Figure 55 ESS Architecture.................................................................................................... 141 Figure 56 Customer Rental System Network Structure ......................................................... 143 Figure 57 Hotel Broadband Network...................................................................................... 145 Figure 58 IVR-1000 Architecture............................................................................................ 146
System Overview
mSwitch
About This Guide
Introduction
The mSwitch System Overview is intended to give an overall idea of the mSwitch system products to users. Being a reference document, this guide covers multiple mSwitch networking applications to meet multiple market requirements. Different markets might only use one or several of the solutions described in the guide. This guide cannot be used as a contract clause to provision all services for users. This guide is applicable to UTStarcom mSwitch R6.0 and earlier mSwitch R5.x releases. This document provides a systematic and comprehensive description of the mSwitch system. It includes the following chapters: Chapter 1 Overview This chapter introduces the architecture, features, subscriber types, service functions, and system availability of the mSwitch system, familiarizes the user with the whole system. Chapter 2 Typical Applications This chapter describes the wireless and wire line applications of mSwitch, including PHS solution, VoIP solution, C4 solution, C5 solution, IN service solution, and VoIP solution that cooperates with 3G network. Chapter 3 Typical Service Solutions This chapter describes the typical service solutions implemented in the mSwitch system, including Q-box service, Centrex service, iNumber service, CRBT service, and Phone Bar service, SIM Card Roaming service. Chapter 4 System Functional Components This chapter introduces the mSwitch hardware platform and various functional components of the system, including components in control layer, service/application layer, access layer, operation support layer, as well as their features, architectures and functions. Chapter 5 System Disaster Tolerance Solution This chapter describes the disaster tolerance solution of the system. Chapter 6 Performance Specifications This chapter lists technical parameters of mSwitch system. Appendix A Compliant Specifications and Standards Appendix B Acronyms
mSwitch
System Overview
About This Guide
Audience
Core Network Technical Engineers and Executives Operation Support Network Technical Engineers and Executives System Engineers Installation Engineers Operation & Maintenance Engineers
Conventions
This guide may contain notices, figures, screen captures, and certain text conventions.
Notices
The following table lists notice icons used in this guide.
Icon Notice Type Note Description Information that contains important features or instructions but is not hazard-related. Information to alert of potential damage to a program, data, system, or device. If not avoided, may result in minor or moderate damage. It may also alert against unsafe practices and potential program, data, system, device damage. Information to alert of operations that may cause potential accident, casualty, personal injury, fatality or potential electrical hazard. If not avoided, could result in death or serious injury. Information that indicates proper grounding precautions is required before handling a product.
Caution
Warning
ESD
Text
The following table lists text conventions in this guide.
Convention Description This typeface represents text that appears on a terminal screen, including, configuration file names (only for system output file names), and command names, for example login. Commands entered by users are represented by bold, for example, cd $HOME. This typeface represents window names, dialog box names, tabs, field names, function names, directory, file names, process names, and commands in text, for example, set the Time field. This square brackets represents menus such as [File], and [File/New] This angle bracket represents button on screen, function key on the keyboard and icon names for example, click <OK>. This typeface represents documents for reference, for example, Netman 2020 Installation Guide
mSwitch
Text represented by Courier New Font
Text represented by bold Text represented by [Menu] and [Menu/Sub-menu] Text represented by <Button> Text represented by Document Name
System Overview
About This Guide
Convention Text represented by
Description This typeface represents files in Unix/Linux system files.
# File format:
Figures and Screen Captures

This guide provides figures and screen captures as example. These examples contain sample data. This data may vary from the actual data on an installed system.
mSwitch
System Overview
Overview
The softswitch technology is the core of the next generation network (NGN). It implements an architecture that uses softswitch-enabled call servers to separate call control from transmission, and application servers to separate call service provisioning from call control. This softswitch architecture is based on a broadband packet-switched network infrastructure, with standard interfaces between different system units, and an open structure that delivers reduced cost in both operating and service development. It is a perfect architecture for carriers to migrate from traditional circuit-switched network to the NGN. The mSwitch system is a softswitch network product developed by UTStarcom for the next generation network (NGN). It is based on softswitch architecture, delivering a unified and fully IP-based solution to voice, data, fax, Internet content, and various broadband services for subscribers accessed through different interfaces. The mSwitch system also supports intercommunication with PSTN, third party softswitch system (interconnected through SIP-T/BICC), and third party VoIP system (interconnected through H.323 or SIP). It is an ideal system to construct the next generation network.
Typical Networking Architecture

Logically, the mSwitch network consists of four layers: OSS, Service/Application, Control, and Access. The Access layer supports various types of terminals which primarily can be divided into three categories: PHS terminals, which access the system through CSC/RPC (connected to the iUMG through the E1 interfaces using Q.921/Q.931 protocol). IP terminals, which access the system through IP network; the mSwitch system supports various types of VoIP protocols (such as SIP, H.323, MGCP), hence various types of VoIP terminals (such as MGCP IP phone, MGCP iAD, H.323 IP phone, H.323 iAD, SIP IP phone, and UTSmart PC phone). POTS terminals, which access the mSwitch system through iAN-8000 (connected to the iUMG using V5 protocol).
The OSS (Operation Support System) and Service/Application layers form a unified multi-service platform for subscribers using different types of terminals. The Control layer undertakes call processing, media conversion, and so on, and in particular, coordinates with the Access layer to enable service provision for PSTN subscribers.
mSwitch
System Overview
Chapter 1 Overview
Figure 1 mSwitch System Architecture
CS -A /C S -T /M S
CS -A /C S -T /M S
iMS 4 0 0 0
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
iAN-08E
S G
iAN-20 00
R P C
Net Edge 2024A L
iAN-2000
iAN-2000
As shown in Figure 1, the mSwitch system consists of the following components working in four layers, which are described as below:
System Overview mSwitch
Chapter 1 Overview
Operation Support Layer Core Network Sub-Network Management System (CN SNMS): provides functions such as system configuration, performance management, control & status management, and alarm management. Subscriber Application Management System (SAM): provides functions such as Point-of-Sale handling, resource management, staff management, and CDR metering, and so on. Online Billing System (OBS): provides functions such as multi-service billing, billing policy formulation, billing data processing, accounting, performing statistics and analysis. Customer Self-Service System (CSS): establishes connections between databases and customer to enable various customer self-care functions. Prepaid Service Center (PSC) / Accounting Center (AC): responsible for collecting and processing CDRs generated within the mSwitch system, supporting both prepaid and postpaid CDRs, and in particular, able to deliver real-time billing functions needed in prepaid service, such as calculating Allowed Call Time, debit prepaid subscribers deposit balance. Charging Gateway (CG): interfaces with third party billing systems, and collects CDRs generated within the whole network and sends related billing data to third party billing systems. RADIUS Server: implements the authentication and accounting functions for broadband, WLAN and 3G subscribers. RADIUS Server acts as a component of billing support system to be applied to different networks. Feature Server: enables local SCF to provide VAS functions, such as Calling Card, Prepaid services. Application Server: serves as an entity for service provisioning; communicates with the Open API provided by the Parlay GW in the mSwitch system, or with the Call Server through the standard SIP provided by iCS-P. Parlay GW: provides standard Parlay API for various applications, including those provided by third parties. Parlay APP: it is the service application of the Parlay platform, which interconnects with Parlay GW through Parlay API. IP-Based Call Server (iCS-P): serves as a C5 call server to provide call processing functions for various types of subscribers in the PHS and VoIP networks, and in C4 application, as a tandem office or a gateway office. As a call server, iCS-P undertakes number analysis, call connection, routing, and media resource control. It is one of the important components in mSwitch core network. Subscriber Location Register (SLR): manages and maintains subscribers profiles, location information, and provides various functions needed during call connection, such as authentication, authorization, address translation and route analysis. And also, it supports several supplementary services provision.
System Overview
Service and Application Layer -
Control Layer -
mSwitch
Chapter 1 Overview
Home Location Register (HLR): stores the location information of local subscribers. Visited Location Register (VLR): stores the current location information of the visiting subscribers.
Access Layer The access layer contains two types of entities, Access Gateways and terminals as described below: Signaling Gateway (iSG): provides signaling interface between mSwitch and PSTN/IN. Integrated Media Gateway (iUMG): serves as a media gateway to provide access, media conversion and switching services for PHS subscribers, and as a trunking gateway to complete media conversion between IP-based and TDM-based network. IP-based Media Server (iMS): controlled and managed by iCS-P to deliver media services to IP terminals, such as announcement playback, media resource needed in conference, and so on. The access layer contains terminals of different types as listed below: a PHS phone b V5 POTS phone c H.323 IP phone d MGCP/H.248 IP phone e SIP IP phone f Integrated Access Device (iAD): accesses the mSwitch system using MGCP/H.323 protocol. g iAN-8000: accesses the mSwitch system using MGCP/H.248 protocol, or through iUMG and using V5 protocol. h UTSmart PC phone
System Characteristics
The significant highlights of the mSwitch system are its unified IP-based platform, multi-protocol, multi-service and multi-access, as described below. IP-based and softswitch-enabled transmission network The mSwitch network features an IP-based and softswitch-enabled transmission network, with its IP packet transmission layer, control layer, call processing layer and application layer separated one another. Hence, the access, switching, service provisioning, and HLR/VLR function are all implemented separately; the switching functions is implemented in the IP-based transmission layer, and the other functions are implemented in Client/Server mode above the IP layer. This optimizes the network structure and reduces the complexity and cost of the network infrastructure. Multi-protocol support
System Overview
mSwitch
Chapter 1 Overview
The mSwitch supports various TDM-based and IP-based protocols, such as SS7 TUP/ISUP, INAP, SIGTRAN, SCTP, MTP, wireless Q.931, V5.X, ISDN PRI, MGCP/H.248, H.323, SIP, MEGACO, SCTP, SIP-T, SNMP, as well as the conversion among these protocols. Large processing capacity The iCS-P in the mSwitch system can deliver up to 1.5M BHCA of processing capability for ISUP-ISUP calls when the iCS-P working as a C4 call server, and 3M BHCA for ISUP-IP calls. Multi-access support The mSwitch supports multi-access, such as wireless access through standard PHS air interface, V5.x wire line access, and IP-based MGCP/H.248, H.323, SIP, iAN-8000 access. Unified multi-service platform The mSwitch employs a unified platform to provide telecom and network services, such as voice over TDM, VoIP and telecommunications supplementary services, as well as various types of VAS, such as PIAFS, c-mode wireless data service, SMS, MCN, Centrex and prepaid service. It also offers a unified service switching platform to support various traditional IN services, such as FPH (Free Phone), ACC (Accounting Card Calling), VPN (Virtual Private Network), UPT (Universal Personal Telecommunication), and so on. The mSwitch system is also equipped with a service provisioning system compliant to Parlay API standards, which provides iNumber service and shortcut to implement more newly developed services. By using enhanced AS/MS, mSwitch system can also provide various enhanced IP services, such as Web-Conferencing (WC) and Unified Messaging (UM). High performance softswitch control platform The mSwitch uses a powerful softswitch control platform to enable various softswitch real-time logics, such as authentication, authorization, address parsing, roaming, routing, real-time billing, and so on. Support for multiple networking solutions The mSwitch system employs a subscriber data center which is separated from switching. This mobile softswitching system architecture is able to support multiple networking solutions for different service requirements. Powerful Operation Support System The mSwitch employs powerful server clusters to support various back office management functions, such as subscriber management, on-line billing, customer self service, network management and operation and maintenance. It provides service operators with comprehensive and effective tools for system operation and maintenance as well as service provisioning. High Availability The mSwitch system has a high availability level of 99.999% as required in telecommunication system.
10
Chapter 1 Overview
The system supports seamless system upgrade, without interrupting service provisioning. In the mSwitch system, all key functional boards running on mSwitch hardware platform, such as MPU, HSM, PPU, CLK, DSP, SEM, and DPS, support hot-swap and redundancy. MPU supports warm standby, which results in no billing data lost during switch-over. Power supply modules (DPS) support redundancy and load sharing. Under the control from SLR, iCS-P provides n+1 redundancy and warm standby. Under the control from iCS-P, iUMG/iMS provides n+1 redundancy and warm standby. iSG supports 1+1 redundancy and warm standby. Applications such as SLR, PSC, etc. support dual NIC configuration. SLR/PSC supports n+1 redundancy; loads can be shared among these SLRs. MCNC supports 1+1 load sharing. Heartbeat mechanism is used among the systems key modules, for example, the heartbeat between SLR/RS/PSC, and that between SLR/RS/PSC and CS or CN SNMS. Dual OSS DB servers, with RAID disk system, ensure data security, and optional dedicated backup server. In system networking, all IP links have redundant backups. MTBF > 400,000 hours MTTR < 30 minutes
System Features
The mSwitch system provides an IP-based total solution for various types of subscribers, including mobile terminals accessing through air interfaces, POTS terminals accessing through access devices, and IP terminals accessing through broadband network.
System-Level Features
Multi-protocol Support
The mSwitch system supports: Trunking gateway control protocol: MEGACO/H.248 SIGTRAN protocol for SS7 signaling encapsulation H.323 and SIP-I protocols, needed to enable the interconnection with third party VoIP networks PRI, ISUP and TCAP/INAP, needed to enable the interconnection with PSTN.
System Overview
mSwitch
Chapter 1 Overview
11
Interworking with PSTN

The mSwitch system supports: ITU SS7 signaling ANSI SS7 signaling SIGTRAN protocol (including M3UA, M2UA and IUA) T.38 protocol on the SIP trunk side and MGCP and H.248-based access side Up to 128 SS7 signaling links per SG, also redundancy have been taken into consideration INAP protocol, which enables communication with SCP in SS7 network needed in intelligent network service provisioning. T1/E1 PRI and R2 protocols, needed by trunking gateway for interworking with PSTN Various types of media codecs: G.711 G.723.1 G.726 G.729A/B
Carrier-Level Features
Call Control
Emergency call Subscriber authentication, authorization and access control Calling number and called number analysis and routing Subscriber information management Announcement configuration (multiple languages supported)
NMS Features
Supports SNMP v2. Provides NMS GUI for configuration management, performance management, fault management, and system security management. Provides NMS operator management functions.
Types of Subscribers Supported

The mSwitch system provides access support for various terminal subscribers.
mSwitch
PHS (access through iUMG) V5 POTS (access through iAN-8000) IP-based POTS (access through iAN-8000/iAD) IP terminals, include MGCP/H.248 IP phone, MGCP/H.248 iAD
System Overview
12
Chapter 1 Overview
H.323 phone, H.323 iAD SIP phone UTSmart PC phone (SIP-enabled)
Besides, the mSwitch system supports interconnection with third party networks, such as interconnecting with PSTN, supporting communications between subscribers in local network and those in PSTN; interconnecting with third party H.323 network, supporting communications between subscribers in local network and those in third party H.223 network; interconnecting with third party SIP network (through SIP-T), supporting communications between subscribers in local network and those in third party SIP network; and interconnecting with third party PHS network (through MAP), supporting PHS communications and roaming among PHS systems provided by different service providers.
Subscriber-Level Features
Basic Services
Voice service Voice over IP service (VoIP) Circuit-switched data service (including analog dial-up services and basic fax services) Audio/Visual call Emergency call service (fire alarm, police alarm, and so on, supporting call routing to nearest local alarm center) Special service (1xx, 2xx, and so on)
Supplementary Services
Table 1 lists the supplementary services that the mSwitch provides for PHS subscribers. Table 1 Supplementary Services Available to PHS Subscribers
No. 1. 2. 3. 4. 5. 6. Supplementary Service Abbreviated Dialing Outgoing Call Barring Incoming Call Barring Do Not Disturb service Malicious Call Identification Alarm Call service PHS Remarks
System Overview
mSwitch
Chapter 1 Overview
13
No.
Supplementary Service
PHS
Remarks When a subscriber dials an unallocated subscriber number or has operation mistakes, this service automatically intercepts the calls and routes the calls to a pickup device to answer them. This service is free of charge. No application or operation is required.
7.
Interception Calls
8.
Absent Subscriber service
The CDR forwarded contains an original callee identifier, which can be configured through OBS, and is used to specify whether the original callee is to be charged for roaming service and by what tariff rate the callee is to be charged.
9.
Call Forwarding Unconditional (CFU)
10. 11. 12. 13. 14. 15.
Call Forwarding No Reply (CFNR) Call Forwarding Busy (CFB) Call Forwarding on Not Reachable (CFNRC) Call Forwarding Operator Activation (CFOA) Call Waiting (CW) Call Hold
Available in mSwitch Release 5.6.5 and later for ordinary NGN subscribers Available in mSwitch Release 5.6.5 and later for ordinary NGN subscribers Available in mSwitch Release 2.5.3 and later Available in mSwitch Release 5.6.5 and later
16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28.
Call Transfer Three Party Service Conference Calling Calling Line Identification Presentation (CLIP) Calling Line Identification Restriction (CLIR) Call Destination Restriction/Incoming Blacklist Call Destination Restriction/Outgoing Blacklist
Call Destination Connection/Outgoing Whitelist
Up to five parties supported
Automatic Callback Call Back on Busy Last Number Redial Voice Mail Service (VMS) Voice Mail Notification (VMN)
Available in mSwitch Release 5.6.5 and later Available in mSwitch Release 5.6 and later Available in mSwitch Release 5.6.5 and later
Note: means supported.

14
Chapter 1 Overview
Table 2 lists the supplementary services that the mSwitch system provides for IP terminal subscribers and V5 POTS subscribers in NGN applications. Table 2 Supplementary Services Available to IP Terminal Subscribers / V5 POTS Subscribers
No Supplementary Service H.323 Terminal Subscribers MGCP/H.24 8 Terminal Subscribers SIP Terminal Subscribers V5 POTS Subscribers Remarks
1. 2. 3. 4.
Abbreviated Dialing Hotline Service Outgoing Call Barring One-time Debarring
X Available in mSwitch Release 5.5 and later Available in mSwitch Release 5.6 and later
5.
Incoming Call Barring
6. 7. 8. 9.
4Do Not Disturb Service Malicious Call Identification Alarm Call Service (Casual) Alarm Call Service
X -
X X -
Available in mSwitch Release 5.6.5 and later for Brazil No announcement played for SIP terminal subscribers
10.
Wake up Service (Regular)
11. 12. 13.
Interception Calls Absent Subscriber Service Call Forwarding Unconditional (CFU)
The CDR forwarded contains an original callee identifier, which can be configured through OBS, and is used to specify whether the original callee is to be charged for roaming service and by what tariff rate the callee is to be charged.
14. 15. 16.
Call Forwarding No Reply (CFNR) Call Forwarding Busy (CFB) Call Forwarding Operator Activation (CFOA)
Available in mSwitch Release 5.6.5 and later

mSwitch
System Overview
Chapter 1 Overview
15
No
H.323 Terminal Subscribers
MGCP/H.24 8 Terminal Subscribers
SIP Terminal Subscribers
V5 POTS Subscribers
Remarks
17. 18.
Call Waiting (CW) Call Hold
Available in mSwitch Release 5.6.5 and later for ordinary NGN subscribers Available in mSwitch Release 5.6.5 and later for ordinary NGN subscribers Whether SIP subscriber can use this service depends on terminal functions. It is required that the terminal initiate a new call after a connection has been created (available in mSwitch Release 5.3 and later)
19.
Call Transfer
(Unattended Transfer available in mSwitch R6.0 and later) X
20.
Three Party Service
21. 22. 23. 24. 25. 26. 27.
Conference Service Calling Line Identification Presentation (CLIP) Calling Line Identification Restriction 4 (CLIR) Call Destination Restriction /Outgoing Blacklist Call Destination Restriction /Incoming Blacklist Call Destination Connection /Outgoing Whitelist Anonymous Call Rejection (ACR)
Available in mSwitch Release 5.5 and later Available in mSwitch Release 5.5 and later Available in mSwitch Release 5.5 and later Available in mSwitch Release 5.6.5 and later IP terminal needs to support CLIP IP terminal needs to support CLIP
28.
Automatic Callback (AC)
29.
Automatic Recall (AR)
30.
Call Back on Busy
mSwitch
System Overview
16
Chapter 1 Overview
No
H.323 Terminal Subscribers
MGCP/H.24 8 Terminal Subscribers
SIP Terminal Subscribers
V5 POTS Subscribers
Remarks
31.
Multiline Hunt Service (MLH)
Available in mSwitch Release 5.6 and later Available in mSwitch Release 5.6.5 and later
32.
Last Number Redial
33. 34.
Voice Mail Service (VMS) Voice Mail Notification (VMN)
Note: means supported, X means not supported, - means not applicable. Note: For IP terminals (including POTS subscribers on iAD devices), the availability of services listed above are device-dependent. Those supplementary services are available to IP terminals in the Switch system if the IP terminals are interoperable with standard access protocols. Table 3 lists the ANSI standard-compatible supplementary services available to NGN subscribers. It is applicable to North America market. Table 3 ANSI Standard-Compatible Supplementary Services
No. 1 2 3 4 5 Supplementary Service Speed Dialing Call Forward on Busy (CFB) Call Forward on No Reply (CFNR) Call Forward on Unconditionally (CFU) Call Waiting (CW) MGCP Terminal SIP Terminal Grand Stream SIP phone only Remarks
6 7 8 9 10 11 12 13 14 15 16 17
System Overview
Caller ID (CID) Call Waiting ID (CWID) Call ID Delivery Blocking-All Call (CIDB-All Call) Call ID Delivery Blocking-Per Call (CIDB-Per Call) Multiple Numbers with Distinctive Ringing (MNDR) Voice Mail (VM) Voice Mail Notification (VMN) Outgoing Call Barring (OCB) Outgoing Trunk Selection Selective Call Rejection (SCR) Anonymous Call Rejection (ACR) Automatic Callback (AC)

mSwitch
Chapter 1 Overview
17
No. 18 19 20 21 22 23 24
Supplementary Service Automatic Recall (AR) Three-Way Calling (TWC) Feature Group D (FG-D) Local Number Portability Toll Free Service (TFS) Service Access Code E911
MGCP Terminal
SIP Terminal
Remarks
Note: E911 emergency service is a public security service provided over the emergency communications network in the United States, which enables related government departments to precisely locate callers in help, to respond quickly to sudden events, such as accidents, criminal attacks, disasters, and so on. Being an NGN-enabled solution, the mSwitch system can interface with Intrado system to enable both real-time location query and DB provisioning for its VoIP subscribers.
Value-added Services
The mSwitch system provides value-added services (VAS) for PHS, V5 POTS and IP terminals, as listed in the following table: Table 4 VAS Provided by mSwitch System
POTS Subscr ibers on H.323 IP Phone & iAD X X -
No.
Value-Added Services
PHS
V5 POTS Subscrib ers on iAN-8000
POTS Subscribes on MGCP IP phone& iAD/iAN-8000
SIP IP Phone Subscr ibers
Remarks
1 2 3 4 5
C-mode service Short Message Service (SMS) Missed Call Notification (MCN) Voice Mail Service (VMS) Location Service (LS)
X X X X
X X X X A WPABX supports only one Centrex group, and the group number must be set as 1. Besides, connection with PSTN through API is supported only. Based on CLIP and SMS
Wireless Private Automatic Branch Exchange (WPABX)
6a
Basic call service: intra-group calls, calls between internal and external lines Pick up Service Intercept Service
Provides intra-team pickup and inter-team pickup features.
6b 6c
mSwitch
System Overview
18
Chapter 1 Overview
No.
Value-Added Services
PHS
V5 POTS Subscrib ers on iAN-8000
POTS Subscr ibers on H.323 IP Phone & iAD -
POTS Subscribes on MGCP IP phone& iAD/iAN-8000
SIP IP Phone Subscr ibers
Remarks
6d 6e 6f 6g
Call Transfer Call Forwarding Operator Team Service
Provides normal team and closed team features. The malicious call identification feature is not available.
6h 7 8 9 10 11 12 13 14 15 16 17
Other supplementary services Unified Messaging (UM) 32Kbps/64Kbps PIAFS Wireless Dial-up Service Web-Conferencing (CB) PHS First Color Ring Back Tone (CRBT) Caller-CRBT Lawful Interception Service Centrex Multimedia conference (iWeSee) StudentComm Service Multiple Numbers with Distinctive Ringing (MNDR)
This feature takes precedence over the MCN feature.
Available in OSX release 3.0.
Note: means supported, X means not supported, and means not applicable. Lawful Interception Service The mSwitch system supports lawful intercept of the user traffic in its network; with legitimate permissions, special monitoring devices can be used to monitor the subscribers calls in mSwitch system, without interrupting the calls. Centrex service The mSwitch provides Centrex service for PHS and IP terminal subscribers within a domain. Subscribers in a Centrex group may belong to different gateways (iMG), or different call servers (iCS-P), or a mixture of subscribers, partially belonging to gateways (iMG) and partially belonging to call servers (iCSP). These subscribers form a virtual group. They can make intra-group calls with the private numbering plan (PNP) numbers, and call external lines through the operator or by making direct outward dialing. The operator transfers inbound or outbound calls.
Chapter 1 Overview
19
Centrex group subscribers are charged with different tariffs. In addition, supplementary services and value-added services available to normal mSwitch subscribers are also available to Centrex subscribers. IP Centrex service is a subcategory of Centrex service, intended for IP terminal subscribers. Subscribers in a Centrex Group may belong to one or more call servers (iCS-P). These subscribers form a virtual set, and each has two numbers; one is a PNP number, used to communicate within the Centrex group; the other is a long number, used to communicate with outside subscribers. In the mSwitch system, Centrex service has the following characteristics: An iCS-P supports up to 5000 Centrex groups. Fully based on the traditional Centrex features, with additional features. PHS subscribers and IP terminal subscribers can belong to the same Centrex group. IP Centrex subscribers are charged with different tariffs. IP Centrex service is carried over IP network, which greatly reduces the operating cost. Geographically, IP Centrex subscribers can be located at any areas, minimizing the communication expenses of a company with subsidiaries or offices at different places. Supports operator-initiated operations, such as service registration, cancellation and traffic management, through PHS and IP terminals. Provides auto attendant feature and attendant night service. Provides Call Park, Call Hold, Outgoing Trunk Selection, and Forward to PSTN features.
Missed Call Notification (MCN) The mSwitch system delivers MCN service for PHS subscribers based on Calling Line Identification Presentation (CLIP) and short message service (SMS). When a subscribers phone is powered off or outside the service area, the missed call records (MCRs) will be stored in the missed call notification center (SLR/MCNC) and database. When the subscriber is reachable (such as performing registration at a new location, placing or receiving a call), the MCNC will notify the iPAS gateway to send to the subscriber an MCR which states the calling number. A star key * will be added to the calling number to differentiate it from an ordinary incoming call number. Alternatively, the MCNC notifies the SMS center (SMSC), to have the SMGW send a MCR message to the subscriber. When signing up for the MCN service, the subscribers can select whether to receive a missed call notification based on CLIP or SMS. The mSwitch system also provides MCN service for inter-domain roaming subscribers.
Short Message Service (SMS) mSwitch system provides PHS subscribers with a variety of short message services, including sending and receiving point-to-point text short messages, receiving Short Message Peer to Peer (SMPP)-compatible broadcast short messages (such as weather forecast and stock information), as well as supports
mSwitch
System Overview
20
Chapter 1 Overview
for other value-added services, such as, SMS-based MCN, E-mail notification, voice-mail notification, E-bank service and personal financing. The Short Message Service Center (SMSC) and the Short Message Gateway (SMGW) provide short message service for mSwitch system. Also, the system supports storing and forwarding short messages. When a subscriber is unreachable, the short messages will be stored in the SMSC and resent when the subscriber becomes reachable. Location service (LS) Location service is the facility where the system provides a PHS subscribers location to authorized users. The system delivers two types of location services: Location Dependent Service (LDS): It is triggered by a PHS subscriber. LDS is primarily used to support C-mode Web browser service, for example, allow a PHS subscriber to know the location of the handset and get local service (such as ISP service etc) Location Tracing Service (LTS): a feature provided to an authorized authority, such as 911, taxi-calling center etc. It enables automatically locating emergency phones, locating and tracing handsets.
C-mode The mSwitch system provides PHS subscribers with C-mode wireless data service, also called P-mail Deluxe Service (PDX). The C-mode services provided in mSwitch system include E-mail service, E-mail service with attachment (audio file and video file), Web browsing service, LDS based Web browsing service (e.g. roaming subscribers are served at the visited area, but the feature is not supported in this version of mSwitch), and service subscription. The subscribers can get the required information through the handset screen. The C-mode system consists of several servers, such as application server, registration server, information server, Web server, E-mail gateway, Mail transmission agent (MTA) server, etc. It connects with gateway in the mSwitch system through iAG PDX, accepting the access of PHS users. It connects with SMGW to provide E-mail notification service. It connects with SAM to maintain the registered subscriber information. It connects with CDR Mediation, a CDR processing center, to transmit the usage records for the purpose of implementing C-mode service billing. It connects with Location Server (LS) to support LDSbased Web browsing service.
Voice mail service (VMS) The mSwitch system provides voice mail service. To enable the voice mail service, iCS-P needs to be connected with Voice Mail System (VMS) through SIP protocol. When a subscriber has applied for the VMS, the mSwitch system will forward a call to the subscriber to the Voice Mail System (VMS) when the subscriber is busy, or makes no reply, or unreachable, depending on how it is configured. At the same time, the VMS will notify the calling party to leave a message; the subscriber also can call VMS to pick up the message.
System Overview
mSwitch
Chapter 1 Overview
21
The Short Message Service Center (SMSC) in the mSwitch system supports SMPP to enable communications with the VMS and implement voice message notification through short messages. 32 Kbps/64 Kbps PIAFS Wireless Dial-up Service The mSwitch supports 32 Kbps/64 Kbps wireless dial-up service. The iMG can interconnect with a third party RAS gateway (i.e. iAG) through SS7 TUP, SS7 ISUP or ISDN PRI protocol interface, to communicate with multiple ISPs. The mSwitch system can provide high-speed Internet data service to the wireless PHS subscribers, document the changes in Internet access rates and connection time, and perform subscriber charging. A PHS subscriber can connect a computer with the handset and dial a designated access number to access Internet. Unified Messaging Service (UMS) The Unified Messaging Service (UMS) is an integrated information service that stores and manages at the same location all the data to be exchanged between subscribers, such as voice, fax, paging, short message, e-mail and multimedia data. It allows subscribers to send and receive data through various types of terminals, including the phone, fax machine, handset, pager, PC, or PDA. This way, the information service becomes more personalized and intelligent. Web-Conferencing (CB) The Web-Conferencing service offers a flexible interactive communication environment to enable voice and data exchange among remotely separated subscribers, allowing people at different places (home or office), or working on different terminal devices (phone or Web browser) to book or attend a phone conference. It assists a company in enhancing the efficiency and cutting down travel expenses. Color Ring Back Tone (CRBT) Service The Color Ring Back Tone (CRBT) service is a callee-orient service. It allows CRBT subscribers to set different ring back tones for different caller groups, different dates, or different time segments in a day, so that callers could receive different ring back tones when calling to these callees, other than those plain ring tones commonly used. CRBT subscribers are required to customize each type of color ring back tones to be used; these tones could be ring tones/music provided by the system, or audio files CRBT subscribers prepared via IN network system or downloaded from other network to IN network system. The CRBT service plays as a contributor to carriers business volume and revenue by delivering personalized value-added services that are based on carriers existing network resources. The CRBT service allows the subscribers to display their individualities; it has a potential customer basis. Caller CRBT service The Caller Color Ring Back Tone (Caller CRBT) service is a new service developed on the basis of Callee CRBT service. After a user subscribes to the Caller CRBT service, when waiting for the answer from the called party, the
22
Chapter 1 Overview
service subscriber will hear the color ring back tone defined by the calling party himself/herself, instead of hearing a beep tone or the color ring back tone defined by the called party. When the called party hooks off, the ring back tone is cut and the both parties enter a conversation. The Caller CRBT service takes full use of the existing network resources of the carrier and provides a personalized value-added service to the markets. The purpose is to effectively improve the network traffic of the carrier and increase the network operation income of the carrier. Multiple Numbers with Distinctive Ringing (MNDR) The Multiple Numbers with Distinctive Ringing service allows a service subscriber to apply for several numbers. No matter which number is called, the service subscriber can be found. In addition, the service subscriber can define different ringing tones for the different numbers to distinguish the calling parties. Usually there are two categories of terminals. One category can support ringing tones controlled by the call server. The other category only supports ringing tones controlled by the terminals themselves. This service is available only to the first category of terminals. Currently, there are the following terminals in the mSwitch network. Their support for this service is described as follows: PHS terminals (the protocol does not support): The terminals play the ringing tone and cannot support the current service. POTS terminals (the protocol supports): The protocol supports the terminals that are accessed by iAN-8000 to the iCS-P. The iAN-8000 controls the playing of the ringing tone of these terminals. If the iAN-8000 supports the control of the ringing tone, the terminals can support the current service. (At present, the iAN-8000 does not support this service in the cases of V5 access). H.248 terminals (the protocol supports): For the terminals that are accessed by iAD to the iCS-P, the iAD plays the ringing tone of these terminals. If the iAD supports the control of the ringing tone, the terminals can support the current service. MGCP terminals (the protocol supports): The protocol supports the terminals that are accessed by iAN-8000 or iAD to the iCS-P. The iAN-8000 or the iAD controls the playing of the ringing tone of these terminals. If the iAN-8000 or the iAD supports the control of the ringing tone, the terminals can support the current service. (At present, the iAN-8000 supports this service in the cases of MGCP access). SIP terminals (the protocol does not support): The terminals play the ringing tone and cannot support the current service. H.323 terminals (the protocol does not support): The terminals play the ringing tone and cannot support the current service.
Note: The same type of IP terminals might have several models. Different models have different functions. Therefore, for the later three types of terminals, if some models of them support the ringing tones controlled by the call server, the terminals of these models can support the current service.
Chapter 1 Overview
23
Intelligent Services
The mSwitch system supports various traditional IN services defined in CS-1 and CS2. These services are listed in the table below: Table 5 IN Services Supported in the mSwitch System
No. 1 2 3 4 5 6 7 8 9 10 11 12 IN Service Free Phone Service ( FPH), 800 number Account Card Calling (ACC) , 300 number Virtual Private Network (VPN) Service, 600 number Universal Personal Telecommunication ( UPT) Number Portability ( NP) Mass Call (MAS) Service Tele-voting (VOT) Service Wide Area Centrex (WAC) Service iWAC Service Unique Number (iNumber) Service Prepaid Service Q-Box Service mSwitch Subscriber The 3.0 version of mSwitch supports lastminute notification. Currently not available Currently not available Remarks
Free Phone Service, 800 Free phone service, also known as 800 service, is a special service associated with certain callee numbers, usually offered by some large companies for customers convenience. These companies pay charges involved, to encourage their customers to call these numbers. Ordinary subscribers can access 800 services within specified regions by dialing 800-preceded numbers.
Accounting Card Calling, 300 In this service, accounting cards, which are provided by operators or distributors to the ordinary users, are used as a payment method. A cardholder can make a local or long distance call by inputting the account number and password from any DTMF telephone, regardless whether this telephone is barred from long distance dialing or not, and the charge for the call will be debited to the account. Accounting card is classified as prepaid card and postpaid card, and both types of accounting card support roaming.
VPN Service, 600 In a VPN service, the subscribers form a virtual group which is served over the existing physical network resources. It enables many dedicated features such as numbering plan, dial-up mode, routing and accounting plan. The service is particularly suitable for large companies with subsidiaries and branches in different geographical areas.
mSwitch
System Overview
24
Chapter 1 Overview
NP Service The Number Portability (NP) Service is designed to offer a solution to frequent phone move due to the frequent move of subscribers (companies or individuals). It enables the portability of phone numbers within a local network scope through a unified IN platform, allowing subscribers to keep their phone numbers after moving to new locations. In other words, it makes a number permanent to a subscriber.
UPT Service The Universal Personal Telecommunication (UPT) Service is a portabilityoriented service, which allows subscribers to use a unique personal number. With this personal number, subscribers can place and receive calls in one network or across several networks. UPT can incorporate multiple telecommunication devices, such as mobile phone, home phone, office phone, voice mailbox, etc., and allows subscribers to define the way the UPT service is implemented through the CSS system or IVR system. The communication number of a subscriber is translated to a corresponding number, and the incoming calls to the number are routed as predefined. Calls are not restricted by geographical locations, but may be restricted by the network capacity or by terminal capacity. UPT subscribers are characterized by the charging methods for outgoing calls and incoming calls/management service. UPT account billing and usage limitation method could involve both outgoing calls and incoming calls. If a subscriber applies for account billing, all the outgoing calls and incoming calls/management service will be debited to the account; if the subscriber applies for monthly usage limitation or daily usage limitation, this limitation could apply to both outgoing calls and incoming calls, or only to outgoing calls. If the limitation is set to apply to both outgoing calls and incoming calls, it must be checked before each outgoing or incoming call/management service.
VOT Service The VOT service is designed mainly for companies or organizations to conduct a public survey or public opinion poll. A company or an organization requests from the service provider (or carrier) for one or more phone numbers. The end users can dial these numbers on any DTMF phone and register their votes. The system records the number of calls and sends the data to the user. VOT service can be categorized into the following types: Simple VOT: a simple VOT service, in which each number represents an opinion; to vote for the opinion, end users only need to call the number, and every call to the number is automatically recorded by the system as a vote supporting the opinion. Simple VOT with Reward: a simple VOT service with reward, in which each number represents an opinion; to vote for the opinion, end users only need to call the number, and every call to the number is automatically recorded by the system as a vote supporting the opinion. In addition, the system will pick a call as the reward winner and forward the call to a specific number according to configured rules (for example, according to the sequence number of the call, or the time when the call is placed).
mSwitch
System Overview
Chapter 1 Overview
25
Multi-Choice VOT: in this service, each number represents a project, not an opinion; the end users cast votes or participate in a reward according to the voice prompt.
MAS Service The MAS service is similar to a hot line, but it is capable of dealing with short time traffic peak. The MAS user requests a service number from the carrier and makes it known to the public. The system makes responses to calls from the end users in two ways: diverting the calls to a hot line, or playing a voice announcement to instruct the callers to perform keyboard operations.
Wide Area Centrex (WAC) Service The ordinary Centrex service can be implemented only in a group of subscribers using access devices of the same type. For example, subscribers in a Centrex could be those under iUMG, or under iCS-P, however, subscribers under iUMG and those under iCS-P cannot be in the same Centrex. WAC Service suffers no such a limitation; it can resort to IN architecture and the VPN service in this intelligent network to group Centrex subscribers and other individual subscribers distributed in different switching devices (iCS-P, iUMG, access equipment in PSTN or third party networks) into a virtual network, so that related services can be delivered. Calls among WAC subscribers within the same switching device (that is, within the same Centrex) are processed within the Centrex and charged according to the billing method implemented in the Centrex; calls among individual subscribers and between different switching devices are processed through IN SSP and SCP and charged according to the billing method implemented in VPN. It could be said that WAC Centrex service is a combination of ordinary Centrex service with VPN service.
iWAC Service The iWAC service is a supplement to the Centrex service provided by UTStarcom. The iWAC service interconnects the Centrex/PBX groups across several areas by using the mSwitch softswitching system to build a larger virtual private network, and based on it, to provide the various Centrex services for end users. In the whole network, the users can dial to each other by using Private Numbering Plan (PNP) numbers. Compared with the Centrex service, the iWAC service has a coverage area of several cities. This enlarges the usage of mutual dialing based on PNP numbers and benefits the internal communication inside the corporations across several areas. An iWAC group might include the following types of users: mSwitch Centrex users: These include PHS subscribers, SIP terminals, H.323 terminals, H.248 terminals, MGCP terminals, iAD-accessed POTS terminals, MGCP iAN-8000 subscribers, and V5 iAN-8000 POTS subscribers that belong to the mSwitch system. These users must have been added in a Centrex group before they are added to the iWAC group. mSwitch PBX users: These include PRI/R2-accessed PBX users that belong to the mSwitch system.
mSwitch
System Overview
26
Chapter 1 Overview
PSTN Centrex users: These include ISUP-based, ordinary PSTN/PLMN subscribers. These subscribers must first form a Centrex group on the carrier side and own the iWAC service attribute. PSTN PBX users: These include PBX users under the control of PSTN exchanges.
For the internal subscribers in the mSwitch system, to reduce network overhead, usually the mSwitch subscribers in different areas first form different Centrex groups, and then the Centrex groups in the different areas are added in the iWAC group. In this way, calls within a Centrex group can be processed by the local call server; only those beyond the Centrex group need to be routed to the upper layer service platform for further processing, hence the signaling traffic in the network reduces. In addition, the iWAC group covers the PRI/R2-accessed PBX users in the mSwitch system and the PSTN Centrex users or PBX users interconnected by a C4 office. Calls between the mSwitch Centrex users and these users all need to be routed to the upper layer service platform for further processing. The users in the iWAC group use a unified PNP. The PNP prefix cannot be the same as those for special services or the prefix for outward dialing. With this service, the wireless users and wired users in the same group can dial to each other by using PNP numbers, add the outward dialing prefix when calling the subscribers outside the group, enjoy a lower tariff, and have the other Centrex features. iNumber Service The iNumber is the short for Unique Number, a service that allows subscribers to use a unique number to access a network, and to cross multiple networks, or simply speaking, binds a service number with multiple terminals. The iNumber service can be flexibly implemented in networking environments involving multiple types of networks. Deployment of iNumber service leverages carriers existing network resources, and facilitates personalized VAS delivery, allowing carriers to achieve increased volume of service sale and increased revenue. The iNumber is a callee-intended VAS. Its basic function is to correlate all the communication numbers a subscriber owns with one specified number, so as to achieve the ever-accessibility to the subscriber when as a callee. There are typically two types of logic governing how the master number and correlated numbers will ring when iNumber service is triggered: Group Hunting and Group Ringing. The iNumber service supports prepaid subscribers; it also supports monthly rent and CDR-based billing, as well as the combination of these two methods. The CDRs for iNumber service are explicitly marked to tell the CDRs generated for iNumber services from other types of CDRs; and each of them contains the master number and the number answering the call. Prepaid Service
System Overview
mSwitch
Chapter 1 Overview
27
Prepaid services provided by mSwitch system include various functions, such as opening accounts for prepaid subscribers, recharging, querying the current balance of a prepaid subscriber, querying the usage detail of prepaid subscribers, setting callee discount numbers for a prepaid subscriber, querying existing callee discount numbers of a prepaid subscriber, balance notification, and so on. SLR/RS, PSC, iCS-P, SAM (Subscriber Application Management), and OBS (Online Billing System) should be configured to support this service. More detailed discussions are given below. b c The operator should work on a SAM system to create subscribers accounts to enable prepaid billing. The operator should configure relevant parameters through OBS, including service plan, price plan, domain information (such as country, province/state, area), discount package, tariff plan, day/time discount, and usage credit, settings related to callee discount (such as the number of callee discount numbers allowed for a subscriber, discount rate, lock period, and so on). When processing a call from a prepaid subscriber, the iCS-P gets the calling partys profile from the SLR to judge whether the caller is a prepaid subscriber or not. If the caller is a prepaid subscriber, the iCS-P will ask the PSC (Prepaid Service Center) to calculate maximum allowed calling time. The PSC is in charge of processing prepaid service; it will calculate the maximum allowed calling time according to the balance of the prepaid account and the OBS configuration info mentioned above, and then send the result to the iCS-P. If the actual calling time reaches the maximum allowed calling time, the iCS-P will disconnect the call. After the call is over, the iCS-P will send CDR for this call to PSC immediately. PSC will charge this call according to calling time and the OBS configuration information, and debits the balance of this prepaid subscriber with the charge for the call.
The mSwitch system is equipped with an interactive voice response system (IVR1000), which allows subscribers to complete various self-assistant operations, such as depositing, querying balance, setting callee discount numbers; and could be used to implement balance notification/payment collection. Note: The implementation of balance-notification/payment-collection involves setting operations on OBS management GUI, a background program (balancenotify), an API (IVR_Agent) and IVR-1000. The parameters related to balance-notification/paymentcollection have to be configured on the OBS management GUI; the background program monitors subscribers deposit status on real-time basis, checking if the deposit status of a subscriber meets the settings made on OBS GUI (for example, the balance is below certain preset level); the IVR_Agent interfaces with the IVR-1000, sending subscribers information to the IVR system; the IVR system issue notices to subscribers accordingly. These self-assistant operations, for example, balance inquiry and familiarity number setting, can be performed by an operator on an OBS console, or completed through a customer self-service system (CSS). Multi-Service Interface Protocol (MSIP), an UTStarcom private protocol, is used for service switching and data switching between the mSwitch OSS and IVRmSwitch System Overview
28
Chapter 1 Overview
1000 system. The MSIP uses TCP/IP or UDP as transmission layer protocol to ensure reliable transmission. In mSwitch 2.5 or above, the MSIP is used as the interface protocol between IVR-1000 and OBS/SAM, and also as the standard communication protocol between mSwitch system and third party systems, such as China Telecoms 97-system, third party IVR system, and third party accounting systems, and bank systems, to implement prepaid services in third party systems. Q-Box service The Q-Box service is a new service based on the POTS + PHS Home Station concept, which is substantiated as a Q-Box terminal, a CPE that delivers homecoverage mobility for PHS while inherit the advantages of traditional POTS in terms of voice quality and widely covered line infrastructure. The Q-Box service employs iCS-P as its call server to enable necessary call control functions. The Q-Box service mainly features: A Q-Box terminal is integrated with functionality of POTS phone; hence it can be used as an ordinary POT phone. A Q-Box terminal can work as a home-coverage RF station, allowing PHS handsets under Q-Box coverage to access call service through PSTN while service charges are still on the accounts of these PHS subscribers. If a PHS handset is a permanent user of the Q-Box and makes calls through the QBox, the calls are charged to the PSTN number. A PHS handset goes freely and seamlessly between public wireless network and Q-Box signal coverage, enjoying two-mode featured service.
Roaming Services
The mSwitch system provides inter-domain PHS roaming services, including: Semi-auto roaming service Typically, an mSwitch subscriber when roaming to another domain can make emergency calls only. The semi-auto roaming service allows the subscriber to enable the roaming service in the visited domain and make any calls, or disable the roaming service and make emergency calls only. When the subscriber returns to the home mSwitch domain, the semi-auto roaming service is disabled automatically. Roaming service within an mSwitch domain, including: Roaming between iCS-Ps Roaming between CSCs/RPCs under an iCS-P
Roaming service between different mSwitch domains Roaming service between an mSwitch domain and the third party PHS domain Under the control of iCS-P, the mSwitch system provides the following handover service for PHS subscribers:
System Overview
mSwitch intra-domain handover, including Handover between iCS-Ps

mSwitch
Chapter 1 Overview
29
Handover between ASs under the same iCS-P Handover within an AS
mSwitch inter-domain handover Handover service between an mSwitch domain and a third-party PHS domain
Note: The following limitations apply to mSwitch intra-domain handover: (1) A call will be released if a handover takes place during the call ringing on the called party. (2) The iCS-P supports a handover when the calling party or the called party is on a normal conversation. Whether a handover is allowed when the calling party is listening to the ringback tone or an announcement depends on the setting of the Originating Connect Occasion parameter. On the iCS-P Configuration Management window, click [All \ IUA Related \ PHS \ PHS Service General Information] and select a value option for the Originating Connect Occasion parameter. To reject a handover on the calling party, select the Called Party Answered option. To allow a handover on the calling party, select one of other options. (3) For services involving multiple parties such as calling waiting, three-party calling, conference call and call forwarding, the iCS-P does not support a handover between different ASs or different iCS-Ps, if one party is held on the call. For example, if subscriber A is on a call with subscriber B, while subscriber C is held on the call, the call will be handled in the following ways: -- The call continues if a handover takes place on the subscriber B or on the subscriber C. -- The call is released if a handover takes place on the subscriber A.
NGN Applications
The mSwitch system supports the following service categories: Basic C4/C5 service Multiple signaling protocols Routing and digit analysis Supplementary services IP Centrex / Host IP Centrex service (applicable to UTSmart terminals) Value Added Services and intelligent services Fixed-Mobile Convergence solution mBOSS Operation and maintenance Regulatory service System redundancy and reliability
Basic C4/C5 Service
mSwitch
Basic voice service

System Overview
30
Chapter 1 Overview
Carrier selection Region-specific announcement, tone and dialing plan Multi-area code support Emergency call Battery reversal Fax (T.38/G.711 VBD mode) 64 kbps data service ISDN PRI PBX access R2 PBX access NDD/IDD blocking for PBX access ISDN BRI subscriber System level blacklist/whitelist ANI screening Forced call release for certain destination Long time duration call Support 100 digit Map entry configuration Codec: G.711 A-law/G.711 G-Law /G.723.1/G.726/G.728/G.729A/EVRC Echo Cancellation / Comfort Noise Generation / VAD Physical interfaces: E1, T1, STM-1 and OC-3
Multiple Signaling Protocols

The mSwitch5.6 system supports the following signaling protocols: ITU-T/ANSI MTP/ISUP/TUP (with country variants) SS7 ISUP variants (ITU-T Q.764, Q.767, ITU-T 97 version, ANSI ISUP) SS7 MTP/TUP ITU-T SCCP/CAP/CAMEL/INAP (CS1&CS2) GSM MAP IS-41 SIGTRAN SCTP/M2UA/M3UA/M2PA/IUA R2 Signaling (ITU-T) PRI Support ITU-T Q.921/ITU-T Q.931/5ESS PRI/Nortel DMS100 PRI Variants) V5.2 SIP (RFC3261) SIP-T/SIP-I (Q.1912.5) H.323
The mSwitch R5.6 supports the following media protocol:

System Overview
H.248/MGCP
mSwitch
Chapter 1 Overview
31
Feature: A-Link and F-Link support 64 kbps E1/56 kbps T1 signaling link, 2 M high speed link support SS7 COT reception (ITU-T/ANSI) Cyclic Redundancy Checking (CRC) Multi-point code support ISUP/SCCP screening SIP offer/answer mode for the dynamic codec negotiation (RFC3264) Q. 50 DCME support RFC2833 T.38 FAX
Routing and Digit Analysis

The mSwitch system provides flexible routing mechanism: Alternative routing Proportional routing Overflow routing Priority based routing Automatic re-routing Routing based on source and destination Re-routing based on congestion conditions Routing based on calling party category Scheduled routing
The mSwitch system provides power digit analysis and digit translation function: Digit analysis Number translation Number pre-analysis HEX (A, , D, #) digit analysis Invalid caller party number analysis Calling Party Category (CPC) modification
Supplementary Services

mSwitch
Abbreviated dialing Absent subscriber service Alarm Call Anonymous Call Rejection Automatic Callback
System Overview
32
Chapter 1 Overview
Automatic Recall Call Forwarding Unconditional Call Forwarding on No Response Call Forwarding on Busy Call Transfer Call Waiting Calling Line Identification Presentation Calling Line Identification Presentation Restriction Multi-party Calling (up to six parties) Do Not Disturb service Hotline Incoming Call Blacklist Interception of calls to an announcement International Call Blocking Malicious Call Identification Message Waiting Notification MLHG Multi-Line Hunting Group MLHG per subscriber based CID Display Multiple Number Distinctive Ringing Selective Call Rejection Speed Dialing (Speed dialing 8 & 30) Three-way Calling One Time Debarring Outgoing Call Barring Outgoing Call Blacklist Outgoing Call Whitelist Change of the supplementary service operation password initiated from subscriber terminals
IP Centrex/Host IP Centrex (applicable to UTSmart terminal)

System Overview
Customized Abbreviated dialing (dial one or two digits) Abbreviated Dialing (common) Attendant log on/log off Attendant Night service Auto Attendant Incoming call blacklist Outgoing call blacklist Call Forwarding on Busy
mSwitch
Chapter 1 Overview
33
Call Forwarding on No Response Call Forwarding Unconditional Call Pickup Call Transfer Call Waiting Calling Line Identification Presentation Calling Line Identification Presentation Restriction Conference (up to six parties) Call Hold Closed User Group Call Park Direct Inward Dialing Direct Outward Dialing Hotline Incoming Call Queuing Message Waiting Notification Music on-hold One Time Debarring Operator service Outgoing call whitelist Outgoing call barring Private Numbering Plan Three-way Calling Trunk Selection for outgoing call Wake-up service IP based Operator Console Call status monitoring Time Scheduled announcement iWAC (Wide Area Centrex) Grouping PSTN PBX, PSTN Centrex, NGN PBX, and NGN IP Centrex into one iWAC group PNP dialing within iWAC group PNP number CID display ESS manager supports ESS portal client creation/deletion/modification ESS manager supports ESS client operation privilege setting
Enterprise Self-service System (ESS) -
mSwitch
System Overview
34
Chapter 1 Overview
Value-added Service and Intelligent Service

Color Ring Back Tone Color Ring Copy iWAC (Wide Area Centrex) iNumber Local Number Portability and LNP call gapping Prepaid service Prepaid Calling Card service Toll Free and Toll Free gapping SMS (applicable to UTSmart terminals) Unified Message Service (UMS) USSD USSD Callback Video Conference service Virtual Roaming Voice Mail Service (VMS) Web Conference
UTSmart Softphone
Basic voice call (G.711 A-law/G.711 G-Law/G.729/iLBC Audio volume adjustment Video (MPEG4/H.263) Address book Terminal voice mail Short message DTMF Collection Supplementary service Intelligent dialing Logo / skin modification Customized Ring back tone Whiteboard/chat Log Trace Automatic System Upgrading Instant Message / Presence
Fixed-Mobile Convergence
System Overview
WiFi-GSM network integration WiFi Homed User Registration

mSwitch
Chapter 1 Overview
35
GSM Homed User Registration in mSwitch Incoming / outgoing calls (WiFi homed users) Incoming / outgoing calls (GSM homed users) VLR/HLR fault recovery FMC HLR supporting Visited Location Number assignment mode Additional GSM number management and assignment GSM-homed subscriber roaming at WiFi with voice mail services and MWI services Voice mail services and MWI services for WiFi-home subscriber at home domain and VPLMN GSM-homed subscriber roaming at WiFi with SMS service SMS service for WiFi-homed subscriber at home domain and VPLMN Call Forward Call Hold Handover from WiFi to MSC Handover from MSC to WiFi Single number over WiFi network and CDMA network CDMA/Wi-Fi roaming Incoming / outgoing calls over WiFi Incoming / outgoing calls in celluar Caller ID (CDMA home) Call Waiting (CDMA home)
WiFi-CDMA network integration
mBOSS
Subscriber service provisioning
mSwitch
Add/delete/resume/suspend subscriber Change subscribers attribute, such as enable or disable a supplementary service Modify subscribers service data Change subscribers information Query subscribers service provisioning data Subscriber data dumpling tool for migration Unified voice & data provisioning Bulk user data provisioning Bulk user data deletion Bulk user data modification Open SOAP or MSIP interface to the third party service provisioning system
CDR medication for postpaid subscribers

System Overview
36
Chapter 1 Overview
IVR
System Overview
C4 originating / terminating CDR generation Trunk incoming / outgoing CDR generation Automatic Message Accounting (AMA) CDR CDR mediation Support MTP message billing Prepaid procedure control Prepaid to support other networks such PSTN Supports prepaid and postpaid billing management Supports multiple rate in one program Change subscribers price plan Change subscribers account number Freebie points and credit services Query prepaid subscribers deposit in OBS Add or subtract subscribers deposit in OBS Unlimited price plan Multiple discount methods Flexible accounting formula Prepaid service Accounting Daily rent Statistics and reports Settlement payment Generate card number and password Provide card number and password data to manufacture scratch cards Provide card number and password authentication when subscriber uses the scratch cards Record the log of card usage, together with the information of which phone number is to be recharged Provide SS7/TDM connection to PSTN network Use a fixed access number to route calls to the IVR platform and set up voice connections Provide interactive voice announcement flow based on the service flow logic Collect subscribers DTMF inputs
Prepaid service center (PSC)
Online Billing System (OBS) for rating, billing, accounting and settlement
Card management
Customer self care system

mSwitch
Chapter 1 Overview
37
Upgrade tools
Operation and Maintenance

Topology management mSwitch
Network topology planning Network component status monitoring Topology map toolbar Network level functions navigation NE and NE group management functions navigation Network and service level configuration management Equipment and facility configuration Status polling and control operation or network resources Configuration data synchronization Batch configuration Software upgrade and download Real-time alarm / event detection and reporting History alarm / outstanding alarm browsing and monitoring Alarm filtering / suppression / severity redefinition Alarm acknowledgement Alarm clearing Proactive alarm management Troubleshooting guide Alarm synchronization Alarm notification via short message and email Performance task administration and setup Performance data collection and aggregation Friendly graphical performance data reporting Various user adjustable performance data reporting Performance analysis for trend analysis and network optimization Performance degradation TCA (threshold crossing alarm) NE group inventory management NE inventory management Card inventory management Circuit / link inventory NE process inventory management
System Overview
Configuration management
Fault management
Performance management
Inventory management
38
Chapter 1 Overview
Security management Log management TDM operation and maintenance Routing configuration and digit analysis configuration Traffic statistics for ISUP, TUP, R2 and PRI Signaling statistics for MTP, SCCP, ISUP, TUP messages Traffic statistics per trunk group, per destination, per route, per cause code Long time duration call monitoring and forced release Long time duration mediate CDR generation and aggregation Call tracing Signaling tracing Designated trunk call testing Trunk maintenance / monitoring Traffic overload control Call gapping and percentage based traffic control Performance TCA altering Board diagnosis and resource diagnosis VoIP QoS tagging configuration (TOS, Diffserv configuration) IP trunk call testing IP route maintenance Traffic statistics on SIP, H.323, and IP trunk DSP IP channel monitoring RTP QoS measurement (jitter, delay, packet send / receive) QoS degradation alarms based on measurement of delay, jitter End-to-end call tracing for SIGTRAN, MGCP, ISUP, and internal messages Cisco AS management Sun Server management Oracle DB management System log integration, real-time alarm, history alarm, event browser Performance management (CPU, memory, process, IP packet, UDP and ICMP) IP QoS monitoring
VoIP operation and maintenance -
Server/database management -
Service analysis tool Standard XML NBI interface for upper level NMS integration
Regulatory
System Overview
E911
mSwitch
Chapter 1 Overview
39
Lawful interception
System Redundancy and Reliability

Line card redundancy (1+1 or N+1 mode) Main processing card redundancy DSP media card redundancy AG/TG dual home to Softswitch Softswitch geographical redundancy SLR cluster load sharing DB geographical redundancy mBOSS/NMS geographical redundancy primary SLR&PSC configuration in iCS-P TS synchronization after IP connection recovery
New Features in mSwitch R5.4

mSwitch R5.x is a brand new softswitch core network that achieves full separation of service data from call control; network elements, such as call servers (iCS-P) and media servers (iMS/iUMG) are individual. The mSwitch R5.4 is backward compatible with mSwitch R2.x, mSwitch R3.x, mSwitch R4.x and mSwitch R5.x in terms of services and functions. It is implemented on the same hardware platform as earlier versions, and supports a seamless upgrade from an earlier version. mSwitch R5.4 provides the following new features: Provides Fixed-Mobile Convergence (FMC) solution based on ContinuityTM core network. The FMC solution, in single-number configuration, enables the convergence of WiFi network and GSM network. New supplementary services: Multiple Numbers with Distinctive Ringing (MNDR) Anonymous call rejection
For more information, see mSwitch Supplementary Service Provisioning Guide. E911 service IP Centrex service A wide range of dialing plans. For more information, see mSwitch Supplementary Service Provisioning Guide.
New Features in mSwitch R5.4.1

mSwitch R5.4.1 provides the following new features: SIM Card Roaming service solution which enables the provision of IDD and roaming service at a low cost. For more information, refer to the SIM Card Roaming Service Solution section.
System Overview
mSwitch
40
Chapter 1 Overview
The iCS-P adopts C4- and C5-level dual-home control mechanism. This mechanism allows a media GW to be managed by two iCS-Ps which function as MGCs. The two MGCs work in active and standby mode which enhances the fault tolerability of the system. The CN SNMS applies one set of configuration data to two iCS-Ps in dual-home configuration. For details, refer to iCS-P documents.

mSwitch R5.5 provides the following new features: Hardware features Equipped with a new clock board CK4102(E1) / CK4202(T1) to provide stratum 3E reference clock. RH3000, RH4000 and ZT5550 boards support 512 M Flash disk.
For more information, refer to mSwitch Hardware Platform User Guide. System features Offers Fixed-Mobile Convergence (FMC) solution to enable the convergence of WiFi network and GSM network. Besides the single-number configuration available in mSwitch release 5.4, this release introduces dual-number configuration (applicable to FMC environment only). For more information, refer to FMC Service Provisioning Guide. Supports India TEC SS7 signaling. The CN SNMS assigns user permissions for security management operations, including inquiry, fault management, performance management, call tracing, diagnosis, and administration. Users perform the operations allowed by the defined permissions. For more information, refer to Netman 2020 Core Network SNMS Operation Guide. Regular Wake-up service: Different from the casual wake up service that serves the subscriber on a one-time basis, regular wake up service serves the subscriber on a regular basis. It is available to NGN applications only. Anonymous Call Rejection: Allows the subscriber to reject incoming calls with Calling Line Presentation Restriction feature. It is available to NGN applications only. Automatic Callback: Allows the subscriber, when encountering busy signals, to enter feature activation codes and hang up. Once the line becomes idle, the system automatically connects the subscriber to the last number that the subscriber calls before activating the Automatic Callback feature, eliminating the need for redialing the number. It is available to NGN applications only. Automatic Recall: Allows the subscriber to return the last incoming call, no matter whether the last call is answered or not. It is available to NGN applications only. One-time Debarring (OTD): Allows the subscriber to place calls to restricted phone numbers by dialing features code, password and the desirable phone number. It is available to NGN applications only.
mSwitch
Service features -
System Overview
Chapter 1 Overview
41
Conference Call: It is available to NGN applications only. Services available to Centrex subscribers, such as Outgoing Call Barring (OCB), Call Waiting, Abbreviated Dialing, Hotline, and Regular Wake up service. Supplementary services and localized announcements for Philippine market.
For more information, refer to mSwitch Supplementary Service Provisioning Guide and Centrex Service Provisioning Guide.

mSwitch R5.6.5 provides the following new features: Hardware features Equipped with a new main control board RH3010, with the carrier board RH3000 delivering enhanced network interface electrical performance and memory access speed. For more information, refer to mSwitch Hardware Platform User Guide. Supports the configuration combination of PE3000 and RT6410. The iUMG interconnects with PBX using PRI or R2 protocol, to allow access of PBX POTS subscribers. For more information, refer to iUMG documents. The iCS-P communicates with a third party FHLR using SIP-I protocol. Offers FMC solution which enables GSM/WiFi dual-mode handsets to hand over between the GSM network and the WiFi network. It is available to FMC configuration only. For more information, refer to FMC Service Provisioning Guide. Offers FMC solution which enables the convergence of the WiFi network and the CDMA network. It is available to FMC configuration only. For more information, refer to FMC Service Provisioning Guide. Offers FMC Dual Attachment solution. It is available to FMC configuration only. For more information, refer to FMC Service Provisioning Guide. Provides a new FMC solution in mSwitch R5.6 Phase 5. The Fixed-Mobile Convergence (FMC) solution designed by UTStarcom enables the convergence of a WiFi-based VoIP network and the existing GSM network to provision abundant supplementary services and value-added services. This end-to-end solution takes advantage of the popularization of home wireless data access, and addresses the demands for expanded coverage of the GSM network. Compared with the earlier FMC solutions, this one enhances Dual Attachment and enlarges the rich service functions. It is available to FMC configuration only. For more information, refer to FMC Service Provisioning Guide. Supports Chile SS7 signaling. Supports data import to or export from the CN SNMS. The CN SNMS automatically creates backup configuration data on a daily basis. The backup data are valid in the CN SNMS server for a maximum of seven days.
System Overview
System features
mSwitch
42
Chapter 1 Overview
The CN SNMS supports configuration data synchronization from the network elements. This feature is available in mSwitch R5.6 Phase III. The CN SNMS provides an initial configuration data script to simplify initial setup configuration procedures. Supports separation of HLR from VLR. For the detailed description of VLR functions and configuration, refer to VLR (SG+TSVLR+SAU-V) User Guide. System disaster tolerance functionality. For more information, refer to Chapter 5 System Disaster Tolerance Solution. Implements lawful interception function: This release supports interception on short messages and location. The CN SNMS supports querying the serial number and agile number of PE4000 board and RH3010 board. Data synchronization mechanism of the TS network element. For more information, refer to TS/HLR/VLR System Overview. The iCS-P supports SIP protocol to identify the Domain Name Service (DNS) on the trunk side and access side. The iCS-P distinguishes CDRs according to whether the calls are successful. For information about CDR types, refer to iCS-P System Overview. GHLR product is launched in mSwitch R5.6 Phase 5. The GHLR (GSM HLR) is designed as the logical entity of the home location register in the GSM network, used to store the local subscriber location information, and responsible for data management authentication of the terminal subscribers. The GHLR integrates the Home Location Register (HLR), Authentication Center (AuC), and Equipment Identify Register (EIR) together, providing all basic HLR, AuC, and EIR functions that comply with the international GSM specifications, such as call management, location update, roaming area management, authentication, and equipment management. In addition, the system offers a graphical GHLR data management tool named GHLR Assistant for the carriers to manage the subscriber data, intelligent network service data, and authentication data that are saved in the GHLR database. For more information, see GHLR User Guide. The iCS-P supports GMSC applications. For details on the functions and configurations, refer to iCS-P System Overview and iCS-P Provisioning Guide. Supports Brazil protocol variants of ISUP protocol, R2 interface protocol and PRI interface protocol. The mSwitch R5.6.5 system introduces a new NE iSG 5.6 that is a largecapacity signaling gateway and supports multiple adaptation protocols. For more information, refer to iSG5.6 System Overview, iSG5.6 Installation Guide and iSG5.6 Provisioning Guide. The mSwitch R5.6.5 system can be managed by the periodic healthy checking tool. For details, refer to CN SNMS Periodic Healthy Checking Tool Operation Guide. The iCS-P provides access to the ISDN BRI interface through iAN-8000.
System Overview
mSwitch
Chapter 1 Overview
43
The iCS-P sets limits on the maximum count of number analysis. For details, refer to iCS-P System Overview. The iCS-P provides task monitoring function. The mSwitch R5.6.5 system provides a unified installation platform for Server type NEs, mBOSS NEs, VAS NEs, and CSS, allowing automatic installation and upgrade of the NEs. For more information, refer to mSwitch Servers Installation Guide. Servers of the mSwitch system are running over SUN Solaris 10 operating system on both Sparc and X86 platforms. At this stage, mSwitch R5.6.5 applications and mBOSS 5.0.3 applications have been tested on the Sparc platform, but only some of mBOSS 5.0.3 applications have been tested on the X86 platform. For more information, refer to mSwitch Servers Installation Guide. Outgoing call barring (OCB): Forbids the subscriber to place calls under predefined call categories, with a maximum of 30 categories allowed in the mSwitch system. The restricted call categories depend on the Restriction Codes in the subscription window. Incoming call barring (ICB): Rejects all incoming calls to the subscriber, but allows the subscriber to place outgoing calls normally. It is available to NGN applications only. Multiline Hunt service (MLH): Includes multiple phone subscribers in an MLH group (MLHG). Upon reception of an incoming call to the pilot number of the MLHG or a member in the MLHG, the MLH service triggers a search for an idle phone in the group and routes the call to the idle phone. It is available to NGN applications only. Call back on busy: Allows the subscriber, when encountering busy signals, to dial the feature activation code and hang up. When the line becomes idle, a call is returned to the subscriber. The subscriber picks up the phone, and the original called party rings. This feature is available to PHS applications only. Three-way service: The subscriber can be the calling party or called party. It allows the subscriber to invite a third party to join the on-going two-way call. Services available to Centrex subscribers, such as Call Park, Call Hold, Outgoing Trunk Selection, Attendant Night Service, One-time Debarring (OTD), Multiline Hunt Service (MLH), Centrex Group Outgoing Black List, Forward to PSTN, and Centrex Group Abbreviated Dialing. Operator attendant function: A new product named iOperator2000 is available. For more information, refer to iOperator2000 User Guide. The iCS-P supports the iWAC service. For more information, see iWAC Service Provisioning Guide. Supports Multiple Numbers with Distinctive Ringing (MNDR) Being the CRBT front-end processor, the iCS-P supports CRBT duplication function and Advertisement CRBT service.
Service features -
mSwitch
System Overview
44
Chapter 1 Overview
Implements the function of nearest connection of emergency calls by grouping the calling numbers. The FMC solution supports Short Message Service, Voice Mail service, and Voice Mail Notification service. For more information, refer to FMC Service Provisioning Guide. In an mSwitch system earlier than release 5.6 P4, the iCS-P does not support the semi-auto roaming service. It is supported in the mSwitch release 5.6 P5. Toll Free service is supported in the mSwitch R5.6 Phase 5. (For service description and provisioning, see Toll Free Service Provisioning Guide.) The Centrex service solution supports setting Attendant Night service number by the operator and activating the Attendant Night service from the terminal. The solution also supports customization of the Auto Attendant announcement. (For more information, see Centrex Service Provisioning Guide.) The mSwitch R5.6 Phase 5 supports the video conferencing service system which employs video technology and IP data communication technology and establishes the visual communication between two or more sites over the IP network to achieve the exchange of graphics, voice, and data. (For more information, see iWeSee Service Provisioning Guide.)

mSwitch R6.0 provides the following new features: Hardware features The system main control boards and peripheral processing boards adopt 1 GB Compact Flash to replace the earlier 512 MB Flash Disk. The applicable board groups include RH3010+HS3010, RH3000+HS3002, RH3000+HS3001, RH4000+RT4000, RH4010+RT4010, AP3001+RT7100, and AP3011+RT7110. The media processing boards PE4000 series has a new member PE4241, which is composed of one carrier board PE4701 and two daughter boards PE404. One daughter board is used to provide VoIP voice codec processing. The other one is used to provide media services such as announcement playback, conferencing, and color ring back tones.
For more information, refer to mSwitch Hardware Platform User Guide. System features The mSwitch system supports multiple time zones and daylight saving time (DST). The system supports marking DSCP flag at the IP packet header of the signaling messages and OAM messages. DSCP is the acronym of Differentiated Service Code Point. IP messages with ToS byte marked with DSCP flag have higher priority in network transmission. This is helpful in improving the Quality of Service of the system. (For more information, see iCS-P Provisioning Guide.)
mSwitch
System Overview
Chapter 1 Overview
45
The system provides a C-SG dual-home Geographical Redundancy (GR) solution. When there is the C-SG deployed in the network instead of iSG to fulfill the signaling conversion function, the C-SG can work in the SEP mode or STP mode. The system supports dual-home of M3UA links between the C-SG and the iCS-P/CPS2100 and dual home of M2UA links between the iUMG and the C-SG. Each C-SG has two M3UA links to two iCSP/CPS2100 devices. One link is active, and the other is a redundancy. When a fault occurs to the active iCS-P/CPS2100 or the active M3UA link, the CSG switches to the redundancy M3UA link to make communication with the redundancy iCS-P/CPS2100. In addition, each iUMG has two M2UA links to two C-SG devices. One link is active, and the other is a redundancy. When a fault occurs to the active C-SG or the active M2UA link, the iUMG switches to the redundancy M2UA link to make communication with the redundancy C-SG. (Dual-home function at the M3UA link layer is applicable to mSwitch R5.4.1 and later. Dual-home function at the M2UA link layer is applicable to mSwitch R6.0 and later. For more information, see mSwitch GR Solution User Guide.) The system provides a CPS2100 dual-home Geographical Redundancy (GR) solution. When the CPS2100 is used to provide standard MAP/CAP/INAP/IS-41 protocols to achieve the interaction between the upper-level applications and the third party network, the system supports dual-home between the CPS2100 and the iCS-P. In cases of faults or failures, the system supports protocol switchover/switchback and application switchover/switchback to ensure high reliability. (For more information, see mSwitch GR Solution User Guide.) The system offers AG-based traffic measurement, that is, the system can make traffic measurement according to the calls taking place on a specified iAN-8000. (This function is only applicable to NGN applications. For more information, see iCS-P Performance Management User Guide.) The system offers traffic measurement based on the specified origination code/destination code/PRI interface, including the following types of traffic measurements: measurement of calls from a designated origination code group or prefix through a designated PRI interface, measurement of calls to a designated destination code or prefix through a designated PRI interface, and measurement of calls from a designated origination code group or prefix through a designated PRI interface to a designated destination code or prefix. (For more information, see iCS-P Performance Management User Guide.) The system offers traffic measurement based on the specified PRI trunk, that is, measurement of the calls from and into the specified PRI trunk(s). The system collects the call traffic using PRI protocol(s) for up to three segments of PRI trunk IDs. (For more information, see iCS-P Performance Management User Guide.) The system enhances traffic measurement based on supplementary services and valued-added services. (For more information, see iCS-P Performance Management User Guide.)
mSwitch
System Overview
46
Chapter 1 Overview
The system enhances the iCS-P call trace tool. (For more information, see iCS-P Call Trace Tool Operation Guide.) The enhancement involves two aspects: a Enhancing the trace task object management function: The system provides a function to create a call tracing tree including all possibly involved devise and boards to support the entire process of the traced calls and obtain all call-related information. b Enhancing the message resolution library file management function: The system supports the call trace tool to manage several versions of message resolution library files. For different versions of call device, the system allows import of the appropriate resolution library for call tracing purposes.
The system supports remote upgrade of mSwitch R6.0 network elements in the mSwitch 5.x management domain by using FTP. Such network elements include iCS-P, iUMG, iMS, C-SG, and iSG. (For more information, see Netman 2020 Core Network SNMS Maintenance Guide.) The system further enhances the network management functions, for example, supporting and optimization of some GUIs and network element restart from the CN SNMS. In addition to the installation of sharing chassis with iUMG or iCS-P, the system also provides a solution of installing the C-SG in a stand-alone chassis. The system supports several C-SG network elements sharing the same BasicGW chassis to achieve integrated management on all C-SG devices in the network. Alternatively, this installation is recommended if the board slots in the iUMG/iCS-P chassis are not enough. BasicGW chassis is a 4U or 14U chassis with only MPU boards inserted. (For more information, see C-SG User Guide.) The system provides PRI and R2 trunk subscriber management functions through the Subscriber Application Management (SAM) module of the mBOSS. In the mSwitch system, the traditional PBX trunk subscribers accessed to the iUMG by using PRI and R2 are considered as a group for management purposes to achieve integrated management on all such trunk subscribers. For example, the system makes a unified billing rule for them, and defines the same call permissions and supplementary services. The system allocates a virtual number for the trunk subscribers for unified billing usage, however what is involved in the calls is the real number of the members. (For more information, see mSwitch-SAM Operation Guide and iCS-P System Overview) The system supports call transfer service for calling subscribers. (For more information, see mSwitch Supplementary Service Provisioning Guide.) The system supports customized welcome announcements played to the calling subscribers when they are originating calls to Multiline Hunting Group subscribers. The system takes advantage of the announcement management server CAMS with the cooperation from the SAM to implement the upload and management of the customized announcements. (This
mSwitch
Service features -
System Overview
Chapter 1 Overview
47
function is only applicable to NGN applications. For more information, see SAM (NGN) Operation Guide.) The system provides mSwitch products to be used in the legacy VoIP network to construct the Intelligent Network to provision such Intelligent Network services as CLI Screening service, Prepaid Telephony service, and Advanced Freephone service. Being C4 network, the mSwitch gets access to the current VoIP network of the carrier to construct the Intelligent Network, where the combination of iCS-P+CPS2100 in the mSwitch system offers SSP functions. The SCP can adopt the SCP product of UTStarcom or other third-party products. The standard INAP protocol is used for communication between the mSwitch SSP and the SCP. (For more information, see CLI Screening, PPT, and AFS Service Provisioning Guide.)
mSwitch
System Overview
Typical Applications
This chapter describes networking models of the mSwitch intended for different applications.
Tandem-Level Networking Solution

The mSwitch provides carriers with Class 4 switching functions by incorporating different softswitch-enabled functional modules, such as CS, TG, SG and MGC. As shown in the following figures, to offer a C4 solution, the mSwitch system functions as a gateway office to interconnect with PSTN or third party networks, or as an SSP to trigger IN services. Figure 2 Class 4 Solution Provided by the mSwitch
PSC CSS SAM IVR OBS
mBOSS
Operation Support Layer

Service Parlay- GW Platform
API
Parlay AS
3rd Service Platform
Service Provisioning Layer

mSwitch - CN iMS
SNSP MEGA CO MEGA CO MEGA CO
TS
iUMG
SS7
iUMG
PSTN iCS-P
M3UA
Tandem Layer
PHS
SG
VoIP
3G
Access Layer
When functioning as a gateway office interconnecting with PSTN network, the mSwitch system should include call server (iCS-P), signaling gateway (iSG), trunking gateway (iUMG), transaction server (TS), and multi-service business operation support system (mBOSS), core network management system (CN SNMS). The iUMG supports H.248 and MEGACO protocols. The iSG supports SIGTRAN and SS7 signaling conversion. Interfaces to the PSTN network support PRI, ISUP, TUP, R2, and TCAP/INAP protocols. Supports MAP, CAP, INAP, and IS41 protocols to provide intelligent services.
System Overview

mSwitch
50
Chapter 2 Typical Applications
When providing a gateway office interconnecting with third party VoIP networks, the mSwitch system should employ iCS-P which functions as the office gateway to connect with the third party call server. The interface between the iCS-P and the third party call server supports H.323 and SIP-T/SIP-I protocols. When providing access system for Parlay-enabled IN service provisioning platform, the mSwitch system should include iCS-P, iUMG, iSG, TS, mBOSS and NMS. The iCS-P communicates with Parlay GW using SIP-T or SNSP. The Parlay GW communicates with Parlay APP through standard API. In this application scenario, the types of terminals are not a matter of concern; the Parlay platform can offer services to different types of terminals (including PSTN phones) through the mSwitch system, only if the terminals are accessible to the iCS-P. At present, UTStarcom provides the following Parlay-enabled services: iNumber, VPN, Q-Box, multimedia conference, and WAC service. When providing service switching point (SSP) function, the mSwitch system should include iCS-P, iSG, TS and NMS. The iCS-P, featuring service switching function (SSF), can work as a service trigger point to provide IN service triggering function for a third party service control point (SCP). The iSG interfaces with SS7 network to complete protocol conversion between M3UA/SCTP/IP and MTP3/MTP2/MTP1.
Access of Multiple Terminal Types

The mSwitch system supports a variety of end users, including PHS users, IP terminal users, V5 POTS users, and i-AN8000 users. Figure 3 illustrates the C5 solution provided by mSwitch: Figure 3 Class 5 Solution
iUNG SG TS
MEGACO M3UA SNSP
mSwitch iUMG
iCS-P
MEGA CO MEGA CO
iMS
G.711/G.723/G.729
PRI
V5
i AN-2 000
PHS
PHS
SIP
SIP
H.323
MGCP
MGCP
iAD
MGCP /H.248
i AN-20 00
Net Edge 2024AL
R PC
iCSC RPC V5 AN PBX
UTSmart SIP H.323 PC phone Phone Phone PHS
MGCP Phone POTS

Signaling Data
iAN-8000
CS/RP
In this solution, the mSwitch system works in the access layer. It provides SIP interfaces to connect with C4 equipment by different equipment vendors.
51
Typical Solution to PHS Network

This section discusses a typical networking solution to mSwitch-based PHS application. In this solution, the core network consists of iUMG, iCS-P and iSG. Other supporting components (such as NMS and mBOSS), as well as the service provisioning platform, are the same as those in a C4 solution. An iUMG in this solution plays two roles. It functions as an access gateway (AG) to access the PHS subscribers to the core network. It also functions as a trunk gateway (GW) to process the voice channels between the interconnected PHS network and PSTN network. An iCS-P in this solution can also play two roles: working as a call server in access layer to process PHS calls, or as a C4 gateway to enable the tandem functions in a complicated network environment. An iSG in this solution is used to implement the conversion between M3UA/SCTP/IP protocol in an IP network and MTP3/MTP2/MTP1 protocol in a PSTN network, so that the signaling carried over different networks can interwork.
Interconnection between PHS Terminals

Figure 4 illustrates the interconnected media and signaling streams between two PHS terminals. When a PHS terminal calls another PHS terminal, the call signaling goes through the iUMG serving the caller to the iCS-P which performs signaling control; the media stream is transferred directly between the iUMGs concerned. If the two PHS subscribers are served by the same iUMG, the media stream will be processed within the iUMG. Figure 4 Interconnection between PHS Terminals in mSwitch Network
iCS-P
SIP-T
iCS-P
M3UA
iSG
iUMG(AG)
MAGACO
mSwitch
MAGACO
iUMG(AG)
iUMG(TG)
ISUP E1
E1
E1
SS7 RF RF PSTN
mSwitch
System Overview
52
Interconnection between PHS Terminals and PSTN Terminals

Figure 5 illustrates the media and signaling stream between two PHS terminals. When a PHS subscriber calls a PSTN subscriber, the call signaling goes through the iUMG serving the caller to the iCS-P. The iCS-P, knowing by number analysis that the callee is a PSTN subscriber, sends the call signaling to the iSG. The iSG routes the signaling to the PSTN gateway office, and the PSTN gateway office locates the called party and completes signaling interaction. The media stream is transferred from the iUMG in trunk layer to the iUMG in transmission layer (TG) before it reaches the PSTN network. In actual networking, the TG and AG can be implemented by one iUMG for cost consideration. Figure 5 Interconnection between PHS Terminals in mSwitch Network and Terminals in PSTN
iCS-P
SIP-T
iCS-P
M3UA
iSG
MAGACO
iUMG(AG)
mSwitch
MAGACO
iUMG(AG)
iUMG(TG)
ISUP E1
E1
E1
E1
E1
SS7 RF RF PSTN
Typical Solution to VoIP Network

This section discusses a typical networking solution to mSwitch-based PHS application. In this solution, the core network mainly consists of iUMG, iCS-P, iMS and iSG; other supporting components (such as NMS and mBOSS), as well as the service provision platform, are the same as in C4 solution. An iCS-P in this solution could play two roles: working as a call server in access layer to process VoIP calls, or as a C4 gateway to enable the tandem functions needed in a network environment with complicated topologic structure. The iMS in this solution mainly manages media resources in the mSwitch system, completing tasks such as announcement playback and number receiving. The iUMG in this solution works as a TG (trunking gateway) to process the media flow between VoIP network and PSTN network.
53
The iSG is a signaling gateway; it is mainly used to complete the protocol conversion between IP network and PSTN network, namely the conversion between M3UA/SCTP/IP protocol and MTP3/MTP2/MTP1 protocol, so as to enable the interconnection between the two types of networks.
Interconnection between VoIP Terminals

Figure 6 illustrates the media and signaling flow between two VoIP terminals. When a VoIP terminal calls to another VoIP terminal, the call signaling is processed by an iCS-P, which works as a call server to complete call control, number analysis, routing and so on; the media flow is transferred end-to-end, directly between the two terminals. The iMS, being controlled by the iCS-P, provides media services requested, such as announcement playback, number receiving, media resource needed in conference, and so on. Figure 6 Interconnection between VoIP Terminals in mSwitch Network
iCS-P iMS
MAGACO M3UA
iSG
MAGACO
mSwitch
IP IP IP IP
iUMG(TG)
ISUP
IP
E1
SBC
iAD VoIP VoIP
SS7 PSTN
Interconnection between VoIP Terminals and PSTN Terminals

Figure 7 illustrates the media and signaling flow between two PHS terminals. When a VoIP subscriber calls to a PSTN subscriber, the call signaling processed by an iCS-P, which, knowing by number analysis that the callee is a PSTN subscriber, sends the call signaling to the iSG; the iSG routes it to the PSTN gateway office for further routing and processing. When the system needs to inform the caller (VoIP subscriber) of the callees status (being busy, for example), the iMS plays related announcement to the caller. The media flow is to be transferred from the iUMG in access layer (AG) to the iUMG in transmission layer (TG) before it can reach the PSTN network. In practice, the TG and AG could be implemented by one iUMG for cost consideration.
mSwitch
System Overview
54
Figure 7 Interconnection between VoIP Terminals in mSwitch Network and Terminals in PSTN
iCS-P iMS
MAGACO M3UA MAGACO
iSG
mSwitch
IP IP IP IP
iUMG(TG)
ISUP
IP
E1
SBC
iAD VoIP VoIP
SS7 PSTN
System Overview
mSwitch
Typical Service Solutions
This chapter introduces several typical service solutions that can be implemented in mSwitch system through different networking configurations.
Q-Box Service Solution

Q-Box is a service provision solution launched by UTStarcom to reinforce the popular PSTN and the prevailing mSwitch PHS services, hence to satisfy PHS carriers as well as subscribers. This solution achieves a better coordination between PHS network and softswitch network. It is not only applicable to UTStarcoms PHS network but also to third party PHS networks. This solution uses Q-Box terminal, a two-in-one customer premise equipment (CPE) featured with POTS + PHS Home Station functionality, as well as Q-Box service logic based on the new-generation switching platform. The Q-Box solution has the following advantages: Significantly expanding wireless PHS network coverage, offering a cost-effective, ease-to-implement wireless solution for poorly signaled environment. An indoor PHS could work as the cordless phone of a Q-Box terminal to access service via PSTN or VoIP network. An outdoor PHS or an indoor PHS suffering busy line can access service via public PHS network.
Allowing smooth handover for PHS subscribers between PSTN, VoIP, and PHS networks at indoors or outdoors. Delivering Broadband+Wireless feature, allowing PHS subscribers use Q-Box terminals Voice over ADSL channel or VoIP uplink channel, so as to achieve three party call wait among PHS, POT and VoIP phones, hence increased call completion rate (available in future versions). O-Box terminal can provide ADSL access support, even wireless ADSL access support (available in future versions).
A Q-Box terminal is a piece of intelligent customer premise equipment (CPE) integrated with PHS HomeStation, POTS phone, which allows PHS subscribers to access quality wireless PHS service, wireless/lined broadband service, and so on. Q-Box terminal features: Integrated with functionality of POTS phone. Integrated with a HomeStation that delivers functionalities to enhances the access capability of PHS handsets: A PHS handset can normally access PHS network outdoor, working as an ordinary PHS handset. A PHS handset within the service coverage of an indoor HomeStation can login to the HomeStation, hence is bound to be a cordless POTS served by the HomeStation. In such a case, the HomeStation routes outgoing and
System Overview
mSwitch
56
Chapter 3 Typical Service Solutions
incoming calls to PSTN network if the PSTN channel is not busy, otherwise it routes these calls to public PHS network. A Q-Box can simultaneously bind 99 PHS handsets, providing quality wireless access for the handsets. A PHS handset can be bound with a QBox in two modes: permanent binding (10 handsets at most) and temporary binding (89 handsets at most). The permanent binding is intended for family members, the temporary binding is intended for visitors. A call is made in different ways under different binding modes, and is charged differently.
Q-Box terminal can allocate an extension number (abbreviated number) to each of the handsets bound according to the order they are bound, so as for other phones to call it. In addition, the handsets bound to a Q-Box can call one another via the abbreviated numbers allocated. A PHS handset can login to HomeStation, and be set to wait for calls from both PHS and PSTN networks, or wait for only those calls from PHS network, or calls routed by Q-Box. When the Q-Box terminal is powered out, it can still relay PSTN service, although unable to provide PHS service for handset.
The Q-Box service features the following: A PHS handset can normally access to public PHS network outdoor. When bound to a Q-Box terminal, a PHS handset works a cordless phone: When making a call, the handset first access to PSTN or VoIP network via the Q-Box terminal; if the PSTN or VoIP network is available, the call will go over the PSTN or VoIP network; if the PSTN or VoIP network is busy, the call is routed to the public PHS network. When a call is coming in, it first goes through PSTN to the POTS port on the Q-Box terminal; if PSTN channel is busy, it goes through IP network to the VoIP port on the Q-Box terminal; if both PSTN and VoIP channels are busy, it goes via public PHS network to reach the PHS handset.
A PHS handset can access short message service via VoIP channel or public network. A PHS handset could be bound with Q-Box in two modes: permanent binding and temporal binding. The outgoing calls by a handset in permanent binding mode are charged under the PSTN or VoIP service account of the Q-Box subscriber, while those by a handset in temporal binding mode are charged under the callers own service account.
Figure 8 illustrates a solution to Q-Box service. In this solution, the Parlay GW and the Parlay APP forms the service provision platform that manages the Q-Box service logic needed in service provisioning for subscribers in the mSwitch network or those in third party networks; the iCS-P, iUMG and iSG forms the switching platform that triggers Q-Box services.
System Overview
mSwitch
57
Figure 8 Solution to Q-Box Service

Parlay-GW Service Platform
SNSP API
Q-Box AS
SNSP
mSwitch Domain
iCS-P
iUMG
SG
iCS-P
iUMG
iSG
VLR
TS
SNSP
SIP-T/IP trunk ISUP MAP
iCS-P OSS
MEGACO
iMS
3rd PHS network
MSC
HLR PSTN(SS7) Network
NMS
PHS Access Network
POTS
Q-Box
The solution given in Figure 8 is a Q-Box solution based on distributed SSPs; the switching platform for service triggering has to be deployed in each of the networks involved. The Q-Box service can also be implemented using a centralized SSP. In a centralized SSP solution, the switching platform and the service platform could be deployed as a multi-network enabled layer, with the central iCS-P connected to the call servers in the involved networks, namely the service triggering is implemented by a centralized open switching platform. Such a solution delivers simplified network topology and reduced investment.
Centrex Service Solution

Central User Private Branch Exchange Service (Centrex Service) provides virtual and enhanced Private Branch Exchange (PBX) functionality. It is an enterprise-oriented service provided by telecom carriers. Subscribers in a Centrex group can use not only the standard features available to normal telephone subscribers, but also the features available to PBX subscribers. In addition, there are optional features specific to Centrex subscribers. The mSwitch softswitch system developed by UTStarcom offers an overall Centrex service solution. Subscribers in the mSwitch system can form a Centrex group that has its private numbering plan (PNP). Each member in the Centrex group has a PNP number and an ordinary directory number (DN). Subscribers in the Centrex group make intra-group calls with PNP numbers. To call an external line, the Centrex subscriber places a Direct Outward Dialing (DOD) call by dialing a prefix followed by the called number, or places an outgoing call with the aid of the operator. Similarly, a
58
subscriber outside the Centrex group places a Direct Inward Dialing (DID) call to a Centrex subscriber, or places an incoming call with the aid of the operator. Centrex service in the mSwitch system has the following characteristics: Centrex group A Centrex group is the basic unit of Centrex subscribers. Each group functions as if it owns a PBX, and has its PNP. Each Centrex group has a group telephone number (GTN) that identifies the Centrex group. The GTN is an ordinary directory number (DN). A subscriber outside the Centrex group can reach a Centrex subscriber by dialing the GTN and having the call transferred to the desired party through an operator. Subscribers in a Centrex group may belong to different iCS-Ps that, however, must be in the same domain. Centrex subscriber categories A Centrex subscriber can be a PHS subscriber, SIP terminal, H.323 terminal, H. 248 terminal, MGCP terminal, POTS terminal on IAD, MGCP iAN-8000 subscriber, and V5 iAN-8000 POTS subscriber. Except the H.323 terminal, other categories can register as Centrex operator. Two phone numbers for a Centrex subscriber A Centrex subscriber has an ordinary DN and a PNP number. PNP numbers are typically used to make intra-group calls. A subscriber outside a Centrex group can make DID calls to Centrex subscribers, except closed team subscribers. Operator feature The operator transfers intra-group calls, or calls between Centrex subscribers and PSTN subscribers. A normal Centrex subscriber can register or deregister operator functionality, and change the operator password dynamically. A Centrex group can have up to ten operators. Traffic sharing is supported among the operators. Auto Attendant feature With the Auto Attendant feature activated, a calling party that places a call to the Centrex GTN number hears an announcement, for example "Thanks for calling xxx company. Please dial the extension number..." The system collects the number of the calling party through DTMF mode, treats the calling number as a PNP number, and routes the call to the destination. Centrex team A Centrex group can be divided into multiple Centrex teams. Numbering rules of the Centrex group apply to all teams in the group. In addition, more functions are attached to the team. A Centrex subscriber may not belong to any team, or belongs to one team only. Subscribers in a team may belong to different iCS-Ps.
59
Centrex teams fall into two categories: normal teams and closed teams. A normal team subscriber can call other team subscribers in the same Centrex group. A closed team subscriber can only make internal calls within the closed team. To call a subscriber outside the closed team, the closed team subscriber must call the operator first, and have the call transferred by the operator. Similarly, to call a closed team subscriber, a subscriber outside the closed team must first call the operator, or dial GTN of the closed team and have the call transferred by the operator. PHS Centrex subscriber roaming When PHS Centrex subscribers are roaming within their home domains, they can use Centrex features as they do in the home call server. PHS Centrex subscribers roaming outside home domains can no longer use standard Centrex services. However, the subscribers are still normal phone subscribers on the call server. They use the dialing plan and supplementary services, and perform operations on the terminals in the same way as normal phone subscribers do. When a PHS subscriber that has registered as operator leaves the home domain, the operator functionality is deactivated automatically. But a subscriber roaming outside the home domain cannot actively deregister the operator functionality; this must be done before the roaming. As long as the operator functionality is not deregistered, the system continues to route calls to the operator. Other features available to the PHS Centrex subscriber are the same as those available to a normal Centrex subscriber roaming outside the home domain. Centrex service billing The mSwitch system provides flexible billing for Centrex intra-group calls. Currently, Centrex service billing is available to postpaid subscribers only. But the mSwitch system supports inquiries into late payments for charged special service calls (for example calls to information stations). The mSwitch system supports the nearest termination of Centrex subscribers special service calls.
The mSwitch system provides the following standard Centrex features: Intra-group call: Centrex subscribers make intra-group calls with PNP numbers. Direct Outward Dialing (DOD) call: Centrex subscribers directly call subscribers outside the Centrex group, without the assistance of the operator. Direct Inward Dialing (DID) call: subscribers outside a Centrex group directly call Centrex subscribers, without the assistance of the operator. Call Transfer by Operator: the operator transfers outgoing calls from Centrex subscribers, or incoming calls from external lines. Call Pickup In terms of pickup privilege, call pickup falls into two categories: intra-team pickup and inter-team pickup. Intra-team pickup: the pickup privilege is defined as Team. It allows pickup of calls to the team only.
System Overview
mSwitch
60
Inter-team pickup: the pickup privilege is defined as TeamAndGroup. It allows pickup of calls to the Centrex group.
In terms of pickup objects, call pickup falls into the following two categories: coteam pickup and designated pickup. Centrex Outbound Call Restriction: allows a Centrex subscriber to only make intra-group calls by defining call limitations. This feature is not available in regions where RC selection applies. Centrex Outgoing Call Blacklist: set a blacklist based on the GTN of a Centrex group; the blacklist is applicable to all subscribers in the Centrex group. At the same time, blacklists on individual Centrex subscriber basis are still effective. Call Forwarding (including Call Forwarding no Reply, Call Forwarding not Reachable, Call Forwarding on Busy, and Call Forwarding Unconditional): The forwarded-to number can be the PNP number of a Centrex subscriber, an ordinary DN or a mobile phone number. For the latter two cases, an outgoing prefix must be appended to the forwarded-to number. Callback: the Centrex subscriber can press the Redial button or Send key (on PHS handsets) to call back an original calling number from outside the Centrex group, without re-entering the number. The original calling number must be displayed as follows on the Centrex line: outgoing prefix + ordinary DN.
In addition to the standard Centrex features, the mSwitch system provides the following special Centrex features: Unified Centrex Any subscriber under the iCS-Ps control can subscribe as a Centrex group member, including a PHS subscriber, V5 POTS subscriber and IP terminal subscriber (SIP terminal, MGCP terminal, H.248 terminal and H.323 terminal subscriber). The iCS-P enables Centrex calls between different types of subscribers. Operator overriding Do Not Disturb/Absent service This feature allows an operator to make an intra-group call to a Centrex subscriber even if the subscriber has activated Do Not Disturb service or Absent service. Operator traffic load sharing and queuing feature The system provides automatic call distribution (ACD) feature to support load sharing among operators. When no operator is available for an incoming call, the call is placed to a queue and music is played to the calling party. When the operator is available, music stops and the call is connected to the operator. By default, a queue contains a maximum of 50 calls; additional calls will be released. Distinctive ring tones for intra-group/out-group calls The called party hears long rings for incoming calls from external lines, and short rings for intra-group calls.
System Overview
mSwitch
61
Customized CLIP display for Centrex outbound calls On the Subscriber Application Management system (SAM), the carriers can define to display Centrex calling numbers in one of the following ways: GTN GTN + PNP number Ordinary DN
Attendant Night Service The attendant night service allows the absence of Centrex operators at the predetermined period of time, for example, at night. When the operator is absent, all incoming calls to the operator are transferred to a preset night service number. Every Centrex group can have a night service number that is designated by the SAM operator. The night service number must be a PNP number in the Centrex group. Only the operators can activate or deactivate the attendant night service. When activated, the attendant night service takes precedence over other called party-based features, for example call transfer, call park and call hold features.
Call Park The call park feature allows a subscriber in a call park subscriber group (CPSG) to park and retrieve a call on a second phone set. The call park feature provides the following functionality: The phone set where a call is parked can be used to receive or place a second call. A parked call can be retrieved from any phone set in the CPSG or from the phone set where it is parked. When a parked call is not retrieved within the preset time, it will be reconnected to the phone set where it is initially parked. The call will be released after three attempts of reconnection but is still not retrieved. A calling number can only be parked once at a time. A Centrex group supports up to 100 concurrent parked calls. The number of calls to be parked is configurable. The subscriber that parks the call is charged until the release of the parked call. The subscriber that retrieves the parked call is charged at a normal call rate. The call park feature cannot be subscribed along with call transfer, call waiting, three-way calling, and/or call hold feature(s).
Outgoing trunk selection This feature enables the system to route calls to appropriate trunks based on the prefixes entered by Centrex subscribers.
Multiline hunt service Multiline Hunt (MLH) service is a general supplementary service. It combines multiple phone subscriber groups into an MLH group (MLHG). Upon the reception of an incoming call to the pilot number of the MLHG or a member in the
mSwitch
System Overview
62
MLHG, the MLH service triggers a search for idle phones in the group and routes the call to an idle phone. Subscribers in an MLHG must be under the same category, for example, an MLHG cannot mix Centrex subscribers with normal phone subscribers, nor mix Centrex subscribers in one team with subscribers in other teams. A Centrex subscriber belongs to one MLHG only. A Centrex group can have up to 5,000 MLHGs. MLHG configuration procedures for Centrex subscribers are the same as those for normal subscribers, except a few parameters. For more information of the operational procedures, refer to mSwitch Supplementary Service Provisioning Guide. This document focuses on the following special parameter settings for Centrex subscribers. The GTN of a Centrex group cannot be defined as the pilot number of an MLHG. When an ordinary DN of a Centrex subscriber has been defined as the pilot number, a call to the ordinary DN triggers the MLH service. Beside, a call to the PNP number of the subscriber also triggers the MLH service. A Centrex subscriber is added to an MLHG with the ordinary DN, and a call to the ordinary DN triggers the MLH service if the called party is not available. Besides, a call to the PNP number of the subscriber also triggers the MLH service. When Centrex subscribers make calls within an MLHG, applicable number display rules are a combination of those applied to both Centrex groups and normal MLHG subscribers. For more information, refer to mSwitch Supplementary Service Provisioning Guide.
iNumber Service Solution

The iNumber is the short for Unique Number, a service that allows subscribers to use a unique number to access a network, and to cross multiple networks, or simply speaking, binds a service number with multiple terminals. The iNumber is a callee-intended VAS. Its basic function is to correlate all the communication numbers a subscriber owns with one specified number, so as to achieve the ever-accessibility to the subscriber when as a callee. Number Correlation Plan The service numbers in iNumber service include a master number and several correlated numbers; these numbers must all be real service numbers. The subscriber owning the master number must be an mSwitch subscriber already registered iNumber service; an mSwitch subscriber could be a PHS user, VoIP terminal user, UTSmart PC Phone user, or POTS user. Subscribers owning correlated numbers could be PSTN subscribers, mobile subscribers, or mSwitch subscribers. Typically, one master number correlates with multiple correlated numbers.
System Overview
Ringing Selection
mSwitch
63
Typically, there are two types of ringing selections for iNumber master number and correlated numbers: group hunting and group ringing. Forwarding Plan The iNumber service offers several forwarding plans for subscriber to select, including Call Filter, Scheduled Forward, or Temporary Forward. Service Application and Customizing Subscribers could set number plan, forwarding plan and ringing mode at POS or through IVR/CSS website. Billing Options The iNumber service supports prepayment; it also supports monthly rent and CDR-based billing, as well as combination of these two methods. The CDRs for iNumber service are explicitly marked to tell the CDRs generated for iNumber services from other types of CDRs; and each of them contains the master number and the number answering the call. Triggering Mechanism The iNumber service features a nesting-Proof trigger mechanism. An iNumber service triggered by a master number excludes the iNumber service trigger of other numbers correlated with this master number. In other words, the iNumber service of a number correlated with a master number can be triggered only after the iNumber service triggered by this master number is over. Service Compatibility The iNumber service breaks the exclusiveness of traditional services; it is able to nest or be nested in other types of IN services (such as CRBT, etc), delivering more options of personalized services and new technologies for subscriber to enjoy, hence more flexible service packages that can significantly promote carriers business. The iNumber service delivers convenience for subscribers owning several terminals. It makes subscribers accessible wherever they are, at home, in an office, or outside, or surfing on Internet, significantly decreasing cases of unreachable resulting from channel congestion or coverage limitation of the communication network concerned, or limitation of the terminal being called.
mSwitch
System Overview
64
Figure 9 Solution to iNumber Service
Figure 9 illustrates a solution to iNumber service. This solution is based on an OSX platform and a Parlay service platform. The iCS-P and iUMG in the access layer provides access support for different types of terminals; the OSX is responsible for service triggering; and the Parlay service platform processes service logic. These network elements coordinate with one another to provide all the functions needed for iNumber service. The iNumber service could be flexibly deployed, either by adding an OSX and a Parlay service platform on each of existing networks involved, or by establishing a centralized (or province-level) OSX and Parlay combination over the involved networks, or if the existing network is mSwitch, directly using iCS-P to trigger service, with the Parlay platform connected to the iCS-P to enable the service provisioning. Note: OSX service switching platform includes such network elements as iCS-T, iUMG, and iSG. This platform might be not available in some application sites. It depends on the actual deployment plans.
CRBT Service Solution

The Color Ring Back Tone (CRBT) service is a callee-orient service, which allows CRBT subscribers to set different ring back tones for different caller groups, different dates, or different time segments in a day, so that callers could receive different ring
65
back tones when calling to these callees, other than those plain ring tones commonly used. CRBT subscribers are required to customize each type of color ring back tones to be used; these tones could be ring tones/music provided by the system, or audio files CRBT subscribers prepared via IN network system or downloaded from other network to IN network system. The CRBT service plays as a contributor to carriers business volume and revenue by delivering personalized value-added services that are based on carriers existing network resources. The CRBT service offers a platform for subscribers to display their individualities; it has a potential customer basis. CRBT service is characterized by subscriber-customized ring back tones that replace the plain ring back tone as commonly used, hence provide more friendly interfaces for call interaction. More detailed descriptions are given below: Callee-Initiated Service The CRBT service is to be enabled by callee party by triggering a callee-orient service process flow; which will instructs service provisioning system to play callee-customized ring tones to callers other than the plain ring tone traditionally used. Selectable Ring Back Tones CRBT subscribers can group their callers, and select certain ring back tone for each group, so that the service provisioning system can play different ring back tones for callers in different groups based on the service settings correlated to caller numbers. Subscriber-Prepared Ring Back Tones CRBT subscribers can work on a subscriber-intended operational interface to record and upload audio files they want to use as voice notifications to specific groups of callers. Company Individuality A company customer with CRBT service enabled can uniform ring back tone for its hot line or office phones to enhance its market image and satisfy its customers. Rich Ring Back Tone Resources The CRBT service is backed by rich ring back tone resources for subscribers to select. Subscribers can easily access ring back tone resources either by dialing a special service number, or by accessing a personalized ring tone portal (Web or WAP). Auto-Bypass CRBT Provisioning Faults When CRBT provisioning equipment is in fault, calls will still be connected as traditionally processed, except that the callers will not be able to hear the customized ring back tones. UTStarcom CRBT system features the following:
mSwitch
Selectable default power-off tone

System Overview
66
A Subscriber can select a CRBT from the audio libratory provided by the system and set it as default power-off tone. With this setting done, calls to the subscribers will receive the selected ring back tone. If no such setting made, the systems default power-off tone will be used as the announcement to inform the callers of the subscribers power-off. The power-off tone could be customized to different segments of a day. For example, if a subscriber takes moontime snooze everyday, he/she could leave a message to be announced within 13:00-14:00, saying Sorry, Im now napping, please call me later. Selectable tone for call on busy service A Subscriber can customize a ring back tone as the announcement for calls on busy. Calls on busy to the subscriber with such setting made will receive the ring back tone selected by the subscriber. If no such setting is made, the systems default announcement for calls on busy will be played to inform the callers. Selectable ring back tone, which could be customized for different callers A Subscriber can select different ring back tones for different groups of callers. With these settings done, calls to the subscriber will be analyzed by the system, and if a caller is among one of the groups, the system will play the ring back tone the subscriber customizes for the group. The method for selecting a ring back tone for a specific group of callers is as same as that for selecting a default power-off tone. Graded service provisioning The system can implement graded service provisioning for differently graded subscribers (currently could be graded as Ordinary, VIP, or Enterprise), so as to restrict the number of callers a subscriber of a certain grade can set ring back tones for (for example, Ordinary subscribers can customize tones for 10 caller, VIP 20 callers, Enterprise 50 0r 100 callers), as well as to restrict the maximum number of tones a subscriber of a certain grade is allowed to upload. Subscriber-prepared ring back tones In addition to the system-provided music materials, subscribers can resort to the audio libraries prepared and organized by themselves. These music libraries could be built up using one of the following methods: Recording by handset
Subscribers can record their music materials using phone handset; the system will store the recorded materials in the subscribers own music libraries for them to select later. Uploading music files
Subscribers can work on web to upload various types of music audio files (MP3, MID, WAV); the system will verify the content of the uploaded files, convert them into certain format, and store them in the subscribers own music libraries. Incoming call filter
System Overview
mSwitch
67
A CRBT subscriber can set to enable incoming call filter to reject calls made by certain callers specified or made within certain time segments. Subscriber-orient management functions of CRBT service are provisioned in several ways: voice service (IRV), Web, POS. Voice service offers traditional IRV workflows for subscribers to edit and manage their own audio materials; other management functions are provided by web-enabled interaction and POS. Figure 10 Solution to CRBT Service
UTStarcom-provided CRBT service platform is integrated as a self-contained provisioning platform separated from switching core network; it interconnected with mSwitch network via standard signaling protocol interfaces and operating support interfaces. UTStarcoms PHS network is responsible for call processing, signaling analysis and routing, while CRBT service platform is responsible for CRBT playback and related management jobs, and must have self-contained operating support system and service provisioning interfaces. In this integration solution, mSwitch systems core network and CRBT service platform are completely separated, and this makes it easy and flexible to build and deploy CRBT service in existing mSwitch networks. Figure 10 illustrates a solution to CRBT service. The solution Figure 10 is a distributed solution that needs to be deployed in each of the networks involved, namely for each local network, there should be an access platform and a CRBT platform. The CRBT service could also be implemented in a more centralized way by centralizing the background support part of the CRBT platform in province-level office, and distributing NAS servers and front switch systems distributed in the local networks. In this solution, the data in each of the distributed NAS servers is synchronized with those in the central NAS through a dedicated 2M DDN cable. Such a solution delivers simplified network topology and reduced investment.
68
The mSwitch system also support company-orient CRBT service; it is an enhanced CRBT service based on the ordinary CRBT service, featuring optimized functions in terms of billing, discount offer and tone management. A company with this service registered could have a unified company-specific color ring tone that takes effect within the work time (9:00-18:00, for example) for all the subscribers under the company while reserving the personalized ring tones customized for these subscribers during off-work time. This service is helpful for enterprises and companies to enhance their market image and open more friendly communication windows to their customers. The mSwitch system supports nested CRBT service; subscribers may apply for iNumber service while applying for CRBT service to benefit more package discount.
PBMS Solution
The Phone Bar Management System (PBMS) is an IP-based public phone solution delivered by mSwitch system, which uses existing communication network resource, together with some terminal devices (IAD, IP phone, etc.) owned and managed by phone bar owner, to deliver IP public phone service. In this solution, phone bar terminals (such as IAD, IP phone, etc.) access mSwitch system through iCS-P, and communicate with other subscribers (PHS, V5 and PSTN subscribers) through the interconnection between iCS-P and iUMG. The PBMS consists of two parts: A carrier-intended phone bar server, which is connected to the OSS database, and allows carriers to manage phone bars distributed over the mSwitch network on a real-time basis, creating, modifying and querying data information related to phone bar owners and phone bar users. A CSS server intended for phone bar owner; this server is web-enabled, allowing phone bar owner/ operators to remotely access the self-care service over Internet (by working on a PC with HTTP-enabled browser connected to Internet), hence, to complete various management operations, in terms of payment collection, account balance, deposit withdraw, query and statistics.
The PBMS features: Fully IP-based call access and switching, enhancing the utilization efficiency of the exiting IP network resource. Based on the mSwitch system, delivering carrier-class high availability. Integrated access devices (iAD) are immune from illegal attack; the mSwitch system offers authentication mechanism to ensure that no users without correct passwords can access the system. Information transmission between the CSS server and user browsers uses SSL (Security Socket Layer) protocol to ensure the security of HTTP transmission over Internet.
System Overview
mSwitch
69
Figure 11 Solution to Phone Bar Management System
Figure 11 illustrates a solution to phone bar management system. In this solution, the system consists of phone bar, iCS-P, iUMG, iMS and mBOSS. A phone bar features a mini LAN with iAD, SIP/MGCP/H.323 IP phones and a PC connected on it, and some traditional phone sets connected to the POTS ports of the iAD. The LAN is connected to the carriers IP network through a dedicated line. The bar owner/operator uses the PC to manage billing and accounting settlement. The iCS-P accesses and processes calls going through the phone bar; the iMS provides the announcement playback service for VoIP terminals; the iUMG coordinates with the iSG to enable the interconnection with PSTN network; the mBOSS provides carrier-intended phone bar server for the carrier to manage the prepayment of different phone bars, and phone bar owner self-care server for bar owners to do routine business.
mSwitch
System Overview
70
FMC Solution
Fixed-Mobile Convergence (FMC) solution launched by UTStarcom enables the convergence of WiFi-based VoIP network and the existing GSM network or CDMA network. This end-to-end solution takes advantages of the popularization of home wireless data access, and addresses the demands for expanded coverage of GSM network or CDMA network. At this stage, UTStarcom FMC solution falls into the following three scenarios, depending on specific market demands: WiFi/GSM FMC Single-Number solution: This solution is available to both VoIP carriers and traditional GSM carriers. It enables the VoIP carriers and GSM carriers to allow homed FMC single-number service subscribers to seamlessly roam between VoIP network and GSM network, which consequently expands the network coverage. An FMC Single Number service subscriber uses a single number in VoIP and GSM networks. This solution benefits the carriers in the following ways: Allows the traditional GSM carriers to increase the coverage of existing GSM networks. In the WiFi/GSM FMC Single-Number solution, WiFi-based VoIP network covers blind spots in areas such as residential buildings and downtown. It provides an end-to-end and cost-effective solution for the traditional GSM carriers. Allows the emerging VoIP carriers to attract more customers if reaching inter-network roaming agreements with GSM network carriers.
WiFi/GSM FMC Dual-Number solution: This solution is available to VoIP carriers only. It enables the VoIP carriers to allow homed FMC dual-number service subscribers to seamlessly roam between VoIP network and GSM network, which consequently expands the network coverage. An FMC Dual Number service subscriber has two numbers: one number for VoIP network (represented by F#), and another number in GSM network (represented by M#). This solution allows VoIP carriers to attract more customers if reaching internetwork roaming agreements with GSM network carriers.
WiFi/CDMA FMC Single-Number solution: This solution is available to both VoIP carriers and CDMA carriers. It enables the VoIP carriers and CDMA carriers to allow homed FMC single-number service subscribers to seamlessly roam between VoIP network and GSM network, which consequently expands network coverage. An FMC Single Number service subscriber uses a single number in VoIP and CDMA networks. This solution benefits the carriers in the following ways: Allows the traditional CDMA carriers to increase the coverage of existing CDMA. In the WiFi/CDMA FMC Single-Number solution, WiFi-based VoIP network covers blind spots in areas such as residential buildings and downtown. It provides an end-to-end and cost-effective solution for the traditional GSM carriers. Allows the emerging VoIP carriers to attract more customers if reaching inter-network roaming agreements with CDMA network carriers.
mSwitch
System Overview
71
As an end-to-end solution, the FMC solution consists of the following core components: WiFi/GSM or WiFi/CDMA dual-mode phone: the dual-mode phones are embedded with Subscriber Identity Module (SIM) card and Session Initiation Protocol (SIP) User Adapter (UA) application software, and have WiFi and GSM (or CDMA) wireless access capability. At any given time, a WiFi/GSM or WiFi/CDMA dual-mode phone is bound to one network only. GSM or CDMA network: provides wireless access and network services for FMC service subscribers. VoIP network Access Network: employs WiFi-, or WiMax-based wireless technology to provide wireless broadband access for FMC service subscribers. Service Network: built on ContinuityTM system, the service network provides SIP-based call control, roaming management and security authentication functionality for FMC service subscribers. It enables seamless convergence between VoIP network and GSM / CDMA network. That allows the FMC dual-mode handset to roam and hand over between VoIP network and GSM / CDMA network using a single set of subscriber profile.
Currently, UTStarcom FMC solution can be deployed in the following three networking configurations: WiFi/GSM FMC networking solution with roaming capability: This configuration provides WiFi/GSM FMC single-number service and dual-number service with inter-network roaming capability, but without inter-network handover capability. WiFi/GSM FMC networking solution with roaming and handover capability: this configuration provides WiFi/GSM FMC single-number service with inter-network roaming and handover capabilities. WiFi/CDMA FMC networking solution with roaming capability: This configuration provides WiFi/CDMA FMC single-number service with inter-network roaming capability.
For more information of the FMC solution, refer to FMC Service Provisioning Guide. Currently, the FMC solution supports the following supplementary services and valueadded services: Calling Line Identification Presentation (CLIP): The system can send the caller phone number to the callee, and display the number on the callee phone. Calling Line Identification Restriction (CLIR/CIDB): If a caller does not want to have his/her number displayed on the called terminal, the subscriber can enable CLIR. Short Message Service (SMS): Short Message Service (SMS) enables a subscriber to send and receive short messages by using the phone. Voice Mail (VM) Service: Voice Mail (VM) service provides voice-messaging capability for subscribers when they are unavailable to answer calls, for example, when they are busy or unreachable. If a subscriber registers Voice Mail service, those calls will be automatically forwarded to the voice mailbox, and the calling parties will be prompted to leave a message. After that, the subscriber can dial
System Overview
mSwitch
72
the access code of the voice mailbox to get access to it and retrieve the messages. Voice Mail Notification (VMN) Service: Voice Mail Notification (VMN) service enables the subscriber to be notified when a voice mail arrives to the voice mailbox.
SIM Card Roaming Service Solution

SIM Card Roaming service solution is designed for various types of subscribers, such as GSM, PHS, VoIP terminal, and PSTN subscribers, to access IDD call service at lowered price. SIM Card Roaming service subscribers can access not only the basic IDD service, but also short message service (SMS) and voice mail service (VMS). After subscribing the SIM Card Roaming service, PHS subscribers, VoIP subscribers or PSTN subscribers get a SIM card. This card is to be used with a GSM handset. In addition, the subscriber must have a GSM handset that can roam into the visited location. Before visiting a country, the subscriber sets on his/her PHS/VoIP/PSTN terminal a Hunt Me forwarded-to number; and after arriving the country, the subscriber, by using a GSM handset identified by the SIM card, can access the call service provisioned by the GSM network of the visited country, including making calls or receiving calls originated from the home site to the PHS/VoIP/PSTN number and forwarded to the roaming GSM handset the subscriber uses at the visited site, and at the same time, benefit lower IDD rate. When a GSM subscriber subscribes the SIM Card Roaming service and is roaming to another country, the SIM Card Roaming service provider will inform the subscriber of a new MSISDN number with Hunt Me logic activated. So, the subscriber, by using the new MSISDN number, can access the call service provisioned by the GSM network of the visited country, including making calls or receiving calls originated from the home site to the original MSISDN and forwarded to the new MSISDN, and at the same time, benefit lower IDD rate.
Networking Model
SIM Card Roaming service network mainly consists of a VoIP IDD network and the GSM networks to be visited.
System Overview
mSwitch
73
Figure 12 SIM Card Roaming Service Solution
As shown in the figure above, the mSwitch core network (i.e. SIM Card Roaming service network in above figure) is the main part of SIM Card Roaming service solution, located between SIM Card Roaming service subscribers home network and the visited network; it mainly consists of the following components: HLR HLR stores and manages subscribers information data required in service provisioning, including: The data required to implement authentication The data required to identify subscribers property and service The data that reflect the relation between the IMSI/MSISDN numbers SIM Card Roaming service subscribers use at home site and the V-MSISDN numbers the subscribers use at visited sites The number resources of all the visited sites involved in the SIM Card Roaming service network.
USSD Server
mSwitch
System Overview
74
USSD Server enables the billing for calls initiated by SIM Card Roaming service subscribers from visited sites; it allows the home network to directly exchange information with the roaming SIM Card service caller, hence to implement independent billing for calls initiated by these callers, saving the settlement procedure between the home network and the visited networks. At present, the function of USSD Server is implemented by UTStarcoms Feature Server (FS). In other words, to enable the USSD functionality in a SIM Card Roaming service network, the carrier only needs to install a Feature Server. iCS-P, iSG and iUMG iCS-P communicates with call servers of third party VoIP networks through SIP-T protocol; it mainly offers such functions as call processing, number analysis, and call routing. iSG and iUMG work as Signaling Gateway and Trunking Gateway to complete signaling protocol conversion and media conversion respectively, enabling the interconnection between TDM network and IP network, as well as between local GSM network and SIM Card Roaming service network. In addition, an iUMG could also work as a media server to provide media functions like playing announcement, generating DTMF tone, and so on. mBOSS mBOSS mainly consists of SAM (Subscriber Application Management System), CSS (Customer Self-service System), OBS (Online Billing System) and PSC (Prepaid Service Center). SAM manages and maintains subscribers profile and service status, provides functions required to handle subscribers applications for service registration, as well as subscribers requests for adding additional attributes to their service, such as value-added services and various supplementary services. CSS is a customer self-service system, provided either as a Web-based server or an IVR platform. CSS allows subscribers to query related information, such as carriers billing policy, the information about the services they use, the service usage they have consumed, and to apply for services and credit. When implemented in a SIM Card Roaming service network, in particular, it allows SIM Card Roaming service subscribers to enable their service with various SIM Card Roaming service features, for example, to activate Follow Me to Home and Hunt Me service logic, set Hunt Me number, and so on. OBS provides various billing functions, such as data collection, billing, accounting, payment, information maintenance, auditing and checking, query and statistic analysis, related data management, and so on. PSC provides functions such as collecting CDRs, pricing, and charging and so on, both for prepaid and postpaid subscribers. IVR-1000 is an interactive voice response platform integrated in mSwitch network to support prepaid service provisioning; like CSS, it is a customer self-service system.
System Overview
mSwitch
75
mBOSS can deliver flexible billing policies and price plans adapted to different business modes, and different billing requirements of different subscribers using different services they think suit them most. Message GW Message GW enables short message service for SIM Card Roaming service subscribers roaming outside the home network. In SIM Card Roaming service solution, Message GW is mainly designed to offer such short messages that carry instructions required by SIM Card Roaming service subscribers while making calls at visited sites, including those messages that inform the roaming subscribers of the V-MSISDN numbers they should use at visited sites. VMS VMS is used to provide voice mailbox service for SIM Card Roaming service subscribers.
Service Logic
Caution: A carrier can provide SIM Card Roaming service for SIM Card Roaming service subscribers only when it gets the V-MSISDN number resource of the to-bevisited networks. These V-MSISDN numbers can be allocated to SIM Card Roaming service subscribers for call services; otherwise, the SIM Card Roaming service subscribers can only use their H-MSISDN numbers to access the ordinary IDD call service, namely, they cannot benefit IDD rate discount, since calls made by HMSISDN numbers are processed by the IDD gateway of the existing network implementing ordinary IDD call processing flow. In this chapter, we suppose that the carrier is allowed to allocate the V-MSISDN number resource of the to-be-visited networks, namely, the SIM Card Roaming service subscribers can benefit the IDD rate discount. If a SIM Card Roaming service subscriber is also a PHS subscriber or a PSTN subscriber, the subscriber must have a GSM handset to use the SIM Card Roaming service at a visited site. The MSISDN number used by SIM Card Roaming service subscribers in visited site is allocated by the SIM Card Roaming service network, which is hereafter called V-MSISDN for short. If a SIM Card Roaming service subscriber is also a GSM subscriber, the subscriber has an IMSI number allocated within the home GSM network (namely the MSISND number of the home site, which is hereafter called H-MSISDN for short) and an IMSI number allocated within the SIM Card Roaming service network. When the subscriber roams to a visited site, the HLR in the SIM Card Roaming service network will, according to the IMSI, allocate to a new MSISDN (hereafter called V-MSISDN for short) for the subscriber to use at the visited site. Note: Since for each visited site involved in a SIM Card Roaming service network, the SIM Card Roaming service carrier may only get a limited V-MSISDN number segment, the V-MSISDN resource is not rich enough for each of SIM Card Roaming service subscribers to have a fixed V-MSISDN. So, fixed V-MSISDN numbers should be allocated only to those SIM Card Roaming service subscribers who frequently visit certain sites (countries).
mSwitch
System Overview
76
If a SIM Card Roaming service subscriber has applied for a fixed V-MSISDN to be used at a to-be-visited site, the allocated V-MSISDN will be stored as part of the subscriber CSI (CAMEL Subscription Information). This is to ensure that the subscriber can always have the same V-MSISDN each time when visiting this site. If the subscriber has not yet applied for such a fixed V-MSISDN, the SIM Card Roaming service network will dynamically allocate from the available V-MSISDN resource a temporary V-MSISDN for the subscriber. The SIM Card Roaming service provider sets the valid period of the temporally allocated V-MSISDN, and the subscriber will use this number within the valid period. When the number expires, the HLR will allocate another V-MSISDN to the subscriber if he/she still stays in the visited site. Service logic that enables SIM Card Roaming service subscriber to work as a called party at the visited site
Note: A Hunt Me number refers to the original number a SIM Card Roaming service subscriber uses at home, which could be a PHS number, a PSTN number, or a GSM number. A Hunt Me forwarded-to number refers to the forwarded-to number a SIM Card Roaming service subscriber set on his/her terminal. Before roaming to a visited site, a SIM Card Roaming service subscriber must activate the Hunt Me service logic on the handset, to enable all calls to be forwarded to a number with a fixed prefix (for example, 1-800-xxxx) and to store the Hunt Me number in the HLR of the SIM Card Roaming service network. When this is done, calls to the subscriber will be forwarded to the SIM Card Roaming service network according to the number with a fixed prefix and rerouted accordingly. Note: In the HLR of the SIM Card Roaming service network, an IMSI could correlate with multiple Hunt Me numbers, which respectively correspond to different types of terminals (PHS, PSTN, and GSM) a subscriber owns. After roaming to the visited site, the SIM Card Roaming service subscriber will register to the MSC in the visited network (hereafter called V-MSC for short). When the V-MSC receives the registration request, it retrieves from the IMSI the information about the HLR, and sends to the HLR a request, informing it to update the subscribers location information. The HLR will then allocate a VMSISDN to the subscriber, and at the same time return this number to the VMSC. The V-MSC will store this number in the VRL of visited site. When these procedures are completed, the further registration procedures to be done for the SIM Card Roaming service subscriber will be the same as those for ordinary GSM subscribers. The allocated V-MSISDN is sent through the Message GW as a short message to the SIM Card Roaming service subscriber. The HLR in the SIM Card Roaming service network is logically a HLR of the visited site, although not geographically located within the visited site; the V-MSC can retrieve from it all the information required to enable call service provisioning for the SIM Card Roaming service subscriber, such as IMSI, H-MSISDN, VMSISDN, Hunt Me number and other service-related information. In brief, calls (initiated by other subscribers from the home site) to a SIM Card Roaming service subscriber visiting another country will first trigger Hunt Me
77
service logic, being forwarded to the SIM Card Roaming service network and rerouted accordingly. The SIM Card Roaming service network will route these calls from the home TDM network to the home VoIP network, then to the visited VoIP network, and finally to the visited TDM network. Since such a route path bypasses the IDD TDM gateway, the SIM Card Roaming service subscriber could benefit IDD rate discount. When as a called party to communicate with subscribers of the visited network, the SIM Card Roaming service subscriber uses the V-MSISDN allocated by the SIM Card Roaming service network. So, the SIM Card Roaming service subscriber is treated as a local subscriber by the visited GSM network, hence benefits a called party rate lower than that set for ordinary IDD. Service logic that enables SIM Card Roaming service subscriber to work as a caller at the visited site After roaming to the visited site, a SIM Card Roaming service subscriber will receive a short message sent from the Message GW, which carries instructions required by the subscriber when making calls at visited sites. To make an IDD call (play as a caller) at the visited site, the SIM Card Roaming service subscriber must resort to the USSD Server, more specifically, must have the USSD Server to trigger the USSD Call Back service logic, as described below. First, the subscriber, as instructed by the message from the Message GW, sends to the USSD Server a message that carries the called party number (for example, *100*13012345678#, where the 100 refers to the service code, the 13012345678 refers to the called party number). After receiving the message, the USSD Server transparently sends it to the call server (iCS-P) in the SIM Card Roaming service network . The iCS-P retrieves from the message the caller number and called party number respectively, and initiates a call to each of the two numbers. If both of the two parties respectively answer the call, the iCS-P will work as a bridge to enable the interconnection between the caller and the callee. Since such a call process bypasses the IDD TDM gateway, the SIM Card Roaming service subscriber could benefit IDD rate discount. When as a caller to communicate with subscribers of the visited network, the SIM Card Roaming service subscriber is treated as a local subscriber by the visited GSM network, hence benefits a caller rate lower than that set for ordinary IDD. Service logic for SIM Card Roaming service subscriber to work as a called party after returning home from a visited site After returning home from a visited site, a SIM Card Roaming service subscriber needs to activate Follow Me to Home service logic to release the V-MSISDN the subscriber currently occupies, so that the V-MSISDN can be allocated to other SIM Card Roaming service subscribers visiting the same site. After this logic is activated, calls to the subscriber will be forwarded to the (PHS/PSTN/GSM) terminal the subscriber uses at home network, and the Follow Me to Home service number the subscriber sets when activating the Follow Me to Home logic is just the number of the terminal the subscriber uses at home network.
78
Call Flow
In the call flow discussed below, we suppose that the SIM Card Roaming service subscriber involved is a GSM subscriber. Call flow for a SIM Card Roaming service subscribers request for registration in visited network and location information update Figure 13 Call Flow for a SIM Card Roaming Service Subscribers Request for Registration in Visited Network and Location Information Update
1 2
The SIM Card Roaming service subscriber, after roaming to the visited site, sends to the VMSC/VLR a request for location information update. After making sure the subscriber is a SIM Card Roaming service subscriber by checking the IMSI, the VMSC/VLR sends to the HLR (the location register in the SIM Card Roaming service network) a message, requesting for location information update. This message is first sent to the SG in the SIM Card Roaming service network for lower three layers of protocol conversion. Upon converting the MTP signaling into M3UA signaling, the SG forwards the message to the HLR. a After receiving the message, the HLR retrieves from it the VMSC number to get the subscribers current location information, and then send to the iCS-P a request for location information synchronization.
4 5 6 7
The HLR returns authentication data to the SG. The SG converts the lower layer of signaling and then sends the converted authentication data to the VMSC/VLR. The VMSC/VLR, upon receiving the authentication data, performs authentication operation against the GSM handset being used by the subscriber. The HLR allocates a V-MSISDN to the roaming subscriber, correlates the VMSISDN with subscribers IMSI and H-MSISDN, and at the same time, returns the V-MSISDN, together with the subscribers attribute information, to the SG. The SG converts the lower-layer of signaling and then sends the converted message to the VMSC/VLR.
mSwitch
8
System Overview
79
The VMSC/VLR, upon receiving the subscribers attribute information and the VMSISDN sent from the HLR, sends to the subscribers terminal a confirmation response, indicating that the location information update or the authentication is successfully completed. Up on receiving this response, the SIM Card Roaming service subscriber can access call service in the visited network.
10 After allocated the V-MSISDN to the subscriber, the HLR sends to the Message GW a message, instructing the Message GW to send to the SIM Card Roaming service subscriber a short message that informs the subscriber to use the allocated V-MSISDN to access call services during his/her stay in the visited site. 11 The SMS GW (Message GW) communicates with the H-SMSC (Home SMS Center) through SMPP, so that the SIM Card Roaming service subscriber can get the short message that carries the V-MSISDN the subscriber can use to access call service provisioned by the visited GSM network. Call flow for SIM Card Roaming service subscribers request for activating Follow Me to Home logic and registering a new Follow Me to Home number at the visited site Figure 14 Call Flow for SIM Card Roaming Service Subscribers Request for Activating Follow Me to Home Logic and registering a New Follow Me to Home Number at the Visited Site
The SIM Card Roaming service subscriber, after roaming to the visited site, sends to the VMSC/VLR a USSD message to activate the Follow Me to Home logic or register a Follow Me to Home number for another terminal the subscriber uses at home. Upon receiving the message, the VMSC/VLR checks the subscribers IMSI to determine if the requesting subscriber is a SIM Card Roaming service subscriber; if so, it sends to the SG in the subscribers home domain a standard MAP-based USSD message. The SG, after completing necessary lower-layer of protocol conversion, sends the MAP-based USSD message to the HLR.
mSwitch
System Overview
80
The HLR, by analyzing the service code carried in the message received, gets informed that this message is to be sent to USSD Server, and accordingly forwards the message to the USSD Server. The USSD Server resolves the content of the message received, and then sends the resolved message to the HLR. The HLR checks the content of the message sent from the USSD Server, and after informed that the message is requesting for activating the Hunt Me logic or for registering a new Follow Me to Home number, it sets the subscribers service status as Follow Me to Home activated, or stores the newly requested Follow Me to Home number in the HLR database, and at the same time, synchronizes the data change to the iCS-P cache.
5 6
After completing this operation, the HLR sends a response to the SG. The SG, after completing necessary protocol conversion, sends the response message to the VMSC/VLR. The VMSC/VLR sends to the SIM Card Roaming service subscriber a message, as a response to the subscribers service request, and also as an indication that the Follow Me to Home service logic has been activated or the registration of the new Follow Me to Home number has been completed.
Note: The Follow Me to Home and Hunt Me service logics conflict each other. When a SIM Card Roaming service subscriber activates the Follow Me to Home logic, its Hunt Me logic will be deactivated automatically. The Hunt Me is registered as default service logic when opening account for a SIM Card Roaming service subscriber; it will be automatically activated when the SIM Card Roaming service subscriber roaming to an to-be-visited site and initiating the location update request, and deactivated once the Follow Me to Home logic is activated. Call flow for calls made by SIM Card Roaming service subscriber at the visited site to local subscribers After a SIM Card Roaming service subscriber has successfully registered to the visited network, the V-MSISDN allocated to the subscriber will be stored in the VMSC/VLR. So, when the subscriber initiates a call from the visited network to a local subscriber, the visited GSM network will implement an MO call flow same as that for an ordinary local GSM call.
System Overview
mSwitch
81
Call flow for IDD calls made by SIM Card Roaming service subscriber from the visited site Figure 15 Call Flow for IDD Calls Made by SIM Card Roaming Service Subscriber from the Visited Site
When a SIM Card Roaming service subscriber initiating an IDD call from the visited site, the subscriber terminal sends to the VMSC/VLR a USSD message carrying IDD call request. Upon receiving the USSD message, the VMSC/VLR checks the subscribers IMSI to determine if the requesting subscriber is a SIM Card Roaming service subscriber; if so, it sends to the SG in the subscribers home domain a standard MAP-based USSD message. The SG, after completing necessary protocol conversion, sends the MAP-based USSD message to the HLR. The HLR forwards the message to the USSD Server. The USSD Server sends to the iCS-P in the SIM Card Roaming service network a message (Call Back Notification) that carries the caller number and the called number. In response to the Call Back Notification received, the iCS-P first sends an SIP Invite message to the caller. The Call Server in the third party VoIP network sends an IAM to the MSC/VLR of the called partys home network (note: the caller number carried in this IAM identifies the SIM Card Roaming service network, and the called number identifies the SIM Card Roaming service subscriber that initiates the IDD call). This MSC/VLR accordingly initiates a call to the SIM Card Roaming service subscriber (the IDD caller), and after the subscriber answers the call, it returns an ACM and an ANM to the Call Server.
3 4
5 6
mSwitch
System Overview
82
In response to the messages received from the MSC/VLR, the Call Server sends a SIP 200 OK message to the iCS-P, indicating the caller has been successfully addressed and connected. The iCS-P sends to the iUMG&MS a Megaco-based message, requesting for the media resource required to play announcement to the caller, and once the caller answers, it instructs the iUMG&MS to play the requested announcement to the caller, telling the caller the call setup is in process. After the caller is successfully connected, the iCS-P sends a SIP Invite message to the called party.
10 The Call Server in the third party VoIP network sends an IAM message to the MSC/VLR of the called partys home network (note: the caller number carried in this IAM identifies actual IDD caller, and the called number identifies the actual called party). This MSC/VLR accordingly initiates a call to the called party, and after the called party answers the call, it returns to the Call Server an ACM and an ANM. 11 In response to the messages received from the MSC/VLR, the Call Server sends a SIP 200 OK message to the iCS-P, indicating the called party has been successfully addressed and connected. 12 Upon respectively connected to the caller and the called party, the iCS-P sends to the iUMG&MS a Megaco-based message, requesting for the media resource required to play announcement to both the caller and the called party, and then works as a bridge to enable the call connection between the caller and the called. Note: The red line in the figure above indicates the media flow. Call flow for calls originated from a V-MSISDN allocated to SIM Card Roaming service subscriber at the visited site to another visiting SIM Card Roaming service subscriber After a SIM Card Roaming service subscriber has successfully registered to the visited network, the V-MSISDN allocated to the subscriber will be stored in the VMSC/VLR. So, when the subscriber uses the V-MSISDN to initiate a call from the visited country to another SIM Card Roaming service subscriber visiting the same country, the visited GSM network will implement an MT call flow same as that for an ordinary GSM call. If the SIM Card Roaming service provider is granted the permission to use certain MSISDN segments of different cities in a country, the HLR will allocate different V-MSISDN numbers to the SIM Card Roaming service subscriber when visiting different cities of this country. In this case, the visited GSM network will process the call by implementing an MT call flow same as that for an ordinary local GSM subscriber. If the SIM Card Roaming service provider is granted the permission to use only one MSISDN segment of a country, a call to the SIM Card Roaming service subscriber visiting the country must be routed to the MSC/VLR the allocated VMSISDN belongs to. In this case, the visited GSM network will process the call by implementing an MT call flow same as that for a domestic GSM call.
System Overview
mSwitch
83
Call flow for calls originated from a Hunt Me number to a SIM Card Roaming service subscriber at the visited country Figure 16 Call Flow for Calls Originated from a Hunt Me Number to a SIM Card Roaming Service Subscriber at the Visited Country
In the call flow discussed below, we suppose that the called party is a SIM Card Roaming service subscriber who has roamed to the visited site, activated the Hunt Me service logic, get the Hunt Me number, and has set the Hunt Me forwarded-to number. The caller is a GSM subscriber homed to the SIM Card Roaming service network. A call is placed to the Hunt Me number of the SIM Card Roaming service subscriber roaming to the visited site. 1 The GSM subscriber at home uses the Hunt Me number to call the visiting SIM Card Roaming service subscriber. Since the visiting subscriber has already activated the Hunt Me logic, the GMSC, referring the Hunt Me forwarded-to number the called party set, forwards the call out. This call is first forwarded to the SG directly connected to the PLNM (the TG&SG as illustrated in Figure 16). This SG converts the ISUP message as SIGTRAN-based message and then sends the converted message to the iCS-P in the SIM Card Roaming service network. The iCS-P sends to the HLR a query request for the V-MSISDN. The HLR retrieves from the database the V-MSISDN allocated to the SIM Card Roaming service subscriber (the called party), and returns the number to the iCS-P. The iCS-P, referring to the V-MSISDN, forwards the call to the Call Server in the third party VoIP network. The Call Server, referring the received V-MSISDN, forwards the call to the TG&SG directly connected to the GSM network currently being visited by the SIM Card Roaming service subscriber (the called party).
System Overview
3 4
5 6
mSwitch
84
This SG converts the SIP message as an ISUP message, and then sends the converted message to the GMSC of the GSM network currently being visited by the SIM Card Roaming service subscriber. This GSMC, upon receiving the message, sends to the HLR a request for routing information. The HLR, in response to the request, sends through the SG (in the SIM Card Roaming service network) a message to the MSC/VLR currently being visited by the SIM Card Roaming service subscriber (the called), requesting for the roaming number allocated to the called.
8 9
10 This MSC/VLR returns through the SG (in the SIM Card Roaming service network) the requested roaming number to the HLR. 11 The HLR returns through the SG the requested routing information (namely, the roaming number), to the GSMC currently being visited by the SIM Card Roaming service subscriber. 12 The GSMC, referring the returned roaming number, initiates a MT call to the MSC currently being visited by the called. 13 The MSC/VLR addresses the SIM Card Roaming service subscriber (the called) and then setup the call connection between the caller and the called. Note: The red line in the figure above indicates the media flow. Call flow for SIM Card Roaming service subscribers VMS request Figure 17 Call Flow for SIM Card Roaming Service Subscribers VMS Request
The call flow for a SIM Card Roaming service subscribers VMS request is similar to that designed for the message delivery to a SIM Card Roaming service subscriber plays as a caller; the only difference is that the called party involved in this flow is the voice mailbox.
85
Note: If there is a voice message to a subscriber remaining unchecked by the subscriber, the VMS will sends to the H-SMSC a SMPP message, instructing the HSMSC to inform the subscriber to check the message (refer to the procedure labeled as a in the Figure 17). 1 The SIM Card Roaming service subscriber sends a MAP-based USSD message to query voice message.
Note: A USSD message sent by a SIM Card Roaming service subscriber to communicate with the VMS could be one of the two formats described below: a. The called party is the voice mailbox ID b. The called party is the V-MSISDN allocated to the SIM Card Roaming service subscriber; in this case, the SIM Card Roaming service subscriber uses the VMSISDN as the voice mailbox ID Both of the two formats work in terms of setting up a successful call to the VMS. 2 After making sure the subscriber is a SIM Card Roaming service subscriber by checking the IMSI, the VMSC/VLR forwards the USSD message to the SG in the SIM Card Roaming service network. The SG, after completing necessary protocol conversion, sends the message to the HLR. The HLR, by analyzing the service code carried in the message, gets informed that this message is to be sent to USSD Server, and accordingly forwards the message to the USSD Server. The USSD Server resolves the content of the message received, and then sends the resolved message (called number and caller number) to the iCS-P. The iCS-P, in response to the message sent from the USSD Server, sends an SIP Invite message to the caller. This message is further forwarded to the MSC/VLR currently being visited by the SIM Card Roaming service subscriber, going through the Call Server and then the TG&SG in the third party VoIP network. In response to the messages received from the MSC/VLR, the Call Server sends a SIP- 200 OK message to the iCS-P, indicating the caller has been successfully addressed. The iCS-P sends to the iUMG&MS a Megaco-based message, requesting for the media resource required to play announcement to the caller, and once the caller is connected, it instructs the iUMG&MS to play the requested announcement to the caller, telling the caller the call setup is in process. After the caller is successfully connected, the iCS-P sends a SIP Invite message to the called party. The VMS (the called party), in response to the Invite message, returns a response to the iCS-P. Upon respectively connected to the caller and the called, the iCS-P sends to the iUMG&MS a Megaco-based message, requesting for the media resource required to exchange voice message between the caller and the called, and then works as a bridge to enable the media flow connection between the caller and the called (the VMS).
3 4
5 6
mSwitch
System Overview
86
Note: The red line in the figure above indicates the media flow.
SIM-Based IP Terminal Subscriber Solution (release to PLDT only)

Along with other access systems, the mSwitch system can provide telecommunication services for SIM-based IP terminal subscribers. Figure 18 illustrates the networking model of the mSwitch system in the SIM-based IP terminal subscriber solution. Figure 18 SIM-Based IP Terminal Subscriber Solution
Wi-Fi Subscriber Unit
NGN network AuC Protocol
IP Phone Wi-Fi Network SIP SIM card Wi-Fi Access Point
SIP,TFTP,FTP
Terminal Config Server TC DB SIP
AuC
AuC DB AuC Protocol
IP Phone DSL Network SIP SIM card Cable Modem
Session Border Controller
SIP
SoftSwitch
SS7, DM
PSTN
SS DB
In this solution, the mSwitch system is composed of iCS-P, iUMG, iSG, and SLR. Figure 19 shows the external interfaces of the mSwitch network elements. Figure 19 External Interfaces of mSwitch Network Elements
iSG TC DB AuC
AuC Protocol
iCS-P
SNSP
M3UA
ISUP
SS7
E1 MEGACO
PSTN
SLR
SIP
iUMG
SIP Phone (With SIM)
The external interfaces of the mSwitch network elements include the following:
System Overview
Interface between iCS-P and SIP terminal by using SIP protocol Interface between SLR and AuC by using AuC protocol to transfer authentication tetrads Interface between iSG and SS7 network for IP-TDM signaling conversion
mSwitch
87
Interface between iUMG and PSTN for interaction of media streams
Note: In the mSwitch network, iSG and iUMG are used for interworking with the PSTN. Please use them according to the actual application. In the SIM-based IP terminal subscriber solution, SLR implements the Authentication, Authorization, and Accounting (AAA) functions, and iCS-P compares the calculation results that IP terminals and AuC obtained by using a fixed algorithm and determines the validity of the terminal subscribers.
iWeSee Service
Different from the traditional videoconferencing service, the IP-based video conference service (iWeSee service) of UTStarcom employs video technologies and IP data communication technologies to set up sessions and exchange audio, video and data streams between two or more terminations over an IP network. The conference participants can see and hear the speakers at the conference sites on a real-time basis using computer terminals, cameras and microphones. This emulates a face-to-face meeting environment. Being a modern multimedia communication tool, the iWeSee service is catching on due to its important role in conducting meetings with people in scattered locations. It aids in making decisions, issuing news, improving working efficiency, and saving time and travel costs. In addition, the iWeSee service benefits from the IP-based broadband architecture to achieve flexible service scalability. The iWeSee delivers free-to-talk video conference service. In such a conference, there is only one chairperson, and each party can become a speaker or sitter-in. There is no concept of fixed or definitive speakers applied. The chairperson holds full control over the conference, able to control attendees speech, invite a new party to join the conference, hand over the chairperson role to an attendee, lock the conference, and prolong the conference. As an implementation of a new generation multimedia service in the mSwitch system, the iWeSee features the following: Support to standard Parlay API Support to a broad range of terminal types, including SIP/MPEG4-based video terminal SIP/MGCP/H.248 voice terminal PSTN/GSM phone
Allowing conference parties to initiate access to a conference by dialing the conference access number +conference ID+conference password. Media Server can mix G.711 A-law/-law audio stream and transfer the audio stream through RTP/RTCP protocol. Media Processor can distribute a real time MPEG4 video stream through the RTP protocol. Web portal based service management function, allows users to reserve and manage a video conference, including
System Overview
mSwitch
88
Reserve and manage the conference through ESS-Enterprise Portal, as well the e-mail notification to parties. Reserve and manage the conference through ESS-Enterprise Manager.
IVR-based service management function SOAP (Simple Object Access Protocol) /HTTP (Hypertext Transfer Protocol) is employed as the interface between the conference application server (Webconf APP) and the web portal. Conferences can be convened either through a parties initiative access (Call-in ) or system initiative inviting (Call-out) Real-time billing for iWeSee services initiated by postpaid subscribers. Unified database; the service data generated when users reserve, join and manage a conference, or take certain control actions in the conference using different fore-ends (terminals, IVR and web portal clients), are all stored in the same database, and will be synchronized to these fore-ends for subscribers to access.
The iWeSee system of UTStarcom is based on a Parlay value-added service platform. In addition to video and audio transmission, the iWeSee system has the following advantages: Two simultaneous speakers to guarantee the best voice quality The iWeSee system employs advanced audio codec technologies to offer a twoway audio mixing effect. During the conference, all attendees can simultaneously receive the voices of two speakers at most. This makes communication more fluent, and with the best voice quality. Four-channel video pictures and free switch between the video windows The iWeSee system provides four channels of video pictures. During the conference, all attendees are displayed in a user list. The users can click a videoenabled attendee from the user list to view the video pictures from his/her site. The iWeSee system enables users to view the current pictures of any attendee in the conference no matter whether he/she is the speaker. Flexible web-based service management: The chairperson can work on a Web portal to reserve and manage a conference; flexibly add and delete attendees, and modify information of an existing attendee. The system administrator can handle conference reservation applications, approving or rejecting an application.
Reliable controls on a conference: During a video conference, the chairperson is assigned with the privilege to take some advanced control actions on the conference, for example, allow an attendee to be heard, invite an new party to join the conference, silence a speaker, reject an application for speaking to the conference, remove an attendee from the video conference, and so on.
System Overview
Leading video codec technology

mSwitch
89
The iWeSee uses the MPEG4 codec, which is suitable for both high density/quality video streaming over broadband and low density video streaming over narrow bandwidth (less than 64 kbps). Mixing calls Accept a mixed attendance of audio/video-enabled participants, for example, the UTSmart PC phone of UTStarcom, and only-audio-enabled terminals to a conference, allowing these two types of terminals to access the conference call simultaneously. Automatic email-based conference notification to attendees When a conference is reserved, or the reservation information is modified, the system will automatically deliver an email notice to the attendees. The notice will carry such information as the conference access number, ID, password, the date the conference will be held, and the time the conference will start. In contrast to the traditional voice service, the multimedia conferencing service demands a more feature-rich communications system, in terms of integrity, interaction and synchronization. The softswitch system offers an ideal solution to the provisioning of the multimedia conferencing service. Based on hierarchical network architecture, the softswitch system provides converged voice, data, and multimedia service. It features openness, and has an edge in various aspects; for example integrated access, service provisioning, network management, user authentication, authorization and billing. The mSwitch system, a softswitch system developed by UTStarcom, serves as the backbone for multimedia conferencing service provisioning. The mSwitch system is based on open system architecture (OSA). It splits the media flow and call control, as well as the call control and service bearer, so that the applications are separated from the underlying network. In addition, the mSwitch system provides an application protocol interface (API) to support the provisioning and deployment of new valueadded services (VAS). Multimedia conferencing service is one of the VAS. The figure below shows the implementation architecture of the multimedia conferencing service. This architecture utilizes the openness of the Parlay platform in the mSwitch system. APIs, primarily Parlay API, define the function set for the multimedia conferencing service applications, and are effectively integrated with audio and video processing technologies.
mSwitch
System Overview
90
Figure 20 iWeSee Service Implementation Architecture
1 1 1 1 1 1 1 1 1 1 1 1 11 1
iAN-08E
System Overview
mSwitch
System Functional Components
Introduction to mSwitch Platform

Applications in mSwitch run on two types of hardware platform: mSwitch platform and Sun server. All the mSwitch applications are installed on hardware platforms of these two types, e.g. components like iCS-P, iUMG, and iSG run on mSwitch platforms, while components, such as SLR, Parlay GW, CN SNMS, OSS (SAM, OBS, CSS), run on Sun servers. A brief introduction to mSwitch platform is given below. The mSwitch platform is a carrier-class switching device featuring a bus/modular structure that delivers high performance, as well as flexibility in configuration and expansion. The platform consists of a gateway backplane containing a series of standard communication buses, and function boards fulfilling specific functions. There are 21 slots on the backplane for insertion of the function boards. The function boards communicate with each other through the buses on the backplane. The backplane includes the following buses Dual CompactPCI buses 8 32M H.110 buses Two sets of UT star fast Ethernet buses Two sets of PICMG2.16 GE Ethernet buses
The design of mSwitch hardware platform features: High availability; supporting active/standby redundancy and hot swap for function boards. Load sharing redundancy of different types, delivering enhanced system reliability. Modular structure, delivering flexibility in configuration and expansion. High-speed switching capability enabled by UT star fast Ethernet and PICMG2.16 compliant GE Ethernet buses, delivering enhanced system performance.
At present, there are two types of chassis being used in mSwitch system, which are 3U and 14U in height. The former, which can pack together key NEs (such as iCS-P, iUMG, and iSG), is commonly used; the later is used only for those cases where the capacity required is small. 14U Chassis Figure 21 shows the front view of a 14U mSwitch chassis
mSwitch
System Overview
92
Chapter 4 System Functional Components
Figure 21 4U Chassis (Front View)

Chassis Alarm Panel Fan Power Module
Functional Module Board
Fan
The upper part of the chassis is used for DC/DC power supply module (DPS) and its backplane provides 6 DPS slots. The lower part is used for functional modules, and its backplane provides 21 slots. Since slots are not designed to offer the same kinds of buses, some slots on the backplane are not universal. For example, slot9, 11 can accept only MPU boards; slot10, 12 only for HSC/HSM boards; PPU and PEM boards can be plugged in slot3-8, 13-18; SEM and EAM boards can be plugged only in slot1, 2, 19, 20, and must be on the same side with PEM-HD; ESEM can be plugged only in slot 19, 20; and CLK boards can be plugged only in slot 21, which consists of two 3U slots. Based on the above principle, the system can be flexibly configured according to the actual requirements of application and network planning. 4U Chassis There two types of 4U chassis: CH1200 and CH1210. Both of the two can be amounted on an EIA standard 19 rack, and use almost the same components, except the power supply module; CH1200 uses a DC/DC power supply module (DPS), while CH1210 uses an AC/DC power supply module (APS). The DPS/APS, Chassis Management System module (CM1210) and function boards are to be installed on the front part of the chassis; and the IEE1101.11 compliant rear-panel boards and the fan on the rear part. The main power switch is also on the rear side of the chassis. Figure 22 and Figure 23 show the front view and rear view of a 4U mSwitch chassis respectively.
System Overview
mSwitch
93
Figure 22 4U Chassis (Front View)
CM1200 CMS DPS/APS Power Supply DPS/APS Power Supply DPS/APS Power Supply
RH4000 RH4000 PEM/PPU PEM/PPU PEM/PPU PEM/PPU SEM/EAM CLK (slot 8) CLK
(slot 1) (slot 2) (slot 3) (slot 4) (slot 5) (slot 6) (slot 7) (slot 9)
Dust Filter
Figure 23 4U Chassis (Rear View)
(slot 1) (slot 2) (slot 3) (slot 4) (slot 5) (slot 6) (slot 7) (slot 8) 8) (slot
RT3010 RT3010 32E1 or STM-1 32E1 or STM-1 32E1 or STM-1 32E1 or STM-1 EAM II/SEMI/O/EAMI/O CLK I/O
Fan unit
Being CompactPCI compliant, this type of chassis provides slots to accept 6U boards and 3U boards (CLK boards), including front-panel and rear-panel boards. Among these slots, slot1 and slot2 are used for CPU boards; slot3~6 for nonsystem board, slot7 for switching board, slot8 and slot9 for CLK boards.
Components in Service/application Layer

The service/application layer of mSwitch system includes the following network elements:
mSwitch
Parlay GW Parlay APP Feature Server (FS).

System Overview
94
Parlay GW
The Parlay GW is the bridge between the network layer (control layer and access layer) and the application servers in the service/application layer, providing open API (PARLAY/OSA) needed in third party service development. It is a highly abstracted representation of the lower network capabilities, delivering fully transparent interfaces that allow applications in upper layer to make full use of the resources in the network layer without awareness of the network structure, hence a unified platform for developers to flexibly and efficiently develop value-added services, including dynamically and seamlessly add new service functions into the system and upgrade the existing service functions. In order to provide value-added services, an application server is required to work with Parlay GW. This server is implemented as a module called Parlay APP. The Parlay Framework Server, Parlay APP, and various Parlay service function modules coordinate with one another to form an API platform that can flexibly deliver NGNenabled value-added services of diversified types. Figure 24 shows the architecture of such an API platform. Figure 24 Parlay API Structure
P arlay App App3 App2 App1
P arlay C hassis P arlay G W
SF 3 S F2 S F1 P arlay S ervice
In this architecture, the Parlay APP offers an environment for service logics to reside and execute. There could be multiple Parlay APP instances; each of them is required to register its existence in the Parlay Framework Server. When the Parlay APP calls a service, it goes first to the Parlay Framework Server to get the desired service interface, and then uses this interface to access network resources needed. The Parlay service function module provides the network capabilities and related information needed by service applications, such as call control, subscriber information exchange, mobility, and connection management. A Parlay service function module could include multiple service instances; and this module is also required to register all of its instances in the Parlay Framework Server. The Parlay Framework Server provides all the security and management capabilities needed by Parlay service function modules. It acts like a depot, storing service functions (SCF). Each application goes to the depot to select the desired SCF and state that it will use the selected SCF. In other words, it plays as a bridge between the services available and the applications substantiating these services, allowing third party application developers to fully leverage the network capabilities.
95
Parlay APP
The Parlay APP holds various kinds of applications based on Parlay GW; it uses standard API to interact with the Parlay GW, hence allows third party service providers to develop applications, and offers more choices for carriers serve different types of subscribers. At present, The Parlay APP provided by UTStarcom provides the following services: iNumber UPT VPN Multimedia Conference (iWeSee) Enhanced Wide Area Centrex (iWAC) One Number Two Sets (one number shared by a PHS set and a PSTN phone)
Feature Server
The Feature Server (FS) is an important network element in intelligent network service solution of mSwitch. It consists of multiple logic entities, which provides different applications for different solutions. Currently, the FS mainly provides the following applications: FS Acting as an SCP in the IN System The Feature Server (FS) works as an SCF instance in mSwitch-based IN service platform. It stores service logic and service data, and can complete the following tasks involved in IN call process control: Receives requests from SSP Query related service data Execute service logic Completes coding/decoding Sends instructions to SSP
At present, the FS in mSwitch network is mainly used to process prepaid VAS logics (300 service, for example), namely works with PSC to enable logic control for prepaid subscribers over the whole network. The FS also plays as an SCP to provide service logics for third party networks, including authentication and billing functions needed in VAS provisioning for prepaid subscribers, for example, processing CRBT customization fee, and supporting Information on Demand service provided by content providers (CP). It can also detect and manage, hence efficiently control subscribers call status, for example, change a subscribers call status in case of abnormal occurrence or being requested by the subscriber. The location of the FS in mSwitch network is illustrated in Figure 25.
mSwitch
System Overview
96
Figure 25 Location of the FS in mSwitch Network
i AN-2000
i AN-2000
FS Acting as USSD Server in IN Service Solution In the mSwitch-based SIM Card Roaming service platform, the FS acts as the functional entity of USSD Server to provide interactive mobile data service (USSD service) for GSM subscribers. The USSD Server is the bridge for data transport between subscribers and system device. The exchanged interactive data includes calling and called subscriber information in callback service logic, service activation and deactivation information of subscribers, bound numbers of various services, query information of subscribers, and so on. The figure below illustrates the position of FS when acting as USSD Server in mSwitch network
System Overview
mSwitch
97
Figure 26 Position of FS Acting as USSD Server in mSwitch Network
In the mSwitch SIM Card Roaming service network, there are the following network entities in addition to the FS: Home Location Register (HLR), Signaling Access Unit (SAU), and IP-based Signaling Gateway (iSG) The HLR is responsible for data management and authentication of subscribers. The subscriber data under the management includes authentication data, subscriber profile, service data, correspondence between International Mobile Subscriber Identity (IMSI) of SIM Card Roaming service subscribers and visited area identity, correspondence between home Mobile Subscriber ISDN Number (MSISDN) of SIM Card Roaming service subscribers and visited area identity, and all number resources in different visited areas. The HLR also stores service activation/deactivation data (resolved from the USSD Server) and service bind number. In addition, the HLR provides MAP-SNSP signaling conversion for the USSD Server. Functioning as the MAP adapter of the HLR, the SAU implements protocol conversion between application layer and service layer of MAP. The iSG implements conversion function of underlying bearer protocols of signaling messages between the (IP-based) mSwitch SIM Card Roaming service network and (SS7-based) visited network. Prepaid Service Center (PSC) The PSC has CDR collection, pricing functions for both prepaid and postpaid subscribers. The USSD Server communicates with the PSC to fetch the account balance of prepaid subscribers or recharge the accounts of prepaid subscribers. Credit Card Agent The Credit Card Agent offers an interface to the bank credit card center. Upon receipt of requests from the USSD Server, the Agent initiates credit card recharge, cancellation, or query operations to the bank credit card center.
SN
SP
SP SN
98
IP-based Call Server (iCS-P) The iCS-P communicates with the call server in a third-party VoIP network through the Session Initiation Protocol for Telephones (SIP-T). The iCS-P implements number analysis, routing, and call processing functions. Upon receipt of a callback request from the USSD Server, the iCS-P initiates a SIP-T call to the calling and called parties.
Components in Control Layer

The control layer of mSwitch system includes the following network elements: iCS-P, TS, HLR, VLR, SAU and CPS2100.
iCS-P
An iCS-P is a caller server working at access layer, featuring rich service provisioning functions and powerful networking capabilities; it can: Work as a C5 office to provide access support for IP terminals based on different types of protocols, such as MGCP, H.248, SIP and Q.931 Work as a C4 office to support SS7 signaling and by coordinating with other gateways such as iSG and iUMG, to interconnect with PSTN networks and provide call processing functions, including number analysis and routing functions. Work as an H.323-enabled GW to interconnect with traditional VoIP GW and traditional MCU used in conference, or directly provide access support for H.323 IP terminals. Work as a GK to enable NAT (network address translation), access control, broadband control, and so on. Work as an SSP, coordinating with Parlay platform, to implement various kinds of IN services.
Figure 27 illustrates the external interfaces an iCS-P may use to interconnect with different type of NEs under different networking solutions that meet carriers needs for service provisioning.
System Overview
mSwitch
99
Figure 27 External Interfaces of the iCS-P
Protocol interface with Parlay GW: Parlay GW manages logic needed in IN services; iCS-P communicates with Parlay GW through SNSP when implementing Q-Box service; and through SIP-T protocol when implementing iNumber/UPT service. So, a Parlay GW is a bridge between the network layer (control layer and access layer) and the application servers in the service/application layer, providing open API (PARLAY/OSA) needed in third party service development, a unified platform for developers to flexibly and efficiently develop value-added services, to seamlessly add new service functions into the system. Protocol interface with SLR: iCS-P communicates with SLR through internal SNSP to sends messages related to mobility management, call management, supplementary service management, and routing management. In mobility management, SLR specifies which iCS-P a terminal being served currently belongs to, records the terminals location information. The
System Overview
mSwitch
100
messages exchanged include those induced when terminals registering to an iCS-P, powering off, and changes its current location. In call management, iCS-P resorts to SLR to authenticate call validity. In supplementary service management, iCS-P updates supplementary service related data stored in the SLR. The messages exchanged include those induced when a subscriber activating/deactivating, canceling/registering supplementary services, and querying service status. In routing management, iCS-P gets C4/C5 route information from SLR. The messages exchanged mainly include messages carrying route information and roaming-related information.
Protocol interface with PSC: iCS-P communicates with PSC through SNSP.
Note: An iCS-P is a billing data collection points; it collects, sorts and post-processes CDRs of subscribers it serves, and sends the results to PSC by issuing SetCDR requests. Protocol interface with CN SNMS: iCS-P can be managed through the mSwitch CN SNMS; it communicates with CN SNMS through SNSP to implement fault management, configuration management, performance management, and service status control. Protocol interface with iUMG: iCS-P communicates with iUMG through IUA/MEGACO, with IUA used for signaling conversion and transfer, and MEGACO for media control. Protocol interface with iUMG: iCS-P communicates with iMG through SNSP/SIPT. Protocol interface with other iCS-P servers: iCS-P servers communicate with one another through SNSP/SIP-T. Protocol interface with iSG: iCS-P communicates with iSG through SIGTRAN to enable transmission of SCN (Switch Circuit Network) signaling over IP network; the signaling conversion between ISUP/TUP over IP and ISUP/TUP over TDM are implemented through ISUP/M3UA. Protocol interface with SBC: The SBC is a security device that assists IP terminals to be put through firewall to mSwitch system; iCS-P communicates with SBC through SIP or MGCP. Protocol interface with iAN8000/IAD: iCS-P communicates with iAN8000/IAD through MGCP to enable access control for iAN8000/IAD as well as POTS subscribers. Protocol interface with IP terminals: iCS-P supports access control for IP terminals based on different protocols, including MGCP, SIP, H.323, H.248 and so on.
At present, the iCS-P-based services include:

System Overview
PWLAN Q-Box iNumber

mSwitch
101
Accounting Card Calling PHS Prepaid PSTN Prepaid iWAC CRBT Multi-session GetAlt enabled Prepaid Phone Bar PC Phone Multimedia Conference (iWeSee.)
Technical specifications: Table 6 iCS-P Performance Specifications

Parameter Processing capability (per AS) System processing capability Specification 150 K BHCA 750 K BHCA
Transaction Server
In mSwitch, the transaction server (TS) is located at the control layer, providing functions for subscribers data management through its DB Cache, including mobile management, call routing, service control, system resource management, subscriber profile management, and so on. The TS consists of such sub-modules as SLR, iTS, Event Handler, MCNC, and so on. These modules coordinate with one another to enable various functions such as authentication, authorization, address resolution, IP terminal identification, routing analysis, and to support various types of supplementary services, inter-domain roaming among mSwitch/iPAS/PAS domains, and interconnection with third party networks. The MCNC, in particular, is a somewhat independent function module, which stores missed call records, and delivers MCN messages to called party subscribers when becoming accessible. The functions of each module are described below: SLR (Subscriber Location Register) stores and maintains subscribers information; SLR supports n+1 load sharing; and multiple SLRs support backup for each other. The data to be maintained are listed below: Subscribers profiles, general information, basic service information, supplementary information and IN service information. Subscriber location information Routing information
Interface Routing Server (iTS), which interconnects with iTSs in other mSwitch domains to enable data transmission and routing resolution among different networks. iTSs in different domains communicate with each other through IP
System Overview
mSwitch
102
network and Softswitch network using private SNSP protocol. Currently iTS supports active/standby redundancy. Event Handler enables synchronization between DB and SLR, and also among multiple SLRs and iTSs. Missed Call Notification Center (MCNC) stores missed call records (MCR) for PHS subscribers. When a subscribers phone is powered off or unreachable (outside the service area), the system will record calls to the subscriber; when the subscriber is reachable (such as performing registration at a new location, powering on to make a call), MCNC will notify the subscriber. In addition, the system will also periodically try the notification. mSwitch delivers two types of MCN services: CLIP-based MCN and SMS-based MCN. CLIP-based MCN is implemented by sending MCR to subscribers home gateway; while SMS-based MCN is implemented by sending MCR to SMSC, which ten relay the MCR as a SMS to subscribers through SMS gateway (SMS-based MCN is available in mSwitch2.5).
The TS modules (such as SLR, iTS, MCNC, Event Handler) communicates with majority of the functional modules using internal protocols, except the interface to the network management system. It can also communicate with the third party networks using H.323 RAS and SIP/SIP-T protocols. See the figure below.
System Overview
mSwitch
103
Figure 28 TS External Interfaces and Protocols

Third party PHS Network/GSM Network
MAP
SS7
CN-SNMS
SNMP MAP
HLR/VLR
SNSP
SNMP API
iTS in another mSwitch domain
Event Handler
TCP/IP SNSP
TS
DB
SNSP
SLR
SNSP SNSP
SNSP
iTS
IP Network
MCNC
SAM
CBK
SNSP
SMSC
iCS-T
iCS-P
SLR/RS coordinates closely with iCS-P and iUMG, to provide various subscriber data, location and routing information to these entities, and to perform operations involved in call process, such as subscriber authentication and authorization, call setup and processing, advanced service control and implementation, and in particular, providing C4 routing information to iCS-P and C5 routing information to iCS-P and iUMG. SLR employs API to communicate with DB, and the synchronization between SLR and DB is implemented by the synchronization mechanism of Event Handler (TSEH). The DB is the bridge between SLR and SAM for exchange of information, e.g., subscriber data updating etc; TS/HLR/VLR communicates with CN SNMS through standard SNMP to enable various management functions such as configuration, control, performance statistics and alarms; iTS interfaces with external networks to process all the routing requests forwarded by SLR, thus assisting SLR to complete routing tasks. The iTS uses SIP to communicate with SIP Proxy of third party softswitch network; it also support standard H.323 RAS to communicate with Gatekeeper (GK) of third party H.323 networks.
System Overview
mSwitch
104
MCNC is used to store the Missed Call Records (MCR) of the PHS subscribers. When a PHS handset is powered off or not reachable (for example, moving out of the signaling coverage area), the system will record the calls to this subscriber; and when the subscriber is available, the MCNC will notify the subscriber. At the same time, the MCNC periodically tries to send missed call notification. mSwitch system provides two modes of MCN. One is caller-based CLIP. The other is short message. HRL/VLR is used to enable the data exchange when mSwitch system interconnects with third party PHS/GSM network. CBK is used to back up the important data of other applications caches in the local server, in a real time basis. It mainly serves the SLR currently, for backing up VAS data. SLR uses SNSP to communicate with VAS servers, such as MCNC (missed call notification center) SMGW (short message service gateway), to provide location query functions to these servers.
HLR
The Home Location Register (HLR) is a database used to store location information of local subscribers. Each mSwitch local network (an area) has a HLR, and each PHS subscriber is registered in a HLR. The content of the registration can be classified as two types: one holds permanent parameters, such as phone number, mobile device ID, and access PRI, service types subscribed, and so on; the other holds temporary, parameters that are easily subject to change, that is, those about subscribers current location. In mSwitch network, the HLR is mainly used to communicate with third party network. It is a SNSP-MAP protocol adapter as shown in Figure 29. With this function, mSwitch subscribers can roam into third party system. Currently, UTStarcom provides three HLR solutions: one is a pure HLR product, another is a combined product of SLR and HLRA, and the third is a combination of SLR, GHLRA, and SAU. For the SLR+HLRA solution, when the SLR accesses a third party database, the HLR converts the SNSP protocol used by the SLR to MAP protocol to achieve SLR access to the database of the third party PHS system and thus achieve mSwitch subscriber roaming in the third party PHS system. The SLR+GHLRA+SAU solution separates the common protocol stack from the SLR+HLRA solution to a common module called Signaling Access Unit (SAU) which is also available for other server network elements requiring protocol conversion.
System Overview
mSwitch
105
Figure 29 Protocol Conversion through HLR
VLR
Visited Location Register (VLR) a database used to store location information of visiting subscribers. Typically, a HLR serves one local network. When a PHS subscriber roams to a PHS network, it must register to the VLR in the visited location. The VLR queries information from the subscribers HLR, assigns the subscriber a new MSRN, and inform the HLR of the subscribers location, so that calls to the subscriber can get routing information. If the subscriber roams from a location served by a VLR to another location served by another VLR, the HLR, after update the subscribers location information, will inform the previous VLR to delete the subscribers location information. In mSwitch network, the VLR is mainly used to communicate with third party network. It is a SNSP-MAP protocol adapter; as shown in Figure 30, when the SLR accesses the data of a third party system, the VLRA converts the SNSP protocol used by the SLR into MAP protocol, so as for SLR to access the data in the third party system. With this function, mSwitch subscribers can roam into third party PHS system. Currently, UTStarcom provides two VLR solutions: one is a combined product of SLR and VLRA, and the other is a combination of SLR, GVLRA, and SAU. The SLR+GVLRA+SAU solution separates the common protocol stack from the SLR+VLRA solution to a common module called Signaling Access Unit (SAU) which is also available for other server network elements requiring protocol conversion.
mSwitch
System Overview
106
Figure 30 Protocol Conversion through VLR
SAU
Signaling Access Unit (SAU) functions as a protocol adaptor. In an mSwitch network, it performs application layer / service layer protocol conversions for the signaling messages. The SAU supports INAP/CAP/MAP/WIN-MAP protocol adaptation. In addition, the SAU provides routing function. It routes the service requests from the intelligent network access layer to the appropriate NE. The SAU can be installed on a server together with NEs that require protocol adaptation, for example, Feature Server (FS), HLR, and VLR. The SAU can also be installed on a server individually. The SAU architecture is shown in Figure 31. Figure 31 SAU Architecture
SAU Common Protocol Adaptor
WIN-MAP/ CAP/MAP/ INAP Tight coupling TCAP SCCP M3UA SCTP Common Protocol Loose coupling
System Overview
mSwitch
107
The SAU works along with different network elements in the mSwitch network to deliver different functions. FS+SAU+SE=SCP The FS performs service control point (SCP) function for the service logic and service data of intelligent network applications. Connected to the iSG through the SAU, the FS processes SS7-based service activation messages and provides intelligent services for SS7-based end users. The SAU, as a protocol adaptor for the FS, performs application layer / service layer protocol conversions. It supports INAP/CAP/MAP/WIN-MAP protocol adaptation. In addition, the SAU is capable of routing service requests from the IN access layer to the appropriate FS. The SAU communicates with the FS using INAP/CAP/MAP/WIN-MAP protocols. It assists the FS in implementing active/standby service processing and load sharing. The SAU communicates with FS using INAP/CAP/MAP/WIN-MAP. Figure 32 FS + SAU Functioning as SCP
SLR+GHLRA+SAU=GHLR In a WiFi/GSM FMC solution, the SLR, GHLRA and SAU collectively perform HLR functions. The GHLR delivers all basic HLR/AUC/EIR functions compatible with GSM standards, including call management, location update, roaming area management, authentication, and device management. The GHLR also provides short message service and a range of supplementary service, for example, call forwarding, call restriction, caller identification display, and unstructured supplementary services. The SLR, GHLRA, and SAU can be installed on one server, or on different servers. The SAU, as a protocol adaptor for the SLR, performs application layer / service layer protocol conversions. It supports INAP/CAP/MAP/WIN-MAP protocol adaptation. In addition, the SAU is capable of routing service requests from the
mSwitch
System Overview
108
iCS-P to the appropriate HLR. The SAU assists the SLR in implementing active/standby service processing and load sharing. Figure 33 GHLR and GVLR Deployed in WiFi/GSM FMC Solution
SLR+GVLRA+SAU=GVLR In a WiFi/GSM FMC solution, the SLR, GVLRA and SAU collectively perform VLR functions. The GVLR serves the mobile subscribes within its coverage area. The SAU, as a protocol adaptor for the VLR, performs application layer / service layer protocol conversions. It supports INAP/CAP/MAP/WIN-MAP protocol adaptation. In addition, the SAU is capable of routing service requests from the iCS-P to the appropriate VLR. The SAU assists the VLR in implementing active/standby service processing and load sharing.
SLR+CHLRA+SAU=CHLR In a WiFi/CDMA FMC solution, the SLR, CHLRA and SAU collectively perform CHLR functions. The CHLR functions as the HLR of the home VoIP network. It stores the location information of the home domain subscribers, and is responsible for the data management and authentication of the terminal subscribers. The CHLR also supports IS-41 protocol and communicates with the VLR of the CDMA network. The SAU, as a protocol adaptor for the SLR, performs application layer / service layer protocol conversions. It supports INAP/CAP/MAP/WIN-MAP protocol adaptation. In addition, the SAU is capable of routing service requests from the
System Overview
mSwitch
109
iCS-P to the appropriate CHLRA. The SAU assists the SLR in implementing active/standby service processing and load sharing. Figure 34 CHLR and CVLR Deployed in WiFi/CDMA FMC Solution
SLR+CVLRA+SAU=CVLR In a WiFi/CDMA FMC solution, the SLR, CVLRA and SAU collectively perform CVLR functions. The CVLR functions as the VLR of the home VoIP network. In addition, it supports IS-41 protocol and communicates with the HLR of the CDMA network. The SAU, as a protocol adaptor for the SLR, performs application layer / service layer protocol conversions. It supports INAP/CAP/MAP/WIN-MAP protocol adaptation. In addition, the SAU is capable of routing service requests from the iCS-P to the appropriate CVLRA. The SAU assists the SLR in implementing active/standby service processing and load sharing.
HLR+HLRA+SAU=HLR (SIM Card Roaming service) The SIM Card Roaming service application deploys HLR, HLRA and SAU to collectively perform HLR functions. The HLR manages the following data of the SIM Card Roaming service subscribers: mapping relationships between IMSI and numbers of the visited networks, mapping relationships between MSISDN and numbers of the visited networks, all number resources of the visited networks. The HLR also stores the service activation/deactivation data resolved by the USSD server, and the service bounded numbers.
mSwitch
System Overview
110
Figure 35 HLR Deployed in SIM Card Roaming Service Solution
CPS2100
As an independent NE of the mSwitch core network, Common Protocol Server (CPS) provides common protocol stack for other NEs, enabling the related NEs to process certain protocols. The CPS2100 can provide these protocols: MAP, PHS-MAP, INAP, CAP, IS-41 and other application protocols. It can serve such NEs as iCS-P, iCS-T, HLR, VLR, FS, SMSC and Parlay GW. The following part details the functions and implementation of the CPS2100. As shown in Figure 36, the CPS2100 is at the network edge, providing standard interworking protocol to the relevant NEs when the mSwitch network is interconnected with a third-party network, for the purpose of interworking.
System Overview
mSwitch
111
Figure 36 Position of CPS2100 in Network

iCS-P iCS-T SMSC
CPS2100
SG mSwitch network
PSTN
The 3rd party Signal Access Device The 3rd party MSC/ VLR,SCP,HLR,SMSC etc
The communication protocols inside the mSwitch network are over IP, but the thirdparty network may be based on TDM. Therefore, before the signaling is transported to the mSwitch network, signaling conversion must be performed by the Signaling Gateway (SG) which translates MTP1~3 protocols to M3UA/SCTP/IP (SIGTRAN) protocols. In the mSwitch network, the call server (iCS-P/iCS-T) communicates with the Short Message Service Center (SMSC) using SNSP. When interconnected with a thirdparty network, the mSwitch system communicates with the third-party network using MAP, CAP, INAP, and/or IS-41 protocols. In such case, the SG performs signaling conversion, but call servers and server type NEs cannot identify application layer protocols. They need to invoke the common protocol stack of the CPS2100 to translate the protocols. At present, the communication between the CPS2100 and the corresponding served NEs is fulfilled in client/server mode. The CPS2100 serves as the server, and packs such communication protocols as MAP, CAP, INAP and IS-41 and then performs transmission based on the Trillium standard. The corresponding served NE serves as the client. To invoke a standard protocol for message resolution, the served NE working as the client sends a request to the server. The CPS working as the server monitors the request from the client, and provides response to this client. In this way, the communication between the CPS2100 and the served NE is fulfilled. Table 7 describes the CPS-provided standard protocols used by each served NE in the current applications.
mSwitch
System Overview
112
Table 7 Usage of CPS-Provided Standard Protocol Stack by NEs in mSwitch Network

NE Name Used Protocol Description INAP is used for interworking with the PSTN Intelligent Network (IN). CAP is used for interworking between the iCS-P serving as the SSP with the SCP in IN. INAP is used for interworking with the PSTN Intelligent Network (IN). CAP is used for interworking between the iCS-T serving as the SSP with the SCP in IN. MAP is used for processing the messages of the C interface (between HLR and MSC) and D interface (between HLR and VLR) in the interworking with the third party using the GSM-standard network. HLR MAP, IS-41, PHS-MAP IS-41 protocol is used for processing the messages of the C interface (between HLR and MSC) and D interface (between HLR and VLR) in the interworking with the third party using the ANSI-standard network. PHS-MAP is used for processing the messages of the C interface (between HLR and MSC) and D interface (between HLR and VLR) in the mSwitch internal network. MAP is used for processing the messages of the D interface (between HLR and VLR) in the interworking with the third party using the GSM-standard network. VLR MAP, IS-41, PHS-MAP IS-41 protocol is used for processing the messages of the D interface (between HLR and VLR) in the interworking with the third party using the ANSI-standard network. PHS-MAP is used for processing the messages of the D interface (between HLR and VLR) in the mSwitch internal network. MAP is used for processing the Short Message Service (SMS) requests sent from the HLR in the GSM-standard network. IS-41 protocol is used for processing the SMS requests sent from the HLR in the ANSI-standard network. PHS-MAP is used for processing the SMS requests sent from the HLR in the mSwitch network. IS-41 protocol is used by the FS serving as SCP for processing the service triggering requests sent from the SSP in the ANSI-standard network. FS IS-41, INAP, CAP INAP is used by the FS serving as SCP for the service triggering requests sent from the PSTN. CAP is used by the FS serving as SCP for the service triggering requests sent from the GSM-standard network. processing SSP in the processing SSP in the
iCS-P
INAP, CAP
iCS-T
INAP, CAP
SMSC
MAP, IS-41, PHS-MAP
Note: At this stage, the CPS2100 does not provide protocol stack service for HLR, VPR, FS and Parlay GW. It is available in later versions.
System Overview
mSwitch
113
Components in Access Layer

The access layer of mSwitch system includes the following network elements: iUMG iSG iMS
iUMG
The IP-based Unified Media Gateway (iUMG) is controlled by the CS-P to provide media conversion and switching functions between the mSwitch network and PSTN. The iUMG provide access support for both PHS and PSTN terminals. When serving PHS terminals, it works as a media switching device to complete media conversion and control, and at the same time, send call singling to iCS-P in transparent mode, hence complete call connection or routing under the control of iCS-P. When serving PSTN terminals, it works as a trunking gateway to complete media conversion and control, namely, to interconnect with PSTN network, and if necessary, to provide new services for PSTN subscribers. Figure 37 iUMG External Interfaces
The iUMG involves the following external interfaces: Protocol interface with CN SNMS: iUMG can be managed through the mSwitch CN SNMS; it communicates with CN SNMS through SNSP to implement fault management, configuration management, performance management, and service status control.
System Overview
mSwitch
114
Protocol interface with CSC/RPC: the iUMG communicates with the CSC/RPC using IUA protocol. Protocol interface with iCS-P: iUMG communicates with iCS-P through IUA or M2UA for signaling exchange, and through to MEGACO for media control.
Listed below are iUMG performance specifications: Up to 38400 IP channels (supporting G.711 codec without echo suppression) Up to 504 E1 ports and 672 T1 ports Up to 32 MTP2/M2UA signaling links Up to 1024 LAPD/LAPV5 signaling links
Optical interface specifications summarized in Table 8. Table 8 Optical Interface Specifications

S1.1 Parameter Optical Transmit Power Measured Range Min. Max. Center Wavelength Receiver Overload Standard Standard Typical Sensitivity Standard Typical Unit dBm dBm nm dBm dBm dBm dBm Measured Value -15 -8 1310 > -8 0 < -31 -38
Electrical interface specifications summarized in Table 9. Table 9 Electrical Interface Specifications

E1 Parameter Bitrate Coding Impedance Signal Amplitude Jitter Unit kbit/s V Measured Value 2048 HDB3 75 (120) +/-2.37 (+/-3.00) G.823 compliant
iSG3200
In mSwitch, the signaling gateway (iSG) works as a signaling converter between SS7 signaling networks and IP network. Hence enables interconnection between mSwitch and PSTN/IN. In mSwitch R5.3, the iSG is implemented by iSG3200, which supports up to 128 64Kbit/s signaling links. In practice, the iSG is mainly used for signaling conversion. The figure below illustrates the conversion relation among the involved protocols:
115
Figure 38 Signaling Conversion between mSwitch and PSTN/IN enabled by iSG
As shown in the above figure, iSG mainly carries out signaling protocol conversion, i.e. the conversion between MTP1~3 and M3UP/SCTP/IP (SIGTRAN). This conversion is transparent for protocols at user layer. Protocols involved are described below: ISUP is used to enable transmission between iUMG and SS7 signaling network, so as to support subscribers within the domain to communicate with PSTN network. MAP is used to enable transmission between HLR/VLR Adapter and SS7 signaling network, so as to support the mSwitch system to communicate with third party HLR/VLR through PSTN network, hence to interconnect with third party PHS system.
The iSG also communicates with the mSwitch CN SNMS through SNMP, so that it can be managed through CN SNMS, in terms of configuration, control, alarm, performance statistics, and so on. The iSG has five external interfaces as shown in the figure below:
mSwitch
System Overview
116
Figure 39 iSG External Interfaces
As shown in the above figure, four of these five are designed for use within mSwitch domain, connecting to IP networks in mSwitch through the Ethernet port of active MPU in iSG, and the rest is for third party networks outside mSwitch, connecting to SS7 networks through E1 interface.
iSG5.6
The iSG5.6 developed by UTStarcom is a new generation large-capacity signaling GW product. It can be located on the edge of an SS7 network and an IP softswitch network, and can implement the translation, adaptation and distribution functionality of SS7 and SIGTRAN signaling messages. It can also be located on the edge of two IP softswitch networks, and implement the adaptation and distribution functionality of SIGTRAN signaling messages. The iSG serves as the signaling translation device for interconnection between the IP softswitch network and the conventional PSTN/PLMN network, or between the IP softswitch networks. It is located on the edge of the mSwitch IP softswitch network and SS7 network, or on the edge of the third IP softswitch network and SS7 network. As shown in Figure 40, the iSG5.6 primarily implements translation, adaptation and distribution functionality for SIGTRAN and SS7 signaling messages on the bottom layer, and the translation, adaptation and distribution functionality for M3UA-based SIGTRAN signaling and M2UA-based SIGTRAN signaling.
System Overview
mSwitch
117
Figure 40 Position of iSG5.6 in mSwitch Network
The iSG5.6 accesses the IP network through Gigabit Ethernet and 100M Ethernet. In an mSwitch network, the iSG5.6 communicates with the following devices: Call Server: The call server comes in two types of devices: iCS-P and iCS-T. It is located on the switch & control layer of the mSwitch Softswitch network, and primarily performs call control and media connection control for packet-based voice, data, and multimedia services. IP-based Service Control Point (IP SCP): Provides service logic for controlling intelligent service requests. IP-based Home Location Register (IP HLR): Provides the database for storing location information of local subscribers on the mSwitch network; performs data management and authentication of the terminal subscribers. IP-based Visited Location Register (IP VLR): Stores the information of roaming subscribers on the visited domain. Online Billing System (OBS): Configures the tariff parameters for MTP message billing and sends them to the PSC which charges the MTP tickets. Core Network SNMS (CN SNMS): Provides GUIs for iSG5.6 configuration management, performance management, fault management, and operation & maintenance management.
The iSG5.6 can access an SS7-based PLMN/PSTN network through an E1 or T1 interface. It communicates with the local exchange, HLR, VLR and SCP on the PLMN/PSTN network. The iSG5.6 can also access the IP-based PLMN/PSTN network through Ethernet interface. It communicates with the local exchange, HLR, VLR, and SCP on the IPbased PLMN/PSTN network. The key performance specifications of iSG5.6 are listed in the table below:
mSwitch
System Overview
118
Table 10 iSG5.6 Performance Specifications

Parameter Maximum number of networks supported Maximum number of SPCs Maximum number of destination SPCs Maximum number of 56 k / 64 k MTP3 links Maximum number of 2 M MTP3 links Maximum number of MTP linkset Maximum number of MTP3 signaling route set Maximum number of MTP3 message screening rules Maximum number of MTP billing rules Maximum number of M3UA ASPs Maximum number of M3UA AS Maximum number of M3UA routes Maximum number of M3UA SPMC Maximum number of M2PA links Maximum number of SCTP association Maximum number of SCCP routes Maximum number of SCCP GTT rules Maximum number of SCCP GTTs Maximum number of SCCP message screening rules Maximum number of GTTs Maximum number of MSUs Reliability index 56 k / 64 k link load (single link) 2 M link load (single link) Message loss ratio Message sequence error ratio unnoticeable error rate High availability Down time Regular Maximum Regular Maximum Single Chassis 32 32 256 256 16 128 2048 2048 2048 512 1024 2048 1024 1024 2048 2048 256 2048 2048 100000 100000 >=99.999% <=5 minutes/year TUP/ISUP>=0.2Erl MAP/INAP>=0.4Erl TUP/ISUP>=0.7Erl MAP/INAP>=0.95Erl <10
-7
Eight Chassis 32 256 1024 256*8=2048 16*8=128 128*8=1024 2048 2048 2048 512 1024 2048 1024 1024 2048 2048 256 2048 2048 100000*8=800000 100000*8=800000 >=99.999% <=5 minutes/year TUP/ISUP>=0.2Erl MAP/INAP>=0.4Erl TUP/ISUP>=0.7Erl MAP/INAP>=0.95Erl <10-7 <10-10 <10-10 90% of the messages <80ms <160ms <400ms 90% of the messages <80ms
mSwitch
<10-10 <10-10 50% of the messages
iSG delay time caused by M3UA module
Under normal load Under 15% overload Under 30% overload
<40ms <80ms <200ms 50% of the messages
iSG delay time caused by M2PA module Under normal load

System Overview
<40ms
119
Parameter Under 15% overload Under 30% overload
Single Chassis <80ms <200ms
Eight Chassis <160ms <400ms
The table below lists the external interfaces and protocol specifications the iSG5.6 uses: Table 11 iSG5.6 External Interfaces and Protocol Specifications
Physical Interfaces and Protocols Interface Type E1 10/100 Base-T 1000 Base-T RS232 Rate (bps) 2.048 M 10/100 M 1000 M 115200 Specifications ITU-T I.431, G.703, G.736, G.823, G.704, G.706, Q.703, G.732, ANSI T1.403 IEEE802.3 IEEE802.3 V.24/V.28
Logical Interfaces and Protocols Interface Type M2PA M3UA SCTP SNMP SS7 Specifications IEFT Draft11 RFC3332 RFC2960 V2c ITU-T Q.701~Q.706, Q.711~Q.715 ANSI T1.111- SS7 MTP1, MTP2, MTP3 ANSI T1.112 - SS7 Signalling Connection Control Part(SCCP) ANSI T1.113 - SS7 ISDN User Part(ISUP) ANSI T1.114 -SS7 Transaction Capabilities Application Part(TCAP) YD/T1180-2002, Technical Specification of the SS7 Network Management Interface MTP Part and SCCP Part
Table 12 and Table 13 list the physical specifications of the iSG5.6. Table 12 iSG5.6 Physical Specifications
Parameter Specification Width Rack Size Depth Height Rack Weight Empty Rack Full Configuration Width Chassis Size Depth Height Chassis Weight
mSwitch
650 mm 1100 mm 2200 mm 120 kg 400 kg 19 (483 mm) 15 (381 cm) 24.5" (622 cm) About 120 kg About 400 kg
System Overview
Empty Chassis Full Configuration
120
Parameter Security Authentication EMI/EMC
Specification UL 1950 FCC Part 15 rule China GB6833
Table 13 Power Consumptions of the iSG5.6 Key Boards

Current (A) Function Board +3.3V ZT5550 series boards ZT4804 board RH3000 board HS3002 board HSM board HSM I/O board PEM-S7 board SP8201 board 32E1 I/O board (75 Ohm) 32E1 I/O board (120 Ohm) AP3001 board SPU board SEM2 board SEM I/O board CLOCK board CLOCK I/O board 2.7 0.0 4.8 2.0 2.0 0.0 4.7 6.1 2.5 3.1 2.5 5.9 0.0 1.0 0.0 +5V 2.2 0.5 2.7 0.0 0.0 0.0 0.7 0.5 0.7 2.8 3.3 1.7 0.0 0.0 0.0 +12V 0.25 0.00 0.01 0.00 0.00 0.00 0.01 0.00 0.00 0.00 0.03 0.00 0.00 0.00 0.00 Power Consumption (W) 22.91 2.50 29.46 6.60 6.60 0.00 19.13 22.63 22.91 24.23 25.11 27.97 0.00 3.30 0.00
Note: The maximum current of the air-break switch of each output on PDP is 20A. The environmental requirements of iSG5.6 are listed below: Table 14 Environmental Specifications
Environment Type Parameter Grounding Resistance Temperature Operating Environment Relative Humidity Weight Sustained by the Floor Sound Pressure Level (Noise Level) Storage Environment Temperature Relative Humidity
System Overview
Specification 0.5 (joint grounding) 0~+45 C 5% ~ 85% 600 kg/m2 65 dB -40 C ~+70 C 10% ~ 100%
mSwitch
121
Environment Type
Parameter Grounding Resistance Temperature
Specification 0.5 (joint grounding) 0~+45 C 5% ~ 85% 600 kg/m2 65 dB 1120 W/m2 600 W/m2 65 dB
Operating Environment
Relative Humidity Weight Sustained by the Floor Sound Pressure Level (Noise Level) Solar Radiation Heat Radiation
Equipment Noise
Sound Pressure Level (Noise Level)
Table 15 Power Module Specifications

Type of Power Supplies Nominal Value (V) Allowable Voltage Fluctuation Range (V) 0~300 Hz 300~3400 Hz 3.4~150 kHz Noise Voltage 150~200 kHz 200~500 kHz 500 kHz~30 MHz DC Power Supply 48 V 40 V ~ 57 V 100 mV peak-peak value 2 mV (the weighted noise is to be considered.) Single Frequency 5 mV effective value Single Frequency 5 mV effective value Single Frequency 3 mV effective value Single Frequency 1mV effective value Broadband 100 mV effective value Broadband 150 kHz~30 MHz 30 mV effective value
iMS
The iMS (Media Server) is designed to provide different types of media services for different types of terminals. Its service provision covers not only IP-based network but also traditional narrow band network, such as PSTN. The types of terminals supported include:
mSwitch
POTS under IAD/iAN-8000 PHS V5 POTS MGCP iAD H.323 IP terminal MGCP IP terminal SIP IP terminal
System Overview
122
iSmart1500 PC Phone
The types of media services supported include: 2k rated tone Conference call DTMF tone detection and DTMF tone generation CID, COT Announcement IVR Conference bridging (multiple conferences and conference center) Various kinds of Codec, including G711a/u, G723, and G729a/b Enhanced variable rate codec (EVRC)
In mSwitch network, iMS attends on iCS-P. These two instruct iMS to deliver to terminals various types of media services (announcement playback, number receiving, media resource needed in conference). The tables below summarize the technical specifications of iMS. Table 16 Performance Specifications
Parameter Processing capability Concurrent calls supported CPU peak usage CPU average usage Specification 82% 60%
Table 17 Reliability Specifications

Parameter Availability MTBF MTTR Down Time Specification 99.999% 106 hours 30 minutes (exclusive of preparation time) < 3 minutes per year
iAN-8000
The iAN-8000 is a new generation of Multi-Service Access Node (MSAN) that provides both narrowband and broadband services. In addition, it is a carrier-class Softswitch media gateway. The iAN-8000 provides V5 interface to interconnect with PSTN. It is equipped with an IP-DSLAM module to provide broadband Internet service and video service. It also provides MGCP/MEGACO protocol to interconnect with UTStarcom mSwitch system.
System Overview
mSwitch
123
Figure 41 iAN-8000 Network Topology

mSwitch
PSTN
LE
E1/V5 E1
SG/TG
ATM
HCM
GE FE iAN-8000 E1/V5 iAN-8000
Internet
ASM over:
-E1/T1 IMA -OCS3/STM-1
NR-600
MSTP Ring
SDT1/SDT12
iAN-8000 EoE
NR-600
FE/MGCP E1/V5 iAN-8000 iAN-8000
NR-600
V5/E1 iAN-8000
FE/MGCP
HDM
iAN-8000
IVD/FXS
IVD/FXS
IVD/FXS
IVD/FXS
IVD/FXS
IVD/FXS
For the voice applications, the iAN-8000 provides the V5.1/5.2 interface compliant with the ITU-T recommendation, for interconnection with switches supporting the V5 standard. The iAN-8000 also provides 2-wire POTS or an ISDN interface for a switch without the V5 interface. The iAN-8000 enables operators to eliminate costly platform migration by upgrading the original Z interface (2-wire) to the V5 interface. For broadband data application, iAN-8000 supports Internet broadband service and video service through multiple broadband service interfaces, such as xDSL and Ethernet. It also provides standard IP/ATM interface for interconnection with carriers backbone equipment. As a media access gateway, the iAN-8000 can inter-operate with UTStarcom's mSwitch platform or a third party Softswitch platform via the standard MGCP/MEGACO protocol. The iAN-8000 supports seamless access to both traditional networks and Next Generation Networks (NGN). It also supports multi-routing among PSTN, ATM and NGN/Softswitch networks. It enables smooth evolution from narrowband and broadband access to NGN. The iAN-8000 is a high-density multi-services access platform that supports both narrowband and broadband service interfaces. The iAN-8000 allows interchangeable broadband and narrowband service boards, and allows the carrier to configure different numbers of broadband users and narrowband users flexibly. The iAN-8000 has the following features:
mSwitch
A range of services supporting Open standards Standard interfaces VoIP features

System Overview
124
High reliability System security Unparalleled scalability Flexible networking deployment OAM features NGN migration Special features
A Range of Services Supporting Traditional narrowband services Plain Old Telephone service (POTS) ISDN Basic Rate Access (BRA) ISDN Primary Rate Adaptation (PRA) Leased line (2/4 wires audio private line) 64 kbps and lower data private line N 64 kbps data private line 2 Mbps channel (framed and unframed) Z interface (FXO module) ADSL, ADSL2 and ADSL2+ interfaces IP G.SHDSL interfaces LAN interface IP-based voice Transparent transmission and T.38 Fax over IP Transparent transmission Modem over IP Pulse billing and polarity reverse billing based on Softswitch platform Basic service, supplementary service and Centrex service based on Softswitch platform Intelligent and special services based on Softswitch platform
Broadband services
VoIP services
Co-existence of narrowband voice service and VoIP service through V5 interface and VoIP interface Multi-routing of POTS and VoIP voice through V5 interface and VoIP interface
Open Standards Narrowband access standards V5 interface defined in ITU-T Inter-operates with all industry standard PSTN switches as per ITU-T standards, such as ZXJ10, S1240, EWSD, F150, 5ESS, AXE10, C&C08, HJD04, and SP30
mSwitch
System Overview
125
VoIP standards MGCP (RFC3435), H.248/Megaco(RFC3525) G.711, G.729, G.726, G.723.1 T.38, T.30 RTP/RTCP, RFC2833 Inter-operates with UTStarcom mSwitch in addition to other third party Softswitch platforms that comply with IETF/ITU-T standards, such as Huawei, ZTE, Broadsoft, OKI, and Teligent ADSL ITU-T G.992.2, ITU-T G.992.1, ANSI T.413 ADSL2/2+ ITU-T G.992.3, ITU-T G.992.5 G.SHDSL ITU-T G.992.1.2 TCP/UDP/IP DHCP, TFTP, TELNET, SNTP/NTP IEEE 802.3 & 802.3u, IEEE 802.1Q
Broadband access standards -
TCP/IP standards -
Standard Interfaces Interfaces on the subscriber side POTS interfaces FXS, FXO ISDN BRI (2B+D), PRI 2/4 wires audio interface, V.24 and V.35 interfaces G.703 E1 ADSL G.dmt/G.Lite ADSL2+ SHDSL FE electrical interface G.703 E1 STM-1 GE optical/electrical interface FE optical/electrical interface FE RS-232
Interfaces on the network side:
NMS interfaces
VoIP Features ITU-T standard voice encoding G.711, G.726 (32k), G.729AB, and G.723.1 Real-time voice encapsulation and decapsulation based on the RTP/RTCP protocol
System Overview
mSwitch
126
DTMF detection, generation and relay Caller ID with number display TX/RX gain control Quality Enhancement Technology Dynamic, intelligent jitter buffer (maximum 500 ms), Echo cancellation (up to 64 ms), Compensation for lost packets, Voice Activity Detection (VAD), silence suppression and Comfort Noise Generation(CNG) QoS IP Precedence, prioritizing voice over data, VLAN tagging and ToS tagging Dynamic coding switching. Switch over time is less than 60 ms Convergence 1:11:8 Each iAN-8000 system provides up to 2880 subscribers access Support 20K BHCA(Busy Hour Call Attempt), 6 CPS(Call Per Second) 1:1 redundancy of system modules (SCM4, VPM) VPM module supports load balancing Each node can contains up to 6 VPM modules, provides up to 720 call access capacity Carrier's voice quality, supports basic services, supplementary service and Centrex service T.38 Modem services
High Reliability Dual homing iAN-8000 can register to two Softswitch platforms simultaneously. When the switch failure occurs, the iAN-8000 system can switch to another switch automatically, without affecting service V5 link redundancy 1+1 redundancy for critical modules (such as SCM4, EBAM3 and ICM3) The system expansion bus architecture allows up to three expansion shelves, resources sharing among shelf increase the system utilization and reliability SDH (STM 1) protection loop. Voice and broadband services share SDH protection Online diagnostics and loop test Module hot-pluggable. All modules can be replaced without affecting service System abnormal protection, including power failure protection, power switch mis-operation protection, lightning protection, over voltage and over current protection, and short circuit protection Supports Watch Dog Timer (WDT) that recovers abnormal software automatically
mSwitch
System redundancy -
Self protection
System Overview
127
Data backup on the flash. When system malfunction occurs, the data on the flash can help to recover the system immediately Overload protection. When the CPU is overloaded, the iAN-8000 system can generate overload alarm, and restrict traffic according to user priority Employs advanced programming with modularized, object-oriented and auto-recovery design. It ensures the high reliability of the system software
Software reliability -
System Security iAN-8000 supports Softswitch based equipment authentication, preventing forbidden Media Gateway (MG) access Telnet address filtering 3-level (administrator, super user and normal user) user access management mechanism, avoid unauthorized user access System log function. Logs are used to record system running information and user related operations
Unparalleled Scalability Modular architecture iAN-8000 implements a modular architecture to support multiple applications. Each shelf can be configured flexibly from 48 lines to 2880 lines POTS services or 48 lines to 2688 lines ADSL services. The system capacity can be extended by the multiple expansion shelves High-density each shelf supports up to 720 POTS or 672 ADSL subscribers Dynamic convergence ability feature enables flexible capacity extension V5.x multiplexing assign V5.x to remote nodes which supply different services, making full use of the V5.x resources on LE
Flexible Networking Deployment Supports xDSL, LAN, SDH, and MSTP access. Can use point to point, ring, star, chain, tree or T networking topology according to the actual application. It can optimize the network planning and meets FTTB and FTTC requirements RT self networking, can connect with local switch/IP backbone network directly and saves investment for the first installation COT self networking. Controlled by the COT system control module, providing access services within COT covering range Multiple transmission media, including optical fiber or copper cable Supports FE/GE access, provides large capacity broadband service
OAM Features The Netman 4000, an SNMP-based UTStarcom network management system provides comprehensive management for the iAN-8000 system. The Netman 4000 provides unified fault, configuration, performance, and security management, displays real-time alarm, enables the user to monitor the real-time operation of the network. Module virtual configuration and batch configuration
System Overview
mSwitch
128
POTS, U interface and xDSL subscribers line loop test Provides real-time environmental and power system monitoring for the remote node Degrade by backing up the software and configuration data in the system flash Serial port, FTP, TFTP download and online upgrade Fault localization and diagnosis of a connection without disturbing it, replacing the malfunction module without affecting service
NGN Migration iAN-8000' s combined narrowband, broadband, and VoIP capabilities enable service providers to migrate from legacy to Next Generation Networks based on a single unified multi-service platform. This smooth migration to NGN services enables all new revenue-generating services. Figure 42 NGN Migration
Special Features The iAN-8000 provides the following special features: Integrated Voice and Data Module The Integrated Voice and Data (IVD) module combines 24 pairs of FXS and ADSL ports in one card with built-in splitters. It enables voice and data service via a single module using one twisted pair cable. Co-existence of V5/VoIP Service The iAN-8000 supports the co-existence of V5 service and VoIP service. It provides POTS, ISDN BRI (2B+ D) and PRI interfaces to support POTS service and narrowband services. In addition, it supports VoIP services.
129
Supports MGCP/MEGACO protocol Supports ITU-T compliant vodec (G.711, G.726(32k), G.729AB, G.723.1) Supports RTP/RTPC-enabled packet encapsulation and de-encapsulation.
Components in Operation Support Layer

The mSwitchs operation support layer contains the following modules: CN SNMS SAM OBS PSC/CG CSS ESS
These modules conform to telecom management network (TMN) architecture standards set by ITU. The conformance relations in the architecture are illustrated in the figure below. Figure 43 Architecture Conformance between mSwitch O/M Modules and TMN Layers
mSwitch Operating Management Layer CSS/ESS SAM Service Management Layer OBS PSC/GG Network Management Layer Telecom Management Network Architecture(TMN Customer Care Layer
CN SNMS
Element Management Layer
NE
Element Layer
CN SNMS
CN-SNMS2020 is a unified network management system in mSwitch, consisting of iNMS (for upper-layer network management), CN SNMS (for core network device management), OMC-R (for RF management), OMC-A (for iAN-2000 IAD
130
management), OMC-T (for IP terminal management, integrated in CN SNMS), and so on. The CN SNMS, in particular, is a management subsystem that manages all core network devices used in mSwitch, covering network management layer and network entity (NE) management layer in TMN. It is designed with web-based and Java-based GUIs to implement various functions needed in network and NE management, such as configuration, fault, performance, security, operation and maintenance, as well as the management for NMS itself. We here will focus our discussion on this subsystem. The CN SNMS uses a three-layer structure, NE/Server/Client, as shown below: Figure 44 Three- layer Structure of CN SNMS
And involves the following protocol interfaces: Server layer communicates with NE layer through SNMP (Get, Set, Trap), ICMP (Ping), FTP. Client layer communicates with servers through HTML. Server layer uses FTP file sharing to support communication with upper layer management system (iNMS). Server layer uses RMI interface send alarm messages to upper layer upper layer management system (iNMS).
The CN SNMS can manage the following NEs (refer to the figure below): NEs at the service control layer: iSG, iCS-P, Parlay GW, Parlay App, and so on. Core network NEs and terminals: iCS-P, SLR HLR, TS, iAN-8000, iUMG, IP terminals (including H.323 phone, MGCP phone, SIP phone, etc.), as well as RPC/RP and CSC/CS (for example, EOC configuration); Servers in mBOSS (such as PSC, AC, SAM, OBS, CSS, PBMS, and so on) and third party devices (such as CISCO Router/Switch, Sun Server, DB). NEs in CN SNMS itself, including CN SNMS Server, CN SNMS Client, and so on.
System Overview
mSwitch
131
Figure 45 NEs Managed by CN SNMS
Each NE to be managed is configured with an Agent. Management data are transferred between a NE and the NMS Manager through the Agent supported by SNMP V2C. The mSwitchs CN SNMS can implement the following management functions: Network topology Configuration management Fault management Performance management Operation and maintenance management Transaction events management(currently not supported) Security management CN SNMS management
SAM
The mSwitch system is designed with a web-based subsystem for subscriber application management, namely the Subscriber Application Management System (SAM). The SAM mainly implements service supervision and subscriber management. It communicates with SLR, NMS, VAS center and other supervision/subscriber management systems over IP network, as illustrated in the figure below:
mSwitch
System Overview
132
Figure 46 NEs communicating with SAM
SAM communicates with SLR, and the subscriber information data in these two servers are synchronized though an event-driven mechanism. In other words, a data synchronization operation will be triggered between the two servers whenever subscriber basic information data and service-related information data in one of the two changes, for example, a subscriber changes its profile, or applies for a new service. iAN-8000 subscriber information (device ID and logic ID, etc.) is exchanged between SAM and CN SNMS of iAN-8000 over IP network; SAM also communicates with VAS center. When SAM enables or disables a VAS, it will notify the VAS center, which will then send requests for opening or canceling the service. CN SNMS also communicates with SAM server to implement part of management functions for SAM server, such as querying SAM process status and login users, managing and controlling login users, and so on.
The SAM subsystem implements the following management functions: Customer information management: A customer refers to an organization or a person having account and using one or more services provided by the carrier. The SAM system records three categories of information: Subscriber basic information (also called customer profile), such as subscriber name, subscriber type, address, nation, and so on. Payment-related information (also called account information), such as account number, payment method, bank account, and son. Service information, namely the information about the services provided by telecommunication carriers or service providers, such as POTS, ADSL, and so on.
Service handling The service handling refers to the management works to be done when a subscriber applies for certain type of service at a point of sale, which may involve:
System Overview
mSwitch
133
Allocating system resources (such as phone number, device-related resources). Specifying billing policy that is to be implemented in the service being applied. Specifying the service instance the subscriber applying for. Recording the basic information about the subscriber, and so on.
The SAM subsystem in mBOSS currently supports the following services: Basic services, which include PHS, V5, VoIP (for example, subscribers under IAD, IP terminal, iAN-8000), Centrex, WLAN-based broadband, PSTN prepaid service enabled through intelligent network (IN), portability-enabled FHLR, IP-featured and PHS-featured WiFi. These basic services could be accompanied with certain types of supplementary services (such as CLIP, call forwarding, etc) and value added services (such as SMS, c-mode, etc). Value added services (VAS), which include iNumber (UPT), VPN, video conference, enhanced wide area Centrex (iWAC), multi-domain service, as well as the commonly used SMS and c-Mode service. Credit packages: The SAM subsystem also manages those services that are independent of the existing price plans and required to be separately applied for. At present, the SAM supports: multi-service package, callee discount, usage peak limitation, time and zone discount.
Service management Carriers can work on SAM to perform various service control actions according to subscribers needs and service status, such as service suspending (requested by subscriber or induced by payment overdue), service resuming, service termination, and handling subscribers reports on lost handset or requests for canceling a loss report.
Query and Event Management: The SAM provides a dedicated query menu for users to query subscriber information, and events related to subscriber service status; these events reflect how the data synchronization between the SAM and other related NEs.
OBS
The mSwitch OBS (Online Billing System) is a web-based multi-service billing system, supporting multiple languages (Chinese, English, etc.), modular structure, and provides comprehensive solution to satisfy different and ever changing customer needs. OBS performs primarily the following functions: data collection, billing, accounting, writeoff, info, checking & auditing, query, statistics, and data management. OBS supports the following features:
mSwitch
Supports multi-service Supports real-time pricing and billing Supports prepaid and postpaid services Supports accounting cards billing
System Overview
134
Supports VoIP service billing Supports VAS billing Supports Centrex billing Supports roaming service billing (includes inter-domain and intra-domain roaming) Supporting multi-Call billing Provides multiple billing methods Provides various discount packages Provides multi-service invoice Supports prepaid VAS billing Supports multiple carriers, provides different virtual billing systems or virtual customer service systems Provides a unified service plan description mechanism for multi-services Supports customer agent management Supports settlement among sub-bureaus within an mSwitch domain and with other carriers.
OBS uses a three-tier architecture consisting of DB/Logic Module/Client, as shown in the figure below: Figure 47 OBS Architecture and External Interfaces
As shown above, OBS communicates with system DB through API, and shares information with SAM through the DB, while the OBS clients perform console
135
operations through web browser. OBS communicates with PSC to receive CDR file from PSC, and to process postpaid bills; it also communicates with CN SNMS through SNMP to enable OBS server management. In addition to web-based operation interfaces for the users, OBS also provides some back office application tools, which coordinate with OBS user interfaces to complete back office tasks, such as batch pricing and accounting, usage daily summary, invoicing, writeoff, statistic, auto suspending/resuming, daily rent calculation, and so on. The processing flow is illustrated below: Figure 48 OBS Background Administration Flow
PSC: Real-time pricing for prepaid, usage PSC: Generating postpaid usage
Batchload for postpaid
Usage daily Sum
charge
comm writeoff invoice general writeoff write off autopay
oss monthly statistics oss stat oss daily statistics payment autosuspend/autoresume/ prepay suspend/ resume
The mSwitch provides reseller management system for carriers to deploy and manage resellers at different levels. The reseller management system consists of two parts: carrier-intended reseller management system and reseller self-care management system, as illustrated in the figure below:
136
Figure 49 Reseller Management System Structure
DB
Carrier-initiated reseller management Reseller Info
Reseller selfmanagement Security
Commission
User Management
Payment Group
Payment Collection
Statistic
Statistic
The carrier-intended reseller management system is integrated in OSS, and is used to: Configure resellers deployed over the whole network, formulating and modifying and reseller contract information. Manage payment group, commission, and payment-collection information. Manage receivable and subscriber statistics Manage organizations involved, account information, and related bank information. Query service information, and so on.
The reseller self-care management system is usually installed at resellers POSs to manage subscribers contracted with them. It mainly includes the following functions: Agent self-assistant management, such as password modification, and so on. Payment collection Batch management; Invoice management; Query.
System Overview
mSwitch
137
PSC
In mSwitch, The Prepaid Service Center (PSC), by working with GG, is responsible for call record information collection and charging to each subscriber (prepaid or postpaid). For prepaid application deployment, PSC collects CDR data from iCS-P, and provides logic to handle all prepaid applications including account authentication, maximum allow call duration, real-time account balance update, and also sorts and post-processes CDR and prepares for billing system integration, delivering highspeed call processing capability. The billing data paths in the system are illustrated in Figure 50. Figure 50 System Billing Data Paths
CG
The Charging Gateway (GG) is an important solution developed by UTStarcom to sort, filter, format CDRs of postpaid applications, so as to reduce the number of physical interfaces needed for CDR exchange and of CDR formats need to be processed. This solution delivers flexibility in implementation of billing strategy, reduced time to market for new service lunch, and enhanced network efficiency. The billing data paths in the system are illustrated in Figure 50.
CSS
For customers convenience, mSwitch supports a Customer Self Service (CSS) system, which is both web-enabled and PHS-based, allowing customers to access information about telecom services and price policies, apply for new service and discount package, query their service and usage, etc. CSS is an integrated component in mSwitch OSS, sharing the same DB with OSS. Carriers can maintain CSS website through background administration system, and subscribers can access CSS via one of the two ways:
138
Access CSS Website via Internet; Access CSS-delivered C-mode service via PHS C-mode;
The figure below illustrates the CSS architecture. Figure 51 CSS Architecture
SAM OBS
DB
HTTP DB Cache API
C-mode PS
C-mode Center
Web Server
HTTP
CSS
SMPP
Internet/ Intranet
Client Broowser PS SMSC
Access CSS website via Internet/Intranet This is the traditional way to access CSS; it includes BBS, e-POS and e-business. Carriers can enhance the CSS website to provide more comprehensive and more convenient services to end-users. CSS website shares subscribers profiles through JDBC API; users can login on CSS through Web browser to carry out maintenance. CSS mainly includes three functional modules: e-POS, BBS and background administration. They are discussed below in detail: e-POS It provides the following functions: Password change Personal profile updating Service customization, including supplementary services, VAS, and so on (and in mSwitch R2.5, support to iNumber service, UPT service is added, and subscriber can access service logic setup functions through CSS website) Service query Card management
System Overview
mSwitch
139
Notification through e-mail (offering information about fee default, balance query, usage detail, service; currently not supported) SMS (customer can work on web page to edit SMS text and send SMS)
This module is a functional subsystem intended for customers. Through system configuration, Carriers can control whether to provide SSL security channel for customers browsers to access the server or not. BBS BBS is a platform for communication between carriers and customers. Through it, carriers can promulgate information and news, manage service information, accept customer complaints, and collect market feedbacks, all on a real-time basis. This module provides facility for business news, service information, online complaints, on-line query, FAQ, on-line forum (currently not supported), and so on. The e-POS and BSS are open for subscribers; they can use Web browser to complete various self-maintenance operations. The main page of a typical CSS is as shown below: Figure 52 An Exemplary CSS Website Main Page
Background administration The mSwitch system provides a background administration system for carriers to maintain CSS and privilege management. The background administration system allows the carriers to implement management functions for privileges, news release, price policy formulation, complaints acceptance, and other facilities such as configuring a subset of an opened service, call duration allowed, default password, default system language, SMTP server; monitoring DBCache; analyzing and reporting subscriber type, access time and duration etc.
mSwitch
System Overview
140
A carriers supervisor must login on the administration center before performing the above operations. Figure 53 Administration Center Login Page
C-mode service support The C-mode service is one of the value-added services (VAS) provided by mSwitch system via the VAS system developed by UTStarcom. The C-mode service center in VAS system consists of a series of servers, such as iAG, e-POS Server, Email GW, Content Server, Register Server, Location Server, MTA Server, etc.. The communication between Content Server and CSS server is implemented via HTTP, and CSS acts as an ICP to provide contents for C-mode center and receive requests from C-mode center; while C-mode iAG uses ISDN PRI to communicate with iUMG in mSwitch system, enabling C-mode message exchange among C-mode PHS, as shown in the figure below: Figure 54 CSS Supports C-mode Service
By using a C-mode enabled PHS, subscribers can access CSS, browsing c-mode content and performing various operations directly via the PHS set:
System Overview
mSwitch
141
Modify password. Query service information, such as balance, usage detail, payment history, and so on. Customize service, such as call forwarding, call diverting, and so on.
Note: For detailed discussion about C-mode center, refer to VAS-related user manual.
ESS
The enterprise communications system is moving toward the integration and customization. Efficient and cost-effective enterprise communications systems are attractive to the telecom carriers. To address this market demand, UTStarcom has developed Web-based Enterprise Self-service System (ESS). The ESS solution integrates the services available on the mService platform and provides a unified portal website, so that the enterprises can perform authorized service operations on the website, for example, setting operation permissions, querying tickets, and managing various value-added services, including short message service, Centrex service, Multiline Hunt Service (MLHG), location service, conferencing service, and video conferencing. The ESS is a component of mBOSS (Operation Support System). It shares the database with the OSS. In addition, it has a dedicated MySQL database that stores a large volume of enterprise data. The network structure is illustrated in the figure below. Figure 55 ESS Architecture
As shown in Figure 55, the ESS consists of two parts: Enterprise Self-service Management System (Enterprise Manager), which manages enterprise customers under an mBOSS. For example, carriers can
System Overview
mSwitch
142
work on this manager to create an enterprise, and allocate services, number resources, supplementary service sets, and call right sets to the enterprise. Enterprise Self-service Portal (Enterprise Portal), a client/server system that delivers self-assistant functions for enterprises to manage their own services through Internet-enabled clients. Taking Centrex/MLHG service as an example, the enterprise can: Manage organization, including the affiliated departments and the employees, and also, allocate the ESS privileges the carrier assigned to the enterprise among the employees. Manage Centrex business, including managing Centrex and MLHG service, as well as querying the enterprises invoice/usage. Manage short message service (SMS), including both business and personal messages. Manage meeting room, including meeting room reservation, reservation query/ change, as well as issuing notification through short message or email. Manage video conference, including video conference reservation, reservation query/ change, as well as issuing notification through short message or email. Query the operation records of the subscribers within the enterprise and their usage records, as well as generate related statistics. Manage personal profile, including editing contact information and employees profile.
VSP Management System

Virtual service providers (VSP) refer to those service providers who use your resources and service products to do telecommunication business. The mSwitch supports VSP management, allowing carrier to deploy leased services (rental terminal, broadband access facilities, data service, and VOD) in hotels, bars or at public sites that have dense visitors and remotely manage these distributed services.
Customer Rental System

The Customer Rental System (CRS) is designed for organizations, public sites (such as hotel) that have dense visitors, hence need a dedicated call service provision system that deliver mobility, privacy and price advantage to these visitors.
System Overview
mSwitch
143
Figure 56 Customer Rental System Network Structure

VSP
mBOSS
VSP CRS (server)
CN SNMS
CDR server
VAS servers
DB
SNMP
'GTP
PSC SLR/RS
SNSP
IP Network
SNSP
iMG
Q.931 IU SCT A P I P
V5.2 Q.931 E E SIP-T 1 1
iMG A N
RPC/ CS C
RPC/CSC
CRS (client)
RPC/CSC RP/CS
CRS (client)
RPC/CSC RP/CS
RPC/CSC RP/CS
RP/CS
PS PS PS PS PS
PS
PS
PS
Hotels
Densly populated areas
As shown in Figure 56, CRS is both IP and wireless enabled, able to provide serviceprovisioning support for widely distributed VSPs. To implement a CRS, a VPS needs only a PC with browser and network connection. The PC could manage terminals under this VPS and access related information (payment, accounting, etc.) through Intranet, ISDN, dial up, ADSL, LAN, or PWLAN. The terminals used could be Personal Phone System (PHS) or Fixed Subscriber Unit (FSU). With CRS installed in a hotel, for example, guests, upon check-in, could apply for CRS service to benefit low-price and convenience offered by CRS. CRS is also applicable to other public sites, or organization, such as school, construction filed, scenic site, shopping centre and mall, playing as an independent operating point of public call service for users convenience, as well as a driver for promotion of carriers revenue. CRS includes two parts: VSP-intended CRS and carrier-intended CRS. The VSP-intended CRS provides operating support for VSP (leaseholder) to perform related management operations, including:
144
Lease idle phones to users, and complete necessary service settings before leasing them. Manage leased phones, such as handling returned phone, renewal requests and service deposit, accounting. Query users service fee. Set rental rate/penalty. Employee management.
The carrier-intended CRS (including carrier-intended VSP management system and related OSS modules) manages all distributed leaseholders: such as: Create, delete a leaseholder, and modify leaseholder properties, and so on. Manage the terminal numbers allocated to leaseholders, for example, allocate more PHS numbers to or reclaim some PHS numbers from a leaseholder, configure default call barring attributes for PHS number allocated. Perform accounting against each leaseholder account, and generate related statistic reports. Perform service controls on terminals under leaseholders, such as service suspending/resuming, and so on.
Hotel Broadband System

The hotel broadband system (HBS) is developed by UTStarcom in response of the demand for accessibility of broadband access facilities, data service, and VOD service in hotels. This system could make hotels more attractive to visitors.
System Overview
mSwitch
145
Figure 57 Hotel Broadband Network
As shown in Figure 57, HBS is both IP and wireless enabled, able to provide serviceprovisioning support for widely distributed VSPs. To implement a HBS, a VPS needs only a PC with browser and network connection. The PC could manage terminals under this VPS and access related information (payment, accounting, etc.) through Intranet, ISDN, dial up, ADSL, LAN, or PWLAN. With HBS installed in a hotel, guests, upon check-in, could apply for media service or broadband access, data service, or VOD. HBS includes two parts: VSP-intended HBS and carrier-intended HBS. The VSP-intended HBS provides operating support for VSP (leaseholder) to perform related management operations, including:
mSwitch
Enable service for a guest room. Change guest room. Handle service renewal requests, checkout, and accounting. Lease terminal devices to users, and complete necessary settings. Query related information, including users usage history, payment history, related statistic reports (daily report, monthly report), audience rating, and so on. Manage guest and HBS operators
System Overview
146
The carrier-intended HBS (including carrier-intended VSP management system and related OSS modules) manages all distributed leaseholders: such as: Create, delete a leaseholder, and modify leaseholder properties, and so on. Manage the terminal numbers allocated to leaseholders, for example, allocate more PHS numbers to or reclaim some PHS numbers from a leaseholder, configure default call barring attributes for PHS number allocated. Perform accounting against each leaseholder account, and generate related statistic reports. Perform service controls on terminals under leaseholders, such as service suspending/resuming, and so on.
IVR-1000
The IVR-1000 is an interactive voice response system provided by mSwitch for prepaid customers; like CSS, it is a customer self-service system. The figure below illustrates mSwitch IVR-1000 architecture: Figure 58 IVR-1000 Architecture
As shown in the figure above, the IVR-1000 works in Client/Server mode. Subscribers in mSwitch system can access IVR-1000 by dialing a specific number to perform some interactive operations on their prepaid accounts (including PHS and V5 POTS subscriber accounts), such as
System Overview
Verify charge card Check prepaid balance Charge prepaid card

mSwitch
147
Set family or friend numbers for discount (Callee Discount number) Query Callee Discount Number already set Balance notification Change service password, and so on.
Note: The balance notification function in IVR system is also applicable to postpaid subscribers. Just as implemented for prepaid subscribers, the balance notification for postpaid subscribers also involves several coordinated actions that are to be taken by operator on OBS console, by background notification program and related API, as well as by carriers customer service system or by IVR-1000. It should be noticed that the parameters configured on OBS and the background notification program used for prepaid subscribers are somewhat different from those for postpaid subscribers. Being a server/client system, the IVR-1000 is based on the mSwitch DB that holds information related to prepaid services (such as subscribers profiles, service information, prepaid account balance, callee discount numbers, maintained by OBS, SAM). When subscribers dials IVR-1000 through PSTN, the IVR-1000, as a client of OBS DB, sends various requests related to prepaid services through the IVR Agent to the DB, and gets or updates related prepaid service info, then sends back the results to subscribers, enabling the interaction with subscribers on an interactive voice response platform. IVR Agent provides an open Multi-service Interface Protocol (MSIP), which enables not only the interaction among mSwitch billing system DBs, but also the communication with third party IVR systems, allowing subscribers to use third party IVR to perform various self services, such as balance query, password modification, card charge, accounting check, etc. In addition, IVR Agent also support interfacing with bank system, allowing subscribers to charge their cards at bank. When third party billing system is involved, IVR Agent can enable the data exchange with these billing systems via mSwitch IVR. So, mSwitch prepaid system can support multiple billing systems and multiple card charging platforms. On the other hand, the IVR-1000 uses SNMP to communicate with CN SNMS, hence it can be managed, for some extent, through CN SNMS, for example, users can work on SNMS to set up query conditions, monitor IVR status, manage alarms, and so on. IVR-1000 uses industrial computer or Pc (with sound card and signaling card installed) as its hardware platform, running under Windows 2000 OS. IVR-1000 supports a maximum of 60 ~ 240 subscribers simultaneously dialing to IVR-1000, depending on hardware configuration.
VAS
As discussed above, mSwitch can provide various value added services (VAS), such as SMS, C-mode, MCN, VMS, Prepaid, Centrex, and so on. The implementation of SMS and C-mode need a specially designed supporting system, VAS. The VAS system is a comprehensive solution provided by UTStarcom for carriers, mainly intended for SMS and C-mode; with VAS, subscribers can send/receive short massage and e-mail, access content, etc.
148
In addition to VAS for iPAS/PAS subscribers, exchange of SMS with other third party networks, can also be enabled through a VAS center, as the UTStarcom VAS system can be connected with VAS systems of PSTN and GSM networks. In addition to the features mentioned above, the newly updated VAS (VAS2.1) also supports SMS roaming (including inter-roaming within PAS domains, within iPAS, and within PAS-iPAS hybrid) and prepaid services. The combination of VAS with mSwitch can be an addition to carriers business promotion.
RADIUS Server
The mSwitch system supports broadband and WLAN subscribers by employing dedicated Remote Authentication Dial-In User Server (RADIUS). RADIUS server runs at operation supporting layer to enable AAA function (Authentication, Authorization, and Accounting) needed for broadband and WLAN subscribers to access services. RADIUS server communicates with NMS, OSS, and mSwitch DB over IP network (WAN/LAN), and serves terminals in server/client mode. Being connected with mSwitch DB, the server can responds on a real-time basis to various requests from subscribers, completing AAA task. RADIUS server uses RADIUS protocol to communicate with its client. It also provides authentication and accounting support for subscribers under third party gateways, as well as roaming support for broadband/WLAN subscribers. At present, RADIUS server supports two types of authentication protocols: PAP and CHAP. It uses MD5 encryption algorithm, and supports three types of authentication applications: 802.1x based PPPoE based Web-based
System Overview
mSwitch
System Disaster Tolerance Solution
The NGN is an open and distributed network where various devices can get access to the softswitching equipment from any place over the IP-based packet network. If interruption occurs on the bearer network or a device becomes faulty, the entire softswitching network will not provide services for subscribers. This has a direct negative effect on the robustness and reliability of the system. Currently, the mSwitch network provides the following disaster tolerance solutions: Core network disaster tolerance solution The iCS-P employs 1+1 backup mode. Two devices have a mutual hot backup relationship. When one of the iCS-Ps becomes faulty, the other one automatically replaces the faulty device to provide services. The iCS-P employs priority-based disaster tolerance technology. This technology ensures selection of transaction servers (TS servers) according to their priority settings and avoids interruption of service provisioning due to loss of subscriber profiles provided by the transaction servers. The iCS-P employs dual-home disaster tolerance technology. This technology effectively ensures the communication with every media gateway (iUMG) and signaling gateway (iSG) and avoids interruption of service provisioning due to loss of control of the iCS-P.
TS system disaster tolerance solution There might be such a case in the system networking: several domains are independent from each other on two multicast layers; multicast communication is not allowed between these domains, but their SLRs are required to save the same target data during the running process; and the PSCs are also required to save the same target data during the running process. In this case, Data Synchronizing Controller (DSC) can be installed in the TS cluster in each domain to achieve both the synchronization of SLR cache databases in the different multicast domains and the synchronization of PSC cache databases in the different multicast domains.
mBOSS and NMS disaster tolerance solution Currently, a third-party software application Veritas is used for disaster tolerance application backup and data backup. UTStarcom can provide a dedicated software application UTHA for application backup.
Note: For details about the mSwitch disaster tolerance solution, see mSwitch GR Solution User Guide.
mSwitch
System Overview
Performance Specifications
Table 18 System Performance

Parameter Capacity Specifications A maximum of 5 ,000,000 PHS subscribers A maximum of 1,000,000 IP terminals 15M BHCA High Availability 99.999% MTBF > 400,000 hours MTTR < 30 minutes
Table 19 Interface and Protocols

Interface/protocol TDM Ethernet Trunking protocols supported Access protocols supported NMS interface protocol Interconnection protocol between softswitch systems VoIP interface Specifications 2.048Mbps E1/T1, STM-1(63E1) 10/100/1000Base-T SS7 TUP/ISUP, INAP, ISDN PRI, SIP-T, MAP, CAP, Parlay API, SNSP, SIGTRAN RF Q.931, H.323, MGCP, SIP, DHCP SNMPv2 SIP-T Signaling Media transmission Codec Noise Depression Echo Cancellation FoIP interface RAS interface T.38, G.711 RADIUS, PPP, PIAFS, voice modem, PRI H225.0, H.245, H.450, H.323, MGCP, SIP, SIGTRAN RTP/RTCP G.711, G.729X, G.723.1 G.723.1, G.729 G.168
Table 20 NE Specifications
Network Element iCS-P (single board/redundancy) iUMG Performance Specifications Processing capacity (BHCA) Max. E1 trunk Processing capacity (BHCA) iSG3200 Max. SS7 links Signaling processing capacity 150 K 320 E1 400 K 128 x 64 Kbit/s 15 K MSU/s
mSwitch
System Overview
Compliant Specifications and Standards

Note: The specifications and standards listed in this appendix are mSwitch-wide. Because specific network elements are used in different applications, they comply with different specifications or standards. Please read the respective system overview of the network elements to get their specific compliant standards.
China Standards
YDC 003-2001 General Technical Specifications for Softswitching Equipment YD/T 1044-2000 General Technical Specifications for IP-based Telephone/Fax Services YD/T 1127-2001 Technical Interworking Requirements between SS7 Signaling and IP YD/T 1128-2001 Supplementary Service Requirements for Digital ProgramControlled Exchange Equipment YD/T 1243.1-2002 Technical Requirements for Media Gateway EquipmentIP Trunking Media Gateway YDN 065-1997 General Requirements for Switching Equipment YDN 038-1997 National SS7 Signaling Technical SpecificationsISUP Part YDN 038-1997 National SS7 Signaling Technical SpecificationsTUP Part YDN 034.2-1997 ISDN User-Network Interface Specifications Part 2: Data Link Layer Technical Specifications YDN 034.2-1997 ISDN User-Network Interface Specifications Part 3: Layer-3 Basic Call Control Technical Specifications General Technical Specifications for Telephone Switching Equipment by Ministry of Posts Telephone and Telegraph 12/01/1997 General Technical Specifications for Softswitch (Draft) Technical Specifications for Mobile Intelligent Network Management Interface
China Telecom Standards

Network Management Requirements for China Telecom PHS Base Stations PHS Module Technical Specifications for Local Network Management System v5 China Telecom PHS Maintenance Procedure
ITU-T Recommendations

mSwitch
ITU-T H.248 Gateway control protocol ITU-T Recommendation H.225.0, Version 2 Call Signaling Protocols and Media Stream Packetization for Packet Based Multimedia Communications Systems
System Overview
154
Appendix A Compliant Specifications and Standards
ITU-T Recommendation H.245, Version 3 Control Protocol for Multimedia Communication ITU-T Recommendation Q.50, Signalling between Circuit Multiplication Equipment (CME) and International Switching Centres (ISC) ITU-T Recommendation G.165, ECHO CANCELLERS ITU-T Recommendation G.168, Digital network echo cancellers ITU-T Recommendation G.711, PULSE CODE MODULATION (PCM) OF VOICE FREQUENCIES ITU-T Recommendation G.711-AppenDIX II, A comfort noise payload definition for ITU-T G.711 use in packet-based multimedia communication systems ITU-T Recommendation G.723.1, DUAL RATE SPEECH CODER FOR MULTIMEDIA COMMUNICATIONS TRANSMITTING AT 5.3 AND 6.3kbit/s ITU-T Recommendation G.726, 40, 32, 24, 16 kbit/s ADAPTIVE DIFFERENTIAL PULSE CODE MODULATION (ADPCM) ITU-T Recommendation G.728, CODING OF SPEECH AT 16 kbit/s USING LOW-DELAY CODE EXCITED LINEAR PREDICTION ITU-T Recommendation G.729, CODING OF SPEECH AT 8 kbit/s USING CONJUGATE-STRUCTURE ALGEBRAIC-CODE-EXCITED LINEAR-PREDICTION (CS-ACELP) ITU-T Recommendation T.38, Procedures for real-time Group 3 facsimile communication over IP networks M. 3100 MAINTENANCETELECOMMUNICATIONS MANAGEMENT NETWORK---GENERIC NETWORK INFORMATION MODEL M. 3000 Overview of TMN Recommendations M.3108 MANAGED OBJECT CONFORMANCE STATEMENTS FOR THE GENERIC NETWORK INFORMATION MODE M. 3400 TMN management functions E.164 The international public telecommunication numbering plan E.412 Network management controls
IETF Standards

System Overview
RFC 2198 RTP Payload for Redundant Audio Data RFC 2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification. RFC 2543 SIP: Session Initiation Protocol. RFC 2719 Framework Architecture for Signaling Transport. RFC 2833 RTP Payload for DTMF Digits, Telephony Tones and elephony Signals. RFC 2976 The SIP INFO Method. RFC 3015 Megaco Protocol Version 1.0 RFC3057 ISDN Q.921-User Adaptation Layer
mSwitch
155
RFC 3204 MIME media types for ISUP and QSIG Objects. RFC 3261 SIP: Session Initiation Protocol. RFC 3262 Reliability of Provisional Responses in Session Initiation (SIP). Protocol
RFC 3264 An Offer/Answer Model with Session Description Protocol (SDP). RFC 3267 Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs. RFC 3286 An Introduction to the Stream Control Transmission Protocol (SCTP) RFC 3309 Stream Control Transmission Protocol (SCTP) Checksum Change. RFC 3331 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer. RFC 3332 Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA). RFC 3372 Session Initiation Protocol for Telephones (SIP-T): Context and Architectures. RFC 3389 Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping. RFC 3413 Simple Network Management Protocol (SNMP) Applications. RFC 3417 Transport Mappings for the Simple Network Management Protocol (SNMP). RFC 3418 Management Information Base (MIB) for the Simple Network Management Protocol (SNMP). RFC 3435 Media Gateway Control Protocol (MGCP) Version 1.0. RFC 3525 Gateway Control Protocol Version 1. RFC 3545 Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering. RFC 3550 RTP: A Transport Protocol for Real-Time Applications. RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control RFC 3556 Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth RFC 3558 RTP Payload Format for Enhanced Variable Rate Codecs (EVRC)and Selectable Mode Vocoders (SMV) RFC 3578 Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP). RFC 3660 Basic Media Gateway Control Protocol (MGCP) Packages. RFC 3661 Media Gateway Control Protocol (MGCP) Return Code Usage. RFC 3605 Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP) RFC 1157 A Simple Network Management Protocol (SNMP)
System Overview

mSwitch
156
RFC 2572 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) RFC 3412 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) RFC 3416 Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)
North America BELLCORE Standards

GR 533 Service Switching Points -Toll-Free Service (FSD 31-01-0000) GR 477 Network Traffic Management GR 1298 Switching Systems GR 2936 Local Number Portability (LNP) Capability Specification: Service Provider Portability GR 1428 CCS Network Interface Specification (CCSNIS) Supporting Toll-Free Service
NTT Standards
NTT Q.701-Q.704 MTP Spec NTT Q.761-Q.764 ISUP Spec.
ANSI Standards
ANSI T1.113 Telecommunications Signaling System No. 7 (SS7) Integrated Services Digital Network (ISDN) User Part (ISUP)
India TEC Standards

Interface Requirements of a Switching Node with Network-Network Interface at 2048 kbits/s, India TEC Specification, IR/PNI-05/01 Jul 2004. Test Schedule for Interface Approval of Digital Exchange with 2048 kbits/s Interface, India TEC Specification, TSTP/PNI-05/01 Jul 2004. India, National CCS7 Standards for MTP and ISUP, No. S/CCS-02/03.JAN2000, Telecomm. Eng. Centre. Inter-working between PSTN and Private Operators Switch for Basic Telephony Service, India TEC GR G/PNI-03/01 Sept. 95. Large Size Digital Local Cum Tandem Exchanges, Volume I and II, India TEC, GR No. G/LLT-01/04 Dec.98 and its Amendments 1 to 3. Service description for analog subscribers, India TEC, GR No S/ASF-01/02 Nov.98 and its Amendments 1 to 4. R2 MFC Signaling standard
System Overview
mSwitch
157
Chile Standards
Chile SS7 National Specification [2]
mSwitch
System Overview
Acronyms
These terms and acronyms are used throughout the mSwitch system documentation. While not all terms in this list are used in this particular document, the complete list is provided to ensure fast access to the definition of these terms regardless of how they are encountered. ACC ACP AFS AuC AN API AS A/V BCP BHCA BRI C4 C5 CA CAMEL CAMS CAP CCF CDR CDRS Centrex CLIP CLI Screening
mSwitch
Account Card Calling Service Advanced Call Processing Advanced Freephone Service Authentication Center Access Network Application Programming Interface Application Server Audio/Video Basic Call Processing Busy-Hour Call Attempts Basic Rate Interface (2B+D) Class 4 Office Class 5 Office Call Agent Customized application for mobile networks enhanced logic Customized Announcement Management System CAMEL Application Part Call Control Function Call Detail Record CDR Server Central Office Exchange Service Calling Line Identification Presentation Calling Line Identification Screening service
System Overview
160
Appendix B Acronyms
CLK C-mode CN SNMS CNG CompactPCI CPU CS CS CSC C-SG CSS DB DHCP DPS DSCP DSP DST DTMF Enhanced AS Enhanced MS EAM EOC FE FoIP FPH FMC FS FSU
System Overview
Clock Board China Mode P-mail Deluxe Service Operation and Maintenance Center-Switch Comfort Noise Generation Compact PCI Bus Central Processing Unit Call Server Cell Station Cell Station Controller Combined Signaling Gateway Customer Self-Service System Database Dynamic Host Configuration Protocol DC/DC Power Supply Module Differentiated Service Code Point Digital Signal Processor Daylight Saving Time Dual-Tone MultiFrequency Enhanced Application Server Enhanced Media Server Ethernet Adaptor Module Embedded Operation Channel Fast Ethernet Fax over IP Free Phone Service Fixed-Mobile Convergence Feature Server Fixed Subscriber Unit
mSwitch
Appendix B Acronyms
161
GBP GE GHLR GK GMSC GPS GR GSM GW H.323 HA HLR HDLC HSC HSM HTML HTTP iAD iAG iAN-8000 ICMP iCS-P IN INAP iNMS IP iPAS iRS
mSwitch
Gateway Backplane Gigabit Ethernet GSM Home Location Register Gatekeeper Gateway Mobile Switching Center Global Positioning System Geographical Recovery Global System for Mobile Communication Gateway ITU protocol serials, define the multimedia service over packet base network High-level Availability Home Location Register High Lever Data Link Control Hot Swap Controller Hot Swap Module Hypertext Markup Language Hypertext Transfer Protocol Integrated Access Device Internet Access Gateway IP based AN product Internet Control Massage Protocol IP-Based Call ServerProfessional Intelligent Network Intelligent Network Application Part NetMan2020 Integrated Management Part Internet Protocol IP-based Personal Access System Interface Routing Server
System Overview
162
Appendix B Acronyms
ISDN ISP ISUP iSG iTG IUA iUMG JDBC LAN LDS LE LNP LTS M3UA MAN MAP MAS MCN MCNC MCR MEGACO MG MGCP MIB MML MNP MoUDP MPU
System Overview
Integrated Services Digital Network Internet Service Provider ISDN User Part Signaling Gateway Trunking Media Gateway ISDN Q.921-User Adaptation Layer IP-based Unified Media Gateway Java Database Connection Local Area Network Location Dependent Service Local Exchange Local Number Portability Service Location Tracing Service MTP3 User Adaptation Layers Metropolitan Area Network Mobile Application Part Mass Call Missed Call Notification Missed Call Notification Center Missed Call Record Media Gateway Control Media Gateway Media Gateway Control Protocol Management Information Base Man Machine Language Mobile Number Portability Message over UDP Main Processing Unit
mSwitch
Appendix B Acronyms
163
MS MSC mSwitch MTBF MTP MTP2 MTP3 MTTR NAS NE NGN NMS NP OBS OMC-A OMC-R OMC-T OSS PAS PEM PEM-HD PHS PIAFS PLMN POTS PPT PPU PRI
mSwitch
Media Server Mobile Switching Center mobile, multi-media, multi-service (multi-access) SoftSwitch system Mean Time Between Failures Message Transfer Part MTP Layer 2 MTP Layer 3 Mean Time to Repair Network Access Service/Server Network Element Next Generation Network Network Management System Number Portability Online Billing System Operation and Maintenance Center-Access Operation and Maintenance Center-Radio Operation and Maintenance Center-Terminal Operation Support System Personal Access System Packet Engine Module Packet Engine Module-High Density Personal Handset System PHS Internet Access Forum Standard Public Land Mobile Network Plain Old Telephone Service Prepaid Telephony Service Peripheral Processing Unit ISDN Primary Rate Interface(30B+D)
System Overview
164
Appendix B Acronyms
PS PSC PSTN RADIUS RAS RMI RP RPC RTCP RTN RTP SAM SCCP SCE SCEF SCF SCP SCTP SDF SDF SEM SEP SIGTRAN SIP SIP-T SLR SMBus SMGW
System Overview
Personal Station Prepaid Service Center Public Switched Telephone Network Remote Authentication Dial-In User Service Remote Access Server Java Remote Method Invocation Radio Port Radio Port Controller Real-time Control Protocol Roaming Telephone Number Real-time Transport Protocol Subscriber Application Management System Signaling Connection Control Part Service Creation Environment Service Creation Environment Function Service Control Function Service Control Point Stream Control Transmission Protocol Service Data Function Service Data Function Switching Engine Module Signaling End Point Signaling Transport protocols over IP Session Initiation Protocol Session Initiation Protocol for Telephones Subscriber Location Register System Management BUS Short Message Gateway
mSwitch
Appendix B Acronyms
165
SMPP SMS SMSC SNMP SNSP SP SRF SS7 SSF SSL SSP STP TCAP TCP/IP TDM ToS TPC TSEH TUP UPT VAD VAS VLR VMS VoIP VOT VPE VPN
mSwitch
Short Message Peer-to-Peer Protocol Short Message Service Short Message Service Center Simple Network Management Protocol Softswitch Network Signaling Protocol Signaling Point Specialized Resource Function Signaling System No.7 Service Switching Function Security Socket Layer Service Switching Point Signaling Transfer Point Transaction Capabilities Application Part Transmission Control Protocol/Internet Protocol Time Division Multiplex Type of Service Timing, Protocol Control Module TS Event Handler Telephone User Part Universal Personal Telecommunication Voice Activity Detection Value Added Service Visited Location Register Voice Mail Service/System Voice over IP Tele-Voting Voice Packetization Engine Module Virtual Private Network Service
System Overview
166
Appendix B Acronyms
VSA WAC
Visiting Subscriber Address Wide Area Centrex
System Overview
mSwitch
China No. 368 Liuhe Road, Hi-Tech Industry Development Zone, Binjiang, Hangzhou 310053, PRC +86-571-81920000 About UTStarcom
UTStarcom, Inc. USA 1275 Harbor Bay Parkway Alameda, CA 94502, USA Tel: 510-864-8800 Fax: 510-864-8802 India Japan 805 Signature Towers II, Shiba Koen Parktower 9F/10F South City I 2-11-1 Shiba-koen, Minato-ku Gurgaon, Tokyo 105-0011 JAPAN Haryana 122001, India +81-3-6430-8600 +91 124 5166100
Europe Campus Kronberg 7 Kronberg, 61476 Germany +49 (617) 3946-3460
Latin America 2801 SW 149th Ave Suite 100 Miramar, FL 33027, USA 954-447-3077 www.utstar.com
Headquartered in the United States with sales, support, and manufacturing facilities worldwide, UTStarcom designs, manufactures, sells, and installs an integrated suite of wireless and wireline access network and switching systems. UTStarcom's complete suite of network equipment gives telecommunication service providers the means to cost-effectively provide efficient and scalable voice, data, and Internet services around the globe. Copyright 2006 UTStarcom, the UTStarcom logo, !-Volution, AIRSTAR, AN-2000, AN-FTTB, CommWorks, the CommWorks logo, iAN, iCell, Internode, Intranode, iPATH, ISP, MovingMedia, mSwitch, Next Generation Network Technology. Now, NGDLC, PAS, PAS Wireless, Seamless World, Softexchange, Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC, Sonata WLL, Telos, Total Control, Unitech, WACOS, WICOPS, WLL, and Xtreme IP are registered trademarks or trademarks of UTStarcom, Inc. and its subsidiaries.

Mswitch R6.0 Overview E SZ v1.0

Uploaded by

Copyright:

Available Formats

Mswitch R6.0 Overview E SZ v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mswitch R6.0 Overview E SZ v1.0

Uploaded by

Copyright:

Available Formats

mSwitch

Typical Applications ........................................................................................49

Typical Service Solutions ............................................................................... 55

System Functional Components.................................................................... 91

About This Guide

About This Guide

Text represented by Courier New Font

About This Guide

Convention Text represented by

Description This typeface represents files in Unix/Linux system files.

Figures and Screen Captures

Typical Networking Architecture

Figure 1 mSwitch System Architecture

Net Edge 2024A L

Service and Application Layer -

Interworking with PSTN

Types of Subscribers Supported

H.323 phone, H.323 iAD SIP phone UTSmart PC phone (SIP-enabled)

Absent Subscriber service

Call Forwarding Unconditional (CFU)

10. 11. 12. 13. 14. 15.

Up to five parties supported

Note: means supported.

Abbreviated Dialing Hotline Service Outgoing Call Barring One-time Debarring

Incoming Call Barring

Wake up Service (Regular)

11. 12. 13.

Interception Calls Absent Subscriber Service Call Forwarding Unconditional (CFU)

14. 15. 16.

Available in mSwitch Release 5.6.5 and later

H.323 Terminal Subscribers

MGCP/H.24 8 Terminal Subscribers

SIP Terminal Subscribers

Call Waiting (CW) Call Hold

(Unattended Transfer available in mSwitch R6.0 and later) X

Three Party Service

21. 22. 23. 24. 25. 26. 27.

Automatic Callback (AC)

Automatic Recall (AR)

Call Back on Busy

H.323 Terminal Subscribers

MGCP/H.24 8 Terminal Subscribers

SIP Terminal Subscribers

Multiline Hunt Service (MLH)

Last Number Redial

Voice Mail Service (VMS) Voice Mail Notification (VMN)

V5 POTS Subscrib ers on iAN-8000

POTS Subscribes on MGCP IP phone& iAD/iAN-8000

SIP IP Phone Subscr ibers

Wireless Private Automatic Branch Exchange (WPABX)

Provides intra-team pickup and inter-team pickup features.

V5 POTS Subscrib ers on iAN-8000

POTS Subscr ibers on H.323 IP Phone & iAD -

POTS Subscribes on MGCP IP phone& iAD/iAN-8000

SIP IP Phone Subscr ibers

Call Transfer Call Forwarding Operator Team Service

This feature takes precedence over the MCN feature.

Available in OSX release 3.0.

mSwitch intra-domain handover, including Handover between iCS-Ps