IPLOOK MSC/VLR Feature Specification

The information in this document is proprietary to IPLOOK . The information shall not be used, copied, reproduced or disclosed
in whole or part without the written consent of IPLOOK Office of Technology Development.
Copyright 2018 IPLOOK All Rights Reserved
IPLOOK MSC/VLR (GSM and WCDMA)
Feature Specification
V2 2017.3

Table of Contents
1 Feature List................................................................................................................................................... 6
1.1 MSC Function........................................................................................................................................ 6
1.2 VLR Function.......................................................................................................................................10
1.3 SMSC Function....................................................................................................................................11
1.4 RTP Proxy Function............................................................................................................................11
1.5 SMCLI Function...................................................................................................................................12
1.6 MNP Function......................................................................................................................................12
1.7 EMS Function...................................................................................................................................... 13
1.8 Iu UP Gateway Function....................................................................................................................14
2 Function Specifications............................................................................................................................. 15
2.1 LITECORE 3G Core Network Architecture.....................................................................................15
2.2 Interfaces..............................................................................................................................................15
2.2.1 A Interface to BSC........................................................................................................................................16
2.2.2 SS7 Networks............................................................................................................................................... 16
2.2.3 ISUP............................................................................................................................................................... 17
2.2.4 Stream Control Transmission Protocol (SCTP).......................................................................................18
2.2.5 MTP 2 User Adaptation (M2UA).................................................................................................................19
2.2.6 MTP 3 User Adaptation (M3UA).................................................................................................................20
2.2.7 Session Initiation Protocol (SIP).................................................................................................................20
2.2.8 Radio Access Network Application Part (RANAP) Protocol..................................................................21
2.2.9 Iu Interface.....................................................................................................................................................22
2.2.10 Iu User Plane (Iu-UP) Protocol...................................................................................................................23
2.2.11 Media Gateway Control Protocol (Megaco)............................................................................................. 24
2.3 Voice Services.....................................................................................................................................25
2.3.1 Telephony - Full Rate Speech.................................................................................................................... 25
2.3.2 Emergency Calls...........................................................................................................................................25
2.3.3 Emergency Calls Enhancements...............................................................................................................26
2.3.4 DTMF..............................................................................................................................................................26
2.3.5 Multiple Vocoders......................................................................................................................................... 27
Reference.....................................................................................................................27
2.3.6 Payload Type Selection...............................................................................................................................27

2.4 Supplementary Services....................................................................................................................28
2.4.1 Call Forwarding.............................................................................................................................................28
2.4.2 Call Forwarding Unconditional................................................................................................................... 28
2.4.3 Call Forwarding on Mobile Subscriber Busy............................................................................................29
2.4.4 Call Forwarding on Mobile Subscriber Not Reachable.......................................................................... 29
2.4.5 Call Forwarding on No Reply......................................................................................................................30
2.4.6 Call Forwarding on Mobile Subscriber Unavailable................................................................................31
2.4.7 Call Forwarding - Cancel All....................................................................................................................... 31
2.4.8 Notification of Call Forwarding................................................................................................................... 32
2.4.9 Call Hold.........................................................................................................................................................32
2.4.10 Call Waiting....................................................................................................................................................33
2.4.11 Call Barring....................................................................................................................................................34
2.4.12 Barring of All Outgoing Calls.......................................................................................................................34
2.4.13 Barring of Outgoing International Calls.....................................................................................................35
2.4.14 BOIC Except Directed to Home PLMN Country......................................................................................35
2.4.15 Barring of All Incoming Calls.......................................................................................................................36
2.4.16 BIC When Roaming Outside 0f Home PLMN Country...........................................................................36
2.4.17 Password Control......................................................................................................................................... 37
2.4.18 Operator Determined Barring..................................................................................................................... 37
2.4.19 ODB - Outgoing Calls.................................................................................................................................. 38
2.4.20 ODB - Incoming Calls.................................................................................................................................. 39
2.4.21 ODB - Roaming Outside HPLMN/HPLMN Country................................................................................ 39
2.4.22 ODB - Premium Rate Calls (Information/Entertainment)....................................................................... 40
2.4.23 ODB - Supplementary Service................................................................................................................... 40
2.4.24 Operator Specific Barring (OSB)................................................................................................................41
2.4.25 Calling Line Identification Presentation.....................................................................................................41
2.4.26 Calling Line Identification Restriction........................................................................................................ 42
2.4.27 Connected Line Identification Presentation..............................................................................................42
2.4.28 Connected Line Identification Restriction................................................................................................. 43
2.4.29 Unstructured Supplementary Service Data..............................................................................................43
2.4.30 Explicit Call Transfer.................................................................................................................................... 44
2.4.31 enhanced Multi-Level Precedence and Preemption (eMLPP)..............................................................45
2.5 Short Message Services....................................................................................................................46
2.5.1 Short Message Service Mobile Originated...............................................................................................46
2.5.2 Short Message Service Mobile Terminated..............................................................................................46
2.5.3 Short Message Broadcasting (ESME-SMB)............................................................................................ 47

2.6 Enhanced Services.............................................................................................................................48
2.6.1 Voice Mail Service........................................................................................................................................48
2.6.2 Mobile Number Portability - Database Query.......................................................................................... 48
2.6.3 Mobile Number Portability - Ported Number Reception......................................................................... 49
2.6.4 SMS Email Gateway....................................................................................................................................49
2.6.5 Lawful Interception....................................................................................................................................... 50
2.6.6 Intelligent MAP-D Multiplexer (IMDX)....................................................................................................... 51
2.6.7 Open-to-all Prepaid Roaming (OPR).........................................................................................................52
2.6.8 Location Services (LCS)..............................................................................................................................53
2.6.9 IP Private A-link Intelligent Multiplexer (iPALIM)......................................................................................53
2.6.10 intelligent Gb Routing System (iGRS).......................................................................................................55
2.6.11 Gb Converter.................................................................................................................................................55
2.6.12 intelligent RTP Local Switching (iRLS)......................................................................................................56
2.6.13 Voice Insertion Monitoring (VIM)................................................................................................................57
2.6.14 User Equipment Simulator (UES)..............................................................................................................57
2.6.15 Multi-Core Multi-System (MCMS)..............................................................................................................58
2.7 Numbering and Routing.....................................................................................................................59
2.7.1 Flexible / Multiple Point Codes...................................................................................................................59
2.7.2 Longest-prefix Match Routing.....................................................................................................................59
2.7.3 Called Number Group Routing...................................................................................................................60
2.7.4 Intelligent Routing.........................................................................................................................................60
2.7.5 Number Length Dependent Routing..........................................................................................................61
2.7.6 Routing by Caller Location..........................................................................................................................61
2.7.7 Uniform Numbering Plan.............................................................................................................................61
2.7.8 Registered Exchange Numbering Plan.....................................................................................................62
2.7.9 Current Exchange Numbering Plan...........................................................................................................62
2.7.10 Flexible Recorded Announcements...........................................................................................................63
2.7.11 Recorded Announcements on Call Hold...................................................................................................63
2.7.12 Datafillable Cause Values........................................................................................................................... 63
2.7.13 Support for ‘*’ & ‘#’ Dialing...........................................................................................................................64
2.8 Mobility..................................................................................................................................................64
2.8.1 Location Update............................................................................................................................................64
2.8.2 IMSI Attach and Detach...............................................................................................................................65
2.8.3 VLR Purge..................................................................................................................................................... 65
2.8.4 Handover....................................................................................................................................................... 66
2.8.5 Inter PLMN Roaming................................................................................................................................... 66

2.8.6 Country Specific Roaming Restrictions.....................................................................................................67
2.9 Security.................................................................................................................................................68
2.9.1 Authentication............................................................................................................................................... 68
2.9.2 Ciphering........................................................................................................................................................68
2.9.3 Support for TMSI.......................................................................................................................................... 69
2.9.4 Ki Encrypted in AUC.....................................................................................................................................69
2.9.5 Multiple Concurrent A3/A8 Algorithms Support in AUC..........................................................................70
2.9.6 IMEI Checking...............................................................................................................................................70
2.10 Elements Management...................................................................................................................... 71
2.10.1 HTML Based Graphic Display.................................................................................................................... 71
2.10.2 Linkset and SG Status.................................................................................................................................71
2.10.3 Trunk Group and MG Status.......................................................................................................................71
2.10.4 Online License Update................................................................................................................................ 72
2.10.5 Detailed Statistic by Category Index......................................................................................................... 72
2.10.6 Database Backup and Restore.................................................................................................................. 74
2.10.7 Near Real Time Roaming Data Exchange (NRTRDE)...........................................................................75
2.10.8 Welcome Short Message Service..............................................................................................................75
2.10.9 Online Help....................................................................................................................................................76
2.10.10 System Self-protection.................................................................................................................................76
2.11 Multimedia Services........................................................................................................................... 77

1 Feature List
1.1 MSC Function
Feature Descriptions
Interface SCCP (ANSI T1.112, ITU-T Q)
TCAP (ANSI T1.114, ITU-T Q)
ISUP
 ITU ISUP (ITU 92/97)
 ETSI ISUP (ETSI V2)
 ANSI ISUP (ANSI T1.113-1995)
ISDN
 ITU ISDN (Q.931 05/98)
 ETSI ISDN (QSIG ECMA-143)
 ANSI ISDN (NIS-A233-1)
