IP Library Granted Patent US 12,538,116
Granted Patent B2
US 12,538,116 · App. 18/305,621 · Granted Jan 27, 2026

Cellular service activation and deactivation on mobile devices

Inventors: Jonathan William Yuresko (Doylestown, PA); Joshua Jagdfeld (Minneapolis, MN)
Assignee: JAMF Software, LLC
H04W8/18G06F9/546H04W12/06H04W12/30
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 12,538,116
App. No.
18/305,621
Granted
Jan 27, 2026
Kind
B2
Abstract

In certain aspects of the present disclosure, a computer-implemented method includes receiving, at a mobile device management server in response to authentication being granted to an organization app on a mobile device, an API enable message from an organization service associated with the organization app. The API enable message includes instructions for the mobile device management server to retrieve device and user data from the mobile device. The method includes retrieving, responsive to receiving the API enable message, the device and user data from the mobile device. The method includes transmitting the device and user data to the automation service for requesting activation of an organization owned line of service ESIM on the mobile device. The method includes deploying a management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device.

Claims (46)

1 . A computer-implemented method comprising:

receiving, at a mobile device management server in response to authentication being granted to an organization app on a mobile device, an Application Programming Interface (API) enable message from an organization service associated with the organization app, wherein the API enable message includes instructions for the mobile device management server to retrieve device and user data from the mobile device;

retrieving, responsive to receiving the API enable message, the device and user data from the mobile device;

transmitting the device and user data to an automation service for requesting activation of an organization owned line of service ESIM on the mobile device; and

deploying a management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device.

2 . The computer-implemented method of claim 1 , wherein the organization app comprises a time clock.

3 . The computer-implemented method of claim 2 , wherein deploying the management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device is further based on carrier information being transmitted to the mobile device from a carrier server.

4 . The computer-implemented method of claim 2 , wherein deploying the management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device is further based on carrier information being transmitted to the mobile device from a carrier server via the automation service.

5 . The computer-implemented method of claim 3 , further comprising:

receiving, at the mobile device management server in response to a disable option being selected on the organization app on the mobile device, an Application Programming Interface (API) disable message from the organization service associated with the organization app, wherein the API disable message includes instructions for the mobile device management server to retrieve the device and user data from the mobile device;

retrieving, responsive to receiving the API disable message, the device and user data from the mobile device;

transmitting the device and user data to the automation service for requesting deactivation of the organization owned line of service ESIM on the mobile device; and

removing the management app and security posture from the mobile device based on the organization owned line of service ESIM being deactivated on the mobile device.

6 . The computer-implemented method of claim 5 , wherein the mobile device is a personally owned device.

7 . The computer-implemented method of claim 5 , wherein the mobile device is an organization owned device.

8 . A system comprising:

a memory comprising instructions; and

a processor configured to execute the instructions which, when executed, cause the processor to:

receive, at a mobile device management server in response to authentication being granted to an organization app on a mobile device, an Application Programming Interface (API) enable message from an organization service associated with the organization app, wherein the API enable message includes instructions for the mobile device management server to retrieve device and user data from the mobile device;

retrieve, responsive to receiving the API enable message, the device and user data from the mobile device;

transmit the device and user data to an automation service for requesting activation of an organization owned line of service ESIM on the mobile device; and

deploy a management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device.

9 . The system of claim 8 , wherein the organization app comprises a time clock.

10 . The system of claim 9 , wherein the processor is configured to execute the instructions to deploy the management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device to be further based on carrier information being transmitted to the mobile device from a carrier server.

11 . The system of claim 9 , wherein the processor is configured to execute the instructions to deploy the management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device to be further based on carrier information being transmitted to the mobile device from a carrier device via the automation service.

12 . The system of claim 8 , wherein the processor is further configured to execute the instructions which, when executed, cause the processor to:

receive, at the mobile device management server in response to a disable option being selected on the organization app on the mobile device, an Application Programming Interface (API) disable message from the organization service associated with the organization app, wherein the API disable message includes instructions for the mobile device management server to retrieve the device and user data from the mobile device;

retrieve, responsive to receiving the API disable message, the device and user data from the mobile device;

transmit the device and user data to the automation service for requesting deactivation of the organization owned line of service ESIM on the mobile device; and

