mobile ip pbx low level design - v0 5

1

Low Level Design forMobile PBX

May, 2010

Version Changes Date

0.1 Initial draft May 10, 2010

0.2 Changes according to STC comments May 16, 2010

0.3 Final changes – technical part June 5, 2010

0.4 Prefix updated August 10, 2010

0.5 Changes according to STC comments August 11, 2010

Contents

1 Introduction ............................................................................................ 5

2 Mobile PBX Solution Architecture ............................................... 72.1 Solution .................................................................................................... 72.2 Supported Features ................................................................................. 92.3 Service Customization (Business/Private Role)..................................... 102.4 Scenarios........................................................................................... 112.4.1 Mobile Originated Call (private role) ...................................................... 112.4.2 Mobile Originated Call (business role) ................................................... 122.4.3 hiQ4200 Originated Call (business role) ................................................ 132.4.4 Mobile Terminating Call ......................................................................... 142.5 End to End Call Flows............................................................................ 152.5.1 Call Flows .............................................................................................. 152.5.2 Special Cases ........................................................................................ 182.6 Technical Requirements ........................................................................ 19

3 Mobile PBX Implementation................................................................ 203.1 Software/License Updates ..................................................................... 203.2 Integrations ............................................................................................ 223.3 Installations ............................................................................................ 22

4 Appendix - Glossary ............................................................................ 23

4 (24)

[Type text]

Table of FiguresFigure 1: Solution Overview........................................................................................................................ 5Figure 2: Solution Architecture - The parts marked in RED are new additions in this project. The

boxes in ORANGE have software/license updates in the project ..................................................................... 7

Figure 3: Mobile PBX Connectivity ............................................................................................................ 8Figure 4: Mobile originated Call (private role) ........................................................................................ 11Figure 5: Mobile originated Call (business role) .................................................................................... 12Figure 6: hiQ4200 originated Call (business role) ................................................................................. 13

1 Introduction

Mobile PBX is a solution that delivers PBX functionality such as Attendant service, Call Hunting, Outgoing Call Blocking as a service available over the GSM Network. Fixed and Mobile network can offer to their enterprise customers hosted communication services, covering simultaneously mobile and fixed users.

Figure 1: Solution Overview

The users can be combined in the same private numbering plan and have a common set of business group features like enterprise common contact list, presence status of other users, or definition of line, toll or call restrictions. Depending on the sort of terminal, subscriber features are assigned to each individual user, like speed diali‐ ng, calling number display, creation of black list‐ / white list‐ for screening, support of conference calls. The hiQ 4300 based ComManager can be used to view the calls, configure calls (e.g. define rules for inbound calls, define presence status), control calls (e.g. accept and end Voice / Video calls, initiate Voice/Video calls, Transfer, On Hold, retrieve ).

6 (24)

The scope of this project is to provide IP Centrex features (originating, terminating and mid‐ call features) as well as web services (presence, address book, call control, call journal, feature settings) to the mobile network users.

Migrations scenarios (e.g. fixed mobile substitution with the re‐use of the SIP based landline phone number) shall be supported. Following items are included in the scope of this project:

• hiQ4200/4300 system expansion with 4k PBX/IP‐PBX & 6k Mobile Centrex users

• Movious expansion

• Integration with Mobile network (optional physical connectivity)

• Multi Vendor Integration (application level integration)

• Service Customization (business/private role functionality)

• Integration & Verification with Billing system

• Integration & Verification with Provisioning system

• Integration & Verification with OSS

• iSuite NMS/EMS Application expansion

2 Mobile PBX Solution Architecture

2.1 SolutionMobile PBX solution is built on top of the existing IP Centrex which uses the Application Servers hiQ4200 and hiQ4300. This feature allows a Business Group to span across Mobile 2G and 3G Endpoints (GSM, UMTS). The hiQ4200 provides IP Centrex services for dynamically registered SIP subscribers, as well as for Mobile subscribers who are provisioned statically as virtual SIP subscribers on the hiQ.

Figure 2: Solution Architecture The‐ parts marked in RED are new additions in this project. The boxes inORANGE have software/license updates in the project

The hiQ 4200 (VoIP server) and hiQ 4300 (Business Management server) are connected to the mobile network via the NGN network. And opposite, mobile devices are connected via the MSC / NGN to the voice application server. SIP phones (and PBX’s) are connected via the Session Border Controller to the voice applications server.

8 (24)

