NGCSS

Fundamental

Training Material

ZTE UNIVERSITY
ZTE University, Dameisha
YanTian District, Shenzhen,
P. R. China
518083
Tel: (86) 755 26778800
Fax: (86) 755 26778999
URL: http://ensupport.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Publishing Date (MONTH/DATE/YEAR) : 10/13/2010

Contents

NGCSS Fundamental..................................................... 1
1Network Architecture ................................................. 3
1.1System Network Diagram of Smartfren...................................... 3
1.2System Architecture ............................................................... 4
1.2.1Service Execution Core ................................................... 5
1.2.2Data and Media Center.................................................... 6
1.2.3Message Delivery and Presence ........................................ 7
1.2.4Service Support and Monitoring........................................ 7
1.3System Interfaces .................................................................. 8
1.3.1Interface Between NGCSS and SMSC ................................ 9
1.3.2Interface Between NGCSS and MSCe ................................ 9
1.3.3Interface Between NGCSS and MGW ................................. 9
1.3.4Interface Between NGCSS and BOSS ................................ 9
1.3.5Interface Between NGCSS and NMS .................................10
2Hardware Architecture ............................................. 11
2.1Introduction..........................................................................11
2.2Server Basic Structure ...........................................................13
2.2.1SIP Proxy Basic Structure ...............................................13
2.2.2Parlay Server Basic Structure..........................................13
2.2.3Database Server Basic Structure .....................................13
2.2.4Notify Scheduler Basic Structure .....................................14
2.2.5Mail Processor Basic Structure.........................................15
2.2.6Mail Clear Server Basic Structure.....................................15
2.2.7UMA Basic Structure ......................................................15
2.2.8Smart Call Alert Basic Structure ......................................15
2.2.9VGW Basic Structure......................................................16
2.2.10BOSS Agent Basic Structure..........................................16
2.2.11Statistics Server Basic Structure ....................................16
2.2.12OMMP Basic Structure ..................................................16
2.2.13NetNumenN31 Basic Structure ......................................16
2.3Network Devices ...................................................................17
3Software Architecture .............................................. 19
 3.1Overview..............................................................................19
3.2SIP Proxy Module ..................................................................20
3.3Parlay Application Module .......................................................20
3.4Mail Processor Module ............................................................20
3.5Notify Scheduler Module .........................................................20
3.6Mail Clear Server Module ........................................................21
3.7Network Storage Module.........................................................21
3.8Database Server Module.........................................................21
3.9Media Server Module..............................................................21
3.10UMA Module........................................................................22
3.11Web Module ........................................................................22
3.12Smart Call Alert Module ........................................................22
3.13VGW Module .......................................................................22
3.14BOSS Agent Module .............................................................23
3.15Statistics Module .................................................................23
3.16OMMP Module......................................................................23
3.17System Monitor Module ........................................................23
4Service Introduction................................................. 25
4.1Voice Mail Service..................................................................25
4.1.1Service Overview ..........................................................25
4.1.2Guest Access Scenario ...................................................25
4.1.3New Message Notification ...............................................27
4.1.4Common Access Scenario ...............................................28
4.1.5Subscriber Access Scenario.............................................28
4.1.6Personalize Mailbox .......................................................31
4.1.7Mailbox Provisioning ......................................................32
4.1.8Dynamic Mailbox ...........................................................32
4.1.9Expired Message Auto-Purge...........................................33
4.2Missed Call Notification Service................................................33
4.2.1Service Overview ..........................................................33
4.2.2Delay to Trigger Missed Call Notification ...........................33
4.2.3Aggregated Notification Comprising Different Callers ..........34
4.2.4User Blacklist................................................................34
4.2.5Activate/Deactivate Missed Call Notification ......................35
4.2.6SMS Templates for CoS and Language..............................35
4.2.7Push Or Pull Missed Call Info...........................................35
4.2.8Distinguish Different Missed Call Reasons .........................36
4.2.9Announcement Modes ....................................................36
4.2.10Supporting Multi-Language ...........................................37
NGCSS Fundamental
After you have completed this course, you

will be able to:

>> Master the system architecture
>> Master NGCSS system hardware archi-
tecture
>> Master NGCSS system software archi-
tecture
>> Understand VMS and MCN service func-
tion

Confidential and Proprietary Information of ZTE CORPORATION 1

NGCSS Fundamental

This page is intentionally blank.

2 Confidential and Proprietary Information of ZTE CORPORATION

 �1 Network Architecture
After you completing this chapter, you will know:
>> System Network Diagram of Smartfren
>> System Architecture
>> System Interfaces

1.1 System Network Diagram of

Smartfren
External Network The figure below illustrates the external network.
Diagram
FIGURE 1 EXTERNAL NETWORK DIAGRAM OF SMARTFREN

Confidential and Proprietary Information of ZTE CORPORATION 3

NGCSS Fundamental

Internal Network The figure below illustrates the internal network.

Diagram
FIGURE 2 INTERNAL NETWORK DIAGRAM OF SMARTFREN

1.2 System Architecture

ZTE Next Generation Call Service System is an open, powerful, ro-
bust and creative total hardware and software solution for compre-
hensive call-relative services, such as voicemail, visual voicemail,
video mail, missed call notification, call me now, unified message
and infotainment etc.
The figure below illustrates the logical architecture of the NGCSS
environment.

4 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 1 Network Architecture

FIGURE 3 CURRENT SYSTEM DESCRIPTION

The system architecture of the NGCSS is divided into the following

five layers in terms of function:
¡ Service Execution Core
Service logic execution function
¡ Data and Media Center
Data storage function and media resources function
¡ Message Delivery and Presence
Short Message (SM) sending and receiving function, and Web
portal function
¡ Service Support and Monitor
Account creating/deleting interface, operation statistics and re-
source management functions, and system performance and
alarm monitoring functions

1.2.1 Service Execution Core

SIP Proxy The SIP Proxy is a message forwarding device between Parlay
Servers and the softswitch devices or other SIP application
servers. Based on predefined rules, the SIP Proxy distributes SIP
messages from the softswitch devices to different Parlay Servers,
maintains sessions between the softswitch devices and Parlay
Servers, and maintains a load balance across Parlay Servers.
Parlay Server Parlay Servers are core devices of the NGCSS and provide the fol-
lowing functions:

Confidential and Proprietary Information of ZTE CORPORATION 5

