US 8026804

I'll search for this specific patent number in the USPTO database and CAFC dockets.

Let me run additional searches to verify the USPTO record and check for any CAFC activity under alternate docket formats.

Let me run one final check for any litigation or CAFC proceedings referencing this patent number.

Summary of US Patent 8026804

Search results note

• USPTO/Google Patents record found (confirmed via patents.google.com, Justia, and golden.com). All sources agree on the bibliographic data below.
• CAFC 2026 docket search: no results. Searches for CAFC/ Federal Circuit/appeal activity referencing "8026804" returned nothing. I found no indication of any appeal or pending litigation at the Federal Circuit involving this patent, but an empty docket search is not conclusive proof of absence.

Bibliographic data (high confidence — matches full patent text and search results)

• Patent number: US 8026804 B2 (application no. US 12/125,218)
• Title: Residential security surveillance and notification management system
• Assignee: Chunghwa Telecom Co., Ltd. (Taiwan)
• Inventors: Chien-Huang Wu; Show-Ling Wu; Jhao-Siang Sun; Lun-Hsing Yeh; Shu-Fang Xiao; Yu-Huan Wang
• Priority date: August 29, 2007 (TW 096131979)
• Filing date: May 22, 2008
• Issue date: September 27, 2011
• Legal status: Expired – Fee Related. Per the USPTO legal-event record on the patent: maintenance-fee reminder mailed May 8, 2015; patent lapsed September 27, 2015 for failure to pay maintenance fees (FP event, effective 2015-09-27). Adjusted expiration listed as 2030-03-22, but the patent lapsed early in 2015 due to nonpayment.

Abstract (verbatim from the patent record)

"The apparatus is applicable to a communications network, wherein, via an information processing platform of a network server end, the system is connected to a network surveillance device installed in a monitored environment, in which the information processing platform processes and saves event message about the environment acquired by the network surveillance device, and generates corresponding notification messages. Via a browsing authorization certification mechanism, the system allows a user having been identified as a certified user to connect to the information processing platform via a communication terminal device for monitoring message information. Using the system, a certified user is capable of the following: accessing or receiving surveillance message information via the information processing platform, receiving notification message from the information processing platform, accessing the information processing platform to manage and maintain user authorized certification information, and/or selectively switching on/off connection between the network surveillance device and the information processing platform."

Independent claims

The patent has 15 claims, with only one independent claim (claim 1); claims 2–15 are dependent. Plain-language overview of claim 1:

Claim 1 — A residential security surveillance and notification management system operating over a communication network, comprising three main components plus an access-control requirement:

1. Network surveillance device — a body housing an image and/or sound acquisition unit. It captures analog or digital images/audio, converts them to digital signals, and can receive control signals over the network. Based on those control signals and/or a preset schedule, it can: (a) turn image/audio acquisition on or off, (b) adjust focus, and (c) physically move the device body.
2. Information processing platform — has a database; receives the digital signals from the surveillance device over the network, processes them, and stores them in the database. It must include a certification module that verifies whether the surveillance device and/or the communication terminal are authorized to connect.
3. Communication terminal device — has network communication, data processing, and input/display functions. Connected to the platform over the network, it can access/display stored digital-signal information and receive user control-signal information and/or a preset schedule, which it forwards to the platform. The platform then generates control signals that remotely operate the surveillance device over the network.

• Access-control requirement (the limiting feature): For each user, the database pre-stores (i) identity-identification/access-authorization information and (ii) certification information defining an access validity period for viewing the stored digital signals. The certification module contains:
  • a user identity identification module that checks whether the identity information transmitted by the terminal is authorized, and
  • an access-validity-period certification module that, after identity is verified, determines whether the user's access authorization has expired — granting access if still valid and denying access if expired.

Dependent claims (brief)

• Claims 2–6: add a surroundings-detecting unit connected to the surveillance device that sends security-event messages (e.g., from entrance, poisonous gas, fire, smoke, CO, or CO₂ detectors) to the platform for conversion into notification messages; notification delivery channels (instant message, e-mail, alarm announcement, audio); and immediate capture of image/audio at the detector location upon an event.
• Claim 7: certification of the surveillance device via its MAC address against a pre-stored identification list.
• Claim 8: identity identification uses a one-time password (OTP).
• Claim 9: adds a user information management module for managing/maintaining user information after identity verification.
• Claim 10: the surveillance device has a surveillance switching module to turn remote transmission to the platform on/off (privacy control, per the specification).
• Claims 11–12: the surveillance device has a wired or wireless communication interface; the wired interface may be a power-line communication (PLC) interface.
• Claim 13: a firewall and/or network routing device sits between the surveillance device and the platform; the device uses physical/floating/real/virtual addresses to pass security restrictions and rejects requests not originating from the platform.
• Claim 14: digital-signal processing includes conversion to 3GP, MPEG-1/2/4, MP3, WAV, or AVI formats and transmission via RTP and/or RTSP.
• Claim 15: the surveillance device includes an encryption module, with a corresponding decryption module in the platform.

Uncertainty note

• The bibliographic facts above are corroborated by the full patent text (provided as authoritative source) and by independent web search results (Google Patents, Justia, golden.com), which agree with one another.
• I could not verify via live search that the USPTO's current public record (e.g., Patent Center) still reflects the 2015 lapse, but the legal-event data in the authoritative patent text is explicit and internally consistent.
• No CAFC 2026 docket entries referencing patent 8026804 were found; this is reported as "no results found," not as a confirmed negative.

Based on my searches of litigation-focused sources (including Unified Patents case lists, CourtListener/docket sources, and general web searches for "8026804" litigation), I found no known litigation involving US Patent 8,026,804 ("Residential security surveillance and notification management system").

Details of what I did find:

• The number "8026804" appears in search results only as a citation/reference listed on other patents' pages (e.g., Justia pages for later Denso patents such as 12,017,506 and 12,269,315, where 8,026,804 is listed in a family/citation table along with other Chunghwa Telecom patents like 8,019,525). Those are not litigation references.
• No district-court complaints, CAFC appeals, PTAB proceedings (IPR/PGR/CBM), ITC investigations, or Unified Patents caselist entries naming US 8,026,804 were surfaced.
• Patent-office legal-status records (reflected in the Google Patents record) show the patent expired/lapsed effective September 27, 2015, due to nonpayment of maintenance fees under 37 CFR 1.362, and its adjusted expiration was 2030-03-22. The original assignee is Chunghwa Telecom Co., Ltd. (Taiwan). A lapsed, unmaintained patent held by a Taiwanese telecom would be an unlikely litigation subject, which is consistent with the absence of any litigation record.