A interface (ETSI, ANSI, IPA BSC):
 BSSMAP: Manage the AIF circuit between MSC and BSC
 DTAP: Implement mobility management, call control, supplementary service and SMS
to mobile station
SSF (GSM 03.78, 03.18):
 CAMEL interface on switch side
MAP 1,2,3 (ETSI, ANSI):
 MAP B (to VLR)
 MAP C (to HLR)
 MAP D (VLR to HLR, for inter-PLMN roaming)
 MAP F (to EIR)
 MAP E (to SMSC)
CAMEL I, II, III (ETSI, GSM 09.78)SNMP V2 (RFC 1905): Heartbeat report,parameters
maintenance, CDR, statistics
Soft switch:
 SIGTRAN:
 SCTP (RFC 2960): Provide efficient signaling transport over IP network
between SG and MGC (MSC)
 M2UA (RFC 3331): Adaptation layer for transport of MTP2
 IUA (RFC 3057): Adaptation layer for transport of ISDN Q.921
 M3UA (RFC 3332): Adaptation layer for transport of MTP3
 MTP3 (ANSI, ITU, SCCP-Lite): Messages between the SG and the MGC
 MGCP (RFC 2705): Provide media gateway control function between the MG and MGC
(MSC)
 BICC (ITU-T Q): Provide call service between soft switches
 RTP (RFC 1889): Real time transport of audio packets
 SIP (RFC 3261)
 H.248/MEGACO (RFC 3525, ITU-T H.248) interface to Iu UP Gateway
Signaling 14-bit/24-bit point code
4 SS7 networks
512 linksets, 1024 links

 1 to 16 links per linkset (The total number of links should be less than or equal to 1024)
 Flexible point code: OPC and DPC per linkset
 Network Indicator per linkset
STP (point code and GTT E.164, E.212 and E.214)
Switching and Numbering Uniform numbering plan (NDC dialing plan in HPLMN)
Registered exchange numbering plan (No NDC dialing plan in HPLMN)
Normal routing:
 1023 trunk groups, 1023 trunks
 1 to 127 trunks per trunk group (The total number of trunks should be less than
or equal to 1023)
 Support E.164 “+”
 Longest-prefix match routing
 Called number group routing
 Intelligent routing
 Number length dependent routing
 Alternative trunk group routing
Routing by caller location:
 15 dialing plans, each plan defines:
 1023 16-digit dialing prefixes or groups
 16-digit prefix manipulation for up to 32-digit called number
 Calling number manipulation
 E.164 international number manipulation
 MNP flag
 Premium call flag
 Support up to 31 routing zones, each routing zone has:
 1 dialing plan
 Up to 63 routing plans (trunk group)
 1 announcement plan
 2 AAS/SRF addresses
Mobility Location update
IMSI attach/detach
VLR purge
Intra-MSC handover
Inter-PLMN roaming
1023 location areas
Restoration in VLR
Basic Services Telephony full rate speech (TS11)
Emergency call setup (TS12)
DTMF support
Short message service
CDR and Measurement CDR (GSM12.05)
Measurement (GSM 12.04)
Support CDR local backup
Call Measurement Call service, origination, destination or trunk based statistics
 Mobile originating call
 Mobile terminated call
 Incoming trunk call
 Outgoing trunk call

 Mobile to mobile call
 Trunk to mobile call
 Mobile to IP (Intelligent Peripheral) call
 Trunk to IP call
 IP terminated call
 Mobile to trunk call
 Trunk to trunk call
 Inter-connection call
Statistics on network traffic basis
Security Authentication messages and procedures
Enhanced security (Ki encrypted in AUC)
Multiple concurrent A3&A8 algorithms
EIR inter-working, IMEI checking
Ciphering (A5)
TMSI allocation
IN Services Integrated MSC/SSP
Support for CAMEL flags
Billing records for MO, MT, CF calls
Billing records for transit calls
Billing records for SMS
Diagnostic field stored in billing record
CDR generation
SCP directed activation of call limit timing
Supplementary Services Call forwarding
 Call forwarding unconditional (CFU)
 Call forwarding on subscriber busy (CFB)
 Call forwarding on no reply (CFNRy)
 Call forwarding on subscriber not reachable (CFNRc)
Call hold
Call waiting
Call barring / Operator determined barring
Premium call
Notification of call barring
Password control
Calling line identification presentation (CLIP)
Calling line identification restriction (CLIR)
Connected line identification presentation (COLP)
Connected line identification restriction (COLR)
Notification of call forwarding
Explicit call transfer
Operator specific barring (OSB)
Three-party call (3PTY)
Unstructured supplementary service data (USSD)
Enhanced multi-level precedence and preemption (eMLPP)
Voice Codec Support voice codec G.711, G.729, FR, EFR and AMR
Codec negotiation and transcoding
Enhanced codec support for dynamic payloads
Location Services Cell ID based location query

Standard MAP-interface Lg to Gateway Mobile Location Center
Support up to 1024 LAC+Cell ID
Call Interception Support lawful call interception
Enhanced Services Support SMS
 MO/MT SMS
 Short Message Service to and from Application (SMPP)
 Short Message Service to other SMSC
Voice mail service
Support SRF
Programmable announcement for unattainable call setup and PPS
Call teardown announcement
Call duration control
Echo canceling (Media Gateway)
Support of 3G Support 3G protocols
 MAP (3GPP TS 29.002 V8.10.0 Release 8)
 RANAP (3GPP 25.413 V4.12.0 Release 4)
 Megaco Mc H.248 (ITU-T H.248)
 Iu UP (3GPP TS 25.415 V10.1.0 Release 10)
Support 3G authentication and ciphering
Support 3G multimedia applications
Redundancy Dual switches load sharing and active redundancy
Signaling link redundancy
RTP stream routing redundancy
License Control MSC application flag
8 to 1024 at multiples of 8 trunks
Table 1 MSC function

1.2 VLR Function
Data Management Authentication
Location update
TMSI allocation
MSRN
Ciphering
Purge
Data restoration
IMSI detach/attach
MAP/CAP version negotiation
Basic Services MO/MT call
Emergency call
Short message service
Supplementary Services Call forwarding:
 Call forwarding unconditional (CFU)
 Call forwarding on subscriber busy (CFB)
 Call forwarding on no reply (CFNRy)
 Call forwarding on subscriber not reachable (CFNRc)
Call hold
Call waiting
Call barring
Premium call
Password control
Calling line identification presentation (CLIP)
Calling line identification restriction (CLIR)
Connected line identification presentation (COLP)
Connected line identification restriction (COLR)
Explicit call transfer
Operator determined barring (ODB)
Operator specific barring (OSB)
Three-party call (3PTY)
Unstructured supplementary service data (USSD)
Enhanced multi-level precedence and preemption (eMLPP)
Support of Encryption Encryption provisioning (Kc)
Support of 3G Support 3G authentication and ciphering
Support 3G multimedia applications
Redundancy Dual servers load sharing and active redundancy
License Control VLR application flag
100 to 100k VLR subscribers at multiples of 100
Table 2 VLR function

1.3 SMSC Function
SMS MO, MT point to point short message
MO/MT verification
SMS status report
Delivery acknowledgement
Store max. 100k pending short messages (8 per subscriber)
SMS polling
Default alphabet (English) and UCS-2 character (Chinese)
SM notification:
 Reporting account balance
 Notification for new voice mail
 Notification for low balance or expiry
 Recharge via short message
SMPP Support SMPP v3.4
32 SMPP links over UDP or TCP
Number type and number plan manipulation for up to 64 service numbers
Transmit messages between ESME and SME
Support Tx/Rx/TRx for each SMPP link
Support 7 and 8 bit DCS coding for each SMPP link
Redundancy Dual servers load sharing and active redundancy
License Control SMSC application flag
100 to 100k SMSC subscribers at multiples of 100
Table 8 SMSC function
1.4 RTP Proxy Function
Interface MGCP control protocol per RFC 3435
RTP packet streaming per RFC 3550
RTP Packet Control Media relay for RTP streams between the source and destination MGs
Source MGs filter
MG Resource Control Allocate or release MG resources according to MGCP commands
Support of 3G Iu UP protocol to Iu-UP gateway per 3GPP TS 25.415
Table 11RTP Proxy function

1.5 SMCLI Function
SMCLI Subscriber provisioning command line interface
Independent software module deployed with EMS server
HLR Subscriber Read, create, modify, delete, export and import HLR subscriber
VMS Subscriber Read, create, modify, delete, export and import VMS subscriber
MNP Subscriber Read, create, modify, delete, export and import MNP subscriber
OPPS Subscriber Read, create, modify, delete, export and import OPPS subscriber
iPALIM Subscriber Read, create, modify, delete, export and import iPALIM subscriber
AUC Subscriber Delete AUC subscriber
PPS Subscriber Read, create, modify, delete, export and import PPS subscriber
Recharge account via recharge card or by changing balance
PPS Recharge Card Read PPS recharge card
PPS Tariff Plan Read and modify PPS tariff plan
OPR Subscriber
Registration
Recharge OPR account in PPS database
IMDX Command Read and modify IMDX exclusive access setting
Table 12 SMCLI function
1.6 MNP Function
Solution MNP-SRF
ANSI IN-Query (support in phase 2)
MNP Mobile Number Portability, ability allowing customers change service provider while
retaining an existing mobile phone number
MNP to different networks (with different CC or NDC)
Independent software module deployed with MSS server
Support telephony and SMS
NPDB Number Portability DB, stores all ported subscribers
Network (operator) independent
Synchronized between networks
20K MNP subscribers, capable of expansion
RN Routing Number, identify each PLMN in the portability domain
Used by ported MSISDN for addressing subscription (port-to) network
Redundancy Dual servers load sharing and redundancy
License Control MNP application flag
100 to 100k MNP subscribers at multiples of 100
Table 13 MNP function

