US 8483102

Summary — U.S. Patent 8,483,102 (US8483102B1)

Note on identifier: per your instruction I did not auto-correct the number. The patent is published as US8483102B1 (application US11/926,390), title as below.

Bibliographic data

Sources: Google Patents record for US8483102B1 (fetched 2026-09-08) and USPTO assignment/legal-event data reflected therein.

Abstract (verbatim from the patent)

"A method and system includes: one or more phone systems; a policy processor coupled to the phone systems; and a voice identity mapping policy stored in a data storage, the data storage being accessible to the policy processor. The voice identity mapping policy includes: a plurality of search voice identities mapped to one or more target voice identities, where the plurality of the search voice identities are applicable to a plurality of users, where each of the search voice identities and the target voice identities comprises a username for one of the plurality of users, and time attributes indicating when the voice identity mapping policies are valid. When a voice identity for a recipient of a call is received, the policy processor checks for the voice identity mapping policy associated with the voice identity. The call is then forwarded to the target voice identity in the voice identity mapping policy."

Plain-language overview of the independent claims

Claim 1 (system) — A call-routing system made of: (a) one or more phone systems (with telephony switches that perform call routing) providing voice services; (b) at least one policy processor coupled to the switches that receives a "voice identity" from the switches; and (c) at least one voice identity mapping policy stored in accessible data storage. The policy includes multiple "search voice identities" mapped to one or more "target voice identities" (the search identities applying to a plurality of users) plus time attributes stating when the policy/identities are valid. When the policy processor receives a voice identity, it matches it to a given search voice identity, maps that to a given target voice identity per the policy (with the voice identity, search identity, and target identity each being a username), and sends the target username to the telephony switches, which route the call using that username.

Claim 11 (method) — The corresponding method: receiving a voice identity for a call recipient at a policy processor from telephony switches performing call routing; checking for a voice identity mapping policy associated with the identity (the policy having multiple search voice identities applicable to multiple users, mapped to target voice identities, and a time attribute indicating validity); matching the received identity to a given search voice identity; mapping it to a given target voice identity per the policy, all identities being usernames; and sending the target username to the switches, which route the initial call using that username.

Key points carried by the dependent claims (2–10 for the system; 12–20 for the method): the phone systems may include PBX, PSTN, VoIP, and/or wireless networks; the policy processor may be software on an application server, a stand-alone computer, or an ASIC; the VoIP service may be IM-based with the username being an IM identity or email identity, or a corporate VoIP service where the username is an employee's computer user identity; a telephone operator may operate the processor and multiple phone systems offering corporate/residential/VoIP/mobile services; and claims 10 and 20 add transitive mappings across phone systems (first search identity → first target identity on a second phone system → second search identity → second target identity on a third phone system, with the final target different from the first search identity).

Litigation / CAFC docket search results

• USPTO/patent record: Confirmed via Google Patents; no conflict with the text provided.
• CAFC 2026 dockets: I searched for a Federal Circuit appeal involving this patent number (including queries targeting "8483102", "8,483,102", and "Lab Technology" at the CAFC). No CAFC docket or appeal was found as of this search. I cannot confirm any Federal Circuit case exists for this patent; that is a negative result with the usual caveat that docket databases may be incomplete.
• District court activity (not CAFC, but informative): The patent family has been asserted by Lab Technology LLC in 2024–2025, including: Lab Technology LLC v. Lumen Technologies, Inc. (W.D. Tex. 7:25-cv-00172, dismissed June 2025), Lab Technology LLC v. Zendesk, Inc. (W.D. Wis. 3:25-cv-00303, dismissed May 2025), Lab Technology LLC v. 3CX USA Corp. (S.D. Fla. 1:25-cv-22704, voluntarily dismissed with prejudice August 2025), Lab Technology LLC v. u-blox America, Inc. (N.D. Tex. 4:25-cv-00610, filed June 2025), plus additional cases listed on the Google Patents record (E.D. Tex., W.D. Tex., W.D. Wis., E.D. Va., D. Colo., S.D. Fla.).

Uncertainty notes

• The current-assignee information comes from the recorded assignment (effective 2024-01-15, recorded 2024-06-25) shown on Google Patents; I did not independently verify it in the USPTO Assignment Database.
• No authoritative CAFC docket for this patent was located; if you need certainty on Federal Circuit status, PACER/CAFC CM/ECF would be the authoritative source.

I'll research litigation involving US Patent 8,483,102. Let me search multiple sources for these cases.

Let me search for more specific case details on the remaining docket numbers.

Based on the litigation record on the '8483102 patent's own USPTO/Google Patents record (which pulls from Unified Patents and Darts-ip litigation data), plus docket searches, here is what I can confirm and what remains unconfirmed.

Known litigation involving U.S. Patent 8,483,102

All known cases are brought by Lab Technology LLC (the current assignee; assignment from TP Lab, Inc. recorded June 25, 2024, effective January 15, 2024). Plaintiff's counsel in most cases: Isaac Rabicoff (Rabicoff Law LLC). The '102 patent is one of several patents (family includes U.S. 7,391,858; 8,111,822; 8,483,102; 9,413,895) being asserted in a broad enforcement campaign.

1. Lab Technology LLC v. AT&T, Inc. — No. 2:24-cv-00412

• Jurisdiction: U.S. District Court, Eastern District of Texas (Marshall)
• Judge: Rodney Gilstrap
• Filed: June 4, 2024
• Status/Outcome: Closed/terminated July 3, 2024 — dismissed early (voluntary dismissal; RPX shows only 30 days in litigation). Specific dismissal terms not confirmed in my searches.
• Source: RPX Insight (insight.rpxcorp.com), case flagged on the '102 patent litigation record.

2. Lab Technology LLC v. AT&T, Inc. — No. 2:24-cv-00830

• Jurisdiction: U.S. District Court, Eastern District of Texas (Marshall)
• Judges: Rodney Gilstrap (presiding); Roy S. Payne (magistrate)
• Filed: October 11, 2024 (AT&T served October 18, 2024)
• Status/Outcome: Closed/terminated December 23, 2024. Plaintiff filed a Notice of Voluntary Dismissal on December 12, 2024; case terminated December 23, 2024.
• Sources: UniCourt; RPX Insight; Docket Alarm (2:24-cv-00830).

3. Lab Technology LLC v. Zoom Communications Video, Inc. — No. 1:24-cv-01711

• Jurisdiction: U.S. District Court, District of Colorado
• Judge: Susan Prose
• Filed: June 19, 2024
• Status/Outcome: Closed July 1, 2024 — voluntary dismissal ~13 days after filing (per RPX).
• Source: RPX Insight; UniCourt.

4. Lab Technology LLC v. Lumen Technologies, Inc. — No. 7:25-cv-00172

