Patent 10031715

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

Active provider: Google · gemini-2.5-flash

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

✓ Generated

Obviousness Analysis of US Patent 10,031,715 Under 35 U.S.C. § 103

This analysis identifies combinations of prior art references that would render the claims of US Patent 10,031,715 obvious to a person having ordinary skill in the art (PHOSITA), and explains the motivation for such combinations. The independent claims (1, 10, and 17) of US10031715 center on a method and apparatus for dynamic master device switching within a synchrony group. Key elements involve a master device receiving a request to transfer mastership to a slave device, the master sending a message to cause the slave to become master, and the new master (formerly the slave) notifying a third device of its new status.

Identified Prior Art References

Based on the "Prior art" section, the most relevant references for this analysis are:

  1. US6909689B1 ("System and method for synchronizing operations among a plurality of independently-clocked digital data processing devices"): This patent, assigned to Sonos Inc., describes a networked audio system with "synchrony groups" comprising master devices and slave devices that synchronously play media using precise timing mechanisms. However, according to the prior analysis, it does not explicitly disclose dynamic switching of the master role from a first device to a second device in response to a request, nor the subsequent notification by the newly appointed master to a third device. It focuses on establishing and maintaining synchrony.
  2. US6665721B1 ("Speaker array control system"): Describes a system for controlling an array of speakers in a multi-room audio environment, with a central controller or master. It highlights distributed audio control and user interaction for control.
  3. General Knowledge of a Person Having Ordinary Skill in the Art (PHOSITA) in Networked Distributed Systems: This encompasses common design principles for distributed computing, fault tolerance, role management, and user interface interaction in networked environments.

Obviousness Combination and Motivation

Combination: US6909689B1 + General Knowledge of Fault Tolerance and Flexible Role Management in Distributed Systems + US6665721B1 (for User Interaction Context)

1. Foundation from US6909689B1:
US6909689B1 provides the fundamental architecture for the claimed invention. It clearly teaches a networked audio system comprising multiple zone players (devices) interconnected by a network. Within this system, devices can form "synchrony groups" where a "master device" and "slave devices" synchronously play an audio program using sophisticated timing mechanisms. This reference establishes the context of synchronized multi-room audio with designated master and slave roles for media playback.

2. Motivation for Dynamic Master Switching:
While US6909689B1 focuses on maintaining synchrony with a generally fixed master, a PHOSITA would be motivated to introduce dynamic master switching into such a system for several compelling reasons, which are often addressed in the design of robust and flexible distributed systems:

  • Fault Tolerance: In any distributed system, a single point of failure is undesirable. If the current master device were to fail, disconnect, or be shut down, the entire synchrony group might cease to function. Enabling another device (a slave) to seamlessly take over as master would enhance the system's resilience and continuity of service. The specification of US10031715 itself hints at this, noting that master migration "may occur for any of a number of reasons, including, for example, that the master device 21 is terminating playback by it of the audio program and is leaving the synchrony group 20, but one or more of the other devices in the synchrony group is to continue playing the audio program."
  • User Convenience and Flexibility: Users often desire flexibility in controlling their networked devices. For instance, a user might initiate playback from a device in one room (making it the master), but then move to another room and wish for the device in that second room (initially a slave) to assume mastership for easier control or proximity to an audio source. This desire for flexible control is inherent in networked entertainment systems, as exemplified by US6665721B1's emphasis on controlling speaker arrays.
  • Load Balancing/Resource Optimization: In some scenarios, transferring mastership could optimize network traffic or processing load, although this specific motivation is not explicitly detailed in the prior art, it is a general consideration in distributed system design.

3. Obvious Implementation Details (Request, Messaging, Notification):
Once the motivation to implement dynamic master switching into a system like US6909689B1 is established, the specific steps claimed in US10031715 would be obvious implementations for a PHOSITA:

  • Receiving a Request to Transfer Mastership (Claims 1 & 10):
    • Networked audio systems, including those described in US6909689B1, utilize user interface modules (e.g., element 13 in US6909689B1) for user control. It is a common and obvious practice in distributed systems for users to initiate changes to system configuration or roles via a user interface. Therefore, receiving a "request" (e.g., as a command from a user interface module) at the current master device to transfer its role to another device would be a straightforward design choice.
  • Sending a Message to Cause the Slave to Become Master (Claims 1 & 10):
    • In a networked environment, the mechanism for one device to "cause" another device to assume a new role is by sending a control message over the network. The current master, upon receiving a request to transfer mastership, would obviously send a specific message (e.g., a "transfer mastership" command or a "become master" instruction) to the designated slave device. This explicit messaging ensures clear communication and coordinated action during a critical role change, which is fundamental to reliable distributed system operation.
  • The New Master Notifying a Third Device (Claims 1 & 10):
    • After a device transitions to a critical role like "master," it is standard and obvious practice in distributed systems for the new role-holder to announce its new status. This "notification" can be sent to various "third devices" which need to maintain an accurate understanding of the system's current state. For example, the "user interface module 13" (as taught in US6909689B1 and reinforced by US6665721B1's concept of a controller interacting with a user interface) would be a prime candidate for receiving such a notification, allowing it to update its display and correctly route subsequent commands to the new master. This ensures system consistency, prevents stale information from causing operational errors, and provides essential feedback to the user.

4. Apparatus Claim (Claim 17):
Claim 17 describes a media playback device configured to perform the method of Claim 10. Given that US6909689B1 discloses zone players (devices) with processors, memory, and network interfaces for audio playback and communication, if the method of Claim 10 is obvious, then configuring such a device to execute these obvious steps (i.e., by implementing the corresponding software instructions) would also be obvious to a PHOSITA. The hardware components are generic, and the inventive step lies in the programmed functionality.

Conclusion

The independent claims 1, 10, and 17 of US10031715, related to dynamic master device switching, would have been obvious to a person of ordinary skill in the art at the time of the invention. US6909689B1 provides the foundational system of networked synchronized audio players with master/slave roles. The motivation to introduce dynamic master switching stems from well-known needs in distributed systems for fault tolerance, user convenience, and flexibility. The specific implementation steps—receiving a request (e.g., from a user interface), sending a message to instruct the transfer, and the new master sending a notification to a third device—are all conventional and obvious communication and state management techniques in networked distributed environments.

Generated 5/26/2026, 1:07:10 AM