When a Mobile subscriber initiates or receives a call, the mobile network transfers the call to NGN via PSTN (SN), which then forwards it to the hiQ4200 via SIP I‐ GW. The hiQ4200 executes A party‐ and/or B party‐ services and routes the call to either the NGN or a SIP Client depending on the destination of the called party.

Web based‐ rich communication services are accessed via any standard internet browser or via a dedicated JAVA application installed on the mobile phone.

Figure 3: Mobile PBX Connectivity

The service triggering is done based on the prefix to the B party‐ number. The MSC will forward the call with prefix to the NGN network. The NGN soft switch will forward call to IPCX (SIP I‐ GW) based on prefix to the B Party‐ number. The voice application server will execute the originating and (if possible) the terminating services. The MSC and NGN soft switch need to support the P‐ asserted ide‐ ntity (calling party number) and the privacy (CLIR) headers.

When using international trunks between the visited MSC and the NGN the assigned routing prefix and the dialed number must not exceed the maximum called party number length supported via the international trunk. Charging of incoming calls in case Mobile user is roaming would have high processing impact on Billing system. Due to this, roaming for Mobile subscribers will not be allowed.

The Mobile PBX user will be a postpaid subscriber which will be able to use his Mobile serviceseven if his personal limit has been reached.

2.2 Supported Features

The Mobile PBX supports the following features:

Basic VoIP:• Support Presence Service with Presence Screening List (redisplay via refresh button)• Calling Number Delivery• Call Forwarding Variable Unconditional (CFV)• Call Forwarding Busy Line (CFBL)• Call Forwarding Fixed• Call Forwarding Don't Answer (CFDA)/No Reply• Courtesy Call for Call Forwarding• Remote Activation Call Forwarding (RACF)• Anonymous Call Rejection (ACR)• Simultaneous Ringing• Direct Outward Dialing (DOD)• Direct Inward Dialing (DID)• Business Group Main Number• Fully Restricted Originating/Terminating Line• Semi Restricted Originating/Terminating Line• Traffic Measurements for Business Groups• Billing for Business Groups• Private Dialing and Numbering Plans• Extension Dialing• Serial Ringing• Toll & Call Restrictions

ComManager Mobile• Missed Call Logs• Hosted Contact List with Presence Status• Visual MWI Indication• Dial From Contact List / Missed Call Logs• Set own Presence Status• Set Own Forwarding Status• Web based mid call features

via GSM Network‐ GSM Device‐• Three Way Calling• Call Hold• Connected Party ID Display (intra switch)‐

10 (24)

• Calling Party ID Display (intra switch)‐• Call Waiting• Call Waiting Caller Notification

List maintained by Web GUI via PC• Selective Call Forwarding (via screening list only)• Enhanced/ Selective Call Forwarding• Selective Call Rejection (SCR)• Selective Call Acceptance (SCA)• ComMobile Rules settings ( Rules, Contacts etc.)

Voicemail, Unified messaging• Full set of features

2.3 Service Customization (Business/Private Role)

requires this project to utilize only the existing network capabilities. Also it is required to customize the service to support private and business roles for mobile users.

User’s default role is “private”. In this case hiQ4200 originating services are not triggered. The user is presented with the MSISDN to the called party. The “business role” option is available on per call basis. The hiQ4200 originating services are triggered in this case and the user is presented with the business number to the called party.

For the terminating calls, hiQ4200 terminating services are not triggered if the call is made to user’s MSISDN and the call is delivered as per the existing routing/LNP. The hiQ4200 terminating services are triggered if the call is made to user’s business number and the call is forwarded to MSISDN.

2.4 Scenarios

2.4.1 Mobile Originated Call (private role)

Dial manually or from thephone contactlist

Dial manually or fromthe hiQ4300 contactusing theComManager Mobile

Figure 4: Mobile originated Call (private role)

Regular CS call

1. The user dials the number of the called party as usual using the mobile phone or the CSversion of ComManager Mobile.

2. As the hiQ4200 is not involved in the call, no Ctx services are executed. With this short dialing (VPN service) is not possible.

3. The caller is presented with the MSISDN.

2.4.2 Mobile Originated Call (business role)

Dial manually or from thephone contact list(with pre‐assigned11* to the contact)

Dial manually or from the hiQ4300 contact using the ComManager Mobile and the “businesscall” option which willassign the 11* prefix

Regular CS call(11* shall result in routingthe call to hiQ4200)

Figure 5: Mobile originated Call (business role)

1. The user dials the number of the called party as usual using the mobile phone or the CSversion of ComManager Mobile and assigns a prefix (e.g. 11*).ComManager Mobile could assign the prefix also automatically to every call or e.g. tothe office phone number or to a dedicated category of the hiQ4300 contact.