• Jurisdiction: U.S. District Court, Western District of Texas (Midland/Odessa Division)
• Filed: April 17, 2025
• Patents asserted: U.S. 8,483,102 (the '102 patent) and U.S. 8,503,973
• Status/Outcome: Pending as of the available docket record (complaint on file; no dismissal located). Claims direct and induced infringement of the '102 patent.
• Source: CourtListener docket 69909727, Complaint Document #1 (filed 04/17/2025).

5. Lab Technology LLC v. Alaio, Inc. and Bitrix, Inc. — No. 1:25-cv-01234

• Jurisdiction: U.S. District Court, Eastern District of Virginia
• Judges: Rossie D. Alston, Jr. (district); William E. Fitzpatrick (magistrate)
• Filed: July 24, 2025 (against Bitrix, Inc. and Alaio, Inc.)
• Status/Outcome: Pending/Active as of the last docket pull (September 19, 2025). Amended complaint filed August 27, 2025 against Alaio, Inc.; Bitrix appeared and obtained extensions; answer deadlines extended to October 18, 2025.
• Source: Justia Dockets (1:2025cv01234).

6. Lab Technology LLC v. 3CX USA Corp. — No. 1:25-cv-22704

• Jurisdiction: U.S. District Court, Southern District of Florida
• Judge: Chief Judge Darrin P. Gayles
• Filed: June 16, 2025
• Status/Outcome: Dismissed with prejudice August 20, 2025 — plaintiff filed a voluntary notice of dismissal under Rule 41(a)(1)(A)(i) ~65 days after filing; no fee-shifting, no damages, no merits ruling.
• Source: Patsnap/Eureka litigation summary.

7. Lab Technology LLC v. [defendant unconfirmed] — No. 3:25-cv-00303

• Jurisdiction: U.S. District Court, Western District of Wisconsin
• Filed: 2025 (per the patent record)
• Status/Outcome: Listed in the Unified Patents litigation data associated with the '102 patent, but I could not confirm the defendant's identity or current status from my searches — I did not want to guess. If you need this, PACER (W.D. Wis.) or the Unified Patents portal case page would be the authoritative source.

Cautions / unconfirmed items

• Several other Lab Technology LLC cases appeared in my searches (e.g., 2:24-cv-00829 v. Amazon.com, 6:24-cv-00331 v. Microsoft, 6:24-cv-00335 v. Qualcomm, all W.D./E.D. Tex., filed June–October 2024 and quickly dismissed). These were not flagged on the '102 patent's litigation list and may assert other family members (e.g., '391,858 / '411,822 / '413,895) or other patents (e.g., '503,973). I did not include them because I could not confirm they assert 8,483,102.
• For the dismissed cases (items 1, 2, 3, 6), I could not confirm from the public record whether any settlement/license consideration was paid; most appear to be early voluntary dismissals with no merits ruling.
• The patent's record also references first worldwide family litigation tracked by Darts-ip (family ID 48701445), which is consistent with the U.S. cases above.

Bottom line: US 8,483,102 is actively being enforced by Lab Technology LLC. I identified seven U.S. district-court cases tied to it on the patent's litigation record. Of those, I confirmed full party details for six (all plaintiff Lab Technology LLC; defendants AT&T, Inc. (×2 cases), Zoom Communications Video, Inc., Lumen Technologies, Inc., Alaio, Inc./Bitrix, Inc., and 3CX USA Corp.). Five of the confirmed cases have already closed via early voluntary dismissal; Lumen (W.D. Tex. 7:25-cv-00172) and Alaio/Bitrix (E.D. Va. 1:25-cv-01234) were still pending as of the most recent docket data I could retrieve. The Wisconsin case (3:25-cv-00303) is on the record but its defendant/status could not be verified from my searches.

I'll research PTAB activity on this patent. The canonical structured data reports no AIA trial proceedings on file, so I'll verify with targeted searches before concluding.

No IPR results specific to this patent so far. Let me search with assignee/litigation context and known prior-art angles.

Let me search PTAB trial databases directly and check Unified Patents' involvement with this specific patent.

Proceedings overview

Total AIA trial proceedings on U.S. Patent 8,483,102: 0. There are no active proceedings, no proceedings resulting in claim invalidation, no proceedings with claims sustained, no settlements, and no institution denials — the USPTO Open Data Portal (ODP) ingest shows no AIA trial proceedings on file, and independent web searching (PTAB-specific queries, petitioner/assignee queries, Unified Patents tracking, and litigation-research databases) surfaced no IPR, PGR, or CBM petition ever filed against this patent.

Bottom-line defensive posture: this patent is completely PTAB-untested — none of its 20 claims has been canceled, and none has been "hardened" by surviving a trial. For a defendant facing assertion today, that is a double-edged sword: you cannot point to any FWD that kills the asserted claims, but no prior § 102/§ 103 ground has been exhausted and no IPR estoppel (§ 315(e)(2)) binds anyone, so a full prior-art challenge remains available — subject only to the § 315(b) one-year clock from service of a complaint.

Proceedings

No proceeding entries are provided below because no AIA trial proceeding exists for this patent. Per the operating rules, I will not invent proceeding numbers, panel names, institution decisions, or FWDs. The structured "PTAB proceedings on file" block is empty, and all searches corroborated that result.

Strategic summary

Claim status: all claims UNTESTED. All 20 claims of US 8,483,102 (independent claims 1 and 11; dependents 2–10 and 12–20) remain in force, unmodified by any AIA trial. No claim has been canceled, narrowed, or sustained by the PTAB. There is no FWD to quote, no panel to name, and no CAFC appeal because there has been no underlying PTAB decision.

Estoppel landscape — a clean slate. Because no IPR/PGR/CBM has been instituted, 35 U.S.C. § 315(e)(2) estoppel has never attached to anyone. Every prior-art ground under pre-AIA §§ 102/103 (the patent's priority chain runs back to 2004-11-02 via parent US10/980,046 → US7391858B1, with this CIP filed 2007-10-29) is still available to any defendant, in district court under § 282 or before the PTAB. The only timing trap is § 315(b): a petition must be filed within one year of service of a complaint alleging infringement of this patent on the would-be petitioner or its real party in interest/privy. Several of Lab Technology's 2024–2025 cases against this patent were voluntarily dismissed very early (often before answer) — meaning defendants in those cases may have been served and thus may have already burned part or all of their 315(b) clock, while never-sued parties retain a full, unstarted clock. Anyone currently in suit (e.g., the more recent 2025 filings) should calendar the one-year-from-service deadline immediately if an IPR is on the table.

Pattern signals. This patent is asserted by Lab Technology LLC (originally TP Lab Inc.), a classic patent-assertion entity. Its 2024–2025 enforcement campaign against this patent has been characterized by rapid voluntary dismissals — often within weeks and typically without prejudice (e.g., the AT&T E.D. Tex. 2:24-cv-00412 matter dismissed 2024-07-03; the Zoom D. Colo. 1:24-cv-01711 matter dismissed 2024-07-01; the 3CX S.D. Fla. 1:25-cv-22704 matter dismissed with prejudice 2025-08-20). No single petitioner has filed multiple IPRs on this patent (there are none), and the patent owner has never defended a PTAB trial on it. Notably, Unified Patents is actively tracking the Lab Technology portfolio — it has run PATROLL prior-art crowdsourcing contests on sibling Lab Technology patents (e.g., US 8,498,388 and US 8,503,973) and filed an ex parte reexamination (not an IPR) against US 8,498,388 in 2024-11-27 — but no Unified Patents challenge to US 8,483,102 was located. That is a meaningful absence: for a patent that has now been asserted against AT&T, Zoom, Lumen, Zendesk, 3CX, u-blox, and others, the total lack of PTAB activity suggests either that defendants are resolving cases before the investment is justified, that prior-art hunting is still underway (Unified's contests often precede a petition by many months), or that the quick-dismissal strategy is deliberately keeping defendants under the 315(b) radar. Expect that this could change; the patent's age (pre-AIA, priority 2004), its broad "username-as-voice-identity" claim language, and its heavy assertion campaign make it a plausible future IPR target.

Recommended next steps

1. Confirm the zero-proceeding finding at the authoritative source. Query the USPTO PTAB E2E / ODP trial-search interface (proceeding search by patent number 8483102) and the USPTO Patent Center file history yourself before making representations to a court or client. The ODP ingest and my searches returned nothing, but docket databases can lag by days for brand-new petitions.

2. If you are a defendant in active litigation (or expect to be served): treat the § 315(b) one-year bar as the controlling deadline. File any IPR petition within one year of service of the complaint on you (or on any RPI/privy). Do not assume a plaintiff's voluntary dismissal resets that clock for a served defendant. If Lab Technology's pattern holds and your case is dismissed early without prejudice, note that the plaintiff keeps refiling rights — an IPR (if filed in time) is the only mechanism that strips claims in rem and binds the patent owner in every later forum.

3. Run the prior-art analysis now, with an eye to the specification's own admissions. The patent's "Related Arts" section candidly describes conventional multi-number reachability, call-forwarding between office/cellular/home phones, and time-based forwarding — fertile ground for § 103 combinations from the 1990s–2004 window (the same era as the art the examiner already cited: US 5,737,403; US 6,539,090; US 6,898,274; US 2004/0091095; US 7,171,190). Because no IPR has been filed, none of those references has been tested before the Board, and § 315(e)(2) estoppel is a non-issue for grounds built on them.

4. If the goal is quick claim kill-through rather than litigation leverage: the absence of any PTAB history means all 20 claims are presumptively valid but entirely unproven. A well-constructed IPR on independent claims 1 and 11 (the "username" routing claims) would, if successful, take down the entire claim tree, since every dependent claim (2–10, 12–20) ultimately depends on claims 1 or 11. If your demand letter cites only dependent claims, an IPR narrowing strategy may still be warranted — but confirm which claims are actually charted before committing.

5. Monitor Unified Patents and the remaining 2025 cases. Unified's established pattern with Lab Technology (reexam on US 8,498,388; contests on US 8,498,388 and US 8,503,973) and its litigation-tracking of this very patent suggest it may be developing the file. If Unified (or a member) files an IPR on US 8,483,102, institution would be decided within roughly six months of filing, with a statutory FWD deadline one year from institution — and any defendant sued after such a petition is filed can ride the resulting estoppel and any adverse-claim rulings.

Sources: USPTO ODP PTAB ingest (canonical, empty for this patent); Google Patents record for US8483102B1 (fetched 2026-09-08) including litigation and legal-event data; Unified Patents litigation/PTAB insight pages (2024–2025) confirming activity against sibling Lab Technology patents but none against US 8,483,102; PatSnap/Unicourt summaries of the district court cases. I located no PTAB Final Written Decision, institution decision, settlement, or CAFC appeal to cite — because none exists for this patent as of the search date.

I'll research the assignment chain for US 8483102 using multiple sources. Let me start with several parallel searches.

I have good initial data. Now let me dig into the specific USPTO assignment records and the entities involved.

Inventors

• Chi Fai Ho — Palo Alto, CA. Principal/employee at the time of filing: TP Lab, Inc., which he founded in 2004. Prior roles: Senior Director of Business Strategy at Nokia, VP Engineering at Amber Networks (acquired by Nokia), CTO of the Ethernet Product Division at Vitesse Semiconductor, VP Engineering at Tidal Networks; earlier founded IPLearn (1997) and Spear Multiprocessing. TP Lab's own "About Us" page describes him as founding TP Lab "with a focus on invention with licensing to monetize the Lab's ideas" — i.e., the lead inventor is also the founder of a patent-monetization shop, not an operating company.
• Shin Cheung Simon Chiu — Palo Alto, CA. Co-inventor at the time of filing: TP Lab, Inc.; he appears as co-inventor on numerous TP Lab telecom patents (e.g., US 7,778,630, US 7,840,769, US 7,986,638, US 8,032,421).

Unusual pattern check: Not present in the classic sense. Both inventors assigned their rights to TP Lab, Inc. (recorded Reel 020027/0818, executed 2007-10-27 to 2007-10-29) — a company the lead inventor founded. There is no "inventors fled the assignee within 12 months of filing" pattern; rather, the inventors are the assignee's principals, and TP Lab was set up from day one as an invention-and-licensing entity.

Original assignee

• TP Lab, Inc. (Palo Alto, California) — the entity named on the issued patent and original assignee of record.
• Line of business / products: No evidence of any product embodying the claims. TP Lab's own website states it was founded (2004) with "a focus on invention with licensing to monetize the Lab's ideas," in areas including Internet-telecommunication convergence. It is an invention/licensing studio, not a practicing entity. (Per its founder's bio it had filed 80+ applications; Patent Leaderboard credits Chi Fai Ho with 234 patents, 136 through TP Lab.)
• Current status: Still apparently operating as a filer — third-party assignee profiles show TP Lab grants as late as 2022-11-08. It is not in bankruptcy or dissolved. It transferred this patent (and evidently a broader portfolio, including family member US 9,413,895) to Lab Technology LLC effective 2024-01-15 (recorded Reel 067830/0076, 2024-06-25).

Assignment timeline

Only two recorded assignments appear in the USPTO/Google Patents legal-event record for this patent number. The correspondent-of-record field for both recordings could not be retrieved in this session — the USPTO Assignment Center pages did not resolve through the available search tools. That field should be verified directly at assignmentcenter.uspto.gov; I have not fabricated it. The litigation-counsel observation below (Rabicoff Law LLC) is a separate, confirmed data point from court dockets.

• 2007-10-27 to 2007-10-29 (executed) / recorded 2007-10-29 — Reel 020027/0818

  • Conveyance: Assignment (of Assignors' Interest)
  • Assignor: Chi Fai Ho; Shin Cheung Simon Chiu (inventors)
  • Assignee: TP Lab, Inc.
  • Correspondent: Not retrievable in this session — verify at assignmentcenter.uspto.gov.
  • Context: Original inventors-to-company assignment, recorded the same day the CIP application US11/926,390 was filed (2007-10-29) — routine.

• 2024-01-15 (effective/executed) / recorded 2024-06-25 — Reel 067830/0076

  • Conveyance: Assignment (of Assignors' Interest)
  • Assignor: TP Lab, Inc.
  • Assignee: Lab Technology LLC (New Mexico LLC; per the Lumen complaint, principal place of business at 1209 Mountain Rd Pl NE STE n, Albuquerque, NM 87110)
  • Correspondent: Not retrievable in this session — verify at assignmentcenter.uspto.gov. Flag for follow-up: Lab Technology's litigation counsel across its 2024–2026 suits is Isaac Rabicoff of Rabicoff Law LLC (seen in E.D. Tex., W.D. Tex., D. Del., S.D.N.Y. dockets); if Rabicoff Law is also the assignment correspondent on Reel 067830/0076 (or on sibling-family recordings), that would satisfy the repeat-correspondent signal — but I cannot confirm that from data available here.
  • Context: Portfolio transfer from a licensing shop (TP Lab) to a litigation-active LLC, executed ~4 months before the first infringement complaints asserting this patent were filed in 2024 (E.D. Tex. 2:24-cv-00412, E.D. Tex. 2:24-cv-00830, D. Colo. 1:24-cv-01711 per the Google Patents record), and ~15 months before the W.D. Tex. Lumen suit (7:25-cv-00172, filed 2025-04-17), which expressly asserts the '102 patent.

Note: Google Patents legal events for US8483102B1 show exactly these two assignment events (plus maintenance-fee events in 2016, 2020, 2025 and the 2024 grant/issuance bookkeeping). Sibling applications (parent US10/980,046 → US7,391,858; child US13/910,789 → US9,413,895) carry the same TP Lab → Lab Technology LLC chain per Unified Patents family data, but I did not independently retrieve their separate reel/frame entries.

Timeline diagram

timeline
    title Ownership of US 8483102
    2004 : Priority application filed by TP Lab
    2007 : CIP application filed
         : Inventors assign to TP Lab Inc
    2013 : Patent issued
    2024 : TP Lab assigns to Lab Technology LLC
         : First infringement suits filed
    2025 : More suits filed nationwide

NPE / troll-pattern signals

1. Shell-entity transfer — Present (with the caveat that the assignor was itself non-practicing). The patent moved to Lab Technology LLC, a New Mexico LLC with no identified products, a small-suite Albuquerque address (1209 Mountain Rd Pl NE STE n, 87110), and no business footprint beyond patent enforcement — via Reel 067830/0076 (effective 2024-01-15). The "operating company → licensing LLC" shape is softened because TP Lab was itself an invention/licensing entity, but the current assignee meets the licensing-only-LLC indicators. Note a data conflict: ExParte tags Lab Technology as "Operating Company," but PatSnap/RPX and the litigation record characterize it as a patent-assertion entity; the record contains no product evidence, so I credit the PAE characterization.

2. Known asserter in the chain — Present. Lab Technology LLC is a high-frequency plaintiff tracked by RPX Insight (e.g., Lab Technology LLC v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.), W.D. Tex. 6:24-cv-00331, filed 2024-06-21) and appearing on the Unified Patents litigation portal, and is characterized as a "Patent assertion entity" by PatSnap. Its 2024–2026 docket includes suits against Microsoft, Verizon, Cisco, Lumen, Zendesk, 3CX, u-blox, Keysight, Everbridge, Solera, and others. The '102 patent is expressly asserted in Lab Technology LLC v. Lumen Technologies, Inc. (W.D. Tex. 7:25-cv-00172, ¶¶ 6, 11–16) and is named on the Google Patents litigation list (E.D. Tex. 2:24-cv-00412, 2:24-cv-00830, D. Colo. 1:24-cv-01711, W.D. Wis. 3:25-cv-00303, E.D. Va. 1:25-cv-01234, S.D. Fla. 1:25-cv-22704).

3. Repeat correspondent across the chain — Unclear / not verifiable in this session. I could not retrieve the assignment correspondent names on Reels 020027/0818 or 067830/0076. Separate from the assignment record, litigation counsel Rabicoff Law LLC (Isaac Rabicoff) recurs across Lab Technology's many 2024–2026 cases (E.D. Tex. 2:24-cv-00323; W.D. Tex. 6:24-cv-00338; S.D.N.Y. 7:26-cv-00374; D. Del. 1:25-cv-01355). Whether Rabicoff Law also files the USPTO recordings is the specific check that would upgrade this signal — do not infer it without the Assignment Center correspondent field.

4. Cascading transfers — Not present. Only two recorded assignments, 17 years apart (2007 inventors→TP Lab; 2024 TP Lab→Lab Technology). No chained-LLC conveyor belt in <24 months.

5. Pre-litigation transfer — Present. Assignment effective 2024-01-15 (Reel 067830/0076); first infringement complaints naming the '102 patent were filed in 2024 (E.D. Tex. 2:24-cv-00412 and 2:24-cv-00830; D. Colo. 1:24-cv-01711, per the Google Patents litigation list) — i.e., within roughly 3–6 months. The transfer placed enforcement rights (and standing/venue) in the asserting entity immediately before the suit wave.

6. Bankruptcy fire-sale — Not present. No bankruptcy proceeding involving TP Lab or Lab Technology is in the record; TP Lab continued obtaining patents through at least 2022.

7. Privateering — Not present / unclear. TP Lab is not an operating company with products or direct competitors in the sense privateering contemplates; the transfer is from one monetization entity to a litigation-active LLC rather than an operating company outsourcing enforcement against rivals.

8. Defensive aggregator (anti-NPE) — Not present. The chain terminates at Lab Technology LLC, a plaintiff. No RPX, AST, LOT, Unified Patents, or OIN involvement; this patent is being asserted, not neutralized.

Verdict

NPE — high confidence.

Two strong signals drive this: (1) the current assignee, Lab Technology LLC, is a non-practicing, litigation-only LLC that has filed a dozen-plus infringement suits since taking the portfolio via Reel 067830/0076 (effective 2024-01-15), and is tracked as a patent-assertion entity by RPX Insight and Unified Patents; and (2) the transfer was timed immediately before the 2024 assertion wave (first '102 suits filed in E.D. Tex. and D. Colo. in 2024), consistent with a standing/venue-arranged transfer-to-asserter. The original assignee TP Lab was itself founded expressly as an invention-and-licensing monetization shop (per tplab.com), so this is a licensing-entity-to-assertion-LLC chain, not an operating-company assertion.

Verification link: https://assignmentcenter.uspto.gov/ (search patent number 8483102). The correspondent-of-record fields for Reels 020027/0818 and 067830/0076 should be pulled from that system to test the repeat-correspondent signal; they were not retrievable through the tools available in this session and are the one gap in an otherwise complete record.

I have reached the tool-use limit for this session, so I'll answer based on the patent record already in hand plus the citation data retrieved. Note upfront: my "USPTO database" queries resolved through Google Patents/USPTO-mirror records (patents.google.com, uspto.report, patentimages.storage.googleapis.com), which consistently identify U.S. Patent 8,483,102 B1 (application 11/926,390) with the title System and method for mapping a voice identity across multiple telephony networks with time attributes. No similar-numbered patent was substituted.

Scope and legal framework

• Patent under analysis: US8483102B1 (filed Oct. 29, 2007; issued July 9, 2013; priority claimed to parent US10/980,046 filed Nov. 2, 2004 — the '102 is a continuation-in-part of that parent, which issued as US7391858B1).
• Applicable statute: Because the application was filed before March 16, 2013, the pre-AIA version of 35 U.S.C. § 102 governs. The relevant subsections are § 102(a) (knowledge/use/patent/printed publication before invention), § 102(b) (patented or described in a printed publication more than one year before the effective U.S. filing date), and § 102(e) (U.S. patent application filed by another before the invention date).
• Anticipation standard (caveat): Anticipation under § 102 requires a single reference disclosing every claim limitation, arranged as in the claim. My analysis below identifies, for each reference, which claim limitations it appears to disclose and therefore which claims it could potentially anticipate as a technical matter; whether it in fact anticipates is a legal conclusion requiring claim construction and, for this CIP, a determination of which claims are entitled to the Nov. 2, 2004 priority date (for § 102(b) timing) versus only the Oct. 29, 2007 filing date.

The claimed subject matter centers on: (1) a policy processor coupled to telephony switches; (2) a stored voice-identity mapping policy having multiple search voice identities → target voice identities, applicable to a plurality of users; (3) time attributes governing validity; (4) the voice identity, search identity, and target identity each being a username; and (5) routing the call using the username (independent claims 1 and 11). Dependent claims add: PBX/PSTN/VoIP/wireless networks (2, 12); processor implementation forms (3, 13); IM-based VoIP with the username being an IM or e-mail identity (4–5, 14–15); corporate VoIP with the username being an employee computer identity (6, 16); a telephone operator providing multiple voice services (7–9, 17–19); and transitive mappings across three phone systems (10, 20).

A. References cited on the face of US8483102B1 ("Patent Citations" — the five primary references)

All five are marked "*" (cited by examiner) on the Google Patents record.

1. US5737403A — "Interaction of routing features in a telephone system"

Description. Analyzes and implements interactions of call-routing features by classifying each feature as a "telephone feature" (applies to a telephone number representing a telephone) or a "subscriber feature" (applies to a telephone number representing a subscriber/person). It expressly handles follow-me vs. delegate forwarding, recursive invocation of routing features, and forwarding chains of any length (e.g., forward from phone 1 → phone 2 → phone 3), with each hop's forwarding logic dependent on whether the "forwarded-to" number represents a person or a telephone.

Potential § 102 relevance to '102 claims. This is the closest art on the transitive mapping chain concept. The reference's recursive forwarding chain (a target number that is itself subject to forwarding) maps well onto the limitation in claims 10/20: a first search voice identity on a first phone system mapped to a first target on a second phone system, which is then a second search identity mapped to a second target on a third system. It also discloses routing features applied at switches and, arguably, "subscriber-representing" identifiers that function like a per-person (per-user) identity. However, the '737 reference (i) does not disclose a stored policy having multiple search identities applicable to a plurality of users, (ii) does not disclose time attributes conditioning forwarding validity, and (iii) routes to telephone numbers, not to usernames as the routing identifier. Potentially anticipates: portions of claims 10 and 20 (transitive chain) if the username/time limitations were read as not required or were separately met — but as a single reference it most likely fails to anticipate the full claims 1/11 or 10/20. Most probative as: § 102(b) art against the chaining feature; it is best used to attack claims 10/20 in combination with other prior art (obviousness under § 103) rather than as a clean single-reference anticipation.

2. US6539090B1 — "Generalized arrangement for routing telecommunications calls"

Description. Proposes a generalized routing architecture that replaces per-switch number translation with a centralized database that maps a customer identifier — explicitly including an Internet name (e.g., an e-mail address) or other "handle" — to routing/translation information (analogous to the way an 800-number database maps to a POTS number, or DNS maps a name to an IP address). The disclosure expressly motivates assigning such handles to customers for routing over the PSTN and to special destinations (announcements, mailboxes, prompts).

Potential § 102 relevance to '102 claims. This is the strongest single-reference art on the "username/identity as a routable identifier" concept that pervades claims 1 and 11 ("voice identity, the given search voice identity, and the given target voice identity each comprises a username"; "routes the call using the username"). The reference discloses a database lookup translating an identifier (e.g., an e-mail address, i.e., a username-type handle) to route a telecommunications call. Against claim 1/11, however, the reference does not disclose: a plurality of search identities applicable to a plurality of users within a per-user mapping policy; time attributes controlling validity; or a policy processor returning the target identity itself as a username for downstream routing (the '090 reference translates a handle into a network address/number rather than chaining username-to-username). Potentially anticipates: no full independent claim standing alone, but it is highly probative against the username-recitation in claims 1, 5, 11, 14–15 and would be a primary § 102(b) reference (published 2003, well before both the 2004 priority date and the 2007 filing date).

3. US20040091095A1 — "Locale based call forwarding with automated creation of new locales"

Description. Discloses call forwarding controlled by the user's physical locale. A wireless network tracks recent locations of the user's mobile device; the system compares recent locations to historical location records that define a "locale"; if no matching locale exists, it automatically creates a new locale record; and it forwards calls to a telephone number based on the detected/current locale. User records, phone-number records, call-forwarding records, and forwarding rules are stored in persistent storage, with administration through a web browser/application server.

Potential § 102 relevance to '102 claims. Relevant to the general notion of automated, condition-driven forwarding selection to a stored destination and to user-customizable forwarding records (which parallels the '102 policy-editing architecture of its FIG. 3). The condition used here is location, not time, so it does not disclose the "time attributes" element of claims 1/11; it also does not disclose multi-user policy mapping or username-based identities/routing. Potentially anticipates: none of the full independent claims standing alone. It is § 102(b) art (published May 2004) and could support an § 103 obviousness combination for the policy-storage/customization and condition-triggered-forwarding features of claims 1/11. Published before the '102 priority date (Nov. 2, 2004), so it is available as § 102(a)/(b) art.

4. US6898274B1 — "Method and apparatus for adaptive time-based call routing in a communications system"

Description. A communications-system routing method in which a subscriber specifies a call-routing schedule based on the current time of day, and also specifies a list of functions each tied to a different subscriber activity. Incoming calls are routed per the time-of-day schedule unless function-based routing is active and a function is selected; when selected, the function overrides the schedule and the call is routed to a sequence of destinations associated with that function. The system monitors routing results and automatically modifies the routing information for subsequent calls. Architecture includes SCP-based (intelligent network) elements.

Potential § 102 relevance to '102 claims. This is the single strongest reference on the time-attribute feature ("time attributes indicating when the voice identity mapping policies are valid," claims 1 and 11). It expressly discloses time-of-day/day-based routing schedules stored per subscriber, selection among scheduled destinations, and routing to a defined destination sequence. Against the full claims 1/11 it lacks: (i) a "voice identity mapping policy" framed as search→target voice identities applicable to a plurality of users (the Nortel schedule is per-subscriber), and (ii) the username identity/routing limitation. Potentially anticipates: the time-validity limitations of claims 1 and 11 and the conditional-routing concept generally; not the full claims standing alone. As § 102(b) art (published May 24, 2005 — after the Nov. 2, 2004 priority date but before the Oct. 29, 2007 filing date), its availability depends on whether the relevant claims are entitled to the 2004 parent priority date: if they are, this reference is not § 102(b) prior art (it published <1 year after Nov. 2, 2004 — actually, note: publication May 24, 2005 is about 6.5 months after Nov. 2, 2004, so it is within one year of the priority date and would not be a § 102(b) bar against priority-date-entitled claims; it could still be § 102(a)/(e) art if the invention was made after its publication/filing). If the username-related claims are held not entitled to the 2004 priority date (CIP subject-matter support issue), the § 102(b) bar date shifts to Oct. 29, 2006 and this reference becomes squarely available § 102(b) art. This timing nuance makes '8274 one of the most important references in the file history.

5. US7171190B2 — "Intelligent messaging"

Description. (Based on the bibliographic record and citation context; full text was not retrievable within this session's search budget.) The title and assignee indicate a system for routing communications/messages intelligently — in Oracle's product line of that era, this covers unified messaging with routing of calls/messages to message stores and destinations based on rules, including message-deposit handling. I could not verify the complete disclosure contents, so characterization here is lower-confidence than for the other four references.

Potential § 102 relevance to '102 claims. Given the '102 specification's repeated treatment of voice mail as a routable "voice identity" (the spec states the voice mail number can be the user's voice identity and that the policy can route to "a designated voice application such as voice mail"), an intelligent-messaging routing reference is potentially relevant to the target voice identity being a voice-application/mailbox destination (claims 1, 11 and the "voice mail" embodiments). Because it published Jan. 30, 2007 — after the Nov. 2, 2004 priority date but before the Oct. 29, 2007 CIP filing date — and was filed June 25, 2003 (before the parent's priority date), it is best characterized as potential § 102(e) prior art (U.S. application by another filed before the invention date) and as § 102(b) art only if the claims are not entitled to the 2004 priority date. Potentially anticipates: no full claim on the available record; flagged here because its late publication date relative to the CIP filing makes it a likely examiner tool against CIP-added subject matter (notably the claim amendments reciting "username" routing, which appear to be the CIP's added scope).

B. Family-level citations ("Family Cites Families" — six additional references)

These six appear in the Google Patents "Family Cites Families" list, meaning they were cited during prosecution of related family members (parent US7391858B1 and/or continuation US9413895B1) rather than on the face of the '102 patent itself. They are not formal "citations of record" against the '102 patent, so I flag them as secondary:

1. JPH0779285A — Fujitsu Ltd., "Switch control system," filed Sept. 6, 1993, published Mar. 20, 1995. Japanese switch-control art; general call-control background.
2. US5920404A — Novell, Inc., "Method and system for dynamic control of a messaging environment from a facsimile processor," filed Mar. 15, 1996, published July 6, 1999. Messaging-environment control; relevant to routing to messaging/voice-mail destinations.
3. US6072862A — Srinivasan, "Adaptable method and system for message delivery," filed July 2, 1996, published June 6, 2000. Adaptable message delivery; relevant to destination-selection based on user context.
4. US20040057561A1 — Gilbert, "System and method for message delivery to a busy called party," filed Sept. 19, 2002, published Mar. 25, 2004. Message delivery on busy; relevant to voice-mail routing.
5. US8458277B2 — Verizon Business Global LLC, "Method and system for providing universal relay services," filed Jan. 22, 2004, published June 4, 2013. Note: published after the '102 patent issued (June 4, 2013 vs. July 9, 2013 — actually before issue date but after the '102's filing), so it cannot be § 102 prior art against the '102 claims; it is cited only against family members and is legally irrelevant as § 102 art here.
6. CN101064661B — Huawei Technologies, "Method and apparatus for notifying user to complement service," filed Apr. 29, 2006, published Aug. 24, 2011. Foreign-language art; filed/published after the '102 priority date; cannot be § 102(a)/(b) prior art against priority-date-entitled claims (and only potentially § 102(a) if invention occurred after its publication — implausible for the '102).

C. Synthesis: which references most plausibly anticipate which claims

Overall prior-art posture: No single cited reference appears, on the available record, to disclose the complete combination of (multi-user voice-identity mapping policy + time attributes + username-based search/target identities + switch routing using the username) required by claims 1 and 11 — so a clean § 102 anticipation of the independent claims by any one of these references is unlikely. The Nortel '8274 reference is the most threatening to the time-attribute limitation, the Lucent '090 reference is the most threatening to the username limitation, and the AT&T '403 reference is the most threatening to the transitive-chain dependent claims (10/20). The realistic invalidity theories against the '102 patent would therefore be § 103 obviousness combinations (e.g., '8274 + '090, or '403 + '090), rather than single-reference § 102 anticipation, unless claim construction narrows the independent claims in a way that lets one reference cover all limitations.

D. Caveats and confidence levels

• Full-text verification: I directly retrieved substantive content for US5737403A, US6539090B1, US20040091095A1, and US6898274B1 (abstracts, claims, and detailed excerpts). For US7171190B2 I could only confirm bibliographic data and title from the citation record; its substantive disclosure description is lower-confidence and should be verified against the full text before it is relied upon.
• "Family Cites Families" references are not of record against the '102 patent itself; per your instruction to interpret identifiers literally, I have listed them separately and noted that US8458277B2 and CN101064661B post-date the '102's priority/filing in ways that make them non-art for § 102 purposes.
• Anticipation determinations are legal conclusions. The claim-element mapping above is a technical assessment of what each reference discloses; a § 102 analysis also requires (a) claim construction (particularly of "username" and "voice identity mapping policy"), and (b) resolution of which '102 claims are entitled to the Nov. 2, 2004 parent priority date — a live question for a CIP whose amended claims added the username-recitation. That priority-date issue directly controls whether US6898274B1 and US7171190B2 are available as § 102(b) art.

Obviousness Analysis Under 35 U.S.C. § 103

U.S. Patent 8,483,102 B1 ("System and method for mapping a voice identity across multiple telephony networks with time attributes")

Analyst: Technical patent analyst | Date: April 26, 2026
Scope: Claims 1–20, analyzed against the prior-art references listed in the patent's own citations (the "Prior Art section" of the Google Patents record reproduced in the case file).

I. Governing framework and key caveats

Section 103 forbids a patent if the differences between the claimed subject matter and the prior art are such that the 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). Under Graham v. John Deere, the inquiry considers (1) the scope and content of the prior art; (2) the differences between the prior art and the claims; (3) the level of ordinary skill; and (4) objective indicia. Under KSR Int'l Co. v. Teleflex, a combination of known elements is obvious when the prior art provides a reason, suggestion, or predictable motivation to combine them, and common sense may supply the missing instruction.

Priority-date caveat. This patent (filed Oct. 29, 2007) is a continuation-in-part of US 10/980,046 (filed Nov. 2, 2004, issued as US 7,391,858 B1). Claim language reciting that each voice identity "comprises a username" and the VoIP/IM-based dependent claims may be new matter relative to the parent, so their effective prior-art date could be as late as Oct. 29, 2007. This matters only for references published between Nov. 2, 2004 and Oct. 29, 2007. As shown below, every primary reference in the proposed combinations is prior art under pre-AIA § 102(a)/(b)/(e) against both dates:

• U.S. patents filed before Nov. 2, 2004 are § 102(e) art even against parent-priority claims: US 5,737,403 (filed 1995); US 6,539,090 (filed Oct. 6, 1998); US 6,898,274 (filed Sep. 21, 1999); US 7,171,190 (filed Jun. 25, 2003); US 8,458,277 (filed Jan. 22, 2004).
• Published applications/patents published before Nov. 2, 2004 are § 102(a)/(b) art against both dates: US 2004/0091095 A1 (published May 13, 2004); JPH0779285A (1995); US 6,072,862 (2000); US 5,920,404 (1999).
• CN101064661B (filed Apr. 29, 2006; published ~2007) is § 102(a)/(b) art only against claims that cannot claim the Nov. 2, 2004 parent priority date; it is the least useful reference and is not relied on in the primary combinations.

Evidence caveat. I verified the substance of four references from live sources: US 6,898,274 (Nortel, via USPTO grant text), US 2004/0091095 (IBM, via the published application PDF and RPX abstract), US 5,737,403 (AT&T, via Google Patents full text), and US 6,539,090 (Lucent, via Google Patents and USPTO text). Characterizations of US 7,171,190, US 6,072,862, US 5,920,404, US 8,458,277, JPH0779285A, and CN101064661B are based on their titles, abstracts, and general knowledge and are flagged as unverified where I rely on them.

II. Level of ordinary skill

A PHOSITA would be a person with a bachelor's degree in computer science, electrical engineering, or equivalent, and 2–4 years of experience in telephony systems — including PSTN switching (Class 5), PBX, mobile/wireless, and VoIP architectures — plus experience with call-routing features (call forwarding, follow-me, find-me/follow-me), centralized network databases (SCP/IN, number portability), and telephony application servers. The person would be familiar with IM-based voice services (as the specification itself acknowledges: Yahoo Messenger, MSN Messenger, AOL IM, Skype) and with per-subscriber feature programming.

III. The prior-art universe (references cited on the face of the patent)

Verified references relied on in the primary combinations:

1. US 6,539,090 B1 (Frey et al.; Lucent; filed Oct. 6, 1998; granted Mar. 25, 2003) — "Generalized arrangement for routing telecommunications calls."
   Verified. Discloses a centralized routing database (implemented as a switching control point/SCP, optionally distributed) queried by originating switches on every call. The database stores translation information for customers and returns the identity of the terminating switch/port, or for another carrier, an access switch and trunk group. Importantly, the reference identifies as a problem that "there is no facility for assigning a handle such as an Internet name to a customer being routed over the public switched telephone network," and describes the known practice of translating "an Internet name (e.g., e-mail address), or other handle ... in a database into an Internet protocol address." Its claims recite routing on an "access identification of the called party" and updating "a single database" when "telephone number or other access identifiers" change. It expressly addresses mobile customers, customers served by different carriers, and updating a single centralized database when a customer moves — so a customer's stable "identity" maps to a current network location in a shared database queried by multiple switches.

2. US 6,898,274 B1 (Galt et al.; Nortel; filed Sep. 21, 1999; granted May 24, 2005) — "Method and apparatus for adaptive time-based call routing in a communications system."
   Verified. Claim 1 discloses: "specifying a call routing schedule that is based on a current time of day"; a subscriber-specified list of "functions," each "associated with a different activity"; receiving a call and identifying call-routing information; routing "according to a current time of day utilizing said call routing schedule"; optionally overriding the schedule with "a sequence of destinations associated with the function"; monitoring routing results; and "automatically modifying the call routing information." This squarely teaches time-attribute-driven call routing to destination sequences, on a per-subscriber, programmable basis.

3. US 5,737,403 A (Laird; AT&T; filed Sep. 15, 1995; granted Apr. 7, 1998) — "Interaction of routing features in a telephone system."
   Verified. Teaches call-forwarding arrangements in which a call may be forwarded from one telephone number to another and the forwarded-to number's own routing features are then applied, creating a chain of forwarding steps (the "follow-me"/"subscriber feature" model versus the "delegate"/"telephone feature" model). The reference manages the interaction between successive routing features, addresses loops/non-termination in chained routing, and uses "the forwarded-to telephone number [as] a key or pointer to the subscriber who normally receives calls." This is a direct analog of the '102 patent's transitive-mapping and loop-prevention teaching (claims 10 and 20; spec Figs. 4a–4b discussion of "transitive chain" and stopping on repeats).

4. US 2004/0091095 A1 (Weaver; IBM; filed Nov. 7, 2002; published May 13, 2004) — "Locale based call forwarding with automated creation of new locales."
   Verified. Teaches call-forwarding services in which a network tracks a user's recent locations, matches them against stored "historical location records identifying a locale," and forwards "a telephone number in dependence upon the ... locale," automatically creating new locale and forwarding records. It stores per-user forwarding records in data structures (locale records, call-forwarding records, phone-number records) — i.e., a database of forwarding rules keyed on a user identity/location, applied at call time by the network.

References verified only by title/metadata (secondary support):
5. US 7,171,190 B2 (Oracle; filed Jun. 25, 2003; granted Jan. 30, 2007) — "Intelligent messaging." Per its title and family record, discloses policy-driven message/call handling (follow-me-type routing of communications to a user's available destinations). Treat as secondary; unverified detail.
6. US 6,072,862 A (Srinivasan; filed Jul. 2, 1996; granted Jun. 6, 2000) — "Adaptable method and system for message delivery." Discloses delivery of messages/calls to a user across multiple addresses based on rules. Secondary; unverified detail.
7. US 5,920,404 A (Novell; filed Mar. 15, 1996) — dynamic control of a messaging environment. Secondary.
8. US 2004/0057561 A1 (Gilbert; published Mar. 25, 2004) — "System and method for message delivery to a busy called party." Secondary.
9. US 8,458,277 B2 (Verizon; filed Jan. 22, 2004) — "Method and system for providing universal relay services." Secondary.
10. JPH0779285A (Fujitsu; 1995) — switch control system. Minor.

IV. Claim construction anchors (from the specification)

Consistent with the earlier claim summary, the dispositive limitations of independent claims 1 and 11 are:

• A "voice identity" that is a designation a caller uses to reach a user, optionally (per claims 1/11) comprising a username — the specification expressly equates voice identities with VoIP/IM usernames, e-mail identities, employee computer user identities, as well as phone/extension numbers (spec, "Voice Identity" section).
• A "search voice identity" → "target voice identity" mapping stored in a policy; policies can apply to one user or a plurality of users (spec: "some voice identity mappings may be specific to individual users while other voice identity mappings may apply to a plurality of users").
• Time attributes indicating when a mapping is valid (recurring day/time windows and date ranges in the examples).
• Architecture: telephony switches perform call routing; a policy processor (integrated server, stand-alone computer, or ASIC) receives the called identity from the switch, queries the policy database, and returns a target identity; the switch completes routing.
• Claims 10/20 add transitive chains across phone systems — a target on a second phone system is itself a search identity under a second policy leading to a target on a third phone system, with loop/non-termination handling.

V. Primary obviousness combinations and motivation

Combination 1 (primary): Lucent '090 + Nortel '274 → claims 1–3, 11–13 and base elements of all claims

Element mapping:

Motivation to combine — KSR reasoning:

• The two references address the same problem from complementary angles. Lucent '090 addresses network-level routing on non-telephone "access identifications" and customer mobility through a single shared database queried by switches; Nortel '274 addresses subscriber-level routing that changes by time of day to a sequence of destinations. A PHOSITA designing a "follow the user wherever they are, whenever they are there" service would naturally graft Nortel's time-of-day destination schedules onto Lucent's centralized identity-to-location translation database: the Lucent database already must be updated when a "customer moves," and Nortel provides the rule language for when each destination applies. The combination yields exactly the claimed system: switches query a shared policy store; the store holds, for a plurality of users, mappings from a stable called identity to time-qualified target identities; the switches route to the returned target.
• There is an express design incentive in Lucent '090 itself: it identifies as a shortcoming that there is "no facility for assigning a handle such as an Internet name to a customer being routed over the public switched telephone network" — directly motivating the "username" element of claims 1/11, since Lucent's "access identification" language (claim 1) already covers usernames.
• Implementation of the "policy processor" as software in an application server, a stand-alone computer, or an ASIC (claims 3, 13) is a set of three conventional implementation choices for a network control point, all known in the art (Lucent's SCP itself is a network processor); this would have been obvious design choice with no unexpected result.

Combination 2: Add AT&T '403 to Combination 1 → claims 10 and 20 (transitive mappings across phone systems)

Element mapping:

• Claims 10/20 require: a first search identity on a first phone system → first target identity of a second phone system under a first policy; the first target identity matches a second search identity of a second policy → second target identity of a third phone system; second target ≠ first search identity.
• AT&T '403 teaches exactly this cascading-forwarding semantics: after a call is forwarded from number A to number B, "the telephone system not only forwards the first user's call to the second user's telephone number, but also forwards it from the second user's telephone number as indicated by the forwarding features activated for that telephone number" (the "follow-me"/subscriber-feature model). The reference's figures show multi-hop chains (DEL(2) → FM(3) → N O F) and its routing table (FIG. 5) resolves a call through successive forwarding steps.
• The '102 specification's own "transitive chain" description (a target identity of one mapping is the search identity of the next) is a direct paraphrase of AT&T '403's follow-me chain. The '102's loop-protection teaching ("checks if a matching voice identity mapping was used previously ... stops the processing"; "checks for repeating target voice identity") is likewise anticipated in kind by AT&T '403's handling of routing-feature interactions and non-terminating chains.

Motivation to combine: A PHOSITA combining Lucent '090 (centralized identity translation) and Nortel '274 (time-based routing) with AT&T '403 (cascading routing features) does so for the obvious reason that a user's several phones may be served by different switches/networks (Lucent '090 already routes "if the called party is served by another carrier" through inter-carrier access switches). Once forwarding spans networks, the question of whether the next network's forwarding features apply — and how to avoid loops — is the precise problem AT&T '403 solves. The combination is the predictable union of a routing database, time-based routing rules, and cross-switch feature chaining — all in the same field, all addressing call completion to a roaming user. AT&T '403's classification of features as "telephone features" vs. "subscriber features" even supplies the '102 distinction between forwarding to a line versus forwarding to a person/identity (the '102 "voice identity" notion).

Combination 3: IBM '095 as the forwarding-record/automated-provisioning reference, in place of or with Nortel '274

Element mapping and motivation:

• IBM '095 stores per-user forwarding records (locale records, call-forwarding records) in network data storage and applies them automatically at call time — an obvious alternative embodiment of the "voice identity mapping policy" data structure. It teaches automated creation of new forwarding rules based on observed conditions, which maps to the '102 policy-processing embodiment (Fig. 4b) in which the policy processor pre-computes forwarding configurations and pushes them to phone systems.
• Replacing Nortel '274's time trigger with IBM '095's location trigger, or combining time and location qualifiers, would have been obvious: Nortel '274 and IBM '095 are both "conditional call forwarding" references; time-of-day and location are the two classic conditions in the find-me/follow-me art, and the '102 specification itself uses time attributes as the condition while acknowledging the user may be "in his office," "in a meeting," "visits a branch office," or "works from home according to some schedule." A PHOSITA would understand a user's location and the time of day as interchangeable/accumulating predicates on the same forwarding rule. IBM '095's wireless-network context also supports dependent claims reciting a wireless network (claims 2, 12).

Combination 4: Add Oracle '190 / Srinivasan '862 as policy/messaging-layer support (secondary)

• If a challenger needs an additional reference teaching policy-driven, user-centric routing rules evaluated against multiple communication destinations (rather than pure telephony call forwarding), Oracle '190 ("Intelligent messaging") and US 6,072,862 (rule-based delivery of messages/calls to a user at an appropriate address) supply it. Both are in the same field (communications routing based on user state), and combining a messaging-policy engine with telephony switches and a centralized database is the routine convergence of unified-messaging and follow-me telephony that the '102 specification itself describes as conventional (multiple voice mail systems, forwarding between them). Caveat: my characterization of '190 and '862 is based on titles/abstracts only; before relying on either in a final position, counsel should verify their disclosures.

VI. Dependent-claim coverage

• Claims 2 / 12 (PBX, PSTN, VoIP, wireless): Lucent '090 expressly routes across PSTN switches, PBX-connected trunk ports, wireless/radio links, and Internet-name translation; IBM '095 is wireless-specific; AT&T '403 is a generic telephone system. A system spanning these network types in one routing fabric is Lucent's own multi-network teaching. VoIP-specific disclosure is thinner in the cited list; Lucent '090's Internet/e-mail-handle discussion plus IM-based voice being well-known general knowledge by 2004 would carry this element, but this is the dependent claim most vulnerable to challenge for lack of a squarely on-point VoIP disclosure in the listed art.
• Claims 3 / 13 (processor implementation forms): Conventional implementation choices (software on an integrated server, stand-alone computer, or ASIC), as discussed under Combination 1.
• Claims 4–6 / 14–16 (IM-based VoIP; username = IM identity, e-mail identity, or employee computer user identity): Lucent '090's "Internet name (e.g., e-mail address), or other handle" translation directly supports "e-mail account identity." "IM identity" and "employee's computer user identity" are the standard handle formats of IM-based voice services and corporate VoIP that the specification itself lists as known (Yahoo Messenger, MSN, AOL, Skype) — general knowledge that a PHOSITA would apply to Lucent's handle-routing database. This is the weakest link in the combination analysis because none of the listed references squarely discloses IM-based telephony usernames; a robust § 103 case here would need supplemental art (e.g., pre-2004 IM-voice disclosures) not present on the face of the patent.
• Claims 7–9 / 17–19 (telephone operator running a policy processor and multiple phone systems providing corporate, residential, VoIP, and mobile services): Lucent '090's centralized database expressly serves multiple carriers and treats "a different carrier ... essentially as if it were a customer," partitioning records by customer subsets and routing inter-carrier. Nortel '274 and AT&T '403 operate in multi-switch carrier networks. That one operator would administer a single policy store across a Class 5 switch, PBX, MSC, and IP telephony system (the '102 Fig. 5 architecture) is the direct application of Lucent's "single database for all customers ... served by a network" teaching, extended to a multi-service operator, with different services on different systems being the ordinary deployment those systems already represent. Obvious.
• Claims 10 / 20: see Combination 2 (AT&T '403).

VII. Differences over the prior art and the strongest counterarguments

An honest analysis must flag where the combination case is weakest, because the examiner did consider these same references and still allowed the claims:

1. The "username" requirement in every identity (claims 1, 11). The cited references are number-centric. Lucent '090 is the best hook (handles/Internet names/e-mail addresses as "access identifications"), but Lucent's primary embodiment still routes to switch/port/trunk identities, not "usernames" in the IM sense. A patentee would argue the claims require the telephony switches themselves to route using the username (claims 1, 11: "routes the call using the username"), a capability not explicitly shown in the listed art. The rebuttal: Lucent '090's claim 1 routes on an "access identification of the called party" that is not limited to a telephone number, and its specification identifies e-mail addresses/Internet handles as the paradigm access identifiers — so routing on a non-E.164 username is disclosed, not merely suggested.
2. "Applicable to a plurality of users" (claims 1, 11). Lucent '090's shared, multi-customer database supplies this for the data structure and processing elements; a patentee could argue the claims require a single policy with mappings applicable to multiple users, which the specification describes as a group policy. The rebuttal: the specification itself says a policy may be a mix of individual and group mappings, and Lucent's partitions "for subsets of customers" plus Nortel's per-subscriber schedules trivially coexist in one shared store; no inventive concept resides in aggregating per-user rules in a shared database — an obvious design choice with a predictable result.
3. Time attributes as part of the stored mapping record. Nortel '274 discloses time-based routing schedules, and IBM '095 discloses stored forwarding records, but neither stores a time-validity attribute on an identity-to-identity mapping record exactly as claimed. The rebuttal: this is at most a difference in data-record format (adding a validity field to a forwarding record), which is a textbook obvious variation; Nortel's schedules are, functionally, time attributes on destination rules.
4. Transitive chains across three phone systems with a "second target different from the first search identity" (claims 10, 20). AT&T '403 discloses multi-hop chains and even distinguishes telephone-versus-subscriber features, but the specific three-network, two-policy formulation is an implementation detail of applying AT&T's follow-me semantics in Lucent's multi-carrier network — predictable and conventional.

VIII. Secondary considerations

No objective indicia of non-obviousness appear in the record before me (no evidence of long-felt need, industry copying, licensing, or unexpected results was identified in the litigation or prosecution materials summarized in the prior sections). The reference to the specification's own "Related Arts" section confirms the problem — callers dialing multiple numbers and leaving redundant voice mails — was a well-known, long-standing nuisance, and every building block (call forwarding, time-of-day routing, centralized translation databases, follow-me chaining) was mature by 2004. That context favors an obviousness finding.

IX. Bottom line

• Claims 1–3 and 11–13 are the strongest § 103 targets, via Lucent '090 + Nortel '274 (centralized identity-to-destination database queried by telephony switches, populated with time-qualified per-user forwarding rules, routing on non-telephone "access identifications"/usernames). IBM '095 is a natural substitute or addition for the forwarding-record and automated-provisioning elements.
• Claims 10 and 20 (and the corresponding transitive-mapping disclosures throughout) fall under Combination 2 adding AT&T '403, which squarely teaches cascading follow-me forwarding and loop handling.
• Claims 7–9 and 17–19 are supported by Lucent '090's multi-carrier, partitioned, single-database architecture applied to the conventional multi-service operator plant of Fig. 5.
• The principal vulnerability in any § 103 case is the IM/VoIP-username limitation of claims 4–6 and 14–16 (and the "username" recitation in claims 1/11): the references listed on the face of the patent provide only partial support (Lucent's e-mail/handle language). A petitioner would need to supplement with pre-2004 IM-based-voice or corporate-VoIP-user-identity art not present in the patent's citation list, or rely on Lucent '090 plus well-documented general knowledge.

This analysis is an advocacy framework, not a final validity opinion; before it is used in any proceeding, the unverified characterizations (especially of US 7,171,190, US 6,072,862, US 5,920,404, and US 8,458,277) should be confirmed against the actual disclosures, and the effective priority date of each claim (parent versus CIP new matter) should be resolved from the prosecution history.