A large and growing population of users is enjoying entertainment through the consumption of digital media items (or simply “media items”), such as music, movies, images, electronic books, and so on. The users employ various electronic devices to consume such media items. Among these electronic devices are electronic book reader devices, cellular telephones, personal digital assistant (PDA), portable media players, tablet computers, netbooks, and the like. As the quantity of available electronic media content continues to grow, along with increasing proliferation of devices to consume that media content, finding ways to enhance user experience continues to be a priority.
The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.
This disclosure describes an architecture and techniques in which a user leverages a sharing service to share a media item stored on a device of the user with one or more other content rendering devices. These content rendering devices receive the shared media item in response to providing a pass phrase associated with the media item to the sharing service.
The media item may be of various types of digital content, such as a document, an audio file, a video file, an image, an electronic book, and so on. Both the device on which the media item is originally stored and the receiving content rendering devices may be embodied in many ways, such as electronic book reader devices, cellular telephones, personal digital assistant (PDA), portable media players, tablet computers, netbooks, and the like. However, in specific implementations described below, the shared media item is originally stored on an electronic book (eBook) reading device (“eBook reader device”), while the devices that receive the shared media item from the sharing service also comprises eBook reader devices.
In these implementations, the user initially sends a request to the sharing service (from the eBook reader device or otherwise) to share the media item stored on the eBook reader device for a predetermined amount of time (e.g., 2 hours, 2 weeks, etc.). The sharing service then associates a pass phrase (e.g., “Pink Gorilla”) with the request and communicates this pass phrase to the user. The eBook reader device (or another device of the user) then uploads the media item to the sharing service, which stores the item in association with the pass phrase for the predetermined amount of time.
In the interim, the user who wishes to share the document communicates the pass phrase to those users with whom the sharing user desires to share the item. For instance, the sharing user may send the pass phrase to these users via an email, a text message, or the like. Conversely, in instances where these users are physically proximate to the sharing user, the sharing user may simply audibly recite the pass phrase to these users. Each of these users then sends the pass phrase to the sharing service via their respective eBook reader devices or otherwise. In response, the sharing service downloads some or the entire shared media item to each of the eBook reader devices. In addition, these users may alternatively or additionally request that the sharing service send the media item to a different type of user device, such as a laptop, a cellular phone, or the like.
After the predetermined amount of time elapses, the sharing service removes the media item from storage. Should the sharing user desire to share another media item with a group of users, this user may again send a request to the sharing service, which will again associate a pass phrase with this new request. As such, the described architecture and techniques facilitate convenient sharing of media items amongst devices, such as eBook reader devices and the like.
Architectural Environment
As discussed further herein, a media item stored on one device may be transmitted to a sharing service 110, which stores the document in association with a pass phrase. The sharing service 110 then passes the media item to those devices that send the appropriate pass phrase to the sharing service 110.
In the illustrated architecture 100, essentially any type of content rendering device may be used to share and consume media items. In this example, the user 102 operates a desktop computer 104(1) to share the media item 106 stored on the eBook reader device 104(N). Of course, the user 102 could instead use any other device (e.g., the cellular phone 104(2)) to share the media item 106 stored on the eBook reader device 104(N), or the user 102 could simply share the media item 106 directly from the eBook reader device 104(N). In addition, while
In the illustrated example, the user 102 desires to share the media item 106, which comprises a personal document stored on the eBook reader device 104(N) and entitled “Grace's Outline for Criminal Procedure.” This document may be in a Portable Document Format (PDF), a Microsoft Word® format from Microsoft, Inc. or any other document format. In addition, this document may also be stored on one or more other devices associated with the user 102. For instance, the user may connect the eBook reader device 104(N) (in a wired or wireless manner) to the desktop computer 104(1) in order to allow the user 102 to manage the media items and other files stored on the eBook reader device 104(N). As such, the media item 106 may also be stored on or accessible by the desktop computer 104(1).
The user 102 then utilizes the desktop computer (or the eBook reader device 104(N) in some instances) to send a request, to the sharing service 110 and over a network 112, to share the media item 106. That is, the user 102 requests that the sharing service 110 make some or all of the media item 106 available to one or more other devices, such as the devices 108(1)-(S). The network 112 is representative of any one or combination of multiple different types of networks, such as the Internet, cable networks, cellular networks, wireless networks, and wired networks. One example of a wireless technology and associated protocols is the Wireless Fidelity (WiFi) wireless networking technologies defined according to IEEE 802.11 standards, while another example is a cellular network.
As illustrated, the sharing service 110 is embodied as one or more servers that collectively have processing and storage capabilities to receive the request from the device 104(1) of the user 102. In response to receiving such a request, the sharing service 110 communicates with the device 104(1) and/or the eBook reader device 104(N) for the purpose of making the media item 106 available to the devices 108(1)-(S). In some implementations, the sharing service 110 makes media items available to these devices by storing the media items, although in other implementations the servers merely facilitate communications between devices or may provide pointers to the media items.
The servers of the sharing service 110 may be embodied in any number of ways, including as a single server, a cluster of servers, a server farm or data center, and so forth, although other server architectures (e.g., mainframe) may also be used. Alternatively, the sharing service 110 may be embodied as a client device, such as desktop computer, a laptop computer, an eBook reader device and so forth.
In the illustrated example, the sharing service 110 includes storage 114 for storing media items 116. These items may include audio files 118, documents 120, video files 122 or any other form of media item, as described above. After receiving a request to make a media item available to multiple devices, such as the request sent by the user 102 from the desktop computer 104(1), the sharing service associates a pass phrase with the request.
The pass phrase comprises a string of alphanumeric characters that, when supplied by another device, grants the device access to the media item associated with the phrase. For instance, the pass phrase may comprise or consist of two or more grammatically correct words, such as “Pink Gorilla,” “Good to Go,” “Feisty Mango,” “Walking in the Rain,” or any other group of multiple words. In instances where the pass phrase comprises multiple grammatically correct words, these words may be separated by a space (“Pink Gorilla”) or they may not (“PinkGorilla”). In addition, these phrases may be free from numerals, punctuation and/or any other symbol other than letters.
In some instances, the sharing service 110 generates and/or selects the pass phrase and provides the pass phrase to the requesting device (e.g., the desktop computer 104(1)) via the network 112. In other instances, however, the user 102 may select the pass phrase and provide this phrase to the sharing service 110. The sharing service 110 may then associate this received pass phrase with the request.
A different pass phrase may be associated with each request from a particular user, such as the user 102. For instance, if the user 102 desires to share a first media item, the sharing service 110 may provide a first pass phrase (e.g., “Pink Gorilla”) to the user 102. If, at a later time, the user 102 desires to share a different media item, the sharing service 110 may provide a different pass phrase (e.g., “Feisty Mango”). In other instances, however, the pass phrase is a phrase that is uniquely and persistently associated with a user and/or a user account of the user. That is, the pass phrase may be a phrase that the user 102 uses repeatedly to share documents with devices. For instance, the user 102 may consistently share media items with use of the pass phrase “Pink Gorilla” that is unique to the user 102.
One type of phrase that is persistently and uniquely associated with a user account is a transaction phrase token, described in U.S. patent application Ser. No. 11/548,111, incorporated by reference above. As this application describes, a transaction phrase token may bind to one or more aspects of a user account, such as a payment instrument and shipping address of the user 102. As such, the user may conduct transactions with retailers (e.g., e-commerce retailers) with use of the transaction phrase token. Furthermore, the user 102 may share documents via the sharing service 110 with use of the transaction phrase token.
In one example described above, the sharing service 110 selects a pass phrase (e.g., “Pink Gorilla”) and sends this pass phrase to the device 104(1) of the user 102 that sent the request. Before or after receiving the identification of the pass phrase, the device 104(1) sends the media item 106 to the sharing service 110 for storing. In instances where the eBook reader device 104(N) stores the media item, however, the eBook reader device 104(N) may send this item 106 wirelessly to the sharing service 110 in lieu of the desktop computer 104(1) sending the item 106.
In either instance, after receiving the item the sharing service 110 stores the media item 106 in association with the corresponding pass phrase.
At this point, the user 102 provides the pass phrase to those users or devices with whom the user 102 desires to share the media item 106. The user 102 may provide this pass phrase audibly (e.g., in-person, over the phone, etc.) or electronically (e.g., by sending an email, a text message, etc.). After receiving the pass phrase, each of these users then sends a request for the media item 106 to the sharing service 110 accompanied by the phrase. In response to receiving these requests accompanied by the phrase “Pink Gorilla,” the sharing service 110 retrieves the media item associated with this phrase and sends the media item 106 to the corresponding devices.
The device 104(1) that sends the original request, the sharing service, and the content rendering devices 108(1)-(S) that receive the shared media item may be configured in numerous ways. Several example configurations are provided below with respect to
Example Devices and Sharing Service
As illustrated, the device 104(1) renders a user interface 208 that lists the media items 210 stored on the eBook reader device 104(N). These example items include document 212(1), 212(2) and 212(3), as well as an audio file 214. In this example, the user 102 chooses to share the document 212(2). In response to selecting the document 212(2), the sharing application 206 renders a menu 216 that includes an option 218 to “share this item.” When selected, this option 218 sends a request to the sharing service 110 to store the document 212(2) for later access by other devices, such as the content rendering devices 108(1)-(S) of
As illustrated, the menu 216 may also include an option 220 entitled “un-share this item.” In response to selecting this option 220, the device 104(1) sends a request to make a previously shared item unavailable to requesting devices. In response, the sharing service 110 may remove the item from storage 114 of the sharing service or may simply deny later requests for the item.
In the illustrated example, the user 102 selects the option 304. Here, the menu 302 further allows the user 102 to select a desired level of security 308. In this non-limiting example, the user 102 selects to receive a phrase having a relatively low level of security in lieu of a medium or high level of security. A pass phrase having a relatively higher level of security may consist of more words and/or more complex words than when compared to a pass phrase being relatively less secure.
The user 102 may also elect to receive an additional piece of information (e.g., a numerical PIN) in instances where the user 102 believes that security is of the utmost importance. In these instances, a requesting device must include the pass phrase (e.g., “Pink Gorilla”) and the additional piece of information (e.g., “8833”) in a request to the sharing service 110 to receive the media item 106. As such, the menu 302 allows the user 102 to decide upon a security level while taking into account the nature of the item being shared, the desired difficulty in remembering the phrase, and other factors.
The menu 302 further allows the user 102 to select an amount of time 310 for which the user 102 desires to share the document 212(2). This time may comprise any length of time, such as five minutes, two hours, two weeks, or any other amount of time, including for an indefinite amount of item. Here, the menu 302 provides a drop-down menu and, hence, a discrete number of time periods to choose from. However, other implementations instead allow the user 102 to enter a custom amount of time, or the sharing service may store the media item for an indefinite amount of time. In the illustrated example, after making the appropriate selections of the options discussed above, the user 102 selects a “Share!” icon 312.
The memory 504 also stores, in this example, a pass phrase generator 512, which serves to generate pass phrases for association with shared media items. The generator 512 may generate these phrases in any number of ways, such as by mining corpuses of text for phrases of varying lengths, by combining words according to part-of-speech templates or in any other manner. In some instances, the pass phrase generator 512 generates these pass phrases in a manner similar to the techniques described in U.S. patent application Ser. No. 12/352,970, incorporated in its entirety above.
Finally, the memory 504 includes a media item sharing module 514, which works in tandem with the network interface 506 to communicate with client devices to facilitate item sharing. For instance, the sharing module 514 and the network interface 506 function to receive a share request from a device, store a received media item for sharing and provide an identification of a pass phrase associated with this stored media item. After the media item is stored in association with the pass phrase, the module 514 and the interface 506 may receive a request for an item accompanied by a pass phrase, may determine a media item associated with the phrase and may provide the associated media item to the requesting device.
In a very basic configuration, the device 108(1) includes one or more processing units 602 and memory 604. Depending on the configuration of a dedicated eBook reader device 108(1), the memory 604 (and other memories described throughout this document) is an example of computer storage media and may include volatile and nonvolatile memory. Thus, the memory 604 may include, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, or any other medium which can be used to store media items or applications and data which can be accessed by the eBook reader device 108(1).
The memory 604 may be used to store any number of functional components that are executable on the processing unit(s) 602, as well as data and media items that are rendered by the eBook reader device 108(1). Thus, the memory 604 may store an operating system 606 and an eBook storage database to store one or more media items 608, such as eBooks and audio books. The memory 604 may further include a memory portion designated as an immediate page memory to temporarily store one or more pages of an electronic book. The pages held by the immediate page memory are placed therein a short period before a next page request is expected.
The term “page,” as used herein, refers to a collection of content that is presented at one time in a display of the eBook reader device 108(1). Thus, a “page” may be understood as a virtual frame of the content, or a visual display window presenting the content to the user. Thus, “pages” as described herein are not fixed permanently, in contrast to the pages of published “hard” books. Instead, pages described herein may be redefined or repaginated when, for example, the user chooses a different font for displaying the content in the first display. In addition to pages, the terms “page views”, “screen views”, and the like are also intended to mean a virtual frame of content.
An interface module 610 may also be provided in memory 604 and executed on the processing unit(s) 602 to provide for user operation of the device 108(1). One feature of the interface module 610 allows a user to enter a pass phrase into the eBook reader device 108(1) for the purpose of requesting a corresponding shared media item stored on the sharing service 110. The interface module 610 may facilitate textual entry of the pass phrase (e.g., via a keyboard), audible entry of the pass phrase (e.g., via a microphone) or entry of the pass phrase in any other manner. The interface module 610 may provide menus and other navigational tools to facilitate selection and rendering of the media items 608. The interface module 610 may further include a browser or other application that facilitates access to sites over a network, such as websites or online merchants.
A content presentation application 612 renders the media items 608. The content presentation application 612 may be implemented as various applications depending upon the media items. For instance, the application 612 may be an electronic book reader application for rending electronic books, or an audio player for playing audio books, or a video player for playing video, and so forth.
The memory 604 also stores a media item sharing module 614 that is executable on the processing unit(s) to both share a media item and send a request to the sharing service 110 to receive a shared item, as discussed above. The media item sharing module 614 acts in unison with the interface module 610 to receive a pass phrase from a user. When the eBook reader device receives a shared media item, the sharing module 614 stores the item with the other media items 608 stored on the device. The sharing module 614 may also include an indication that the item is a “shared” item, as described and illustrated below with reference to
The memory 604 may also store user credentials 616. The credentials 616 may be device specific (set during manufacturing) or provided as part of a registration process for a service. The credentials may be used to ensure compliance with DRM aspects of rendering the media items 608.
The eBook reader device 108(1) may further include a display 618. In one implementation, the display uses electronic paper (ePaper) display technology, which is bi-stable, meaning that it is capable of holding text or other rendered images even when very little or no power is supplied to the display. Some example ePaper-like displays that may be used with the implementations described herein include bi-stable LCDs, MEMS, cholesteric, pigmented electrophoretic, and others. In other implementations, or for other types of devices, the display may be embodied using other technologies, such as LCDs and OLEDs, and may further include a touch screen interface. In some implementations, a touch sensitive mechanism may be included with the display to form a touch-screen display.
The eBook reader device 108(1) may further be equipped with various input/output (I/O) components 620. Such components may include various user interface controls (e.g., buttons, a joystick, a keyboard, etc.), audio speakers, connection ports, and so forth.
A network interface 622 supports both wired and wireless connection to various networks, such as cellular networks, radio, WiFi networks, short range networks (e.g., Bluetooth), IR, and so forth.
The eBook reader device 108(1) also includes a battery and power control unit 624. The power control unit operatively controls an amount of power, or electrical energy, consumed by the eBook reader device. Actively controlling the amount of power consumed by the reader device may achieve more efficient use of electrical energy stored by the battery.
The eBook reader device 108(1) may have additional features or functionality. For example, the eBook reader device 108(1) may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. The additional data storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
Various instructions, methods and techniques described herein may be considered in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. for performing particular tasks or implement particular abstract data types. These program modules and the like may be executed as native code or may be downloaded and executed, such as in a virtual machine or other just-in-time compilation execution environment. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media.
General Operation
For discussion purposes, the process 700 (as well as processes 1500 and 1600 below) is described with reference to the architecture 100 of
At 702, the client device 104(1), which is embodied as a desktop computer in this example and is shown connected to the eBook reader device 104(N), sends a request to share a media item for a predetermined amount of time to the sharing service 110. For instance, the user 102 of the client device 104(1) may send a request to share the media item 106 (“Grace's Outline for Criminal Procedure”) stored on the eBook reader device 104(N).
At 704, the sharing service 110 receives the request. The sharing service 110 then associates a pass phrase with this request, such as the pass phrase “Pink Gorilla,” at 706. The service 110 may generate and/or select this phrase in some instances, while the user 102 may select this phrase in other instances. At 708, the sharing service 110 sends the pass phrase to the client device 104(1) and/or to the eBook reader device 104(N). In either instance, the user 102 receives an identification of the pass phrase at 710.
At 712, the client device 104(1) or the eBook reader device 104(N) sends the media item 106 to be shared to the sharing service 110. In some instances, the eBook reader device 104(N) provides the item to the client device 104(1), which then uploads the media item 106 to the sharing service 110. In other instances, the eBook reader device 104(N) uploads the media item 106 directly to the sharing service 110 (e.g., via a cellular or WiFi network).
In each instance, the sharing service 110 receives the item at 714. In this example, the sharing service 110 receives the media item 106 in a format that is not compatible with an eBook reader device that may later access the item. Therefore, at 716, the sharing service 110 converts the media item to a format that is compatible with the eBook reader device that may later access the item. In some instances, the sharing service 110 may convert the received media item 106 to multiple different formats, each corresponding to a particular format preferred by a particular device (e.g., a cellular phone, a PDA, different types of eBook reader devices, etc.).
At 720, one or more devices, including an eBook reader device 108(1), send a request for the media item accompanied by the pass phrase 124, “Pink Gorilla.” At 722, the sharing service 110 receives the request(s) and determines one or more media items that are associated with the pass phrase. In the instant example, the sharing service 110 determines that the phrase “Pink Gorilla” is associated with a single item, namely the media item 106. The sharing service 110 then sends at least a portion of the media item 106 to the requesting devices at 724.
In some implementations, the sharing service 110 may take into account the capabilities and features (e.g., native applications, screen size, etc.) of a receiving device when determining which version of the media item to send to the respective receiving device. For instance, the sharing service 110 may receive a request for a media item from a receiving device that is able to render a format of the media item in its original form, while also receiving a request for the media item from a receiving device that is not able to render that format. In this example, the sharing service 110 may send the media item in the original format to the former device while sending a modified or converted format of the media item to the latter device.
In the instant example where the media item 106 comprises a personal document of the user 102, the sharing service 110 may provide the entire item. In other instances, however, the sharing service 110 may provide less than the entire item. For instance, when the shared media item comprises a copyrighted work, such as an eBook, the sharing service 110 may share a sample of the eBook in lieu of the entire book. The sharing service 110 or the book publisher may predetermine which portion of the book share (e.g., Chapter 1 of the book). In other instances, however, the user 102 may specify which portion of the eBook to share (e.g., the portion currently accessed by the eBook reader device 104(N) of the user). In instances where the shared media item 106 comprises an article in a periodical, meanwhile, the sharing service 110 may provide some or the entire article along with a free trial offer for the periodical and/or a request to subscribe to the periodical. While a few examples have been discussed and are illustrated in greater detail below, multiple other sharing scenarios exist.
At 726, the receiving device(s), including the eBook reader device 108(1), receive the media item 106. At 728, these devices store the media item 106 in a local storage of the respective device. At this point, each receiving device may render the received portion of the shared media item 106, as
The process 700 illustrates but one example of how the architecture 100 of
Example eBook Reader Device User Interfaces
As illustrated, the user interface 1002 includes a listing of media items 1004 currently stored on or accessible by the eBook reader device 108(1). In addition, the user interface 1002 includes an interface 1006 that facilitates entry of the pass phrase 124. While this example interface 1006 comprises a user interface that facilitates textual entry of a pass phrase, other implementations may employ other interfaces that facilitate entry of pass phrases in other ways (e.g., audibly). In this example, the user of the eBook reader device 108(1) enters the pass phrase “Pink Gorilla” into a text box 1008 and then selects an example icon 1010 entitled “Get Shared Item!” At this point, the eBook reader device 108(1) sends a request to the sharing service for the media item 106 associated with the pass phrase, “Pink Gorilla.”
In addition, the user interface 1002 includes an indication 1110 of which media items are shared media items. Shared media items are those items that the eBook reader device 108(1) has received from the sharing service 110 and/or those items that the device 108(1) has shared with others via the sharing service 110.
Example Sharing Configurations
Example Processes
In response, the sharing service 110 may determine, at 1506, whether a local copy of the media item is available to the sharing service 110. For instance, the sharing service request and receive a checksum of the media item from the requesting device in order to compare this checksum to the media items that the sharing service 110 already stores or has local access to. Conversely, if the item to be shared is an eBook or the like, then the sharing service may request and receive a unique identifier (e.g., an ISBN number) associated with the item. Again, the sharing service 110 may then compare this identifier to those media items already available to the sharing service to determine if the item to be shared is amongst these available items. The sharing service may also make the determination of 1506 in many other ways.
In response to determining that a local copy of the item is available, the sharing service 110 obtains a locally-available copy of this media item at 1508. If not, then the sharing service 110 receives the media item to be shared from the requesting device at 1510 (possibly in response to a request from the sharing service 110).
At 1512, the sharing service associates a pass phrase and/or an additional piece of information (e.g., a numerical PIN) with the request and/or the media item. The size and complexity of the pass phrase may depend upon the desired level of security, as may the inclusion or exclusion of the additional piece of information. At 1514, the sharing service 110 converts the item to a format that is compatible with an eBook reader device and stores the converted and/or the original item.
At 1516, the sharing service 110 receives the pass phrase and the additional piece of information from an eBook reader device, such as the eBook reader device 108(1) described above. The sharing service 110 then provides the media item to the eBook reader device at 1518. Providing the item may include downloading the item, streaming the item, providing a pointer to the item stored at another location or the like.
At 1520, the sharing service 110 queries whether the service has received a request to remove the media item from the user that originally shared the item. If so, then the sharing service 110 removes the media item 106 from the storage 114 at 1522. In other instances, the sharing service 110 may simply refrain from further sharing of the item in lieu of removing the item from the storage 114. Furthermore, in some instances, the sharing service 110 may (or may not) also remove the item from the eBook reader device that received the item at 1518. This removal is represented at 1524.
If, however, the sharing service 110 has not received a request to remove the item, then the service 110 queries whether the predetermined amount of time has elapsed at 1526. If not, then the process 1500 returns to the query of 1520. If so, then the sharing service 110 removes the media item from the storage 114. Again, the sharing service 110 may (or may not) also remove the item from the eBook reader device that received the item at 1518.
The device 104(1) or 104(N) then receives, at 1606, an identification of a pass phrase associated with the request from the sharing service 110. The service 110 may have associated the phrase with the request after generating and/or selecting the phrase or after receiving the phrase from the device 104(1) or 104(N). Finally, at 1608, the device 104(1) or 104(N) sends the media item to be shared to the sharing service 110 for sharing with those devices that provide the pass phrase to the sharing service 110 within the predetermined amount of time.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.
This application claims priority to and is a continuation of U.S. patent application Ser. No. 12/715,780, filed on Mar. 2, 2010, the entire contents of which are incorporated herein by reference. This application is related to U.S. Provisional Application No. 60/823,611, filed on Aug. 25, 2006, and U.S. patent application Ser. No. 11/548,111, filed on Oct. 10, 2006, both entitled UTILIZING PHRASE TOKENS IN TRANSACTIONS and both incorporated herein by reference in their entirety. This application is also related to U.S. patent application Ser. No. 12/352,970, filed on Jan. 13, 2009, entitled GENERATING AND SUGGESTING PHRASES and incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4674065 | Lange et al. | Jun 1987 | A |
4773039 | Zamora | Sep 1988 | A |
5255386 | Prager | Oct 1993 | A |
5696962 | Kupiec | Dec 1997 | A |
5710887 | Chelliah et al. | Jan 1998 | A |
5721902 | Schultz | Feb 1998 | A |
5771378 | Holt et al. | Jun 1998 | A |
5828991 | Skiena et al. | Oct 1998 | A |
5862321 | Lamming et al. | Jan 1999 | A |
5870473 | Boesch et al. | Feb 1999 | A |
5898825 | Eberhard | Apr 1999 | A |
5907824 | Tzirkel-Hancock | May 1999 | A |
5953710 | Fleming | Sep 1999 | A |
5963965 | Vogel | Oct 1999 | A |
6047268 | Bartoli et al. | Apr 2000 | A |
6141760 | Abadi et al. | Oct 2000 | A |
6178396 | Ushioda | Jan 2001 | B1 |
6202064 | Julliard | Mar 2001 | B1 |
6314419 | Faisal | Nov 2001 | B1 |
6332131 | Grandcolas et al. | Dec 2001 | B1 |
6343279 | Bissonette et al. | Jan 2002 | B1 |
6377965 | Hachamovitch et al. | Apr 2002 | B1 |
6411950 | Moricz et al. | Jun 2002 | B1 |
6496931 | Rajchel et al. | Dec 2002 | B1 |
6539481 | Takahashi et al. | Mar 2003 | B1 |
6564213 | Ortega et al. | May 2003 | B1 |
6640304 | Ginter et al. | Oct 2003 | B2 |
6658568 | Ginter et al. | Dec 2003 | B1 |
6665659 | Logan | Dec 2003 | B1 |
6697793 | McGreevy | Feb 2004 | B2 |
6853987 | Cook | Feb 2005 | B1 |
6856963 | Hurwitz | Feb 2005 | B1 |
6892198 | Perisic et al. | May 2005 | B2 |
6988657 | Singer et al. | Jan 2006 | B1 |
7035789 | Abrego et al. | Apr 2006 | B2 |
7076652 | Ginter et al. | Jul 2006 | B2 |
7136841 | Cook | Nov 2006 | B2 |
7184950 | Weise | Feb 2007 | B2 |
7191115 | Moore | Mar 2007 | B2 |
7197455 | Sudo et al. | Mar 2007 | B1 |
7213748 | Tsuei et al. | May 2007 | B2 |
7264152 | Tsuei et al. | Sep 2007 | B2 |
7383224 | Huennekens et al. | Jun 2008 | B2 |
7395241 | Cook et al. | Jul 2008 | B1 |
7418444 | Flank et al. | Aug 2008 | B2 |
7426507 | Patterson | Sep 2008 | B1 |
7519590 | Chandrasekar et al. | Apr 2009 | B2 |
7548899 | Del Favero, Jr. et al. | Jun 2009 | B1 |
7565345 | Bailey et al. | Jul 2009 | B2 |
7587197 | Kimbrell | Sep 2009 | B2 |
7664831 | Cartmell et al. | Feb 2010 | B2 |
7676507 | Maim | Mar 2010 | B2 |
7865567 | Hendricks et al. | Jan 2011 | B1 |
7912702 | Bennett | Mar 2011 | B2 |
7925498 | Baker et al. | Apr 2011 | B1 |
7991608 | Johnson et al. | Aug 2011 | B2 |
8037086 | Upstill et al. | Oct 2011 | B1 |
8065328 | Strandel et al. | Nov 2011 | B2 |
8131540 | Marchisio et al. | Mar 2012 | B2 |
8136034 | Stanton et al. | Mar 2012 | B2 |
8150769 | Gupta et al. | Apr 2012 | B2 |
8161534 | Golle et al. | Apr 2012 | B2 |
8166045 | Mazumdar et al. | Apr 2012 | B1 |
8170954 | Keresman, III et al. | May 2012 | B2 |
8190628 | Yang et al. | May 2012 | B1 |
8266169 | Bobrow et al. | Sep 2012 | B2 |
8316041 | Chang et al. | Nov 2012 | B1 |
8316296 | Paek et al. | Nov 2012 | B2 |
8346792 | Baker et al. | Jan 2013 | B1 |
8359190 | Kirshenbaum | Jan 2013 | B2 |
8359191 | Chen et al. | Jan 2013 | B2 |
8374871 | Ehsani et al. | Feb 2013 | B2 |
8380491 | Leacock et al. | Feb 2013 | B2 |
8423349 | Huynh et al. | Apr 2013 | B1 |
8484016 | Brockett et al. | Jul 2013 | B2 |
8484089 | Lin et al. | Jul 2013 | B1 |
8516013 | Geller | Aug 2013 | B2 |
8661012 | Baker et al. | Feb 2014 | B1 |
20010032192 | Putta et al. | Oct 2001 | A1 |
20010041977 | Aoyagi et al. | Nov 2001 | A1 |
20020032564 | Ehsani et al. | Mar 2002 | A1 |
20020046169 | Keresman, III et al. | Apr 2002 | A1 |
20020112171 | Ginter et al. | Aug 2002 | A1 |
20020123973 | Eccles et al. | Sep 2002 | A1 |
20020188587 | McGreevy | Dec 2002 | A1 |
20020188621 | Flank et al. | Dec 2002 | A1 |
20030004716 | Haigh et al. | Jan 2003 | A1 |
20030061170 | Uzo | Mar 2003 | A1 |
20030065919 | Albert et al. | Apr 2003 | A1 |
20030088784 | Ginter et al. | May 2003 | A1 |
20030120846 | Clapper | Jun 2003 | A1 |
20030187789 | Karas et al. | Oct 2003 | A1 |
20030208439 | Rast | Nov 2003 | A1 |
20030233318 | King et al. | Dec 2003 | A1 |
20040030551 | Marcu et al. | Feb 2004 | A1 |
20040064447 | Simske et al. | Apr 2004 | A1 |
20040078273 | Loeb et al. | Apr 2004 | A1 |
20040083184 | Tsuei et al. | Apr 2004 | A1 |
20040098375 | DeCarlo, III | May 2004 | A1 |
20040153451 | Phillips et al. | Aug 2004 | A1 |
20040177120 | Kirsch | Sep 2004 | A1 |
20040199375 | Ehsani et al. | Oct 2004 | A1 |
20040254893 | Tsuei et al. | Dec 2004 | A1 |
20040254894 | Tsuei et al. | Dec 2004 | A1 |
20040260653 | Tsuei et al. | Dec 2004 | A1 |
20050027691 | Brin et al. | Feb 2005 | A1 |
20050044160 | McElligott | Feb 2005 | A1 |
20050050469 | Uchimoto et al. | Mar 2005 | A1 |
20050120108 | Wisniewski et al. | Jun 2005 | A1 |
20050131826 | Cook | Jun 2005 | A1 |
20050171851 | Applebaum et al. | Aug 2005 | A1 |
20050240536 | Davis et al. | Oct 2005 | A1 |
20050261988 | Horel et al. | Nov 2005 | A1 |
20060015484 | Weng et al. | Jan 2006 | A1 |
20060087941 | Obradovich | Apr 2006 | A1 |
20060173772 | Hayes et al. | Aug 2006 | A1 |
20060230022 | Bailey et al. | Oct 2006 | A1 |
20060253399 | Chatani | Nov 2006 | A1 |
20070011154 | Musgrove et al. | Jan 2007 | A1 |
20070022058 | Labrou et al. | Jan 2007 | A1 |
20070088952 | Hewitt et al. | Apr 2007 | A1 |
20070168469 | Church et al. | Jul 2007 | A1 |
20070226169 | Solyanik et al. | Sep 2007 | A1 |
20080019530 | Eldridge et al. | Jan 2008 | A1 |
20080040233 | Wildman et al. | Feb 2008 | A1 |
20080040274 | Uzo | Feb 2008 | A1 |
20080046366 | Bemmel et al. | Feb 2008 | A1 |
20080046980 | Peng | Feb 2008 | A1 |
20080052226 | Agarwal et al. | Feb 2008 | A1 |
20080082903 | McCurdy et al. | Apr 2008 | A1 |
20080114721 | Jones et al. | May 2008 | A1 |
20080154772 | Carlson | Jun 2008 | A1 |
20080162455 | Daga et al. | Jul 2008 | A1 |
20080168073 | Siegel et al. | Jul 2008 | A1 |
20080189188 | Morgenstern | Aug 2008 | A1 |
20080189293 | Strandel et al. | Aug 2008 | A1 |
20080209534 | Keronen et al. | Aug 2008 | A1 |
20080222711 | Michaelis | Sep 2008 | A1 |
20090030989 | Maresh et al. | Jan 2009 | A1 |
20090064294 | Cook et al. | Mar 2009 | A1 |
20090070103 | Beggelman et al. | Mar 2009 | A1 |
20090113543 | Adams et al. | Apr 2009 | A1 |
20090192928 | Abifaker | Jul 2009 | A1 |
20090234876 | Schigel et al. | Sep 2009 | A1 |
20090271283 | Fosnacht et al. | Oct 2009 | A1 |
20090282035 | Ferreira et al. | Nov 2009 | A1 |
20090293110 | Koga | Nov 2009 | A1 |
20090326953 | Peralta Gimenez et al. | Dec 2009 | A1 |
20090327244 | Rizal | Dec 2009 | A1 |
20100031043 | Burger et al. | Feb 2010 | A1 |
20100032192 | Kishi | Feb 2010 | A1 |
20100042628 | Crowley et al. | Feb 2010 | A1 |
20100042717 | Strandell et al. | Feb 2010 | A1 |
20100083103 | Paek et al. | Apr 2010 | A1 |
20100138397 | Li et al. | Jun 2010 | A1 |
20100146115 | Bezos | Jun 2010 | A1 |
20100146283 | Poitier et al. | Jun 2010 | A1 |
20100161314 | Karttunen et al. | Jun 2010 | A1 |
20100179801 | Huynh et al. | Jul 2010 | A1 |
20100250130 | Wiegand et al. | Sep 2010 | A1 |
20100312778 | Lu et al. | Dec 2010 | A1 |
20100333131 | Parker et al. | Dec 2010 | A1 |
20110131157 | Iyer et al. | Jun 2011 | A1 |
20110153854 | Chickering | Jun 2011 | A1 |
20110154456 | Machani | Jun 2011 | A1 |
20110225417 | Maharajh et al. | Sep 2011 | A1 |
20120072404 | Murphy et al. | Mar 2012 | A1 |
20130198084 | Agarwal et al. | Aug 2013 | A1 |
20130204789 | Agarwal et al. | Aug 2013 | A1 |
20130204790 | Agarwal et al. | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
1077436 | Feb 2001 | EP |
H11265413 | Sep 1999 | JP |
2001357202 | Dec 2001 | JP |
2002163579 | Jun 2002 | JP |
2002197024 | Jul 2002 | JP |
2003308437 | Oct 2003 | JP |
2004005515 | Jan 2004 | JP |
2004240764 | Aug 2004 | JP |
2005018265 | Jan 2005 | JP |
2006040235 | Feb 2006 | JP |
WO2004006194 | Jan 2004 | WO |
WO2005109268 | Nov 2005 | WO |
WO2008025037 | Feb 2008 | WO |
Entry |
---|
Utility U.S. Appl. No. 11/548,111, filed Oct. 10, 2006, entitled “Utilizing Phrase Tokens in Transaction” Agarwal, et al. |
Utility U.S. Appl. No. 12/331,894, filed Dec. 10, 2008, entitled “Content Sharing” Jeffrey P. Bezos. |
Utility U.S. Appl. No. 12/352,970, filed Jan. 13, 2009, entitled “Generating and Suggesting Phrases” Jesensky, et al. |
U.S. Appl. No. 12/353,025, filed Jan. 13, 2009, Jesensky, et al., “Generating Personalized Phrases”. |
U.S. Appl. No. 12/353,059, filed Jan. 13, 2009, Jesensky, et al., “Generating Mined Phrases”. |
U.S. Appl. No. 12/353,091, filed Jan. 13, 2009, Jesensky, et al., “Generating Constructed Phrases”. |
U.S. Appl. No. 12/353,120, filed Jan. 13, 2009, Huynh, et al., “Filtering Phrases”. |
U.S. Appl. No. 12/353,155, filed Jan. 13, 2009, Huynh, et al., “Filtering Phrases”. |
U.S. Appl. No. 12/353,170, filed Jan. 13, 2009, Huynh, et al., “Phrase Feedback Loop”. |
U.S. Appl. No. 12/353,184, filed Jan. 13, 2009, Gefen, et al., “Using Phrase Tokens for Performing Transactions”. |
U.S. Appl. No. 12/510,761, filed Jul. 28, 2009, Jesensky, et al., “Determining Similar Phrases”. |
Utility U.S. Appl. No. 12/544,891, filed Aug. 20, 2009, entitled “Enforcing User-Specified Rules” Williams, et al. |
U.S. Appl. No. 12/715,780, filed Mar. 2, 2010, Sellier, et al, “Sharing Media Items with Pass Phrases”. |
U.S. Appl. No. 61/021,275, filed Jan. 15, 2008, Rode, et al., “Systems and Methods of Retrieving Informaton”. |
Allan, et al., “Using Part-of-speech Patterns to Reduce Query Ambiguity”, Proceedings of the 25th annual international ACM SIGIR conference on Research and development in information retrieval (SIGIR'02), ACM, New York, NY, pp. 307-314. |
“Amazon.com: What are Statistically Improbable Phrases?”, retrieved on Dec. 15, 2008 at <<http://www.amazon.com/gp/search-inside/sipshelp.html>>, Amazon.com, 1 page. |
Brown, et al., “Class-Based n-gram Models of Natural Language”, MIT Press, Computational Linguistics, vol. 18, Issue 4, Dec. 1992, pp. 467-479. |
Evernote.com, retrieved on Jul. 21, 2009 at <<http://evernote.com/>>, 5 pgs. |
“Google Sets”, retrieved on Dec. 15, 2008 at <<http://labs.google.com/sets>>, Google, 1 page. |
Jones, et al., “Generating Query Substitutions”, WWW 2006, Edinburgh, Scotland, ACM, 2006, pp. 387-396. |
Office action for U.S. Appl. No. 12/353,184, mailed on Jul. 6, 2012, Gefen et al., “Using Phrase Tokens for Performing Transactions”, 20 pages. |
Office action for U.S. Appl. No. 12/715,780, mailed on Jan. 11, 2013, Sellier et al., “Sharing Media Items with Pass Phrases”, 45 pages. |
Office action for U.S. Appl. No. 12/352,970, mailed on Jan. 16, 2013, Jesensky et al., “Generating and Suggesting Phrases for a User”, 26 pages. |
Office action for U.S. Appl. No. 12/353,059, mailed on Jan. 24, 2013, Jesensky et al., “Mining Phrases for Association With a User”, 40 pages. |
Office action for U.S. Appl. No. 12/353,155, mailed on Jan. 29, 2013, Huynh et al., “Determining Phrases Related to Other Phrases”, 36 pages. |
Office action for U.S. Appl. No. 12/353,025, mailed on Oct. 24, 2011, Jesenky et al., “Generating Personalized Phrases”, 25 pages. |
Office Action for U.S. Appl. No. 12/510,761, mailed on Nov. 19, 2013, James Jesensky, “Determining Similar Phrases”, 19 pages. |
Office action for U.S. Appl. No. 12/353,184, mailed on Nov. 28, 2011, Gefen et al., “Using Phrase Tokens for Performing Transactions”, 19 pages. |
Office action for U.S. Appl. No. 12/544,891, mailed on Nov. 5, 2012, Williams et al, “Enforcing User-Specified Rules”, 21 pages. |
Office action for U.S. Appl. No. 12/715,780, mailed on Dec. 2, 2013, Sellier, et al., “Sharing Media Items with Pass Phrases”, 49 pages. |
Non-Final Office Action for U.S. Appl. No. 12/353,091, mailed on Dec. 8, 2011, James Jesensky et al., “Generating Constructed Phrases”, 18 pages. |
Office Action for U.S. Appl. No. 12/353,091, mailed on Apr. 9, 2014, James Jesensky, “Generating Constructed Phrases”, 21 pages. |
Non-Final Office Action for U.S. Appl. No. 12/544,891, mailed on May 24, 2012, Matthew T. Williams et al., “Enforcing User-Specified Rules”, 17 pages. |
Non-Final Office Action for U.S. Appl. No. 12/353,170, mailed on May 25, 2012, Steve Huynh et al., “Phrase Feedback Loop”, 40 pages. |
Non-Final Office Action for U.S. Appl. No. 12/715,780, mailed on Jun. 19, 2012, Laurent E. Sellier et al., “Sharing Media Items with Pass Phrases”, 46 pages. |
Office action for U.S. Appl. No. 12/352,970, mailed on Jun. 27, 2012, Jesensky et al., “Generating and Suggesting Phrases”, 34 pages. |
Final Office Action for U.S. Appl. No. 12/510,761, mailed on Jun. 4, 2014, James Jesensky, “Determining Similar Phrases”, 25 pages. |
Final Office Action for U.S. Appl. No. 12/353,091, mailed on Jun. 7, 2012, James Jesensky et al., “Generating Constructed Phrases”, 18 pages. |
Office action for U.S. Appl. No. 12/715,780, mailed on Jul. 10, 2013, Sellier et al., “Sharing Media Items with Pass Phrases”, 46 pages. |
Non-Final Office Action for U.S. Appl. No. 12/353,059, mailed on Jul. 13, 2012, James Jesensky et al, “Generating Mined Phrases”, 37 pages. |
Non-Final Office Action for U.S. Appl. No. 12/353,120, mailed on Jul. 19, 2012, Steve Huynh et al., “Filtering Phrases”, 63 pages. |
Non-Final Office Action for U.S. Appl. No. 12/353,155, mailed on Aug. 1, 2012, Steve Huynh et al., “Determining Phrases Related to Other Phrases”, 29 pages. |
Office action for U.S. Appl. No. 12/353,170, mailed on Sep. 14, 2012, Huynh et al., “Phrase Feedback Loop”, 48 pages. |
“Statistically Improbable Phrases” retrieved on Dec. 15, 2008 at <<http://en.wikipedia.org/wiki/Statistically—Improbable—Phrases>>, Wikipedia, the free encyclopedia, 2 pages. |
Wang, et al., “Mining Term Association Patterns from Search Logs for Effective Query Reformulation”, CIKM'08, Napa Valley, CA, USA, ACM, 2008, pp. 479-488. |
“What are Amazon.com Statistically Improbable Phrases?”, retrieved on Dec. 15, 2008 at <<http://www.amazon.com/gp/search-inside/sipshelp-dp.html>>, Amazon.com, 1 page. |
Office action for U.S. Appl. No. 12/353,184, mailed on Oct. 3, 2014, Gefen et al., “Using Phrase Tokens for Performing Transactions”, 28 pages. |
Office action for U.S. Appl. No. 12/353,025, mailed on Sep. 10, 2014, Jesensky et al., “Generating Personalized Phrases”, 22 pages. |
Final Office Action for U.S. Appl. No. 11/548,111, mailed on Jun. 17, 2015, Amit D. Agarwal, “Utilizing Phrase Tokens in Transactions”, 20 pages. |
Office action for U.S. Appl. No. 12/544,891 mailed on Aug. 25, 2015, Williams et al., “Enforcing User-Specified Rules”, 18 pages. |
Office Action for U.S. Appl. No. 12/353,170, mailed on Mar. 2, 2015, Steven Huynh, “Phrase Feedback Loop”, 12 pages. |
Final Office Action for U.S. Appl. No. 12/353,025, mailed on Apr. 28, 2015, James Jesnsky, “Generating Personalized Phrases”, 12 pages. |
Final Office Action for U.S. Appl. No. 12/414,236, mailed on Jan. 30, 2015, Rajendra Kumar Vippagunta, “Querying for User Account Information”, 18 pages. |
Office action for U.S. Appl. No. 12/414,236, mailed on Oct. 12, 2012, Vippagunta et al., “Querying for User Account Information”, 15 pages. |
Non-Final Office Action for U.S. Appl. No. 11/548,111, mailed on Oct. 20, 2014, Amit D. Agarwal, “Utilizing Phrase Tokens in Transactions”, 24 pages. |
Final Office Action for U.S. Appl. No. 11/548,111, mailed on Nov. 13, 2009, Amit D. Agarwal, “Utilizing Phrase Tokens in Transactions”, 26 pages. |
Non-Final Office Action for U.S. Appl. No. 12/414,236, mailed on Dec. 8, 2011, Rajendra Kumar Vippagunta et al., “Querying for User Account Information”, 12 pages. |
Non-Final Office Action for U.S. Appl. No. 11/548,111, mailed on Apr. 2, 2009, Amit D. Agarwal, “Utilizing Phrase Tokens in Transactions”, 21 pages. |
Office action for U.S. Appl. No. 12/510,761, mailed on May 8, 2015, Jesensky et al., “Determining Similar Phrases”, 24 pages. |
Final Office Action for U.S. Appl. No. 12/353,184, mailed on Jun. 16, 2015, Howard B. Gefen, “Using Phrase Tokens for Performing Transactions”, 29 pages. |
Office action for U.S. Appl. No. 12/414,236, mailed on Jul. 8, 2014, Vippagunta et al., “Querying for User Account Information”, 14 pages. |
PCT International Search Report and Written Opinion for PCT Application No. PCT/US07/76920 mailed on May 2, 2008, 13 pages. |
Riloff et al., “Learning Extraction Pattern for Subjective Expressions”, Proceedings of the 2003 Conference on Empirical Methods in Natural Language Processing, 2003, 8 pages. |
Offce Action for U.S. Appl. No. 13/829,435, mailed on Oct. 7, 2015, Agarwal et al., “Utilizing Phrase Tokens in Transactions”, 21 pages. |
Offce Action for U.S. Appl. No. 13/828,841, mailed on Oct. 8, 2015, Agarwal et al., “Utilizing Phrase Tokens in Transactions”, 19 pages. |
Office action for U.S. Appl. No. 12/414,236, mailed on Sep. 21, 2015, Vippagunta et al., “Querying for User Account Information”, 23 pages. |
Office action for U.S. Appl. No. 12/353,170, mailed on Sep. 24, 2015, Huynh et al., “Phrase Feedback Loop”, 10 pages. |
Office action for U.S. Appl. No. 12/544,891, mailed on Mar. 10, 2016, Williams et al., “Enforcing User-Specified Rules”, 22 pages. |
Office action for U.S. Appl. No. 12/353,025, mailed on Mar. 18, 2016, Jessensky et al., “Generating Personalized Phrases”, 29 pages. |
Office action for U.S. Appl. No. 12/414,236, mailed on Jun. 2, 2016, Vippagunta et al., “Querying for User Account Information”, 17 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 12715780 | Mar 2010 | US |
Child | 14312924 | US |