# US 2023/0068519 A1 · Extensible format-independent middleware message interpreter

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

- Number: US 2023/0068519 A1
- Document ID: US20230068519A1
- Status: Published application
- Kind: A1
- Application number: 17/461,683
- Filed: 2021-08-30
- Published: 2023-03-02
- Earliest claimed: 2021-08-30
- Assignees: KYOCERA Document Solutions Inc.
- Applicants: KYOCERA Document Solutions, Inc.
- Inventors: Neil-Paul P. Bermundo; Katherine Bayquen Lao
- Web page: https://patentgrep.com/patent/US20230068519A1

## CPC

- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 8/61: Installation
- G06F 9/4413: {Plug-and-play [PnP]}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 8/70: Software maintenance or management
- G06F 2209/547: Messaging middleware
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and apparatus for an extensible, format-independent middleware message interpreter is disclosed in which a host machine is configured with a universal message service (UMS). The UMS communicates with local and cloud servers and destination devices. The UMS is configured with a plug-in service that can accommodate plug-in libraries of plug-in modules. The UMS receives formatted messages from the local and cloud server applications and destination devices, parses the messages, and identifies a command message type. Based on the command message type, the UMS performs actions including executing the local command on the host machine, relaying the embedded-sub-message data to the at least one destination device as indicated by the destination identification, and relaying the embedded-sub-message data to the plug-in service.

## Claims

### Claim 1

A method comprising:
configuring a host machine with a universal message service (UMS), the UMS transmitting to and receiving from at least one of a local server application and a cloud server application, and to at least one destination device;
configuring the UMS with a plug-in service, the plug-in service accommodating at least one plug-in library, the at least one plug-in library comprising at least one installable plug-in module;
receiving a formatted message at the UMS from at least one of the local server application and the cloud server application, the formatted message including a destination identification, a command message type, an actual message type, and an actual message including embedded-sub-message data;
parsing and identifying the command message type at the UMS, the command message type being at least one of a local command, a relay command, and a relay plug-in command; and
performing at least one action based on the command message type, wherein the at least one action includes at least one of executing the local command on the host machine, relaying the embedded-sub-message data to the at least one destination device as indicated by the destination identification, and relaying the embedded-sub-message data to the plug-in service.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
parsing and identifying, by the plug-in service, relayed embedded-sub-message data from the UMS;
translating the relayed embedded-sub-message data using the plug-in service, resulting in translated embedded-sub-message data; and
performing at least one of:
executing the translated embedded-sub-message data on the UMS;
relaying the translated embedded-sub-message data to another application running on the host machine;
relaying the translated embedded-sub-message data to the at least one destination device; and
on condition the at least one destination device does not have the ability to process the translated embedded-sub-message data: sending a response to a user.

### Claim 3 (depends on 1)

The method of claim 1, wherein in the command message type is the local command executed on at least one of the UMS and another application running on the host machine, wherein the local command indicates actions including:
auto-discovery of the at least one destination device;
retrieval of device attributes for the at least one destination device;
destination device firmware updates for the at least one destination device;
destination device settings queries and changes to the at least one destination device;
rebooting the at least one destination device;
restarting the at least one destination device; and
waking the at least one destination device up from a sleep state.

### Claim 4 (depends on 1)

The method of claim 1, wherein the command message type is the relay command, the method further comprising transmitting the formatted message to the at least one destination device, wherein the relay command includes the embedded-sub-message data to be processed.

### Claim 5 (depends on 1)

The method of claim 1, further comprising installing the at least one plug-in library to the plug-in service.

### Claim 6 (depends on 5)

The method of claim 5, wherein the command message type is the relay plug-in command and the plug-in service includes the at least one plug-in library, the method further comprising:
transmitting the formatted message to the plug-in service, wherein the relay plug-in command is at least one of a plain data message the at least one plug-in library is able to understand and an executable script the at least one plug-in library is able to execute.

### Claim 7 (depends on 5)

The method of claim 5, wherein installing the at least one plug-in library comprises using a plug-in library installation program stored on the host machine.

### Claim 8 (depends on 5)

The method of claim 5, further comprising:
packaging at least one of plug-in library files, plug-in library scripts, the installable plug-in modules, and a plug-in library installation program into a local command message;
receiving at the UMS the local command message, the local command message instructing the UMS to install at least one of the plug-in library files, the plug-in library scripts, the installable plug-in modules, and the plug-in library installation program; and
installing the at least one plug-in library on the host machine.

