# US 2025/0097304 A1 · Session management 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/0097304 A1
- Document ID: US20250097304A1
- Status: Published application
- Kind: A1
- Application number: 18/829,915
- 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/US20250097304A1

## 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 session management for variable-length message streams. In an example method, a computing system establishes a first session by receiving, from a first computer system, registration information including a first session identifier and a specification of a channel; determining a stream orchestration instance for the channel; and joining the first computer system to the first session for the stream orchestration instance based on the first session identifier. The computing system receives, from a second computer system, a message including context information, the context information including the first session identifier. The computing system identifies the first session based on the first session identifier, the first session having one or more member computer systems. The computing system outputs the message to at least one of the one or more member computer systems of the first session.

## Claims

### Claim 1

A computer-implemented method, comprising:
establishing a first session, wherein establishing the first session comprises:
receiving, from a first computer system, registration information, the registration information including a first session identifier and a specification of a channel,
determining a stream orchestration instance for the channel, and
joining the first computer system to the first session for the stream orchestration instance based on the first session identifier;
receiving, from a second computer system, a message, the message including context information, the context information including the first session identifier;
identifying the first session based on the first session identifier, the first session having one or more member computer systems; and
outputting the message to at least one of the one or more member computer systems of the first session.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein:
the message is a variable-length message further including a payload;
the 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 1)

The computer-implemented method of claim 1, further comprising:
determining, from the context information, routing information including a specification of the at least one of the one or more member computer systems, the routing information based on a set of stream orchestration specifications, 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 the specification of the at least one of the one or more member computer systems.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein:
the routing information includes one or more first tasks defining a first route; and
the routing information is determined based on a specification of the first route that is included in the context information.

### Claim 5 (depends on 1)

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

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein joining the first computer system to the first session for the stream orchestration instance based on the first session identifier comprises generating a new session for the stream orchestration instance.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein joining the first computer system to the first session for the stream orchestration instance based on the first session identifier comprises joining an existing session for the stream orchestration instance.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, further comprising:
determining that the first session for the stream orchestration instance has expired; and
generating a new session for the stream orchestration instance.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, further comprising, responsive to receiving the registration information, generating the stream orchestration instance.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the at least one of the one or more member computer systems includes the first computer system and further comprising:
receiving, from the first computer system, a second message, the second message including second context information, the second context information including the first session identifier;
identifying the first session based on the first session identifier; and
outputting the message to the at least one of the one or more member computer systems of the first session including the second computer system.

### Claim 11 (depends on 1)

The computer-implemented method of claim 1, further comprising:
receiving, from the first computer system, a second message, the second message including second context information, the second context information including the first session identifier;
identifying the first session based on the first session identifier; and
outputting the message to the at least one of the one or more member computer systems of the first session not including the second computer system.

### Claim 12 (depends on 1)

The computer-implemented method of claim 1, wherein the message is based on a format described using a specification written in a capability interface definition language.

### Claim 13 (depends on 12)

The computer-implemented method of claim 12, wherein the channel is defined using the capability interface definition language.

### Claim 14 (depends on 12)

The computer-implemented method of claim 12, wherein:
the capability interface definition language is AsyncAPI; and
the message is received using a WebSocket endpoint.

### Claim 15 (depends on 12)

The computer-implemented method of claim 12, wherein the context information includes a plurality of sections, wherein content of each section is defined in the specification using the capability interface definition language.

### Claim 16

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:
establishing a session, comprising:
receiving, from a first computer system, registration information, the registration information including a first session identifier and a specification of a channel;
determining a stream orchestration instance for the channel; and
joining the first computer system to a first session for the stream orchestration instance based on the first session identifier;
receiving, from a second computer system, a message, the message including context information, the context information including the first session identifier; and
identifying the first session based on the first session identifier, the first session having one or more member computer systems; and
outputting the message to at least one of the one or more member computer systems of the first session.

### Claim 17 (depends on 16)

The system of claim 16, wherein:
the message is a variable-length message further including a payload;
the message is encoded in a binary format;
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; and
the operations further comprise:
determining, from the context information, routing information including a specification of the at least one of the one or more member computer systems, the routing information based on a set of stream orchestration specifications, 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 the specification of the at least one of the one or more member computer systems.

### Claim 18 (depends on 17)

The system of claim 17, wherein:
the message is based on a format described using a specification written in a capability interface definition language; and
the message is received using a WebSocket endpoint.

### Claim 19

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:
establishing a session, comprising:
receiving, from a first computer system, registration information, the registration information including a first session identifier and a specification of a channel;
determining a stream orchestration instance for the channel; and
joining the first computer system to a first session for the stream orchestration instance based on the first session identifier;
receiving, from a second computer system, a message, the message including context information, the context information including the first session identifier; and
identifying the first session based on the first session identifier, the first session having one or more member computer systems; and
outputting the message to at least one of the one or more member computer systems of the first session.

### Claim 20 (depends on 19)

The non-transitory computer-readable media of claim 19, wherein
the message is a variable-length message further including a payload;
the message is encoded in a binary format;
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; and
the operations further comprise:
determining, from the context information, routing information including a specification of the at least one of the one or more member computer systems, the routing information based on a set of stream orchestration specifications, 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 the specification of the at least one of the one or more member computer systems.