1.7 EMS Function
System Platform Ubuntu 12.04 (64bit)
Interface HTML GUI MMI
SNMP compliant
SMCLI
SMPP
Client PC Supported webpage browsers in multiple operation systems:
 Internet Explorer
 Mozilla Firefox
Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) log on
Real Time Status Time synchronization with the network elements
HTML network status GUI
Status details for network elements - application
Status of connections - linkset, TG and MG
Status of hard disk mirroring - raid
System resource summary - platform
Event and alarm counter
Performance Call measurement by entity
Call measurement by category
Call measurement by connection
Enhanced graphic statistics profile
Log Organized CDR for MSC, SMSC, PPS and EIR
PPS daily report
Daily status of PPS accounts
Short message content record
Event and alarm logs
Operation history logs
CDR and measurement backup
Configuration Network element configuration and management
Cascading style parameter configuration
Online license implementation
Support standard MIB file
Account Subscriber profile management
Prepaid card query
Tariff query
Maintenance Database backup and restore
System parameter backup and restore
Manually synchronize configuration between MSS
Subscriber profiles backup
CDR, measurement, event and alarms backup
Periodic export CDR and call measurement via Secure FTP or FTP
Automatically export files to appointed server via Secure FTP or FTP

NRTRDE configuration:
 Support up to 100 roaming partners
 Delays among sending NRTRDE files can be set
 Transmitting NRTRDE data in Secure FTP or FTP
 Directory for NRTRDE files and reports can be separately set
Welcome short message configuration:
 SMPP interface with SMSC
 Messages are definable to the system by country and carrier
 Support 160 7-bit , 140 8-bit, or 70 16-bit characters’ message
 Support up to 100 carriers
 Default messages for undefined carriers
 1 predefined welcome and 8 predefined advertisement messages per carrier
 The validity period of advertisement message can be set
Advanced Operation Network elements customization
Tariff plan setup
Login account management (operator privilege)
Online Help Step by step guide for monitoring, configuration and commissioning
Support of 3G Support configuration for 3G entities
Support 3G measurement
Licenses Control Application flag
Table 17 EMS function
1.8 Iu UP Gateway Function
Capacity Up to 1023 entries
Interface RTP to IP GSM EDGE Radio Access Network (GERAN)
RTP to 2G MGW
RTP to IP VMS and AAS/SRF
Iu UP to IP Universal Terrestrial Radio Access Network (UTRAN)
MEGACO (H.248) Mc to MSC
Featured Services 3G Iu UP to 2G RTP conversion
Table 19Iu UP Gateway function

2 Function Specifications
2.1 LITECORE 3G Core Network Architecture
The IPLOOK LITECORE 3G core network covers the network management entities, the service control
points, the service switching points, the mediate peripherals and the 3G gateways. It includes the following
entities: MSC/VLR, GMSC, AuC, HLR, Iu UP MGW, SMSC, PPS, IP VMS, AAS/SRF, and EMS. The 2G
gateways, the internet gateways and the radio access networks are not covered by the core network.
LITECORE 3G System core network architecture follows the dual system design of the LITECORE 2G
System. The service control point entities, the HLR/AuC, the SMSC, the PPS, and the service switching
point entities, the MSC/VLR, the GMSC, are in dual-system-load-sharing structure; while the network
management entities, the EMS and PM, are in master-slave structure. The media peripherals and gateway
entities, the AAS/SRF, the VMS and the Iu UP gateway are in dual-homing structure.
The IPLOOK LITECORE R9.2 3G system is based on LITECORE R9.1 2G system, and reuse all the 2G
LITECORE entities, including the MSC/VLR, HLR/AuC, SMSC, PPS, AAS/SRF, IP VMS, and EMS. New
3G functions and 3G interfaces are added to the MSC/VLR, HLR/AuC and EMS to support the 3G WCDMA
network. The new Iu UP Gateway entity is added to provide the 3G Iu UP to 2G RTP conversion, so that the
old 2G media peripherals and gateways can be used to support the 3G UTRAN.
2.2 Interfaces
As the core entity of the core network in UMTS, MSC is a functional entity that implements mobile call
service, mobility management, handover, and other supplementary services. MSC provides Nc interface to
connect with its gateway MSC, Mc interface with MGW, C/D interface with HLR, A interface with 2G Base
Station Controller (BSC), and the optional Gs interface with SGSN.
A MGW in UMTS implements bearer processing functions between different networks. MGW provides
Iu-CS interface to connect with Radio Network Controller (RNC) in Radio Access Network (RAN), Nb
interface with its peer MGW, Mc interface with MSC Server, A interface with BSC, and Ai interface with
PSTN.

SGSN is responsible for the delivery of data packets from and to MSs within its serving area. Its interfaces
include Iu-PS interface connecting to RNC, Gn/Gp interface to GGSN, Gr interface to HLR, Gs interface to
MSC, Gd interface to Short Message Center (SMCS), and Ga interface to Charging Gateway.
2.2.1 A Interface to BSC
Descriptions
The GSM A interface is the interface between the Base Station Subsystem (BSS) and the Mobile Switching
Center (MSC). The MSC A interface handles the basic connectionless and connection oriented layer 2
protocol.
Principle Benefits
The interface has been designed to follow as closely as possible GSM reference models.
Reference
 GSM 04.07 Mobile radio interface signaling layer 3
 GSM 04.08 Mobile radio interface layer 3 specification
 GSM 08.08 Mobile Switching Centre to Base Station System interface layer 3 specification
2.2.2 SS7 Networks
Descriptions
Signaling System Number 7 (SS7) is a sophisticated, integrated signaling protocol designed to increase the
efficiency of telephone service delivery. It has become the central nervous system for the delivery of
wireline and wireless, and more recently IP services, the latest step in the convergence of communication
networks. All networks need signaling to create connections, activate service, and deliver traffic.
LITECORE MSC supports SS7 basic functions such as MTP, SCCP, TCAP, ISUP, GSM MAP, CAP, BSSAP
and RANAP. To offer the best foundation for future applications and deployments, LITECORE R9 is
focused on SS7 over IP by supporting IETF SIGTRAN protocols including M2UA and SCTP.
Principle Benefits
 Faster call set up

 More efficient use of network resources
 A tested and reliable signaling protocol with global acceptance
 Support for network convergence
 Support for large, high-density, high-reliability systems
 Scalable architecture
 More cost-effective than Integrated Services Digital Network(ISDN) and Channel Associated Signaling
(CAS)
 Support RANAP for 3G
Reference
 ITU-T Q.704 Signaling network functions and messages
 ITU-T Q.705 Signaling network structure
2.2.3 ISUP
Descriptions
ISDN User Part (ISUP) is the call control part of the SS7 protocol which provides the signaling functions
required to support basic bearer services and supplementary services for voice and non-voice applications
in an SS7 network. The ISUP determines the procedures for setting up, coordinating, and taking down
trunk calls on the SS7 network. This feature provides a standard PSTN and/or PLMN interconnection with
ISUP over a media gateway transport.
Principle Benefits
ISUP is a standard SS7 based PSTN protocol widely used in the international markets. The ISUP protocol
support on LITECORE MSC allows us to interconnect with the PSTN switch over this standard interface.
The key benefits of ISUP can be summarized as follows:
 ISUP is very efficient compared with R2/R1 type of in-band signaling protocols. It greatly shortens
setup/connection time for calls, and it allows sophisticated signaling options and end user services.
 ISUP allows tighter integration with various existing MAP/SS7 signaling over E1 interface which is not
easily done with other protocols (in which case more than one E1 trunk may be required compared with
one E1 using ISUP).
 A generic ISUP is the basis for any country variant which may be required in any specific ISUP
deployment. The LITECORE MSC currently supports ITU-T ISUP, ETSI ISUP, and ANSI ISUP.

Reference
 ITU-T Q.761 Functional description of the ISDN user part of Signaling System No. 7
 ITU-T Q.762 General function of messages and signals of ISDN User Part of Signaling System No.7
 ITU-T Q.763 Formats and codes of the ISDN User Part of Signaling System No. 7
 ITU-T Q.764 ISDN user part signaling procedures
 ETSI EN 300 356-1 ISDN User Part (ISUP): Basic Services
 ETSI EN 300 356-2 ISDN User Part (ISUP): ISDN supplementary services
 ND1007:2006/4 ISDN User Part
2.2.4 Stream Control Transmission Protocol (SCTP)
Descriptions
The drive to exploit the values of the Internet protocol (IP) suite in the traditional telecom network spawned
the creation of the SIGTRAN workgroup within the Internet Engineering Task Force (IETF). The IETF is the
body responsible for developing the open specifications that define the Internet suite of applications and
protocols. SIGTRAN found its IETF home in the Transport Area sub-working group. The creators of
specification realized and accepted the unique needs of telephony signaling and understood that a new
protocol was required to meet the demands of determinism, reliability and timeliness that were a key
characteristic of the SS7 signaling network.
LITECORE SCTP is a Linux based streams implementation, existing within the operating system kernel.
Because it is within the OS, it does not suffer from context switching overhead that occurs with software
executing in the user space. This provides high capacity throughput and robust implementation.
LITECOREportability ensures that applications can easily be migrated across operating environments
within the LITECORE family.
Principle Benefits
 Delivery of data chunks within independent streams
 Support of multiple IP addresses
 Path selection and continuity monitoring
 Flood attack prevention
 Multi-homed endpoint support
 Reliable, connection oriented
 Message unit based

 User data message delivery within independent streams
 Security mechanisms
