IP Library Granted Patent US 9,612,825
Granted Patent B2
US 9,612,825 · App. 14/213,994 · Granted Apr 4, 2017

Systems and methods for merging metadata-based applications

Inventors: Arlen Sander Feldman (Colorado Springs, CO); Vance Franklin Brown (Colorado Springs, CO)
Assignee: Wells Fargo Bank, National Association, As Agent
G06F8/71G06F17/30595
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,612,825
App. No.
14/213,994
Granted
Apr 4, 2017
Kind
B2
Abstract

Systems and methods for mergeable metadata-based applications may be provided. According to some embodiments, a method may include determining, by a computer including one or more processors, one or more changes to be made to an application on a target computer. The method may also include identifying metadata associated with the application, the metadata corresponding to the one or more changes to be made. Furthermore, the method may include generating at least one tag associated with the metadata. The at least one tag may include information that describes one or more database definitions included in the metadata. Additionally, the method may include wrapping the at least one tag and the metadata into a mergeable metadata application and transmitting, to the target computer, the mergeable metadata application.

Claims (36)

1. A method of merging functionality of multiple applications, comprising: determining, by a computer comprising one or more processors, a change to be made to one or more operating conditions associated with an application on a target computer; identifying metadata associated with the application, the metadata corresponding to the change to be made to the one or more operating conditions associated with the application; generating a tag associated with the metadata, the tag comprising information that describes one or more database definitions included in the metadata and at least one connection point associated with the application, wherein the at least one connection point includes information about a physical component of the target computer, and wherein generating the tag comprises determining a dependency between two or more database objects associated with the metadata for inclusion in the information, wherein the dependency is not included in the information; wrapping the tag and the metadata into one or more mergeable metadata applications; and transmitting, to the target computer, the one or more mergeable metadata applications along with one or more database object stubs, the database object stubs including information for matching database constructs and less information than a fully realized database object, wherein the target computer performs operations comprising: identifying a digital signature associated with a first change comprised in the change to be made; identifying, based on the digital signature, a first mergeable metadata application that originally effected the change; comparing one or more database definitions of the first mergeable metadata application and the one or more database object stubs to the one or more operating conditions associated with the target application; and determining, based at least in part on the comparison, one or more conflict resolution changes to be made to the target application.

2. The method of claim 1 , wherein the one or more database definitions comprise one or more new database definitions to be used by the application.

3. The method of claim 1 , wherein the at least one tag comprises information describing one or more modifications to existing database definitions used by the application.

4. The method of claim 1 , wherein transmitting the mergeable metadata application further comprises: serializing the mergeable metadata application into a transportable format.

5. The method of claim 1 , wherein the at least one tag further comprises information describing respective dependencies between one or more database objects associated with the application.

6. The method of claim 1 , further comprising associating the one or more changes with one or more digital signatures.

7. A method of merging functionality of multiple applications, comprising: receiving, by a target computer comprising one or more processors, one or more mergeable metadata applications along with one or more database object stubs, the database object stubs including information for matching database constructs and less information than a fully realized database object, the target computer executing a target application; extracting metadata and at least one tag from the one or more mergeable metadata applications, the at least one tag comprising description information that describes one or more database definitions included in the metadata and at least one connection point associated with the target application, wherein the at least one connection point includes information about a physical component of the target computer, and wherein extracting the metadata and the at least one tag comprises determining one or more dependencies between two or more database objects associated with the metadata for inclusion in the information, wherein at least one dependency of the one or more dependencies is not included in the information; identifying, based at least in part on the description information and one or more operating conditions associated with the target application, one or more conflicts between the one or more mergeable metadata applications and the target application; identifying a digital signature associated with a first conflict comprised in the one or more conflicts; identifying, based on the digital signature, a first metadata application that originally effected the first conflict; comparing one or more database definitions of the first mergeable metadata application and the one or more database object stubs to the one or more operating conditions associated with the target application; and determining, based at least in part on the comparison, one or more conflict resolution changes to be made to the target application.

8. The method of claim 7 , further comprising: merging the one or more database definitions with the target application.

9. The method of claim 8 , further comprising:

receiving an indication to remove, from the target application one or more merged changes associated with the mergeable metadata application;

identifying the one or more merged changes based at least in part on a digital signature associated with the mergeable metadata application and the merged changes; and

removing the one or more merged changes from the target application.

10. The method of claim 7 , further comprising: merging the one or more conflict resolution changes into the target application.

11. The method of claim 7 , wherein the one or more conflict resolution changes comprise one or more modifications to database definitions associated with the target application.

