Patent Grant
11416197
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.
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 (handheld 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.
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.
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, 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.
To illustrate, an information worker at an airport receiving Email in his handheld 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.
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.
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.
Installation of a device driver (e.g., printer driver) or application may be accomplished by, for example, manual installation using a CD or floppy 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-and-play driver installation, the user is still required to execute a multi-step process for each printer or output device.
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.
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-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-install all of the possible hundreds, or even thousands, of printer drivers or device drivers available to the user's information apparatus.
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 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).
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-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.
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 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.
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 invention and should in no way be construed as limiting the scope of the invention to a particular example, class, or category.
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.
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, etc., are all valid forms of object definition.
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.
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) actual digital content or (2) 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.
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.
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.
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 or attributes may or may not exist in a particular implementation (e.g., may be empty or NULL).
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.
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, authentication, 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.
Pointer or reference to any one of the above mentioned information, instructions, preferences and defaults.
Pointer or reference to another object or objects.
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.
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.
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.
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.
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-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.
Information apparatus 100 may contain components (not shown) such as a processing unit, a memory unit, a storage unit and an input/output 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, without limitation, one or more of a mouse, a keyboard, a touch-sensitive or non-touch-sensitive screen, push buttons, soft keys, a stylus, a speaker, a microphone, etc.
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
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 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, 56 kb, X.25) or broadband connections (e.g., ISDN, Frame Relay and ATM), among others.
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
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.
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 or language (e.g., Page description language, mark-up 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 application of the present invention. For example, a document editing software such as Microsoft Word™ also allows users to view and edit digital documents that have various file extensions (e.g., doc, rtf, html, XML etc.) whether stored locally in the information apparatus or in a network node.
In some instances restrictions may be imposed on the format or size of digital content that may be transmitted to information apparatus 100, such as when information apparatus 100 has limited processing power, screen size, memory space, or a limited application, or when bandwidth is a valuable resource in the transmission link to information apparatus 100 (such as in some wireless data network). As a result, there are situations where a user may not be able to view on information apparatus 100 the full content of a digital document in its original form using a document browsing application. For example, some images, tables, graphics, fonts and formats in a digital document may be “clipped” out or completely or partially altered from the original content before or during the transmission process. Such restrictions may be, sometimes, imposed by a service providing the content, or by the application rendering the content, or by the user to avoid slow transmission etc.
To address the difficulties described above, information apparatus 100 includes a pervasive output client application 102 that provides pervasive output capability of the present invention. Client application 102 may include software and data that can be executed by the processing unit of information apparatus 100. Client application 102 may be implemented as a stand-alone software application or as a part or feature of another application software, or in the form of device driver, which may be invoked, shared and used by other application software. Pervasive output client application 102 may also have means to invoke other applications (e.g., a document browsing application, a communication manager, etc.) to provide certain feature sets, as described below. Client application 102 may be variously implemented in an information apparatus 100 and may run on different operating systems or platforms. As an example, client application 102 may include one or more of the following functionalities:
Obtain output device object as a result of communication or negotiation with output device 106.
Obtain document object (1) from user input or selection, or (2) from other applications (e.g., a document browsing application) residing in the information apparatus 100.
Coordinate with a server application 112 residing in application server 110 to manage the process of communication and transmission of objects or data to and from application server 112.
Coordinate with output device 106 that include an output controller 104 to manage the process of transmitting output data (or print data in the case of printers) received from the server application 112 for output.
The client application may also optionally comprise one or more of the following functionalities:
Communicate directly or indirectly (such as through an operating system or component or object model or message, etc.) with other applications residing in the same information apparatus 100 to obtain objects, data, and or content needed, or relating to the pervasive output process of present invention.
Directly or indirectly manage and utilize functionalities provided by hardware components residing in its host information apparatus such as the communication unit, storage unit, memory unit, etc.
Provide a graphical user interface (GUI) in its host information apparatus 100 to interact with user.
Obtain job object. Job object may be obtained (1) by user input through a GUI, or (2) by using default values stored in a network node or in the output device, or (3) the combination of the above. Default values may be pre-set or may be obtained calculated or generated by the client application as result of communication or negotiation between client application 102, output device 106 and or server application 112.
Launch or provide an interface, session or emulation for server application 112.
Further process output data or print data received from server application 112 before sending the data to output device 106 for final output. The processing may include converting the output data into a form (e.g., format, language, or instruction) more acceptable to or compatible with the associated output device 106. The processing may also include at least in part one or more raster image processing operations such as rasterization, scaling, color management, color conversion, halftoning, compression, decompression, etc.
Launch, invoke, integrate or involve a helper application to assist at least in part in the processing of the output data.
The above functionalities and process of pervasive output client application 102 are described in further detail in the pervasive output process with reference to
Output device 106 is an electronic system capable of outputting digital content or data content regardless of whether the output medium is a substrate (e.g., paper), display, projection, or sound. A typical example of output device 106 may be a printer, which outputs digital documents containing text, graphics, image or any combination onto a substrate. Output device 106 may also be a display device capable of displaying still images or video, such as, without limitation, televisions, monitors, and projectors. Output device 106 can also be a device capable of outputting sound. Any device capable of playing or reading digital content in audio (e.g., music) or data (e.g., text or document) formats is also a possible output device 106. A printer (including a fax machine, copier, etc.) is frequently referred to herein as the exemplary output device 106. However, it should be recognized that the present invention applies also to output device 106 other than printers.
Outputting a data content or output content at an output device (e.g. printers, display devices, projection devices, sound output devices etc.) includes rendering the output content on a specific output medium (e.g., papers, display screens etc.). For example, rendering an output content at a printer generates image on a substrate; rendering an output content at a display device generates image on a screen; and rendering an output content at an audio output device generates sound.
A printing system includes three basic components: a raster image processor, a memory buffer, and a marking engine. The raster image processor converts digital content into a raster suitable for printing; the memory buffer holds the rasterized image ready for printing; and the marking engine transfers colorant to a substrate (e.g., paper).
Marking engine may use any of a variety of different technologies to transform a rasterized image to paper or other media or, in other words, to transfer colorant to a substrate. The different marking or printing technologies that may be used include both impact and non-impact printing. Examples of impact printing may include dot matrix, teletype, daisywheel, etc. Non-impact printing technologies may include inkjet, laser, electrostatic, thermal, dye sublimation, etc.
The marking engine and memory buffer of a printer form its printer engine, which may also include additional circuitry and components, such as firmware, software or chips or chipsets for decoding and signal conversion, etc. Input to a printer engine is usually a final rasterized print data that is generated by the raster image processor. Such input is usually device dependent and printer specific. The printer engine may take this device dependent input and generate output pages.
The Raster image processor (RIP) may be located within an output device itself (as shown by raster image processor 1002 in
When a RIP 1002 is located inside an output device 106, the RIP 1002 is usually included in a printer controller 1010 (as shown in
A variety of other page description languages, markup languages, image formats, graphic formats, and file formats may be used as input print data to a printer 1000A or output device 106. Examples of possible inputs other than PostScript and PCL may include without limitation, EMF, XML, HTML, among many others. Some printer manufacturers may also employ a combination of proprietary or non-proprietary page description languages, markup languages, file formats, graphics and image formats, color spaces, metafiles, encoding, decoding, compression or decompression etc. for the print data. The print data sent to a printer with printer controller 1010 is usually an intermediate description of a digital document that may require further interpretation, processing or conversion before the print data can be sent to a printer engine 1008 for output. A printer controller 1010 may interpret and process the input intermediate print data into a final format that can be understood by the printer engine 1008. Regardless of the type of print data, conventionally, a user may need a device-specific driver in his or her information apparatus 100 in order to output the proper language, format, or file that can be accepted by a specific printer or output device 106
Regardless of type or sophistication level, different output devices 106 conventionally need different printer drivers or output management applications in the information apparatus 100 to provide output capability. Some mobile devices may have limited memory and processing power to store or process multiple device drivers. It may also be infeasible to install or preinstall multiple device dependent or specific printer drivers in such mobile devices. In pervasive output operations of the present invention described below, various device specific drivers or applications may be available and may be executed completely or partially in a remote application server 110, thereby reducing the workload of information apparatus 100 and realizing device-independent pervasive output.
In one implementation, output device 106 includes at least a communication unit or adapter to interface with information apparatus 100, as described below in greater detail. Output device 106 may sometimes include more than one communication unit in order to support different interfaces, protocols, or communication standards with different devices. For example, output device 106 may communicate with a first information apparatus 100 through a Bluetooth interface while communicating with a second information apparatus 100 through a parallel interface, and so on. Exemplary hardware components of a wireless communication unit are described below with reference to
Output device 106 may also include an output controller 104 to help manage communication and negotiation processes with information apparatus 100. Output controller 104 may be dedicated hardware or software or combination of both for at least one output device 106. Output controller 104 may also be integrated, installed, or connected externally to one or more output devices 106. In such cases the output controller 104 may sometimes be referred to as print server or output server.
The difference between output controller 104 and printer controller 1010 should be noted. Printer controller 1010 and output controller 104 are both controllers and are both dedicated hardware and or software for at least one output device 106. Output controller 104 refers to a controller with feature sets, capabilities, and functionalities of the present invention. Printer controller 1010 may contain functions such as interpreting an input page description language, raster image processing, and queuing, among others. Output controller 104 may also contain partially or all the features of a printer controller 1010, plus the feature set, functionalities, capabilities, and processes of present invention.
In one embodiment, output controller 104 does not include a communication unit, but rather utilizes or manages a communication unit residing in the associated output device 106. In another embodiment, output controller 104 may include or provide a communication unit to output device 106. For example, an output controller 104 with a wireless communication unit may be installed internally or connected externally to a legacy printer to provide it with wireless communication capability that was previously lacking.
Other possible implementations of output controller 104 may include, for example, a conventional personal computer (PC), a workstation, and an output server or print server. In these cases, the functionalities of output controller 104 may be implemented using application software installed in a computer (e.g., PC, server, or workstation), with the computer connected with a wired or wireless connection to an output device 106. Using a PC, server, workstation, or other computer to implement the feature sets of output controller 104 with application software is just another possible embodiment of the output controller 104 and in no way departs from the spirit, scope and process of the present invention.
Regardless of its manner of implementation, the output controller 104 will usually include hardware, software, or a combination. For example, an output controller 104 may include components using one or more or combinations of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), firmware, system on a chip, and various communication chip sets. Output controller 104 may also contain embedded processors with software components or embedded application software to implement its feature sets, and functionalities.
Output controller 104 may contain an embedded operating system. With an operating system, some or all functionalities and feature sets of the output controller 104 may be provided by application software managed by the operating system. Additional application software may be installed or upgraded to newer versions in order to, for example, provide additional functionalities or bug fixes.
Output controller 104 typically includes a memory unit, or may share a memory unit with, for example, printer controller 1010. The memory unit, such as ROM, RAM, flash memory and disk drive among others, may provide persistent or volatile storage. The memory unit may store objects, codes, instructions or data (collectively referred to as software components) that implement the functionalities of the output controller 104. Part of the software components (e.g., the printer object) may be uploaded to information apparatus 100 during a data output operation.
Functionalities and components of output controller 104 for the purpose of providing pervasive output may include:
Input components and operations for receiving service requests from a plurality of information apparatuses 100.
Storage components and operations for storing partial or the entire printer or output object in a memory component.
Transmission components and operations for transmitting partial or the entire printer or output object to the information apparatus 100 requesting pervasive output service. The output controller 104 may transmit the output device object in one or multiple sessions.
Receiving components and operations for receiving output data (e.g., print data) from information apparatus 100 and sending the data to output device 106 or output engine (or printer engine) 1008.
In addition to the above functionalities, output controller 104 may further optionally include one or more of the following:
Response components and operations to respond to service request from an information apparatus 100 (e.g., in a discovery process, described below) by providing at least a partial output device object (e.g., printer object for printers).
Broadcast components and operations to broadcast or advertise the services provided by a host output device 106 to an information apparatus 100 that may request such services.
Payment components and operations for implementing payment processing and management functions by, for example, calculating and processing payments according to the services requested or rendered to a client (information apparatus 100).
Components and operations for implementing job management functionalities such as queuing and spooling among others.
User interface components and operations for providing a user interface (e.g., display screen, touch button, soft key, etc.) when it is implemented as an external box connected to an output device 106.
Security components and operations for implementing security or authentication procedures. For example, the output controller 104 may store in its memory component (or shared memory component) an access control list, which specifies what device or user may obtain service from its host (or connected) output device 106. Therefore, an authorized information apparatus 100 may gain access after confirming with the control list.
Processing components and operations to further process the output data. The processing of the output data may include converting the output data into a form (e.g., format, language, and or instruction) at least more acceptable to or compatible with the associated output device 106 or output engine or printer engine 1008. The processing may also include at least in part one or more raster image processing operations such as rasterization, scaling, color management, color conversion, halftoning, compression, decompression etc.
When output controller 104 is implemented as firmware, or an embedded application, the configuration and management of the functionalities of output controller 104 may be optionally accomplished by, for example, using controller management software in a host computer. A host computer may be a desktop personal computer (PC), workstation, or server. The host computer may be connected locally or through a network to the output device 106 or the controller 104. Communication between the host computer and the output controller 104 can be accomplished through wired or wireless communication. The management application software in the host computer can manage the settings, configurations, and feature sets of the output controller 104. Furthermore, host computer's configuration application may download and or installed application software, software components and or data to the output controller 104 for the purpose of upgrading, updating, and or modifying the features and capabilities of the output controller 104.
Output device 106 in one implementation includes or is connected to output controller 106 described above. Therefore, functionalities and feature sets provided by output controller 106 are automatically included in the functionalities of output device 106. The output device 106 may, however, implement or include other controllers and/or applications that provide at least partially the features and functionalities of the output controller 104.
Therefore, the output device 106 may include some or all of the following functionalities:
Components and operations to receive multiple service requests or queries (e.g., a service request, a data query, an object query etc.) from a plurality of information apparatus 100 and properly respond to them by returning software components, which may contain data, codes, instructions and/or objects.
Components and operations to receive, from information apparatus 100 device-specific output data containing the digital document intended for output.
Components and operations to output final output data or print data on a substrate or in another medium such as display screen.
An output device may further comprise optionally one or more of the following functionalities:
Components and operations for establishing and managing a communication link with an information apparatus 100 requesting service;
Components and operations to store and/or further process input print data or output data.
Components and operations for storing partial or the entire output device object (e.g. printer object) in a memory component.
Components and operations to advertise or broadcast services provided or available to an information apparatus 100 that may request such services.
Application server 110 is a node on network 108. An application server 110 may include computing capability, data storage capability, and mechanisms for servicing requests from a plurality of client computers (referred to as clients), including the information apparatus 100, needing computational or data storage resources. A server typically includes processing unit, memory unit, storage unit, input/output control unit, and a communication unit, among others. Application server 110 may also include an interface to interact with users. The interface may be implemented with, for example, display screen, touch-sensitive screen, keyboard, mouse, stylus, push button, microphones and speakers among others.
Application server 110 preferably includes at least an operating system for supporting a plurality of application software to implement the functionalities of the application server 110 and to provide services to its clients (e.g., information apparatus 100). To provide services to multiple clients at the same time, the application server 110 may run a multi-user operating system that enables multiple concurrent users to log on and run applications in separate, protected sessions.
Application server 110 typically includes a server application 112 that may include software and data to be executed in the processing unit of a server node. The server application 112 may include one or more of the following functionalities:
Components and operations to receive data and/or objects (with at least a output device object and a document object) from client application 102.
Components and operations to process the objects received to generate device-dependent output data acceptable to one or more output devices 106 selected by a user. The server application 112 may perform the processing function independently or in combination with other applications.
Components and operations to transmit output data back to the client application 102.
The server application 112 may optionally include one or more of the following functionalities:
Components and operations to obtain digital document (output content) from other network node if it is not included or completely included in the document object received from client application 102.
Components and operations to obtain output device parameters if they are not included or completely included in the output device object received from client application 102.
Components and operations to obtain job object or relating parameters if it is not included or completely include in the composite message received from client application 102. The server application 112 may obtain job object by querying user or by assuming default values. For example, if a user did not specify print or output range, the server application 112 may assume the default by printing or outputting all pages.
Components and operations to manage and coordinate communication with an information apparatus 100 requesting output service.
Components and operations to identify, invoke and or incorporate appropriate applications (residing in the application server 112 or in other network nodes) to help interpret and or process the digital document obtained and generate output data. The processing of the digital document may include converting the digital document into an output data related at least in part to the output device object. The processing may also include at least in part one or more raster image processing operations such as rasterization, scaling, color management, color conversion, halftoning, compression, decompression, etc.
Components and operations to interact with (e.g., store, update, verify, etc.) one or more databases that store profiles of information apparatuses 100 and/or users who have subscribed to output service provided by the server application 112.
Components and operations to implement an independent computing architecture where the execution of the server application 112 may occur entirely in the application server 110. The GUI of the application 112, keystrokes and mouse clicks are transmitted over the network 108 to and from the client such as a user's information apparatus 100.
It should be noted that, in the example shown here, server application 112 is illustrated as the only application in application server 110. But in actuality, more than one application may exist in the application server 110 and the applications may provide various services to different clients. It is also possible that the functionalities and feature sets of the server application 112 may be implemented with multiple applications residing in the same server, multiple servers (e.g., in a server farm), or network nodes or combination.
Content server 114 may represent one of a plurality of server nodes on network 108 that may store digital documents 116. The digital documents stored in content server 114 may be viewed or edited by a user using an information apparatus 100. As an example, the content server 114 may be a web server that hosts a plurality of web pages written in mark up languages such as HTML, WML, XML, HDML, CHTML, among others. A user may view web pages using an Internet browsing application such as Internet Explorer or Netscape Navigator, a WAP browser, etc. As another example, the content server 114 may be a file server that allows multiple clients to store and share digital files with appropriate security or authentication procedures. These digital files or documents may contain one or more of image, text, graphics, sound and video. The files may be saved in various file formats (e.g., MS Word, Excel, PowerPoint, PDF, Postscript, JPEG, GIF, MPEG, etc.). A user may need to have appropriate application on his/her information apparatus 100 to access, view and edit these files.
It should be noted that in
Further description of the functionalities and feature sets of different devices and applications illustrated in
RF link controller 210 implements real-time lower layer (e.g., physical layer) protocol processing that enables the hosts (e.g., information apparatus 100, output controller 104, output device 106, etc.) to communicate over a radio link. Functions performed by the link controller 210 may include, without limitation, error detection/correction, power control, data packet processing, data encryption/decryption and other data processing functions.
A variety of radio links may be utilized. A group of competing technologies operating in the 2.4 GHz unlicensed frequency band is of particular interest. This group currently includes Bluetooth, Home radio frequency (Home RF) and implementations based on IEEE 802.11 standard. Each of these technologies has a different set of protocols and they all provide solutions for wireless local area networks (LANs). Interference among these technologies could limit deployment of these protocols simultaneously. It is anticipated that new local area wireless technologies may emerge or that the existing ones may converge. Nevertheless, all theses existing and future wireless technologies may be implemented in the present invention without limitation, and therefore, in no way depart from the scope of present invention.
Among the current available wireless technologies, Bluetooth may require relatively lower power consumption. Bluetooth has its own protocol stack and is designed for short range (10 meters), point-to-multipoint voice and data transfer. It is based on a frequency-hopping version of spread spectrum. Seventy-nine hop frequencies are utilized beginning at the lowest frequency of 2402 MHz and each of the 79 hop frequencies is 1 MHz above the next lower frequency. Bluetooth-enabled devices operate in piconets, in which several devices, using the same hopping pattern or sequence, are connected in a point-to-multipoint system (piconet). There is one device (master) in each piconet that determines how the bandwidth is allocated to other devices (slaves). As many as 10 piconets of 8 devices each can operate simultaneously.
Referring to
Configuration of infrared adapters 220 may vary depending on the intended rate of data transfer.
In the configuration illustrated by
In another implementation shown by
In the third implementation shown in
The above are exemplary implementations and configurations of output controller 104. Other implementations are also possible. For example, partial functionalities of output controller 104 may be implemented in an external box or station while the remaining functionalities may reside inside an output device 106 as a separate board or integrated with a printer controller 1010. As another example, the functionalities of output controller 104 may be implemented into a plurality of external boxes or stations connected to the same output device 106. As a further example, the same output controller 104 may be connected to service a plurality of output devices 106. Variously implemented output controllers 104 should not depart from the spirit and scope of the present invention provided that they all support the functionalities and feature sets described herein.
A client application 102, in an information apparatus 100, obtaining objects; with at least one object including a document object and another object including an output device object (or printer object in the case of a printer);
A client application 102 transmitting objects to a server application 112;
A server application 112 obtaining and processing the document object and converting it into output data, reflecting at least in part a relationship to said output device object;
A server application 112 transmitting output data to the information apparatus 100 including a client application 102;
The information apparatus 100 including a client application 102 transmitting output data to an output device 106;
An output device 106 generating output with the output data.
Pervasive output process 401 may be initiated by a user in step 400. Typically, a user initiates output process 401 by invoking a client application 102 in his/her information apparatus 100. The client application 102 may be launched as an independent application or it may be launched from other applications 103 (such as from a document browsing, creating or editing application) or as part of or component of or a feature of another application 103 residing in the same information apparatus 100. When launched from another application 103, the client application 102 may obtain information, such as a partial or an entire document object, from that another application 103. This can be accomplished, for example, by one or combinations of messages or facilitated through an operating system or a particular object or component model etc. The client application may be a device driver in this example.
During output process 401, a user may need to select one or more output devices 106 for output service. An optional discovery process step 404 may be implemented to help the user select an output device 106. During the discovery process step 404, a user's information apparatus 100 may (1) search for available output devices 106; (2) provide the user with a list of available output devices 106; and (3) provide means for the user to choose one or more output devices 106 to take the output job. An exemplary discovery process 404 is described below in greater detail with reference to
The discovery process 404 may sometimes be unnecessary. For example, a user may skip the discovery process 404 if he or she already knows the output device (e.g., printer) 106 to which the output is to be directed. In this case, the user may simply connect the information apparatus 100 to that output device 106 by wired connections or directly point to that output device 106 in a close proximity such as in the case of infrared connectivity. As another example, a user may pre-select or set the output device or devices 106 that are used frequently as preferred defaults. As a result, the discovery process 404 may be partially or completely skipped if the default output device 106 or printer is found to be available.
In stage 406, the client application 102 may interact with output device 106, the user, and or other applications residing in the same information apparatus 100, to obtain (1) a document object, (2) an output device object and (3) any other optional objects such as a job object. These objects may be obtained sequentially, concurrently, or in any order. It should be noted that some of the objects or partial objects might have been acquired in prior steps. For example, the client application 102 may have obtained partially or entirely document objects or related information when the client application 102 was launched from or by another application. As another example, a partial output device object may have been uploaded to the information apparatus 100 during the optional discovery process 404. The client application 102 may create a composite message including these objects (document object, output device object and other optional objects) and transmit the composite message to server application 112 for processing, as described below in greater detail with reference to
The server application 112, after receiving such a composite message from the client application 102, may in step 408 processes the document object or objects contained in the composite message and convert it or them into output data. Additional helper applications may be needed to help in this processing task. The processing and generation of output data may reflect at least in part a relationship to the output device object and or job object contained in the composite message received from client application 102. The output data generated may be transmitted back to the information apparatus 100, requesting output service or process 401 via network 108. An exemplary implementation of a server application process is described below with reference to
In step 410, information apparatus 100 transmits output data, with or without further processing, to the selected output device 106 through a local communication link 116. Preferably, the output data is in a format or language acceptable to or compatible with the output device 106 selected by the user. When receiving output data from information apparatus 100, an output device 106 may simply buffer the output data before sending it to output engine (or printer engine) 1008 for final output. In cases where an output device 106 includes or is connected to a printer controller 1010, output controller 104 or a combined controller, such controllers may further process the output data received from information apparatus 100 before sending the output data to printer engine 1008 for final output. Further processing, if it exists, may include at least partially conversion operations and or raster image processing operations on the output data. The output controller 104 may also provide queuing or spooling or other job management features. An exemplary implementation of such an output process is described below with reference to
The steps included in pervasive output process 401 may proceed automatically when a user requests output service. Alternatively, a user may be provided with options to proceed, cancel, or input information at each and every step. For example, after the client application process step 406 is finished, the user may be asked whether or not he or she wishes to continue to communicate with a remote application server. As another example, a user may cancel the output service at any time by, for example, indicating a cancellation signal or command or by terminating the client application or by shutting down the information apparatus 100 etc.
A printer is used as a primary output device 106 in this example. It should be recognized, however, that pervasive output process 401 described above can be similarly applied to other output devices such as fax machines, digital copiers, display screens, monitors, televisions, projectors, voice output devices, among others.
The discovery process 520 may include or utilize:
A client application 102 in an information apparatus 100 communicating with available output devices 106 to obtain information such as partial or complete output device object or objects.
A client application 102 that provides to the user information on each available and or compatible output device 106.
User selection or determination by a client application 102 (automatically or not) of one or more devices 106 for output service from the available or compatible output devices 106.
Various protocols and or standards may be used during discovery process 520. Wireless communication protocols are preferred. Wired communication, on the other hand, may also be implemented. Examples of applicable protocols or standards may include, without limitation, Bluetooth, HAVi, Jini, Salutation, Service Location Protocol, and Universal Plug-and-play among others. Other proprietary protocols or combination may also be implemented in the discovery process 520. However, these different protocols, standards, or combination shall not depart from the spirit and scope of present invention.
In one implementation an application (referred here for simplicity of discussion as a “communication manager,” not shown) residing in the information apparatus 100 helps communicate with output device 106, manage service requests and discovery process 520. The communication manager may be a part of or a feature of the client application 102. Alternatively or in combination, the communication manager may also be a separate application. When the communication manager is a separate application, the client application 102 may have the ability to communicate, manage or access functionalities of the communication manager.
The discovery process 520 may be initiated manually by a user or automatically by a communication manager when the user requests an output service with information apparatus 100.
In the optional step 500, a user may specify searching or matching criteria. For example, a user may indicate to search for color printers and or printers that provide free service. The user may manually specify such criteria each time for the discovery process 520. Alternatively or in combination, a user may set default preferences that can be applied to a plurality of discovery processes 520. Sometimes, however, no searching criteria are required—the information apparatus 100 may simply search for all available output devices 106 that can provide output service.
In step 501, information apparatus 100 searches for available output devices 106. The searching process may be implemented by, for example, an information apparatus 100 multi-casting or broadcasting or advertising its service requests and waiting for available output devices 106 to respond. Alternatively or in combination, an information apparatus 100 may “listen to” service broadcasts from one or more output devices 106 and then identify the one or more output devices 106 that are needed or acceptable. It is also possible that multiple output devices 106 of the same network (e.g., LAN) register their services with a control point (not shown). A control point is a computing system (e.g., a server) that maintains records on all service devices within the same network. An information apparatus 100 may contact the control point and search or query for the needed services.
In step 502, if no available output device 106 is found, the communication manager may provide the user with alternatives 504. Such alternatives may include, for example, aborting the discovery process 520, trying discovery process 520 again, temporarily halting the discovery process 520, or being notified when available output device 106 is found. As an example, the discovery process 520 may not detect any available output device 106 in the current wired/wireless network. The specified searching criteria (if any) is then saved or registered in the communication manager. When the user enters a new network having available output devices 106, or when new compatible output devices 106 are added to the current network, or when an output device 106 becomes available for any reason, the communication manager may notify the user of such availability.
In step 506, if available output devices 106 are discovered, the communication manager may obtain some basic information, or part of or the entire output device object, from each discovered output device 106. Examples of such information may include, but not limited to, device identity, service charge, subscription, service feature, device capability, operating instructions, etc. Such information is preferably provided to the user through the user interface (e.g., display screen, speaker, etc.) of the information apparatus 100.
In step 508, the user may select one or more output devices 106 to take the output job. If the user is not satisfied with any of the available output device 106, the user may decline the service. In this case, the user may choose to try again in step 510 with some changes made to the searching criteria. Alternatively, the user may choose to terminate the service request.
In step 512, with one or more output devices 106 selected or determined, the communication link between information apparatus 100 and the selected output device or devices 106 may be “locked”. Other output devices 106 that are not selected may be dropped. The output process 520 may then proceed to a client application process 601 referenced in step 406 of
A client application 102 that obtains an output object or objects as a result of communication and or negotiation with an output device 106.
A client application 102 that obtains a document object (1) from user input or selection, or (2) from other applications (e.g., document browsing application) residing in the same information apparatus 100.
A client application 102 that coordinates with server application 112 to manage the process of communication and transmission of a composite message (including at least a printer object and a document object) to the server application 112 for further processing.
Step 600 indicates that client application 102 obtains a document object. To assemble or create a document object, the client application 102 may need to obtain output content (or a digital document) or pointers to the output content, or both. In cases where the output content is downloaded or partially downloaded to a user's information apparatus 100, the client application 102 may include both the output content and pointers to the output content in its document object. In cases where the output content is not downloaded to the information apparatus 100, the client application 102 may include only pointers to the output content in the document object.
There are various ways that a client application 102 may obtain a digital document or a pointer or reference to the digital document. In one embodiment, the client application 102 may provide a GUI with which a user can directly input the pointer or reference (e.g., URL, IP address, filename, path, etc.) of a digital document stored locally or in a network node. This manual process may be facilitated by, for example, providing a GUI with which users may select one or more pointers from a list of pointers or references of digital documents stored locally or in a remote network node. For instance, through a GUI provided by the client application 102, a user may see and select pointers of digital documents stored in a remote file server. In this case, the document object created by the client application 102 may contain only pointers or references to the output content.
In another embodiment, the client application 102 may obtain output content or pointer to output content from another application in the same information apparatus 100. As an example, a user may (1) launch the client application 102, and (2) invoke another application 103 (e.g., document editing and or browsing application) residing in the same information apparatus 100 to view or download the digital document. As another example, a user may (1) run another application 103 (e.g., document editing and or browsing application) residing in the same information apparatus 100 to view or download the digital document; and (2) launch or invoke the client application 102. In these cases, the client application 102 may communicate with another application 103 (e.g., document browsing application) to obtain pointers to the digital document and or the digital document itself (if it has been downloaded locally for viewing) to be included in document object.
It should be noted that the document object may have been partially or entirely obtained by the client application 102 in previous steps such as in step 400 of
In some instance such as in document browsing applications, a user may be limited to viewing or downloading only part of, or a reduced version of, the original digital document stored in a network node. This may be due to small screen size, limited bandwidth, memory size, and lack of application support, among other issues. In these cases, the client application 102 may allow the user to choose to output the original digital document or the reduced sized document. In the case of the original document, the document object created by the client application 102 may, for example, contain only references or pointers to the original output content stored in a server or network node. In the case where user wants to output the reduced version document that has been downloaded locally, the client application 102 may include in the document object one or more of (1) the obtained reduced output content (2) the reference to the reduced content in the server or network node, and (3) pointer or pointers to the original output content.
In another instance, for example, with a document browsing application, a user may see only the name or path to output content without being able to download or open it due to, for example, no compatible applications residing on the information apparatus 100, small display screen etc. According to the present invention, however, a user may still be able to output the original digital document by indicating to the client application 102 the pointer or reference of the output content. For example, the user may select or highlight the name or path of the output content through a GUI provided by the document browsing application. In this case, the document object created by the client application 102 may contain only pointers to the output content.
A document object may also contain instructions. Instructions in an object may provide description, operation, and status information of the content or data of the document object, etc. For example, instructions may provide information about the changes or differences between an output content included in a document object relative to the original output content (stored in a network node) that is pointed to by the reference field in the document object. The output content included in a document object may be an edited or altered version while the output content referred to by the pointers may be the original version.
It should be noted that some output content may be publicly available to all users (e.g., generic web pages) while other output content may be restricted to one or a group of users (e.g., secure documents stored in a corporate network). In the latter case, authentication information such as a password, user name, id number, biometric information, digital certificate or security key, among others, may need to be provided to the server application 112 for accessing and or fetching the digital document with reference to a pointer or reference. In one example, such authentication information may be included in document object, printer object, or job object. In another example, server application 112 may prompt the user to enter authentication information through a GUI in information apparatus 100 when necessary.
Step 602 indicates whether an output device object is obtained. In the case where an output device object is not obtained, then in step 604, with one or more output devices 106 selected, the client application 102 may communicate with the selected output device or devices 106 to upload output device objects or related information stored in memory or storage components of the output device or devices 106. It should be noted that a partial or entire output device object or related information might have been already obtained by the client application 102 during the prior optional discovery process (520 and step 402 in
To successfully obtain the output device object or objects from the selected output device or devices 106, several additional optional processes may be involved. As an example, authentication may be necessary when the selected output device 106 provides service to a restricted group of users. A simple authentication may be implemented by, for example, comparing the identity for the information apparatus 100 with an approved control list of identities or elements stored in the output device 106. Other more complex authentication and encryption schemes may also be used. Information such as user name, password, ID number, signatures, security keys (physical or digital), biometrics, fingerprints, voice, among others, may be used separately or in combination as authentication means. Such identification and or authentication information may be manually provided by the user or automatically detected by the selected output device or devices 106. With successful authentication, a user may gain access to all or part of the services provided by an output device 106. The output device object that the client application 102 obtains may vary according to the type or quality of service requested or determined. If authentication fails, it is possible that a user may be refused partially or completely all access to the service. In this case, the user may be provided with alternatives such as selecting another output device 106 or alternative services.
Another optional process is that a user may be asked to provide payment or deposit or escrow before, during or after output service. Examples of payment or deposit may include cash, credit card, bankcard, charge card, smart card, electronic cash, among others. The output controller 104 may provide payment calculation or transaction processing as optional feature sets.
It should be noted that a plurality of information apparatuses 100 may request to obtain output device object or objects from the same output device 106 at the same time or at least during overlapping periods. The output device 106 may have components or systems to manage multiple communication links and provide the output device object or objects concurrently or in an alternating manner to multiple information apparatuses 100. Alternatively, an output device 106 may provide components or systems to queue the requests from different information apparatuses 100 and serve them in a sequential fashion according to a scheme such as first come first serve, quality of service, etc. Multi-user communication and service management capability with or without queuing or spooling functions may be implemented by, for example, the output controller 104 as optional feature sets.
Step 606 indicates that the client application 102 may optionally obtain a job object. A job object may include a user's preferences and parameters relating to the output job or process. The client application 102 may obtain a job object by, for example, capturing a user's output preferences through a GUI. In one instance, the client application 102 may provide a universal GUI to a user regardless of what output device 106 is selected. Through such an interface, the user may specify some device-independent parameters such as page range, number of cards per page, number of copies, etc. Alternatively or in combination, the client application 102 may incorporate device-dependent features and preferences into the GUI provided to user. The device dependent portion of the GUI may be supported partially or entirely by some information contained in or provided by the output device object obtained from the selected output device 106. Examples of such device dependent features may include quality of service, service fee, print quality, color or grayscale, duplex or single sided, output page size, among others.
It is possible that some or all components, attributes or fields of a job object have default values. The client application 102 may have certain defaults such as those hard-coded in software or hardware or pre-configured by the user or a manufacturer. In addition, the client application 102 may access a file to obtain default values or by other means such as communicating with the output device 106, the server application 112 or other applications in the information apparatus 100 or in a network node. The client application 102 may also create or calculate certain default values based on the information it has or obtained during the output process. These default values may be related, at least in part, to the output device object and or the server application 112 involved in the output process. In some instances, a user may or may not have an opportunity to change or overwrite some or all defaults. The client application 102 may obtain and use some or all defaults with or without user intervention or knowledge.
In step 608, the client application 102 may create or assemble a composite message. A composite message may be any type of data transferred across network 108 that may include one or more transmissions. A composite message typically includes partially or entirely the objects (with some default values) obtained by the client application 102 in previous steps.
In step 610, the client application 102 transmits the composite message to server application 112. The client application 102 may communicate with the server application 112 using one or more or a combination of standard network protocols such as WAP, Web Clipping, I-Mode, TCP/IP, SPX/IPX, PPP, NetBEUI, Apple Talk, among others. Proprietary network protocols or a combination that includes them may also be used. The communication link between information apparatus 100 and application server 112 may be implemented with one or a combination of standard network connections and communication links such as telephone lines, LAN or WAN links (T1, T3, 56 kb, X.25, etc.), broadband connections (ISDN, Frame Relay, ATM etc.), wireless connection (radio link, inferred, microwave, etc.) as well as the Internet or corporate Intranets.
In addition to the composite message, the client application 102 and server application 112 may also exchange various types of messages back and forth to, for example, request service, confirm service availability, configure protocol stack, or confirm or acknowledge receipt of the previous message, among other messages. The server application 112 may also prompt the client application 102 to send or resend some components or objects of the composite message if such components or objects are incomplete, missing or corrupted. The server application 112, however, may also try to fill in default values (if available) for some or all of the information missing in the composite message. Encode/decode, compression/decompression and/or encryption techniques may be used to facilitate the transmission of the composite message.
There is a possibility that the application server 112 only provides services to users who have subscribed to such services. In this case, a user may be prompted to log in or sign up when he or she requests service from the server application 112.
The server application 112 may receive composite messages or service requests from a plurality of client applications 102 at the same time or at least during overlapping periods. It is therefore, beneficial that the server application 112 runs on a multi-user operating system that enables multiple concurrent users to run applications in separate, protected sessions.
It should be recognized that
A server application 112 that receives a composite message (including an output device object and a document object) from client application 102.
A server application 112 that processes the objects received to generate device-dependent output data acceptable to one or more output devices 106 selected by a user. The server application 112 may perform the processing function independently or in combination with other applications.
A server application 112 that transmits output data back to the information apparatus 100 requesting output service or services.
In step 700, server application 112 receives a composite message from client application 102. As mentioned earlier, the composite message may include one or more of a document object, an output device object and an optional job object.
After receiving the composite message from client application 102, the server application 112 may process the document object and convert it into output data. The output data generated is preferred to be in a format or language acceptable or compatible to the output device or devices 106 selected by the user.
In some cases, the document object or output device object in a composite message may include only references, pointers and or instructions. Such a configuration may, for example, reduce the size of the composite message and therefore make it easier to transmit through a network. In another case, the document object or output device object in a composite message may include missing or incomplete information. Digital document (e.g., output content) or output device parameters may not be available or completely available in the document object or the output device object, respectively. In these cases, as shown in step 704, the server application 112 may need to find or fetch partially or entirely the output content or device parameters from network nodes or otherwise obtain the content or parameters according to the pointers, references or instructions provided by the objects. For example, an output device object received in a composite message may contain insufficient output device parameters—only the brand name and model number of a selected output device 106 may be provided. In this case, the server application 112 may either find or fetch the missing output device parameters according to pointers or references provided in the output device object, or the server application 112 may consult a translation service or application in order to obtain the complete output device parameters based on the partial or limited device information that is available. If no further information or data can be found or obtained, predefined defaults may be used to fill in missing information about the output device 106 or alternatively a warning or an error message may be provided to the user for either continuation or cancellation of the process.
Step 704 (obtaining output content and or device parameters) may be entirely or partially skipped if the output content and output device parameters are already included in the document object and output device object, respectively.
In order to process a digital document into device dependent output data, step 706 shows that the server application 112 may need to involve one or more helper applications. A helper application is any application in the server 110 or other network node that participates, helps or assists in the output process of the present invention. Examples of helper applications may include, software components, software applications, device drivers, printer drivers, etc. The helper application or applications may perform one or more of the following tasks among others:
Open, parse, or interpret a particular digital document format or language.
Convert a digital document into an intermediate format, language or data.
Process an input digital document into a raster format including, as an example, one or more raster image processing operations such rasterization, scaling, color correction, color matching, segmentation, halftoning, compression, decompression etc.
Convert or encode rasterized data into a device specific output data.
The helper applications may participate in the output process in various ways. As an example, a server application 112 may involve one or more helper applications to decode, parse, interpret, and or process a digital document into an intermediate file, format, language or data. And then the server application 112 may involve one or more helper applications to further convert the intermediate result into output data. In another example, the server application 112 may involve two or more groups of helper applications. The first group of helper applications may decode, interpret, and process a digital document into intermediate file, format, language or data. The second group of helper applications may convert the intermediate results into output data. A group may consist of one or more applications.
The server application 112 may identify, locate, invoke, launch, and or integrate the appropriate helper applications or its components based on the information (e.g., output device parameters) provided in an output device object. A translation service (e.g., database application, directory service) may provide information to the server application 112 as to where to find, obtain, or use the helper applications. The helper applications may reside locally in the application server 110 or remotely in another network node. If a helper application is located in another network node, the server application 112 may acquire or download the helper application to the application server 110. Alternatively, the server application 112, considering application availability or load balancing, may direct the digital document to be processed in another server node where the helper application or applications are run.
In some cases, however, the server application 112 may have the ability to process and generate the correct output data without involving additional helper applications and step 706 may be skipped. As an example, the server application 112 may already contain software components and feature sets capable of supporting and generating, different print data or output data formats or language such as PostScript or PCL or XML etc. Therefore, if the output device object indicates that the output device 106 is a PostScript printer or any other that it supports, the server application 112 may not need to invoke, or download or incorporate a helper application or a helper application component such as a PostScript driver. The server application 112 may just proceed and convert the digital document into a PostScript file as print data. PostScript is used here as an example, other formats, languages, data used for other types of print data or output data follows the same fashion.
When fetching output content or device parameters or software components or drivers from other network nodes, the server application 112 may need authentication information in order to gain access. Such authentication information may be already stored in the server application 112 (e.g., in a user profile), in the received objects (e.g., job object, output device object or document object), or the user may input authentication information as needed.
While processing digital content in step 708, the server application 112 may also distribute or send a presentation or GUI to a client device (e.g., information apparatus 100) to inform the user of the processing status (shown in step 709). The presentation or GUI in the client device may also capture user's preferences and inputs such as login information, security information among other preferences or inputs. This client/server implementation described here may provide an efficient computing environment. For example, logic for the server application 112 may run in the application server 110 and its distributed user interface may run in the client device (e.g., information apparatus 100). Therefore, only data relating to keystrokes, mouse clicks and screen updates may, as an example, travels through the network. This client/server implementation may reduce bandwidth requirements. Such a GUI may be implemented by, for example, instructing the client application 102 to launch on the display screen of the client information apparatus 100 a plurality of windows emulating the user interface of the server application 112. The presentation of the server application interface may be displayed efficiently through these windows in the client application 102.
If the server application 112 receives no job object or an incomplete job object in a composite message, the server application 112 may assume default values for the job object or optionally, as shown in step 709, it may also launch a GUI in the information apparatus 100 as described above to obtain partially or entirely the job object fields (job preference) from the user. Information provided in the job object may be used in the process of generating output data (step 708).
It is noted that the output data (or print data in the case of a printer) generated by the server application 112 may or may not be the final output data or the final print data that can feed directly into an output engine or a printer engine 1008. The output data sent to output device 106 through information apparatus 100 may in some cases need further processing by an application in the information apparatus 100 or by the output controller 104 or printer controller 1010 or combination before finally being sent to output engine or printer engine 1008. All these different combinations of processes and tasks or load distributions are possible implementations that shall fall within the scope and spirit of the present invention.
In step 710, the server application 112 transmits output data to the information apparatus 100 through network 108. Encryption techniques may be applied to the output data to ensure security. Compression/decompression, encode/decode may also be implemented to facilitate the transmission of output data over network 108.
A server application 112 transmits output data to information apparatus 100.
An information apparatus 100 transmits output data, with or without further processing, to the output device 106 selected by the user.
An output device 106 generates final output based on the input output data with or without further processing.
After receiving output data from server application 112, the information apparatus 100 may then transmit the output data to the output device 106 selected by the user in step 806. In some cases, the client application 102 may further process the output data (as shown in step 804). This further processing in the information apparatus 100 may include one or more operations such as encoding, decoding, compression, decompression, rasterization, scaling, color correction, halftoning, watermarking, adding templates, name, time stamps, etc., as shown in step 804, before sending the output data to the output device 106 through communication link 116 in step 806. The client application 102 may involve other applications 103 for part or all of the processing in step 804.
During the time when server application 112 processes a composite message, the communication link 116 between information apparatus 100 and output device 106 selected by the user may be constantly maintained or it may be temporarily dropped and then resumed for transmitting output data. Encryption techniques may be applied to the output data to ensure security. Compression/decompression, encode/decode may also be implemented to facilitate the transmission of output data over communication link 116.
After receiving output data from information apparatus 100, an output device 106 may simply buffer the output data, as shown in step 810, before sending the data to output engine (or printer engine in the case of a printer) 1008 for final output. In cases where an output device 106 includes a printer controller 1010, output controller 104 or combined controller, such controller may, jointly or individually, further process the output data (shown in step 814) before sending the data to output engine or printer engine 1008 for final output.
It is possible that a plurality of information apparatuses 100 may transmit output data to an output device 106 at the same time or at least during overlapping periods. It may then become necessary to implement queuing or spooling functionality in the output device 106. Preferably, the output device 106 stores output data it receives in a queue until the output data can be processed. Such queuing and spooling capability may be implemented partially or entirely by the output controller 104 as an optional feature set. A user may be notified when the output device 106 is ready to process a particular output job or the status of the output job in the queue. Once the output device 106 completes the output service, the user may terminate the output process by indicating such an intention through an interface on information apparatus 100 or by moving the information apparatus 100 out of the communication range of the output device 106.
Referring to
As shown in
When the user selects Print function control 902, the client application 102 may be invoked or launched. The output process 401 described with reference to
Since the user does not have a pre-selected or default output device 106, a discovery process 520 may automatically proceed in this example. A communication manager may coordinate the discovery process 520. As described earlier, the communication manager may be part of the client application 102 or may be a separate application that can communicate with the client application 102.
Assuming in this example that he or she did not specify any searching criteria for the discovery process 520, the user may be presented with all the printers 106, if any, that are available to take the print job. In the case where no available printers are found (not shown here), the user may also be notified and provided with alternatives as described earlier in the discovery process 520.
Assume in this example that three printers 106 are found. Their identities and service charges are listed on the GUI illustrated in
Assume in this example that the user has selected the PH inkjet 260 printer. The next GUI, as illustrated in
After the user confirms all the information and provides payment or deposit as requested, the user may be prompted to describe the job object as illustrated in
After the user submits the job object, the client application 102 sends a composite message 430 to an application server 110. The composite message 430 may include a document object, a printer object, and a job object. The application server 110 may contain server application 112. In this example, the server application 112 may need to fetch the output content (in its original format) based on the pointers provided in the document object. The server application 112 may obtain or invoke helper applications to process the output content (e.g., the news article) into print data that can be accepted by the printer 106 selected by the user (e.g., PH Inkjet 260). The server application 112 and or the helper application may perform one or more raster image processing operations on the output content. During this server application process 701, the sever application 112 may optionally launch a GUI in a window 912 as shown in
After it has finished processing the output content and has generated the necessary print data, the server application 112 transmits the print data to the selected output device 106 through the user's information apparatus 100. Transmission may be wired or wireless. The client application 102 in the information apparatus 100 may or may not further process the print data before passing it to the output device 106. The output device 106, after receiving the print data, may queue the print job in its memory or storage component until it is ready to process this particular print job. As shown in
Having described and illustrated the principles of our invention with reference to an illustrated embodiment, it will be recognized that the illustrated embodiment can be modified in arrangement and detail without departing from such principles. In view of the many possible embodiments to which the principles of our invention may be applied, it should be recognized that the detailed embodiments are illustrative only and should not be taken as limiting the scope of our invention. Rather, I claim as my invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.
This application is a continuation of U.S. patent application Ser. No. 16/215,506 filed Dec. 10, 2018, which is a continuation of U.S. patent application Ser. No. 15/785,190 filed Oct. 16, 2017 and issued as U.S. Pat. No. 10,152,285, which is a continuation of U.S. patent application Ser. No. 09/992,413 filed Nov. 18, 2001 and issued as U.S. Pat. No. 9,965,233, which claims benefit of U.S. Provisional Patent Application Ser. No. 60/252,682 filed Nov. 20, 2000. The complete disclosures of the above patent applications are hereby incorporated by reference for all purposes. Additionally, this application is a continuation-in-part of U.S. patent application Ser. No. 16/200,380 filed Nov. 26, 2018, which is a continuation of U.S. patent application Ser. No. 15/332,432 filed Oct. 24, 2016 and issued as U.S. Pat. No. 10,140,071, which is a continuation of U.S. patent application Ser. No. 10/053,765 filed Jan. 18, 2002, and issued as U.S. Pat. No. 9,836,257, which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/262,764 filed Jan. 19, 2001. The complete disclosures of the above patent applications are hereby incorporated by reference for all purposes. Moreover, this application is a continuation-in-part of U.S. patent application Ser. No. 16/416,088 filed May 17, 2019, which is a continuation of U.S. patent application Ser. No. 16/229,896 filed Dec. 21, 2018 and issued as U.S. Pat. No. 10,642,576, which is a continuation of U.S. patent application Ser. No. 15/201,194 filed Jul. 1, 2016 and issued as U.S. Pat. No. 10,162,596, which is a continuation of U.S. patent application Ser. No. 13/710,295 filed Dec. 10, 2012 and issued as U.S. Pat. No. 9,383,956, which is a continuation of U.S. patent application Ser. No. 12/903,048 filed Oct. 12, 2010 and issued as U.S. Pat. No. 8,332,521, which is a continuation of U.S. patent application Ser. No. 10/016,223 filed Nov. 1, 2001 and issued as U.S. Pat. No. 7,941,541, and which claims benefit of U.S. Provisional Patent Application Ser. No. 60/245,101 filed Nov. 1, 2000. The complete disclosures of the above applications are hereby incorporated by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3629493 | Morgenfruh | Dec 1971 | A |
| 3833297 | Swartz | Sep 1974 | A |
| 3848856 | Reeber et al. | Nov 1974 | A |
| 4262301 | Erlichman | Apr 1981 | A |
| 4266863 | Hollingsworth et al. | May 1981 | A |
| 4291956 | Vogelgesang | Sep 1981 | A |
| 4291957 | Hollingsworth | Sep 1981 | A |
| 4301599 | Leay | Nov 1981 | A |
| 4335955 | Lopata | Jun 1982 | A |
| 4340905 | Balding | Jul 1982 | A |
| 4360264 | Baker et al. | Nov 1982 | A |
| 4417792 | Martin | Nov 1983 | A |
| 4428001 | Yamamura et al. | Jan 1984 | A |
| 4431282 | Martin | Feb 1984 | A |
| 4435059 | Gerber | Mar 1984 | A |
| 4495490 | Hopper et al. | Jan 1985 | A |
| 4539585 | Spackova et al. | Sep 1985 | A |
| 4541010 | Alston | Sep 1985 | A |
| 4553835 | Morgan, Jr. | Nov 1985 | A |
| 4580880 | Watson | Apr 1986 | A |
| 4602280 | Maloomian | Jul 1986 | A |
| 4603330 | Horne et al. | Jul 1986 | A |
| 4758881 | Laspada | Jul 1988 | A |
| 4956665 | Niles | Sep 1990 | A |
| 4958220 | Alessi et al. | Sep 1990 | A |
| 4979032 | Alessi et al. | Dec 1990 | A |
| 5048057 | Saleh et al. | Sep 1991 | A |
| 5129639 | DeHority | Jul 1992 | A |
| 5166809 | Surbrook | Nov 1992 | A |
| 5220674 | Morgan et al. | Jun 1993 | A |
| 5228118 | Sasaki | Jul 1993 | A |
| 5257097 | Pineau et al. | Oct 1993 | A |
| 5270773 | Sklut et al. | Dec 1993 | A |
| 5287194 | Lobiondo | Feb 1994 | A |
| 5303342 | Edge | Apr 1994 | A |
| 5319711 | Servi | Jun 1994 | A |
| 5337258 | Dennis | Aug 1994 | A |
| 5353388 | Motoyama | Oct 1994 | A |
| 5404433 | Hosogai | Apr 1995 | A |
| 5412798 | Gamey | May 1995 | A |
| 5463623 | Grimes et al. | Oct 1995 | A |
| 5467434 | Hower, Jr. et al. | Nov 1995 | A |
| 5475507 | Suzuki et al. | Dec 1995 | A |
| 5479206 | Ueno et al. | Dec 1995 | A |
| 5485634 | Weiser et al. | Jan 1996 | A |
| 5487069 | O'Sullivan et al. | Jan 1996 | A |
| 5490287 | Itoh | Feb 1996 | A |
| 5506661 | Hanzawa | Apr 1996 | A |
| 5515480 | Frazier | May 1996 | A |
| 5519641 | Beers et al. | May 1996 | A |
| 5524185 | Na | Jun 1996 | A |
| 5537107 | Funado | Jul 1996 | A |
| 5537517 | Wakabayashi et al. | Jul 1996 | A |
| 5546079 | Wagner | Aug 1996 | A |
| 5564109 | Snyder et al. | Oct 1996 | A |
| 5566278 | Patel et al. | Oct 1996 | A |
| 5568595 | Yosefi et al. | Oct 1996 | A |
| 5572632 | Laumeyer et al. | Nov 1996 | A |
| 5574979 | West | Nov 1996 | A |
| 5579087 | Salgado | Nov 1996 | A |
| 5580177 | Gase et al. | Dec 1996 | A |
| 5589889 | Kawaoka | Dec 1996 | A |
| 5596697 | Foster et al. | Jan 1997 | A |
| 5604843 | Shaw et al. | Feb 1997 | A |
| 5613123 | Tsang et al. | Mar 1997 | A |
| 5613124 | Atkinson et al. | Mar 1997 | A |
| 5613191 | Hylton et al. | Mar 1997 | A |
| 5619250 | McClellan et al. | Apr 1997 | A |
| 5619257 | Reele et al. | Apr 1997 | A |
| 5619649 | Kovnat et al. | Apr 1997 | A |
| 5625757 | Kageyama et al. | Apr 1997 | A |
| 5629981 | Nerlikar | May 1997 | A |
| 5636211 | Newlin | Jun 1997 | A |
| 5644662 | Vuylsteke | Jul 1997 | A |
| 5664243 | Okada et al. | Sep 1997 | A |
| 5675717 | Yamamoto | Oct 1997 | A |
| 5687332 | Kurahashi et al. | Nov 1997 | A |
| 5699495 | Snipp | Dec 1997 | A |
| 5708780 | Levergood et al. | Jan 1998 | A |
| 5710557 | Schuette | Jan 1998 | A |
| 5717688 | Belanger et al. | Feb 1998 | A |
| 5717742 | Hyde-Thomson | Feb 1998 | A |
| 5724106 | Autry | Mar 1998 | A |
| 5727135 | Webb et al. | Mar 1998 | A |
| 5737501 | Tsunekawa | Apr 1998 | A |
| 5739928 | Scott | Apr 1998 | A |
| 5748859 | Takayanagi et al. | May 1998 | A |
| 5754655 | Hughes et al. | May 1998 | A |
| 5757952 | Buytaert et al. | May 1998 | A |
| 5761480 | Fukada et al. | Jun 1998 | A |
| 5771353 | Eggleston et al. | Jun 1998 | A |
| 5793966 | Amstein et al. | Aug 1998 | A |
| 5796394 | Wicks et al. | Aug 1998 | A |
| 5796442 | Gove et al. | Aug 1998 | A |
| 5796727 | Harrison et al. | Aug 1998 | A |
| 5799067 | Kikinis et al. | Aug 1998 | A |
| 5799068 | Kikinis et al. | Aug 1998 | A |
| 5802314 | Tullis et al. | Sep 1998 | A |
| 5815194 | Ueda | Sep 1998 | A |
| 5822230 | Kikinis et al. | Oct 1998 | A |
| 5826244 | Huberman | Oct 1998 | A |
| 5831664 | Wharton et al. | Nov 1998 | A |
| 5832191 | Thorne | Nov 1998 | A |
| 5838320 | Matthews, III et al. | Nov 1998 | A |
| 5838926 | Yamagishi | Nov 1998 | A |
| 5845078 | Tezuka et al. | Dec 1998 | A |
| 5850449 | McManis | Dec 1998 | A |
| 5852721 | Dillon et al. | Dec 1998 | A |
| 5859970 | Pleso | Jan 1999 | A |
| 5862321 | Lamming et al. | Jan 1999 | A |
| 5862404 | Onaga | Jan 1999 | A |
| 5867633 | Taylor, III et al. | Feb 1999 | A |
| 5870723 | Pare, Jr. et al. | Feb 1999 | A |
| 5880858 | Jin | Mar 1999 | A |
| 5881213 | Shaw et al. | Mar 1999 | A |
| 5884140 | Ishizaki et al. | Mar 1999 | A |
| 5897260 | Zingher | Apr 1999 | A |
| 5903832 | Seppanen et al. | May 1999 | A |
| 5907831 | Lotvin et al. | May 1999 | A |
| 5911044 | Lo et al. | Jun 1999 | A |
| 5916309 | Brown et al. | Jun 1999 | A |
| 5917542 | Moghadam et al. | Jun 1999 | A |
| 5926104 | Robinson | Jul 1999 | A |
| 5930466 | Rademacher | Jul 1999 | A |
| 5931919 | Thomas et al. | Aug 1999 | A |
| 5933498 | Schneck et al. | Aug 1999 | A |
| 5937112 | Herregods et al. | Aug 1999 | A |
| 5940843 | Zucknovich et al. | Aug 1999 | A |
| 5946031 | Douglas | Aug 1999 | A |
| 5946110 | Hu et al. | Aug 1999 | A |
| 5946458 | Austin et al. | Aug 1999 | A |
| 5949966 | Hayashi | Sep 1999 | A |
| 5949978 | Kondo et al. | Sep 1999 | A |
| 5953546 | Okada et al. | Sep 1999 | A |
| 5960162 | Yamamoto | Sep 1999 | A |
| 5968176 | Nessett et al. | Oct 1999 | A |
| 5970473 | Gerszberg et al. | Oct 1999 | A |
| 5974234 | Levine et al. | Oct 1999 | A |
| 5974312 | Hayes, Jr. et al. | Oct 1999 | A |
| 5974401 | Enomoto et al. | Oct 1999 | A |
| 5978560 | Tan et al. | Nov 1999 | A |
| 5983200 | Slotznick | Nov 1999 | A |
| 5987454 | Hobbs | Nov 1999 | A |
| 5993047 | Novogrod | Nov 1999 | A |
| 6003065 | Yan et al. | Dec 1999 | A |
| 6006265 | Rangan et al. | Dec 1999 | A |
| 6008777 | Yiu | Dec 1999 | A |
| 6009464 | Hamilton et al. | Dec 1999 | A |
| 6020973 | Levine et al. | Feb 2000 | A |
| 6023715 | Burkes et al. | Feb 2000 | A |
| 6034621 | Kaufman | Mar 2000 | A |
| 6035214 | Henderson | Mar 2000 | A |
| 6037981 | Wilson et al. | Mar 2000 | A |
| 6039426 | Dobbs | Mar 2000 | A |
| 6041346 | Chen et al. | Mar 2000 | A |
| 6043898 | Jacobs | Mar 2000 | A |
| 6046820 | Konishi | Apr 2000 | A |
| 6061142 | Shim | May 2000 | A |
| 6061452 | Suzuki | May 2000 | A |
| 6069707 | Pekelman | May 2000 | A |
| 6070185 | Anupam et al. | May 2000 | A |
| 6072595 | Yoshiura et al. | Jun 2000 | A |
| 6076076 | Gottfreid | Jun 2000 | A |
| 6076109 | Kikinis | Jun 2000 | A |
| 6078906 | Huberman | Jun 2000 | A |
| 6084968 | Kennedy et al. | Jul 2000 | A |
| 6087060 | Chase et al. | Jul 2000 | A |
| 6088337 | Eastmond et al. | Jul 2000 | A |
| 6088450 | Davis et al. | Jul 2000 | A |
| 6088702 | Plantz et al. | Jul 2000 | A |
| 6091956 | Hollenberg | Jul 2000 | A |
| 6101291 | Arney et al. | Aug 2000 | A |
| 6115137 | Ozawa et al. | Sep 2000 | A |
| 6122526 | Parulski et al. | Sep 2000 | A |
| 6138178 | Watanabe | Oct 2000 | A |
| 6141659 | Barker et al. | Oct 2000 | A |
| 6144950 | Davies et al. | Nov 2000 | A |
| 6144997 | Lamming et al. | Nov 2000 | A |
| 6145031 | Mastie et al. | Nov 2000 | A |
| 6148081 | Szymanski et al. | Nov 2000 | A |
| 6148346 | Hanson | Nov 2000 | A |
| 6157809 | Kambayashi | Dec 2000 | A |
| 6167514 | Matsui et al. | Dec 2000 | A |
| 6169789 | Rao et al. | Jan 2001 | B1 |
| 6173407 | Yoon et al. | Jan 2001 | B1 |
| 6175922 | Wang | Jan 2001 | B1 |
| 6177926 | Kunert | Jan 2001 | B1 |
| 6184996 | Gase | Feb 2001 | B1 |
| 6189148 | Clark | Feb 2001 | B1 |
| 6189993 | Mantell | Feb 2001 | B1 |
| 6192407 | Smith et al. | Feb 2001 | B1 |
| 6195564 | Rydbeck et al. | Feb 2001 | B1 |
| 6199099 | Gershman et al. | Mar 2001 | B1 |
| 6199106 | Shaw et al. | Mar 2001 | B1 |
| 6201611 | Carter et al. | Mar 2001 | B1 |
| 6205495 | Gilbert et al. | Mar 2001 | B1 |
| 6211858 | Moon et al. | Apr 2001 | B1 |
| 6215483 | Zigmond | Apr 2001 | B1 |
| 6215494 | Teo | Apr 2001 | B1 |
| 6223029 | Stenman et al. | Apr 2001 | B1 |
| 6223059 | Haestrup | Apr 2001 | B1 |
| 6225993 | Lindblad et al. | May 2001 | B1 |
| 6226098 | Kulakowski | May 2001 | B1 |
| 6233611 | Ludtke et al. | May 2001 | B1 |
| 6236971 | Stefik et al. | May 2001 | B1 |
| 6246486 | Takahashi | Jun 2001 | B1 |
| 6252964 | Wasilewski et al. | Jun 2001 | B1 |
| 6255961 | Van Ryzin et al. | Jul 2001 | B1 |
| 6256666 | Singhal | Jul 2001 | B1 |
| 6263503 | Margulis | Jul 2001 | B1 |
| 6285357 | Kushiro | Sep 2001 | B1 |
| 6285889 | Nykänen et al. | Sep 2001 | B1 |
| 6288790 | Yellepeddy et al. | Sep 2001 | B1 |
| 6292283 | Grandbois | Sep 2001 | B1 |
| 6312106 | Walker | Nov 2001 | B1 |
| 6324521 | Shiota et al. | Nov 2001 | B1 |
| 6330611 | Itoh et al. | Dec 2001 | B1 |
| 6332193 | Glass et al. | Dec 2001 | B1 |
| 6339706 | Tillgren et al. | Jan 2002 | B1 |
| 6360252 | Rudy et al. | Mar 2002 | B1 |
| 6363149 | Candelore | Mar 2002 | B1 |
| 6363452 | Lach | Mar 2002 | B1 |
| 6366682 | Hoffman et al. | Apr 2002 | B1 |
| 6366912 | Wallent et al. | Apr 2002 | B1 |
| 6366965 | Binford et al. | Apr 2002 | B1 |
| 6369909 | Shima | Apr 2002 | B1 |
| 6379058 | Petteruti et al. | Apr 2002 | B1 |
| 6385305 | Gerzberg et al. | May 2002 | B1 |
| 6389010 | Kubler et al. | May 2002 | B1 |
| 6393271 | Dougherty | May 2002 | B1 |
| 6396531 | Gerszberg et al. | May 2002 | B1 |
| 6396598 | Kashiwagi et al. | May 2002 | B1 |
| 6418439 | Papiemiak et al. | Jul 2002 | B1 |
| 6421716 | Eldridge et al. | Jul 2002 | B1 |
| 6421748 | Lin et al. | Jul 2002 | B1 |
| 6426798 | Yeung | Jul 2002 | B1 |
| 6430599 | Baker et al. | Aug 2002 | B1 |
| 6430601 | Eldridge et al. | Aug 2002 | B1 |
| 6434535 | Kupka et al. | Aug 2002 | B1 |
| 6437786 | Yasukawa | Aug 2002 | B1 |
| 6442375 | Parmentier | Aug 2002 | B1 |
| 6449052 | Sherer et al. | Sep 2002 | B1 |
| 6452692 | Yacoub | Sep 2002 | B1 |
| 6453127 | Wood et al. | Sep 2002 | B2 |
| 6467688 | Goldman et al. | Oct 2002 | B1 |
| 6470189 | Hill et al. | Oct 2002 | B1 |
| 6473070 | Mishra | Oct 2002 | B2 |
| 6473800 | Jerger et al. | Oct 2002 | B1 |
| 6477575 | Koeppel et al. | Nov 2002 | B1 |
| 6480292 | Sugiyama | Nov 2002 | B1 |
| 6483906 | Iggulden et al. | Nov 2002 | B1 |
| 6487587 | Dubey | Nov 2002 | B1 |
| 6487599 | Smith et al. | Nov 2002 | B1 |
| 6489934 | Klausner | Dec 2002 | B1 |
| 6493104 | Cromer et al. | Dec 2002 | B1 |
| 6493550 | Raith | Dec 2002 | B1 |
| 6496802 | van Zoest et al. | Dec 2002 | B1 |
| 6496855 | Hunt et al. | Dec 2002 | B1 |
| 6510235 | Shin et al. | Jan 2003 | B1 |
| 6510515 | Raith | Jan 2003 | B1 |
| 6515988 | Eldridge et al. | Feb 2003 | B1 |
| 6519049 | Nagasaka | Feb 2003 | B1 |
| 6526129 | Beaton et al. | Feb 2003 | B1 |
| 6529522 | Ito et al. | Mar 2003 | B1 |
| 6532368 | Hild et al. | Mar 2003 | B1 |
| 6535855 | Cahill et al. | Mar 2003 | B1 |
| 6540722 | Boyle et al. | Apr 2003 | B1 |
| 6542173 | Buckley | Apr 2003 | B1 |
| 6542491 | Tari et al. | Apr 2003 | B1 |
| 6545612 | Lindgren et al. | Apr 2003 | B1 |
| 6545669 | Kinawi et al. | Apr 2003 | B1 |
| 6545722 | Schultheiss | Apr 2003 | B1 |
| 6546387 | Triggs | Apr 2003 | B1 |
| 6546419 | Humpleman et al. | Apr 2003 | B1 |
| 6550672 | Tracy et al. | Apr 2003 | B1 |
| 6553240 | Dervarics | Apr 2003 | B1 |
| 6553431 | Yamamoto et al. | Apr 2003 | B1 |
| 6556313 | Chang et al. | Apr 2003 | B1 |
| 6560651 | Katz et al. | May 2003 | B2 |
| 6574672 | Mitchell et al. | Jun 2003 | B1 |
| 6577861 | Ogasawara | Jun 2003 | B2 |
| 6578072 | Watanabe et al. | Jun 2003 | B2 |
| 6584903 | Jacobs | Jul 2003 | B2 |
| 6587835 | Treyz | Jul 2003 | B1 |
| 6598031 | Ice | Jul 2003 | B1 |
| 6600569 | Osada et al. | Jul 2003 | B1 |
| 6601093 | Peters | Jul 2003 | B1 |
| 6601108 | Marmor | Jul 2003 | B1 |
| 6604135 | Rogers et al. | Aug 2003 | B1 |
| 6604140 | Beck et al. | Aug 2003 | B1 |
| 6604148 | Dennison | Aug 2003 | B1 |
| 6607314 | McCannon et al. | Aug 2003 | B1 |
| 6608928 | Queiroz | Aug 2003 | B1 |
| 6618039 | Grant et al. | Sep 2003 | B1 |
| 6618592 | Vilander et al. | Sep 2003 | B1 |
| 6621589 | Al-Kazily et al. | Sep 2003 | B1 |
| 6622015 | Himmel et al. | Sep 2003 | B1 |
| 6622018 | Erekson | Sep 2003 | B1 |
| 6623527 | Hamzy | Sep 2003 | B1 |
| 6628302 | White et al. | Sep 2003 | B2 |
| 6628417 | Naito et al. | Sep 2003 | B1 |
| 6633346 | Yamamoto | Oct 2003 | B1 |
| 6633395 | Tuchitoi et al. | Oct 2003 | B1 |
| 6633757 | Hermann et al. | Oct 2003 | B1 |
| 6636202 | Ishmael, Jr. et al. | Oct 2003 | B2 |
| 6636259 | Anderson et al. | Oct 2003 | B1 |
| 6643650 | Slaughter et al. | Nov 2003 | B1 |
| 6654135 | Mitani | Nov 2003 | B2 |
| 6658625 | Allen | Dec 2003 | B1 |
| 6662224 | Angwin et al. | Dec 2003 | B1 |
| 6670982 | Clough et al. | Dec 2003 | B2 |
| 6671068 | Chang et al. | Dec 2003 | B1 |
| 6678004 | Schultheiss | Jan 2004 | B1 |
| 6678751 | Hays et al. | Jan 2004 | B1 |
| 6690918 | Evans et al. | Feb 2004 | B2 |
| 6694371 | Sanai | Feb 2004 | B1 |
| 6697848 | Hamilton et al. | Feb 2004 | B2 |
| 6701009 | Makoto et al. | Mar 2004 | B1 |
| 6702181 | Ramachandran | Mar 2004 | B2 |
| 6705781 | Iwazaki | Mar 2004 | B2 |
| 6707581 | Browning | Mar 2004 | B1 |
| 6711677 | Wiegley | Mar 2004 | B1 |
| 6725281 | Zintel et al. | Apr 2004 | B1 |
| 6735616 | Thompson et al. | May 2004 | B1 |
| 6737591 | Lapstun et al. | May 2004 | B1 |
| 6738841 | Wolff | May 2004 | B1 |
| 6741871 | Silverbrook et al. | May 2004 | B1 |
| 6745229 | Gobin et al. | Jun 2004 | B1 |
| 6745937 | Walsh et al. | Jun 2004 | B2 |
| 6748056 | Capriotti et al. | Jun 2004 | B1 |
| 6748195 | Phillips | Jun 2004 | B1 |
| 6750978 | Marggraff et al. | Jun 2004 | B1 |
| 6751732 | Strobel et al. | Jun 2004 | B2 |
| 6753978 | Chang | Jun 2004 | B1 |
| 6757070 | Lin et al. | Jun 2004 | B1 |
| 6760745 | Tan et al. | Jul 2004 | B1 |
| 6769012 | Liu et al. | Jul 2004 | B1 |
| 6771749 | Bansal et al. | Aug 2004 | B1 |
| 6775407 | Gindele et al. | Aug 2004 | B1 |
| 6778289 | Iwata | Aug 2004 | B1 |
| 6784855 | Matthews et al. | Aug 2004 | B2 |
| 6785727 | Yamazaki | Aug 2004 | B1 |
| 6788332 | Cook | Sep 2004 | B1 |
| 6788428 | Shimokawa | Sep 2004 | B1 |
| 6789107 | Bates et al. | Sep 2004 | B1 |
| 6789228 | Merril et al. | Sep 2004 | B1 |
| 6792148 | Wergeland et al. | Sep 2004 | B1 |
| 6798530 | Buckley | Sep 2004 | B1 |
| 6801692 | Nishimura et al. | Oct 2004 | B2 |
| 6801962 | Taniguchi et al. | Oct 2004 | B2 |
| 6813039 | Silverbrook et al. | Nov 2004 | B1 |
| 6816724 | Asikainen | Nov 2004 | B1 |
| 6819919 | Tanaka | Nov 2004 | B1 |
| 6826632 | Wugofski | Nov 2004 | B1 |
| 6830340 | Olson et al. | Dec 2004 | B2 |
| 6839623 | Tillgren et al. | Jan 2005 | B1 |
| 6839775 | Kao et al. | Jan 2005 | B1 |
| 6840441 | Monaghan et al. | Jan 2005 | B2 |
| 6845398 | Galensky et al. | Jan 2005 | B1 |
| 6850252 | Hoffberg | Feb 2005 | B1 |
| 6850767 | Maxymych | Feb 2005 | B1 |
| 6856430 | Gase | Feb 2005 | B1 |
| 6857021 | Schuster et al. | Feb 2005 | B1 |
| 6857132 | Rakib et al. | Feb 2005 | B1 |
| 6857716 | Nagahashi | Feb 2005 | B1 |
| 6859197 | Klein | Feb 2005 | B2 |
| 6859228 | Chang et al. | Feb 2005 | B1 |
| 6859937 | Narayan et al. | Feb 2005 | B1 |
| 6873836 | Sorrells et al. | Mar 2005 | B1 |
| 6882859 | Rao et al. | Apr 2005 | B1 |
| 6885878 | Borgstrom et al. | Apr 2005 | B1 |
| 6888643 | Grimes | May 2005 | B1 |
| 6889385 | Rakib et al. | May 2005 | B1 |
| 6892230 | Gu et al. | May 2005 | B1 |
| 6892251 | Anderson et al. | May 2005 | B2 |
| 6895444 | Weisshaar et al. | May 2005 | B1 |
| 6898640 | Kurita et al. | May 2005 | B1 |
| 6901429 | Dowling | May 2005 | B2 |
| 6904527 | Parlour et al. | Jun 2005 | B1 |
| 6909424 | Liebenow et al. | Jun 2005 | B2 |
| 6910068 | Zintel et al. | Jun 2005 | B2 |
| 6914694 | Ichikawa et al. | Jul 2005 | B1 |
| 6915124 | Kiessling et al. | Jul 2005 | B1 |
| 6915422 | Nakamura | Jul 2005 | B1 |
| 6922258 | Pineau | Jul 2005 | B2 |
| 6922725 | Lamming et al. | Jul 2005 | B2 |
| 6928614 | Everhart | Aug 2005 | B1 |
| 6930709 | Creamer et al. | Aug 2005 | B1 |
| 6932523 | Yamada et al. | Aug 2005 | B1 |
| 6941014 | Lin et al. | Sep 2005 | B2 |
| 6947067 | Halttunen | Sep 2005 | B2 |
| 6947995 | Chang et al. | Sep 2005 | B2 |
| 6950645 | Kammer et al. | Sep 2005 | B1 |
| 6952414 | Willig | Oct 2005 | B1 |
| 6957194 | Stefik et al. | Oct 2005 | B2 |
| 6958821 | McIntyre | Oct 2005 | B1 |
| 6959339 | Wu et al. | Oct 2005 | B1 |
| 6963582 | Xu | Nov 2005 | B1 |
| 6980319 | Ohta | Dec 2005 | B2 |
| 6983310 | Rouse et al. | Jan 2006 | B2 |
| 6990548 | Kaylor | Jan 2006 | B1 |
| 6995859 | Silverbrook et al. | Feb 2006 | B1 |
| 6996555 | Muto et al. | Feb 2006 | B2 |
| 6999112 | Seaman et al. | Feb 2006 | B2 |
| 7004395 | Koenck et al. | Feb 2006 | B2 |
| 7007066 | Malik | Feb 2006 | B1 |
| 7007067 | Azvine et al. | Feb 2006 | B1 |
| 7016062 | Ishizuka | Mar 2006 | B2 |
| 7020685 | Chen et al. | Mar 2006 | B1 |
| 7024200 | McKenna et al. | Apr 2006 | B2 |
| 7025256 | Drummond et al. | Apr 2006 | B1 |
| 7028102 | Larsson et al. | Apr 2006 | B1 |
| 7038797 | Lapstun et al. | May 2006 | B1 |
| 7039358 | Shellhammer et al. | May 2006 | B1 |
| 7039445 | Yoshizawa | May 2006 | B1 |
| 7047302 | Chatani et al. | May 2006 | B1 |
| 7054296 | Sorrells et al. | May 2006 | B1 |
| 7058356 | Slotznick | Jun 2006 | B2 |
| 7062651 | Lapstun et al. | Jun 2006 | B1 |
| 7068621 | Bouet et al. | Jun 2006 | B2 |
| 7069578 | Prus et al. | Jun 2006 | B1 |
| 7076534 | Cleron et al. | Jul 2006 | B1 |
| 7076730 | Baker | Jul 2006 | B1 |
| 7085814 | Gandhi et al. | Aug 2006 | B1 |
| 7088691 | Fujita | Aug 2006 | B2 |
| 7088990 | Isomursu et al. | Aug 2006 | B1 |
| 7095854 | Ginter et al. | Aug 2006 | B1 |
| 7099027 | Barry et al. | Aug 2006 | B1 |
| 7099304 | Liu et al. | Aug 2006 | B2 |
| 7103834 | Humpleman et al. | Sep 2006 | B1 |
| 7112138 | Hedrick et al. | Sep 2006 | B2 |
| 7113979 | Smith et al. | Sep 2006 | B1 |
| 7133845 | Ginter et al. | Nov 2006 | B1 |
| 7133846 | Ginter et al. | Nov 2006 | B1 |
| 7136999 | Griffiths | Nov 2006 | B1 |
| 7139591 | Callaghan et al. | Nov 2006 | B2 |
| 7143356 | Shafrir et al. | Nov 2006 | B1 |
| 7149726 | Lingle et al. | Dec 2006 | B1 |
| 7155163 | Cannon et al. | Dec 2006 | B2 |
| 7158953 | DeMello et al. | Jan 2007 | B1 |
| 7164413 | Davis et al. | Jan 2007 | B2 |
| 7164885 | Jonsson et al. | Jan 2007 | B2 |
| 7170857 | Stephens et al. | Jan 2007 | B2 |
| 7178718 | Silverbrook et al. | Feb 2007 | B2 |
| 7180475 | Slobodin et al. | Feb 2007 | B2 |
| 7180614 | Senoo et al. | Feb 2007 | B1 |
| 7184707 | Tada et al. | Feb 2007 | B2 |
| 7185108 | Okachi | Feb 2007 | B1 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7197531 | Anderson | Mar 2007 | B2 |
| 7203721 | Ben-Efraim et al. | Apr 2007 | B1 |
| 7213061 | Hite et al. | May 2007 | B1 |
| 7215436 | Hull et al. | May 2007 | B2 |
| 7221961 | Fukumoto et al. | May 2007 | B1 |
| 7237253 | Blackketter et al. | Jun 2007 | B1 |
| 7239346 | Priddy | Jul 2007 | B1 |
| 7239868 | Furukawa et al. | Jul 2007 | B2 |
| 7260597 | Hofrichter et al. | Aug 2007 | B1 |
| 7262873 | Rasche et al. | Aug 2007 | B1 |
| 7263270 | Lapstun et al. | Aug 2007 | B1 |
| 7272788 | Anderson et al. | Sep 2007 | B2 |
| 7283808 | Castell et al. | Oct 2007 | B2 |
| 7287089 | Lamoureux et al. | Oct 2007 | B1 |
| 7289792 | Turunen | Oct 2007 | B1 |
| 7289964 | Bowman-Amuah | Oct 2007 | B1 |
| 7305713 | Crance | Dec 2007 | B1 |
| 7318086 | Chang et al. | Jan 2008 | B2 |
| 7327481 | Such et al. | Feb 2008 | B2 |
| 7330110 | Heintzman et al. | Feb 2008 | B1 |
| 7334024 | Martino | Feb 2008 | B2 |
| 7337472 | Olsen et al. | Feb 2008 | B2 |
| 7346374 | Witkowski et al. | Mar 2008 | B2 |
| 7348961 | Shneidman | Mar 2008 | B1 |
| 7349722 | Witkowski et al. | Mar 2008 | B2 |
| 7349955 | Korb et al. | Mar 2008 | B1 |
| 7353280 | Chiles et al. | Apr 2008 | B2 |
| 7355730 | Landau et al. | Apr 2008 | B2 |
| 7355732 | Yamaguchi | Apr 2008 | B2 |
| 7356347 | Kammer | Apr 2008 | B1 |
| 7359714 | Parupudi et al. | Apr 2008 | B2 |
| 7360230 | Paz et al. | Apr 2008 | B1 |
| 7366468 | Yoshida | Apr 2008 | B2 |
| 7370090 | Nakaoka et al. | May 2008 | B2 |
| 7376583 | Rolf | May 2008 | B1 |
| 7379660 | Shiohara | May 2008 | B2 |
| 7379914 | Aoki et al. | May 2008 | B2 |
| 7379958 | Karhu | May 2008 | B2 |
| 7383355 | Berkman et al. | Jun 2008 | B1 |
| 7403510 | Miyake | Jul 2008 | B1 |
| 7412651 | Lapstun et al. | Aug 2008 | B2 |
| 7428575 | Motoyama | Sep 2008 | B1 |
| 7440772 | White et al. | Oct 2008 | B2 |
| 7451195 | Seligmann | Nov 2008 | B1 |
| 7454796 | Mazzagatte et al. | Nov 2008 | B2 |
| 7460853 | Toyoshima | Dec 2008 | B2 |
| 7477890 | Narayanaswami | Jan 2009 | B1 |
| 7478403 | Allavarpu et al. | Jan 2009 | B1 |
| 7483958 | Elabbady et al. | Jan 2009 | B1 |
| 7511630 | Strickland et al. | Mar 2009 | B2 |
| 7512671 | Gladwin et al. | Mar 2009 | B1 |
| 7526762 | Astala et al. | Apr 2009 | B1 |
| 7533344 | Motoyama et al. | May 2009 | B1 |
| 7554684 | Senoo et al. | Jun 2009 | B1 |
| 7555287 | Heinonen et al. | Jun 2009 | B1 |
| 7571142 | Flitcroft et al. | Aug 2009 | B1 |
| 7574723 | Putterman et al. | Aug 2009 | B2 |
| 7577910 | Husemann et al. | Aug 2009 | B1 |
| 7580005 | Palin | Aug 2009 | B1 |
| RE40910 | Aoki et al. | Sep 2009 | E |
| 7584269 | Moore et al. | Sep 2009 | B2 |
| 7587196 | Hansen | Sep 2009 | B2 |
| 7593123 | Sugahara | Sep 2009 | B2 |
| 7609402 | Chang et al. | Oct 2009 | B2 |
| 7616600 | Sparr et al. | Nov 2009 | B2 |
| 7630721 | Ortiz | Dec 2009 | B2 |
| 7644018 | Yukie et al. | Jan 2010 | B1 |
| 7644039 | Magee et al. | Jan 2010 | B1 |
| 7646503 | Silverbrook et al. | Jan 2010 | B2 |
| 7650145 | Ukita et al. | Jan 2010 | B2 |
| 7660460 | Wu et al. | Feb 2010 | B2 |
| 7660601 | Janik et al. | Feb 2010 | B2 |
| 7668535 | Conneely et al. | Feb 2010 | B2 |
| 7685244 | Mousseau et al. | Mar 2010 | B2 |
| 7688467 | Enmei | Mar 2010 | B2 |
| 7697467 | Kubler et al. | Apr 2010 | B2 |
| 7712125 | Herigstad et al. | May 2010 | B2 |
| 7725912 | Margulis | May 2010 | B2 |
| 7738886 | Connolly et al. | Jun 2010 | B1 |
| 7743133 | Motoyama et al. | Jun 2010 | B1 |
| RE41416 | Liu et al. | Jul 2010 | E |
| 7761541 | Morley et al. | Jul 2010 | B1 |
| RE41487 | Liu et al. | Aug 2010 | E |
| RE41532 | Liu et al. | Aug 2010 | E |
| 7779097 | Lamkin et al. | Aug 2010 | B2 |
| RE41689 | Liu et al. | Sep 2010 | E |
| 7797367 | Gelvin et al. | Sep 2010 | B1 |
| 7805720 | Chang et al. | Sep 2010 | B2 |
| RE41882 | Liu et al. | Oct 2010 | E |
| 7812856 | Ortiz et al. | Oct 2010 | B2 |
| 7814516 | Stecyk et al. | Oct 2010 | B2 |
| 7831276 | Kumar | Nov 2010 | B2 |
| 7840639 | Gough | Nov 2010 | B1 |
| 7890581 | Rao et al. | Feb 2011 | B2 |
| 7894474 | Bell | Feb 2011 | B1 |
| 7900833 | Silverbrook et al. | Mar 2011 | B2 |
| 7904579 | Janik et al. | Mar 2011 | B2 |
| 7908401 | Chang | Mar 2011 | B2 |
| 7929950 | Rao et al. | Apr 2011 | B1 |
| 7937450 | Janik | May 2011 | B2 |
| 7941541 | Chang et al. | May 2011 | B2 |
| 7944577 | Chang et al. | May 2011 | B2 |
| 7949223 | Shiohara | May 2011 | B2 |
| 7953818 | Chang et al. | May 2011 | B2 |
| 7957354 | Hickman et al. | Jun 2011 | B1 |
| 7958457 | Brandenberg et al. | Jun 2011 | B1 |
| 7971784 | Lapstun et al. | Jul 2011 | B2 |
| 7984098 | Enete et al. | Jul 2011 | B2 |
| 7986298 | Dulaney et al. | Jul 2011 | B1 |
| 7991347 | Chan | Aug 2011 | B1 |
| RE42725 | Chang et al. | Sep 2011 | E |
| RE42828 | Liu et al. | Oct 2011 | E |
| 8045952 | Qureshey et al. | Oct 2011 | B2 |
| 8073565 | Johnson | Dec 2011 | B2 |
| 8082491 | Abdelaziz et al. | Dec 2011 | B1 |
| 8082572 | Tilford | Dec 2011 | B1 |
| 8086961 | Saeki et al. | Dec 2011 | B2 |
| 8098140 | Escobosa et al. | Jan 2012 | B1 |
| RE43181 | Liu et al. | Feb 2012 | E |
| 8122163 | Morohashi | Feb 2012 | B2 |
| 8146077 | McNally et al. | Mar 2012 | B2 |
| 8169649 | Chang et al. | May 2012 | B2 |
| 8184324 | Chang et al. | May 2012 | B2 |
| 8285802 | Chang et al. | Oct 2012 | B2 |
| 8295406 | Sorrells et al. | Oct 2012 | B1 |
| 8296757 | Chang et al. | Oct 2012 | B2 |
| 8332521 | Chang et al. | Dec 2012 | B2 |
| 8339496 | Shiohara | Dec 2012 | B2 |
| 8359397 | Traversal et al. | Jan 2013 | B2 |
| 8386557 | Fillebrown et al. | Feb 2013 | B2 |
| RE44103 | Williams | Mar 2013 | E |
| 8448215 | Hassell et al. | May 2013 | B2 |
| 8467969 | Nielsen et al. | Jun 2013 | B2 |
| 8533352 | Chang | Sep 2013 | B2 |
| 8583263 | Hoffberg et al. | Nov 2013 | B2 |
| 8595717 | Chang et al. | Nov 2013 | B2 |
| 8630000 | Chang et al. | Jan 2014 | B2 |
| 8705097 | Chang et al. | Apr 2014 | B2 |
| 8706627 | Shore | Apr 2014 | B2 |
| 8707185 | Robinson et al. | Apr 2014 | B2 |
| 8711408 | Chang et al. | Apr 2014 | B2 |
| 8964220 | Chang et al. | Feb 2015 | B2 |
| 8972610 | Chang | Mar 2015 | B2 |
| 8989064 | Chang et al. | Mar 2015 | B2 |
| 9009060 | McNally | Apr 2015 | B2 |
| 9015329 | Chang et al. | Apr 2015 | B2 |
| 9031537 | Ortiz et al. | May 2015 | B2 |
| 9036181 | Chang et al. | May 2015 | B2 |
| 9037088 | Chang et al. | May 2015 | B2 |
| 9042811 | Chang et al. | May 2015 | B2 |
| 9043482 | Chang | May 2015 | B2 |
| 9069510 | Chang et al. | Jun 2015 | B2 |
| 9075504 | Takeuchi | Jul 2015 | B2 |
| 9092177 | Chang et al. | Jul 2015 | B2 |
| 9092535 | Gough | Jul 2015 | B1 |
| 9099152 | Marcus | Aug 2015 | B2 |
| 9100825 | Schultz et al. | Aug 2015 | B2 |
| 9110622 | Chang et al. | Aug 2015 | B2 |
| 9116723 | Chang et al. | Aug 2015 | B2 |
| 9122429 | Cecile et al. | Sep 2015 | B1 |
| 9164718 | Chang et al. | Oct 2015 | B2 |
| 9210340 | Mizutani et al. | Dec 2015 | B2 |
| 9298407 | Chang et al. | Mar 2016 | B2 |
| 9324208 | Gagner et al. | Apr 2016 | B2 |
| 9351193 | Raleigh et al. | May 2016 | B2 |
| 9383956 | Chang et al. | Jul 2016 | B2 |
| 9389822 | Chang et al. | Jul 2016 | B2 |
| 9491523 | Margulis | Nov 2016 | B2 |
| 9549835 | Short et al. | Jan 2017 | B2 |
| 9622058 | Imes | Apr 2017 | B1 |
| 9798516 | Chang et al. | Oct 2017 | B2 |
| 9819710 | Anderson et al. | Nov 2017 | B2 |
| RE46637 | Liu et al. | Dec 2017 | E |
| 9836257 | Chang et al. | Dec 2017 | B2 |
| 9836259 | Chang | Dec 2017 | B2 |
| 9841935 | Chang et al. | Dec 2017 | B2 |
| 9965233 | Chang et al. | May 2018 | B2 |
| 9971555 | Chang et al. | May 2018 | B2 |
| 10037178 | Chang et al. | Jul 2018 | B2 |
| 10055634 | Han et al. | Aug 2018 | B2 |
| 10108394 | Chang et al. | Oct 2018 | B2 |
| 10126991 | Chang | Nov 2018 | B2 |
| 10133527 | Chang | Nov 2018 | B2 |
| 10140071 | Chang et al. | Nov 2018 | B2 |
| 10140072 | Chang et al. | Nov 2018 | B2 |
| 10140073 | Chang et al. | Nov 2018 | B2 |
| 10152285 | Chang et al. | Dec 2018 | B2 |
| 10162596 | Chang et al. | Dec 2018 | B2 |
| 10261739 | Chang et al. | Apr 2019 | B2 |
| 10284953 | Hammer et al. | May 2019 | B2 |
| 10303411 | Chang et al. | May 2019 | B2 |
| 10346114 | Chang et al. | Jul 2019 | B2 |
| 10359957 | Chang et al. | Jul 2019 | B2 |
| 10387087 | Chang et al. | Aug 2019 | B2 |
| 10481846 | Chang et al. | Nov 2019 | B2 |
| 10481847 | Chang | Nov 2019 | B2 |
| 10489096 | Chang et al. | Nov 2019 | B2 |
| 10592201 | Chang et al. | Mar 2020 | B2 |
| 10592202 | Chang et al. | Mar 2020 | B2 |
| 10606535 | Chang et al. | Mar 2020 | B2 |
| 10642576 | Chang et al. | May 2020 | B2 |
| RE48066 | Liu et al. | Jun 2020 | E |
| RE48088 | Liu et al. | Jul 2020 | E |
| 10740066 | Chang et al. | Aug 2020 | B2 |
| 10761791 | Chang et al. | Sep 2020 | B2 |
| 10768871 | Chang et al. | Sep 2020 | B2 |
| 10841798 | Chang et al. | Nov 2020 | B2 |
| 10846031 | Chang et al. | Nov 2020 | B2 |
| 10860290 | Chang et al. | Dec 2020 | B2 |
| 10866773 | Chang et al. | Dec 2020 | B2 |
| 10873856 | Chang et al. | Dec 2020 | B2 |
| 10915296 | Chang et al. | Feb 2021 | B2 |
| 20010011302 | Son | Aug 2001 | A1 |
| 20010012281 | Hall et al. | Aug 2001 | A1 |
| 20010015717 | Mishra | Aug 2001 | A1 |
| 20010019953 | Furukawa et al. | Sep 2001 | A1 |
| 20010029531 | Ohta | Oct 2001 | A1 |
| 20010032254 | Hawkins | Oct 2001 | A1 |
| 20010034222 | Roustaei et al. | Oct 2001 | A1 |
| 20010055492 | Wood et al. | Dec 2001 | A1 |
| 20010055951 | Slotznick | Dec 2001 | A1 |
| 20020002707 | Ekel et al. | Jan 2002 | A1 |
| 20020009988 | Murata | Jan 2002 | A1 |
| 20020010756 | Oku | Jan 2002 | A1 |
| 20020012329 | Atkinson et al. | Jan 2002 | A1 |
| 20020013730 | Bigus | Jan 2002 | A1 |
| 20020017827 | Zuppero et al. | Feb 2002 | A1 |
| 20020026492 | Fujita | Feb 2002 | A1 |
| 20020038612 | Iwazaki | Apr 2002 | A1 |
| 20020042263 | Ishikawa | Apr 2002 | A1 |
| 20020049580 | Kutaragi et al. | Apr 2002 | A1 |
| 20020049839 | Miida et al. | Apr 2002 | A1 |
| 20020051200 | Chang et al. | May 2002 | A1 |
| 20020057452 | Yoshino | May 2002 | A1 |
| 20020059489 | Davis et al. | May 2002 | A1 |
| 20020062398 | Chang et al. | May 2002 | A1 |
| 20020062406 | Chang et al. | May 2002 | A1 |
| 20020065873 | Ishizuka | May 2002 | A1 |
| 20020071577 | Lemay et al. | Jun 2002 | A1 |
| 20020077980 | Chang et al. | Jun 2002 | A1 |
| 20020078101 | Chang et al. | Jun 2002 | A1 |
| 20020078161 | Cheng | Jun 2002 | A1 |
| 20020081993 | Toyoshima | Jun 2002 | A1 |
| 20020087622 | Anderson | Jul 2002 | A1 |
| 20020090912 | Cannon et al. | Jul 2002 | A1 |
| 20020092029 | Smith | Jul 2002 | A1 |
| 20020097408 | Chang et al. | Jul 2002 | A1 |
| 20020097415 | Chang et al. | Jul 2002 | A1 |
| 20020097416 | Chang et al. | Jul 2002 | A1 |
| 20020097417 | Chang et al. | Jul 2002 | A1 |
| 20020097418 | Chang et al. | Jul 2002 | A1 |
| 20020097419 | Chang et al. | Jul 2002 | A1 |
| 20020097433 | Chang et al. | Jul 2002 | A1 |
| 20020099884 | Chang et al. | Jul 2002 | A1 |
| 20020178272 | Igarashi et al. | Nov 2002 | A1 |
| 20020194302 | Blumberg | Dec 2002 | A1 |
| 20030002072 | Berkema et al. | Jan 2003 | A1 |
| 20030013483 | Ausems et al. | Jan 2003 | A1 |
| 20030013484 | Nishimura et al. | Jan 2003 | A1 |
| 20030028481 | Flitcroft et al. | Feb 2003 | A1 |
| 20030054846 | Parry | Mar 2003 | A1 |
| 20030061381 | Brisebois et al. | Mar 2003 | A1 |
| 20030061606 | Hartwig et al. | Mar 2003 | A1 |
| 20030073431 | Dorenbosch | Apr 2003 | A1 |
| 20030084177 | Mulligan | May 2003 | A1 |
| 20030088421 | Maes et al. | May 2003 | A1 |
| 20030115256 | Brockway et al. | Jun 2003 | A1 |
| 20030120754 | Muto et al. | Jun 2003 | A1 |
| 20030122934 | Shiohara | Jul 2003 | A1 |
| 20030128272 | Clough et al. | Jul 2003 | A1 |
| 20030160993 | Kang | Aug 2003 | A1 |
| 20030211188 | Kachnic | Nov 2003 | A1 |
| 20030228842 | Heinonen et al. | Dec 2003 | A1 |
| 20040024688 | Bi et al. | Feb 2004 | A1 |
| 20040057075 | Stewart et al. | Mar 2004 | A1 |
| 20040127254 | Chang | Jul 2004 | A1 |
| 20040193900 | Nair | Sep 2004 | A1 |
| 20050078088 | Davis et al. | Apr 2005 | A1 |
| 20050086300 | Yeager et al. | Apr 2005 | A1 |
| 20050114869 | Iwamura et al. | May 2005 | A1 |
| 20050125664 | Berkema et al. | Jun 2005 | A1 |
| 20050204176 | Togawa | Sep 2005 | A1 |
| 20050210120 | Yukie et al. | Sep 2005 | A1 |
| 20050222963 | Johnson | Oct 2005 | A1 |
| 20050231761 | Pineau | Oct 2005 | A1 |
| 20060013630 | Silverbrook et al. | Jan 2006 | A1 |
| 20060112414 | Ikonen et al. | May 2006 | A1 |
| 20060129627 | Phillips et al. | Jun 2006 | A1 |
| 20060167784 | Hoffberg | Jul 2006 | A1 |
| 20070125860 | Lapstun et al. | Jun 2007 | A1 |
| 20070129109 | Silverbrook et al. | Jun 2007 | A1 |
| 20070133073 | Shida et al. | Jun 2007 | A1 |
| 20080004925 | Bangel et al. | Jan 2008 | A1 |
| 20080004965 | Park | Jan 2008 | A1 |
| 20080007482 | Morioka | Jan 2008 | A1 |
| 20080049253 | Chang et al. | Feb 2008 | A1 |
| 20080049651 | Chang | Feb 2008 | A1 |
| 20080098468 | Cortopassi et al. | Apr 2008 | A1 |
| 20080146283 | Rao et al. | Jun 2008 | A1 |
| 20080201236 | Field et al. | Aug 2008 | A1 |
| 20080218776 | Takami et al. | Sep 2008 | A1 |
| 20080250459 | Roman | Oct 2008 | A1 |
| 20080318602 | Chang et al. | Dec 2008 | A1 |
| 20090002760 | Chang et al. | Jan 2009 | A1 |
| 20090048978 | Ginter et al. | Feb 2009 | A1 |
| 20090070411 | Chang et al. | Mar 2009 | A1 |
| 20090094457 | Lapstun et al. | Apr 2009 | A1 |
| 20090180142 | Suzuki et al. | Jul 2009 | A1 |
| 20090290182 | Hashimoto et al. | Nov 2009 | A1 |
| 20100003966 | Lu et al. | Jan 2010 | A1 |
| 20100020199 | Meitav et al. | Jan 2010 | A1 |
| 20100020382 | Su et al. | Jan 2010 | A1 |
| 20100022755 | Umeda et al. | Jan 2010 | A1 |
| 20100039660 | Chang et al. | Feb 2010 | A1 |
| 20100039669 | Chang et al. | Feb 2010 | A1 |
| 20100201996 | Chang et al. | Aug 2010 | A1 |
| 20100203824 | Chang et al. | Aug 2010 | A1 |
| 20100227550 | Chang et al. | Sep 2010 | A1 |
| 20110016280 | Chang et al. | Jan 2011 | A1 |
| 20110034150 | Chang et al. | Feb 2011 | A1 |
| 20110035319 | Brand et al. | Feb 2011 | A1 |
| 20110035682 | Chang et al. | Feb 2011 | A1 |
| 20110138378 | Chang et al. | Jun 2011 | A1 |
| 20110145074 | Polizzotto | Jun 2011 | A1 |
| 20110167166 | Chang et al. | Jul 2011 | A1 |
| 20110167175 | Chang | Jul 2011 | A1 |
| 20110197159 | Chaganti et al. | Aug 2011 | A1 |
| 20110211226 | Chang et al. | Sep 2011 | A1 |
| 20110279829 | Chang et al. | Nov 2011 | A1 |
| 20110279863 | Chang et al. | Nov 2011 | A1 |
| 20110313775 | Laligand et al. | Dec 2011 | A1 |
| 20120036016 | Hoffberg et al. | Feb 2012 | A1 |
| 20120089299 | Breed | Apr 2012 | A1 |
| 20120226777 | Shanahan | Sep 2012 | A1 |
| 20120230315 | Chang et al. | Sep 2012 | A1 |
| 20120258700 | Chang et al. | Oct 2012 | A1 |
| 20130079141 | Barney et al. | Mar 2013 | A1 |
| 20130095887 | Chang et al. | Apr 2013 | A1 |
| 20130103775 | Chang et al. | Apr 2013 | A1 |
| 20130104052 | Chang et al. | Apr 2013 | A1 |
| 20130109353 | Chang et al. | May 2013 | A1 |
| 20130267204 | Schultz et al. | Oct 2013 | A1 |
| 20130297670 | Lundberg et al. | Nov 2013 | A1 |
| 20140018130 | Chang | Jan 2014 | A1 |
| 20140082604 | Chang et al. | Mar 2014 | A1 |
| 20140309806 | Ricci | Oct 2014 | A1 |
| 20140309813 | Ricci | Oct 2014 | A1 |
| 20140309862 | Ricci | Oct 2014 | A1 |
| 20140309863 | Ricci | Oct 2014 | A1 |
| 20140309870 | Ricci et al. | Oct 2014 | A1 |
| 20140310031 | Ricci | Oct 2014 | A1 |
| 20140310333 | Franco et al. | Oct 2014 | A1 |
| 20140310788 | Ricci | Oct 2014 | A1 |
| 20150238817 | Watterson et al. | Aug 2015 | A1 |
| 20150325061 | Gerstenberg et al. | Nov 2015 | A1 |
| 20150356561 | Chang et al. | Dec 2015 | A1 |
| 20150356564 | Chang et al. | Dec 2015 | A1 |
| 20150356565 | Chang et al. | Dec 2015 | A1 |
| 20150363763 | Chang et al. | Dec 2015 | A1 |
| 20150381612 | Chang et al. | Dec 2015 | A1 |
| 20150382150 | Ansermet et al. | Dec 2015 | A1 |
| 20160011836 | Chang et al. | Jan 2016 | A1 |
| 20160054962 | Park | Feb 2016 | A1 |
| 20160072975 | Fujioka | Mar 2016 | A1 |
| 20160087957 | Shah et al. | Mar 2016 | A1 |
| 20160112798 | Kim et al. | Apr 2016 | A1 |
| 20160174068 | Chang et al. | Jun 2016 | A1 |
| 20160179462 | Bjorkengren | Jun 2016 | A1 |
| 20160239232 | Chang et al. | Aug 2016 | A1 |
| 20160239243 | Chang et al. | Aug 2016 | A1 |
| 20160274839 | Ohguro et al. | Sep 2016 | A1 |
| 20160313974 | Chang et al. | Oct 2016 | A1 |
| 20160314546 | Malnati et al. | Oct 2016 | A1 |
| 20160360341 | Srivatsa et al. | Dec 2016 | A1 |
| 20170006329 | Jang et al. | Jan 2017 | A1 |
| 20170039009 | Chang et al. | Feb 2017 | A1 |
| 20170064746 | Chang et al. | Mar 2017 | A1 |
| 20170075636 | Chang et al. | Mar 2017 | A1 |
| 20170078521 | Chang et al. | Mar 2017 | A1 |
| 20170078922 | Raleigh et al. | Mar 2017 | A1 |
| 20170185376 | Chang et al. | Jun 2017 | A1 |
| 20170228202 | Chang et al. | Aug 2017 | A1 |
| 20170242649 | Jarvis et al. | Aug 2017 | A1 |
| 20170249116 | Chang et al. | Aug 2017 | A1 |
| 20170277487 | Chang et al. | Sep 2017 | A1 |
| 20170286027 | Chang et al. | Oct 2017 | A1 |
| 20170318115 | Peng et al. | Nov 2017 | A1 |
| 20170364326 | Chang et al. | Dec 2017 | A1 |
| 20180011667 | Chang et al. | Jan 2018 | A1 |
| 20180024790 | Chang | Jan 2018 | A1 |
| 20180024791 | Chang et al. | Jan 2018 | A1 |
| 20180039456 | Chang et al. | Feb 2018 | A1 |
| 20180039459 | Chang et al. | Feb 2018 | A1 |
| 20180041482 | Chang et al. | Feb 2018 | A1 |
| 20180046418 | Chang | Feb 2018 | A1 |
| 20180107449 | Krampf et al. | Apr 2018 | A1 |
| 20180203647 | Chang et al. | Jul 2018 | A1 |
| 20180203648 | Chang et al. | Jul 2018 | A1 |
| 20180227140 | Ansari et al. | Aug 2018 | A1 |
| 20180253264 | Chang et al. | Sep 2018 | A1 |
| 20180335989 | Chang | Nov 2018 | A1 |
| 20180364929 | Chang et al. | Dec 2018 | A9 |
| 20180370701 | Maguire | Dec 2018 | A1 |
| 20190107980 | Chang | Apr 2019 | A1 |
| 20190121585 | Chang et al. | Apr 2019 | A1 |
| 20190121613 | Chang et al. | Apr 2019 | A1 |
| 20190250883 | Chang et al. | Aug 2019 | A1 |
| 20190272148 | Chang et al. | Sep 2019 | A1 |
| 20190303100 | Chang et al. | Oct 2019 | A1 |
| 20190344944 | Maguire | Nov 2019 | A1 |
| 20190361617 | Chang et al. | Nov 2019 | A1 |
| 20190384547 | Chang | Dec 2019 | A1 |
| 20200097225 | Chang et al. | Mar 2020 | A1 |
| 20200225889 | Chang et al. | Jul 2020 | A1 |
| 20210055891 | Chang | Feb 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 1217503 | May 1999 | CN |
| 1488106 | Apr 2004 | CN |
| 100334577 | Aug 2007 | CN |
| 1541370 | May 2010 | CN |
| 101833430 | Sep 2010 | CN |
| 101834892 | Sep 2010 | CN |
| 101825996 | May 2012 | CN |
| 19846452 | Dec 1999 | DE |
| 0866398 | Sep 1998 | EP |
| 0938041 | Aug 1999 | EP |
| 738949 | Feb 2002 | EP |
| 952513 | Feb 2004 | EP |
| 691619 | Feb 2007 | EP |
| 2357663 | Jun 2001 | GB |
| 2332764 | Nov 2002 | GB |
| H11143656 | May 1999 | JP |
| 11316658 | Nov 1999 | JP |
| 2000132353 | May 2000 | JP |
| 9817032 | Apr 1998 | WO |
| 9833293 | Jul 1998 | WO |
| 9839766 | Sep 1998 | WO |
| 9843433 | Oct 1998 | WO |
| 0002358 | Jan 2000 | WO |
| 0024192 | Apr 2000 | WO |
| 0051293 | Aug 2000 | WO |
| 0142894 | Jun 2001 | WO |
| 0195096 | Dec 2001 | WO |
| 0195097 | Dec 2001 | WO |
| 02084928 | Oct 2002 | WO |
| Entry |
|---|
| International Telecommunication Union, “Series T: Terminals for Telematic Services, Mixed Raster Content (MRC)”, Apr. 1999, 55 pages. |
| Bluetooth, Core, “Specification of the Bluetooth System,” Dec. 1, 1999, 1080 pages (attachments are in 4 parts). |
| White, “How Computers Work,” Oct. 2003, 420 pages (attachments are in 5 parts). |
| Wright, “Design Goals for an Internet Printing Protocol,” Apr. 1999, 43 pages. |
| “Part 11 Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” ANSI/IEEE Std. 802.11, 1999 Edition, 528 pages (attachments are in 2 parts). |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 16/215,506, filed Aug. 6, 2020, 119 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 16/696,989, filed Aug. 7, 2020, 92 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 16/403,113, filed Aug. 19, 2020, 13 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 16/696,989, filed Jan. 11, 2021, 22 pages. |
| United States District Court for the District of Delaware Memorandum Order, Jan. 31, 2020, 9 pages. |
| US Patent Trial and Appeal Board, Decision Granting Institution of Post-Grant Review, Jul. 7, 2020, 41 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/477,987, filed Sep. 26, 2014, 42 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Oct. 15, 2014, 14 pages. |
| United States Patent and Trademark Office, Supplemental Notice of Allowability for U.S. Appl. No. 13/477,987, filed Jan. 21, 2015, 7 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,689, filed Feb. 3, 2015, 57 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,695, filed Feb. 3, 2015, 57 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Feb. 19, 2015, 14 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Jun. 4, 2015, 17 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/204,695, filed Sep. 28, 2015, 33 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/204,689, filed Oct. 5, 2015, 33 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Oct. 5, 2015, 9 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,031, filed Feb. 10, 2016, 106 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/204,695, filed Feb. 26, 2016, 13 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Aug. 11, 2016, 26 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 11/933,031, filed Oct. 5, 2016, 12 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Jan. 12, 2017, 10 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed May 3, 2017, 9 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,031, filed Jun. 26, 2017, 28 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Aug. 23, 2017, 8 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 11/933,031, filed Dec. 27, 2017, 11 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/785,190, filed Feb. 23, 2018, 72 pages. |
| United States Patent and Trademark Office, Corrected Notice of Allowability for U.S. Appl. No. 09/992,413, filed Apr. 4, 2018, 7 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/978,076, filed Jun. 28, 2018, 19 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/785,190, filed Jul. 18, 2018, 21 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/922,741, filed Sep. 27, 2018, 76 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 15/787,067, filed Sep. 28, 2018, 73 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/973,317, filed Sep. 28, 2018, 71 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/924,077, filed Oct. 18, 2018, 75 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/973,317, filed Nov. 29, 2018, 9 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/973,317, filed Feb. 13, 2019, 14 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 15/978,076, filed Apr. 1, 2019, 85 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/973,317, filed Jun. 7, 2019, 10 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/787,067, filed Aug. 29, 2019 14 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/978,076, filed Oct. 4, 2019, 17 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 15/787,067, filed Oct. 23, 2019, 7 pages. |
| Albrecht, Markus et al., “IP Services over Bluetooth: Leading Way to a New Mobility,” IEEE Proceedings of 24th Conferences on Local Computer Networks, Oct. 18-20, 1999, Lowell, MA, 10 pages. |
| Petition filed in the US Patent Trial and Appeal Board for Post Grant Review of U.S. Pat. No. 10,303,411, filed Dec. 23, 2019, 129 pages. |
| Defendant Arlo Technologies, Inc.'s Opening Brief In Support Of Motion To Dismiss Plaintiffs First Amended Complaint For Failure To State A Claim, filed in the US District Court for the District of Delaware, Oct. 7, 2019, 26 pages. |
| Defendant PetCube, Inc.'s Opening Brief In Support Of Its Renewed Motion To Dismiss For Failure To State A Claim, filed in the US District Court for the District of Delaware, Nov. 5, 2019, 26 pages. |
| Defendant PetCube, Inc.'s Reply In Support Of Its Renewed Rule 12(b)(6) Motion To Dismiss For Failure To State A Claim, filed in the US District Court for the District of Delaware, Nov. 19, 2019, 15 pages. |
| Defendant Arlo Technologies, Inc.'s Reply Brief In Support Of Motion To Dismiss Plaintiffs First Amended Complaint, filed in the US District Court for the District of Delaware, Nov. 25, 2019, 15 pages. |
| Schulyer et al., “Solutions to Sharing Local Printers: LAN Systems Inc., LANSpool, $395 per Server”, PC Week, Oct. 1989, vol. 6, No. 39, p. 75 (2), 3 page. |
| Haynie, Dave, “The Zorro III Bus Specification: A General Purpose Expansion Bus for High Performance Amiga Computers,” Mar. 20, 1991, Revision 1.0, pp. 1-84. |
| House et al., “An on-line communication print service for the demanding client.” In Proceedings of the 11th Annual International Conference on Systems Documentation (Waterloo, Ontario, Canada, Oct. 5-8, 1993). SIGDOC 93. ACM, New York, NY, 135-139, 8 pages. |
| Screenshots from Microsoft® NT™, Figures 5-7, 1998, 3 pages. |
| Bisdikian et al., “WiSAP: a wireless personal access network for handheld computing devices,” Personal Communications, IEEE [see also IEEE Wireless Communications], vol. 5, No. 6, pp. 18-25, Dec. 1998, 9 pages. |
| Screenshots from Microsoft® Word 2000, Figures 1-4, 1999, 4 pages. |
| Miller, Brent, “Mapping Salutation Architecture APIs to Bluetooth Service Discovery Layer”, Jul. 1, 1999, Version 1.0, 26 pages. |
| U.S. Appl. No. 60/239,320, U.S. Appl. No. 60/239,320, U.S. Appl. No. 60/239,320, U.S. Appl. No. 60/239,320, U.S. Appl. No. 60/239,320, U.S. Appl. No. 60/239,320. |
| Bettstetter et al., “A Comparison Of Service Discovery Protocols And Implementation Of The Service Location Protocol”, Sep. 13-15, 2000, In Proceedings of the 6th EUNICE Open European Summer School: Innovative Internet Applications, 12 pages. |
| United States Patent and Trademark Office, International Search Report for PCT Application No. PCT/US01/43796, dated Mar. 20, 2002, 3 pages. |
| United States Patent and Trademark Office, International Preliminary Examination Report for PCT Application No. PCT/US01/43796, dated Jan. 15, 2003, 5 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,198, filed Jul. 6, 2004, 7 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,417, filed Oct. 27, 2004, 28 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,420, filed Feb. 25, 2005, 24 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,183, filed Mar. 14, 2005, 10 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,198, filed Apr. 4, 2005, 8 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,413, filed Jun. 29, 2007, 10 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,413, filed Apr. 1, 2009, 11 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,031, filed Sep. 9, 2009, 5 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,183, filed Jan. 13, 2010, 11 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,005, filed Apr. 30, 2010, 26 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,413, filed May 25, 2010, 12 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,689, filed Sep. 15, 2010, 9 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/684,869, filed Sep. 29, 2010, 17 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,413, filed Dec. 17, 2010, 14 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,695, filed Dec. 21, 2010, 13 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 11/933,005, filed Jan. 12, 2011, 44 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,183, filed Jan. 25, 2011, 40 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,689, filed Feb. 22, 2011, 33 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,031, filed May 26, 2011, 63 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,413, filed Sep. 14, 2011, 29 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,695, filed Sep. 15, 2011, 38 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/108,922, filed Mar. 15, 2012, 40 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/108,925, filed Mar. 26, 2012, 30 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 11/933,031, filed May 9, 2012, 60 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/108,922, Nov. 5, 2012, 63 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/108,925, filed Feb. 11, 2013, 44 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/108,922, filed May 24, 2013, 24 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 13/108,925, filed Jul. 17, 2013, 46 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,031, filed Jul. 18, 2013, 60 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,689, filed Aug. 15, 2013, 63 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,695, filed Aug. 27, 2013, 62 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 09/992,413, filed Sep. 17, 2013, 60 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/108,922, filed Sep. 19, 2013, 44 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/477,987, filed Feb. 25, 2014, 104 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 11/933,031, filed Apr. 22, 2014, 68 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/477,987, filed Jun. 6, 2014, 26 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,689, filed Jun. 10, 2014, 59 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 12/204,695, filed Jun. 10, 2014, 58 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, filed Jun. 19, 2014, 70 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210055891 A1 | Feb 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60252682 | Nov 2000 | US | |
| 60262764 | Jan 2001 | US | |
| 60245101 | Nov 2000 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16215506 | Dec 2018 | US |
| Child | 17092138 | US | |
| Parent | 15785190 | Oct 2017 | US |
| Child | 16215506 | US | |
| Parent | 09992413 | Nov 2001 | US |
| Child | 15785190 | US | |
| Parent | 17092138 | US | |
| Child | 15785190 | US | |
| Parent | 15332432 | Oct 2016 | US |
| Child | 16200380 | US | |
| Parent | 10053765 | Jan 2002 | US |
| Child | 15332432 | US | |
| Parent | 17092138 | US | |
| Child | 15332432 | US | |
| Parent | 16229896 | Dec 2018 | US |
| Child | 16416088 | US | |
| Parent | 15201194 | Jul 2016 | US |
| Child | 16229896 | US | |
| Parent | 13710295 | Dec 2012 | US |
| Child | 15201194 | US | |
| Parent | 12903048 | Oct 2010 | US |
| Child | 13710295 | US | |
| Parent | 10016223 | Nov 2001 | US |
| Child | 12903048 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16200380 | Nov 2018 | US |
| Child | 17092138 | US | |
| Parent | 16416088 | May 2019 | US |
| Child | 17092138 | US |