Reference
 RFC 2960 Stream Control Transmission Protocol (SCTP)
 RFC 3286 Introduction to the Stream Control Transmission Protocol (SCTP)
2.2.5 MTP 2 User Adaptation (M2UA)
Descriptions
The SIGTRAN Working Group of the IETF has specified the MTP2 User Adaptation Layer as its standard
protocol to enable remote termination of SS7 links via an SCTP association. The M2UA protocol is the layer
between SCTP and MTP3 that separates the physical SS7 termination from the actual signaling point
within the network. M2UA serves several purposes. The first purpose is to provide a mechanism for the
transport of SS7 MTP2 user signaling (e.g., MTP3 messages) over IP using SCTP. The second purpose is
to allow remote placement of SS7 link terminations and back haul SS7 traffic to a centralized point in the
network.
With M2UA several signaling points can be consolidated into a centralized network element. In turn, one
can then co-locate points of SS7 presence closer to the element to which they need to connect. This results
in a substantial cost savings in terms of backhauling SS7 dedicated circuits. M2UA deployments consist of
2 entities, the client and the server. The server provides physical SS7 termination and communicates with
the client over an SCTP association using IP. The client houses the MTP3 and thus is the point code
addressable element within the SS7 network. It is also appropriate for consolidating point code usage and
simplifying SS7 network provisioning overhead.
M2UA allows LITECORE to optimize the network topology and use IP to transport SS7 messages instead
of traditional 64K-based links. All remaining elements from the classic SS7 network remain the same. From
the outside, the fact that signaling is carried over IP is not detectable.
Principle Benefits
 Remotely locates SS7 terminations from point of interconnection
 Enables network architecture with minimal point codes
 Reduces SS7 transport, overhead, collocation and maintenance costs
 Separates and centralizes service signaling components from transport

 Reduces network routing complexity
 Deploys remote points of presence in interconnecting networks
 Easily expands network reach
 Increases operational flexibility and scalability
Reference
 RFC 3331 SS7 MTP2 User Adaptation Layer
2.2.6 MTP 3 User Adaptation (M3UA)
Descriptions
M3UA supports the transport of any SS7 MTP3-User signaling (such as ISUP and SCCP messages) over
IP, using the services of the Stream Control Transmission Protocol (SCTP). The protocol is used for
communication between a Signaling Gateway (SG) and a Media Gateway Controller (MGC) or IP-resident
database. It is assumed that the SG receives SS7 signaling over a standard SS7 interface using the SS7
Message Transfer Part (MTP) to provide transport.
Principle Benefits
 Replaces physical SS7 links with virtual IP transport associations
 Maintain deterministic real time qualities demanded in signaling applications
 Eliminates SS7 bandwidth limitations incurred by 64Kbps restrictions
 Eliminates traditional SS7 provisioning complexity
 Deploy existing SS7 call setup & value added service with minimal legacy overhead
 Deployable in point-to-point or gateway intermediary configuration
Reference
 RFC 3332 SS7 MTP2 User Adaptation Layer
2.2.7 Session Initiation Protocol (SIP)
Descriptions
The Session Initiation Protocol (SIP) is an application-layer control protocol that can establish, modify, and

terminate multimedia sessions with one or more participants. These sessions include Internet telephone
calls, multimedia distribution, and multimedia conferences.
SIP invitations used to create sessions carry session descriptions that allow participants to agree on a set
of compatible media types. SIP makes use of elements called proxy servers to help route requests to the
user's current location, authenticate and authorize users for services, implement provider call-routing
policies, and provide features to users. SIP also provides a registration function that allows users to upload
their current locations for use by proxy servers. SIP runs on top of several different IP transport protocols
including UDP, SCTP, and TCP.
LITECORE MSC adds SIP User Agent (UA) functionality into R9.1.5 system to support the following
applications:
 IP lawful interception
 Three-way calling
Principle Benefits
The main advantages of SIP are its extensibility and flexibility for adding new features.
The SIP client-server and header format design is based on proven Internet standards such as Hyper Text
Transfer Protocol (used on commercial web servers) and Simple Mail Transfer Protocol (used for internet
email services). The client-server design means that each SIP request will result in a well-defined set of SIP
responses. This modular design makes it easy to extend SIP to support new operations by simply adding a
new request (or SIP Method) and its corresponding response message. Because SIP is text-based, it is
easy to parse the various SIP commands.
Reference
 RFC 3261 SIP: Session Initiation Protocol
2.2.8 Radio Access Network Application Part (RANAP) Protocol
Descriptions
The Radio Access Network Application Part (RANAP) protocol is used in UMTS signaling between the
Core Network, which can be a MSC or SGSN, and the UTRAN. RANAP is carried over
Iu-interface.
RANAP signaling protocol resides in the control plane of Radio network layer of Iu interface in the UMTS
(Universal Mobile Telecommunication System) protocol stack. The Iu interface is the interface between

RNC (Radio Network Controller) and CN (Core Network).
The LITECORE 3G RANAP protocol has the following functions:
 Relocating serving RNC.
 Overall RAB management.
 Queuing the setup of RAB.
 Requesting RAB release.
 Release of all Iu connection resources.
 Requesting the release of all Iu connection resources.
 SRNS context forwarding function.
 Controlling overload in the Iu interface.
 Resetting the Iu.
 Sending the UE Common ID (permanent NAS UE identity) to the RNC.
 Paging the user.
 Controlling the tracing of the UE activity.
 Transport of NAS information between UE and CN.
 Controlling the security mode in the UTRAN.
 Controlling location reporting.
 Location reporting.
 Data volume reporting function.
 Reporting general error situations.
 Location related data
Principle Benefits
It enables LITECORE 3G core network to support Iu-CS related services.
Reference
 3GPP 25.413 V4.12.0 Release 4: UTRAN Iu interface Radio Access Network Application Part (RANAP)
signaling
2.2.9 Iu Interface
Descriptions
This interface connects the core network and the UMTS Radio Access Network (URAN). The Iu can have

two different physical instances: Iu-CS and Iu-PS. The Iu-CS connects the radio access network to a
circuit-switched core network, that is, to an MSC. The Iu-PS connects the access network to a
packet-switched core network, which in practice means a connection to an SGSN.
The Iu-CS interface locates between MGW and RNC to establish the voice channel and transport the
Radio Access Network Application Part (RANAP) signaling message. In CS voice user plane, Iu Interface
User Plane Protocol (Iu-UP) stands on the top layer.
The Iu-PS is the interface between the RNC and the Packet Switched Core Network. The interface carries
user traffic as well as control information.
Principle Benefits
It enables LITECORE 3G core network to support Iu-CS related services.
Reference
 3GPP TS 25.414 version 10.1.0 Release 10: UTRAN Iu interface data transport and transport signaling
2.2.10 Iu User Plane (Iu-UP) Protocol
Descriptions
The Iu UP (Iu User Plane) protocol is located in the user plane of the Radio Network layer over the Iu
interface; the Iu UP protocol layer. Standard Iu UP interfaces with RTP/GTP-u/AAL2 layers at its lower
interface and interfaces with a customer provided application at the upper interface. Iu-UP is used to
convey user data associated to Radio Access Bearers. The first release of the Iu UP 2.0 will only support
the RTP lower layer.
The Iu UP protocol can operate in two modes:
 Transparent mode;
 Support mode.
The particular mode is decided by the CN when this protocol task is created. It cannot be modified later
unless the associated radio access bearer is modified at the same time.
The transparent mode is, as the name indicates, transparent. In this mode the only function of this task is to
transfer user data across the Iu interface. No special Iu UP frames will be generated for this transfer, but
lower layer PDUs can be used instead.
LITECORE MSC adds Iu UP protocol into R9.2 system to support the following functions:
 Transfer of user data;
 Initialization;

 Rate control;
 Time alignment;
 Handling of error events;
 Frame-quality classification.
Principle Benefits
It enables LITECORE 3G core network to support 3G voice service and make 3G-2G users can
communication.
Reference
 3GPP TS 25.415 V10.1.0 Release 10: UTRAN Iu interface user plane protocols
2.2.11 Media Gateway Control Protocol (Megaco)
Descriptions
Megaco (officially H.248) is a gateway control protocol and an implementation of the Media Gateway
Control Protocol architecture for controlling media gateways in Internet Protocol (IP) networks and
the Public Switched Telephone Network (PSTN). It is for the control of elements of a physically
decomposed multimedia gateway, which enables separation of call control from media conversion. Though
H.248 performs the same functions as MGCP, it uses different commands and processes and supports a
broader range of networks.
H.248 protocol module provides an API interface for the user to add, modify or subtract terminations, to
request report event or play signal, and so on. H.248 protocol module uses the IPTRANS API interface to
send or receive H.248 PDU over UDP/IP. It will also support H.248 PDU over SCTP/IP in phase II.
Principle Benefits
It enables LITECORE 3G system to control 3G media gateway.
Reference
 RFC 3525: Gateway Control Protocol
 ITU H.248: Gateway Control Protocol

