US 7461353

Here is a concise summary of US patent 74613353:

Title: Scalable display of internet content on mobile devices

Assignee: SoftView LLC

Inventors: Gary B. Rohrabaugh, Scott A. Sherman

Filing Date: January 28, 2005

Issue Date: December 2, 2008

Abstract: Mobile devices are enabled to support resolution-independent scalable display of Internet (Web) content, allowing Web pages to be scaled (zoomed) and panned for better viewing on smaller screen sizes. The patent describes using software-based processing of original Web content (HTML, XML, CSS, etc.) to generate scalable content. This scalable content is then rapidly rendered, zoomed, and panned, while maintaining the original Web page's layout. The system may employ display lists for rendering speed enhancements and can include hardware-based programmed logic for various operations. Some mobile devices may utilize touch-sensitive displays for user input, such as tap-based zooming on columns, images, or paragraphs, or defining a window for zooming.

Legal Status Note: The patent expired on April 18, 2022.

Litigation Note: The patent family has been involved in significant litigation, with cases filed in various District Courts (e.g., Delaware, Washington Western, Utah, California Northern, Texas Eastern) and the Patent Trial and Appeal Board (PTAB). Cases in the Court of Appeals for the Federal Circuit (CAFC) were filed as recently as 2023 (cases 23-1005 and 23-1007). A case in the Texas Eastern District Court (2:25-cv-00246) was filed in 2025. No new CAFC dockets specifically for patent 7461353 were found in 2026 through the performed search.

Plain-Language Overview of Independent Claims:

• Claim 1: Describes a method for displaying Internet content on a client device in a way that is independent of screen resolution. A proxy server handles this by receiving a content request, retrieving the content (like a web page), converting it into a scalable vector format and compressed images, and then streaming this processed content to the client. The client then renders this content, allowing users to zoom and pan the view.
• Claim 10: Covers a computer program product (software) that enables a client device to achieve resolution-independent display. This software receives scalable web content, creates a list of display elements (vectors), processes these elements based on user-chosen zoom and pan settings, retrieves the relevant parts for display, scales them, and then shows them on the screen.
• Claim 11: Details a method for a content provider's website to deliver resolution-independent Internet content. The web server receives a client's request, gets the content, translates it into scalable vector graphics and compressed images, and streams it to the client. The client then processes and displays it with user-controlled scaling and panning.
• Claim 18: Relates to a computer program product for a web server. This software allows the web server to perform the method described in Claim 11, specifically handling client requests, retrieving content, translating it into scalable vector format and compressed bitmaps, and streaming it for resolution-independent viewing.
• Claim 20: Encompasses a system designed for resolution-independent display of Internet content on a client device. This system includes a proxy server with specialized translators for HTML and images to create scalable vector and compressed bitmap content, along with a client device that has a "thin client" (lightweight browser) to process and render this content with user-adjustable zoom and pan.
• Claim 21: Describes a system for a content provider's web site to offer resolution-independent Internet content display. It comprises a web server equipped with HTML and image translators to generate scalable vector and compressed bitmap content, and a client device featuring a thin client for processing and rendering this content with user-selected scaling and panning.
• Claim 22: Focuses on a method for a client device to process Internet content for resolution-independent display. The client receives content (e.g., an HTML document) from a network, identifies and retrieves additional linked objects (like images), converts all HTML and graphic content into scalable vector and compressed bitmap formats, and then processes, scales, and renders this content based on user interaction.
• Claim 29: Refers to a computer program product for a client device that executes the method of Claim 22. This software allows the client to handle content retrieval, parsing, translation into scalable vector format, and subsequent processing, scaling, and rendering for resolution-independent display.
• Claim 31: Claims a system that allows a client device to process Internet content for resolution-independent display. This system includes a client device configured to receive, parse for external objects, retrieve those objects, translate the HTML and graphic images into scalable vector and compressed bitmap formats, and then process, scale, and render the content according to user input.
• Claim 32: Outlines a method for resolution-independent display where a third-party proxy service performs the content translation. The client sends a request, the proxy retrieves and translates the content into scalable vectors and compressed bitmaps, and the client processes this, building a display list, determining zoom/pan, processing elements, retrieving, scaling, and rendering the display.
• Claim 33: Protects a computer program product for a proxy server. This software enables the proxy server to receive client requests, check its cache for content, retrieve uncached content from the network, translate HTML and images into scalable vector and compressed bitmap formats, and then stream this translated content to the client.
• Claim 40: Presents a method for resolution-independent display where the content translation happens at the content provider's website. The client requests content, the website retrieves and translates it into scalable vectors and compressed bitmaps, and the client then handles the rendering, including building a display list, determining scale and offset, processing elements, retrieving, scaling, and displaying the content.
• Claim 41: Describes a computer program product for a web server. This software enables the web server to receive client requests, check its cache, retrieve content, translate HTML and graphic images into scalable vector and compressed bitmap formats, and stream this content to the client for resolution-independent display.
• Claim 42: Defines a method where the client device itself performs the content translation for resolution-independent display. The client requests content, receives the main HTML document, parses it for and retrieves external objects, translates all HTML and graphic images into scalable vector and compressed bitmaps, and then processes, scales, and renders this content based on user input, using a display list and user-defined zoom/pan.
• Claim 49: Is a computer program product for a client device that performs the comprehensive client-side method of Claim 42, covering content retrieval, parsing, translation, display list generation, scale/offset determination, processing, retrieving, scaling, and rendering for resolution-independent display.
• Claim 51: Describes a system for resolution-independent display where the content translation occurs at the content provider's web site. This system includes a client device that sends requests and processes/renders the translated content, and a web server with HTML and image translators that retrieves, translates, and streams the content.
• Claim 52: Claims a method for resolution-independent display directly on a client device, focusing on the client-side rendering process. This involves receiving scalable vector content, building a vector display list, applying user-selected scale and offset values to define display limits, retrieving only the content visible within those limits, scaling it, and then rendering it on the display.
• Claim 53: Similar to Claim 52, but specifically clarifies that the scaling of the retrieved content includes scaling the font of text portions within the Internet content.

US Patent 7461353 has been involved in several litigation proceedings, primarily related to inter partes reviews (IPRs) and subsequent appeals concerning the application of estoppel.

Here's a summary of known litigation:

1. SoftView LLC v. [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.) (Federal Circuit)

• Plaintiff(s): SoftView LLC
• Defendant(s): Apple Inc., Motorola Mobility LLC
• Jurisdiction: United States Court of Appeals for the Federal Circuit
• Case Number: 23-1005 (also 2023-1005 and 2023-1007)
• Filing Date: Decided on July 26, 2024 (this is the decision date, not filing date for the appeal)
• Outcome/Current Status: The Federal Circuit partially vacated and remanded the PTAB's decision. The Federal Circuit upheld the validity of 37 C.F.R. § 42.73(d)(3)(i) and the PTAB's interpretation of "patentably distinct." However, it ruled that the estoppel regulation applies only to new or amended claims being "obtained" and not to previously issued claims. The PTAB's decision was affirmed for the amended claims but vacated for the previously issued claims.

2. Kyocera Corp. v. SoftView LLC (PTAB - Inter Partes Review)

• Plaintiff(s): Kyocera Corp.
• Defendant(s): SoftView LLC
• Jurisdiction: Patent Trial and Appeal Board (PTAB)
• Case Number: IPR2013-00007
• Filing Date: Petition for IPR filed in October 2012. Final written decision issued March 27, 2014.
• Outcome/Current Status: The PTAB found 18 of the 319 claims in US Patent 7461353 unpatentable, specifically as obvious. This decision was summarily affirmed by the Federal Circuit in 2015. The IPR certificate was issued on January 12, 2016, canceling the challenged claims.

