Exhibit E-20
`Chart for U.S. Patent No. 9,928,044 (“the ’044 patent”)
`U.S. Patent Appl. Publ. No. 2007/0118844 (“Huang”)
`
`As shown in the chart below, all asserted claims of the ’044 patent are invalid under (1) 35 U.S.C. § 1021 (a), (b), (e), and (g) because
`Huang meets each element of those claims, and (2) 35 U.S.C. § 103 because Huang renders those claims obvious either alone, or in
`combination with the knowledge of a person having ordinary skill in the art, and in further combination with the references
`specifically identified in the following claim chart and/or one or more references identified in Google’s Preliminary Invalidity
`Contentions. As used herein, “Huang” refers to U.S. Patent Appl. Publ. No. 2007/0118844 and includes material incorporated by
`reference, including without limitation U.S. Patent Appl. Ser. No. 11/241,073, subsequently published on April 5, 2007 as U.S. Patent
`Appl. Publ. No. 2007/0079282 to Nachnani (“Nachnani”). Huang constitutes prior art under 35 U.S.C. § 102(a), (b), (e) and (g)
`because it was published by the U.S. Patent Office on May 24, 2007 prior to the alleged priority date of the ’044 patent (January 12,
`2008).
`Motivations to combine the disclosures of Huang with disclosures of other systems available to the public and publications known in
`the art, as shown in this chart, include at least the similarity in subject matter between the references to the extent they concern
`information input devices. Insofar as the references cite other patents or publications, or suggest additional changes, one of ordinary
`skill in the art would look beyond a single reference to other references in the field. One of ordinary skill in the art would have been
`motivated to combine Huang with references and systems such as: U.S. Patent App. Pub. No. 2006/0271537 (“Chandrasekharan”),
`U.S. Patent Publication No. 2007/0067421 (“Angelov”), U.S. Patent Publication No. 2006/0129972 (“Tyburski”). Chandrasekharan,
`Angelov, and Tyburski are in the same or similar technical field as the Huang and the ’044 patent, and addresses the same or similar
`technical problem (e.g., providing software that interfaces to a web service) as the ’044 patent. Accordingly, a POSITA would have
`had reason to consider the teachings of Chandrasekharan, Angelov, and/or Tyburski when implementing the Huang’s system. A
`person of ordinary skill in the art would be motivated to combine Huang with any of these references in order to create more effective
`systems to create displays on devices..
`These invalidity contentions are based on Google’s present understanding of the ’044 patent claims and Express Mobile’s theories of
`infringement against Google. Google expressly does not agree that, under a correct construction or reading of the claims, that
`Google’s accused products meet the limitations of the asserted claims of the ’044 Patent or that the claims satisfy the requirements of
`35 U.S.C. § 112. Google’s contentions herein are not, and should in no way be seen as, admissions as to or adoptions of any particular
`
`1 The ’044 patent is subject to pre-AIA 35 U.S.C. §102.
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0001
`
`

`

`claim scope or construction, or as an admission that any particular element is met by any accused product in any particular way.
`Google objects to any attempt to imply claim construction from this chart. Google’s invalidity contentions do not represent Google’s
`agreement or view as to the meaning, definiteness, written description support for, or enablement of any claim contained therein.
`However, at least under Express Mobile’s apparent application of the claims for the purposes of infringement (which Google
`expressly disagrees with), Huang would have rendered the asserted claims of the ’044 patent invalid.
`The following contentions are subject to revision and amendment pursuant to Federal Rule of Civil Procedure 26(e), the Local Rules
`of the Western District of Texas, and the Orders of record in this matter subject to further investigation and discovery regarding the
`prior art and the Court’s construction of the claims at issue. For example, discovery is ongoing, and Google reserves the right to
`supplement these contentions with references to additional materials and evidence obtained in discovery describing Huang.
`
`Patent No. 9,928,044
`Claim 1
`[preamble] 1. A system for
`generating code to provide content
`on a display of a device, said
`system comprising:
`
`[a] computer memory storing:
`
`[b] a) symbolic names required for
`evoking one or more web
`components each related to a set of
`inputs and outputs of a web service
`obtainable over a network, where
`the symbolic names are character
`strings that do not contain either a
`persistent address or pointer to an
`output value accessible to the web
`service, where each symbolic name
`has an associated data format class
`
`Huang
`
`
`To the extent the preamble is limiting, Huang discloses a system for generating code to provide
`content on a display of a device.
`
`See Exhibit D-20, claim 1, element [preamble].
`Huang discloses a computer memory.
`
`See Exhibit D-20, claim 1, element [a].
`Huang discloses computer memory storing symbolic names required for evoking one or more
`web components each related to a set of inputs and outputs of a web service obtainable over a
`network, where the symbolic names are character strings that do not contain either a persistent
`address or pointer to an output value accessible to the web service, where each symbolic name
`has an associated data format class type corresponding to a subclass of User Interface (UI)
`objects that support the data format type of the symbolic name, and where each symbolic name
`has a preferred UI object.
`
`See Exhibit D-20, claim 1, element [b].
`
`2 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0002
`
`