NGCSS Fundamental

¡ Communicating with the core network softswitch devices or

other external application servers through the SIP Proxy to ac-
complish call control
¡ Determining service logic to invoke according to received sig-
naling messages and controlling service execution according to
service logic
¡ Requesting media resources and resources on other modules
for service calls
Mail Processor The Mail Processor provides the following mail processing functions
for the NGCSS:
¡ Copying mails on request of Parlay Servers
¡ Moving mails on request of Parlay Servers
¡ Merging mails on request of Parlay Servers
Notify Scheduler The Notify Scheduler provides the following notification functions:
¡ Sending mail notification messages to subscribers through the
mobile messager on request of Parlay Servers
¡ Sending message waiting indicator (MWI) clearing messages
to subscribers through the mobile messager on request of the
BOSS Agent
¡ Sending mail, mailbox or message deletion notification mes-
sages to subscribers through the mobile messager on request
of the mail clear server
¡ Resending expired and timed out notification messages
¡ Resending notification messages at scheduled times, based on
the notification failure records stored in the database server,
and using predefined notification modes
Mail Clear Server The Mail Clear Server provides the following functions:
¡ Deleting expired messages automatically
¡ Deleting expired mails automatically
¡ Deleting specified mails on request of Parlay Servers
¡ Deleting expired mailboxes automatically
¡ Deleting directories and files stored in deregistered mailboxes
on request of Parlay Servers, the BOSS Agent, or Web server

1.2.2 Data and Media Center

Network Storage The Network Storage provides the following functions for the
NGCSS:
¡ Storing voice (WAVE), fax (TIF) and email files
¡ Providing network file system (NFS) access for other modules
Database Server The database server stores the following data:
¡ System and service configuration data
¡ User profile data
¡ Voice mail and fax mail encapsulation data

6 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 1 Network Architecture

¡ Service statistics and analysis data

Media Server The media server provides the following media resource functions
for the NGCSS:
¡ Voice playing
¡ Voice recording
¡ Audio conferencing
¡ Fax receiving and sending
¡ DTMF signal collection and decoding

1.2.3 Message Delivery and Presence

Web Server The Web server provides the Web portal function for system man-
agement and service management through Web.
UMA The UMA provides the following SMS functions:
¡ Receiving requests from the Notify Scheduler and forwarding
VMS service notification messages to the SMSC according to
the requests. The SMSC sends the messages to subscribers.
¡ Receiving requests from Parlay servers and forwarding VMS
service notification messages to the SMSC according to the
requests. The SMSC sends the messages to subscribers.
Smart Call Alert The Smart Call Alert provides the following functions for the
NGCSS:
¡ Receiving requests from Parlay servers and integrating MCN
notification messages according to the requests.
¡ Sending the integrated MCN notification message to the VMG,
who will deliver the message.
VGW The VGW provides the following SMS functions:
¡ Receiving requests from the Smart Call Alert and forwarding
the integrated MCN notification message to the SMSC accord-
ing to the requests. The SMSC sends the message to sub-
scribers.
¡ Receiving self-service request messages from the SMSC, con-
verting them into internal messages and sending them to the
Parlay servers for processing.
¡ Receiving result messages of self-service request processing
from the Parlay servers and forwarding them to the SMSC, who
will send them to subscribers.

1.2.4 Service Support and Monitoring

BOSS Agent The BOSS Agent provides the following functions to the NGCSS:
¡ Access to the BOSS system for VMS and MCN service subscriber
account creation, deletion, query and data modification.
¡ Access to the OCS system for VMS and MCN service charging
of pre-paid and post-paid subscribers.

Confidential and Proprietary Information of ZTE CORPORATION 7

NGCSS Fundamental

Statistics Server The Statistics server collects original service data and system data
and automatically generates reports on service usage, system per-
formance and system resource usage.
The Web portal supports statistics query and export in different
file formats.
OMMP The OMMP provides the following functions for the NGCSS:
¡ Service resource management function
¡ Service data configuration function
¡ Service running control function
¡ Service monitoring function
NetNumenN31 The NetNumenN31 provides the following functions for the NGCSS:
¡ Periodically querying the running status of each module and
generating performance counters
¡ Reporting failure alarms and performance alarms to the Net-
work Management System (NMS)

1.3 System Interfaces

The NGCSS is connected to different network elements (NEs)
through different interfaces, as shown in the figure below.

FIGURE 4 NGCSS INTERFACES

8 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 1 Network Architecture

Note:
Figure 4 does not contain the connections between the NetNu-
menN31 and other internal modules.

1.3.1 Interface Between NGCSS and

SMSC

This interface works based on the SMPP protocol.

¡ The NGCSS connects the SMSC through UMA to deliver VMS
notifications or short messages to subscribers.
¡ The NGCSS connects the SMSC through VGW to deliver inte-
grated MCN notification messages to subscribers.
¡ The NGCSS connects the SMSC through VGW to receive MCN
self-service request messages and deliver processing result
messages to subscribers through the VGW.

1.3.2 Interface Between NGCSS and

MSCe

This interface works based on the SIP protocol.

The NGCSS connects the MSCe through the SIP Proxy to provide
access for CDMA2000 subscribers.

1.3.3 Interface Between NGCSS and

MGW

This interfaces is based on the UDP/IP-bearing RTP protocol.

The NGCSS is connected to the MGW by the Media Server. The
Media Server provides media resource services for NGCSS sub-
scribers in the CDMA2000 network.

1.3.4 Interface Between NGCSS and

BOSS

This interface is based on the MML protocol.

By the BOSS Agent, the NGCSS uses the MML protocol to con-
nect to the BOSS so that the BOSS can perform account creation,
account deletion, account query, and user data modification oper-
ations.

Confidential and Proprietary Information of ZTE CORPORATION 9

NGCSS Fundamental

1.3.5 Interface Between NGCSS and

NMS

This interface is based on the SNMP protocol.

The NGCSS is connected to the NMS by the system monitor. The
system monitor reports alarms to the NMS automatically and gen-
erates performance statistics files (in text format) for the NMS to
collect.

10 Confidential and Proprietary Information of ZTE CORPORATION

�2 Hardware Architecture
After you completing this chapter, you will know:
>> Introduction
>> Server Basic Structure
>> Network Devices

2.1 Introduction
The figure below illustrates the hardware architecture of the
NGCSS.