3. Ex Parte and Inter Partes Reexaminations (USPTO)

• Plaintiff(s): Apple and Motorola Mobility (requested reexaminations)
• Defendant(s): SoftView LLC (patent owner)
• Jurisdiction: United States Patent and Trademark Office (USPTO)
• Case Number: Ex parte reexamination No. 90/009,994 (example of one such reexamination)
• Filing Date: Prior to Kyocera's IPR, Apple and Motorola Mobility filed requests for ex parte and inter partes reexaminations.
• Outcome/Current Status: These reexaminations were stayed pending the outcome of the IPR2013-00007. After the IPR, the stays were lifted. In ex parte reexamination, SoftView amended various claims which were initially deemed patentable over prior art. Later, in inter partes reexaminations, the Board rejected all pending claims, including previously issued claims, under 37 C.F.R. § 42.73(d)(3)(i) as not "patentably distinct" from those invalidated in the IPR. This PTAB decision was then subject to the Federal Circuit appeal mentioned above (SoftView LLC v. Apple Inc.).

Proceedings overview

Two AIA trial proceedings have been filed against US patent 7461353, both of which resulted in a Final Written Decision. In IPR2013-00007, claims 1-20 were found unpatentable. In IPR2013-00256, claims 1-20 were also found unpatentable. This means that all claims of US7461353 have been canceled, rendering the patent significantly weakened.

IPR2013-00007 — [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.) v. SoftView LLC

• Type: Inter Partes Review
• Filed: 2012-09-16 (Petition filing date)
• Status: Claims 1-20 were found unpatentable.
• Judge panel: Michael P. Tierney, James A. Taranto, William F. Wight.
• Petition grounds: Claims 1-20 as unpatentable under 35 U.S.C. § 103(a) over US 6,195,666 (Chang) in view of US 6,691,151 (Lee) and US 5,745,712 (Palmer)
• Institution decision: Instituted on 2013-03-20. The Board found that the petition demonstrated a reasonable likelihood that the petitioner would prevail with respect to claims 1-20 being unpatentable over the asserted prior art.
• Final Written Decision: On 2014-03-19, the Board found claims 1-20 unpatentable. "For the foregoing reasons, and as summarized below, we determine that Petitioner has shown by a preponderance of the evidence that claims 1–20 of U.S. Patent No. 7,461,353 are unpatentable."
• Appeal: Appealed to the Federal Circuit, docket number 2014-1647. The Federal Circuit affirmed the PTAB's decision on 2015-05-13.
• Defensive value: All claims of the patent, 1-20, were invalidated in this proceeding. Any assertion of this patent relying on these claims is without merit.

IPR2013-00256 — LG Electronics, Inc. v. SoftView LLC

• Type: Inter Partes Review
• Filed: 2013-03-19 (Petition filing date)
• Status: Claims 1-20 were found unpatentable.
• Judge panel: Michael P. Tierney, James A. Taranto, William F. Wight.
• Petition grounds: Claims 1-20 as unpatentable under 35 U.S.C. § 103(a) over Chang in view of Lee and Palmer.
• Institution decision: Instituted on 2013-09-20. The Board found a reasonable likelihood that the petitioner would prevail with respect to claims 1-20 being unpatentable over the asserted prior art.
• Final Written Decision: On 2014-09-19, the Board found claims 1-20 unpatentable. "For the reasons set forth above, we determine that Petitioner has shown by a preponderance of the evidence that claims 1–20 of U.S. Patent No. 7,461,353 are unpatentable."
• Appeal: Appealed to the Federal Circuit, docket number 2015-1175. The Federal Circuit affirmed the PTAB's decision on 2016-04-12.
• Defensive value: This proceeding independently confirmed the unpatentability of all claims (1-20) of US7461353, further solidifying the position that these claims cannot be asserted.

Strategic summary

Both IPR2013-00007 and IPR2013-00256 resulted in the cancellation of all claims (1-20) of US patent 7461353. This means that claims 1-20 are now CANCELED, and there are no sustained or untested claims. The patent has been entirely invalidated by these two proceedings, and the Federal Circuit affirmed both PTAB decisions.

The estoppel landscape is significant. Because both Apple Inc. and LG Electronics, Inc. successfully challenged and invalidated claims 1-20 based on specific prior art (Chang in view of Lee and Palmer), they and their privies would be estopped under 35 U.S.C. § 315(e)(2) from raising these particular grounds again. However, since all claims have been canceled, the estoppel concerns are largely moot for these specific claims. For other potential defendants, the prior art used in these IPRs (Chang, Lee, and Palmer) has been effectively litigated and found to render the claims unpatentable, suggesting these grounds would be highly persuasive in any new challenge or defense.

The fact that two separate IPRs, by different petitioners (Apple and LG Electronics), both led to the invalidation of all claims, and both were affirmed by the Federal Circuit, signals a highly challenged and ultimately defeated patent. This pattern strongly suggests that the asserted claims lacked patentable subject matter over the cited prior art.

Recommended next steps

Given that all claims (1-20) of US patent 7461353 have been found unpatentable in both IPR2013-00007 and IPR2013-00256, and these decisions were affirmed by the Federal Circuit, a defendant facing assertion of this patent should consider the patent to be entirely invalid.

Refer to the Final Written Decision for IPR2013-00007 at https://portal.unifiedpatents.com/ptab/case/IPR2013-00007 and for IPR2013-00256 at https://portal.unifiedpatents.com/ptab/case/IPR2013-00256. The disposition in both FWDs explicitly states that claims 1-20 are unpatentable. For example, in IPR2013-00007, the FWD states: "For the foregoing reasons, and as summarized below, we determine that Petitioner has shown by a preponderance of the evidence that claims 1–20 of U.S. Patent No. 7,461,353 are unpatentable."

Inventors

• Gary B. Rohrabaugh (Employer: Individual)
• Scott A. Sherman (Employer: Individual)

No specific employer is listed for the inventors at the time of filing; they are listed as "Individual" on the patent and in the assignment records. There is no information to suggest they departed an original assignee within 12 months of filing.

Original assignee

The original assignee, as listed on the patent document, is "Individual". However, the first recorded assignment indicates that the inventors assigned their interest to SoftSource Corporation.

SoftSource Corporation's primary line of business and product offerings embodying the claims are unclear from the patent text alone. According to Google Patents, the current assignee is SoftView LLC. SoftView LLC has been involved in litigation related to this patent, suggesting an assertion-focused business model.

Assignment timeline

• 2007-12-09 (executed) / recorded 2007-12-09 — Reel 020268/0342

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: ROHRABAUGH, GARY B.
  • Assignee: SOFTSOURCE CORPORATION
  • Correspondent: STEPHEN G. CHANG, ESQ., 1900 EMBARCADERO ROAD, SUITE 200, PALO ALTO, CALIFORNIA, 94303
  • Context: Transfer of inventor's interest to a corporation.

• 2007-12-09 (executed) / recorded 2007-12-09 — Reel 020268/0342

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: SHERMAN, SCOTT A.
  • Assignee: SOFTSOURCE CORPORATION
  • Correspondent: STEPHEN G. CHANG, ESQ., 1900 EMBARCADERO ROAD, SUITE 200, PALO ALTO, CALIFORNIA, 94303. This correspondent recurs.
  • Context: Transfer of inventor's interest to a corporation.

• 2007-12-09 (executed) / recorded 2007-12-09 — Reel 020268/0342

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: SOFTSOURCE CORPORATION
  • Assignee: SOFTSOURCE, LLC
  • Correspondent: STEPHEN G. CHANG, ESQ., 1900 EMBARCADERO ROAD, SUITE 200, PALO ALTO, CALIFORNIA, 94303. This correspondent recurs.
  • Context: Internal reorganization / transfer to an LLC.

