Patent 9519729

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

Active provider: Google · gemini-2.5-flash

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

✓ Generated

A comprehensive obviousness analysis under 35 U.S.C. § 103 requires specific prior art references that predate the patent's priority date (June 12, 2000) and that embody elements of the claimed invention. The provided patent text, while listing "Prior art keywords" (content, html, display, web page, touch) and "Prior art date" (2000-06-12), does not include specific prior art documents (e.g., other patents, scientific publications, or commercial products) against which to assess obviousness.

Therefore, this analysis will proceed by:

  1. Defining the Person Having Ordinary Skill in the Art (PHOSITA) at the priority date.
  2. Identifying the problem US9519729 aims to solve, as articulated by the patent itself.
  3. Hypothetically considering combinations of known technologies and the potential motivations for a PHOSITA to combine them to arrive at the claimed invention, explicitly acknowledging the absence of specific prior art references.

1. Person Having Ordinary Skill in the Art (PHOSITA)

At the priority date of June 12, 2000, a PHOSITA in the field of internet content display on mobile devices would likely possess:

  • Knowledge of web technologies including HTML, XML, CSS, HTTP, and TCP/IP.
  • Familiarity with various image formats (GIF, JPEG, BMP) and compression techniques.
  • Understanding of web browser architecture and rendering engines.
  • Knowledge of mobile device capabilities and limitations, particularly concerning screen size, resolution, processing power, and network bandwidth (e.g., WAP, i-Mode).
  • Experience with graphics rendering, including both raster and vector graphics, and techniques for zooming and panning in applications like CAD.
  • Familiarity with server-side processing, proxy servers, and caching mechanisms.
  • Basic understanding of user interface design, especially for touch-sensitive screens if applicable at the time.

2. Problem Solved by US9519729

The patent explicitly states the problem it addresses: "The majority of Internet content displays as a flat single resolution with no browser support for zoom." and "Much of the Internet content has been designed for display on desktop computers with a single target resolution." It notes that this "fixed resolution approach... does present 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." [cite: "Description" section]

The invention seeks to enable "resolution-independent scalable display of Internet (Web) content to allow Web pages to be scaled (zoomed) and panned for better viewing on smaller screen sizes." [cite: Abstract]

3. Hypothetical Obviousness Analysis (without specific prior art references)

Without specific prior art references, a precise § 103 analysis is not possible. However, we can hypothetically consider what combinations of generally known technologies might lead to the claimed invention, and what motivations a PHOSITA would have.

Core Idea: Converting fixed-resolution web content into a scalable vector representation (like SVF) for display on mobile devices with zoom and pan capabilities, often facilitated by a proxy server.

