IP Library Granted Patent US 8,989,179
Granted Patent B2
US 8,989,179 · App. 13/726,777 · Granted Mar 24, 2015

System and method for originating a call via a circuit-switched network from a user equipment device

Inventors: Adrian Buckley (Tracy, CA); Jan Hendrik Lucas Bakker (Irving, TX)
Assignee: BlackBerry Limited
H04M7/0075H04L12/66H04W8/26H04W76/022H04L65/1069H04W76/021H04W80/10H04L65/1016H04L65/1006
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,989,179
App. No.
13/726,777
Granted
Mar 24, 2015
Kind
B2
Abstract

In one aspect, an application server (AS) node comprises a processor configured to receive a first SIP Invite request from the UE device, the first SIP Invite request having call information which includes a URI of a called party and data indicating that the first SIP Invite request is for a bearer over a circuit-switched (CS) network. An E.164 number is associated with the call information in the first SIP Invite request and a SIP response including the E.164 number is sent to the UE device in response to receiving the first SIP Invite request. When a call setup message including the E.164 number received from the CS network, the received E.164 number is verified if it is valid and if so, the call information is identified based on the E.164 number and is sent to the called party via a second SIP Invite request.

Claims (30)

1. A method for an application server (AS) node, the method comprising:

receiving a first SIP Invite request from a mobile communication device, the first SIP Invite request having call information which includes a call reference number, a uniform resource indicator (URI) of a called party and data used for determining whether the first SIP Invite request is for a bearer over a circuit-switched (CS) network;

associating an E.164 number with the call information in the first SIP Invite request;

sending a SIP response to the mobile communication device in response to receiving the first SIP Invite request, the SIP response including the E.164 number and the call reference number;

after sending the SIP response, receiving a call setup message from the CS network, the call setup message having the E.164 number;

verifying that the received E.164 number remains valid;

identifying the call information based on the E.164 number; and

sending, to the called party, a second SIP Invite request that includes the call information.

2. The method of claim 1 , further comprising:

identifying the URI of the called party in a TARGET field of the first SIP Invite request.

3. The method of claim 1 , wherein a URI field of the first SIP Invite request is populated with a public service identifier (PSI) of the AS node of an Internet Protocol (IP) multimedia subsystem (IMS) network.

4. The method of claim 1 , further comprising:

reading the data; and

determining, based on the data, that the first SIP Invite request is for the bearer over the CS network.

5. The method of claim 1 , wherein the call setup message is another SIP Invite request.

6. An application server (AS) node comprising:

a processor configured to:

receive a first SIP Invite request from a mobile communication device, the first SIP Invite request having call information which includes a call reference number, a uniform resource indicator (URI) of a called party and data used for determining whether the first SIP Invite request is for a bearer over a circuit-switched (CS) network;

associating an E.164 number with the call information in the first SIP Invite request;

send a SIP response to the mobile communication device in response to receiving the first SIP Invite request, the SIP response including the E.164 number and the call reference number;

after sending the SIP response, receive a call setup message from the CS network, the call setup message having the E.164 number;

verify that the received E.164 number remains valid;

identify the call information based on the E.164number; and

send, to the called party, a second SIP Invite request that includes the call information.

7. The AS node of claim 6 , wherein the processor is further configured to identify the URI of the called party in a TARGET field of the first SIP Invite request.

8. The AS node of claim 6 , wherein the processor is further configured to select the E.164 number by allocating the E.164 number from a plurality of E.164 numbers.

9. The AS node of claim 6 , wherein the processor is further configured to:

read the data; and

determine, based on the data, that the first SIP Invite request is for the bearer over the CS network.

10. The AS node of claim 6 , wherein the call setup message is another SIP Invite message.

Assignments (4)
CHANGE OF NAME Recorded Oct 20, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 034016/0738 →
CHANGE OF NAME Recorded Aug 18, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 033551/0640 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 28, 2013
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 029705/0825 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 11, 2013
From: BUCKLEY, ADRIAN; BAKKER, JAN HENDRIK LUCAS
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 029613/0535 →
Continuity (5)
Continuation 12732041 · Mar 25, 2010
Continuation 11740102 · Apr 25, 2007
Continuation In Part 11542462 · Oct 3, 2006
Continuation In Part 11347874 · Feb 6, 2006
Related Publication 20130107876A1 · May 2, 2013