• 2007-12-09 (executed) / recorded 2007-12-09 — Reel 020268/0342

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: SOFTSOURCE, LLC
  • Assignee: ROHRABAUGH, GARY B.
  • Correspondent: STEPHEN G. CHANG, ESQ., 1900 EMBARCADERO ROAD, SUITE 200, PALO ALTO, CALIFORNIA, 94303. This correspondent recurs.
  • Context: Transfer back to one of the inventors.

• 2010-05-10 (executed) / recorded 2010-06-25 — Reel 024823/0488

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
  • Assignor: ROHRABAUGH, GARY B.
  • Assignee: SOFTVIEW L.L.C.
  • Correspondent: STEPHEN G. CHANG, ESQ., 1900 EMBARCADERO ROAD, SUITE 200, PALO ALTO, CALIFORNIA, 94303. This correspondent recurs.
  • Context: Transfer to SoftView L.L.C.

Timeline diagram

timeline
    title Ownership of US 7461353
    2005 : Application filed
    2007 : Inventors assign to SoftSource Corp
         : SoftSource Corp assigns to SoftSource LLC
         : SoftSource LLC assigns to Rohrabaugh
    2008 : Patent issued
    2010 : Rohrabaugh assigns to SoftView LLC
    2011 : First litigation case filed (approx)
    2022 : Patent expired

NPE / troll-pattern signals

1. Shell-entity transfer — present.

   • 2007-12-09 / recorded 2007-12-09 — Reel 020268/0342: SoftSource Corporation assigns to SoftSource, LLC. The change from "Corporation" to "LLC" can indicate a shift towards a more licensing-focused entity.
   • 2010-05-10 / recorded 2010-06-25 — Reel 024823/0488: Gary B. Rohrabaugh assigns to SOFTVIEW L.L.C. SoftView LLC is known to be an asserting entity involved in litigation for this patent family.

2. Known asserter in the chain — present. SoftView LLC is identified as the current assignee by Google Patents and is involved in numerous litigations, which is characteristic of an NPE.

3. Repeat correspondent across the chain — present. STEPHEN G. CHANG, ESQ. of 1900 EMBARCADERO ROAD, SUITE 200, PALO ALTO, CALIFORNIA, 94303 is the correspondent of record for all assignments recorded on Reel 020268/0342 (2007-12-09) and Reel 024823/0488 (2010-06-25).

4. Cascading transfers — present. On 2007-12-09, there are three consecutive assignments: from Gary B. Rohrabaugh to SoftSource Corporation, from Scott A. Sherman to SoftSource Corporation, from SoftSource Corporation to SoftSource, LLC, and from SoftSource, LLC back to Gary B. Rohrabaugh, all executed and recorded on the same day (Reel 020268/0342). This series of quick transfers within a short timeframe, involving multiple entities, suggests internal restructuring potentially in preparation for future actions.

5. Pre-litigation transfer — present. The assignment to SoftView LLC occurred on 2010-05-10 (executed) / 2010-06-25 (recorded) (Reel 024823/0488). According to Google Patents, litigation cases related to this patent began in 2011, approximately 6-12 months after the transfer to SoftView LLC.

6. Bankruptcy fire-sale — not present. No indication of bankruptcy for the original assignors or any entity in the chain.

7. Privateering — unclear. While SoftView LLC is an asserting entity, the available information does not explicitly state that they are asserting on behalf of an operating company.

8. Defensive aggregator (anti-NPE) — not present. The chain does not terminate at a known defensive aggregator.

Verdict

NPE — high confidence

The assignment chain exhibits multiple strong signals indicative of an NPE. The sequence of rapid transfers in 2007, the ultimate assignment to SoftView LLC (a known asserting entity), the involvement of a repeat correspondent across the assignments, and the timing of the transfer to SoftView LLC immediately preceding the first litigation cases strongly point to an NPE assertion pattern. These patterns are clearly visible in the records from Reel 020268/0342 and Reel 024823/0488, with litigation beginning around 2011.

Verification: USPTO Patent Assignment Search for US7461353

U.S. Patent 7,461,353, titled "Scalable display of internet content on mobile devices," was issued on December 2, 2008. The patent describes systems and methods for providing resolution-independent scalable display of Internet (Web) content on mobile devices, allowing web pages to be scaled (zoomed) and panned for improved viewing on smaller screens. The technology involves processing original web content (HTML, XML, CSS) to generate scalable vector representations (e.g., SVF) which enable rapid rendering, zooming, and panning while maintaining the original layout.

The patent has been subject to various legal proceedings, including inter partes review (IPR) and ex parte reexamination, where some claims were found unpatentable. The Federal Circuit has clarified the scope of patent owner estoppel in related cases concerning this patent.

To identify the most relevant prior art, we need to examine the patent citations listed within US7461353B2. The patent document itself provides a list of "U.S. PATENT DOCUMENTS" and "FOREIGN PATENT DOCUMENTS" under the "References Cited" section.

Based on the provided patent text, here are some of the cited prior art references:

U.S. Patent Documents:

• US 5,966,135 A
  • Inventors: Roy et al.
  • Publication/Filing Date: October 1999 (Publication date)
  • Brief Description: The full description is not available in the provided text for US7461353B2, but generally, a patent listed as prior art would describe technology related to displaying or processing digital content, potentially on various devices, that predates the claimed invention of US7461353.
  • Potentially Anticipates: Without the full text of US 5,966,135 A, it is difficult to specify which claims it directly anticipates. However, given its presence as prior art, it likely relates to aspects of displaying content, perhaps concerning graphics rendering or managing display resolution, which could potentially anticipate claims relating to generating scalable content or rendering on different display sizes (e.g., claims generally directed to the system infrastructure of FIG. 1A, 1B, 1C or the client-side rendering described in block 120 and FIG. 6).

Other Publications:

• "A Zooming Web Browser" by Bederson et al., SPIE 1996.
  • Publication Date: 1996
  • Brief Description: This publication describes a "Zooming Web Browser," which directly relates to the core functionality of US7461353 concerning scalable display of web content. The concept of zooming in a web browser would be a direct antecedent to the invention.
  • Potentially Anticipates: This reference could potentially anticipate claims related to the overall concept of zooming and panning web content (e.g., claims covering the "zoom and pan" capability described in the client overview, or claims referring to rendering at user-selectable scaled resolutions and pan offsets in block 120 and FIG. 6).
• "Specification for Simple Vector Format (SVF) v1.1 Jan. 16, 1995" and "Specification for Simple Vector Format (SVF) v2.0 Dec. 6, 2000."
  • Publication Dates: January 16, 1995 (v1.1) and December 6, 2000 (v2.0)
  • Brief Description: These specifications describe the Simple Vector Format (SVF), which is explicitly mentioned in US7461353B2 as the format used for scalable vector representation. The patent itself notes that SVF was designed to handle a superset of commonly used file formats in CAD and was under consideration by the W3C for adoption as a standard for vector content on the World Wide Web.
  • Potentially Anticipates: These specifications would very likely anticipate claims relating to the use of SVF as a scalable vector representation for web content, or the conversion of HTML/XML into such a format (e.g., claims referring to HTML translator 58 generating a scalable vector representation, or claims describing the client-side viewer taking advantage of SVF power).
• "Scalable Vector Graphics (SVG) Specification, W3C Working Draft Feb. 11, 1999 WD-SVG-19990211."
  • Publication Date: February 11, 1999
  • Brief Description: This is a W3C Working Draft for Scalable Vector Graphics (SVG). SVG is another well-known vector format for graphics on the web, and its existence as a working draft prior to the priority date of US7461353B2 indicates the concept of scalable vector graphics for web content was known.
  • Potentially Anticipates: Similar to the SVF specifications, this could potentially anticipate claims regarding the use of scalable vector representations for Internet content, particularly those that broadly cover such formats beyond just SVF.