12. The method of claim 7 , wherein the one or more conflict resolution changes comprise one or more new database definitions to be added to the target application.

13. The method of claim 7 , wherein the one or more conflict resolution changes comprises one or more user interface changes to a user interface associated with the target application.

14. A target computer, comprising:

at least one processor:

at least one memory storing computer-executable instructions, that when executed by the at least one processor, cause the at least one processor to:

execute a target application;

receive one or more mergeable metadata applications along with one or more database object stubs, the database object stubs including information for matching database constructs and less information than a fully realized database object;

extract metadata and at least one tag from the one or more mergeable metadata applications, the at least one tag comprising description information that describes one or more database definitions included in the metadata and at least one connection point associated with the target application, wherein the at least one connection point includes information about a physical component of the target computer, and wherein extracting the metadata and the at least one tag comprises determining one or more dependencies between two or more database objects associated with the metadata for inclusion in the information, wherein at least one dependency of the one or more dependencies is not included in the information;

identify, based at least in part on the description information and one or more operating conditions associated with the target application, one or more conflicts between the one or more mergeable metadata applications and the target application;

identify a digital signature associated with a first conflict comprised in the one or more conflicts;

identify, based on the digital signature, a first metadata application that originally effected the first conflict;

compare one or more database definitions of the first mergeable metadata application and the one or more database object stubs to the one or more operating conditions associated with the target application; and

determine, based at least in part on the comparison, one or more conflict resolution changes to be made to the target application.

15. The target computer of claim 14 , wherein the computer-executable instructions further cause the at least one processor to: merge the one or more database definitions with the target application.

16. The target computer of claim 15 , wherein the computer-executable instructions further cause the at least one processor to:

receive an indication to remove, from the target application, one or more merged changes associated with the mergeable metadata application;

identify the one or more merged changes based at least in part on a digital signature associated with the mergeable metadata application and the merged changes; and

remove the one or more merged changes from the target application.

17. The target computer of claim 14 , wherein the computer-executable instructions further cause the at least one processor to: merge the one or more conflict resolution changes into the target application.

18. The target computer of claim 14 , wherein the one or more conflict resolution changes comprise one or more modifications to database definitions associated with the target application.

19. The target computer of claim 14 , wherein the one or more conflict resolution changes comprise one or more new database definitions to be added to the target application.

20. The target computer of claim 14 , wherein the one or more conflict resolution changes comprises one or more user interface changes to a user interface associated with the target application.

Assignments (15)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 16, 2025
From: IVANTI SECURITY HOLDINGS LLC
To: CHERWELL SOFTWARE, LLC
Reel/Frame 071719/0706 →
2025-1 SECOND LIEN SECURITY AGREEMENT Recorded May 5, 2025
From: IVANTI SECURITY INTERMEDIATE HOLDINGS LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0498 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2025
From: IVANTI, INC.
To: IVANTI SECURITY HOLDINGS LLC
Reel/Frame 071180/0690 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2025
From: CHERWELL SOFTWARE, LLC
To: IVANTI SECURITY HOLDINGS LLC
Reel/Frame 071025/0538 →
PARTIAL RELEASE OF SECURITY INTERESTS Recorded May 5, 2025
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; CHERWELL SOFTWARE, LLC
Reel/Frame 071176/0289 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 3, 2025
From: IVANTI SECURITY HOLDINGS LLC
To: ALTER DOMUS (US) LLC
Reel/Frame 071165/0164 →
RELEASE OF SECURITY INTEREST Recorded May 2, 2025
From: ALTER DOMUS (US) LLC
To: IVANTI SECURITY HOLDINGS LLC
Reel/Frame 071162/0130 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 056311/0111 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071123/0491 →
SECURITY INTEREST Recorded May 21, 2021
From: CHERWELL SOFTWARE, LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 056311/0111 →
SECURITY INTEREST Recorded May 21, 2021
From: CHERWELL SOFTWARE, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 056311/0065 →
RELEASE OF SECURITY INTEREST Recorded Mar 30, 2021
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
To: CHERWELL SOFTWARE, LLC
Reel/Frame 055761/0590 →
SECURITY INTEREST Recorded May 10, 2016
From: CHERWELL SOFTWARE, LLC
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 038529/0352 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 14, 2014
From: FELDMAN, ARLEN SANDER; BROWN, VANCE FRANKLIN
To: CHERWELL SOFTWARE, LLC
Reel/Frame 032447/0164 →
Continuity (2)
Provisional Application 61792781 · Mar 15, 2013
Related Publication 20140282466A1 · Sep 18, 2014