Device synchronisation over a network

Patent No. US7274761 (titled "Device synchronisation over a network") on Jun 21, 2001. The application was issued on Sep 25, 2007.

What is this patent about?

’761 is related to the field of synchronizing real-time clocks across separate devices in a distributed network. It specifically addresses the challenges of maintaining temporal alignment in multimedia applications, such as surround sound systems or video playback, where audio and video streams must be perfectly coordinated despite being processed by different hardware components. The background context highlights the difficulty of achieving this synchronicity when communication latencies are unknown or variable, particularly in wireless environments.

The underlying idea behind ’761 is the clever reuse of an existing low-level network heartbeat to calibrate high-level application clocks. Instead of attempting to transmit a real-time clock value directly—which would be rendered inaccurate by unpredictable transmission delays—the system anchors a specific real-time value to a specific, identifiable beat of a common time reference already used for network maintenance. By mapping a wall-clock time to a specific network slot or frame index, the receiver can reconstruct the correct time regardless of when the message actually arrives.

The claims of ’761 focus on a transceiver architecture and associated methods that utilize a shared time reference with distinguishable instances to synchronize clocks. The independent claims cover the mechanism of reading a real-time clock at a specific network instance and transmitting both that value and the identity of the instance. Conversely, they cover a receiver that uses this paired information to calculate a current real-time value by accounting for the elapsed intervals of the common reference between the identified instance and the present moment.

In a practical implementation, such as a Bluetooth piconet, the invention leverages the Link Level Synchronisation used for fast frequency hopping as the common time reference. The controller identifies a specific Bluetooth clock slot or frame number and associates it with the value of a separate Real Time Clock. Because the master and slave devices are already synchronized at the bit level to the frequency hopping sequence, they share a precise understanding of when each slot occurs, providing a sub-microsecond accurate framework for time distribution.

This approach differs from prior methods by decoupling the transmission latency from the synchronization accuracy. Traditional methods often suffer from jitter caused by protocol stack delays; however, by using distinguishable instances of a shared heartbeat, the ’761 invention ensures that the receiver can accurately 'back-date' or 'forward-date' the received time stamp to the correct network beat. This effectively eliminates the impact of variable network traffic or processing overhead, allowing distributed wireless speakers or displays to maintain perfect phase alignment.

How does this patent fit in bigger picture?

Technical Landscape

In the late 1990s when ’761 was filed, the synchronization of distributed multimedia devices was typically implemented using physical wired connections to ensure low-latency timing across multiple outputs. At a time when wireless systems commonly relied on asynchronous data transfer or basic link-level timing for radio frequency management rather than high-precision application-layer clock alignment, maintaining synchronicity between spatially separated audio and video components was non-trivial. Hardware and software constraints of the era meant that variable latencies in wireless transmission often resulted in perceptible drift between real-time clocks, as standard network protocols lacked a unified mechanism to map local system time to a shared, high-resolution temporal reference across independent nodes.

Prosecution Position

The disclosed invention achieves a technical advancement in distributed clock synchronization by establishing a mapping between a local real-time clock and a shared network-level time reference characterized by distinguishable, periodic instances. The architectural shift involves utilizing existing link-level synchronization—originally designed for frequency hopping or radio timing—as a common temporal anchor to distribute specific real-time clock values associated with discrete time instances. This integration enables receivers to calculate and correct their own real-time clocks based on the temporal offset between a transmitted reference instance and the current network state. The resulting technical effect is the mitigation of variable transmission latencies, enabling microsecond-level synchronization across wireless nodes without requiring dedicated physical timing hardware.

Claims

This patent contains 68 claims, with independent claims 1, 16, 34, 35, 36, 37, 38, and 39 focusing on devices and methods for synchronizing real-time clock information between a transmitter and a receiver using a shared common time reference with distinguishable instances, particularly within low-power frequency hopping networks. The independent claims cover both the transmission side, where a clock value is associated with a specific instance of the common reference, and the reception side, where the received value is used to determine a current clock time by correcting for differences between time instances. The dependent claims serve to further define the technical implementation by specifying Bluetooth standard compatibility, link-level synchronization details, frame and slot numbering for instance identification, and the use of specific hardware interfaces or media device applications.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Common time reference
(Claim 1, Claim 16, Claim 34, Claim 35, Claim 36, Claim 37, Claim 38, Claim 39)
In a preferred embodiment, the Link Level Synchronisation which is used for the timing of Fast Frequency Hopping is used as the common time reference of the present invention. This advantageously provides Real Time synchronism between devices in the range of a few microseconds. In embodiments of the invention, the synchronous instances of the common time reference are such that when there is an instance in one device there is an identifiably corresponding instance in an other device.A shared temporal framework used by both transmitter and receiver to establish synchronous instances, specifically utilized to coordinate the timing of real time clocks across separate devices.
Distinguishable instances
(Claim 1, Claim 16, Claim 34, Claim 35, Claim 36, Claim 37, Claim 38, Claim 39)
The transmitter is arranged to synchronise to a common time reference having distinguishable instances. In embodiments of the invention, the synchronous instances of the common time reference are such that when there is an instance in one device there is an identifiably corresponding instance in an other device. Preferably, the instances are separated by a fixed time period or an integral number of fixed time periods.Specific, identifiable points in time within the common time reference that allow devices to correlate a real time clock value with a precise moment shared by other devices in the network.
First instance
(Claim 1, Claim 16, Claim 34, Claim 35, Claim 36, Claim 37, Claim 38, Claim 39)
The first instance may be in the past or may be in the future at the moment of transmission. The transmitter may calculate the real time clock value at the first instance by adding the time difference between the first instance and the identified instance to the real time clock value at the identified instance. However, the first instance and the identified instance may be one and the same, in which case such calculation is unnecessary.A specific point in the common time reference (past or future) for which a corresponding real time clock value is identified and transmitted to facilitate synchronization.
Low power frequency hopping network
(Claim 36, Claim 37, Claim 38, Claim 39)
According to a preferred embodiment of the present invention, the wireless communication is provided in accordance with the Bluetooth Standard. In this preferred embodiment, existing aspects of the existing Bluetooth system are ingeniously re-used. In particular the Link Level Synchronisation which is used for the timing of Fast Frequency Hopping is used as the common time reference of the present invention.A wireless communication environment, such as one operating under the Bluetooth Standard, where devices use fast frequency hopping and link-level synchronization to maintain timing.
Real time clock
(Claim 1, Claim 16, Claim 34, Claim 35)
The present invention relates to the synchronisation of Real Time clocks of separate devices. If the outputs are distributed in space, however, it may be difficult to establish and maintain synchronicity between the real time clocks associated with each output. During recording and playback the different media streams (audio and video) need to be adjusted with respect to a certain time reference.A local clock within a device that tracks actual time for multimedia synchronization, which is calibrated against the common time reference to ensure alignment with other devices.
Real time clock value
(Claim 1, Claim 16, Claim 34, Claim 35)
The transmitter may calculate the real time clock value at the first instance by adding the time difference between the first instance and the identified instance to the real time clock value at the identified instance. The real time clock value is the received value, if necessary, corrected in accordance with the time difference between the first and second instances. This allows for the control of the timing of multimedia output so that each of the outputs have the correct timing relative to other events.The specific time data read from a device's local clock at a designated instance, which is then transmitted or corrected to achieve synchronization with other devices.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
2:25-cv-00333Feb 21, 2025Ecolab Usa Inc. V. Zappbug Inc

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US7274761

Application Number
US09885130A
Filing Date
Jun 21, 2001
Publication Date
Sep 25, 2007
External Links
Slate, USPTO , Google Patents