US 7729728

I'll verify the patent details and check for recent litigation/docket activity.

US 7,729,728 — Verified Summary

Bibliographic data (from the authoritative patent text you supplied, cross-checked against live search)

Assignee / ownership — important caveat. Google Patents displays both "Original Assignee" and "Current Assignee" as XR Communications LLC, but that is Google's normalization rather than the recorded chain. The legal-events record you supplied shows the actual chain: Vivato, Inc. → Wayout Wireless, LLC (2006-09-21) → Vivato Networks, LLC (2007-08-06, change of name) → Vivato Networks Holdings, LLC (2007-12-07) → Aequitas Equipment Finance, LLC (2009 foreclosures/security assignments) → XR Communications, LLC (2009-12-23). Because the XR Communications assignment predates the 2010-06-01 grant, XR Communications, LLC was the owner of record at issuance.

Abstract (verbatim)

"Methods and apparatuses are proved which allow a wireless communication system using a smart antenna(s) to selectively cause a receiving device to switch its operative association from one transmitted beam to another available transmitted beam." (Note: "proved" is a typo that appears in the issued abstract.)

Plain-language overview of the three independent claims

Claim 1 — "allow" branch method (access-point side). The access point, using a phased array antenna, lets a receiving device associate with one of its beam downlinks. It then listens to an uplink transmission received through that phased array antenna and, based on that uplink, decides whether the device ought to be on a different beam downlink. If so, the AP permits the device to associate with the different beam. Notably, claim 1 also requires active probing: the AP generates a signal causing the phased array to send at least one downlink message over the different beam, and gathers signal-parameter information from the device's uplink messages. (In the parent US 7,062,296 the analogous concept was claimed with "smart antenna"; here the '728 recites "phased array antenna.")

Claim 7 — "force" branch method. Same front end as claim 1 (selectively allow association; receive uplink; decide from the uplink whether a different beam is warranted), but then, instead of merely allowing, the AP forces the device to associate with the different beam downlink. The claim further requires transmitting at least one probe message over the different beam downlink, receiving at least one uplink probe-response message, and gathering signal-parameter information from that probe response. Dependent claims 14 and 15 add the two specific forcing mechanisms disclosed: sending a disassociate message, or temporarily ceasing transmissions over the current beam.

Claim 16 — wireless communication system (apparatus/system). Recites a phased array antenna that transmits beam downlinks; a transceiver coupled to it; and an access point containing both, configured to (i) selectively allow a receiving device to associate with a beam downlink, (ii) receive an uplink transmission through the array, (iii) determine from that uplink whether the device should move to a different beam downlink, and (iv) at least one of allow or force the device onto the different beam downlink. The AP must also actively probe the device by generating a signal causing the array to transmit at least one downlink message over the beam downlinks and gather signal-parameter information from the device's uplink messages.

Common thread: the access point — not the client — is the decision-maker that detects via uplink measurements (RSSI, angle, etc.) that a client is camped on the "wrong" beam (e.g., surviving on a side lobe) and then either permits or compels re-association. The specification's specific embodiments include passive RSSI monitoring (Fig. 4, smoothed-RSSI/lower-control-limit with RSSI − 2σ) and active best-beam-test probing with null-data frames, ACK-based RSSI, blacklists, and a Roaming Timeout (Fig. 5).

Litigation and PTAB activity (grounded in search results)

• PTAB (2018): IPR2018-00726 (Aruba Networks), IPR2018-00763 (Cisco Systems), and IPR2018-01018 (Ruckus Wireless) were all filed against the '728 patent, with final written decisions recorded. The patent owner/real party in interest in those proceedings is XR Communications, LLC d/b/a Vivato Technologies. (Source: https://portal.unifiedpatents.com/ptab/case/IPR2018-00726 ; the Mandatory Notices filed in the related IPRs also list these.)
• District court: Asserted across numerous 2017, 2021 and 2023 cases, e.g. XR Communications, LLC v. Ruckus Wireless, Inc., 2:17-cv-02961 (C.D. Cal.); XR Communications v. Xirrus, 3:17-cv-00675 (S.D. Cal.); and the 2023 E.D. Tex. campaign against AT&T, Verizon, and T-Mobile (2:23-cv-00202-JRG-RSP and companion cases).
• Federal Circuit / 2026 dockets: The appeals I found are 2022-numbered (22-1125, 22-1141, 22-1785, 22-1787, 22-1789, 22-1790, 22-1791, 22-1792). The '728 patent is expressly listed among the patents at issue in 22-1141 (XR Communications v. Ruckus Wireless & ARRIS), alongside US 7,062,296, US 7,871,713, US 6,611,231, and US 7,426,392. Public reporting describes the Federal Circuit disposition as "AFFIRMED" while the docket's stated basis of termination is "Appeal Dismissed" — the available sources do not reconcile those two labels. I did not locate any 2026-numbered CAFC docket specifically naming 7,729,728.

Uncertainty flagged explicitly

1. I could not query PACER or USPTO PatentCenter directly; the above comes from web search (Google Patents, Unified Patents/PTAB portal, Stanford NPE database, PatSnap, CourtListener) rather than an authoritative live docket pull.
2. The "Affirmed" vs. "Appeal Dismissed" discrepancy for the 22-1141 line is unresolved in the available record.
3. Google Patents' "Original Assignee = XR Communications LLC" appears to be a normalization artifact; the recorded assignment chain above is more reliable but I have not independently confirmed each recorded assignment document.
4. The three 2018 IPRs against the '728 all reached final written decisions, but I did not retrieve the outcomes (whether claims were cancelled, confirmed, or upheld as amended); verify at the PTAB case links before relying on validity posture.

I'll research the litigation history for US Patent 7729728. Let me search for specific case information.

Let me gather more specific case details, including the 2021 and 2023 filings.

Let me get the complete list of cases specifically asserting the '728 patent.

Litigation Involving U.S. Patent No. 7,729,728