2. Because of the prefix the mobile network shall involve hiQ4200 in the call. Short dialing(VPN service) and Ctx originating services (CLIR, OCB, USCID, media status) are possible.

3. When using the USCID service the caller is presented with the business number.

Note: Prefix 11* is shown here only as an example. In final solution prefix *3 will be used.

2.4.3 hiQ4200 Originated Call (business role)

Dial manually or from the hiQ4300 contact using the ComManager Mobile

MakeCallto 014435000

Translate dialstringExecute services (USCID)

Figure 6: hiQ4200 originated Call (business role)

1. The user is using the click to‐ dial‐ (C2D) version of the ComManager Mobile.

2. C2D ComManager Mobile will trigger the call setup via the mobile internet to the hiQ4300 / hiQ4200. The hiQ4200 will setup both call legs sequentially and connect them upon answer.

3. When using the USCID service the caller is presented with the business number.

14 (24)

2.4.4 Mobile Terminating Call

Called Party = MSISDN

• Without the T_CSI the hiQ4200 will not be involved in the terminating call leg. No terminating services are executed in the hiQ4200.

• The call is delivered to the mobile phone via the existing routing / LNP means in the operator’s network.

Called Party = Business Number

• The call to the business number shall be automatically routed via the existing routing/ LNP means to the hiQ4200.

• hiQ4200 will execute the terminating services associated with the business number.This services will be an operator provisioned CFSIE‐All to the user’s MSISDN. With this the hiQ4200 will execute the terminating services associated with the MSISDN, too.

• The call is delivered to the mobile phone via the existing routing / LNP means in the operators network. CF notification / COLP must not be used or COLR must be activated in the MSISDN profile to protect the MSISDN from being shown / announced to the caller.

2.5 End to End Call Flows

2.5.1 Call Flows

Mobile PBX user calling another Mobile PBX user Dial‐ from phone or call setup from ComMng M:

Mobile PBX user calling another Mobile PBX user Call setup‐ from ComManager:

16 (24)

Mobile PBX user calling CS user Dial‐ from phone or call setup from ComManag M:

CS user calling Mobile PBX user:

Mobile PBX user calling IP Centrex user Dial‐ from phone or call setup from ComManag M:

IP Centrex user calling Mobile PBX user:

18 (24)

2.5.2 Special Cases

Ctx user in business role calling MSISDN of another Ctx user

• If a Ctx user is using the business role and calling the MSISDN of another Ctx user, the called party will be validated in the hiQ4200 and the terminating services associated with the MSISDN profile will be executed.

• The execution of the terminating services associated with the MSISDN profile can be suppressed by explicitly routing the called MSISDN to the SIP I‐ GW destination. This will create the same user experience as in case of a call originated by a non‐Ctx user.

Ctx user in private role is calling another Ctx user

• If a Ctx user is using the private role and calling another Ctx user, the hiQ4200 will validate the callers number (the MSISDN) and execute the originating services (e.g. replace the MSISDN by the business number). This means that calling another Ctx user in a private role is not possible per default.

• If the use case must be supported in the operators network, the SIP I‐ GW must re‐ format the calling party number (P Asserted I‐ ‐ dentity) when not receiving the *3 prefix. If the hiQ4200 receives the P A I in‐ ‐ e.g. national format the originating services associated with the MSISDN will not be executed. An option is SIP I‐ GW sending the USCID suppression prefix for all calls which do not have the *3 routing prefix assigned to the called party number.

2.6 Technical Requirements

Following are the mandatory requirements for this project:

1. The V‐MSC to route a prefixed call to the NGN network. NGN SS to route a prefixed call to SIP I‐ GW (IPCX).

2. The MSC, NGN SS to support the P Asserted‐ ‐Identity (calling party number) and the privacy (CLIR) headers.

3. The MSC, NGN SS to support the diversion or history info headers to detect CF loops.

4. The MSC, NGN SS to support INVITE, reINVITE and UPDATE with or without SDP.

5. The mobile network to support GPRS or UMTS for HTTPS (SSL certificate) based internet connections for the web service delivery to the mobile phones.

6. The mobile phones to be JAVA capable.

7. The mobile phones to connect via UMTS or to support dual transfer mode (GPRS + CS)for web services used during an active CS call.