FIGURE 5 NGCSS HARDWARE ARCHITECTURE

Table 1 lists the hardware devices involved in the NGCSS.

Confidential and Proprietary Information of ZTE CORPORATION 11

NGCSS Fundamental

TABLE 1 NGCSS HARDWARE DEVICES

No. Module Function

1 ATCA SIP Proxy Proxy device between Parlay Servers

and the MSCe.
Maintains a load balance across
Parlay servers.

Parlay Server Service control module.

Processes call flows in different
networks.

OMMP Service resource management

module.
Manages service resources,
configures service data, controls
service operation, and monitors
Parlay servers and the SIP Proxy.

Database Server Stores system configuration data,

service configuration data, user
data, and statistics and analysis
data.

Mail Processor Moves, deletes, and copies files and

converts mail formats.

Mail Clear Server Clears expired mails, mailboxes, and

messages.

Notify Scheduler Sends notifications of new mails and

schedules notification tasks.

UMA Connects to the SMSC to deliver

VMS service messages.

Smart Call Alert Integrates downlink notification

messages of the MCN service.

VGW Connects to the SMSC to receive

MCN messages and receives
messages.

BOSS Agent Acceptance interface of the BOSS

system for VMS and MCN subscriber
account creation, deletion, query
and data modification.

Web server Provides the system management

portal and service management
portal.

Statistics server Collects statistics of and analyzes

NGCSS service usage.

NetNumenN31 Serves as the interface between

the NGCSS and the NMS, reporting
alarms to the NMS and generating
performance statistics files for the
NMS to collect.

12 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2 Hardware Architecture

No. Module Function

2 Media server Provides media resource services.

3 Network Storage Provides the NFS service for voice,

fax and mail file storage.

2.2 Server Basic Structure

2.2.1 SIP Proxy Basic Structure

The SIP Proxy is a message forwarding device between Parlay

Servers and the MSCe. Based on predefined rules, the SIP
Proxy distributes SIP messages from the MSCe to different Par-
lay Servers, maintains sessions between the MSCe and Parlay
Servers, and maintains a load balance across Parlay Servers.
To ensure the stable and reliable operation of the system, two
high-performance and high-stability blade servers are used as the
SIP Proxy, and the SIP Proxy works in an active/standby mode.

2.2.2 Parlay Server Basic Structure

As the core part of the NGCSS, Parlay Servers execute service logic
programs (SLPs) and exchange signaling messages with the MSCe
through the SIP Proxy to implement call control.
High-performance and high-stability blade servers serve as Parlay
Servers. A load balance across Parlay Servers is maintained by
the SIP Proxy. When one Parlay Server is faulty, the SIP Proxy
distributes new calls to other normal Parlay Servers to ensure the
stable and reliable operation of the system.

2.2.3 Database Server Basic Structure

The NGCSS uses the following four types of databases to store

different data:
¡ Oracle
The Oracle database stores system and service configuration
data.
To ensure the stable and reliable operation of the system, two
high-performance and high-stability blade servers are used as
the Oracle database, and the Oracle database works in an ac-
tive/standby mode.
¡ eBase
The eBase database stores the following data:

Confidential and Proprietary Information of ZTE CORPORATION 13

NGCSS Fundamental

� User profile data

� Voice, fax, video and mail encapsulation data
High-performance and high-stability blade servers are used as
the eBase database. The eBase database works in an N+1
mode for load sharing.
¡ Sybase
The Sybase database stores service statistics and analysis
data.
To ensure the stable and reliable operation of the system, two
high-performance and high-stability blade servers are used as
the Sybase database, and the Sybase database works in an
active/standby mode.
¡ SQL Server
The SQL Server database stores monitoring data.
To ensure the stable and reliable operation of the system, two
high-performance and high-stability NT servers are used as the
SQL Server database, and the SQL Server database works in
an active/standby mode.

2.2.4 Notify Scheduler Basic Structure

The Notify Scheduler sends notifications of new mails and sched-

ules notification tasks.
High-performance and high-stability blade servers are used as the
Notify Scheduler. To ensure the stable and reliable operation of
the system, the Notify Scheduler is divided into the following two
parts:
¡ Control module
The control module is a two-server cluster and works in an
active/standby mode.
¡ Execution module
The execution module may work in a two-server or N+1 (N≥2)
configuration.
� In a two-server configuration, the execution module works
in an active/standby mode.
� In an N+1 configuration, the execution module works in a
load-sharing mode scheduled by the control module.
The control module exchanges heart messages with each
node of the execution module to monitor the running sta-
tus of each node. When one node is faulty due to network
errors or other errors, the control module fails to receive
heartbeat responses from this node. In this case, the con-
trol module determines this node is faulty and does not
distribute new tasks to this node until heartbeat responses
are returned from this node.

14 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2 Hardware Architecture

2.2.5 Mail Processor Basic Structure

The Mail Processor moves, copies, and merges mails. In addition,

the Mail Processor converts mails if required.
To ensure the stable and reliable operation of the system, two
high-performance and high-stability blade servers are used as the
Mail Processor, and the Mail Processor works in an active/standby
mode.

2.2.6 Mail Clear Server Basic Structure

The Mail Clear Server deletes expired mails, mailboxes and mes-
sages.
To ensure the stable and reliable operation of the system, two high-
performance and high-stability blade servers are used as the Mail
Clear Server, and the Mail Clear Server works in an active/standby
mode.

2.2.7 UMA Basic Structure

The UMA connects to the SMSC to enable the NGCSS to deliver

VMS service messages.
High-performance and high-stability blade servers are used as the
UMA. The UMA works in different modes to meet different service
capabilities.
¡ In a two-server configuration, the UMA works in an ac-
tive/standby mode.
¡ In an N+1 configuration, the UMA works in a load-sharing mode
scheduled by the notify scheduler.
The notify scheduler exchanges heart messages with each
node of the UMA to monitor the running status of each node.
When one node is faulty due to network errors or other errors,
the notify scheduler fails to receive heartbeat responses from
this node. In this case, the notify scheduler determines this
node is faulty and does not distribute new tasks to this node
until heartbeat responses are returned from this node.

2.2.8 Smart Call Alert Basic Structure

The Smart Call Alert allows the NGCSS to integrate MCN downlink
notification messages.
To ensure stable and reliable system operation, two high-perfor-
mance and high-stability blade servers are used as the Smart Call
Alert, which works in an active/standby mode.