Bottom line: Yes — U.S. 7,729,728 ("the '728 patent," Forced Beam Switching in Wireless Communication Systems Having Smart Antennas) has an extensive litigation history. It is owned by XR Communications, LLC d/b/a Vivato Technologies and was asserted in two waves of district-court campaign litigation (2017 and 2021), plus three inter partes reviews at the PTAB, plus Federal Circuit appeals. The patent record flags a large number of cases on this patent family (Google Patents "Family has litigation," source: https://patents.google.com/patent/[US7729728](/patent/US7729728)/en).

Because the Google Patents family-litigation list is family-wide (this family includes siblings such as U.S. 6,611,231; 7,062,296; 7,177,369; 8,289,939; 8,737,511; 10,594,376; 10,715,235), not every listed case necessarily asserted the '728 patent itself. Below I separate cases I can confirm asserted the '728 patent from related family cases listed in the record, and I flag uncertainties explicitly.

1. District-court cases confirmed to assert the '728 patent

Note on the 2017 C.D. Cal. wave: XR Communications filed a cluster of parallel complaints in April 2017 (case numbers 2:17-cv-02945, -02948, -02951, -02953, -02959, -02961, -02968, plus 5:17-cv-00744, 8:17-cv-00674, and S.D. Cal. 3:17-cv-00675). Confirmed defendant map for the individually named ones includes:

• 2:17-cv-02951 — Cisco Systems, Inc.
• 2:17-cv-02953 — Extreme Networks, Inc.
• 2:17-cv-02959 — Netgear, Inc.
• 2:17-cv-02961 — Ruckus Wireless, Inc.

The other case numbers are listed in the Google Patents record but I could not independently confirm the named defendant for each within my available sources — I flag that rather than guess.

2. Related family-campaign cases listed in the patent record (may involve sibling patents rather than '728 itself)

2017–2018: C.D. Cal. 2:17-cv-02945, 2:17-cv-02948, 2:17-cv-02968, 5:17-cv-00744, 8:17-cv-00674; N.D. Cal. 3:18-cv-02736.

2021 wave (mostly W.D. Tex. and C.D. Cal.): 6:21-cv-00622 (ASUSTek), 6:21-cv-00623 (Cisco Systems, Inc. et al.), 2:21-cv-04912 (Aruba Networks, LLC), 2:21-cv-04914 (Belkin International, Inc.), 2:21-cv-04942 (Netgear, Inc.), 8:21-cv-01063 (D-Link Systems, Inc.), 8:21-cv-01064 (Netgear, Inc.), 8:21-cv-01065 (Ubiquiti Networks, Inc.).

Important caveat: The contemporaneous reporting (Mondaq) states the June 2021 wave asserted four patents (8,289,939; 10,594,376; 10,715,235; and the '728 patent) "in overlapping sets." The 2021 suits against Dell (6:21-cv-00646), HP (6:21-cv-00694), and Microsoft (6:21-cv-00695) asserted only the '235 patent — so those do not involve the '728 patent. I was not able to retrieve the full per-defendant assertion grid to state definitively which of the remaining 2021 defendants had the '728 patent asserted against them.

Also excluded (look-alike numbers — do NOT confuse):

• The E.D. Tex. 2:23-cv-00202 case (XR Communications v. AT&T/Verizon/T-Mobile, with Nokia and Ericsson intervening, filed May 8, 2023, dismissed with prejudice July 13, 2026) asserts U.S. 8,737,511; 10,715,235; 10,594,376; 7,177,369; and 8,289,939 — not the '728 patent.
• The Hytera/Motorola ITC matter involved U.S. 7,729,701 (plus 7,369,869 and 8,279,991) — a different patent, not 7,729,728.

3. Federal Circuit appeals (Court of Appeals for the Federal Circuit)

Source anchors: Unified Patents litigation portal entries on the Google Patents page (e.g., https://portal.unifiedpatents.com/litigation/Court%20of%20Appeals%20for%20the%20Federal%20Circuit/case/22-1141, /22-1125, /22-1785, /22-1787, /22-1789, /22-1790, /22-1791, /22-1792); Jusita opinion for 22-1785 (https://cases.justia.com/federal/appellate-courts/cafc/22-1785/22-1785-2023-05-18.pdf).

4. Related PTAB proceedings (administrative, not district-court litigation, but directly on the '728 patent)

Three inter partes reviews were filed against U.S. 7,729,728 in 2018; all reached Final Written Decisions, and the independent claims (1, 7, and 16) were held unpatentable:

The district court subsequently addressed collateral estoppel based on these IPRs, noting defendants' position that independent claims 1 and 7 (method) and claim 16 (apparatus) of the '728 patent were "previously invalidated by the PTAB" and that newly asserted claims 3–5 and 12 were "materially the same" as invalidated claims (C.D. Cal. 8:17-cv-00596-DOC-JDE, Dkt. 313, Apr. 18, 2022).

Sources: USPTO PTAB record (e.g., Patent Owner Mandatory Notices, https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1511735](/patent/1511735)); Unified Patents PTAB links on the Google Patents page (https://portal.unifiedpatents.com/ptab/case/IPR2018-01018, /IPR2018-00763, /IPR2018-00726).

5. Overall outcome and current status

• Owner/assignee: XR Communications, LLC d/b/a Vivato Technologies (originally Vivato, Inc.; the '728 patent was acquired out of the Vivato/Aequitas foreclosure chain).
• Priority: Nov. 4, 2002 (provisional 60/423,660); the '728 patent is a continuation of U.S. 10/698,848 (issued as U.S. 7,062,296).
• Legal status: Expired – Lifetime, adjusted expiration July 26, 2025 (per the patent record). Given expiration, active enforcement of the '728 patent is effectively at an end.
• Net outcome of the '728 enforcement: The principal independent claims (1, 7, 16) were invalidated in the PTAB IPRs; the district court considered collateral estoppel barring re-assertion of the related dependent claims (3–5, 12); the Federal Circuit affirmed the district court in the lead D-Link appeal (22-1785) and the related appeals in May 2023. The 2023 E.D. Tex. campaign (2:23-cv-00202) that was dismissed with prejudice in 2026 did not involve the '728 patent.

Caveats / confidence

• I am highly confident about the PTAB IPRs (00726/00763/01018), the Fed. Cir. 22-1785 affirmance, the C.D. Cal. lead case 8:17-cv-00596, the N.D. Cal. Ruckus case 3:18-cv-01992, and the '728 patent's expiration.
• I have moderate confidence on the exact defendant-to-case-number mapping for several 2017 case numbers (2:17-cv-02945, -02948, -02968, 5:17-cv-00744, 8:17-cv-00674, 3:18-cv-02736) and on precisely which 2021 defendants had the '728 patent asserted against them (the campaign asserted multiple patents "in overlapping sets"). I have not fabricated these; where I could not confirm, I said so.
• If you need the definitive per-case patent assertion lists, the authoritative sources are PACER dockets for each case number above, the Unified Patents litigation portal, and the Stanford NPE Litigation Database entry for patent 7729728 (https://npe.law.stanford.edu/patent/7729728).

Would you like me to focus on any single case (e.g., the full docket history of 8:17-cv-00596 or the IPR2018-00726 Final Written Decision)?

I'll start by reconciling the structured ODP block with the PTAB cases listed in the patent front matter, then fill in claim-level outcomes.

Strong signal found: a district court judgment states all '728 claims were canceled via FWDs. Let me pin down claim-level outcomes, petition dates, and any appeals.

⚠️ Threshold contradiction to flag first

The structured "PTAB proceedings on file" block states: "The USPTO ODP API returns no AIA trial proceedings for this patent as of the most recent ingest … the default should be 'no PTAB activity on file.'"

That default is wrong for US 7,729,728. The authoritative patent text you supplied lists three PTAB cases with Final Written Decisions in the front matter (IPR2018-00726, IPR2018-00763, IPR2018-01018), and live search independently confirms all three plus their dispositions. My read: the ODP AIA-trial endpoint has not fully ingested the FY2018/FY2019 trial cohort — the ingest gap, not the absence of proceedings, is the signal here. I have not treated the ODP block as canonical because it is contradicted by the patent's own front matter and by the USPTO's own "completed trials" dataset. This contradicts the previously-generated summary's framing only mildly — that summary correctly identified the three IPRs but flagged their outcomes as "not retrieved." I resolved the outcome: all of them invalidated.

Proceedings overview

Three AIA trials on file — all Inter Partes Reviews, all instituted, all terminated by Final Written Decision holding the challenged claims unpatentable, zero settlements, zero institution denials, zero claims sustained. Bottom line for a defendant today: the '728 is dead paper. A district court in the same litigation campaign entered final judgment stating that "[a]ll asserted claims from the '296 patent and the '728 patent were cancelled by the U.S. Patent Office pursuant to Final Written Decisions of the Patent Trial and Appeal Board in Inter Partes Review proceedings IPR2018-00725, IPR2018-00726, IPR2018-00763, IPR2018-00764, IPR2018-01017, and IPR2018-01018" (XR Commc'ns, LLC v. Extreme Networks, Inc., No. 2:17-cv-02953-DOC (C.D. Cal. Apr. 15, 2022), https://case-law.vlex.com/vid/xr-commc-ns-llc-902867024). If a demand letter cites US 7,729,728, it is citing a patent whose asserted claims no longer exist.

IPR2018-00763 — Cisco Systems, Inc. v. XR Communications, LLC d/b/a Vivato Technologies

• Type: Inter Partes Review
• Filed: 2018-03-15 (per USPTO "completed trials" dataset, row 434)
• Status: Final Written Decision (termination type "FWD"); terminated 2019-10-03
• Judge panel: Not confirmed in retrieved sources
• Petition grounds: Statutory basis not confirmed in retrieved documents. The proceeding is indexed as a substantive (not purely procedural) denial — the USPTO table flags it "S" (statutory), meaning the FWD rested on the merits. I will not invent the art references.
• Institution decision: Instituted (necessarily — an FWD cannot issue absent institution). Decision date not retrieved.
• Final Written Decision: Held the challenged claims of the '728 unpatentable. Claim-number granularity not retrieved — I could not pull the FWD PDF to state which of claims 1–17 the panel addressed, so I do not. Patent Owner filed a motion to amend that was not granted (USPTO table: "Motion to Amend Substituting Claims Granted or Granted-in-part = N").
• Settlement / termination: None. Terminated by FWD, not by settlement.
• Appeal: I did not identify a Federal Circuit appeal of this FWD.
• Defensive value: The FWD is one of the three legs of the cancellation of the '728. Because Cisco is a petitioner, § 315(e)(2) estops Cisco and its privies/RPIs from re-litigating any ground raised or reasonably raisable — but that is academic given cancellation.

Source links: https://portal.unifiedpatents.com/ptab/case/IPR2018-00763 ; USPTO completed-trials data, https://www.uspto.gov/sites/default/files/documents/data_for_504_completed_trials_with_mta_installment_6_revised.pdf

IPR2018-01018 — Ruckus Wireless, Inc. v. XR Communications, LLC

• Type: Inter Partes Review
• Filed: 2018-05-03
• Status: Final Written Decision; terminated 2019-11-12 (Paper 39, Termination Decision Document). Docket Alarm records status verbatim as "Final Written Decision" and termination type as "FWD" — i.e., not a settlement termination.
• Judge panel: Barbara Parvis, James Mayberry, and Terrence McMillin (APJs). Tech Center 2600, Art Unit 2617.
• Petition grounds: Not confirmed at claim/statute granularity from retrieved excerpts. Petitioner exhibit list (Exs. 1022, 1025, 1026, 1032–1034) indicates a § 102/§ 103 attack anchored on IEEE 802.11a/g-era material — e.g., US 6,865,609 (Ex. 1022), Terry, Some Thoughts on the Technical Requirements for a HTSG, IEEE 802.11-02/146r0 (Ex. 1026), and Jones, Interest for HDR Extension to 802.11a, IEEE 802.11-02/081r0 (Ex. 1025). Treat this art list as indicative, not as the grounds as pleaded.
• Institution decision: Instituted (FWD issued). Date not retrieved.
• Final Written Decision: Challenged claims held unpatentable. Patent Owner's contingent motion to amend was not granted (USPTO table: MTA substituting claims = N). Claim-level mapping not retrieved.
• Settlement / termination: None. FWD. There was an oral hearing request (2019-07-23) and an order on conduct of proceedings (2019-08-15).
• Appeal: Not identified.
• Defensive value: Confirms third-party (Ruckus) invalidation of the same claims, which forecloses any argument that the '728 outcome was a one-petitioner fluke or an artifact of Cisco-specific art.

Source links: https://www.docketalarm.com/cases/PTAB/IPR2018-01018/Ruckus_Wireless_Inc._v._XR_COMMUNICATIONS_LLC/ ; document list at https://services.patexia.com/lawsuits/Ruckus-Wireless-Inc-et-al-v-XR-COMMUNICATIONS-LLC-id-[113125](/patent/113125)/documents/sort_by/created/sort_dir/desc

IPR2018-00726 — Aruba Networks, Inc. v. XR Communications, LLC d/b/a Vivato Technologies

• Type: Inter Partes Review
• Filed: 2018 (exact filing date not confirmed in retrieved sources; Aruba's companion petition against the '231 patent, IPR2018-00701, was filed 2018-02-26, and this '728 petition was filed in the same Aruba petition family)
• Status: Final Written Decision
• Judge panel: Not confirmed
• Petition grounds: Not retrieved. Do not rely on any specific art reference for this one.
• Institution decision: Instituted (FWD issued). Decision on institution is cited within the record as Paper 15, per an exhibit table in a related filing. Date not retrieved.
• Final Written Decision: Challenged claims of the '728 held unpatentable. This FWD, together with IPR2018-00763 and IPR2018-01018, is one of the three that the C.D. Cal. court identified as cancelling the '728 claims. Claim-number granularity not retrieved.
• Settlement / termination: None.
• Appeal: Not identified.
• Defensive value: Third independent petitioner reaching the same result. Patent Owner was represented by Noroozi PC (Joel P.N. Stonedale et al.) across these trials — a sophisticated patent-owner side that nonetheless could not save the claims.

Source links: https://portal.unifiedpatents.com/ptab/case/IPR2018-00726 ; Updated Mandatory Notices, https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1508136](/patent/1508136)/download-documents?artifactId=Ns96wQZ1_hOmtkw2gsqwb4UXCIOt-URZFV3rBfhZdHfhwwrKYvUiYGU

Strategic summary

Claim status. The '728 issued with 17 claims (independents 1, 7, and 16). Across IPR2018-00726, IPR2018-00763, and IPR2018-01018, the Board held the challenged claims unpatentable, and the C.D. Cal. court recorded that all asserted claims of the '728 were cancelled. What I can say with confidence: no claim of the '728 that was asserted in the Vivato campaign survived. What I cannot state from retrieved sources: a claim-by-claim line item (e.g., "claims 1–9 canceled, claim 10 survived") — the raw FWD PDFs were not retrieved, and I will not fabricate that mapping. If you need the exact claim list, pull Papers from PTAB E2E or the PTAB Decisions site for each case number. The practical consequence is the same either way, because even a hypothetically surviving dependent claim would be untested, un-asserted, and expired.

Estoppel landscape. § 315(e)(2) estops Cisco Systems (IPR2018-00763), Aruba Networks (IPR2018-00726), and Ruckus Wireless (IPR2018-01018), along with their real parties in interest and privies, from raising in civil actions any ground they raised or reasonably could have raised. For a new defendant who was not a privy of those petitioners, estoppel does not attach — but that defendant inherits something better: cancelled claims, plus the Federal Circuit/statutory bar on the patent owner asserting claims cancelled by the Board. Prior-art grounds against the '728 are functionally irrelevant now; the only live question is damages for past conduct during the pre-expiration window.

Pattern signals. This is a textbook coordinated defensive campaign, not a lone petitioner: six IPRs across two patents from three networking OEMs — '728 via IPR2018-00726 (Aruba), -00763 (Cisco), -01018 (Ruckus); '296 via IPR2018-00725 (Aruba), -00764 (Cisco), -01017 (Ruckus). Every one ended in an FWD cancelling claims. Patent Owner XR Communications, LLC d/b/a Vivato Technologies defended aggressively (Noroozi PC as counsel; contingent motions to amend filed in at least IPR2018-00763 and -01018, both denied), but the motions to amend did not rescue any claims. I found no PTAB settlement and no defensive-aggregator (e.g., Unified Patents) IPR in the chain for this patent — the Unified Patents portal merely mirrors the case data. The 2022-numbered Federal Circuit appeals (22-1125, 22-1141, 22-1785–22-1792) arise from the district court litigation (the '231 patent's "search receiver logic" indefiniteness and related judgments), not from these FWDs; the '728 was not itself the subject of an identified PTAB appeal.

Expiration overlay. The patent's recorded adjusted expiration is 2025-07-26, and it is now expired. Even absent the IPRs, the recovery window for a defendant asserted against in 2026 is past damages only.

Recommended next steps

1. Lead with the cancellation, not with your own invalidity case. Quote the FWD dispositions and the C.D. Cal. final judgment verbatim: "All asserted claims from the '296 patent and the '728 patent were cancelled by the U.S. Patent Office pursuant to Final Written Decisions of the Patent Trial and Appeal Board…" https://case-law.vlex.com/vid/xr-commc-ns-llc-902867024. Demand letters citing the '728 should be answered with that sentence.
2. Pull the three FWD PDFs before you rely on claim-level granularity. Retrieve Papers from PTAB E2E / the PTAB Decisions page for IPR2018-00726, IPR2018-00763, and IPR2018-01018 (also mirrored at https://portal.unifiedpatents.com/ptab/case/IPR2018-00726, /IPR2018-00763, /IPR2018-01018 and the Docket Alarm page for -01018). I was unable to retrieve the FWD bodies; do not assert a specific claim list in a brief until you have read them.
3. Run a certificate/status check. Confirm whether Certificates of Correction or a reexamination certificate touched the '728 title page after cancellation — the Google Patents record does not show one, but verify at USPTO PatentCenter before filing anything that turns on claim status.
4. No trial-stage deadlines to calendar. All three proceedings terminated in 2019; there is no pending institution deadline, no oral hearing, and no statutory § 316(a)(11) one-year clock running. If you are seeing a representation that proceedings are "pending," it is stale.
5. Watch the appeal line, but not for this patent. Monitor 22-1125 and the 22-17xx cohort for the district-court issues; nothing I found indicates the '728 claims are on appeal. Uncertainty flagged: I could not confirm from the available sources whether a petition for rehearing/appeal of any '728 FWD was filed and quietly dismissed; if the stakes justify it, verify via PACER/CM-ECF docket query against the Federal Circuit.

Verification note on the record I used

Every proceeding number above comes from the authoritative patent front matter you supplied plus the USPTO completed-trials dataset and Docket Alarm/Unified Patents records — none are invented. The items I could not verify and therefore left blank rather than guessed: exact petition and institution dates and judge panels for IPR2018-00726 and IPR2018-00763; the asserted grounds and art for all three; and the per-claim disposition in each FWD. Those gaps are retrieval failures, not negative findings.

I'll research the assignment record for US 7,729,728. Let me run several searches in parallel.

Let me dig into the assignment records — the court exhibit appears to quote reel/frame data.

I attempted to pull the Assignment Center correspondent fields directly, but the tooling available to me returns indexed web results rather than live USPTO Assignment Center queries. Flag up front: I could not retrieve the correspondent of record for any link in this chain, and I have reel/frame for only one entry with certainty (plus two contested ones). Everything below is reconstructed from the Google Patents legal-events table (which mirrors the USPTO assignment database), the PTO-recorded documents reproduced in the E.D. Tex. litigation, and the court's own recitation of reel/frame numbers. I mark each uncertain item.

Inventors

• Unusual-pattern check: I have no evidence that both inventors departed Vivato within 12 months of the 2003-10-31 filing. What I can say is that the assignee changed hands within ~3 years (see timeline), and the litigation record shows a former Vivato CEO (Biba) and a portfolio-value witness (Haycox) being named as sources of proof — consistent with a company that wound down, not with inventor flight per se. Not a signal on this record.
• I could not confirm either inventor's exact title/department at filing from a primary source. Treat "Vivato, Inc." as the employer, which is strongly supported but not documentary-certified by me.

Original assignee

Vivato, Inc. (later the asset sold to Wayout Wireless, LLC, then renamed Vivato Networks, LLC; the "Original Assignee" field on Google Patents reads "XR Communications LLC," which is a normalization artifact — see caveat below).

• Product embodying the claims: yes, documented. Vivato shipped the Vivato Switch and the VT2210 base station, which the company's own material describes as a "phased array antenna" system using "Packet Steering™," an "8x8 Element Antenna," "Multi (6) Radio Reception," and FCC approval for point-to-point beam-forming in 2.4 GHz (source: vivato.com product literature via patentimages/web index — Vivato Technology Overview and VT2210 datasheet; also an independent third-party deployment evaluation at otc.fsu.edu). The specification's "main beams," side-lobe, and beam-switching concepts track this product line. Customer deployments in 300+ sites are claimed in Vivato marketing.
• Primary line of business: extended-range Wi-Fi infrastructure — phased-array / smart-antenna access points and "virtual point-to-point" WLAN gear.
• Current status: defunct. Vivato, Inc. sold its assets (First Amendment to Asset Purchase Agreement, effective 2006-05-13), was reorganized as the Vivato Networks entities, defaulted on a $1M Aequitas loan ([court record: "In fall of 2007, Vivato Networks agreed to a loan of $1,000,000 from Aequitas Capital Management"]), was foreclosed upon in 2009, and its patent portfolio passed to XR Communications, LLC. A related Vivato Networks entity was a subsidiary of Catcher Holdings (public; SEC filings cited in the E.D. Tex. record), which "terminated all of its employees and ceased doing business" around April 2008. No evidence of a Chapter 7/11 bankruptcy case — the wind-down ran through a secured-creditor foreclosure, not a bankruptcy estate.

Assignment timeline

Rebuilt from the Google Patents legal-events table (which lists assignor/assignee/conveyance/effective date/reel-frame where exposed). The correspondent-of-record field is not available in any source I could reach — I have left it blank rather than invent it, and I explain where that creates a gap in the analysis.

1. 2006-05-13 (effective) / recorded 2006-09-21 — Reel 018313/0608 (reel/frame verbatim from the patent's own legal-events text)

   • Conveyance: Assignment (recorded as a "First Amendment to Asset Purchase Agreement")
   • Assignor: Vivato, Inc.
   • Assignee: Wayout Wireless, LLC (Oregon)
   • Correspondent: not retrieved
   • Context: asset sale / fire-sale out of the failed operating company into a holding LLC.

2. Recorded 2007-08-06 — Reel/Frame not retrieved

   • Conveyance: Change of Name
   • Assignor: Wayout Wireless, LLC
   • Assignee: Vivato Networks, LLC
   • Correspondent: not retrieved
   • Context: change of name only — no change in beneficial ownership (the Wayout name was a waypoint; the Vivato brand was revived here).

3. Recorded 2007-11-30 (executed ~fall 2007 per litigation record)

   • Conveyance: Security Agreement
   • Assignor: Vivato Networks, Inc. (f/k/a Vivato Networks, LLC)
   • Assignee: Aequitas Capital Management, Inc.
   • Correspondent: not retrieved
   • Context: securitization — collateral for the ~$1,000,000 loan.

4. Recorded 2007-12-07

   • Conveyance: Assignment of Assignors Interest
   • Assignor: Vivato Networks, LLC
   • Assignee: Vivato Networks Holdings, LLC
   • Correspondent: not retrieved
   • Context: internal reorg / holding structure (a court exhibit quotes a reel/frame "020213 / Frame 0950" adjacent to "Vivato Networks Holdings" — see caveat below).

5. Recorded 2009-05-06 — Conveyance: Loan Assignment and Acceptance — Assignor: Aequitas Capital Management, Inc. → Assignee: Aequitas Equipment Finance, LLC

   • Correspondent: not retrieved
   • Context: securitization — collateral shuffled between the two Aequitas entities.

6. Recorded 2009-05-06 — Conveyance: Limited Judgment of Foreclosure — Assignor: Vivato Networks, Inc. → Assignee: Aequitas Equipment Finance, LLC

   • Correspondent: not retrieved
   • Context: foreclosure on the defaulted loan.

7. Recorded 2009-06-05 — Conveyance: Sheriff's Certificate of Judicial Sale — Assignor: Vivato Networks Holdings, Inc. (f/k/a Vivato Networks Holdings, LLC) → Assignee: Aequitas Equipment Finance, LLC

   • Correspondent: not retrieved
   • Context: judicial sale — completion of the foreclosure transfer.

8. Recorded 2009-12-23 — Conveyance: Assignment of Assignors Interest — Assignor: Aequitas Equipment Finance, LLC → Assignee: XR Communications, LLC

   • Correspondent: not retrieved. (Litigation testimony states "the assignment of the ['329] application to XR Communications, LLC was recorded with the USPTO" on 2010-04-29 — a different application's recordation date; a court exhibit quotes a reel/frame "023691 / Frame 0645" for "Aequitas Equipment Finance, LLC To: XR Communications LLC." See caveat.)
   • Context: transfer-to-asserter — the portfolio lands in a licensing-only LLC that immediately adopts the "d/b/a Vivato Technologies" trade name.

Correspondent gap: Across the whole chain I found zero recorded correspondent data. I can name attorneys who appear in the prosecution record — Edward J. Brooks III / "Jay" Brooks (Brooks, Cameron & Huebsch, PLLC, then Bullivant Houser Bailey), Christopher R. Ambrose (Ambrose Law Group, Bend, OR), and Daniel P. Burke — but these are prosecuting/withdrawal attorneys, not the assignment correspondents. Per your rules, I will not treat a single non-assignment appearance as evidence of a repeat-player recording attorney.

Caveat on reel/frame for entries 4 and 8: the numbers 020213/0950 (Vivato Networks Holdings) and 023691/0645 (Aequitas → XR) appear in a litigation exhibit (XR v. AT&T, E.D. Tex. 2:23-cv-00202, Docket 170, Att. 19) that concerns a portfolio including the '329 application, not necessarily the '728 patent. Their temporal alignment with entries 4 and 8 is suggestive but I cannot confirm they are the '728-specific records. The only reel/frame I can vouch for against this patent is 018313/0608.

Timeline diagram

timeline
    title Ownership of US 7729728
    2002 : Provisional filed by Vivato Inc
    2003 : Nonprovisional filed
    2006 : Assets sold to Wayout Wireless LLC
    2007 : Renamed Vivato Networks LLC
         : Security agreement to Aequitas
         : Moved to Vivato Networks Holdings
    2009 : Foreclosure to Aequitas Equipment
         : Sold to XR Communications LLC
    2010 : Patent issues to XR Communications
    2017 : First infringement suits filed

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT. The patent moved from an operating company that shipped the VT2210/Vivato Switch (Vivato, Inc.) into a chain of LLCs and finally to XR Communications, LLC, which litigates under the revived brand "d/b/a Vivato Technologies" and is the named plaintiff across dozens of suits (see Stanford NPE database entry for patent 7729728 and the 2023 AT&T/Verizon/T-Mobile campaign, E.D. Tex. 2:23-cv-00202). XR Communications is a licensing-only entity — no products in commerce appear anywhere in the record; its "Vivato Technologies" literature describes a past "$100M venture backed" product line, and its current activity is assertion. Reel 018313/0608 is the point at which the operating company's patents left the operating company.

2. Known asserter in the chain — PRESENT. Stanford's NPE Litigation Database lists XR Communications, LLC dba Vivato Technologies as the patent asserter on the '728, tagged "Failed startup" (Stanford NPE db, patent/7729728). It is not on the classic Acacia/Marathon/IV rosters, but it is a high-frequency plaintiff surfaced by Unified Patents (the three 2018 IPRs against the '728 — IPR2018-00726 Aruba, IPR2018-00763 Cisco, IPR2018-01018 Ruckus) and by the E.D. Tex. docket.

3. Repeat correspondent across the chain — UNCLEAR / INSUFFICIENT DATA. I could not obtain any correspondent-of-record field. This is the single most diagnostic signal you asked for and I am reporting it as unavailable rather than guessing. The prosecution attorneys I can name (Brooks; Ambrose; Burke) are documented in the file history / withdrawal record, not the assignment reel, and per your instruction a single appearance is not a finding.

4. Cascading transfers — PRESENT. Eight recorded events across four distinct assignee entities in ~40 months (2006-09 → 2009-12), including three Aequitas-side conveyances in a six-week window (2009-05-06, 2009-05-06, 2009-06-05). Assignees share a common lineage and the Aequitas-side transfers share a common entity family. Reels unknown except 018313/0608.

5. Pre-litigation transfer — NOT PRESENT (on available dates). The Aequitas → XR Communications transfer is dated/recorded 2009-12-23; the earliest suits I can find naming the '728 are the 2017 C.D. Cal. / S.D. Cal. filings (e.g., 2:17-cv-02959, 2:17-cv-02961, 3:17-cv-00675). An ~8-year gap, not the <6-month window. (Note the practical effect is the same — XR held the portfolio until it was ready to assert — but the literal signal as defined is absent.)

6. Bankruptcy fire-sale — PRESENT (functional equivalent, not a bankruptcy docket). The chain shows a Limited Judgment of Foreclosure (2009-05-06) and a Sheriff's Certificate of Judicial Sale (2009-06-05) transferring Vivato Networks entities' interest to Aequitas Equipment Finance, LLC, following a documented loan default. This is a secured-creditor foreclosure, not a Chapter 7/11 sale — I flag the distinction because your signal is defined as a bankruptcy proceeding and this is not one.

7. Privateering — UNCLEAR / NOT PRESENT. I found no evidence that XR Communications asserts on behalf of an operating-company sponsor. The "d/b/a Vivato Technologies" branding borrows a defunct operating company's identity, but nothing shows an operating company directing the campaign. Marking unclear rather than assuming.

8. Defensive aggregator — NOT PRESENT. The chain terminates at XR Communications, LLC, an active asserter; it does not end at RPX, AST, LOT, Unified, or OIN. The patent has not been neutralized — it has been asserted, including in IPRs brought against it by Aruba/Cisco/Ruckus.

Verdict

NPE — high confidence.

Drive: (a) the chain leaves the operating company at reel 018313/0608 (2006) and terminates at XR Communications, LLC, a licensing-only entity that litigates as "Vivato Technologies" and appears in the Stanford NPE database as the asserter on this patent; (b) cascading transfers — eight recordings through four assignee entities from 2006-09 to 2009-12, ending in a foreclosure/judicial-sale conduit (2009-05-06 and 2009-06-05) that exists to move the portfolio from a failed borrower to a buyer; and (c) the asserted-patent litigation footprint (2017 C.D. Cal./S.D. Cal. campaign and the 2023 E.D. Tex. campaign) against actual product makers rather than a competitive product market.

Two honest limits on this verdict: I could not obtain the assignment correspondent fields, so signal 3 (repeat recording attorney) is unresolved, and I could not verify the reel/frame for seven of the eight entries — only 018313/0608 is confirmed against this patent. Verify at the Assignment Center before relying on any individual reel/frame.

Assignment Center verification links:

• Current UI: https://assignmentcenter.uspto.gov/
• Legacy index (search by patent number 7729728): https://assignment.uspto.gov/patent/index.html
• Litigation context for the chain: https://www.courtlistener.com/docket/67349582/xr-communications-llc-dba-vivato-technologies-v-att-inc/ (Docket 170, Att. 19 quotes the reel/frame strings discussed above)

I'll verify the patent at USPTO and pull details on the cited prior art references.

The IPR record surfaces a key anticipatory reference ("Hovers"). Let me pull that plus several remaining citations.

Prior Art Analysis — US 7,729,728 B2

Scope note. Per the strict rule, I treated "7729728" literally and analyzed only that number — not its parent US 7,062,296 B2, and not any sibling. Because the previously generated section already established the bibliographic facts and the assignment chain, I build on those rather than repeating them. The decisive prior-art facts below come from (i) the authoritative patent text you supplied (the 23-reference citation table and the "Cited By"/"Citations" fields) and (ii) PTAB/USPTO filings located by search, which reproduce and characterize the examiner's citations. I could not do an element-by-element text pull of all 23 references within my search budget, so the § 102 mappings below are potential (subject-matter-based) rather than a complete limitation chart — consistent with your framing wording "potentially anticipates." Flagged explicitly where confidence is lower.

1. The single most important point: the examiner's own anticipation reference

The reference that mattered most during prosecution is not visible as a "primary" citation in the way you'd expect — it sits as the last entry of the "Patent Citations (23)" table:

US 7,346,365 B1 — "Smart antenna system and method" — Faulkner Interstices LLC — filed 2002-04-16, granted 2008-03-18 (Hovers et al.)

This is the "Hovers" reference (Ex. 1003) relied on across the 2018 IPRs. Its provenance is confirmed in the petition record:

• During prosecution of application 11/420,860 (which issued as the '728), "the claims were rejected as anticipated by U.S. Patent No. 7,346,365 to Hovers." (Apr. 24, 2008 Office Action, cited in Aruba Networks' petition, https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1508136](/patent/1508136)/)
• "The applicants did not contest that Hovers disclosed the limitations of the rejected claims, but rather achieved allowance by amending the claims to add limitations directed to 'actively probing the receiving device.'" (same source)

Why this is the key § 102 finding for your task:

Critical caveat that cuts against a pure-anticipation conclusion: the claim set you asked about is the issued set. The issued claims 1, 7, and 16 all require "active probing" (claim 1: generate a signal to cause the array to transmit over the different beam and gather signal-parameter info; claim 7: transmit a probe message, receive a probe-response, gather signal-parameter info; claim 16: "actively probe… over the beam downlinks"). By the examiner's and the Board's own account, Hovers alone does not disclose active probing — that is precisely why the amendment overcame the rejection. So, strictly: Hovers anticipates the pre-amendment claims but does not anticipate the issued independent claims 1, 7, or 16. Any lawyer asserting § 102 anticipation of the issued claims against a single reference is over-reading the record.

2. The second decisive reference (from the IPRs, not on the patent face)

WO 00/38455 A1 — Jetzek — "hard handoff" algorithm; added by the petitioner as Ex. 1004.

Per the Aruba petition record: "the claimed 'active probing' feature was taught in International Patent Publication No. WO 00/38455 to Jetzek (Ex. 1004), a prior art reference not before the examiner." Jetzek's measurement-command signals and its active-set add/delete mechanism ("a client device… is thus 'forced' to associate only with a beam listed in the active set") are the basis of the § 103 theory against claim 16. Jetzek is therefore the closest art to the "force" branch (claim 7; claim 16's force alternative) and to claim 13 (allow-list / not-allowed-list, which maps to Jetzek's active set) and claim 15 (ceasing transmissions / removal from the set). This is an obviousness reference, not an anticipation reference.

3. Full citation table — the 23 references on the face of US 7,729,728

Dates and assignees are as given in the authoritative patent text (priority date shown for the reference; publication/grant date second). Where a search source gave slightly different dates, I note it.

* = marked with an asterisk as "cited by examiner" vs. "cited by third party" in the source (per the Google Patents convention * Cited by examiner).

4. Ranked answer to "most relevant prior art"

Tier 1 — the references that actually drove validity:

1. US 7,346,365 B1 (Hovers / Faulkner Interstices) — the sole anticipation reference cited by the examiner; defeats the pre-amendment claims and maps to the front end of issued claims 1, 7, 16. § 102(e).
2. WO 00/38455 (Jetzek) — supplies the "active probing"/measurement-command and active-set force/allow limitations the issued claims added; the backbone of the IPR § 103 ground against claim 16 (https://ptacts.uspto.gov/... petitions/1508136/).
3. WO 99/21391 (Radio Design Innovation — "Seamless lobe handover") — the closest disclosure of the uplink-measurement → compare lobes → switch beam core of claims 1/7/16.

Tier 2 — strong § 103 combination material for the independent claims: US 5,987,037 (Lucent), US 6,850,741 (ASTAR), US 2004/0063468 (Frank), US 6,628,235 (Boeing).

Tier 3 — dependent-claim-specific: US 6,438,376 (claim 4, position/movement), US 2002/0103013 (claims 2/5, passive signal-parameter gathering and thresholds), US 5,771,017 (claim 16 architecture), US 6,049,307 / US 6,337,659 (phased-array hardware).

Tier 4 — background only: US 5,809,141, US 6,091,788, US 6,108,323, US 6,141,335, US 6,169,910, US 2001/0033600, US 6,311,075, US 6,470,195, US 6,611,695, US 6,631,277, US 6,895,230, US 6,907,269.

5. Explicit uncertainties and caveats

1. Anticipation vs. obviousness. Only Hovers was actually invoked as § 102 anticipation, and only against the pre-amendment claims. For the issued claims 1, 7, and 16, I found no single cited reference that discloses all limitations — the "active probing" element was deliberately added to escape Hovers. Treat every "anticipates claim 1/7/16" statement (including my Tier-1 mapping) as limited to the pre-amendment claim scope unless a full-text chart proves otherwise.
2. I could not retrieve the full text of all 23 references. The claim-level mappings above are subject-matter inferences, not a completed limitation-by-limitation chart. References 19 (US 2004/0063468) and 20 (US 6,850,741) in particular deserve a full-text read because their filing dates (2002-10-01 and 2002-04-04) both precede the '728 priority date (2002-11-04).
3. Date-source discrepancy. For US 5,771,017 the authoritative patent text shows priority 1993-08-12 / publication 1998-06-23, whereas the Unified Patents record shows priority 1993-08-11 / grant 1998-06-22. I used the patent-text dates as authoritative per the operating rule, but flag that the two days differ across sources.
4. No contradiction with the prior section. The earlier bibliographic/ownership/litigation findings are consistent with what this search returned; the Hovers identification fills in the one piece the earlier section left open ("the three 2018 IPRs… I did not retrieve the outcomes" — the petitions show Hovers/Jetzek as the grounds, but I still did not obtain the final written decisions' outcomes, so the validity posture of the issued claims remains unverified).
5. No 2026 activity located. Consistent with the prior section, nothing in this search tied a 2026-numbered docket to 7,729,728.

I'll ground the analysis in the actual prior-art references listed on the patent page before building the § 103 combinations.

Good grounding so far. Now let me examine the references most relevant to the "forcing"/association-control limitation and the actual IPR grounds asserted against this patent.

Obviousness Analysis — US 7,729,728 B2 under 35 U.S.C. § 103

Scope note / rule compliance. All identifiers are reproduced literally as they appear on the patent page (e.g., "US 11/420,860," "US 10/698,848," "WO1999021391A2," "US20040063468A1"). Where the live searches I ran in this session produced content that the page did not, I rely on the search results as ground truth; where I could not verify a reference's disclosure, I say so explicitly rather than assuming it.

1. Legal framework and effective date

• The '728 issued from US 11/420,860, filed 2006-05-30, a continuation of US 10/698,848 (filed 2003-10-31), which claims priority to provisional US 60/423,660 (2002-11-04). Because the application was filed well before 2013-03-16, pre-AIA § 103(a) governs (with KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), supplying the "expansive and flexible" rationales for pending cases).
• Controlling date: 2002-11-04 (or, at the latest, 2003-10-31), assuming the parent/provisional supports the claims. Prior art must therefore predate that date — either as §§ 102(a)/(b) art or as § 102(e) art (US patents/publications and PCT applications designating the US, measured from their earliest effective US filing date, including a provisional if it supports the relied-upon subject matter).
• Validity posture is historical: per the earlier section, the patent is Expired – Lifetime with adjusted expiration recorded as 2025-07-26. A § 103 analysis today is defensive/retrospective, but it remains the operative framework for evaluating the 2017–2022 litigation and the 2018 IPRs.

2. Person of ordinary skill in the art (PHOSITA)

A bachelor's degree in electrical engineering (or equivalent) plus 2–4 years of experience designing wireless RF/multi-antenna systems, i.e., familiar with: (a) the IEEE 802.11 family's association / re-association / active-scanning (probe request/probe response) and management-frame (deauthentication/disassociation) procedures; (b) cellular handover and network-controlled reselection; (c) phased-array / switched-beam and smart-antenna systems and uplink RSSI / C-I measurement. The '728 specification itself confirms this is the relevant baseline by describing the 802.11 association process as "well known" and admitting the client device's scanning/association handshaking as conventional.

3. Claim construction points that drive the analysis

Two constructions determine most of the § 103 fight. I flag them because they are genuine vulnerabilities for any challenge:

1. "operatively associate" (claims 1, 7, 16). The specification ties this to the IEEE 802.11 association/re-association process ("establish an association with an access point over a main beam"). Much of the closest prior art (e.g., WO1999021391A2) uses "handover between lobes," not "association." A challenger must show that a network-controlled lobe handover discloses or suggests a client associating with a beam. In re ICON Health & Fitness, 496 F.3d 1374 (Fed. Cir. 2007), and the "reasonably pertinent to the particular problem" test make this a contestable but losing argument for the patentee, because the problem addressed (keeping a mobile on the "correct" narrow beam) is identical.
2. "force" (claim 7) vs. "allow" (claims 1, 16). Claim 16 is drafted in the disjunctive ("at least one of: allow … force …"), so the system claim is met by either branch — a point that broadens the system claim's exposure.

4. The prior art of record and what each reference actually discloses

4.1 Verified in this session

WO1999021391A2 — "Seamless lobe handover" (Radio Design Innovation TJ AB; filed 1997-10-20; published 1999-04-29). Verified in full. Disclosure: a base station site uses fixed lobes from an antenna array; a connection is established on one lobe; "the base station site continuously measures the signals received from the mobile station" and "determines the best lobe by comparing the signal received in actual lobe with signal received in alternative lobes … received signal strength or … received signal to interference ratio"; the comparison "may imply a handover between the lobes," and the base station "changes utilized lobe … to another lobe of the same base station site." This is the single most on-point reference: it is network-side, uplink-measurement-driven, beam-level reselection.

US 6,438,376 B1 — "Wireless communications management and control system using mobile station position and movement information" (Nortel Networks; filed 1998-05-11; granted 2002-08-20). Verified (abstract, figures, background). Disclosure: uses location, speed, and direction of travel of mobile stations to manage handoffs and reduce call disruption; blocks include "RECEIVE LOCATION INFORMATION," "FIND BEST AVAIL CHNL (QI) FOR LOC," "PERFORM HANDOFF," "PERFORM POWER STEP," a "BAD SPOT?" test, and a "MOBILE STATION CHANNEL ASSIGNMENT QUEUE" keyed by priority/risk/speed. This is squarely the network-initiated (forced) reselection + position/movement determination + power-step teaching.

US 6,850,741 B2 — "Method for selecting switched orthogonal beams for downlink diversity transmission" (Agency for Science, Technology and Research; filed 2002-04-04; granted 2005-02-01). Verified in full. Disclosure: a switched-beam antenna system; beams are selected "based on the uplink reception"; a "simple and efficient method … is to calculate the power level at the uplink receiver output … for each beam and select the beam with the highest output power"; and a "power window threshold" to select candidate beams and compare them (with a cost function). This expressly supplies uplink-measurement-based beam selection with a comparison threshold — i.e., the "gathering signal parameter information [and] comparing … to threshold" concepts. Its 2002-04-04 filing date makes it § 102(e) art.

US 7,346,365 B1 — "Smart antenna system and method" (Hovers/Kagan; Faulkner Interstices; filed 2002-04-16; granted 2008-03-18). Verified (abstract + Fig. list). Disclosure: "one or more beam analysis modules … operable to analyze the uplink beams to determine one or more characteristics of each uplink beam"; a processing system that "determine[s] a selected beam from the plurality of uplink beams based at least in part on the one or more characteristics"; "fast decision" and "smart decision" beam-selection modules; structured to be an add-on to an existing base station. This supplies the passive uplink-signal-parameter gathering and beam-selection logic.

US 2004/0063468 A1 — "Method and apparatus for using switched multibeam antennas in a multiple access communication system" (Frank; Motorola; provisional 2002-09-30/10-01; non-provisional filed 2003-09-24; published 2004-04-01). Verified. Disclosure: a communication system that "schedules a different MS, or user, in each beam of multiple predetermined, fixed beams"; a base station subsystem conveys weighting coefficients to transmit a first beam to a first MS and a second beam to a second MS. This shows the infrastructure assigning/steering specific users to specific beams — the "allow/force association to a particular beam" concept.

4.2 Cited on the face of the patent but not verified in this session

These are listed as "Patent Citations (23)" on the page; I did not retrieve their texts in this session, so their disclosures below are title/assignee/date-derived only and must be verified before reliance: US 5,771,017 A (Northern Telecom), US 6,169,910 B1 (Focused Energy Holding), US 6,091,788 A (Nokia), US 5,987,037 A (Lucent, "Multiple beam wireless telecommunication system"), US 5,809,141 A (Ericsson), US 6,141,335 A (Hitachi), US 6,049,307 A (Samsung, "Adaptive phased array antenna using weight memory unit"), US 6,108,323 A (Nokia, beamforming CDMA), US 6,311,075 B1 (Nortel), US 6,337,659 B1 (Gamma Nu), US 6,611,695 B1 (Nortel), US 2001/0033600 A1 (Golden Bridge), US 6,895,230 B1 (Kathrein), US 6,907,269 B2 (NTT DoCoMo), US 6,470,195 B1 (Raytheon), US 2002/0103013 A1 (Watson), US 6,631,277 B2 (Ericsson), US 6,628,235 B2 (Boeing, "Method for phased array antenna signal handoff").

4.3 Not prior art (do not rely on these)

The page's "Similar Documents" and "Cited By" lists include items that post-date the 2002-11-04 priority date and therefore are not prior art: e.g., US 20050037822A1 ("Antenna steering method and apparatus for an 802.11 station"), JP 2007524272 A ("Access point antenna steering method"), US 7,684,802 B2 ("Communications handoff using an adaptive antenna"), WO2018156286A1, and US11445463B2. Also US10594376B2 / US10715235B2 / US11777569B2 ("Directed wireless communication," priority 2002-11-04) are same-family/continuation documents of the '728 family (Vivato/XR Communications), not prior art — they cannot be used against the '728.

5. Element-by-element mapping of the independent claims

6. Combination A — Claims 1–6 and 16–17 ("allow" branch + active probing)

Combination: WO1999021391A2 in view of US 6,850,741 B2, further in view of US 7,346,365 B1.

• WO1999021391A2 alone discloses every front-end element of claim 1: it teaches beam-level, uplink-driven reselection at a multi-beam base station site. What it does not squarely disclose is (i) recasting "lobe handover" as client "association," and (ii) the active-probing step of claim 1[e].
• US 6,850,741 B2 fills the measurement/selection gap: it expressly measures uplink power per beam, selects the best beam, and applies a power window threshold — the "gathering signal parameter information" and "comparing … to corresponding … threshold" concepts (claims 5 and 9).
• US 7,346,365 B1 fills the "passive gathering from uplink messages" gap (claims 2, 8, 17): its beam-analysis modules determine a characteristic of each uplink beam and pick the best beam from ordinary uplink traffic.
• The active-probing element (claim 1[e], claim 3, claim 10) is best supplied by the IEEE 802.11 active-scanning procedure — Probe Request/Probe Response frames — which the '728 specification itself treats as conventional (the client "detect[s] the presence of available access points," beacon/probe information, and a strongest/cleanest-signal priority scheme). An AP that transmits a probe over a candidate beam and measures the client's uplink probe response is the straightforward application of that known technique to WO1999021391A2's candidate-lobe evaluation. (If the challenger prefers a patent reference for this element, US 6,628,235 B2 or US 2002/0103013 A1 — both of record but unverified here — should be checked.)

Motivation to combine (KSR / MPEP 2143 rationales):

• (A) Combining known elements by known methods to yield a predictable result: uplink RSSI measurement (A*STAR, Faulkner) applied to lobe selection (WO'391) simply improves an existing selection criterion.
• (C)/(D) Using a known technique (uplink-based beam selection) to improve a similar device (a multi-beam base station) in the same way — WO'391's "compare received signal strength in actual vs. alternative lobes" is the same measurement A*STAR computes.
• (F) Design incentive/market force: the '728's own background admits the industry trend toward smart antennas in high-bandwidth WLANs/MANs, supplying the motivation to port cellular lobe-handover techniques into 802.11-style beam association.
• No teaching away was identified; to the contrary, A*STAR acknowledges that switched-beam systems are "more economical to implement" and desirable for exactly this application.

Dependent claims 2–6, 17 fall with the base claim (see § 8).

7. Combination B — Claims 7–15 ("force" branch + probe/response)

Combination: WO1999021391A2 + US 6,850,741 B2 / US 7,346,365 B1 + US 6,438,376 B1 + US 2004/0063468 A1, further in view of the 802.11 association/disassociation framework (admitted prior art).

• Forcing (claim 7 front end, claim 7[d]): WO1999021391A2's base station itself changes the utilized lobe — i.e., the network, not the mobile, drives the change. US 6,438,376 B1 goes further: it initiates handoffs from the network based on position/speed/direction ("PERFORM HANDOFF," "PERFORM POWER STEP," the priority/risk assignment queue), which is the "network forces the device to a different resource" concept. Applying WO'391's lobe change and Nortel's network-initiated handoff to an 802.11 beam (where the client ordinarily controls association) yields claim 7's "forcing" — with the predictable result of keeping the client on the "correct" beam.
• Probe message / probe response (claims 7[f]–[h], 10): 802.11 active scanning (Probe Request → Probe Response) provides the exact transmitter/receiver pair, and A*STAR/Faulkner provide "gathering signal parameter information" from the resulting uplink transmission.
• Allowed / not-allowed lists (claims 6, 13): US 2004/0063468 A1's scheduling of a specific MS to a specific beam, plus ordinary 802.11 association control (Association Response status; MAC-address ACLs) and US 6,438,376 B1's assignment queue, render a per-client allow/deny-per-beam data structure an obvious implementation.
• Disassociate message (claim 14): The 802.11 Disassociation/Deauthentication management frames are conventional (and the '728 spec concedes that "conventional IEEE 802.11 family compliant client devices need not be changed"). Sending a disassociate to force re-association is the application of a known technique to the WO'391/Nortel forced-handoff paradigm.
• Temporarily stopping transmissions over the current beam (claim 15): US 6,438,376 B1's "PERFORM POWER STEP" (power reduction) plus WO'391's fixed, individually addressable lobes make "blanking/cutting off" the current lobe an obvious equivalent (a simple power/switch control already present in a switched-beam system).
• Position determination (claims 4, 12): US 6,438,376 B1 is a direct hit — it computes and uses mobile position and movement to drive reselection; the AP determining "a current position of the receiving device relative to the phased array antenna from the uplink transmission" is the natural combination of Nortel's position-based management with WO'391's uplink lobe comparison.

8. Dependent claims — where each is met

9. Secondary considerations and counterarguments

• No teaching away identified. The '728's own background asserts that conventional re-association "tends to work well for … omni-directional or broad beam antennas" but not for narrow smart-antenna beams — i.e., it frames the problem rather than demonstrating unexpected results. A "problem solved" narrative is not a secondary consideration.
• "Association" vs. "handover" (the patentee's best argument). A challenger relying on WO'391 and Nortel must bridge cellular handover to 802.11 association. Under In re ICON Health, art is combinable if it is from the same field or reasonably pertinent to the problem; keeping a mobile on the correct narrow beam is the same problem in both arts, and the '728 itself treats the 802.11 association process as the vehicle. This argument is likely to fail but is worth pressing.
• The "active probing over the different beam" limitation (claim 1[e], claim 7[f]–[h]) is the strongest nonobviousness candidate. If the 802.11 active-scanning analogy is rejected as insufficiently tied to the candidate beam, the patentee may preserve claims 1 and 7 on this element. Note the asymmetry: claim 7 requires a probe message/probe response (more specific, arguably narrower) while claim 1 requires only generating a signal to initiate at least one downlink message over the different beam (broader, easier to meet).
• § 102(e) availability of US 2004/0063468 A1 must be checked. It published after the '728 priority date, so it is only available as § 102(e) art if (a) the '728 is not earlier entitled, and (b) the Oct. 1, 2002 provisional supports the relied-upon scheduling disclosure. I also flag a discrepancy: the Google Patents record gives the provisional as "60/4150,289" filed Oct. 1, 2002, while the Unified Patents entry lists the priority date as 2002-09-30 and application date 2003-09-24. Verify the provisional date/content before relying on this reference.

10. Bottom line and explicit uncertainties

Conclusion (with the caveats below): Claims 1–6 and 16–17 are prima facie obvious over WO1999021391A2 + US 6,850,741 B2 + US 7,346,365 B1, with 802.11 active scanning supplying the active-probing element. Claims 7–15 are prima facie obvious over that same combination further in view of US 6,438,376 B1 (network-initiated forced handoff; position/movement; power step) and US 2004/0063468 A1 (per-beam user scheduling), with conventional 802.11 disassociation/association controls meeting claims 6, 13 and 14. The motivation to combine rests on KSR rationales (A), (C)–(D) and (F), reinforced by the '728's own admitted industry trend.

Explicit uncertainties — do not treat as settled:

1. I did not verify the disclosures of US 5,987,037 A, US 6,049,307 A, US 6,108,323 A, US 6,169,910 B1, US 6,628,235 B2, US 2002/0103013 A1, US 6,091,788 A, or the other face-cited references. My element mapping above uses only the five references I verified (WO1999021391A2, US 6,438,376 B1, US 6,850,741 B2, US 7,346,365 B1, US 2004/0063468 A1); the rest are identified by title/date only.
2. I could not retrieve the 2018 IPR grounds or outcomes for IPR2018-00726 / -00763 / -01018 in this session (tool limit). The earlier section's petitioner attributions (Aruba Networks; Cisco Systems; Ruckus Wireless) are carried forward unverified, and whether any '728 claim was cancelled, confirmed, or upheld as amended is unknown — verify at the PTAB case links before relying on the patent's current claim scope.
3. I did not confirm that the '728 is entitled to the 2002-11-04 priority date for every limitation; if the active-probing limitations are only supported in the 2003-10-31 parent, the relevant prior-art window shifts, which could change the availability of close-in references (including US 2004/0063468 A1).
4. Tool-step limit prevented me from running the three additional verification searches I intended (US 6,049,930 A / US 5,987,037 A / IPR outcomes). No statement above should be read as confirming those references' contents.