# US 2026/0099392 A1 · Rule-based Cross-Tenancy Event Delivery

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

- Number: US 2026/0099392 A1
- Document ID: US20260099392A1
- Status: Published application
- Kind: A1
- Application number: 18/906,986
- Filed: 2024-10-04
- Published: 2026-04-09
- Earliest claimed: 2024-10-04
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Kripa Kanchana Sivakumar; Suman M. Somasundar; Sriram Ananthakrishnan
- Web page: https://patentgrep.com/patent/US20260099392A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one embodiment, a method includes receiving from a service executing in a service tenancy and by an event broker, a request to modify a rule to deliver a set of events from a first tenancy to the service tenancy. Modify may include at least one of create or update. The method also includes receiving from the service and by the event broker, a proxy token for substantiating the request. The proxy token represents an authority of a user principal of the first tenancy. The method further includes determining, by the event broker, whether modification of the rule is authorized based at least on the authority of the user principal, and subsequent to determining that the modification of the rule is authorized, delivering, by the event broker, the set of events from the first tenancy to the service tenancy according to the rule.

## Claims

### Claim 1

A non-transitory computer-readable medium comprising instructions that are configured, when executed by a processor, to perform operations comprising:
receiving, from a service executing in a service tenancy and by an event broker, a request to modify a rule to deliver a set of events from a first tenancy to the service tenancy, wherein modify comprises at least one of create or update;
receiving, from the service and by the event broker, a proxy token for substantiating the request, wherein the proxy token represents an authority of a user principal of the first tenancy;
determining, by the event broker, whether modification of the rule is authorized based at least on the authority of the user principal; and
subsequent to determining that the modification of the rule is authorized, delivering, by the event broker, the set of events from the first tenancy to the service tenancy according to the rule.

### Claim 2 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the authority of the user principal is based at least on an access policy that permits the user principal to inspect the set of events in the first tenancy.

### Claim 3 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the authority of the user principal is based at least on an access policy that permits the user principal to manage rules in the first tenancy.

### Claim 4 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the authority of the user principal is based at least on a cross-tenancy access policy pair that permits the user principal to modify the rule, wherein the cross-tenancy access policy pair comprises an endorse rule in the service tenancy and an admit rule in an events tenancy, wherein the event broker executes in the events tenancy.

### Claim 5 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the service is a machine learning (ML) pipeline service.

### Claim 6 (depends on 4)

The non-transitory computer-readable medium of claim 4, wherein the proxy token is associated with one or more characteristics comprising:
has an expiry time; or
is revocable by the user principal prior to the expiry time.

### Claim 7 (depends on 4)

The non-transitory computer-readable medium of claim 4, wherein:
the request to modify the rule comprises a condition string;
the rule comprises the condition string; and
the condition string is used to match the set of events to a particular type of event.

### Claim 8 (depends on 4)

The non-transitory computer-readable medium of claim 4, wherein:
the request to modify the rule comprises a pipeline stream identifier;
the pipeline stream identifier identifies a pipeline stream; and
the event broker delivers, in accordance with the rule, the set of events to the pipeline stream within the service tenancy in accordance with the pipeline stream identifier.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the set of events are delivered to the pipeline stream in real time.

### Claim 10 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the pipeline stream is owned and managed by the service.

### Claim 11 (depends on 1)

The non-transitory computer-readable medium of claim 1, the operations further comprising:
receiving, from the service and by the event broker, a request to update the rule, wherein the request to update the rule comprises an identifier for the rule.

### Claim 12 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein:
the set of events represents a set of dataflow run events;
each dataflow run event of the set of dataflow run events comprises a tag; and
the tag is used to filter its respective dataflow run event such that the event broker only delivers a subset of dataflow run events from the set of dataflow run events that are created by the service to the service tenancy.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, wherein the tag is generated as part of creation of its respective dataflow run event.

### Claim 14 (depends on 1)

The non-transitory computer-readable medium of claim 1, the operations further comprising deleting, by the event broker, the rule in response to determining that the rule is not associated with any pipeline runs in progress.

### Claim 15 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the first tenancy is a secure and isolated partition within an infrastructure of the event broker.

### Claim 16 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the rule is associated with a rule identifier and a pipeline run compartment identifier.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the rule identifier and the pipeline run compartment identifier are stored in a rule bucket.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the rule bucket is not accessible by the first tenancy.

### Claim 19

A system, comprising:
one or more processors; and
a non-transitory computer-readable medium comprising instructions that are configured, when executed by the one or more processors, to perform operations comprising:
receiving, from a service executing in a service tenancy and by an event broker, a request to modify a rule to deliver a set of events from a first tenancy to the service tenancy, wherein modify comprises at least one of create or update;
receiving, from the service and by the event broker, a proxy token for substantiating the request, wherein the proxy token represents an authority of a user principal of the first tenancy;
determining, by the event broker, whether modification of the rule is authorized based at least on the authority of the user principal; and
subsequent to determining that the modification of the rule is authorized, delivering, by the event broker, the set of events from the first tenancy to the service tenancy according to the rule.

### Claim 20

A method by one or more computing systems, comprising:
receiving, from a service executing in a service tenancy and by an event broker, a request to modify a rule to deliver a set of events from a first tenancy to the service tenancy, wherein modify comprises at least one of create or update;
receiving, from the service and by the event broker, a proxy token for substantiating the request, wherein the proxy token represents an authority of a user principal of the first tenancy;
determining, by the event broker, whether modification of the rule is authorized based at least on the authority of the user principal; and
subsequent to determining that the modification of the rule is authorized, delivering, by the event broker, the set of events from the first tenancy to the service tenancy according to the rule.