Conclusion: As of April 26, 2026, I am not aware of, and could not locate, any litigation involving US Patent 8,026,804. Accordingly, there are no cases to report for plaintiff(s), defendant(s), jurisdiction, case number, filing date, or outcome/status. If you want me to check additional fee-based docket services (e.g., DocketNavigator, LexisNexis IP, Westlaw Dockets) or conduct a deeper PACER search, I can do so, but my public-web searches did not surface any such proceedings.

I'll verify the PTAB record for US Patent 8,026,804 through web searches before concluding.

The initial searches surfaced no PTAB matters for this patent. Let me run two more targeted searches to confirm the absence of any proceeding record.

I ran four independent web searches targeting PTAB proceedings, IPR/PGR/CBM petitions, institution decisions, and final written decisions naming US Patent 8,026,804 or its family. None returned any PTAB matter for this patent — only unrelated proceedings involving different patents and generic AIA practice content. Combined with the canonical USPTO ODP block in the prompt (which lists no AIA trial proceedings), the record is clear.

Proceedings overview

Total AIA trial proceedings on US Patent 8,026,804: zero. There are no active, instituted, settled, or denied IPR/PGR/CBM proceedings on file, and none were surfaced by web search. Bottom-line defensive posture: this patent has never been challenged at the PTAB, so it carries none of the "hardening" that comes from surviving review — but that fact is largely academic because the patent lapsed on 2015-09-27 for failure to pay maintenance fees (37 CFR 1.362) and has never been revived per the USPTO legal-event record. Any current assertion is therefore met first with an unenforceability/lapse defense, not an IPR strategy.

There are no proceedings to profile individually. The remainder of this analysis addresses what the empty docket means.

Strategic summary

Claim status — CANCELED vs. SUSTAINED vs. UNTESTED. All fifteen claims (independent claim 1 and dependent claims 2–15) are UNTESTED in any AIA trial proceeding. No petitioner has ever challenged a single claim under § 102, § 103, or § 112 before the Board. The only relevant post-issuance events are administrative, not adversarial: the patent issued 2011-09-27, was assigned to Chunghwa Telecom Co., Ltd. (Taiwan), received a maintenance-fee reminder on 2015-05-08, and lapsed on 2015-09-27 for nonpayment (legal events "LAPS," "STCH — patent expired due to nonpayment of maintenance fees," and "FP — lapsed due to failure to pay maintenance fee," effective 2015-09-27). The Google Patents "adjusted expiration" of 2030-03-22 reflects the statutory term had the patent been maintained; it was not, and the record shows no petition to revive under 37 CFR 1.378. No claim has been canceled by the PTAB, and no claim has been sustained in a FWD — there simply is no PTAB merits record for this patent.

Estoppel landscape. Because there has never been a final written decision (or any instituted proceeding) under 35 U.S.C. § 318, no § 315(e)(2) estoppel attaches to anyone. No petitioner, real party in interest, or privy is barred from raising any prior-art ground. For a defendant facing assertion today, this cuts in the defendant's favor in one narrow sense: every § 102/§ 103 ground that could have been raised in an IPR remains fully available in district court, in an ex parte reexamination, or in a future IPR petition (subject to the § 315(b) one-year bar if a complaint has been served — but note that the practical window for an IPR-based defense is dominated by the lapse issue discussed below).

Pattern signals. There are none: no serial petitioner, no Unified Patents or other defensive aggregator in the chain, no patent-owner PTAB litigation behavior to study, and no Federal Circuit appeals of any FWD (there is no FWD to appeal). The absence of PTAB activity is itself the expected signal for this asset — a low-profile Taiwanese telecom patent that lapsed within four years of grant for unpaid maintenance fees is precisely the kind of patent that never attracts an IPR because it is not being actively asserted.

Recommended next steps

• Lead with the lapse, not an IPR. If you are a defendant and this patent is asserted against you, your threshold defense is that the patent expired/lapsed effective 2015-09-27 due to nonpayment of maintenance fees under 37 CFR 1.362. The USPTO legal-event record is public (Google Patents legal-events table for US8026804B2: "LAPS" 2015-09-27, "STCH — Patent Expired Due to Nonpayment of Maintenance Fees Under 37 CFR 1.362" 2015-10-23/2015-10-26, "FP — Lapsed due to failure to pay maintenance fee" 2015-11-17). Verify in USPTO Patent Center/PAIR that no petition to revive was granted after 2015-11-17 — if none was, the patent is unenforceable for any post-lapse conduct, and any viable damages theory is confined to alleged infringement before 2015-09-27, nearly a decade before today's date. That limitation alone should be dispositive against most modern accusations.
• Confirm revival status before any deeper spend. If the record ever shows a revival, then reassess: the claims are wholly untested, so a validity challenge would start from a clean slate — no estoppel binds you, and any § 102/§ 103 combination over the cited art (e.g., US 7,409,045 to @Security Broadband Corp. and US 2006/0001537 A1 to Blake, both of record during prosecution) or over newly found art remains available in district court or via ex parte reexamination.
• Do not file an IPR reflexively. Even setting aside the lapse, note the practical posture: the patent's most recent priority date is 2007-08-29 (TW 096131979), so the PGR window closed long ago; an IPR would need to clear § 315(b) if a complaint was served more than one year before the petition; and the PTAB's discretionary-denial practice (including post-2025 Director-level institution review) makes IPRs against lapsed, unasserted-or-minimally-asserted patents an uphill and likely wasteful use of fees. If the goal is purely to clear the field of a revived patent, ex parte reexamination is the cheaper administrative route.
• If you are the patent owner: the patent is lapsed, and revival under 37 CFR 1.378 requires a showing that the maintenance-fee nonpayment was unavoidable (or unintentional, depending on timing) plus payment of the fee and any surcharge — and the window for an "unavoidable" petition has long since closed; only the "unintentional" route could conceivably remain, and even that is doubtful more than ten years post-lapse. In practical terms, treat US 8,026,804 as a dead asset.

