Wireless communication system

- Apple

A processing system is described that includes a wireless communication interface that wirelessly communicates with one or more wireless client devices in the vicinity of an establishment. The wireless communication interface receives a remote order corresponding to an item selected by at least one of the wireless client devices. A local server computer located in proximity to the establishment generates instructions for processing the remote order received from the wireless communication interface. The local server computer then passes the processing instructions to an order processing queue in preparation for processing of the remote order.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/760,479, filed Apr. 14, 2010 now U.S. Pat. No. 8,072,956, and entitled “WIRELESS COMMUNICATION SYSTEM,” which is hereby incorporated by reference herein, which in turn is a continuation of U.S. patent application Ser. No. 11/485,142, filed Jul. 11, 2006 now U.S. Pat. No. 7,724,716, and entitled “WIRELESS COMMUNICATION SYSTEM,” which is hereby incorporated by reference herein, and which in turn claims priority to U.S. Provisional Patent Application No. 60/805,328, filed Jun. 20, 2006, and entitled “WIRELESS COMMUNICATION SYSTEM,” which is hereby incorporated by reference herein.

FIELD OF INVENTION

This invention relates generally to personal, portable electronic devices such as media players, radios, cell phones and the like.

DESCRIPTION OF RELATED ART

Recent developments in consumer electronics have included the introduction of portable personal communication devices such as media players (such as MP3 players, minidisk players), cell phones, personal digital assistants (PDAs) and the like. In the case of a cell phone, a user can communicate by voice, text, or other multimedia data. For example, a cell phone user can send a text message by means of any number of communication protocols such as the Short Message Service—Point to Point (SMS-PP) protocol (defined in GSM recommendation 03.40). Using SMS-PP, messages are sent via a store-and-forward mechanism to a Short Message Service Center (SMSC), which will attempt to send the message to the recipient and possibly retry if the user is not reachable at a given moment.

Using a cell phone or other such device to remotely enter into a commercial transaction (such as food or drink ordering) is widespread and well understood. However, in order to initiate such a remote transaction using a cell phone, a user must be aware that a merchant of interest is nearby, must be aware of a list of available items for purchase by the merchant, must be aware of a price for each item, etc. Even in those cases where all the relevant knowledge is available and known, the user must then pay for the services or goods purchases. In some cases, the user must use a credit or debit card by repeating very sensitive information in a voice loud enough to be heard and understood over the phone, or enter the information manually if speaking is not an option. In some cases, if the merchant does not accept the particular payment method, the customer must pay using cash thereby eliminating most, if not all, of the perceived efficiencies of remotely ordering using the cell phone, PDA, media player, etc.

In any case, once the transaction is entered into, the customer order is then queued up in, typically, a first in first out order without distinguishing if the order was placed locally or remotely. In this way, a remote purchaser has only an approximate idea of a time to actually retrieve the order. This can result in an annoying wait in a long queue if the purchaser arrives before completion of the order. In the case of a food and/or drink purchase, a hot drink such as coffee is picked up in a tepid state if the purchaser arrives substantially after the ordered hot drink is ready for pickup.

Therefore, there is a need for improved approaches to process a remote order.

SUMMARY OF THE INVENTION

A processing system is described that includes a wireless communication interface that wirelessly communicates with one or more wireless client devices in the vicinity of an establishment. The wireless communication interface receives a remote order corresponding to an item selected by at least one of the wireless client devices. A local server computer located in proximity to the establishment receives the remote order from the wireless communication interface and generates instructions for processing the remote order. The local server computer then passes the processing instructions to an order processing queue in preparation for processing of the remote order.

In one embodiment, an acknowledgement is forwarded to the originating wireless client device indicating that the remote order has been successfully received. Furthermore, an estimate order completion time can then visually displayed by the wireless client device and/or audibly rendered by way of a speaker or earphone.

In another embodiment, a method can order an item from an establishment using a wireless client device in the vicinity of the establishment. The method can, for example, perform the operations of: presenting, on a display screen of the wireless client device, an item ordering user interface provided that the wireless client device is located proximate to the establishment; receiving, at the wireless client device, a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface; forming, at the wireless client device, a remote order request for the particular item in response to the user selection; wirelessly sending the remote order request to a computing device associated with the establishment; wirelessly receiving, at the wireless client device, a notification from the computing device associated with the establishment; and presenting the notification on the display screen of the wireless client device.

In another embodiment, a non-transitory computer readable medium can include at least computer program code that when executed by a wireless client device provides for ordering an item from an establishment, The computer program code provided on the computer readable medium includes at least: computer program code for presenting, on a display screen of the wireless client device, an item ordering user interface provided that the wireless client device is located proximate to the establishment; computer program code for receiving, at the wireless client device, a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface; computer program code for forming, at the wireless client device, a remote order request for the particular item in response to the user selection; computer program code for wirelessly sending the remote order request to a computing device associated with the establishment; computer program code for wirelessly receiving, at the wireless client device, a notification from the computing device associated with the establishment; and computer program code for presenting the notification on the display screen of the wireless client device.

In still another embodiment, a wireless portable electronic device can, for example, include at least: a processor for processing executable instructions; a display coupled to the processor for displaying text and images; a wireless interface coupled to the processor arranged to send and receive wireless signals; and a memory arranged to store data and the executable instructions. The executable instructions can, for example, include at least: computer program code for presenting, on the display of the wireless portable electronic device, an item ordering user interface provided that the wireless portable electronic device is located proximate to the establishment; computer program code for receiving a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface; computer program code for forming a remote order request for the particular item in response to the user selection; computer program code for sending, via the wireless interface, the remote order request to a computing device associated with the establishment; computer program code for receiving, via the wireless interface, a notification from the computing device associated with the establishment; and computer program code for presenting the notification on the display screen of the wireless client device.

Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood by reference to the following description taken in conjunction with the accompanying drawings.

FIG. 1 shows a portable media player according to one embodiment of the invention.

FIG. 2A is a block diagram of a wireless system according to one embodiment of the invention.

FIG. 2B is a block diagram of the wireless system shown in FIG. 2A suitably configured for receiving and processing a remote order from a wireless client device.

FIG. 3 shows a wireless communication system in accordance with an embodiment of the invention.

FIG. 4 illustrates the wireless mobile device implemented as a wireless media player in accordance with an embodiment of the invention.

FIG. 5 illustrates an example of the wireless media player receiving the ping signal from a recognized merchant in accordance with an embodiment of the invention.

FIG. 6 illustrates an example of the wireless media player receiving the ping signal from the recognized merchant in accordance with an embodiment of the invention.

FIG. 7 shows a updating a merchant status in accordance with an embodiment of the invention.

FIG. 8 illustrates a purchase transaction in accordance with an embodiment of the invention.

FIG. 9 illustrates authenticating a customer in accordance with an embodiment of the invention.

FIG. 10 illustrates dealing with a customer without sufficient funds in accordance with an embodiment of the invention.

FIG. 11 shows how once a transaction has been authenticated and authorized the merchant sends a purchase inquiry in accordance with an embodiment of the invention.

FIG. 12 shows a flowchart detailing a process for a wireless transaction in accordance with an embodiment of the invention.

FIG. 13 shows a flowchart detailing a process for determining if a wireless client device is within range of a wireless data network in accordance with an embodiment of the invention.

FIG. 14 shows a flowchart detailing a process for determining if a merchant is a recognized merchant or an unrecognized merchant in accordance with an embodiment of the invention.

FIG. 15 shows a flowchart detailing a process responding to a merchant in accordance with an embodiment of the invention.

FIG. 16 shows a flowchart detailing a process for responding to instruction for a recognized merchant in accordance with an embodiment of the invention.

FIG. 17 shows a flowchart detailing a process for processing a customer selection by a merchant in accordance with an embodiment of the invention.

FIG. 18 shows a flowchart detailing a process for authenticating a customer in accordance with an embodiment of the invention.

FIG. 19 shows a flowchart detailing a process for authorizing a customer to purchase the selected item(s) in accordance with an embodiment of the invention.

 DETAILED DESCRIPTION OF SELECTED EMBODIMENTS

Reference will now be made in detail to a particular embodiment of the invention, an example of which is illustrated in the accompanying drawings. While the invention will be described in conjunction with the particular embodiment, it will be understood that it is not intended to limit the invention to the described embodiment. To the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims.

Embodiments of the invention can provide a method, system, and apparatus for wirelessly executing a commercial transaction using a wireless client device such as a cell phone or wireless portable media player. When within wireless range of a participating merchant, at least one of a number of selectable items is selected for purchase. An indication of the selected item is then wirelessly forwarded to the participating merchant who confirms that there are sufficient financial resources available to the consumer to complete the transaction. The selected item(s) are then placed in a priority queue. In a particularly useful embodiment, a time for pickup is forwarded to the wireless consumer product and visually displayed by the wireless client device and/or audibly rendered by way of a speaker or earphone.

The invention will now be described in terms of a client device that includes a portable media player capable of storing a number of multimedia digital data files connected to a media delivery accessory arranged to broadcast audio by way of a plurality of speakers. In the case of the media player being a pocket sized portable player (such as the iPod® player manufactured by Apple Inc. of Cupertino, Calif.), the multimedia data files can include MP3 files as well as any other appropriately formatted data files. It should be noted that although the described embodiments rely upon using a wireless portable media player, any personal communication device (such as a text message enabled cell phone) can be used to practice the invention.

