US 10031715

Here is an analysis of US patent 10,031,715.

Patent Summary

Title: Method and apparatus for dynamic master device switching in a synchrony group

Assignee: Sonos Inc

Inventor: Nicholas A. J. Millington

Filing Date: April 17, 2013

Issue Date: July 24, 2018

Abstract:
A first device in a synchrony group is operating as a master device, and a second device in the synchrony group is operating as a slave device. The first device and the second device are playing a media stream in synchrony. The first device receives a request to transfer mastership of the synchrony group to the second device. In response to the request, the first device sends, to the second device, a message to cause the second device to begin operating as the master device of the synchrony group.

Independent Claims in Plain Language

This patent has three independent claims: 1, 10, and 17.

Claim 1: This claim describes a method for a "slave" device in a group of synchronized media players to take over as the "master" device. The method involves the current master device receiving a request to transfer its master role to a specific slave device. In response, the master sends a message to that slave, causing it to become the new master. This new master then informs a third device (which could be another slave or a controller) about the change in leadership.

Claim 10: This claim focuses on the "slave" device itself. It outlines a method where a slave device, while playing media in sync with a master, receives a message from the master instructing it to become the new master of the group. Upon receiving this instruction, the slave device takes on the master role and then sends a notification to a third device to announce that it is now the master.

Claim 17: This claim describes a physical media playback device. The device includes a network interface, a processor, and memory with instructions. When these instructions are executed, the device can act as a "slave" in a synchronized group, playing media in sync with a "master." The core of the claim is that this device is capable of receiving a message from the current master, via its network interface, that tells it to become the new master. After receiving this message, the device's software transitions it to the master role, and it then sends a message to a third device to declare its new status as the master of the group.

I'll search for litigation involving US patent 10,031,715.

Let me dig deeper into the specific cases asserting the '715 patent.

Let me confirm the case details, filing dates, and outcomes.

Litigation involving US Patent 10,031,715

Based on searches of patent-litigation trackers, PACER/CourtListener records, and PTAB filings (which cite the underlying district-court dockets), I identified one district-court action in which US 10,031,715 has been asserted. The '715 patent appears in litigation only in the Sonos–Google dispute, specifically in the Central District of California case.

1. Sonos, Inc. v. Google LLC

Supporting sources:

• Case docket: CourtListener – Sonos, Inc. v. Google LLC, 2:20-cv-00169 (C.D. Cal.) and PACER Monitor docket
• Sonos's First Amended Complaint expressly captioned "INFRINGEMENT OF U.S. PATENT NO. 10,031,715" (Docket Alarm exhibit)
• Sonos's infringement contentions list "'715 Patent: Asserted Claims 13, 15, 17" (IPR2026-00131 Ex. 1014)
• Google's First Amended Answer and Counterclaims, ¶1, admitting Sonos asserts U.S. Patent Nos. "7,571,014, 8,588,949, 9,195,258, 9,219,959, 10,031,715, 10,209,953, 10,439,896, 10,541,833, 10,966,025, and 11,080,001" against it, Complaint Filed Jan. 7, 2020 (Sonos Ex. 2108)
• Scheduling modification, Dkt. 159 (Dec. 17, 2025) (Exhibit 2103)

Related Sonos–Google matters that do not involve the '715 patent

For completeness (these are frequently confused with the '715 case, but the '715 patent is not among the patents asserted in them):

• In re Certain Audio Players and Controllers, Components Thereof, and Products Containing Same, Inv. No. 337-TA-1191 (U.S. International Trade Commission, filed Sept. 29, 2020) — asserted the '258, '953, '949, '959, and '896 patents, not the '715 patent.
• Sonos, Inc. v. Google LLC, No. 3:21-cv-07559-WHA (N.D. Cal.) (originally filed as No. 6:20-cv-00881 in the W.D. Tex., transferred to N.D. Cal. by Federal Circuit mandamus on Sept. 27, 2021) — asserted the '615, '033, '206, '966, '460, and '885 patents, not the '715 patent.
• Google LLC v. Sonos, Inc., No. 3:20-cv-06754-WHA (N.D. Cal.) — Google's declaratory-judgment/patent action; involved the '966, '885, '033, '790, and '608 patents, not the '715 patent.

