RFQ - Request For Quotation

Gateway MSC Solution for

MIRS Communications Ltd.

January, 9 2005
Version 1.1
Author: Mori Eliav
Revised: Ezra Eldis
Engineering & Network Development Division

1 MIRS Confidential
 Table of contents

1. GMSC General Information……………………………………… 3

2. Architecture and Technology…………………………………….. 3
3. Routing…………………………………………………………… 4
4. Signaling………………………………………………………….. 4
5. Interfaces and Protocols………………………………………….. 5
6. Transmission……………………………………………………… 5
7. Capacity…………………………………………………………… 5
8. Network Features…………………………………………………. 6
9. Subscriber Services……………………………………………….. 6
10. Authentication……………………………………………………. 6
11. Synchronization…………………………………………………… 6
12. Announcements…………………………………………………… 6
13. Call Data Recording………………………………………………. 7
14. Billing Interfaces………………………………………………….. 7
15. Lawful Call Interception………………….…………………….. 7
16. Installation Implementation & Integration………………………... 7
17. Acceptance Test Plan……………………………………………. 8
18. Operations, Administration & Maintenance……………………… 8
19. Logs and Alarms…………………………………………………. 9
20. Stats……………………………………………………………… 9
21. Support………………………………………………………….. 9
22. Product Evolution………………………………………………. 10
23. Training………………………………………………………….. 10
24. Documentation …………………………………………………… 10

2 MIRS Confidential
 1. GMSC General Information
Integration of Gateway MSC in MIRS Network is based on the
concept of offloading existing MSC and saving E1’s ports by
using the GMSC to concentrate all PSTN traffic.
It has to be a flexible system that can be configured to support
various network protocols and types, such as GSM, UMTS,
CDMA, iDEN, WLAN, WiMAX etc.

It is imperative that the GMSC be able to differentiate the type of

calls: data, fax, cellular voice calls, limited subscriber calls,
international calls and others, for the purpose of routing or
blocking. This shall also be indicated in the Call Detail Recording
and other possible situations.

2. Architecture and Technology

The GMSC architecture and technology must be described in
details, including but not limited to the subscriber interface,
network synchronization function, mass storage function,
dimensioning and parts list.

The GMSC must interconnect to all network elements as depicted

in the network architecture as follows, but not limited to:

 Mobile Switching Center (Nortel MSC)

 Home Location Register (Nortel HLR)
 Signaling Transfer Point (Nortel USP)
 Base Station Controller (Motorola iDEN)
 Short Message Service
 Voice Messaging System (Comverse)
 Service Control Point
 PABX / IVR
 PSTN Network

3 MIRS Confidential
 3. Routing
The MSC must be capable of handling different traffic routing,
including but not limited to:
 Intra-network routing
 Inter-network routing
 Mobile routing
 Fixed routing
 International routing
 Multiple routing
 Trunk discrimination routing
 Random routing
 Routing by percentage
 Calling Number based routing
 Speech path
 Alternative routing and overflow

The vendor shall elaborate on the implementation and

functionality of each type of routing and describe types of routing
other than the above mentioned, if any.

4. Signaling

The system will be capable of handling different signaling

protocols, but not limited to:
 MSC-HLR Mobile Application Part (GSM 09.02)
 MSC-PSTN comply to ISUP White Book
 MSC-PSTN comply to ISUP Blue Book
 MSC-PSTN comply to Israeli ISUP
 MSC-PSTN comply to Israeli PRI
 MSC-PSTN comply to Israeli MFCR2
 DTMF Signaling
 CCS7 which includes MTP for ISUP traffic
 ITU-T CCS7 SCCP related procedures for MAP
(GSM09.02) inter working
 ITU-T CCS7 TCAP and MAP for mobility
management
 ETSI SS7 for inter working between MSC’s
 SIGTRAN for STP connectivity
 SIP for Third Part Application Servers
4 MIRS Confidential
 5. Interfaces and protocols

The system must also support interfaces and protocol standards

for system interoperability between GMSC and other network
elements.
 Intelligent Network (INAP, CS1-R, CAP, SIP)
 Voice Messaging System (ISUP Blue Book)
 Short Message Service (CCS7)
 Network Management Interfaces (TCP/IP, SNMP)
 Billing Interface (TCP/IP, FTP)
 PABX / IVR interfaces (PRI, MFCR2, H.323)
 PSTN interfaces (ISUP, VOIP)
 Digital Trunk Interface E1 / STM-1

6. Transmission

PCM (Pulse Code Modulation) for transmission of voice and data

circuits of 64kbps, 2Mbps and others.
Digital 64kbps co-directional channel shall be in accordance to
ITU-T G.703

7. Capacity

Parameter Value
Number of subscribers 500,000
Calls requiring Pre-Call processing 40 %
Call Completion rate 70 %
Conversation length (sec) 90
Length of paging (sec) 14
Incoming Traffic (mErl) per sub 10 mErl
Outgoing Traffic (mErl) per sub 15 mErl
BHCA per subscriber 1

The vendor shall indicate the subscriber capacity and the BHCA
of the proposed system.

5 MIRS Confidential
 The capacity factors will include but not limited to:
 Processor unit
 Memory
 Traffic pattern
 Traffic Loading
 Total number of subscribers
 Number of subscribers for different services
 Maximum and minimum traffic handling
 Number of voice channels

8. Network Features

The basic network services must include but not limited to the
following:
 Inter MSC handover
 Roaming within own network
 Roaming between other networks
 Nail Up connection
 Security and fraud control features
 Long Call cut off
 Premium Call

9. Subscriber Services
Subscriber data in GMSC must be compatible with subscribers’
information in HLR, existing VLR and others, depending on the
network configuration and evolution.