Confidential and Proprietary Information of ZTE CORPORATION 15

NGCSS Fundamental

2.2.9 VGW Basic Structure

The VGW connects to the SMSC to enable the NGCSS to deliver

and receive MCN short messages.
To ensure stable and reliable system operation, two high-perfor-
mance and high-stability blade servers are used as the VGW, and
the VGW works in an active/standby mode.

2.2.10BOSS Agent Basic Structure

The BOSS Agent connects to the carrier’s BOSS system to enable

the NGCSS to access the BOSS system.
To ensure stable and reliable system operation, two high-per-
formance and high-stability blade servers are used as the BOSS
Agent, and the BOSS Agent works in an active/standby mode.

2.2.11Statistics Server Basic Structure

The Statistics Server collects and analyzes original data accessed

and used by service.
To ensure stable and reliable system operation, two high-perfor-
mance and high-stability blade servers are used as the Statistics
Server, and the Statistics Server works in an active/standby mode.

2.2.12OMMP Basic Structure

The OMMP manages service resources, configures service data,

controls service operation, and monitors Parlay servers and the
SIP proxy.
To ensure stable and reliable system operation, two high-perfor-
mance and high-stability blade servers are used as the OMMP, and
the OMMP works in an active/standby mode.

2.2.13NetNumenN31 Basic Structure

The NetNumenN31 monitors internal NEs and reports faults to the

NMS.
To ensure stable and reliable system operation, two high-perfor-
mance and high-stability blade servers are used as the NetNu-
menN31, and the NetNumenN31 works in an active/standby mode.

16 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 2 Hardware Architecture

2.3 Network Devices

All the physical devices of the NGCSS may be in the same local
area network (LAN). The LAN is designed in a two-network and
two-plane structure to avoid single-point faults. These physical
devices communicate with one another through two adaptive high-
speed layer 3 Ethernet switches.
Signaling and media must run in different network segments so
that media streams do not affect control flows.

Confidential and Proprietary Information of ZTE CORPORATION 17

NGCSS Fundamental

This page is intentionally blank.

18 Confidential and Proprietary Information of ZTE CORPORATION

�3 Software Architecture
After you completing this chapter, you will know:
>> Overview
>> SIP Proxy Module
>> Parlay Application Module
>> Mail Processor Module
>> Notify Scheduler Module
>> Mail Clear Server Module
>> Network Storage Module
>> Database Server Module
>> Media Server Module
>> UMA Module
>> Web Module
>> Smart Call Alert Module
>> VGW Module
>> BOSS Agent Module
>> Statistics Module
>> OMMP Module
>> System Monitor Module

3.1 Overview
The NGCSS has a modular software architecture. The figure below
illustrates the software architecture.

FIGURE 6 NGCSS SYSTEM SOFTWARE ARCHITECTURE

Confidential and Proprietary Information of ZTE CORPORATION 19

NGCSS Fundamental

3.2 SIP Proxy Module

The SIP Proxy module is a message forwarding device between
Parlay Application modules and the softswitch devices. Based on
predefined rules, the SIP Proxy module distributes SIP messages
from the softswitch devices to different Parlay Application mod-
ules, maintains sessions between the softswitch devices and Parlay
Application modules, and maintains a load balance across Parlay
Application modules.

3.3 Parlay Application Module

As a core module of the NGCSS, the Parlay Application modules
provide the following functions:
¡ Communicating with the core network softswitch devices or
other external application servers through the SIP Proxy mod-
ule to accomplish call control
¡ Determining service logic to invoke according to received sig-
naling messages and controlling service execution according to
service logic
¡ Requesting media resources and resources on other modules
for service calls

3.4 Mail Processor Module

The Mail Processor module provides the following mail processing
functions for the NGCSS:
¡ Copying mails on request of Parlay Application modules
¡ Moving mails on request of Parlay Application modules
¡ Merging mails on request of Parlay Application modules

3.5 Notify Scheduler Module

The Notify Scheduler module provides the following notification
functions for the NGCSS:
¡ Sending mail notification messages to subscribers through the
UMA module on request of Parlay Application modules
¡ Sending MWI clearing messages to subscribers through the
UMA module on request of the BOSS Agent module
¡ Sending mail, mailbox or message deletion notification mes-
sages to subscribers through the UMA module on request of
the Mail Clear module
¡ Resending expired and timed out notification messages

20 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Software Architecture

¡ Resending notification messages at scheduled times, based on

the notification failure records stored in the Database module,
and using predefined notification modes

3.6 Mail Clear Server Module

The Mail Clear module provides the following functions for the
NGCSS:
¡ Deleting expired messages automatically
¡ Deleting expired mails automatically
¡ Deleting specified mails on request of Parlay Application mod-
ules
¡ Deleting expired mailboxes automatically
¡ Deleting directories and files stored in deregistered mailboxes
on request of Parlay Application modules, the BOSS Agent
module, or Web module

3.7 Network Storage Module

The Network Storage module provides the following functions for
the NGCSS:
¡ Storing voice (WAV), fax (TIF) and email files
¡ Providing NFS file access for other modules

3.8 Database Server Module

The Database module stores the following data:
¡ System and service configuration data
¡ User profile data
¡ Voice, fax, video and mail encapsulation data
¡ Service statistics and analysis data

3.9 Media Server Module

The Media Server module provides the following media resource
functions for the NGCSS:
¡ Voice playing
¡ Voice recording
¡ Audio conferencing

Confidential and Proprietary Information of ZTE CORPORATION 21

NGCSS Fundamental

¡ Fax receiving and sending

¡ DTMF signal collection and decoding

3.10 UMA Module

The UMA module provides the following message sending functions
for the VMS service:
¡ Receive requests from the Notify Scheduler module and send
notification messages to subscribers according to the requests.
¡ Receive requests from the Parlay server and send notification
messages to subscribers according to the requests.

3.11 Web Module

The Web module provides the Web portal function for system man-
agement and service management through Web.

3.12 Smart Call Alert Module

The Smart Call Alert module provides the following functions for
the NGCSS:
¡ Receive requests from the Parlay server and integrate MCN
notification messages according to the requests.
¡ Send the integrated MCN notification messages to the VGW
module, which will delivery the short messages.

3.13 VGW Module