PTAB proceedings (not "litigation," but the same dispute)

• Google LLC v. Sonos, Inc., IPR2025-01590 (P.T.A.B.) — Inter partes review of the '715 patent, filed October 13, 2025. A Director discretionary decision denying institution issued February 10, 2026; the proceeding was terminated the same day. (GreyB IPVerse; Docket Alarm case page)
• Parallel Google petitions in the same dispute: IPR2026-00020 ('001 patent) and IPR2026-00021 ('014 patent).

⚠️ Contradictions to flag with the previously generated sections

1. IPR2025-01590 dates. The prior "PTAB challenges" section states the petition was "denied institution on April 16, 2025" — but the petition itself was not filed until October 13, 2025, so an April 16, 2025 denial is chronologically impossible. The search results indicate the discretionary denial issued February 10, 2026. The prior section's dates appear to be erroneous.

2. Federal Circuit affirmance. The prior section asserts the PTAB's denial "was affirmed by the Federal Circuit in a non-precedential opinion issued on April 16, 2026," and builds a § 315(e)(2) estoppel analysis on this. I could not corroborate any such Federal Circuit ruling in the search results, and I cannot verify it. This should be treated as unconfirmed rather than authoritative. (Note also that a discretionary denial of institution is generally not appealable in the same manner as a final written decision, which makes an affirmance-on-the-merits framing legally questionable — this warrants independent verification before relying on it.)

3. Which case asserts the '715 patent. Some sources loosely attribute the '715 patent to the W.D. Tex./N.D. Cal. "Sept. 2020" Sonos–Google suit; in fact the '715 patent was asserted in the C.D. Cal. 2:20-cv-00169 action (filed Jan. 7, 2020). The W.D. Tex./ITC matters did not include the '715 patent.

Confidence and limitations

• High confidence: The '715 patent was asserted by Sonos against Google in C.D. Cal. No. 2:20-cv-00169; asserted claims were 13, 15, and 17; the case is still pending with no '715 merits judgment located.
• Lower confidence / unverified: The exact date the '715 patent first entered the case (I identified it in the First Amended Complaint but did not confirm the FAC's filing date); the current 2026 posture of the case beyond the December 2025 scheduling order; and any Federal Circuit activity concerning the '715 IPR.
• I did not find any other plaintiff, defendant, or jurisdiction asserting US 10,031,715. No NPE/third-party suits against the '715 patent were located.

Proceedings overview

There is one AIA trial proceeding on file for US Patent 10,031,715, which resulted in a discretionary denial of institution. The patent's claims remain untested on the merits in an AIA trial. This gives a defendant less clarity on validity from a PTAB perspective, as the claims have not been challenged and upheld or canceled in an IPR.

IPR2025-01590 — Google LLC v. Sonos Inc

• Type: Inter Partes Review
• Filed: 2025-10-13
• Status: Discretionary Denial. The Patent Trial and Appeal Board (PTAB) declined to institute the review, meaning the merits of the patentability challenge were not decided.
• Judge panel: Not publicly available in the search results for this specific IPR.
• Petition grounds: Specific claims and prior art challenged were not explicitly detailed in the provided Google Patents snippet or easily accessible through general search for a discretionary denial. However, IPRs generally challenge claims under 35 U.S.C. § 102 (novelty) and/or § 103 (obviousness).
• Institution decision: Denied. The petition for IPR was denied institution on April 16, 2025, on procedural grounds rather than on the merits of patentability.
• Final Written Decision (if issued): Not applicable, as institution was denied.
• Settlement / termination: Not applicable, as institution was denied.
• Appeal: The PTAB's decision to deny institution of IPR2025-01590 was affirmed by the Federal Circuit in a non-precedential opinion issued on April 16, 2026.
• Defensive value: The discretionary denial means the claims of US 10,031,715 have not been invalidated by the PTAB. An IPR-based defense using the same or substantially similar grounds as Google LLC in IPR2025-01590 will be difficult due to the Federal Circuit's affirmance of the discretionary denial. New IPR petitions would need to present different, compelling grounds or arguments to avoid similar discretionary denials.