The GMSC shall be able to support voice and data services and
different type of calls such as data, fax or voice calls.

10. Authentication
The proposed GMSC shall support full
authentication feature such as default and
random Authentication-key functionality to
ensure fraud free service is provided.

6 MIRS Confidential
 11. Synchronization
The vendor shall propose synchronization method.
The External synchronization from BITS is required.
When clock accuracy is concerned, internal
reference clock must be made available. It
must function as a back up clock.

12. Announcements

The GMSC must be able to provide multiple announcements,

depending on call flow or release message. The MSC must
include, but not limited, the following announcements:
 Answer Time Out
 Unallocated Number
 Blocking for All Incoming Calls
 Blocking for Outgoing International Calls
 The number has been changed
 Premium Call announcement

13. Call Detail Recording

The GMSC CDR must differentiate but not limited to:

 Type of calls such vice, data, fax and other
 Mobile Terminating Call
 Mobile Originating Call
 Transit Call
 Roaming Call

The system will generate Call Detail Record (CDR) during call
processing, according to 3GPP 32.01 standards.

7 MIRS Confidential
 14. Billing Interfaces
The GMSC will generate CDR (Call Detail
Recording) and close CDR files periodically or
by size. The GMSC must store the old CDR
files for 2 weeks minimum and must be able to
back-up the old CDR files to tapes or other
media.

The GMSC must be able to transfer file

automatically (scheduled) or manually by FTP
to Billing Server.

15. Lawful Call Interception

The GMSC must be compatible with Nortel

Call Interception Interface Specification
(GSMINTER.AJ03).

16. Initial and Abiding Procedure

The vendor will be responsible for the

complete end-to-end installation, integration
and final deployment of the system. Once the
system has been transferred to the carrier, the
vendor will provide maintenance and upgrade
thereafter.

The vendor must provide the full project

implementation plan including project
management documentation such as GANTT
charts, in both hard copy and electronic format.

8 MIRS Confidential
 17. Acceptance Test Plan

The Vendor will define and execute ATP to

verify that all of the hardware, maintenance
and features are operational and meet the
requirements. MIRS Engineers will
participate during the performance of ATP.
Mirs expects these tests to include a minimum:
 System and Sub-systems Redundancy verification
 System Databases Backups and Restore verification
 GMSC basic Call Handling function
 Administrative interface function
 Spare testing and demonstrations

18. Operations, Administration and Maintenance

The GMSC must have a full reliable and redundancy mechanism

on signaling network. The proposed platform has to comply with
these requests:
 Fault – Tolerance
 High Availability
 Load sharing

The GMSC yearly outage has to meet the 5 NINES goal.

The vendor shall provide MTBF (Mean Time Between Failure),

MTTR (Mean Time To Repair), and MTBO (Mean Time Between
Outage) for all hardware components. Reliability calculation
should be based on Bellcore methods, if applicable.

The GMSC must have the capability to

perform Software upgrade in live system
without downtime.

9 MIRS Confidential
 A full system Backup comprehending all
GMSC software and data elements must be
supported. The Backup must be performed
automatically and without operation
intervention.

The vendor shall describe the backup storage:

 CD/RW, Tape, External disk and others
 Maximum Storage capacity (how many days
backups?)
 Schedule time, Automatic schedule.

19. Logs and Alarms

The standard logs will be generated by the

GMSC and will not be modified by the users.
This consists of:
 Platform Statistics
 Event Log
 Administration Change History
 Users Log

The Critical, Major and Minor alarms will be

defined by the operator.
The GMSC must be able to send alarms to
external system (HP-OVO) by SNMP or by
other compatible protocol.

20. Statistics

The GMSC must be able to generate stats of all

major events and Call Processing.

21. Support

10 MIRS Confidential
 The proposal should include support programs,
available service levels (SLA), warranty and
pricing.

11 MIRS Confidential
 Mirs requires on-line access to Vendor ‘s
customer support database (containing status
of open tickets and resolved issues).
The reports text will contain following information:
 Problem Name
 Priority
 Problem description
 Date reported
 Date registered in DB
 Current status
 Updates
 Problem resolution

The proposal should describe the policy and

procedures used by the customer support to
follow an open case or ticket.
It should also describe the mechanism for a
Remote login,
and the patches installation procedure.

22. Product Evolution (Roadmap)

The proposal should relate to the GMSC roadmap

For, at least, 3 years:

 Elaborating on next generation 3G, 4G

 Multi Media Service and future wireless
data applications.
 Releases schedule.
 Existing and planned advanced features
that may be of interest to Mirs in the
near and long terms.
 Outline hardware upgrades and design
modifications.
 Software & OS new releases upgrades
e.g. (Unix, Windows, Oracle, SQL).

12 MIRS Confidential
 23. Training

List all applicable training courses available, specify course name,

brief description, availability, duration, location and price.
The vendor will provide several training seats for GMSC
administration and operation at no additional cost.

24. Documentation

The vendor must provide documentation about all the systems and
subsystems. The documentation must be divided per subject
(Administration, System Configuration, Translation, Network,
Billing, Database, etc). The Documentation has to describe the
functionality of each sub system, hardware specifications,
software details, protocols description, connectivity between
subsystems, interfaces details, and all engineering specifications.

The vendor will provide all engineering and operation manuals to

manage daily operations, maintenance, and engineering of all the
GMSC system and subsystems. Maintenance manuals for
hardware and Software must be provided.

All GMSC system manuals must be supplied in electronic form

(CD-ROM) with built-in search engine.

Adobe Acrobat PDF documents is the most recommended.

The manual must be provided in English; Hebrew is optional.

13 MIRS Confidential