2.3 Voice Services
2.3.1 Telephony - Full Rate Speech
Key Capabilities
Telephony service (TS11) allows GSM subscribers to set up and receive calls to and from other GSM
subscribers, plus those in other mobile and fixed networks and engage in speech communications.
Principle Benefits
This provides the basic speech communications according to GSM specifications.
Reference
2.3.2 Emergency Calls
Key Capabilities
Emergency service (TS12) allows the mobile stations to male calls which are automatically routed to an
appropriate regional emergency service center based on the geographical location of the mobile subscriber
(e.g. based on the identity of the cell on which the call has been established).
An emergency call may be made by the subscriber:
 Dialing 112 which causes the mobile station to initiates an Emergency Setup procedure (type 1 call).
 Dialing a national emergency number which initiates a regular Setup procedure which the MSC
recognizes as an emergency call via Datafill (type 2 call).
Principle Benefits
This enables emergency calls to be processed according to common regulatory directives.
Reference
 GSM 02.03 Teleservices supported by a GSM Public Land Mobile Network (PLMN)

2.3.3 Emergency Calls Enhancements
Key Capabilities
Type 1 emergency calls (those invoked via the GSM defined Emergency Setup procedure) are enhanced
by:
 Allowing the LITECORE MSC to optionally check the mobile stations service registration before
accepting and routing the call to the emergency center.
 Providing the flexibility to determine if type 1 emergency calls should be service validated,
authenticated, ciphered or IMEI checked.
 Supporting SS7 signaling to transfer location and calling number information to the emergency center.
Principle Benefits
This provides the network operator with greater compliance to national regulatory directives.
Reference
 GSM 02.03 Teleservices supported by a GSM Public Land Mobile Network (PLMN)
2.3.4 DTMF
Key Capabilities
This feature allows a GSM subscriber to send Dual Tone Multi Frequency (DTMF) digits to the other party
during a call. Dual to potential incompatibilities with the voice encoding, GSM has specified that DTMF
digits input by the subscriber are sent by the GSM mobile station as signaling messages which are then
decoded by the MSC and passed as tones through the network. Tones sent towards the mobile station are
not encoded and are received by the mobile stations as inband tones.
Principle Benefits
The DTMF feature allows the mobile subscriber to interface to non-human devices in the same way e.g.
voice mail systems.
Reference

2.3.5 Multiple Vocoders
Key Capabilities
This feature enables the LITECORE MSC to allow mobile stations to request allocation of Vocoders and
Channel Rates in addition to that defined originally by GSM.
At mobile originating or terminating call setup the mobile station indicates its preferred Vocoders and
Channel Rates to the MSC which relays it to the BSS, which then selects and allocates the appropriate
speech coder and channel rate and informs the MSC the resultant choice.
Principle Benefits
This enables the network to support new and improved voice encoding and transmission capabilities other
than the original GSM version.
Dependencies
Mobile stations need to support enhanced full rate (EFR) coding and related signaling.
Reference
2.3.6 Payload Type Selection
Key Capabilities
Payload types define the content and format of Real-Time Transport Protocol (RTP) packets and the
resulting stream of data generated by the RTP flow. The payload type defines the codec in use and is
identified in the payload type field of the header of each RTP packet. There are two mechanisms for
specifying payload type, static and dynamic.
Static payload types are assigned to specific RTP formats by RFC 1890 and these mappings are registered
with the Internet Assigned Numbers Authority (IANA).
Unlike static payload types, Dynamic payload types are not assigned in the IANA. They map a RTP
payload type to an encoding for the duration of a session. Different members of a session could, but
typically do not, use different mappings. Dynamic payload types use the range 96 to 127. They are

assigned by means outside of the protocol specification.
Principle Benefits
 Expanded dynamic payload support on LITECORE MSC, resulting in enhanced bandwidth control
 Expanded interoperability and interconnectivity between gateways, applications, and services in the
network
2.4 Supplementary Services
2.4.1 Call Forwarding
Key Capabilities
Call Forwarding allows mobile subscribers to forward mobile terminated calls to a new destination. The call
forwarding service is divided into four different individual supplementary services:
 Call Forwarding Unconditional
 Call Forwarding on mobile subscriber Busy
 Call Forwarding on No Reply
 Call Forwarding on mobile subscriber Not Reachable
The mobile subscriber can control (register, erase, change) the forwarding service, from his mobile station,
and also interrogate its status and any forwarded number.
Call Forwarding can also be controlled by the network operator via the EMS interface to the HLR.
Principle Benefits
Call Forwarding increases the number of calls that complete successfully, and therefore increases user
satisfaction and network utilization. Call Forwarding is also the mechanism used to route calls to voice mail.
Reference
 GSM 02.82 Call Forwarding (CF) Supplementary Services
2.4.2 Call Forwarding Unconditional
Key Capabilities

This service permits a called mobile subscriber to send all incoming calls to the forwarding number. The
mobile subscriber can still make outgoing calls.
The subscriber can register, interrogate and erase the service from the mobile station. The service can also
be controlled by the network operator via the EMS interface to the HLR.
Principle Benefits
Like all types of Call Forwarding, CFU is useful to increase the probability that an incoming call actually
gets answered. This is especially useful when the mobile subscriber does not want to receive any phone
calls or knows for sure that he will not be able to answer them.
Reference
2.4.3 Call Forwarding on Mobile Subscriber Busy
Key Capabilities
This service permits a called mobile subscriber to send all incoming calls to the forwarding number when
the mobile subscriber busy condition is encountered. The mobile subscriber can still make outgoing calls.
Principle Benefits
Like all types of Call Forwarding, CFB is useful for increasing the chances that an incoming call actually
gets answered. This type is especially useful when the mobile subscriber is already engaged in a call. The
forwarded-to number could be a voice mail system or another directory number.
Reference
2.4.4 Call Forwarding on Mobile Subscriber Not Reachable
Key Capabilities

the called mobile subscriber is not reachable. The mobile subscriber can still make outgoing calls in
principal, but may be affected if the mobile subscriber is de-registered, if there is radio congestion or if the
mobile subscriber is out of radio coverage.
The Call Forwarding Not Reachable service forwards incoming calls to a specified destination address
under one of the following conditions:
 Not registered: the call is forwarded if the Call Forwarding mobile subscriber has performed an IMSI
detach.
 Radio congestion: the call is forwarded if the radio channels associated with the current location area of
the Call Forwarding mobile subscriber is unavailable.
 No page response: the call is forwarded when the Call Forwarding mobile subscriber cannot be located
within the MSC coverage area.
Principle Benefits
Like all types of Call Forwarding, CFNRc is useful for increasing the probability that an incoming call
actually gets answered. This type is especially useful when the mobile subscriber has decided not to
receive any calls and turned off his mobile station. The forwarded-to number could be a voice mail system
or another directory number.
Reference
2.4.5 Call Forwarding on No Reply
Key Capabilities
the no reply condition is encountered. The mobile subscriber can still make outgoing calls.
The subscriber can register, interrogate and erase the service from the mobile station. The mobile
subscriber also has the ability to change the period of time that his mobile station rings before forwarding
the call. The service can also be controlled by the network operator via the EMS interface to the HLR.

Principle Benefits
Like all types of Call Forwarding, CFNRy is useful for increasing the probability that an incoming call
actually gets answered. This is especially useful when the mobile subscriber thinks he may not be able to
answer his incoming calls but still wants to have a chance to answer them.
Reference
2.4.6 Call Forwarding on Mobile Subscriber Unavailable
Key Capabilities
This service allows the mobile subscriber to register or erase the following Call Forwarding supplementary
services by one action.
 Call Forwarding on mobile subscriber Busy
 Call Forwarding on No Reply
 Call Forwarding on mobile subscriber Not Reachable
Principle Benefits
Like all types of Call Forwarding, Call Forwarding on Mobile Subscriber Unavailable is useful for increasing
the probability that an incoming call actually gets answered. This is especially useful when the mobile
subscriber is unavailable due to busy, no reply or not reachable.
Dependencies
Mobile stations need to support this feature and related signaling.
Reference
2.4.7 Call Forwarding - Cancel All
Key Capabilities

This service allows the mobile subscriber to erase all Call Forwarding supplementary services by one
action.
Dependencies
Mobile stations need to support this feature and related signaling.
Reference
2.4.8 Notification of Call Forwarding
Key Capabilities
This feature enables Call Forwarding Notifications to be passed in the following cases:
To the mobile subscriber, (via DTAP signaling messages) when:
 An incoming call is forwarded on MS busy and the subscriber has the subscription option.
 An incoming call is forwarded on no replay and the subscriber has the subscription option.
 A mobile subscriber with CF feature active makes an outgoing call.
To the calling subscriber, (via ISUP signaling messages) when:
 A call is being forwarded and the mobile subscriber has the subscription option.
To the forwarded to subscriber, (via ISUP signaling messages) when:
 A call has been forwarded.
Principle Benefits
This feature keeps all parties informed of the status of the call, which improves user perception and
satisfaction.
Reference
2.4.9 Call Hold