Sources: USPTO Open Data Portal AIA trial database (no proceeding on file — canonical); USPTO legal-event records as reproduced on Google Patents (US8026804B2 legal-events table: lapse 2015-09-27, FP 2015-11-17); web searches conducted 2026-09-04 returned no PTAB or Federal Circuit matter naming this patent. No FWD, institution decision, or CAFC opinion exists to link because none was ever issued.

I have reached the limit of my live-search steps, so I will answer from the authoritative patent record provided plus the search results already gathered. I want to be transparent up front: I was unable to pull the USPTO Assignment Center cover sheet directly (the reel/frame record for this patent did not surface in my web searches), so the correspondent name on the sole recorded assignment is not verified from the primary USPTO interface. Everything below that concerns what is recorded is taken from the USPTO legal-event data embedded in the authoritative patent text, which lists all recorded conveyances affecting this patent.

Inventors

All six named inventors executed the original assignment (effective 2008-01-10) in favor of Chunghwa Telecom Co., Ltd. — the same entity that filed and owns the application — which indicates they were Chunghwa Telecom personnel (R&D staff) at the time of filing:

• Chien-Huang Wu
• Show-Ling Wu
• Jhao-Siang Sun
• Lun-Hsing Yeh
• Shu-Fang Xiao (recorded in the USPTO legal event with name order "Xiao, Shu-fang")
• Yu-Huan Wang

Unusual patterns: none observed. No indication that any inventor departed Chunghwa Telecom around filing, and there is no post-filing inventor-side assignment or portfolio fire-sale. The invention is consistent with Chunghwa Telecom's internal R&D on ISP-hosted surveillance services (the specification explicitly contemplates an ISP-provided information processing platform).

Original assignee

• Chunghwa Telecom Co., Ltd. (Taiwan) — the entity named on the issued patent and the current assignee of record per Google Patents.
• Primary line of business: Taiwan's largest telecommunications / ISP operator (fixed-line, mobile, broadband, and ICT services; formerly the state monopoly, publicly listed). This is squarely an operating company, not a patent-holding vehicle.
• Product embodiment: the patent's architecture (network camera → centrally hosted processing platform with database → authenticated remote terminal) matches a carrier-class home-security/IoT service an ISP like Chunghwa Telecom would deploy. I could not confirm a specific commercial product embodying the claims, so this is unclear, but the assignee is an operating telecom, not a shell.
• Current status: operating (no bankruptcy, no acquisition, no dissolution found). The patent, however, lapsed September 27, 2015 for failure to pay maintenance fees (USPTO legal events: REMI reminder 2015-05-08; LAPS 2015-09-27; FP effective 2015-09-27).

Assignment timeline

The USPTO legal-event record embedded in the authoritative patent text shows exactly one recorded assignment affecting this patent — the pre-issuance inventors-to-company assignment. There are no post-issuance recorded assignments (no reassignment, no security agreement, no change of name, no merger, no license). Google Patents' "Current Assignee" field likewise still points to Chunghwa Telecom Co., Ltd., corroborating that the chain never moved.

• 2008-01-10 (executed) / recorded 2008-05-22 — Reel 020983 / Frame 0771
  • Conveyance: Assignment of Assignors' Interest (ASSIGNMENT OF ASSIGNORS INTEREST, SEE DOCUMENT FOR DETAILS)
  • Assignor: Chien-Huang Wu; Show-Ling Wu; Jhao-Siang Sun; Lun-Hsing Yeh; Shu-Fang Xiao; Yu-Huan Wang (the six inventors)
  • Assignee: Chunghwa Telecom Co., Ltd.
  • Correspondent: Not retrievable from the sources available to me — the cover-sheet correspondent name is not shown in the Google Patents legal-event text, and my live searches did not return the USPTO Assignment Center cover sheet for reel 020983/0771. I will not guess or fabricate this field.
  • Context: Original inventors-to-employer assignment recorded on the filing date (2008-05-22) — a routine, standard prosecution-chain step, not an acquisition or transfer of an issued asset.

If the USPTO Assignment Center has no records beyond this: that is consistent with what I found. The finding here is that Chunghwa Telecom Co., Ltd. remained the owner of record from issuance (2011-09-27) until the patent lapsed (2015-09-27) for nonpayment of maintenance fees.

Timeline diagram

timeline
    title Ownership of US 8026804
    2007 : Taiwan priority filing
    2008 : US application filed
         : Assigned to Chunghwa Telecom
    2011 : Patent issued
    2015 : Maintenance fee unpaid
         : Patent lapsed

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. The only assignee in the chain is Chunghwa Telecom Co., Ltd., a large operating telecom. No transfer to any "IP / Holdings / Licensing" LLC, no registered-agent address, no single-purpose Delaware/Texas LLC appears anywhere in the record (reel 020983/0771 only).
2. Known asserter in the chain — Not present. Chunghwa Telecom does not appear on Acacia, Marathon, Intellectual Ventures, RPX, or Unified Patents asserter lists, and no litigation naming this patent was found in the prior analysis.
3. Repeat correspondent across the chain — Not present / unverifiable. There is only a single recorded conveyance, so no recurrence is possible. The correspondent name for reel 020983/0771 could not be retrieved from available sources.
4. Cascading transfers — Not present. No chained assignments through multiple LLCs; the ownership chain is flat (inventors → Chunghwa Telecom) and never moved post-issuance.
5. Pre-litigation transfer — Not present. No litigation exists naming this patent, and there is no assignment within six months of any suit (there is no suit).
6. Bankruptcy fire-sale — Not present. Chunghwa Telecom has not filed bankruptcy; the patent lapsed for nonpayment of maintenance fees in 2015 (FP event effective 2015-09-27), which is abandonment, not an asset sale.
7. Privateering — Not present. No transfer from an operating company to an NPE for assertion against competitors; the patent never left Chunghwa Telecom.
8. Defensive aggregator (anti-NPE) — Not present. The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. It terminates at the original operating assignee and then lapses.

Verdict

Insufficient data