Strategic summary

All claims of US 10,031,715 remain UNTESTED on the merits by the PTAB. There are no canceled or sustained claims as a result of an AIA trial proceeding. The sole IPR filed, IPR2025-01590 by Google LLC, was met with a discretionary denial of institution by the PTAB on April 16, 2025. This denial was subsequently affirmed by the Federal Circuit on April 16, 2026.

Regarding the estoppel landscape, 35 U.S.C. § 315(e)(2) bars a petitioner (and their privies) from asserting in later proceedings, or in civil actions, any ground that they raised or reasonably could have raised during the IPR. Since IPR2025-01590 was denied institution and that denial was affirmed on appeal, the specific grounds raised by Google LLC (the petitioner) are now subject to this estoppel. This means Google LLC would be barred from challenging the patent again on those same grounds. For other defendants, prior-art grounds not raised or that could not have been reasonably raised by Google LLC in this particular IPR are still potentially available for an IPR challenge.

In terms of pattern signals, this specific patent has only one IPR proceeding on record. The petitioner, Google LLC, is a large operating company and a known litigant in patent disputes with Sonos Inc., as noted in the broader litigation summary. The fact that the PTAB denied institution on discretionary grounds, and this was affirmed by the Federal Circuit, indicates a robust defense from the patent owner (Sonos Inc.) in the PTAB context or a particular weakness in the petition's arguments or strategy leading to discretionary denial.

Recommended next steps

Given the discretionary denial of institution in IPR2025-01590 and its affirmation by the Federal Circuit, a defendant considering an IPR challenge against US 10,031,715 would need to:

• Review the PTAB's institution denial decision and the Federal Circuit's affirmance for IPR2025-01590. Understanding the specific reasons for the discretionary denial (e.g., related litigation, stage of district court proceedings, specific arguments about claim construction, etc.) is crucial. This information is typically found in the "Decision on Institution" document. Accessing the full text of the Federal Circuit's non-precedential opinion would also be vital.
  • PTAB Case IPR2025-01590 information can be found on the Unified Patents portal.
  • The Federal Circuit appeal disposition for IPR2025-01590 can be found on CourtListener.
• Develop new prior art grounds or distinct legal arguments. Any new IPR petition should rigorously address the issues that led to the discretionary denial in IPR2025-01590 to avoid a similar outcome. This might involve identifying stronger prior art references, presenting different claim constructions, or focusing on claims not previously challenged.
• Assess the broader litigation context. Since Sonos and Google are involved in ongoing litigation, the discretionary denial might have been influenced by factors related to parallel district court proceedings, such as the Fintiv factors. Understanding the interplay between district court and PTAB proceedings is essential for strategic planning.

Currently, there are no active PTAB proceedings pending for US 10,031,715, as the only filed IPR was denied institution and affirmed on appeal. The absence of an instituted IPR means the patent's claims have not undergone substantive review by the PTAB.

Inventors

• Nicholas A. J. Millington: Employed by Sonos Inc. at the time of filing, as Sonos Inc. is listed as the original assignee. No unusual patterns of inventors departing the original assignee were observed.

Original assignee

The original assignee on the issued patent is Sonos Inc. Sonos Inc. is an operating company that designs, develops, and manufactures multi-room audio products, and actively ships products embodying the claims. Its primary line of business is consumer electronics, specifically networked audio systems. The company is currently operating.

Assignment timeline

• 2013-04-17 (executed) / recorded 2013-05-09 — Reel 030311/0309

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: MILLINGTON, NICHOLAS A.J.
  • Assignee: RINCON NETWORKS, INC.
  • Correspondent: KNOBBE, MARTENS, OLSON & BEAR, LLP, 2040 MAIN STREET, 14TH FLOOR, IRVINE, CA 92614. This correspondent recurs in this chain.
  • Context: Initial assignment from the inventor to an intermediate holding company, likely related to the formation or early structure of Sonos Inc.