8. Zero size SDP INVITE message (SDP less‐ INVITE) need to be supported by all SIP entities in call trajectory. hiQ and SIP I‐ GW already support it. NGN, MNO side (Huawei SS, Huawei & E/// MSS) also need to be confirmed.

9. Number ranges have to be reserved as business numbers for all dual profile Mobile PBXusers and assigned to IP Centrex.

In addition to the above, below are the optional requirements:

1. The NGN SS to change the P Asserted I‐ ‐ dentity number format to a national one when processing the terminating routing number prefix.

2. The MSC, NGN SS to support SIP / ISUP mediation for enhanced services such asCCBS/NR.

3. The mobile network to support service codes, e.g. *21*destination or 2*21*destination(if the called party number must not start with “*”).

4. If integration to Al Jawal‐ network via NGN network is not supported, IP Centrex can be integrated with MNO directly. Then physical connectivity to the MNO and integration effort will be needed.

20 (24)

3 Mobile PBX Implementation

3.1 Software/License Updates

The following software/licenses expansions will be made during this project:

Model Description Item Description Total Qty

hiQ4200/4300 system expansion with 4k PBX/IP- PBX & 6k Mobile Centrex users (R13)

hiQ4300 Mobile Client SW for PDA and Mobile PhoneV2 (SW update via MS)

1


ATTENDANT 1,000


hiQ SW: Service provider Admin 10,000


hiQ SW: Advanced voice 1,000


hiQ SW: Office suite integration 1,000


hiQ SW: Group Admin 1,000


hiQ SW: Business voice 10,000


hiQ SW: Presence service 6,000


hiQ SW: COM MANAGER - Portal functionality 6,000


hiQ SW: Team function 1,000


hiQ SW: Family and community voice 10,000


hiQ SW: Base system software 10,000


hiQ SW: COM manager - Enhanced functionality 6,000


hiQ SW: Video telephony support 1,000


hiQ SW: Classic voice 10,000


hiQ SW: User self Admin 6,000


hiQ SW: GROUPWARE Server synchronisation 1,000


hiQ SW: Instant messaging support 1,000


hiQ SW: CALEA and Lawful Interception 10,000


hiQ SW: COM MANAGER - Basic functionality 6,000


Movious (expansion)

Movious (expansion)

Movious (expansion)

hiQ SW: Specific features for SIP users 1,000

Announcement/VR channel SW and Licensing 10

N-way conference channel SW and Licensing 7

FAX channel SW 1

Movious (expansion)Mereon UM Mailbox - UM subscriber software licensing

2,000

Movious (expansion) Conference Bridge Audio, WEB SW and Licensing 5

Movious (expansion) AUTO ATTENDANT SW AND LICENSING 2

iSuite NMS/EMS Application expansion (R13) iSuite Basic License per subscriber for hiQ 10,000

iSuite NMS/EMS Application expansion (R13) iSuite IPMC per subscriber for hiQ R13 10,000

NetManager expansionNETMANAGER BASE SYSTEM RTU FEE PER 1000PORTS. PACKAGE V6.2 3

NetManager expansion NETM BASE SYSTEM (per POP ports) 1,898

NetManager expansion NetM Georedundancy (per 1000 Ports) 3

NetManager expansion NETM PP: NetM Georedundancy (per POP ports) 1,898

NetManager expansionALARM INTERFACE RTU FEE PER 1000 PORTS. PACKAGE V6.2

3

NetManager expansion NETM PP: ALARM INTERFACE (per POP ports) 1,898

NetManager expansionTTY INTERFACE RTU FEE PER 1000 PORTS. PACKAGE V6.2

3

NetManager expansion NETM PP: TTY Interface (per POP ports) 1,898

NetManager expansionNETM TECHNOLOGY PACKAGE FOR STMI (per1000 trunks) 2

NetManager expansion SUBSCRIBER MAINTENANCE COMMAND 3

NetManager expansionPERFORMANCE DATA COLLECTION RTU FEE PER1000 TRUNKS. PACKAGE V6.2

2

NetManager expansion NETM PERF.DATA COLLECTION (per POP) 1,898

NetManager expansion NETM TECHNOLOGY PACKAGE FOR hiE9200 V4 3,796

NetManager expansionNetManager TP for IP UNITY, RTU fee per NEpackage V3.1

1

NetManager expansionNetManager TP for ACME, RTU fee per NE packageV5.0 1

NetManager expansion Integration services for NetManager expansion 1

22 (24)

3.2 Integrations

Following integrations will be performed during this project:


Integration with Mobile network Integration with Mobile network 1

Multi Vendor Integration (MVI) Mulit Vendor integration 1

Service Customization Service Customization 10

Integration & Verification with Billing system Integration & Verification with Billing system 1

Integration & Verification with Provisioing system

Integration & Verification with provisioing system 1

Integration & Verification with OSS Integration & Verification with OSS 1

3.3 Installations

Following installations will be performed during the project:



hiQ4200/4300 SW expansion installation 1

Redundant power supply for existing IP routers Installation of additional power supply for IP-router 2

4 Appendix - Glossary ACD Automatic Call Distribution ACP Access Control ProtocolADMOSS Advanced Multifunctional Operator Service SystemADSL Asymmetric Digital Subscriber LineATM Asynchronous Transfer ModeBG Business GroupBHCA Busy Hour Call AttemptsBICC Bearer Independent Call ControlBOOTP Bootstrap ProtocolB RAS‐ Broadband Remote Access Server CAGR Compound Annual Growth Rate CAPEX CApital EXPenditureCAS Channel Associated SignalingCBR Constant Bit RateCLIP Calling Line Identification PresentationCM Cable ModemCO Central OfficeCoPl Commercial PlatformCORBA Common Object Request Broker ArchitectureCPE Customer Premises EquipmentCPG Customer Premises GatewayCSTA Computer Supported Telecommunications ApplicationsCTI Computer Telephony Integration DHCP Dynamic Host Configuration Protocol DLU Digital Line UnitDN Directory NumberDOCSIS Data Over Cable Service Interface SpecificationsDSL Digital Subscriber LineDSLAM Digital Subscriber Line Access MultiplexerDSS1 Digital Subscriber Signaling No. 1DTMF Dual Tone Multi FrequencyETH EthernetFCAPS Fault, Configuration, Accounting, Performance Monitoring and SecurityFITL Fiber In The LoopFSK Frequency Shift Keying GUI Graphical User Interface GW GatewayHFC Hybrid Fiber CoaxHTTPS Hypertext Transport Protocol with Secure Socket LayerIAD Integrated Access DeviceIN Intelligent NetworkINAP Intelligent Network Application PartIP Internet ProtocolIPSEC IP Security ProtocolISDN Integrated Services Digital NetworkISP Internet Service ProviderISUP ISDN User PartIUA ISDN User Adaptation layer protocol IVR Interactive Voice Response Systems LAC Local area codeLAN Local Area NetworkLDAP Lightweight Directory Access ProtocolLEA LAW Enforcement AgenciesLEX Local ExchangeMG Media GatewayMGCP Media Gateway Control Protocol

24 (24)

MIB Management Information BaseMML Man Machine LanguageMSB Multifunctional Switchboard MSF Multiservice Switching Forum MSO Multiple Service Operators MTA Media Terminal AdapterMTP Message Transfer Part (#7) NAS Network Access ServerNAT Network Address TranslatorNGN Next Generation Network NNI Network Network Interface NPV Net Present ValueOAM&P Operation Administration, Maintenance and ProvisioningOPEX OPerational EXPenditure OSP Operator Service Provider OSS Operation Support System PBX Private Branch Exchange POP Post Office ProtocolPOTS Plain old Telephone ServicePRI Primary Rate InterfacePSTN Public Switched Telephone NetworkPVC Permanent Virtual ChannelQoS Quality of ServiceRAS Registration, Admission and StatusRDLU Remote DLURRS Registration and Roting ServerRSDLU Remote Shelter DLURTP Real Time Transport ProtocolSCTP Stream Control Transfer Protocol (RFC 2960) SDSL Symmetric Digital Subscriber LineSHDSL Symmetric DSLSIP SIMPLE SIP for Instant Messaging and Presence Leveraging ExtensionsSME Small Medium EnterpriseSMS Short Message ServicesSNMP Simple Network Management ProtocolSOAP/XML Simple Object Access Protocol/Extensible Markup LanguageSOHO Small Offices and Home OfficesSQL Structured Query LanguageSS7 Signaling System No.7SSH/CLI Secure Shell Command Line InterfaceSSL Secure Sockets LayerToS Type of ServiceTCP Transmission Control Protocol TGCP Trunk Gateway Control Protocol TTS Text To SpeechTTY Tele Type InterfaceUCD Uniform Call Distribution UM Unified Messaging VoCable Voice over CableVoDSL Voice over Digital Subscriber LineVoIP Voice over IPVPN Virtual Private Network WML Wireless Markup Language XML Extensible Markup Language

mobile ip pbx low level design - v0 5

Documents

mobile network users

mobile pbx connectivity

mobile pbx implementation

business role

fixed mobile substitution

control calls

voicevideo calls

inbound calls