FIG. 1 shows a portable media player 100 according to one embodiment of the invention. The media player 100 includes a processor 102 that pertains to a microprocessor or controller for controlling the overall operation of the media player 100. The media player 100 stores media data pertaining to media assets in a file system 104 and a cache 106. The file system 104 is, typically, a storage disk or a plurality of disks. The file system 104 typically provides high capacity storage capability for the media player 100. However, since the access time to the file system 104 is relatively slow, the media player 100 can also include a cache 106. The cache 106 is, for example, Random-Access Memory (RAM) provided by semiconductor memory. The relative access time to the cache 106 is substantially shorter than for the file system 104. However, the cache 106 does not have the large storage capacity of the file system 104. Further, the file system 104, when active, consumes more power than does the cache 106. The power consumption is particularly important when the media player 100 is a portable media player that is powered by a battery (not shown). The media player 100 also includes a RAM 120 and a Read-Only Memory (ROM) 122. The ROM 122 can store programs, utilities or processes to be executed in a non-volatile manner. The RAM 120 provides volatile data storage, such as for the cache 106.

The media player 100 also includes a user input device 108 that allows a user of the media player 100 to interact with the media player 100. For example, the user input device 108 can take a variety of forms, such as a button, keypad, dial, etc. Still further, the media player 100 includes a display 110 (screen display) that can be controlled by the processor 102 to display information to the user. A data bus 124 can facilitate data transfer between at least the file system 104, the cache 106, and the processor 102. The media player 100 also includes a bus interface 116 that couples to a data link 118. The data link 118 allows the media player 100 to couple to a host computer over a wired connection.

In one embodiment, the media player 100 serves to store a plurality of media assets (e.g., songs) in the file system 104. When a user desires to have the media player 100 play a particular media item, a list of available media assets is displayed on the display 110. Then, using the user input device 108, a user can select one of the available media assets. The processor 102, upon receiving a selection of a particular media item, supplies the media data (e.g., audio file) for the particular media item to a coder/decoder (CODEC) 112. The CODEC 112 then produces analog output signals for a speaker 114. The speaker 114 can be a speaker internal to the media player 100 or external to the media player 100. For example, headphones or earphones that connect to the media player 100 would be considered an external speaker.

The media player 100 also includes a wireless network interface 126 arranged to wirelessly transmit any selected data from the media player 100 to any appropriately configured receiver unit over a wireless network. In the embodiment shown in FIG. 1, the wireless network interface 126 takes the form of a “WiFi” interface according to the IEEE 802.11b or 802.11g standards. Other wireless network standards could also be used, either in alternative to the identified standards or in addition to the identified standards. Such other network standards could include the IEEE 802.11a standard or the Bluetooth standard.

In one embodiment, the media player 100 is a portable computing device dedicated to processing media such as audio. For example, the media player 100 can be a media player (e.g., MP3 player), a game player, a remote controller, a portable communication device, and the like. These devices are generally battery-operated and highly portable so as to allow a user to listen to music, play games or video, record video or take pictures, communicate with others, and/or control other devices. In one implementation, the media player 100 is a handheld device that is sized for placement into a pocket or hand of the user. By being handheld, the media player 100 is relatively small and easily handled and utilized by its user. By being pocket sized, the user does not have to directly carry the device and therefore the device can be taken almost anywhere the user travels (e.g., the user is not limited by carrying a large, bulky and often heavy device, as in a portable computer). Furthermore, the device may be operated by the user's hands, no reference surface such as a desktop is needed.

Although the media items of emphasis in several of the above embodiments were audio items (e.g., audio files or songs), the media items are not limited to audio items. For example, the media item can alternatively pertain to recorded discussions and the like.

FIG. 2A is a block diagram of a wireless system 200 according to one embodiment of the invention. The system 200 includes a central server 202 and a wired data network 204. The central media server 202 couples to the wired data network 204. The wired data network 204 can be a global network, a wide area network, or a local area network. In one example, the wired data network 204 pertains to some portion of the World Wide Web. A personal computer 206 can couple to the wired data network 204. A wireless data network 208 can also couple to the wired data network 204. The wireless data network 208 can include one or more wireless data networks, such as cellular networks, WiFi networks, WiMAX networks, Bluetooth networks, etc. The wireless system 200 can also include a local server 210 that can couple to one or both of the wired data network 204 and the wireless data network 208.

The central server 202 stores or has access to numerous product data items. The local server 210 also stores or has access to various product data items. In addition, the system 200 supports a plurality of portable media devices 212 and 214. The portable media device 212 can couple to the wireless data network 208 over a wireless link 216. Similarly, the portable media device 214 can couple to the wireless data network 208 over a wireless link 218. In this regard, the portable media devices 212 and 214 can access the central media server 202 and/or the local server 210 via the wireless data network 208.

In one embodiment, one or more of the mobile devices, such as the mobile devices 212 and 214 illustrated in FIG. 3, can pertain to media devices. More particularly, the media devices can pertain to media players, such as the iPod® media player from Apple Inc. These mobile devices can include a purchase transaction management application that operates on the mobile device to facilitate a purchase transaction between the mobile device and a merchant with access to the servers 202 and/or 210. Given the portability of mobile devices, mobile devices are smaller and have less resources. Consequently, a purchase transaction management application designed for use on a mobile device may offer less features and capabilities than would a counterpart purchase transaction management application operating on a larger, more powerful computing device, e.g., a personal computer. Given that the mobile devices have wireless access to the local server 210 and/or the central server 202, the mobile devices can interact with the servers 202 and 210 to request and/or receive product data (or other data). In this regard, a purchase transaction management application operating on the mobile devices can communicate with the media servers 202 and 210 to perform various tasks, including: selecting items to purchase, receiving a periodic delivery of product content to media devices (such as daily pushing advertisements from a server to a media device), etc.

FIG. 2B is a block diagram of the wireless system 200 shown in FIG. 2A suitably configured for receiving and processing a remote order from a wireless client device. The system 200 includes the local server computer 210 located at an establishment 220 in wireless communication with the wireless data network 208 by way of a wireless communication interface 222. When the local server computer 210 receives a remote order 224 by way of the wireless communication interface 222, the local server computer 210 generates a tagged remote order entry 226 that determines an order of processing of the remote order 224. The tagged remote order entry 226 is, in turn, sent to and stored in a processing queue 228 that also receives any local order entries 230 from a local ordering system 232. In the described embodiment, the processing queue 228 is updated based upon whether or not a particular order entry is tagged. For example, if a local order entry is currently stored in the processing queue 228 and a next queue entry is a tagged order entry, then the tagged order entry takes priority over the local (untagged) order entry for processing by a local processing center 234. In this way, the establishment can prioritize, not, processing of remote orders over local orders as appropriate for pick up at a pick up station 236 when completed. In a particularly useful implementation, once the processing queue 228 has forwarded a next item to process command 238 to the local processing center 234, the local processing center 234 originates and forwards a notification of estimated time for completion of processing 240 to the wireless client device 216 by way of the wireless communication interface 222 and wireless data network 208.

FIG. 3 shows a wireless communication system 300 in accordance with an embodiment of the invention. The system 300 includes a wireless mobile device 302 capable of wireless communication with a wireless network 304 in communication with a local server computer 306 associated with a merchant 308. In the particular embodiment described, the merchant 308 primarily provides ready to eat comestibles (such as coffee, sandwiches, etc.) and any associated peripheral products (such as coffee grinders in the case of the merchant 308 being a purveyor of coffee and/or coffee products). In order to alert the wireless mobile device 302 that the wireless mobile device 302 is within range R of the wireless network 304, the wireless network 304 periodically emits a ping signal 310 that includes a merchant ID 312 that uniquely identifies the merchant 308. The ping signal 310 is arranged such that any compatible wireless mobile devices within the range R of the wireless network 304 will receive the ping signal 310 at a signal strength greater than a preset threshold value.

If the wireless mobile device 302 receives such a signal, then the wireless mobile device 302 responds (or not) to the wireless network 304 based upon any number of predetermined conditions set forth in a customer preference file 316 stored in a memory 318 in the wireless mobile device 302. For example, if the merchant ID 312 is identified as being associated with a recognized merchant (i.e., a merchant having had a previous transaction with a current user of the wireless mobile device), the wireless mobile device 302 will respond based upon a set of instructions included in the customer preference file 316 corresponding to a recognized merchant. Conversely, if the merchant ID 312 is identified as belonging to that of an unrecognized merchant (i.e., having had no previous transaction), the response is based upon another set of instructions associated with an unrecognized merchant.

FIG. 4 illustrates the wireless mobile device 302 implemented as a wireless media player 402 in accordance with an embodiment of the invention. When within the range R of wireless data network 304, the wireless media player 402 receives a ping signal 406 that includes a merchant ID 408 that uniquely identifies a merchant 410. A processor 412 in the wireless media player 402 receives the merchant ID 408 and sends a merchant ID recognition query 414 to a database 416 stored in a memory device 418 located in the media player 402. The database 416 includes a list of merchants 420 that are considered to be recognized by the user having a customer ID 422. In order to ascertain whether or not the merchant ID 408 is recognized, the merchant ID 408 is compared to the merchant IDs included in the list of merchants 420. If there is a hit (i.e., a match) the merchant 410 is considered to be recognized, otherwise the merchant 410 is considered to be unrecognized. In any case, once the status of the merchant 410 is determined, a fetch instruction command 422 is forwarded to a customer preference file 424 that responds by providing an instruction command 426 to the processor 412 based upon whether or not the merchant 410 is recognized.

