Obviousness

To analyze the obviousness of US patent 10083154 under 35 U.S.C. § 103, we must identify combinations of prior art references that would render the claims obvious to a person having ordinary skill in the art (PHOSITA) as of the priority date of June 12, 2000. A PHOSITA in this field around 2000 would likely possess knowledge of web technologies (HTML, CSS), mobile device capabilities (small screens, limited processing, WAP), vector graphics, and user interface design.

The independent claims (1, 13, 20, 21, 22, 23, 25) of US10083154 generally describe a mobile hand-held device or a method/computer-readable medium for:

1. Receiving and processing an HTML document using an HTML rendering engine to interpret page layout, group content into objects, and generate bounding boxes and page layout information.
2. Translating this representation into a scalable vector representation by defining a primary datum for the page, object datums for bounding boxes, generating vectors between datums, and creating references.
3. Rendering the scalable vector representation on a touch-sensitive display to fit the width, and enabling user-defined zoom and pan operations via touch input while preserving the original layout, functionality, and design.

The patent itself acknowledges the challenges of displaying web content designed for desktop computers on small screens, noting that "The majority of Internet content displays as a flat single resolution with no browser support for zoom." (BACKGROUND OF THE INVENTION) and that "major Internet content providers have chosen to create their Web pages using fixed resolution structures, such as tables." (BACKGROUND OF THE INVENTION).

Given the priority date of June 12, 2000, we will look for prior art that addresses these technical areas.

The provisional applications 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, are cited in US10083154B2 as priority documents. The abstract of US 8145995 B2, which claims continuity from an application that itself claims priority from these provisional applications, states that it enables "Mobile devices enabled to support 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." It further describes using "software-based processing of original Web content, including HTML-based content, XML, cascade style sheets, etc. to enable Web page content to be rapidly rendered, zoomed, and panned." This indicates that the core concepts of scalable display, zooming, and panning of web content on mobile devices were present in the provisional applications as of their filing dates. However, for obviousness analysis under 35 U.S.C. § 103, we need to consider prior art that was publicly available before the earliest priority date (June 12, 2000). Provisional patent applications are generally not published or made public at their filing date unless a non-provisional application claiming priority to them is subsequently published.

Therefore, we will focus on other publicly available prior art.

1. General Knowledge of HTML Rendering and Processing on Mobile Devices (before June 2000)

By June 2000, HTML 4.01 was an official standard (December 1999), and XHTML 1.0, a reformulation of HTML using XML syntax, was released in 2000. HTML 3.2, released in January 1997, standardized features like tables and text flow around images. Web browsers of the time, such as Netscape and Internet Explorer, processed HTML by parsing it, identifying elements, and building a page layout. The Mozilla rendering engine, for example, started development in 1997 and by May 2000 was designed to fully support HTML4 rendering requirements, including incremental layout with reflow, CSS, and a Document Object Model. This engine comprised HTML parsing and rendering, along with other functionalities.

Mobile devices, such as PDAs and early cell phones, were already capable of accessing internet content, albeit with significant limitations. WAP (Wireless Application Protocol), introduced in 1999, was a global standard for bringing internet content to mobile phones, but it used Wireless Markup Language (WML) instead of HTML, and suffered from "ridiculously small screens, slow bandwidth, and the need to place a new call every time the device needs to connect." WAP was designed for the "limited capabilities of a mobile device." While WAP browsers could not read HTML pages, some phones were starting to incorporate HTML browsers, such as Microsoft Mobile Explorer. There was a recognized need to adapt web content for these devices.

2. Scalable Graphics and Zooming/Panning in Computing Environments (before June 2000)

The concept of scalable graphics was well-established. Vector graphics, which are images built from mathematical formulas, have a history dating back to the 1940s and 1950s, used in early computer displays due to limited memory, and became prominent in CAD (Computer-Aided Design) and desktop publishing. The World Wide Web Consortium (W3C) adopted Scalable Vector Graphics (SVG) as a standard file format for vector graphics in 1999. SVG files are XML-based and can be executed to draw graphics, mitigating the overhead of downloading image files like BMP, GIF, or JPG.

Zooming and panning as user interaction techniques in graphical interfaces also existed before 2000. For instance, "A Zooming Web Browser" by Benjamin B. Bederson et al. (1996) describes a prototype zooming browser that depicts multiple web pages and links on a large zoomable information surface, where pages are scaled for readability and context, and layout changes are animated. This paper also mentions an extension to HTML called Multi-Scale Markup Language (MSML) to support multi-scale layout within a page, including variable-sized dynamic objects, graphics, and other interface mechanisms, and notes that MSML allowed control over the size of all types of objects, including images and graphics.

Touchscreens themselves had a long history, with multi-touch being implemented as early as 1982 by the University of Toronto's Input Research Group, and touch-sensitive devices with gestures existing in the late 1980s. While "pinch-to-zoom" specifically gained widespread recognition with later devices, the underlying concepts of touch interaction for scaling and manipulating displayed content were present.

Obviousness Combinations and Motivation to Combine:

A PHOSITA in June 2000, facing the challenge of displaying full internet content effectively on mobile devices with small screens and limited resources, would have been motivated to combine existing technologies to overcome the limitations of current mobile browsing solutions like WAP, which delivered a "substandard" experience.

Combination 1: HTML Rendering Engine + Scalable Vector Graphics + Mobile Device Constraints

• HTML Rendering and Processing: It was known to use HTML rendering engines (like Mozilla's, in development since 1997) to parse HTML documents, identify elements, logically group content, and determine page layout with bounding boxes. This is a fundamental aspect of any web browser.
• Scalable Vector Graphics (SVG): The W3C adopted SVG in 1999, recognizing its benefits for scalability, smaller file sizes, and ability to be executed via basic ASCII drawing commands. This was a clear advantage for resource-constrained mobile devices where "traffic is held to a few bytes."
• Motivation to Combine: The motivation to combine these would be to address the well-known problem of displaying fixed-resolution HTML content on small, diverse mobile screens, which often resulted in "miserable usability." A PHOSITA would recognize that translating the fixed-layout HTML output of a rendering engine into a scalable vector format would allow for resolution-independent display, making web content viewable on devices with varying screen sizes and resolutions without degradation. SVG, being a web-native vector format, would be a natural choice for this conversion. The goal would be to "display the web pages in a simple and reasonable way" on handheld devices, as stated in the patent. (DETAILED DESCRIPTION OF THE INVENTION).

This combination directly addresses the first two major steps of the claims: processing HTML to understand its layout and then translating it into a scalable vector representation.

Combination 2: (Combination 1) + Touch-Sensitive Displays + Zoom/Pan Interaction

• Prior art for touch-sensitive displays and interaction: Touchscreens existed for decades, and by the 1990s, single and multi-touch gestures, including zooming, were being explored in various contexts. Concepts of manipulating content on a display via touch, such as tapping to select or performing gestures for zooming, were known. For example, the Pad++ project (Bederson et al., 1995-1998) explored zoomable graphical interfaces. The Bederson 1996 "Zooming Web Browser" specifically mentions "automatic zooming and panning to support navigation" on a "large zoomable information surface."
• Motivation to Combine: Given the small screen sizes of mobile devices, simply scaling content down often made it "difficult to read." (DETAILED DESCRIPTION OF THE INVENTION). Allowing users to interactively zoom and pan through the content, especially using direct manipulation via a touch-sensitive display (which was a feature of some mobile devices like PDAs), would be a highly desirable improvement for usability. A PHOSITA would logically apply known zooming and panning interface techniques, previously seen in other graphical applications or experimental browsers, to the newly vectorized web content on touch-enabled mobile devices. This would directly enable the "user-defined zoom levels by rendering the scalable vector representation on the touch-sensitive display using one or more respective scale factors in response to associated user inputs made via the touch-sensitive display" as claimed.

This combination makes obvious the rendering of the scalable vector representation on a touch-sensitive display with user-controlled zoom and pan, and the preservation of layout and design, which is a key aspect of the claims. The patent explicitly identifies the lack of browser support for zoom as a problem it solves, which indicates the motivation for a PHOSITA to implement such a feature. (BACKGROUND OF THE INVENTION).

Combination 3: (Combination 2) + Datum and Vector Generation for Scalable Rendering

• Vector Graphics Principles: Vector graphics inherently rely on mathematical descriptions (e.g., points, lines, curves) and coordinate systems to enable scaling without loss of quality. CAD software, long using vector graphics, would have established practices for defining origins, object positions, and relationships using vectors.
• HTML Layout Information: HTML rendering engines, by their nature, determine the position and size of elements (bounding boxes) on a page. The patent notes that "the location of each object on a display page will be dependent on previous HTML layout elements." (DETAILED DESCRIPTION OF THE INVENTION).
• Motivation to Combine: Once the decision is made to convert HTML layout to a scalable vector representation, a PHOSITA would find it obvious to use geometric principles common in vector graphics (such as defining datums and vectors) to represent the position and size of HTML objects. This approach provides the underlying structure necessary for efficient and resolution-independent scaling and panning. Connecting "each HTML object with its corresponding page layout information," and then "defining a primary datum" and "an object datum" for "generating a vector from the primary datum to the object datum" (Claim 1) is a standard method of representing spatial relationships in a vector-based system. This mechanical step would be obvious to anyone skilled in graphical rendering once the concept of vectorizing HTML layout for scalability is conceived.

The specific "parsing," "logically grouping content into HTML objects," "generating page layout information including a bounding box for each HTML object," and "storing information that links each HTML object with its corresponding page layout information" are all standard operations performed by an HTML rendering engine. (Claim 1). The translation into a scalable vector representation by defining datums and vectors for these objects is a logical application of known vector graphics principles to the layout information already generated.

In summary, a person having ordinary skill in the art in 2000, motivated by the poor user experience of fixed-resolution web content on small mobile screens and aware of existing HTML rendering techniques, scalable vector graphics, and touch-based interaction paradigms, would have found it obvious to combine these elements to create a system for scalable, zoomable, and pannable display of internet content on mobile devices. The individual components and the underlying problems they solve were known, and the combination would have been a predictable solution to a recognized challenge in mobile web browsing.