`
`Technical Field of the Invention
`
`[0001]
`
`Present invention relates to providing digital content to an output
`
`device and, in particular, to providing pervasive output in which an
`
`information apparatus can pervasively output digital content to an output
`
`device regardless of the processing power, display screen size and memory
`
`space of the information apparatus.
`
`Background and Summary of the Invention
`
`[0002]
`
`As described herein, information apparatuses refer generally to
`
`computing devices, which include both stationary computers and mobile
`
`computing devices (pervasive devices). Examples of such information
`
`apparatuses include, without limitation, desktop computers, laptop
`
`computers, networked computers, palmtop computers (hand-held
`
`computers), personal digital assistants (PDAs), Internet enabled mobile
`
`phones, smart phones, pagers, digital capturing devices (e.g., digital
`
`cameras and video cameras), Internet appliances, e-books, information
`
`pads, and digital or web pads. An output device may include any one or
`
`more of fax machines, printers, copiers, image and/or video display devices
`
`(e.g., televisions, monitors and projectors), and audio output devices.
`
`[0003]
`
`For simplicity and convenience, hereafter, the following description
`
`may refer to an output device as a printer and an output process as printing.
`
`However, it should be understood that the term printer and printing used in
`
`the discussion of present invention may refer to a specific example used to
`
`simplify description or may be one exemplary embodiment. The reference
`
`to printer and printing used here is intended to be applied or extended to the
`
`larger scope and definition of output devices and should not be construed as
`
`restricting the scope and practice of present invention.
`
`[0004]
`
`Fueled by ever-increasing bandwidth and processing power and
`
`ever-increasing numbers of wireless mobile devices and available software
`
`applications for pervasive devices, millions of users are or will be creating,
`
`1
`
`ROKU EXH. 1010
`
`
`
`downloading, and transmitting content and information using their pervasive
`
`computing devices. As a result, there is a need to allow users to easily
`
`output content and information from their pervasive computing devices to
`
`any output device. People need to output directly and conveniently from
`
`their pervasive information apparatus, without depending on synchronizing
`
`with a stationary computer (e.g., desktop personal computer) for printing, as
`
`an example.
`
`[0005]
`
`To illustrate, an information worker at an airport receiving Email in his
`
`hand-held computer may want to walk up to a nearby printer or fax machine
`
`to have his e-mail printed. In addition, the mobile worker may also want to
`
`print a copy of his to-do list, appointment book, business card, and his flight
`
`schedule from his mobile device. As another example, a user reading a
`
`news article using his/her Internet-enabled pager or mobile phone may want
`
`to print out the complete article instead of reading it through the small
`
`screen on the pager or mobile device. In still another example, a user
`
`visiting an e-commerce site using his mobile phone may want to print out
`
`pictures of the product he/she is buying because the pictures (image and/or
`
`graphics) may not be displayed on the small screen of his/her mobile phone.
`
`In yet another example, a user who takes a picture with a digital camera
`
`may want to easily print it out to a nearby printer. In still another example, a
`
`user with a mobile device may want to simply walk up to a printer and
`
`conveniently print a file that is stored on the mobile device or that is stored
`
`on a network (e.g., Internet, corporate network) and accessible from the
`
`mobile device, such as a PowerPoint® display application document, word
`
`processing document, or a document in any other file format such as PDF,
`
`HTML, JPEG etc. In addition, a user should also be able to print a web
`
`page or a book or a report published on the Internet. Finally, a user may
`
`want to output a complete web page or any document or file to a larger
`
`display screen nearby, even though the small screen of his/her mobile
`
`device cannot completely display or open a document of such a size.
`
`2
`
`ROKU EXH. 1010
`
`
`
`[0006]
`
`Conventionally, an output device (e.g., a printer) is connected to an
`
`information apparatus via a wired connection such as a cable line. A
`
`wireless connection is also possible by using, for example, radio
`
`communication or infrared communication. Regardless of wired or wireless
`
`connection, a user must first install in the information apparatus an output
`
`device driver (e.g., printer driver in the case the output device is a printer)
`
`corresponding to a particular output device model and make. Using a
`
`device-dependent or specific driver, the information apparatus may process
`
`output content or digital document into a specific output device's input space
`
`(e.g., printer input space). The output device input space corresponds to the
`
`type of input that an output device (e.g., a printer) understands (herein
`
`referred to as output data or print data in the case the output device is a
`
`printer). For example, the printer input space or print data may include
`
`printer specific input format (e.g., one or more of an image format, graphics
`
`format, text format, audio format, video format, file format, and data format),
`
`encoding, language (e.g., page description language, markup language etc),
`
`instructions, protocols or data that can be understood or used by a particular
`
`printer make and model.
`
`[0007]
`
`Output data may be proprietary or published or a combination of the
`
`two. An output device's input space or output data is therefore, in general,
`
`device dependent. Different output device models may have their own input
`
`spaces specified, designed or adopted by the output device manufacturer
`
`(e.g., the printer manufacturer) according to a specification for optimal
`
`operation. Consequently, different output devices usually require use of
`
`specific output device drivers (e.g., printer drivers) for accurate output (e.g.,
`
`printing). For example, a printer driver may control, manage, communicate,
`
`and output print data to a printer. Sometimes, instead of using a device
`
`driver (e.g., printer driver), the device driving feature may be included or as
`
`part of an application software.
`
`[0008]
`
`Installation of a device driver (e.g., printer driver) or application may
`
`be accomplished by, for example, manual installation using a CD or floppy
`
`3
`
`ROKU EXH. 1010
`
`
`
`disk supplied by the printer manufacturer. Or alternatively, a user may be
`
`able to download that particular driver or application from a network. For a
`
`home or office user, this installation process may take anywhere from
`
`several minutes to several hours depending on the type of driver and user's
`
`sophistication level with computing devices and networks. Even with plug(cid:173)
`
`and-play driver installation, the user is still required to execute a multi-step
`
`process for each printer or output device.
`
`[0009]
`
`This installation and configuration process adds a degree of
`
`complexity and work to end-users who may otherwise spend their time doing
`
`other productive or enjoyable work. Moreover, many unsophisticated users
`
`may be discouraged from adding new peripherals (e.g., printers, scanners,
`
`etc.) to their home computers or networks to avoid the inconvenience of
`
`installation and configuration. Therefore, there is a need to provide a
`
`manner in which a user can more conveniently or easily output digital
`
`content to an output device without the inconvenience of finding and
`
`installing new device drivers or printer drivers.
`
`[0010]
`
`In addition, conventional output or printing methods may pose
`
`significantly higher challenges and difficulties for mobile device users than
`
`for home and office users. The requirement for pre-installation of a device(cid:173)
`
`dependent driver diminishes the benefit and concept of mobile (pervasive)
`
`computing and output. For example, a mobile user may want to print or
`
`output e-mail, PowerPoint® presentation documents, web pages, or other
`
`documents in an airplane or at an airport, gas station, convenient store,
`
`kiosk, hotel, conference room, office, home, etc. It is highly unlikely that the
`
`user would find at any of these locations a printer of the same make and
`
`model as is at the user's base station. It is usually not a viable option to pre(cid:173)
`
`install all of the possible hundreds, or even thousands, of printer drivers or
`
`device drivers available to the user's information apparatus.
`
`[0011]
`
`As a consequence, the user would currently have to install and
`
`configure a printer driver each time at each such remote location before
`
`printing. Moreover, the user may not want to be bothered with looking for a
`
`4
`
`ROKU EXH. 1010
`
`
`
`driver or downloading it and installing it just to print out or display one page
`
`of email at the airport. This is certainly an undesirable and discouraging
`
`process to promote pervasive or mobile computing. Therefore, a more
`
`convenient or automated printing and output solution is needed so that a
`
`user can simply walk up to an output device (e.g., printer or display device)
`
`and easily output a digital document without having to install or pre-install a
`
`particular output device driver (e.g., printer driver).
`
`[0012]
`
`Another challenge for mobile users is that many mobile information
`
`apparatuses have limited memory space, processing capacity and power.
`
`These limitations are more apparent for small and low-cost mobile devices
`
`including, for example, PDAs, mobile phones, screen phones, pagers, e(cid:173)
`
`books, Internet Pads, Internet appliances etc. Limited memory space poses
`
`difficulties in installing and running large or complete printer or device
`
`drivers, not to mention multiple drivers for a variety of printers and output
`
`devices. Slow processing speed and limited power supply create difficulties
`
`driving an output device. For example, processing or converting a digital
`
`document into output data by a small mobile information apparatus may be
`
`so slow that it is not suitable for productive output. Heavy processing may
`
`also drain or consume power or battery resources. Therefore, a method is
`
`needed so that a small mobile device, with limited processing capabilities,
`
`can still reasonably output digital content to various output devices.
`
`[0013]
`
`Finally, some small mobile devices with limited display screens, such
`
`as mobile phones, may in some cases be limited to display only a few lines
`
`of text. Browsing the Internet with such devices can be a disappointing
`
`experience when viewing, for example, complex web pages containing rich
`
`formats, graphics, and images. Furthermore, some small mobile devices
`
`may not have appropriate applications to display complex documents or
`
`languages such as PDF-format files, word processing documents and
`
`PowerPoint® presentation documents etc. Typically, if an application is
`
`available, displaying complex original documents on small mobile devices
`
`may require downsizing the document or page into, for example, a few lines
`
`5
`
`ROKU EXH. 1010
`
`
`
`of text. As an example, WAP protocol, I-Mode, and web clipping among
`others may downsize, reduce or truncate information on the original web
`page for display on mobile devices. Therefore, it is desirable to allow mobile
`users to output from their small information apparatuses to an output device
`the full richness of the original document content.
`One implementation of the present invention provides an easy,
`friendly and convenient process for digital output. Unlike conventional
`output or printing, a user does not have to manually pre-install a device
`driver (e.g., printer driver) from a CD, floppy disk, or download the driver
`somewhere from a network. This is well-suited for providing output
`capability to small and lower-cost mobile devices with limited memory
`
`space, power supply and processing capability to still be able to output or
`print to an output device.
`In addition, this allows small mobile devices with limited display,
`processing power, and memory to be able to output a digital document (e.g.,
`PDF, HTML, PowerPoint etc) in its full original richness, without resorting to
`downsizing, truncating, reducing, clipping or otherwise altering the original
`document. A user can output the original content or document even when
`the small mobile device cannot display or fully display the original digital
`document or content.
`Finally, one implementation provides a convenient method allowing
`users to output to an output device with or without connection to a static
`network. Through local communication and synchronization between
`information apparatus and output device, hardware and software installation
`for static or permanent network connectivity may not be necessary for the
`output device.
`Additional objects and advantages of the present invention will be
`apparent from the detailed description of the preferred embodiment thereof,
`which proceeds with reference to the accompanying drawings.
`
`[0014]
`
`[0015]
`
`[0016]
`
`[0017]
`
`6
`
`ROKU EXH. 1010
`
`
`
`[0018]
`
`Brief Description of the Drawings
`Fig. 1 is a block diagram of a pervasive output system that can
`
`implement the process and apparatus of the present invention.
`
`[0019]
`
`Figs. 2A and 28 are block diagrams illustrating exemplary
`
`configurations of hardware components of wireless communication units.
`
`[0020]
`
`Figs. 3A~3C illustrate various configurations and implementations of
`
`output controller with respect to an output device such as a printer.
`
`[0021]
`
`Fig. 4 is a flow diagram of a pervasive output process of the present
`
`invention.
`
`[0022]
`
`Fig. 5 is a flow diagram of an exemplary implementation of a
`
`discovery process optionally included in the output process of Fig. 4.
`
`[0023]
`
`Fig. 6 is a flow diagram of an exemplary client application process
`
`included in the output process of Fig. 4.
`
`[0024]
`
`Fig. 7 is a flow diagram of an exemplary server application process
`
`utilized in the output process of Fig. 4.
`
`[0025]
`
`Fig. 8 is a flow diagram of an exemplary final output process for
`
`pervasive output.
`
`[0026]
`
`Figs. 9A - 9F show a series of exemplary graphical user interfaces
`
`(GUls) rendered at different times on a display screen of an information
`
`apparatus.
`
`[0027]
`
`Fig. 1 OA is an exemplary block diagram of a conventional printing
`
`system or printer with a conventional printer controller.
`
`[0028]
`
`Fig. 1 OB is an exemplary block diagram of a conventional output
`
`system or an output device such as a printing system or printer that does not
`
`include a conventional printer controller.
`
`[0029]
`
`Detailed Description of Preferred Embodiments
`Sets forth below are definitions of terms that are used in describing
`
`implementations of the present invention. These definitions are provided to
`
`facilitate understanding and illustration of implementations of the present
`
`7
`
`ROKU EXH. 1010
`
`
`
`invention and should in no way be construed as limiting the scope of the
`
`invention to a particular example, class, or category.
`
`(0030] Objects
`
`[0031]
`
`An object may refer to a software and data entity, which may reside in
`
`different hardware environments or platforms or applications. An object may
`
`encapsulate within itself both data and attributes describing the object, as
`
`well as instructions for operating that data. For simplicity of discussion, an
`
`object may also include, for example, the concept of software components
`
`that may have varying granularity and can consist of one class, a composite
`
`of classes, or an entire application.
`
`[0032]
`
`It is important to note that the term object is not limited to software or
`
`data as its media. Any entity containing information, descriptions, attributes,
`
`data, instructions etc. in any computer-readable form or medium such as
`
`hardware, software, files based on or including voice, text, graphics, image,
`
`or video information, electronic signals in analog or digital form, etc., are all
`
`valid forms of object definition.
`
`[0033]
`
`An object may also contain in one of its fields or attributes a reference
`
`or pointer to another object, or a reference or pointer to data and or content.
`
`(The terms reference and pointer may be used interchangeably herein.) A
`
`reference to an object or any entity or content may include one or more, or a
`
`combination of, pointers, identifiers, names, paths, addresses or any
`
`descriptions relating to a location where an object, data, or content can be
`
`found. Examples of reference may include universal resource identifier
`
`scheme (URI), uniform resource locator (URL), IP address, file names,
`
`directory pointers, software object and component pointers, and run-time
`
`address, among others.
`
`[0034]
`
`By way of example, a document object described in the present
`
`invention may contain or encapsulate one or more digital documents and/or
`
`one or more pointers or references to digital documents. Therefore,
`
`moving or passing document objects in connection with the present
`
`invention may include moving or passing (1) actuat digital content or (2)
`
`8
`
`ROKU EXH. 1010
`
`
`
`reference to the actual content or (3) both. It will be appreciated that the
`
`document object can be quite small and lightweight if it does not also
`
`contain the digital document. These are examples of valid implementations
`
`and may be used in the description of present invention. Different
`
`implementations in different situations can be easily discerned and
`
`recognized by persons of ordinary skill in the art.
`
`[0035]
`
`An object can reside anywhere in a network and can be transmitted to
`
`different environments, platforms, or applications. Downloading or
`
`transferring an object over the network may involve protocols such as file
`
`transfer protocol (FTP) or hypertext transfer protocol (http), among others.
`
`Transferring an object may also involve using messages or other methods
`
`through an object or component model. Three major objects used and
`
`described in present invention are output device object (or printer object in
`
`the case the output device is a printer), job object, and document object.
`
`[0036]
`
`Output Device Object (or Printer Object in the case the output device is a
`
`printer)
`
`[0037]
`
`An output device object may contain one or more attributes that may
`
`identify and describe, for example, the capabilities and functionalities of a
`
`particular output device such as a printer. An output device object may be
`
`stored in the memory component of an output device. As described below
`
`in greater detail, an information apparatus requesting output service may
`
`communicate with an output device. During such local service negotiation,
`
`at least a partial output device object may be uploaded to the information
`
`apparatus from the output device. By obtaining the output device object (or
`
`printer object in the case of a printer), the information apparatus may learn
`
`about the capability, compatibility, identification, and service provided by the
`
`output device.
`
`[0038]
`
`As an example, an output device object or printer object may contain
`
`one or more of the following fields and or attribute descriptions. Each of
`
`following fields may be optional, and furthermore, each of the following fields
`
`9
`
`ROKU EXH. 1010
`
`
`
`or attributes may or may not exist in a particular implementation (e.g., may
`
`be empty or NULL).
`
`•
`
`Identification of an output device (e.g., brand, model, registration, IP
`
`address etc.)
`
`• Services and feature sets provided by an output device (e.g., color or
`
`grayscale output, laser or inkjet, duplex, output quality, price per page,
`
`quality of service, etc.)
`
`• The type of input languages, formats, and or output data (e.g.,
`
`Postscript, PCL, XML, RTL, etc.) supported by an output device.
`
`• Device specific or dependent profiles (e.g., output device profiles,
`
`printer profiles, color profiles, halftoning profiles, communication
`
`profiles etc.). Device profiles may include information such as color
`
`tables, resolution, halftoning, dpi (dots-per-inch), bit depth, page size,
`
`printing speed, etc. One or multiple profiles may exist.
`
`• Payment information on a plurality of services provided by an output
`
`device.
`
`•
`
`Information or security requirements and type of authentication an
`
`output device supports.
`
`• Date and version of the output device object (e.g., printer object).
`
`• Software components containing algorithms or instructions or data,
`
`which may be uploaded to run in an information apparatus, as
`
`described with reference to Fig. 1. For example, a graphical user
`
`interface (GUI) software component may be uploaded to an
`
`information apparatus. The software component may be incorporated
`
`into or launched in the information apparatus by a client application of
`
`present invention to capture a user's preferences (e.g., print quality,
`
`page layout, number of copies, number of card per page, etc.). The
`
`client application may capture these user preferences and create a job
`
`object, as described below.
`
`• Pointer or reference to any one or more output device parameters
`
`(output device parameters include one or more of the above described
`
`10
`
`ROKU EXH. 1010
`
`
`
`output device object fields and or attribute descriptions). For example,
`
`a more up-to-date or original version of output device parameters may
`
`sometimes be stored in a network node. An output device or may
`
`include pointer or pointers to these output device parameters.
`
`• Pointer or reference to another object or objects, including output
`
`device object, job object (described below) or document object.
`
`[0039]
`
`Job Object
`
`[0040]
`
`A job object may contain attributes and information that describe an
`
`output job. A user may provide some or all of these attributes, preferences
`
`and or information about the output job consciously by, for example,
`
`specifying his/her preference through a GUI or through defaults in his/her
`
`information apparatus. Alternatively or in combination, a job object may be
`
`obtained without active user intervention. In one instance, default
`
`parameters may be provided, obtained, negotiated or calculated without
`
`user knowledge.
`
`[0041]
`
`Examples of attributes and information contained in a job object may
`
`include one or more of the following, among others. Each of following fields
`
`may be optional, and furthermore, each of the following fields or attributes
`
`may or may not exist in a particular implementation (e.g., may be empty or
`NULL):
`
`• Preferences such as print quality, page layout, number of pages, number
`
`of cards per page, output size, color or grayscale, among others.
`
`•
`
`Information on security, auth~ntication, payment, subscription,
`
`identification among others.
`
`•
`
`Information on priority or quality of service.
`
`• Status information of the output job or process.
`
`• Job instructions such as queuing, cancellation, execution, output priority
`
`among others.
`
`• Version or date of the job object.
`
`• Sets of default parameters or instructions. The defaults may be stored in
`
`an output device, in the information apparatus, or in any network nodes.
`
`11
`
`ROKU EXH. 1010
`
`
`
`• Pointer or reference to any one of the above mentioned information,
`
`instructions, preferences and defaults.
`
`• Pointer or reference to another object or objects.
`
`[0042]
`
`[0043]
`
`Document Object
`
`A document object may contain attributes and fields that describe a
`
`digital document and or reference or references to digital document or
`
`documents. The term digital document as used herein may refer to any
`
`digital content or data content that an output device may output. A digital
`
`document may contain text, graphics, image, sound, voice, forms, and
`
`video, among other content types. Examples of a digital document may be
`
`any one or combination of file types: HTML, VHTML, Postscript, PCL, XML,
`
`PDF, MS Word, PowerPoint, JPEG, MPEG, GIF, PNG, WML, VWML,
`
`CHTML, HDML, ASCII, 2-byte international coded characters, etc. A digital
`
`document can be composed of any format, language, encoding, data or
`
`"'
`
`combination, and the digital document may be partially or totally proprietary
`
`or otherwise. A digital document may be used interchangeably with the term
`
`output content or data content in the descriptions of present invention.
`
`[0044]
`
`A document object may contain one or more of the following attributes,
`
`fields, or descriptions. Each of the following fields may be optional, and
`
`furthermore, each of the following fields or attributes may or may not exist in
`
`a particular implementation (e.g., may be empty or NULL).
`
`• The actual digital document or output content.
`
`• A pointer or reference to a digital document or output content and or
`
`instructions of where a digital document can be found and or retrieved.
`
`A digital document may be located in a user's information apparatus, in
`
`an application, or anywhere in a network node (e.g., in a content or file
`
`server). Using a pointer or reference to a digital document may reduce
`
`the size of the document object. Therefore, this may be beneficial, for
`
`example, when passing or uploading a document object from information
`
`apparatus to server application through a narrow bandwidth
`
`communication link.
`
`12
`
`ROKU EXH. 1010
`
`
`
`• Date and version of the digital document.
`
`• A history with the dates and descriptions of any changes, modifications,
`
`and updates made to the document since its creation.
`
`• Descriptions and instructions for viewing, obtaining, opening, interpreting,
`
`encoding, decoding, compressing, decompressing, rendering,
`
`converting, describing, processing, and manipulating the digital
`
`document.
`
`• Status and state of the digital document. For example, one of the fields
`
`may provide priority or instructions of when or where to use the reference
`to digital document or the actual digital document itself if they are both
`
`contained in a document object.
`
`• Pointer or reference to another object or objects.
`
`[0045]
`
`Fig. 1 is a block diagram of a pervasive output system 98 that can
`
`implement the process and apparatus of present invention. In one
`
`implementation, electronic system 98 includes an information apparatus
`
`100, an application server 110 and a content server 114 (sometimes
`
`referred to as "network nodes") that are connected together through network
`
`108. Electronic system 98 may also include an output device 106 that
`
`communicates with information apparatus 100 through a communication link
`
`116.
`
`[0046]
`
`Network 108 generally refers to any type of wire or wireless link
`
`between multiple computing devices. Examples of network 108 may
`
`include, but are not limited to, a local area network (LAN), a wide area
`
`network (WAN), or a combination of networks. In one embodiment of the
`
`present invention, network 108 may include the Internet. In another
`
`embodiment, network 108 may contain multiple networks, including local
`
`area networks or wide area networks such as the Internet.
`
`[0047]
`
`Information apparatus 100 is a computing device with processing
`
`capability. In one embodiment, information apparatus 100 may be a mobile
`
`computing device such as palmtop computer, handheld device, laptop
`
`computer, personal digital assistant (PDA), smart phone, screen phone, e-
`
`13
`
`ROKU EXH. 1010
`
`
`
`book, Internet pad, communication pad, Internet appliance, pager, digital
`
`camera, etc. It is possible that information apparatus 100 may also include
`
`a static computing device such as a desktop computer, workstation, server,
`
`etc.
`
`[0048]
`
`Information apparatus 100 may contain components (not shown) such
`
`as a processing unit, a memory unit, a storage unit and an inpuVoutput
`
`control unit. Information apparatus 100 may also contain an interface (not
`
`shown) for interactions with users. The interface may be implemented in
`
`software or hardware or a combination. Examples of such interfaces
`
`include,.wit.hout limitation, one or more of a mouse, a keyboard, a touch(cid:173)
`
`sensitive or non-touch-sensitive screen, push buttons, soft keys, a stylus, a
`
`speaker, a microphone, etc.
`
`[0049]
`
`Information apparatus 100 typically contains at least one network
`
`communication unit that interfaces with other electronic devices such as
`
`other nodes in network 108 or output device 106. The network
`
`communication unit may be implemented with hardware (e.g., silicon
`
`chipsets, antenna), software (e.g., protocol stacks, applications) or a
`
`combination. Sometimes an information apparatus 100 may contain more
`
`than one communication unit in order to support different interfaces,
`
`protocols, and or communication standards with different devices and or
`
`network nodes. For example, information apparatus 100 illustrated in Fig. 1
`
`may communicate with output device 106 through a Bluetooth standard
`
`interface while communicating with other network nodes (e.g., content
`
`server 114 or application server 110) through a cellular telephone modem
`
`interface.
`
`[0050]
`
`Information apparatus 100 may be coupled to network 108 through
`
`wired or wireless connections, or a combination of them. As an example,
`
`information apparatus 100 may subscribe to a wireless data network in
`
`which packet data is transmitted through, for example, radio links between
`
`information apparatus 100 and a plurality of base stations. A wireless
`
`communication connection may include a cellular telephone communication
`
`14
`
`ROKU EXH. 1010
`
`
`
`channel. As another example, information apparatus 100 may be connected
`
`to network 108 through wired lines such as, without limitation, telephone
`
`lines, Ethernet, WAN links (e.g., T1, T3, 56kb, X.25) or broadband
`
`connections (e.g., ISDN, Frame Relay and ATM), among others.
`
`[0051]
`
`In one embodiment of present invention, interface 116 between
`
`information apparatus 100 and output device 106 is a wireless interface. As
`
`an example, the wireless interface may be a short-range radio interface
`
`such as those implemented according to the Bluetooth or IEEE 802.11
`
`standard. However, the interface may be realized by other means of
`
`wireless communication such as radio, infrared, ultrasonic or hydrophonic
`
`among others. The HomeRF Shared Wireless Access Protocol (SWAP) and
`
`one of many standards for cellular communication may constitute
`
`alternatives to the Bluetooth standard. Wired line connections such as serial
`
`or parallel interface, USB interface and fire wire (IEEE 1394) interface,
`
`among others, are also possible. Connection to a local network such as an
`
`Ethernet or a token Ring network, among others, may also be implemented
`
`in the present invention for local communication between information
`
`apparatus 100 and output device 106. Exemplary hardware components of
`
`communication units that may be used to implement wireless interface
`
`between the information apparatus 100 and output device 106 are described
`
`below with reference to Figs. 2A and 2B.
`
`[0052]
`
`Information apparatus 100 may be a dedicated device (e.g., email
`
`terminal, web terminal, digital camera, e-book, web pads, internet
`
`appliances etc.) with functionalities that are pre-configured by
`
`manufacturers. Alternatively, information apparatus 100 may allow users to
`
`install additional hardware components and or application software to
`
`expand its functionality.
`
`[0053]
`
`Information apparatus 100 may contain a plurality of applications to
`
`implement its feature sets and functionalities. As an example, a document
`
`browsing application 103 may be implemented to help a user view and
`
`perhaps edit, partially or entirely, digital documents written in certain format
`
`15
`
`ROKU EXH. 1010
`
`
`
`or language (e.g., Page description language, markup language, etc.).
`
`Digital documents may be stored locally in the information apparatus 100 or
`
`in a network node (e.g., in content server 114). An example of a document
`
`browsing application is an Internet browser such as Internet Explorer,
`
`Netscape Navigator, or a WAP browser. Such browsers may use one or
`
`more standard protocols (e.g., HTTP, WAP, web clipping, I-Mode, etc.) to
`
`retrieve and display digital content written in mark-up languages such as
`
`HTML, WML, XML, CHTML, HDML, among others. Other software
`
`applications may also constitute examples of the document browsing
`