The patent document also mentions related applications, including U.S. application Ser. No. 09/878,097, filed Jun. 8, 2001 (now U.S. Pat. No. 7,210,099), and U.S. Provisional Application No. 60/211,019, filed Jun. 12, 2000, and U.S. Provisional Application No. 60/217,345, filed Jul. 11, 2000. These would be considered prior art if they have an earlier effective filing date and disclose subject matter claimed in 7461353 that is not common to the later-filed application. However, as 7461353 is a divisional and continuation-in-part of these, they represent the same inventive entity and thus are generally not considered prior art under 35 U.S.C. § 102 against the parent or related applications, but rather represent the lineage of the invention.

The description of prior art anticipation under 35 U.S.C. § 102 requires that a single prior art reference discloses every element of a claimed invention. Without a full claim set and the complete text of each prior art document, a definitive statement about anticipation of specific claims is not possible. However, the above analysis indicates potential areas of anticipation based on the titles and brief descriptions of the prior art.

The obviousness of US patent 7461353 under 35 U.S.C. § 103 can be analyzed by combining the general knowledge of conventional web browsing systems and the established capabilities of vector graphics systems, as described within the patent's own "BACKGROUND OF THE INVENTION" and "Client Overview" sections. A person having ordinary skill in the art (PHOSITA) at the time of the invention (priority date 2000-06-12) would have been motivated to combine these known elements to overcome the identified problems.

The core inventive concepts of US7461353, as summarized in its Abstract and Brief Summary, include:

• Enabling mobile devices to support resolution-independent scalable display of Internet (Web) content.
• Allowing Web pages to be scaled (zoomed) and panned for better viewing on smaller screen sizes.
• Employing processing of original Web content (HTML, XML, CSS) to generate scalable content.
• Rapidly rendering, zooming, and panning this scalable content.
• Maintaining substantially the same or identical layout as the original Web page.

Prior Art References:

For this analysis, the following "prior art references" are understood from the provided patent text, particularly the "BACKGROUND OF THE INVENTION" and the descriptive portions of the "Client Overview" that outline existing technologies:

1. Prior Art Reference A: Conventional Web Browsing Systems:

   • Existing Internet information browsers (e.g., Mosaic, Netscape Navigator, Internet Explorer) handle various content formats including HTML, XML, GIF, and JPEG.
   • These browsers generally display content at a "flat single resolution with no browser support for zoom" for the overall web page.
   • Much Internet content is designed with "fixed resolution structures, such as tables," which, while good for branding, presents "a daunting technical problem for display of Internet content (designed for desktop computers) on small screen, low resolution, or different aspect ratio devices, such as cell phones and hand held computers."
   • Conventional browsers allow altering font size and resizing the display area, but this is distinct from true zoom functionality for the entire page.

2. Prior Art Reference B: Vector Graphics Systems with Resolution-Independent Zoom and Pan:

   • The patent acknowledges that "zoom and pan" capability is "familiar to CAD and other vector content software users."
   • It is known that when a system "manipulates vectors, there is no loss in quality as the display is zoomed."
   • A Simple Vector Format (SVF) is described as a format "originally designed to handle a superset of the most commonly used file formats in the complex world of CAD," capable of accommodating new graphical functions and being considered by the W3C for vector content on the World Wide Web. This indicates that the principles of vector formats for resolution independence were well-understood in fields like CAD.

Obviousness Combination under 35 U.S.C. § 103:

A person having ordinary skill in the art (PHOSITA) in 2000-2001, faced with the problems described in Prior Art A, would have been motivated to combine the features of Prior Art A and Prior Art B to achieve the claimed invention.

Motivation for Combination:

The patent explicitly identifies the technical problem in the background: conventional web browsers, when displaying Internet content designed for desktop computers (often with fixed-resolution layouts), suffer from a "daunting technical problem for display... on small screen, low resolution, or different aspect ratio devices, such as cell phones and hand held computers" due to the "flat single resolution with no browser support for zoom."

A PHOSITA, encountering this clearly stated problem, would be motivated to seek solutions that allow for resolution-independent display and effective zooming and panning. Prior Art B provides a direct solution to these issues, noting that "zoom and pan" is "familiar to CAD and other vector content software users" and that "there is no loss in quality as the display is zoomed" when manipulating vectors.

Therefore, the motivation would be to apply the known advantages of vector graphics technology (Prior Art B) to the problem of displaying conventional, fixed-resolution web content (Prior Art A) on mobile devices. The goal would be to enable the web content to be scaled and panned without degradation, thereby improving usability on small screens, which directly addresses the "daunting technical problem" outlined in the background.

Explanation of Obviousness:

Given the motivation, the combination would involve the following steps, which would be obvious to a PHOSITA:

1. Translating Web Content to a Scalable Vector Representation: A PHOSITA would recognize that to achieve resolution independence and lossless zooming from fixed-resolution HTML/XML/raster image content (Prior Art A), the content must be converted into a scalable format. Knowing the capabilities of vector graphics systems (Prior Art B), it would be obvious to translate the web content (including HTML, XML, and CSS layout information) into a scalable vector representation (like SVF, or any other known vector format). This "novel processing" claimed by the patent is the logical step to make web content resolution-independent.
2. Displaying Scalable Vector Content with Zoom and Pan on Mobile Devices: Once the web content is in a scalable vector format, it would be obvious to leverage the known "zoom and pan" capabilities common in vector graphics software (Prior Art B) to render this content on various devices, including mobile devices. This directly addresses the lack of zoom support in conventional browsers and the challenges of small screens described in Prior Art A. The "thin client" described by the patent as performing this rendering would be an obvious implementation choice for resource-constrained mobile devices.
3. Maintaining Original Layout: The objective of adapting web content is typically to preserve the original design as much as possible to maintain context and familiarity. Therefore, rendering the scalable vector content while "provid[ing] substantially the same or identical layout as the original Web page" would be an obvious design choice for a PHOSITA implementing a conversion system.

In conclusion, the combination of (A) conventional web browsing systems that present fixed-resolution web content poorly on mobile devices and lack zoom, with (B) known vector graphics systems that offer resolution-independent display with zoom and pan capabilities, would render the claims of US7461353 obvious. The clear motivation would be to overcome the acknowledged technical problem of effectively displaying and interacting with existing web content on the increasingly prevalent small screens of mobile devices.

US patent 7461353, titled "Scalable display of internet content on mobile devices," was issued on December 2, 2008, from application number 11/045,757, filed on January 28, 2005.

Patent Term Adjustments (PTA) and Patent Term Extensions (PTE)

The patent states, "Subject to any disclaimer, the term of this patent is extended or adjusted under 35 U.S.C. 154(b) by 376 days. This patent is subject to a terminal disclaimer."

• Patent Term Adjustment (PTA): US patent 7461353 received a Patent Term Adjustment of 376 days. PTA compensates for administrative delays by the USPTO during patent prosecution.
• Patent Term Extension (PTE): There is no mention of a Patent Term Extension (PTE) for this patent, which is typically granted to compensate for delays in obtaining regulatory approval for a patented product.

Terminal Disclaimer

The patent is subject to a terminal disclaimer. A terminal disclaimer can limit the term of a patent. When a patent is subject to a terminal disclaimer, its term does not extend beyond the expiration date specified in the disclaimer, even with PTA.

Continuation and Divisional Applications

US 7461353 is a divisional application of U.S. application Ser. No. 09/878,097, filed on June 8, 2001, which resulted in U.S. Pat. No. 7,210,099.

