patent.fyi
Applications  /  US 2026/0354773
United States Patent Application Publication

US 2026/0354773 A1

Published
Nov 12, 2026
Filed
Jul 16, 2026
Earliest date on the face
Jan 20, 2021
Classification
A61B 5/746
First published here
Nov 19, 2026

Generated automatically. Not reviewed by a person. Not legal advice or an opinion.

Section 1 · machine-generated

What if?

Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.

1.2Derive the wearable address

What ifWhat if the server computed the wearable identifier from the user identifier without looking it up in a database?
Claim language“query a device database”

During enrollment, a provisioning station assigns the wearable the first 128 bits of a keyed hash of its assigned user's identifier. The monitoring server repeats the calculation when a request arrives and combines the result with a locally configured gateway address and port.

1.3Queue requests for collection

What ifWhat if the server queued each request for the wearable to collect without checking for an active channel?
Claim language“whether an active bidirectional communication channel exists”

The server writes the request to a queue keyed by wearable identifier and sets a 30-second expiration time. The wearable retrieves pending requests every five seconds and acknowledges each request by its sequence number.

1.4Connect on a wearable timer

What ifWhat if a timer in the wearable initiated the secure connection without a notification from the watch service server?
Claim language“pushes a notification to the target wearable device”

The wearable opens an authenticated connection to the monitoring server every ten seconds. The monitoring server returns any pending session request during registration, and the wearable closes the connection when the server has no pending request.

1.6Start capture from wearable controls

What ifWhat if the wearer started capture locally and the server applied the client's data type selection to the incoming streams?
Claim language“transmit monitoring activation signals to the target wearable device”

The wearer selects the microphone, display, or camera on the wearable and presses a start button. The wearable tags outgoing packets by source, and the server forwards packets whose source matches the client's selection.

1.8Relay over a dedicated connection

What ifWhat if each monitoring request used its own dedicated connection to the requesting client?
Claim language“through group-based connections”

The server binds the wearable stream to the open response for that request using a unique request identifier. The relay writes each received packet to that response, which serves a single client.

Section 2 · machine-generated

Variations

Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.

Other field of use

Remote inspection of utility tunnels

An inspection technician wears a camera, microphone, and wrist display connected to a wearable computing unit. A monitoring server maps the technician identifier to the wearable and requests a secure bidirectional session through a notification service when the wearable is offline. The server forwards requested camera images and audio to the inspection console in the session group and sends console audio back to the technician.

Component substitution

Connection readiness through a message queue

A persistent message queue replaces the in-memory object that signals completion of a connection request. The monitoring server creates a pending request with a correlation identifier and passes the identifier to the notification service for delivery to the wearable. The wearable returns the identifier in its registration message, and the registration handler publishes a readiness event after establishing the secure channel. A queue consumer matches the event to the pending request and sends the requested capture settings over the channel.

Media delivery through a forwarding unit

A selective forwarding unit replaces the monitoring server's media packet relay. The monitoring server resolves wearable identifiers, verifies connection state, and sends capture commands over a secure control channel. The wearable publishes separately identified audio and image tracks to the forwarding unit over an encrypted media connection. The client presents a session credential to the forwarding unit, which checks the group identifier and forwards the tracks selected by the client.

Parameter or scale variation

Low bandwidth audio and image sessions

A wearable encodes mono audio at 16 kilobits per second in 40-millisecond frames and caps each camera image at 40 kilobytes. It sends one 320 by 240 pixel image every five seconds and gives audio frames transmission priority over image fragments. The monitoring server relays both data types to the session group and ends audio capture after 15 seconds without a client keep-alive, which the client sends every five seconds.

Combination with existing systems

Monitoring sessions from veterinary patient records

A veterinary patient-record system stores the identifier of a wearable assigned to an animal during admission. A clinician selects a monitoring control in the active encounter, and the record system sends the animal identifier and requested capture types to the monitoring server. The monitoring server resolves the wearable and returns a session reference that the record interface uses to display the live feed. Closing the encounter sends a session termination request to the monitoring server.

Automated or data-driven variant

Fall detection triggers remote assessment

A wearable samples a three-axis accelerometer and gyroscope at 50 samples per second and checks for an impact followed by a posture change and ten seconds of low movement. After the wearer has ten seconds to cancel the alert, the wearable sends an event and its device identifier to a dispatch service. The dispatch service selects the on-duty responder and submits a monitoring request for that wearable. The monitoring server establishes or reuses the secure session and enables microphone capture when the responder opens the alert.

Specific version of a part

Structured monitoring request body

The client sends an authenticated HTTP POST with a JSON body containing a user identifier and an array of requested capture types. The request handler checks that the identifier is present and passes it to the device lookup routine.

Certificate authenticated wearable registration

The wearable opens an encrypted connection and presents a device certificate. Its first application message carries a group identifier, which the server verifies against the device identity before enabling bidirectional messages for the session.

Length prefixed monitoring packets

The wearable sends packets over the encrypted connection with a payload length, source code, sequence number, and capture timestamp in each header. The server buffers incoming bytes until it has the declared payload length, then passes the complete packet to the relay.

Keep-alive with missed interval timeout

The client sends a keep-alive message every five seconds with the audio session identifier. Each valid message resets a 15-second server timer, and timer expiration closes the audio stream.

Section 3 · quoted from USPTO records

Other work

Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.

Document AUS 7,450,580 B2
Published
Nov 11, 2008
Filed
Dec 20, 2002
Class
H04L 12/28
Document BUS 2020/0092211 A1
Published
Mar 19, 2020
Filed
Sep 19, 2018
Class
H04L 47/20
Claim 1
Document A
Document B
1.1a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: receive, via an application programming interface, a monitoring request containing a user identifier from a client computing device;
The workflow 400 begins at block 404, where the Controller 105 Receives flow information. In the illustrated embodiment, the flow information indicates that the Controller 105 should request telemetry for the flow from Host 115A to Host 115B.
B · US 2020/0092211 A1 · ¶ 42
1.2a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: query a device database to resolve the user identifier to a specific wearable device identifier and associated connection parameters;
1.3a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: determine, via a connection state manager, whether an active bidirectional communication channel exists between the monitoring server and a target wearable device;
1.4a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: responsive to determining no active channel exists, generate a task completion source object and transmit a connection initiation signal to a watch service server, wherein the watch service server pushes a notification to the target wearable device instructing establishment of a secure connection;
1.5a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: establish a secure bidirectional connection with the target wearable device upon receiving a registration request containing a group identifier;
1.6a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: transmit monitoring activation signals to the target wearable device specifying requested data types selected from audio stream capture, screen capture, and/or camera image capture;
1.7a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: receive monitoring data packets from the target wearable device via the secure connection;
According to the present invention, an application-layer multicast system for multicast content data from a sender too a plurality of receivers through an intermediate system on a unicast network based on a data request message of each of the receivers, wherein the intermediate system includes: a routing controller controlling application-layer multicast routing based on the data request message at application layer; and at least one data copying device, each of which is made
A · US 7,450,580 B2 · ¶ 15
1.8a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: relay the received monitoring data to the client computing device through group-based connections; and
As described later, for each ALM data, an ALM delivery tree is formed from the data sending host 100 to the data receiving hosts 140, 150, 160 and 170 through the intermediate nodes 110, 120 and 130. The ALM delivery tree is dynamically changed with data receiving hosts joining or leaving the group at any time.
A · US 7,450,580 B2 · ¶ 43
1.9a monitoring server comprising a processor and memory storing executable instructions that, when executed by the processor, cause the monitoring server to: maintain active audio streaming sessions by monitoring for periodic keep-alive signals from the client computing device at predetermined intervals, wherein absence of a keep-alive signal within a timeout threshold triggers automatic stream termination.

An empty cell means only that no passage was reproduced there.

Statements in these documents
To support IP multicast, however, all network systems including intermediate nodes must be multicast-enabled.
A · US 7,450,580 B2 · ¶ 6
Accordingly, ALM advantageously uses an existing unicast IP network at the network layer.
A · US 7,450,580 B2 · ¶ 9
More specifically, embodiments disclosed herein relate to use of policies to track telemetry of packets in a network.
B · US 2020/0092211 A1 · ¶ 1
Detecting packet drops in network flows, as well as isolating the node where the drop occurred, is a challenge for network operators.
B · US 2020/0092211 A1 · ¶ 2
Cite aspatent.fyi, US 2026/0354773 A1, claim 1, first published 2026-11-19T03:31:31-05:00, https://patent.fyi/US20260354773/, SHA-256 8e6d1363d77e6d204857eb00726c0d817443280fcca1bd0bdf2e47a7d1c2d033
First published
Permanent addresshttps://patent.fyi/US20260354773/
Content fingerprint (SHA-256)8e6d1363d77e6d204857eb00726c0d817443280fcca1bd0bdf2e47a7d1c2d033
Methodv2026-11-18.2 · automated, not reviewed by a person
Correctionscorrections@patent.fyi