# US 2023/0065589 A1 · Using persistent finite state machine to coordinate lifecycle operations in service broker

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

- Number: US 2023/0065589 A1
- Document ID: US20230065589A1
- Status: Published application
- Kind: A1
- Application number: 17/460,890
- Filed: 2021-08-30
- Published: 2023-03-02
- Earliest claimed: 2021-08-30
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Abhik Gupta; Shivansh Rai; Vineet Singh
- Web page: https://patentgrep.com/patent/US20230065589A1

## CPC

- G06F 9/4498: {Finite state machines}
- G06F 8/36: Software reuse
- G06F 9/466: {Transaction processing}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/562: Brokering proxy services
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems may be associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment. A persistent finite state machine may be associated with an OSB API service broker, and a database may store a current state of the service broker. A computer processor of a state machine executor may retrieve the current state of the service broker from the database, and (based on the current state) use the persistent finite state machine to coordinate a distributed transaction workflow for the service broker, the distributed transaction workflow including asynchronous instance OSB API lifecycle operations that span multiple entities. The state machine may then update the database with state outputs for the service broker.

## Claims

### Claim 1

A system associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, comprising:
a persistent finite state machine associated with an OSB API service broker;
a database storing a current state of the service broker; and
a state machine executor, including:
a computer processor, and
computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor cause the processor to:
retrieve the current state of the service broker from the database,
based on the current state, use the persistent finite state machine to coordinate a distributed transaction workflow for the service broker, the distributed transaction workflow including asynchronous instance OSB API lifecycle operations that span multiple entities, and
update the database with state outputs for the service broker.

### Claim 2 (depends on 1)

The system of claim 1, wherein the multiple entities are associated with at least one of: (i) a cloud provider network, and (ii) persistent storage.

### Claim 3 (depends on 1)

The system of claim 1, wherein the OSB API service broker is used to provision, manage, and access service instances of a service offering.

### Claim 4 (depends on 1)

The system of claim 1, wherein the persistent finite state machine spans Hyper-Text Transfer Protocol (“HTTP”) boundaries and provides at least one of: (i) scalability, (ii) support for serial and parallel task workflows, (iii) support for conditional units of execution, (iv) distributed transaction support, (v) language-agnostic representation of states and transitions, (vi) persistence, and (vii) fault tolerance.

### Claim 5 (depends on 1)

The system of claim 1, wherein the OSB API computing environment is associated with at least one of: (i) a cloud infrastructure provider, and (ii) an on-premises deployment.

### Claim 6 (depends on 1)

The system of claim 1, wherein the persistent finite state machine defines a data model including state machine executions fields and state machine master fields.

### Claim 7 (depends on 6)

The system of claim 6, wherein the state machine execution fields include at least one of: (i) a machine identifier, (ii) a state identifier, (iii) state name, (iv) an invocation identifier, (v) a resource identifier, (vi) state outputs, and (vii) a timestamp.

### Claim 8 (depends on 1)

The system of claim 1, wherein the state machine executor executes a state transition from a first state to a second state, each state including handler and a reset command.

### Claim 9 (depends on 1)

The system of claim 1, wherein a finite state machine library includes an API module, a document parser, a plugin module for executors, a core orchestration controller, a data translator, and an object-relational mapping module.

### Claim 10

A computer-implemented method associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, comprising:
retrieving, by a computer processor of a state machine executor, a current state of an OSB API service broker from a database;
based on the current state, using a persistent finite state machine to coordinate a distributed transaction workflow for the service broker, the distributed transaction workflow including asynchronous instance OSB API lifecycle operations that span multiple entities; and
updating the database with state outputs for the service broker.

### Claim 11 (depends on 10)

The method of claim 10, wherein the multiple entities are associated with at least one of: (i) a cloud provider network, and (ii) persistent storage.

### Claim 12 (depends on 10)

The method of claim 10, wherein the OSB API service broker is used to provision, manage, and access service instances of a service offering.

### Claim 13 (depends on 10)

The method of claim 10, wherein the persistent finite state machine spans Hyper-Text Transfer Protocol (“HTTP”) boundaries and provides at least one of: (i) scalability, (ii) support for serial and parallel task workflows, (iii) support for conditional units of execution, (iv) distributed transaction support, (v) language-agnostic representation of states and transitions, (vi) persistence, and (vii) fault tolerance.

### Claim 14 (depends on 10)

The method of claim 10, wherein the OSB API computing environment is associated with at least one of: (i) a cloud infrastructure provider, and (ii) an on-premises deployment.

### Claim 15

A non-transitory, computer readable medium having executable instructions stored therein that, when executed by a computer processor cause the processor to perform a method associated with an Open Service Broker (“OSB”) Application Programming Interface (“API”) computing environment, the method comprising:
retrieving, by a computer processor of a state machine executor, a current state of an OSB API service broker from a database;
based on the current state, using a persistent finite state machine to coordinate a distributed transaction workflow for the service broker, the distributed transaction workflow including asynchronous instance OSB API lifecycle operations that span multiple entities; and
updating the database with state outputs for the service broker.

### Claim 16 (depends on 15)

The medium of claim 15, wherein the persistent finite state machine defines a data model including state machine executions fields and state machine master fields.

### Claim 17 (depends on 16)

The medium of claim 16, wherein the state machine execution fields include at least one of: (i) a machine identifier, (ii) a state identifier, (iii) state name, (iv) an invocation identifier, (v) a resource identifier, (vi) state outputs, and (vii) a timestamp.

### Claim 18 (depends on 15)

The medium of claim 15, wherein the state machine executor executes a state transition from a first state to a second state, each state including handler and a reset command.

### Claim 19 (depends on 15)

The medium of claim 15, wherein a finite state machine library includes an API module, a document parser, a plugin module for executors, a core orchestration controller, a data translator, and an object-relational mapping module.

### Claim 20 (depends on 15)

The medium of claim 15, wherein the OSB API computing environment is associated with at least one of: (i) a cloud infrastructure provider, and (ii) an on-premises deployment.