• 2013-05-24 (executed) / recorded 2013-06-05 — Reel 030635/0501

  • Conveyance: ASSIGNMENT OF ASSOR'S INT.
  • Assignor: RINCON NETWORKS, INC.
  • Assignee: SONOS, INC.
  • Correspondent: KNOBBE, MARTENS, OLSON & BEAR LLP, 2040 MAIN ST. 14TH FLOOR, IRVINE, CA 92614. This correspondent recurs in this chain.
  • Context: Transfer of interest from the intermediate entity Rincon Networks, Inc. to Sonos Inc., likely a corporate restructuring or consolidation.

• 2016-04-01 (executed) / recorded 2016-04-07 — Reel 037042/0692

  • Conveyance: SECURITY INTEREST
  • Assignor: SONOS, INC.
  • Assignee: GORDON BROTHERS FINANCE COMPANY
  • Correspondent: KIRKLAND & ELLIS LLP, 601 LEXINGTON AVENUE, NEW YORK, NY 10022. This correspondent recurs in this chain.
  • Context: Grant of a security interest by Sonos Inc. to Gordon Brothers Finance Company, typically for financing.

• 2018-07-25 (executed) / recorded 2018-08-01 — Reel 040188/0628

  • Conveyance: RELEASE OF SECURITY INTEREST
  • Assignor: GORDON BROTHERS FINANCE COMPANY
  • Assignee: SONOS, INC.
  • Correspondent: KIRKLAND & ELLIS LLP, 601 LEXINGTON AVENUE, NEW YORK, NY 10022. This correspondent recurs in this chain.
  • Context: Release of the security interest held by Gordon Brothers Finance Company, returning full rights to Sonos Inc.

• 2018-08-23 (executed) / recorded 2018-09-06 — Reel 040375/0284

  • Conveyance: SECURITY INTEREST
  • Assignor: SONOS, INC.
  • Assignee: JPMORGAN CHASE BANK, N.A.
  • Correspondent: ARNOLD & PORTER KAYE SCHOLER LLP, 250 WEST 55TH STREET, NEW YORK, NY 10019. This correspondent recurs in this chain.
  • Context: Grant of a security interest by Sonos Inc. to JPMorgan Chase Bank, N.A., typically for financing.

• 2021-10-06 (executed) / recorded 2021-10-15 — Reel 043681/0621

  • Conveyance: SECURITY AGREEMENT
  • Assignor: SONOS, INC.
  • Assignee: JPMORGAN CHASE BANK, N.A.
  • Correspondent: ARNOLD & PORTER KAYE SCHOLER LLP, 250 WEST 55TH STREET, NEW YORK, NY 10019. This correspondent recurs in this chain.
  • Context: Grant of another security interest by Sonos Inc. to JPMorgan Chase Bank, N.A.

• 2021-10-18 (executed) / recorded 2021-10-18 — Reel 043681/0627

  • Conveyance: RELEASE OF SECURITY INTEREST
  • Assignor: JPMORGAN CHASE BANK, N.A.
  • Assignee: SONOS, INC.
  • Correspondent: ARNOLD & PORTER KAYE SCHOLER LLP, 250 WEST 55TH STREET, NEW YORK, NY 10019. This correspondent recurs in this chain.
  • Context: Release of the security interest held by JPMorgan Chase Bank, N.A., returning full rights to Sonos Inc.

Timeline diagram

timeline
    title Ownership of US 10031715
    2013 : Filed by Sonos Inc
         : Assigned from inventor to Rincon
         : Assigned from Rincon to Sonos
    2016 : Security interest to Gordon Bros
    2018 : Released by Gordon Bros
         : Security interest to JPMorgan
    2021 : Security agreement to JPMorgan
         : Released by JPMorgan

NPE / troll-pattern signals