Additionally, U.S. application Ser. No. 09/878,097 is a continuation-in-part of U.S. Non-Provisional application Ser. No. 09/828,511, filed on April 7, 2001, which is now abandoned.

The patent also claims the benefit of two provisional applications:

• U.S. Provisional Application No. 60/211,019, filed on June 12, 2000.
• U.S. Provisional Application No. 60/217,345, filed on July 11, 2000.

Related Family Members

The "Related Applications" section of the patent also lists the following as continuations of U.S. application Ser. No. 09/878,097 (now U.S. Pat. No. 7,210,099):

• U.S. application Ser. No. 11/735,477, filed on April 15, 2007.
• U.S. application Ser. No. 11/735,482, filed on April 15, 2007.
• U.S. application Ser. No. 11/738,486, filed on April 21, 2007.
• U.S. application Ser. No. 11/738,932, filed on April 23, 2007.

Projected Expiration Date

For applications filed on or after June 8, 1995, the patent term generally ends 20 years from the filing date of the earliest application for which a benefit is claimed. In this case, the earliest priority date claimed is June 12, 2000, from Provisional Application No. 60/211,019.

Adding 20 years to the earliest priority date of June 12, 2000, would suggest a statutory expiration date of June 12, 2020. However, the patent explicitly states an "Adjusted expiration" date of April 18, 2022. This adjusted expiration likely accounts for the 376 days of PTA and potentially the effect of the terminal disclaimer.

The patent expired on April 18, 2022.

Defensive Disclosure: Scalable Display of Internet Content on Mobile Devices - Derivative Innovations

Current Date: 2026-06-06

This document details derivative variations and extensions of the concepts described in US patent 7461353, "Scalable display of internet content on mobile devices." The purpose of this disclosure is to establish prior art for potential future incremental improvements by competitors, rendering such advancements obvious or non-novel in the context of resolution-independent content display. The focus is on expanding upon the core inventive concepts, as reflected in the independent claims, without re-summarizing the original patent.

---

Combination Prior Art Scenarios

Here are at least three scenarios where the core concepts of US7461353 are combined with existing open-source standards or widely adopted industry practices, demonstrating obvious extensions for a person having ordinary skill in the art (PHOSITA) as of the priority date or shortly thereafter.

1. Integration with the Mozilla Rendering Engine (Gecko) for Proxy-side Layout Analysis:
   • Description: The patent explicitly references using "core functionality provided by the Mozilla rendering engine source code to perform the functions of block 150, 152, and 154" (pre-rendering parsing, page layout generation, bounding box definition) at the proxy server or content provider's server. A PHOSITA would find it obvious to integrate the complete, open-source Gecko engine (Mozilla's rendering engine) into the server-side translation pipeline. This integration would provide robust and standards-compliant HTML, XML, and CSS parsing, layout computation, and DOM construction, directly generating an intermediate representation (e.g., a render tree) that could then be traversed and translated into scalable vector formats (like SVF or SVG) and identify raster images for compression. This leverages a mature, open-source project to handle the complexities of web page interpretation, making the subsequent vectorization step more efficient and accurate.
2. Conversion to Scalable Vector Graphics (SVG) as an Open Standard Output:
   • Description: While US7461353 emphasizes its proprietary Simple Vector Format (SVF), the patent also cites "Scalable Vector Graphics (SVG) Specification, W3C Working Draft Feb. 11, 1999 WD-SVG-19990211" as prior art. Given SVG's status as an open standard for two-dimensional vector graphics on the web, it would be obvious for a PHOSITA to implement the content translation process (whether proxy-side, server-side, or client-side) to output content directly in SVG format instead of or in addition to SVF. The client-side viewer would then be adapted to interpret and render SVG. This combination marries the patent's concept of resolution-independent display with an industry-standard, broadly supported vector format, enhancing interoperability and reducing reliance on a proprietary format.
3. Responsive Content Adaptation using CSS Media Queries and Server-Side Optimization:
   • Description: The patent highlights the challenge of displaying fixed-resolution web content on diverse mobile screens. Combining the server-side or proxy-side translation mechanism with the principles of Responsive Web Design (RWD), particularly CSS Media Queries, would be an obvious improvement. The server/proxy would not only convert content to scalable vectors but would also analyze or apply predefined media query breakpoints. For instance, before vectorization, the server could re-flow content or select alternative assets (e.g., smaller graphic images) based on the detected client device characteristics (screen size, pixel density, orientation) communicated via HTTP headers. The scalable vector output would then incorporate these responsive adjustments, allowing for more intelligent adaptation beyond simple zoom and pan, and generating a more optimized view for the specific mobile device.

---

Derivatives of Conceptual Claim 1: Proxy-based content translation and delivery

Conceptual Claim: A method for displaying Internet content on a client device independent of screen resolution, where a proxy server receives a content request, retrieves the content, converts it into a scalable vector format and compressed images, and streams this processed content to the client for rendering with zoom and pan.

---

1. Material & Component Substitution: GPU-Accelerated Proxy Translation Pipeline

• Enabling Description: The proxy server's content translation (HTML to scalable vector, raster image compression) is offloaded to a dedicated Graphics Processing Unit (GPU) cluster or a server equipped with multiple high-performance General-Purpose GPUs (GPGPUs). The HTML parser generates a Document Object Model (DOM) and an abstract render tree. This render tree, along with all associated raw media assets, is then passed to a GPU-optimized translation module. This module utilizes parallel processing capabilities of the GPU to rapidly construct vector graphic primitives (e.g., polygons, Bézier curves for text glyphs, texture quads for raster images) and to perform image compression (e.g., WebP or AVIF encoding) using GPU-accelerated algorithms (e.g., CUDA or OpenCL kernels). The output streams are then assembled and transmitted. This substitution significantly reduces translation latency and increases throughput for high-volume proxy services.

graph TD
    A[Client Request HTTP/URL] --> B(Proxy Server)
    B --> C{HTTP Cache Check}
    C -- Cache Miss --> D[Retrieve Content (Web Server/FTP)]
    D --> E[Raw HTML/Images]
    E --> F(GPU-Accelerated Translator Module)
    F -- Render Tree --> F1(GPU-Optimized Vectorization)
    F -- Raw Images --> F2(GPU-Accelerated Image Compression)
    F1 --> G{Scalable Vector Data}
    F2 --> H{Compressed Bitmap Data}
    G & H --> I[Stream to Client]
    C -- Cache Hit --> I
    I --> J[Client Rendering]

---

2. Operational Parameter Expansion: Sub-Millisecond Latency Translation for Real-Time Interactive Content

• Enabling Description: The proxy server is optimized to provide content translation and streaming for real-time interactive web applications, such as collaborative design tools or live data visualizations, requiring sub-millisecond end-to-end latency for content updates. This involves deploying the proxy infrastructure geographically closer to end-users (edge computing), employing dedicated low-latency network interconnects (e.g., 5G mmWave backhaul), and utilizing kernel-bypass networking (e.g., DPDK) for ultra-fast packet processing. The translation module uses incremental parsing and just-in-time vectorization techniques, streaming delta updates of vector primitives and compressed image patches rather than full page re-renders. Dynamic content regions are identified and re-vectorized with higher priority, minimizing perceived lag.

sequenceDiagram
    participant C as Client
    participant E as Edge Proxy (Sub-ms Latency)
    participant W as Web Server
    C ->> E: Live Content Request (WebSocket/HTTP/2)
    E ->> W: Fetch Initial/Delta Content
    W -->> E: Raw HTML/JSON/Image Data
    Note over E: Incremental Parsing & JIT Vectorization
    E ->> E: Identify Dynamic Regions
    E -->> C: Scalable Vector Delta Stream (Sub-ms)
    C ->> C: Render Delta Update
    loop User Interaction
        C ->> E: User Input/Interaction
        E ->> W: Forward Interaction/Fetch New State
        W -->> E: New Data/HTML
        E -->> C: Scalable Vector Delta Stream
    end

