PUBLIC PMN v5 Specification v1.11
2G GSM/3G UMTS Mobile Switching Centre Product Highlights
3GPP switching compliant Distributed Network Architecture Multiple processing units & redundancy, High GSM Compliant ‘A’ Interface – IP Availability, Scalability & Flexibility
3GPP compliant Iu-CS/Iu-PS Interfaces MSC, GMSC, HLR, VLR Central HLR (Network)
Multiple Vendor Radio Access Networks MAP-C, MAP-D, MAP-E, MAP-F supported IP: SS7 over SIGTRAN and SIP support Call forwarding (conditional, unconditional), TDM: SS7 over TDM via Gateway call waiting, call hold, call transfer GTT translations, STP supported Calling party based routing, Intelligent call routing Support for SMS (MT/MO)
Caller Id; CLIP/CLIR Explicit/Implicit IMSI detach & VLR purge
Connected Line Id; COLP/COLR GPRS, EDGE, HSPA (UMTS) support (Gr over SS7) Operator determined barring CSD Support - secure phones + PSTN Gateway E.164 support Optional built-in SMSC, AuC and EIR function Support for Call intercept Optional voicemail, conferencing and external SIP RFC 3261 Support WAP, multi-media message entity platforms
Call Detail Recoding Optional Media Termination Point [Transcoding outbound & Inbound] SOS: Default or LA originated intelligent routing of emergency and e911 calls
Enterprise Support Highlights
SIP registration and operation of mobiles as IP extensions direct to IP switch Extensive Routing Tables
Full PBX network node support (trunks) Optional: Private Mobile Office – Personal Number, Personal Translation table, Inbound & Outbound Assistant, Unified Messaging, Call recording, conferencing, IVR incl. Call Queuing etc.
PUBLIC
Table of Contents
Foreward ...... 3 Introduction...... 3 2G/3G Specification [V5.0] ...... 6 Administration ...... 6 Database ...... 6 Mobile Switching Centre ...... 6 Supplementary Services ...... 7 SIP input/output support ...... 9 Registration and operation as IP extension ...... 9 IP Trunking ...... 9 HLR ...... 10 AuC ...... 10 VLR ...... 11 Equipment identity register (EIR) ...... 11 MSC/VLR ...... 12 Short Message Service Centre (Built-in Option)...... 12 Multi-media Message Service ...... 12 HNB-GW ...... 12 DATA services – HSPA, UMTS, EDGE and GPRS ...... 13 2G GSN Features and Support ...... 13 SGSN functions ...... 13 GGSN functions ...... 13 2G GSN as a Combined GSN ...... 13 Standards Conformance ...... 14 Supported Communication interfaces ...... 16 Supported interfaces ...... 17 Mobile Application Part (MAP) ...... 18 MAP/SIGTRAN Stack...... 18 Signalling conforms to; ...... 19 TDM Signalling Gateway ...... 19 Distributed Network Architecture ...... 20 MSC/HLR/VLR Platform...... 20 Distributed HLR ...... 21 Distributed MSC/VLR and HLRs ...... 22 Gateways to Mobile Networks...... 22 Networked PBX/PMN ...... 22 Radio Access Networks ...... 23 Acronyms ...... 25
Private Mobile Networks Ltd is a subsidiary of TeleWare Group plc Copyright and Confidentiality Notice This document contains information that is confidential and proprietary to TeleWare Group plc, its subsidiaries and its suppliers and shall not be reproduced, disclosed or distributed to any other party without prior written consent of TeleWare Group plc. The software described in this document is furnished under a licence and may be used or copied only in accordance with the terms of such licence. The information in this document is subject to change without notice and should not be construed as a commitment by TeleWare plc. TeleWare plc assumes no responsibility for any errors that may appear in this document. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by TeleWare plc or its associated companies.
2
PUBLIC Foreward
The purpose of this document is to provide a technical breakdown of the specifications of the Private Mobile Networks 2G and 3G products. Introduction
Private Mobile Networks provide a 2G/3G mobile network switching subsystem implemented in software with all the components for switching mobile calls, switching short message service calls, storing and transmitting SMS and providing Packet Data (HSPA, UMTS, EDGE and GPRS) in software complete with translation and routing tables to act as a replacement PBX and/or MSC.
The Radio Access Network is connected via IP to the MSC through either a Base Station Controller which in turn connects to the Base Transceiver Station for a 2G RAN or via the Home Node B Gateway (or potentially Radio Network Controller) which in turn connects to the Home Node B or Access Point in 3G, the MSC can connect to both BSC and HNB-GW/RNC simultaneously providing both 2G and 3G services. Typical 2G
PMN components are shown below, other IP PBX are supported see section 2.4: The 3G components are largely the same with the main differences being the BSC is replaced by either a Radio Network Controller or as is the case in the below by a Home Node B Gateway. The BTS are replaced with Home Node B’s or Access Points.
3
PUBLIC
The MSC can connect to both 2G and 3G RAN’s simultaneously as shown in the below.
The hardware requirements are largely driven by the number of users, expected call and DATA volumes and redundancy but an example of the hardware breakdown is shown here. Note the 2G SGSN/GGSN and the 3G SGSN/GGSN cannot run on the same server.
Database: The database is Microsoft SQL. SQL provides for the Home Location Register (HLR) which stores comprehensive details of authorised subscribers.
The database supports multiple tenancies with discrete networks and dial plans enabling operators to share infrastructure and to provide for flexible multiple enterprise and flexible network deployments. The SQL Database provides for all structured storage requirements of the product.
Mobile Switching Centre (MSC): The MSC, 3GPP compliant switching core, manages all call traffic; registration of authorised handsets, making, connecting, transferring and terminating calls. The MSC also manages the handover of calls on the RAN. External voice calls, inbound and outbound are SIP compliant with the codec used on the network providing the digital voice coding.
Short Message Service Controller (SMSC): The SMSC manages the receipt, routing and transmission of SMS messages – mobile originated or terminated.
Multimedia Message Service Controller (MMSC): The MMSC manages the receipt, routing and transmission of MMS messages provided by a multimedia message entity platform (3rd party).
4
PUBLIC
DATA services (HSPA, UMTS, EDGE and GPRS)-optional for 2G: The DATA components include a Combined GSN (GGSN and SGSN) for 2G and separate GGSN and SGSN for 3G installations.
SNMP support for the MSC and SMSC: The PMN Extension Agent supports SNMP v1. All traps sent out will be SNMP v1 but it should be possible to perform GET, GET-NEXT and SET requests using SNMP v2c if desired.
Translation and Routing Tables: Private Mobile Networks provide extensive translation and routing capability enabling solutions to be deployed as a mobile network switching core in a mobile network or to replace an enterprise Private Branch eXchange (PBX) or to act as a node in an enterprise switch network.
Interoperability: Mobile Networks: HLR/VLR interconnection via MAP over SIGTRAN. Interconnection to TDM networks through SS7 Signalling Gateway. A Gateway would be required for SIP to TDM connectivity (such as SS7 ISUP). Enterprise: Interconnection with other enterprise IP switches is enabled using SIP and through gateways into a TDM network.
5
PUBLIC 2G/3G Specification [V5.0]
The features and functions listed in this specification are dependant of the Radio Access Network supporting the features and functions within the GSM specifications implemented by the manufacturer. Any RAN dependant features or functions are highlighted.
Administration
All administration and documentation is in UK English.
Database
The PMN database holds information subscriber information relevant to Home Location Registers (HLR, LHLR and CHLR), active subscriber information, Visitor Location Register (VLR), and Equipment Identity Register and all other information stored by the system. It contains certain features which are different to normal GSM operation (although the GSM standards may contain analogous elements). Such features are:
Multi-partitioned: May separate user groups into separate partitions. Alias IDs: Allow user to be identified by multiple numbers/aliases. Class of Service: Options to specify what access individual users have - e.g. internal calls only, local calls only, national, international etc.
The Database is Microsoft SQL.
Mobile Switching Centre
The Mobile Switching Centre (MSC) is the primary service delivery node for 2G and 3G service for delivering services such as voice, SMS and DATA over both the 2G Network Switching Subsystem and the 3G Core Network (CN)
The MSC sets up and releases the end-to-end connection, handles mobility and handover during calls.
For 2G - The MSC is compatible with 3GPP (Phase 2+ Release 1998). For 3G - The MSC, 3G GSN and AC are compliant to 3GPP Release 6 for the IU Interface/RANAP.
Voice Calls via RAN and via SIP: Call Connect Call Disconnect Call Hold Call transfer
6
PUBLIC
Calling Line Identity Restriction: ability to turn off CLI presentation when making calls Name Display; Database name forced when originating a mobile call to the outbound leg to on-net or via SIP. Registration: Authentication and ciphering, Ki authentication between SIM and network IMSI IMEI
Supplementary Services
SS group Supplementary services Standalone Central TS HLR / VLR HLR Line Identification Calling line identification presentation CLIP 02.81 Calling line identification restriction CLIR 02.81 Connected line presentation COLP 02.81 Connected line restriction COLR 02.81 Name identification Calling name presentation CNAP 02.96 Call forwarding Call forwarding - unconditional CFU 02.82 Call forwarding - busy CFB 02.82 Call forwarding - no reply CFNRY 02.82 Call forwarding - not reachable CFNRC 02.82 Call offering Explicit call transfer ECT 02.91 Call completion Call waiting CW 02.83 Call hold CH 02.83 Call Barring Barring of all outgoing calls BAOC * * 02.88 Barring of outgoing international calls BOIC * * 02.88 Barring of outgoing international calls BOIC-ex * * except to the home country Hc 02.88
* Currently only via Operator determined barring Note: CNAP for SIP to Mobiles, any display text (alias) in the “From” header of a SIP Invite message will be passed onto the Mobile Handset – not all handsets are capable of displaying this name text.
Handset Information Display (HID) Calling *#100# from a handset will display the designated extension number of the handset whilst on the Private Mobile Network.
2G Codec specification: GSM-EFR or AMR (if supported by handset) as an alternative to GSM-FR (not possible to mix).
3G Codec specification: AMR only.
Follow me service: Call forwarding based on a pre-set number list – sequential.
7
PUBLIC
SOS: Configurable call routing based on Default route (when no specific route is given) or LA dependant routing (route depending on the originating LA receiving the call).
Emergency Call Support: Emergency state support permitting the immediate and graduated restriction of subscribers’ ability to utilize resources.
SMS: Mobile Originated (MO): Message Send Mobile Terminated (MT): Message Receive
Unstructured Supplementary Service Data (USSD) support: Phase 2 supported A HTTP interface is provided for transmission and response of USSD if not using MAP.
Call Detail Recording (CDR)
Call Intercept: The ability to remote monitor/transit calls on a subscriber basis to an Intercept Gateway.
CSD RAN Dependant and only applicable for 2G Handsets Tested: o Sectera TalkSecure Wireless [V.32] o Enigma (Tripleton T301B) [V.110] o GSMK CryptoPhone G10i [V.32/V.110] o GSMK CryptoPhone CP300 [V.32/V.110] 9.6 Kbps support for Base Station to Base Station for encrypted calls. 9.6Kbps CSD transparent mode calls off-net Inbound & Outbound [V.110] – Requires optional PMN VoIP Gateway.
The following is a list of GSM/UMTS standards to which the MSC conforms (either fully or partially):
GSM 03.09: Handover Procedures GSM 04.08: Mobile Radio Interface Layer 3 GSM 08.08: BSS-MSC: Layer 3 GSM 11.30: Mobile Services Switching Centre
GSM 03.40: Technical realisation of Short Message Service (SMS) Point-to-Point (PP)
GSM 09.02: Mobile Application Part (MAP) [When SS7/SIGTRAN connection is used]
For UMTS the MSC conforms to the following specifications for the lu interface (Release 6) 3GPP TS 25.410 UTRAN Iu Interface: general aspects and principles 3GPP TS 25.412 UTRAN Iu interface signalling transport 3GPP TS 25.413 UTRAN Iu interface RANAP signalling 3GPP TS 25.414 UTRAN Iu interface data transport and transport signalling 3GPP TS 25.415 UTRAN Iu interface user plane protocols
8
PUBLIC lu interface details for the MSC: IP v4 Iu-CS over IP Control plane; RANAP/SCCP/M3UA/SCTP (ASP-ASP mode of operation for M3UA) Iu-CS over IP User plane; Iu-UP/RTP/UDP Iu-CS compliant to 3GPP Release 6 lu interface details for the GSN: IP v4 Iu-PS over IP Control plane; RANAP/SCCP/M3UA/SCTP (ASP-ASP mode of operation for M3UA) Iu-PS over IP User plane; (Iu-UP)/GTP/UDP Iu-PS compliant to 3GPP Release 6 Both MSC and GSN will enable the use of UIA1 and can enable the use of UEA1 for security.
SIP input/output support
The MSC supports the registration and operation of mobiles to an IP switch as extensions on the IP switch or as a node in an IP switch or TDM switch network.
Telephony, PBX / PSTN input/output is via IP SIP. The interface conforms to; SIP standard RFC 3261 Other endpoint must support re-INVITEs for RTP media redirection RTP media must be that supported by the MSC DTMF via SIP INFO messages RFC 2976 or RFC 2833 Support for REFER messages RFC 3515 Note: If the MTP application is not being used the RTP codec for both input and output is required to match the setting for the RAN. All codec transcoding and protocol conversion is a function of an external gateway. PMN have integrated with most IP PBX suppliers including: Asterisk, Avaya, Cisco, Innovaphone, Mitel and NEC.
Registration and operation as IP extension
An IP Proxy has been specifically developed to register mobiles present on the private network as IP extensions. This enables the mobile to operate as an extension when specified in any features of the IP switch (e.g. voicemail, presence, key-lamp displays, group ringing etc.). Registration will cease when the mobile is known not to be on the private network.
IP Trunking This is the traditional connectivity for the MSC with capability to partake as a node in a switch network, IP or through a gateway TDM. Extensive translation and routing capabilities are provided.
9
PUBLIC HLR
The Home Location Register (HLR) is a database containing details of each mobile phone subscriber authorised to use the GSM network or part of the network. The HLR stores the details of every Subscriber Identification Module (SIM). Each SIM has a unique identifier, International Mobile Subscriber Identity (IMSI) which is the primary key to each HLR. Each IMSI has an associated MSISDN (mobile telephone number) and aliases– the MSISDN is also a primary key to the HLR. The HLR data is stored for as long as the subscriber remains with the mobile phone operator.
Example of data stored; GSM services available GPRS settings to allow access to packet services Current location of subscriber (VLR and Serving GPRS Support Node/SSGN) Call divert settings Authentication values Ki and class of service data
The HLR receives and processes MAP transactions and messages from elements of the GSM network (e.g. the location update messages received as mobile phones roam).
User Account suspension supported.
HLR conforms to; 3GPP TS 09.02 (Phase 2+) version 7.15.0 (2004-03) Mobile Application Part (MAP) specification (Release 1998)
AuC
The Authentication Centre (AuC) is a function to authenticate each SIM attempting registration. Once the authentication is complete the HLR is allowed to manage the SIM and associated services.
The AuC does not engage directly in the authentication process, but generates data known as triplets or in the case of 3G quintuplets for the MSC to use during the procedure. The security of the process depends upon a shared secret between the AuC and the SIM called the Ki. The Ki is securely burnt into the SIM during manufacture and securely replicated into the AuC. The Ki is never transmitted between the AuC and the SIM, but is combined with the IMSI to produce a challenge/response for identification purposes and an encryption key called Kc for use in over air communications.
10
PUBLIC VLR
The Visitor Location Register (VLR) is a temporary database of subscribers who have roamed or registered to an area of the network served by the VLR. A VLR has an associated MSC - VMSC. A subscriber cannot be present in more than one VLR.
Example of data stored; IMSI Authentication data MSISDN GSM services available GPRS settings to allow access to packet services The HLR address of the subscriber
The primary functions of the VLR are: To inform the HLR that a subscriber has arrived in a particular area of the network covered by the VLR To track where the subscriber is within the VLR area (location area) when no call is ongoing To allow or disallow which services the subscriber may use To allocate roaming numbers during the processing of incoming calls To purge the subscriber record if the subscriber becomes inactive whilst in the area of the VLR. The VLR deletes the subscriber’s data after a fixed time period of inactivity and informs the HLR (e.g. when the phone has been switched off, left off or when the subscriber has moved to another area with no coverage for a long time) To delete the subscriber record when a subscriber explicitly moves to another area of the network as instructed by the HLR.
The VLR receives and processes MAP transactions and messages from elements of the GSM network (e.g. the location update messages received as mobile phones roam).
MSC/VLR conforms to; 3GPP TS 09.02 (Phase 2+) version 7.15.0 (2004-03) Mobile Application Part (MAP) specification (Release 1998)
Equipment identity register (EIR)
The Equipment Identity Register (EIR) keeps a list of mobile phones (identified by their international mobile equipment identifier - IMEI) which are to be banned from the network or monitored. This is designed to allow for tracking of stolen mobile phones. In theory all data about all stolen mobile phones should be distributed to all EIRs in the world through a central EIR. This is not universal. The MAP messaging for EIR notification is supported for a central EIR.
11
PUBLIC MSC/VLR
The MSC/VLR and Proxy VLR are written to the following standard: 3GPP TS 09.02 (Phase 2+) version 7.15.0 (2004-03) Mobile Application Part (MAP) specification (Release 1998)
Short Message Service Centre (Built-in Option)
The SMSC supports SMPP v3.4 and can operate as an SMPP server and/or an SMPP client. Supported SMPP operations are: BIND_TRANSMITTER BIND_RECEIVER BIND_TRANSCEIVER SUBMIT_SM DELIVER_SM QUERY_SM CANCEL_SM ENQUIRE_LINK UNBIND
Support for message receipt from external 3rd party SMS provider via Microsoft Message Queue.
Multi-media Message Service
Support for MMS via 3rd party MMSC (using SMPP to SMSC).
HNB-GW
Core Network interfaces Iu-CS interface over IP Iu-PS interface over IP
Features The HNB-GW Iuh interface is based on Release 9 RUA and HNBAP specifications. (Release 6 for RANAP.) ANSI or ETSI Iu
12
PUBLIC DATA services – HSPA, UMTS, EDGE and GPRS
The 2G GSN provides General Packet Radio Service (GPRS) services using a GPRS Support Node (GSN) that combines the functionality of both a Serving GPRS support node (SGSN) and a Gateway GPRS Support Node (GGSN) in the same physical node. For 3G services this application is split into two separate component parts being the SGSN and the GGSN.
A proprietary interface (i.e. Local Gr interface) exists between the SGSN and the PMN database, which accesses the relevant HLR information for maintenance of subscriber data. The (S)GSN software has support for Local as well as for Remote HLR (via SS7).
2G GSN Features and Support
Please note, further 3rd Party components may be required to support certain features.
SGSN functions The SGSN supports the following: All Mobility Management functions including Attach, Detach and Routing Area Update. Session Management functions including Quality of Service (QoS) negotiation. SMS CDR generation Ciphering Compression Anonymous PDP Context Activation/Deactivation procedures
Circuit-switched procedures over the Gs interface
GGSN functions The GGSN supports the following: Security using RADIUS authentication· RADIUS accounting IPCP support Anonymous PDP Context Activation/Deactivation procedures· Static/dynamic address allocation IPCP support Network-requested PDP Context Activation procedures
Gc Interface with HLR Dynamic address allocation through DHCP and RADIUS
2G GSN as a Combined GSN GSN running as a combined GSN supports the functionality of both SGSN and GGSN. In the combined mode, GSN supports inter-SGSN procedures and serves as the GGSN for the PLMN in which it is deployed. In addition, it serves as the GGSN for subscribers who have roamed into other PLMNs.
13
PUBLIC Standards Conformance
2G GSN conforms to the following standards:
Interface Protocol Specs Compliance SNDCP (SGSN & MS) GSM 04.65 version 7.1.1 Release 1998 LLC (SGSN & MS) GSM 04.64 version 7.1.1 Release 1998 Gb BSSGP (SGSN & BSS) GSM 08.18 version 7.1.0 Release 1998 NS (SGSN & BSS) GSM 08.16 version 7.1.0 Release 1998 SGSN-VLR Gs interface network service specification GSM 09.16 version 7.0.1 Release 1998 Gs SGSN-VLR Gs interface layer 3 specification GSM 09.18 version 7.1.0 Release 1998 PP-SMS:
Gd SGSN & SMS-IWMSC GSM 04.11 version 7.0.0 Release 1998 SGSN & SMS-GMSC
Gr MAP (SGSN & HLR)
Gf MAP (SGSN & EIR) GSM 09.02 version 7.1.0 Release 1998
Gc MAP (GGSN & HLR)
Gp GTP (GSN & GSN) GSM 09.60 version 7.3.0 Release 1998
GI IP (GGSN & External IP) GSM 09.61 version 7.1.0 Release 1998:
Ga GTP’ (GSN & CG) GSM 12.15 version 7.4.0 Release 1998 ITU-T Recommendation Q.771 to Q.774 TCAP ANSI Recommendations T1.114.1 to T1.114.4 (1996) ITU-T Recommendation Q.711 to Q.714 SCCP ANSI Recommendation T1.112 (1996) ITU-T Recommendation Q.704 SS7 MTP3 ANSI Recommendations T1.111.4 and T1.111.7 (1996) ITU-T Recommendation Q.701 ITU-T Recommendation Q.703 MTP2* ITU-T Recommendation Q.752 ANSI T1.111 ITU-T Recommendation Q.922 Frame Relay* ITU-T Recommendation Q.933 ANSI T1.606, T1.617, T1.618 IP IETF STD 5 IP UDP IETF STD 6 RADIUS (GGSN & RADIUS) IETF RFC 2865, IETF RFC 2986 SNMP IETF RFC 1157 GPRS Service Description Stage 2 GSM 03.60 version 7.4.0 Release 1998 Others Mobile radio interface signalling layer 3; General GSM 04.07 version 7.3.0 Release 1998 aspects Mobile radio interface signalling layer 3 GSM 04.08 version 7.4.0 Release 1998 specification
14
PUBLIC
3G-GSNLite GGSN conforms to the following standards
Interface Protocol Specs Compliance
Gc MAP (GGSN & HLR) GSM 09.02 version 7.1.0 Release 1998 GSM 09.60 version 7.3.0 Release 1998 and Gp GTP (GSN & GSN) 3GPP 29.060 Version 7 3GPP 23.060 (June’11) Release 7
GI IP (GGSN & External IP) GSM 09.61 version 7.1.0 Release 1998:
Ga GTP (GSN & CG) GSM 12.15 version 7.4.0 Release 1998 TCAP ITU-T Recommendation Q.771 to Q.774 ANSI Recommendations T1.114.1 to
T1.114.4 (1996) SCCP ITU-T Recommendation Q.711 to Q.714 ANSI Recommendation T1.112 (1996) SS7 MTP3 ITU-T Recommendation Q.704 ANSI Recommendations T1.111.4 and
T1.111.7 (1996) ITU-T Recommendation Q.701 MTP2* ITU-T Recommendation Q.703 ITU-T Recommendation Q.752 ANSI T1.111 IP IP IETF STD 5 UDP IETF STD 6 IETF RFC 2865, IETF RFC 2866, IETF RFC 2869, draft-lior-radius- RADIUS (GGSN & RADIUS) prepaidextensions- Others 11 - Prepaid extensions to Remote Authentication Dial-In User Service (RADIUS) GPRS Service Description Stage 2 GSM 03.60 version 7.4.0 Release 1998
3G-GSNLite SGSN conforms to the following standards
Interface Protocol Specs Compliance
Gr MAP (SGSN & HLR) 3GPP TS 29.002 V5.b.0 PP-SMS:
Gd SGSN & SMS-IWMSC 3GPP TS 29.002 V5.b.0 SGSN & SMS-GMSC
Ga GTP (GSN & CG) 3GPP TS 32.015 V3.5.0
Iu-PS RANAP (SGSN & RAN) 3GPP TS 25.413 V6.16.0
Gn GTP (GGSN & SGSN) 3GPP TS 29.060 V7 3GPP TS 23.078 V4.6.0 (2002-09), Technical Ge CAP (with gsmSCF) Specification Group Core CAMEL Phase 3, Stage 2 (Release 1999) 3GPP TS 29.078 V3.13.0 (2002-03), Technical Network
Specification CAMEL Application Part (CAP) Specification Group Core CAMEL Phase 3 (Release 99) Network
15
PUBLIC Supported Communication interfaces
The 2G GSN supports the following combination of interfaces to enable communication with Network Elements (NEs) such as BSS and other SS7 nodes such as MSC/VLR, HLR, and SMSC:
Supported Communication interfaces for 2G GSNLite GSN/SGSN
FR/E1-based communication towards BSS and SS7/E1-based communication towards all SS7 nodes (SS7 compliant to ITU-T standards)· FR/E1-based communication towards BSS and SS7/IP-based communication towards all SS7 nodes (SS7 compliant to ITU-T standards)· IP-based communication towards BSS and SS7/E1-based communication towards all SS7 nodes (SS7 compliant to ITU-T standards)· IP-based communication towards BSS and SS7/IP-based communication towards all SS7 nodes (SS7 compliant to ITU-T standards)· FR/E1-based communication towards BSS and SS7/T1-based communication towards all SS7 nodes (SS7 compliant to ANSI standards)· FR/E1-based communication towards BSS and SS7/IP-based communication towards all SS7 nodes (SS7 compliant to ANSI standards)· IP-based communication towards BSS and SS7/T1- based communication towards all SS7 nodes (SS7 compliant to ANSI standards)· IP-based communication towards BSS and SS7/IP-based communication towards all SS7 nodes (SS7 compliant to ANSI standards) FR/E1-based communication towards BSS and Localized Gr based communication towards Local HLR and SGSN. IP based communication towards BSS and Localized Gr based communication towards Local HLR and SGSN. FR/E1-based communication towards BSS and both SS7/E1-based and localized Gr based communication towards HLR and SGSN. IP based communication towards BSS and both SS7/E1-based and localized Gr based communication towards HLR and SGSN.
Supported Communication interfaces for 3G-GSNLite SGSN
IP based communication towards RNC (IPv4) – Iu-PS Localized Gr based communication towards Local HLR and SGSN Both SS7/IP-based and localized Gr based communication towards HLR and SGSN
16
PUBLIC
Supported Communication interfaces for 3G-GSNLite GGSN
3G-GSNLite-GGSN supports the following combination of interfaces to enable communication with Network elements (NEs) such as SS7 nodes such as HLR: SS7/E1-based communication towards all SS7 nodes (SS7 compliant to ITU-T standards) SS7/IP-based communication towards all SS7 nodes (SS7 compliant to ITU-T standards) SS7/T1-based communication towards all SS7 nodes (SS7 compliant to ANSI standards) SS7/IP-based communication towards all SS7 nodes (SS7 compliant to ANSI standards)
The usual configuration supported by PMN is to use IP transport for the interface to the BSS (NS over IP) and to use the Local HLR interface into the PMN database, with the option of simultaneously using SS7 over SIGTRAN (IP transport) for communication to SS7 nodes.
Supported interfaces
The 2G GSN supports DATA interfaces as mentioned in the following table
Interface Interfacing Entities
Gb SGSN and Base Station Subsystem (BSS)
Gc GGSN and Home Location Register (HLR)
Gr SGSN and HLR
Gs SGSN and Mobile Switching Center/Visitor Location Register (MSC/VLR)
Gd SGSN and Short Message Service (SMS)-Gateway MSC (GMSC)/SMS-Interworking MSC (IWMSC)
Gi GPRS and external packet data network
Gn Two GSNs within the same Public Land Mobile Network (PLMN)
Ga SGSN/GGSN and CGF
The 3G GGSN/SGSN supports DATA interfaces as mentioned in the following table
Interface Interfacing Entities Iu-PS SGSN and Radio Access Network (RAN)
Gc GGSN and Home Location Register (HLR)
Gr SGSN and HLR
Gd SGSN and Short Message Service (SMS)-Gateway MSC (GMSC)/SMS-Interworking MSC (IWMSC)
Gi GPRS and external packet data network
Gn Two GSNs within the same Public Land Mobile Network (PLMN)
Ga SGSN/GGSN and CGF
17
PUBLIC Mobile Application Part (MAP)
PMN Map Gateway Subsystem (MGS) PMN provides an integrated MAP/SS7 over SIGTRAN + SIP and through a signalling gateway MAP/SS7/over C7 + ISUP.
PMN MAP stacks are compliant to GSM, GSM Phase 2+, 3GPP R99, R4 specs.
MAP/SIGTRAN Stack
MAP Interface Message Sent Received MAP-C SendRoutingInfo (only T-MAP) (only T-MAP) SendRoutingInfoForSM InformSC AlertServiceCentre ReportSMDeliveryStatus MAP-D UpdateLocation CancelLocation InsertSubscriberData DeleteSubscriberData PurgeMS SendAuthenticationInfo ProvideRoutingNumber ReadyForSM RegisterSS EraseSS ActivateSS DeactivateSS InterrogateSS RegisterPassword GetPassword ProcessUSSRequest USSRequest USSNotify MAP-E MOForwardShortMessage MTForwardShortMessage MAP-F CheckIMEI MAP-Gd MOForwardShortMessage MTForwardShortMessage MAP-Gr UpdateGPRSLocation CancelLocation InsertSubscriberData DeleteSubscriberData PurgeMS SendAuthenticationInfo
18
PUBLIC Signalling conforms to;
SS7 Specifications ITU Recommendation for TCAP Q.771 to Q.774(1996) ITU Recommendation for SCCP Q.711 to Q.714(1996)
SIGTRAN Specifications RFC 3332 for MTP3 User Adaptation Layer (M3UA) RFC 2960 for Stream Control Transmission Protocol (SCTP)
MAP Specifications ETSI GSM 09.02 (Phase 1) version 3.11.0 May 1995 – Mobile Application Part Specifications ETSI GSM 09.02 (Phase 2) version 4.19.1 – Mobile Application Part Specifications ETSI GSM 09.02 (Phase 2+) version 7.5.1 – Mobile Application Part Specifications (Release 1998) 3GPP TS 29.002 (Phase 2+) version 3.8.0 (2001-03) Mobile Application Part (MAP) specification (Release 1999) 3GPP TS 29.002 (Phase 2+) version 4.8.0 Mobile Application Part (MAP) specification (Release 4)
TDM Signalling Gateway
Scalability: Scales to 128 SS7 Signalling links in a dual redundant deployment Redundancy: Carrier Grade, 1+1 Dual Plane worker/hot standby redundancy (Single Point Code) A, F link support.
SS7 Specifications ISUP: International variants optional SCCP: ITU-T Q.711-Q.714 MTP L1-L3: ITU-T Q.701-Q.707
SIGTRAN Specifications RFC 3332 Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) RFC 2960 Stream Control Transmission Protocol (SCTP)
19
PUBLIC Distributed Network Architecture
PMN has been designed to operate in the mobile environment as outlined below; networking HLR/VLR subscriber information and networking MSC/VLR for call control. The interoperation with mobile networks is performed through MAP Gateway Subsystem. The connectivity into the mobile operator network is standard SS7 over SIGTRAN for the MAP signalling and SIP for call control or with an additional Gateway to provide a TDM interface taking in the SS7 over SIGTRAN and SIP and connecting using TDM SS7 (MAP & ISUP).
The PMN solution is also designed to act as an IP Private Branch eXchange (PBX) replacement/substitute, as a node within a private telephone network or as a switch providing mobility alongside a PBX. The telephone network can be a legacy network with PMN working through gateways, an IP PBX directly connected over IP or a combination of legacy and IP. PMN is defined with the traditional Translation and Routing tables plus specific support for gateways and protocols (optional media termination point, MTP)
MSC/HLR/VLR Platform.
The PMN platform as a standalone system or as a system node (MSC instance) is capable of deployment on a single server (as in the Rapid Deployment Unit within a case) or as multiple servers with redundancy to provide high availability, scalability and redundancy.
The larger Private Mobile Networks platforms are designed around a Distributed Network Architecture at the platform level. The servers are industry standard servers and are specified with resilience options for power (dual power supplies often with separate power sources), teamed network interfaces and RAID discs where disc storage is local. The servers are organised in functionally similar clusters providing redundancy at server level. This enables continuing availability when there is a failure of a server, the others assume the load. All platform deployments are recommended to have Uninterruptible Power Supplies (UPS) with, where possible, two different power sources. Rack mounted servers (blades are an option) are wired for redundant networks and switches. The SQL data storage (including HLR and VLR) can be located on Storage Areas Networks (SAN) to provide scalability, backup and multi point access from clustered server farms. The current platforms often use virtualization to maximize efficiency and usage.
The use of the proven Distributed Network Architecture provides the ultimate in flexibility and manageable incremental growth and cost efficient deployments whilst retaining the integrity of the service to subscribers.
20
PUBLIC Distributed HLR
MSC network architecture provides for flexibility within a multi operator/enterprise environment. A Local HLR (LHLR) may authorise subscribers to a specific MSC/VLR and the attached RAN only as a standalone or as an instance in a network.
There is provision for multiple instances of MSC/VLR (and LHLR) to share central HLR (CHLR) enabling common subscribers across multiple MSC/VLRs or RANs. The CHLR has capability to restrict subscriber to individual instances of MSC/VLR.
To provide an intermediate level of clustering of MSC/VLR instances there is a Hub HLR where as part of a larger network there is required a level of subscriber registration and authentication across a grouping of MSC/VLR instances (e.g. an operator or a common grouping for a larger enterprise with multiple MSC instances deployed.
A proprietary MAP based protocol, T-MAP, has been developed enabling network messaging between networked PMN component HLRs and the MAP Gateway Subsystem.
From the Central HLR the network will provide connection into a telephony network and / or access through the MAP Gateway for roaming into and out of the PMN network from/to other mobile network operators.
Discrete PMX
SS7/SIGTRAN SS7/TDM
Mobile Centrex IP MNO network Central HLR/VLR Routed via IMSI SS7/SIGTRAN SS7/TDM
SS7 Gateway
Proxy PMX (HLR/VLR) Distributed Network
Local/Remote HLR/VLR Routed to Central HLR/VLR using IMSI
21
PUBLIC Distributed MSC/VLR and HLRs
The MSC network architecture provides for flexibility within a multi operator/enterprise environment to provide multiple instances of MSC/VLR. The networking of HLRs is outlined above for the interchange of subscriber information.
Gateways to Mobile Networks
At the edge of the PMN Network, at the point of interconnect to the Mobile Network the PMN MAP Sub System, MAP Gateway System (MGS), based on the Aricent nexGen platform, will service the SS7 over SIGTRAN signalling and the PMN SIP Sub System (SGS) will service the Call interoperation.
CHLR/VLR – Routed using IMSI
TMAP
TWMAP MNO IP MNO TDM interconnect interconnect nexGen platform SIGTRAN – SS7 Signalling
SS7 MAP MNO CALL - SIP ISUP E1/T1
If a TDM interface is required for interoperation with an existing mobile network this is facilitated by an SS7 Signalling and SIP Gateway into SS7 over TDM (for MAP & ISUP) from a third party.
Networked PBX/PMN
The platform is designed as a node within a digital switch network operating on a peer-to-peer level or as a replacement/substitute PBX. The PMN is an IP based switch interfacing with other IP switches via IP SIP and with legacy TDM products through gateways for ISDN, Q931 and QSig etc.
22
PUBLIC Radio Access Networks
Radio Access Networks (RAN) are supported based on equipment from a number of manufactures and may consist of 2G only, 3G only or 2G and 3G implementations. From a 2G perspective one or more Base Station Subsystem (BSS) each supports one or more Base Transceiver Station (BTS) and one or more Base Station Controllers (BSC). The number of BSS supported depends on the chosen Manufacturer equipment and throughput. Similarly for 3G in that RAN’s from one or more HNB-GW and RNC’s can be supported, each supporting one or more Home Node B’s or Node Bs in the case of RNCs.
The deployable configurations are outlined and illustrated below;
Note: The two illustrations below are based on two manufacturer’s RANs; each will differ in detail depending on manufacturer. MSC features and facilities are maintained, where possible, regardless of RAN manufacturer. Each MSC may support a RAN from more than one manufacture concurrently. A deployment may support more than one MSC and RANs from more than one manufacturer.
In this 2G example the BTS, radio access points, are distributed throughout the area of coverage connected via LAN and or WAN back to the Base Station Controller (BSC). The BTS supports up to 7 Base Station connections (typically mobile calls) using standard rate (GSM) and optionally 14 Base Station connections using AMR (i.e. 7 or 14 concurrent calls)
The Base Station Controller (BSC) acts as a controller between the links serving the BTS radio channels and the MSC. The BSC handles the handover of calls between BTSs under its control and between itself and other BSCs subject to direction from the MSC dictated by the SQL Database.
3G In this 3G example the Home Node B’s, are 3G distributed throughout the area of coverage connected via LAN and or WAN back to the Home Node B Home Node B
Home Node B Gateway (HNB-GW). The IP HNB supports up to 16 connections IP (typically mobile calls) using AMR. network IP
IP PSTN IP PBX
A X C o n t r o l l e r
GSM SIP PMX
23
PUBLIC
Where manufacturer equipment is specified in clusters (i.e. 1, 2 or 3 BTSs + BSC as a BSS) then a number of BSC clusters or a number of BSCs may be specified as input to the MSC. Diagram below:
The BSS clusters, BTSs + BSC are connected back to the MSC by IP, LAN, internet or satellite. The MSC then manages the network as one network, enabling calling across BSCs. There is currently no handover between MSCs. These clusters can vary in BTS and the maximum BTSs in a cluster according to manufacturer.
The above diagrams show a Private Mobile Network deployed as a Mobile Network Operator or as an enterprise PBX replacement using standard gateways into the PSTN and Mobile Networks.
The components of a PMN may be installed on a single Server (as above) or components scaled for capacity and high availability (resilience and redundancy) over multiple servers for each component is architected as a distributed network server allowing continuation of service in the event of failure of one or more component. The database is an SQL database with its own resilience and replication features.
Distributed Network Architecture
24
PUBLIC
The diagram, above, shows the connectivity and distribution of a hosted service, integration with an IP switch and applications platform. An extensive range of integrated services are provided over a mobile network or an enterprise/user over the common network. The SQL Database controls access to authorised parts of a network and any interoperation/access (i.e. direct dialling).
Acronyms
ALCAP Access Link Control Application Protocol AMR Adaptive Multi-Rate (codec) ANSI American National Standards Institute AP Access Point APN Access Point Name AuC Authentication Centre
BAOC Barring of all outgoing calls BOIC Barring of outgoing international calls BOIC-ex Hc Barring of outgoing international calls except to the home country BSC Base Station Controller BSS Base Station Subsystem BTS Base Transceiver Station
CAMEL Customised Applications for MOBILE Network Enhanced Logic CCBS Completion of Call to Busy Subscriber CDR Call Data Record CF Call Forwarding CFB Call Forwarding on Mobile Subscriber Busy CFNRc Call Forwarding on Mobile Subscriber Not Reachable CFNRy Call Forwarding on Mobile Subscriber No Reply CFU Call Forwarding Unconditional CH Call Hold CHLR Central Home Location Register CLI Calling Line Identity CLIP Calling line identification presentation CLIR Calling line identification restriction CN Core Network CNAP Calling Name Presentation CODEC Coder/Decoder COLP Connected line presentation COLR Connected line restriction CS-CN Circuit Switched Core Network CSD Circuit Switched Data CW Call Waiting
DHCP Dynamic Host Configuration Protocol DTMF Dual Tone Multiple Frequency
ECT Explicit Call Transfer EDGE Enhanced Data Rates for GSM Evolution EFR Enhanced Full Rate EIR Equipment Identification Register ETSI European Telecommunications Standards Institute
GGSN Gateway GPRS Support Node
25
PUBLIC GHLR Gateway Home Location Register GMSC Gateway Mobile Switching Centre GPRS General Packet Radio Service GSM Global System for Mobile Communication gsmSCF GSM Service Control Function GSN GPRS Support Node GTT Global Title Translation
HID Handset Identification Display HLR Home Location Register HHLR Hub Home Location Register HPLMN Home Public Land Mobile Network HSPA High Speed Packet Access HSDPA High Speed Downlink Packet Access HSUPA High Speed Uplink Packet Access HNB-GW Home Node B GateWay HTTP Hypertext Transport Protocol
IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity IP Internet Protocol IPCP Internet Protocol Control Protocol ITU International Telecommunication Union ISDN Integrated Services Digital Network ISUP ISDN user part Iu-CS Iu – Circuit Switch Iu-PS Iu – Packet Switch Iuh Iu home IVR Interactive Voice Response
Kc Cipher/Decipher Key Ki Subscriber Authentication Key
LAC Location Area Code LAN Local Area Network LHLR Local Home Location Register LTE Long Term Evolution
MAC Media Access Control MAP Mobile Application Part MGS MAP Gateway Subsystem MGW Media Gateway MMS Multi-media Messaging Service MMSC Multi-media Messaging Service Centre MNO Mobile Network Operator MO Mobile Originated MS Mobile Station MSC Mobile Switching Centre MSISDN Mobile Station ISDN Number MT Mobile Terminated MTP Media Termination Point
NBAP Node-B Application Part NSS Network Switching Subsystem
PBX Private Branch eXchange
26
PUBLIC PDP Packet Data Protocol PLMN Public Land Mobile Network PMR Private Mobile Radio PSTN Public Switched Telephone Network
QoS Quality of Service
RADIUS Remote Authentication Dial-In User Service RAID Random Array of Inexpensive Discs RAN Radio Access Network RANAP Radio Access Network Application Part RB Radio Bearer RFC Request For Comment (IETF Standards Specification) RLC Radio Link Control RNC Radio Network Controller RNSAP Radio Network Subsystem Application Part RRC Radio Resource Control RRM Radio Resource Management RTP Real Time Protocol
SG Signalling Gateway SGSN Serving GPRS Support Node SIGTRAN Signalling Transport SIM Subscriber Identification Module SIP Session Initiation Protocol SMPP Short Message Peer-to-Peer Protocol SMS Short Message Service SMSC Short Message Service Centre SQL Structured Query Language SRB Signalling Radio Bearer SS7 Signalling System No 7 SSS SIP Gateway Subsystem STP Signalling Transfer Point
T-MAP Proprietary May base Protocol - PMN Networking
TDM Time Division Multiplex TMSI Temporary Mobile Subscriber Identity TTI Transmission Time Interval
UE User Equipment UMTS Universal Mobile Telecommunications System UPS Uninterruptible Power Supply USIM Universal Subscriber Identity Module USSD Unstructured Supplementary Service Data
27
PUBLIC VLR Visited Location Register VMSC Visited Mobile Switching Centre
WAN Wide Area Network WAP Wireless Application Protocol
3GPP 3GPP Specifications & Technical Reports
28
PUBLIC
QWB1466 v1.11
This document is provided for information only. In line with company policy of continued improvement of products and services, TeleWare reserves the right to alter product specification without notice. Private Mobile Networks is a registered trademark. Copyright © 2015 TeleWare plc.
Private Mobile Networks York Road, Thirsk, T: +44 (0) 1845 52 10 52 North Yorkshire, YO7 3BX, UK E: [email protected] Registered in England No 5614745 W: www.privatemobilenetworks.com
29