# US 2012/0254474 A1 · Milarrs Systems and Methods

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

- Number: US 2012/0254474 A1
- Document ID: US20120254474A1
- Status: Published application
- Kind: A1
- Application number: 13/494,452
- Filed: 2012-06-12
- Published: 2012-10-04
- Earliest claimed: 2005-01-07
- Assignees: Lantronix, Inc.
- Inventors: Curtis D. Brown; Nicholas J. Witchey
- Web page: https://patentgrep.com/patent/US20120254474A1

## CPC

- H04L 41/00: Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- G06F 11/3495: {for systems}
- H04L 41/0213: Standardised network management protocols, e.g. simple network management protocol [SNMP]
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 43/106: using time related information in packets, e.g. by adding timestamps
- H04L 43/16: Threshold monitoring
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An add-on module provides extrinsic management functionality to legacy and other devices. Contemplated modules include: (a) a state agent that provides at least one of the MILARRS function, and (b) a product agent that communicates with the device using at least one serial interface. Implementations are contemplated for both legacy devices that natively provide less than complete MILARRS functionality, and newly developed devices for which the developer desires a ready-made implementation of MILARRS functionality.

## Claims

### Claim 1

A device management module comprising:
a medical device connection configured to communicatively couple with at least one target medical device lacking a management functionality; and
a hardware-based management module configured to:
have an interaction with the target medical device to access device data from the target medical device; and
provide a non-native version of the management functionality for the at least one target medical device by translating or manipulating the device data into management data, where the non-native version of the management functionality includes at least one MILARRS management functionalities.

### Claim 2 (depends on 1)

The module of claim 1, wherein the medical device connection comprises a wired interface.

### Claim 3 (depends on 2)

The module of claim 2, wherein the wired interface comprises at least one of the following types of interfaces: I2C, SPI, CAN, RS-232, RS-485, RS-422, USB, Firewire, Profibus, and Ethernet.

### Claim 4 (depends on 1)

The module of claim 1, wherein the medical device connection comprises a wireless interface.

### Claim 5 (depends on 4)

The module of claim 4, wherein the wired interface comprises at least one of the following types of interfaces: 802.11, WiMAX, Bluetooth, and Zigbee.

### Claim 6 (depends on 1)

The module of claim 1, wherein the interaction comprises instructing the target medical device to power down.

### Claim 7 (depends on 1)

The module of claim 1, wherein the interaction comprises configuring the target medical device.

### Claim 8 (depends on 1)

The module of claim 1, wherein the interaction comprises sending complex instructions to the target medical device.

### Claim 9 (depends on 1)

The module of claim 1, wherein the interaction comprises autonomously managing the target medical device.

### Claim 10 (depends on 1)

The module of claim 1, wherein the interaction comprises querying the target medical device.

### Claim 11 (depends on 11)

The module of claim 11, wherein the interaction further comprises receiving the device data as a response to querying the target medical device.

### Claim 12 (depends on 1)

The module of claim 1, wherein the MILARRS management functionalities includes at least one of the following: monitoring, inventorying, logging, alerting, recovering, reporting, and securing.

### Claim 13 (depends on 1)

The module of claim 1, wherein the hardware-based management module is further configured to provide non-management functionalities for the target medical device.

### Claim 14 (depends on 11)

The module of claim 11, wherein the non-management functionalities include at least one of the following: a web server, an FTP server, an operating system, a developer infrastructure, and a device manager infrastructure.

### Claim 15 (depends on 1)

The module of claim 1, wherein the hardware-based management module comprises a device server.

### Claim 16 (depends on 15)

The module of claim 15, wherein the device server comprises an embedded component.

### Claim 17 (depends on 15)

The module of claim 15, wherein the device server comprises an external device server.

### Claim 18 (depends on 1)

The module of claim 1, wherein the hardware-based management module is further configured to have an interaction with multiple target medical devices via the medical device connection to access the device data.

### Claim 19 (depends on 1)

The module of claim 1, wherein the management data reflects state information derived from the device data.

### Claim 20 (depends on 19)

The module of claim 19, wherein the state information includes at least one of the following: a configuration item, a time stamp, an event, an alert policy, an inventory item, reporting information, a trend, security information, authentication information, monitoring data, an action, and logging data.

### Claim 21 (depends on 1)

The module of claim 1, wherein the management data is in the form of a management ecosystem format.

### Claim 22 (depends on 21)

The module of claim 21, wherein the management ecosystem format comprises a mark-up language.

### Claim 23 (depends on 22)

The module of claim 22, wherein the management ecosystem format comprises a mark-up language.

### Claim 24 (depends on 22)

The module of claim 22, wherein the management ecosystem format comprises an XML-based format.

### Claim 25 (depends on 1)

The module of claim 1, wherein the management data is in the form of a management ecosystem protocol.