Under the rubric, this is the correct call: the record contains only the original inventors-to-assignee assignment (reel 020983/0771, recorded 2008-05-22), and no post-issuance transfer, litigation, or asserter activity exists. The chain of title is a flat, unremarkable employer assignment ending at Chunghwa Telecom Co., Ltd., a major operating telecom whose patent then lapsed in 2015 for unpaid maintenance fees — the profile of an abandoned operating-company asset, not an NPE vehicle. Every NPE signal is "not present" (or, for the correspondent tell, unverifiable because no cover sheet was retrievable in my searches). Verification: USPTO Patent Assignment Search at https://assignmentcenter.uspto.gov/ (search patent number 8026804); reel/frame 020983/0771 is also reflected in the Google Patents legal-event feed for US8026804B2.

Caveat: I could not open the USPTO Assignment Center cover sheet directly in this session, so if you need the correspondent-of-record name for reel 020983/0771 (or want to confirm no later security-interest filings), that single field should be pulled from the Assignment Center by patent number before any reliance.

I'll research the prior-art references cited against US 8026804, verifying each against current USPTO records.

I have good data on both US citations. Let me verify the USPTO citation record for 8026804 itself and check whether the Blake application (US20060001537A1) ever granted, which affects its §102 status.

Let me verify whether the Blake application (US20060001537A1) ever issued as a patent, and check its application number.

USPTO Prior-Art Analysis — US 8,026,804 B2 (Residential Security Surveillance and Notification Management System)

Scope note on the USPTO record

I verified the USPTO/Google Patents record for US8026804B2 (application US 12/125,218, filed 2008-05-22, priority TW 096131979 of 2007-08-29, granted 2011-09-27, Chunghwa Telecom Co., Ltd.). The examiner-cited art on the record consists of exactly two U.S. references (both flagged "* Cited by examiner" on the Google Patents record):

1. US7409045B2 — Lifestyle multimedia security system
2. US20060001537A1 — System and method for remote access to security event information

The Google Patents family page additionally lists 12 foreign references under "Family Cites Families" (cited during prosecution of the TW/JP/KR family members). Those are secondary; I summarize them after the two U.S. references.

Because US 12/125,218 was filed May 22, 2008 (before the March 16, 2013 AIA transition), pre-AIA 35 U.S.C. § 102 governs. Claim 1 is the only independent claim; claims 2–15 are dependent.

Reference 1 — US7409045B2 (primary examiner citation)

Full citation: Naidoo, Surendra N.; Glasgow, William P.; Feldkamp, Gregory E. (assignee: @Security Broadband Corp., Austin, TX), Lifestyle Multimedia Security System, US 7,409,045 B2, appl. no. 10/607,008, filed June 26, 2003 (earliest U.S. family filing Feb. 1, 2002, app. 10/061,959 → US 6,658,091), granted Aug. 5, 2008. Related pre-grant publication: US 2004/0041910 A1 (Mar. 4, 2004). Classifications: H04M11/04, H04N7/18, G08B25/008, H04L63/08, G08B13/196.

Brief description. Remote monitoring of a premises. A geographically remote client is authenticated by a security system server; upon authentication the client receives an access token and connects (directly) to a premises security gateway that manages cameras, audio stations, and sensors. The gateway continuously caches and records audiovisual data (pre-event/post-event and on a pre-determined schedule), streams live media, and associates sensors with cameras so a triggering sensor causes capture from the associated camera. Access is governed by permission profiles and time-limited access tokens (expiring at a designated time/date, after a set duration, after a set number of accesses, or on revocation). The General Administrator can create guest accounts with limited, time-restricted permissions; remote users can adjust camera settings including pan, tilt, focus, brightness, contrast, zoom, arm/disarm the system, and receive alarm notifications via page, phone, e-mail, interactive voice response, or SMS. It expressly addresses privacy by notifying occupants that remote monitoring is occurring.

Prior-art status (§ 102). The cited B2 patent itself granted Aug. 5, 2008 — after the 8026804 filing (May 22, 2008) — so it is not § 102(a)/(b) prior art by its own grant date. However, its disclosure is carried by U.S. applications filed Feb. 1, 2002 / June 26, 2003, well before 8026804's invention/filing dates, so it qualifies as pre-AIA § 102(e) prior art ("patent granted on an application ... by another filed in the United States before the invention thereof"). The inventive entity (Naidoo et al.) and assignee differ from Wu et al./Chunghwa Telecom, satisfying the "by another" requirement. Additionally, the identical disclosure was already publicly available via US 6,658,091 (granted Dec. 9, 2003) and US 2004/0041910 A1 (published Mar. 4, 2004), both more than one year before 8026804's filing — so the underlying disclosure is independently available under § 102(a)/(b) through those family members.

Claims of 8026804 it potentially anticipates:

• Claim 1 (independent): Strongest overlap of any citation. The reference discloses every major component: (i) network cameras/audio stations (image and sound acquisition) whose signals are digitized (explicitly at the camera for "smart cameras," or centrally), remotely controllable for on/off, focus, and pan/tilt/zoom of the camera body; (ii) a server-side platform with a database (automation system server/database server) that receives, processes, and stores the audiovisual data; (iii) remote client terminals (PC, PDA, mobile phone) accessing/presenting stored and live data; and (iv) a two-stage access framework — server authentication of user identity (username/password, smartcard, biometric) followed by token/validity checking with expiration of access, against pre-stored per-user permissions. This maps closely onto claim 1's certification module + user-identity-identification module + access-validity-period module. Note: 7409045 frames much of this as a method (its claim 1 is method-based), but the specification discloses the corresponding system structure, and family members contain system claims. Caveat: it does not literally recite 8026804's exact two-module certification structure applied to "digital signal information saved in the database," so a single-reference anticipation of claim 1 is plausible but not airtight — the reference is at minimum primary evidence for § 103.
• Claim 9 (user information management module): Disclosed — General Administrator manages account data, creates guest users, edits permissions via web interface.
• Claim 10 (surveillance switching module to cut remote transmission): Disclosed in substance — arming/disarming, deactivating cameras/zones, and occupant-controlled privacy; remote transmission can be enabled/disabled by the user.
• Claim 11–12 (communication interface; PLC): Disclosed — wired/wireless interfaces; smart cameras expressly communicate over a home network "such as ... 802.11b, or power-line."
• Claim 14 (MPEG conversion/streaming): Disclosed in part — MPEG-family compression and streaming are described; the specific 3GP/MPEG-1/2/4/MP3/WAV/AVI + RTP/RTSP list is not literal.
• Claim 15 (encryption/decryption between device and platform): Disclosed in substance — encrypted protocols where the link is not secure.
• Claims 2, 4–6 (surrounding detecting units and event-triggered capture): Disclosed in part — sensors (motion, contact, carbon monoxide, fire) are wired/wirelessly coupled to the gateway and associated with specific cameras, and sensor triggers cause immediate capture from the associated camera (claim 6 analogue); notifications go by page/e-mail/phone/IVR/SMS (claim 5 analogue). However, the reference does not recite the full selective combination of claim 3's six detector types (entrance/poisonous gas/fire/smoke/CO/CO₂ — CO and fire appear; poisonous gas does not), so claim 3 is unlikely to be anticipated.
• Claims 7–8 (MAC-address device certification; OTP): Not disclosed → not anticipated.