The instruction command 426 (when executed by the processor 412) directs the wireless media player 402 to take a predetermined action in response to the received ping signal 406. For example, if the merchant 410 is unrecognized, a user can tailor the customer preference file 424 to issue an instruction command that directs the wireless media player 402 to ignore the ping signal 406. Alternatively, the user could tailor the customer preference file 424 to issue an instruction command to update the list of merchants 420 to include the unrecognized merchant ID 408 thereby changing the merchant status from unrecognized to recognized.

FIG. 5 illustrates an example of the wireless media player 402 receiving the ping signal 406 from a recognized merchant 502 in accordance with an embodiment of the invention. In this example, an instruction command 504 is issued from the customer preference file 424. The instruction command 504 is passed to and executed by the processor 412, which in turn directs the wireless media player 402 to open a graphical user interface (GUI) 506 on a display 508 that includes a list of items 510 previously purchased from the merchant 502 stored in the memory 418. In the described embodiment, each displayed item responds to a selection tool 512 by causing the wireless media player 402 to send a selection request 514 that includes an indication 516 of the item selected from the list 510 to the merchant 502 for additional processing. It should be noted that, typically, the list of items previously purchased by the user is stored locally in the memory 418. However, in some cases it may be desirable to store customer information (such as the list of previously purchased items) on either or both the local server 306 or the central server 202. In this way, even in those cases where a user purchases a new item or is using a different media player than would otherwise be used that does not have a current, or accurate, customer preference file for that particular user, the local server 306 or remote server 202 can be used to update, or synchronize, the local memory 418.

It should be noted that the customer preference file 424 can be as dense or sparse as desired based on, for example, an amount of on-board memory storage available, personal preferences of a user, etc. In some cases, the wireless media player 402 can have more than one user associated with it such as when two or more people share the wireless media player 402. In this case, each individual user would have a unique customer ID that would be entered manually by the user when they took current possession of the player 402. When multiple customer IDs are available, then each customer ID can point to a particular customer preference file unique to that customer ID.

In some cases, whenever a wireless media player comes within range of the wireless data network, the wireless media player can be (unbeknownst to the user) directed to send a wireless media player identifier that uniquely identifies the particular wireless media player to the wireless data network. The wireless media player identifier can be used to track lost or stolen media players when the rightful owner has placed the wireless media player identifier in a central database of lost or stolen media players. In this way, if a lost or stolen media player is tracked, any number of subsequent actions can be taken such as notifying the authorities, disabling the wireless media player, displaying a notice to return the wireless media player, etc. thereby providing a strong disincentive for stealing the player.

FIG. 6 illustrates an example of the wireless media player 402 receiving the ping signal 406 from the recognized merchant 502 in accordance with an embodiment of the invention. In this case, processor 412 directs the wireless media player 402 to generate and forward to the merchant 502 a request 602 with an instruction 604 that directs the merchant 502 to generate a merchant response 606 that includes information 608 that is pushed to the wireless media player 402. In this example, the information 608 is displayed on the graphical user interface (GUI) 506 as the list of previously purchased items 510 thereby providing the user the capability of selecting those item(s) from the list 510 along the lines previously discussed.

Therefore, by providing a simple modification to the customer preference file 424, any transaction between the merchant and the current user of the wireless media player 402 can be customized as appropriate. For example, if a user desires to enter into a transaction with only particular merchants, then only those merchants whose merchant IDs are stored in the customer preference file will be allowed to open a channel with the user. Alternatively, some customers may prefer that no merchant advertisements can be forwarded whereas in some cases, the user may prefer advertisements but only for a limited number of products. By tailoring the customer preference file for each customer and merchant, the user can provide as much control as desired in the information provided from and/or to a particular merchant or merchant class (i.e. category of merchants, such as food providers, etc).

In yet another scenario shown in FIG. 7, a merchant 702 is unrecognized. In this case, the media player 402 uses a merchant ID 704 included in a ping signal 706 to update the list of merchants 420 thereby changing the status of the merchant 702 from unrecognized to recognized. In this particular embodiment, once the list of merchants 420 has been updated to include the merchant ID 704, the wireless media player 402 sends a media player response 708 with an acknowledgement 710 of the receipt of the ping signal 706 to the merchant 702. In some cases, in addition to the acknowledgment 710, the media player response 708 can include a merchant request 712 requesting that the merchant 702 send any information, such as advertisements, daily specials, or other enticements that the merchant 702 believes would induce the user to place an order. In this way, the newly recognized merchant 702 can provide the database 416 with information specific to the merchant 702 so as to facilitate a current or future transaction.

FIG. 8 illustrates a purchase transaction 800 in accordance with an embodiment of the invention. It should be noted that the list of selectable items 510 can originate from the memory 418, the local server 308 or the central server 202. Accordingly, starting where FIG. 5 left off where a user has selected an item to purchase from the list of selectable items 510, the wireless media player 402 sends the purchase request 514 having the purchase item indicator 516, the customer ID 422, and an authentication code 802 to the merchant 502. As illustrated in FIG. 9, the merchant 502 then proceeds to authenticate the customer ID 422 associated with the purchase request 514 by verifying the authentication code 802. If the purchase request 514 did not have an authentication code 802 associated with it (i.e., a null field), then the merchant 502 sends an authentication request 902 back to the wireless media player 402. The wireless media player 402 then displays an authentication request icon 904 on the display 508 requesting that the user provide a predetermined authentication code. In some cases, the authentication code can be a pre-selected number, name, combination of words and numbers, or any such combination. In response to the authentication request 902, the user inputs the appropriate authentication code 802, which is then forwarded back to the merchant 502 by the wireless media player 402 by way of an authentication response 906. Once the merchant 502 has received the authentication code 802, the merchant 502 forwards an authentication code verification request 908 to the local computer 306 (or the remote computer 202), which responds with an authentication code status 910. If the authentication code 802 is not verified, then a cancellation notice 912 is forwarded back to the wireless media player 402 canceling the transaction, otherwise, if the authentication code 802 is verified, the merchant 502 is allowed to proceed with the transaction 800.

Referring back to FIG. 8, if the authentication code 802 is verified, then an account enquiry 804 is made of a user account 806 associated with the customer ID 422 to determine if there is sufficient funds in the user account 806 to complete the requested purchase transaction 800. Again, the user account 806 can be stored in either the local computer 306 or the central server 202, thereby providing redundancy. Referring to FIG. 10, if the user account 806 does not have sufficient funds, then any number of actions can be taken. In one case, if the user has preauthorized access to another source of funds 1002 (such as a checking or savings account) located in a bank 1004, for example, then a request 1006 is forwarded to the bank 1004 to access the preauthorized source of funds 1002 from which a predetermined amount 1008 is transferred to the user account 806. If the preauthorized source of funds 1002 is either unavailable or insufficient to cover the predetermined transfer amount, then a cancellation notice 1010 is forwarded back to the wireless media player 402. In another embodiment, instead of a cancellation notice 1010, a request 1012 is forwarded to the wireless media player 402 requesting the user manually input a credit card number (either in written form using an input icon 1014, or verbally using a microphone 1016), for example, to cover the transaction. This could also apply in those situations where the user does not have a preauthorized account from which to draw additional funds when needed to replenish the user account.

In some cases, the user can direct that the user account 806 never fall below a specified amount thereby eliminating the possibility of a transaction being cancelled for lack of funds. In some cases, a notice can be forwarded to the wireless media player 402 indicating that the user account 806 has fallen to a preselected amount and requesting that the user either replenish the account or authorize a transfer from the preauthorized source of funds 1002.

Referring to FIG. 11, once the transaction 800 has been authenticated and authorized, the merchant 502 sends a purchase inquiry 1102 to a database 1104 (that can also be located on the central server 202) that includes a customer information file 1106 having information specific to the customer ID 422 and merchant information 1108 (based upon merchant IDs). The customer information file 1106 can include such information as customer purchase history, customer product preferences (coffee with room for cream, for example), etc.; whereas the merchant information 1108 can include such information as current menu items, specialty menu items, and any other information that a particular merchant deems relevant. Using the information included in the customer preference file 1106, a processing queue 1110 is updated to include the item(s) purchased and any particular customer preferences (such as room for cream, particular temperature if its a hot drink, etc.). Once the processing queue 1110 has been updated, the merchant 502 sends a purchase confirmation 1112 having information 1114 related to the purchase that is displayed on the display 508. Such information can include an estimate of the time for pickup in either textual or iconic form (such as a clock face), the item ordered, the price, and any other information that the merchant 502 deems appropriate. In some situations, the user can specify a particular time to pick up the selected items as opposed to the merchant 502 specifying the pick up time. In some cases, the merchant may decide to give a remote purchaser priority over those who purchased the same or similar items locally at the merchant's place of business. In any case, once the user has the verification notification and estimated time for pickup, the user can go directly to the pickup station at the merchant without having to waste time waiting for an unfinished order or arriving after a order has been finished and has lost its freshness.