The VGW module provides the following SMS functions:
¡ Receive requests from the Smart Call Alert module and forward
integrated MCN notification messages to the SMSC, which will
send the messages to subscribers according to the requests.
¡ Receive self-service request messages from the SMSC, con-
vert them into internal messages and send them to the Parlay
server module for processing.
¡ Receive the result messages of self-service request processing
from the Parlay server and forward them to the SMSC, which
will send them to subscribers.

22 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 3 Software Architecture

3.14 BOSS Agent Module

The BOSS agent module provides the BOSS access function to ac-
complish registration, deregistration, user data query and modifi-
cation in the BOSS.

3.15 Statistics Module

The statistics module collects original service data and system data
and automatically generates reports on service usage, system per-
formance and system resource usage.
The carrier can query statistical results through the web portal
provided by the web module, and export the results in different
formats.

3.16 OMMP Module

The OMMP module provides the following functions for the NGCSS:
¡ Service resource management function
¡ Service data configuration function
¡ Service running control function
¡ Service monitoring function

3.17 System Monitor Module

The System Monitor module provides the following functions for
the NGCSS:
¡ Periodically querying the running status of each module and
generating performance counters
¡ Reporting failure alarms and performance alarms to the NMS

Confidential and Proprietary Information of ZTE CORPORATION 23

NGCSS Fundamental

This page is intentionally blank.

24 Confidential and Proprietary Information of ZTE CORPORATION

 �4 Service Introduction
After you completing this chapter, you will know:
>> Voice Mail Service
>> Missed Call Notification Service

4.1 Voice Mail Service

4.1.1 Service Overview

The VMS service is a personalized communication tool that have

information delivery, storage, retrieval, deletion, forwarding and
notification functions. This service allows VMS subscribers to leave
and retrieve voice messages. It also provides the function of no-
tification upon new messages and other auxiliary functions. The
VMS service supports voice messages and fax messages. Sub-
scribers can subscribe to either or both of the two message types.

4.1.2 Guest Access Scenario

Guest Records ¡ Play Free Announcement

Message
To prompt the caller that his calling has been forwarded to VMS
service, system plays a free announcement after receiving a
guest calling. If caller hangs up during this announcement,
the caller is not charged.
¡ Check Mailbox Full
To limit the mailbox capacity, VMS service sums up total
amount of voice messaged in the called party’s mailbox. If
reach the maximum pieces defined in mailbox CoS (Class of
Service), VMS service prompts the caller and then releases
this call.
¡ Play Greeting
In guest call flow, VMS service can play greeting before record.
¡ Input Specific Key to Skip Call Flow
Before recording, the caller can input # key to interrupt an-
nouncement or greeting. VMS service requests the caller to
input password of the called party’s mailbox. If password au-
thentication is past, system executes the subscriber flow.
Before recording, the caller can input * key to interrupt
announcement or greeting. System directly starts to begin
recording.

Confidential and Proprietary Information of ZTE CORPORATION 25

NGCSS Fundamental

Besides the # or * key, system ignores any other invalid key

inputted by user.
¡ Input Specific Key to End Recording
During recording, the caller can input # key to end the record-
ing. After that, the caller can edit the record segment, set
delivery option or directly deposit this message to mailbox.
¡ Input Specific Key to Cancel recording
During recording, the guest can input * key to cancel the
recording. VMS service returns to begin recording again.
¡ Release Call if Repeatedly Cancel Recording
Some advertisement companies make out-dialing to end users
by its Media Server. This ad call maybe is redirected to VMS
service if the called party can’t receive incoming call. To release
call ASAP, ad company’s Media Server will send * key period-
ically (e.g., in 3 second interval) after the call is answered. If
VMS service detects the caller party cancels recording repeat-
edly for configured times (e.g. 3 times) in one call instance.
VMS service will automatically release this call.
¡ Automatically End Recording when Reach Max Length
Max time length of each voice message is defined in CoS pro-
file. If recording time length reaches the max limit, VMS ser-
vice automatically stops the recording and prompts the caller.
After that, the caller can edit the record segment, set delivery
option or simply deposit this message to mailbox.
¡ Hang Up to Deposit Message
For convenient usage, the caller can simply hang up after
recording a voice segment. If this segment is not an empty
voice segment, VMS service will automatically save it as a
voice message to the called party mailbox.
¡ Empty Message Check
To avoid empty message in mailbox, VMS service checks
whether the recording time length is large than the configured
invalid message length, no matter the caller inputs # key to
end recording or hangs up during recording.
Guest Edits After record message, the guest has the following options:
Message
¡ Edit the recording
¡ Send
¡ Delivery option
In edit option, the guest can choose the operation below:
¡ Replay: System plays the recorded voice segment.
¡ Re-record: System begins recording a voice segment to over-
write the recorded one.
¡ Append recording: The caller can record another voice seg-
ment. System adds this segment to the tail of the recorded
one as a whole voice message. To limit the max length of each
message, system disables the append option if the time length
of the combined voice message reaches the max length.
Guest Delivers In this option, the guest can set the following delivery conditions.
Message

26 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Service Introduction

Delivery Time Set The guest can input a future date and time to deliver his voice
message to the mailbox subscriber. The future delay days must
be less than the max configured days (e.g. 60 days). Before the
data time reaches, mailbox subscriber can’t hear this hidden voice
message in his mailbox. When this date time reaches, system
automatically changes voicemail as a “visible” voice message and
send a new message notification to the mailbox subscriber.
Delivery Class Set The guest can set his voicemail as one of the class types below:
¡ Urgent
¡ Confidential
¡ Urgent and Confidential
¡ Normal
Urgent message is played prior to others in messages queue. For
confidential message, the mailbox subscriber is forbidden to for-
ward it to other mailbox.

4.1.3 New Message Notification

