Patent Grant
10740066
Present invention relates to device synchronization and digital output and, in particular, to providing pervasive output for information apparatuses.
An Information apparatus refers to both stationary computers and mobile computing devices (pervasive devices). Examples of information apparatuses include without limitation desktop computers, laptop computers, palmtop (hand-held) computers, personal digital assistants (PDAs), Internet-enabled cellular phones, smart phones, pagers, Internet appliances, e-books, digital pads, Web pads, and digital capturing devices (e.g., digital cameras and video cameras). An output device 140 may include a fax machine, printer, copier, image or video display device, projector, and an audio output device.
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 is used as a specific example to simplify description or may be one exemplary embodiment. The reference to 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. Unfortunately, the small display screen of a pervasive device may not provide a good viewing experience. 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 e-mail in his hand-held computer may want to walk up to a nearby printer or fax machine to have his e-mail printed. In addition, the mobile worker may also want to print a copy of his to-do list, appointment book, business card, and his flight schedule from his mobile device. As another example, a traveler stopping at a convenience store, gas station, or kiosks may want to print out a copy of the map he just downloaded from the Internet using his Internet enable wireless phone (information apparatus). In still another example, an individual who just finished a stock trade or performed an e-commerce transaction using his PDA (information apparatus) may want to print out a copy of his transaction confirmation, invoice or receipt. 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.
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 whether the connection is wired or wireless, a user must first install in the information apparatus a printer driver corresponding to a particular printer model and make. Using a device-dependent or specific driver, the information apparatus may process output content or a digital document into the printer input space. The printer input space corresponds to the type of input that a printer understands (herein referred to as print data). For example, the printer input space or print data may include a printer-specific input format (e.g., image, graphics, file, data format), encoding, page description language, markup language, instructions, protocols or data that can be understood or used by a particular printer make and model.
Print data may be proprietary or a published standard or a combination of the two. A printer input space or print data is therefore, in general, device dependent. Different printer models may specify their own input, designed or adopted for optimal operation by the printer manufacturer according to a specification. Consequently, different printers usually require use of specific printer drivers for accurate printing. A device driver (printer driver in this example) may control, manage, communicate, and output print data to a printer. Sometimes, instead of using a printer or device driver, the device driving feature may be included as part of an application software. The application in this example may process the document and communicate directly with an output device without utilizing a device driver. Print data is an output data sent to a printer. However, the term print data used here is intended to be applied or extended to the larger scope and definition of output data which applies to any output devices including display, projection and audio devices, and this should not be construed as restricting the scope and practice of present invention.
Installation of a 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. This installation and configuration process add 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 way for a user to more conveniently or easily output digital content to an output device without the inconvenience of manually finding and installing new device drivers or printer drivers. Installation of printer drivers, if needed, should be more automatic and transparent to end-users.
In addition, conventional printing methods may pose significantly higher challenges and difficulties for mobile device users than for home and office computer users. The requirement for pre-installation of a device-dependent driver is in conflict with the concept of mobile (pervasive) computing and output. For example, a mobile user may want to print e-mail, PowerPoint® presentation documents, web pages, or other documents in an airplane or at an airport, gas station, convenience 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. Therefore, the user may have to install and configure a printer driver each time at each of these locations before printing. Alternatively, it is also not a viable option usually to pre-install all of the possible hundreds, or even thousands, of printer drivers available to the user's information apparatus. A mobile information device usually has limited memory and storage capacity. As a consequence, the user would currently be required to install and configure a printer driver each time at each such different 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 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 solution is needed so that a user can simply walk up to a printer and easily print a digital document without having to install or pre-install a particular printer driver.
Network printing may partially solve the above problem in a local area network (LAN). Network printing was first motivated to allow people to share printing resources within a network. Printers are often connected to the network using a network adapter or network card. Print servers may be used to manage print jobs (such as spooling). Different clients may send print jobs to the print server for queuing, prioritizing and managing. The driver of each networked printer may be stored in the network (for example, in an application server) and available for clients to download.
The above configuration is often used in a local area network (LAN) such as in an office building. An office worker with a mobile or static computing device connected to this network may be able to send a print job to any printer that is connected to the same network. He either has the necessary printer drivers pre-installed in his device or he can download a driver from the LAN before printing to a particular printer. But once outside of the office building, or meaning outside of his wired or wireless network coverage, the office worker can no longer print to any printer he or she desires.
In one instance, it has been argued that the idea of local network printing can be further extended to the Internet as the larger and public network. In an ideal situation, every printer and every computing device (information apparatus) is connected to the same network, for example the Internet. But in reality, extending network printing to a big super-network or the Internet is still unavailable.
Nevertheless, one drawback of network printing may be higher cost. To connect the output devices and information apparatus to the same network, additional hardware or software may need to be installed. And therefore, the costs of output devices may be raised substantially. In addition to hardware and software costs there are also service charges to maintain the connectivity to a large network such as the Internet. Furthermore, a large permanent network infrastructure would need to be built and made available to each location.
In addition to costs, another drawback of network printing is reliability. Network printing requires perfect function in any part of the chain of network hardware, software and services. If any component of the link is down or not fully functional, for any reason, printing service may be unavailable, interrupted or result in inaccuracies.
Finally, another drawback of network printing is the issue of security. A user does not feel secure if confidential documents or information must pass through the entire network before reaching the printer immediately in front of him or her. There may be the fear that the confidential document could be intercepted, viewed, copied or stored within any segment of the connected network. There can also be the fear that the document could actually be printed to a different printer instead of the intended one. This problem may be caused by, for example, errors in directory service software, a software component that is not up-to-date or corrupted, inconsistent or incompatible software and/or hardware versions, or any combination of human, software, network, or hardware errors. There is also risk when downloading a software component (e.g., printer driver) from the network to an information apparatus. This software component maybe damaged, corrupted or carrying a malicious attack or virus or otherwise modified by hackers. A damaged software component can disrupt or corrupt the user's information apparatus. Finally, some internal corporate or local networks may reject unknown documents trying to reach their printers and other output devices protected within a firewall. It is therefore more desirable if the communication and exchange of information are done locally between users' information apparatus and the selected output device, all within the range of the users watchful, and inspecting eyes.
Accordingly, the present invention provides a convenient method of digital printing in which a user need not pre-install a device-dependent printer driver on an information apparatus in order to print.
This invention can provide an easy, friendly and convenient process for printing. Unlike conventional printing, a user need not manually install a printer driver from a CD, floppy disk, or download it somewhere from an existing static network. With the apparatus and process of present invention, all the software components, data, or printer drivers can be loaded to the information apparatus through easy and automatic synchronization process between the information apparatus and a printer having an output controller of present invention. As a result, a mobile user with an information apparatus equipped with an output manager of present invention can print pervasively virtually at any time, anywhere, to any printer.
Furthermore, this invention can provide a convenient method allowing users to print to any printer with or without connection to a static permanent network for both the information apparatus and the output device. Through local communication and synchronization directly between the information apparatus and the output device, hardware and software installation for static network connectivity may not be necessary. Therefore printing costs may be reduced.
In addition, this invention can provide a more reliable printing method than conventional remote network printing methods or processes. By communicating locally between an information apparatus and an output device, the printing process does not depend on the perfect function of each element of a network chain. This chain may include, for example, network connections, network servers, application servers, service providers and application providers. Therefore, the chance of a successful printing under present invention is greatly enhanced as processing and communication involves fewer elements.
This invention can further provide a more secure printing process than conventional network printing processes and methods. Uploading or downloading data or software components such as a printer driver from an output device immediately in front of user provides a more secure feeling than dealing with components from a remote location in the network. Components stored in a large network may be perceived to have more exposure to tampering (e.g., contaminated with a virus). An erroneous module or component in the network caused by a human or software or hardware error may also disrupt the function of the information apparatus. Furthermore, sending a confidential digital document or print data directly to the printer in front of user provides a more secure feeling than if the document is routed through a large network with a plurality of users and servers. There are greater possibilities of the document being intercepted, viewed, copied, stored or finally printed on a wrong printer in conventional network printing.
In accordance with present invention, an electronic system and method of pervasive output allow an information apparatus to output digital content conveniently to virtually any output device. The information apparatus may be equipped with a central processing unit, input/output control unit, storage unit, memory unit, and wired or wireless communication unit or adapters. The information apparatus preferably also includes output manager that may be implemented as application software, a client application, or device driver (printer driver in case of printer). The output manager may include management and control capabilities with hardware and software components including for example one or more communication chipsets residing in its host information apparatus.
The output manager in the information apparatus may be capable of communicating with, managing and synchronizing data or software components with an output device equipped with an output controller of present invention. Examples of output devices include, without limitation, printers, fax machines, copiers, image or video display devices, monitors, display screens, projectors, and audio output devices.
The output controller may be a circuit board, card or software components residing in an output device. Alternatively, the output controller may be connected externally to an output device as an external component or “box.” The output controller may be implemented with one or a combination of embedded processor, software, firmware, ASIC, DSP, FPGA, system on a chip, special chipsets, among others. In another embodiment, the functionality of the output controller may be provided by application software running on a PC, workstation or server connected externally to an output device.
The output controller may include a processing unit, memory/storage unit and communication adapter unit, among others. The storage or memory unit of the output controller may store device drivers, software components or objects encapsulating device dependent data, algorithms, and code. Device dependent data may be, for example, parameters and information about the output device and output controller. Software components and objects may encapsulate for example code or executables of algorithms necessary for converting or encoding an image or document description or language into print data or output data compatible with a specific output device. The output manager may manage the process of uploading data and or software components from an output controller to an information apparatus in order to, for example, enable the information apparatus to generate and transmit print data or output data accurately to the output device or the output controller.
Output data (or print data in the case where the output device is a printer) may be specific data, instructions, page description language, markup language, graphics and or image file format among others. Print data may also be encoded or compressed with one or more compression or encoding techniques. Furthermore, print data may use one or more open standards or one or more proprietary techniques and formats, or a combination. Output data (or print data for printers) refers to the electronic data sent from an information apparatus to the output device.
One implementation of a digital content output process of this invention includes the following steps.
1. A user requests to print a digital content from his/her information apparatus.
2. The information apparatus detects available output devices by a discovery process.
3. The information apparatus exchanges service information with output controllers associated with the available output devices in a service negotiation process. The user may then select one or more output devices based on the service information provided.
4. The information apparatus communicates with output controller to identify and upload the necessary components to enable output to a specific output device as part of a synchronization process. The uploaded components or data may then be installed or configured in the information apparatus.
5. The digital content intended for output is processed by one or more components to be compatible with the output device. The one or more components include the information apparatus with an output manager, an output controller and the output device.
6. The printer engine or display engine or audio engine generates final output.
In the output process of present invention, an output manager residing in the information apparatus may participate in, coordinate and manage the communication and exchange of information/components between its host information apparatus and output controllers.
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, as are known in the art. 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 an interface include, without limitation, a mouse, a keyboard, a touch-sensitive or non-touch-sensitive screen, one or more push buttons, soft keys, a stylus, a speaker, a microphone, etc.
An information apparatus 100 may be a dedicated single task device (e.g. email terminal, web terminal, e-book, etc) or a general-purpose computing device with multiple features and functions. These multiple functions and features may be implemented by one or more software applications (e.g., applications 302,
Some information apparatuses 100 (e.g., dedicated devices) may be pre-configured by manufacturers with fixed functionalities and features. Other information apparatuses 100 may allow users to install additional hardware components and application software (e.g., applications 302,
Functionalities and feature sets of an information apparatus 100 may be implemented in software or hardware or a combination of both. When features are implemented in software, this software may be installed by the manufacturer or by users. Application software may be implemented using embedded software running on embedded processors or it may run on a specific operating system. Some or all or combinations of applications and feature sets may also be implemented in hardware or in silicon. Some functionality or feature sets may be implemented in special chip sets and may include one or more or combinations of, for example, application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), systems on a chip, firmwares, etc.
Information apparatus 100 may or may not contain an operating system. In an implementation having an operating system, the operating system may provide a variety of application programming interfaces (APIs) or object models (e.g., APIs 300,
In one implementation, information apparatus 100 includes an output manager 308 (
One task for output manager 308 is to manage and coordinate communication between information apparatus 100 and one or more output controllers 120. Output manager 308 may, for example, implement an open-standard or a proprietary communication protocol to directly or indirectly interact with, manage, or utilize functionalities provided by hardware components residing in a host information apparatus 100. Such hardware components may include, for example, a processing unit, a memory unit and communication chipsets (not shown). Output manager 308 may include one or more of the following features and functionalities:
Output manager 308 may communicate and interact with one or more software applications 302 included in a host information apparatus 100 to provide pervasive output capability or feature to those software applications 302. The type of information passed from the software applications 302 to the output manager 308 may be, for example, a digital document or digital content data that needs output. In some instances, application software 302 may invoke or launch the output manager 308 as a separate application (as shown in
Output manager 308 may manage and maintain wired or wireless communications with output controller 120. Output manager 308 may interact with functionalities implemented by hardware components of its host information apparatus 100. As an example, the output manager 308 may manage and interact with the communication unit in the information apparatus 100.
Output manager 308 may help discover available output devices 140, verify communication connections, identify devices available or compatible for service, or send or broadcast service requests to one or more devices.
Output manager 308 may communicate with output controller 120 to identify necessary software components, data, or any other device dependent information or parameters, if any, that need to be uploaded from the output controller 120 to the host information apparatus 100 to enable pervasive output. Software components may be, for example, a device driver, an application, a special code or algorithm, an executable object or device dependent data, parameter, information, etc.
Output manager 308 may coordinate with output controller 120 to upload the necessary components or data from the output controller 120 to its host information apparatus 100 so that the user can output digital content pervasively to that output controller 120 or its associated output device 140.
Output manager 308 may perform raster image processing operations (e.g. rasterization, color management, half-toning operations) or convert digital content from its original format into print data compatible for input to a specific output controller 120 or output device 140. The digital content may be created, stored or received by the information apparatus 100. For example, an output manager 308 may convert digital document information from a certain format or language into a specific print data or intermediate format or language such as PostScript, PCL, EMF, XML, TIFF, JPEG, RTL, among others, for output.
Output manager 308 may coordinate or manage the communication between a host information apparatus 100 and output controller 120 to send or transmit the print data to the output controller 120.
Output Controller 120
An output controller 120 may be implemented as software or hardware and may be connected to or integrated within an output device 140. Output controllers 120H illustrate hardware implementations in the form of a circuit board or card that is installed or integrated into an output device 140, such as a printer, copiers, fax machine, display screen among others. In another configuration (not shown), output controller 120 may be implemented as a software application or component that is installed or integrated into an output device 140. Output controller 120G illustrates a hardware implementation in the form of an external component or “box” that is separately connected to one or more output devices 140.
Whether externally connected to or internally installed in output device 140, output controller 120 may be implemented with hardware, software, or both, that perform the feature sets and functionalities of the output controller 120 described herein. In the case of output device 140 being a printer, output controller 120 can also sometimes be called a printer server. Exemplary configurations and implementations of output controller 120 are described below with reference to
As one example, output controller 120 may be implemented as a computer connected to one or more output devices 140. For example, a conventional PC, workstation or server may serve the purpose of an output controller 120. In this case, the functionalities of output controller 120 may be implemented using application software installed in the computer (PC, server, or workstation), with the computer connected to the output device 140.
An output controller 120 installed or connected to an output device 140, such as a printer, enables the output device 140 to communicate and negotiate services with information apparatus 100. In one implementation, an information apparatus 100 may communicate with an output controller 120 connected to a printer or an output controller 120 internally installed within a printer to obtain device dependent data or software components such as device specific printer driver. An application such as an output manager 308 residing in the information apparatus 100 may install and configure the uploaded components or data, allowing information apparatus 100 to print to that printer directly. An example of an output process is described below with reference to
Functionalities and feature sets of output controller 120 may include one or more of the following:
Provide service to clients—Output controller 120 may actively search for available clients, including information apparatus 100 or output manager 308 or other communication units, to which clients' output service could be provided. Alternatively or in combination, an output controller 120 may passively wait to be discovered by one or more clients, including information apparatus 100, to provide output service to the client or clients.
Negotiation of services with information apparatus 100—Output controller 120 may communicate and exchange information with information apparatus 100 as part of negotiating the output services to be provided. As an example, in communication with an information apparatus 100, an output controller 120 may inform the information apparatus 100 of the make, model, identification, version, type of input language, type of device driver software, type of services provided, type of components available for upload, etc. for a selected output device 140 such as a printer. As another example, an information apparatus 100 may send one or more messages to an output controller 120 inquiring about what software component or data, if any, the information apparatus 100 needs to upload from the output controller 120 to enable output to a specific output device 140.
Provide security functionalities such as authentication and encryption—Authentication is used to prevent unwanted access to services, while encryption is used to prevent eavesdropping. Security procedures may be implemented by software, hardware or a combination of both, in various steps and stages of communication between the output controller 120 or the output device 140 and the information apparatus 100.
Payment or transaction management and services—A user may be charged a service fee when, for example, providing output to a printer 140 or other output device 140. Output controller 120 may have the ability to calculate and process payment according to the services requested by or rendered to a client. Output controller 120 may process payments in various forms such as cash, E-cash, credit card, debit card, E-card, smart card, virtual cash, etc.
Storage capability—Output controller 120 may include a memory or storage unit and may store within it one or more of the following: application software, device or printer driver, software components, device dependent data or parameters, user interfaces, etc. Software components or data stored in the output device 140 or the output controller 120 may be uploaded to the information apparatus 100 in order for the information apparatus 100 or the output manager 308 to drive the output device 140. Software components may be executable or partially executable programs or data.
Synchronize with information apparatus 100—After output controller 120 or the output manager 308 in information apparatus 100 identifies the components (software component, data, information or parameters) necessary to enable output or printing, the output controller 120 may coordinate with the output manager 308 to upload to the information apparatus 100 the components stored in a memory or storage unit of output controller 120.
Provide management tools—Multiple information apparatuses 100 may request service from the same output device 140 at the same time or at overlapping times. Management tools such as queuing and spooling of print jobs, quality of service, etc. may be provided by the output controller 120.
As indicated above, output controller 120 may be implemented in a variety of ways and may include hardware, software, or a combination of the two. In hardware implementations, for example, output controller 120 may include components using one or more of hardware types such as ASIC, DSP, FPGA, firmware, system on a chip, and communication chip set. Output controller 120 may also include embedded processors with software components or embedded application software to implement its feature sets, and functionalities. An output controller 120 may or may not contain an operating system.
Output controller 120 typically includes a memory or storage unit (ROM, RAM, flash memory, disk drive—not shown), which may store one or more software applications, software components and data. Some software applications may run in the output controller 120 to perform its functionalities (e.g., communicate with information apparatus 100).
The memory or storage unit of an output controller 120 may also store data and one or more software components that may be available to be uploaded to or synchronized with an information apparatus 100 during communication with output manager 308. A software component may be a device driver or complete application software that can run on the information apparatus 100. Once such a software component is uploaded and installed, the information apparatus 100 can drive or output to that specific output device 140.
A software component may also be a partial device driver or partial application software or partial software component. A software component may be an executable or partially executable program, object or code. Software components may encapsulate information, algorithms, and data. Examples (of algorithms that may be included in the software components include compression/decompression methods, file conversion, graphics representation and rendering, image processing and enhancement operations, color space transformation and data conversion, encoding/decoding techniques, color matching and management methods, image transformation, interpolation methods halftoning techniques, user interface software codes etc. Examples of data that may be included in software components include, for example, a color table, color space information, halftoning tables, output device type, output resolution, bit depth, input type, format or language, communication protocol type, output status, device identification and signature, graphics, image and text descriptions etc.
Such software components may be uploaded to output manager 308 to facilitate communication and generation of print data or output data suitable, compatible or optimized for the output controller 120 or the output device 140. The output controller 120 and output manager 308 manage and negotiate the proper components to be uploaded to the information apparatus 100.
Not all situations require uploading an entire or complete driver or application to output manager 308 or information apparatus 100. In some implementations uploading only a software component may be sufficient. For example, there are many inkjet printers that commonly use one-bit or multi-bit CMYK printing technology, and sometimes have similar resolutions. An information apparatus 100 may pre-install a more generic printer driver, where this printer driver contains the device independent portion of the software code, algorithms, and data that is common or can be used for this entire class of printers. Device-independent code may include, for example, a rasterization process (including half-toning and color management methods) and image enhancement of the digital document that is suitable for use with this entire class of printers. In this example, it is feasible to upload only a smaller software component or data that includes the device-dependent components for a particular printer or output device 140. The device-dependent portion or component or data may include, but is not limited to, color tables, halftoning tables, output resolution, bit depth, compression/decompression methods, color space conversion, encoding algorithms or conversion software that is specific to that printer or output device 140.
Another example of a software component stored in the memory unit of an output controller 120 for uploading to an information apparatus 100 is an installation wizard or a user interface to capture a user's preferences for printing or output operation. Examples of user preferences in the case of printing may include, without limitation, color and print quality parameter adjustments, number of copies, number of cards per page, number of pages per sheet, duplex, portrait or landscape, security information, etc.
Once the software components or data are uploaded or installed in information apparatus 100, the information apparatus 100 can drive or output to the output device 140. For example, an application 302 in the information apparatus 100 can print a digital document or image to a printer.
Different information apparatuses 100 may require different software components to be uploaded in order to drive a specific output device 140. Accordingly, a variety of software components and data or device drivers for a plurality of information apparatuses 100, operating systems, and platform types may be stored in the memory or storage components of an output controller 120.
Output controller 120 may contain an embedded operating system to manage its applications. With an operating system, some or all functionalities and feature sets of the output controller 120 may be implemented as application software. Additional application software may be installed or upgraded to newer versions in order to, for example, provide additional functionalities or bug fixes.
Output controller 120 may contain a user interface that allows a user to configure and manage the functions provided by the output controller 120. The user interface of the output controller 120 maybe accomplished by, for example, using display screens, soft keys, pushbuttons, mouse, stylus and keypads to allow users to interact with and manage the functions provided by the output controller 120. Examples of such functions may include any or all of an on-off power switch, status display or indicator, cancel current job, or reorder existing jobs, etc.
Output controller 120 typically also includes a communication or adapter unit, which allows output controller 120 to communicate with other devices including information apparatus 100 through wired or wireless connections. Exemplary configurations of wireless adapter or communication unit are described below with reference to
When output controller 120 is implemented as firmware, or an embedded application, the configuration and management of the functionalities of output controller 120 may be optionally accomplished by, for example, using controller management software in a host computer (not shown). 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 140 or controller 120. Communication between the host computer and output controller 120 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 120. Furthermore, a host computer configuration application may download or install application software, software components or data in the output controller 120 for the purpose of upgrading, updating, and or modifying the features and capabilities of the output controller 120.
Output device 140 in one implementation includes or is connected to output controller 120 described above. Therefore, functionalities and feature sets provided by output controller 120 are automatically included as part of the functionalities of output device 140. The output device 140 may, however, implement or include other controllers or applications that provide at least partially the features and functionalities of the output controller 120.
Therefore, the output device 140 may include some or all of the functionalities and feature sets provided by the output controller 120.
Output Device 140
Output device 140 is an electronic system capable of outputting digital content regardless of whether the output medium is a substrate (e.g., paper), a display image, a projection, or sound. A typical example of output device 140 may be a printer, which outputs digital documents containing text, graphics, images or any combination onto a substrate. Output device 140 may also be a display device capable of displaying still images or video, such as, without limitation, televisions, monitors, and projectors. Output device 140 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 140. A printer (including a fax machine, copier, etc.) is frequently referred to herein as the exemplary output device 140. However, it should be recognized that the present invention applies as well to output devices 140 other than printers.
Marking engine 906 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.
Marking engine 906 and memory buffer 904 of a printer 900 form its printer engine 908, which may also include additional circuitry and components, such as firmware, software and or chips or chipsets for decoding and signal conversion etc. (not shown). Input to a printer engine 908 is usually a final rasterized print data generated by the raster image processor 902. Such input is usually device dependent and printer specific. The printer engine 908 may take this device dependent input and generate output pages.
Raster image processor (RIP) 902 may be located within the printing device itself (as shown in
When a RIP 902 is located inside an output device 140, the RIP 902 is usually included in a printer controller 910 that may, for example, interpret, convert and/or rasterize input print data into a final format, language or instructions that printer engine 908 can understand. A laser printer with a faster printing speed is an example that falls in this category. For example, a PostScript printer controller 910 may contain a postscript interpreter (not shown) and a raster image processor 902 (RIP). Postscript interpreter interpret the postscript language and the raster image processor 902 may process the digital document and converting it to a printer specific format, language or instructions that can be accepted by the printer engine 908. In this example, a device-dependent printer driver (e.g., a Postscript driver, not shown) may be needed in the information apparatus 100 to convert digital document from its original format into print data (e.g. in PostScript) that is acceptable to the printer controller 910.
Another example of page description language is PCL (Printer Command Language) from HP (Hewlett Packard). In the same way as postscript, a printer equipped with PCL printer controller 910 can take PCL as input. Information apparatus 100 usually needs to have PCL printer driver in order to drive or print to a printer equipped with a PCL controller.
Although the illustrations above use PostScript and PCL as examples, a variety of other page description languages, markup languages, image formats, graphics formats, and file formats may also be used as input print data 920 to a printer 900 or output device 140. Examples of possible inputs other than PostScript and PCL may include without limitation, EMF, XML, HTML, among many others. Some printer manufacturers may also use 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 920. Print data 920 sent to printers with printer controllers 910 are usually intermediate descriptions of a digital document that may require further interpretation, processing and/or conversion before it can be send a printer engine for output. A printer controller 910 may interpret and process the input intermediate print data information into the final format that can be understood by the printer engine 908. Regardless of the type of print data 920, users usually have to pre-install a device-specific driver in their information apparatus 100 in order to output the proper language, format, or file that can be accepted by a specific printer 140.
Some output devices 900B do not have a printer controller 910 as shown in
In present invention, for the printer 900B, RIP can be integrated within the output manager 308 or application software 302 in the information apparatus 100. Alternatively, RIP may also be integrated as a part or a function of any one of output controllers as shown in configurations 120D, 120E, and 120F.
The output controller 120 may be connected externally to an output device 140 or integrated internally into the output device 140. If an output device 140 such as a printer already includes a printer controller 910, the output controller 120 may be implemented serially or cascaded with the printer controller 910 as two separate controllers. Alternatively, output controller 120 can be integrated with a printer controller to become a “combined controller” 120C. A combined controller (e.g., 120 C or 120 F) has functionalities of both printer controller 910 (e.g., input interpretation and or raster image processing) and output controller 120 of the present invention. Other configurations and implementations of output controller 120 and printer controller 910 are also possible. The various possible configurations and implementations of output controller are described below with reference to
Communication Unit
Communication links 150 and 160 between information apparatus 100 with an output controller 120, whether externally connected and or internally integrated, may be variously implemented. In one implementation, information apparatus 100 communicates with output controller 120 through wireless connections such as infrared or radio links. Examples of wireless connections technology include without limitation IrDA, home RF, Bluetooth, IEEE 802.11, HiperLan2, among others. However, wired connections such as serial interfaces, parallel interfaces, USB interfaces, Fire Wire (IEEE 1394), Ethernet and token ring network among others may also be implemented in the present invention. Adapter pairs may be incorporated into each communicating node (e.g., information apparatus 100 and output controller 120) to conduct communications by performing signal conversions.
In the case that output controller 120 is installed as an external component or “box” (as shown 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 120, output device 140, 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, including a group of competing technologies operating in the 2.4 GHz unlicensed frequency band. This group currently includes Bluetooth, Home radio frequency (Home RF) and implementations based on the 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 to transmit data between different devices without limitation and therefore in no way depart from the scope of present invention.
Among the current available wireless technologies, Bluetooth requires 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). One device (master) in each piconet 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.
Different Output Manager Configurations and Processes
As shown in
It should be recognized that the three software applications 302(1)-302(3) illustrated in
Instead of integrating the output manager 308 into application software 302, an alternative implementation is shown in
The communication and exchange of information between output manager 308 and other software applications 302 can be accomplished by one or more of many available techniques, such as passing, transferring or exchanging objects, messages, procedural calls, files, metafiles, etc. Some of these techniques may be facilitated by a set of APIs or object models provided by the application software 302 or output manager 308 or the operating system. The exact technique may depend for example on the type of application, platform, language, and developer preference etc. This may be easily implemented and recognized by an average software engineer skilled in the art.
The above are merely exemplary implementations of output manager 308. Due to the diversity of feature sets and capabilities of operating systems, other implementations of output manager 308 are also possible. As an example, some operating systems may provide partial APIs or object models to support limited output capability. In this case, software applications 302 may rely on the limited output capacity to interact with device management applications, or the software applications 302 can implement or incorporate partially other desired output features of the output manager 308 using the configurations or combination of configuration illustrated in
Different Output Controller Configurations and Processes
Some printers do not include a raster image processor or printer controller 910, as illustrated in
The above are exemplary implementations of output controller 120, but other implementations are also possible. For example, partial functionalities of output controller 120 may be implemented in an external “box” while the remaining functionalities may reside within an output device 140 as a separate circuit board or integrated with a printer controller. As another example, the functionalities of output controller 120 may be implemented into a plurality of external boxes connected to the same output device 140. As a further example, the same output controller 120 may be connected to and service multiple output devices 140.
Step 500 indicates that a user initiates output from an information apparatus 100. For example, a user may want to print or otherwise output an email, receipt, confirmation, map, photo, graphics, web page, one or more slides of a PowerPoint®-brand presentation, or any other document or digital content from an information apparatus 100. The output may be initiated by various means, such as by using a soft key, push button, keyboard, keypad, mouse, stylus, software GUI, command or voice activated command, etc. An exemplary user interface with which a user may initiate such a process from an information apparatus 100 is described below with reference to
Step 502 references a discovery process in which, for example, information apparatus 100 searches for available output devices 140, including display devices, printers, copiers or fax machines among others (collectively refer to as “printers” here for simplicity of discussion), that can perform a requested output or print job. The output manager 308 residing in the information apparatus 100 may participate in, coordinate and manage the discovery process 502. As part of discovery process 502, information apparatus 100 may communicate via a wired or wireless connection with output controllers 120 that are connected to or included in output devices 140.
In some situations, the discovery process 502, or part of it, may be skipped. For example, discovery process 502 may be skipped if a user already knows the output device or printer to which output is to be directed. As another example, a user may set a frequently used printer as a preferred default printer so that discovery process 502 may be partly skipped if the default printer is found to be available. Other examples in which discovery process 502 may be optional or partly skipped involve direct wire line connections or infrared communications. In these cases, a user may directly connect or physically point an information apparatus 100 to a specific output device 140 so that it could be sufficient only to check the connection and establish communication between the devices.
Discovery process 502 may operate in a variety of scenarios. In one scenario, information apparatus 100 broadcasts a service request, for example printing, through wired or wireless signals. Service devices, such as output device 140 equipped with output controller 120, “listen to” such signals, “read” the request, “see” whether they can provide requested service, and respond if they can provide the requested service. Alternatively or in combination, all service devices can periodically or continuously announce or advertise the services they provide. Information apparatus 100 “listens to” such announcements and identifies the service it needs. In a third scenario, service devices of the same network (e.g., LAN) register their services with a control point. A control point is a computing system (e.g. a server, controller) that maintains records on all service devices within the same network. Information apparatus 100 may contact the control point to search for the service it needs.
Various protocols may be implemented in the discovery process 502. Wireless communication protocols are preferred. Wired communication, on the other hand, may also be implemented. Examples of applicable protocols may include, without limitation, Bluetooth, HAVi, Jini, Salutation, Service Location Protocol, and Universal Plug-and-play, among others. Other proprietary protocols or combinations may also be implemented in the discovery process.
In the discovery process 502, information apparatus 100 may or may not find an output device 140 available to accept its print or output job. Exemplary factors that may impact the availability of output devices 140 may include, without limitation, the following:
Physical distance—Some wireless communication links may impose limitations on physical distance between communicating devices. The restrictions on physical distance may vary among different wireless communication technologies. Wired communication, on the other hand, is also subject to the availability and length of cable or other wired lines.
Compatibility—The output process with reference to
Security authentication—Security authentication may be implemented in various steps of communication, including the discovery step 502. Security authentication may be required for example when an output service is restricted to a certain group of users or information apparatuses. When a user requests service, output device 140 or output controller 120 may process an authentication step by automatically detecting the identification or other information provided by the user, output manager 308 or information apparatus 100. As a result of such an authentication process, the information apparatus 100 of a particular user may not be able to discover an available output device 140 because access is not authorized for the user or the apparatus.
User specified search criteria—The user may specify certain search criteria for discovery process 502, such as output device model, quality of service provided, range or price of service charge, etc. Output devices 140 not satisfying user criteria or a default profile may not be shown to the user.
Step 506 indicates that the user is notified if no available output device 140 is found in the discovery process 502. The user may be notified by an application such as the output manager 308 through a user interface of the information apparatus 100. The information apparatus 100 may also provide more detailed information such as the reasons why the requested service is not available. Examples of possible reasons may include, among others: no output device within limited physical distance, no compatible hardware or software components, technical difficulties, security authentication not satisfied, no subscription to the service, search criteria not met, etc.
Step 508 indicates that alternatives are provided when a requested service is not available at the current moment. The user may be provided with alternatives such as canceling the service request, trying again, or being notified when the requested service is available or the requested output device 140 is identified or becomes available. As an example, the user's information apparatus 100 may not detect any available output devices 140 in the current wired/wireless network. The print requests are then queued or registered within the information apparatus 100. When the user enters a new network having available printers, or when new compatible printers are added to the current network or when a printer becomes available for any reason, the user would be notified of such availability through the information apparatus 100. The user may then output the print job to the newly detected or now available printer with, for example, a mere click of a button. This detection and notification function may be implemented by a software program or as a feature of the output manager 308. This feature may also be implemented in hardware or combination of hardware and software residing in the information apparatus 100.
Step 514 indicates that service negotiation is performed, such as when one or more available printers are discovered in the discovery process 502. In service negotiation process 514, information apparatus 100 exchanges information with output controllers 120 connected to or installed in the available output devices 140. The output manager 308 may participate in, coordinate or manage negotiation process 514 with output controller 120. Information being exchanged may include, for example, the following:
Type, make and model of each available output device 140, including information about the printer engine, its technology and specifications of the output device.
Type and parameters of the output device 140 such as font or international character code supported, paper size, resolution, bit depth, color space, number of colors supported, color or grayscale etc.
Type of service and quality of service provided by each available output device 140.
Conditions under which the services are provided (e.g., service charge, subscription charge) and whether, for example, transaction and service charges are satisfied.
Whether the usage or service of each output device 140 is restricted to certain groups, in which case the user may have to provide authentication information to be identified as member of such a group before use of that device is allowed.
Type, make and model (including operating system) of the information apparatus 100.
The type of input format, encoding, language, data, color space, and or compression that the output controller 120 or other device may take as input, for example, PostScript, PCL, RTL, XML, etc.
The type of component or data that may need to be uploaded from output controller 120 to information apparatus 100 so as to enable output to a specific output device.
The information being exchanged may be entered manually by the user or may be automatically detected and or synchronized between the information apparatus 100 and the output controller 120 or it may be partially assisted by the user or partially automated. Some or all of the information being exchanged may be provided to the user through a user interface in the information apparatus 100. The user may monitor the status or approve certain transactions. One embodiment of the service negotiation process 514 is described below with reference to
Step 516 indicates that a synchronization process is performed once an output device 140 has been identified and selected. Before synchronization process 516 begins, the information apparatus 100 may communicate with the output controller or controllers 120 of the selected output device or devices 140 to identify what components, if any, need to be uploaded to the information apparatus 100 to enable printing or other output. This communication between information apparatus 100 and output controller or controllers 120 may not be necessary if adequate information has been obtained in the discovery process 502 and or service negotiation process 514. Synchronization process 516 may be optional or it may be partially skipped if the necessary components (e.g., identified in the service negotiation step 514) already exist in information apparatus 100.
After they have been identified, the necessary components or parts of components or data may be uploaded to the information apparatus 100 from output controller 120. Examples of possible components may include, without limitation, one or more of the following: data, device driver, printer driver, application software, software components, metafiles, user interface etc. The output manager 308 may participate in, coordinate or manage the synchronization process 516. Encryption techniques may be implemented in the synchronization process 516 to prevent eavesdropping.
The newly uploaded components may be incorporated into the output manager 308 residing in the user's information apparatus 100. Alternatively or in combination, the newly uploaded components may be installed into the information apparatus 100 as a separate application or as part of the output manager 308. The process of uploading and installing may be done automatically or manually by the user, or a combination of the two.
Part or all of synchronization process 516 may be skipped in some instances. For example, the information apparatus 100 may already include all the software components and data or drivers necessary for output to the selected output device or devices 140. This may be due to the components having been uploaded from a previous synchronization process 516 and left undeleted, or alternatively the user may have preinstalled all the necessary components for output in the information apparatus 100. In these cases, no software components are being uploaded and the user may be notified of this status for possible override of synchronization process 516. Alternatively synchronization process 516 may be automatically skipped transparently to the user.
Step 518 indicates that print or output job processing is performed. In this step 518, the print request or print job is processed and digital content or document may be converted to the final format to send to the output device 140 for output. At the beginning of this step 518, the user may be provided with options to select or change or input printing or output preferences such as page layout, number of copies, color/grayscale, print quality parameters, etc. These options may include or offer pre-configured user preferences or factory defaults. Some options, parameters and preferences may be device-dependent while others may be device-independent. For example, device dependent parameters and preferences may be presented after having synchronized or uploaded device dependent components or information from the output controller 120. Device independent parameters and preferences may also be uploaded and synchronized like the device dependent parameters and preferences or may be pre-installed as part of the output manager 308 prior to the synchronization and uploading of information.
With reference to
Step 520 indicates that the printer engine or display engine 908 generates a final output. In this step 520, the processing result of step 518 is sent to a printer engine or display engine 908 of an output device 140 to generate final output on a substrate, for example. Memory buffers may be needed to temporarily store print data before output. Firmware, DSP, ASIC, FPGA, system-on-a-chip, software, or a combination, may be used or involved to convert digital data into signals suitable for the printer engine or display engine 908.
After a print job or output job has been successfully printed or displayed, the user may be provided a choice (not shown) to delete the components that have been uploaded to the information apparatus 100 during the synchronization process 516. This optional feature may be useful when the information apparatus 100 has limited storage space. One implementation of this optional feature is to provide a setting in the output manager 308 in which the user has a choice to (1) always keep the uploaded data or components; or (2) always automatically delete the uploaded data or components upon completion of the print job, or upon exit of the application, or upon shutting down of the information apparatus or upon elapse of certain amount of time; or (3) always ask the user whether to delete or keep the uploaded component or data.
The above description illustrates an exemplary embodiment of output process 501. A printer is referred to as output device 140 in the above illustration, however, it should be recognized that output process 501 could be easily applied to other output devices 140 such as fax machines, digital copiers, display screens, TVs, monitors, projectors, voice output devices etc.
A pervasive output process implementing fewer or additional steps may also be possible. For example step 502, the discovery process, may be skipped if the user already knows which printer or printers are to output the content. As another example, a payment-processing step may be added to the above-described output process 501 if the printing service is provided for a fee. Output controller 120, in this case, may provide services such as calculating payment amount or collecting payments in a variety of possible forms, for example, credit card, bank card, cash, E-cash, smart card, among others. The payment information (e.g., credit card number or other credit identification or payment) may be stored in the information apparatus 100 and released to the output controller 120 at the user's choice. Adding additional processes or skipping one or more steps in output process 501 does not, however, depart from the spirit and scope of present invention.
(1) The user may be provided with information on the available output devices 140.
(2) The user may select a desired output service according to the information provided.
The output manager 308 residing in the information apparatus 100 may participate in, coordinate and manage the service negotiation process 514, together with the output controller 120.
In step 600, the user may be provided at information apparatus 100 with information on some or all available output devices 140 identified in the discovery process 502. Information being provided here may include one or more of the following:
Total number of available output devices discovered.
Model and make of each available output device.
Type and capability of the output device.
Type of service and quality of service provided by each available output device.
Conditions under which the services are provided. For example, if service charge or subscription fee is required and the acceptable payment method.
Whether the use of each output device is restricted to certain groups.
The components or information, if any, need to be uploaded to the information apparatus to enable output to the selected output devices.
Information collected during discovery process 502 may be provided to the user through a user interface on the information apparatus 100, such as a GUI or voice or another interface.
In step 602, based on some or all of the information provided, the user may choose one or more output devices to take the print request or print job. On the other hand, the user may choose to decline the output service offered, and choose not to output the document or content to any of those devices. In this case, alternatives may be provided to the user as previously described with reference to step 508 (
Authentication step 604 is optional, but may be necessary if, for example, the use of an output device 140 is restricted to a group of users. In this case, the user may have to provide authentication information to identify him/herself as part of the authorized group to use the service. Examples of authentication methods may include a user's name, password, personal identification number (PIN), ID number, signatures, security keys (physical or digital), biometric, fingerprint, voice, etc. ID number or IP address of the information apparatus 100 may also be used as authentication information. Such authentication information may be provided by the user manually or detected automatically by the output controller 120 or output device 140.
It should be recognized that
In step 700, output manager 308 processes an input digital document or content 701 and converts it to print data 703 that can be transmitted to output controller 120, combined controller (120C, 120F) or directly to printer engine 908. Rasterization, interpretation, encoding, decoding, etc. may take place in this step. In one implementation, print data 703 may utilize an intermediate format or language to facilitate the transmission of the digital document or content 701 to the output controller 120. This intermediate format or language may be a predefined input format or language that the output controller 120 can understand. It is also possible in this step 700 that the output manager 308 simply passes the digital document 701 in its original format to the output controller 120 with little processing. In still another exemplary implementation, the output manager 308 may process (e.g. raster image process) the digital content or document 701 into a final print data or output data format compatible to the input requirements of the output device 140. Encryption techniques may be used to assure the security of communication between information apparatus 100 and output devices 140.
As indicated above, output data or print data (in case of a printer) 703 generated by step 700 may be in various formats. In one embodiment, the print data 703 may be in a final format suitable for sending directly to the printer engine. In this case, the output controller 120 does little or no processing. One exemplary use of this configuration can be implemented in a low cost inkjet printer that does not have a printer controller. In this example, the print data 703 may be in a compressed 1 bit or more CMYK data format that can be sent directly to the printer engine 908 for final output as shown in step 702. Or print data 703 can be sent to the output controller 120 for possible optional features such as buffering, queuing, and print job management as shown in step 704.
In another embodiment, output manager 308 may generate print data 703 in an intermediate format, language, or instruction that requires further processing. Examples of such format, language or instruction may include, without limitations, Page description languages (e.g. PostScript, PCL), metafiles (e.g. EMF), markup languages (e.g. XML, HTML), image or graphics formats (TIFF, GIF, PNG, JPEG compressed), among others. The intermediate format may also include proprietary solutions in page description languages, markup languages, metafiles, image and graphics formats, encoding and decoding, compression and decompression. The above-mentioned intermediate formats may be used independently, or in combinations.
As described above with reference to
As shown in step 702, the print data 703 is sent directly to the printer or display engine 908 for final output with little or no further processing from output controller 120 or a printer controller 910. In this case, the print data or output data 703 is preferably to be in a final format or language that can be understood by the printer or display engine 908 that is part of the selected output devices or devices 140.
Alternatively, as shown in step 704, print data 703 is sent to an output controller 120 connected to or installed within a selected printer or output device 140. In one embodiment, the print data 703 may be in a final format or language that can be understood and processed by the printer or display engine 908. In this case, the output controller may buffer the input print data 703 before passing it to the printer or display engine 908 with little or no further processing. In another embodiment, print data 703 maybe in an intermediate format or language not understood by the printer 900 or output engine 908. Therefore, the output controller 120 may process the print data and convert it into a final format, language or instruction that can be sent to the printer engine (or other output engine, in the case of other type of output device).
Regardless of the format of input print data 703, the output controller 120 may perform additional management functions such as payment processing, service verification, authentication, print job management, queuing, spooling, quality of service among others.
As illustrated in step 706 and 708, the print data 703 may be processed by both output controller 120 (in step 706) and printer controller 910 (in step 708) separately before being sent to the printer engine 908 for final output. For example, some printers, such as high-speed laser printers, already include a printer controller 910 that has the capability of processing certain types of input such as PostScript, PCL, and XML, among others. In this case, the output controller 120 may process or convert the print data 703 into the input 707 required by the printer controller 910. Alternatively, in a different implementation, if the print data 703 is already in one of the formats or languages that are compatible and can be understood by the printer controller 910, the output controller 120 may simply buffer the print data 703 and sent it directly to the printer controller 910 as needed with little or no processing. In step 708, the printer controller 910 may perform functions such as interpretation, decoding, and raster image processing operations on the input print data 707 (such as a page description language) if such operations were not already performed by output controller 120 or by output manager 308. The processed result of the printer controller 910 may be sent to the printer engine 908 for final output.
As illustrated in step 710, a single combined controller 120F, 120C (as illustrated in
Similarly, other than processing print data, the output controller 120 and the combined controller (120C, 120F) may perform functions such as payment processing (if service charge applies); print job management, queuing, spooling, etc.
Referring to
As the user selects “Print” function control 802, the output process described with reference to
Assume in this example that three printers are found available as the result of discovery process step 502. In
If a printer is restricted to be used by a certain group, the user may be required to provide identification information before being able to select this printer. For example, to use a printer placed in the hallway of a company office building, a user may have to identify himself or herself as an employee of such company. Password, personal identification number or I.D. number of the information apparatus 100 may be required for authorization purposes. The identification information may be provided by the user manually or detected by the output controller 120 or output device 140 automatically. If the printer provides fee-based service, certain payment process steps may be required additionally, which are not shown in the figures for simplicity.
After the user has successfully selected the desired output device or devices in the service negotiation process 514, the information apparatus 100 may communicate with output controller 120 to identify data or software components, if any, which need to be uploaded to the information apparatus 100 to enable printing. The output manager 308 residing in the information apparatus 100 may participate in, coordinate and manage the communications between applications in the information apparatus 100 and the output controller 120.
In this particular example, as illustrated in
The above description gives an example of a printer driver component that may need to be uploaded. Other components and combinations may also be possible; this may include for example a partial print driver, data, software components, or a user interface. A partial print driver or component may for example include only device dependent software components and data specific to an output device. Device independent code and data of the device driver may have been previously installed in the information apparatus 100 and therefore need not be uploaded. It is also possible that no components need to be uploaded because all the components needed for printing to the selected output device 140 may already reside in the information apparatus 100. Assuming in this example that the user agrees to upload the driver,
When the synchronization process 516 is completed, screen 840 is displayed to the user as shown in
Steps 518 and 520 can proceed after the user finishes selecting any preferences. The user, after selecting the confirmation control or “OK” button 844 shown in
After the print job has been successfully finished, the user may be provided with an option to keep or delete the printer driver or software components or synchronized device dependent data, which was uploaded to information apparatus 100 in the earlier steps. This option may be beneficial to those mobile information apparatuses 100 with limited memory space or a casual user of that particular output device 140. A user who frequently uses a selected printer may wish to keep the printer driver, software components, or data installed so that synchronization for uploading components may be skipped when the printer is used again.
Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their legal equivalents.
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/229,896 filed Dec. 21, 2018, 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. 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, and 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 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 et al. | Feb 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 |
| 5574979 | West | 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 |
| 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 et al. | 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 |
| 5710557 | Schuette | Jan 1998 | A |
| 5717688 | Belanger et al. | Feb 1998 | A |
| 5717742 | Hyde-Thomson | Feb 1998 | A |
| 5724106 | Autry et al. | 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 |
| 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 |
| 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 |
| 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 |
| 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 et al. | Nov 1999 | A |
| 6003065 | Yan et al. | Dec 1999 | A |
| 6006265 | Rangan et al. | 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 |
| 6041346 | Chen et al. | Mar 2000 | A |
| 6043898 | Jacobs | Mar 2000 | A |
| 6046820 | Konishi | Apr 2000 | A |
| 6061142 | Shim | May 2000 | A |
| 6069707 | Pekelman | May 2000 | A |
| 6070185 | Anupam et al. | May 2000 | A |
| 6072595 | Yoshiura et al. | Jun 2000 | A |
| 6076076 | Gotffreid | 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 |
| 6122526 | Parulski et al. | Sep 2000 | A |
| 6138178 | Watanabe | Oct 2000 | A |
| 6141659 | Barker et al. | Oct 2000 | A |
| 6144997 | Lamming et al. | Nov 2000 | A |
| 6145031 | Mastie et al. | Nov 2000 | A |
| 6148346 | Hanson | Nov 2000 | A |
| 6167514 | Matsui et al. | Dec 2000 | A |
| 6173407 | Yoon et al. | Jan 2001 | B1 |
| 6175922 | Wang | Jan 2001 | B1 |
| 6177926 | Kunert | Jan 2001 | B1 |
| 6184996 | Gase | Feb 2001 | B1 |
| 6189148 | Clark et al. | 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 et al. | 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 |
| 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 |
| 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 |
| 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 | Oct 2002 | B1 |
| 6473070 | Mishra et al. | 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 |
| 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 | Nagaska | Feb 2003 | B1 |
| 6526129 | Beaton et al. | Feb 2003 | B1 |
| 6529522 | Ito 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 |
| 6545722 | Schultheiss et al. | 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 |
| 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 et al. | Jul 2003 | B1 |
| 6598031 | Ice | Jul 2003 | B1 |
| 6600569 | Osada | Jul 2003 | B1 |
| 6601108 | Marmor | Jul 2003 | B1 |
| 6604135 | Rogers 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 |
| 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 |
| 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 |
| 6670982 | Clough et al. | Dec 2003 | B2 |
| 6671068 | Chang | Dec 2003 | B1 |
| 6678004 | Schultheiss et al. | 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 | Lintel et al. | Apr 2004 | B1 |
| 6735616 | Thompson 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 |
| 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 |
| 6798530 | Buckley et al. | Sep 2004 | B1 |
| 6801692 | Nishimura et al. | Oct 2004 | B2 |
| 6801962 | Taniguchi et al. | Oct 2004 | B2 |
| 6813039 | Silverbrook et al. | Nov 2004 | B1 |
| 6816274 | Silverbrook et al. | Nov 2004 | B1 |
| 6816724 | Asikainen | Nov 2004 | B1 |
| 6819919 | Tanaka | Nov 2004 | B1 |
| 6826632 | Wugofski | Nov 2004 | B1 |
| 6839623 | Tillgren et al. | Jan 2005 | B1 |
| 6839775 | Kao et al. | Jan 2005 | B1 |
| 6840441 | Monaghan et al. | Jan 2005 | B2 |
| 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 et al. | Feb 2005 | B2 |
| 6859228 | Chang | Feb 2005 | B1 |
| 6859937 | Narayan et al. | Feb 2005 | B1 |
| 6873836 | Sorrells | Mar 2005 | B1 |
| 6882859 | Rao et al. | Apr 2005 | B1 |
| 6885878 | Borgstrom et al. | Apr 2005 | B1 |
| 6889385 | Rakib 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 |
| 6914694 | Ichikawa et al. | Jul 2005 | B1 |
| 6915124 | Kiessling et al. | Jul 2005 | B1 |
| 6915422 | Nakamura | Jul 2005 | B1 |
| 6922258 | Pineau | Jul 2005 | B2 |
| 6930709 | Creamer et al. | Aug 2005 | B1 |
| 6941014 | Lin et al. | Sep 2005 | B2 |
| 6947067 | Halttunen | Sep 2005 | B2 |
| 6947995 | Chang et al. | Sep 2005 | B2 |
| 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 |
| 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 |
| 7058356 | Slotznick | Jun 2006 | B2 |
| 7062651 | Lapstun et al. | Jun 2006 | B1 |
| 7068621 | Bouet | Jun 2006 | B2 |
| 7076534 | Cleron et al. | Jul 2006 | B1 |
| 7076730 | Baker | Jul 2006 | B1 |
| 7088691 | Fujita | Aug 2006 | B2 |
| 7088990 | Isomursu et al. | Aug 2006 | B1 |
| 7095854 | Ginter et al. | Aug 2006 | B1 |
| 7099304 | Liu et al. | Aug 2006 | B2 |
| 7103834 | Humpleman | Sep 2006 | B1 |
| 7113979 | Smith et al. | Sep 2006 | B1 |
| 7133845 | Ginter et al. | Nov 2006 | B1 |
| 7133846 | Ginter et al. | Nov 2006 | B1 |
| 7143356 | Shafrir et al. | Nov 2006 | B1 |
| 7149726 | Lingle et al. | Dec 2006 | B1 |
| 7155163 | Cannon et al. | Dec 2006 | B2 |
| 7164885 | Jonsson et al. | Jan 2007 | B2 |
| 7170857 | Stephens | Jan 2007 | B2 |
| 7178718 | Silverbrook et al. | Feb 2007 | B2 |
| 7180614 | Senoo et al. | Feb 2007 | B1 |
| 7184707 | Tada | 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 |
| 7209955 | Major et al. | Apr 2007 | B1 |
| 7213061 | Hite et al. | May 2007 | B1 |
| 7221961 | Fukomoto 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 | Aug 2007 | B1 |
| 7263270 | Lapstun et al. | Aug 2007 | B1 |
| 7272788 | Anderson et al. | Sep 2007 | B2 |
| 7287089 | Lamoureux et al. | Oct 2007 | B1 |
| 7289792 | Turunen | Oct 2007 | B1 |
| 7289964 | Bowman-Amuah | Oct 2007 | B1 |
| 7318086 | Chang et al. | Jan 2008 | B2 |
| 7327481 | Such | 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 |
| 7355730 | Landau et al. | 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 |
| 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 | Jan 2009 | B1 |
| 7511630 | Strickland et al. | Mar 2009 | B2 |
| 7533344 | Motoyama et al. | May 2009 | B1 |
| 7554684 | Senoo et al. | Jun 2009 | B1 |
| 7555287 | Heinonen | Jun 2009 | B1 |
| 7571142 | Flitcroft et al. | Aug 2009 | B1 |
| 7574723 | Putterman | Aug 2009 | B2 |
| RE40910 | Aoki et al. | Sep 2009 | E |
| 7584269 | Moore | Sep 2009 | B2 |
| 7587196 | Hansen | Sep 2009 | B2 |
| 7593123 | Sugahara | Sep 2009 | B2 |
| 7609402 | Chang et al. | Oct 2009 | B2 |
| 7616600 | Sparr | Nov 2009 | B2 |
| 7644039 | Magee et al. | Jan 2010 | B1 |
| 7650145 | Ukita et al. | Jan 2010 | B2 |
| 7660460 | Wu et al. | Feb 2010 | B2 |
| 7660601 | Janik et al. | Feb 2010 | B2 |
| 7697467 | Kubler et al. | Apr 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 | Oct 2010 | B2 |
| 7831276 | Kumar | Nov 2010 | B2 |
| 7840639 | Gough | Nov 2010 | 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 |
| 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 |
| 8359397 | Traversat | Jan 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 9549835 | Schreck 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 et al. | 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 et al. | Nov 2018 | B2 |
| 10133527 | Chang et al. | 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 |
| 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 et al. | 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 |
| 20010011302 | Son | Aug 2001 | A1 |
| 20010012281 | Hall et al. | Aug 2001 | A1 |
| 20010015717 | Mishra et al. | 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 |
| 20020009988 | Murata | 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 |
| 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 |
| 20020081993 | Toyoshima | Jun 2002 | A1 |
| 20020087622 | Anderson | Jul 2002 | A1 |
| 20020090912 | Cannon | 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 |
| 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 | 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 |
| 20030228842 | Heinonen | Dec 2003 | A1 |
| 20040057075 | Stewart et al. | Mar 2004 | A1 |
| 20040127254 | Chang | Jul 2004 | A1 |
| 20050086300 | Yeager | Apr 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 |
| 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 et al. | 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 |
| 20080318602 | Chang et al. | Dec 2008 | A1 |
| 20090002760 | Chang et al. | Jan 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 |
| 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 et al. | 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 et al. | 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 | Aug 2018 | A1 |
| 20180253264 | Chang et al. | Sep 2018 | A1 |
| 20180335989 | Chang et al. | Nov 2018 | A1 |
| 20180364929 | Chang et al. | Dec 2018 | A9 |
| 20190107980 | Chang et al. | Apr 2019 | A1 |
| 20190121585 | Chang et al. | Apr 2019 | A1 |
| 20190121613 | Chang et al. | Apr 2019 | A1 |
| 20190272148 | Chang et al. | Sep 2019 | A1 |
| 20190303100 | Chang et al. | Oct 2019 | A1 |
| 20190361617 | Chang et al. | Nov 2019 | A1 |
| 20190384547 | Chang et al. | Dec 2019 | A1 |
| 20200097225 | Chang et al. | Mar 2020 | 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 |
| 738949 | Feb 2002 | EP |
| 952513 | Feb 2004 | EP |
| 691619 | Feb 2007 | EP |
| 2332764 | Nov 2002 | GB |
| 11316658 | Nov 1999 | JP |
| 0195096 | Dec 2001 | WO |
| 0195097 | Dec 2001 | WO |
| 02084928 | Oct 2002 | WO |
| Entry |
|---|
| Schulyer et al., “Solutions to Sharing Local Printers: LAN Systems Inc., LANSpool, $395 per Server”, PC Week, Oct. 1989, vol. 6, No. 39, pp. 75 (2), 3 pages. |
| 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. |
| Provisional Applications, via public pair: U.S. Appl. Nos. 60/224,701, 60/227,878, 601243,654, 60/208,967, 60/220,047, 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. |
| Jun. 7, 2002, International Search Report from the International Searching Authority in international patent application No. PCT/US01/46247, 4 pages. |
| Jul. 24, 2002, International Preliminary Examination Report from the International Preliminary Examining Authority in international patent application No. PCT/US01/46247, 3 pages. |
| Jan. 6, 2003, International Search Report from the International Searching Authority in international patent application No. PCT/US01/48057, 3 pages. |
| May 28, 2004, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/016,630, 34 pages. |
| Aug. 24, 2004, International Preliminary Examination Report from the International Preliminary Examining Authority in international patent application No. PCT/US01/48057, 11 pages. |
| Jan. 13, 2005, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/000,732, 16 pages. |
| Mar. 9, 2005, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/003,594, 13 pages. |
| Mar. 29, 2005, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/016,630, 33 pages. |
| Oct. 11, 2005, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/000,732, 18 pages. |
| Sep. 11, 2006, Advisory action from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/000,732, 3 pages. |
| Jun. 24, 2010, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/016,223, 7 pages. |
| Oct. 26, 2010, Office action from the European Patent Office in European patent application No. 01985549.3, 4 pages. |
| Dec. 29, 2010, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 10/016,223, 5 pages. |
| Mar. 18, 2011, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 12/907,865, 22 pages. |
| Jun. 11, 2012, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 12/907,865, 37 pages. |
| Jul. 17, 2012, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 12/903,048, 11 pages. |
| Nov. 16, 2012, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/103,958, 6 pages. |
| Jun. 24, 2013, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/708,607, 36 pages. |
| Jun. 24, 2013, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,295, 24 pages. |
| Jul. 26, 2013, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/864,000, 41 pages. |
| Sep. 11, 2013, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/103,958, 15 pages. |
| Sep. 26, 2013, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,306, 72 pages. |
| Dec. 23, 2013, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/476,947, 20 pages. |
| Jan. 13, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/864,000, 16 pages. |
| Feb. 28, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/103,958, 11 pages. |
| Mar. 20, 2014, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/708,607, 19 pages. |
| Apr. 2, 2014, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,306, 24 pages. |
| Apr. 17, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/864,000, 6 pages. |
| Jun. 18, 2014, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/103,958, 8 pages. |
| Jun. 26, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/476,947, 85 pages. |
| Jul. 7, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,295, 85 pages. |
| Aug. 29, 2014, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/864,000, 7 pages. |
| Oct. 31, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,299, 145 pages. |
| Nov. 17, 2014, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/103,958, 6 pages. |
| Dec. 19, 2014, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/684,000, 7 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/866,143, dated Aug. 25, 2017, 25 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,369, dated Feb. 22, 2018, 151 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,359, dated Feb. 23, 2018, 153 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,349, dated Mar. 9, 2018, 121 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/866,143, dated Apr. 18, 2018, 11 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/866,143, dated Jun. 28, 2018, 9 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 15/201,194, dated Aug. 9, 2018, 87 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,359, dated Oct. 29, 2018, 50 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,369, dated Oct. 29, 2018, 52 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,349, dated Dec. 26, 2018, 43 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,349, dated Apr. 15, 2019, 57 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,359, dated Jun. 21, 2019, 56 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 16/229,896, dated Jul. 29, 2019, 7 pages. |
| Office Action prepared by the US Patent and Trademark Office for U.S. Appl. No. 14/828,369, dated Sep. 6, 2019, 52 pages. |
| Jan. 8, 2015, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/476,947, 55 pages. |
| Jan. 14, 2015, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/708,607, 66 pages. |
| Jan. 21, 2015, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,306, 42 pages. |
| Mar. 25, 2015, Corrected Notice of Allowability from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/708,607, 6 pages. |
| Jun. 10, 2015, Notice of Allowance from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/103,958, 7 pages. |
| Jun. 12, 2015, Office action from the U.S. Patent and Trademark Office in U.S. Appl. No. 13/710,299, 94 pages. |
| Jun. 25, 2015, Notice of Allowance from the United States Patent and Trademark Office in U.S. Appl. No. 13/710,295, 42 pages. |
| Oct. 13, 2015, Notice of Allowance from the United States Patent and Trademark Office in U.S. Appl. No. 13/710,295, 10 pages. |
| Feb. 22, 2016, Notice of Allowance from the United States Patent and Trademark Office, in U.S. Appl. No. 13/710,295, 9 pages. |
| Apr. 1, 2016, Office Action from the United States Patent and Trademark Office, in U.S. Appl. No. 13/710,299, 70 pages. |
| Oct. 4, 2016, Notice of Allowance from the United States Patent and Trademark Office, in U.S. Appl. No. 13/710,299, 14 pages. |
| May 6, 2013, Notice of Allowance from the United States Patent and Trademark Office, in U.S. Appl. No. 13/103,958, 10 pages. |
| Jan. 26, 2017, Notice of Allowance from the United States Patent and Trademark Office, for U.S. Appl. No. 13/710,299, 16 pages. |
| Jun. 14, 2017, Notice of Allowance from the United States Patent and Trademark Office, for U.S. Appl. No. 13/710,299, 16 pages. |
| Jan. 10, 2017, Examination Report from the European Patent Office, for European Patent Application No. 01985549.3, 10 pages. |
| Albrecht et al., “IP Services over Bluetooth: Leading the Way to a New Mobility,” IEEE Proceedings of 24th Conference on Local Computer Networks, Lowell, MA, Oct. 18-20, 1999, 10 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/692,977, dated Oct. 3, 2019, 114 pages. |
| Notice of Allowance prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 16/229,896, dated Nov. 7, 2019, 82 pages. |
| Final Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/828,349, dated Nov. 26, 2019, 56 pages. |
| Notice of Allowance prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/828,359, dated Jan. 10, 2020, 47 pages. |
| Notice of Allowance prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/828,369, dated Jan. 13, 2020, 46 pages. |
| Office Action prepared by the United States Patent and Trademark Office for U.S. Appl. No. 14/828,349, dated Apr. 13, 2020, 84 pages. |
| Office Action prepared by the United States Patent and Trademark Office for U.S. Appl. No. 16/416,088, dated Apr. 15, 2020, 87 pages. |
| Office Action prepared by the United States Patent and Trademark Office for U.S. Appl. No. 16/444,261, dated Apr. 29, 2020, 88 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190250883 A1 | Aug 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60262764 | Jan 2001 | US | |
| 60245101 | Nov 2000 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16229896 | Dec 2018 | US |
| Child | 16396460 | US | |
| Parent | 15332432 | Oct 2016 | US |
| Child | 16200380 | 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 | 10053765 | Jan 2002 | US |
| Child | 15332432 | US | |
| Parent | 10016223 | Nov 2001 | US |
| Child | 12903048 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16200380 | Nov 2018 | US |
| Child | 16229896 | US |
