Core Voice Network Overview

All-IP CDMA2000
Sonata Core Voice Network

Release 4.5.3
Core Voice Network Overview
Part Number D02109 Rev A0

All-IP CDMA2000
Sonata Core Voice Network
Release 4.5.3
Core Voice Network Overview

Copyright 2009, Global Star Solutions ULC. All rights reserved. No part of this documentation may be reproduced in any form
or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without prior written
permission from Global Star Solutions ULC.
Global Star Solutions ULC reserves the right to revise this documentation and to make changes in content from time to time
without obligation on the part of Global Star Solutions ULC to provide notification of such revision or change.
Global Star Solutions ULC provides this documentation without warranty of any kind, either implied or expressed, including, but
not limited to, the implied warranties of merchantability and fitness for a particular purpose. Star Solutions may make
improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.
UNITED STATES GOVERNMENT LEGENDS:
If you are a United States government agency, then this documentation and the software described herein are provided to you
subject to the following:
United States Government Legend: All technical data and computer software is commercial in nature and developed solely at
private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995) or as a
commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in Star Solutions's
standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR
252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion
of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this
User Guide.
Star Solutions, the Star Solutions logo, iCell, Softexchange, Sonata, Sonata Access Tandem, Sonata HLR, Sonata IP, Sonata MSC,
Sonata WLL, and Telos are registered trademarks or trademarks of Global Star Solutions ULC and its subsidiaries.
CDMA2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA).
Intel and Pentium are registered trademarks of the Intel Corporation or its subsidiaries in the United States and other countries.
Microsoft, Windows, Windows NT, and NetMeeting are registered trademarks of Microsoft Corporation. Sun, Java, and Solaris
are trademarks or registered trademarks of Sun Microsystems, Inc. Oracle is a registered trademark of Oracle Corporation. HP,
HP-UX, and HP Openview are trademarks or registered trademarks of the Hewlett-Packard Company. UTStarcom, the
UTStarcom logo, MovingMedia, mSwitch, and Total Control are registered trademarks or trademarks of UTStarcom, Inc. and its
subsidiaries.
Other brand and product names may be registered trademarks or trademarks of their respective holders.
CONTENTS
ABOUT THIS GUIDE