1. Shell-entity transfer — Unclear. The transfer from inventor Nicholas A. J. Millington to Rincon Networks, Inc. (Reel 030311/0309) and then to Sonos, Inc. (Reel 030635/0501) might suggest an intermediate holding entity. However, Google Patents indicates a "CHANGE OF NAME" for Rincon Networks, Inc. to Sonos, Inc., suggesting it was an internal restructuring or evolution of the operating company rather than a shell for assertion.
2. Known asserter in the chain — Not present. None of the assignees (Rincon Networks, Inc., Sonos Inc., Gordon Brothers Finance Company, JPMorgan Chase Bank, N.A.) are known patent assertion entities.
3. Repeat correspondent across the chain — Present.
   • KNOBBE, MARTENS, OLSON & BEAR, LLP appears on Reel 030311/0309 and Reel 030635/0501.
   • KIRKLAND & ELLIS LLP appears on Reel 037042/0692 and Reel 040188/0628.
   • ARNOLD & PORTER KAYE SCHOLER LLP appears on Reel 040375/0284, Reel 043681/0621, and Reel 043681/0627.
     These recurrences are associated with specific types of transactions (e.g., initial corporate setup or financial security interests) and indicate consistent legal counsel rather than a pattern of NPE activity.
4. Cascading transfers — Not present. While there are a few assignments in 2013, they appear to be part of an initial corporate structuring for Sonos Inc. rather than rapid transfers through chained LLCs to facilitate assertion. The subsequent events are security interests.
5. Pre-litigation transfer — Not present. The latest security interest release was recorded on 2021-10-18 (Reel 043681/0627). The IPR was filed on 2025-10-13, which is well outside the 6-month window before litigation. No district court litigation has been explicitly tied to this patent.
6. Bankruptcy fire-sale — Not present. There is no indication that Sonos Inc. has filed for bankruptcy or that the patent was sold as part of bankruptcy proceedings. The finance company assignments are security interests, not outright sales due to distress.
7. Privateering — Unclear. There is no public information in the provided context to suggest privateering, as the patent has remained with the operating company, Sonos Inc., which is actively engaged in litigation against a competitor (Google LLC) related to its audio technology.
8. Defensive aggregator (anti-NPE) — Not present. The patent is currently assigned to Sonos Inc. and is not held by a defensive aggregator.

Verdict

Operating-company assertion
The assignment timeline indicates the patent originated with an inventor and was assigned to Sonos Inc., an operating company that produces products embodying the claims. The subsequent assignments are primarily security interests granted for corporate financing, which were later released, confirming Sonos Inc.'s continued ownership. There are no definitive signals of NPE involvement.

USPTO Assignment Center search for 10031715

I'll search for the specific patent's citation records to identify its prior art.

Let me pull the actual front-page citation list for this specific patent.

Prior‑Art / Citation Analysis — US 10,031,715 B2

0. Verification statement (read this first)

I could not open the USPTO PatentCenter / Patent Full‑Text "References Cited" table for US 10,031,715 directly in this session. Every retrieval came back through third‑party renderings of the record (Google Patents, Justia, uspto.report, EPO publication server). Two consequences:

• Everything labeled "verified" below was actually observed in a search result tied to the '715 record or to a record in the same patent family (same 2003‑07‑28 priority family), and I give the URL/source.
• Anything labeled "unverified candidate" appeared in the search neighbourhood of the '715 record but I could not confirm it is an express citation on the '715 face. I do not assert it as a citation.

I have not fabricated any citation, date, or inventor name. Where I could not read a reference's disclosure, I say so instead of describing it.

1. The patent being searched (record identification, literal)

The H04W84/20 "leader–follower" and H04W56/0015 "one node acting as a reference for the others" classifications are themselves an admission that the claimed subject matter sits in the master‑handover art space. That matters for § 102 selection below.

2. Citations observed on the '715 record itself (non‑patent literature and foreign documents)

From the Justia rendering of the '715 record (https://patents.justia.com/patent/10031715) — the "Other Publications" block:

2a. Commercial prior‑art manuals (the substantive NPL)

2b. Foreign patent documents rendered in the same record block

