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

• US 9,179,487 B2
• Filed: 04/05/2013
• Issued: 11/03/2015
• 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:
  US13/857,872
• Publication Number:
  US 20130223347A1
• Time in Patent Office: 942 Days
• Field of Search: 370/352, 370/328, 370/353, 370/401, 455/554.1, 455/435.1, 455/439, 455/445, 379/88.1
• US Class Current: 1/1
• 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 email H04Q2213/13375
• 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:

receiving a data message from a mobile device at an application server, the data message comprising an originating subscriber number corresponding to the mobile device and a destination number corresponding to a destination device;

routing the data message to a gateway server (GS);

responsive to receiving the data message, originating a session comprising a first session leg via the application server to the destination device identified via the data message;

establishing a second session leg to the mobile device via the application server;

joining the first session leg and the second session leg to establish an end-to-end session;

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;

wherein the mobile device accepts a routing session to an intermediary destination gateway server identified by a subscriber profile associated with the mobile device, wherein the intermediary destination is different from the final destination; and

routing the session from the intermediary destination to the final destination.

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

3. The method of claim 1, wherein the mobile device accepts the session automatically.

4. The method of claim 1, further comprising:

analyzing possible session routes via the GS for routing the session and re-routing the session to an enterprise network.

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

6. The method of claim 4, further comprising:

establishing a third session leg via a GS to a different communication network from the first session leg and the second session leg; and

handing over the session to the third session leg while at least one of the first session leg and the second session leg are still in progress.

7. 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.

8. A method comprising:

receiving a session request from a mobile device to a destination device at an application server, the session request comprising an originating subscriber number corresponding to the mobile device and a destination number corresponding to the destination device;

routing the session to a gateway server (GS);

establishing a first session leg to the destination device via the application server;

establishing a second session leg to the mobile device via the application server;

joining the first session leg and the second session leg to establish the session as an end-to-end session;

wherein the session request is one of a short message service (SMS) message, a mobile data message and an unstructured supplementary service data (USSD) message;

wherein the mobile device accepts a routing session to an intermediary destination gateway server identified by a subscriber profile associated with the mobile device, wherein the intermediary destination is different from the final destination; and

routing the session from the intermediary destination to the final destination.

9. The method of claim 8, wherein the session request is one of the short message service (SMS) message, the mobile data message and the unstructured supplementary service data (USSD) message.

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

11. The method of claim 8, further comprising:

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

receiving a response to the session 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.

12. The method of claim 8, 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.

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

14. The method of claim 8, further comprising:

establishing a third session leg to at least one of the first session leg and the second session leg; and

handing over the session to the third session leg while at least one of the first session leg and the second session leg are still in progress;

wherein the 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.

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

16. A method comprising:

originating a session from a mobile device to a final destination via a message comprising an originating subscriber number corresponding to the mobile device and a destination number corresponding to the final destination;

automatically routing the message to an intermediary destination gateway server (GS) identified by a subscriber profile associated with the mobile device, wherein an intermediary destination is different from the final destination and is identified via a specific route or trunk group;

routing the session from the intermediary destination to the final destination;

wherein the message is one of a short message service (SMS) message, a mobile data message and an unstructured supplementary service data (USSD) message;

wherein the mobile device accepts a routing session to an intermediary destination gateway server identified by a subscriber profile associated with the mobile device, wherein the intermediary destination is different from the final destination; and

routing the session from the intermediary destination to the final destination.

17. The method of claim 16, further comprising:

capturing and analyzing origination information and destination information from the GS; and

identifying a route to the final destination via the GS;

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

18. The method of claim 16, wherein the identified route is part of an enterprise network.

19. The method of claim 18, wherein the enterprise network operates with a voice over the Internet protocol (VoIP).