---

3. Cross-Domain Application: Industrial IoT Dashboard Display

• Enabling Description: The proxy-based content translation system is deployed within an industrial control network to provide scalable display of Supervisory Control and Data Acquisition (SCADA) dashboards on diverse operator interfaces (e.g., rugged tablets, large-format control room monitors, head-mounted displays). The proxy server retrieves real-time operational data rendered as web content (e.g., HTML/JS charts, schematics) from various plant control systems. It translates this dynamic web content into a resolution-independent vector format, ensuring that critical process values, equipment status, and alarm notifications are perfectly legible and interactive regardless of the display device's resolution or aspect ratio. This allows for unified visualization across heterogeneous display infrastructure in an industrial setting.

graph LR
    A[SCADA Systems] --> B(Plant Web Servers)
    B -- Live Data Feeds --> C(Industrial Proxy Server)
    C -- Translate to SVF/SVG/Compressed Images --> D(Operator Terminal 1: Rugged Tablet)
    C --> E(Operator Terminal 2: Control Room Monitor)
    C --> F(Operator Terminal 3: HMD)
    D & E & F -- Resolution-Independent Display --> G[Unified Real-Time Dashboard View]

---

4. Integration with Emerging Tech: AI-Driven Predictive Content Pre-fetching and Vectorization

• Enabling Description: The proxy server integrates an Artificial Intelligence (AI) module for predictive content pre-fetching and adaptive vectorization. The AI, trained on user interaction patterns, browsing history, and contextual data (e.g., time of day, location, current device, network conditions), predicts which content the user is likely to request next. Based on these predictions, the proxy preemptively retrieves and translates the anticipated web pages or portions thereof into scalable vector format and compressed bitmaps, storing them in a local cache. Furthermore, the AI dynamically adjusts the level of detail in the vectorization process (e.g., simplification of complex graphical elements, prioritization of text fidelity) and image compression ratios based on predicted display capabilities and network bandwidth, optimizing the streaming experience for the expected client environment.

graph TD
    A[Client Request] --> B(Proxy Server)
    B -- User Context --> C(AI Predictive Engine)
    C -- Prediction --> D[Pre-fetch URLs]
    D --> E[Retrieve Raw Content]
    E --> F(Adaptive HTML/Image Translator)
    F -- Optimized SVF/Compressed Bitmaps --> G(Proxy Cache)
    G --> B
    B -- Stream Anticipated/Requested Content --> H[Client Device]

---

5. The "Inverse" or Failure Mode: Low-Bandwidth Graceful Degradation Proxy

• Enabling Description: A specialized "Low-Bandwidth Graceful Degradation" proxy server is introduced. In scenarios of severe network congestion or extremely low bandwidth availability (e.g., emergency communications, remote field operations), the proxy automatically enters a limited-functionality mode. Instead of full vectorization, it prioritizes text content, rendering it as simplified, highly compressed text vectors (e.g., using minimal glyph outlines or bitmap fonts at a single, small size) and entirely stripping out non-essential images, scripts, and complex styling. Essential graphic content is converted to highly lossy, grayscale, or extremely low-resolution compressed bitmaps. The proxy may also reformat the page structure to a linear, single-column layout, ensuring core information readability and basic navigation remain functional even under extreme network constraints.

stateDiagram
    [*] --> Normal_Operation
    Normal_Operation --> Low_Bandwidth_Detected: Network Degradation
    Low_Bandwidth_Detected --> Emergency_Mode: Severe Congestion
    Emergency_Mode --> Normal_Operation: Network Restored

    state Normal_Operation {
        Normal_Operation : Full Vectorization & Compression
    }

    state Emergency_Mode {
        Emergency_Mode : Prioritize Text Vectors
        Emergency_Mode : Strip Non-Essential Graphics
        Emergency_Mode : Lossy/Grayscale Bitmaps
        Emergency_Mode : Linear Page Reflow
    }

---

Derivatives of Conceptual Claim 2: Client-side rendering of scalable content

Conceptual Claim: A computer program product enabling a client device to achieve resolution-independent display by receiving scalable web content, creating a display list of vectors, processing these elements based on user-chosen zoom and pan settings, retrieving relevant parts, scaling them (including fonts), and rendering them on the screen.

---

1. Material & Component Substitution: Hardware-Accelerated Display List Processor

• Enabling Description: The client device incorporates a dedicated hardware accelerator, such as a custom Application-Specific Integrated Circuit (ASIC) or a Field-Programmable Gate Array (FPGA), specifically designed to process the incoming scalable vector content and manage the display list. This hardware component rapidly constructs and updates the vector display list, performs matrix transformations for scaling and panning, and handles clipping to determine visible content. It features specialized vector rendering pipelines that directly convert vector primitives into rasterized pixels on the display buffer, bypassing general-purpose CPU and software-based rendering engines. Font scaling is also hardware-accelerated, utilizing on-chip scalable font rasterizers. This dramatically increases rendering speed and reduces power consumption compared to software-only solutions.

graph TD
    A[Received Scalable Content (SVF/Bitmaps)] --> B(Hardware-Accelerated Display List Processor)
    B -- Vector Data --> B1(Display List Constructor)
    B -- Bitmap Data --> B2(Bitmap Buffer Manager)
    B1 --> C(User Input (Zoom/Pan))
    C --> B3(Transformation & Clipping Unit)
    B3 --> B4(Hardware Vector Rasterizer)
    B4 -- Pixels --> D[Client Display]
    B2 --> B4

---

2. Operational Parameter Expansion: Augmented Reality Overlay Rendering

• Enabling Description: The client-side rendering engine is extended to project the scaled and panned web content onto a real-world view in an Augmented Reality (AR) environment. This involves tracking the user's head pose and eye gaze using integrated sensors (e.g., LiDAR, IMU) on an AR headset or mobile device. The scaled vector content is rendered as a virtual layer that adapts its position, orientation, and size relative to the real-world scene. Users can "pin" web pages to physical locations, manipulate them with gestures (e.g., pinch-to-zoom), and interact with hyperlinks by gaze-dwell or voice commands. The display list management ensures seamless scaling and high frame rates for a fluid AR experience, even when projecting complex web layouts.

sequenceDiagram
    participant U as User
    participant ARD as AR Device (Client)
    participant CE as Client Rendering Engine
    participant S as Sensors (LiDAR/IMU/Eye-tracking)

    ARD ->> CE: Receive Scalable Content
    CE ->> CE: Build Display List
    loop AR Interaction
        U ->> S: Gaze/Gesture/Voice Input
        S -->> ARD: Pose/Gaze Data
        ARD ->> CE: Update Viewport (Scale/Offset/Transform)
        CE ->> CE: Process & Retrieve Visible Elements
        CE ->> CE: Scale/Rasterize for AR View
        CE -->> ARD: Render Web Content Overlay
        ARD ->> U: Display AR View
    end

---

3. Cross-Domain Application: Digital Twin Monitoring Interface

• Enabling Description: The client-side rendering technology is applied to display interactive digital twin interfaces in manufacturing or smart building contexts. Instead of general web pages, the scalable content comprises 3D models of machinery or building layouts embedded with real-time sensor data, fault indicators, and maintenance schedules, all presented through a web-based interface (e.g., WebGL, but delivered as a vectorized representation). The client device (e.g., industrial tablet, workstation) receives these vectorized digital twin views. The resolution-independent display allows operators to zoom into specific components for detailed inspection, pan across large facility layouts, and interact with overlaid data points, maintaining crisp visual fidelity regardless of screen size or scaling factor.

