US 8537195

I'll search for the patent and any 2026 litigation/docket activity.

Let me run a couple more targeted searches.

Summary — U.S. Patent No. 8,537,195 B2

Bibliographic data (from the authoritative patent text)

(The patent text also notes earlier security-interest/release filings by Morgan Stanley, Macquarie, and Wells Fargo, and a 2023 assignment to H-P. The assignee records are as listed; the patent document lists "Polycom LLC" as filing entity and "POLYCOM, INC." as original assignee in the prosecution history.)

Abstract (as issued)

A videoconference multipoint control unit (MCU) automatically generates display layouts for videoconference endpoints. Display layouts are generated based on attributes associated with video streams received from the endpoints and display configuration information of the endpoints. An endpoint can include one or more attributes in each outgoing stream. Attributes can be assigned based on video streams' role, content, camera source, etc. Display layouts can be regenerated if one or more attributes change. A mixer can generate video streams to be displayed at the endpoints based on the display layout.

Plain-language overview of the independent claims

Claim 1 — Method. A method of generating display content for an endpoint that talks over a network to at least one other endpoint. The core steps are:

1. Automatically build a display layout for the receiving endpoint — no human/VNOC operator. The layout is derived from (a) attributes carried on the video streams received from the other endpoint(s), and (b) display-configuration information of the receiving endpoint, which must include at least the number of display devices at that endpoint.
2. Building the layout involves creating a set of cells and assigning received video streams to those cells, with one video stream per cell.
3. Mix the received video streams according to that layout to make one or more outgoing video streams for the endpoint, where mixing includes combining the video streams in the cells into an outgoing video stream.
4. Crucially, the layout must preserve a spatial relationship between at least two of the video streams received from the other endpoint(s) — i.e., streams that were spatially related at the source (e.g., left/center/right camera views of one room) stay spatially related on the display.

Claim 9 — Apparatus (MCU). The same invention expressed as a videoconferencing MCU that manages a conference between an endpoint and at least one other endpoint. It has:

1. A layout manager that automatically generates the display layout for the endpoint from stream attributes plus endpoint display-configuration information (again, at least the number of display devices), by generating cells and assigning one received video stream per cell.
2. A mixer, communicatively coupled to the layout manager, that mixes the received streams per the layout to produce the outgoing stream(s) for the endpoint, including combining the cell-assigned streams into an outgoing video stream.
3. The layout must likewise preserve a spatial relationship between at least two of the received video streams.

Dependent claims worth noting (briefly): the layout is a continuous-presence layout (2, 10); a stream may carry more than one attribute (3, 11); the layout is dynamically regenerated when an attribute changes (4, 12); identification of the stream carrying the current speaker and tagging the outgoing stream as containing the current speaker (5–7, 13–15); spatial arrangement of cells to preserve source spatial relationships (8, 17); and the MCU may be located at the endpoint itself (16).

Litigation / docket check (as requested)

I searched for CAFC 2026 docket activity and district-court litigation specifically citing 8,537,195. I found no appeal or 2026 Federal Circuit docket entry involving this patent, and no infringement suit asserting it. Results returned for the query included unrelated matters (e.g., Headwater Research LLC v. Verizon in E.D. Tex. involving U.S. 9,215,613 and 8,589,541; Contour IP Holding LLC v. GoPro, Inc., Fed. Cir. No. 2026-2012; and an Amazon v. Perplexity appeal), none of which involve 8,537,195 — I did not attribute those to this patent.

The only non-patent-office third-party record tying this exact number to outside activity is Polycom's IETF IPR disclosure (submitted Dec. 5, 2013 under RFC 3979/4879) in connection with "Framework for Telepresence Multi-Streams" (draft-ietf-clue-framework-12), which lists US 8,537,195 along with AU 2012200314, CN102638672A, EP2487903A2, HK 121085118.6, IN 302/CHE/2012, JP 2012-026497, and US 13/970,231. Source: https://datatracker.ietf.org/ipr/2265/

Uncertainty / caveats

• I did not find authoritative confirmation of any CAFC 2026 docket activity for this patent; treat the "no known appeal" statement as the absence of evidence, not proof, since public docket coverage of every district case is not exhaustive.
• Assignee of record has changed hands several times; the "current assignee" field on Google Patents (Hewlett-Packard Development Company, L.P.) reflects a recorded 2023 assignment, but the patent's face lists Polycom. I have not independently verified the chain of title beyond the assignment entries in the patent record.
• Independent-claim analysis is based directly on the issued claim text in the patent document; claim terms are quoted/paraphrased literally, including the original's inconsistencies (e.g., "video steams" and "one ore more" in the patent text) which I have not auto-corrected.

I'll research litigation involving US patent 8537195.

Empty results. Let me try other search approaches.

The initial results don't show cases specifically asserting the '195 patent. Let me search more targeted sources.

