Note: Descriptions are shown in the official language in which they were submitted.
CA 2680559 2017-03-22
81595463
1
PERSONALIZING HANDHELD ELECTRONIC BOOK READERS
BACKGROUND
As handheld electronic book reader devices become more popular and widely
accepted, early adopters of these devices may upgrade to newer, more capable
versions of
these readers. In some cases, customers who purchase a replacement may face
the prospect
of manually transferring content or information that they loaded into the
previous device.
Having to repeat previous effort may dissuade some customers from upgrading
their devices,
or from purchasing an electronic reader device at all.
SUMMARY OF THE INVENTION
According to an aspect of the present invention, there is provided a method
comprising: under control of one or more computer systems configured with
executable
instructions, receiving an indication that a customer device associated with a
customer has
accessed a network location through which an electronic book reader device is
offered;
receiving an order for the electronic book reader device from the customer
device, the
.. electronic book reader device being a replacement for a previous electronic
book reader
device associated with the customer, and wherein the customer device is
different from both
the electronic book reader device and the previous electronic book reader
device; receiving
an identifier associated with an account of the customer; obtaining
personalization
information associated with the identifier, the personalization information
including data
associated with the previous electronic book reader device; and loading the
personalization
information into the electronic book reader device before a first use of the
electronic book
reader device.
According to another aspect of the present invention, there is provided at
least
one non-transitory computer-readable storage medium having recorded thereon
computer-
executable instructions that when executed by at least one processor implement
the method
as described above.
CA 2680559 2017-03-22
81595463
la
According to another aspect of the present invention, there is provided a
method comprising: under control of one or more computer systems configured
with
executable instructions, receiving a first indication that a customer device
associated with a
first customer account has accessed a network location through which an
electronic device is
offered; receiving, in association with the first indication, a second
indication of a
transaction with the first customer account and via the network location, the
transaction
involving upgrading to the electronic device; receiving an identifier
associated with a second
customer account, wherein the first customer account is different from the
second customer
account; obtaining personal information associated with the second customer
account based
at least in part on the receiving of the identifier, the personal information
including: at least
one content item previously associated with the second customer account, and
data
associated with a previous electronic device associated with the second
customer account;
and loading the personal information associated with the second customer
account into the
electronic device before a first use of the electronic device, the loading
being based at least
in part on the receiving the second indication of the transaction involving
upgrading to the
electronic device.
According to another aspect of the present invention, there is provided a
method
comprising: under control of one or more computer systems configured with
executable
instructions, receiving a command to power-up an electronic book reader device
that has
been personalized prior to a first use of the electronic book reader device;
and responding to
the command by presenting a personalized welcome message on the electronic
book reader
device, the personalized welcome message including personalization information
that is
loaded into the electronic book reader device from a customer account
associated with a
different electronic book reader device prior to the first use of the
electronic book reader
device.
According to another aspect of the present invention, there is provided at
least
one non-transitory computer-readable storage medium having recorded thereon
computer-
executable instructions that when executed by at least one processor implement
the method
as described above.
81595463
lb
According to another aspect of the present invention, there is provided a
system
comprising: a server including at least one processor and at least one
computer-readable
storage medium, wherein the computer-readable storage medium includes a device
personalization component for: providing, to a customer device, a user
interface for
conducting a transaction with an account associated with a customer and for
offering a first
electronic book reader device in the transaction; and personalizing the first
electronic book
reader device before a first use of the first electronic book reader device,
the device
personalization component personalizing the first electronic book reader
device according to
data associated with a second electronic book reader device associated with
the customer
account, the data including at least one of: an electronic book or electronic
article that,
according to the customer account, has been previously licensed, or an
electronic periodical
that, according to the customer account, has been previously subscribed, the
first electronic
book reader device being a replacement for the second electronic book reader
device, and
the customer device being different from both the first electronic book reader
device and the
second electronic book reader device.
According to another aspect of the present invention, there is provided an
electronic book reader device comprising: at least one processor and at least
one non-
transitory computer-readable storage medium, wherein the at least one non-
transitory
computer-readable storage medium includes: a device personalization unit for
personalizing
the electronic book reader device by loading personalization data stored on a
previous device
associated with a customer account prior to a first use of the electronic book
reader device,
the personalization data including community membership information associated
with the
customer account, and instructions for presenting a personalized message,
wherein the
personalized message is generated based on the personalization data and
presented upon first
powering up the electronic book reader device.
BRIEF DESCRIPTION OF THE DRAWINGS
100011 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
CA 2680559 2019-01-30
, ¨
81595463
1 c
reference number first appears. The use of the same reference numbers in
different figures
indicates similar or identical components or features.
[0002]
Figure 1 is a block diagram illustrating components and data flows relating to
illustrative operating environments for personalizing handheld electronic book
readers.
CA 2680559 2019-01-30
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
2
[0003] Figure 2 is a block diagram illustrating server-side processes and
data
flows relating to personalizing handheld electronic book readers.
[0004] Figure 3 is a block diagram illustrating data structures suitable
for
personalizing handheld electronic book readers.
[0005] Figure 4 is a block diagram illustrating process flows for
personalizing
handheld electronic book readers.
[0006] Figure 5 is a block diagram illustrating client-side components
and data
flows relating to personalizing an electronic book reader (eBook) device.
[0007] Figure 6 is a block diagram illustrating components and data flows
relating to customer interactions with the cBook device.
[0008] Figure 7 is a block diagram illustrating process flows related to
example
customer interactions with the cBook device.
DETAILED DESCRIPTION
[0009] This disclosure is directed to tools and techniques related to
personalizing handheld electronic book readers. The description of these tools
and
techniques begins with an overview of illustrative operating environments for
personalizing handheld electronic book readers, presented with Figure 1.
[0010] Methods, systems, and computer-readable media (collectively,
"tools"
and/or "techniques") are described herein for personalizing handheld
electronic
book readers. The tools provide methods that include receiving an indication
of a
customer transaction involving an electronic book reader device. The methods
may
also receive an identifier associated with the customer, obtain
personalization
information associated with the identifier, and load the personalization
information
into the electronic book reader device. The tools also provide methods that
include
receiving a command that is input to the electronic book reader device, where
the
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
3
device has been personalized for the particular customer; and responding to
the
command using the personalization information. A server includes a processor
and
a computer-readable storage medium that includes a device personalization
component for personalizing the electronic book reader device. The electronic
book reader device includes a processor and computer-readable storage medium
that includes a device personalization unit for personalizing the electronic
book
reader device.
100111 For ease of description and understanding, but not to limit
implementations of the description herein, the following terms are used herein
with
these definitions. Books distributed using electronic technologies are
commonly
referred to as electronic books ("eBooks"). The terms "eBook" and "digital
work"
are used synonymously and, as used herein, may include electronic or digital
representations of printed works, as well as original electronic or digital
content that
may include text, multimedia, hypertext and/or hypermedia. Examples of eBooks
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.
[0012] Typically, digital works are structured as virtual frames
presented on a
display device, and a user may turn or change from one virtual frame or "page"
of
electronic content to another. The term "page" as used herein refers to a
collection
of content that is presented at one time on a display. Thus, "pages" as
described
herein are not fixed permanently, and may be redefined or repaginated based on
variances in display conditions, such as screen size, font type or size,
margins, line
spacing, resolution, or the like.
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
4
[0013] EBooks may be displayed and read on a variety of different display
devices, such as computer monitors, portable digital assistants (PDAs), pocket
personal computers (PCs), and specialized eBook reader devices, for example.
[0014] Also, while various aspects and features are described herein as
applied
to an eBook reader, the concepts may be implemented in other electronic
devices or
electronic readers besides eBook reader devices including, for example,
personal
computers, portable computers (e.g., laptops or pocket PCs), personal digital
assistants (PDAs), portable gaming devices, wireless phones, and the like.
[0015] Figure 1 illustrates components and data flows relating to
illustrative
operating environments 100 for personalizing handheld electronic book readers.
The operating environments may include one or more systems 102 that include
one
or more servers or other suitable computer-based processing systems, as shown
in
Figure 1. For ease of reference and discussion, but not limitation, this
description
refers to the system and the server 102 interchangeably.
100161 The operating environments 100 may provide at least the servers
102 as
part of infrastructure that supports one or more resources 104 that are
accessible
over a network 106. Examples of these network-accessible resources may include
Internet websites. Figure 1 shows two such network-accessible resources,
denoted
at 104a and 104n, but implementations of the operating environments may
include
any number of network-accessible resources.
100171 In some implementations, the network-accessible resources may
include
merchant websites that offer goods and/or services (collectively and
interchangeably referred to as "items") to customers 108. In the example shown
in
Figure 1, such items may include an electronic book ("eBook") reader device,
denoted at 110. In other possible implementations, the device 110 may take the
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
form of wireless telephones or personal digital assistants (PDAs). Examples of
the
device 110 may also include portable media, video, or audio players, or the
like.
[0018] Figure 1 denotes interactions between the websites and the
customers
generally at 112, and these interactions may include the customers providing
payments to or through the websites, in exchange for the eBook devices.
[0019] Having enabled the customers 108 to purchase the eBook devices,
whether for themselves or for other persons, the websites may authorize one or
more order fulfillment entities to deliver the eBook devices to the customers.
For
conciseness of illustration and description, Figure 1 does not depict such
order
fulfillment entities, but instead illustrates the server system 102 generally.
In so
doing, it is understood that at least parts of the description of the server
system 102
may be performed by such order fulfillment entities.
100201 Turning to the server system 102 in more detail, the server may
include
one or more processors 116 that communicate with one or more instances of
computer-readable storage media 118. The processors 116 may read data from or
write data to portions of the computer-readable storage media 118 in
performing
any of the functions described herein. Additionally, the computer-readable
storage
media 118 may contain software instructions that, when loaded into the
processors,
cause the server to perform any of the functions described herein.
100211 The storage media 118 may contain one or more software modules
that
define a device personalization unit 120, which represents a software-based
implementation of suitable instructions for personalizing the handheld
electronic
book readers for particular customers 108. As will become clear from the
description below, the device personalization unit 120 may be considered a
server-
side component that may cooperate with a corresponding client-side component
residing on, for example, the handheld electronic book readers 110.
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
6
[0022] The device personalization unit 120 may interact with a data store
122 to
personalize the handheld electronic book readers for the customers. The data
store
122 may, for example, include a data base that houses information relating to
particular customers, such that when a given customer orders an eBook device,
the
device personalization unit may personalize an cBook device for a particular
given
customer, and deliver the personalized eBook device to the customer. Figure 2
now
presents further details relating to ordering and personalizing the eBook
devices.
100231 Figure 2 illustrates server-side processes and data flows 200
relating to
personalizing handheld electronic book readers. For convenience but not
limitation,
some elements described above are carried forward into Figure 2, and are
denoted
by the same reference numbers.
[0024] As described in Figure 1, the server system 102 may include a
device
personalization unit 120 that enables the system to personalize handheld
electronic
book readers for particular customers 108. Assuming the personalization unit
is
implemented in connection with a website, for example, the personalization
unit
may populate a browser interface 202 that facilitates interaction with the
customer.
More specifically, the browser interface 202 may enable the customer to
provide
one or more identifiers relating to the customer. Figure 2 denotes these
identifiers
generally at 204.
100251 In some instances, the customer 108 who is ordering the eBook
device
may be the same customer who receives and uses the eBook device. In this case,
the customer 108 may provide identifiers 204 for himself or herself. However,
in
other instances, the customer 108 who is ordering the eBook device may not be
the
same customer who receives and uses the eBook device. For example, the
customer
108 may be ordering the eBook device as a gift for someone else. In these
latter
cases, the server system 102 may prompt the customer 108 to indicate whether
the
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
7
eBook device is intended for the customer 108, or for another person. If the
eBook
device is intended for another person, the server system 102 may direct the
customer to provide identifiers 204 for the intended recipient of the eBook
device.
[0026] For illustration only and not limitation, Figure 2 lists several
examples of
the identifiers 204 that may be collected from the customer. Implementations
of the
operating environments described may include one or more, but not necessarily
all,
of these examples. A name field 206 may indicate the name of the customer. A
telephone number field 208 may indicate a landline or wireless telephone
number
associated with the customer. This field 208 may also indicate IP addresses
for
those customers who use voice-over-IP (VoIP) technology. A field 210 may
contain data representing a customer number that identifies records associated
with
the customer, as maintained by a website. A mailing address field 212 may
contain
data representing a delivery address for shipping the eBook device to the
customer.
An e-mail address field 214 may contain data representing an e-mail address
for the
customer. A field 216 may contain any other data suitable for uniquely
identifying
the customer.
100271 In some instances, the customer 108 may be a repeat customer of
the
website, and the website may have records of previous dealings with the
customer.
More specifically, a data store (e.g., the data store 122) may contain these
records.
In these instances, the device personalization unit 120 may query these
records to
obtain information used to personalize the eBook reader ordered by the
customer.
Figure 2 generally represents these queries at 218. The queries 218 may
include at
least one or more of the identifiers obtained from the customer as indexes or
search
keys. Figure 2 denotes the identifiers as included in the queries at 204a.
[0028] The data store 122 may search its records for any data matching
the
search criteria specified in the queries 218. If the data store contains any
records
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
8
matching the search criteria specified in the query 218, the data store may
return
these records in response to the query. Figure 2 generally denotes these
responses
as personalization data 224.
[0029] The personalization data 224 may include one or more of the
example
fields shown in Figure 2. A transaction history field 226 may contain data
representing previous transactions involving the customer 108. These previous
transactions may include previous purchases, inquiries about items, requests
for
information, or the like. An interests/preferences field 228 may contain data
representing particular areas of interest to the customer, whether expressly
specified
or inferred from previous interactions. A subscription information field 230
may
indicate any publications to which the customer subscribes, whether in printed
or
electronic form. A community memberships field 232 may indicate any groups
(e.g., online discussion groups) of which the customer is a member. A contact
list
field 234 may contain one or more address book entries associated with the
customer 108. A content field 236 may contain digital or electronic content
that the
customer may access using the eBook device (e.g., 114). Such content may
include
electronic books licensed by the customer, or electronic articles or
periodicals to
which the customer subscribes. A bookmarks field 238 may indicate any
bookmarks inserted in electronic content by the customer.
100301 It is noted that any of the fields 226-238 could contain the
information
described herein, or may contain pointers to where that information is stored.
It is
also noted that in some instances, the customer 108 may be obtaining the eBook
device as a replacement for a previous eBook device or other electronic
device. In
these instances, one or more of the fields 226-238 may have been populated
using
the previous device, and the device personalization unit 120 may transfer one
or
more of these fields to the new device. In this manner, the device
personalization
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
9
unit may enable a seamless experience for the customer in transitioning from
the
previous device to the new device.
[0031] Without loss of generality, examples of the personalization data
may
include information that is loaded onto the previous device after the previous
device
has been delivered to the customer. The personalization data may include
information and/or content that the customer specifically selects for loading
onto
the device. On at least these bases, the personalization data is distinguished
from
information related to providing local number portability (LNP) capability in
the
context of telecommunications services.
[0032] In cases in which the customer is new to the website, the device
personalization unit may prompt the customer for at least some of the
information
described in the fields 226-238. If the customer provides any information in
response to these prompts, the device personalization unit may store this
information in the appropriate fields 226-238. In turn, the device
personalization
unit may use at least some of this information to personalize the eBook device
for
the customer.
100331 Having described the processes and data flows relating to
personalizing
handheld electronic book readers in Figure 2, the discussion now turns to a
description of data structures that may be suitable for implementing the data
store,
now presented with Figure 3.
100341 Figure 3 illustrates data structures 300 suitable for
personalizing
handheld electronic book readers. For convenience but not limitation, some
elements described above are carried forward into Figure 3, and are denoted by
the
same reference numbers.
[0035] An example of the data store is carried forward at 122. The data
store
may include a plurality of records 302. The records 302 may, for example,
contain
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
information relating to respective different customers (e.g., 108 in Figure
1).
Figure 3 shows two examples of the records 302, denoted at 302a and 302n.
However, it is noted that the data store may contain any number of records,
depending on how many customers have information contained in the data store.
[0036] Turning to the records 302 in more detail, for convenience, Figure
3
shows these records as organized by customer identifier fields 304 and by
personalization data fields 306. Figure 3 shows two examples of the customer
identifier fields, denoted at 304a and 304n, and shows two examples of the
personalization data fields, denoted at 306a and 306n.
[0037] The customer identifier fields 304 contain any information
pertaining to
the customers that may serve as search keys or indexes when querying the data
store
122. For example, the identifiers 204 obtained from the customers as shown in
Figure 2 may correspond to the customer identifier fields 304. Accordingly,
the
customer identifier fields 304 may contain at least one of the subfields 206-
216, as
illustrated in Figure 3.
100381 The personalization data fields 306 may contain any information
used to
personalize the eBook reader for a particular customer. in some instances, the
data
stored in the customer identifier fields 304 and the personalization data
fields 306
may overlap, in other words, searchable data may also be loaded onto the eBook
reader to personalize the device. The personalization data 224 as shown in
Figure 2
may correspond to the. personalization data fields 306. Accordingly, the
personalization data fields 306 may contain at least one of the subfields 226-
238, as
illustrated in Figure 3.
100391 Having described the data structures 300 in Figure 3, the
discussion now
turns to a description of server-side process flows for personalizing handheld
electronic book readers, now presented with Figure 4.
CA 02680559 2015-05-06
50655-19
II
100401 Figure 4 illustrates process flows 400 for personalizing
handheld
electronic book readers. While these process flows 400 are described here as
being
performed by certain systems and components, such as the server 102 and the
device personalization unit 120, other systems and components may also perform
at
least parts of the process flows 400 without departing from the scope of
the description herein. For convenience but not limitation, some elements
described above are carried forward into Figure 4, and are denoted by the same
reference numbers.
100411 Block 402 represents receiving an indication of a customer
interaction
with, for example, a website hosted on the server system 102. This customer
interaction may involve a customer (e.g., 108 in Figure 1) purchasing or
inquiring
about an eBook device (e.g., 110 in Figure 1) through the website.
[0042] Block 404 represents receiving one or more identifiers
associated with
the customer. Figure 2 shows examples of such identifiers at 204. Generally,
these
identifiers may take any form suitable to enable the process 400 to determine
the
identity of the customer, to personalize the eBook device with information for
the
appropriate person. Figures 2 and 3 provide non-limiting examples of such
identifiers at 206-216.
100431 Block 406 represents querying for personalization data relating
to the
customer whose identifier was received in block 404. In some instances, block
406
may include querying a data store (e.g., 122 in Figure 1) for any records
pertaining
to a particular customer, as denoted at block 408. In other instances, block
406 may
include prompting the customer for at least some of this personalization data,
as
denoted at block 410.
[0044] Block 412 represents receiving personalization data for a
particular
customer. In different possible scenarios, block 412 may include receiving at
least
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
12
some personalization data from the data store, as represented in block 414. In
addition to, or instead of, the personalization data received from the data
store,
block 408 may include receiving at least some personalization data directly
from the
customer, as represented in block 416. Block 416 may include receiving the
personalization data in response to the prompting represented in block 410.
[0045] In
transactions involving new customers, the data store may not contain
any personalization data or other information pertaining to these new
customers. In
these transactions, the personalization data may primarily include information
obtained directly from the customer. In other transactions involving existing
customers, the personalization data may include only information queried from
the
data store. In other cases, the process flow 400 may include supplementing or
clarifying information from the data store, as appropriate, through
interaction with
the customer.
100461 Block 416
represents loading the personalization data into an eBook
device to be personalized. The previous Figures show examples of such devices
at
110. In
addition, Figures 2 and 3 provide non-limiting examples of such
personalization data at 226-238.
[0047] Having
described the server-side process flows 400 in Figure 4, the
discussion now proceeds to a description of components and data flows relating
to
the electronic book reader (eBook) device, now presented in Figure 5.
100481 Figure 5
illustrates client-side components and data flows 500 relating to
personalizing an electronic book reader (eBook) device. For convenience but
not
limitation, some elements described above are carried forward into Figure 5,
and
are denoted by the same reference numbers.
[0049] As
described above, the server system 102 may include the device
personalization unit 120, which may function as a server-side component that
loads
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
13
personalization data (e.g., 224) into the electronic book reader (eBook)
device (e.g.,
110).
[0050] Turning to
the eBook device 110 in more detail, it may include a
processor 502 coupled to a communications interface 504. In some
implementations, the communications interface 504 may include one or more
connectors, ports, adapters, and related driver software for a wired network
(e.g., a
local area network) or a universal serial bus (USB) port, denoted generally at
506.
In other implementations, the communications interface 404 may include
adapters
and related drivers for a wireless interface (e.g., a WiFi interface), denoted
generally at 508.
[0051] Through
the communications interface 504, the eBook device 110 may
receive the personalization data from the server system 102, as represented at
224a.
Additionally, the eBook device 110 may include one or more computer-readable
storage media 510, which may store the personalization data 224 as received
from
the server system 102. The computer-readable storage media 510 may also
include a
device personalization unit 512, which may provide a client-side counterpart
to the
device personalization unit 120 that resides on the server system 102. As
such, the
device personalization unit 512 may include a set of computer-readable
instructions
that, when loaded into the processor 502 and executed, cause the eBook device
110
to perform any of the functions attributed herein to the eBook device. As
detailed
further below, the device personalization unit 512 may load and process the
personalization data to cause the eBook device to, for example, present
customer-
specific information.
100521 Having
described components and data flows 500 relating to the eBook
device in Figure 5, the discussion now turns to a description of customer
interactions with the eBook device, now presented in Figure 6.
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
14
[0053] Figure 6 illustrates components and data flows 600 relating to
customer
interactions with the eBook device. For convenience but not limitation, some
elements described above are carried forward into Figure 6, and arc denoted by
the
same reference numbers.
[0054] Figure 6 shows an example of the eBook device at 110, carried
forward
from previous drawings. A customer, denoted generally at 602, may receive the
eBook device. The customer 602 shown in Figure 1 may or may not be the same
customer (e.g., 108 in Figure 1) who ordered the eBook device, in an example
described above, the customer 108 may order the eBook device as a gift for
another
person, who may be the customer 602 shown in Figure 6.
[0055] The eBook device may include one or more processors 502 and one or
more computer readable storage media 510, carried forward from Figure 5. The
computer readable storage media 510 as shown in Figure 6 may contain the
personalization data 224a, and the device personalization unit 512, also
carried
forward from previous Figures, for ease of reference, but not limitation.
100561 The eBook device may also include a user interface 604 that is
coupled to
communicate with the processor 502 and the computer readable storage media
510.
The user interface 604 may include output components, such as one or more
display
screens for presenting visual information visually to the customer 602, and/or
one
or more speakers or the other devices for providing audible information to the
customer. The user interface 604 may include input components, such as one or
more touch-sensitive panels or displays, rotary input devices (e.g.,
trackballs),
pointers, mice, keyboards or keypads, or the like.
100571 Having received the eBook device, the customer 602 may interact
with
the eBook device through the user interface 604, with these interactions
denoted
generally at 606. These interactions 606 may include one or more commands 608
CA 02680559 2015-05-06
50655-19
that are issued by the customer to the eBook device. The customer may provide
these commands using any feature of the user interface 604. The eBook device
processes the commands from the customer, and provides responses 610 thereto.
More specifically, the device personalization unit 512 may process these
commands
and generate output to the customer in response to the commands, based on the
personalization data 224a.
100581 Having described the components and data flows 600 relating to
customer interactions with the eBook device in Figure 6, the discussion now
proceeds to a description of process flows related to example customer
interactions
with the eBook device, now presented in Figure 7.
100591 Figure 7 illustrates process flows 700 related to example
customer
interactions with the eBook device. For convenience but not limitation, some
elements described above are carried forward into Figure 7, and are denoted by
the
same reference numbers. Additionally, while these process flows 700 are
described
here as being performed by certain systems and components, such as the server
102
and the client-side device personalization unit 512, other systems and
components
may also perform at least part of the process flow 700 without departing from
the
scope of the description herein.
f00601 Block 702 represents receiving a command from a customer using
the
eBook device (e.g., 602 in Figure 6). Block 702 may include receiving the
command through a user interface (e.g., 604 in Figure 6).
100611 Block 704 represents responding to the command received in
block 702,
using personalized data specific to the customer using the eBook device. The
previous Figures provide examples of the personalized data at 224a, which is
carried forward into Figure 7 for ease of reference, but not limitation.
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
16
[0062] Figure 7 also provides several non-limiting examples of commands
and
responses that the personalized data 224a may facilitate. These examples arc
provided only for ease of understanding, and do not limit possible
implementations
of the description herein.
[0063] Block 706 represents receiving a command to power-up the eBook
device. For example, the user may have activated an on-off button provided by
the
eBook device. In response to the power-up command, as represented by block
708,
the eBook device may present a personalized message to the customer, using a
name of the customer as indicated in the personalization data. For example
only,
the eBook device may display a welcome message that includes text such as:
"Hello Mr. Davis, congratulations on your purchase!"
[0064] Block 708 may include displaying the welcome message each time the
device is powered-up, or may include displaying the message only the first
time that
the device is powered-up. In some instances, block 708 may include displaying
a
message such as the one above only the first time the device is powered-up,
but
displaying other personalized messages afterwards.
100651 Block 710 represents receiving a command to obtain content for
display
on the eBook device. For example, the user may request content stored in an
older
eBook device and transitioned to the new eBook device (e.g., electronic
content at
236 in Figure 2). As another example, the user may begin searching for content
of
possible interest, for downloading to the eBook device.
100661 In response to such a command, or asynchronously therewith, block
712
represents recommending or providing content to the customer. As noted above,
this content may include content stored on a previous eBook device and copied
to
the new eBook device. In this example, block 712 may include incorporating any
previous bookmarks or annotations inserted by the customer (e.g., 238 in
Figure 2).
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
17
Additionally, block 712 may include transferring any subscriptions by which
the
customer may access articles or periodicals (e.g., 230 in Figure 2).
[0067] In other instances, block 712 may include analyzing previous
transaction
history involving the customer (e.g., 226 in Figure 2) to determine what
content
may be of interest to the customer. Block 712 may include recommending any
content identified by this analysis for consideration by the customer.
[0068] Additionally, block 712 may include analyzing any information
indicating item preferences or items of interest to the customer, whether
expressly
specified by the customer, or inferred from previous customer activity. Figure
2
shows examples of this information at 228. Block 712 may include recommending
any content resulting from this analysis as well.
[0069] Block 714 represents receiving a command to display content on the
eBook device. For example, the customer may select a particular instance of
content for display on the eBook device. Examples of content may include
electronic or digital representations of text.
100701 Block 716 represents displaying the content requested by the
customer.
The eBook device may enable the customer to specify a zoom level at which the
eBook device may render these representations of text for viewing by the
customer.
These zoom levels may be set on a per-content basis, or may apply globally to
any
content displayed on the eBook device.
100711 In cases where the customer is replacing a previous eBook device
with
another eBook device, these zoom levels may be incorporated into the
preference
information (e.g., 228) and transferred to the new eBook device. In this
manner,
block 716 may include enabling the customer to continue viewing content using
the
same settings specified on the previous device, thereby providing a more
seamless
transition from the previous device to a replacement device.
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
18
[0072] Block 718 represents receiving a command to access a contact. For
example, block 718 may include receiving a request from the customer to access
one or more contacts in an address book or contact list. Also, block 718 may
include receiving a request to access the address book or contact list as a
whole,
rather than entries contained therein.
[0073] Block 720 represents providing the contact information requested
in
block 718. In instances in which the customer obtains the eBook device as a
replacement for a previous device, block 720 may include sending entries from
an
address book or contact list on the previous device. This address book or
contact
list from the previous device may be included in the personalization data
loaded
onto the new device. Figure 2 shows examples of this address book or contact
list
or contact information at 234.
100741 Block 722 represents receiving a command to access a community or
other group construct of which the customer is a member. If the customer is a
member of more than one such community, block 722 may include receiving an
indication of which community the customer wishes to access. In some
instances,
block 722 may include receiving a request to list the communities of which the
customer is a member, or to list all communities that the customer may join.
100751 Block 724 represents providing the customer access to the
community
requested in block 722. As discussed above with the contact list information,
in
cases where the customer obtains the eBook device as a replacement for a
previous
eBook device, the personalization data may include the community membership
information from the previous eBook device (e.g., at 232 in Figure 2). In this
manner, this previous community membership information may be transferred to
the new eBook device, enabling the customer to access his or her communities
or
groups without manually reloading this information.
CA 02680559 2009-09-08
WO 2008/112038 PCT/US2007/089123
19
Conclusion
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.