remove the management app and security posture from the mobile device based on the organization owned line of service ESIM being deactivated on the mobile device.

13 . The system of claim 12 , wherein the mobile device is a personally owned device.

14 . The system of claim 12 , wherein the mobile device is an organization owned device.

15 . A non-transitory machine-readable storage medium comprising machine-readable instructions for causing a processor to execute a method, the method comprising:

receiving, at a mobile device management server in response to authentication being granted to an organization app on a mobile device, an Application Programming Interface (API) enable message from an organization service associated with the organization app, wherein the API enable message includes instructions for the mobile device management server to retrieve device and user data from the mobile device;

retrieving, responsive to receiving the API enable message, the device and user data from the mobile device;

transmitting the device and user data to an automation service for requesting activation of an organization owned line of service ESIM on the mobile device; and

deploying a management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device.

16 . The non-transitory machine-readable storage medium of claim 15 , wherein deploying the management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device is further based on carrier information being transmitted to the mobile device from a carrier server.

17 . The non-transitory machine-readable storage medium of claim 15 , wherein deploying the management app and security posture to the mobile device based on the organization owned line of service ESIM being activated on the mobile device is further based on carrier information being transmitted to the mobile device from a carrier server via the automation service.

18 . The non-transitory machine-readable storage medium of claim 15 , further including instructions for causing the processor to execute the method comprising:

receiving, at the mobile device management server in response to a disable option being selected on the organization app on the mobile device, an Application Programming Interface (API) disable message from the organization service associated with the organization app, wherein the API disable message includes instructions for the mobile device management server to retrieve the device and user data from the mobile device;

retrieving, responsive to receiving the API disable message, the device and user data from the mobile device;

transmitting the device and user data to the automation service for requesting deactivation of the organization owned line of service ESIM on the mobile device; and

removing the management app and security posture from the mobile device based on the organization owned line of service ESIM being deactivated on the mobile device.

19 . The non-transitory machine-readable storage medium of claim 18 , wherein the mobile device is a personally owned device.

20 . The non-transitory machine-readable storage medium of claim 18 , wherein the mobile device is an organization owned device.

Assignments (4)
PATENT SECURITY AGREEMENT Recorded Mar 3, 2026
From: JAMF SOFTWARE, LLC
To: BLUE OWL CAPITAL CORPORATION, AS COLLATERAL AGENT
Reel/Frame 075025/0447 →
RELEASE OF SECURITY INTEREST Recorded Jan 30, 2026
From: JPMORGAN CHASE BANK, N.A., AS AGENT
To: JAMF SOFTWARE, LLC; WANDERA, INC.
Reel/Frame 073647/0447 →
SECURITY INTEREST Recorded May 3, 2024
From: JAMF SOFTWARE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 067304/0042 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2023
From: YURESKO, JONATHAN WILLIAM; JAGDFELD, JOSHUA
To: JAMF SOFTWARE, LLC
Reel/Frame 063436/0601 →
Continuity (2)
Continuation In Part 17934608 · Sep 23, 2022
Related Publication 20240107289A1 · Mar 28, 2024
References Cited (14)
US 10708759B1 · Roy · 2020 [cited by examiner]
US 20170048713A1 · Guday · 2017 [cited by examiner]
US 20170250977A1 · Turner · 2017 [cited by examiner]
US 20180206123A1 · Guday · 2018 [cited by examiner]
US 20180270363A1 · Guday · 2018 [cited by examiner]
US 20220014900A1 · Gandhi · 2022 [cited by examiner]
US 20220086633A1 · Sureshlal · 2022 [cited by examiner]
US 20220104005A1 · Xiong · 2022 [cited by examiner]
US 20220141642A1 · Boyapalle · 2022 [cited by examiner]
US 20240163657A1 · Williams · 2024 [cited by examiner]
US 20250097688A1 · Orcutt · 2025 [cited by applicant]
Non-Final Office Action issued in related U.S. Appl. No. 17/934,608, dated Nov. 19, 2024. [cited by applicant]
Non-Final Office Action issued in U.S. Appl. No. 17/934,608, dated Jul. 16, 2025. [cited by applicant]
Final Office Action issued in U.S. Appl. No. 17/934,608, dated Apr. 25, 2025. [cited by applicant]