FIG. 12 shows a flowchart detailing a process 1200 for a wireless transaction in accordance with an embodiment of the invention. At 1200, if a user having a wireless client device is within wireless range of a merchant and if the user wants to purchase an item for sale by the merchant at 1204, then the user selects the item to purchase using the wireless client device at 1206. An indication of the item selected is wirelessly forwarded to the merchant at 1208 and an order queue is subsequently updated at 1210. Once the order queue has been updated, a notification is sent from the merchant to the wireless client device at 1212 notifying the user that the selected item has been queued up. In some embodiments, the notification includes more specific information related to the transaction such as a time for pickup, etc. At 1214, the user picks up the selected item at the merchant thereby completing the wireless transaction.

FIG. 13 shows a flowchart detailing a process 1300 for determining if a wireless client device is within range of a wireless data network in accordance with an embodiment of the invention. The process 1300 begins at 1302 with the wireless data network emitting a ping signal. At 1304, the wireless client device receives the ping signal having a signal strength S. If, at 1306, the signal strength S is greater than a predetermined signal strength value, then at 1308 the wireless client device is within range of the wireless data network.

FIG. 14 shows a flowchart detailing a process 1400 for determining if a merchant is a recognized merchant or an unrecognized merchant in accordance with an embodiment of the invention. The process 1400 begins at 1402 by retrieving a merchant ID from the received ping signal and, at 1404, determining if the merchant ID is associated with a previously recognized merchant or an unrecognized merchant. If the merchant ID is associated with a previously recognized merchant, then at 1406, an instruction for a previously recognized merchant is fetched from a customer preference file and the fetched instruction is executed at 1408.

On the other hand, if it had been determined at 1404 that the merchant ID is associated with an unrecognized merchant, then at 1410 an instruction associated with an unrecognized merchant is fetched from the customer preference file at 1412 and executed at 1414.

FIG. 15 shows a flowchart detailing a process 1500 of responding to a merchant in accordance with an embodiment of the invention. The process 1500 begins at 1502 by determining if the wireless client device is to remain in communication with the unrecognized merchant. If it is determined that communication is to cease, then the unrecognized merchant is ignored at 1504 and the process 1500 stops, otherwise, the unrecognized merchant is recognized at 1506. In the described embodiment, the recognition of the heretofore unrecognized merchant can be accomplished by updating the customer preference file to include the merchant ID associated with the heretofore unrecognized merchant. At 1508, an instruction associated with the newly recognized client is executed that can include requesting specific merchant information from the merchant such as a list of current menu items that is, in turn, used to update a merchant information file and the customer preference file stored in the wireless client device.

FIG. 16 shows a flowchart detailing a process 1600 for responding to an instruction from a recognized merchant in accordance with an embodiment of the invention. The process 1600 begins at 1602 by getting a list of selectable items from either the merchant or from the wireless client device. In the case that the list of selectable items is from the wireless client device, a database stored in the wireless client device is accessed at 1604 which includes a list of previously purchased items. The merchant ID associated with the merchant is then compared to those merchant IDs included in the list of previously purchased items at 1606 and, at 1608, the list of previously purchased items that are associated with the stored merchant ID that matches the current merchant ID are displayed on a display.

On the other hand, when the list of selectable items is obtained from the merchant, then at 1610 a database stored in the wireless data network is accessed, which includes a list of purchased items associated with a customer ID that uniquely identifies a previous customer. At 1612, a list of stored customer IDs is compared with the current customer ID and at 1614, the list of selectable items associated with the stored customer ID that matches the current customer ID is sent from the wireless data network to the wireless client device. The list of selectable items is then displayed at 1608.

FIG. 17 shows a flowchart detailing a process 1700 for processing a customer selection by a merchant in accordance with an embodiment of the invention. The process 1700 begins at 1702 with the merchant receiving a customer selection request that includes an indication of the item(s) selected, an authentication code, and a customer ID. At 1704, the customer is authenticated and at 1706 the customer is authorized to purchase the selected item(s). At 1708 a processing queue is updated to include indicators of the selected item(s). At 1710, an estimate of an amount of time required to make the selected item(s) available for pickup is calculated.

FIG. 18 shows a flowchart detailing a process 1800 for authenticating a customer in accordance with an embodiment of the invention. The process 1800 begins at 1802 by determining if a customer authentication code is valid. If the authentication code is not valid, then a determination is made at 1804 of whether or not the customer is to be requested to supply a valid authentication code. If the customer is not requested to supply a valid authentication code, then the customer is tagged as unauthenticated at 1806 and the transaction is ended at 1808 thereby ending the process 1800. On the other hand, if at 1804 the customer is requested to supply a valid authentication code, then at 1810, an authentication code request is forwarded to the customer at the wireless client device and control is passed back to 1802 for a determination of the validity of the authentication code. If the received authentication code is determined to be valid at 1802, then at 1812, the customer is tagged as authenticated and control passes back to the process 1700.

FIG. 19 shows a flowchart detailing a process 1900 for authorizing a customer to purchase the selected item(s) in accordance with an embodiment of the invention. The process 1900 begins at 1902 by determining if the customer has a valid customer account. If the customer does not have a valid customer account, then at 1904 a request is forwarded from the wireless data network to the customer requesting that the customer open a customer account. If, at 1906, the customer chooses to not open an account, then the transaction is ended at 1908, otherwise, at 1910, a customer account is opened. On the other hand, if at 1902 it has been determined that a customer does have a valid customer account, then a determination is made at 1912 of whether or not the customer account has sufficient funds to purchase the selected item(s). If the customer account does not have sufficient funds, then at 1914 the customer is requested to credit sufficient funds to the customer account. If the customer does not credit sufficient funds, then the transaction is ended at 1908, otherwise, the account is credited with sufficient funds at 1916. In any case, if the customer account has sufficient funds to purchase the selected item(s), either as determined at 1912 or credited at 1916, processing is passed to 1708.

The invention can be preferably implemented by software, but can also be implemented in hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The many features and advantages of the present invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.

While this invention has been described in terms of a preferred embodiment, there are alterations, permutations, and equivalents that fall within the scope of this invention. It should also be noted that there are many alternative ways of implementing both the process and apparatus of the present invention. It is therefore intended that the invention be interpreted as including all such alterations, permutations, and equivalents as fall within the true spirit and scope of the present invention.

Claims

1. A method of ordering an item from an establishment using a wireless client device in the vicinity of the establishment, comprising:

receiving a signal with an identifier from a wireless network at the wireless client device;
comparing, at the wireless client device, a signal strength of the received signal with identifier from the wireless network to a threshold value;
comparing, at the wireless client device, the received identifier to a list of identifiers to find a match when the signal strength exceeds the threshold value; and
presenting, at the wireless client device, on a display screen of the wireless client device, if a match is found, an item ordering user interface;
receiving, at the wireless client device, a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface, the selection being made via the item ordering user interface;
forming, at the wireless client device, a remote order request for the particular item in response to the user selection; and
accessing order history data for the user of the wireless client device,
wherein at least one of the plurality of items available for ordering via the item ordering user interface is a previously purchased item,
wherein the user selection is the previously purchased item, and
wherein the remote order request includes data from the order history data.

2. The method as recited in claim 1, wherein the notification includes at least an estimated amount of time until the particular item denoted by the remote order is available at the establishment.

3. The method as recited in claim 1, wherein the notification includes at least an estimated amount of time until the particular item denoted by the remote order is available for pick up at the establishment.

4. The method as recited in claim 1, wherein the notification indicates at least that the particular item denoted by the remote order is available at the establishment.

5. The method as recited in claim 1, wherein the wireless client device is a wireless client device selected from a group comprising: a wireless media player, a wireless personal digital assistant, or a cell phone.

6. The method as recited in claim 1,

wherein the method further comprises:
storing order history data for the user on the wireless client device.

7. The method as recited in claim 1, wherein the method further comprises:

wherein the presenting operates to present the item ordering user interface on the display screen of the wireless client device when the signal is above the threshold and the identifier is found in the list of identifiers.

8. The method as recited in claim 1, wherein the method further comprises:

storing data on authorized establishments on the wireless client device.

9. The method as recited in claim 8, wherein the method further comprises:

storing distinct user data on the wireless client device in association with each of a plurality of the authorized establishments.

10. The method as recited in claim 1, wherein the method further comprises:

paying for the particular item via a user account of the user.

11. A method as recited in claim 1, wherein the method further comprises:

receiving, from the computing device associated with the establishment, information regarding at least one available item.

12. The method as recited in claim 1, wherein the method further comprises:

receiving, from the computing device associated with the establishment, information regarding advertisements unrelated to the establishment.

13. The method as recited in claim 1, wherein the receiving and the sending are performed when the wireless client device is external but proximate to the establishment.

14. The method as recited in claim 1, further comprising wirelessly sending the remote order request to a computing device associated with the establishment.

15. The method as recited in claim 1, further comprising:

wirelessly receiving, at the wireless client device, a notification from the computing device associated with the establishment; and
presenting the notification on the display screen of the wireless client device.

16. A method of ordering an item from an establishment using a wireless client device in the vicinity of the establishment, comprising:

receiving a signal with an merchantID from a wireless network at the wireless client device;
comparing, at the wireless client device, a signal strength of the received signal with merchantID from the wireless network to a threshold value;
ignoring, at the wireless client device, the signal when the signal strength does not exceed the threshold value, and
comparing, at the wireless client device, the received merchantID to a list of merchantIDs to find a match, when the signal strength exceeds the threshold value;
ignoring, at the wireless client device, the received signal if a match is not found;
accessing order preference data associated with the user of the wireless client device; and
presenting, on a display screen of the wireless client device, an item ordering user interface associated with the merchantID;
receiving, at the wireless client device, a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface, the selection being made via the item ordering user interface; and
forming, at the wireless client device, a remote order request for the particular item in response to the user selection, the remote order request being based on or including data from the order preference data.

17. The method as recited in claim 16, wherein the method further comprises:

storing order preference data for the user on the wireless client device.

18. The method as recited in claim 1, wherein the method further comprises:

receiving, at the wireless client device, an acknowledgement of the remote order request from the computing device associated with the identifier.

19. The method as recited in claim 16, wherein the method further comprises:

storing distinct order preference data on the wireless client device for each of a plurality of establishments, and
wherein the accessing of the order preference data associated with the user of the wireless client device comprises accessing the order preference data pertaining to the establishment that has been recognized.

20. The method as recited in claim 16, further comprising wirelessly sending the remote order request to a computing device associated with the establishment.

21. The method as recited in claim 16, further comprising:

wirelessly receiving, at the wireless client device, a notification from the computing device associated with the establishment; and
presenting the notification on the display screen of the wireless client device.

22. A non-transitory computer readable medium including at least instructions that when executed by a wireless client device provides for ordering an item from an establishment, comprising:

instructions for receiving a signal with an identifier from a wireless network at the wireless client device;
instructions for comparing, at the wireless client device, a signal strength of the received signal with identifier from the wireless network to a threshold value;
instructions for comparing, at the wireless client device, the received identifier to a list of identifier to find a match when the signal strength exceeds the threshold value;
instructions for presenting, on a display screen of the wireless client device, an item ordering user interface associated with the identifier;
instructions for receiving, at the wireless client device, a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface, the selection being made via the item ordering user interface;
instructions for forming, at the wireless client device, a remote order request for the particular item in response to the user selection; and
instructions for accessing order history data for the user of the wireless client device,
wherein at least one of the plurality of items available for ordering via the item ordering user interface is a previously purchased item,
wherein the user selection is the previously purchased item, and
wherein the remote order request includes data from the order history data.

23. The non-transitory computer readable medium as recited in claim 22, wherein the non-transitory computer readable medium further comprises:

instructions for receiving, from the computing device associated with the establishment, information regarding advertisements unrelated to the establishment.

24. The non-transitory computer readable medium as recited in claim 22, wherein the non-transitory computer readable medium further comprises instructions for wirelessly sending the remote order request to a computing device associated with the establishment.

25. The non-transitory computer readable medium as recited in claim 22, wherein the non-transitory computer readable medium further comprises:

instructions for wirelessly receiving, at the wireless client device, a notification from the computing device associated with the establishment; and
instructions for presenting the notification on the display screen of the wireless client device.

26. A wireless portable electronic device, comprising:

a processor for processing executable instructions;
a display coupled to the processor for displaying text and images;
a wireless interface coupled to the processor arranged to send and receive wireless signals; and
a memory arranged to store data and the executable instructions,
wherein the executable instructions include at least:
instructions for receiving a signal with an identifier from a wireless network at the wireless client device;
instructions for comparing, at the wireless client device, a signal strength of the received signal with identifier from the wireless network to a threshold value;
instructions for comparing, at the wireless client device, the received identifier to a list of identifier to find a match when the signal strength exceeds the threshold value,
instructions for presenting, on the display of the wireless portable electronic device, an item ordering user interface associated with the identifier;
instructions for receiving a user selection of a particular item of a plurality of items available for ordering via the item ordering user interface;
instructions for forming a remote order request for the particular item in response to the user selection; and
instructions for accessing order preference data for the user of the wireless client device,
wherein the remote order request is based on or includes data from the order preference data.

27. The wireless portable electronic device as recited in claim 26, wherein the executable instructions further include instructions for sending, via the wireless interface, the remote order request to a computing device associated with the establishment.

28. The wireless portable electronic device as recited in claim 26, wherein the executable instructions further include:

instructions for receiving, via the wireless interface, a notification from the computing device associated with the establishment; and
instructions for presenting the notification on the display screen of the wireless client device.
Referenced Cited
U.S. Patent Documents
4090216 May 16, 1978 Constable
4386345 May 31, 1983 Narveson et al.
4451849 May 29, 1984 Fuhrer
4589022 May 13, 1986 Prince et al.
4908523 March 13, 1990 Snowden et al.
4928307 May 22, 1990 Lynn
4951171 August 21, 1990 Tran et al.
5185906 February 16, 1993 Brooks
5293494 March 8, 1994 Saito et al.
5379057 January 3, 1995 Clough
5406305 April 11, 1995 Shimomura et al.
5559945 September 24, 1996 Beaudet et al.
5566337 October 15, 1996 Szymanski et al.
5583993 December 10, 1996 Foster et al.
5608698 March 4, 1997 Yamanoi et al.
5616876 April 1, 1997 Cluts
5617386 April 1, 1997 Choi
5670985 September 23, 1997 Cappels, Sr. et al.
5675362 October 7, 1997 Clough
5684513 November 4, 1997 Decker
5710922 January 20, 1998 Alley et al.
5712949 January 27, 1998 Kato
5717422 February 10, 1998 Fergason
5721949 February 24, 1998 Smith et al.
5726672 March 10, 1998 Hernandez et al.
5739451 April 14, 1998 Winksy et al.
5740143 April 14, 1998 Suetomi
5760588 June 2, 1998 Bailey
5778374 July 7, 1998 Dang et al.
5803786 September 8, 1998 McCormick
5815225 September 29, 1998 Nelson
5822288 October 13, 1998 Shinada
5835721 November 10, 1998 Donahue et al.
5835732 November 10, 1998 Kikinis et al.
5838969 November 17, 1998 Jacklin et al.
5864868 January 26, 1999 Contois
5867163 February 2, 1999 Kurtenbach
5870710 February 9, 1999 Ozawa et al.
5918303 June 29, 1999 Yamaura et al.
5920728 July 6, 1999 Hallowell et al.
5923757 July 13, 1999 Hocker et al.
5952992 September 14, 1999 Helms
6006274 December 21, 1999 Hawkins et al.
6009237 December 28, 1999 Hirabayashi et al.
6011585 January 4, 2000 Anderson
6018705 January 25, 2000 Gaudet et al.
6041023 March 21, 2000 Lakhansign
6052654 April 18, 2000 Gaudet et al.
6108426 August 22, 2000 Stortz
6122340 September 19, 2000 Darley et al.
6158019 December 5, 2000 Squibb
6161944 December 19, 2000 Leman
6172948 January 9, 2001 Keller et al.
6179432 January 30, 2001 Zhang et al.
6185163 February 6, 2001 Bickford et al.
6191939 February 20, 2001 Burnett
6208044 March 27, 2001 Viswanadham et al.
6216131 April 10, 2001 Liu et al.
6217183 April 17, 2001 Shipman
6248946 June 19, 2001 Dwek
6295541 September 25, 2001 Bodnar et al.
6297795 October 2, 2001 Kato et al.
6298314 October 2, 2001 Blackadar et al.
6332175 December 18, 2001 Birrell et al.
6336365 January 8, 2002 Blackadar et al.
6336727 January 8, 2002 Kim
6341316 January 22, 2002 Kloba et al.
6357147 March 19, 2002 Darley et al.
6377530 April 23, 2002 Burrows
6452610 September 17, 2002 Reinhardt et al.
6467924 October 22, 2002 Shipman
6493652 December 10, 2002 Ohlenbusch et al.
6536139 March 25, 2003 Darley et al.
6549497 April 15, 2003 Miyamoto et al.
6560903 May 13, 2003 Darley
6587127 July 1, 2003 Leeke et al.
6587403 July 1, 2003 Keller et al.
6587404 July 1, 2003 Keller et al.
6605038 August 12, 2003 Teller et al.
6606281 August 12, 2003 Cowgill et al.
6611607 August 26, 2003 Davis et al.
6611789 August 26, 2003 Darley
6617963 September 9, 2003 Watters et al.
6621768 September 16, 2003 Keller et al.
6623427 September 23, 2003 Mandigo
6626706 September 30, 2003 Siddiqui et al.
6631101 October 7, 2003 Chan et al.
6693612 February 17, 2004 Matsumoto et al.
6731312 May 4, 2004 Robbin
6760536 July 6, 2004 Amir et al.
6762741 July 13, 2004 Weindorf
6775539 August 10, 2004 Deshpande
6781611 August 24, 2004 Richard
6794566 September 21, 2004 Pachet
6799226 September 28, 2004 Robbin et al.
6801964 October 5, 2004 Mahdavi
6832373 December 14, 2004 O'Neill
6844511 January 18, 2005 Hsu et al.
6851952 February 8, 2005 Ueshima et al.
6870529 March 22, 2005 Davis
6876947 April 5, 2005 Darley et al.
6882955 April 19, 2005 Ohlenbusch et al.
6886749 May 3, 2005 Chiba et al.
6898550 May 24, 2005 Backadar et al.
6901261 May 31, 2005 Banatre et al.
6911971 June 28, 2005 Suzuki et al.
6918677 July 19, 2005 Shipman
6931377 August 16, 2005 Seya
6934812 August 23, 2005 Robbin et al.
6950087 September 27, 2005 Knox et al.
7010365 March 7, 2006 Maymudes
7028096 April 11, 2006 Lee
7043479 May 9, 2006 Ireton
7046230 May 16, 2006 Zadesky
7050790 May 23, 2006 Yamaga
7062225 June 13, 2006 White
7076561 July 11, 2006 Rosenberg et al.
7084856 August 1, 2006 Huppi
7084921 August 1, 2006 Ogawa
7092946 August 15, 2006 Bodnar
7107296 September 12, 2006 Novak et al.
7119267 October 10, 2006 Hirade et al.
7124125 October 17, 2006 Cook et al.
7131059 October 31, 2006 Obrador
7143241 November 28, 2006 Hull
7146437 December 5, 2006 Robbin et al.
7149813 December 12, 2006 Flanagin et al.
7155163 December 26, 2006 Cannon et al.
7155681 December 26, 2006 Mansour et al.
7162543 January 9, 2007 Fischer et al.
7171331 January 30, 2007 Vock et al.
7187948 March 6, 2007 Alden
7190883 March 13, 2007 Yeo
7191244 March 13, 2007 Jennings et al.
7213228 May 1, 2007 Putterman et al.
7215649 May 8, 2007 Yu
7234026 June 19, 2007 Robbin et al.
7272385 September 18, 2007 Mirouze et al.
7277928 October 2, 2007 Lennon
7289393 October 30, 2007 Keller et al.
7301857 November 27, 2007 Shah et al.
7312785 December 25, 2007 Tsuk et al.
7343317 March 11, 2008 Jokinen et al.
7345671 March 18, 2008 Robbin et al.
7356679 April 8, 2008 Le et al.
7366659 April 29, 2008 Etter
7377440 May 27, 2008 Casey
7385359 June 10, 2008 Dowling et al.
7502626 March 10, 2009 Lemilainen
7508535 March 24, 2009 Hart et al.
7574272 August 11, 2009 Gibbs et al.
7590773 September 15, 2009 Robbin et al.
7593782 September 22, 2009 Jobs et al.
7620363 November 17, 2009 Spurgat et al.
7627343 December 1, 2009 Fadell et al.
7657224 February 2, 2010 Goldberg et al.
7664558 February 16, 2010 Lindahl et al.
7686215 March 30, 2010 Jones et al.
7724716 May 25, 2010 Fadell
7747781 June 29, 2010 Maurya et al.
7757173 July 13, 2010 Beaman
7810223 October 12, 2010 Hemerick et al.
7870197 January 11, 2011 Lewis et al.
8024419 September 20, 2011 Gudorf
8072956 December 6, 2011 Fadell
8188357 May 29, 2012 Robbin et al.
8288641 October 16, 2012 Wilson
8663106 March 4, 2014 Stivoric et al.
8689113 April 1, 2014 Eytchison et al.
9274576 March 1, 2016 Janik et al.
20010013983 August 16, 2001 Izawa et al.
20010018668 August 30, 2001 Yanase et al.
20010029178 October 11, 2001 Criss et al.
20010036224 November 1, 2001 Demello et al.
20010037367 November 1, 2001 Iyer
20010041021 November 15, 2001 Boyle et al.
20010042107 November 15, 2001 Palm
20020002413 January 3, 2002 Tokue
20020013784 January 31, 2002 Swanson
20020013818 January 31, 2002 Yamaga
20020028683 March 7, 2002 Banatre et al.
20020045961 April 18, 2002 Gibbs et al.
20020046315 April 18, 2002 Miller et al.
20020055934 May 9, 2002 Lipscomb et al.
20020059440 May 16, 2002 Hudson et al.
20020059499 May 16, 2002 Hudson
20020090912 July 11, 2002 Cannon et al.
20020109718 August 15, 2002 Mansour et al.
20020116082 August 22, 2002 Gudorf
20020116517 August 22, 2002 Hudson et al.
20020122031 September 5, 2002 Maglio et al.
20020123359 September 5, 2002 Wei et al.
20020152045 October 17, 2002 Dowling et al.
20020156833 October 24, 2002 Maurya et al.
20020161865 October 31, 2002 Nguyen
20020173273 November 21, 2002 Spurgat et al.
20020174269 November 21, 2002 Spurgat et al.
20020189426 December 19, 2002 Hirade et al.
20020189429 December 19, 2002 Qian et al.
20020198790 December 26, 2002 Paulo et al.
20020199043 December 26, 2002 Yin
20030002688 January 2, 2003 Kanevsky et al.
20030007001 January 9, 2003 Zimmerman
20030007464 January 9, 2003 Balani
20030018799 January 23, 2003 Eyal
20030037254 February 20, 2003 Fischer et al.
20030046434 March 6, 2003 Flanagin et al.
20030050092 March 13, 2003 Yun
20030065680 April 3, 2003 Hatakeyama
20030074457 April 17, 2003 Kluth
20030076301 April 24, 2003 Tsuk et al.
20030076306 April 24, 2003 Zadesky et al.
20030079038 April 24, 2003 Robbin et al.
20030095096 May 22, 2003 Robbin et al.
20030097379 May 22, 2003 Ireton
20030104835 June 5, 2003 Douhet
20030126016 July 3, 2003 Asano
20030127307 July 10, 2003 Liu et al.
20030128192 July 10, 2003 van Os
20030133694 July 17, 2003 Yeo
20030153213 August 14, 2003 Siddiqui et al.
20030156503 August 21, 2003 Schilling et al.
20030167318 September 4, 2003 Robbin et al.
20030176935 September 18, 2003 Lian et al.
20030182100 September 25, 2003 Plastina et al.
20030221541 December 4, 2003 Platt
20030229490 December 11, 2003 Etter
20030236695 December 25, 2003 Litwin, Jr.
20040001395 January 1, 2004 Keller et al.
20040001396 January 1, 2004 Keller et al.
20040012556 January 22, 2004 Yong et al.
20040055446 March 25, 2004 Robbin et al.
20040066363 April 8, 2004 Yamano et al.
20040069122 April 15, 2004 Wilson
20040076086 April 22, 2004 Keller
20040086120 May 6, 2004 Akins, III et al.
20040094018 May 20, 2004 Ueshima et al.
20040103411 May 27, 2004 Thayer
20040125522 July 1, 2004 Chiu et al.
20040128198 July 1, 2004 Register et al.
20040139180 July 15, 2004 White et al.
20040165302 August 26, 2004 Lu
20040177063 September 9, 2004 Weber et al.
20040198436 October 7, 2004 Alden
20040199631 October 7, 2004 Natsume et al.
20040210628 October 21, 2004 Inkinen et al.
20040216108 October 28, 2004 Robbin
20040224638 November 11, 2004 Fadell et al.
20040225613 November 11, 2004 Narayanaswami et al.
20040242224 December 2, 2004 Janik et al.
20040246275 December 9, 2004 Yoshihara et al.
20040255135 December 16, 2004 Kitaya et al.
20040267825 December 30, 2004 Novak et al.
20050015254 January 20, 2005 Beaman
20050053365 March 10, 2005 Adams et al.
20050060240 March 17, 2005 Popofsky
20050060542 March 17, 2005 Risan et al.
20050097595 May 5, 2005 Lipsanen et al.
20050102191 May 12, 2005 Heller et al.
20050107031 May 19, 2005 Wood et al.
20050108754 May 19, 2005 Carhart et al.
20050111820 May 26, 2005 Matsumi et al.
20050122315 June 9, 2005 Chalk et al.
20050123886 June 9, 2005 Hua et al.
20050146534 July 7, 2005 Fong et al.
20050149213 July 7, 2005 Guzak et al.
20050152294 July 14, 2005 Yu et al.
20050156047 July 21, 2005 Chiba et al.
20050160270 July 21, 2005 Goldberg et al.
20050166153 July 28, 2005 Eytchison et al.
20050216855 September 29, 2005 Kopra et al.
20050218303 October 6, 2005 Poplin
20050234983 October 20, 2005 Plastina et al.
20050245839 November 3, 2005 Stivoric et al.
20050246324 November 3, 2005 Paalasmaa et al.
20050248555 November 10, 2005 Feng et al.
20050257169 November 17, 2005 Tu
20050259064 November 24, 2005 Sugino et al.
20050259219 November 24, 2005 Helbrecht et al.
20050259524 November 24, 2005 Yeh
20050270276 December 8, 2005 Sugimoto et al.
20050288046 December 29, 2005 Zhao et al.
20060013414 January 19, 2006 Shih
20060025068 February 2, 2006 Regan et al.
20060026424 February 2, 2006 Eto
20060061563 March 23, 2006 Fleck
20060068760 March 30, 2006 Hameed et al.
20060071899 April 6, 2006 Chang et al.
20060088228 April 27, 2006 Marriot et al.
20060092122 May 4, 2006 Yoshihara et al.
20060094409 May 4, 2006 Inselberg
20060095502 May 4, 2006 Lewis et al.
20060098320 May 11, 2006 Koga et al.
20060100978 May 11, 2006 Heller et al.
20060135883 June 22, 2006 Jonsson et al.
20060143236 June 29, 2006 Wu
20060145053 July 6, 2006 Stevenson et al.
20060152382 July 13, 2006 Hiltunen
20060155914 July 13, 2006 Jobs et al.
20060168340 July 27, 2006 Heller et al.
20060168351 July 27, 2006 Ng et al.
20060170535 August 3, 2006 Watters et al.
20060173974 August 3, 2006 Tang
20060180668 August 17, 2006 Casey
20060190577 August 24, 2006 Yamada
20060190980 August 24, 2006 Kikkoji et al.
20060218040 September 28, 2006 Sabapathypillai
20060221057 October 5, 2006 Fux et al.
20060221788 October 5, 2006 Lindahl et al.
20060235864 October 19, 2006 Hotelling
20060259758 November 16, 2006 Deng et al.
20060265503 November 23, 2006 Jones et al.
20060272483 December 7, 2006 Honeywell
20060277336 December 7, 2006 Lu et al.
20070014536 January 18, 2007 Hellman
20070028009 February 1, 2007 Robbin et al.
20070038941 February 15, 2007 Wysocki et al.
20070060109 March 15, 2007 Ramer et al.
20070061759 March 15, 2007 Klein, Jr.
20070074118 March 29, 2007 Robbin et al.
20070084333 April 19, 2007 Robbin et al.
20070089057 April 19, 2007 Kindig
20070106660 May 10, 2007 Stern et al.
20070124679 May 31, 2007 Jeong et al.
20070124681 May 31, 2007 Abbar et al.
20070129062 June 7, 2007 Pantalone et al.
20070135225 June 14, 2007 Nieminen et al.
20070155307 July 5, 2007 Ng et al.
20070169087 July 19, 2007 Fadell
20070226384 September 27, 2007 Robbin et al.
20070239849 October 11, 2007 Robbin et al.
20070248311 October 25, 2007 Wice et al.
20070255163 November 1, 2007 Prineppi
20070271312 November 22, 2007 Heller et al.
20070291710 December 20, 2007 Fadell
20080055228 March 6, 2008 Glen
20080086494 April 10, 2008 Heller et al.
20080134287 June 5, 2008 Gudorf et al.
20080168185 July 10, 2008 Robbin et al.
20080168245 July 10, 2008 Deatley et al.
20080168391 July 10, 2008 Robbin et al.
20080168525 July 10, 2008 Heller et al.
20080288046 November 20, 2008 Hemerick et al.
20080305832 December 11, 2008 Greenberg
20090239573 September 24, 2009 Kretz et al.
20090241070 September 24, 2009 Robbin et al.
20100077338 March 25, 2010 Matthews et al.
20100198704 August 5, 2010 Fadell
Foreign Patent Documents
4334773 April 1994 DE
4445023 June 1996 DE
0127139 May 1984 EP
0578604 November 1997 EP
0813138 December 1997 EP
0863469 September 1998 EP
0917077 May 1999 EP
0 952 510 October 1999 EP
0982732 March 2000 EP
1028425 August 2000 EP
1028426 August 2000 EP
1076302 February 2001 EP
0757437 June 2002 EP
1213643 June 2002 EP
1248414 October 2002 EP
1289197 March 2003 EP
1372133 December 2003 EP
1503363 February 2005 EP
1530115 May 2005 EP
1536612 June 2005 EP
1566743 August 2005 EP
1566948 August 2005 EP
1622293 February 2006 EP
1686496 August 2011 EP
2384399 February 2004 GB
2399639 May 2005 GB
2370208 June 2005 GB
5923610 May 1916 JP
2000090651 March 2000 JP
2000224099 August 2000 JP
2000285643 October 2000 JP
2000299834 October 2000 JP
2000311352 November 2000 JP
2000339864 December 2000 JP
2001236286 August 2001 JP
2001312338 November 2001 JP
2002076977 March 2002 JP
2002175467 June 2002 JP
2003188792 July 2003 JP
03228490 August 2003 JP
2003259333 September 2003 JP
2003319365 November 2003 JP
2004021720 January 2004 JP
2004219731 August 2004 JP
2004220420 August 2004 JP
04243386 September 2004 JP
6096520 April 2006 JP
8235774 October 2008 JP
9259532 November 2009 JP
9050676 September 2010 JP
20010076508 August 2001 KR
WO 9516950 June 1995 WO
WO 9817032 April 1998 WO
WO 9928813 June 1999 WO
WO 0022820 April 2000 WO
WO 00/38443 June 2000 WO
WO 0133569 May 2001 WO
WO 0165413 September 2001 WO
WO 0167753 September 2001 WO
WO 0225610 March 2002 WO
WO 03023786 March 2003 WO
WO 03036457 May 2003 WO
WO 03036541 May 2003 WO
WO 03067202 August 2003 WO
WO 2004049182 June 2004 WO
WO 2004055637 July 2004 WO
WO 2004061850 July 2004 WO
WO 2004077706 September 2004 WO
WO 2004084413 September 2004 WO
WO 2005031737 April 2005 WO
WO 2005048644 May 2005 WO
WO 2005008505 July 2005 WO
WO 2005109781 November 2005 WO
WO 2006040737 April 2006 WO
WO 2006071364 June 2006 WO
WO 2006108104 October 2006 WO
Other references
  • Communication Relating to the Results of the Partial International Search Report, PCT/US2007/070906, mailed May 2, 2008.
  • International Search Report and Written Opinion for PCT/US2007/070906, mailed Jun. 30, 2008.
  • Office Action for U.S. Appl. No. 11/485,142 mailed Aug. 3, 2009.
  • Office Action for Australian Patent Application No. 2007261116, dated Dec. 24, 2009.
  • Notice of Allowance for Australian Patent Application No. 2007261116, dated May 12, 2011.
  • Communication pursuant to Article 94(3) EPC for European Patent Application No. 07798392.2, dated Nov. 5, 2010.
  • Office Action for Australian Patent Application No. 2007261116, dated Jan. 10, 2011.
  • Notice of Allowance for U.S. Appl. No. 11/485,142 mailed Jan. 7, 2010.
  • Office Action for U.S. Appl. No. 12/760,479 mailed Feb. 17, 2011.
  • Notice of Allowance for U.S. Appl. No. 12/760,479 mailed Aug. 5, 2011.
  • “Apple Announces iTunes 2,” Press Release, Apple Computer, Inc., Oct. 23, 2001.
  • “Apple Introduces iTunes—World's Best and Easiest To Use Jukebox Software,” Macworld Expo, San Francisco, Jan. 9, 2001.
  • “Apple's iPod Available in Stores Tomorrow,” Press Release, Apple Computer, Inc., Nov. 9, 2001.
  • “Nomad Jukebox,” User Guide, Creative Technology Ltd., Version 1, Aug. 2000.
  • “SoundJam MP Plus Manual, version 2.0”—MP3 Player and Encoder for Macintosh by Jeffrey Robbin, Bill Kincaid and Dave Heller, manual by Tom Negrino, published by Casady & Greene, Inc., 2000.
  • “Digital Still Cameras—Downloading Images to a Computer,” Mimi Chakarova et al., Multi-Media Reporting and Convergence, 2 pgs.
  • Adam C. Engst, “SoundJam Keeps on Jammin',” Jun. 19, 2000, http://db.tidbits.com/getbits.acgi?tbart=05988.
  • Andrew Birrell, “Personal Jukebox (PJB),” Oct. 13, 2000, http://birrell.org/andrew/talks/pbj-overview.ppt.
  • Compaq, “Personal Jukebox,” Jan. 24, 2001, http://research.compaq.com/SRC/pjb/. De Herrera, Chris, Microsoft ActiveSync 3.1, Version 1.02, Oct. 13, 2000.
  • IEEE 1394—Wikipedia, 1995, http://www.wikipedia.org/wiki/Firewire.
  • iTunes 2, Playlist Related Help Screens, iTunes v2.0, Apple Computer, Inc., Oct. 23, 2001.
  • iTunes, Playlist Related Help Screens, iTunes v1.0, Apple Computer, Inc., Jan. 2001.
  • Miniman, “Applian Software's Replay Radio and Player v1.02,” Product review, pocketnow.com, http://www.pocketnow.com/reviews/replay/replay.htm, Jul. 21, 2001.
  • Musicmatch, “Musicmatch and Xing Technology Introduce Musicmatch Jukebox,” May 18, 1998, http://www.musicmatch.com/info/company/press/releases/?year=1998$release=2.
  • Personal Jukebox (PJB), “Systems Research Center and PAAD,” Compaq Computer Corp., Oct. 13, 2000, http://research.compaq.com/SRC/pjb/.
  • Sinitsyn, Alexander, “A Synchronization Framework for Personal Mobile Servers,” Pervasive Computing and Communications Workshops, 2004. Proceedings of the Second IEEE Annual Conference on, Piscataway, NJ, USA, IEEE, Mar. 14, 2004, pp. 208-212.
  • SoundJam MP Plus, Representative Screens, published by Casady & Greene, Inc., Salinas, CA, 2000.
  • Specification Sheet, iTunes 2, Apple Computer, Inc., Oct. 31, 2001.
  • Steinberg, “Sonicblue Rio Car,” Product Review, Dec. 12, 2000, http://electronics.cnet.com/electronics/0-6342420-1304-4098389.html.
  • Travis Butler, “Archos Jukebox 6000 Challenges Nomad Jukebox,” Aug. 13, 2001, http://db.tidbits.com/getbits.acgi?tbart=06521.
  • Travis Butler, “Portable MP3: The Nomad Jukebox,” Jan. 8, 2001, http://db.tidbits.com/getbits.acgi?tbart=06261.
  • “Creative Zen Vision: M 30GB”, Dec. 21, 2005; downloaded on Jan. 11, 2008 from http://web.archive.org/web/20051221050140/http://www.everthingusb.com/creative—zen—vision:m—30gb.html>.
  • Kadir et al., “Adaptive Fast Playback-Based Video Skimming Using a Compressed-Domain Visual Complexity Measure”, 2004 IEEE Intl Conference on Multimedia and Expo, pp. 2055-2058.
  • Yee et al., “Faceted Metadata for Image Search and Browsing.” Association For Computing Machinery, Conference Proceedings, Apr. 5, 2003.
  • Apple iTunes Smart Playlists, downloaded Apr. 5, 2005 from http://web.archive.org/web/20031002011316/www.apple.com/itunes/smartplaylists.. pp. 1-2.
  • iTunes, Wikipedia, the free encyclopedia; downloaded on Oct. 5, 2005, pp. 1-6.
  • Nutzel et al., “Sharing Systems for Future HiFi Systems”, The Computer Society, Jun. 2004.
  • Hart-Daves, Guy, “How To Do Everything with Your IPod & Mini IPod Mini”, 2004, McGraw-Hill Professional, p. 33.
  • “Creative liefert erstes Portable Media Center aus” [Online] Sep. 2, 2004, Retrieved from the internet on Sep. 20, 2007 from http://www.golem.de/0v09/33347.html>.
  • “Combination Belt Clip Leaf Spring and Housing Latch”, Wandt et al.; Motorola Technical Developments, Motorola Inc. Schaumburg, IL. vol. 18, Mar. 1, 1993.
  • “12.1” 925 Candela Mobile PC, downloaded from LCDHardware.com on Dec. 19, 2002, http://www.lcdharware.com/panel/12—1—panel/default.asp.
  • “BL82 Series Backlit Keyboards”, www.tg3electronics.com/products/backlit/backlit.htm, downloaded Dec. 19, 2002.
  • “Bluetooth PC Headsets—Enjoy Wireless VoIP Conversations: ‘Connecting’ Your Bluetooth Headset With Your Computer”, Bluetooth PC Headsets; downloaded on Apr. 29, 2006 from http://www.bluetoothpcheadsets.com/connect.htm.
  • “Creative MuVo TX 256 MB,” T3 Magazine, Aug. 17, 2004, http://www.t3.co.uk/reviews/entertainment/mp3—player/creative—muvo—tx—256mb [downloaded Jun. 6, 2006].
  • “Eluminx Illuminated Keyboard”, downloaded Dec. 19, 2002, http://www.elumix.com/.
  • “How To Pair a Bluetooth Headset & Cell Phone”, About.com: downloaded on Apr. 29, 2006 from http://mobileoffice.about.com/od/usingyourphone/ht/blueheadset—p.htm.
  • “Peripherals for Industrial Keyboards & Pointing Devices”, Stealth Computer Corporation, downloaded on Dec. 19, 2002, http://www.stealthcomputer.com/peropherals—oem.htm.
  • “Poly/Optical Fiber Optic Membrane Switch Backlighting”, downloaded Dec. 19, 2002, http://www.poly/optical.com/membrane—switches.html.
  • “Public Safety Technologies Tracer 2000 Computer”, downloaded Dec. 19, 2002, http://www.pst911.com/traver.html.
  • “QuickTime Movie Playback Programming Guide”, Apple Computer, Inc., Aug. 11, 2005.
  • “QuickTime Overview”, Apple Computer, Inc., Aug. 11, 2005.
  • “Rocky Matrix Backlit Keyboard”, downloaded Dec. 19, 2002, http://www.amrel.com/asi—matrixkeyboard.html.
  • “Sony Ericsson to introduce Auto pairing to improve Bluetooth connectivity between headsets and phones”, Sep. 28, 2005 Press Release, Sony Ericsson Corporate; downloaded on Apr. 29, 2006 from http://www.sonyericsson.com/spg.jsp?cc=global&lc=en&ver=4001&template=pc3—1—1&z . . . .
  • “Taos, Inc., Announces Industry's First Ambient Light Sensor to Convert Light Intensity to Digital Signals”, www.taosinc.com/pressrelease—090902.htm, downloaded Jan. 23, 2003.
  • “Toughbook 28: Powerful, Rugged and Wireless”, Panasonic: Toughbook Models, downloaded Dec. 19, 2002, http:www.panasonic.com/computer/notebook/html/01a—s8.htm.
  • “When it Comes to Selecting a Projection TV, Toshiba Makes Everything Perfectly Clear, Previews of New Releases”, www.bestbuy.com/HomeAudioVideo/Specials/ToshibaTVFeatures.asp, downloaded Jan. 23, 2003.
  • “WhyBuy: Think Pad”, IBM ThinkPad Web Page Ease of Use, downloaded on Dec. 19, 2002, http://www.pc.ibm.com/us/thinkpad/easeofuse.html.
  • 512MB Waterproof MP3 Player with FM Radio & Built/in Pedometer, Oregon Scientific, downloaded on Jul. 31, 2006 from http://www2.oregonscientific.com/shop/product.asp?cid=4&scid=11&pid=581.
  • Alex Veiga, “AT&T Wireless Launching Music Service,” Yahoo! Finance, Oct. 5, 2004, pp. 1/2.
  • Apple iPod Technical Specifications, iPod 20GB and 60GB Mac + PC, downloaded from http://www.apple.com/ipod/color/specs.html on Aug. 8, 2005.
  • Bociurkiw, Michael, “Product Guide: Vanessa Matz,”, www.forbes.com/asap/2000/1127/vmartz—print.html, Nov. 27, 2000.
  • Creative: “Creative NOMAD MuVo TX,” www.creative.com, Nov. 1, 2004, http://web.archive.org/web/20041024175952/www.creative.com/products/pfriendly.asp?product=9672 [downloaded Jun. 6, 2006].
  • Creative: “Creative NOMAD MuVo,” www.creative.com, Nov. 1, 2004, http://web.archive.org/web/20041024075901/www.creative.com/products/product.asp?category=213&subcategory=215&product=110 [downloaded Jun. 7, 2006].
  • iAP Sports Lingo 0×09 Protocol V1.00, May 1, 2006.
  • Jabra Bluetooth Headset User Manual; GN Netcom A/s, 2005.
  • Jabra Bluetooth Introduction: GN Netcom A/S Oct. 2004.
  • Jabra FreeSpeak BT200 User Manual; Jabra Corporation, 2002.
  • Kennedy, “Digital Data Storage Using Video Disc,” IBM Technical Disclosure Bulletin, vol. 24, No. 2, Jul. 1981.
  • Nonhoff/Arps, et al., “StraBenmusik Portable MP3/Spieler mit USB/Anschluss,” CT Magazin Fuer Computer Technik, Verlag Heise GMBH, Hannover DE, No. 25, Dec. 4, 2000.
  • Peter Lewis, “Two New Ways to Buy Your Bits,” CNN Money, Dec. 31, 2003, pp. 1/4.
  • Sastry, Ravindra Wadali. “A Need for Speed: A New Speedometer for Runners”, submitted to the Department of Electrical Engineering and Computer Science at the Massachusetts Institute of Technology, May 28, 1999.
  • Spiller, Karen. “Low/decibel earbuds keep noise at a reasonable level”, The Telegraph Online, dated Aug. 13, 2006, http://www.nashuatelegraph.com/apps/pbcs.dll/articl?Date=20060813&Cate . . . Downloaded Aug. 16, 2006.
  • Waterproof Music Player with FM Radio and Pedometer User Manual, Oregon Scientific, 2005.
  • De Herrera, Chris, Microsoft ActiveSync 3.1, Version 1.02, Oct. 13, 2000.
  • Creative: “MP3 Player,” www.creative.com, Nov. 1, 2004, http://web.archive.org/web/20041024074823/www.creative.com/products/product.asp?category=213&subcategory=216&product=4983 [downloaded Jun. 7, 2006].
Patent History
Patent number: 9747248
Type: Grant
Filed: Nov 22, 2011
Date of Patent: Aug 29, 2017
Patent Publication Number: 20120071100
Assignee: APPLE INC. (Cupertino, CA)
Inventor: Anthony M. Fadell (Portola Valley, CA)
Primary Examiner: Nghi H Ly
Application Number: 13/303,021
Classifications
Current U.S. Class: Contiguous Regions Interconnected By A Local Area Network (370/338)
International Classification: H04W 4/00 (20090101); G06F 15/02 (20060101); G06Q 30/06 (20120101); H04L 29/08 (20060101);