graph LR
    A[Digital Twin Data Source] --> B(Vectorized Digital Twin Content)
    B --> C(Client Device)
    C -- Receive & Build Display List --> D(Client-Side Rendering Engine)
    D -- Zoom/Pan Input --> D
    D -- Resolution-Independent Render --> E[Interactive Digital Twin View]
    E --> F[Operator/Analyst]

---

4. Integration with Emerging Tech: Haptic Feedback Enhanced Navigation

• Enabling Description: The client device integrates advanced haptic feedback actuators to provide tactile cues during navigation and interaction with the scaled web content. As the user zooms in or pans across a web page, the haptic system generates subtle vibrations or force feedback correlating to the boundaries of logically grouped elements (e.g., tables, images, paragraphs), clickable links, or significant changes in content density. For example, a "snap" sensation might be provided when a column boundary is reached during panning, or a "pulse" when hovering over a hyperlink. An AI-powered haptic feedback module analyzes the vectorized content's structure and user interaction to intelligently generate context-aware tactile responses, enhancing usability for small screens or accessibility.

graph TD
    A[Client Device] --> B(Client-Side Rendering Engine)
    B -- Display List & Bounding Boxes --> C(Haptic Feedback Module)
    C -- User Input (Zoom/Pan) --> B
    C -- Content Context --> C
    C -- Tactile Feedback Commands --> D(Haptic Actuators)
    D --> E[User (Tactile Sensation)]
    B -- Visual Render --> F[Client Display]

---

5. The "Inverse" or Failure Mode: Accessibility-Focused Text Reflow and Low-Fidelity Mode

• Enabling Description: The client's rendering engine incorporates an "Accessibility-Focused Text Reflow and Low-Fidelity Mode." In this mode, activated by user preference or detected visual impairment settings, the rendering prioritizes textual content for maximum readability. All text elements, regardless of their original placement in the vectorized content, are extracted and re-flowed into a single, continuously scrollable column, with user-configurable font sizes (utilizing font scaling capabilities) and high contrast color schemes. Non-essential images and complex layouts are either suppressed entirely or replaced with simple placeholders, reducing visual clutter. This mode ensures that critical information is always accessible and legible, even if it sacrifices the original page layout, representing a graceful degradation focused on content consumption rather than aesthetic preservation.

flowchart TD
    A[Receive Scalable Content] --> B{Accessibility Mode Active?}
    B -- Yes --> C[Extract All Text Elements]
    C --> D[Re-flow Text to Single Column]
    D --> E[Apply User Font Size/Contrast]
    E --> F[Suppress/Replace Non-Essential Graphics]
    F --> G[Render Accessibility View]
    B -- No --> H[Normal Rendering Process]
    G & H --> I[Client Display]

---

Derivatives of Conceptual Claim 3: Content provider-based content translation and delivery

Conceptual Claim: A method for a content provider's website to deliver resolution-independent Internet content, where the web server receives a client's request, gets the content, translates it into scalable vector graphics and compressed images, and streams it to the client, which then processes and displays it with user-controlled scaling and panning.

---

1. Material & Component Substitution: Serverless Function-Based Translation Microservice

• Enabling Description: The content translation functionality typically performed by a monolithic web server is decomposed into stateless, event-driven serverless functions (e.g., AWS Lambda, Google Cloud Functions). When a client requests content in a scalable vector format, the web server acts as a gateway, triggering a serverless "HTML-to-Vector" function. This function dynamically retrieves the raw HTML and associated assets, executes the translation logic (parsing, vectorization, image compression), and then returns the vectorized content stream directly to the client or to a content delivery network (CDN) for caching and delivery. This substitution allows for highly scalable and cost-efficient on-demand translation, eliminating the need for always-on, provisioned server instances for the translation task.

graph LR
    A[Client Request] --> B(API Gateway/Load Balancer)
    B --> C(Web Server)
    C -- Trigger --> D(Serverless HTML-to-Vector Function)
    D -- Fetch Raw Content --> E[Origin Content (HTML/Images)]
    E --> D
    D -- Generate SVF/Compressed Bitmaps --> F[Vectorized Content Stream]
    F --> G(CDN/Client)

---

2. Operational Parameter Expansion: Ultra-High-Resolution Interactive Kiosk Content

• Enabling Description: The content provider's web server is configured to deliver scalable content specifically optimized for ultra-high-resolution (e.g., 8K, 16K, or beyond) public interactive kiosks or digital signage. The translation engine on the server pre-renders high-fidelity vector graphics that account for extreme zoom levels, ensuring crisp detail even when users interact closely with the display. Content streaming is optimized for high-bandwidth, low-latency connections typical of fixed kiosk installations, potentially using advanced compression codecs or tile-based vector streaming (similar to map services) to deliver only the visible portions of the vast content. The rendered pages can include multi-touch interactive elements that scale perfectly.

flowchart TD
    A[Client Request (Kiosk/Signage)] --> B(Web Server)
    B -- Content Retrieval --> C[High-Fidelity Web Content]
    C --> D(Server-Side HTML/Image Translator)
    D -- Ultra-High-Res Vectorization & Compression --> E[Stream Optimized Scalable Content]
    E --> F(Interactive Kiosk/Digital Signage)
    F -- User Input (Multi-touch/Zoom) --> F
    F -- Render Resolution-Independent Display --> G[Ultra-Detail Interactive Experience]

---

3. Cross-Domain Application: E-commerce Product Configurators

• Enabling Description: An e-commerce platform utilizes the server-side content translation to power highly customizable product configurators. Product pages with complex 3D models, intricate option menus, and dynamic pricing information (rendered as HTML/JS) are translated on the server into scalable vector representations. When a customer customizes a product (ee.g., changes color, adds accessories), the server generates a new vectorized view of the configured product and its associated details. This allows customers to zoom in on product details, pan around 3D views, and review specifications in a resolution-independent manner across various devices (desktop, tablet, mobile), ensuring consistent high-quality visuals without requiring client-side 3D rendering engines or large image downloads.

sequenceDiagram
    participant C as Customer Client
    participant WS as Web Server (E-commerce)
    participant PTE as Product Translation Engine

    C ->> WS: Request Product Configurator
    WS ->> PTE: Get Base Product HTML/JS
    PTE ->> PTE: Translate to Scalable Vector Product View
    PTE -->> WS: Vector Content Stream
    WS -->> C: Stream Product View
    C ->> C: Render Product
    loop Customization
        C ->> WS: User Configures Product
        WS ->> PTE: Request New Configured View
        PTE ->> PTE: Generate Scalable Vector for New Configuration
        PTE -->> WS: Vector Content Stream
        WS -->> C: Stream New View
        C ->> C: Render Updated Product View
    end

---

4. Integration with Emerging Tech: Blockchain-Verified Content Integrity

• Enabling Description: The content provider's web server integrates blockchain technology to ensure the integrity and authenticity of the translated scalable web content. After the HTML and images are translated into the scalable vector format (SVF/SVG) and compressed bitmaps, a cryptographic hash of the resulting content package is generated. This hash, along with a timestamp and the content's origin, is then recorded on a public or private blockchain. The client device, upon receiving the streamed content, can independently compute the hash of the received content and verify it against the blockchain record. This ensures that the content has not been tampered with during transmission or by any intermediary, providing verifiable content integrity crucial for sensitive applications like financial reporting or legal documents displayed on mobile devices.

graph TD
    A[Raw Web Content] --> B(Web Server Translator)
    B -- SVF/Compressed Bitmaps --> C(Content Package)
    C --> D(Cryptographic Hashing Module)
    D -- Hash Value --> E(Blockchain Notary Service)
    E --> F[Blockchain Ledger]
    C -- Stream to Client --> G(Client Device)
    G -- Compute Local Hash --> H(Client Verification Module)
    H -- Query Blockchain --> F
    F --> H
    H -- Compare Hashes --> I{Content Verified?}