Reference 2 — US20060001537A1 (primary examiner citation)

Full citation: Blake, Wilbert L. (Boca Raton, FL) and Salcedo, David (Lake Worth, FL), System and method for remote access to security event information, US 2006/0001537 A1, appl. no. 11/050,028, filed Feb. 3, 2005 (recorded priority date Nov. 20, 2003), published Jan. 5, 2006. This is an application publication; I found no evidence it ever issued as a U.S. patent, and later patents cite it solely as an A1 publication. Classifications: G08B 19/00, H04N 7/18, G08B 1/00.

Brief description. A security system with a remote/mobile access component for receiving and evaluating security data away from a central monitoring location. A security-event data-collection system gathers alarm data from detection devices; a video surveillance system captures images from cameras; a remote access system links the event/alarm data to the associated video data, stores the linked data in a consolidated database, and transmits it to mobile access devices. A notification/messaging system actively notifies users of events (e.g., with video clips and event timing). The remote access system can include a video/audio streaming and control system with dome control (camera positioning), video encoder, encryption device, and stream manager; a web server behind a firewall; and security technologies including two-factor authentication, PKI, SSL, and digital certificates.

Prior-art status (§ 102). Published Jan. 5, 2006 — before 8026804's priority date (Aug. 29, 2007) and before its U.S. filing (May 22, 2008), and more than one year before that filing (critical date May 22, 2007). It is therefore prior art under pre-AIA § 102(a) (publication before the invention) and § 102(b) (publication more than one year before the U.S. filing date — a statutory bar). Because it did not grant, § 102(e) does not apply to it.

Claims of 8026804 it potentially anticipates:

• Claim 1 (independent): Substantial overlap on the platform/database/terminal framework — a central remote-access system with a consolidated database storing linked alarm + video data, accessible by remote/mobile terminals, with authentication/security at the platform. Gap: the reference does not clearly disclose 8026804's specific time-limited access-validity-period certification module with pre-stored per-user validity information; its security disclosures are general (two-factor auth, PKI, SSL, certificates). Thus single-reference anticipation of claim 1 is weaker than for 7409045, but the reference is highly relevant for the platform-side processing/storage/notification elements, alone or combined under § 103.
• Claims 2 and 5 (security-event messages from surrounding detectors converted to notifications transmitted to the terminal via instant message/e-mail/alarm/audio): Strongly disclosed — event/alarm data is linked to video, stored in the consolidated database, and pushed via the notification/messaging system to mobile access devices.
• Claim 6 (instant acquisition of image/audio of the detecting unit's surroundings upon an event): Disclosed in substance — event data is linked to video of the event captured by the surveillance cameras, and streaming/control (including camera positioning via dome control) is provided.
• Claim 15 (encryption at the device/platform transmission path): Disclosed — the video/audio streaming and control system includes an encryption device (encrypting encoded video before wireless transmission), with corresponding decryption at the receiving/access side.
• Claim 4 (wired or wireless connection): Disclosed (Ethernet network 150; wireless LAN and cellular WAN interfaces).
• Claims 3, 7–14: Not specifically disclosed (no full six-type detector combination; no MAC-based device list; no OTP; no user-information-management module; no surveillance switching module; no PLC emphasis; no 3GP/MPEG/RTP/RTSP recitation) → not anticipated by this reference alone.

Secondary: foreign family-member citations (from TW/JP/KR prosecution)

These appear on the 8026804 family record ("Family Cites Families") and corroborate the same field of art; they are not part of the U.S. examiner's citation list on the face of US8026804B2. Listed literally as recorded:

These are relevant mainly to dependent-claim features (e.g., authentication for remote home control — JP2003179699A; remote monitoring servers — JP4595438B2; alarm e-mail notification — JP2006178837A) but none individually maps to all elements of claim 1.

Bottom line

• US7409045B2 (pre-AIA § 102(e); disclosure also public by 2003–2004 through family members) is the closest single reference — it most plausibly potentially anticipates claim 1 and dependent claims 2, 4–6, 9–12, 14–15 (with gaps noted above), and is the strongest § 103 anchor for the remainder.
• US20060001537A1 (pre-AIA § 102(a) and § 102(b), published Jan. 5, 2006) most directly reads on the platform-side event-notification/data-linking features — dependent claims 2, 4, 5, 6, and 15 — and on claim 1's platform/database/terminal skeleton, though it lacks the specific validity-period certification structure.
• Claims 3, 7, 8, and 13 are the least likely to be anticipated by any single cited reference; attack on those would need combinations under § 103.

Verification caveats (stated per operating rules): I confirmed the two U.S. citations from the authoritative patent text and live search results. I could not access the USPTO Patent Center prosecution file directly to confirm the examiner's reasons for allowance or the full file-wrapper citation list; the "no grant" conclusion for US20060001537A1 is based on absence of any issued-patent record across multiple sources, not on a USPTO database confirmation. The filing-date discrepancy for US20060001537A1 (record priority 2003-11-20 vs. Justia's filed date of Feb. 3, 2005, app. 11/050,028) is noted; publication date Jan. 5, 2006, is consistent across sources and is the operative § 102 date.

Obviousness Analysis — US Patent 8,026,804 (pre-AIA 35 U.S.C. § 103)