Key Capabilities
The Call Hold feature gives the mobile subscriber the capability of placing an active call on hold and to
subsequently retrieve the call on hold.
If the mobile subscriber has one call on hold, she can set up another call and switch between the two, or
disconnect either party.
LITECORE also provides the capability to play to the party who has been put on hold by a MS either a tone
or a recorded announcement for the duration of the call hold.
Principle Benefits
Provides the capability to make more than one call at once, plus it is the basis for setting up other services,
such as multi-party calling.
Reference
 GSM 02.83 Call Waiting and Call Holding Supplementary Services
2.4.10 Call Waiting
Key Capabilities
Call Waiting allows a mobile subscriber who is already engaged in call to receive notification of another
incoming call. As defined by the GSM standards, upon receiving the call waiting notification, the mobile
subscriber can:
 Disconnect the active call and answer the waiting call.
 Put the active call on hold and answer the waiting call.
 Ignore the waiting call.
 Reject the waiting call.
Subscribers to Call Waiting can activate and deactivate the service from their mobile station.
Call Waiting can also be activated and deactivated by the network operator.
While the call is waiting, and before the mobile subscriber has taken an action on it, it appears to the calling
party as unanswered.
Principle Benefits

Call Waiting improves connectivity, by enabling the mobile subscriber to be informed of all calls, even when
engaged in one.
The ability to deactivate Call Waiting allows the mobile subscriber to make an important call and not be
disturbed (by the call waiting tone).
Reference
 GSM 02.83 Call Waiting and Call Holding Supplementary Services
2.4.11 Call Barring
Key Capabilities
The Call Barring services allow mobile subscribers to decide the categories of calls that may or may not be
made to and from their mobile station.
Several types of call restriction are available:
 Barring of all outgoing calls
 Barring of outgoing international calls
 Barring of international calls except those directed to the home PLMN country
 Barring of all incoming calls
 Barring of incoming calls when roaming outside the home PLMN country
The user can activate/deactivate under the protection of password control, the Call Barring services from
the mobile station. The network operator can also use Call Barring to restrict service (note that this
capability is also available via the Operator Determined Barring services).
Flexible treatment ensures that a mobile user making a call from which he is barred can be routed to an
announcement (“feature not available to caller”).
Reference
 GSM 02.88 Call Barring (CB) Supplementary Services
2.4.12 Barring of All Outgoing Calls
Key Capabilities

This service makes it possible for a mobile subscriber to restrict any outgoing calls. Activation of BAOC
prohibits the mobile subscriber from making outgoing calls with the exception if emergency calls.
Activation and deactivation of BAOC is accomplished under the password protection provided with the
operation.
Principle Benefits
The mobile station owner may loan the mobile station to another person and restrict use of the mobile
station to making going calls.
Reference
2.4.13 Barring of Outgoing International Calls
Key Capabilities
This service restricts the mobile subscriber from making any international calls. Outgoing calls are allowed
to subscribers (PLMNs and PSTNs) in the country where the mobile subscriber is presently located.
Activation and deactivation of BOIC is accomplished under the password protection provided with the
operation.
Principle Benefits
The feature allows a mobile subscriber to restrict international calls originating from the mobile station.
Reference
2.4.14 BOIC Except Directed to Home PLMN Country
Key Capabilities
This service restricts the mobile subscriber from making any international calls except calls directed to the
home country. Outgoing calls are allowed to subscribers (PLMNs and PSTNs) in the country where the

mobile subscriber is presently located as well as to the home country.
Activation and deactivated of BOIC-exHC is accomplished under the password protection provided with the
operation.
Principle Benefits
The feature provides restrictions to allowable international calls, primarily when roaming.
Reference
2.4.15 Barring of All Incoming Calls
Key Capabilities
This service allows the mobile subscriber to restrict any incoming calls. Activation of BOIC prohibits any call
terminations to the mobile subscriber.
Activation and deactivation of BAIC is accomplished under the password protection provided with the
operation.
Principle Benefits
Occasionally, the mobile subscriber may not want any disturbance, without forwarding the call, and
therefore activates the BAIC service.
Reference
2.4.16 BIC When Roaming Outside 0f Home PLMN Country
Key Capabilities
This service allows the mobile subscriber to receive calls only while in the home PLMN country. When the
mobile subscriber roams outside the home PLMN country, incoming calls are not allowed.
Activation and deactivated of BIC-Roam is accomplished under the password protection provided with the

operation.
Principle Benefits
In accordance with the international roaming agreements set up by GSM operators, mobile subscribers pay
for the international part of the call from their HPLMN country to the country where they are located, when
roaming outside their HPLMN country, when they receive a call.
Subscribers can use this service to restrict incoming calls when roaming, to avoid incurring charges for
those international calls.
Reference
2.4.17 Password Control
Key Capabilities
This service offers the ability of the system to handle transactions requiring the use of a password. The
instances when this feature is used are:
 Registering a new password
 Activating and deactivating a supplementary service which is password controlled
Currently, password control is only used with call barring services.
Principle Benefits
Provides protection to user controlled barring services to prevent unauthorized activation or deactivation.
Reference
GSM 04.10 Mobile Radio Interface Layer 3 Supplementary Services Specification
2.4.18 Operator Determined Barring
Key Capabilities
Operator Determined Barring (ODB) is a network feature allowing a network operator to regulate

subscribers’ access to GSM services, by barring certain categories of incoming or outgoing traffic or of
roaming. Operator Determined Barring always applies to all basis services simultaneously, but is not
applicable to emergency calls. Only the Home PLMN operator can activate, change, or deactivate the
application of this ODB network feature.
ODB can have several types and there are variants within each of the ODB types. The variants of each
ODB type are described in the following sections.
The rules for applying ODB, as defined by GSM are:
 ODB - outgoing calls
 ODB - incoming calls
 ODB - roaming outside HPLMN/HPLMN country
 ODB - premium rate calls (information/entertainment)
 ODB - supplementary services
Reference
 GSM 02.41 Operator Determined Barring (ODB)
2.4.19 ODB - Outgoing Calls
Key Capabilities
Operator Determined Barring of outgoing calls includes:
 Barring outgoing calls (BAOC)
 Barring outgoing international calls (BOIC)
 Barring outgoing international calls except those directed to the Home PLMN country
Refer to the “Call Restriction Supplementary Services” section of this document for more details on
invocation of each type of outgoing barring service.
Principle Benefits
Provides the similar level of support as the call barring supplementary service, which is controllable by the
user.
Reference

2.4.20 ODB - Incoming Calls
Key Capabilities
Operator Determined Barring of incoming calls includes:
 Barring of all incoming calls which prevents the mobile subscriber from receiving any incoming call
 Barring of all incoming calls when roaming outside the HPLMN country, which bars the mobile
subscriber from receiving incoming calls only when the mobile subscriber roams the HPLMN country
Refer to the “Call Restriction Supplementary Services” section of this document for more details on
invocation of each type of incoming barring service.
Principle Benefits
Provides the similar level of support as the call barring supplementary service, which is controllable by the
user.
Reference
2.4.21 ODB - Roaming Outside HPLMN/HPLMN Country
Key Capabilities
Operator Determined Barring of roaming includes:
 Barring of roaming outside the Home PLMN
 Barring of roaming outside the Home PLMN country
Principle Benefits
The operator can offer different levels of roaming service:
 Within the network only (no roaming allowed)
 Within the country only
 Full roaming anywhere
Reference

2.4.22 ODB - Premium Rate Calls (Information/Entertainment)
Key Capabilities
Operator Determined Barring of outgoing premium rate calls includes:
 Barring of outgoing premium rate calls (information)
 Barring of outgoing premium rate calls (entertainment)
This service bars mobile subscribers from calling directory numbers that are classified as premium rate. A
mobile subscriber may have one or both of the above variants activated at any given time.
Principle Benefits
This allows the operator to control the calling ability of the subscriber for marketing purposes or budget
limitation purposes. It may also be used by end users who never wish to use the services being barred.
Reference
2.4.23 ODB - Supplementary Service
Key Capabilities
This feature allows barring of supplementary service management, with prevents user control of any
supplementary service. However, this does not prevent invocation of the supplementary services, e.g. an
existing call forwarding or barring state will remain unaffected.
Principle Benefits
This allows the operator to market subscriber control of supplementary services as an additional feature.
This may also be used in the case of a rental company where a voice mail box is provided but no charge for
the call forwarding data is made.
Reference

2.4.24 Operator Specific Barring (OSB)
Key Capabilities
The Operator Specific Barring (OSB) feature allows an operator or service provider to bar subscriber within
his home PLMN from making an outgoing call with certain destination prefix. There can be multiple
destination prefixes to be barred and they are configurable. There are two different profiles allowed to be
set. Each profile contains a different set of number prefixes subject to barring. Operator can then assign
different profiles to different subscribers according to the services they have subscribed.
Principle Benefits
This feature provides operators a truly flexible call barring tool for a variety of destinations to be restricted.
Since the restriction is dialing prefix based, this feature gives the operator full flexibility to bar some
subscribers from calling any call destinations; no matter it is local or domestic or international. This is in
addition to the already implemented standard international call barring and the Operator Determined Call
Barring features. The operators may want to enable the barring for those who have difficulty paying the bills
while putting not barring for their premium subscribers.
Reference
 GSM 03.15 Technical Realization of Operator Determined Barring (ODB)
 GSM 09.02 Mobile Application Part (MAP) specification
