System and method for enabling call originations using SMS and hotline capabilities

• US 10,313,846 B2
• Filed: 10/10/2017
• Issued: 06/04/2019
• Est. Priority Date: 03/02/2006
• Status: Active Grant

• Current Assignee: Tango Networks Incorporated
• Original Assignee: Tango Networks Incorporated
• Inventors: Silver, Andrew
• Primary Examiner(s): Sivji, Nizar N
• Application Number:
  US15/729,265
• Publication Number:
  US 20180098204A1
• Time in Patent Office: 602 Days
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04M 2207/18 wireless networks
• CPC Class Codes: H04M 3/42042 Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile
• CPC Class Codes: H04M 3/42382 Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
• CPC Class Codes: H04Q 2213/1307 Call setup
• CPC Class Codes: H04Q 2213/13091 CLI, identification of calling line
• CPC Class Codes: H04Q 2213/13098 Mobile subscriber
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13109 Initializing, personal profile
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13152 Callback
• CPC Class Codes: H04Q 2213/13176 Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/1318 Ringing
• CPC Class Codes: H04Q 2213/13196 Connection circuit/link/trunk/junction, bridge, router, gateway
• CPC Class Codes: H04Q 2213/13206 User-to-user signaling, UUS
• CPC Class Codes: H04Q 2213/1322 : PBX
• CPC Class Codes: H04Q 2213/13336 : Store & forward, messaging systems
• CPC Class Codes: H04W 4/14 : Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections

Abstract

A method for handling call originations is provided. The method includes sending origination information from a mobile device to an application server in an enterprise network using Short Message Service (SMS) and determining whether a hotline feature is present in a subscriber profile associated with the mobile device. Data is then routed from the mobile device to a predetermined destination based on the hotline feature.

Claims

1. A method, comprising:

activating a hotline feature in a subscriber profile associated with a mobile device;

initiating a communication session from a mobile device intended for a destination device;

transmitting a data message from a gateway server to an application server comprising session setup information corresponding to the communication session and originating subscriber information corresponding to the mobile device and destination information corresponding to the destination device,

responsive to receiving the data message at the application server,

storing the originating subscriber information and the destination information;

routing a first session leg from the mobile device to a gateway server;

instructing the gateway, via the application server, to initiate routing a second session leg from the gateway server to the destination device; and

joining, via the gateway server, the first session leg and the second session leg to complete the communication session between the mobile device and the destination device.

2. The method of claim 1, wherein the data message is one of a short message service (SMS) message, a mobile data message and an unstructured supplementary service data (USSD) message.

3. The method of claim 1, wherein the mobile device accepts the routing of one or more of the session legs automatically.

4. The method of claim 1, further comprising analyzing possible session routes via the gateway server for routing the communication session and rerouting the communication session to an enterprise network.

5. The method of claim 4, wherein the enterprise network processes the communication session with a voice over the Internet protocol (VoIP).

6. The method of claim 1, wherein the second session leg is established at least one of simultaneously, in advance of, and after the first session leg is established.

7. A method, comprising:

responsive to receiving, at an application server, a data message comprising originating subscriber information corresponding to a mobile device and destination information corresponding to a destination device in advance of a first session leg routed from the mobile device to a gateway server communicatively coupled to the application server based on an activated hotline feature in a subscriber profile associated with the mobile device;

storing the originating subscriber information and the destination information;

routing the first session leg from the mobile device to the gateway server;

instructing the gateway, via the application server, to initiate routing a second session leg from the gateway server to the destination device; and

joining, via the gateway server, the first session leg and the second session leg to complete a session between the mobile device and the destination device.

8. The method of claim 7, wherein the data message comprises a session request as one of a short message service (SMS) message, a mobile data message and an unstructured supplementary service data (USSD) message.

9. The method of claim 7, wherein the second session leg is established at least one of simultaneously, in advance of, and after the first session leg is established.

10. The method of claim 7, further comprising:

responsive to receiving a session request, originating the session via the application server to the destination device identified via the session request;

receiving a response to the session request from the destination device at the application server; and

transmitting a session connection message to the mobile device from the application server indicating a session connection to the destination device.

11. The method of claim 7, comprising performing a handover to a different communication network than a communication network of at least one of the first session leg and the second session leg.

12. The method of claim 11, wherein the different communication network is at least one of a WiFi network, a packet data network and a cellular network.

13. The method of claim 7, wherein a third session leg is established if one of the first session leg and the second session leg fails and is used to re-establish a connection for the failed session leg while the other session leg is still active.

14. The method of claim 13, wherein a party connected to the remaining of the first and the second session legs is notified of a connection re-establishment, and wherein the third session leg is established by one of the application server and the mobile device.

15. A non-transitory computer readable storage medium configured to store instructions that when executed causes a processor to perform:

activating a hotline feature in a subscriber profile associated with a mobile device;

initiating a communication session from a mobile device intended for a destination device;

transmitting a data message from a gateway server to an application server comprising session setup information corresponding to the communication session and originating subscriber information corresponding to the mobile device and destination information corresponding to the destination device,

responsive to receiving the data message at the application server,

storing the originating subscriber information and the destination information;

routing a first session leg from the mobile device to a gateway server;

instructing the gateway, via the application server, to initiate routing a second session leg from the gateway server to the destination device; and

joining, via the gateway server, the first session leg and the second session leg to complete the communication session between the mobile device and the destination device.

16. The non-transitory computer readable storage medium of claim 15, wherein the data message is one of a short message service (SMS) message, a mobile data message and an unstructured supplementary service data (USSD) message.

17. The non-transitory computer readable storage medium of claim 15 configured to store instructions that when executed causes the processor to perform:

capturing and analyzing origination information and destination information from the gateway server (GS);

identifying a route to the final destination via the GS; and

routing the communication session to the final destination via the GS based on the identified route.

18. The non-transitory computer readable storage medium of claim 15, wherein the identified route is part of an enterprise network.

19. The non-transitory computer readable storage medium of claim 18, wherein the enterprise network operates with a voice over the Internet protocol (VoIP).