Findings: Litigation Involving U.S. Patent No. 8,537,195

I could not identify any litigation asserting or otherwise involving U.S. Patent No. 8,537,195 ("Automatic video layouts for multi-stream multi-site telepresence conferencing system"). Searches of patent-litigation aggregators (RPX/insight, Unified Patents, CourtListener, Justia Dockets, UniCourt, Patexia) and general web searches returned no complaint, docket entry, or case caption in which this specific patent number appears.

What I searched and what came back

Note the strict-identifier rule: a related but distinct number appeared in one result — the WiLAN v. Apple matter involved U.S. Patent Nos. 8,537,757 and 8,457,145. 8,537,757 ≠ 8,537,195, so that case is not relevant and I am not reporting it as litigation on the '195 patent.

Nearby Polycom cases surfaced (NOT involving '195 — listed only to show what was checked)

• Realtime Adaptive Streaming LLC v. Polycom, Inc. — D. Colo., No. 1:17-cv-02692, filed 11/10/2017 (asserted Realtime's patents, not '195).
• Wave Linx LLC v. Polycom, Inc. — D. Del., No. 1:19-cv-00609, filed 3/29/2019; voluntarily dismissed 4/26/2019 (asserted U.S. 8,843,549 B2).
• American Patents LLC v. Polycom, Inc. et al. — W.D. Tex., No. 6:21-cv-00742; dismissed 3/10/2022.
• directPacket Research, Inc. v. Polycom, LLC — E.D. Va. → N.D. Cal., No. 3:19-cv-03918 (asserted directPacket's patents, e.g., '588, '978, '828; Polycom filed IPRs).
• Codian Ltd v. Polycom, Inc. — W.D. Ark., No. 07-4063 (asserted U.S. 5,262,964 and 6,535,238).

None of these assert the '195 patent.

Caveats and confidence

• Confidence: moderate-to-low that "no litigation exists." My searches did not return results for the literal patent number, but I cannot rule out litigation that is unreported, sealed, or not indexed by the sources I could reach. The empty result sets I received are also consistent with a search-coverage gap rather than affirmative proof of no litigation.
• I was unable to complete direct lookups on the Unified Patents litigation portal and PACER/CAFC dockets within the available steps, so PACER-level confirmation is outstanding.
• This analysis reflects information available as of the search date and is not a legal opinion or a freedom-to-operate/clearance conclusion.

Bottom line: Based on the sources searched, no known litigation involving U.S. Patent No. 8,537,195 was found. If you need a definitive answer, I recommend a PACER/CAFC docket search and a Darts-ip/Unified Patents litigation query restricted to the exact number, which I can help interpret if you obtain the results.

I'll start by verifying the structured block against live sources before drawing any conclusions.

No PTAB hits yet. Let me check litigation/family context and run a couple more targeted queries.

Let me do a final confirmation pass on the Unified Patents portal and litigation dockets.

Proceedings overview

Zero AIA trial proceedings are on file for US 8,537,195 as of the most recent USPTO ODP ingest, and my independent web searches surfaced no IPR, PGR, or CBM against it either — so the breakdown is 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denied. The bottom-line defensive posture: all 17 claims are untested at the PTAB, which cuts both ways — you cannot point to a canceled claim to kill a demand letter, but you also inherit no adverse claim-construction or validity findings, and the patent remains fully enforceable in its original scope with an adjusted expiration of 2032-02-08.

A caveat on scope, stated plainly because it matters to a defendant: "no PTAB activity" is the default position here, not a proof of impossibility. Termination-before-institution proceedings and very recent filings can lag in ODP indexing, and my search tooling is a general web index, not a live PTAB E2E docket query. The only way to convert this from "no activity found" to "no activity exists" is a PATENTSCOPE / PTAB E2E search-party-instrument or party-name query for Polycom and Hewlett-Packard Development Company filtered to the '195 patent. I could not execute that query here.

Proceedings

None to report. There is no proceeding number to list, and I will not manufacture one. Per the constraints of this task, I am not going to fabricate a docket, a panel, or an FWD that does not exist.

For completeness on the things I did check:

• PTAB trials on the '195 patent: none found. (Source: structured ODP block in the prompt; confirmed by searches for "8537195" IPR, "8537195" PTAB E2E trial proceeding, and Polycom/Unified Patents telepresence IPR queries, none of which returned a trial number for this patent.)
• Unified Patents or other defensive aggregator involvement: none found. A search surfaced only Unified's public patent-analytics page for the European sibling EP-2487903-A3 (portal.unifiedpatents.com/patents/patent/EP-2487903-A3) — that is a data page, not a filed challenge, and Unified is not in the chain as a petitioner.
• Federal Circuit appeals: none found tying to US 8,537,195. One Polycom-related CAFC item did surface (a June 2025 affirmance of invalidity in a "multimedia communication technology" suit where Polycom was the accused infringer); based on the description I cannot link it to this patent, and I am expressly not treating it as related. Flagging it only so the negative result is auditable.

Sibling / family considerations

The structured data shows a continuation child, US 13/970,231, which issued as US 9,462,227 B2 (filed 2013-08-19, claiming priority to the same 2011-02-09 date; listed "Active, expires 2031-07-25"). This matters tactically: the '227 continuation claims substantially the same automatic-layout subject matter, so a defendant analyzing freedom-to-operate on the '195 should analyze the '227 in parallel — otherwise invalidating one leaves the sibling standing. I found no PTAB proceedings on the '227 either, though I did not perform an exhaustive check on that number.

Ownership chain (relevant to who you'd actually be defending against)

Current assignee per the structured data: Hewlett-Packard Development Company, L.P., via a nunc pro tunc assignment from Polycom, Inc. recorded 2023-06-22. This is the ordinary Polycom-alumni chain (Polycom → Plantronics/Polycom security interests → HP), not a troll acquisition. Practical effect: assertion would most likely come from an operating company (HP/Poly), which means a business-resolution / cross-license path is plausible and the litigation posture is likely to be conventional rather than NPE-style volume filing. It also means the patent owner has the resources to defend an IPR to the Federal Circuit — a factor in your cost model.

Strategic summary

Claim status. All claims 1–17 are untested: no independent claim has been canceled, none has been confirmed, and no claim has been construed by the PTAB. That is an unusual and notable posture for a 2011-priority patent that sits in a crowded, heavily litigated art unit (telepresence MCU layout) and that is cited forward by a substantial number of later Cisco, Microsoft, and Polycom rights. Well-asserted patents in this space — Cisco's and Tandberg's telepresence portfolios, for instance — have historically attracted IPR attention. The absence here is more consistent with a patent that has not been used in high-stakes assertion than with one that has been tried and survived. Do not read "no IPRs" as "the claims are strong." Read it as "nobody has bothered yet."

Estoppel landscape. With no petitioner and no institution, no § 315(e)(2) estoppel has attached to anyone. For a defendant being asserted against today, the full universe of § 102/§ 103 prior art remains available — nothing is foreclosed because nothing has been raised. Practically, that means you are the first mover: you can pick your best art, and you are not boxed out of grounds by anyone else's prior petition. The trade-off is that you also get no free roadmap — there is no FWD reasoning to mine for how a panel reads "preserves a spatial relationship" (claim 1) or "display-configuration information" (claim 1), which are the two phrases most likely to carry the infringement analysis.

Pattern signals. No repeat petitioner, no serial-filing pattern, no defensive aggregator, and no evidence of the patent owner prosecuting PTAB appeals on this family. The forward-citation list shows this disclosure is load-bearing prior art for later Polycom and Cisco work (e.g., US 9,606,771; US 10,681,309), and the spec itself incorporates two Polycom patents by reference (U.S. Pat. No. 6,912,178 to Chu et al.; U.S. Ser. No. 12/581,626 to Halavy). Those incorporations are worth a look as potential § 112 support issues, but they are not prior art against the '195 by definition.

Recommended next steps

1. Verify the null result against a primary source before you rely on it. Query PTAB E2E / Patent Center for the '195 and the '227 sibling under both Polycom, Inc. and Hewlett-Packard Development Company, L.P., and check for termination-before-institution proceedings that ODP may not surface. If the answer stays zero, document that — it becomes your due-diligence record.
2. Because no claims are invalidated, there is no FWD to link to or quote. A defendant cannot run the "claim 1 is dead, this is sanction-bait" play here. Your invalidity work is greenfield: budget a full prior-art search, not a gap-fill exercise.
3. Assume the '227 continuation will be asserted alongside the '195. Any invalidity contention or IPR strategy should cover both family members, since a win on one does not clear the other. Note the '195 has an adjusted expiration of 2032-02-08 — roughly five and a half years of term remain from today, which is meaningful runway for the owner and a real cost driver for you.
4. If you do file, watch the statutory clock. For any IPR you institute, the PTAB's one-year trial deadline runs from the institution decision under § 316(a)(11), and the institution decision itself is due within six months of the petition's filing date (or the petitioner's last § 312 supplement, whichever is later) under § 314(b). Those two dates are your project milestones; there is no existing proceeding to piggyback on.
5. Treat the owner's identity as a settlement signal. An HP-family operating-company owner changes the calculus versus an NPE: a cross-license or portfolio-resolution approach is a live option and may be cheaper than a full IPR-plus-district-court campaign.

I'll research the assignment record for this patent, starting with reel/frame data.

Let me try more targeted searches for the assignment records.

Let me look for the specific reel/frame records and the HP assignment.

Assignment Record Reconstruction — U.S. Patent No. 8,537,195 B2

Important sourcing caveat up front: I was unable to retrieve reel/frame numbers or correspondent-of-record fields for this patent's assignments. My searches of the USPTO Assignment Center index (assignment.uspto.gov / assignmentcenter.uspto.gov), PlainSite assignment pages, and general web queries did not return the individual reel/frame for the '195 patent's chain, and I exhausted my search budget before reaching a docket-level record. Rather than infer or fabricate reel/frame identifiers and correspondent names, I have recorded only the assignment events that are documented in the authoritative patent text (Google Patents "reassignment" legal-events table). The correspondent field — the single most useful tell for anonymous assignee LLCs — is not available to me for this chain and should be pulled directly from Assignment Center before this analysis is relied on. Everything below is flagged accordingly.

Inventors

• All four inventors assigned their rights to Polycom, Inc. in a single recorded assignment executed April 2011 (see timeline). That is the standard employee-inventor assignment pattern for a large operating company and is not a fire-sale precursor.
• Unusual-pattern check: I found no evidence that any of the four inventors departed Polycom within 12 months of the February 9, 2011 filing. I could not locate employment-history records for the individual inventors within my available search reach, so this is "not determinable from available records," not "not present." Do not treat the absence of a departure signal as a confirmed negative.
• No inventor is separately listed as a later assignor or assignee anywhere in the chain, which is consistent with a clean all-rights assignment to the employer at filing.

Original assignee

• Entity on the issued patent's face: the prosecution-history entries show "Application filed by Polycom LLC" while the original assignee of record is POLYCOM, INC. (assignment recorded 2011-04-21). Google's entity-tracking renders these as one and the same Polycom; the discrepancy is a naming artifact, not a second entity. (This mirrors the naming inconsistency already flagged in the Patent Summary section; I am not auto-correcting it.)
• Line of business: Polycom, Inc. was a publicly traded (NASDAQ: PLCM) unified-communications vendor — conference phones, video endpoints, and multipoint control units (MCUs). The '195 claims read directly on an MCU/telepresence product line, and the patent cites Polycom's own work (U.S. 6,912,178, Chu et al.; application Ser. No. 12/581,626, Halavy) as incorporated prior work, which is strong evidence Polycom shipped products embodying the claimed subject matter (e.g., its telepresence/MCU platforms).
• Current status: no longer independent. Polycom was taken private (Siris Capital, 2016), later combined with Plantronics (which rebranded as Poly), and its patent estate was assigned to Hewlett-Packard Development Company, L.P. by a nunc pro tunc assignment recorded 2023-06-22. The current holder is therefore an operating company.

Assignment timeline

Chronological list of every assignment event documented in the authoritative patent record. Reel/frame and correspondent are unavailable to me and are shown as "not retrieved" — see caveat above.

• 2011-04-21 (executed 2011-04-21) — Reel not retrieved

  • Conveyance: Assignment of assignors' interest ("ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: SALEH, YOUSSEF; MACEDO, MARCIO; PARIPALLY, GOPAL; DUCKWORTH, MARK R. (the four inventors)
  • Assignee: POLYCOM, INC.
  • Correspondent: not retrieved
  • Context: internal — standard employee-inventor assignment to the operating employer; not an acquisition or fire-sale.

• 2013-12-09 (executed 2013-12-09; underlying credit agreement dated 2013-09-13) — Reel not retrieved

  • Conveyance: SECURITY AGREEMENT
  • Assignor: POLYCOM, INC.; VIVU, INC.
  • Assignee: MORGAN STANLEY SENIOR FUNDING, INC. (as collateral agent)
  • Correspondent: not retrieved
  • Context: securitization — collateral grant under Polycom's 2013 credit facility (the related first-lien IP Security Agreement Supplement is Exhibit 10.1 to Polycom's 8-K, SEC accession 0001564590-13-000868). Not a transfer of title.

• 2016-09-27 — Reel not retrieved

  • Conveyance: GRANT OF SECURITY INTEREST IN PATENTS — FIRST LIEN
  • Assignor: POLYCOM, INC.
  • Assignee: MACQUARIE CAPITAL FUNDING LLC, AS COLLATERAL AGENT
  • Correspondent: not retrieved
  • Context: securitization — replacement first-lien collateral agent on Polycom's post-take-private debt.

• 2016-09-27 — Reel not retrieved

  • Conveyance: GRANT OF SECURITY INTEREST IN PATENTS — SECOND LIEN
  • Assignor: POLYCOM, INC.
  • Assignee: MACQUARIE CAPITAL FUNDING LLC, AS COLLATERAL AGENT
  • Correspondent: not retrieved
  • Context: securitization — second-lien tranche of the same collateral package.

• 2016-09-27 — Reel not retrieved

  • Conveyance: RELEASE OF SECURITY INTEREST
  • Assignor: MORGAN STANLEY SENIOR FUNDING, INC.
  • Assignee: POLYCOM, INC.; VIVU, INC.
  • Correspondent: not retrieved
  • Context: securitization unwind — release of the 2013 Morgan Stanley lien in connection with the Macquarie refinancing.

• 2018-07-03 — Reel not retrieved (two separately recorded release entries on this date)

  • Conveyance: RELEASE OF SECURITY INTEREST
  • Assignor: MACQUARIE CAPITAL FUNDING LLC
  • Assignee: POLYCOM, INC.
  • Correspondent: not retrieved
  • Context: securitization unwind — release of the 2016 first- and second-lien grants, clearing the Macquarie liens.

• 2018-07-05 — Reel not retrieved

  • Conveyance: SECURITY AGREEMENT
  • Assignor: PLANTRONICS, INC.; POLYCOM, INC.
  • Assignee: WELLS FARGO BANK, NATIONAL ASSOCIATION
  • Correspondent: not retrieved
  • Context: securitization — new collateral grant covering Polycom and its then-parent Plantronics; again a lien, not a title transfer.

• 2022-08-30 — Reel not retrieved

  • Conveyance: RELEASE OF PATENT SECURITY INTERESTS
  • Assignor: WELLS FARGO BANK, NATIONAL ASSOCIATION
  • Assignee: PLANTRONICS, INC.; POLYCOM, INC.
  • Correspondent: not retrieved
  • Context: securitization unwind — Wells Fargo lien released.

• 2023-06-22 — Reel not retrieved

  • Conveyance: NUNC PRO TUNC ASSIGNMENT (SEE DOCUMENT FOR DETAILS)
  • Assignor: POLYCOM, INC.
  • Assignee: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
  • Correspondent: not retrieved
  • Context: acquisition — outright title transfer of the Polycom patent estate to HP (operating company to operating company); nunc pro tunc language indicates the parties back-dated the assignment to an earlier effective date. This is the only true title transfer after the original inventor assignment.

(Also recorded on the patent are several foreign "Priority to" filings — AU 2012200314, EP 12152578.6, JP 2012-026497, JP 2014-057290, CN 201210027888.9, CN 201611205936.3, and US 13/970,231 — these are family/priority events, not assignments, and are excluded from the chain above.)

Assignment Center check: I was not able to confirm from Assignment Center that the above list is exhaustive (e.g., possible name-only "Change of Name" records for Polycom→Poly, or Intel/HP corporate-entity records). If Assignment Center shows no additional records, that is itself a finding — but I cannot represent that here.

Timeline diagram

timeline
    title Ownership of US 8537195
    2011 : Inventors assign to Polycom Inc
         : Application filed Feb 9
    2012 : Pre-grant publication
    2013 : Patent issued Sep 17
         : Security agreement to Morgan Stanley
    2016 : Macquarie first lien grant
         : Macquarie second lien grant
         : Morgan Stanley lien released
    2018 : Macquarie liens released
         : Security agreement to Wells Fargo
    2022 : Wells Fargo liens released
    2023 : Assigned to Hewlett Packard

NPE / troll-pattern signals

I'll research the specific patent and its cited prior art. Let me start with targeted searches.

Let me research more of the key cited references.

Prior-Art Analysis — U.S. Patent No. 8,537,195 B2

Method note. I could not run a live USPTO PatentCenter/PATENTSCOPE query within the step budget, so this analysis is grounded in the authoritative front-page citation record reproduced in the patent text you supplied (the "Citations (23)" / "References Cited" table and the "Family Cites Families (22)" table), supplemented by the Google Patents and secondary pages retrieved in the searches above. Where I did not personally open a reference's full text, I say so. I did not substitute any similar number; every identifier below is transcribed literally from the record for 8,537,195.

1. The 23 references cited on/against 8,537,195

Dates are the priority date and publication date exactly as listed by Google Patents for the '195 record. §102 relevance is keyed to the '195 filing/priority date of 2011-02-09.

2. Ranked assessment of the most relevant prior art

A. US 2011/0018960 A1 — Polycom (CP layout in a cascading conference) — priority 2006-03-01; pub. 2011-01-27. Most on-point single reference. The retrieved text discloses: continuous-presence (CP) "layouts"; a composition controller that "determines which conferee endpoints to present … and in which window the conferees should appear"; selection "can dynamically change during the conference"; and scaling of source video into CP windows. That maps to claim 1's "generate a plurality of cells / assign … one video stream to one cell," claim 2/10 ("continuous presence layout"), and claim 4/12 ("dynamically regenerating"). However, on the text retrieved it does not clearly disclose (i) attributes carried on the incoming streams driving the layout, or (ii) display-configuration information including the number of display devices of the receiving endpoint as claim 1 requires. So it is a strong §103 combination reference, not a clean §102 anticipation of claim 1. Source: https://patents.google.com/patent/US20110018960 and EP 1 830 568 A2.

B. US 8,355,040 B2 — Teliris — priority 2008-10-16; pub. 2013-01-15. Its claim 1 recites "stream IDs … where a stream ID designates a physical position in which an associated participant camera and participant display pair is located in a composite participant display," plus configuration tables keyed to room type/number of displays and a scenario manager. This is the closest prior art to the "preserve a spatial relationship between at least two of the video streams" limitation (claim 1's final clause; dependents 8/17). It is §102(e) art (filed 2008 < 2011-02-09). Still, its layout is pre-configured/scheduled and config-table-driven, which cuts against the "attributes received on the streams" element. Source: https://patents.google.com/patent/[US8355040B2](/patent/US8355040B2)/en.

C. US 2010/0333004 A1 — Tandberg Telecom — priority 2009-06-24; pub. 2010-12-30. Discloses a "Video Composing Server" that "spatially mixes video … to form a composite video signal," CP "layouts," and modifying the composite layout — the mixing/combining and spatial-mix elements of claim 1. The decisive gap: its layout change is via a user touch screen, so it fails claim 1's "automatically." §103 reference.

D. US 8,264,519 B2 — Cisco — priority 2007-03-16; pub. 2012-09-11. Telepresence endpoint with paired displays/cameras, side-by-side large screens, and a reserved display for data/non-telepresence participants — relevant to the multi-display configuration element but not to attribute-driven automatic layout.

E. US 2011/0016204 A1 — Radvision and US 2011/0205333 A1 — Wu (FECC) — both bear on the "attributes/cues" and "participant/layout selection" concepts (claims 1, 3, 5, 11, 13), but neither retrieved text shows the full claim-1 combination.

F. US 7,760,956 B2 (HP) and US 8,327,253 B2 (Shutterfly) — automatic composition of video frames/pages into a layout — the "generate cells / assign frames" concept in a non-conference context.

3. Honest §102 vs §103 bottom line

• No single cited reference appears to anticipate claim 1 or claim 9 under 35 U.S.C. §102 as issued, because each claim requires, in one reference, all of: (a) automatic layout generation; (b) driven by stream attributes; (c) plus display-configuration information including the number of display devices; (d) cells with one stream per cell; (e) mixing/combining the cell streams; and (f) preservation of a spatial relationship between at least two received streams. None of the cited references I could inspect teaches (b) and (c) together with (a).
• The strongest §102 candidates on sub-parts only are Teliris (element f, and the display-config/stream-ID concept) and Polycom '960 (elements a-partial, c-in-part, d, e). These are best characterized as the primary §103 references, optionally combined with Radvision/Wu for the attribute-cue teaching.
• Several references (e.g., #19 is the applicant's own publication; #1–#6, #15–#18) are background/peripheral and would not carry an anticipation case.

4. References noted in the specification itself and in the family (not on the front page)

The '195 specification expressly incorporates by reference:

• U.S. Pat. No. 6,912,178 B2 (Chu et al., Polycom) — "System and method for computing a location of an acoustic source" — this is the speaker-location/microphone-array foundation for the "Speaker" attribute (claims 5–7, 13–15).
• U.S. patent application Ser. No. 12/581,626 (Avishay Halavy) — "System and method for combining a plurality of video streams generated in a videoconference" — the mixer/combining foundation (claim 1/9 "mixing"/"combining").

The family-citation table additionally lists, among others, US 8,228,363 B2 (Polycom — "Method and system for conducting continuous presence conferences"), US 7,707,247 B2 (Cisco — "System and method for displaying users in a visual conference between locations"), and NO 320115 B1 / NO 329739 B1 (Tandberg — CP image generation), which are structurally relevant to the continuous-presence/layout claims but were not the front-page examiner citations.

5. Caveats

• I verified full text for only a subset of the 23 references (notably Tandberg US 2010/0333004, Polycom US 2011/0018960, Cisco US 8,264,519 / US 8,355,040, and the '195's own continuation US 9,462,227). For the remainder I relied on the title/assignee/date data in the citation record; descriptions are therefore title-level, not element-by-element.
• A §102 anticipation conclusion requires reading each reference against the claim as a whole; the "potential §102 relevance" column flags overlap, not a legal conclusion of anticipation. Nothing here is a validity opinion.
• One internal inconsistency to flag: the previously generated sections state today's date as 2026-09-29, while this task's header states April 26, 2026. This does not affect the prior-art analysis, but the two dates are not identical and should be reconciled.

I'll analyze obviousness under §103 using the prior-art references listed on the patent page. Let me first ground details on the most material references.

Let me ground the remaining key references.

Obviousness Analysis — U.S. Patent No. 8,537,195 B2 under 35 U.S.C. § 103

Building on the claim overview already generated. This section does not repeat the bibliographic summary, the plain-language claim walkthrough, or the litigation findings.

1. Governing legal framework

The application was filed February 9, 2011 with an earliest priority date of the same day, i.e., before March 16, 2013. Pre-AIA § 103(a) therefore applies, evaluated under the Graham v. John Deere framework (scope/content of prior art; differences; PHOSITA level; secondary considerations), with the flexibility mandated by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) — a claimed combination may be obvious where the elements were known, the combination was "obvious to try," or there was a design need/market pressure and a finite number of identified, predictable solutions.

One structural point matters throughout: pre-AIA § 103(c) disqualifies, for obviousness purposes, subject matter that qualifies as prior art only under § 102(e), (f), or (g) and that was commonly owned at the time the invention was made. Several of the most on-point references here are Polycom-family documents (e.g., US 2011/0018960 A1, US 8,228,363 B2, US 6,912,178 B2). A challenger relying on those under § 102(e) alone would run into § 103(c); by contrast, the Cisco and Tandberg references in the record are third-party art and carry no such defect. I flag this because it materially affects which combination a petitioner would actually plead.

PHOSITA: a person with a bachelor's degree in EE/CS (or equivalent) and roughly 3–5 years of experience in multipoint videoconferencing/telepresence MCU design, familiar with H.320/H.323/H.324, H.261/263/264, continuous-presence (CP) video mixing, and microphone-array/voice-activity speaker detection. The patent's own "Prior art keywords" — endpoint, video stream, video, layout, display — confirm the field of search.

2. The prior-art universe actually on this page

The patent lists 23 cited references and 22 family-cited references. The ones with real § 103 traction are:

Also of note: the '195 specification itself admits substantial elements are known — protocols (H.323/H.320) "can be extended to include attribute definitions," stream combination is described in incorporated US application 12/581,626, and speaker location is incorporated from US 6,912,178. Admissions in the specification about the state of the art are usable as prior-art evidence against the claims.

3. Element-by-element mapping (claim 1 / claim 9)

4. Combinations that would render the claims obvious

Combination A (primary): US 7,707,247 B2 (Cisco) + US 2010/0333004 A1 (Tandberg)

Coverage. Cisco '247 supplies automatic assignment of remotely-captured multi-camera video signals to the displays of a local site, keyed to how many displays exist and to load per display, with fixed relative display positions and an express rationale of handling sites with fewer displays than cameras. Tandberg '004 supplies the MCU/video-composing-server that mixes streams into a composite with allocated regions ("cells"), the notion of layout templates/regions, and the embeddable-MCU-in-codec teaching. Together they disclose claim 1's "generate cells → assign one stream per cell → mix/combine into an outgoing stream," and claim 9's MCU with a composing unit.

Motivation to combine. Both references are in the same field (multipoint/telepresence video), address the identical problem — placing more source streams than can be shown 1:1 onto a receiving site's displays — and their teachings are complementary rather than conflicting: '247 decides which signals go to which screen; '004 decides how multiple signals are composited within a screen when one screen must carry several. The predictable result is exactly the '195 Figure 4A behavior (4 cells on display 402, single-stream display 406). KSR recognizes this as combining known elements to achieve a predictable result.

Remaining gap. Neither reference uses per-stream attributes as the layout input, and '004's user-facing control is manual (touchscreen). This is where Combinations B/C come in.

Combination B: A + US 8,358,328 B2 (Cisco) [Speaker attribute / speaker-driven selection]

Cisco '328 generates direction-of-sound information from a microphone array and performs voice-activated selection/switching of people views for transmission. Applied to A, this supplies the "attribute … indicates that the first video stream includes an image of a first current speaker" limitation (claim 5) and the automatic speaker-promotion logic. US 6,912,178 (Polycom) is the alternative/companion teaching for locating the speaker with a mic array — and is the very technique the '195 spec incorporates by reference, which strongly supports that the speaker-attribute mechanism was known.

Motivation. '328 is expressly aimed at "dynamic deployment" and at letting a teleconference "use multiple display screens" without a fixed seating arrangement — i.e., the same automated, screen-aware speaker presentation problem. A PHOSITA automating '247/'004 would naturally adopt '328's audio-direction selection rather than VNOC manual operator monitoring, which the '195 background itself criticizes as "error prone," "costly," and slow.

Combination C: B + a per-stream attribute transport reference — US 2011/0016204 A1 (Radvision) and/or US 2006/0085479 A1 (Toshiba metadata)

To get from "MCU knows the speaker" to "attributes associated with the video streams that the layout manager reads," the record supplies Radvision's media cues associating user devices with stream signals and Toshiba's stream metadata structures with reproduction. The '195 specification itself concedes that H.323/H.320 "can be extended to include attribute definitions that may be used to label outgoing data streams," which is an admission that labeling streams with attributes for downstream rendering was conventional.

Motivation. Once the endpoint is the only node that knows which of its several cameras currently holds the speaker, attaching that fact (and camera position/role) to the outgoing stream as metadata is the ordinary, predictable way to make it available to the MCU — exactly the "finite number of identified, predictable solutions" scenario of KSR. Radvision and Toshiba supply the mechanism; the '195's own admission supplies the motivation.

Combination D: A/B/C + US 8,268,519 B2 (Cisco) for the spatial-preservation limitation

'519 teaches mapping the right camera/right screen of site A to the left camera/left screen of site B "to optimize the feeling of presence," so that gaze and left-to-right seating relationships survive transport. This directly meets claim 1's final "wherein the display layout preserves a spatial relationship between at least two of the video streams" and claims 8/17 (spatial arrangement of cells). US 7,707,247's fixed-relative-position assignment reinforces it.

Motivation. Preserving the side-by-side relationship of multi-camera streams is the core premise of telepresence and is explicitly the goal of '519; applying it to the cells of '004 is a design choice with a predictable benefit (continuous-presence realism).

Combination E (alternative primary): US 2011/0018960 A1 (Polycom) standing largely alone, plus '247

'960 arguably comes closest to the whole concept: an MCU-resident controller that automatically and dynamically determines which conferee and which window of a CP layout, based on audio energy. Combined with '247's display-count/assignment logic, only the "attributes" formalism is arguably missing. But '960 is Polycom-owned; if it is relied on only under § 102(e), pre-AIA § 103(c) may disqualify it (common ownership at the time of invention). A petitioner would therefore prefer Combinations A–D, which rest on Cisco/Tandberg third-party art.

5. Dependent claims

No dependent claim adds a limitation that appears to escape these combinations.

6. Where an obviousness case is weakest (non-obviousness arguments to expect)

1. No single reference, and arguably no combination, expressly uses "attributes on received streams" as the input to automatic layout generation. The strongest art splits the two halves: '247, '519, '328 know about multiple streams/speakers but not attribute signaling; Radvision/Toshiba know about stream metadata but not layout. Patentee will argue the synthesis — an attribute-driven, configuration-aware layout manager — was the inventive insight, and that the reference to "attributes" is a specific, unconventional data model rather than a generic label.
2. Teaching away / different purpose. '247's assignment is a switching model ("displaying each selected video signal"), and '004's layout is user-driven (touchscreen) — neither is "automatic." Patentee will argue '004 teaches away from automation by emphasizing user control; a petitioner must rebut with '960/'328 and the '195 background's own critique of manual VNOC operation (which is simultaneously an admission and a motivation argument).
3. '519/'247 preserve positions in a point-to-point/per-display sense, whereas the '195 claims require spatial preservation across a cell structure in a multipoint mix. That is a real, if narrow, gap — best closed by combining '519 (spatial premise) + '004 (cells).
4. § 103(c) exposure for the Polycom-family references (Combination E), which removes some of the most convenient art from the toolbox.
5. Secondary considerations (if any evidence of record): commercial success of Polycom telepresence products, industry adoption, and the IETF "Framework for Telepresence Multi-Streams" (draft-ietf-clue-framework) IPR disclosure (https://datatracker.ietf.org/ipr/2265/) could be argued as nexus evidence of non-obviousness — though the disclosure is dated December 5, 2013, i.e., after the 2011 filing, so it is not prior art itself and would carry weight only as post-hoc industry-recognition evidence.

7. Bottom line

• A strong § 103 case exists; the most viable formulation is US 7,707,247 B2 (Cisco) + US 2010/0333004 A1 (Tandberg) + US 8,358,328 B2 and/or US 6,912,178 for the speaker attribute + US 2011/0016204 A1 (Radvision) for attribute transport + US 8,268,519 B2 (Cisco) for spatial preservation.
• Motivation is supplied by (i) the shared field and shared problem (multi-camera/multi-site video on fewer screens), (ii) the complementary roles of the references (assignment vs. compositing vs. speaker detection vs. metadata), (iii) the patent's own admission that VNOC-manual operation was error-prone and costly, and that H.323/H.320 attribute labeling and stream mixing were known.
• Weak spots: the combination must affirmatively bridge "attribute-carrying streams" → "attribute-driven automatic layout," and must overcome '004's manual-control teaching. The '195 examiner had much of this art of record, so a real-world challenge would likely hinge on whether the Polycom-family art is § 103(c)-disqualified and on how broadly "attributes" is construed.
• Confidence: moderate that claim 1 and claim 9 are obvious over the above combinations; lower for a single-reference anticipation (none found). This is a paper analysis only — it applies an ordinary-meaning reading of the claim terms, does not perform formal claim construction, and is not a legal opinion.

Note on identifiers: all reference numbers above are quoted exactly as they appear on the patent page; I did not auto-correct any number. Where I describe a reference only by its listed title (e.g., NO 320115 B1, JP 2009-239762 A) I have not independently retrieved its full text, and that characterization should be verified before being relied on in a filing.