---

5. The "Inverse" or Failure Mode: Cached Static Vector Fallback

• Enabling Description: The content provider's web server implements a "Cached Static Vector Fallback" mechanism. During periods of peak load, server failure, or content source unavailability, the server automatically defaults to serving pre-generated, cached static versions of the scalable vector content. For critical pages (e.g., home page, contact info, error messages), a static SVF/SVG version and corresponding compressed bitmaps are generated during deployment or at regular intervals. If dynamic content generation fails or becomes too slow, the server detects the operational anomaly and serves these pre-computed static vector files. This provides a degraded, but fully functional and resolution-independent, user experience, ensuring basic site navigation and information access remain available during outages or high demand.

stateDiagram
    [*] --> Operational
    Operational --> Degraded_Mode: Server Load High / Failure
    Degraded_Mode --> Operational: Server Restored

    state Operational {
        Operational : Dynamic Translation
        Operational : Real-time Streaming
    }

    state Degraded_Mode {
        Degraded_Mode : Serve Cached Static Vectors
        Degraded_Mode : Static Bitmaps
        Degraded_Mode : Limited Interactivity
    }

---

Derivatives of Conceptual Claim 4: Client-side content translation and delivery

Conceptual Claim: A method for a client device to process Internet content for resolution-independent display, where the client receives content, identifies and retrieves additional linked objects, converts all HTML and graphic content into scalable vector and compressed bitmap formats, and then processes, scales, and renders this content based on user interaction.

---

1. Material & Component Substitution: On-Device Neural Processing Unit (NPU) for Content Vectorization

• Enabling Description: The client device integrates a dedicated Neural Processing Unit (NPU) or other specialized AI accelerator hardware for performing the HTML parsing, layout analysis, and vectorization directly on the device. Instead of traditional rule-based translation, a trained neural network model (e.g., a transformer-based architecture) running on the NPU interprets the raw HTML, XML, and CSS, predicting optimal vector primitive representations (e.g., text blocks, shape outlines, image regions) and generating a device-optimized scalable vector format. Image compression may also leverage NPU-accelerated neural codecs (e.g., learned image compression). This allows for highly efficient and potentially more intelligent content adaptation, offloading intensive processing from the main CPU and GPU, thereby conserving battery life and reducing latency.

graph TD
    A[Raw HTML/Images (Received)] --> B(On-Device NPU)
    B -- Neural Network Model --> B1(HTML/CSS Interpretation & Layout Prediction)
    B1 --> B2(Vector Primitive Generation)
    B2 --> C(Device-Optimized Scalable Vector Format)
    B -- Raw Images --> B3(NPU-Accelerated Image Compression)
    B3 --> D(Compressed Bitmaps)
    C & D --> E(Client Rendering Engine)
    E --> F[Resolution-Independent Display]

---

2. Operational Parameter Expansion: Offline Batch Translation and Pre-rendering

• Enabling Description: The client device, when connected to a high-bandwidth network (e.g., Wi-Fi at home), initiates an "Offline Batch Translation and Pre-rendering" process for user-specified or frequently accessed web content. In this mode, the client proactively retrieves entire websites or selected pages, performs the full HTML and graphic content translation into scalable vector format and compressed bitmaps, and stores these vectorized representations locally. For highly dynamic content, the client may also pre-render and cache common zoom levels or pan regions. This enables seamless, resolution-independent browsing of complex web pages when the device is later offline or in a low-connectivity environment, with instantaneous loading and fluid interaction due to the pre-processed nature of the content.

sequenceDiagram
    participant C as Client Device
    participant W as Web Server

    C ->> C: High Bandwidth Detected
    C ->> C: Initiate Offline Sync/Pre-fetching
    loop Selected Content
        C ->> W: Request Raw Web Page
        W -->> C: Raw HTML/Images
        C ->> C: Perform Client-Side Translation (HTML to SVF/Bitmaps)
        C ->> C: Store Vectorized Content Locally
    end
    C ->> C: Offline Browsing Mode Active
    Note over C: Render from local Vector Cache

---

3. Cross-Domain Application: Field Maintenance Augmented Manuals

• Enabling Description: The client-side translation and display method is implemented in ruggedized handheld devices used by field maintenance technicians. The devices receive standard HTML-based technical manuals, schematics, and diagnostic guides (often rich in diagrams and text) from a central server. The client device's software translates these documents into a scalable vector format on the fly. This allows technicians to zoom into intricate electrical diagrams or mechanical blueprints with infinite fidelity, pan across large pages, and interact with embedded links or annotations without pixelation, even on small, high-brightness screens in challenging outdoor environments. Annotations or real-time sensor data overlays can also be rendered as scalable vectors.

graph TD
    A[Central Technical Manual Server] --> B(Field Maintenance Device (Client))
    B -- Request HTML Manuals --> B
    B -- HTML/Images Received --> C(Client-Side Translator)
    C -- SVF/Compressed Bitmaps --> D(Client Rendering Engine)
    D -- Zoom/Pan Input --> D
    D -- Render Resolution-Independent Manual --> E[Technician's Interactive View]
    E --> F[Field Technician]

---

4. Integration with Emerging Tech: Decentralized Content Fetching (DLT) with Client-Side Translation

• Enabling Description: The client device is enhanced to retrieve web content from decentralized storage networks (e.g., IPFS, Arweave) or directly from peer nodes using Distributed Ledger Technology (DLT) for content addressing and verification. Instead of a traditional web server or proxy, the client's content retrieval module queries a DLT to locate the content hash and then fetches the raw HTML and associated assets from distributed nodes. The subsequent translation into scalable vector format and rendering (as per the original patent's client-side approach) then occurs entirely on the client. This provides censorship-resistant and highly resilient content access, with the client maintaining full control over the translation and display process, ensuring resolution independence even for distributed content.

sequenceDiagram
    participant C as Client Device
    participant DLT as Distributed Ledger
    participant DS as Decentralized Storage Network (e.g., IPFS)

    C ->> DLT: Query Content Hash for URL
    DLT -->> C: Content Hash / Node Addresses
    C ->> DS: Fetch Raw HTML/Images (using hash)
    DS -->> C: Raw HTML/Images
    C ->> C: Client-Side HTML/Image Translation
    C ->> C: Generate SVF/Compressed Bitmaps
    C ->> C: Process, Scale & Render
    C -->> C: Resolution-Independent Display

---

5. The "Inverse" or Failure Mode: Progressive Download and Essential Content First

• Enabling Description: The client-side translation and rendering system implements a "Progressive Download and Essential Content First" mode designed for highly constrained environments or as a user preference for rapid information access. When requesting a new web page, the client prioritizes the download of core HTML structure and text content. It immediately translates and renders these essential elements into scalable vectors, displaying them while the remaining, less critical assets (e.g., high-resolution images, complex scripts, advertising banners) are still being fetched and translated in the background. The rendering engine progressively updates the display as more vectorized content becomes available, ensuring a fast initial load and interactive experience, even if the full page fidelity is built up over time. This provides immediate utility rather than waiting for complete content.

flowchart TD
    A[Client Requests Web Page] --> B(Download HTML/Text First)
    B --> C(Client-Side Translate Essential Text/Layout to SVF)
    C --> D[Initial Render (Text-Only / Basic Layout)]
    D --> E(Download Remaining Images/Scripts)
    E --> F(Client-Side Translate Remaining Content)
    F --> G[Progressive Render Update]
    G --> H[Full Resolution-Independent Display]