Scope note. This analysis uses the prior art appearing in the "Prior Art" section of the US8026804 patent record: the two U.S. references cited by the examiner (US7409045B2 and US20060001537A1) and the foreign references cited in the family members ("Family Cites Families"). Because the application was filed May 22, 2008 (priority Aug. 29, 2007), the pre-AIA § 103 standard applies. All references discussed below are prior art under pre-AIA § 102(a)/(b) and/or § 102(e): both U.S. references were published well over one year before the May 22, 2008 filing (US7409045's parent US6658091 issued Dec. 2, 2003, and its application publication US2004/0041910 A1 published Mar. 4, 2004; US20060001537A1 published Jan. 5, 2006), and US7409045B2 has an effective filing date of Feb. 1, 2002.

I. Legal framework and person of ordinary skill

Under pre-AIA § 103, a claim is unpatentable if the differences between it and the prior art are such that the claimed subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (PHOSITA), considering the Graham factors: (1) scope and content of the prior art, (2) differences between the prior art and the claims, (3) level of ordinary skill, and (4) secondary considerations.

A PHOSITA here would be an engineer or system architect with a bachelor's degree (or equivalent experience) in electrical engineering, computer science, or network engineering, and roughly 2–4 years of experience designing networked video-surveillance, home-security, or remote-monitoring systems, including familiarity with IP networking, authentication/access-control mechanisms, streaming media formats/protocols, and residential alarm sensors. The patent itself describes a modest, hardware-and-network integration task over a well-populated field (network cameras, home security, remote monitoring), not a new scientific field.

II. The references available from the Prior Art section

Primary reference — US7409045B2 ("Lifestyle multimedia security system"; Naidoo et al.; @Security Broadband Corp.; priority Feb. 1, 2002; granted Aug. 5, 2008). This is the strongest reference and was cited by the examiner. Verified content includes:

• Remote monitoring of a residential premises by a geographically remote client over a network, through a security system server that authenticates the user and a security gateway that manages monitoring (abstract; ¶¶0031–0062).
• Cameras 112 and audio stations 107 (microphones/speakers) at the premises, wired or wireless, indoors/outdoors, with the gateway creating associations between sensors and cameras and capturing audiovisual data upon sensor triggers and on scheduled bases (¶¶0045–0050, 0078).
• Analog cameras digitized by the video module; MPEG and other compression; continuous caching and recording; streaming to remote users (¶¶0048, 0070).
• Remote camera control: "pan, tilt, focus, brightness, contrast and zoom" adjustable by an authenticated remote user (¶0104); web-based remote client on PC/PDA/mobile phone (¶0039); remote arming/disarming and configuration (¶¶0054–0061, 0088–0092).
• Sensors 105 including "magnetic contact switches, audio sensors, infrared sensors, motion detectors, fire alarms, panic buttons, and carbon monoxide sensors" (¶0045).
• User identity authentication (username/password, smartcards, biometrics) by the server (¶0055); General Administrator and guest accounts with permission profiles (¶¶0054, 0092).
• Time-limited access: guest access "limited to certain time intervals … or for a certain number of times"; server checks whether the user has permission for "access during a particular time period" before issuing an access token having a desired lifespan; after token expiration the user must re-authenticate (¶¶0059, 0097–0101).
• Central server-side architecture with database server 436 / automation system server 420 storing account data and alarm history, and a media handler storing AV data; non-alarm video "may also be sent to the security system server 131 for storage" (¶¶0070, 0085–0092); "smart camera" embodiments communicating over 802.11b or power-line home networks (¶0078).

Secondary reference — US20060001537A1 ("System and method for remote access to security event information"; Blake; published Jan. 5, 2006; cited by the examiner). Verified content includes:

• A security system with detection devices 104, a video surveillance system 108 (cameras 110), and a remote access system 120 containing a consolidated database 130 that links alarm/event data to video data and stores them (¶¶0025–0033).
• Mobile access devices 112 that remotely receive and evaluate security event information, with notification/messaging (¶¶0025, 0033).
• Security technologies "including two-factor authentication, Public Key Infrastructure (PKI) security, secure sockets layer (SSL) and digital certificates" (¶0030); a firewall restricting external access (¶0034).
• A video/audio streaming and control system 210 with a dome control for camera positioning, a video encoder, and an encryption device encrypting encoded video for wireless transmission (¶0035).

Supporting family-cited references (content inferred from titles and family status; listed on the patent's family-citation page, so their full text was not verified live here): KR100716423B1 (SK Telecom, 2007) — "Remote monitoring and control system using communication network and method"; JP2003179699A (Matsushita, 2003) — "Network home appliance remote control system, method and authentication system"; JP4595438B2 (Panasonic Electric Works, 2010) — "Remote monitoring control system, center server… and communication method"; JP2002223483A (Yamatake, 2002) — "Remote management system." These corroborate that central-server remote monitoring/control of home devices with authentication was well developed in the 2002–2007 timeframe, particularly in the same East Asian market as the applicant.

III. Claim 1 — element-by-element obviousness analysis

Claim 1 is the only independent claim. Its elements map almost one-for-one onto the combined teachings of US7409045 and US20060001537.

Element 1: Network surveillance device (camera/audio unit in a body; digitization; network control; on/off acquisition, focus, and body movement; schedule-based operation)

US7409045 discloses cameras 112 and audio stations 107 at the premises, where the video module "may digitize the video" if the camera is analog (¶0070), cameras/audio transmit AV data continuously to the gateway (¶0047), and authenticated remote users control camera settings "including without limitation pan, tilt, focus, brightness, contrast and zoom" (¶0104). The smart-camera embodiment discloses a network camera appliance that "receive[s] instructions from the security gateway to control the session, FPS, quality, bandwidth" (¶0078). Recording is performed "at scheduled times" (¶0050) and at times defined by sensors (¶0045). Turning image/audio acquisition on/off is inherent in the gateway's remote arming/disarming and per-zone control (¶¶0054–0057), and Blake independently discloses a dome control for camera positioning plus a video encoder (¶0035). Difference from prior art: none of substance; the claim merely packages these known functions into a "network surveillance device" with a body, which is the conventional network-camera form factor described in the patent's own Background.

Element 2: Information processing platform with a database that receives, processes, and stores the digital signals

US7409045 discloses the data-center/security-system-server architecture in which the server includes a database server and automation system server storing customer data and alarm history (¶¶0085, 0089–0092), a media handler that receives and stores AV data (¶0086), and the option that "non-alarm video may also be sent to the security system server 131 for storage" (¶0070). Blake discloses the central consolidated database 130 that links and stores alarm and video data (¶0026, 0033). A PHOSITA would read the claim's "information processing platform … saving [digital signals] in the database" as satisfied by either the US7409045 data center or the Blake remote access system. Difference: none of substance.

Element 3: Communication terminal device that accesses/displays stored data and relays control signals/preset schedules, with the platform generating control signals to operate the surveillance device

US7409045's remote client 155 (PC, PDA, or mobile phone, ¶0039) uses a web-based video client to "view and hear live and recorded media from premises 110" (¶0088), and the authenticated user can reconfigure the security system and adjust camera settings remotely (¶0104); the application server "may relay control and configuration data destined for security gateways" (¶0086). Blake's mobile access device receives security event data and the video/audio streaming and control system 210 manages camera control (¶¶0025, 0035). Difference: none of substance.

Element 4 (the limiting feature): Certification module with (a) per-user pre-stored identity-identification/authorization info, (b) pre-stored "access validity period" certification info, (c) a user-identity-identification module, and (d) an access-validity-period certification module that grants access if unexpired and denies if expired

This is the feature most likely to have been argued as the point of novelty, but it is squarely taught by US7409045:

• Per-user identity info pre-stored in a database: US7409045 stores "usernames and passwords" in the automation system server database (¶0092), with the General Administrator creating guest accounts with defined permission profiles (¶¶0054, 0092).
• Access-validity-period certification info: "Access may be limited to certain time intervals (such as only at certain times during the day), a certain interval of time (such as beginning Friday and ending Sunday), or for a certain number of times" (¶0059). The server "determines if the remote user has the necessary permissions to access the security gateway. Necessary permissions may include … access during a particular time period" (¶0097).
• Identity identification module: the security system server authenticates the user by username/password, smartcard, or biometrics before any access (¶0055; Fig. 5, steps 510–520), and denies access if authentication fails (¶0096).
• Access-validity-period module granting/denying based on expiry: the server issues an access token with "the desired lifespan of the token" (¶0098); the user may access "until the remote user logs out … or the access token expires" (¶0100); "after a pre-specified time or event, the access token expires and the remote user may not access the security gateway after the expiration … [and] must reconnect to the security system server and provide valid authentication information" (¶0101). Blake corroborates authentication-before-access and denial of unauthorized access via two-factor authentication, PKI, SSL, and digital certificates (¶0030), and a firewall restricting external access (¶0034).

Thus the claimed "certification module" with its two sub-modules is, at most, a labeled restatement of US7409045's server-side authentication-and-time-limited-token architecture, implemented on the central platform of Blake. Difference: none of substance.

Element-by-element conclusion for claim 1

A PHOSITA reading US7409045 (optionally with Blake) would find every recited structural and functional limitation. There is no element that requires new technology, a new protocol, or a result not achieved by the references. Claim 1 is therefore a prime candidate for obviousness over US7409045 alone or US7409045 in view of US20060001537.

IV. Motivation to combine

A challenger can articulate a strong, non-hindsight rationale for combining these references:

1. Same field, same problem. Both US7409045 and Blake are directed to security-event monitoring with remote user access — US7409045 explicitly targets residential premises ("lifestyle monitoring" of children/elderly, alarm verification), and Blake targets remote access to security data away from a central station. Combining references in the same field to fill gaps is the paradigm case of obviousness (see, e.g., KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007)).

2. Complementary architectures. US7409045 solves bandwidth problems by letting an authenticated client connect to the premises gateway while the server authenticates and issues time-limited tokens; but it also discloses server-side storage (¶¶0070, 0085–0092). Blake solves a complementary problem — a single consolidated, centrally searchable database of linked event/video data accessible by mobile devices. The claimed invention is essentially the intersection: a centrally controlled processing platform (Blake's consolidated database; US7409045's data center) that authenticates users and enforces access-validity periods (US7409045's server) for AV captured by a controllable network camera (US7409045). A PHOSITA seeking to "process and save security event messages via a centrally-controlled information processing platform" (the patent's own stated objective) would naturally take the central database of Blake and the authentication/time-window/token-expiry framework of US7409045. This combination is "the combination of familiar elements according to known methods" that KSR identifies as obvious when it yields a predictable result.

3. Express teaching of time-limited access as a security/privacy measure. US7409045 repeatedly ties authentication, per-user permissions, and time-limited access tokens to the goal of balancing "security, privacy, and convenience concerns, particularly with residential security systems" (¶¶0013, 0059, 0097–0101) — the same problems the '804 specification's Background identifies (third-party interception, privacy, unauthorized remote access). The motivation to implement the claimed access-validity check is therefore explicit in the primary reference itself.

4. The examiner's own citation pattern. Both U.S. references are listed as "Cited by examiner" on the face of US8026804, meaning the examiner already recognized them as the closest art. That does not, by itself, establish obviousness, but it confirms that these are the references a PHOSITA would locate in a search of the field.

5. Reasonable expectation of success. The combination requires no technical innovation: standard networking, a database, an authentication server, and an IP camera — all commodity components by 2007, as evidenced further by the contemporaneous family-cited KR/JP references (KR100716423B1; JP2003179699A; JP4595438B2) showing central-server remote monitoring/control of home devices with authentication in the same period.

V. Dependent claims 2–15

• Claim 2 (surroundings detecting unit sending security-event messages to the device → platform → notification to terminal): US7409045 discloses sensors 105 wired or wirelessly coupled to the security gateway, event messages relayed to the security system server, and alarm notifications sent to contacts via "page, phone, e-mail, interactive voice response, short message service, or other messaging tool" (¶¶0045, 0089; messaging interface 438). Blake discloses event data from detection devices linked to video and transmitted to mobile devices with a notification/messaging system (¶¶0025–0026, 0033). Obvious.
• Claim 3 (detector types: entrance, poisonous gas, fire, smoke, CO, CO₂): US7409045's sensor list includes magnetic contact switches (door/window), fire alarms, and carbon monoxide sensors (¶0045); its Background describes conventional door/window contacts, smoke detectors, and gas/fire sensors. Adding CO₂ and general poisonous-gas detectors to a residential alarm/sensor suite was standard, off-the-shelf design choice by 2007. Obvious.
• Claim 4 (wired or wireless sensor connection): US7409045 discloses sensors "wired directly into an alarm control panel … or … wirelessly connected" (¶0045). Literally disclosed.
• Claim 5 (notification via instant message, e-mail, alarm announcement, audio): US7409045 ¶0089 (messaging interface 438: page, phone, e-mail, IVR, SMS); Blake's notification/messaging system 164. Obvious.
• Claim 6 (instant capture of image/audio of the sensor's surroundings upon an event): US7409045 ¶¶0047, 0050: the gateway creates an association between sensors and cameras/audio stations and, when a sensor is triggered, stores the cached AV segment from the associated camera/audio station beginning before and ending after the trigger — the exact "instantly acquires" behavior. Literally disclosed.
• Claim 7 (device certification via MAC address against a pre-saved list): US7409045's media handler tracks network addresses of all security gateways (¶0086) and the system identifies wireless remotes as unique users (¶0073); MAC-based identification of network appliances was a routine, well-known technique for network-device authentication by 2007 (also corroborated by the family-cited JP/KR network-device authentication references). The dependent limitation adds only a conventional implementation detail of device certification.
• Claim 8 (OTP identity identification): Blake discloses "two-factor authentication" (¶0030), and OTPs were a standard two-factor technique. Applying OTP as the authentication token in a remote security-access system was an obvious selection among known authentication means; US7409045 itself says "the present invention contemplates the use of many authentication techniques" (¶0055). Obvious.
• Claim 9 (user information management module): US7409045's General Administrator can "review and change account information," create guest accounts, and manage permissions through the web interface (¶¶0054, 0057, 0088, 0092). Literally disclosed.
• Claim 10 (surveillance switching module turning remote transmission on/off; local monitoring instead): US7409045 is expressly concerned with occupants' privacy, permits remote arming/disarming and per-user/per-zone permission control, and lets the administrator withdraw access at any time (¶¶0054, 0059–0061). A user-operable switch to disable outbound transmission while retaining local monitoring is a straightforward, predictable privacy control, especially given US7409045's teaching of "smart camera[s]" that can serve a local home-area network (¶0078). Obvious as a design choice for privacy (the '804 specification itself frames it as a privacy objective).
• Claims 11–12 (wired/wireless interface; PLC): US7409045 ¶0078 expressly discloses smart cameras communicating over "a home area network, e.g., … 802.11b, or power-line." Literally disclosed (PLC = power-line communication).
• Claim 13 (firewall/routing device between camera and platform; device rejects requests not from the platform): Blake discloses a firewall restricting external access to the remote access system (¶0034). Placing a firewall/router between a network device and a central server, and configuring the device to accept only server-originated communications, is a routine network-hardening measure; US7409045's token model likewise prevents direct unauthorized access to the gateway (¶¶0096–0101). Obvious.
• Claim 14 (conversion to 3GP/MPEG-1/2/4/MP3/WAV/AVI; RTP/RTSP transmission): US7409045 discloses MPEG compression and standard streaming protocols (¶¶0048, 0070); Blake discloses a video encoder (¶0035). Selecting among then-standard codecs (3GP, MPEG family, MP3/WAV/AVI) and standard streaming protocols (RTP/RTSP) was a routine implementation choice for network video by 2007, with no unexpected result. Obvious.
• Claim 15 (encryption at the device; decryption at the platform): Blake discloses an "encryption device 216 that encrypts the encoded video data" before wireless transmission (¶0035); US7409045 discloses encrypted protocols for non-secure connections (¶0081). Obvious.

VI. Secondary considerations and counterarguments

• No known secondary indicia of non-obviousness. The earlier analysis found no litigation involving US8026804, and the patent lapsed in September 2015 for failure to pay maintenance fees after only four years — facts inconsistent with strong commercial success or industry recognition. Nothing in the record suggests long-felt need, unexpected results, licensing, or praise that would rebut a prima facie obviousness case.
• Potential patentee counterarguments and their likely force. A patentee might argue that (i) US7409045 routes live media around the central server to the premises gateway rather than through a central platform, and (ii) the specific "access validity period" claim language requires the database (not the server logic generally) to store the validity data. Both are weak: US7409045 also discloses server-side storage of non-alarm video and account/alarm data (¶¶0070, 0085–0092), and Blake's consolidated database plus notification system supplies the central-platform architecture; the validity-period feature is disclosed nearly verbatim in US7409045 ¶¶0059, 0097–0101 (time-window permissions and expiring tokens). Implementing those teachings in Blake's centralized database is the kind of predictable re-arrangement KSR treats as obvious.
• High-level functional claiming. Claim 1 is drafted in broad functional language ("capable of," "executing at least," "certifying if"), which a PHOSITA would read to cover conventional implementations. The breadth of the claim makes it easier, not harder, to map onto the prior art.

VII. Conclusion

On the record available from the Prior Art section, US Patent 8,026,804's claims would likely be held obvious under pre-AIA 35 U.S.C. § 103, with the strongest case being:

• Claim 1 obvious over US7409045B2 alone, and in any event over US7409045B2 in view of US20060001537A1 — the former supplying the residential network-camera/monitoring system, database/server storage, remote terminal control, user authentication, per-user permission profiles, and time-limited (expiring) access enforcement; the latter supplying the centralized consolidated event/video database, mobile access, camera-position control, encryption, and firewall protection.
• Claims 2–15 obvious over the same combination, with US7409045 literally disclosing the sensor/camera association and trigger-based capture (claim 6), wired/wireless and power-line interfaces (claims 11–12), user-account management (claim 9), and messaging-notification channels (claims 2, 5), and with the remaining dependent limitations (MAC/OTP authentication, detector-type menu, encryption, codec/protocol selection, firewall) being conventional design choices well within the PHOSITA's toolkit by the 2007 priority date.

Caveats. (1) My content verification was live and deep for US7409045B2 and US20060001537A1 only; the Korean/Japanese family-cited references were relied on only as corroborating background because their full texts were not retrieved. (2) Obviousness is ultimately decided case-by-case, and a complete analysis would also consider the prosecution history (not reviewed here) for any applicant arguments that narrowed claim scope. (3) This is a technical analysis, not a legal opinion; a court or the PTAB would apply additional procedural and evidentiary rules.