IP Library Granted Patent US 10,856,359
Granted Patent B2
US 10,856,359 · App. 16/823,174 · Granted Dec 1, 2020

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/029H04W4/90H04M3/42068H04M7/006H04M2242/04H04W80/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,856,359
App. No.
16/823,174
Granted
Dec 1, 2020
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 (31)

1. A method for a user equipment (UE) to respond to an emergency-related message comprising:

sending, from the UE, a first Session Initiation Protocol (SIP) request message;

receiving, at the UE, a SIP rejection response message comprising a P-Asserted Identity header field, wherein the P-Asserted Identity header field comprises an indicator indicating that the first SIP request message is an emergency-related request, and a contact header field of the SIP rejection response message comprises a Uniform Resource Name (URN) of an emergency service; and

in response to receiving the SIP rejection response message, sending, from the UE, a second SIP request message towards a Public Safety Answering Point (PSAP), wherein the second SIP request message includes the URN of the emergency service and emergency-related information associated with the UE.

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

3. The method of claim 1 , wherein the SIP rejection response message is a SIP 3XX response.

4. The method of claim 3 , wherein the SIP 3XX response is a SIP 380 response.

5. The method of claim 1 , wherein the emergency-related information associated with the UE comprises location information.

6. The method of claim 1 , wherein the SIP rejection response comprises an Extensible Markup Language (XML) body.

7. The method of claim 6 , wherein the XML body comprises a type element set to emergency.

8. The method of claim 1 , wherein the UE is unaware that the first SIP request message is an emergency-related request prior to sending the first SIP request message.

9. A user equipment (UE), 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 UE to perform operations comprising:

sending, from the UE, a first Session Initiation Protocol (SIP) request message;

receiving, at the UE, a SIP rejection response message comprising a P-Asserted Identity header field, wherein the P-Asserted Identity header field comprises an indicator indicating that the first SIP request message is an emergency-related request, and a contact header field of the SIP rejection response message comprises a Uniform Resource Name (URN) of an emergency service; and

in response to receiving the SIP rejection response message, sending, from the UE, a second SIP request message towards a Public Safety Answering Point (PSAP), wherein the second SIP request message includes the URN of the emergency service and emergency-related information associated with the UE.

10. The UE of claim 9 , wherein the URN of the emergency service comprises a country code.

11. The UE of claim 9 , wherein the SIP rejection response message is a SIP 3XX response.

12. The UE of claim 11 , wherein the SIP 3XX response is a SIP 380 response.

13. The UE of claim 9 , wherein the emergency-related information associated with the UE comprises location information.

14. The UE of claim 9 , wherein the SIP rejection response comprises an Extensible Markup Language (XML) body.

15. The UE of claim 14 , wherein the XML body comprises a type element set to emergency.

16. The UE of claim 9 , wherein the UE is unaware that the first SIP request message is an emergency-related request prior to sending the first SIP request message.

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

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

receiving, at the UE, a SIP rejection response message comprising a P-Asserted Identity header field, wherein the P-Asserted Identity header field comprises an indicator indicating that the first SIP request message is an emergency-related request, and a contact header field of the SIP rejection response message comprises a Uniform Resource Name (URN) of an emergency service; and

in response to receiving the SIP rejection response message, sending, from the UE, a second SIP request message towards a Public Safety Answering Point (PSAP), wherein the second SIP request message includes the URN of the emergency service and emergency-related information associated with the UE.

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

19. The non-transitory computer-readable medium of claim 17 , wherein the SIP rejection response message is a SIP 3XX response.

20. The non-transitory computer-readable medium of claim 19 , wherein the SIP 3XX response is a SIP 380 response.

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 Mar 19, 2020
From: BAKKER, JAN HENDRIK LUCAS; BUCKLEY, ADRIAN; ALLEN, ANDREW MICHAEL
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 052165/0696 →
CHANGE OF NAME Recorded Mar 19, 2020
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 052189/0973 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 19, 2020
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 052165/0740 →
Continuity (9)
Continuation 16192613 · Nov 15, 2018
Continuation 15789586 · Oct 20, 2017
Continuation 15253036 · Aug 31, 2016
Continuation 14968686 · Dec 14, 2015
Continuation 12937199
Continuation In Part 12131785 · Jun 2, 2008
Provisional Application 61081576 · Jul 17, 2008
Provisional Application 61061507 · Jun 13, 2008
Related Publication 20200221537A1 · Jul 9, 2020