### Claim 9 (depends on 8)

The method of claim 8, further comprising the UMS calling at least one of an operating system process and a third-party tool to perform the installation of the at least one plug-in library.

### Claim 10 (depends on 8)

The method of claim 8, further comprising at least one of auto-registering the at least one plug-in library with the UMS upon installation of the at least one plug-in library and the UMS calling a registration application programming interface of the at least one plug-in library to register the at least one plug-in library with the UMS.

### Claim 11

A computing apparatus comprising:
a processor; and
a memory storing instructions that, when executed by the processor, configure the apparatus to:
configure a host machine with a universal message service (UMS), the UMS transmitting to and receiving from at least one of a local server application and a cloud server application, and to at least one destination device;
configure the UMS with a plug-in service, the plug-in service accommodating at least one plug-in library, the at least one plug-in library comprising at least one installable plug-in module;
receive a formatted message at the UMS from at least one of the local server application and the cloud server application, the formatted message including a destination identification, a command message type, an actual message type, and an actual message including embedded-sub-message data;
parse and identify the command message type at the UMS, the command message type being at least one of a local command, a relay command, and a relay plug-in command; and
perform at least one action based on the command message type, wherein the at least one action includes at least one of executing the local command on the host machine, relaying the embedded-sub-message data to the at least one destination device as indicated by the destination identification, and relaying the embedded-sub-message data to the plug-in service.

### Claim 12 (depends on 11)

The computing apparatus of claim 11, wherein the instructions further configure the apparatus to:
parse and identify, by the plug-in service, relayed embedded-sub-message data from the UMS;
translate the relayed embedded-sub-message data using the plug-in service, resulting in translated embedded-sub-message data; and
perform at least one of:
execute the translated embedded-sub-message data on the UMS;
relay the translated embedded-sub-message data to another application running on the host machine;
relay the translated embedded-sub-message data to the at least one destination device; and
on condition the at least one destination device does not have the ability to process the translated embedded-sub-message data: sending a response to a user.

### Claim 13 (depends on 11)

The computing apparatus of claim 11, wherein in the command message type is the local command executed on at least one of the UMS and another application run on the host machine, wherein the local command indicates actions including:
auto-discovery of the at least one destination device;
retrieval of device attributes for the at least one destination device;
destination device firmware updates for the at least one destination device;
destination device settings queries and changes to the at least one destination device;
rebooting the at least one destination device;
restarting the at least one destination device; and
waking the at least one destination device up from a sleep state.

### Claim 14 (depends on 11)

The computing apparatus of claim 11, wherein the command message type is the relay command and the instructions further configure the apparatus to transmit the formatted message to the at least one destination device, wherein the relay command includes the embedded-sub-message data to be processed.

### Claim 15 (depends on 11)

The computing apparatus of claim 11, wherein the instructions further configure the apparatus to install the at least one plug-in library to the plug-in service.

### Claim 16 (depends on 15)

The computing apparatus of claim 15, wherein the command message type is the relay plug-in command and the plug-in service includes the at least one plug-in library, and wherein the instructions further configure the apparatus to:
transmit the formatted message to the plug-in service, wherein the relay plug-in command is at least one of a plain data message the at least one plug-in library is able to understand and an executable script the at least one plug-in library is able to execute.

### Claim 17 (depends on 15)

The computing apparatus of claim 15, wherein installing the at least one plug-in library comprises using a plug-in library installation program stored on the host machine.

### Claim 18 (depends on 15)

The computing apparatus of claim 15, wherein the instructions further configure the apparatus to:
package at least one of plug-in library files, plug-in library scripts, the installable plug-in modules, and a plug-in library installation program into a local command message;
receive at the UMS the local command message, the local command message instructing the UMS to install at least one of the plug-in library files, the plug-in library scripts, the installable plug-in modules, and the plug-in library installation program; and
install the at least one plug-in library on the host machine.

### Claim 19 (depends on 18)

The computing apparatus of claim 18, wherein the instructions further configure the UMS to call at least one of an operating system process and a third-party tool to perform the installation of the at least one plug-in library.

### Claim 20 (depends on 18)

The computing apparatus of claim 18, wherein the instructions further configure the apparatus to at least one of auto-register the at least one plug-in library with the UMS upon installation of the at least one plug-in library and instruct the UMS to call a registration application program interface of the at least one plug-in library to register the at least one plug-in library with the UMS.