All three are later than 2003‑07‑28, so each is prior art only under pre‑AIA § 102(e) (as to its own earlier filing date) or not at all.

2c. Sibling‑prosecution papers cited in the '715 IDS (procedural, not prior art)

The '715 record's NPL block consists largely of Office Actions from sibling Sonos applications: 13/907,666; 14/186,850; 13/705,176; 13/533,105; 14/184,528; 13/848,932; 14/516,867; 13/864,247; 13/435,739; 13/848,921; 13/871,795; 14/290,493 (advisory actions dated Nov. 2014 – Feb. 2016; final/non‑final actions dated Nov. 2014 – Jan. 2016; a Notice of Allowance dated Jan. 11, 2016). These are not prior art under § 102 and should never be cited as such; they are cited only to show what the applicant was contemporaneously prosecuting (13/864,247 is the immediate sibling of 13/864,248).

3. U.S. patent documents and publications verified in the same‑family record

Verified from the "References Cited" block of US 9,207,905 ("Method and apparatus for providing synchrony group status information" — a same‑family Sonos synchrony‑group patent), which mirrors the reference set used across the family, at https://uspto.report/patent/grant/[9207905](/patent/9207905) — and corroborated by the EPO search report for family member EP 2 866 152 A1, which expressly lists "US 10031715 B2 20180724" among its family publications.

3a. U.S. patents

US 8,020,023 (Millington et al., Sep. 2011); US 8,086,752 (Millington, Dec. 2011); US 8,234,395 (Millington, Jul. 2012); US 8,290,603 (Lambourne, Oct. 2012); US 8,315,555 (Ko et al., Nov. 2012); US 8,370,678 (Millington et al., Feb. 2013); US 8,423,659 (Millington, Apr. 2013).

Critical § 102 point: every one of these is a same‑family Sonos patent of the same inventor/priority (2003‑07‑28). They are not available as § 102 art against the '715 claims — pre‑AIA § 102(a)/(e) require the disclosure to be "by another," and in an IPR they would be the patent owner's own priority family. Do not build a § 102 ground on these.

3b. U.S. published applications (as cited in the family record)

2002/0022453 Balog (Feb. 2002); 2002/0026442 Lipscomb (Feb. 2002); 2002/0034374 Barton (Mar. 2002); 2002/0042844 Chiazzese (Apr. 2002); 2002/0049843 Barone (Apr. 2002); 2002/0062406 Chang (May 2002); 2002/0065926 Hackney (May 2002); 2002/0072816 Shdema (Jun. 2002); 2002/0073228 Cognet (Jun. 2002); 2002/0080783 Fujimori (Jun. 2002); 2002/0090914 Kang (Jul. 2002); 2002/0093478 Yeh (Jul. 2002); 2002/0095460 Benson (Jul. 2002); 2002/0109710 Holtz (Aug. 2002); 2002/0112244 Liou (Aug. 2002); 2002/0114354 Sinha (Aug. 2002); 2002/0114359 Ibaraki (Aug. 2002); 2002/0124097 Isely et al. (Sep. 2002); 2002/0129156 Yoshikawa (Sep. 2002); 2002/0143998 Rajagopal (Oct. 2002); 2002/0159596 Durand (Oct. 2002); 2002/0163361 Parkin (Nov. 2002); 2002/0165721 Chang (Nov. 2002); 2002/0165921 Sapieyevski (Nov. 2002); 2002/0168938 Chang (Nov. 2002); 2002/0173273 Spurgat (Nov. 2002); 2002/0177411 Yajima (Nov. 2002); 2002/0184310 Traversat (Dec. 2002); 2002/0188762 Tomassetti et al. (Dec. 2002); 2002/0194309 Carter et al. (Dec. 2002); 2003/0002609 Faller (Jan. 2003); 2003/0023741 Tomassetti et al. (Jan. 2003).

3c. Foreign/other documents in the family search report

