Electronic distribution of information has gained in importance with the proliferation of personal computers, and has undergone a tremendous upsurge in popularity as the Internet has become widely available. With the widespread use of the Internet, it has become possible to distribute large, coherent units of information, such as books, using electronic technologies. Books and other printed works available through electronic technologies are commonly referred to as electronic books (“eBooks”). Typical eBook reader devices attempt to mimic the experience of reading a conventional paper book or other printed works through display of electronic information on one or more electronic displays. A typical eBook reader device is a handheld digital device having a liquid crystal display panel and enough memory and processing capability to store several eBooks. Such a device is capable of retrieving and displaying an eBook, in whole or in part, for reading.
There are some advantages to using an eBook reader device over conventional paper books or other printed works. An eBook reader device is often capable of storing a number of complete works. Therefore, an eBook reader device containing a number of stored works weighs significantly less than the same number of printed works. This makes an eBook reader a particularly attractive alternative to paper books for travel, educational purposes, and professional business use. Also, because eBooks do not require the use of paper products, they are generally offered at a lower price than their printed counterparts. Furthermore, the use of eBook reader devices in conjunction with eBooks may be beneficial to the ecosystem, by reducing a number of printed works produced using paper products.
To date, however, eBook readers and the use of eBooks in general have not achieved widespread consumer acceptance. This is mainly attributable to the design and implementation particulars of conventional eBook reader devices and the manner in which content usable with such devices is attainable.
The preceding description of conventional eBook reader devices was provided herein for contextual reasons only.
An electronic book (“eBook”) reader device and a method for operating a reader device are provided that include content indexing features designed to improve a reading experience. A plurality of electronic publication indexes is stored on the eBook reader device. At least one of the indexes stored in the reader device is also stored at a remote site. Several indexes stored at the remote site may be substantially similar to one or more of the indexes stored on the reader device. The indexes stored at the remote site may be used to update one or more indexes stored on the reader device. In one implementation, the remote site is a content repository that includes content available for purchase and download.
The detailed description is described 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.
As will be appreciated from the following disclosure, linking a reader device with a content repository creates an arrangement that will generally make the use of reader devices more attractive. The implementations described herein provide an environment in which content is simple to locate, retrieve and consume using a reader device that includes systems and methods that provide several indexes related to content.
The terms “book” and/or electronic book (“eBook”) as used herein include electronic or digital representations of printed works, as well as digital content that may include text, multimedia, hypertext and/or hypermedia. Examples of printed and/or digital works include, but are not limited to, books, magazines, newspapers, periodicals, journals, reference materials, telephone books, textbooks, anthologies, instruction manuals, proceedings of meetings, forms, directories, maps, etc. Accordingly, the terms book and/or eBook may include any content that is in electronic or digital format.
The description herein provides a non-limiting implementation of an electronic device in the form of an eBook reader device. It is noted, however, that various aspects and features described herein may be implemented in other electronic devices or electronic readers besides eBook reader devices including, for example, portable computers, personal digital assistants (PDAs), portable gaming devices, wireless phones, and the like.
Users of readers implemented as described herein will have a virtual bookstore literally at their finger tips. More specifically, a reader device according to an exemplary implementation described herein makes it possible to search for books, view book summaries, and retrieve books and read retrieved books. All of this is possible from the comfort of one's home, or virtually any other location for that matter.
As noted above, several indexes may allow an eBook reader device to access and use electronic content that may be displayed and/or stored in the device. At least one of the several indexes corresponds to an index stored at a content repository. The indexes stored on an eBook reader device may include a title only index, compiled indexes associated with recent index searches performed on an eBook reader device, and indexes that are associated with unique users of a reader device. In addition, several of the indexes stored in an eBook reader device may be compiled from metadata related to eBooks. The metadata may be used to locate eBooks or other content of interest stored in the eBook reader device and/or a content repository.
In on implementation, an eBook reader device includes wireless communications capabilities. These capabilities allow the eBook reader device to receive index updates and content from a content repository. The index updates may be solicited or unsolicited deliveries from a content repository. The index updates may also be delivered from other sources that store electronic content that may be used on an eBook reader device.
Various examples of indexing features applied to an eBook reader are described below with reference to
Exemplary Environment
The content repositories 104(1)-104(M) and/or 106(1)-106(K) are employed on one or more servers, perhaps arranged as a server farm. Other server architectures may also be used to implement the content repositories 104(1)-104(M) and/or 106(1)-106(K). The content repositories 104(1)-104(M) and/or 106(1)-106(K) are capable of handling requests from many entities and providing, in response, eBook related content that may be received by one or more eBook reader devices 102.
The wireless link 110 that is used by the eBook reader device 102 to communicate with the content repository 104 may be implemented using any applicable wireless technology. The wireless link 110 may also be used by the content repository 104 to communicate with the reader device 102. Ordinarily, the wireless link 110 includes cell sites, base stations and Mobile Telephone Switching Offices (MTSO). Each base station contains a radio transceiver and controller, and provides radio communications to wireless devices operating in its cell. The cells are typically engineered into a network that is deployed in a hexagonal cell pattern, in order to provide local, regional, or national wireless coverage. The MTSO links cells together using traditional copper, fiber optic, and/or microwave technology and acts as a central office exchange, allowing wireless devices to connect to various other communication mediums. One such communication medium is the network 108.
The content repositories 104 and 106 are configured to support providing content to one or more eBook reader devices 102. As will be described in greater detail later, the content may be works that are readable using the eBook reader device 102. Other content for use with the reader device 102 may be stored in the content repositories 104 and 106 as well, such as magazines and newspapers in electronic format. The content repositories 104 and 106 may also provide information related to conventional printed works. This information may include downloadable electronic summaries of the conventional printed works. Other non-limiting examples of information that may be stored in the content repositories 104 and 106 include periodicals and newspapers in electronic format, and Really Simple Syndication (RSS) feeds. Therefore, as noted above, the eBook reader device 102 may be considered as a general reader device that is capable of displaying any content that is stored in electronic format.
The content repository 104 includes a storage medium 126. The content repository 106 may include a similar storage medium as well. The storage 126 includes a title index 128, a plurality of user title indexes 130, various eBook files 132 and other content 134. Although the indexes 128 and 130 are shown as separate, they may be merged into one index as well. This is also true of the other indexes described in the following description. The storage 126 may be implemented using, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by the content repository 104.
The eBook reader device 102 includes a device memory 112. The device memory 112 contains at least eBook indexes 114. These eBook indexes 114 include a title only index 116, recent search indexes 118, common search indexes 120, and user saved indexes 122. The device memory 112 also contains a complete eBook section 124 that is used to store one or more eBooks for use with the reader device 102.
Additional details related to the storage 126 and the device memory 112 are provided below.
Exemplary Repository Content
Content of the storage 126 employed in the content repository 104 is described in detail with reference to
The title index 128 housed in the storage 126 includes a title only index 202 and a title metadata index 204. The title only index 202 has index entries that include titles of eBooks offered for download by the content repository 104. The title only index 202 is shown as including Titles 1-N (e.g., To Kill a Mocking Bird, etc.). The title metadata index 204 includes metadata entries related to eBooks offered for download by the content repository 104. The metadata entries are shown in
The user title indexes 130 of the storage 126 include several user indexes captured from eBook reader devices (e.g., reader device 102) that have connected with the content repository 104. The content repository 104 may track keyword searches performed by the eBook reader device 102. Generally, such keyword searches relate to eBook content stored in the content repository 104. The eBook titles/metadata relevant to those searches may be stored in the user title indexes 130 as user specific indexes directed to particular eBook topics/titles. The content repository 104 may use the user specific indexes to tailor the content of various updates sent to the eBook reader device 102.
In the exemplary implementation illustrated in
The user title indexes 130 also include a purchase history index 208 associated with a User X. The purchase history index 208 includes Title 1 Metadata-Title 2 Metadata. In one implementation, the metadata listed in the index 208 relates to eBooks purchased by the User X. Those purchases were made possible through the use of the eBook reader device 102. Entries in the purchase history index 208 may be used to tailor future eBook related information and other information transmitted to the eBook reader device 102. For example, entries in the index 208 may serve as a basis for transmitting advertisements related to the purchase history, recommendations, promotional coupons or other forms of advertisements, and so forth.
The eBook files 132 of the storage 126 include numerous eBooks 1-N, or other electronic content that may be used by the eBook reader device 102. The eBooks are preferably stored in an electronic format that is displayable on a display of the eBook reader device 102. Depending on the storage capability of the content repository 104, the number of eBooks included in the eBook files 132 may be in the thousands and even the millions. Some or all of the eBooks included in the eBook files 132 are referenced in the title only index 202 and/or the title metadata index 204. In addition to the eBooks 1-N, the eBook files 132 may also include separate eBook Summary 1-K files related to eBooks offered for purchase and download.
These eBook summaries may be sent to the eBook reader device 102 upon request. Alternatively, the eBook summaries may be sent to the reader device 102 automatically during an update procedure implemented by the content repository 104. Such an update procedure may be triggered by the content repository 104 on a periodic basis, by an update schedule in the reader device 102, or some other update activation process. In addition, summaries related to conventional paper books may also be stored in the storage 126 and made available for download or delivery to the reader device 102. Summaries sent to the reader device 102 may be for the purpose of promoting a book recently offered for sale or about to be offered for sale, at the request of an author that desires increased sales, or any other applicable reason.
The other content 134 of the storage 126 include content that is not generally considered as being related to a printed work, but are otherwise useable on the eBook reader device 102. For example, the other content 134 is shown in
Exemplary eBook Reader Device Memory
Content of the device memory 112 employed in the eBook reader device 102 is described in detail with reference to
The title only index 116 contains index entries related to eBook titles that are offered on the content repository 104. Generally, the title only index 116 includes the same index entries included in the title index 128 found in the storage 126. However, the total number of index entries included in the title only index 116 may be limited if the memory capacity of the eBook reader device 102 is approaching full capacity.
The recent search indexes 118 of the device memory 112 include indexes captured by the eBook reader device 102 during a searching process conducted therewith. For example, a recent search index 302(1) may include various eBook references that relate to a general keyword search performed by the reader device 102. In the
The common search indexes 120 of the device memory 112 include indexes generated by the eBook reader device 102 during a searching process conducted therewith. More particularly, the indexes included in the common search indexes 120 may include various eBook references that relate to commonly used keyword searches performed by the reader device 102. For example, a user of the eBook reader device 102 may commonly search for eBooks that relate to computer architecture. Maintaining several indexes related to commonly searched keywords eliminates having to perform the same search again. Furthermore, similar to the indexes contained in the recent search indexes 118, the indexes of the common search indexes 120 are augmented with metadata after a preliminary search of the title only index 116. The metadata is retrieved from the content repository 104. The common search indexes 120 may be linked to unique user logon credentials held by the reader device 102. The common search indexes 120 are substantially similar to the recent search indexes 118. Therefore, a detailed illustration of the common search indexes 120 is not provided in
The user saved search indexes 122 of the device memory 112 include indexes generated by the eBook reader device 102 during a searching process conducted therewith. The indexes included in the user saved search indexes 118 were retained in the eBook reader device 102 by user request. In one implementation, the user indexes are linked with unique user logon credentials held by the reader device 102.
The complete eBook section 124 of the device memory 112 holds eBooks 1-N that are stored locally on the eBook reader device 102. The eBook section 124 may also hold eBook summaries 1-K. The amount of content stored in the section 124 is a function of the storage capability of the device memory 112, the design particulars of the reader device 102, and/or user specified parameters. In one implementation, some or all of the content stored in eBook section 124 was obtained from the content repository 104. The eBook section 124 may also hold summaries related to conventional paper books. The complete eBook section 124, or some other portion of the device memory 112, may also store other content that may be utilized with the eBook reader device 102. Such content may include periodicals and newspapers in electronic format, RSS feeds, audio books, music, and video media.
Exemplary Metadata
In the figure, an eBook metadata 402 includes category fields 404 and value fields 406. In this example, the metadata includes M pairs of fields, including eight particular categories: Title; Contributor (e.g., Author); Publisher; Publishing Data; International Standard Book Number (ISBN); Page Count; eBook File Size; eBook Abstract; and Other. If an eBook reader device has limited storage capability, the eBook metadata 402 may include a subset of these categories, such as the Title, Contributor and eBook Abstract categories.
In one exemplary implementation of the eBook metadata 402 the Other category includes information related to other available formats for a given eBook. Such formats may include one or more audio-book versions of the given eBook, and different language versions of the eBook. The Other category may include rating information that is compiled from reviews of the given eBook and/or a related conventional printed work. For example, an entity may employ a four or five star rating system that is used to convey users' opinions given after reading the eBook. Therefore, the information associated with the Other category may be periodically updated to reflect current reviews provided by others. Certainly, other categories of the metadata 402 may be changed/updated from time-to-time as well.
Additional category and value field combinations may be included in metadata as well. Accordingly, although eight different categories are shown in the eBook metadata 402, this is entirely exemplary and more or less categories may be used in various implementations. Associated with each category is a value field. The value field is shown as being one contiguous data field, but may be a plurality of data fields as well. On example of a value field associated with the title field is “To Kill a Mocking Bird”.
Exemplary eBook Reader Device
Exemplary eBook reader device components 500 are described in detail with reference to
In a very basic configuration, the eBook reader device 502 includes a processing unit 508, the device memory 112 and a display driver 520 that controls eBook content output to a display 522 of the reader device 502. Depending on the exact configuration of an eBook reader device 502, the device memory 112 includes a volatile memory 504 (such as RAM) and a nonvolatile memory 510. The volatile memory 504 includes a memory portion designated as an immediate page memory 506. The immediate page memory 506 may include one or more pages of an eBook. The pages held by the immediate page memory 506 are placed therein a short period before a next page request is expected. An algorithm may be used to predict the rate at which a user turns pages. Pages retrieved from the page memory 506 are displayed on the display of the reader device 502.
The term “page” as used herein refers to a collection of content that is presented at one time in the display 522. Thus, a “page” as described herein 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 or other printed works. Instead, pages described herein may be redefined or repaginated when, for example, the user chooses a different font for displaying the content in the display 522.
The nonvolatile memory 510 includes a flash memory 512 that typically contains an operating system of the eBook reader device 502. The memory 510 also includes the eBook indexes 114 and the complete eBook section 124. Several program modules 514 are stored in the memory 510 and may include a user access module 516 and other modules 518. The other modules 518 may include power management instructions that may be used to control an amount of electrical energy supplied to various components of the eBook reader device 502. Copending application “Predictive Reader Power Management”, application Ser. No. 11/277,880, filed Mar. 29, 2006, discloses various implementations for controlling device power consumption. The entirely of application Ser. No. 11/277,880 is hereby incorporated herein by reference. Other modules may also be included in accordance with the design particulars of the reader device 502.
The user access module 516 includes instructions associated with user logon procedures and requirements. For example, a logon procedure may be implemented to identify and obtain identification information related to users of the eBook reader device 502. This identification information may be used to establish user credentials assigned to users of the reader device 502. Verifying user credentials may include requiring users to enter assigned usernames and passwords before operation of the reader device 502 is permitted, or access to privileged information is allowed. The logon procedure may be included as part of the operating system of the eBook reader device 502. Alternatively, biometric authentication (e.g., fingerprint user identification) may be employed by the eBook reader device 502 to identify distinct users. Technologies related to logon procedures and biometrics are known and thus are not described in further detail herein.
The eBook reader device 502 also includes a communication connection(s) 524 to allow the eBook reader device 502 to communicate with other devices, such as over a network (e.g., the Internet). At the very least, the communication connection(s) 524 includes technology that enables the reader device 502 to communicate wirelessly. The communication connection(s) 524 is one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The eBook reader device 502 also includes a power control unit 526 and a battery 528. The power control unit 524 operatively controls an amount of electrical energy supplied by the battery 528. The manner in which the power control unit 524 controls an amount of electrical energy supplied by the battery 528 is dictated by the power management instructions of the other modules 518. The processing unit 508 supplies computing resources to the power control unit 526, as well as the other components of the eBook reader device 502.
The eBook reader device 502 may have additional features or functionality. For example, the eBook reader device 502 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.
The device memory 112 is an exemplary example of computer storage media. Thus, computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the eBook reader device 502. Any such computer storage media may be part of the eBook reader device 502. The eBook reader device 102 may also have input device(s) such as keyboard, mouse, pen, voice input device, touch input device, external electrical energy connectivity, etc. Output device(s) such as an auxiliary display, speakers, printer, etc. may also be included. Such input/output device(s) may be connected to one or more I/O ports(s) 530. Various devices described above are well know in the art and need not be discussed at length.
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.
Exemplary eBook Reader Device Interface
As is illustrated in
The eBook reader device 102 also includes several additional touch screen implemented buttons labeled logon 618, eBook titles 620, title refresh 622, eBook display 624 and editing tools 626. Depressing the logon button 618 initiates a logon screen that will accept user logon information. Properly logging on through such a screen allows a user to save user specific information in storage of the eBook reader device 102. Use of the eBooks titles button 620 will show a screen that lists titles of complete eBooks stored in the complete eBook section 124. If eBook/book summaries are also stored in the section 124, those titles will also be shown on the screen.
The title refresh button 622 may be used to initiate wireless or other means of communication with the content repository 104. Once a connection is established with the content repository 104, a downloading and/or uploading process may commence. For example, the title only index 116 may be refreshed; metadata may be retrieved and associated with the recent search indexes 118, the common search indexes 120 and/or the user saved search indexes 122. The content repository 104 may also use this connection opportunity to retrieve one or more recent search indexes, common search indexes and/or user specific indexes and save them in the storage 126. Other information exchanges may also occur during the wireless or other communication session established between the eBook reader device 102 and the content repository 104.
The eBook display button 624 is used to display pages of an eBook loaded in the immediate page memory 606. Generally, the button 624 allows a user of the eBook reader device 102 to return to a current eBook being read regardless of a screen displayed on the display 602. The editing tools button 626 is used to access eBook annotation, commenting and editing tools that may part of the reader device's 102 operating system. The reader device 102 also includes a previous page button 628, an on/off button 630, and a next page button 634. The buttons 628 and 630 may be used to “turn” pages of an eBook displayed on the reader device 102. The options button 632, referenced previously, may be used to alter various operating parameters of the reader device 102 (e.g., display contrast, power control functions, etc.).
The title only index screen 702 allows users of the eBook reader device 102 to search and browse titles included in the title only index 116 and/or the title index 128. The screen includes a search field 704 that is capable of receiving keywords related to a topic of interest. Using these keywords, the title only index 116 and/or the title index 128 are searched. Titles matching the entered keywords are shown in a results section 706.
A receive additional information button 708 is included as part of the title only index screen 702. If a wireless (or other) connection is not already active, actuation of the button 708 initiates the eBook reader device 102 to connect wirelessly (or by other means) with the content repository 104. A user of the reader device 102 may highlight various titles included in the results section 706 and request additional information regarding those titles selected using the button 708. Such additional information may include retrieving metadata associated with selected titles, retrieving summaries, or initiating a purchase of one or more of the selected titles. Title searches may be saved in the storage 126 of the content repository 104 and/or in the device memory 112 of the reader device 102.
The local/remote search screen 802 allows users of the eBook reader device 102 to search and browse content stored both locally in the device 102 and/or remotely in the content repository 104. The screen includes a search field 804 that is capable of receiving keywords related to a topic of interest. Using these keywords, the content stored both locally in the device 102 and/or remotely in the content repository 104 are searched. Content matching the entered keywords are shown in a results section 806.
In one exemplary implementation, the results section 806 displays content in categories. One category lists content that is found locally in the eBook reader device 102 and another category lists content that is found remotely in the content repository 104. The user of the device 102 may select one or more of the returned results and appropriate information will be displayed. Selection of search results returned from the content repository 104 may necessitate submission of payment information before content is fully retrievable from the repository 104.
Although not illustrated in the figures, selection of the various other buttons discussed in the foregoing may cause the eBook reader device 102 to display a range of other types of graphical user interfaces on the display 602. For example, to name a few, the reader device 102 may be implemented with graphical user interfaces that enable users to play music, watch video content, and/or browse the Internet.
Exemplary Processes
For discussion purposes, the example processes of
At block 902, one of several indexes stored in the device memory 112 is accessed. For example, the reader device 102 may access the title only index 116, the recent search indexes 118, or the common search indexes 122. Other indexes may be accessed if they are stored in the reader device 102. At block 904, the accessed index is searched. In one implementation, the index is searched using one or more keywords. The one or more keywords may be input into the reader device 102 using a user interface. Exemplary user interfaces are discussed in connection with
At block 906, index entries that relate to the keywords are identified. Depending on the index searched, the identified index entries may be title only index entries and/or metadata index entries. The block 906 may also include a process that detects direct user input actively selecting index entries that relate to the search keywords. Allowing a user to select index entries that relate to the search keywords may serve to narrow or reduce the number of index entries used when the device memory 112 is searched for eBook content. At block 908, the eBook reader device 102 searches the device memory 112 for eBook content (e.g., metadata, summaries, complete eBooks, etc.) that relates to the identified or user selected eBook index entries. If the related eBook content is stored in the eBook reader device 102 (determined at block 910), the desired content is retrieved and displayed on the reader device 102 (block 912).
At block 914, if the eBook related content is not stored on the eBook reader device 102, a wireless (or other) connection is established with the content repository 104. The instructions of block 914 are not performed if a wireless (or other) connection is already active. At block 916, the reader device 102 requests delivery of the related content. The content repository 104 will deliver the requested related content to the reader device 102 if a billing process is not required. If charges are required before delivery of the requested content may occur, a billing process is commenced. An exemplary billing process is discussed in connection with
At block 1004, index entries that result from a search based on the keywords are identified. Depending on the index searched, the identified index entries may be title only index entries and/or metadata index entries. At block 1006, the identified index entries are saved as a group to create an additional index. The created additional index may be saved in one of the indexes 116-120. The additional index may also be saved in the user title indexes 130 located in the content repository 104.
At block 1008, additional data may be received from the content repository 104. For example, additional data may be delivered to augment the index entries now associated with the created additional index. Such additional data may include metadata related to the index entries included in the additional index, or one or more eBook summaries related to the index entries. Delivery of the additional data may be requested by a user of the eBook reader device 102. Delivery of the additional data may also be directed by the content repository 104. For example, the additional data may be delivered automatically in accordance with a defined communications schedule between the reader device 102 and the repository 104.
At block 1102, the title only index 116 in the device memory 112 is searched. The search may be conducted using one or more keywords entered by a user of the eBook reader device 102. If a wireless session (or other communication session) is currently established with the content repository 104, the title index 128 may be searched as well, or instead of searching the title only index 116.
At block 1104, index entries that result from a search based on the keywords are identified. Depending on the index searched, the identified index entries may be title only index entries and/or metadata index entries. At block 1106, the identified index entries are saved as a group to create a user specific index. The created additional index may be saved and included in the user saved search indexes 122. The user specific index may also be saved in the user title indexes 130 located in the content repository 104. At block 1108, the user specific index is associated with the user credentials of a current user of the eBook reader device 102. This association limits access to the user specific index. More specifically, only those users that possess the proper logon username and password of the current user will be able to gain access to the created user specific index.
Additional data may be delivered to augment the index entries associated with the created user specific index. Such additional data may include metadata related to the index entries included in the user specific index, or one or more eBook/book summaries related to the index entries. Delivery of the additional data may be requested by a user of the eBook reader device 102. Delivery of the additional data may also be directed by the content repository 104. For example, the additional data may be delivered automatically in accordance with a defined communications schedule between the reader device 102 and the repository 104.
At block 1204, the eBook reader device 102 receives a billing request from the content repository 104. A billing request is sent to the reader device 102 when requested content has associated fees and payment of those fees is required before delivery and/or download of the content may commence. As is discussed herein, some content available at the content repository 104 may not have associated fees (e.g., eBook titles, metadata, some or all eBook summaries, etc.).
At block 1206, the reader device 102 sends a reply that includes payment information. The payment information may include credit card information, bank account information, etc. Generally, any conventional manner of completing payment between various sources may be used in block 1206. Including, for example, payment by means of a previously established account with a provider of one or more of the eBook services described herein. At block 1208, the content requested in block 1202 is received by the eBook reader device 102. This may be by direct download by the eBook reader device 102, background download, or delivery during a later wireless (or other communication) session with the content repository 104. Moreover, content obtained by the reader device 102 may occur during one contiguous wireless (or other communication) session, or over multiple sessions.
The billing process illustrated in
At block 1306, the eBook reader device 102 processes the received updates and appropriately updates one or more indexes stored in the eBook indexes 114. At block 1308, if the reader device 102 is designed to do so, a message indicating receipt of the updates is sent to the content repository 104.
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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4622627 | Rodriguez et al. | Nov 1986 | A |
| 5544305 | Ohmaye et al. | Aug 1996 | A |
| 5566098 | Lucente et al. | Oct 1996 | A |
| 5623260 | Jones | Apr 1997 | A |
| 5659742 | Beattie et al. | Aug 1997 | A |
| 5663748 | Huffman et al. | Sep 1997 | A |
| 5710922 | Alley et al. | Jan 1998 | A |
| 5711922 | O'Brien et al. | Jan 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5761485 | Munyan | Jun 1998 | A |
| 5765168 | Burrows | Jun 1998 | A |
| 5813017 | Morris | Sep 1998 | A |
| 5845278 | Kirsch et al. | Dec 1998 | A |
| 5847698 | Reavey et al. | Dec 1998 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5940846 | Akiyama | Aug 1999 | A |
| 5956048 | Gaston | Sep 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 5973681 | Tanigawa et al. | Oct 1999 | A |
| 6018575 | Gross et al. | Jan 2000 | A |
| 6034839 | Hamming | Mar 2000 | A |
| 6037954 | McMahon | Mar 2000 | A |
| 6041335 | Merritt et al. | Mar 2000 | A |
| 6049796 | Siitonen et al. | Apr 2000 | A |
| 6064980 | Jacobi et al. | May 2000 | A |
| 6073148 | Rowe et al. | Jun 2000 | A |
| 6148340 | Bittinger et al. | Nov 2000 | A |
| 6154757 | Krause et al. | Nov 2000 | A |
| 6164974 | Carlile et al. | Dec 2000 | A |
| 6201771 | Otsuka et al. | Mar 2001 | B1 |
| 6233318 | Picard et al. | May 2001 | B1 |
| 6300947 | Kanevsky | Oct 2001 | B1 |
| 6308320 | Burch | Oct 2001 | B1 |
| 6313828 | Chombo | Nov 2001 | B1 |
| 6331867 | Eberhard et al. | Dec 2001 | B1 |
| 6335678 | Heutschi | Jan 2002 | B1 |
| 6351750 | Duga et al. | Feb 2002 | B1 |
| 6385596 | Wiser et al. | May 2002 | B1 |
| 6401086 | Bruckner | Jun 2002 | B1 |
| 6401239 | Miron | Jun 2002 | B1 |
| 6442651 | Crow et al. | Aug 2002 | B2 |
| 6449627 | Baer et al. | Sep 2002 | B1 |
| 6457030 | Adams et al. | Sep 2002 | B1 |
| 6466951 | Birkler et al. | Oct 2002 | B1 |
| 6493734 | Sachs et al. | Dec 2002 | B1 |
| 6496803 | Seet et al. | Dec 2002 | B1 |
| 6529920 | Arons et al. | Mar 2003 | B1 |
| 6542874 | Walker et al. | Apr 2003 | B1 |
| 6560699 | Konkle | May 2003 | B1 |
| 6642947 | Feierbach | Nov 2003 | B2 |
| 6658623 | Schilit et al. | Dec 2003 | B1 |
| 6685482 | Hopp et al. | Feb 2004 | B2 |
| 6687878 | Eintracht et al. | Feb 2004 | B1 |
| 6704733 | Clark et al. | Mar 2004 | B2 |
| 6721869 | Senthil | Apr 2004 | B1 |
| 6724403 | Santoro et al. | Apr 2004 | B1 |
| 6725227 | Li | Apr 2004 | B1 |
| 6735583 | Bjarnestam et al. | May 2004 | B1 |
| 6744891 | Allen | Jun 2004 | B1 |
| 6847966 | Sommer et al. | Jan 2005 | B1 |
| 6904449 | Quinones | Jun 2005 | B1 |
| 6912398 | Domnitz | Jun 2005 | B1 |
| 6933928 | Lilienthal | Aug 2005 | B1 |
| 6938076 | Meyer et al. | Aug 2005 | B2 |
| 6985932 | Glaser et al. | Jan 2006 | B1 |
| 6999565 | Delaney et al. | Feb 2006 | B1 |
| 7007015 | Nayak | Feb 2006 | B1 |
| 7009596 | Seet et al. | Mar 2006 | B2 |
| 7010500 | Aarnio | Mar 2006 | B2 |
| 7020654 | Najmi | Mar 2006 | B1 |
| 7054914 | Suzuki et al. | May 2006 | B2 |
| 7057591 | Hautanen et al. | Jun 2006 | B1 |
| 7062707 | Knauft et al. | Jun 2006 | B1 |
| 7092116 | Calaway | Aug 2006 | B2 |
| 7103848 | Barsness et al. | Sep 2006 | B2 |
| 7107533 | Duncan et al. | Sep 2006 | B2 |
| 7130841 | Goel et al. | Oct 2006 | B1 |
| 7133506 | Smith | Nov 2006 | B1 |
| 7135932 | Quadir et al. | Nov 2006 | B2 |
| 7149776 | Roy et al. | Dec 2006 | B1 |
| 7165217 | Kondo | Jan 2007 | B1 |
| 7188085 | Pelletier | Mar 2007 | B2 |
| 7209888 | Frid-Nielsen et al. | Apr 2007 | B2 |
| 7237123 | LeVine et al. | Jun 2007 | B2 |
| 7246118 | Chastain et al. | Jul 2007 | B2 |
| 7249060 | Ling | Jul 2007 | B2 |
| 7249324 | Nakamura et al. | Jul 2007 | B2 |
| 7257577 | Fagin et al. | Aug 2007 | B2 |
| 7287068 | Eriksson et al. | Oct 2007 | B1 |
| 7290285 | McCurdy et al. | Oct 2007 | B2 |
| 7298851 | Hendricks et al. | Nov 2007 | B1 |
| 7304635 | Seet et al. | Dec 2007 | B2 |
| 7310629 | Mendelson et al. | Dec 2007 | B1 |
| 7313759 | Sinisi | Dec 2007 | B2 |
| 7350704 | Barsness et al. | Apr 2008 | B2 |
| 7355591 | Sugimoto | Apr 2008 | B2 |
| 7386480 | Sarig | Jun 2008 | B2 |
| 7398244 | Keith | Jul 2008 | B1 |
| 7401286 | Hendricks et al. | Jul 2008 | B1 |
| 7454238 | Vinayak et al. | Nov 2008 | B2 |
| 7496767 | Evans | Feb 2009 | B2 |
| 7506246 | Hollander et al. | Mar 2009 | B2 |
| 7509270 | Hendricks et al. | Mar 2009 | B1 |
| 7533152 | Stark et al. | May 2009 | B2 |
| 7539478 | Herley et al. | May 2009 | B2 |
| 7562032 | Abbosh et al. | Jul 2009 | B2 |
| 7574653 | Croney et al. | Aug 2009 | B2 |
| 7631013 | Parsons et al. | Dec 2009 | B2 |
| 7634429 | Narin et al. | Dec 2009 | B2 |
| 7656127 | Shutt et al. | Feb 2010 | B1 |
| 7657459 | Anderson et al. | Feb 2010 | B2 |
| 7657831 | Donahue | Feb 2010 | B2 |
| 7680849 | Heller et al. | Mar 2010 | B2 |
| 7720892 | Healey, Jr. et al. | May 2010 | B1 |
| 7760986 | Beuque | Jul 2010 | B2 |
| 7788369 | McAllen et al. | Aug 2010 | B2 |
| 7792756 | Plastina et al. | Sep 2010 | B2 |
| 7835989 | Hendricks et al. | Nov 2010 | B1 |
| 7849393 | Hendricks et al. | Dec 2010 | B1 |
| 7865405 | Hendricks et al. | Jan 2011 | B2 |
| 7865567 | Hendricks et al. | Jan 2011 | B1 |
| 7870022 | Bous et al. | Jan 2011 | B2 |
| 7900133 | Cragun et al. | Mar 2011 | B2 |
| 7908628 | Swart et al. | Mar 2011 | B2 |
| 8131647 | Siegel et al. | Mar 2012 | B2 |
| 8165998 | Semerdzhiev | Apr 2012 | B2 |
| 20010007980 | Ishibashi et al. | Jul 2001 | A1 |
| 20010025302 | Suzuki et al. | Sep 2001 | A1 |
| 20010027450 | Shinoda et al. | Oct 2001 | A1 |
| 20010027478 | Meier et al. | Oct 2001 | A1 |
| 20010037328 | Pustejovsky et al. | Nov 2001 | A1 |
| 20010049623 | Aggarwal et al. | Dec 2001 | A1 |
| 20010053975 | Kurihara | Dec 2001 | A1 |
| 20020002540 | DeMello et al. | Jan 2002 | A1 |
| 20020010707 | Chang et al. | Jan 2002 | A1 |
| 20020010759 | Hitson et al. | Jan 2002 | A1 |
| 20020012134 | Calaway | Jan 2002 | A1 |
| 20020035697 | McCurdy et al. | Mar 2002 | A1 |
| 20020054059 | Schneiderman | May 2002 | A1 |
| 20020069222 | McNeely | Jun 2002 | A1 |
| 20020069312 | Jones | Jun 2002 | A1 |
| 20020090934 | Mitchelmore | Jul 2002 | A1 |
| 20020091584 | Clark et al. | Jul 2002 | A1 |
| 20020092031 | Dudkiewicz et al. | Jul 2002 | A1 |
| 20020101447 | Carro | Aug 2002 | A1 |
| 20020103809 | Starzl et al. | Aug 2002 | A1 |
| 20020120635 | Joao | Aug 2002 | A1 |
| 20020123336 | Kamada | Sep 2002 | A1 |
| 20020129012 | Green | Sep 2002 | A1 |
| 20020138291 | Vaidyanathan et al. | Sep 2002 | A1 |
| 20020143822 | Brid et al. | Oct 2002 | A1 |
| 20020147724 | Fries et al. | Oct 2002 | A1 |
| 20020184319 | Willner et al. | Dec 2002 | A1 |
| 20020194474 | Natsuno et al. | Dec 2002 | A1 |
| 20030009459 | Chastain et al. | Jan 2003 | A1 |
| 20030018720 | Chang et al. | Jan 2003 | A1 |
| 20030025731 | Chastain et al. | Feb 2003 | A1 |
| 20030028395 | Rodgers et al. | Feb 2003 | A1 |
| 20030040970 | Miller | Feb 2003 | A1 |
| 20030052928 | Williams | Mar 2003 | A1 |
| 20030058265 | Robinson et al. | Mar 2003 | A1 |
| 20030065642 | Zee | Apr 2003 | A1 |
| 20030069812 | Yuen et al. | Apr 2003 | A1 |
| 20030093312 | Ukita et al. | May 2003 | A1 |
| 20030093382 | Himeno et al. | May 2003 | A1 |
| 20030097354 | Finlay et al. | May 2003 | A1 |
| 20030105679 | Krishnan et al. | Jun 2003 | A1 |
| 20030110503 | Perkes | Jun 2003 | A1 |
| 20030129963 | Nurcahya | Jul 2003 | A1 |
| 20030135495 | Vagnozzi | Jul 2003 | A1 |
| 20030152894 | Townshend | Aug 2003 | A1 |
| 20030163399 | Harper et al. | Aug 2003 | A1 |
| 20030164844 | Kravitz et al. | Sep 2003 | A1 |
| 20030182551 | Frantz et al. | Sep 2003 | A1 |
| 20030190145 | Copperman et al. | Oct 2003 | A1 |
| 20030191737 | Steele et al. | Oct 2003 | A1 |
| 20030204496 | Ray et al. | Oct 2003 | A1 |
| 20030212613 | Sarig | Nov 2003 | A1 |
| 20040002943 | Merrill et al. | Jan 2004 | A1 |
| 20040003398 | Donian et al. | Jan 2004 | A1 |
| 20040015467 | Fano | Jan 2004 | A1 |
| 20040030686 | Cardno et al. | Feb 2004 | A1 |
| 20040044723 | Bell et al. | Mar 2004 | A1 |
| 20040054499 | Starzyk et al. | Mar 2004 | A1 |
| 20040098350 | Labrou et al. | May 2004 | A1 |
| 20040117189 | Bennett | Jun 2004 | A1 |
| 20040120280 | Western | Jun 2004 | A1 |
| 20040128359 | Horvitz et al. | Jul 2004 | A1 |
| 20040139400 | Allam et al. | Jul 2004 | A1 |
| 20040167822 | Chasen et al. | Aug 2004 | A1 |
| 20040201633 | Barsness et al. | Oct 2004 | A1 |
| 20040205457 | Bent et al. | Oct 2004 | A1 |
| 20040212941 | Haas et al. | Oct 2004 | A1 |
| 20040237033 | Woolf et al. | Nov 2004 | A1 |
| 20040243613 | Pourheidari | Dec 2004 | A1 |
| 20040267552 | Gilliam et al. | Dec 2004 | A1 |
| 20040268253 | DeMello et al. | Dec 2004 | A1 |
| 20050021464 | Lindauer et al. | Jan 2005 | A1 |
| 20050022113 | Hanlon | Jan 2005 | A1 |
| 20050044148 | Son et al. | Feb 2005 | A1 |
| 20050044224 | Jun et al. | Feb 2005 | A1 |
| 20050066219 | Hoffman et al. | Mar 2005 | A1 |
| 20050069225 | Schneider et al. | Mar 2005 | A1 |
| 20050088410 | Chaudhri | Apr 2005 | A1 |
| 20050102618 | Naito | May 2005 | A1 |
| 20050125222 | Brown et al. | Jun 2005 | A1 |
| 20050138007 | Amitay | Jun 2005 | A1 |
| 20050138428 | McAllen et al. | Jun 2005 | A1 |
| 20050144895 | Grimes et al. | Jul 2005 | A1 |
| 20050176438 | Li | Aug 2005 | A1 |
| 20050177567 | Hughes et al. | Aug 2005 | A1 |
| 20050193330 | Peters | Sep 2005 | A1 |
| 20050195975 | Kawakita | Sep 2005 | A1 |
| 20050198070 | Lowry | Sep 2005 | A1 |
| 20050222977 | Zhou et al. | Oct 2005 | A1 |
| 20050250439 | Leslie | Nov 2005 | A1 |
| 20050256822 | Hollingsworth | Nov 2005 | A1 |
| 20060004840 | Senda | Jan 2006 | A1 |
| 20060020469 | Rast | Jan 2006 | A1 |
| 20060031316 | Forstadius | Feb 2006 | A1 |
| 20060047830 | Nair et al. | Mar 2006 | A1 |
| 20060048184 | Poslinski et al. | Mar 2006 | A1 |
| 20060057960 | Tran | Mar 2006 | A1 |
| 20060061595 | Goede et al. | Mar 2006 | A1 |
| 20060071754 | Tofts et al. | Apr 2006 | A1 |
| 20060075205 | Martin et al. | Apr 2006 | A1 |
| 20060080261 | Christal | Apr 2006 | A1 |
| 20060098900 | King et al. | May 2006 | A1 |
| 20060101328 | Albornoz et al. | May 2006 | A1 |
| 20060123053 | Scannell, Jr. | Jun 2006 | A1 |
| 20060129618 | Maier | Jun 2006 | A1 |
| 20060143558 | Albornoz et al. | Jun 2006 | A1 |
| 20060156222 | Chi et al. | Jul 2006 | A1 |
| 20060161578 | Siegel et al. | Jul 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060175983 | Crouse et al. | Aug 2006 | A1 |
| 20060179137 | Jennings et al. | Aug 2006 | A1 |
| 20060190489 | Vohariwatt et al. | Aug 2006 | A1 |
| 20060190568 | Patterson | Aug 2006 | A1 |
| 20060236240 | Lebow | Oct 2006 | A1 |
| 20060250994 | Sasaki et al. | Nov 2006 | A1 |
| 20060253441 | Nelson | Nov 2006 | A1 |
| 20060253461 | de Bonet | Nov 2006 | A1 |
| 20060256083 | Rosenberg | Nov 2006 | A1 |
| 20060265518 | Owens et al. | Nov 2006 | A1 |
| 20060281058 | Mangoaela | Dec 2006 | A1 |
| 20070014404 | Cha | Jan 2007 | A1 |
| 20070039023 | Kataoka | Feb 2007 | A1 |
| 20070050346 | Goel et al. | Mar 2007 | A1 |
| 20070061335 | Ramer et al. | Mar 2007 | A1 |
| 20070073596 | Alexander et al. | Mar 2007 | A1 |
| 20070079383 | Gopalakrishnan | Apr 2007 | A1 |
| 20070094285 | Agichtein et al. | Apr 2007 | A1 |
| 20070094351 | Kalish et al. | Apr 2007 | A1 |
| 20070105536 | Tingo, Jr. | May 2007 | A1 |
| 20070112817 | Danninger | May 2007 | A1 |
| 20070118533 | Ramer et al. | May 2007 | A1 |
| 20070136660 | Gurcan et al. | Jun 2007 | A1 |
| 20070136679 | Yang | Jun 2007 | A1 |
| 20070150456 | Lian et al. | Jun 2007 | A1 |
| 20070174545 | Okada et al. | Jul 2007 | A1 |
| 20070185865 | Budzik et al. | Aug 2007 | A1 |
| 20070189719 | Furumachi et al. | Aug 2007 | A1 |
| 20070219983 | Fish | Sep 2007 | A1 |
| 20070233562 | Lidwell et al. | Oct 2007 | A1 |
| 20070233692 | Lisa et al. | Oct 2007 | A1 |
| 20070234209 | Williams | Oct 2007 | A1 |
| 20070240187 | Beach et al. | Oct 2007 | A1 |
| 20070282809 | Hoeber et al. | Dec 2007 | A1 |
| 20070283173 | Webb et al. | Dec 2007 | A1 |
| 20070288853 | Neil | Dec 2007 | A1 |
| 20080005097 | Kleewein et al. | Jan 2008 | A1 |
| 20080005664 | Chandra | Jan 2008 | A1 |
| 20080027933 | Hussam | Jan 2008 | A1 |
| 20080031595 | Cho | Feb 2008 | A1 |
| 20080040233 | Wildman et al. | Feb 2008 | A1 |
| 20080082518 | Loftesness | Apr 2008 | A1 |
| 20080082911 | Sorotokin et al. | Apr 2008 | A1 |
| 20080089665 | Thambiratnam et al. | Apr 2008 | A1 |
| 20080113614 | Rosenblatt | May 2008 | A1 |
| 20080120280 | Iijima et al. | May 2008 | A1 |
| 20080133479 | Zelevinsky et al. | Jun 2008 | A1 |
| 20080163039 | Ryan et al. | Jul 2008 | A1 |
| 20080164304 | Narasimhan et al. | Jul 2008 | A1 |
| 20080168073 | Siegel et al. | Jul 2008 | A1 |
| 20080208833 | Basmov | Aug 2008 | A1 |
| 20080222552 | Batarseh et al. | Sep 2008 | A1 |
| 20080235351 | Banga et al. | Sep 2008 | A1 |
| 20080243788 | Reztlaff et al. | Oct 2008 | A1 |
| 20080243828 | Reztlaff et al. | Oct 2008 | A1 |
| 20080259057 | Brons | Oct 2008 | A1 |
| 20080293450 | Ryan et al. | Nov 2008 | A1 |
| 20080294674 | Reztlaff, II et al. | Nov 2008 | A1 |
| 20080295039 | Nguyen et al. | Nov 2008 | A1 |
| 20090094528 | Gray et al. | Apr 2009 | A1 |
| 20090094540 | Gray et al. | Apr 2009 | A1 |
| 20090181649 | Bull et al. | Jul 2009 | A1 |
| 20090228774 | Matheny et al. | Sep 2009 | A1 |
| 20090263777 | Kohn | Oct 2009 | A1 |
| 20090319482 | Norlander et al. | Dec 2009 | A1 |
| 20100023259 | Krumm et al. | Jan 2010 | A1 |
| 20100081120 | Nanjiani et al. | Apr 2010 | A1 |
| 20100188327 | Frid et al. | Jul 2010 | A1 |
| 20120041941 | King et al. | Feb 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 101120358 | Feb 2008 | CN |
| 101120358 | Feb 2008 | CN |
| 1842150 | Oct 2007 | EP |
| 2001100702 | Apr 2001 | JP |
| 2002099739 | Apr 2002 | JP |
| WO9720274 | Jun 1997 | WO |
| WO0045588 | Aug 2000 | WO |
| WO0056055 | Sep 2000 | WO |
| WO0075840 | Dec 2000 | WO |
| WO0239206 | May 2002 | WO |
| WO2004055647 | Jul 2004 | WO |
| WO2006078728 | Jul 2006 | WO |