`

`type corresponding to a subclass of
`User Interface (UI) objects that
`support the data format type of the
`symbolic name, and where each
`symbolic name has a preferred UI
`object, and
`[c] b) an address of the web service; Huang discloses a computer memory storying an address of the web service.
`
`See Exhibit D-20, claim 1, element [c].
`[d] an authoring tool configured to: Huang discloses an authoring tool.
`
`See Exhibit D-20, claim 1, element [d].
`Huang discloses that the authoring tool is configured to define a UI object for presentation on
`the display.
`
`See Exhibit D-20, claim 1, element [d].
`Huang discloses that said defined UI object corresponds to a web component included in said
`computer memory selected from a group consisting of an input of the web service and an output
`of the web service.
`
`See Exhibit D-20, claim 1, element [e]
`
`[e] define a UI object for
`presentation on the display,
`
`[f] where said defined UI object
`corresponds to a web component
`included in said computer memory
`selected from a group consisting of
`an input of the web service and an
`output of the web service,
`[g] where each defined UI object is
`either: 1) selected by a user of the
`authoring tool; or 2) automatically
`selected by the system as the
`preferred UI object corresponding
`to the symbolic name of the web
`component selected by the user of
`the authoring tool,
`
`Huang discloses that the UI object is selected by the user of the authoring tool or automatically
`selected by the system as the preferred UI object corresponding to the symbolic name of the web
`component selected by the user of the authoring tool.
`
`See Exhibit D-20, claim 1, element [e].
`
`3 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0003
`
`

`

`[h] access said computer memory to
`select the symbolic name
`corresponding to the web
`component of the defined UI object,
`
`[i] associate the selected symbolic
`name with the defined UI object,
`where the selected symbolic name
`is only available to UI objects that
`support the defined data format
`associated with that symbolic name,
`[j] store information representative
`of said defined UI object and
`related settings in a database;
`
`Huang discloses the authoring tool is configured to access said computer memory to select the
`symbolic name corresponding to the web component of the defined UI object.
`
`See Exhibit D-20, claim 1, element [f].
`
`Huang discloses the authoring tool is configured to associate the selected symbolic name with
`the defined UI object, where the selected symbolic name is only available to UI objects that
`support the defined data format associated with that symbolic name
`
`See Exhibit D-20, claim 1, element [g].
`
`Huang discloses the authoring tool is configured to store information representative of said
`defined UI object and related settings in a database.
`
`See, e.g., Huang at [0042] (“Applications created by the Designer 104 are stored in Extensible
`Markup Language (XML) format as XML definitions 122 in a database 124, and loaded into the
`Player 106 as the application 111.”).
`
`See, e.g., Nachnani at [0037] (“FIG. 14 is an illustrative drawing of database schemas for storing
`application data according to one embedment of the invention.”).
`
`Id. at [0039] (“The server 106 also sends the application to the Player UI 114 by retrieving an
`Application Definition 108 and any associated Application Data 122, e.g. values for the data
`input form, from the Application Definition table 112 and Application Data table 124,
`respectively, of the database 110.”).
`
`Id. at [0043] (“[D]ata-linkage property, which indicates a source of values for the component,
`e.g. a database column containing values for a selection list, a datatype property, which indicates
`the permitted type of the value 206, and a required property, which indicates whether a value is
`required for the component 204.”).
`
`4 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0004
`
`