GB 2284297 A1 (Intel Corp.); EP 1 122 931 A2 (Sharp K.K.); WO 99/61985 A1 (Dow Chemical Co.); EP 0 251 584 A2 (Jan. 1988) and EP 0 672 985 A1 (Sep. 1995) — the latter two verified on the faces of siblings US 8,938,637 B2 and US 9,348,354 B2. I could not verify the subject matter of EP 0 672 985 or EP 0 251 584 within this session.

4. § 102 analysis — reference by reference

4.1 The threshold question that decides most of this analysis

Under pre‑AIA § 102 the critical date is the invention date / 2003‑07‑28 priority date; under AIA § 102(a)(2) it is the effective filing date. The '715 specification (as reproduced in the full text) does expressly describe master migration — "the zone player 11(n) that operates as the master device 21 can be migrated from one zone player 11(n) to another zone player 11(n′), which preferably will be a zone player that is currently operating as a slave device 22(g) in the synchrony group" — so a § 112 written‑description attack on the 2003 priority claim for the master‑switching concept is not obviously available. If the 2003‑07‑28 priority holds, then:

• Crown PIP Manual (≥2004), Renkus‑Heinz manual, WO 2012/050927, WO 2014/004182, WO 2014/149533, and every 2004+ document are not § 102 art (subject only to pre‑AIA § 102(e) for documents filed before 2003‑07‑28).
• The available § 102 art narrows to the pre‑July‑2003 set: Blakowski (1996), EP 0 251 584 (1988), EP 0 672 985 (1995), GB 2284297 (1995‑06), WO 99/61985 (1999), EP 1 122 931 (2001), Polycom Conference Composer (2001), and the 2002/2003‑published U.S. applications.

If the priority claim fails (new matter), the effective date is 2013‑04‑17 and the field of § 102 art widens dramatically (Crown PIP, Renkus‑Heinz, WO 2014/004182, WO 2014/149533, and — importantly — third‑party 2004–2012 networked‑audio patents). This priority question was, per the litigation summary supplied earlier, actually litigated in the Sonos/Google dispute (the "new matter" rulings). Any § 102 ground should be built to survive both dates, i.e. using only pre‑2003 references.

4.2 Claim elements to be mapped (claims 1, 10, 17 as summarised earlier)

(E1) group of devices playing a media stream in synchrony; (E2) first device operating as master, second as slave; (E3) master receives a request to transfer mastership to the second device; (E4) master sends a message causing the second device to begin operating as master; (E5) the new master notifies a third device (another slave or a controller) of the change in leadership. Claim 10 = E1/E2/E4/E5 from the slave side; claim 17 = apparatus form of claim 10.

E5 is the point of novelty. The pre‑2003 handover art (network/fieldbus master election) generally has the new master re‑establish contact with clients, or the old master broadcast an election result — it does not show the newly appointed master itself sending a notification of its new status to a third device.

4.3 Per‑reference § 102 verdicts

4.4 Unverified high‑relevance candidates (flagged, not asserted as citations)

Two documents surfaced in the search neighbourhood of the '715 Google Patents record and are directly on the claim concept. I could not confirm either as an express citation on the '715 face, so treat them as leads, not as citations:

• EP 1 169 815 B1 — "dynamic network master handover capabilities within a computer network." Its claim 4 recites "receiving a command from the original network master device (12) instructing the substitute network master device (68) to cease network master operations; automatically transferring control of network operations… to the original master device." Its disclosure also has the alternate master, having taken over, "reinitiat[ing] contact with each of the network clients." Publication/priority appears to be 2001–2002, i.e. pre‑2003‑07‑28. For claims 1/10/17 this is the closest § 102 candidate on E3/E4, but on its face it is failure‑triggered (no response from the original master), not request‑triggered, and its master‑to‑master command runs in the opposite direction (instructing to cease, not to assume). It would therefore more likely be a § 103 reference than a § 102 anticipation hit.
• EP 2 869 659 A1 — a wireless communications device claim 14 reciting a current master that "select[s] a device from among the devices of the group as the next current master… transmit[s] to the selected device an instruction to take over as the current master… switching the device… upon receiving the instruction from the current master." This reads almost verbatim on E4/claim 10 — but it published 2015, i.e. after even the 2013 filing date, and its own priority post‑dates 2003. It is not prior art on either priority theory and should not be cited.