Introduction After a mailbox receives a new message, VMS service sends new
message notification to mailbox subscriber immediately. Various
notifications can be supported. System executes the notification
procedure according to the mailbox configuration.
MWI Notification MWI (Message Waiting Indicator) message activates a special icon
displaying on the top of mobile screen. A flash string, which is
generated by SMSC template, displays total count of new voice
messages in mailbox. Meanwhile mobile activates two shortcut
buttons of dial and exit. If user clicks the dial button key, mobile
will automatically dial the short access code stored in SIM card.
So user can directly listen to new voice message.
If one mailbox uses MWI notification method, VMS service sends
the specific MWI message to change the new message counter
stored in mobile or cancel the icon on mobile screen at the follow-
ing cases:
¡ One or all new voice messages in one mailbox are heard.
¡ One or all new voice messages in one mailbox are automatically
purged because of expiration.
¡ One mailbox with new messages is deleted by OSS.
SMS Notification To provide more information about new voice message, system
sends a text short message to the mobile. The content of short
message is like as “New voice message received! Last one <Date
Time> from Caller <Sender>. Please call *100 to listen. ” or
“New voice message received! Last one <Date Time> from un-
known caller. Please call *100 to listen.”. Administrator can easily
configure the content template for different CoS and language.
To avoid receiving more than one short message when the mailbox
subscriber powers on, VMS service can configure to set the replace
flag in SMPP message of SMS notification.
Out-dialing If mailbox subscriber activates out-dialing notification, VMS ser-
Notification vice makes an outgoing call to the mailbox subscriber with a source
number assigned by operator. If the call is answered, system

Confidential and Proprietary Information of ZTE CORPORATION 27

NGCSS Fundamental

prompts the called party there is new message in her or his mail-
box. If the call can’t be answered, system will retry the next
out-dialing. The max retry times, retry interval and the out-dialing
start time and end time permitted in one day can be configured by
administrator.
To avoid the outgoing call is redirected and looped back to VMS
service because the called party is unreachable, VMS service will
check the CLI (Calling Line Identification) number of each incoming
call. If the CLI is equal to one out-dialing number assigned by
operator, system will directly release this call.
If subscriber enters mailbox to hear all new messages, the system
will not make outgoing call again.

4.1.4 Common Access Scenario

After user dials the common access code and call is connected
to VMS service, system requests the caller to choose deposit or
receive voice message. If choose to deposit message, system re-
quests user to input the mailbox number, the call flow will skip to
guest flow to play greeting and deposit message. Otherwise, sys-
tem requests user to input mailbox number and skips to password
check for subscriber call flow.

4.1.5 Subscriber Access Scenario

Introduction In subscriber access scenario, the voice mail subscriber can re-
trieve and manipulate her or his voice messages, send voice mes-
sage and configure own mailbox.
New User Tutorial When a mailbox subscriber dials subscriber access code at first
time after mailbox is created, VMS service will guide this user to
initialize her or his voice mailbox:
¡ Choose subscriber language
¡ Set a new password
¡ Record voice signature
¡ Record personal greeting
To new user tutorial, it is restricted that subscriber must enter via
own phone of the mailbox by dialing subscriber access code.
Identification and ¡ Subscriber Access by Dialing Own Phone
Authentication
A subscriber can dial own phone number via the phone which
registers mailbox. This call is forwarded to VMS service be-
cause the called party is busy. System judges CLI is the same
with the original called party number and then executes the
subscriber access flow.
¡ Identify CLI
A mailbox subscriber can dial the subscriber access code di-
rectly via the phone which registers mailbox. System identifies
CLI of the caller as a mailbox number. If this mailbox doesn’t

28 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Service Introduction

activate the password check, subscriber can enter own mail-

box directly.
¡ Password Authentication
If mailbox subscriber turns on the password check, system will
request user to input password even if accessing from own
phone. Dial via common access code or skip from guest ac-
cess to subscriber flow, the password authentication is always
requested no matter password check is on or off.
Broadcast Bulletin To help operator to issue service notice or promotion information
to user via VMS service, ZTE VMS service supports bulletin.
¡ Operator Uploads files as bulletins via Web
Administrator can upload one or more voice files as bulletins.
Administrator can configure different bulletins for different ar-
eas. These files are not stored into users’ mailboxes.
¡ Play New Bulletins to Subscriber
If one mailbox subscriber doesn’t listen to new bulletins, VMS
service will automatically play the unheard bulletins to sub-
scriber one by one. Subscriber can skip any bulletin and return
to main call flow. At next time, system won’t play the heard
bulletins to this subscriber again.
Mailbox Status ¡ Mailbox Full Alert
If mailbox is full, VMS service alerts subscriber to delete some
messages to keep available capacity.
¡ Remind Special Greeting
If mailbox has a special greeting currently, VMS service will
remind subscriber.
¡ Mail Count
At subscriber logs into mailbox, VMS service advises total count
of new or stored messages and count of urgent messages.
Play Message ¡ Auto-Play New Message
If there is new message in mailbox and mailbox turns new mes-
sage auto-play on, system will automatically play new message
after mail count is played. If subscriber doesn’t input any key
during new message is played, system plays next new mes-
sage one by one. After each new message is played, system
automatically sets the new message as saved status.
¡ Message Queue
The message queue is played as following sequence:
� Urgent message, order is LIFO (i.e., latest one is played
first).
� Confidential message, order is FIFO (i.e., oldest one is
played first).
� Normal message, order is FIFO.
� Stored message, order is FIFO.
A confidential message is always confidential, even after it is
listened. One urgent message is no more urgent after listened.

Confidential and Proprietary Information of ZTE CORPORATION 29

NGCSS Fundamental

During messages are played, subscriber has the following op-

eration options:
� Replay message
� Previous Message
� Next Message
¡ Message Header
If mailbox subscriber turns on message header auto-play, VMS
service automatically plays each message’s header before
message content. The header includes the information of one
message:
� Message Type of voice, fax or video
� Urgent or Confidential flag
� Message sender: if the sender registers voice mailbox and
records a voice signature, system will play its voice signa-
ture. Otherwise, system plays the sender’s the CLI digits.
If the sender number is unknown (i.e., CLI is restrict to
present or empty CLI), system skips to play the sender
number.
� Deposit date time: “Today” or “Yesterday” is played if the
message was deposited at today or yesterday.
For example, “An urgent message of <NNN> received at <Date
Time>” or “An urgent, confidential message received at <Date
Time>”.
Manipulate After a message is played, subscriber has the following operation
Message options:
¡ Save message
If subscriber selects to save one new or old message, this mes-
sage will be stored in subscriber’s mailbox for certain days. The
retention duration of new message, old message, saved mes-
sage is separately configured in CoS profile. If one new mes-
sage is just heard but not saved, this message can be stored
only for the retention duration of old message.
¡ Delete message
After one message is chosen to delete in one calling, VMS ser-
vice doesn’t delete it but just marks a pending-deletion flag
on it before this calling ends. Subscriber can return to this
message and save it again. At the end of each subscriber ac-
cess calling, system automatically removes the pending-dele-
tion messages from this user’s mailbox.
¡ Forward message to others
If mailbox CoS is qualified with forward or reply feature, this
option is available. Subscriber can forward or reply this mes-
sage. Just when the message is not confidential, the for-
ward option is available. After subscriber chooses to forward
one message, system will ask user to input the message’s re-
ceivers. Subscriber can input one or more individual phone
numbers or mail lists. After input receivers, subscriber can
record a voice segment as comment. System appends this
voice segment at the head of the forwarded message. Of
course, if the forwarded message has reached the max mes-
sage length, comment option is not provided.

