# US 2024/0004740 A1 · System and method for interoperability communication using raised intents

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0004740 A1
- Document ID: US20240004740A1
- Status: Published application
- Kind: A1
- Application number: 18/218,860
- Filed: 2023-07-06
- Published: 2024-01-04
- Earliest claimed: 2018-05-16
- Assignees: Finsemble, Inc.
- Applicants: Finsemble Inc.
- Inventors: Terrence Russell Thorsen; Kristopher Charles West; Michael Hugh McClung; Julianna Elizabeth Langston
- Web page: https://patentgrep.com/patent/US20240004740A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The method and system provides for interoperability between mark-up language applications executing in browser containers. The method and system includes executing a first application in an application layer executing within a microservices layer and executing a second application in the application layer. The method and system includes executing a microservices module within a browser container, facilitating communication between the first and second application. The method and system includes executing a first overlay application within the first application, the first overlay application transmitting via the microservices module. Based the method and system transmits, from the first overlay application to the microservices module, a first command transmission having a raised intent data call and a raised intent data field therein, thereby executing a response operation in the second application based thereon.

## Claims

### Claim 1

A computerized method for interoperability between browser-based executable applications, the method comprising:
executing a first application in an application layer executing within a microservices layer, the first application is a browser-based executable application;
executing a second application in the application layer, the second application is a browser-based executable application;
executing a microservices module within a browser container, the microservices module facilitating communication between the first application and the second application via the browser container;
executing a first overlay application within the first application, the first overlay application transmitting via the microservices module;
based on an interaction in the first application, transmitting, from the first overlay application to the microservices module, a first command transmission having a raised intent data call and a raised intent data field therein; and
executing a response operation in the second application based at least on the raised intent data call and the raised intent data field within the first command transmission.

### Claim 2 (depends on 1)

The computerized method of claim 1, further comprising:
executing a second overlay application within the second application, the second overlay application processing the raised intent data call and the raised intent data field.

### Claim 3 (depends on 2)

The computerized method of claim 2, wherein the second overlay application listens for the raised intent data call.

### Claim 4 (depends on 2)

The computerized method of claim 2, wherein the first overlay application executes independent of the first application and operates without modification of an executable code of the first application and wherein the second overlay application executes independent of the second application and operates without modification of an executable code of the second application.

### Claim 5 (depends on 1)

The computerized method of claim 1 further comprising:
associating the second application with the first application for receipt of the raised intent data call and the raised intent data field in response to a user-selection command; and
creating an association data field based on the user-selection command usable for later associations of the second application with the first application without requiring a second user-selection command.

### Claim 6 (depends on 1)

The computerized method of claim 1 further comprising:
executing the browser container on an operating system, wherein the operating system is independent of the first application and the second application.

### Claim 7 (depends on 1)

The method of claim 1, wherein the first application is a financial services application and the second application is at least one of: a communication application and an accounting application.

### Claim 8 (depends on 1)

The method of claim 1, wherein the mark-up language is hypertext mark-up language version five (HTML5).

### Claim 9 (depends on 1)

The method of claim 1, wherein the raised intent data call is an instruction and the raised intent data field is a data value associated with the instruction.

### Claim 10

A processing system or interoperability between browser-based executable applications, the system comprising:
a plurality of executable instructions; and
at least one processing device, in response to the executable instructions, operative to:
execute a first application in an application layer executing within a microservices layer, the first application is a browser-based executable application;
execute a second application in the application layer, the second application is a browser-based executable application;
execute a microservices module within a browser container, the microservices module facilitating communication between the first application and the second application via the browser container;
execute a first overlay application within the first application, the first overlay application transmitting via the microservices module;
based on an interaction in the first application, transmit, from the first overlay application to the microservices module, a first command transmission having a raised intent data call and a raised intent data field therein; and
execute a response operation in the second application based at least on the raised intent data call and the raised intent data field within the first command transmission.

### Claim 11 (depends on 10)

The system of claim 10, the processing device further operative to:
execute a second overlay application within the second application, the second overlay application processing the raised intent data call and the raised intent data field.

### Claim 12 (depends on 11)

The system of claim 11, wherein the second overlay application listens for the raised intent data call.

### Claim 13 (depends on 12)

The system of claim 12, wherein the first overlay application executes independent of the first application and operates without modification of an executable code of the first application and wherein the second overlay application executes independent of the second application and operates without modification of an executable code of the second application.

### Claim 14 (depends on 10)

The system of claim 10, the processing device further operative to:
associate the second application with the first application for receipt of the raised intent data call and the raised intent data field in response to a user-selection command; and
create an association data field based on the user-selection command usable for later associations of the second application with the first application without requiring a second user-selection command.

### Claim 15 (depends on 10)

Th system of claim 10, the processing device further operative to:
execute the browser container on an operating system, wherein the operating system is independent of the first application and the second application.

### Claim 16 (depends on 11)

The system of claim 11, wherein the first application is a financial services application and the second application is at least one of: a communication application and an accounting application.

### Claim 17 (depends on 10)

The system of claim 10, wherein the mark-up language is hypertext mark-up language version five (HTML5).

### Claim 18 (depends on 10)

The system of claim 10, wherein the raised intent data call is an instruction and the raised intent data field is a data value associated with the instruction.

### Claim 19

A computerized method for interoperability between a browser-based executable application and a native application, the method comprising:
executing a first application in an application layer executing within a microservices layer, the first application is the browser-based executable application;
executing a second application within an operating system layer, the second application is a native application;
executing a microservices module and at least one bridging module within a browser container, the microservices module facilitating communication between the first application and the second application via the browser container;
executing a first overlay application within the first application, the first overlay application transmitting via the microservices module;
based on an interaction in the first application, transmitting, from the first overlay application to the microservices module, a first command transmission having a raised intent data call and a raised intent data field therein; and
executing a response operation in the second application based at least on the raised intent data call and the raised intent data field within the first command transmission.

### Claim 20 (depends on 19)

The computerized method of claim 19 further comprising:
executing an operating system bridge in communication with the at least one bridging module within the browser container such that communication with the second application is through the operating system bridge.
