throbber
1. A system for generating code to provide content on a display of a device, said system
`comprising:
`
`computer memory storing a registry of:
`
`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, andwhere 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 has a preferred UI
`object, and
`
`b) thean address of the web service;
`
`an authoring tool configured to:
`
`define a user interface (UI) object for presentation on the display,
`
`where said defined UI object corresponds to thea web component included in said
`registry selected from thea group consisting of an input of the web service and an
`output of the web service, 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,
`
`access said computer memory to select the symbolic name corresponding to the web
`component of the defined UI object,
`
`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, and
`
`produce an Application including the selected symbolic name of the defined UI
`object, where said Application is a device-independent code,; and
`
`produce a Player, where said Player is a device-dependent code;
`such that, wherein, when the Application and Player are provided to the device and
`executed on the device, and when athe user of the device provides one or more input
`values associated with an input symbolic name to an input of the defined UI object,
`
`1) the device provides the user provided one or more input values and corresponding
`input symbolic name to the web service,
`
`SAP Exhibit 1017
`SAP v. Express Mobile, Inc.
`IPR2021-01145
`Page 00001
`
`

`

`2) 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,
`3) said Player receives the output symbolic name and corresponding one or more
`output values and provides instructions for athe display of the device to present an
`output value in the defined UI object.
`
`
`3. The system of claim 1, where said web component is a text chat, a video chat, an image, a
`slideshow, a video, or an RSS feed.
`
`5. The system of claim 1, where said UI object is an input field for a web service.
`
`6. The system of claim 1, where said UI object is an input field usable to obtain said web
`component, where said input field includes a text field, a scrolling text box, a check box, a drop
`down-menu, a list menu, or a submit button.
`
`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.
`
`11. The system of claim 1, where said code is provided over said network.
`
`12. The system of claim 1, wherein said defined UI object corresponds to a widget.
`
`13. The system of claim 1, where said Player is activated and runs in a web browser.
`
`15. A method of displaying content on a display of a device having a Player, where said Player is
`a device-dependent code, said method comprising:
`
`
`12. A method of displaying content on a defining a user interface (UI) object for presentation
`on the display of a device utilizing , where said UI object corresponds to a web component
`included in a registry of one or more web components related to inputs and outputsselected
`from a group consisting of an input of a web service obtainable over a networkand an output
`of the web service, where each web component includes a plurality of symbolic names of
`inputs and outputs associated with each web service, and where the registry includes: a)
`symbolic names required for evoking one or more web components each related to a set of
`inputs and outputs of athe 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, and b) an address of the web service, and where each
`defined UI object is either: 1) selected by a user of an authoring tool; or 2) automatically
`selected by a system as a preferred UI object corresponding to a symbolic name of the web
`component selected by the user of the authoring tool;
`
`b) the address of the web service, said method comprising:
`
`
`
`
`
`-2-
`
`IPR2021-01145 Page 00002
`
`

`

`defining a user interface (UI) object for presentation on the display, where said UI object
`corresponds to a web component included in said registry selected from the group
`consisting of an input of the web service and an output of the web service;
`selecting athe symbolic name from said web component corresponding to the defined UI
`object, where the selected symbolic name has an associated data format class type
`corresponding to a subclass of UI objects that support the data format type of the symbolic
`name, and has the preferred UI object;
`
`associating the selected symbolic name with the defined UI object; and
`
`
`producing an Application including the selected symbolic name of the defined UI object,
`where said Application is a device-dependentdevice-independent code; and
`, whereinproducing a Player, where said Player is a device-dependent code;
`such that, when the Application and Player are provided to the device and executed on the
`device, and when athe user of the device provides one or more input values associated with
`an input symbolic name to an input of the defined UI object,
`
`1) the device provides the user provided one or more input values and corresponding input
`symbolic name to the web service,
`
`2) 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,
`
`3) said Player receives the output symbolic name and corresponding one or more output
`values and provides instructions for athe display of the device to present an output value in
`the defined UI object.
`
`
`1417. The method of claim 1215, where said web component is a text chat, a video chat, an
`image, a slideshow, a video, or an RSS feed.
`
`1619. The method of claim 1215, where said UI object is an input field for a web service.
`
`1720. The method of claim 1215, where said UI object is an input field usable to obtain said web
`component, where said input field includes a text field, a scrolling text box, a check box, a drop
`down-menu, a list menu, or a submit button.
`
`1821. The method of claim 1215, 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.
`
`2124. The method of claim 1215, and such that said Player interprets dynamically received,
`device-independentdevice independent values of the web component defined in the Application.
`
`2225. The method of claim 1215, further comprising:
`
`
`providing said Application and Player over said network.
`
`
`
`-3-
`
`IPR2021-01145 Page 00003
`
`

`

`26. The method of claim 15, wherein said UI object corresponds to a widget.
`
`27. The method of claim 15, where said Player is activated and runs in a web browser.
`
`-4-
`
`IPR2021-01145 Page 00004
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket