IP Library Granted Patent US 10,187,924
Granted Patent B2
US 10,187,924 · App. 15/789,586 · Granted Jan 22, 2019

System and method for managing emergency requests

Inventors: Jan Hendrik Lucas Bakker (Keller, TX); Adrian Buckley (Tracy, CA); Andrew Michael Allen (Hallandale Beach, FL)
Assignee: BlackBerry Limited
H04W76/50H04L65/1006H04L65/1016H04L65/1069H04L65/40H04M3/42348H04W4/90H04M3/42068H04M7/006H04M2242/04H04W4/02H04W80/10
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 10,187,924
App. No.
15/789,586
Granted
Jan 22, 2019
Kind
B2
Abstract

A network component is provided. The network component including a component configured such that the network transmits a response message containing an indicator indicating that a first message is an emergency-related request, and such that the network receives a second message containing information associated with a user equipment (UE).

Claims (34)

1. A method for responding to an emergency-related message by a network node, the network node within a trust domain, the method comprising:

receiving, from a user equipment (UE), a first Session Initiation Protocol (SIP) request message;

determining, at the network node, that the first SIP request message is an emergency-related request;

based on the determining, including, by the network node, the following in a SIP rejection response message: a P-Asserted-Identity header field identifying the network node, an indicator indicating that the first SIP request message is an emergency-related request, and a Contact header field comprising a Uniform Resource Name (URN) of an emergency service; and

sending, by the network node, the SIP rejection response message.

2. The method according to claim 1 , wherein the URN of the emergency service comprises a code identifying a country.

3. The method according to claim 1 , wherein the URN of the emergency service comprises a code identifying a region.

4. The method according to claim 1 , further comprising: receiving a second SIP request message, wherein the second SIP request message comprises the URN of the emergency service, and emergency-related information associated with the UE.

5. The method according to claim 4 , further comprising: sending a message based on the second SIP request message towards a Public Safety Answering Point (PSAP).

6. The method of claim 4 , wherein the emergency-related information associated with the UE included in the second SIP request message comprises at least one of a UE location or UE access network information.

7. The method according to claim 1 , wherein, prior to sending the SIP rejection response message, the UE is unaware that the first SIP request message is an emergency-related request.

8. The method according to claim 1 , wherein the network node comprises a proxy call session control function (P-CSCF).

9. A network node within a trust domain, the network node comprising:

at least one hardware processor; and

a non-transitory computer-readable storage medium coupled to the at least one hardware processor and storing programming instructions for execution by the at least one hardware processor, wherein the programming instructions, when executed, cause the network node to perform operations comprising:

receiving, from a user equipment (UE), a first Session Initiation Protocol (SIP) request message;

determining, at the network node, that the first SIP request message is an emergency-related request;

based on the determining, including, by the network node, the following in a SIP rejection response message: a P-Asserted-Identity header field identifying the network node, an indicator indicating that the first SIP request message is an emergency-related request, and a Contact header field comprising a Uniform Resource Name (URN) of an emergency service; and

sending, by the network node, the SIP rejection response message.

10. The network node according to claim 9 , wherein the URN of the emergency service comprises a code identifying a country.

11. The network node according to claim 9 , wherein the URN of the emergency service comprises a code identifying a region.

12. The network node according to claim 9 , the operations further comprising: receiving a second SIP request message, wherein the second SIP request message comprises the URN of the emergency service, and emergency-related information associated with the UE.

13. The network node according to claim 12 , the operations further comprising: sending a message based on the second SIP request message towards a Public Safety Answering Point (PSAP).

14. The network node according to claim 12 , wherein the emergency-related information associated with the UE included in the second SIP request message comprises at least one of a UE location or UE access network information.

15. The network node according to claim 9 , wherein, prior to sending the SIP rejection response message, the UE is unaware that the first SIP request message is an emergency-related request.

16. The network node according to claim 9 , wherein the network node comprises a proxy call session control function (P-CSCF).

17. A non-transitory computer-readable medium storing instructions which, when executed, cause a computing device to perform operations comprising:

receiving, from a user equipment (UE), a first Session Initiation Protocol (SIP) request message;

determining, at a network node within a trust domain, that the first SIP request message is an emergency-related request;

based on the determining, including, by the network node, the following in a SIP rejection response message: a P-Asserted-Identity header field identifying the network node, an indicator indicating that the first SIP request message is an emergency-related request, and a Contact header field comprising a Uniform Resource Name (URN) of an emergency service; and

sending, by the network node, the SIP rejection response message.

18. The non-transitory computer-readable medium according to claim 17 , wherein the URN of the emergency service comprises a code identifying a country.

19. The non-transitory computer-readable medium according to claim 17 , wherein the URN of the emergency service comprises a code identifying a region.

20. The non-transitory computer-readable medium according to claim 17 , wherein the network node comprises a proxy call session control function (P-CSCF).

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 16, 2018
From: BAKKER, JAN HENDRIK LUCAS; BUCKLEY, ADRIAN; ALLEN, ANDREW MICHAEL
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 044631/0175 →
CHANGE OF NAME Recorded Jan 16, 2018
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 045077/0005 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 16, 2018
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 044631/0237 →
Continuity (7)
Continuation 15253036 · Aug 31, 2016
Continuation 14968686 · Dec 14, 2015
Continuation 12937199
Continuation 12131785 · Jun 2, 2008
Provisional Application 61081576 · Jul 17, 2008
Provisional Application 61061507 · Jun 13, 2008
Related Publication 20180042055A1 · Feb 8, 2018
Cited By (1)
US 12,200,021