2.4.25 Calling Line Identification Presentation
Key Capabilities
Calling Line Identification Presentation (CLIP) provides the mobile subscriber with information about the
calling party when receiving a call. This information is available to the mobile subscriber at call set-up time.
Information is also provided id the mobile subscriber is already engaged in a call, and is notified of a new
incoming call.
Principle Benefits

The presentation of the calling party information allows the mobile subscriber to decide whether and how to
answer the call.
Reference
 GSM 02.81 Line Identification Supplementary Services
2.4.26 Calling Line Identification Restriction
Key Capabilities
Calling Line Identification Restriction (CLIR) provides the mobile subscriber with the ability to block the
presentation of the calling line identification to the connected party:
 For all calls unconditionally (Permanent CLIR)
 On a per call basis, at call set up (Temporary CLIR)
With Temporary CLIR, the mobile subscriber may also select (as subscription option) whether his
identification should be, by default, presented or restricted to the connected party. The mobile subscriber
can then override the default on a per call basis when specified appropriately during call set-up.
The CLIR service has priority over the CLIP service.
Principle Benefits
Permanent CLIR allows the mobile subscriber to restrict the presentation of their identification. Temporary
CLIR allows a mobile subscriber to routinely restrict/present the presentation of his identification, yet still
have the ability to provide/restrict his identification on a per call basis.
Dependencies
Mobile stations need to support the ability to indicate CLIR is required using the GSM Phase 2 defined
procedures at call setup if temporary CLIR is required.
2.4.27 Connected Line Identification Presentation
Key Capabilities

Connected Line Identification Presentation (COLP) provides the mobile subscriber with the possibility of
receiving the line identity of the connected party.
The network delivers the connected line identity to the calling party regardless of the terminal capability to
handle the information. The information is only delivered once the call has been answered.
Principle Benefits
Knowing the connected line identification is particularly useful if the call is forwarded, in order to know the
call’s eventual destination.
Reference
2.4.28 Connected Line Identification Restriction
Key Capabilities
Connected Line Identification Restriction (COLR) service enables the mobile subscriber to prevent
presentation of the line identity to the calling party.
Principle Benefits
Connected line identification restriction can be useful; if the original called party has forwarded all calls and
does not wish the calling party to know they have been routed to a different number.
Reference
2.4.29 Unstructured Supplementary Service Data
Key Capabilities
USSD provides a mechanism that allows a GSM user and a GSM network to communicate in a way which
is transparent to the Mobile Station. This means that the MS does not require knowledge of the services
which may be initiated by the user or the network via USSD.

In operation, USSD is used to send text between the user and some application. USSD should be thought
of as a trigger rather than an application itself. However, it enables other applications such as prepaid. It is
not possible to bill for USSD directly, but instead bill for the application associated with the use of USSD
such as SMS or prepaid.
Principle Benefits
Unstructured Supplementary Service Data allows the operator to offer new services without the subscriber
having to buy a mobile upgrade to support them.
Dependencies
Mobile stations need to support Phase 1 or Phase 2 USSD signaling.
Reference
 GSM 02.90 Unstructured Supplementary Service Data (USSD) - Stage 1
2.4.30 Explicit Call Transfer
Key Capabilities
Explicit Call Transfer allows a GSM subscriber to connect two people he is involved in calls with together
while simultaneously removing himself completely from the call. The other two parties may be fixed or
mobile subscribers. The call transfer can take place after the third party has answered the call or while it is
in the alerting stage.
Principle Benefits
Explicit Call Transfer allows GSM operator to offer a similar service to that used in fixed networks and office
environments.
Dependencies
Mobile stations need to support Phase 2 defined ECT procedures.
Reference

 GSM 02.91 Explicit Call Transfer (ECT) Supplementary Service - Stage 1
2.4.31 enhanced Multi-Level Precedence and Preemption (eMLPP)
Key Capabilities
The enhanced Multi-Level Precedence and Preemption service provides the capability to classify the
mobile subscribers according to a subscriber specific priority. The feature has two parts, precedence and
preemption:
 Precedence means assigning a priority level to a point-to-point call.
 Preemption means the seizing of resources, such as radio channels, by high priority calls that are in
use by low priority calls, when the network offers no idle resources.
The eMLPP service specifies how to handle precedence levels for subscribers within a PLMN including the
possibility to preempt ongoing calls and how to handle the subscribers who are not subscribed to this
service. Furthermore, eMLPP defines setup classes. For each class the setup time and the preemption
capability are specified.
Reference
 GSM 02.67 enhanced Multi-Level Precedence and Preemption Service (eMLPP) - Stage 1

2.5 Short Message Services
2.5.1 Short Message Service Mobile Originated
Key Capabilities
This service (TS22) allows the mobile subscriber to send short messages to a Short Message Service
Center. These messages may be intended for a variety of destinations: other mobile users, subscribers of
other networks, computers, paging systems, etc.
The mobile subscriber can create, store and send short messages using the mobile station or another
device (e.g. PC, notepad, palmtop or laptop) connected to the mobile station.
Principle Benefits
The user can send a textual data message by SMS instead of making a circuit switched data call. As the
network does not need to allocate a traffic channel, the transaction uses less radio resources than a regular
call.
Dependencies
Mobile stations need to support SMS Mobile Originated procedures.
Reference
 GSM 03.40 Technical realization of the Short Message Service (SMS)
2.5.2 Short Message Service Mobile Terminated
Key Capabilities
This service (TS21) allows the Short Message Service Center to send short messages to the mobile station.
The messages may be input to the SMSC by other mobile users (via a mobile originated short message) or
by a variety of other resources.
Principle Benefits
A variety of applications exists for this service. Some of the most important ones are:
 Voice mail alerting: the network sends a short message to the mobile station indicating he has voice

mail.
 Information of prepaid account: a notification short message is sent indicating current account balance
and validity after inquiry.
Dependencies
Mobile stations need to support SMS Mobile Terminated procedures.
Reference
 GSM 03.40 Technical realization of the Short Message Service (SMS)
2.5.3 Short Message Broadcasting (ESME-SMB)
Key Capabilities
Mobile Network operators need a tool to send short messages to mass users; for example, virtual AD,
emergency message. GSM BSC has the ability to broadcast short message to users in its coverage but
need a tool to send short messages to all active users or target user groups. UW LITECORE External Short
Message Entity - Short Message Broadcasting (ESME-SMB) is a tool for the operator to send short
messages to the mass.
ESME-SMB connects to the SMSC (Short Message Service Center) and the MSC/VLR of the UW
LITECORE in SMPP (Short Message Peer to Peer) protocol and SNMP (Simple Network Management
Protocol) respectively. SMPP is for sending short messages to SMSC and SNMP is for collecting online
user information from the VLR.
Principle Benefits
 Broadcasting messages to mass users in a convenience way. Allow communicating to a large user
group in a short period of time.
 Explore more commercial opportunities on short messages business - advertising and promotion
messages.
 Easy to operate and to manage.

2.6 Enhanced Services
2.6.1 Voice Mail Service
Key Capabilities
The voice mail service is one of the value added services of LITECORE system. It provides voice mail to
the calling party when the called party is busy, no answer, not reachable or switched off. When a new voice
message reaches, the Voice Mail System (VMS) notifies the host by a short message. Subscribers can
receive and retrieve their messages and maintain their mailboxes (set greetings, language and password)
at any time from anywhere.
The VMS can be either deployed as part of the LITECORE system, or used as a standalone system. In
LITECORE system the VMS connects to the application servers via IP connection. It also functions along
with SMSC to provide message indications. Each VMS can also be configured to provide a multi-language
announcement service. A single high capacity VMS supports up to 100k subscribers.
Principle Benefits
The voice mail service allows the caller to leave a voicemail message if the called party is unavailable to
answer his call. The called party can:
 be alerted to his waiting voicemail message by a text message
 listen to his message by calling the "Voicemail Retrieval Number"
2.6.2 Mobile Number Portability - Database Query
Key Capabilities
Mobile Number Portability allows subscribers to switch service providers from the same provider and retain
the same directory number. This feature allows the consumer to move from the GSM service provider.
The feature supports the capability whereby the LITECORE MSC can query the Local Number Portability
database for calls to ported number and then route the call to the new destination.
Principle Benefits
The Mobile Number Portability database query feature will provide operators with the ability to obtain local
number portability information without depending on outside parties. By performing their own queries

operators will minimize the costs associated with local number portability compliance.
Reference
 GSM 02.66 Support of Mobile Number Portability
2.6.3 Mobile Number Portability - Ported Number Reception
Key Capabilities
Mobile Number Portability allows subscribers to switch service providers from the same provider and retain
the same directory number. This feature allows the consumer to move from the GSM service provider.
The feature supports the capability to accept ported numbers from other networks. The feature recognizes
calls for ported numbers, which have already been translated, and terminates the call within the GSM
operator’s network or forwards it if the supplementary service is activated.
Principle Benefits
Mobile Number Portability means that subscribers can switch network providers without changing their
number. This allows the network operator with the opportunity to attract new customers from other
networks.
Reference
 GSM 02.66 Support of Mobile Number Portability
2.6.4 SMS Email Gateway
Key Capabilities
The SMS Email Gateway is a software application that provides bi-directional SMS to email support,
allowing email messages to be sent to SMS recipients, and vice versa.
The SMEG relays short messages and internet email messages between the Short Message Center
(SMSC) and the host email server. It links to the host email server and short message center via SMTP and
SMPP respectively. SMEG routes email messages and short messages between them with appropriate
format conversion.