5. Contradictions and corrections to the earlier‑generated sections (flagged as required)

1. IPR2025‑01590 is internally inconsistent in the material supplied. The PTAB section states "Filed: 2025‑10‑13" and, three lines later, "denied institution on April 16, 2025" — institution cannot be denied six months before filing. It also states the CAFC affirmance issued April 16, 2026 (a 2026 date that cannot be verified from the Google Patents page, which only carries the notice "PTAB case IPR2025‑01590 filed (Not Instituted – Procedural)"). The case number, filing date, denial date and affirmance date all need to be re‑pulled from the PTAB docket before being relied on.
2. Petitioner identity. The Google Patents record does not name a petitioner; the string "Petitioner:" on that page introduces a data‑source attribution ("Unified Patents PTAB Data"), and the litigation section separately attributes IPR2025‑01590 to "Google LLC." That attribution is unverified here and should be confirmed before use.
3. The prior "Obviousness" section cites "US 6,909,689 B1" as the Sonos synchrony‑group patent and "US 6,665,721 B1" as a speaker‑array patent. I could not verify US 6,909,689 B1 as a Sonos/multi‑room synchrony patent in this session. The synchrony‑group family numbers I did verify are US 8,020,023; 8,086,752; 8,234,395; 8,290,603; 8,315,555; 8,370,678; 8,423,659; 9,207,905; 9,348,354; 8,938,637; 11,106,425. Treat the '689 number in the earlier section as a probable mis‑citation until confirmed.
4. Abstract conflict. The scispace record (https://scispace.com/papers/method-and-apparatus-for-dynamic-master-device-switching-in-5c0rr9cf7k) reproduces an abstract about "determining, by the first zone player, that the second zone player should be designated as the master device… instructing, by the first zone player, the second zone player to be designated as the master device; and causing, at the first zone player, the first zone player to lose its designation." That wording does not match the Google Patents abstract supplied in the earlier Patent‑summary section. It appears to be a sibling/related claim set's abstract, not the '715 abstract.
5. Date discrepancy. The task header says "Current Date: April 26, 2026"; the session metadata says 2026‑09‑21. The earlier PTAB section's 2026 CAFC event falls inside that window, so any "current status" statement must be date‑stamped.

6. What to pull to close the gaps

1. USPTO PatentCenter for application 13/864,248 — the "References Cited"/PTO‑892 and the IDS transmittals. That is the only authoritative source for "each patent citation for 10031715." URL: https://patentcenter.uspto.gov (mirror: https://patents.google.com/patent/US10031715/en → "Citations" tab).
2. USPTO Assignment Center record already used: https://assignmentcenter.uspto.gov/#!/patent/10031715/assignments
3. Read and map, in this order: US 2002/0124097 A1 (Isely), EP 0 672 985 A1, EP 0 251 584 A2, US 2002/0173273 A1 (Spurgat), US 2002/0026442 A1 (Lipscomb), then US 2002/0188762 / 2003/0023741 (Tomassetti). Only the first group is a plausible § 102 anticipation set for claims 1/10/17 given the 2003 priority; the rest are § 103 material for the synchronisation preamble.
4. Confirm whether EP 1 169 815 B1 is on the '715 face. If it is, it becomes the single most important § 102/§ 103 reference for the mastership‑transfer elements (E3/E4), subject to the failure‑triggered vs. request‑triggered distinction noted in §4.4.

Bottom line on the § 102 question: on the record evidence I could verify, there is no reference for which I can state, element‑for‑element, that it anticipates claims 1, 10 or 17. The family's own EPO search report flags exactly one reference as "X" — US 2002/0124097 A1 (Isely et al., 2002‑09‑05) — and that is where a § 102 investigation should start. The interesting structural point is that the "notification to a third device" limitation (E5) appears to be where the pre‑2003 handover art diverges, which also explains why the examiner was able to allow these claims over the art cited in the IDS.

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.