IP Library Granted Patent US 10,716,152
Granted Patent B2
US 10,716,152 · App. 16/070,718 · Granted Jul 14, 2020

Access point name determination for mission critical services

Inventors: Nicholas James Russell (Newbury, GB); David Philip Hole (Southampton, GB); Adrian Buckley (Tracy, CA)
Assignee: BlackBerry Limited
H04W76/11H04L63/0892H04L65/1016H04W4/90H04W36/0022H04W76/12H04W76/50H04W84/042
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,716,152
App. No.
16/070,718
Granted
Jul 14, 2020
Kind
B2
Abstract

A method for determining an access point name (APN) for mission critical services includes determining, at a user equipment (UE), APN information of a packet data network (PDN) based on at least one of a mission critical organization name, a registered public land mobile network identifier, or a home public land mobile network identifier currently associated with the UE; and connecting to the PDN based on the determined APN information.

Claims (41)

1. A method, comprising:

determining, at a user equipment (UE), access point name (APN) information of a packet data network (PDN) based on at least one of a mission critical organization name, a registered public land mobile network (RPLMN) identifier, or a home public land mobile network (HPLMN) identifier currently associated with the UE, wherein determining the APN information comprises:

storing, at the UE, configured APN information for at least one mission critical organization name and public land mobile network (PLMN) identifiers associated with each of the at least one mission critical organization name; and

identifying a match between the mission critical organization name and the PLMN identifier currently associated with the UE and a mission critical organization name and a PLMN identifier in the configured APN information; and

connecting to the PDN based on the determined APN information.

2. The method of claim 1 , further comprising determining the APN information based on a mission critical service provider identity.

3. The method of claim 1 , further comprising determining the mission critical organization name, the RPLMN identifier, and the HPLMN identifier currently associated with the UE.

4. The method of claim 1 , wherein the PDN is used for at least one of a mission critical service or a mission critical user authentication.

5. The method of claim 1 , wherein the APN information includes an APN network identity.

6. The method of claim 1 , wherein the APN information is further determined by a Mobility Management Entity (MME) based on at least one of the mission critical organization name, the RPLMN identifier, or the HPLMN identifier.

7. The method of claim 1 , wherein determining APN information based on at least one of a mission critical organization name, an RPLMN identifier, or an HPLMN identifier currently associated with the UE comprises:

creating a string of characters including at least one of the mission critical organization name, the RPLMN identifier, or the HPLMN identifier.

8. The method of claim 7 , wherein the UE determines inclusion or exclusion of the mission critical organization name, the RPLMN identifier, or the HPLMN identifier in the string of characters based on a configuration in or available to the UE.

9. The method of claim 7 , wherein creating the string of characters is performed when there is no configured APN information stored at the UE.

10. The method of claim 1 , wherein determining APN information based on at least one of a mission critical organization name, an RPLMN identifier, or an HPLMN identifier currently associated with the UE comprises:

in response to identifying the match, retrieving the configured APN information for the mission critical organization name and the PLMN identifier.

11. The method of claim 1 , further comprising:

comparing the RPLMN identifier currently associated with the UE to a visited public land mobile network (VPLMN) identifier in the configured APN information; and

in response to the RPLMN identifier matching the VPLMN identifier, retrieving the configured APN information for the VPLMN identifier.

12. The method of claim 11 , further comprising:

in response to the RPLMN identifier not matching the VPLMN identifier, comparing the HPLMN identifier currently associated with the UE to an HPLMN identifier in the configured APN information; and

in response to the HPLMN identifier currently associated with the UE matching an HPLMN identifier in the configured APN information, retrieving the configured APN information for the HPLMN identifier.

13. The method of claim 1 , wherein the configured APN information is stored in a management object.

14. The method of claim 1 , wherein the UE includes a mission critical client and a configuration management client.

15. A method, comprising:

sending, by a user equipment (UE) to a first network node, a first message including at least one mission critical user identity associated with the UE;

receiving, from the first network node, a second message indicating that the UE can request access point name (APN) information of a packet data network (PDN) for mission critical services;

sending, by the UE to a second network node, a third message requesting the APN information; and

receiving, from the second network node, a fourth message including the APN information, wherein the first network node and the second network node are an identity management server, the first, second, third and fourth messages are sent or received via an identity management client in the UE, and the first, second, third and fourth messages are authentication messages.

16. The method of claim 15 , further comprising connecting to the PDN based on the received APN information.

17. The method of claim 15 , wherein the APN information includes an APN network identity (NI) of the PDN.

18. A user equipment (UE) comprising a memory, and at least one hardware processor communicatively coupled with the memory and configured to perform operations comprising:

determining access point name (APN) information of a packet data network (PDN) based on at least one of a mission critical organization name, a registered public land mobile network (RPLMN) identifier, or a home public land mobile network (HPLMN) identifier currently associated with the UE, wherein determining the APN information comprises:

storing, at the UE, configured APN information for at least one mission critical organization name and public land mobile network (PLMN) identifiers associated with each of the at least one mission critical organization name; and

identifying a match between the mission critical organization name and the PLMN identifier currently associated with the UE and a mission critical organization name and a PLMN identifier in the configured APN information; and

connecting to the PDN based on the determined APN information.

19. A tangible, non-transitory computer-readable medium containing instructions which, when executed, cause a user equipment (UE) to perform operations comprising:

determining access point name (APN) information of a packet data network (PDN) based on at least one of a mission critical organization name, a registered public land mobile network (RPLMN) identifier, or a home public land mobile network (HPLMN) identifier currently associated with the UE, wherein determining the APN information comprises:

storing, at the UE, configured APN information for at least one mission critical organization name and public land mobile network (PLMN) identifiers associated with each of the at least one mission critical organization name; and

identifying a match between the mission critical organization name and the PLMN identifier currently associated with the UE and a mission critical organization name and a PLMN identifier in the configured APN information; and

connecting to the PDN based on the determined APN information.

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 Mar 18, 2020
From: RUSSELL, NICHOLAS JAMES; HOLE, DAVID PHILIP
To: BLACKBERRY UK LIMITED
Reel/Frame 052155/0852 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2020
From: BUCKLEY, ADRIAN
To: BLACKBERRY CORPORATION
Reel/Frame 052188/0454 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2020
From: BLACKBERRY CORPORATION
To: BLACKBERRY LIMITED
Reel/Frame 052156/0017 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2020
From: BLACKBERRY UK LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 052155/0952 →