Consideration of Independent Claim 1 (Method Claim):
Claim 1 outlines a method performed by a proxy server and a mobile device:

  • Receiving a request for web content with an indication for scalable vector representation (SVF). Proxy servers were known for content adaptation and filtering. A PHOSITA, aware of the limitations of mobile displays and the benefits of vector graphics for scalability, would have a motivation to request content in a scalable format. If a proprietary or emerging standard for scalable web content (like SVF, which the patent mentions was "under consideration by the W3C" [cite: "Client Overview" section]) existed, requesting it specifically would be an obvious choice.
  • Retrieving web content (HTML/CSS/graphics). This was standard web proxy functionality.
  • Translating HTML/CSS into SVF. The patent states HTML describes layout and attributes. Vector graphics (like those used in CAD, for which SVF was designed [cite: "Client Overview" section]) inherently describe geometric shapes and text in a scalable manner. A PHOSITA facing the problem of non-scalable HTML layout on small screens would be motivated to translate the structural and layout information of HTML/CSS into a vector format that supports scalability. The "Mozilla rendering engine" is mentioned as a potential core functionality [cite: "Detailed Description of the Invention" section], suggesting that parsing HTML into an internal representation was already a known technique. Converting this internal representation into a standard vector format (like SVF) to gain scaling advantages would be an apparent solution.
  • Converting graphic images into a compressed bitmap format. Bitmaps are not inherently scalable without quality loss upon zoom. However, image compression (GIF, JPEG) was already widely used to reduce file sizes for faster transmission over networks, including wireless. A PHOSITA would recognize that re-encoding graphics into a more efficient compressed bitmap (rather than attempting to vectorize all bitmaps, which can be computationally intensive and not always yield perfect results for photographic content) combined with the vector representation of the text and layout, could still provide performance benefits, especially for bandwidth-constrained mobile devices. This would represent an optimization rather than a fundamentally new concept.
  • Sending vectorized content and compressed bitmaps to the mobile device. Streaming various content types over a network was a known technique. The patent mentions "streaming" content and even "layering" content by type [cite: "Server Overview" section], which suggests known strategies for optimizing delivery to clients.
  • Mobile device receiving and rendering, enabling user zoom and pan. Client-side rendering of different content types was standard. The "zoom and pan" capability was "familiar to CAD and other vector content software users" [cite: "Client Overview" section]. Given that the content is now in a scalable vector format, implementing zoom and pan on the client side would be a straightforward application of known vector graphics rendering techniques to address the small screen problem. The patent highlights the "ultra-thin client-side viewer" [cite: "Client Overview" section], suggesting efficiency improvements, but the core zoom/pan function itself, once provided with vector data, would be expected.

Motivation for Combination: The primary motivation for a PHOSITA to combine these elements would be to overcome the acknowledged problem of displaying fixed-resolution web content effectively on the burgeoning market of small-screen mobile devices. Given the known advantages of vector graphics for scalability in other domains (e.g., CAD) and the existence of proxy servers for content adaptation, applying these technologies to web content for mobile devices would be a logical step. The combination of converting layout to vector and images to efficient bitmaps, then delivering to a client with vector-rendering capabilities, directly addresses the limitations of mobile browsing in 2000.

Consideration of Independent Claim 11 (System Claim):
Claim 11 describes a system. If the method of Claim 1 is considered obvious, then a system configured to perform that method would also likely be considered obvious, as it would merely be the hardware and software implementation of the obvious method. The components (mobile device, content translation service which could be a proxy/web server/client, processors, memories, communication interfaces) were all well-known at the priority date.

Consideration of Independent Claim 18 (Non-transitory Computer-Readable Medium Claim):
Claim 18 describes a non-transitory computer-readable medium containing instructions for performing the translation and streaming steps. If the method performed by these instructions (translating HTML/CSS to SVF, converting graphics to compressed bitmaps, and streaming) is considered obvious, then storing those instructions on a computer-readable medium would also be obvious. Computer-readable media for storing and distributing software were commonplace by 2000.

Conclusion on Obviousness (Hypothetical)

Based on a hypothetical analysis, and without specific prior art references, it is plausible that a PHOSITA in June 2000, motivated by the recognized challenges of displaying desktop-oriented web content on mobile devices, would have found many aspects of US9519729 obvious. The idea of using vector graphics for scalability was known (e.g., in CAD). The use of proxy servers for content adaptation was also known. The combination of these to translate web content (HTML/CSS layout to vectors, raster images to compressed bitmaps) and enable client-side zoom and pan on mobile devices appears to be a logical application of existing technologies to a known problem.

However, the specific "Simple Vector Format (SVF)" and its precise capabilities, or the exact details of the "ultra-thin client-side viewer" and its rendering efficiency, or the novel "tap-based inputs to selectively zoom in on columns, images, and paragraphs" [cite: Abstract] might contain non-obvious elements that could withstand an obviousness challenge, particularly if specific prior art demonstrating these exact features in combination for web content on mobile devices is lacking.

To perform a conclusive § 103 analysis, specific prior art references that explicitly teach or suggest each element of the claims, and a clear motivation for combining them, are essential. The provided information does not include such references.

Generated 5/29/2026, 5:40:54 PM