`

`Id. at [0044] (“The component properties 208 further include a dataset property, which may
`specify a database column in which the component's value 206 is stored. Because of the
`differences in data representations between the web browser's HTML-based data model, the Java
`object model used by the server, and the relational database model in which data is stored
`persistently, the XML application definition establishes a mapping between application data and
`database data, based on a component naming convention in which a unique name is assigned to
`each component. A DATASET attribute is also assigned to each component. The DATASET
`attribute specifies a database table and column name and thereby binds the component's value to
`a database column. The application data value of the component is stored in the specified
`database column. Multiple instances of application data are stored as separate database rows, so
`that each instance of application data, e.g. each Radiology Order Request instance associated
`with a Radiology Order Request application, is stored as a separate row in the database. The
`unique component name is generated by concatenating the names of enclosing components, such
`as areas and tables, with the component name and numeric counter values as described below.”).
`
`Id. at [0066] (“FIG. 6c illustrates an example database table containing application data
`according to one embodiment of the invention. Database table 512, e.g. a table named
`process_detail stored in the Database 110 of FIG. la, has an "id" column 614, a ‘dtcl’ column
`616 for storage of the date component's value, and an ‘scl’ column 618 for storage of the
`selection list component's value. Database tables that store application data according to one
`embedment are described in more detail below with respect to FIG. 14.”).
`
`Id. at [0106] (“FIG. 9 is a flowchart illustrating a method of saving a specified application
`definition to persistent storage, e.g. to a database, according to one embodiment of the
`invention.”).
`
`Id. at [0130] (“Creating a new application involves the following steps:
`CREATE NEW APPLICATION
`1. A user launches the Application Designer UI.
`2. The user drags and drops components, tables, and the like from the palette to the workspace.
`3. The user updates component properties, selects data types, adds formulas, and the like.
`
`5 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0005
`
`

`

`[k] retrieve said information
`representative of said one or more
`said UI object settings stored in said
`database; and
`
`4. The system stores the new application definition in the database, updates the application mode
`to test, sets the version to 1, and displays the Application List screen. An application name,
`either provided by the user or generated by the system, is determined at or before this step and
`associated with the application.”).
`
`Id. at [0123] “FIG. 13 is an illustrative drawing of a database table schema for storing an
`application definition according to one embedment of the invention. The tables of FIG. 14
`together correspond to the application data table 124 stored in the database 110 of FIG. 1a.”.
`
`Id. at [0124] “FIG. 14 is an illustrative drawing of database table schemas for storing application
`data according to one embedment of the invention. The tables of FIG. 14 together correspond to
`the application data table 124 stored in the database 110 of FIG. 1a.”.
`Huang discloses the authoring tool is configured to retrieve said information representative of
`said one or more said UI object settings stored in said database.
`
`See, e.g., Huang at [0042] (“Applications created by the Designer 104 are stored in Extensible
`Markup Language (XML) format as XML definitions 122 in a database 124, and loaded into the
`Player 106 as the application 111.”).
`
`See, e.g., Nachnani at [0037] (“FIG. 14 is an illustrative drawing of database schemas for storing
`application data according to one embedment of the invention.”).
`
`Id. at [0039] (“The server 106 also sends the application to the Player UI 114 by retrieving an
`Application Definition 108 and any associated Application Data 122, e.g. values for the data
`input form, from the Application Definition table 112 and Application Data table 124,
`respectively, of the database 110.”).
`
`Id. at [0089] (“FIG. 7b is an illustrative drawing of an application displayed in an Application
`Player user interface according to one embodiment of the invention. An Application Player user
`interface, e.g. the Player UI 114 of FIG. la, presents the application to a user and receives
`
`6 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0006
`
`

`

`application data from the user. FIG. 7b shows an example Radiology Order Request application
`721 displayed in an Application Player UI 720. The radiology order request application 721
`includes an area 724, which contains data fields that allow a user to enter application data. The
`input fields shown in FIG. 7b are a Date field 725, a Patient Name field 726, and a Patient Phone
`Number field 727. The application data values associated with the Date and Patient Name fields
`are ‘08/1 l/2005’ and ‘Jane Doe’, respectively. Multiple different application data sets,
`sometimes referred to herein as instances of application data, may be associated with an
`application and stored using distinct identifying numbers or names. For example, the data values
`shown in FIG. 7b, including ‘08/11/2005’, could be saved as a first Radiology Order Request
`application data set, and another set of data values, for example, ‘8/12/2005’ and ‘John Smith’,
`could be saved as a second Radiology Order Request application data set.”).
`
`Id. at [0092] (“The Application List user interface 780 lists applications, templates, and lookups
`that have previously been created using the Application Designer. A user can select an
`application displayed on the Application List 780 for modification in the Application Designer
`or execution in the Application Player.”).
`
`Id. at [0093] (“Each application has a name and a version number. The name is a string, such as
`‘Radiology Order Request’, that identifies the application, and the version number is a number
`that is incremented when an application is modified in the Application Designer. Applications
`can be saved as templates. An application can be in one of three modes: design mode, test mode,
`or production mode.”).
`
`Id. at [0108] (“A user 118 of the Player UI 114 may invoke a command to load a previously-
`saved application, including application data, such as data concerning a particular person or
`transaction, data from the database 110 into the Player UI 114.”).
`
`Id. at [0100] (“The App Designer JSP 852 is a page controller JSP that implements several
`action commands, including getDefinition, saveDefinition, saveDefinitionAsTernplate,
`createNewVersion, and lockdefinition, as described in the table below. These operations are
`invoked in response to corresponding user requests from the Designer UI 805 and Player UI 835.
`COMMAND DESCRIPTION getDefinition Returns a Definition Javascript object.
`
`7 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0007
`
`

`

`[l] build an application consisting
`of one or more web page views
`from at least a portion of said
`database utilizing at least one
`player,
`
`saveDefinition Saves a Definition to the database and unlocks the Definition for edits by other
`users. saveDefinitionAsTemplate Saves a Definition to the database and marks it as a template.
`createNewVersion Creates a new version of a Definition. lockDefinition Marks a Definition as
`locked before a user edits the Definition.”).
`
`Id. at [0131] (“When these steps are complete, the new application screen has been saved in test
`mode and is available for initiating test routings and deployment to production. Creating a new
`application from a template involves the same steps, except step 1 includes launching the
`Application Designer UI with a selected template UI displayed in the workspace.”).
`Huang discloses the authoring tool is configured to build an application consisting of one or
`more web page views from at least a portion of said database utilizing at least one player.
`
`See, e.g., Huang at [0042] (“Applications created by the Designer 104 are stored in Extensible
`Markup Language (XML) format as XML definitions 122 in a database 124, and loaded into the
`Player 106 as the application 111.”).
`
`Id. at [0040] (“The Player 106 is a computer program that provides a user interface which
`executes a browser based application 111, which can receive values from web services, send
`values to web services, and invoke other operations provided by web services.”)
`
`Id. at [0041] (“The web pages may be, for example, Java Server Pages (JSP) or Java Server
`Faces (JSF) pages, and may include HTML and JavaScript™ code that implements the Designer
`104 and Player 106.”).
`
`Id. at [0057] (“As described above with reference to FIG. 1A, an application running in an
`Application Player 106, which is in turn running in the browser 101, interacts with the WS
`Factory 120 running in a server 120.”).
`
`See, e.g., Nachnani at [0037] (“FIG. 14 is an illustrative drawing of database schemas for storing
`application data according to one embedment of the invention.”).
`
`8 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0008
`
`

