Patent Grant
11467856
Present invention relates to a communication device and a method of using it to enable wireless communication between computing devices.
As an example to demonstrate the functionalities and advantages of the communication device of present invention, printing support for wireless mobile devices (e.g. laptops, PDAs, mobile phones) will be described.
Most handheld devices (PDAs, mobile phones) today do not have printing support due to their low processing power and the lack of appropriate printer drivers. One current method of printing wirelessly from mobile devices such as PDAs or mobile phones requires that a user first install an appropriate printer driver corresponding to a device specific printer. One driver is required for each printer. However, most printer drivers are unavailable for operating systems that run on PDAs and mobile phones. Furthermore, it is difficult and burdensome for a user to install a new printer driver each time printing is attempted at a different printer. Also, to print wirelessly, the printer needs to be wireless-enabled. Most printers today are not wireless-enabled. Therefore, users of handheld device rely mainly on “synching” their devices with PCs to print. However, “synching” could be difficult when a user is traveling or “on the go.” Concerns over security, privacy, and complications in installation processes discourage mobile users from synching with PCs in a business lounge, hotel business center, conference center or another person's office.
Wireless communication standards such as WiFi and Bluetooth “cut the wire”, allowing the transfer of files between computing devices. Currently, however, privacy and security concerns dictate that a first computing device sending, transferring, or retrieving file or data wirelessly to and from a second computing device (e.g. to its hard drive) requires that the user of the second computing device respond with an accept or reject command each time (e.g. through a user interface). This current method or process sacrifices the ease of use for wireless devices to safeguard security.
Another difficulty in using wireless communication today is that a user is expected to have technical knowledge of the installation and configuration of the wireless hardware and software (e.g., adapters, dongles, drivers, protocol stacks), and related security settings. The communication device of present invention significantly simplifies the configuration of wireless communications, making it much easier to use.
A communication device of present invention includes a structural, external interface (e.g., a USB interface) for connecting to a computing device, a wireless interface for making a wireless connection to a second computing device, and a memory or storage component for storing and embedding software for a variety of applications. The present invention provides wireless printing without the need to install a device specific printer driver each time at each new location for printing. Moreover, the invention enables wireless printing to any printer—not just to wireless printers. Furthermore, the present invention improves the above processes without compromising security or privacy. The present invention enables transferring of files and data wirelessly from one device to another and improves ease of use.
The communication device of present invention can be connected to a first computing device (e.g., a personal computer or PC) to enable instant wireless communication with a second computing device. No driver or software installation is needed in the first computing device. All software components required to enable the wireless communication are embedded in the communication device itself and can be automatically launched, installed and execute such as through an AutoRun process in the first computing device.
In addition, the embedded software components in the communication device can automatically uninstall or delete applications or data when the communication device is unplugged from the external port such as the USB or FireWire port. No data from the second computing device or from the communication device will be retained in the first computing device after the communication device is disconnected from the first device, thus enhancing privacy and security.
The present invention further allows a computing device to wirelessly provide services to other computing devices. As an examples of such a service, a PC can provide printing or data display services to a mobile computing device (e.g., a mobile computer, digital telephone, or digital camera). For example, a user of the mobile computing device can simply plug the communication device (e.g., size of an adapter or dongle) into a USB interface or port of the PC. The user can then instantly send a document or data over a wireless connection, through the communication device and to a printer connected to the PC, all directly from the mobile device. After the printing process has been completed, the communication device is unplugged from the PC and no data is retained by the PC. No printer driver installation is needed in the mobile device and the user can print to any printer that is connected to the PC. In addition, the printer need not be a wireless printer.
The wireless communication device of the present invention provides numerous advantages and functionalities.
Printing documents from mobile devices is made easy. Present communication device simplifies the user experience of data output from a mobile device. A user only needs to connect the communication device to a desktop PC or laptop or other computing device (e.g. through USB port). An embedded application in the communication device may be automatically launch in the PC. The user launches a client application on the mobile device (e.g. PDA, mobile phone, digital camera etc) can automatically recognizes the service (e.g., printing) enabled by the communication device of present invention. The user just needs to select the document to be printed and the document is printed to a selected printer associated with the PC. Thus, wireless communication device of this invention simplifies the process of getting a print from the mobile device.
The communication device includes embedded software components that automate configuration of wireless connectivity. The present communication device automates the process of configuring the hardware (e.g. installation, un-installation), thus making wireless connectivity easy to use for non-technical users.
Present communication device can be used as an external disk drive. The present communication device is unique since it may also include storage or memory (e.g. flash Memory) that could cache or store data, in addition to the wireless communication capability. The memory component may be segmented into one or more logical segments such as a public area and a private area. The public area for example can be reserved for a user to save and retrieve data or files when the communication device is plug into a PC or laptop. In this case, the communication device is used as an external disk storage drive that a user can easily carry along with him.
The present communication device simplifies sending and retrieving of wireless data from one device another, and makes it easer to use and without compromising privacy and or security. Prior art methods requires user consent or permission from a second party before a first party could send or retrieve data wirelessly to or from the computing device of the second party. The present invention eliminates this requirement without sacrificing privacy and or security.
The present communication device could uniquely be used as a channel for distributing software products. The present invention ties-up the software functionality inside a communication device thus making it more difficult for software piracy or cloning of software comparing to other distribution channels such as CD.
The present communication device can be configured to retrieve data from only the second computing device (e.g. mobile device) of a selected mobile user, thus eliminating the risk of a third device accidentally retrieving data from the first computing device when the communication device is plugged into the first communication device.
No data is retained by the computing device where the communication device is connected. In the aforementioned printing scenario, if the user is using another person's desktop for printing, the user must be sure that no document or data is accidentally left on the desktop. When using another person's PC there is always concern that a confidential document could be left on the PC. In the present invention, one or more software components embedded in the device ensure that no data relating to the output of the digital document is retained by the computing device.
The communication device of present invention can include an optional battery. This enables the communication device to function on its own, without the need to be connected to a PC to draw power. Therefore, a mobile device can send and or retrieve files or data wirelessly to and from the memory component of the communication device directly anywhere (e.g., wireless device in the pocket of the user) without the need to plug the communication device to a PC for usage.
Printing is used as an example to illustrate the advantages of the communication device of present invention. It in no way constrains the scope of the invention. The communication device can embed different programs to provide a variety of functionalities through wireless communications between multiple computing devices such as display, presentation of data, secure wireless data transfer, games, instant messaging, internet access among others as it will be evident by one skilled in the art after a reading of the disclosure and its accompanied drawings.
Additional description and implementations of the present invention will be apparent from the detailed description of the preferred embodiment thereof, which proceeds with reference to the accompanying drawings.
The communication device 100 includes a memory component 130 that may include volatile memory (e.g., ROM, RAM) and or non-volatile memory (e.g., flash memory, hard disk). One or more software components or applications (not shown) may be stored in the memory component 130. The software components or applications stored in the memory component 130 may include programs or functionalities that enable device 100 to “auto run” or “auto play” so that, when the communication device 100 is connected with interface 110 to a computing device 170, the program or software application will be automatically installed, launched and executed in the computing device 170, as will be described in detail below. The memory component 130 may include a program memory segment 140 and an optional separate file memory segment 150. Programs or software applications can be stored or embedded in the program memory 140. The software programs or applications may or may not be viewed or edited (e.g., added, deleted or changed) by a user. Hence program memory segment 140 can be implemented as a private or secure section of the memory component 130.
As an optional feature, file memory segment 150 may provide for additional file or data storage, run time buffering of data, or caching of data and files for faster access. The file storage component 150 is an example of an implementation of such memory segmentation. This component 150 may be optional and may or may not exist depending on implementation. Files and data stored in the file storage memory component 150 typically can be saved, retrieved, viewed or edited by a user through a computing device. As an example, the communication device 100 can be used as an external disk drive (e.g., “Flash drive”) that a user can access and use as separate data storage drive when device 100 is plugged into the computing device 170.
The communication device 100 may include an optional external control switch 165, which can be used to activate, deactivate, control or adjust one or more functions provided by the device. The communication device 100 may also include an interface or status indicator (not shown) such as an LCD displaying text or image, lights or sound for status indication.
As is known in the art, wireless interface 120 may include a radio, a baseband controller and separate internal memory (not shown). The separate internal memory, implemented with Flash, RAM and or ROM circuitry, can store instructions and data required for proper functioning of the wireless component 120, such as a wireless protocol stack. Wireless component interface 120 may include a internal processor (not shown) that implements the instructions and logic for complying with wireless protocols ( e.g. Bluetooth or IEEE 80211, a,b,g,f, among others), in addition to managing the radio and the baseband of the wireless component interface 120.
Computing device 170 (e.g. PC, laptop, server) includes at least one structural interface 172 to which interface 110 of communication device 100 is connectable. In a typical implementation, structural interface 172 is a USB interface, however other interfaces such as parallel, serial, Firewire (IEEE 1394 a, 1394 b), CF (compact flash), SD (secure digital), Ethernet or wireless interfaces can also be implemented. To simplify the following description of the invention, interfaces 110 and 172 will be referred to a USB interfaces. It will be appreciated, however, that interfaces 110 and 172 could alternatively be implemented with any other interface format.
A computing device 180 (e.g., PC, laptop, server, PDAs such pocket PC, Palm, Symbian, Java or Linux cell phones, digital cameras, etc.) includes a wireless interface 182. The communication device 100 can communicate with the computing device 180 via wireless interface 120. Examples of wireless interface 120 that can be implemented include Bluetooth, IrDa, ZigBee, IEEE802.11 A, B, F and G, among others.
The controller 260 may or may not include an operating system. An advantage of the implementation of communication device 200 in
As discussed, memory component 140 can be implemented depending on the application. All above features and requirements can be implemented in a single memory component 130, segmented in to two components 140 and 150, or segmented into three components 144,146, and 150 as illustrated in
In communication devices 400 and 500 private memory component 140 is segmented into two sections: internal section 144 and embedded section 146. Internal memory section 144 can store data and programs required for proper functioning of the communication device 100. These programs and data can be accessed by a memory controller 415 and support its functionalities. Embedded memory section 146 can store programs, applications, and data that will be installed or launched on computing device 170 when communication device 100 is plugged into computing device 170. The software program or applications typically may not be viewed or edited (e.g., added, deleted or changed) by user and is embedded during the manufacture of devices 400 and 500.
Memory controller 415 manages communication with the structural external interface 110 (e.g., USB, FireWire, etc.) and memory component 130. Memory controller 415 can be implemented with a microprocessor, DSP, ASIC, etc and may include internal memory for running its program. Additional memory such as those provided by internal memory section 144 can also be implemented if needed. Examples of the functionality and software components that may be implemented with the memory controller 415 include “auto run” or “auto play” functionalities, segmentation of memory 130, data security, and USB interfacing functionalities, among others.
Communication device 400 includes a hub component 425 (e.g., a chip), which combines the components of wireless interface block 120 with the memory component block 130 and its memory controller 415. The hub 425 enables sharing of the same external structural interface 110 (e.g., USB, FireWire) between wireless component 120, memory controller 415 and memory component 130.
Communication devices 100-500 of the present invention provide users of mobile devices 180 (e.g., wireless enabled digital camera, mobile phone, etc.) data storage that is integral with the wireless communication and may be independent of computing device 170. In accordance with the present invention, each of communication devices 100-500 can be configured to communicate in a point-to-point manner with a wireless-enabled mobile device 180 (e.g., a Bluetooth digital camera, phone etc). An embedded application (not shown) stored on each wireless device 100-500 can manage the communication with an embedded application in the mobile device 180.
In step 602, a wireless communication channel is established between mobile device 180 and communication device 100-500. This step may include additional steps of negotiating the service options between an application in the mobile device 180 and wireless device 100-500 through an interface. The interface may be part of an application GUI (Graphical User Interface) in the mobile device 180 or as part of a switch or display settings provided by the wireless device 100-500.
In step 604, mobile device 180 obtains or accesses digital content. For example, a photo may be taken with a digital camera or camera phone 180 and the photo stored into a memory component of the mobile device 180 (e.g., flash memory).
In step 606, the mobile device 180 sends the digital content wirelessly to communication device 100-500 automatically upon a predefined condition being met. For example, the predefined condition can be that the data storage contained in the mobile device 180 exceeds a certain preset threshold. The preset threshold can be the maximum storage capacity of the mobile device 180, any other storage level, or any other condition.
In step 608, wireless communication device 100-500 stores the transmitted data into the available memory component 150 of device 100-500 for storage. Optionally, communication device 100-500 may return 100-500 a signal or other type of indication to the user of the mobile device 180 if the capacity of memory capacity in communication device 100-500 is reached.
In step 610, communication device 100-500 is plugged into a computing device 170, the data stored in the wireless device 100-500 is transferred to, synchronized with, or stored in the computing device 170 (e.g., on a hard drive). For example, this step may be performed by an embedded application that automatically launches and runs on the computing device 170. This step may be automatic, or partially automatic or manually aided by the user through a GUI that runs in the computing device 170.
In step 612, the data storage area 150 can be cleared manually by the user, automatically or a combination after the digital content has been transferred to computing device 170, thereby enabling communication device 100-500 to wirelessly receive additional data from the mobile device 180.
In step 710, the communication device 100-500 is connected to computing device 170. For example, the connection may use a USB interface or FireWire interface.
In step 720, communication is established between the device 100-500 and computing device 170. For example, the device 100-500 engages dialog with the computing device 170 using one or more standard protocols that are built-into the operating system of the computing device 170 (e.g., a “Plug and Play” feature for USB, and others). In this implementation, the device 100-500 is immediately recognized by the computing device 170 once the connection is made (i.e., no driver or software installation is required). Alternatively, software such as a driver for setting-up communication between the device 100-500 and the computing device 170 may be provided to a user separately (e.g., on a CD or downloaded from a network) if the operating system of the computing device 170 does not include an immediate plug and play feature. In this case, a user installs the software in the computing device 170 so that the device 100-500 can be recognized.
In step 730, one or more applications stored in the memory component 130 may be automatically installed and launched in the computing device 170 when the device 100-500 is connected to the computing device. The installation and launching of the application that is embedded or stored in the communication device 100-500 may be implemented using the “Auto Run” or “auto play” feature, which may be provided by the operating system or software installed in the computing device 170 to automatically launch the program that is stored in the memory component 130 of the communication device 100-500. In one implementation, a pointer may be embedded in the dialog between the device 100-500 and computing device 170 in step 720. The pointer would point to a setup file in the memory component 130 that instructs the computing device 170 to install or run one or more applications stored in the memory component 130. Operating systems can also provide certain means to add entries to AutoRun executables. The various different applications that are stored in the communication device 100-500 may perform various tasks in the computing device 170. For example, they may help manage wireless communication between the computing devices 170 and 180 through wireless interface 120, perform presentations (e.g. Powerpoint™), or perform any of numerous other tasks or operations, some of which are described later with reference to
In step 740, which is an optional step, a user interacts with the launching of an application from the memory component 130 or the subsequent execution of the application on the device 170. As one example, optional user consent or acceptance may be obtained before the application is installed and run in the computing device 170. As another example, a user may control the execution process of the application, such as giving command to initiate, pause, cancel, or abort the application. User interaction options can be implemented by a GUI (graphical user interface) provided (1) locally in the computing device 170, or (2) remotely from another computing device 180 through wireless communication associated with controlling/interacting with the application stored in the communication device 100-500. In addition, a user may optionally activate/deactivate the communication device 100-500 or one or more of its functions by using the external switch 165 if those options are implemented.
In step 750, if the communication device 100-500 is disconnected from the computing device 170, a disconnection signal is received or intercepted by one or more applications launched in step 230. In one implementation, these applications can automatically uninstall the application or applications from computing device 170, and including itself or themselves and may delete any data stored thereon. In this case, no data from the computing device 180 will be retained in the computing device 170 after the communication device is unplugged, thus enhancing privacy and security.
Uninstalling all applications and deleting all data residing in computing device 170 when device 100-500 is disconnected from computing device 170 has the advantage of ensuring privacy for a user of computing device 170 and also protects the manufacturer of the device 100-500 against piracy of the software applications launched in step 730. The communication device 100-500 in this case functions as a security key. When device 100-500 is no longer plugged into the computing device 170, all software applications previously launched can be uninstalled and all data may be deleted—restoring the computing device to its initial state prior to the device 100-500 being plugged in.
Step 750 can also be implemented in various ways, depending on the type of application. When device 100-500 is disconnected from computing device 170, the one or more applications launched in step 830 can also be configured to uninstall applications and delete data only in part so that only certain application modules and data are removed. One advantage of this implementation is that when communication device 100-500 is again plugged into computing device 170, some installation and setup processes can be skipped and the application will launch faster. As another alternative implementation, all applications and data can be retained in the computing device 170 when communication device 100-500 is unplugged. This may be preferred in certain cases such as if privacy and security is not an issue.
In addition to the basic operations described with reference to
In step 810, wireless device 100-500 is plugged into a first computing device 170.
In step 820, wireless device 100-500 is detected by the first computing device 170 (e.g. Play and Play).
In step 830, a user may perform read or write operations with the file storage component 150 of the device 100-500 to use it as an external drive. For example, user may save digital documents to the file storage component 150 or retrieve digital documents stored in the storage component. Step 830 (designated process A) illustrates the communication device 100-500 being used as an external memory drive after communication has been established between the device 100-500 and the computing device 170 such as through a USB interface. No installation of software or driver is needed for using this feature of the device 100-500.
In step 840, the wireless communication means of communication device 100-500 is enabled and activated. Software stored in the device 100-500 may be automatically installed or launched. For example the appropriate wireless communication protocol stack may be installed or launched in the computing device 170, if the computing device 170 does not already have one pre-installed. Such protocol stacks may be automatically launched and installed in the computing device 170 as one of the applications stored in the program memory component 140. User may or may not need to interact with this installation process. In this example, the communication device 100-500 automatically adds wireless capability to the computing device 170 by just plugging in the device 100-500.
In step 850, the computing device 170 may now interact with other wireless enabled devices through the wireless interface 120 of device 100-500. The wireless communication may be enabled with an additional service discovery and selection step. Steps 840 and 850 (designated process B) show the communication device 100-500 having the means for being used as a wireless communication adaptor (e.g., a Bluetooth dongle).
In step 860, an application stored in communication device 100-500 is automatically installed in computing device 170 and launched. In step 870, a query is made as to whether the communication device 100-500 is disconnected from computing device 170. If no, step 870 returns to step 860. If yes, step 870 proceeds to step 880. In step 880, the application is terminated automatically. Steps 860-880 (designated process C) correspond to an autorun functionality described above with reference to
The communication device 100-500 of the present invention may include any or all of process A (step 830), process B (steps 840-850),or process C (steps 860-880) concurrently or in any combination (e.g. A, B, C, A&B, A&C, B&C, or ABC) for one or more implementations of the device 100-500. For example, an application that is stored in the program memory component 130 of the communication device 100-500 may be launched and executed in the computing device 170 to perform certain tasks (e.g. send and/or receive message from other computing devices, or printing digital document to a printer connected to device 170). The application may require that the communication device 100-500 stay connected for interaction with other computing devices through the wireless interface 120 (e.g. to receive user command from computing device 180). In this example, both process B and process C are required and used.
Conventionally, whenever a first computing device sends, transfers, or retrieves a file or data wirelessly to or from a second computing device, a user must manually issue an accept or reject command for security and privacy reasons. The present invention improves upon such a conventional process without sacrificing security or privacy.
In step 902, wireless communication device 100-500 is plugged into a first computing device 170 (e.g., step 810).
In step 904, wireless device 100-500 is detected by the first computing device 170 (e.g., step 820), and a wireless application stored in memory component 130 is automatically launched such as through the process of Auto Run (e.g., step 860).
In step 906, the wireless application enables the communication device 100-500 to send and receive wirelessly data to and from another device 180 (e.g., step 840). A discovery process may be included in this step. The user of device 180 can then wirelessly transfer (e.g., send, receive or retrieve) a document from his computing device 180 (e.g., mobile phone, digital camera, PDA, laptop, etc.) to the communication device 100-500.
In step 908, computing device 180 can send or retrieve data to or from public storage component 150 of the wireless device 100-500 without the need for the user of the first computing device 170 to respond or grant permission (e.g., step 850, process B). The public storage component 150 of the wireless device 100-500 may be configured to be public, and wireless device 100-500 is connected externally to the computing device. This is in contrast to the hard drive of the first computing device 170, which is private to the user of the first computing device 170. Data is transferred to and from mobile device 180 with communication device 100-500 and not directly to and from the hard drive of the computing device 170.
In step 910, the user of the first computing device 170 can receive data sent from the second computing device 180 by retrieving the data or file received from computing device 180 and stored in the public storage area 150 of device 100-500 (e.g., step 830, process A).
Alternately, in step 912, if the user of the first computing device 170 desires to make available or public certain data or files for a second computing device 180, he can simply copy the data or file from his computing device 170 to the public storage area or component 150 of communication device 100-500 (e.g., step 330). The files and data in the public area in the communication device 100-500 become available for other users, and the second computing device 180 can now retrieve the file wirelessly from the public storage area of the memory component 150 in device 100-500 (e.g., step 850, process B).
In step 914, wireless device 100-500 is unplugged and the application that was launched in the computing device 170 may be uninstalled and all data may be totally or partially deleted (process C).
Examples of computing device 1030 include but are not limited to desktop PCs, laptop PCs, tablet computers, servers, PDAs, and handheld computers. The computing device 1030 has at least a USB interface, for example, which can connect to the communication device 100-500 of present invention. Other interfaces are also possible as described above.
Computing device 1020 includes, but is not limited to, desktop PCs, laptop PCs, tablet computers, servers, PDAs, handheld computers, Internet information appliances, mobile phones, web pads, digital cameras, and combinations of these devices. The computing device 1020 has at least a wireless interface that can communicate with the communication device 100-500 through wireless communication protocols such as Bluetooth, Infrared, IEEE 801.11a, IEEE 801.11b (WiFi), IEEE 801.11g, Zigbee, among others. It should be noted that although only one computing device 1020 is shown here, the computing device 1030 with the connected device 100-500 may service more than one computing device 1020 concurrently or alternatively or in combination. In this case, the application 1010 may provide features such as queuing and spooling.
Application 1010 correspond to one or more software components or applications stored or embedded in the memory component 130 of the communication device 100-500. As discussed earlier, application 1010 may be launched and executed automatically in the computing device 1030 when device 100-500 is connected to computing device 1030. For example, application 1010 may AutoRun when device 100-500 is connected to device 1030, with no driver or application installation by the user being necessary. In this particular example, the application 1010, after launching in the computing device 1030, may perform one or more of the following operations:
In addition to the application 1010 above, the memory or storage component 130 of the communication device 100-500 may include other programs (not shown) that can be launched and executed in the computing device 1030. An example of such a program is a portion or the entire wireless communication protocol stack that allows the computing device 1030 to communicate with other computing devices wirelessly through the wireless interface 120 of communication device 100-500. Another example of application 1010 includes components that execute and/or control a presentation program (e.g. PowerPoint®) with the presentation file received and being controlled wirelessly from computing device 1020.
Application 1022 is a software application residing in the computing device 1020. The application 1022 may include any or all of the following components and functionalities:
Blocks 1040 represent output devices. Printers, projectors and monitors are shown as examples of output devices. However, output devices may also include TVs, fax machines, multifunctional machines (e.g. printer/fax/scanner), copiers, sound output systems, among others.
In step 1160, a user has a document in his mobile computing device 1020 that he wishes to print. He connects his communication device 100-500 to the computing device 1030 such as through a USB interface. As discussed earlier, communication is then established between the communication device 100-500 and the computing device 1030.
In step 1165, application 1010 stored in the device 100-500 is launched in the computing device 1030. Optionally, if the wireless communication stack is not already included in application 1010, another program (e.g., which includes wireless communication protocol stack) can also be launched to allow the computing device 1030 to communicate with other devices wirelessly.
In step 1170, application 1022 residing in the computing device 1020 interacts with application 1010 launched in the computing device 1030 to manage or negotiate the data transmission process. User of computing device 1020 may select from a GUI in his mobile device 1020 one or more output devices 1040 associated with or connected to the selected computing system 1035 for providing the output or rendering service. Application 1022 may transmit data content 1024 from the device 1020 to device 1030 through wireless communication link 1015. Application 1022 may encrypt and or compress data content 1024 before transmission.
In step 1175, the data content 1024 received by the device 1030 is further processed. Such process may include, but not limited to, reading, parsing, interpreting, decrypting, and decompressing the data content 1024 received. Process 1175 may also include converting the data content to output data format (e.g. print data, image file) suitable for input to the selected output devices 1040 for output or rendering. These operations may be performed by the application 1010 in the computing device 1030. Or alternatively, application 1010 may invoke other applications (e.g. printer driver application) residing in the computing device 1030 to help in one or more steps in the further processing of the digital document 1024.
In step 1180, the further processed data content 1024 and generated output data is then sent to the output device 1040 for printing or rendering.
During the output process, user may obtain information related to the output process status through a GUI in the computing device 1020. The user may also provide instructions to adjust the output process or options through the GUI.
After the output process has been completed, the user may disconnect 100-500 from the computing device 1030. The application 1010 automatically exits and may remove or uninstall itself from the computing device 1030. Any data that was used in connection with the output process may also be removed or deleted. No data of the content 1024 is left in the computing device 1030, which enhances privacy and security.
Steps 1260, 1265, and 1270 are identical to respective steps 1160, 1165, and 1170 shown in
In step 1275, the data content 1024 (e.g., a presentation file such as in a PowerPoint® format) is displayed or projected by output device 1040 (e.g., a projector).
In step 1280, the display of data content 1024 is controlled by device 1020. Such control may include, but is not limited to, starting or ending the display, going forward to the next page or backward to the previous page, enlarge or minimize the displayed image. Other exemplary features include reading notes of the presentation file with mobile device 1020, while the data content (without the notes) is projected to a projector 1040 through computing device 1030. A GUI may be provided in device 1020 for the user to perform the above-mentioned control.
After the presentation process has been completed, the user may disconnect device 100-500 from the computing device 1030. The application 1010 automatically exits and removes itself from the computing device 1030 as well as any data or file that was used in connection with the data output process. No data of the content 1024 is left in the computing device 1030.
Application 1310 is stored or embedded in the memory component 130 of the communication device 100-500. As discussed earlier, application 1310 may be launched and executed in the computing device 1330 once the device 100-500 is connected to or plugged into computing device 1330. In this particular example, the application 1310, after launched in the computing device 1330, may include but not limited to any combination of the features below:
In addition to application 1310, the program memory 140 may include other programs that can be launched and executed in the computing device 1330. An example of such program is wireless communication protocol stack that allows the computing device 1330 to communicate with other computing devices wirelessly through the communication adapter's wireless interface 120.
Computing device 1330 includes, but not limited to desktop PCs, laptop PCs, tablet computers, servers, PDAs, handheld computers, Internet appliances, Web pads, mobile phones, and digital cameras among others. Preferably, computing device 1330 is a mobile device. The computing device 1330 has at least a USB interface, Firewire, SD (secure digital) interface or CF (compact flash) interface among others that can connect with the interface 110 (e.g., USB) of device 100-500. It should be noted that although only one computing device 1330 is shown here, the computing device 1320 (with the application 1325) may service more than one computing devices 1330 (connected to the communication device 100-500) either concurrently or in an alternative manner for providing service. For example, application 1325 may provide queuing and spooling services based on one or more of quality of service, price, and availability means.
Examples of computing device 1320 include but not limited to desktop PCs, laptop PCs, tablet computers, servers, PDAs, handheld computers, and other dedicated computing devices. Computing device 1320 has at least a wireless interface which can communicate with the device 100-500 through one or more wireless communication protocols such as Bluetooth, Inferred, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11f, IEEE 802.15, IEEE 802.17, etc. As described earlier, the wireless interface of the computing device 1320 may be implemented by built-in wireless communication hardware or by external wireless adapters or by communication device 100-500.
Application 1325 resides in the computing device 1320. In this particular example, the application 1325 in the computing device 1320 may have the following components and functionalities:
In step 1460, a user connects communication device 100-500 to computing device 1430 through USB interface or another interface. As discussed earlier, communication and interaction is then established between the device 100-500 and the computing device 1330.
In step 1465, application 1310 stored in communication device 100-500 is launched in the computing device 1330. This may be launched automatically such as through an AutoRun process as previously discussed. Optionally, another program or component included in application 1310 (e.g., a wireless communication protocol stack) may also be launched in the computing device 1330 from the memory component of the device 100-500 to allow the computing device 1330 to communicate with other devices wirelessly. In step 1465, application 1310 may further include a discovery and selection of the computing device 1325 from among a list of available computing devices available for communication. Information relating to the output device 1340 associated with computing device 1325 may be received and displayed to the user at the computing device 1330 so the user can select the output device 1340.
In step 1470, user transmits data content 1335 (e.g., a digital document) from computing device 1330 to computing 1320 through wireless communication link 1315. Application 1325 residing in the device 1320 communicates with application 1310 running in the computing device 1330 to manage the transmission process. Application 1310 may provide a GUI in device 1330 where the user can obtain information on the output process or interact and control the output process. The application 1310 may encrypt and or compress data content 1335 before transmission.
In step 1475, the data content 1335 (e.g., digital document) received by the device 1320 is further processed. Such processing may include, but is not limited to, reading, parsing, interpreting, decrypting, and decompressing, raster image processing the digital document 1335 received. One or more of these processes may include invoking one or more other applications (e.g. presentation application, printer driver, viewer software etc residing in computing device 1320). Process 1475 may also include converting the digital document to an output data format (e.g. print data, image file) suitable for input to one or more output devices 1340 associated with computing device 1320. These operations may be performed by the application 1325. Alternatively, application 1325 may invoke other applications (e.g. presentation application, printer driver application, viewer or browser application etc) residing in the computing device 1320 to help in one or more of the above described processes as well as steps for further processing of the data content 1335 (e.g., digital document).
In step 1480, the processed data content 1335 or output data is sent to output device 1340 (e.g. printer) for rendering (e.g. printing, displaying or projecting).
After the output process has been completed, the user may disconnect the device 100-500 from device 1330. Disconnecting device 100-500 triggers the application 1310 to automatically exit and remove itself as well as the traces of data relating to the data content 1335.
Steps 1560, 1565, and 1570 are identical to respective steps 1460, 1465, and 1470 shown in
In step 1580, the display of data content 1335 (e.g., a Power Point® presentation file from Microsoft) is controlled by mobile device 1330. Such control may include, but not limited to, starting or ending the display, going forward to the next page or backward to the previous page, enlarge or minimize the displayed image. A GUI may be provided in mobile device 1330 for user to perform the above-mentioned control. Notes related to the presentation pages may be displayed in the GUI of 1330 as an optional feature while the notes do not need to be displayed on by the projector 1340 during the presentation of the presentation file.
After the wireless presentation process has been completed, the user may disconnect device 100-500 from device 1330. Disconnecting device 100-500 triggers the application 1310 to automatically exit and remove itself as well as the trace of data relating to the data content that may reside in communication device 100-500.
Computing device 1610 may include, but is not limited to, desktop PCs, laptop PCs, tablet computers, servers, PDAs, handheld computers, Internet appliances, mobile phones, and digital cameras.
Application 1630 is stored in the memory component 130 of the communication device 100-500. Once the communication device 100-500 is connected with the computing device 1610, the application 1630 is launched and executed in the computing device 1610. The application 1630 can be launched automatically with AutoRun previously discussed.
In this particular example, the application 1630 is a messaging application. The application 1630 may include one or more of the following components and functionalities including but not limited to:
In addition to application 1630, the program memory 140 may include other programs that can be launched and executed in the computing device 1610. An example of such program is wireless communication protocol stack that allows the computing device 1610 to communicate with other computing device wirelessly through the wireless communication interface 120 of device 100-500.
Other examples of Application 1630 that can be launched when device 100-500 is plug in to computing device 1610, include communicate and sharing of service privately through local point to point wireless communication link 1640. Examples of local wireless point-to-point communication include instant messaging, e-mail, phone calls. Other services that can be shared among the users of computing device 1610 include Internet access, transfer and sharing of files, document editing collaboration, printer and other output devices etc.
This application claims priority to U.S. Provisional Patent Application Ser. No. 60/433,196, file Dec. 12,2002, the entire disclosure of which is incorporated Herein by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5166809 | Surbrook | Nov 1992 | A |
| 5220674 | Morgan et al. | Jun 1993 | A |
| 5287194 | Lobiondo | Feb 1994 | A |
| 5337258 | Dennis | Aug 1994 | A |
| 5404433 | Hosogai | Apr 1995 | A |
| 5412798 | Garney | May 1995 | A |
| 5519641 | Beers et al. | May 1996 | A |
| 5564109 | Snyder et al. | Oct 1996 | A |
| 5580177 | Gase et al. | Dec 1996 | A |
| 5596697 | Foster et al. | Jan 1997 | A |
| 5604843 | Shaw et al. | Feb 1997 | A |
| 5613123 | Tsang et al. | Mar 1997 | A |
| 5619250 | McClellan et al. | Apr 1997 | A |
| 5619649 | Kovnat et al. | Apr 1997 | A |
| 5699495 | Snipp | Dec 1997 | A |
| 5705781 | Habedank et al. | Jan 1998 | A |
| 5708780 | Levergood et al. | Jan 1998 | A |
| 5761480 | Fukada et al. | Jun 1998 | A |
| 5796442 | Gove et al. | Aug 1998 | A |
| 5815194 | Ueda | Sep 1998 | A |
| 5832191 | Thorne | Nov 1998 | A |
| 5867633 | Taylor, III et al. | Feb 1999 | A |
| 5911044 | Lo et al. | Jun 1999 | A |
| 5926104 | Robinson | Jul 1999 | A |
| 5926624 | Katz et al. | Jul 1999 | A |
| 5933498 | Schneck et al. | Aug 1999 | A |
| 5940843 | Zucknovich et al. | Aug 1999 | A |
| 5974312 | Hayes, Jr. et al. | Oct 1999 | A |
| 5982520 | Weiser et al. | Nov 1999 | A |
| 5987454 | Hobbs | Nov 1999 | A |
| 6009464 | Hamilton et al. | Dec 1999 | A |
| 6020973 | Levine et al. | Feb 2000 | A |
| 6037981 | Wilson et al. | Mar 2000 | A |
| 6043898 | Jacobs | Mar 2000 | A |
| 6044428 | Rayabhari | Mar 2000 | A |
| 6046820 | Konishi | Apr 2000 | A |
| 6061452 | Suzuki | May 2000 | A |
| 6070185 | Anupam et al. | May 2000 | A |
| 6091956 | Hollenberg | Jul 2000 | A |
| 6119153 | Dujari et al. | Sep 2000 | A |
| 6138178 | Watanabe | Oct 2000 | A |
| 6141659 | Barker et al. | Oct 2000 | A |
| 6148081 | Szymanski et al. | Nov 2000 | A |
| 6148346 | Hanson | Nov 2000 | A |
| 6157809 | Kambayashi | Dec 2000 | A |
| 6167514 | Matsui et al. | Dec 2000 | A |
| 6169789 | Rao et al. | Jan 2001 | B1 |
| 6202023 | Hancock et al. | Mar 2001 | B1 |
| 6205429 | Peng | Mar 2001 | B1 |
| 6216183 | Rawlins | Apr 2001 | B1 |
| 6225993 | Lindblad et al. | May 2001 | B1 |
| 6233611 | Ludtke et al. | May 2001 | B1 |
| 6246486 | Takahashi | Jun 2001 | B1 |
| 6251014 | Stockdale et al. | Jun 2001 | B1 |
| 6256666 | Singhal | Jul 2001 | B1 |
| 6263387 | Chrabaszcz | Jul 2001 | B1 |
| 6263392 | McCauley | Jul 2001 | B1 |
| 6279153 | Bi et al. | Aug 2001 | B1 |
| 6282710 | Boehler | Aug 2001 | B1 |
| 6285889 | Nykanen et al. | Sep 2001 | B1 |
| 6288790 | Yellepeddy et al. | Sep 2001 | B1 |
| 6324521 | Shiota et al. | Nov 2001 | B1 |
| 6330611 | Itoh et al. | Dec 2001 | B1 |
| 6339706 | Tillgren et al. | Jan 2002 | B1 |
| 6353928 | Altberg et al. | Mar 2002 | B1 |
| 6360364 | Chen | Mar 2002 | B1 |
| 6363452 | Lach | Mar 2002 | B1 |
| 6366912 | Wallent et al. | Apr 2002 | B1 |
| 6366965 | Binford et al. | Apr 2002 | B1 |
| 6366966 | Laney et al. | Apr 2002 | B1 |
| 6370686 | Delo et al. | Apr 2002 | B1 |
| 6379058 | Petteruti et al. | Apr 2002 | B1 |
| 6389010 | Kubler et al. | May 2002 | B1 |
| 6389159 | Gilman et al. | May 2002 | B2 |
| 6396531 | Gerszberg et al. | May 2002 | B1 |
| 6405362 | Shih et al. | Jun 2002 | B1 |
| 6418439 | Papierniak et al. | Jul 2002 | B1 |
| 6418554 | Delo et al. | Jul 2002 | B1 |
| 6421748 | Lin et al. | Jul 2002 | B1 |
| 6426798 | Yeung | Jul 2002 | B1 |
| 6434535 | Kupka et al. | Aug 2002 | B1 |
| 6449052 | Sherer et al. | Sep 2002 | B1 |
| 6452692 | Yacoub | Sep 2002 | B1 |
| 6453127 | Wood et al. | Sep 2002 | B2 |
| 6473800 | Jerger et al. | Oct 2002 | B1 |
| 6477575 | Koeppel et al. | Nov 2002 | B1 |
| 6480292 | Sugiyama | Nov 2002 | B1 |
| 6484219 | Dunn et al. | Nov 2002 | B1 |
| 6487587 | Dubey | Nov 2002 | B1 |
| 6487599 | Smith et al. | Nov 2002 | B1 |
| 6493104 | Cromer et al. | Dec 2002 | B1 |
| 6496802 | vanZoest et al. | Dec 2002 | B1 |
| 6529522 | Ito et al. | Mar 2003 | B1 |
| 6532368 | Hild et al. | Mar 2003 | B1 |
| 6545722 | Schultheiss et al. | Apr 2003 | B1 |
| 6546387 | Triggs | Apr 2003 | B1 |
| 6546419 | Humpleman et al. | Apr 2003 | B1 |
| 6550008 | Zhang et al. | Apr 2003 | B1 |
| 6553431 | Yamamoto et al. | Apr 2003 | B1 |
| 6556313 | Chang et al. | Apr 2003 | B1 |
| 6560651 | Katz et al. | May 2003 | B2 |
| 6584903 | Jacobs | Jul 2003 | B2 |
| 6590588 | Lincke et al. | Jul 2003 | B2 |
| 6594723 | Chapman et al. | Jul 2003 | B1 |
| 6600569 | Osada et al. | Jul 2003 | B1 |
| 6601093 | Peters | Jul 2003 | B1 |
| 6603744 | Mizutani et al. | Aug 2003 | B2 |
| 6604135 | Rogers et al. | Aug 2003 | B1 |
| 6604140 | Beck et al. | Aug 2003 | B1 |
| 6607314 | McCannon et al. | Aug 2003 | B1 |
| 6608928 | Queiroz | Aug 2003 | B1 |
| 6611812 | Hurtado et al. | Aug 2003 | B2 |
| 6615404 | Garfunkel et al. | Sep 2003 | B1 |
| 6622018 | Erekson | Sep 2003 | B1 |
| 6623527 | Hamzy | Sep 2003 | B1 |
| 6625472 | Farazmandnia et al. | Sep 2003 | B1 |
| 6625761 | Sartore et al. | Sep 2003 | B1 |
| 6628417 | Naito et al. | Sep 2003 | B1 |
| 6633395 | Tuchitoi et al. | Oct 2003 | B1 |
| 6636929 | Frantz et al. | Oct 2003 | B1 |
| 6654135 | Mitani | Nov 2003 | B2 |
| 6658625 | Allen | Dec 2003 | B1 |
| 6662224 | Angwin et al. | Dec 2003 | B1 |
| 6671068 | Chang et al. | Dec 2003 | B1 |
| 6678751 | Hays et al. | Jan 2004 | B1 |
| 6694371 | Sanai | Feb 2004 | B1 |
| 6697848 | Hamilton et al. | Feb 2004 | B2 |
| 6701009 | Makoto et al. | Mar 2004 | B1 |
| 6705781 | Iwazaki | Mar 2004 | B2 |
| 6730686 | Baynes et al. | May 2004 | B1 |
| 6732179 | Brown et al. | May 2004 | B1 |
| 6735766 | Chamberlain et al. | May 2004 | B1 |
| 6735768 | Tanaka | May 2004 | B1 |
| 6745229 | Gobin et al. | Jun 2004 | B1 |
| 6745255 | Yen et al. | Jun 2004 | B2 |
| 6751732 | Strobel et al. | Jun 2004 | B2 |
| 6753978 | Chang | Jun 2004 | B1 |
| 6757070 | Lin et al. | Jun 2004 | B1 |
| 6757783 | Koh | Jun 2004 | B2 |
| 6760745 | Tan et al. | Jul 2004 | B1 |
| 6772233 | Iida et al. | Aug 2004 | B2 |
| 6785727 | Yamazaki | Aug 2004 | B1 |
| 6788428 | Shimokawa | Sep 2004 | B1 |
| 6798530 | Buckley et al. | Sep 2004 | B1 |
| 6826632 | Wugofski | Nov 2004 | B1 |
| 6829672 | Deng et al. | Dec 2004 | B1 |
| 6830340 | Olson et al. | Dec 2004 | B2 |
| 6839771 | Bouchier et al. | Jan 2005 | B1 |
| 6840441 | Monaghan et al. | Jan 2005 | B2 |
| 6845398 | Galensky et al. | Jan 2005 | B1 |
| 6857716 | Nagahashi | Feb 2005 | B1 |
| 6859228 | Chang et al. | Feb 2005 | B1 |
| 6885362 | Suomela | Apr 2005 | B2 |
| 6889058 | Tordera | May 2005 | B2 |
| 6892230 | Gu et al. | May 2005 | B1 |
| 6895444 | Weisshaar et al. | May 2005 | B1 |
| 6898652 | Peters et al. | May 2005 | B2 |
| 6910068 | Zintel et al. | Jun 2005 | B2 |
| 6922725 | Lamming et al. | Jul 2005 | B2 |
| 6941014 | Lin et al. | Sep 2005 | B2 |
| 6944687 | Doragh et al. | Sep 2005 | B2 |
| 6947995 | Chang et al. | Sep 2005 | B2 |
| 6948165 | Luu et al. | Sep 2005 | B1 |
| 6952831 | Moore | Oct 2005 | B1 |
| 6975644 | Tordera et al. | Dec 2005 | B2 |
| 7028102 | Larsson et al. | Apr 2006 | B1 |
| 7047302 | Chatani et al. | May 2006 | B1 |
| 7050840 | Lin et al. | May 2006 | B2 |
| 7054296 | Sorrells et al. | May 2006 | B1 |
| 7055956 | Olson et al. | Jun 2006 | B2 |
| 7069578 | Prus et al. | Jun 2006 | B1 |
| 7076534 | Cleron et al. | Jul 2006 | B1 |
| 7085814 | Gandhi et al. | Aug 2006 | B1 |
| 7099304 | Liu et al. | Aug 2006 | B2 |
| 7102691 | Dischert et al. | Sep 2006 | B2 |
| 7127541 | Govindarajulu et al. | Oct 2006 | B2 |
| 7136914 | Motoyama | Nov 2006 | B2 |
| 7143408 | Anderson et al. | Nov 2006 | B2 |
| 7149726 | Lingle et al. | Dec 2006 | B1 |
| 7149834 | Peters et al. | Dec 2006 | B2 |
| 7158953 | DeMello et al. | Jan 2007 | B1 |
| 7164885 | Jonsson et al. | Jan 2007 | B2 |
| 7174535 | Wragge | Feb 2007 | B2 |
| 7180475 | Slobodin et al. | Feb 2007 | B2 |
| 7230939 | Toyoshima | Jun 2007 | B2 |
| 7237046 | Paley et al. | Jun 2007 | B2 |
| 7239346 | Priddy | Jul 2007 | B1 |
| 7243153 | McIntyre et al. | Jul 2007 | B2 |
| 7260390 | Skinner | Aug 2007 | B1 |
| 7269668 | Redford et al. | Sep 2007 | B2 |
| 7318086 | Chang et al. | Jan 2008 | B2 |
| 7345347 | Ohkubo et al. | Mar 2008 | B2 |
| 7353416 | Jeansonne et al. | Apr 2008 | B2 |
| 7355732 | Yamaguchi | Apr 2008 | B2 |
| 7356347 | Kammer | Apr 2008 | B1 |
| 7370090 | Nakaoka et al. | May 2008 | B2 |
| 7484245 | Friedman et al. | Jan 2009 | B1 |
| 7577910 | Husemann et al. | Aug 2009 | B1 |
| 7580005 | Palin | Aug 2009 | B1 |
| 7609402 | Chang et al. | Oct 2009 | B2 |
| 7630721 | Ortiz | Dec 2009 | B2 |
| 7644018 | Yukie et al. | Jan 2010 | B1 |
| 7704147 | Quraishi et al. | Apr 2010 | B2 |
| RE41416 | Liu et al. | Jul 2010 | E |
| RE41487 | Liu et al. | Aug 2010 | E |
| RE41532 | Liu et al. | Aug 2010 | E |
| RE41689 | Liu et al. | Sep 2010 | E |
| 7805720 | Chang et al. | Sep 2010 | B2 |
| RE41882 | Liu et al. | Oct 2010 | E |
| 7908401 | Chang | Mar 2011 | B2 |
| 7941541 | Chang et al. | May 2011 | B2 |
| 7944577 | Chang et al. | May 2011 | B2 |
| 7953818 | Chang et al. | May 2011 | B2 |
| RE42725 | Chang et al. | Sep 2011 | E |
| RE42828 | Liu et al. | Oct 2011 | E |
| 8082491 | Abdelaziz et al. | Dec 2011 | B1 |
| 8082572 | Tilford | Dec 2011 | B1 |
| RE43181 | Liu et al. | Feb 2012 | E |
| 8166949 | Hicks et al. | May 2012 | B2 |
| 8169649 | Chang et al. | May 2012 | B2 |
| 8184324 | Chang et al. | May 2012 | B2 |
| 8285802 | Chang et al. | Oct 2012 | B2 |
| 8296757 | Chang et al. | Oct 2012 | B2 |
| 8332521 | Chang et al. | Dec 2012 | B2 |
| 8533352 | Chang | Sep 2013 | B2 |
| 8595717 | Chang et al. | Nov 2013 | B2 |
| 8630000 | Chang et al. | Jan 2014 | B2 |
| 8705097 | Chang et al. | Apr 2014 | B2 |
| 8711408 | Chang et al. | Apr 2014 | B2 |
| 8812398 | Kuhn et al. | Aug 2014 | B2 |
| 8964220 | Chang et al. | Feb 2015 | B2 |
| 8972610 | Chang | Mar 2015 | B2 |
| 8989064 | Chang et al. | Mar 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 |
| 9110622 | Chang et al. | Aug 2015 | B2 |
| 9116723 | Chang et al. | Aug 2015 | B2 |
| 9164718 | Chang et al. | Oct 2015 | B2 |
| 9298407 | Chang et al. | Mar 2016 | B2 |
| 9383956 | Chang et al. | Jul 2016 | B2 |
| 9389822 | Chang et al. | Jul 2016 | B2 |
| 9798516 | Chang et al. | Oct 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 |
| 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 |
| RE48066 | Liu et al. | Jun 2020 | E |
| RE48088 | Liu et al. | Jul 2020 | E |
| 10740066 | Chang et al. | Aug 2020 | B2 |
| 10761791 | Chang et al. | Sep 2020 | B2 |
| 10768871 | Chang et al. | Sep 2020 | B2 |
| 10841798 | Chang et al. | Nov 2020 | B2 |
| 10846031 | Chang et al. | Nov 2020 | B2 |
| 10860290 | Chang et al. | Dec 2020 | B2 |
| 10866773 | Chang et al. | Dec 2020 | B2 |
| 10873856 | Chang et al. | Dec 2020 | B2 |
| 10915296 | Chang et al. | Feb 2021 | B2 |
| 10963169 | Chang et al. | Mar 2021 | B2 |
| 11029903 | Chang et al. | Jun 2021 | B2 |
| 11204729 | Chang et al. | Dec 2021 | B2 |
| 20010029531 | Ohta | Oct 2001 | A1 |
| 20010032254 | Hawkins | Oct 2001 | A1 |
| 20020002707 | Ekel et al. | Jan 2002 | A1 |
| 20020010756 | Oku | Jan 2002 | A1 |
| 20020012329 | Atkinson | Jan 2002 | A1 |
| 20020013730 | Bigus | Jan 2002 | A1 |
| 20020026492 | Fujita | Feb 2002 | A1 |
| 20020032855 | Neves et al. | Mar 2002 | A1 |
| 20020049580 | Kutaragi et al. | Apr 2002 | A1 |
| 20020051200 | Chang et al. | May 2002 | A1 |
| 20020058499 | Ortiz | May 2002 | A1 |
| 20020065098 | Hosogaya | May 2002 | A1 |
| 20020065872 | Genske et al. | May 2002 | A1 |
| 20020078161 | Cheng | Jun 2002 | A1 |
| 20020078367 | Lang | Jun 2002 | A1 |
| 20020081993 | Toyoshima | Jun 2002 | A1 |
| 20020083151 | Adams | Jun 2002 | A1 |
| 20020083430 | Kusuda et al. | Jun 2002 | A1 |
| 20020091843 | Vaid | 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 |
| 20020101515 | Yoshida | Aug 2002 | A1 |
| 20020108054 | Moore et al. | Aug 2002 | A1 |
| 20020145632 | Shmueli | Oct 2002 | A1 |
| 20020147912 | Shmueli et al. | Oct 2002 | A1 |
| 20020169960 | Iguchi | Nov 2002 | A1 |
| 20020174254 | Kita et al. | Nov 2002 | A1 |
| 20020178295 | Buczek et al. | Nov 2002 | A1 |
| 20030028481 | Flitcroft et al. | Feb 2003 | A1 |
| 20030028797 | Long et al. | Feb 2003 | A1 |
| 20030046447 | Kouperchliak et al. | Mar 2003 | A1 |
| 20030084256 | McKee | May 2003 | A1 |
| 20030087601 | Agam et al. | May 2003 | A1 |
| 20030110371 | Yang | Jun 2003 | A1 |
| 20030110372 | Proudler | Jun 2003 | A1 |
| 20030112975 | Taiwanese | Jun 2003 | A1 |
| 20030120754 | Muto | Jun 2003 | A1 |
| 20030122934 | Shiohara | Jul 2003 | A1 |
| 20030126298 | Redford | Jul 2003 | A1 |
| 20030160993 | Kang | Aug 2003 | A1 |
| 20030161193 | Moran | Aug 2003 | A1 |
| 20030182456 | Lin et al. | Sep 2003 | A1 |
| 20030196007 | Baron | Oct 2003 | A1 |
| 20030200372 | Doragh et al. | Oct 2003 | A1 |
| 20030208629 | Parkman | Nov 2003 | A1 |
| 20030212862 | James | Nov 2003 | A1 |
| 20030225971 | Oishi | Dec 2003 | A1 |
| 20040001088 | Stancil | Jan 2004 | A1 |
| 20040006648 | Kita et al. | Jan 2004 | A9 |
| 20040010653 | Grundy | Jan 2004 | A1 |
| 20040015709 | Chen et al. | Jan 2004 | A1 |
| 20040024688 | Bi et al. | Feb 2004 | A1 |
| 20040057075 | Stewart | Mar 2004 | A1 |
| 20040070379 | Koretsky et al. | Apr 2004 | A1 |
| 20040078708 | Li et al. | Apr 2004 | A1 |
| 20040095382 | Fisher et al. | May 2004 | A1 |
| 20040127254 | Chang | Jul 2004 | A1 |
| 20040177355 | Wragge | Sep 2004 | A1 |
| 20040193900 | Nair | Sep 2004 | A1 |
| 20040199909 | Goodman | Oct 2004 | A1 |
| 20040203694 | Wong et al. | Oct 2004 | A1 |
| 20050005149 | Hirota et al. | Jan 2005 | A1 |
| 20050005263 | Miyazaki | Jan 2005 | A1 |
| 20050014534 | Hareng et al. | Jan 2005 | A1 |
| 20050055690 | Cornillon et al. | Mar 2005 | A1 |
| 20050059380 | Tomita | Mar 2005 | A1 |
| 20050246436 | Day et al. | Nov 2005 | A1 |
| 20050250536 | Deng | Nov 2005 | A1 |
| 20060080517 | Brown | Apr 2006 | A1 |
| 20060112414 | Ikonen et al. | May 2006 | A1 |
| 20060173980 | Kobayashi et al. | Aug 2006 | A1 |
| 20070038724 | Toyoshima | Feb 2007 | A1 |
| 20070081486 | Koide | Apr 2007 | A1 |
| 20070240154 | Gerzymisch et al. | Oct 2007 | A1 |
| 20070288611 | Serceki et al. | Dec 2007 | A1 |
| 20080003947 | Morris | Jan 2008 | A1 |
| 20080049740 | Serceki et al. | Feb 2008 | A1 |
| 20080071935 | Ohta | Mar 2008 | A1 |
| 20080126628 | Mullis et al. | May 2008 | A1 |
| 20090048978 | Ginter et al. | Feb 2009 | A1 |
| 20090182903 | Tordera | Jul 2009 | A1 |
| 20090198839 | Banerjee et al. | Aug 2009 | A1 |
| 20090210868 | Parthasarathy | Aug 2009 | A1 |
| 20100174631 | Tian et al. | Jul 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 |
| 20110035682 | Chang et al. | Feb 2011 | A1 |
| 20110138378 | Chang | Jun 2011 | A1 |
| 20110167166 | Chang | Jul 2011 | A1 |
| 20110167175 | Chang | Jul 2011 | A1 |
| 20110211226 | Chang et al. | Sep 2011 | A1 |
| 20110279829 | Chang et al. | Nov 2011 | A1 |
| 20120096451 | Tenbarge et al. | Apr 2012 | A1 |
| 20120230315 | Chang et al. | Sep 2012 | A1 |
| 20120258700 | Chang et al. | Oct 2012 | 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 |
| 20130111459 | Nakamoto | May 2013 | A1 |
| 20140018130 | Chang | Jan 2014 | A1 |
| 20140082604 | Chang et al. | Mar 2014 | 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 |
| 20160011836 | Chang et al. | Jan 2016 | A1 |
| 20160174068 | Chang et al. | Jun 2016 | A1 |
| 20160239232 | Chang et al. | Aug 2016 | A1 |
| 20160239243 | Chang et al. | Aug 2016 | A1 |
| 20160313974 | Chang et al. | Oct 2016 | 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 |
| 20170185376 | Chang et al. | Jun 2017 | A1 |
| 20170228202 | Chang et al. | Aug 2017 | A1 |
| 20170242649 | Jarvis et al. | Aug 2017 | A1 |
| 20170249116 | Chang et al. | Aug 2017 | A1 |
| 20170277487 | Chang et al. | Sep 2017 | A1 |
| 20170286027 | Chang et al. | Oct 2017 | A1 |
| 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 |
| 20180203647 | Chang | Jul 2018 | A1 |
| 20180203648 | Chang | Jul 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 |
| 20190250883 | Chang et al. | Aug 2019 | A1 |
| 20190272148 | Chang et al. | Sep 2019 | A1 |
| 20190303100 | Chang et al. | Oct 2019 | A1 |
| 20190384547 | Chang et al. | Dec 2019 | A1 |
| 20200097225 | Chang et al. | Mar 2020 | A1 |
| 20200225889 | Chang et al. | Jul 2020 | A1 |
| 20210055891 | Chang et al. | Feb 2021 | A1 |
| 20210165632 | Chang et al. | Jun 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 1345497 | Apr 2002 | CN |
| 19846452 | Dec 1999 | DE |
| 0473987 | Mar 1992 | EP |
| 1072976 | Jan 2001 | EP |
| 2357663 | Jun 2001 | GB |
| 9526703 | Oct 1995 | WO |
| 9843433 | Oct 1998 | WO |
| 0002358 | Jan 2000 | WO |
| 0006904 | Feb 2000 | WO |
| 0024192 | Apr 2000 | WO |
| 0044119 | Jul 2000 | WO |
| 0125870 | Apr 2001 | WO |
| 0142894 | Jun 2001 | WO |
| WO0241118 | May 2002 | WO |
| 03015641 | Feb 2003 | WO |
| WO2004093149 | Oct 2004 | WO |
| Entry |
|---|
| World Intellectual Property Organization (Thomas C. Lee, authorized officer);International Search Report for PCT/US20041011372; mailed Jun. 20, 2007; 3 pages. William Ho Chang is an inventor for both PCT/US2004/011372 and U.S. Appl. No. 10/734,481. |
| WIPO (Ellen Moyse and Thomas C. Lee, authorized officers);International Preliminary Report on Patentablity and Written Opinion for PCT/US2004/011372; mailed Aug. 14, 2007; 8 pages. William Ho Chang is an inventor for both PCT/US2004/011372 and U.S. Appl. No. 10/734,481. |
| WIPO (Jason D. Cardone, authorized officer; International Search Report for PCT/US2003/039547; mailed Jul. 15, 2005; 4 pages. William Ho Chang is an inventor for both PCT/US2003/039547 and U.S. Appl. No. 10/734,481. |
| Wiener et al; “Meeting USB and IEEE1394 Overcurrent Protection Requirements Using PolySwitch Devices”; Wescon/97 Conference Proceedings; IEEE Nov. 1997; pp. 442-475. |
| Remple; “USB On-The-Go Interface for Portable Devices”; Consumer Electronics, ICCE 2003 IEEE International Conference; IEEE Jun. 2003; pp. 8-9. |
| Jankovec et al; “Analog Circuit Development System”; EUROCON 2003, Computer as a Tool, The IEEE Region 8; IEEE, Sep. 2003; vol. 1 pp. 125-129. |
| 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. |
| David, Jon, “Security in a Flash,” Computers & Security, Jan. 1, 2003, vol. 22, No. 1, pp. 29-33, Elsevier Science Publishers, Amsterdam, NL. |
| US Receiving Office, International Search Report regarding PCT Application No. PCT/US01/48057, Jan. 6, 2003, 1 page. |
| US Receiving Office, International Preliminary Examination Report regarding PCT Application No. PCT/ US01/48057, Aug. 24, 2004, 11 pages. |
| Attiaoui et al., “Conception of Data Base Management System in USB Smart Card Flash Memory: Application for the Cancer Pathology of Medical Information Systems,” SETIT 2005: 3rd International Conference: Sciences of Electronic Technologies of Information and Telecommunications, Mar. 27-31, 2005, pp. 1-7. |
| Tahir et al., “Analysis of AutoPlay Feature via the USB Flash Drives,” WCE 2008: Proceedings of the World Congress of Engineering, Jul. 2-4, 2008, pp. 1-4. |
| State Intellectual Property Office of the P.R.C., Office Action regarding Chinese Patent Application No. 200480016309.4, May 8, 2009, 10 pages. |
| European Patent Office, Office Action regarding European Patent Application No. 01985549.3, Oct. 26, 2010, 4 pages. |
| State Intellectual Property Office of the P.R.C., Office Action regarding Chinese Patent Application No. 200480016309.4, May 24, 2011, 11 pages. |
| State Intellectual Property Office of the P.R.C., Office Action regarding Chinese Patent Application No. 200480016309.4, Oct. 28, 2011, 6 pages. |
| European Patent Office, Office Action regarding European Patent Application No. 04759486.6, Dec. 23, 2011, 11 pages. |
| US Patent and Trademark Office; Office Action for U.S. Appl. No. 10/823,513; Feb. 8, 2007; 15 pages. |
| USPTO; Office Action for U.S. Appl. No. 10/823,513; Oct 31, 2007; 22 pages. |
| USPTO; Office Action for U.S. Appl. No. 10/823,513; Dec, 29, 2008; 21 pages. |
| USPTO; Office Action for U.S. Appl. No. 10/823,513; Dec, 17, 2009; 22 pages. |
| USPTO; Notice of Allowance for U.S. Appl. No. 10/823,513; Jun, 1, 2010; 10 pages. |
| USPTO; Notice of Allowance for U.S. Appl. No. 12/890,847; Jun. 20, 2012; 10 pages. |
| USPTO; Notice of Allowance for U.S. Appl. No. 12/891,594; Jan. 18, 2013; 11 pages. |
| USPTO; Office Action for U.S. Appl. No. 10/734,848; Sep. 2, 2008; 31 pages. |
| USPTO; Notice of Allowance for U.S. Appl. No. 10/734,848; Oct. 28, 2010; 20 pages. |
| Tahir et al., “Analysis of Autoplay Feature via the USB Flash Drives”, Proceedings of the World Congress on Engineering, Jul. 2-4, 2008, vol. I, pp. 1-4. |
| Jebarajan et al., “A Method for Designing a Operating System for Plug and Play Bootstrap Loader USB Drive”, International Journal of Computer Science, Jan. 2011, vol. 8, Issue 1, pp. 295-301. |
| US Patent and Trademark Office, Office Action regarding U.S. Appl. No. 13/047,672, Jan. 20, 2012, 58 pages. |
| US Patent and Trademark Office, Office Action regarding U.S. Appl. No. 13/047,674, Mar. 14, 2012, 38 pages. |
| US Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/891,594, Jul. 5, 2012, 56 pages. |
| US Patent and Trademark Office, Office Action regarding U.S. Appl. No. 13/047,672, Nov. 6, 2012, 34 pages. |
| US Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 13/047,674, Nov. 6, 2012, 22 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/047,672, Dec. 24, 2013, 21 pages. |
| U.S. Patent and Trademark Office; Office Action regarding U.S. Appl. No. 14/021,974; mailing date Nov. 22, 2013; 16 pages. |
| U.S. Patent and Trademark Office; Office Action regarding U.S. Appl. No. 13/047,672; mailing date Aug. 1, 2013; 25 pages. |
| European Patent Office, Office Action for European Patent Application No. 04759486.6, Mar. 14, 2014, 3 pages. |
| Ray Geroski, Take your data anywhere with these four USB miniature storage devices, Sep. 23, 2002, 6 pages. |
| Ed Roth, Storage in a Flash, Dec. 15, 2002, 4 pages. |
| M-Systems Inc., Mobile DiskOnChip Plus 32/64MByte, Flash Disk with Protection and Security-Enabling Features, 2002, 50 pages. |
| State Intellectual Property Office of the P.R.C., Office Action for Chinese Patent Application No. 200480016309.4, Aug. 5, 2013, 18 pages. |
| European Patent Office, Office Action for European Patent Application No. 04759486.6, Jan. 8, 2014, 14 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 10/734,484, Sep. 2, 2008, 44 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/734,484, Oct. 28, 2010, 57 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/890,487, Jun. 20, 2012, 10 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/891,594, Jul. 22, 2013, 26 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 14/021,974, May 16, 2014, 47 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/047,672, Jun. 25, 2014, 30 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/047,674, Apr. 29, 2013, 15 pages. |
| State Intellectual Property Office of the P.R.C., Office Action Regarding Chinese Patent Application No. 200480016309.4, Apr. 3, 2014, 14 pages. |
| European Patent Office, Office Action for European Patent Application No. 04759486.6, May 22, 2014, 43 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/021,974, dated Sep. 9, 2014, 17 pages. |
| United States Patent and Trademark Office, Office Action for U.S. Appl. No. 14/089,622, dated Oct. 6, 2014, 101 pages. |
| United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/047,672, dated Oct. 17, 2014, 33 pages. |
| State Intellectual Property Office of the P.R.C., Office Action Regarding Chinese Patent Application No. 200480016309.4, dated Sep. 29, 2014, 17 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 14/021,974, dated Dec. 19, 2014, 24 pages. |
| Herman D'Hooge, The Communicating PC, Apr. 1996, 7 pages, IEEE Communication Magazine. |
| Tony K.P. Wong, An Embedded Chip for USB Application: from the Architecture to Implementation, 1999, 10 pages, International IC. |
| E. V. Vetvitskii et al., Use of the USB Universal Serial Bus in Computer Medical Systems, 2000, 6 pages, vol. 34, No. 4, Biomedical Engineering. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 14/089,622, dated Mar. 24, 2015, 44 pages. |
| United States Patent and Trademark Office, Supplemental Notice of Allowability for U.S. Appl. No. 14/089,622, dated Apr. 29, 2015, 16 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/835,585, dated Oct. 4, 2018, 33 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/042,051, dated Sep. 28, 2018, 14 pages. |
| U.S. Patent and Trademark Office, Office Action Regarding U.S. Appl. No. 15/042,051; dated Dec. 28, 2017; 58 pages. |
| U.S. Patent and Trademark Office, Office Action Regarding U.S. Appl. No. 15/042,044; dated Jan. 11, 2018; 55 pages. |
| U.S. Patent and Trademark Office, Office Action Regarding U.S. Appl. No. 14/835,585; dated Mar. 20, 2018; 96 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/835,585, dated Feb. 14, 2019, 37 pages. |
| Notice of Allowance prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/042,051, dated Feb. 26, 2019, 68 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/042,044, dated Jul. 20, 2020, 22 pages. |
| Final Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/835,585, dated Aug. 22, 2019, 47 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/835,585, dated Jun. 5, 2020, 65 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 16/518,727, dated May 15, 2020, 56 pages. |
| Office Action prepared by the United States Patent and Trademark Office for U.S. Appl. No. 15/042,044, dated Jan. 19, 2021, 21 pages. |
| Notice of Allowance prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 16/518,727, dated Nov. 6, 2020, 65 pages. |
| Corrected Notice of Allowability prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 16/518,727, dated Mar. 1, 2021, 9 pages. |
| Kindberg et al., “A Web Based Nomadic Computing System”, HP Laboratories, Palo Alto, CA; Aug. 24, 2000, 14 pages. |
| Bluetooth, Core, “Specification of the Bluetooth System,” Dec. 1, 1999, 1080 pages (attachments are in 4 parts). |
| “Part 11 Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” ANSI/IEEE Std. 802.11, 1999 Edition, 528 pages (attachments are in 2 parts). |
| Richard III, Golden G., “Service Advertisement and Discovery: Enabling Universal Device Cooperation” (IEEE Internet Computing Magazine, Sep./Oct. 2000), 9 pages. |
| Excerpts from Gerard O'Driscoll, The Essential Guide to Home Networking (Published 2000/ Reprinted 2001), 25 pages. |
| Axis Print Server Brochure (archived on Sep. 25, 2000, available at https://web.archive.org/web/20000925114525/http:/www.axis.com/ftp/pub/axis/data_sheets/npsds.pdf), 4 pages. |
| Excerpts from UPnP Forum Connections Newsletter, Third Quarter 2000 (archived on Aug. 16, 2000, available at https://web.archive.org/web/20000816073400/http://upnp.org/newsletter/default.htm, https://web.archive.org/web/20000818105427/http://www.upnp.org/newsletter/devtools.htm), 6 pages. |
| Excerpts from Bluetooth Core Specification v1.0 B (Dec. 1, 1999), 60 pages. |
| Excerpts from Roy Hoffman, Data Compression in Digital Systems (1997), 189 pages. |
| Excerpts from Michael Miller, The Complete Idiot's Guide to Home Theater Systems (2000), 58 pages. |
| Awduche, Daniel O. “On Resource Discovery Systems with Mobile Hosts” (1996), 6 pages. |
| IEEE Standard for Information Technology—Transport Independent Printer/System Interface (TIP/SI) (1997), 124 pages. |
| Macintosh PowerBook User's Manual (1998), 94 pages. |
| Setting Up Your PowerBook (2000), 80 pages. |
| Wright, “Design Goals for an Internet Printing Protocol,” Apr. 1999, 43 pages. |
| Office Action prepared by the United States Patent and Trademark Office for U.S. Appl. No. 15/042,044, dated Jun. 24, 2021, 28 pages. |
| United States Patent and Trademark Office; Office Action dated Aug. 5, 2022 for U.S. Appl. No. 15/042,044; 27 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20040127254 A1 | Jul 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60433196 | Dec 2002 | US |