Conventions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13
Notices - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13
Figures and Screen Captures- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
Text - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
Related Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
Core Voice Network Documents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
Technical Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17
Obtaining Technical Assistance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17
Service Centers Operational Hours - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17
Warranty Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17
Contacting Technical Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18
1 SYSTEM FUNCTION
Evolution to an All-IP Network - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19
System Benefits - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20
All-IP Network Benefits- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20
System Components - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21
Core Voice Network Components - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22
Core Data Network Components - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22
Radio Access Network Components - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22
Additional Network Components - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22
Operational Lifecycle - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23
Functional Description - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24
Mobility Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25
Location Updating- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25
Mobile Origination - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25
Mobile Termination - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25
Call Processing Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26
IP Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26
Protocol Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26
System Interfaces and Protocols - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 26
Signaling Protocols - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Access Network Signaling Protocols- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Core Network Signaling Protocols - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Call-Control Signaling Protocols - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Media-Control Signaling Protocols- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Media Stream Protocols - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28
Network Layer Model - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28
Services Layer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28
Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Part Number D02109 Rev A0 | April 2009
6 Contents
Control Layer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28
Media Layer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29
Sample Call Flows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29
2 SYSTEM FEATURES
Subscriber Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
TTY/TDD support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
1-800 Service - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
International Direct Distance Dialing (IDDD) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Single Number Hotline - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Local Number Portability - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
32-Digit Dialing- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Integrated Subscriber Equal Access Database - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Carrier Access - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Carrier Pre-Selection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Routing Based on Called Number - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Routing Based on Call Type - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Routing Based on Caller ID - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Routing Based on Preferred Inter-exchange Carrier - - - - - - - - - - - - - - - - - - - - - 34
Call Delivery (CD) (664-501-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Forward - Busy (CFB) (664-502-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Forward - Default (CFD) (664-503-A)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Forward - No Answer (CFNA) (664-504-A)- - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Forward - Unconditional (CFU) (664-505-A) - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Call Waiting (CW) (664-507-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 34
Calling Number ID Presentation (CNIP) (664-508-A) - - - - - - - - - - - - - - - - - - - - - - - 35
Calling Number ID Restriction (CNIR) (664-509-A) - - - - - - - - - - - - - - - - - - - - - - - - - 35
Calling Name Presentation / Calling Name Restriction Overview - - - - - - - - - - - - - - 35
Subscriber PIN Intercept / Subscriber PIN Access Overview - - - - - - - - - - - - - - - - - - 35
Color Ringback Tone - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Message Waiting Notification (664-513-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
3 Way Calling (664-522-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Call Hold - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Call Transfer - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Malicious Call Trace - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Voice Message Retrieval (664-523-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
Short Message Delivery Point-to-Point Bearer Service (664-601-A) - - - - - - - - - - - - 36
Over the Air Service Provisioning (664-533-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
Roaming - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
Service Provider Features- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
ISDN PRI Protocol Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
Channel Associated Signaling (CAS) Protocol Support - - - - - - - - - - - - - - - - - - - - - - 36
SS7 Protocol Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
ISUP Protocol Support- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
ANSI ISDN User Part (ISUP) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 36
ITU ISDN User Part (ISUP) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37
ISUP Port Selection Optimization - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37

Contents 7
Concurrent ANSI / ITU ISUP support- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37

Message Transfer Part (MTP) Level 3 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37
Signaling Connection Control Part (SCCP) - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37
SCCP-Lite - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37
Transaction Capabilities Application Part (TCAP) - - - - - - - - - - - - - - - - - - - - - - - 38
SIGTRAN Protocol Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
M3UA (RFC 3332) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
M2UA (RFC 3331) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
Stream Control Transmission Protocol (SCTP) (RFC 2960) - - - - - - - - - - - - - - - - - 38
Media Stream Protocol Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
Enhanced Variable Rate CODEC (EVRC) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 38
Real-time Transport Protocol (RTP) (RFC 3550) - - - - - - - - - - - - - - - - - - - - - - - - 38
RFC 3558 Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
Media Management- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
MGCP (RFC 2705) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
Megaco/H.248 (RFC 3015) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
Concurrent MGCP / Megaco - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 39
Session Initiation Protocol (SIP) (RFC 2543) - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
IP v4 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
MSC-BSC Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
MSC-VLR-HLR Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
MSC-SMS-MC Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
Intersystem Handoff- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
Remote MSC Availability- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
Inter-Working between -law and A-law Encoded Voice - - - - - - - - - - - - - - - - - - - - 40
Transcoder Free Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
Inter-MSC IP Trunking- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 40
Direct SMS Delivery - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
16-KHz Metering - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Missed Call Alert - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Call Processing Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Call Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Call Progress and Treatment Handling - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Alternate Routes for Destinations - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Trunk Grouping- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Routing Control- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Toll Restriction / Classmark - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Classes of Service - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 41
Class of Service Routing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Class of Service Change Based on Call Information - - - - - - - - - - - - - - - - - - - 42
Class of Service Change Based on Collected Information- - - - - - - - - - - - - - - 42
Private Number Plan - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Multiple Call Treatment Sets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Translations - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Translation Sets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Digit Manipulation- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Digit Translations- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42

8 Contents
Reconstruction of Call Information- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42

Enhanced Translation Pattern Matching - - - - - - - - - - - - - - - - - - - - - - - - - - - 42
Defaults for Missing Call Information- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43
Voice Prompts and In-call DTMF Digit Collection - - - - - - - - - - - - - - - - - - - - - - - 43
Prompt and Collect for Additional or Missing Call Information - - - - - - - - - - 43
Call Routing Based on Prompted Call Information- - - - - - - - - - - - - - - - - - - - 43
Nature of Address Routing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43
Original Called Number Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43
Emergency Services Phase 1 (664-529-A) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43
Lawful Intercept - J-STD-025A (CALEA) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43
Wireless Intelligent Networking Pre-paid Service - - - - - - - - - - - - - - - - - - - - - - - - - 43
WIN Office Triggers - Originating (IS 826) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 43
WIN Office Triggers - Terminating (IS 826) - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44
Mobility Management Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44
Authentication - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44
Mobility Pre-translation Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44
Over the Air Parameter Administration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 44
Operations and Maintenance Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
Online Provisioning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
Billing Features- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
Centralized Billing Generation Point - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
Call Detail Record Generation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
Call Detail Record - Multiple Call Forward - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
Selective Call Trace - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 45
3 SYSTEM DESCRIPTION
Core Voice Network Components- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 47
Star Solutions Sonata SE Mobile Switching Center Server - - - - - - - - - - - - - - - - - - - - - - 47
Core Applications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48
Call Processing Engine- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48
Mobility Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 49
Common Services (CONX) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50
SNAP - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50
Operations and Maintenance interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50
Media Gateway Control - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51
Resource Control - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51
Connection Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51
Media Processing Control - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51
Signal and Event Processing- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 51
Statistics Reporting - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52
Provisioning - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52
Protocol Layer Management- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52
Star Solutions Sonata Signaling Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 52
Signaling Protocols - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53
Signaling Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53
Active-Standby Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53
M3UA Support - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54

Contents 9
Signaling Gateway - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 54
Star Solutions Sonata Intelligent Media Gateway - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55
Media Gateway Functionality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 55
Signaling Gateway Functionality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 56
E1/T1 Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 56
Star Solutions Feature Server Home Location Register / Authentication Center - - - - - - 56
Home Location Register - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 56
HLR SIP Gateway - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 57
Authentication Center - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 57
Star Solutions Sonata SE Access Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 57
Capacity - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58
Tone / Announcement Files - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 59
Star Solutions Sonata SE Call Conference Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 59
Star Solutions Sonata SE Lawful Intercept Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - 60
Sonata Lawful Intercept Network - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 61
Star Solutions Sonata Operations and Maintenance Center- - - - - - - - - - - - - - - - - - - - - 62
OMC Server and Client - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 63
OMC Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 63
OMC Client - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 63
OMC Architecture - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 64
Functions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 64
Southbound Mediation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65
Data Storage - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65
Network Element Interfaces - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65
DRUM - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65
SNMP - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
FTP - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
Telnet - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
Northbound Mediation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
Fault Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 66
Configuration Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Accounting Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Performance Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Security Management- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Ethernet Switch - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 67
Serial Port Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 68
4 SONATA SYSTEM TECHNICAL SPECIFICATIONS

Sun Microsystems Netra Processors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 69
Compact PCI (cPCI) System- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 69
OMC Server - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 69
Call Conference Server- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 70
Ethernet Switches - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 70
Additional Hardware - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 70

10 Contents
A ACRONYMS
INDEX

Tables 11
LIST OF TABLES
Table 1 Notice Icon Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 13
Table 2 Text Convention Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
Table 3 Protocols Used at the Sonata System Interfaces- - - - - - - - - - - - - - - - - - - - - 26
Table 4 List of Acronyms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 71

12 Figures
LIST OF F IGURES
Figure 1 Core Voice Network Document Map - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
Figure 2 All-IP Network Compared to a TDM Network - - - - - - - - - - - - - - - - - - - - - - 21
Figure 3 Typical Logical View of a Sonata System in a Network - - - - - - - - - - - - - - - - 22
Figure 4 Operational Lifecycle - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 24
Figure 5 Media, Control, and Service Planes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 28
Figure 6 Mobile-to-PSTN Call Flow - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30
Figure 7 Mobile-to-Mobile Call Flow - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31
Figure 8 MSC Core Applications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 48
Figure 9 MOB Functional Application - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 50
Figure 10 Position of the Signaling Server Node - - - - - - - - - - - - - - - - - - - - - - - - - - - - 53
Figure 11 Active-Standby MSC and SSVR Configuration - - - - - - - - - - - - - - - - - - - - - - 54
Figure 12 Signaling Server Application Messaging for Example 1 - - - - - - - - - - - - - - - 55
Figure 13 Star Solutions Sonata Network - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 57
Figure 14 Access Server Media Streaming - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 58
Figure 15 Lawful Intercept Network Architecture - - - - - - - - - - - - - - - - - - - - - - - - - - - 62
Figure 16 OMC Interactions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 63
Figure 17 Position of the OMC in the TMN Model - - - - - - - - - - - - - - - - - - - - - - - - - - 64
Figure 18 OMC Architecture - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 65

ABOUT THIS GUIDE
The About This Guide section lists guide conventions and related documentation,
and describes how to contact customer service and technical documentation.
This chapter includes:
Conventions
Related Documentation
Technical Support
Warranty Support
Contacting Technical Documentation
This guide is intended for system and network architects, planners, and
operations and support engineers as an introduction to the core voice network
components of the Star Solutions Sonata system. The guide assumes its readers
have an understanding of telecommunications, Internet Protocol (IP) telephony,
and the SS7 and SIGTRAN protocols.
This guide provides an overview of the Sonata Core Voice Network system. It is
intended for system architects, planners, and engineers.
Release notes are issued with some products. If the information in the release
notes differs from the information in this guide, follow the instructions in the
release notes.
Conventions This guide may contain notices, figures, screen captures, and certain text
conventions.
Notices Table 1 lists notice icons used in this guide.
Table 1 Notice Icon Descriptions
Icon Notice Type Description

Information Note Information that contains important features or
instructions but is not hazard-related.

14 Chapter : About This Guide
Table 1 Notice Icon Descriptions (continued)
Icon Notice Type Description

Caution or Warning Cautions are preceded with the word Caution. This
type of caution indicates a potentially hazardous
situation which, if not avoided, may result in minor
or moderate injury. It may also alert against unsafe
practices and potential program, data, system, or
device damage.
Warnings are preceded with the word Warning.
This type of warning indicates a potentially
hazardous situation which, if not avoided, could
result in death or serious injury.
Caution or Warning Cautions due to potential electrical hazards are
due to potential preceded with the word Caution. This type of
electrical hazard caution indicates a potential electrical hazard. This
hazard, if not avoided, may result in minor or
moderate injury. It may also alert against unsafe
practices and potential program, data, system, or
device damage.
Warnings due to potential electrical hazards are
preceded with the word Warning. This type of
warning indicates a potential electrical hazard. This
hazard, if not avoided, could result in death or
serious injury.
ESD Information that indicates proper grounding
precautions are required before handling a product.
Figures and Screen Captures This guide provides figures and screen captures as examples. These examples
contain sample data. This data may vary from the actual data on an installed
system.
Text Table 2 lists text conventions in this guide.
Table 2 Text Convention Descriptions
Convention Description
Text represented as a This typeface represents text that appears on a
screen display terminal screen, for example login:.
Text represented as user This typeface represents commands entered by the
entry. user, for example, cd $HOME.
Text represented as menu, This typeface represents all menu, sub-menu, tab, and
sub-menu, tab, and field field names within procedures, for example:
names On the File menu, click New.
Text represented by This typeface represents a required variable, for example:
<variable> <filename>
Related Documentation The documentation is divided into Core Voice Network documentation and
Access Network documentation.

Related Documentation 15
Core Voice Network Figure 1 maps the relationships between the Core Voice Network documents and
Documents suggests the order in which to read the documents.
For example, to operate and maintain the Signaling Server (SSVR), the document
map suggests reading the documents in the following order:
1 Core Voice Network Overview (this guide)
2 Any relevant release notes
3 OMC User Interface Guide
4 Core Voice Network Operations, Maintenance, and Provisioning Guide
5 Signaling Server and Signaling Server Application Guide
The Core Voice Network Operations, Maintenance, and Provisioning Guide and
the OMC User Interface Guide contain common procedures and information for
all Core Voice Network nodes (except for the Call Conference Server and IMG),
and should be read prior to reading the node-specific guides. The other
node-specific guides are:
MSC Server Provisioning Guide, which contains the MSC-specific tables and
how to provision them.
MSC Server Operations and Maintenance Guide, which contains the
MSC-specific procedures for operating and maintaining the MSC Server, such
as procedures related to upper layer call processing protocols, Call Detail
Records (CDR), and MSC-specific alarms.
HLR and Authentication Center Guide, which contains all HLR-specific
provisioning, operations and maintenance procedures, and HLR-specific
alarms etc.
Signaling Server Application Guide, which contains a description of the
Signaling Server Application and the various configurations that
accommodate the application. This guide contains SS7 operations and
maintenance procedures and SS7 alarm information, as well as Signaling
Server (SSVR) node-specific operations and maintenance procedures.
Access Server (MRF) Guide, which contains a description of the tones and
announcements available to the MSC, a description of the Media Resource
Function (MRF), and operations, maintenance, and provisioning procedures
specific to the Access Server.
Lawful Intercept Server Guide, which contains a description of the Lawful
Intercept Service, the components that are involved the service, and the
operations, maintenance, and provisioning specific to the Lawful Intecept
Server and Service.
Call Conference Server Guide, which contains a description of the Call
Conference Server, a description of the three-way call functionality, and
operations, maintenance, and provisioning procedures specific to the Call
Conference Server.
Media / Signaling Gateway Server Operations, Maintenance, and Provisioning
Guide, which contains the specific procedures for operating and maintaining
the MGW / SGW.
Sonata Core Voice Network Release 4.5.3 Core Voice Network Overview
Figure 1 Core Voice Network Document Map

Technical Support 17
Technical Support The Star Solutions Product Support Team delivers the support services required
for business and professional needs. Our product experts deliver Tier 1, 2 and 3
technical support directly to new and contract-entitled customers including the
following services:
Basic Support Package: Non-emergency technical support
Premium Support Package: 24 hours a day, 7 days a week, and 365 days a year
Emergency technical support
The Star Solutions Service Guide outlines the specific details for obtaining
technical support. The guide is available from a sales account manager. Refer to
the Service Guide for services and options specific to individual support plans,
including guidelines for problem severity and the technical resolution escalation
process.
Obtaining Technical Star Solutions maintains a global presence through its Technical Response and
Assistance Service Centers. These centers are available for technical telephone support to
entitled customers during normal business hours.
Before contacting technical support, have this information available:

Product information
Software and hardware revisions
Serial numbers
Problem description
Symptoms
Known causes
Trouble locating and clearing attempts.
For information about customer service, including support, training, code

releases and updates, contracts, and documentation, contact us at:
http://www.starsolutions.com/support
Service Centers Operational Hours

North America/CALA Region:
09:0018:00 Pacific Time (UTC-8:00)
EMEA/Asia Pacific Region:

09:3018:30 Indian Standard Time (UTC+5:30)
Warranty Support Star Solutions provides its customers warranty support per the terms of the Star
Solutions Warranty Statement for their equipment. Customers who require
warranty support should contact the Star Solutions Customer Service Center as
specified in the customer service guide or at:
http://www.starsolutions.com/service-support
Contacting Technical To provide comments on this documentation, send an e-mail to:

Documentation
dl-techcom@starsolutions.com
Please include the name and part number of the guide being referenced. If
applicable, provide the chapter and page number.

SYSTEM FUNCTION
1
This chapter describes the function of a Star Solutions All-IP CDMA2000 system in
a wireless CDMA voice and data network.
This chapter contains:

Evolution to an All-IP Network
System Benefits
System Components
Core Voice Network Components
Core Data Network Components
Radio Access Network Components
Additional Network Components
Operational Lifecycle
Functional Description
Mobility Functions
IP Functions
Protocol Support
Signaling Protocols
Call-Control Signaling Protocols
Media-Control Signaling Protocols
Media Stream Protocols
Network Layer Model
Sample Call Flows
Evolution to an All-IP The Star Solutions Sonata system is an end-to-end all IP-based CDMA solution.
Network The Sonata system provides the mobility and media control traditionally
associated with a circuit switched Mobile Switching Center (MSC), but in a
packet-based environment.
In traditional TDM networks, call processing functions and switching functions

are usually combined. In the IP world of the Sonata system, these functions are
separated into a software-based (softswitch) Mobile Switching Center (MSC) for
call processing functions, and media and signaling gateways controlled by a
media gateway control protocol for switching functions.
The MSC also performs the mobility function by handling location and
connection establishment before invoking call processing services.

20 Chapter 1: System Function
The Star Solutions Sonata system is 2G and 3G capable, supporting cdmaOne and
CDMA2000 1x networks. By deploying the Sonata system in 2G and 3G
environments, operators gain the efficiency inherent in packet-based networks,
while building a network core capable of supporting 3G standards.
The Sonata system is designed for the CDMA2000 1x IP packet network. In an IP

network, all data is treated as packets that are routed across the network using
routers, gateways, or ATM switches. These devices are capable of supporting
voice streams, Voice-over-Packet (VoP), and signaling streams.
System Benefits Star Solutions system benefits include:

A network core that supports both voice and data traffic, eliminating the need
to operate separate TDM and packet backbones
Distributed switching for efficient call routing from endpoint to endpoint
Centralized control of distributed switching for cost-effective scalability,
security, and ease of operation
Voice carried in native EVRC air-interface format across the packet core for
improved quality and maximum bandwidth efficiency, with Pulse Code
Modulation (PCM) vocoding done by the Media Gateways at the network
edge for Public Switched Telephone Network (PSTN) connectivity
All-IP Network Benefits The Sonata system enables the evolution to an all IP-Network while delivering a
reduced cost of construction and ownership compared to traditional TDM
networks.
In an all-IP network the BSC can connect a mobile-to-mobile call without

involving the MSC (except for signaling support) since all media control is handled
by the BSC.
Figure 2 illustrates the advantage of an all-IP network over a traditional TDM

network. The upper half of Figure 2 illustrates that when a caller makes a
mobile-to-mobile call in a traditional TDM network, the network backhauls the
media to the MSC and back. The lower half of Figure 2 illustrates that when a
caller makes a mobile-to-mobile call in an all-IP network, the Soft Base Station
Controller (sBSC) connects the call without involving the MSC (except for
signaling support) since all media control is handled by the BSC.
When a caller makes a mobile-to-land call in a traditional TDM network, the call
takes up a full 64-Kbps channel all the way from the BSC to the called destination.
In an all-IP network the EVRC media payload is transported in native form
throughout the IP network and only converted to TDM at the edge of the IP
network, via the intelligent media gateway (IMG).
Media resources at the IMG are therefore used only when required, rather than
for every call.
System Components 21
Figure 2 All-IP Network Compared to a TDM Network
MS BTS SS7
BSC MSC
PSTN
MS BTS
Mobile-Mobile Signaling CDMA2000 Abis A/SS7
Mobile-Mobile Media Stream EVRC 64 Kbps TDM
Mobile-Land Signaling CDMA2000 Abis A/SS7 ISUP/SS7
Mobile-Land Media Stream EVRC 64 Kbps TDM
MSC
MS BTS
SS7
SGW
BSC IP
MGW
PSTN
MS BTS
Mobile-Mobile Signaling CDMA2000 Abis/IP A/IP
Mobile-Mobile Media Stream EVRC
Mobile-Land Signaling CDMA2000 Abis/IP A/IP ISUP/IP ISUP/SS7
EVRC 64 Kbps TDM
System Components The Sonata products and components included in a network depend on the
specific function and design of the network. Figure 3 illustrates a typical Sonata
system in a CDMA network.

Figure 3 Typical Logical View of a Sonata System in a Network
Core Voice Network The Sonata core voice network products include:
Components
Star Solutions Sonata SoftExchange Mobile Switching Center (MSC) Server
Visitor Location Register (VLR) functionality
Signaling Server functionality
Star Solutions Sonata SoftExchange Signaling Server (SSVR)
Star Solutions Sonata SoftExchange Access Server
Star Solutions Sonata SoftExchange Call Conferencing Server
Star Solutions Sonata SoftExchange Lawful Intercept Server
Star Solutions Sonata Feature Server Home Location Register (HLR)
Authentication Center (AC) functionality
Star Solutions Sonata Intelligent Media Gateway (IMG)
Star Solutions Sonata Operations and Maintenance Server
Core Data Network The Star Solutions Core Data Network products include:
Components
Packet Data Serving Node (PDSN)
Common Element Manager (CEM)
Home Agent (HA)
Radio Access Network The Star Solutions radio access network components include:
Components
Star Solutions iCell Macro IP Base Transceiver System (BTS)
Star Solutions iCell Pico IP Base Transceiver System (BTS)
Star Solutions iCell Soft Base Station Controller (sBSC)
Additional Network Additional network components include:

Components
Ethernet Switch
Operational Lifecycle 23
Serial Port Server
The Sonata system also interoperates with other products to deliver additional
network services and features. These products include:
Mobile Station (MS)
Short Message Service Message Center (SMS-MC)
Service Control Point (SCP)
Pre-Paid Server (and other service platforms)
UTStarcom 5250 PCMS (and other Voice Mail Systems)
Over-the-Air Facility (OTAF) for Over-the-Air Service Provisioning and
Parameter Administration (OTASP and OTAPA)
This guide covers the Core Voice Network components. Refer to the Access
Network Overview Guide for information on the radio access network
components.
A complete discussion of the other components and products is beyond the

scope of this guide. For additional information on these products refer to each
product's documentation set.
Operational Lifecycle There is an operational lifecycle that is useful to follow when installing and
operating the Sonata system and considering upgrades or changes to the system.
Figure 4 shows this lifecycle.

Figure 4 Operational Lifecycle
Network
Planning
Network Planned
Site Preparation
and Installation
System Installed
Commissioning
System Buildout
System Commissioned
Decision to Expand
Integration System Capacity or Hardware
System Integrated
Optimization
Validation Failed Optimization Needed

System Optimized
Emergency
Fix Integrated Correction
Upgrade/Expansion Complete Validation
Fix Needed
Decision to Upgrade/Expand Troubleshooting Complete
ATP Passed
Normal
Upgrade and
Operations Troubleshooting
Expansion
Planned Obsolescence
Upgrade/Expansion Rolled Back Problem Reported
Obsolescence
Functional Description The role of the Sonata system in the network is to perform the functions required
to allow CDMA 1x mobile stations to obtain all required services of the network.
Functional Description 25
These functions are described from the following three aspects:

Mobility functions
Call Processing Functions
IP functions
These functions are described in the following headings.
Mobility Functions Mobility functions take place primarily in and between the BSC, MSC, VLR, and
HLR. Star Solutions supports the following mobility functions:
Location updating
Mobile origination
Mobile termination
Location Updating
Location updating is initiated by the mobile station (MS). When the MSC is
notified of an MS power-on, the VLR sends an IS-41 RegistrationNotification
(REGNOT) message to the HLR. When the MSC is notified of an MS power-off, it
sends an IS-41 MSInactive (MSINACT) message to the HLR.
On receiving location updates from the mobile, the VLR sends the subscriber's
HLR a message that updates the current location in the subscriber's home profile.
Mobile Origination
When the MSC receives a service request from a mobile station, the MSC
attempts to qualify the MS for service by sending an IS-41 QualificationRequest
(QUALREQ) message to the subscriber's HLR. If the subscriber's profile is not
already in the VLR, the MSC may send a RegistrationNotification (REGNOT)
message to the HLR to retrieve it. Translations then take over to route the call
according to the digits dialed.
Mobile Termination
When an MSC receives a new incoming call request, it assigns a class of service
based on the calling party's mobile identification number (MIN) and origination
indicator (ORIGIND). The MSC is designated the Gateway MSC. The call is
translated and progressed according to the class of service and the dialed digits.
Based on translations, the MSC may also need to contact the subscriber's HLR
with a LocationRequest (LOCREQ) message.
If the called party and calling party are at the same MSC, the HLR inserts CD-Local
in the LOCREQ reply. The MSC assigns a temporary local directory number (TLDN)
internally then performs a second translation. This translation causes the MSC to
page the subscriber in order to complete the call.
If the called party is at a different MSC, the HLR sends a RoutingRequest

(ROUTREQ) message to the Visited MSC. The Visited MSC returns a TLDN in the
ROUTREQ reply, which the HLR passes on to the Gateway MSC in the Digits
portion of the LOCREQ reply. The MSC then performs a second translation on the
TLDN digits and routes the call to the called party's MSC (the Visited MSC).

When the Visited MSC receives the call setup request, it translates the TLDN
digits. If the Visited MSC is a Star Solutions Sonata SE MSC, the translation causes
the MSC to page the subscriber in order to complete the call.
Call Processing Functions Call Processing functions take place primarily in the MSC.
Call processing provides the functionality for call setup and call release, to route
calls, perform digit analysis and translation, and provide call features. It ensures
that call switching is in a consistent state and establishes voice paths.
IP Functions IP functions provide the connectivity and functionality between the MSC, BSC,
and IMG using IP-based protocols.
The Sonata system provides mobility in a network where both the A-interface to
the BSC and the bearer traffic are carried over IP.
The Sonata system is part of an IP network with one of its components, the
Intelligent Media Gateway (IMG), providing access to and from the PSTN.
Protocol Support The protocols supported by the Sonata system can be divided into:
BSC signaling protocols
Call control signaling protocols
Gateway signaling protocols
Media stream protocols
This section provides an overview of supported protocols; for specific

information refer to Service Provider Features in Chapter 2: System Features.
System Interfaces and All Sonata system interfaces are based on standards or proposed standards. Table
Protocols 3 shows the protocols used at the system interfaces.
Table 3 Protocols Used at the Sonata System Interfaces
Interface Protocol(s)
MSC - Signaling Server MAP, ISUP
MSC - Gateway MGCP, Megaco
MSC - BSC MGCP, A-interface
MSC - Call Conferencing Server SIP
MSC - Access Server (MRF) SIP
Gateway - SS7 Network MTP1, MTP2
Gateway - PSTN G.711-encoded audio,
MF-R1 DTMF
BSC - BTS TIA/EIA-828 Abis
BSC - Gateway RTP
BTS - CDMA Network CDMA2000 1x
Call Conferencing Server - Gateway RTP
Protocol Support 27
Table 3 Protocols Used at the Sonata System Interfaces
Interface Protocol(s)
Access Server - Gateway RTP
Signaling Protocols Access Network Signaling Protocols

The A-interface is the call-control signaling between the BSC and the MSC. The
A-interface supports all of the procedures between the MSC and the IP Base
Station that require interpretation and processing of information related to single
calls and resource management.
Below the A-interface, SCCP-Lite provides the TCP/IP socket-based transport

mechanism for SCCP messages. It creates the call context in which to pass
messages between the MSC Server and the IP Base Station.
Core Network Signaling Protocols

Core Network signaling functionality is contained in the MSC, the Signaling Server
application (which occurs in the MSC, HLR, and/or the Signaling Server), and the
Signaling Gateway. The following SS7 and SIGTRAN protocols are supported in
the Core Network:
Message Transfer Part 3 (MTP3) in the Signaling Server application
Message Transfer Part 2 (MTP2) in the Signaling Gateway
Message Transfer Part 1 (MTP1) in the Signaling Gateway
Signaling Connection Control Part (SCCP) in the Signaling Server application
Transaction Capability Application Part (TCAP) in the MSC and HLR
MTP3 User Adaptation Layer (M3UA) in the Signaling Server application
MTP2 User Adaptation Layer (M2UA) in the Signaling Server application
Stream Control Transmission Protocol (SCTP) in the Signaling Server
application
Call-Control Signaling Protocols

The Star Solutions Sonata system supports the following call-control protocols in
the MSC:
ISDN User Part (ISUP)
Primary Rate Interface (PRI)
Channel Associated Signaling (CAS) (MF R1 and MFC R2)
Proprietary channel associated signalling protocol (TCCS)
Session Initiation Protocol (SIP)
Media-Control Signaling Protocols

The media-control signaling protocols are IP protocols that manage the interface
between the MSC Server and the Media Gateway. The MSC Server supports the
MGCP and Megaco (H.248) media-control protocol.

Media Stream Protocols The media stream protocols are responsible for the TDM and IP interfaces to the
Media Gateway. Voice and data calls access the mobile and fixed-line networks
through these interfaces.
Network Layer Model The network can be divided into media, control, and services layers. Figure 5
shows how the Star Solutions Sonata system fits into the network layer model.
Figure 5 Media, Control, and Service Planes
Services Layer
The services layer is responsible for service control functions such as:
Address translations
Intelligent Network services
Enhanced call features (voicemail, prepaid, short message service)
The services layer uses the IS41 Mobile Application Part (IS-41 MAP) or Intelligent
Network Application Part (INAP) protocols to communicate with the control layer.
Control Layer
The control layer is responsible for call control functions such as call processing.
The control layer consists of standardized elements such as:

Media Gateway Controller software module
IS-41 mobility control functions
The control functions communicate using an internal interface. The control layer
uses the MGCP/Megaco protocol to communicate with the media layer.
Sample Call Flows 29
Media Layer
The media layer sets up the Real-time Transport Protocol (RTP) voice and data
streams between network endpoints under the direction of the control layer. The
media layer provides the IP core network, and the PSTN E1/T1 TDM. The control
layer uses the Media Gateway Control Protocol (MGCP) and Megaco protocol.
The media layer consists of:

Radio network access
IP infrastructure equipment
PSTN E1/T1 time-division multiplexing (TDM)
Under the direction of the control layer, the media layer interconnects the voice
streams to either the PSTN, in which the bearer traffic is carried over E1/T1 TDM,
or to the IP network in which the bearer traffic is carried over Real-time Transport
Protocol (RTP).
Sample Call Flows Figure 6 and Figure 7 show the Mobile-to-PSTN and Mobile-to-Mobile call flows
employing the Star Solutions iCell BSS, IMG, MSC Server, and the Access Server
(which provides the Media Resource Function (MRF)).

Figure 6 Mobile-to-PSTN Call Flow
Sample Call Flows 31
Figure 7 Mobile-to-Mobile Call Flow

SYSTEM FEATURES
2
This chapter lists the features supported by the Star Solutions Sonata system.

Subscriber Features
Service Provider Features
Mobility Management Features
Operations and Maintenance Features
Subscriber Features The following headings describe the subscriber features supported by the Star
Solutions Sonata system. Some subscriber-specific features are provisioned on
the HLR. Where applicable, the appropriate TIA/EIA 664 standard is quoted.
TTY/TDD support Signals appropriate for a TeleTYpewriter (TTY) or Telecommunications Device for
the Deaf (TDD) terminals are supported by the Star Solutions Sonata system.
1-800 Service The 1-800 service allows a subscriber to dial a 1-800 number to access a 1-800
service database which translates the dialed number to the actual directory
number of the service that is trying to be located.
International Direct Distance International Direct Distance Dial is an international number which can be dialed
Dialing (IDDD) directly by the user.
Single Number Hotline A single number hotline supports a point-to-point communications link in which
a call may be automatically originated to the pre-selected destination without
any additional action by the user when the user presses Send.
Local Number Portability The AIN LNP (ATIS TIS1.6 TRQ 01 02 03) feature allows subscribers to move
between different service operators and still keep the same telephone number.
32-Digit Dialing 32-digit dialing allows the subscriber to be able to dial addresses of up to 32
digits in length. System translation capabilities are also extended to 32 digits such
that long digit strings can be fully analyzed.
Integrated Subscriber Equal Equal access allows a subscriber access to all service providers on equal terms.
Access Database
Carrier Access Carrier access enables a subscriber to select a preferred service provider by
dialing an access code in front of the dialed number.

34 Chapter 2: System Features
Carrier Pre-Selection Carrier pre-selection enables a mobile user to select a preferred service provider
without the need for dialing an access code. The MSC automatically adds the
Carrier Selection Code to the dialed number.
Call Routing Based on Called Calls can be selectively translated and routed based on digits dialed by the caller.
Number
Call Routing Based on Call Calls can be selectively translated and routed based on the type of call (for
Type example: voice, data, and fax).
Call Routing Based on Caller Calls can be selectively translated and routed based on the caller's calling line
ID identification number (CLID).
Call Routing Based on Calls can be selectively translated and routed based on the caller's preferred
Preferred Inter-exchange inter-exchange carrier code (PIC).
Carrier
Call Delivery (CD) (664-501-A) Call Delivery (CD) permits a subscriber to receive calls to his or her Directory
Number while roaming. CD does not impact a subscriber's ability to originate
calls. CD does not impact a subscriber's ability to receive calls via a roamer port.
Call Forward - Busy (CFB) Call Forwarding-Busy (CFB) permits a called subscriber to have the system send
(664-502-A) incoming calls addressed to the called subscriber's Directory Number to another
Directory Number (forward-to number) or to the called subscriber's designated
voice mail box, when the subscriber is engaged in a call or service.
Call Forward - Default (CFD) Call Forwarding-Default (CFD) permits a called subscriber to send incoming calls
(664-503-A) addressed to the called subscriber's Directory Number to the subscriber's
designated voice mailbox or to another Directory Number (forward-to number),
when the subscriber is engaged in a call.
Call Forward - No Answer Call Forwarding-No Answer (CFNA) permits a called subscriber to have the
(CFNA) (664-504-A) system send incoming calls addressed to the called subscriber's Directory
Number to another Directory Number (forward-to number) or to the called
subscriber's designated voice mailbox, when the subscriber fails to answer, or is
otherwise inaccessible (including no paging response, the subscriber's location is
not known, the subscriber is reported as inactive, Call Delivery is not active for a
roaming subscriber, and Do Not Disturb is active).
Call Forward - Unconditional Call Forwarding-Unconditional (CFU) permits a called subscriber to send
(CFU) (664-505-A) incoming calls addressed to the called subscriber's Directory Number to another
Directory Number (forward-to number) or to the called subscriber's designated
voice mailbox. If this feature is active, calls are forwarded regardless of the
condition of the termination.
Call Waiting (CW) (664-507-A) Call Waiting (CW) provides notification to a controlling subscriber of an incoming
call while the subscriber's call is in the two-way state. Subsequently, the
controlling subscriber can either answer or ignore the incoming call. If the
controlling subscriber answers the second call, it may alternate between the two
calls.
Subscriber Features 35
Calling Number ID Calling Number Identification Presentation (CNIP) provides the number
Presentation (CNIP) identification of the calling party to the called subscriber. One or two numbers
(664-508-A) may be presented to identify the calling party.
Calling Number ID Restriction Calling Number Identification Restriction (CNIR) restricts presentation of that
(CNIR) (664-509-A) subscriber's Calling Number Identification (CNI) to the called party.
Calling Name Presentation / When available, Calling Name Identification (CNA) may include, according to
Calling Name Restriction IS-764 (3GPP2 N.S0012):
Overview
information regarding the availability and presentation status of a calling
party's name, and optionally, the characters in the name
information regarding the availability and presentation status of the last
redirecting party's name, and optionally, the characters in the name
both of the above
The called party invokes Calling Name Presentation (CNAP). The subscriber who
activates the service receives the calling name on the incoming call.
The calling party invokes Calling Name Restriction (CNAR). The subscriber who
activates the service can restrict name presentation to the called party.
Subscriber PIN Intercept / Subscriber PIN Intercept (SPINI) and Subscriber PIN Access (SPINA) enable
Subscriber PIN Access subscribers to use a Personal Identification Number (PIN) to control call
Overview originations and network access from their mobile station. These features
provides a level of security against cloning and fraud.
Color Ringback Tone Instead of playing regular ringback tones from the MRF, the MSC can play Color
Ringback Tones (CRBTs) to the calling party from a CRBT Server. This feature
allows the called party to determine the ringback tone that is played to the
calling party.
Message Waiting Notification Message Waiting Notification (MWN) informs enrolled subscribers when a voice
(664-513-A) message is available for retrieval.
3 Way Calling (664-522-A) Three-Way Calling (3WC) provides the subscriber the capability of adding a third
party to an established two-party call, so that all three parties may communicate
in a three-way call.
Call Hold The customer can hold one call for any length of time provided that neither party
goes off-hook.
Call Transfer TIA/EIA 664-506 defines Call Transfer (CT). CT enables the subscriber to transfer
an in-progress, established call, to a third party. The call to be transferred may be
an incoming or outgoing call.
Malicious Call Trace Malicious Call Trace (MCT) enables a call recipient to mark a phone call as a
malicious call (for example, a threatening or obscene call). Once the call is
marked as malicious, the MSC generates a call trace that is available for further
investigation.

Voice Message Retrieval Voice Message Retrieval (VMR) permits a subscriber to retrieve messages from a
(664-523-A) voice message system (VMS).
Short Message Delivery The system supports Mobile Terminated and Mobile Originated short messages
Point-to-Point Bearer Service for both In-Call and Idle modes.
(664-601-A)
Over the Air Service The Over-the-Air Service Provisioning (OTASP) feature allows a potential wireless
Provisioning (664-533-A) service subscriber to activate (i.e., become authorized for) new wireless service,
and allows an existing wireless subscriber to make changes in existing services
without the intervention of a third party.
Roaming A subscriber can access wireless telecommunication services in areas other than
the one(s) serviced by the operator to which he has subscribed for service.
International roaming support was added in Release 4.5.3.
Service Provider Features

ISDN PRI Protocol Support The Q.930/Q.931 ISDN PRI protocols are supported to provide the signaling
protocol needed to establish, maintain and release circuit-switched connections
across an ISDN PRI network.
Channel Associated Signaling Multi-frequency R1 (MF R1) and Multi-frequency Compelled R2 Signaling System
(CAS) Protocol Support (MFC-R2) are supported in accordance with ITU Blue Book Volume V1 - Fascicle
VI.4 Recommendations Q.421-Q.242.
SS7 Protocol Support The following headings describe the SS7 signaling protocols supported on the
Star Solutions Sonata system.
ISUP Protocol Support

The ISDN User Part (ISUP) protocol is the main protocol responsible for
circuit-related functions, including setting up, managing, and releasing trunk
circuits carrying voice and data calls.
ISUP uses the Message Transfer Part (MTP) layers (MTP3/MTP2/MTP1) of the SS7
protocol stack to communicate with the PSTN. Within the Star Solutions Sonata
IP-based system, MTP3 uses the Internet Engineering Task Force (IETF) Signaling
Transport (SIGTRAN) standards M2UA / SCTP or M3UA / SCTP to transport MTP3
messages.
The Intelligent Media Gateway converts between the SIGTRAN layers (M2UA /
SCTP) and the SS7 layers (MTP2 / MTP1). The M2UA and SCTP layers allow ISUP
messages to be transported between the SS7 network and the IP network with
speed and reliability.
ANSI ISDN User Part (ISUP)

ISUP provides the ability to set-up, manage and release ISUP trunks. The
following ANSI ISUP standards are supported on the Star Solutions Sonata
system:
ANSI 88
Service Provider Features 37
ANSI 92
ANSI 95
ITU ISDN User Part (ISUP)

ISUP provides the ability to set up, manage and release ISUP trunks. The
following ITU ISUP standards are supported on the Star Solutions Sonata system:
ITU Q.762
ITU Q.763
ITU Q.764
ITU Q.730-733
ISUP Port Selection Optimization

The selection algorithm was optimized in release 4.5.2, decreasing the time it
takes the MSC to select a free port.
Concurrent ANSI / ITU ISUP support

ANSI and ITU ISUP standards can be supported on the same system.
Message Transfer Part (MTP) Level 3

MTP3 is the SS7 equivalent to ISO Network Layer. The following standards are
supported on the Star Solutions Sonata system:
ANSI 88
ANSI 92
ITU
ITU China variant (24 Bit Point Code)
Signaling Connection Control Part (SCCP)

SCCP provides the connectionless transport of TCAP messages.
Class 0 (Basic) and Class 1 (Sequenced) connectionless services and Class 2

(connection oriented) services are supported on the Star Solutions Sonata
system, including the following standards:
ITU 88
ITU 92
ITU 96
ANSI 88
ANSI 92
ANSI 96
SCCP-Lite
SCCP-Lite is the Star Solutions proprietary SCCP over IP protocol, used for
signaling between the MSC and BSC.

Transaction Capabilities Application Part (TCAP)

TCAP enables the deployment of IN and MAP services and supports non-circuit
related information exchange between signaling points using the SCCP
connectionless service.
The following TCAP standards are supported on the Star Solutions Sonata system:
ANSI 88
ANSI 92
ITU 96
SIGTRAN Protocol Support The following headings describe the SIGTRAN protocols supported on the Star
Solutions Sonata system.
M3UA (RFC 3332)

MTP3 User Adaptation Layer is used to access MTP3 (Message Transfer Part Level
3) functions using SCTP (Streaming Control Transmission Protocol) over IP. This is
typically used between a Signaling Gateway (SGW) and a Media Gateway
Controller (MGC) or between two IP-based applications.
The Star Solutions Sonata system supports the SIGTRAN M3UA protocol, such
that SS7 application messages can be packaged into M3UA messages and sent to
M3UA capable nodes, such as a Signaling Gateway Point (SGP), HLR, SMS-MC, or
another MSC. The MSC sends M3UA messages over SCTP to an M3UA node.
M2UA (RFC 3331)

MTP2 User Adaptation Layer is used to access MTP2 (Message Transfer Part Level
2) functions using SCTP (Streaming Control Transmission Protocol) over IP. This
protocol is typically used between a Signaling Gateway (SGW) and Media
Gateway Controller (MGC). It is assumed that the SGW receives SS7 signaling
over a standard SS7 interface using MTP2.
Stream Control Transmission Protocol (SCTP) (RFC 2960)

SCTP is a reliable transport protocol operating over IP. It provides acknowledged
error-free non-duplicated transfer of data. SCTP also detects data corruption, loss
of data and duplication of data by using checksum and sequence numbers. A
selective retransmission mechanism is applied to correct loss or corruption of the
data.
Media Stream Protocol The media stream protocols are responsible for the TDM and IP interfaces to the
Support Media Gateway. Voice and data calls access the mobile and fixed-line networks
through these interfaces.
Enhanced Variable Rate CODEC (EVRC)

EVRC is digital voice coding optimized for radio transmission in CDMA networks.
Real-time Transport Protocol (RTP) (RFC 3550)

RTP is an internet-standard protocol for the transport of real-time data, such as
voice. It Includes the Real-time Transport Control Protocol (RTCP).
For IP interconnections, the media stream, or payload, is determined by the

codecs that are mutually supported by either end. For example, Enhanced
Variable Rate Codec (EVRC) encoded calls are transported over the Real-time
Transport Protocol (RTP), User Datagram Protocol (UDP), IP, and finally Ethernet.
For TDM interconnections, the payload is encoded using Pulse Code Modulation
(PCM), the G.711 standard, and transported over E1/T1 to the PSTN.
RFC 3558 Support

RFC 3558 implements Standard Realtime Transport Protocol (RTP) Payload
Format for EVRC. This allows bundling of multiple CODEC frames into one RTP
packet, which can save bandwidth by sending fewer RTP packets and is often
useful for satellite links.
Normally one CODEC frame is sent every 20 ms resulting in 50 packets sent per
second. Two codec frames bundled into one packet results in only 25 packets per
second.
The packets must be destined for the same endpoint. There is not enough
information in the RTP packet or EVRC payload to split the CODEC frames and
send one frame to one endpoint and another frame to another endpoint.
To support RFC 3558, the Media Resource Function (MRF) on the Access Server
must be able to send out packets in RFC 3558 format. A new tool that is run
during installation and initial configuration detects whether the MRF files contain
Draft 7 or RFC 3558 format RTP packets. If they contain Draft 7 packets, the tool
converts the existing EVRC files from Draft 7 to RFC 3558 format.
Media Management Media management enables the negotiation of media characteristics, including
the codec, to be used when transferring media between gateways/BSCs. It does
this by allowing the creation of media profiles, each of which can be applied to
one of more trunk groups. The media control protocols supported are MGCP and
Megaco.
MGCP (RFC 2705)

MGCP is a protocol used for the delivery of information between Media Gateway
Controller (MGC) on the MSC and the Media Gateway (MGW). MGCP is an IETF
standard network control protocol characterized by a master-slave architecture
in which the call control intelligence resides outside of the gateway, in the MSC.
Megaco/H.248 (RFC 3015)

Megaco is a command-based protocol for the delivery of information between
Media Gateway Controller (MGC) and the Media Gateway (MGW).
Concurrent MGCP / Megaco

Concurrent MGCP / Megaco provides simultaneous support of MGCP and
Megaco for media control.

Session Initiation Protocol (SIP) (RFC 2543)

SIP is a signaling protocol for Internet conferencing, telephony, event notification
and instant messaging.
IP v4
IP v4 is supported.
MSC-BSC Interface The MSC-BSC interface conforms to the following CDMA Interoperability
Specifications (IOS):
IOS 2.x
IOS 3.1.0
IOS 4.01
MSC-VLR-HLR Interface The MSC-VLR-HLR interface conforms to the following Mobile Application Part
(MAP) specifications:
TIA/EIA-41B
TIA/EIA-41D
MSC-SMS-MC Interface The interface to a Short Message Service Message Center (SMS-MC) is supported
by the MSC in order to provide the Short Message Service (SMS) to mobile
subscribers.
Intersystem Handoff The Star Solutions Sonata MSC Server supports IS-41-D intersystem handoff. This
means that a mobile station can move from a cell controlled by one MSC to a cell
controlled by a different MSC without losing its connection. This is supported by
configuring clear-channel connections (inter-MSC trunks) between adjacent
MSCs.
Remote MSC Availability The remote MSC availability feature allows mobile subscribers who have
successfully registered in the VLR to make outgoing calls and accept incoming
calls even when connectivity to other network elements on the SS7 network is
lost.
In addition to maintaining service to post-paid subscribers, this feature allows

pre-paid subscribers to continue to make calls even when a pre-paid SCP is not
available, provided that they were successfully registered in the VLR before
connectivity was lost.
Inter-Working between -law The voice path between TDM trunks using A-law and -law is automatically
and A-law Encoded Voice converted.
Transcoder Free Operation Calls are supported that do not have transcoders in the media path between the
endpoints.
Inter-MSC IP Trunking Inter-MSC trunking allows signaling data to be sent over IP between Star
Solutions Sonata MSCs. The MSCs use the SIP protocol to exchange signaling
information. The signaling information is used to complete a call over IP between
a BSC/media gateway controlled by the originating MSC and a BSC/media
gateway controlled by the terminating MSC.
Direct SMS Delivery Direct SMS Delivery allows the service MSC to bypass the originating SMS-MC
and send the message directly to the terminating SMS-MC, which then sends it
back to the MSC. This is a global setting.
16-KHz Metering The 16-kHz metering feature allows the MSC to recognize calls coming from fixed
wireless terminals (FWT) in public call offices (PCO) and to provide the special
signaling that such FWTs require. The special signaling includes line control data,
which some equipment needs in order to start charging, and meter pulses, which
communicate the cost of the call.
Missed Call Alert The Missed Call Alert (MCA) feature enables the MSC (in the Originating/
Gateway MSC role) to notify an MCA server when the called party has the
handset switched off, does not respond to a page (is out of range), does not
answer, or is busy. The MCA server then informs the called party of the missed
calls by SMS. In addition, the MCA feature allows the O/G-MSC to play
announcements to the calling party based on the response from the MCA server
and to record call details.
Call Processing Features The following headings describe the call processing features supported by the
Star Solutions Sonata system.
Call Setup
Call originations can be detected and connections set up to the mobile station.
Call Progress and Treatment Handling

Call progression and treatment can be customized on a subscriber-by-subscriber
basis using feature sets in the subscriber class of service. Announcements can be
played for TDM and packet networks.
Alternate Routes for Destinations

Alternate routes allow a system to be programmed with a set of possible routes
to the final destination. The switch will try the most desirable route first and then
step through the list of alternate routes as needed.
Trunk Grouping
Trunks are organized into groups, and are selected for use based on a number of
selection algorithms (such as odd/even CIC, top-down/bottom-up, most recently
used, least recently used.).
Routing Control
A route to a destination can use multiple trunk groups, based on priority.
Toll Restriction / Classmark

Classmark is a designator used to describe the service feature privileges,
restrictions, and circuit characteristics for lines or trunks that access a switch.
Classes of Service
Subscribers can be organized into one of up to 512 different classes of service.
These classes of service define characteristics such as call originating capabilities,

routing capabilities, call progress, and treatment. The following headings

describe services based on class of service.
Class of Service Routing

Calls can be selectively translated and routed based on the caller's class of
service.
Class of Service Change Based on Call Information

The caller's class of service can be altered dynamically based on digit information
included in the call setup.
Class of Service Change Based on Collected Information

The caller's class of service can be altered dynamically based on digit information
collected from the caller during call setup.
Private Number Plan

Groups of caller can be assigned a unique numbering plan (based on class of
service).
Multiple Call Treatment Sets

Different call treatments can be offered to different callers (based on class of
service).
Translations
Translation Sets
Up to 6000 translation sets (rules) can be defined. A translation set is defined as a
specific interpretation of the meaning of a set of digit strings. The initial
translation set is selected based on the caller's class of service. The translation
class can is dynamic and can be changed based on digit information included in
the call setup.
Subscribers can be organized into Centrex groups or grouped such that some may
be required to do 10-digit dialing while others can do seven-digit dialing (for
example, to distinguish home versus roaming dialing).
Digit Manipulation
Call digit information can be stripped-off the front or the back, pre-pended or
appended, or completely re-written.
Digit Translations
Routing decisions can be made based on address information other than just the
dialed digits. The translation templates are applicable to calling digit buffers as
well as called.
Reconstruction of Call Information

All or part of the call digit information can be copied between digit buffers.
Enhanced Translation Pattern Matching

Call digit information can be matched based on fixed patterns and pattern
templates.
Defaults for Missing Call Information

Pre-provisioned call information can be used in cases where complete call
information is not available during call setup.
Voice Prompts and In-call DTMF Digit Collection

The MSC can be provisioned to prompt for and collect basic in-call DTMF digits
using the Media Resource Function (MRF) of the Access Server.
Prompt and Collect for Additional or Missing Call Information

Call information can be collected from the caller during call setup in cases where
complete call information is not available.
Call Routing Based on Prompted Call Information

Calls can be selectively translated and routed based on digit information
collected from the caller during call setup.
Nature of Address Routing

Calls can be selectively translated and routed based on the nature of address of
the caller's dialed digits.
Original Called Number Support

The original Called Number (OCN) can be relayed to another switching system for
forwarded calls.
Emergency Services Phase 1 The Star Solutions Sonata system supports Phase 0 and 1 of the FCC Emergency
(664-529-A) Call (E911) ruling. The E911 Emergency Service permits a subscriber to dial 9 - 1 -
1 - Send and be connected to a Public Safety Answering Point (PSAP) to request
an emergency response from the appropriate agency (e.g., fire, police,
ambulance, poison control center, or suicide prevention center). Emergency calls
are routed by the MSC regardless of whether the MS is able to authenticate.
Wireless carriers are required to provide the directory number of a wireless 911
caller and the cell site location to the PSAP. The PSAP shall be the PSAP
appropriate to the calling subscriber's current location.
Lawful Intercept - J-STD-025A Call Identification Conformance to US Justice Department requirements for law
(CALEA) enforcement monitoring of selected subscribers. Monitoring may be call
identifying or call content. Lawful Intercept on the Star Solutions Sonata system
provides access, delivery, and collection functions.
Wireless Intelligent The Star Solutions Sonata system supports WIN originating and terminating
Networking Pre-paid Service triggers for the Pre-paid service.
WIN Office Triggers - Originating (IS 826)

WIN originating office triggers define a point at which a call can be intercepted
and call control transferred to an SCP for call processing decisions. Trigger criteria
are based on a combination of who the originator is and the address digits. WIN
originating office triggers can be provisioned to support the Pre-paid service.

WIN Office Triggers - Terminating (IS 826)

WIN terminating office triggers define a point at which a call can be intercepted
and call control transferred to an SCP. Trigger criteria are based on the attributes
of the termination. WIN terminating office triggers can be provisioned to support
the Pre-paid service.
Mobility Management
Features
Authentication Authentication support enables the MSC and VLR to cooperate with an
Authentication Center (AC) in an effort to prevent fraud. The HLR incorporates
the AC and the MSC or VLR can be enabled to support authentication.
Authentication support requires authentication-capable mobile stations.
The Star Solutions Sonata system supports Global Challenge and Unique
Challenge. Mobile stations apply the cellular authentication and voice encryption
(CAVE) algorithm to a random number generated by the BSC in order to
authenticate.
The Star Solutions Sonata system supports shared secret data (SSD) sharing,
whereby the VLR can perform some of the ACs functions, relieving the AC of
processing load and reducing the SS7 signaling required.
Mobility Pre-translation These features are associated with the MSC's mobility functional application and
Features involve actions taken before a handoff would usually occur. The pre-translation
features include:
Allowing and denying the use of feature codes to mobile subscribers based on
the subscribers' OriginationIndicator (OI).
Validating forward-to numbers in feature requests to ensure that they are in
the same local area as the mobile station, and rejecting the feature request if
they are not.
Reconstructing forward-to numbers from local to national format before
sending the number to the HLR.
Playing announcements based on FeatureResult, when the AnnouncementList
is not provided.
Exempting pre-paid subscribers from charges when they originate toll-free,
emergency, and over-the-air service provisioning (OTASP) calls.
Applying a specialized treatment for calls to recharge a pre-paid voucher.
Over the Air Parameter The Over-the-Air Parameter Administration (OTAPA) feature is initiated by the
Administration network service provider at the Customer Service Center (CSC) to program the
Mobile Station's Number Assignment Module (NAM) parameters and the CDMA
Preferred Roaming list. These parameters control the wireless network usage by
the MS. Administration of such parameters without the involvement of mobile
subscribers simplifies and significantly improves the customer care process by
network service providers.
Operations and Maintenance Features 45
Operations and
Maintenance Features
Online Provisioning This feature enables online provisioning of Star Solutions iCell BSC and ISUP
resources at the MSC, such that these tasks can be performed without stopping
the system.
Billing Features Centralized Billing Generation Point

Call detail records (CDR) for a number of network elements can be generated at a
single point in the network.
Call Detail Record Generation

CDRs are generated for each call attempt including the details of the originating
and terminating call legs, timestamps for origination, answer and disconnect, and
the call attempt outcome (such as successful, busy, no answer, and other events).
Call Detail Record - Multiple Call Forward

In real time a dialed or forwarded call may involve multiple parties and may
transit through multiple switches before actual termination. From a billing or
rating perspective it is necessary to accurately identify the parties to whom the
call should be charged.
Selective Call Trace The selective call trace tool allows the operator to collect debug information for
software modules using specific parameters, such as the Mobile Identification
Number (MIN), Mobile Directory Number (MDN), or port.

SYSTEM DESCRIPTION
3
This chapter provides a description of the Star Solutions Sonata system.

Core Voice Network Components
Star Solutions Sonata SE Mobile Switching Center Server
Star Solutions Sonata Signaling Server
Star Solutions Sonata Intelligent Media Gateway
Star Solutions Feature Server Home Location Register / Authentication Center
Star Solutions Sonata SE Access Server
Star Solutions Sonata SE Call Conference Server
Star Solutions Sonata SE Lawful Intercept Server
Star Solutions Sonata Operations and Maintenance Center
Ethernet Switch
The Serial Port Server provides LAN access to all the Star Solutions equipment
in the chassis or cabinet. The Serial Port Server has 24 RS-232 serial ports,
which provide up to 230 Kbps connection speed per port.
Core Voice Network The Star Solutions Sonata Core voice network products include:
Components
Star Solutions Sonata SoftExchange Mobile Switching Center (MSC) Server
Visitor Location Register (VLR) Functionality
Star Solutions Sonata SoftExchange Signaling Server (SSVR)
Star Solutions Feature Server Home Location Register (HLR)
Authentication Center (AC) functionality
Star Solutions Sonata SoftExchange Access Server
Star Solutions Sonata SoftExchange Call Conference Server
Star Solutions Sonata SoftExchange Lawful Intercept Server
Star Solutions Sonata Intelligent Media Gateway (IMG)
Star Solutions Sonata Operations and Maintenance Center (OMC)
Star Solutions Sonata SE The MSC provides convergence of voice and data services over a single IP
Mobile Switching Center infrastructure. This scalable softswitch for wireless networks includes call
Server processing and mobility software.

48 Chapter 3: System Description
Core Applications The MSC supports discrete core applications that run independently and perform
well-defined functions. Core functional applications are the building blocks from
which the Mobile Switching Center (MSC) application and Home Location
Register (HLR) application are constructed.
The MSC supports the following core applications or services:

Call Processing Engine (CPE)
Mobility Management (MOB)
Common communications protocol services (CONX)
SNAP proprietary application for PRI / R2
Operations and Maintenance interface (OAM)
Figure 8 shows the core applications (other than OAM) in the MSC and the
following headings describe each application or service.
Figure 8 MSC Core Applications
NAPI
Mobility Call SNAP

Processing
CONX
MAP
TCAP ISUP
SCCP
MG SIP
MTP3
M2UA
SCTP
HI/TUCL
IP
IOS MAP ISUP MGCP/Megaco SIP to TPNCP to

A-interface to Signaling to Signaling to BSC/Media MRF/Call Media
to BSC Gateway Gateway Gateway Conf Server Gateway
Call Processing Engine

The Call Processing Engine (CPE) provides call processing functions, service
control functions, digit analysis, and routing features. It has no mobility-specific
Star Solutions Sonata SE Mobile Switching Center Server 49
functions; mobility-specific functions and mapping are entirely within the

domain of the MOB core application.
The CPE:
Routes calls, provides digit analysis and translation, and provides call features.
Manages ports and connections, and the relationship between logical
facilities and physical ports/trunks. It ensures that the switching is in a
consistent state and establishes voice paths.
Provides media gateway control for basic call setup and call release, call
waiting, call holding, conference calling, tone enhancement, high availability
and redundancy, and online provisioning.
Provides the set of functions required for interaction between the service
layer and the control layer. These functions include voicemail, lawful
intercept, and intelligent networking.
Mobility Management
The Mobility Management (MOB) functional application comprises the MSC,
Visitor Location Register (VLR), and Home Location Register (HLR).
MOB is responsible for all aspects of mobility control in the MSC, which are
required to provide voice and data services to mobile equipment, including:
Mobility management which performs identity procedures, encryption, and
authentication.
Call management which provides call origination and termination services.
Location management services which are forwarded to the VLR to be
processed.
VLR services.
These functions are commonly known as the MSC and VLR functions.
MOB provides VLR functionality for mobiles in the coverage area. When a mobile
roams into the MSC/VLR area, location services are forwarded from the mobile
through the MSC functions to the VLR function. MOB retrieves the subscriber
profile from the subscriber's HLR and stores it in the VLR for future reference. The
VLR then updates this information when instructed by the HLR.
The call management procedures use the subscriber information in the VLR to
interwork with CPE, which provides the actual call services,
MOB also provides:

Base station and radio access network management
Signaling control
Location area management
Call management protocols between the core network and user equipment.

Figure 9 illustrates the MOB functional application.

Figure 9 MOB Functional Application
Common Services (CONX)

The protocol layers provided by Common Services (CONX) are:
SS7 protocol: MTP3, SCCP, TCAP, MAP, and ISUP layers
SIGTRAN protocol: M3UA, M2UA, and SCTP layers
TUCL: proprietary TCP/UDP Convergence Layer
SIP
MGCP, Megaco
CONX does not provide any of the IP-based transport protocols such as IP, UDP or
TCP. These are functions of the UNIX operating system.
The SS7 link level protocols MTP2 and MTP1 are provided by the signaling
gateway on the Intelligent Media Gateway (IMG).
SNAP
PRI and CAS R2 trunk setup requires communication between the MSC Server
and the Media Gateway (MGW) function on the Media/Signaling Gateway, using
the proprietary TPNCP interface. The TPNCP interface is available via an internal
proprietary call processing entity called SNAP.
Operations and Maintenance interface

The Operations and Maintenance (OAM) functional application provides an
interface to the OMC. The OMC is responsible for collecting and storing
performance information, alarm records, and accounting records, and managing
configuration data and security.
Star Solutions Sonata SE Mobile Switching Center Server 51
Media Gateway Control The Media Gateway Controller (MGC) is software in the MSC Server that supports
the Media Gateway. It conforms to the MGCP media gateway control standard.
Its capabilities include:
Resource control
Connection management
Media processing control
Signal and event processing
Statistics reporting
Provisioning
Resource Control
The resource control capability provides these functions:
Allocates and de-allocates bearer terminations and media resources for use
by a particular call.
Retrieves the status of resources in the Intelligent Media Gateway.
Specifies the resources required for a call or specifies the media gateway from
a resource pool.
Connection Management
The connection management capability provides these functions:
Establishes connections involving packet and circuit bearer terminations in
any combinations. The bearer terminations may be TDM or Ethernet.
Supports the establishment of uni-directional, symmetric bidirectional,
asymmetric bidirectional, point-to-point, and point-to-multipoint flows of
different media types such as audio, text, and video.
Allows the addition or subtraction of one or more media streams to a
connection (as required) during a call.
Media Processing Control

The media processing control capability provides these functions:
Specifies the media transformation parameters for each media stream that is
part of a call. This includes transformation, such as the adaptation of flows
between different types of transport, mediation of flows between different
stream contents, and so on.
Specifies the specialized media processing that is executed on a media stream,
such as echo cancellation, tone detection, silence suppression, -law or A-law
companding, and so on.
Specifies any media insertion that is executed on a media stream such as
playing announcements, or media extraction operations such as DTMF
detection, modem or fax termination, and so on.
Signal and Event Processing

The signal and event processing capability provides these functions:
Specifies the events to be monitored or the signals to be applied by the
Gateway on a particular media stream of a call.

Receives notification of detected events from the Gateway.

Specifies the actions taken by the Gateway when an event occurs, and
specifies when a signal applied to a stream needs to be removed.
Specifies the collection of dialed digits in accordance with a dialing plan.
Statistics Reporting
The statistics reporting capability collects and requests statistics gathered during
a call, such as the volume of content carried, QoS statistics, the duration for
which the media stream was active, and so on.
Provisioning
The provisioning capability provides these functions:
Places the facility (for example, the E1/T1 span) in-service or out-of-service
Receives notification from the Gateway of any hardware failure
Remotely configures the hardware facility at the Gateway
Remotely monitors the status of the Gateway
Protocol Layer Management The MSC has a protocol service that manages, controls, and monitors the
condition of each protocol layer. The protocol service also provides the necessary
functions to configure default parameters used by each protocol layer.
The protocol layer management interface provides a set of primitives to

configure the protocol service including:
Activating and deactivating protocol layer resources
Configuring protocol layer resources
Determining traffic loads and quality of service for the protocol layer
Indicating the current state of the protocol layer
Indicating state change or abnormal conditions in the protocol layer
Sending trace information of all messages received and transmitted towards
the network
Star Solutions Sonata The Signaling Server node is included in some configurations of the core voice
Signaling Server network to offload the Signaling Server application from the MSC and HLR.
The Signaling Server application provides the SS7 and SIGTRAN protocol
functionality for the Sonata product. It provides the means for transporting SS7
application messages (ISUP, MAP, INAP, TCAP) from the IP-based MSC Server and
HLR within an IP network. The Signaling Server application is concerned only with
processing SS7 and SIGTRAN messages - not with media control or voice traffic.
Release 4.5.2 introduces a new, optional, Signaling Server node (SSVR). The
Signaling Server application and protocol layers that make up the SS7 and
SIGTRAN protocol stack may exist in the MSC and HLR or be distributed across
the MSC Server (MSC), HLR, and SSVR, depending on the capacity and
requirements of the network.
Star Solutions Sonata Signaling Server 53
The Signaling Server application can function in simplex or active-standby

configurations. The various configurations of the Signaling Server application are
described in detail in the Signaling Server Application Guide.
Signaling Protocols Signaling takes place through a system of protocol layers, the architecture of
which adheres to the Open System Interconnection (OSI) reference model. The
IETF SIGTRAN class of protocols provides for the transport of SS7 messages within
an IP network. The Stream Control Transmission Protocol (SCTP), the MTP2-User
Adaptation Layer (M2UA), and the MTP3-User Adaptation Layer (M3UA), are
SIGTRAN protocols. The TCP/UDP Convergence Layer (TUCL) is a proprietary
protocol for transporting SIGTRAN over UDP/IP.
Signaling Server The SS7 transport layers (MTP3 and below) can be separated out from the MSC
or HLR application on the MSC or HLR and installed in a separate account on the
MSC and/or HLR or wholly in the Signaling Server (SSVR). The Signaling Server
node (SSVR) is an optional node introduced in Release 4.5.2. When included in
the configuration, the SSVR offloads the MSC and/or HLR, providing SS7 transport
layer (MTP3) services for the MSC and/or HLR, and facilitating communication
between the MSC and the Signaling Gateway, as shown in Figure 10. In the case
shown, the Sonata Intelligent Media Gateway (IMG) incorporates the Signaling
Gateway.
Figure 10 Position of the Signaling Server Node

MSC Mobile Switching Center
MSC SSVR Signaling Server
Server IMG Intelligent Media Gateway
BSS Base Station Subsystem
IOS 4.x (A1)

SCCP-Lite ISUP, MAP, INAP, TCAP
UDP
MGCP MGCP SSVR

UDP UDP
MTP3/M2UA/
SCTP/UDP
ISUP-MAP SS7
MTP/DS0
CDMA BSS Voice/RTP/UDP IMG
G.711/DS0 PSTN
The MSC and SSVR communicate using M3UA. The SSVR and Signaling Gateway
communicate using SIGTRAN.
Active-Standby Configuration The Signaling Server configurations are covered in detail in the Signaling Server
and Signaling Server Application Guide. The Active-Standby configuration is
discussed here as an example.
The Active-Standby configuration consists of 4 servers: an active MSC, a standby

MSC, an active SSVR, and a standby SSVR. Figure 11 shows the Active-Standby

MSC and SSVR configuration. Within each active/standby pair, each server has its
own permanent management IP address, but shares a functional IP address with
its peer.
Figure 11 Active-Standby MSC and SSVR Configuration
MSC (Active) MSC (Standby)
msc msc
MAP MAP
TCAP ISUP HWD TCAP ISUP
SCCP SCCP
M3UA M3UA
SCTP SCTP
SS7
M3UA M3UA
M2UA Signaling M2UA
Gateway
SCTP SCTP
M3UA M2UA M2UA M3UA
HWD
MTP3 MTP3
pro NIF pro NIF
SSVR (Active) SSVR (Standby)
For information on the active-standby MSC, refer to the MovingMedia2000 MSC

Server Operations and Maintenance Guide.
The active-standby configuration protects against the following situations, by

providing failover from the active to the standby SSVR:
Software application failure
Power loss
UNIX operating system failure (lock up, panic, overload)
Disk failure
Loss of communication to/from the active or standby hosts resulting from
failure of the network
Failover is managed by the RAFT hardware daemon (HWD) in conjunction with

the proprietary Habitat CPU_PM (peer_mon).
M3UA Support The Star Solutions Sonata system supports the SIGTRAN M3UA protocol. Refer to
SIGTRAN Protocol Support in Chapter 2, System Features for more information.
Signaling Gateway The Signaling Gateway (SGW) joins the IP and SS7 networks. The nodal
interworking function (NIF) on the SGW converts from M2UA to MTP2 and vice
versa. This IP-SS7 conversion allows IP-based devices, such as the MSC, to
communicate with the SS7 network.
Star Solutions Sonata Intelligent Media Gateway 55
Refer to the Star Solutions Sonata Intelligent Media Gateway, Signaling Gateway
Functionality section in this chapter for more information on the Signaling
Gateway.
Example 1 Signaling Server Application - Messaging

In a configuration that includes a separate or resident (on the MSC) Signaling
Server application, the MSC wishes to send an ISUP message to an MSC in the SS7
network:
The MSC sends an ISUP message to the SSVR using M3UA.
The SSVR packages the ISUP message into an MTP3 package using an NIF and
sends it using M2UA/ SCTP / TUCL / UDP / IP to the Signaling Gateway.
The Signaling Gateway uses an NIF to convert the MTP3 / M2UA package to
MTP3 / MTP2 / MTP1 and sends the message in a T1/E1 timeslot (DS0) into
the SS7 network.
Figure 12 illustrates this messaging example.
Figure 12 Signaling Server Application Messaging for Example 1
MSC
msc
SSVR
MAP
TCAP ISUP
pro SGW
SCCP NIF NIF
MTP3
M3UA M3UA
M2UA M2UA MTP2
SS7
SCTP SCTP SCTP MTP1
M3UA M2UA MTP
Star Solutions Sonata The Intelligent Media Gateway (IMG) mediates the voice stream and provides an
Intelligent Media Gateway SS7 signaling interface between the traditional TDM, PCM-encoded PSTN and the
packet IP network.
The IMG is controlled by the Media Gateway Controller software module in the
MSC Server.
Media Gateway Functionality The Media Gateway in the IMG performs voice mediation and vocoding,
including media initialization procedures and vocoding schemes, such as
Enhanced Variable Rate Codec (EVRC) and G.711 PCM.
The Media Gateway provides voice-processing services such as echo cancellation,

voice encoding, voice and tone signaling discrimination, voice activity detection,
and voice, data, and fax discrimination.

Signaling Gateway The Signaling Gateway in the IMG provides signaling interworking that conforms
Functionality to SS7 and Internet Engineering Task Force (IETF) Signaling Transport (SIGTRAN)
standards.
The signaling functionality transports narrowband SS7 messages received from

the circuit-switched PSTN on incoming E1/T1 spans, and also transports SCCP-Lite
messages from the Base Station Controller (BSC). The Signaling Gateway
transports the signaling over IP to the MSC, using SIGTRAN M2UA over SCTP/IP.
The Signaling Gateway on the IMG joins the SS7 network to the IP network,
allowing IP-based devices, such as the MSC and HLR, to send messages to the SS7
network. (SS7 messages may be sent on behalf of the MSC, via the SSVR,
depending on the network architecture.) For the MSC Server to send an SS7
message to a signaling endpoint (SEP), such as a home location register (HLR), the
message is carried over MTP3 / M2UA / SCTP / IP to the Signaling Gateway
(within the IMG), which converts the message to use MTP3 / MTP2 / MTP1, and
sends the message in a E1/T1 timeslot (DS0).
E1/T1 Interface An IMG supports as few as two T1 / E1 spans or as many as 15 T1 / 12 E1 spans

per board and up to 15 boards per chassis with a high availability n+1
configuration.
Each Gateway card is powered by two VoIP processor modules. Each processor
module can be configured an independent gateway controlling eight trunks at
the back of the chassis.
The 1610 RTM (Rear Transition Module) is used to provide a rear transition I/O
module with E1 or T1 trunks for TDM transmission, and two redundant
10/100Base-T Ethernet interfaces for IP transmission. Each 1610 module has an
associated E1/T1 RTM connected to the mid-plane of the chassis.
Star Solutions Feature The Home Location Register (HLR) / Authentication Center (AC) has four major
Server Home Location components:
Register / Authentication Home Location Register (HLR)
Center
HLR SIP Gateway (HSG)
Authentication Center (AC)
Signaling Server
The HLR/AC can be configured to run as:

Standalone, on its own server
Co-resident with the MSC Server
Home Location Register The HLR is the central repository for a provider's subscriber data. it stores data
relating to the services and features available to each subscriber as well as their
location. Each subscriber's data is stored in only one HLR, and one HLR can serve
multiple MSCs.
Star Solutions Sonata SE Access Server 57
The HLR validates subscribers, allowing for their subscribed features to "follow"
them, and for subscribers to be charged, while they roam. The HLR tracks the
location of each subscriber so that it can direct incoming calls to the MSC
currently serving the subscriber.
HLR SIP Gateway The HLR SIP Gateway (HSG) enables the HLR to respond to INVITEs from a SIP
proxy. To the SIP proxy, the HSG appears to be a SIP redirect server. To the HLR
application, the HSG appears to be a Gateway MSC.
Authentication Center The AC manages the authentication information for subscribers. It generates
authentication keys for use in the authentication process between the mobile
station and the network.
The AC also executes an authentication algorithm based on information about a

subscriber provided by the HLR. This ensures the phone is authenticated, helping
to prevent fraud.
Star Solutions Sonata SE The Access Server contains the media resource function (MRF) which streams
Access Server tones and announcements to clients requesting this service. The MRF is a
software-based media server delivering rich tones and announcements. It
delivers pre-programmed tones and pre-recorded information messages natively
in the IP network using open interfaces. The MSC commands the MRF to play the
specified announcements or tones. Figure 13 shows the Access Server (AS) in the
network.
Figure 13 Star Solutions Sonata Network
When a mobile user makes a call, the MSC requests the MRF on the Access
Server to play the ring-back tone. If the called party is busy or for some reason
the call cannot be connected, the MRF, under the control of the MSC, will play a
specific tone or announcement. Since tones and announcements are streamed
using native coding schemes, no transcoding is required in the network.

Tones appear the same as announcements to the MRF.
The MRF has the following announcement capabilities:

Plays a single announcement or chain of announcements
Plays for a specified number of repetitions
Plays codec-specific announcements
Supports language and locale specific announcements
Includes standard Pre-paid announcements
The MRF has the following tone capabilities:

Plays continuous and cadenced tones
Plays for a specified number of repetitions
Plays codec-specific tones
Includes all standard tones
The MRF supports the following codecs:

EVRC
GSM
G.711 A-law (PCMA)
G.711 mu-law (PCMU)
The MSC requests tones and announcements from the Access Server using the
SIP protocol. One Access Server can support one or more MSCs. The media
streaming for the tones and announcements from the Access Server MRF is
shown in Figure 14.
Figure 14 Access Server Media Streaming
MSC
SIP signaling
(media control)
AS
CDMA
over RTP TDM

over RTP
Media streams
PSTN
MS BTS BSC GW
Capacity The Access Server supports the following service request, media session, tone,
and announcement capacities:
Processes 60,000 busy-hour service requests
Completes 54,000 busy-hour service requests
Up to 1000 MRF files, each used for an individual tone or announcement with
a particular codec. An announcement may consist of a single word or phrase.
Four codecs are supported: GSM, PCMA (A-law), PCMU (Mu-law), and EVRC.
Star Solutions Sonata SE Call Conference Server 59
The number of concurrent tones and announcements sessions is dependent on

the hardware. Refer to the customer-specific hardware and engineering details
for the maximum supported sessions.
Tone / Announcement Files The default configuration has 219 pre-loaded tones / announcements, each with
4 codecs, for a total of 876 MRF files. This leaves space for 124 custom MRF files
(1000 - 876). If all four codecs are used, this translates to 36 custom tones /
announcements.
For customers that only require two codecs (e.g. EVRC, PCMU), additional custom
tones / announcements can be made available. Without affecting the default
MRF files, the 124 custom MRF files can be used for 64 tones / announcements. If
additional custom tones / announcements are required, the default MRF files for
the two unused codecs can be reused for an additional 219 custom tones /
announcements, for a total of 281.
In summary, the maximum MRF capacity currently supported is:

Four codecs - 250 tones / announcements (219 default, 36 custom)
Two codecs - 500 tones / announcements (219 default, 281 custom)
Star Solutions Sonata SE The Call Conference Server works in conjunction with the MSC server to provide
Call Conference Server network support for three-way voice calls.
The MSC communicates with the Call Conference Server via SIP. The MSC passes
control of the three ports in the three-way call to the Call Conference Server. The
Call Conference Server uses RTP to the IMG or BSC to stream and mix the voice
for the three parties.
The Call Conference Server supports a basic three-way call where:

Party A (originating caller) calls party B, places party B on hold, calls party C,
then conferences parties B and C together.
During an active three-way call, if party B or party C disconnects, party A and
the other party remain connected.
During an active three-way call, if party A disconnects, parties B and C are also
disconnected.
Call Conference Server features include:

Use of SIP to communicate with the MSC for media control
Compliance with SIP RFC 3261
Interoperability with a MSC via two 10/100 Base-T Ethernet Interface
connections
Use of an internal SIP Routing Table
Support of the following SIP methods:
INVITE
CANCEL
BYE

ACK
REGISTER
OPTIONS
INFO
REFER
NOTIFY
PRACK
SUBSCRIBE
re-INVITE
Star Solutions Sonata SE Lawful intercept is defined by ANSI J-STD-025-A "Lawfully Authorized Electronic
Lawful Intercept Server Surveillance" to provide legal interception of communications (call content) and
call identifying information (CII). Release 4.5.2 supports Phase II of this standard.
The lawful intercept service allows a service provider to intercept call identifying
information (CII) and/or call content and provide the information to a law
enforcement agency (LEA).
The lawful intercept architecture utilizes:

An access function (AF) which accesses the call information from a targeted
subject. The AF includes a Lawful Intercept Server (LIS) and an Intercept
Access Point (IAP).
A delivery function (DF) which delivers call information to a law enforcement
agency (LEA).
A collection function (CF) at the LEA which collects the information.
A service provider administration function (SPAF) which controls the
surveillance function.
The intercept subject / target is a telecommunications service subscriber in a

defined intercept area, whose communications, call-identifying information (CII),
or both, have been authorized by a court to be intercepted and delivered to an
LEA. The identification of the target is limited to the particular equipment,
facility, or communications service (e.g. network address or terminal identity
subscription identity).
Information collected about a target's calls includes abandoned and incomplete

call attempts and calls that are redirected (e.g., diverted, forwarded, or
deflected) by the intercept subject's equipment, facilities, or services.
In order to perform lawful intercept:

1 The service provider provisions a target, using the SPAF, and flags it for
interception of either CII and/or call content.
2 The SPAF sends the target information to the LIS, which stores it and relays the
information to the intercept access point.
Star Solutions Sonata SE Lawful Intercept Server 61
3 When a call is made which involves the intercept target, the IAP sends the CII to
the LIS which sends it on to the DF. If call content has been flagged for this target
the IAP negotiates where the BSC should send the RTP stream.
Sonata Lawful Intercept The access function (AF) is provided by the Star Solutions All-IP CDMA2000
Network product. The AF consists of: the Lawful Intercept Server (LIS), intercept access
point (IAP), and media gateway controller (MGC).
The intercept access point (IAP) is implemented in the Star Solutions product
within the lawful intercept agent (LIA) component of the MSC. When the MSC
includes the IAP, it is referred to as an MSC-LIA. The MSC-LIA is the point where
the communications or CII of a target are accessed. The MSC-LIA performs the
following functions:
Maintains a copy of the intercept target list in memory which is synchronized
with the LIS target database in real time.
For calls that trigger lawful intercept, the MSC-LIA sends the CII to the LIS
which then sends it to the DF.
If the target is flagged to intercept call content as well, then the MSC-LIA
sends a message to the DF via the LIS to negotiate where to send the call
content. The MSC-LIA informs the Base Station Controller (BSC) of the
destination for the call content, and during interception the BSC sets up an
RTP stream to the designated DF.
The Lawful Intercept Server (LIS) is implemented as a separate server and acts as
a mediation server between the MSC-LIA and SPAF and the MSC-LIA and DF. It is
implemented in the Star Solutions product as a separate server. The LIS is
responsible for:
Storing the list of intercept targets.
Relaying administrative messages from the SPAF to MSC-LIA.
Delivering CII (such as calling number, called number, and timestamps) from
the MSC-LIA to the DF.
There are no changes to the MGC in Release 4.5.3.
Figure 15 shows the Moving Media 2000 lawful intercept architecture.

Figure 15 Lawful Intercept Network Architecture
In summary, the Lawful intercept service requires a Mobile Switching Center

(MSC) with Lawful Interception Agent (LIA) and a Lawful Intercept Server (LIS).
The server accommodating the MSC and LIA is known as the MSC-LIA.
In a network that supports lawful intercept, lawful intercept is triggered by one of
the following conditions:
A soft switched call is originated from, terminated to, or redirected by the
target.
An SMS transfer is requested - either originated from or terminated to the
target.
Star Solutions Sonata The Operations and Maintenance Center (OMC) is an element-management
Operations and system that handles configuration and provisioning, alarm tracking, and
Maintenance Center performance analysis for the Sonata family of products.
The OMC is a standardized, scalable, and comprehensive solution for centralized

element management of all the distributed systems and components. The OMC
interfaces to higher layer Operational Support Systems (OSSs) using the Common
Object Request Broker Architecture (CORBA) interface.
The OMC consists of a UNIX server running the Solaris 8 operating system, and a
client. The client can be a Windows or UNIX workstation, or X Terminal, running
an Internet browser application. The operator uses a web-based user interface
on the Windows client to view network alarms, performance statistics, and
accounting information, configure the network, and manage security.
Star Solutions Sonata Operations and Maintenance Center 63
OMC Server and Client The OMC runs either standalone or on the File Server. The software is made up of
two components: OMC Server and OMC Client. The OMC Server runs the same
operating system (Solaris 8) as the MSC Server. The OMC Client is a Java-based
application that can run on both Solaris and Windows platforms.
The OMC installation has the following requirements:

OMC Server-Sun server or workstation running Solaris 8
OMC Client-UNIX workstation, X terminal, or PC workstation running
Windows NT or Windows 2000, with Netscape 4.7 or higher, or Internet
Explorer 5.0 or higher
Star Solutions installs and configures the operating system and software before
shipping the OMC. For site-specific installation and configuration information,
see the Engineering Document for your system.
Figure 16 OMC Interactions
OMC Server
The installation of the OMC Server consists of the following components:
Web Server software - uploads the OMC Client each time it is launched from
the client's web browser.
OMC Server software - collects, forwards, and validates data being exchanged
between Sonata network elements and the OMC Client.
LDAP (Lightweight Directory Application Protocol) Server software - stores
configuration data and manages user names and passwords for the OMC.
OMC Client
Although the OMC consists of both the server and client software, no manual
installation of software is required on the OMC Client.
The OMC Client is downloaded from the OMC Server through a web browser. It is
installed the first time you access the software. When there is a new version of
OMC Client, you are prompted to upgrade.

The connections between network entities use standard communications

protocols.
OMC Architecture The OMC is designed in accordance with ITU-TMN (Telecommunications

Management Network) standards. The OMC resides in the element management
layer of the TMN management model (TMN M.3400). The TMN architecture is a
reference model for a hierarchical approach to telecommunications
management.
Figure 17 shows where the OMC fits into the TMN model.
Figure 17 Position of the OMC in the TMN Model
The OMC also conforms to the ITU-T categorization of network management

systems called FCAPS (Fault, Configuration, Accounting, Performance, and
Security Management). Each layer of the TMN architecture performs different
FCAPS tasks. Figure 17 shows the FCAPS tasks associated with the OMC at the
element management level.
Functions The key functions of the OMC are southbound and northbound mediation, data
storage, network element interfaces, and user interface functions. Figure 18
shows the OMC architecture.
Star Solutions Sonata Operations and Maintenance Center 65
Figure 18 OMC Architecture
Southbound Mediation
Southbound mediation is communication between the OMC and network
elements such as the MSC Server and Intelligent Media Gateway. The
southbound mediation function collects alarms, statistics, and billing
information, and exchanges configuration data with the managed elements.
Data Storage
The OMC maintains persistent storage of active alarms, performance statistics,
and configuration information. The data schema, along with configuration and
data access procedures, is designed to interoperate with external network
management systems and OSSs.
Network Element Interfaces

DRUM
The OMC interfaces to Sonata servers through the Distributed Resources Unified
Manager (DRUM) framework. Applications such as the call processing engine,
mobility manager, protocol layers, and Home Location Register (HLR) invoke

DRUM services that send and receive management data through an application
programming interface (API). The API communicates with DRUM using TCP/IP
sockets.
SNMP
For the Intelligent Media Gateway and other non-core network elements, the
OMC supports a collection of fault, configuration, and performance information
via a standard SNMP v2c interface.
FTP
File Transfer Protocol (FTP) interfaces are used to transfer periodic performance
statistics and call detail records in XML format from the DRUM to the OMC.
Telnet
A Telnet interface provides reachthrough, or remote access to the local
maintenance terminal to some Sonata system components. A Command Line
Interface (CLI) provides view-only access to system status and configuration.
Northbound Mediation
Northbound mediation is the communication between the OMC and external
operations support systems (OSSs). Alarm data is aggregated to provide a single
northbound feed via TCP/IP to an external fault management system. A CORBA
interface provides configuration and fault data.
Fault Management Fault management is the ability to monitor alarms, locate faults, and take
corrective or preventative actions that assure network and service availability.
The OMC provides centralized monitoring of network alarms and events,

allowing rapid isolation, diagnosis, and recovery of problems that can impact
network services.
The OMC supports asynchronous reporting (ITU-T X.733) of the following

communication or protocol alarms:
Quality of service (QoS) alarms
Software processing errors
External equipment failures
Environmental enclosure alarms
The OMC Client lets you monitor faults reported by network elements and
managed objects in near real time. OMC Client dynamically updates the list of
alarms in the Active Alarms Display, which includes essential information such as
network element identifier (ID), the alarm severity, time of occurrence, alarm
description, probable cause, and acknowledged state.
The alarms are categorized into critical, major, minor, warning, or indeterminate
(informational), with pre-defined colors for each level. Once you acknowledge an
alarm, the alarm's icon changes to indicate that the alarm has been
acknowledged. The alarm is updated with your user name, and the time of
acknowledgement.
Ethernet Switch 67
Operators can also manually clear single or multiple alarms once problems have
been fixed. Since up to 10 users may be accessing the OMC Client at one time,
synchronization of all alarm displays occurs automatically. Alarms are updated to
the display at an aggregate rate of two alarms per second.
Configuration Management
A set of configuration management capabilities is also provided to simplify
network provisioning and enable rapid service activation and deployment.
The OMC presents a hierarchical view of the network and its elements. All system
configuration data is centrally stored and administered through an LDAP
Directory Server.
Accounting Management
To facilitate billing, pricing, and setting of tariffs for services, the OMC aggregates
and processes call detail records (CDRs) for the MSC Server and feeds the data to
upstream billing systems. Open northbound interfaces enable operators to
integrate with upstream back-office and front-office operational support systems
(OSSs) and operational processes.
CDRs are collected and stored by the OMC in XML format for easy export by FTP
to external billing systems. The OMC supports CDR volumes of 360,000 Busy
Hour Call Attempts (BHCA).
Performance Management
The OMC performance management capabilities include statistics graphing and
reports to help you optimize network resource usage and quality of service. The
OMC provides basic performance statistics such as system health, call processing
and mobility management status for Sonata system components. Performance
statistics are collected at 5-minute intervals.
Security Management
Access to OMC tools and reports is protected by user name and password. The
user authentication is performed on the LDAP directory server, where all user
access privileges are stored and administered.
Only valid users can log on to the OMC and use the fault management,
performance management, configuration management, and security
management tools.
Ethernet Switch Sonata uses an IP packet network to provide interconnections between

peripherals within the system. An Ethernet switch provides the mechanism to
switch packets from the source to destination interfaces.
Depending on the hardware configuration, the Ethernet switch may be a

horizontal rack-mountable platform or a CompactPCI blade.

Serial Port Server The Serial Port Server provides LAN access to all the Star Solutions equipment in
the chassis or cabinet. The Serial Port Server has 24 RS-232 serial ports, which
provide up to 230 Kbps connection speed per port.
SONATA SYSTEM TECHNICAL SPECIFICATIONS
4
This chapter summarizes the technical specifications for the Sonata system.

Sun Microsystems Netra Processors
Compact PCI (cPCI) System
OMC Server
Call Conference Server
Ethernet Switches
Additional Hardware
Sun Microsystems Netra All Core Voice Network elements may be configured to operate on the NetraTM
Processors family of servers from Sun Microsystems, with the exception of the Intelligent
Media Gateway and the Call Conference Server. For NetraTM server technical
specifications, refer to the appropriate Sun Microsystems documentation.
For Intelligent Media Gateway technical specifications, refer to the appropriate

Audiocodes documentation.
For Call Conference Server technical specifications, refer to Call Conference

Server on page 70.
Compact PCI (cPCI) System The MSC Server, Access Server, and Intelligent Media Gateway can be configured
as a low-capacity, simplex system in a compact PCI (cPCI) chassis. For complete
information on the cPCI System option refer to the cPCI System Installation and
Initial Configuration Guide.
Appendix A of the cPCI System Installation and Initial Configuration Guide

includes the technical specifications for the cPCI chassis, the MSC Server, HLR,
and Access Server card set, the mirrored drives, and the signaling and media
gateway cards.
OMC Server The OMC is installed as a rackmount server. The client platform can be
X-Terminals that run off the OMC server, or standalone Windows-based PCs.
The OMC platform is designed for 99.99% high availability. Failure of the OMC
does not impact network services.

70 Chapter 4: Sonata System Technical Specifications
Call Conference Server The Sonata Call Conference Server is based on the Audiocodes IPmedia 2000 SIP
Media Server hardware platform. It contains an IPM-1610 board (16 E1/T1 cPCI
VoIP Media Processing Board) which is a hot-swappable compact PCI board with
a capacity of up to 240 ports. Refer to the Moving Media 2000 Call Conference
Server Guide for more information.
Ethernet Switches A simplex system requires one Ethernet switch, where 100BaseT Ethernet is
acceptable and Gigabit Ethernet is optional. A redundant system requires two
Gigabit Ethernet switches.
Additional Hardware The following additional hardware is also recommended:

DSX panels used to demarc IMG Ports; two ports per E1/T1.
Serial port server per switching location (for the MSC or IMG).
VPN appliance per network.
Cabinets / racks as required based on the network equipment to be deployed.
ACRONYMS
A
This appendix defines acronyms used in this guide.
Table 4 List of Acronyms
Acronym Definition
1X CDMA2000 1x. The first phase of 3G for CDMA2000
networks.
2G Second Generation. Indicates the digital cellular and PCS
wireless systems for voice and low speed data services.
3G Third Generation. Indicates the third-generation, hardware
and software advancement in technology, such as CDMA
2000 1x, and UMTS.
AC Access Center or Authentication Center or Alternating
Current
ADPCM Adaptive Differential Pulse Code Modulation
AF Access Function or Audio Frequency or Assigned Frame
AIN Advanced Intelligent Network
AMR Automated Meter Reading or Adaptive Multi-Rate Speech
Codec
ANSI American National Standards Institute
API application programming interface
AS Autonomous System
ATM asynchronous transfer mode
BHCA Busy Hour Call Attempt
BSC Base Station Controller or Binary Synchronous
Communications
BSS Base Station System or Broadband Switching System
BTS Base Transceiver Station
CALEA Commission on Accreditation for Law Enforcement Agencies
CAS Channel-Associated Signaling
CAVE Cellular Authentication and Voice Encryption
CD Compact Disc
CDMA Code Division Multiple Access
CDR Call Detail Record
CF Collection Function
CFB Call Forward Busy
CFD Call Forward Default

72 Chapter :
Acronym Definition
CFNA Call Forward No Answer
CFU Call Forward Unconditional
CIC Circuit Identification Code
CII Call Identifying Information
CLI Command-Line Interface
CNG Comfort Noise Generation
CNI Calling Number ID
CNIP Calling Number ID Presentation
CNIR Calling Number ID Restriction
CORBA Common Object Request Broker Architecture
CPE Call Processing Engine or Customer Premise Equipment
CSC Customer Service Center
CW Call Waiting
DF Delivery Function
DSP Display System Protocol or Digital Signal Processor
DTMF Dual-Tone, Multi-Frequency
EIA Electronics Industry Association
ESD Electro-Static Discharge
EVRC Enhanced Variable Rate Code
FCAPS Fault, Configuration, Accounting, Performance, and Security
management
FCC Federal Communications Commission
FTP File Transfer Protocol
FWT Fixed Wireless Terminal
GB Gigabyte
GSM Global System for Mobile Communication
HA High Availability or Home Agent
HLR Home Location Register
HSG HLR SIP Gateway
IAP Intercept Access Point
IDDD International Direct Distance Dialing
IETF Intelligent Engineering Task Force
IMG Intelligent Media Gateway
IN Intelligent Network
INAP Intelligent Networks Application Protocol
IOS Interoperability Specification or Integrated Office System
IP Internet Protocol
IS Information Services
ISDN Integrated Services Digital Network
73
Acronym Definition
ISO International Organization for Standardization
ISUP Integrated Services Digital Network User Part
ITU International Telecommunications Union
LAN Local Area Network
LDAP Lightweight Directory Application Protocol
LEA Law Enforcement Agency
LFM Logical Facility Manager
LIA Lawful Intercept Access
LIS Lawful Intercept Server
LNP Local Number Portability
LOCREQ Location Request
MAP Mobile Application Part
MDN Mobile Directory Number
MF Multi-Frequency
MFC Microsoft Foundation Classes
MGC Media Gateway Controller
MGCP Media Gateway Control Protocol
MGW Media Gateway
MIB Management Information Base
MIN Mobile Identification Number
MRF Media Resource Function
MS Mobile Station or Microsoft
MSC Mobile Switching Center
MTP Message Transfer Part
MWN Message Waiting Notification
NAM Number Assignment Module
NEBS Network Equipment Building System
NIF Nodal Interworking Function
NVRAM Non-Volatile Random Access Memory
OAM Operation, Administration, Maintenance
OCN Optical Carrier Number or Operating Company Number
OI Origination Indicator or Input Output
OMC Operation and Maintenance Center
ORIGIND Origination Indicator
OSI Open Systems Interconnection
OTAPA Over-the-Air Provisioning Administration
OTASP Over the Air Service Provisioning
PC Personal Computer or Point Code or Printed Circuit
74 Chapter :
Acronym Definition
PCI Protocol Control Information or Peripheral Component
Interconnect
PCM Pulse Code Modulation
PCMA Pulse Code Modulation A-law
PCMS Personal Communication Management System: a UTStarcom
Voice Mail Product
PCMU Pulse Code Modulation U-law
PCO Public Call Office or Point of Control and Observation or
Private Cable Operator
PDSN Public Data Service Node
PIC Point in Call or Primary Interexchange Carrier
PMC Public Mobile Carrier
PRI Primary Rate Interface
PSAP Public Safety Answering Point
PSTN Public Switched Telephone Network.
PSU Packet Switch Unit or Power Supply Unit
QUALREQ Qualification Request
REGNOT Registration Notification
RFC Request for Comments
RH Request Header or Response Header
ROUTREQ Routing Request
RTCP Real Time Control Protocol
RTM Release to Manufacture
RTP Realtime Transport Protocol
SCCP Signaling Connection Control Part
SCP Service Control Point or Signal Control Point
SCSI Small Computer System Interface
SCTP Stream Control Transmission Protocol
SEP Signaling End Point
SGP Signaling Gateway Point
SGW Signaling Gateway
SIGTRAN Signaling Transport
SIM Subscriber Identity Module
SIP Session Initiation Protocol
SMS Short Message Service
SMSC Short Message Service Center
SNAP Sub network Access Protocol
SNMP Simple Network Management Protocol
SPAF Service Provider Access Function
SPARC Sun Microprocessor Architecture RISC
75
Acronym Definition
SS7 Signaling System Seven
SSD Shared Secret Data
SSVR Signaling Server
TCAP Transactional Capabilities Application Protocol
TCCS Telos Common Channel Signaling
TCP Transmission Control Protocol
TDD Time Division Duplex or Telecommunications Device for the
Deaf
TDM Time Division Multiplexed
TIA Telecommunication Industry Association
TLDN Temporary Local Directory Number
TM Traffic Management or Terminal Multiplexer
TMN Telecommunications Management Network
TP Transport Protocol or Twisted Pair or Transition Point or
Transaction Processing
TTY Teletyper
TUCL TCP/UDP Compatibility Layer
UDP User Datagram Protocol
UL Underwriters Laboratories
UMTS Universal Mobile Telecommunications System
USB Universal Serial Bus
VAD Voice Activated Dialing
VLR Visitor Location Register
VMR Violation Monitoring and Removal
VMS Voice Mail System
VoIP Voice over IP
VPN Virtual Private Network
WIN Wireless Intelligent Network
XML Extensible Markup Language
INDEX
CDRs 45 technical documentation department 18

Numerics centralized billing generation point 45 CONX 48, 50
16KHz metering 41 class of service change based on call core voice network components 22, 47
3 way calling wireless feature 35 information 42 cPCI chassis 69
class of service change based on collected CPE 48
information 45 CRBT
A classes of service 41 feature overview 35
access function 60, 61 defaults for missing call information 43 customer service
Access Server digit manipulation 42 contacting 17
SIP and 58 digit translations 42 CW 34
additional network components 22 enhanced translation pattern matching 42
AF 60, 61, 62 integrated subscriber equal access
A-interface 27 database 42 D
all-IP network inter-working between u-law and A-law delivery function 60
benefits 20 encoded voice 40 DF 60, 62
evolution 19 multiple call forward CDRs 45 direct SMS delivery wireless feature 41
announcements multiple call treatment sets 42 DS0 55, 56
concurrent sessions 59 original called number support 43
overview 57 overview 41
authentication private number plan 42 E
MSC 44 prompt and collect for additional or missing emergency services wireless features 43
VLR 44 call information 43 enhanced call processing features
Authentication Center 44 reconstruction of call information 42 nature of address routing 43
routing control 41 overview 44
subscriber category (class of service) 42 voice prompts and in-call DTMF digit
trunk grouping 41 collection 43
B call waiting wireless feature 34
Base Station Controller 61 equal access 33
call-identifying information 60 ethernet switch 67, 70
BSC 61
calling number ID presentation 35 EVRC 38, 39
calling number ID restriction wireless
feature 35
C capabilities
call conferencing server 59 F
MRF 58 files
call delivery wireless feature 34 carrier access 33
call forward-busy wireless feature 34 tones and announcements 59
carrier pre-selection 34
call forward-default wireless feature 34 CAS 27, 36
call forward-no answer wireless feature 34 CD 34
call forward-unconditional wireless CDMA 2000 1X 20
H
feature 34 HLR 56
cdmaOne 20
call hold feature 35 CF 60, 62
call processing features CFB 34
1-800 33 CFD 34 I
32 digit dialing 33 CFNA 34 IAP 61
alternate routes 41, 42 CFU 34 IDDD 33
call progress and treatment handling 41 CII 60 IMG 26, 55
call routing based on call type 34 CNIP 35 intelligent media gateway 26
call routing based on called number 34 CNIR 35 intercept access point 61
call routing based on caller ID 34 codecs intercept subject 60
call routing based on PIC 34 supported 58 interfaces 26
call routing based on prompted call collection function 60 MSC-SMS-MC 40
information 43 concurrent MGCP / Megaco 39 MSC-VLR-HLR 40
call setup 41 contacting inter-MSC IP trunking 40

78 Index
international direct distance dialing 33 MSC-BSC interface 40

intersystem handoff 40 MSC-SMSC interface 39 S
overview 40 MSC-SMS-MC interface 40 SCCP 37
IP MSC-VLR-HLR interface 40 SCCP-Lite 37
functions 25, 26 MTP3 37 SCTP 38
IP v4 40 selective call trace 45
ISDN 36 serial port server 68, 70
ISUP 27, 36, 37 N service provider administration function 60
concurrent ANSI / ITU support 37 network interfaces short message delivery point-to-point bearer
port selection optimization 37 MSC-SMSC interface 39 service 36
network service features signaling
call hold 35 protocols 53
L carrier access 33 signaling gateway 54, 56
law enforcement agency 60 carrier pre-selection 34 signaling server 52, 53
lawful intercept international direct distance dialing 33 SIGTRAN 38, 50, 53
triggering 62 roaming 36 single number hotline 33
lawful intercept access 61 single number hotline 33 SIP 27, 40
Lawful Intercept Server 61 toll restriction / classmark 41 Access Server and 58
LEA 60 transcoder free operation 40 SMS transfer 62
LIA 61, 62 NIF 54 SNAP 48
LIS 61 nodal interworking function 54 soft-switched call 62
LNP 33 SPAF 60, 62
location updating 25 SS7 50
O SSVR 52, 53
OAM 48, 50 subject 60
M OMC 62, 69 system
M2UA 38 online provisioning 45 benefits 20
overview 53 operational lifecycle 24 components 21, 47
M3UA 38, 54 operations and maintenance features 45
MCA online provisioning 45
overview 41 selective call trace 45 T
media gateway 55 OTAPA 44 target 60
media gateway controller 51 OTASP 36 TCAP 38
media management 39 over the air parameter administration 44 TCCS 27
media resource function 57 over the air service provisioning 36 technical support
media stream protocols 28 hours 17
media/session control protocols 40 website 17
Megaco 39 P temporary local directory number 25
MGCP 39 PDSN 70 timeslot 55, 56
MEGACO 62 PRI 27 TLDN 25
Megaco 39 protocol toll restriction / classmark 41
concurrent MGCP / Megaco 39 layer management 28 tones and announcements
message waiting notification wireless protocol support 26 files 59
feature 35 protocols transcoder free operation 40
MGC 51 at system interfaces 26 transport protocols 40
MGCP 28, 39, 62 call-control signaling 27 real-time transport protocol 38
concurent MGCP / Megaco 39 core network signaling 27 SIP 40
Missed Call Alert. see MCA ISUP 36
MOB 48, 49 media stream 28
mobile media-control signaling 27 V
origination 25 signaling 27 visitor location register
termination 25 SS7 36 VLR authentication 44
mobile switching center server 47 VLR 49
mobility voice message retrieval wireless feature 36
functions 25 R
mobility management radio access network components 22
16KHz metering 41 real-time transport protocol 38 W
intersystem handoff 40 regulatory features warranty support 17
mobility pre-translation features 44 E911 43 WIN 43
remote MSC availability 40 lawful intercept 43 office triggers - originating 43
mobility management and network interfaces local number portability 33 office triggers - terminating 44
overview 44 overview 43 wireless features
MRF 57 TTY/TDD support 33 3 way calling 35
capabilities 58 remote MSC availability 40 call delivery 34
MSC 47 roaming 36 call forward-busy 34
MSC authentication 44 RTP 38, 62 call forward-default 34
Index 79
call forward-no answer 34

call forward-unconditional 34
call waiting 34
calling number ID presentation 35
calling number ID restriction 35
direct SMS delivery 41
emergency services 43
message waiting notification 35
over the air parameter administration 44
over the air service provisioning 36
short message delivery point-to-point bearer
service 36
voice message retrieval 36

80 Index
Copyright 2009 Global Star Solutions ULC
Global Star Solutions ULC

120-4600 Jacombs Road
Richmond, British Columbia V6V 3B1 Canada
www.starsolutions.com

Core Voice Network Overview

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Core Voice Network Overview

Uploaded by

Copyright:

Available Formats

All-IP CDMA2000

Sonata Core Voice Network

Core Voice Network Overview

Part Number D02109 Rev A0

Core Voice Network Overview

Part Number D02109 Rev A0

UNITED STATES GOVERNMENT LEGENDS:

CDMA2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA).

ABOUT THIS GUIDE

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Concurrent ANSI / ITU ISUP support- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 37

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Reconstruction of Call Information- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 42

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

4 SONATA SYSTEM TECHNICAL SPECIFICATIONS

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Notices Table 1 lists notice icons used in this guide.

Table 1 Notice Icon Descriptions

Icon Notice Type Description

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Table 1 Notice Icon Descriptions (continued)

Icon Notice Type Description

Text Table 2 lists text conventions in this guide.

Table 2 Text Convention Descriptions

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Figure 1 Core Voice Network Document Map

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Before contacting technical support, have this information available:

For information about customer service, including support, training, code

Service Centers Operational Hours

EMEA/Asia Pacific Region:

Contacting Technical To provide comments on this documentation, send an e-mail to:

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

This chapter contains:

In traditional TDM networks, call processing functions and switching functions

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

The Sonata system is designed for the CDMA2000 1x IP packet network. In an IP

System Benefits Star Solutions system benefits include:

In an all-IP network the BSC can connect a mobile-to-mobile call without

Figure 2 illustrates the advantage of an all-IP network over a traditional TDM

Figure 2 All-IP Network Compared to a TDM Network

Mobile-Mobile Signaling CDMA2000 Abis A/SS7

Mobile-Mobile Media Stream EVRC 64 Kbps TDM

Mobile-Land Signaling CDMA2000 Abis A/SS7 ISUP/SS7

Mobile-Land Media Stream EVRC 64 Kbps TDM

Mobile-Mobile Signaling CDMA2000 Abis/IP A/IP

Mobile-Mobile Media Stream EVRC

Mobile-Land Signaling CDMA2000 Abis/IP A/IP ISUP/IP ISUP/SS7

EVRC 64 Kbps TDM

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Figure 3 Typical Logical View of a Sonata System in a Network

Additional Network Additional network components include:

Serial Port Server

A complete discussion of the other components and products is beyond the

Sonata Core Voice NetworkRelease 4.5.3Core Voice Network Overview

Figure 4 Operational Lifecycle

Validation Failed Optimization Needed

These functions are described from the following three aspects:

These functions are described in the following headings.

If the called party is at a different MSC, the HLR sends a RoutingRequest