`

`
`Id. at [0039] (“Application Data 120 may be provided by the user 118 when the Player UI 114
`executes the application. The Application Data 120 may include, for example, data entered by a
`user, such as data concerning a particular person or transaction. An application may include
`dynamic behavior, calculations, lookups, validations, and linkages to other data via, for example,
`a Uniform Resource Locator (URL) query string.”).
`
`Id. at [0039] (“The server 106 also sends the application to the Player UI 114 by retrieving an
`Application Definition 108 and any associated Application Data 122, e.g. values for the data
`input form, from the Application Definition table 112 and Application Data table 124,
`respectively, of the database 110.”).
`
`Id. at [0051] (“However, such client invocations are useful because they allow a user to write
`Scripts in a language such as JavaScriptTM to customize the behavior of applications.”).
`
`Id. at [0075] (“[A]ny programming language may be used to implement the features described
`herein.”).
`
`Id. at [0079] (“A web service invocation can also be made from the Internet Browser 101 by a
`call embedded in the web page, e.g. a Java TM language call embedded in a Java TM Server
`Page (JSP) that provides the application player 106.”).
`
`Id. at [0089] (“FIG. 7b is an illustrative drawing of an application displayed in an Application
`Player user interface according to one embodiment of the invention. An Application Player user
`interface, e.g. the Player UI 114 of FIG. la, presents the application to a user and receives
`application data from the user. FIG. 7b shows an example Radiology Order Request application
`721 displayed in an Application Player UI 720. The radiology order request application 721
`includes an area 724, which contains data fields that allow a user to enter application data. The
`input fields shown in FIG. 7b are a Date field 725, a Patient Name field 726, and a Patient Phone
`Number field 727. The application data values associated with the Date and Patient Name fields
`are ‘08/1 l/2005’ and ‘Jane Doe’, respectively. Multiple different application data sets,
`
`9 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0009
`
`

`

`sometimes referred to herein as instances of application data, may be associated with an
`application and stored using distinct identifying numbers or names. For example, the data values
`shown in FIG. 7b, including ‘08/11/2005’, could be saved as a first Radiology Order Request
`application data set, and another set of data values, for example, ‘8/12/2005’ and ‘John Smith’,
`could be saved as a second Radiology Order Request application data set.”).
`
`Id. at [0093] (“Each application has a name and a version number. The name is a string, such as
`‘Radiology Order Request’, that identifies the application, and the version number is a number
`that is incremented when an application is modified in the Application Designer. Applications
`can be saved as templates. An application can be in one of three modes: design mode, test mode,
`or production mode.”).
`
`Id. at [0099] (“The Designer UI 805 and Player UI 835 are presented to a user as web pages. The
`web pages are provided by the server 850 to the web browsers 802 and 832 via the network 809
`when a user enters a corresponding URL into the web browser. On the server, these web pages
`are App Designer JSP 852 and App Player JSP 860, for the designer and player, respectively.
`The web browser presents clients 803 and 833 to the user by displaying web pages generated by
`the App Designer JSP 852 and App Player JSP 860, respectively. These generated web pages
`include JavaScript code that uses JavaScript Client Components 807 and 837 to implement the
`Designer and Player user interfaces.”).
`
`Id. at [0100] (“The App Designer JSP 852 is a page controller JSP that implements several
`action commands, including getDefinition, saveDefinition, saveDefinitionAsTemplate,
`createNewVersion, and lockdefinition, as described in the table below. These operations are
`invoked in response to corresponding user requests from the Designer UI 805 and Player UI 835.
`COMMAND DESCRIPTION getDefinition Returns a Definition Javascript object.
`saveDefinition Saves a Definition to the database and unlocks the Definition for edits by other
`users. saveDefinitionAsTemplate Saves a Definition to the database and marks it as a
`template.”).
`
`Id. at [0129] (“Specific examples of how an application design and deployment system is used
`will now be described. Each example includes a set of steps to be performed by the user and the
`
`10 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0010
`
`

`

`system. The examples include creating an application, saving an application, saving an
`application as a template, editing an application in test mode, previewing an application in
`design mode, initiating test routings in test mode, editing saved routings in test mode, saving a
`new application version in test mode, deploying an application to production mode, deactivating
`an application from production mode, copying an application from production mode to test
`mode, and deleting an application in test mode. A routing is, for example, a message that
`transmits an application between users. Such as an email message that contains a URL link to an
`application.”).
`
`Id. at [0131] (“When these steps are complete, the new application screen has been saved in test
`mode and is available for initiating test routings and deployment to production. Creating a new
`application from a template involves the same steps, except step l includes launching the
`Application Designer UI with a selected template UI displayed in the workspace.”).
`
`Id. at [0130]-[0134] (“Creating a new application involves the following steps: . . . When these
`steps are complete, the new application screen has been saved in test mode and is available for
`initiating test routings and deployment to production. Creating a new application from a
`template involves the same steps, except step I includes launching the Application Designer UI
`with a selected template UI displayed in the workspace. Editing an application in test mode
`involves the following steps: . . . When these steps are complete, the application definition has
`been updated and saved in test mode, The application definition is available for initiating test
`routings and for deployment to production mode, 0, 134) Initiating test routings in test mode
`involves the following steps: . . . .”).
`Huang discloses that the player utilizes information stored in said database to generate for the
`display of at least a portion of said one or more web pages.
`
`See, e.g., Huang at [0042] (“Applications created by the Designer 104 are stored in Extensible
`Markup Language (XML) format as XML definitions 122 in a database 124, and loaded into the
`Player 106 as the application 111.”).
`
`
`11 of 14
`
`[m] where said player utilizes
`information stored in said database
`to generate for the display of at
`least a portion of said one or more
`web pages,
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0011
`
`

