IP Library Granted Patent US 9,462,616
Granted Patent B2
US 9,462,616 · App. 14/968,686 · Granted Oct 4, 2016

System and method for managing emergency requests

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 9,462,616
App. No.
14/968,686
Filed
Dec 14, 2015
Granted
Oct 4, 2016
Kind
B2
Examiner
AJAYI, JOEL
Art Unit
2646
USPC
455/404.1
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 (65)

1. An network component, comprising:

a receiver configured to receive from a user equipment (“UE”) a Session Initiation Protocol (“SIP”) request message for a dialog that is an emergency-related request;

one or more processors configured to update header information of the SIP request message for a dialog;

an interface configured to forward the SIP request message for a dialog toward a Public Safety Answering Point (“PSAP”); and

a transmitter configured to send to the UE a SIP response message in response to the SIP request message, the SIP response message containing a P-Asserted-ldentity header field indicating that the network component is part of a trust domain, the P-Asserted-Identity header field including an indicator indicating that the SIP request message for a dialog, sent by the UE, is an emergency-related request, and that the UE should include emergency-related information associated with the UE in a SIP request message within the dialog in response to the SIP response message, the emergency-related information comprising location information;

wherein the indicator comprises a number.

2. The network component of claim 1 , wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises a UE identity.

3. The network component of claim 1 , wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises a UE location.

4. The network component of claim 1 , wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises UE access network information.

5. The network component of claim 1 , wherein the network component is an E-CSCF (emergency call session control function).

6. The network component of claim 1 , wherein the SIP response message is one of a SIP 1xx or 200 (OK) response.

7. The network component of claim 1 , wherein the SIP request message within the dialog is one of:

a SIP ACK;

a SIP PRACK;

a SIP target refresh;

a SIP UPDATE; or

a SIP RE-INVITE request.

8. The network component of claim 7 , wherein the SIP request message is a SIP INVITE request.

9. The network component of claim 2 , wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).

10. The network component of claim 3 , wherein a geolocation header field of the SIP request message within the dialog includes a URI (Uniform Resource Identifier) that points to the UE location.

11. The network component of claim 1 , wherein a message body of the SIP request message within the dialog includes geographical location information of the UE as a PIDF location object.

12. The network component of claim 1 , wherein a contact header field of the SIP request message within the dialog includes a public GRUU value associated with a public user identity.

13. The network component of claim 4 , wherein the UE access network information is included in a P-Access-Network-lnfo header field in the SIP request message within the dialog and comprises one of a location identifier, a cell identifier or an identity of an WLAN access node.

14. The network component of claim 1 , wherein the emergency-related information associated with the UE is not contained in the SIP request message for a dialog.

15. The network component of claim 1 , wherein the indicator indicating that a SIP request message for a dialog is an emergency-related request comprises a Uniform Resource Name (“URN”).

16. The network component of claim 1 , wherein the indicator indicates a PSAP function.

17. The network component of claim 1 , wherein the indicator indicates 911.

18. A method for a network component to manage emergency-related information, comprising:

receiving from a user equipment (“UE”) a Session Initiation Protocol (“SIP”) request message for a dialog that is an emergency-related request;

updating header information of the SIP request message for a dialog;

forwarding the SIP request message for a dialog toward a Public Safety Answering Point (“PSAP”); and

sending from the network component to the UE a SIP response message in response to the SIP request message, the SIP response message containing a P-Asserted-ldentity header field indicating that the network component is part of a trust domain, the P-Asserted-ldentity header field including an indicator indicating that the SIP request message for a dialog, sent by the UE, is an emergency-related request, and that the UE should include emergency-related information associated with the UE in a SIP request message within the dialog in response to the SIP response message, the emergency-related information comprising location information;

wherein the indicator comprises a number.

19. The method of claim 18 , wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises a UE identity.

20. The method of claim 18 , wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises a UE location.

21. The method of claim 18 , wherein the emergency-related information associated with the UE contained in the SIP request message within the dialog comprises UE access network information.

22. The method of claim 18 , wherein the network component is an E-CSCF (emergency call session control function).

23. The method of claim 18 , wherein the SIP response message is one of a SIP 1xx or 200 (OK) response.

24. The method of claim 18 , wherein the SIP request message within the dialog is one of:

a SIP ACK;

a SIP PRACK;

a SIP target refresh;

a SIP UPDATE; or

a SIP RE-INVITE request.

25. The method of claim 24 , wherein the SIP request message is a SIP INVITE request.

26. The method of claim 19 , wherein the UE identity is a globally routable user agent uniform resource identifier (GRUU).

27. The method of claim 20 , wherein a geolocation header field of the SIP request message within the dialog includes a URI (Uniform Resource Identifier) that points to the UE location.

28. The method of claim 18 , wherein a message body of the SIP request message within the dialog includes geographical location information of the UE as a PIDF location object.

29. The method of claim 18 , wherein a contact header field of the SIP request message within the dialog includes a public GRUU value associated with a public user identity.

30. The method of claim 21 , wherein the UE access network information is included in a P-Access-Network-lnfo header field in the SIP request message within the dialog and comprises one of a location identifier, a cell identifier or an identity of an WLAN access node.

31. The method of claim 18 , wherein the emergency-related information associated with the UE is not contained in the SIP request message for a dialog.

32. The method of claim 18 , wherein the indicator indicating that a SIP request message for a dialog is an emergency-related request comprises a Uniform Resource Name (“URN”).

33. The method of claim 18 , wherein the indicator indicates a PSAP function.

34. The method of claim 18 , wherein the indicator indicates 911.

35. A non-transitory computer readable medium storing instructions to cause a processor to perform operations comprising:

receiving from a user equipment (“UE”) a Session Initiation Protocol (“SIP”) request message for a dialog that is an emergency-related request;

updating header information of the SIP request message for a dialog;

forwarding the SIP request message for a dialog toward a Public Safety Answering Point (“PSAP”); and

sending from the network component to the UE a SIP response message in response to the SIP request message, the SIP response message containing a P-Asserted-ldentity header field indicating that the network component is part of a trust domain, the P-Asserted-ldentity header field including an indicator indicating that the SIP request message for a dialog, sent by the UE, is an emergency-related request, and that the UE should include emergency-related information associated with the UE in a SIP request message within the dialog in response to the SIP response message, the emergency-related information comprising location information;

wherein the indicator comprises a number.

36. The computer readable medium of claim 35 , wherein the indicator indicates 911.

37. The computer readable medium of claim 35 , wherein the emergency-related information associated with the UE is not contained in the SIP request message for a dialog.

38. The computer readable medium of claim 35 , wherein the indicator indicating that a SIP request message for a dialog is an emergency-related request comprises a Uniform Resource Name (“URN”).

39. The computer readable medium of claim 35 , wherein the indicator indicates a PSAP function.

40. The computer readable medium of claim 35 , wherein the indicator indicates 911.

Assignments (10)
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 Feb 7, 2018
From: BAKKER, JAN HENDRIK LUCAS; BUCKLEY, ADRIAN; ALLEN, ANDREW MICHAEL
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 044853/0419 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2016
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 038708/0858 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2016
From: BAKKER, JAN HENDRIK LUCAS; BUCKLEY, ADRIAN; ALLEN, ANDREW
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 038708/0843 →
CHANGE OF NAME Recorded Feb 23, 2016
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 037893/0239 →