IP Library Patent Application 17905593
Patent Application
App. No. 17/905,593

PERFORMING LIFECYCLE MANAGEMENT

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 None
App. No.
17/905,593
Abstract

Lifecycle management is implemented in a data processing system. A first workload is provided in a first workload environment. The first workload is used to align one or more first lifecycle management states of the first workload in the first workload environment and one or more second lifecycle management states of a second workload. The second workload is in a second, different workload environment.

Claims (35)

1 . A method of performing lifecycle management in a data processing system, the method comprising:

instantiating a first workload in a first workload environment executing in the data processing system; and

using the first workload to align a first lifecycle management state of the first workload in the first workload environment and a second lifecycle management state of a second workload,

wherein the second workload is instantiated in a second, different workload environment executing in the data processing system.

2 . The method according to claim 1 , wherein the first workload environment is a Kubernetes environment.

3 . The method according to claim 1 , wherein the first workload performs lifecycle management of only the second workload.

4 . The method according to claim 1 , wherein the second workload is a virtual machine.

5 . The method according to claim 1 , wherein the second workload is configured to provide telephony functionality and the first workload is configured to provide a different functionality.

6 . The method according to claim 1 , wherein the first workload environment comprises another workload configured to provide telephony functionality.

7 . The method according to claim 6 , wherein the other workload is configured to perform lifecycle management in relation to the second workload.

8 . The method according to claim 7 , wherein the lifecycle management performed by the other workload comprises causing the second workload to be deleted in response to a deletion condition comprising the first workload no longer being used to perform lifecycle management in relation to the second workload.

9 . The method according to claim 8 , wherein the other workload is configured to perform lifecycle management in relation to a further workload that is in the second workload environment.

10 . The method according to claim 9 , wherein the further workload is in a third workload environment, the third workload environment being different from the first and second workload environments.

11 . The method according to claim 1 , further comprising using the first workload to transmit an authentication token to the second workload environment.

12 . The method according to claim 1 , further comprising using the first workload to provide status report data in relation to the second workload.

13 . The method according to claim 1 , wherein the second lifecycle management state relate to one of:

creating the second workload; or

readiness of the second workload.

14 . A data processing system comprising a processor and memory storing computer-executable instructions that, when executed by the processor, cause the data processing system to perform operations comprising:

instantiating a first workload in a first workload environment executing in the data processing system; and

using the first workload to align a first lifecycle management state of the first workload in the first workload environment and a second lifecycle management state of a second workload,

wherein the second workload is instantiated in a second, different workload environment executing in the data processing system.

15 . (canceled)

16 . The data processing system according to claim 14 , wherein the first workload environment is a containerized environment.

17 . The data processing system according to claim 14 , wherein the second workload is configured to provide telephony functionality.

18 . The data processing system according to claim 14 , wherein:

the first workload environment comprises another workload configured to provide telephony functionality and the other workload is not configured to perform lifecycle management.

19 . The data processing system according to claim 14 , wherein:

the first workload environment comprises another workload configured to perform lifecycle management in relation to the second workload.

20 . The data processing system according to claim 19 , wherein:

the other workload is configured to perform lifecycle management in relation to a further workload in the second workload environment.

21 . A computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by one or more processors of a computing device of a data processing system, cause the computing device to:

instantiate a first workload in a first workload environment executing in the data processing system; and

use the first workload to align a first lifecycle management state of the first workload in the first workload environment and a second lifecycle management state of a second workload,

wherein the second workload is instantiated in a second, different workload environment executing in the data processing system.

Assignments (9)
CHANGE OF NAME Recorded May 13, 2026
From: ALIANZA, INC.
To: ALIANZA, LLC
Reel/Frame 075646/0037 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: METASWITCH NETWORKS LTD.
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 075578/0155 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: ALIANZA, INC.
Reel/Frame 075645/0892 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY NAME PREVIOUSLY RECORDED AT REEL: 71296 FRAME: 1. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jun 10, 2025
From: METASWITCH NETWORKS LTD.
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 071587/0856 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2025
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: ALIANZA, INC.
Reel/Frame 071296/0079 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2025
From: METASWITCH LIMITED
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 071296/0001 →
SECURITY INTEREST Recorded May 6, 2025
From: ALIANZA, INC.; METASWITCH NETWORKS LTD
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 071191/0228 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE ASSIGNEE DATA PREVIOUSLY RECORDED AT REEL: 061395 FRAME: 0786. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 16, 2023
From: WHITE, PETER LOUIS
To: METASWITCH NETWORKS LTD
Reel/Frame 062774/0811 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2022
From: WHITE, PETER LOUIS
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 061395/0768 →