`

`See, e.g.,Nachnani at [0037] “FIG. 14 is an illustrative drawing of database schemas for storing
`application data according to one embedment of the invention.”.
`
`Id. at [0039] (“Application Data 120 may be provided by the user 118 when the Player UI 114
`executes the application. The Application Data 120 may include, for example, data entered by a
`user, such as data concerning a particular person or transaction. An application may include
`dynamic behavior, calculations, lookups, validations, and linkages to other data via, for example,
`a Uniform Resource Locator (URL) query string.”).
`
`Id. at [0039] (“The server 106 also sends the application to the Player UI 114 by retrieving an
`Application Definition 108 and any associated Application Data 122, e.g. values for the data
`input form, from the Application Definition table 112 and Application Data table 124,
`respectively, of the database 110.”).
`
`Id. at [0089] (“FIG. 7b is an illustrative drawing of an application displayed in an Application
`Player user interface according to one embodiment of the invention. An Application Player user
`interface, e.g. the Player UI 114 of FIG. la, presents the application to a user and receives
`application data from the user. FIG. 7b shows an example Radiology Order Request application
`721 displayed in an Application Player UI 720. The radiology order request application 721
`includes an area 724, which contains data fields that allow a user to enter application data. The
`input fields shown in FIG. 7b are a Date field 725, a Patient Name field 726, and a Patient Phone
`Number field 727. The application data values associated with the Date and Patient Name fields
`are ‘08/1 l/2005’ and ‘Jane Doe’, respectively. Multiple different application data sets,
`sometimes referred to herein as instances of application data, may be associated with an
`application and stored using distinct identifying numbers or names. For example, the data values
`shown in FIG. 7b, including ‘08/11/2005’, could be saved as a first Radiology Order Request
`application data set, and another set of data values, for example, ‘8/12/2005’ and ‘John Smith’,
`could be saved as a second Radiology Order Request application data set.”).
`
`Id. at [0099] (“The Designer UI 805 and Player UI 835 are presented to a user as web pages. The
`web pages are provided by the server 850 to the web browsers 802 and 832 via the network 809
`when a user enters a corresponding URL into the web browser. On the server, these web pages
`
`12 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0012
`
`

`

`are App Designer JSP 852 and App Player JSP 860, for the designer and player, respectively.
`The web browser presents clients 803 and 833 to the user by displaying web pages generated by
`the App Designer JSP 852 and App Player JSP 860, respectively. These generated web pages
`include JavaScript code that uses JavaScript Client Components 807 and 837 to implement the
`Designer and Player user interfaces.”).
`Huang discloses that when the application and player are provided to the device and executed on
`the device
`
`See Exhibit D-20, claim 1, element [j].
`Huang discloses that when the user of the device provides one or more input values associated
`with an input symbolic name to an input of the defined UI object, the device provides the user
`provided one or more input values and corresponding input symbolic name to the web service.
`
`See Exhibit D-20, claim 1, element [j].
`
`Huang discloses that the web service utilizes the input symbolic name and the user provided one
`or more input values for generating one or more output values having an associated output
`symbolic name.
`
`See Exhibit D-20, claim 1, element [k].
`
`Huang discloses that the player receives the output symbolic name and corresponding one or
`more output values and provides instructions for the display of the device to present an output
`value in the defined UI object.
`
`See Exhibit D-20, claim 1, element [l].
`
`[n] wherein when the application
`and player are provided to the
`device and executed on the device,
`and
`
`[o] when the user of the device
`provides one or more input values
`associated with an input symbolic
`name to an input of the defined UI
`object, the device provides the user
`provided one or more input values
`and corresponding input symbolic
`name to the web service,
`[p] the web service utilizes the
`input symbolic name and the user
`provided one or more input values
`for generating one or more output
`values having an associated output
`symbolic name,
`[q] and the player receives the
`output symbolic name and
`corresponding one or more output
`values and provides instructions for
`the display of the device to present
`an output value in the defined UI
`object.
`
`13 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0013
`
`

`

`Claim 2
`2. The system of claim 1, where
`said system stores information in a
`registry, and wherein the registry
`includes definitions of input and
`output related to said web service.
`Claim 7
`7. The system of claim 1, where
`said web component is an output of
`a web service, is the text provided
`by one or more simultaneous chat
`sessions, is the video of a video
`chat session, is a video, an image, a
`slideshow, an RSS display, or an
`advertisement.
`Claim 11
`11. The system of claim 1, where
`said code is provided over said
`network.
`
`
`
`
`
`Huang discloses said system stores information in a registry, and wherein the registry includes
`definitions of input and output related to said web service.
`
`See Exhibit D-20, claim 1, elements [a] and [b]; claim 2.
`
`
`Huang discloses that where said web component is an output of a web service, is the text
`provided by one or more simultaneous chat sessions, is the video of a video chat session, is a
`video, an image, a slideshow, an RSS display, or an advertisement.
`
`See Exhibit D-20, claim 7.
`
`
`Huang discloses that said code is provided over said network.
`
`See Exhibit D-20, claim 11.
`
`14 of 14
`
`Adobe v. Express Mobile - IPR2021-01225
`PO_EM044_2005-0014
`
`