# US 2025/0095870 A1 · Stream orchestration for variable-length message streams

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

- Number: US 2025/0095870 A1
- Document ID: US20250095870A1
- Status: Published application
- Kind: A1
- Application number: 18/829,927
- Filed: 2024-09-10
- Published: 2025-03-20
- Earliest claimed: 2023-09-15
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Syed Najeeb Andrabi; Sachin Goel
- Web page: https://patentgrep.com/patent/US20250095870A1

## CPC

- G16H 80/00: ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
- G06F 16/24568: {Data stream processing; Continuous queries}
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 69/22: Parsing or analysis of headers
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- 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

Techniques are disclosed for stream orchestration for variable-length message streams, including routes specified using an implementation-independent stream orchestration language (SOL). In an example method, a computing system receives a variable-length message, the variable-length message including context information and a payload. The computing system determines, from the context information, routing information that identifies at least one consumer of the variable-length message. The computing system outputs the variable-length message to the consumer.

## Claims

### Claim 1

A computer-implemented method, comprising:
receiving a variable-length message, the variable-length message including context information and a payload;
determining, from the context information, routing information that identifies at least one consumer of the variable-length message; and
outputting the variable-length message to the consumer.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein:
the variable-length message is encoded in a binary format; and
the context information comprises a context length and one or more key-value pairs, the context length defining a demarcation between the context information and the payload, the context information and the payload both characterized by a variable-length.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the payload includes binary audio data or textual data.

### Claim 4 (depends on 1)

The computer-implement method of claim 1, wherein the variable-length message is included in a message stream comprising a plurality of messages.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein:
the consumer is at least one of a clinical transcription service, an ambient listening service, or a clinical automation service; and
outputting the variable-length message to the consumer causes an update to a clinical record.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the variable-length message is received via a WebSocket endpoint.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the routing information is determined, from the context information, using a set of stream orchestration specifications.

### Claim 8 (depends on 7)

The computer-implemented method of claim 7, wherein the set of stream orchestration specifications are specified using JavaScript Object Notation (“JSON”).

### Claim 9 (depends on 7)

The computer-implemented method of claim 7, wherein each stream orchestration specification of the set of stream orchestration specifications includes one or more tasks defining a route, including at least one routing task and an output task, the output task including a specification of the consumer.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein:
the set of stream orchestration specifications includes a first stream orchestration specification, including a first task and second task;
the first task is implemented using a first programming language;
the second task is implemented using a second programming language; and
the first programming language and the second programming language are different programming languages.

### Claim 11 (depends on 9)

The computer-implemented method of claim 9, wherein:
the context information includes a specification of a first route; and
the set of stream orchestration specifications includes a first stream orchestration specification corresponding to the first route.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11, wherein the one or more tasks of the first stream orchestration specification are executed in sequence or in parallel.

### Claim 13 (depends on 11)

The computer-implemented method of claim 11, wherein the routing task of the first stream orchestration specification comprises a conditional expression, one or more first tasks, and one or more second tasks, and further comprising evaluating the conditional expression to select the one or more first tasks or the one or more second tasks based on the variable-length message.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, wherein the conditional expression is written in a JSON query language.

### Claim 15 (depends on 13)

The computer-implemented method of claim 13, wherein the conditional expression is evaluated by querying a rules engine.

### Claim 16 (depends on 9)

The computer-implemented method of claim 9, wherein the context information includes one or more dynamic stream orchestration specifications, and further comprising:
identifying a first stream orchestration specification corresponding to a first dynamic stream orchestration specification of the one of the one or more dynamic stream orchestration specifications;
updating the first stream orchestration specification based on the first dynamic stream orchestration specification to result in an updated first stream orchestration specification; and
outputting a broadcast message including information about the updated first stream orchestration specification.

### Claim 17 (depends on 9)

The computer-implemented method of claim 9, wherein the one or more tasks include a transformation task, the transformation task being one of a text-to-speech task, a speech-to-text task, or a structured data format conversion task.

### Claim 18 (depends on 9)

The computer-implemented method of claim 9, wherein the one or more tasks include a data writing task, the data writing task being one of a database writing task or a filesystem writing task.

### Claim 19

A system comprising:
one or more processors; and
one or more computer-readable media storing instructions which, when executed by the one or more processors, cause the system to perform operations comprising:
receiving a variable-length message, the variable-length message including context information and a payload;
determining, from the context information, routing information that identifies at least one consumer of the variable-length message; and
outputting the variable-length message to the consumer.

### Claim 20

One or more non-transitory computer-readable media storing instructions which, when executed by one or more processors, cause a system to perform operations comprising:
receiving a variable-length message, the variable-length message including context information and a payload;
determining, from the context information, routing information that identifies at least one consumer of the variable-length message; and
outputting the variable-length message to the consumer.