Principle Benefits
 Allows SMS users to send text messages to internet email recipients.
 Allows internet email senders to send emails (text messages) to UW SMS recipients (email address
format is phonenumber@domain).
Reference
 RFC 2821 Simple Mail Transfer Protocol
 TS 23.040 Technical realization of Short Message Service (SMS)
2.6.5 Lawful Interception
Key Capabilities
Lawful Interception (LI) is the legally approved surveillance of telecommunication services, and it has
become an important tool for law enforcement agencies (LEAs) around the world for investigating and
prosecuting criminal activities and terrorism. Most countries have passed laws that require
telecommunication service providers to support LEAs with duly authorized requests to identify, monitor, and
deliver all of the electronic communication of specified individuals and groups. While regulations and
requirements vary from country to country, international standardization bodies have developed technical
standards for LI that will facilitate the work of LEAs and help operators and service providers to minimize
their costs.
The main functions of any LI solution are to access Interception-Related Information (IRI) and Content of
Communication sessions (CC) from the telecommunications network and to deliver the information in a
standardized format via the handover interface to one or more monitoring centers of law enforcement
agencies. Of course, before surveillance can take place interception requests must be approved and
appropriately provisioned to the Interception Access Points within the service provider’s network, and they
must be carefully and accurately terminated after the interception authorization expires. In addition, high
security requirements for LI systems are important to prevent possible manipulation and misuse.
LITECORE system introduces a Lawful Interception Sub-System (LISS) to perform Lawful Interception
function upon the mobile targets’ communication contents and related information.
Principle Benefits
 Allows service providers to meet the requirements of the law;

 Provides ISUP or BICC connectivity option to the LEA;
 Leverages existing equipment resources;
 Operates independently of other network elements, providing flexibility to set up a complete
surveillance solution.
Reference
 ETSI TS 101 331 Telecommunications security; Lawful Interception (LI) Requirements of Law
Enforcement Agencies
 ETSI TR 101 943 Telecommunications security; Lawful Interception (LI); Concepts of Interception in a
Generic Network Architecture
 ETSI TS 101 671 Telecommunications security; Lawful Interception (LI); Handover interface for the
lawful interception of telecommunications traffic
 TIA J-STD-025-B-2006 Lawfully Authorized Electronic Surveillance
2.6.6 Intelligent MAP-D Multiplexer (IMDX)
Key Capabilities
Intelligent MAP-D Multiplexer function enables the R9 system to provide private, hybrid and public user
services to the GSM subscribers. A GSM network provides service to GSM users who may be local HPLMN
subscribers or roaming users from other HPLMN. Normally, GSM subscribers are public users and are
accessible by the worldwide telecommunication network. However, under certain circumstances, some
GSM users only request local GSM services. They don’t need to be accessible from other GSM networks.
These GSM users are called private users. The GSM users who act as both public and private users are
called hybrid users.
Public User
User with subscription profile presents in HLR but do not have IMDX account in OPPS. Public user’s
subscription profile may be present in public network’s HLR or local network’s HLR. Public user registers to
the local network as a local GSM subscriber (with subscription profile in local HLR) or a roaming GSM
subscriber (with subscription profile in public HLR). Public user can only call public users.
Private User
User with subscription profile present in local network’s HLR and is being classified as “private user” in

IMDX. Private users have two classes of privilege: ordinary and premium. Ordinary privilege can make calls
among private users, but it is not allowed to make calls to public users (local or roaming GSM subscribers);
Premium privilege is allowed to make calls to both private and public users. Please note that the private
users are not accessible by public users.
Hybrid User
User with two subscription profiles: one in the public network’s HLR and another in the local network’s HLR.
Hybrid user has dual identities: public user and private user; and two MSISDNs: public phone number and
private phone number. Hybrid user owns both the privileges of the public user and private user. He can
access to and be accessible from both the public network and the local network. Hybrid user acts as a
public user when being called by his public MSISDN or is calling a public MSISDN. He will act as a private
user if he is being called by his local private MSISDN or calling the other private MSISDN.
Principle Benefits
 Enable network operators to provide multi-services to GSM users in areas without network coverage,
for example: cruisers, offshore oilfields. Extreme regions.
 Use the existing R9 system to provide GSM services to employee users as a private communication
tool for their daily works.
2.6.7 Open-to-all Prepaid Roaming (OPR)
Key Capabilities
GSM Network covers 222 countries and regions with over 2.1 billion subscribers across 920 networks.
Travelers may roam to foreign networks if their home operator has established with the roaming
agreements the local operators. However, signing up roaming partners can be a laborious and daunting
process, especially for the small operators. If a mobile user’s home network doesn’t has roaming
agreement with the local operators then the only option for him to use the local GSM services is to
purchase a local SIM card or he will experience a loss of service. Travelers are reluctance to change their
SIM cards, especially who are staying in the area for a short period of time. The operators will lose the
revenue opportunity.
Open-to-all Prepaid Roaming function enables the existing LITECORE Prepaid System to provide
temporary services to any visiting GSM users without changing SIM cards – users from operators with or
without roaming agreements; even users from operators that do not have local roaming agreements in
place may use the OPR services. OPR uses the visitor’s home IMSI to identify a subscriber, hence all GSM

users in the world may subscribe to the local OPR services without changing their SIM card. Still they need
to purchase a prepay card from the local operator.
Principle Benefits
 Enable network operators to provide prepaid services to any GSM users entering their network
coverage without purchase the local SIM Cards.
 Use the existing LITECORE Prepaid System and SMS to provide temporary services to users from
operators that do not have local roaming agreements in place.
 Allow small network operators without or with only a few roaming agreements to launch prepaid service
to capture all the potential visitors instantly.
 Low operation cost. Registration and service deliveries are operator care free.
2.6.8 Location Services (LCS)
Key Capabilities
The Location Service feature provides mobile networks with the Cell ID based location query service via
standard Lg and Lh interface, enabling blooming opportunities for the creation of new location services,
such as city navigation, intelligent transportation, regional advertisement and location-based emergency
call.
Reference
 GSM 02.71: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Service
description; Stage 1".
 GSM 04.71: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3
Location Services (LCS) specification".
2.6.9 IP Private A-link Intelligent Multiplexer (iPALIM)
Key Capabilities
IP Private A-link Intelligent Multiplexer (iPALIM) is a function of the LITECOREsoftswitch system to connect
the local Inter-Reach Office (IRO) network to Public Mobile Network (PLMN) via A-interface. It allows the
IRO to perform as a self-contained GSM system or a virtual BSC of the PLMN, depending on the desired

service and user type. iPALIM monitors the messages originated by a subscriber to determine his user type,
and selects the optimal way to route the call.
iPALIM provides two types of services - private service and public service.
 iPALIM routes calls of private users to the local MSC for local switching within the IRO network. The
private users may also make calls to local PSTN or PBX if it is attainable.
 For public users, iPALIM routes calls to the PLMN MSC, bypassing the IRO soft-switch. iPALIM makes
IRO appears as a BSC to the PLMN MSC. iPALIM is transparent to the user and to the IRO MSC.
Moving into and out of the IRO is seamless to the public user.
In some special circumstances, the IRO operator may want to prohibit certain types of users from
registering to the IRO network. For example, the Public and Hybrid users should register to their host
PLMN when the IRO is overlapping with the public network, such as a cruise ship docking to a terminal.
This requires the IRO to prevent all the Public users and public identity of Hybrid users from registering to
the local network. The IRO has to reject any location updates or MO attempts from Public and Hybrid users.
iPALIM provides an “Exclusive Access” operation command for the IRO operator to alter the network
access privilege, which can be applied to each type of users separately:
 Public Exclusive: Allow or forbid Public users to login the local IRO.
 Hybrid Exclusive: Allow or forbid Hybrid users to login the local IRO.
 Private Exclusive: Allow or forbid Private users to login the local IRO.
iPALIM has a 256-entry IMSI Prefix Table. Operator may set the IMSI Prefix Table attribute as a White List
or a Black List. If the IMSI Prefix Table is set as a White List then only users whose IMSI prefix can be found
in the IMSI Prefix Table are allowed to register to the iPALIM network. If the IMSI Prefix Table is set as a
Black List then only users whose IMSI prefixes are listed in the IMSI Prefix Table are prohibited from
registering to the iPALIM network. In other words, white list is a list of IMSI prefixes that are allowed to use
the iPALIM network; while black list is a list of IMSI prefixes that are prohibited from using the iPALIM
network.
Principle Benefits
 Enable hooking the LITECORE IRO network to the PLMN as a BSS to expand the radio coverage for
public users and at the same time to provide local GSM services to private and hybrid users.
 Adding the IRO to the PLMN is simple and straight forward because it is connecting to the PLMN with
A-interface.
 Simple network expansion. iPALIM gateway function supports hierarchical connections to allow
multiple subordinate IRO be connected “behind” the central IRO without the notice of the PLMN. The
central IRO always appear as single BSC to the PLMN no matter how many subordinate IROs in the

IPLOOK MSC/VLR Feature Specification

IPLOOK MSC/VLR Feature Specification

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Similar to IPLOOK MSC/VLR Feature Specification

Similar to IPLOOK MSC/VLR Feature Specification (20)

More from IPLOOK Networks

More from IPLOOK Networks (20)

Recently uploaded

Recently uploaded (20)

IPLOOK MSC/VLR Feature Specification