30 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Service Introduction

4.1.6 Personalize Mailbox

Multiple VMS service supports multiple languages. Subscriber can choose

Languages and one language for prompt and notification content for self.
Various Speech
Styles Administrator can upload different groups of prompt files and con-
figure the notification content templates for different languages.
Before subscriber selects preferred language, system plays prompt
(e.g., announcement after out-dialing) or generates the notifica-
tion content in the default language set by administrator.
For different user groups such as business people or youth,
operator can record more than one set of service prompts with
different styles for target user segments. Administrator just
needs to define virtual language and configure the storage di-
rectory for such prompt set, for example, English4Bussiness or
English4Youth. System can play the corresponding prompt clips
in its true syntax. There is no limit on different styles for each
language.
Manage Greeting System supports the following different types of greeting:
¡ Personal Greeting: The max time length is set in CoS profile.
Default value is 60 seconds.
¡ Special Greeting: The max time length is the same with the
max of persona greeting.
¡ Voice Signature: The time length is configured as a system
parameter. Default is 15 seconds.
At first, system plays mailbox’s current personal greeting, spe-
cial greeting or voice signature. If subscriber has not recorded a
personal greeting, system will remind user and play the system
greeting or voice signature greeting current used by this mailbox.
During edit a greeting, subscriber has the following options:
¡ Keep current greeting
¡ Record a new voice segment to overwrite current one
¡ Delete special greeting or voice signature
Configure Mailbox subscriber can configure:
Password
Modify password to a new digits. The min and max length of pass-
word is configured as system parameter. Default is 4 digits.
Turn password check on or off
Select Notification VMS service supports the new message notifications below:
Method
¡ MWI notification
¡ SMS notification
¡ Out-dialing notification
The available notification methods of one mailbox is defined in CoS
profile.
Message Header Subscriber can turn the message header auto-play on or off. If
Auto-play On/Off turn off, system just plays the header as below:

Confidential and Proprietary Information of ZTE CORPORATION 31

NGCSS Fundamental

¡ The message’s urgent, confidential or urgent + confidential flag

but neither sender number nor deposit date time, e.g.” Mail
mark with urgent and confidential”.
¡ System failure message.
¡ Header of delivery report message.
New Message Subscriber can turn o the new message auto-play on or off. If
Auto-play On/Off turn off, system doesn’t play automatically the new message in
mailbox. Subscriber should select to retrieve message in main
menu.

4.1.7 Mailbox Provisioning

Multiple To flexibly accommodate the integration with different network op-

Provisioning erators, NGCSS supports the MML interfaces with operator OSS.
Interfaces with
OSS Through provisioning interface, OSS can create, delete, modify
and query one mailbox.
Mailbox VMS administrator can create, delete, modify and query mailbox.
Provisioning via Except mailbox management by individual mailbox or mailbox seg-
Management Web ment, administrator can create a batch command text file with the
Interface ZTE defined format, in which there are one or more creation, dele-
tion or modification command lines. Administrator can upload the
batch command file via management web, system can automati-
cally parse each command in this file and execute each provision-
ing command. Finally, system exports a command result file in
which there is a command execution result corresponding com-
mand.

4.1.8 Dynamic Mailbox

Default For dynamic box, administrator can configure the default param-
Parameters for eters, including:
Dynamic Mailbox
¡ Password check on/off
¡ Default password
¡ CoS code
¡ Language
¡ New message notification Mode
¡ New message auto-play on/off
¡ Message header auto-play on/off
Dynamic Creation To automatically recycle the mailbox license, NGCSS supports dy-
and Deletion namic mailbox. There are two application scenarios:
¡ Automatic mailbox creation
Administrator can configure the prefixes of dynamic mailbox.
After VMS service receives an incoming redirected call, if the
called party has no voicemailbox but the called party matches
with one of the configured dynamic mailbox prefix, VMS ser-
vice automatically creates one new mailbox for this called party

32 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Service Introduction

number with the default mailbox profile. Then the caller can
deposit a voice message in this mailbox. Meanwhile, if a user
dials the subscriber access code but she or he doesn’t have a
voicemail box. VMS service will check whether or not the caller
number matches one of dynamic mailbox prefix. If true, sys-
tem automatically creates a new mailbox for this user. By this
way, voicemail service is on-demand for users.
¡ Automatic mailbox deletion
For one dynamic mailbox, VMS service automatically deletes it
if any of the following condition is met:
� This mailbox has not been accessed by guest or subscriber
beyond the configured retention days.
� This mailbox is empty of any message.
After one dynamic mailbox is deleted, its storage space and
license will be reused by other user.

4.1.9 Expired Message Auto-Purge

At each night, VMS service scans each new/old/saved message

stored in each mailbox. If there is an expired message, system
automatically deletes its data from service Database and its mes-
sage file from storage server. If a new message is deleted and
mailbox uses MWI notification, VMS service sends an update or
deactivation MWI message to mailbox user.

4.2 Missed Call Notification

Service
4.2.1 Service Overview

If a subscriber registers the MCN service, when this subscriber’s

phone is power off or out of service area, calls to this subscriber
will be forwarded to the MCN system. The system at first prompts
the caller and then via the SMSC sends a missed call notification
(containing the calling number, calling time and total call times) to
the destination phone number that is set by the subscriber. If the
caller is in the blacklist, the system will not send the missed call
notification to the subscriber.

4.2.2 Delay to Trigger Missed Call

Notification

Usually a caller places more than one call attempts continuously in

a short time if the called party is unreachable or busy. To reduce

Confidential and Proprietary Information of ZTE CORPORATION 33

NGCSS Fundamental

SMS traffic and avoiding receiving unnecessary notification mes-

