IP Library Granted Patent US 10,542,051
Granted Patent B2
US 10,542,051 · App. 15/725,107 · Granted Jan 21, 2020

System and method for determining establishment causes for emergency sessions

Inventors: Chen Ho Chin (Deerlijk, BE); Richard C. Burbidge (Swindon, GB)
Assignee: BlackBerry Limited
H04L65/1016
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,542,051
App. No.
15/725,107
Granted
Jan 21, 2020
Kind
B2
Abstract

A method for initiating a Packet Switched emergency call using a user equipment (UE) is presented. The UE includes a plurality of protocol layers. The plurality of protocol layers including an IMS sublayer, a non-access stratum (NAS) layer and an access stratum (AS) layer. The method includes generating an ATTACH REQUEST using the UE. The ATTACH REQUEST has an attach type. The method includes retrieving the attach type of the ATTACH REQUEST using the NAS layer of the UE, and generating an RRC CONNECTION REQUEST. The RRC CONNECTION REQUEST includes an RRC establishment cause based upon the attach type of the attach request.

Claims (30)

1. A method for initiating a Packet Switched (PS) emergency call using a user equipment (UE), the UE including a plurality of protocol layers, the plurality of protocol layers including an Internet Protocol (IP) Multimedia Subsystem (IMS) sublayer, a non-access stratum (NAS) layer and an access stratum (AS) layer, the method comprising:

generating, at the UE, a first request comprising an indicator that indicates a request type;

determining, at the UE, a Radio Resource Control (RRC) establishment cause based on the request type, wherein the RRC establishment cause indicates that the UE is requesting an establishment of an RRC connection for an emergency call via a PS network; and

generating, at the UE, an RRC CONNECTION REQUEST, the RRC CONNECTION REQUEST including the RRC establishment cause.

2. The method of claim 1 , wherein generating the first request comprises generating the first request in response to the UE being NAS unregistered.

3. The method of claim 1 , wherein the first request is to be sent to a mobility function within a core network.

4. The method of claim 1 , wherein the RRC connection is a signaling connection.

5. The method of claim 1 , wherein the request type comprises a type associated with establishing the PS emergency call via a PS network.

6. The method of claim 1 , further comprising: transmitting the RRC CONNECTION REQUEST to a base station.

7. The method of claim 1 , wherein the first request is one of an ATTACH REQUEST or a Packet Data Network (PDN) CONNECTIVITY REQUEST.

8. The method of claim 1 , wherein the emergency call via the PS network comprises at least one of evolved packet system (EPS) emergency call or session, PS emergency, or IMS emergency call or session.

9. A user equipment (UE), comprising:

a plurality of protocol layers, the plurality of protocol layers including an Internet Protocol (IP) Multimedia Subsystem (IMS) sublayer, a non-access stratum (NAS) layer and an access stratum (AS) layer;

a memory; and

at least one hardware processor communicatively coupled with the memory and configured to:

generate, at the UE, a first request comprising an indicator that indicates a request type;

determine, at the UE, a Radio Resource Control (RRC) establishment cause based on the request type, wherein the RRC establishment cause indicates that the UE is requesting an establishment of an RRC connection for an emergency call via a Packet Switched (PS) network; and

generate, at the UE, an RRC CONNECTION REQUEST, the RRC CONNECTION REQUEST including the RRC establishment cause.

10. The UE of claim 9 , wherein generating the first request comprises generating the first request in response to the UE being NAS unregistered.

11. The UE of claim 9 , wherein the first request is to be sent to a mobility function within a core network.

12. The UE of claim 9 , wherein the RRC connection is a signaling connection.

13. The UE of claim 9 , wherein the at least one hardware processor is further configured to: transmit the RRC CONNECTION REQUEST.

14. The UE of claim 9 , wherein the request type comprises a type associated with establishing a PS emergency call via a PS network.

15. A non-transitory computer-readable medium storing instructions which, when executed, cause a computing device to perform operations for initiating a Packet Switched (PS) emergency call using a user equipment (UE), the operations comprising:

generating, at the UE, a first request comprising an indicator that indicates a request type, wherein the UE comprises a plurality of protocol layers, the plurality of protocol layers including an Internet Protocol (IP) Multimedia Subsystem (IMS) sublayer, a non-access stratum (NAS) layer and an access stratum (AS) layer; and

determining, at the UE, a Radio Resource Control (RRC) establishment cause based on the request type, wherein the RRC establishment cause indicates that the UE is requesting an establishment of an RRC connection for an emergency call via a PS network; and

generating, at the UE, an RRC CONNECTION REQUEST, the RRC CONNECTION REQUEST including the RRC establishment cause.

16. The non-transitory computer-readable medium of claim 15 , wherein generating the first request comprises generating the first request in response to the UE being NAS unregistered.

17. The non-transitory computer-readable medium of claim 15 , wherein the first request is to be sent to a mobility function within a core network.

18. The non-transitory computer-readable medium of claim 15 , wherein the RRC connection is a signaling connection.

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 Jun 27, 2019
From: CHIN, CHEN HO; BURBIDGE, RICHARD C.
To: RESEARCH IN MOTION UK LIMITED
Reel/Frame 049608/0448 →
CHANGE OF NAME Recorded Jun 27, 2019
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 049608/0634 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 27, 2019
From: RESEARCH IN MOTION UK LIMITED
To: RESEARCH IN MOTION LIMITED
Reel/Frame 049608/0532 →
Continuity (5)
Continuation 15349734 · Nov 11, 2016
Continuation 14836266 · Aug 26, 2015
Division 13499644
Provisional Application 61248213 · Oct 2, 2009
Related Publication 20180035271A1 · Feb 1, 2018