EP3416350A1

EP3416350A1 - Method of making voip call on a mobile communication device

Info

Publication number: EP3416350A1
Application number: EP18173719.8A
Authority: EP
Inventors: Vladislav Sobolev
Original assignee: Top Connect Oue
Current assignee: Top Connect Oue
Priority date: 2017-06-13
Filing date: 2018-05-23
Publication date: 2018-12-19
Anticipated expiration: 2038-05-23
Also published as: EP3416350B1; EE01424U1

Abstract

The invention is provided to enable to the caller having in his mobile device installed VoIP application to make a VoIP call starting it as a regular Mobile Originated call, i.e. using for initiating the call the usual means - keyboard, call history, phone book. Mobile network uses CAMEL for intercepting the Mobile originated call, extracting from this call the call-related information and uses it for sending the PUSH-message to the mobile device, where PUSH-message activates VoIP application and the activated VoIP application initiates VoIP outbound call.

Description

Technical Field

The present invention relates to mobile cellular telecommunication networks and application software for Mobile Communication Devices (hereinafter - Mobile Device). More particularly, the present invention relates to methods of enrichment of Mobile Device's capabilities to implement features, which are not available on the Mobile Device, due to software and/or hardware limitations.

Background Art

VoIP (Voice over Internet Protocol) technology is widely used in voice-communications. VoIP technology has many advantages comparing with classic PSTN (Public Switched Telephone Network) telephony. The usual advantages are following cheaper cost, saving of the network bandwidth, better voice quality, faster call connection time, etc.
Current VoIP technology is used in mobile networks on the consumer market by two main methods:
firstly the external applications including downloadable on smartphones VoIP applications - first of all Viber (https://www.viber.com): also a Skype (https://www.skype.com) and WhatsAPP (https://www.whatsapp.com). These applications are easy to install, they do not need to have support from the Mobile networks, they work on almost on any smartphone, there is no need to have any integration with mobile networks, the applications are cheap to implement by service provider or Mobile operator.
All these VoIP applications have similar drawbacks.
Mobile user is unable to make VoIP-call by native way: impossible to dial from native phone dialler, or repeat a call from a call history, or make a call from the address-book, because these calls are impossible to intercept by Mobile Applications using tools provided by OS (Operating System), so Mobile Application cannot convert them into VoIP calls.
In order to make a VoIP call user must find icon of the Mobile Application first, then tap to open it, then must figure out how to dial from this specific application, because the way of presentation of dialling screen is significantly different from the native screen, in many cases user need to find a dialler somewhere in menu of this VoIP application, which required from the user even more effort.
As a conclusion the usability of these applications for ordinary outbound calls is low and their use forces the users to change their habits significantly.
In some cases the problem can be solved by deep modification of OS, but this way will not work for downloadable applications at all, because user need to reinstall OS, make jailbreak to achieve root-rights and these operations are extremely complex and dangerous for ordinary use, the handset can be broken after such upgrade, so this way is not applicable for billions users and their handsets on the market, so the only way to use it for user to achieve the native dialling - to change the handset to compatible with such method.
On some versions of Android OS are possible to intercept native dialling from the VoIP application, but this solution has following drawbacks.
It does not work on all Android versions.
When user dials first time OS may POP-up additional dialog window to choose the default dialling application, this dialog window may confuse the user and user may select wrong answer.
In some cases it does not work if user will dial a number from a call history which was dialled previously via mobile network.
On some versions of iOS are possible to redial via call history, if the call previously was dialled manually from the VoIP application, so user still have to open the VoIP application in order to make this first call.
These solutions are not universal for all handsets but OS-specific ways which work in some specific cases.
Second main method for use of VoIP technology in mobile networks on the consumer market are Network supported applications, e.g. VoLTE or Voice over LTE (http://www.radio-electronics.com/ info/cellulartelecomms/Ite-long-term-evolution/voice-over-Ite-volte.php). They are implemented on handsets level, required support from Operating System, hardware and software, has to be integrated with Mobile network. Advantage of these applications is native way of usage, no need to open Mobile Application in order to make a call, so no need to change habits by the user. As a drawback - VoLTE technology requires support from handset's hardware and software, and has to be deeply integrated with Mobile network. This is very expensive way: to implement this technology mobile operator has to make huge changes in mobile network including building LTE network, and user must change the handset to compatible with VoLTE.
These above solutions have the following drawbacks:

Need to have a handset which supports VoLTE, unfortunately billions handsets on the market have no such support, so the only way to use it for user - change the handset to compatible;
Mobile network must have support of VoLTE, it is extremely expensive for mobile operator;
VoLTE does not work in Roaming by default, the Operator must do VoLTE roaming with each foreign operator.

Summary of invention

The aim of the invention is to modify the procedure of processing of an Outbound call in the Mobile Network enabling to transfer a Mobile Originating call initiated by the caller by simple dialling of the addressee's number from the mobile device's keyboard, or taken either from Address Book or Call History into VoIP call, in other words to enable to the user to dial (initiate) a VoIP call as an usual Mobile Originating call. For this the technical problem on how to transform a made by the caller a Mobile Originating call to a VoIP call both in Home Mobile Network and in Visited Mobile Network (roaming) is to be solved.
The subject aim is achieved using a method of making VoIP call on a mobile device having an installed VoIP application, where Mobile Network using CAMEL (Customised Application for Mobile network Enhanced Logic ) intercepts the caller dialled Mobile Originating call, extracts from this call the call-related information and terminates the Mobile Originating Call, the extracted information is used to send PUSH-message to the mobile device, this PUSH-message is used to activate VoIP application having ability to initiate by receiving the PUSH-notification a VoIP outbound call, hence this activated VoIP application initiates a VoIP outbound call.
The call-related information contains at least the destination number dialled by the caller.
Mobile Network terminates Mobile Originating Call before VoIP outbound call reaches the Destination.

Brief description of drawings

The embodiment of the invention will further be described with reference to the listed below drawings:

Figure 1 - Mobile Device and the structure Mobile Network Setup to initiate VoIP Call using CAMEL and PUSH-message.
Figure 2 - Flow chart of the Outbound VoIP call initiated via CAMEL and PUSH-message.

Description of embodiments

Disclosed on Figure 1 Mobile Device and the structure Mobile Network Setup to initiate VoIP Call using CAMEL and PUSH-message includes belonging to the user mobile device (smartphone) 1 with installed VoIP Application 2, at that the VoIP Application 2 shall have ability to initiate an outbound call when receiving the respective PUSH-notification from the PUSH server 8. The mobile device 1 is able to use mobile services in Mobile Network 4 in HLR/HSS 5 via wireless connection 3. CAMEL GW 7 is connected to PUSH server 8 and to the signalling network MSC (Mobile Switching Centre) 6 and acts here as gsmSCF (GSM Service Control Function).
CAMEL GW 7 is configured to recognize Mobile User's outbound calls (MOC) received from the signalling network MSC 6, to extract from this call the call-related information and to deliver this information (MSISDN and B-nr (B-number) dialled by the caller) to PUSH Server 8. PUSH Server 8 is connected to Packet Data networks (PDN, Internet) and is able to send PUSH message to Mobile Device 1 via PUSH services, for example via Apple Push Notification service (APNs), Google Cloud Messaging (GCM) or by any similar way. VoIP Application 2 and Operating System (OS) on Mobile Device 1 are configured to react on PUSH-messages in a way to generate outbound VoIP-Call via available Mobile DATA-connectivity (Including Mobile DATA in Mobile Network 4, WiFi 13, etc.). VoIP GW 10 is connected to Packet Data networks (Internet) and to GGSN/PGW 9 to receive VoIP Call from Mobile User and subsequently to deliver this VoIP call 11 to Destination User 12.
Presented in Figure 2 flow chart discloses in detailed way the call flow according to the present invention.
Mobile User makes a regular outbound call from his Mobile Device 1 dialling Destination Number (B-nr) from the Native Dialer, or from Call History, or from Address Book i.e. using the traditional means for initiating a call.
Mobile Device 1 takes this call and starts making Call setup via Mobile Network 3.
Call setup Signalling reaches MSC 6.
MSC 6 delivers Initial DP message (call) to GAMEL GW 7 (gsmSCF); GAMEL GW 7 extracts MSISDN or IMSI, and B-nr from the CAP (Camel Application Part) signalling flow and delivers it to Push Server 8.
Push Server 8 converts MSISDN or IMSI into corresponding device Token and sends PUSH-message to Mobile Device 1. PUSH-message contains at least B-nr as a payload.
OS on the Mobile Device 1 based on received Token from the PUSH-message initiates (wakeup or start) corresponding VoIP Application 2 and delivers B-nr as a payload.
VoIP Application 2 makes a VoIP Call via VoIP GW 10. In general it can be any type of VoIP protocol, in particular SIP-protocol (Session Initiating Protocol) use of which is shown on FIG. 2 as an example of usage. For SIP-protocol VoIP Call starts from INVITE message. Alternatively instead of SIP any other VoIP protocol could be used with corresponding changes in VoIP call flow.
INVITE reaches VoIP GW 10, MSISDN can be used as CgPN (Calling Party Number), and B-nr can be used as CdPN (Called Party number, same as B-Nr).
As soon as INVITE reaches VoIP GW 10, VoIP GW 10 sends message for release still regular outbound Camel call attempt "Camel call Release" via Camel GW 7 to MSC 6.
MSC 6 sends the received "Camel call Release" message towards the Mobile Device 1.
INVITE reaches Destination User Equipment (UE) 12.
Message 180 Ringing is sent from Destination User 12 Equipment back to VoIP Application 2 via VoIP GW 10.
Mobile User hears Ringing as well (long rings or similar audio).
As soon as Destination user 12 will answer, the message 200 OK will be sent from Destination User 12 Equipment back to VoIP Application 2 via VoIP GW 10.
VoIP Application 2 will send ACK (acknowledgement) message to Destination User Equipment 12.
RTP-path will be established between VoIP Application 2 and Destination User Equipment 12 together with connection to Mobile User - the conversation is started.
After the conversation, any participant can send a BYE request to terminate the session. On FIG.2 as an example calling party (Mobile User) terminates a SIP-Call.
Alternatively, instead of INVITE any other Success event at any step could be used to determinate if VOIP call could be made or not.
Above has been represented the method for making VoIP Call in home network. To make this method work in the roaming too (in visited networks), each visited network must have the Camel Roaming with Home Network.

Claims

Method of making a VoIP call on a mobile device having installed VoIP application, characterized in that the method comprises the following steps:
a Mobile Originated call made by the user is sent to the Mobile Network;

the Mobile Originated call is intercepted by the Mobile Network using CAMEL;

the call related information is extracted from the Mobile Originated call by the Mobile Network using CAMEL;

the Mobile Originated call is terminated by the Mobile Network using CAMEL; the call-related information is sent to a PUSH-server;

a PUSH-message is sent to the mobile device by the PUSH-server;

a VoIP application having ability to initiate by receiving the PUSH-notification a VoIP outbound call is activated by the PUSH-message and;

the VoIP outbound call is initiated by the activated VoIP application.
Method according to claim 1, characterized in that the call-related information contains at least the destination number dialled by the caller.
Method according to claim 1, characterized in that the Mobile Originating Call is terminated by the Mobile Network before the VoIP outbound call reaches the Destination User.