sage (especially when subscriber is busy without waiting activation
or in data call), the NGCSS system can delay to trigger notifica-
tion for a certain period after receiving a missed call to one MCN
subscriber. System just captures and holds all the missed calls for
this subscriber received during this period. When the delay time
reaches, system generates one or more notification messages and
sends to this subscriber.
Different delay period can be configured for busy, out of coverage
and switched off, for example, busy is 5 minutes period, out of
coverage or switched off is 15 minutes period. Busy condition has
highest priority than others.

4.2.3 Aggregated Notification

Comprising Different Callers

To reduce SMS flow in signal network and show more missed call
info to user, NGCSS support aggregated notification from different
callers in one SMS.
The maximum count of callers in one notification message is con-
figured by administrator and it is 3 by default. If the count of
callers in one missed call notification message doesn’t reach the
maximum value, a new missed call from other distinct caller will
be integrated to this missed call notification message before it is
delivered to subscriber. If one missed call notification message
contains maximum count of callers, a new missed call from other
distinct caller is received by system and a new missed call notifi-
cation message for this call is generated.
There is an example of aggregated missed call notification mes-
sage:
“You have received 1 missed call(s) from 9234354541 at 11:30
AM on Sep. 16, 2 missed call(s) from 9374368432 at 3:30 PM on
Sep. 17, 3 missed call(s) from 9426823346 at 6:43 PM on Sep.
17.”.
After an missed call notification message is delivered to subscriber
by SMSC, all the missed calls carried in this message should be not
notified to subscriber again.

4.2.4 User Blacklist

To avoid disturb, MCN subscriber can send a specific keyword SMS

with one blocked call number (e.g. BAR 12345678) to a short code
of MCN system. System will refuse to send missed call notification
from this blocked caller. Subscriber can send a specific SMS to
unblock one caller (e.g. UNBAR 12345678) or to query all the
blocked callers (e.g. barlist).

34 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Service Introduction

4.2.5 Activate/Deactivate Missed Call

Notification

Subscriber can send a keyword SMS to a short code to deactivate

or activate missed call notification temporarily. If a subscriber de-
activates missed call notification, the MCN system doesn’t send
missed call notification message to him. After subscriber activates
missed call notification again, missed call notification message for
new missed call will be sent to him normally.
For friendly user usage, administrator can turn on the automatic
reminder SMS to the subscriber who has deactivated the MCN ser-
vice currently in configure period.

4.2.6 SMS Templates for CoS and

Language

To provide diverse service for different user group, administrator

can configure the content template of missed call alert for different
CoS and language.

4.2.7 Push Or Pull Missed Call Info

Push Missed Any postpaid or prepaid user of operator can subscribe to MCN ser-
Call Info to vice with monthly charge. If a missed call for a subscription based
Subscription User MCN user lands up to MCN system, the system automatically gen-
erates a new notification message for this call info or aggregates
this call info to a pending notification message. Then system sends
this notification directly to SMSC for delivery. When subscriber’s
mobile becomes available, subscriber receives notification imme-
diately.
To avoid disturbing MCN subscriber because of receiving large
number of notification messages, administrator can configure
the maximum count of notification messages pending delivery in
SMSC. This limit is 3 by default. If SMSC stores maximum count
of notification messages for an unreachable subscriber, MCN
system will replace the oldest missed call item in one notification
message by a new missed call item. For example, during one
subscriber A switches off, there are 3 notification messages in
SMSC pending to send to him as below:
¡ Message 1: “You have received missed call(s) from A1 at T1,
B1 at T2, C1 at T3”
¡ Message 2: “You have received missed call(s) from A2 at T4,
B2 at T5, C2 at T6”
¡ Message 3: “You have received missed call(s) from A3 at T7,
B3 at T8, C3 at T9”
In all the above messages, T5 in message 2 is the oldest calling
date time. When another caller Y fails to call the unreachable sub-

Confidential and Proprietary Information of ZTE CORPORATION 35

NGCSS Fundamental

scriber A at time T10, MCN system will generate new content “A2
at T4, Y at T10, C2 at T6” to replace message 2 stored in SMSC.
Pull Missed To increase service penetration, operator can promote MCN service
Call Info by to certain phone number segments or specific phone numbers. If
Pay-per-used User a promoted user has a missed call, MCN system sends a SMS only
to prompt he has missed call and if he wants to get call details,
he can send a specific keyword SMS (e.g. GET) to a short code
of MCN system. When MCN system receives this SMS from this
user, system queries the user’s missed call info, generates an no-
tification SMS and sends. If other missed call info for this user still
exists, there is a prompt in the end of notification message. Then
as guide, this user can pull out more notifications by send another
keyword SMS (e.g. MORE). For this mode, user will be charged for
each MO SMS.
Administrator can configure the notification content templates:

Template Example

Promotion message You have 4 missed Calls at 11:30 AM

on Sep. 17. For information send
GET to 123. SMS charges 2 cents per
message.

Notify to pay-per-used user You have received 1 missed call(s)

from 9212345678 at 11:30 AM on Sep.
17, 2 missed call(s) from 9287654321
at 3:30 PM on Sep. 17.

Notify to pay-per-used user You have received 1 missed call(s)

with more prompt from 9211111111 at 11:30 AM on Sep.
17, 2 missed call(s) from 9222222222
at 3:30 PM on Sep. 17. Send MORE
to get more.

4.2.8 Distinguish Different Missed Call

Reasons

Missed call notifications will be provided to subscribers when called

party falls in any of the following categories:
¡ Phone switched off
¡ Subscriber out of network coverage area
¡ Subscriber busy without call waiting activated
NGCSS can flexibly be configured whether or not to trigger MCN
notification for each redirection reason filled in IAM message by
MSC.

4.2.9 Announcement Modes

The mcn service provides the MSC plays announcements.

36 Confidential and Proprietary Information of ZTE CORPORATION

 Chapter 4 Service Introduction

Using this mode, the service maps MCN forward reasons to the
corresponding call release reasons and let the MSC play announce-
ments according to call release reasons.

4.2.10Supporting Multi-Language

Function A subscriber can select a language, and then the IVR announce-
ments and notification SMs will use the language.
Principle 1. The administrator sets multiple languages on the Web portal.
2. After an MCN subscriber connects the system through IVR,
he/she can select the favorite language.

Confidential and Proprietary Information of ZTE CORPORATION 37