WO2013132689A1

WO2013132689A1 - Terminal device, method for controlling same, storage medium, and content-playback system

Info

Publication number: WO2013132689A1
Application number: PCT/JP2012/076814
Authority: WO
Inventors: 嶋田　光伸; 名古　和行; 石塚　康司
Original assignee: シャープ株式会社
Priority date: 2012-03-09
Filing date: 2012-10-17
Publication date: 2013-09-12
Also published as: JP2013186805A

Abstract

A terminal device is provided with the following: a playback unit for playing back content; a generation unit for generating associated information that is associated with content that the playback unit is capable of playing back; a storage unit for storing said associated information; and a transmission unit for transmitting the associated information generated by the generation unit to a server device. The playback unit plays back content on the basis of the associated information stored in the storage unit. The transmission unit transmits the associated information generated by the generation unit to the server device independently from the commencement or conclusion of the viewing of the content with which the associated information is associated.

Description

Terminal device and control method thereof, storage medium, and content reproduction system

The present invention relates to a terminal device, a control method thereof, a storage medium, and a content reproduction system, and more particularly to a terminal device that handles incidental information of a content, a control method thereof, a storage medium, and a content reproduction system.

Conventionally, there has been a technology in which content that can be browsed for each user is managed by a server, and a list of the content can be displayed on a terminal device operated by the user.

In addition, as disclosed in, for example, Patent Document 1 (Japanese Patent Laid-Open No. 2000-155766), such a technique includes information attached to content such as a bag sent from a terminal device (hereinafter referred to as “accompanying information”). Some of them managed. In the networking library system described in the document, when the viewer selects content that the viewer wants to browse, the history of the viewer is checked, and if the information to insert the accompanying information is registered, the content and the accompanying information are registered. Data for displaying information is transmitted to the terminal device of the viewer. In the system, accompanying information is transmitted to the system at the end of browsing by the viewer.

JP 2000-155766 A

According to the above-described conventional technology, the terminal device used for browsing the content can receive the accompanying information and can send the accompanying information to the server only when it can communicate with the system (server). It was.

Accordingly, when content is viewed in a state where the terminal device cannot communicate with the server (for example, a place where the communication environment is not established) or in a state where communication is not performed, and the accompanying information is generated in the terminal device, the accompanying information is stored in the server. It was not possible to manage.

The present invention has been conceived in view of such a situation, and an object of the present invention is to enable the server to manage the accompanying information of the content generated without the terminal device communicating with the server. is there.

According to a certain aspect, a terminal device is provided. The terminal device includes a playback unit for playing back content, a generation unit for generating accompanying information that is information accompanying content that can be played back by the playback unit, a storage unit for storing accompanying information, and generation A transmission unit for transmitting the accompanying information generated by the unit to the server device. The reproduction unit reproduces the content based on the accompanying information stored in the storage unit. The transmission unit transmits the accompanying information generated by the generating unit to the server device independently of the start or end of browsing the content corresponding to the accompanying information.

Preferably, the terminal device includes, from the server device, a receiving unit for receiving notification that the accompanying information transmitted by the transmitting unit is in conflict with other accompanying information already stored in the server device, and a receiving unit And an input unit for inputting information as to whether or not to change the accompanying information transmitted by the transmission unit based on the received notification. The receiving unit stores the corrected incidental information in the storage unit when the information permitting the change of the incidental information transmitted by the transmission unit is input to the input unit.

Preferably, the terminal device includes, from the server device, a receiving unit for receiving notification that the accompanying information transmitted by the transmitting unit is in conflict with other accompanying information already stored in the server device, and a receiving unit And an input unit for inputting an instruction to register the accompanying information transmitted by the transmission unit in the server device based on the received notification. When an instruction for registration of the accompanying information in the server device is input to the input unit, the transmitting unit transmits information indicating the registration of the accompanying information transmitted by the transmitting unit to the server device.

According to another aspect, there is provided a storage medium in which a control program for the terminal device that can be executed by a computer of the terminal device including a storage unit and a playback unit for playing back content is recorded non-temporarily. The control program generates, to the computer, a step of generating accompanying information that is information attached to content that can be played back by the playback unit, a step of storing the accompanying information in the storage unit, and a generated accompanying information to the server device. Step. The reproduction unit reproduces the content based on the accompanying information stored in the storage unit. The step of transmitting the accompanying information to the server device includes transmitting the generated accompanying information to the server device independently of the start or end of browsing the content corresponding to the accompanying information.

According to still another aspect, there is provided a control method for a terminal device that is executed by a computer of the terminal device that includes a storage unit and a playback unit that plays back content. The control method includes a step of generating accompanying information, which is information attached to content that can be played back by the playback unit, a step of storing the accompanying information in a storage unit, and a step of transmitting the generated accompanying information to a server device. Prepare. The reproduction unit reproduces the content based on the accompanying information stored in the storage unit. The step of transmitting the accompanying information to the server device includes transmitting the generated accompanying information to the server device independently of the start or end of browsing the content corresponding to the accompanying information.

According to another aspect, a content reproduction system including a terminal device including a reproduction unit for reproducing content and a server device capable of communicating with the terminal device is provided. In the content reproduction system, the terminal device includes a generation unit for generating accompanying information that is information accompanying the content that can be played back by the playback unit, a first storage unit for storing the accompanying information, and a generation unit. A transmission unit for transmitting the generated accompanying information to the server device. The server device includes a second storage unit for storing accompanying information of the content. The reproduction unit reproduces the content based on the accompanying information stored in the first storage unit. The transmission unit transmits the accompanying information generated by the generating unit to the server device independently of the start or end of browsing the content corresponding to the accompanying information.

Preferably, in the content reproduction system, the server device further includes a management unit for managing accompanying information transmitted by the transmission unit. The management unit determines whether or not the accompanying information transmitted by the transmitting unit and the accompanying information stored in the second storage unit compete with each other, and determines that the accompanying information transmitted by the transmitting unit is received. The information is corrected so as to avoid the conflict, and the accompanying information after correction is stored in the second storage unit.

Preferably, in the content reproduction system, when the management unit determines that the accompanying information transmitted by the transmitting unit and the accompanying information stored in the second storage unit compete with each other, the corrected accompanying information is transmitted to the terminal device. Send.

Preferably, in the content reproduction system, when the management unit determines that the accompanying information transmitted by the transmission unit and the accompanying information stored in the second storage unit compete with each other, the management unit stores the corrected accompanying information in the terminal device. An inquiry is made as to whether or not registration is possible, and on the condition that a reply permitting registration has been received, the accompanying information after correction is stored in the second storage unit.

According to the present invention, the accompanying information of the content is transmitted to the server device independently of the start or end of browsing of the content corresponding to the accompanying information.

Thereby, the accompanying information generated in a state in which the terminal device cannot communicate with the server device can be managed by the server device.

It is a figure which shows typically the whole structure of the content delivery system containing one Embodiment of the terminal device of this invention, and a server apparatus. It is a figure which shows typically the hardware constitutions of a terminal. It is a figure which shows typically the hardware constitutions of a content server. It is a figure which shows an example of the content of a meta information file. It is a figure which shows an example of the bookshelf screen displayed on a display part, when the terminal is operate | moving in local mode. It is a figure which shows an example of the bookshelf screen displayed on a display part, when the terminal is operate | moving in online mode. It is a flowchart of the process which a process part performs in order to display a bookshelf screen which was demonstrated with reference to FIG. 5 or FIG. 6 in the terminal. It is a flowchart of the subroutine of the process in step S60 of FIG. It is a flowchart of the said process which the process part of a terminal performs. It is a figure which shows an example of the external appearance of a terminal. It is a figure which shows an example of the screen for displaying accompanying information. It is a flowchart of a backup process. It is a flowchart of the process performed in a content server according to the request | requirement from the terminal in the process of FIG. It is a figure which shows an example of the screen of an inquiry displayed in a terminal. It is a figure which shows an example of the screen which alert | reports that backup of accompanying information was complete | finished. It is a figure which shows an example of the screen displayed in the terminal which received the accompanying information which was not registered. It is a flowchart of the modification of the backup process of FIG. It is a flowchart of the modification of the process of the process part of the content server of FIG. It is a flowchart of the subroutine of step SA540 of FIG. It is a flowchart of the process corresponded to the modification of the process of FIG. 18 of a modification (1). It is a flowchart of the process corresponded to the modification of the process of FIG. 19 of a modification (1). It is a figure which shows an example of the display screen of the dialog in a terminal. It is a flowchart of the process performed for taking out accompanying information in a terminal. It is a flowchart of the process performed in the content server 300 which received the extraction request | requirement from the terminal. It is a figure which shows an example of the screen which displays the list of the content used as the object of extraction of accompanying information. FIG. 11 is a diagram illustrating an example of a screen displayed on the display unit by the processing unit to notify the fact when the accompanying information extraction process is completed. It is a figure for demonstrating the specific example of a terminal device. It is a figure for demonstrating the specific example of a terminal device. It is a figure for demonstrating the specific example of a terminal device. It is a figure for demonstrating the specific example of a terminal device.

Hereinafter, embodiments of the terminal device of the present invention will be described with reference to the drawings. In the following description, elements having the same function and action are denoted by the same reference numerals throughout the same drawings, and redundant description will not be repeated.

<Overall system configuration>
FIG. 1 is a diagram schematically showing an overall configuration of a content distribution system including an embodiment of a terminal device and a server device of the present invention. In the present specification, the “terminal device” may be simply referred to as “terminal” for convenience.

In the system shown in FIG. 1, each of the terminals 100A to 100C communicates with the content server 300 via the network 1000. As a result, the contents are downloaded, stored, and reproduced in each of the terminals 100A to 100C. Note that the reproduction of content in the terminals 100A to 100C is not limited to being performed after downloading, and may be performed by streaming. In this specification, the terminals 100A to 100C may be collectively referred to as “terminal 100”.

The terminals 100A to 100C may be owned by the same user, for example. The user can download content on one or more of the terminals 100A to 100C and play the content on each terminal with respect to the content that the user has the right to use by purchasing or the like.

In this specification, “the user has the right to use the content” is not limited to the case where the user purchases the content, but has the qualification to play the content by becoming a member of a specific group. If the content can be played back by storing the content created by the user in a storage device accessible by the user, the free content can be played back for so-called free content provided to everyone. Including cases where possible.

In the system of FIG. 1, the terminals 100A to 100C are owned by the same user, and the user has the right to use the

contents

901, 902, and 903. In the system shown in FIG. 1, the user downloads the content 901 from the terminal 100A, downloads the content 902 from the terminal 100B, and downloads the content 903 from the terminal 100C.

In the present embodiment, content means files of various formats such as electronic books, audio files, moving image files, and text files. In this specification, browsing of an electronic book is mainly described as an example of content reproduction. Note that the type of content to be played back in the present invention is not limited to an electronic book, and files of various forms such as music content, moving image content, and still image content are targeted.

The book database (DB) 310 is provided in the system of FIG.
The book DB 310 stores data on the main body of each content, information for identifying content purchased by each user (user purchase history DB), and information such as the storage location of each content. The book DB 310 generates a list of contents (content list) each user has a right to use based on information stored in the user purchase history DB and the bibliographic information DB, and distributes the list to the terminals 100A to 100C.

Each of the terminals 100A to 100C obtains a content list for content that the user of each terminal has usage rights from the book DB 310.

<Terminal block configuration>
FIG. 2 is a diagram schematically illustrating a hardware configuration of the terminal 100.

The terminal 100 includes a processing unit 101 that controls the operation of the terminal 100 as a whole, a display unit 102 that includes a display device such as a liquid crystal display device, and an operation unit 103 that includes an input device such as a touch sensor. A storage unit 104 configured by a recording medium such as a hard disk, a communication unit 105 configured by a communication device such as a modem, and a flash memory 106.

The processing unit 101 includes a processor such as a CPU (Central Processing Unit).
The storage unit 104 includes a content storage unit 104A for storing data of the content body, a content DB 104B for storing bibliographic information of the content, and a user information storage unit 104C for storing information related to the user of the terminal 100. And an accompanying information storage unit 104D for storing accompanying information of the content.

Storage unit 104 may be fixed to the main body of terminal 100, or may be a storage medium that can be attached to and detached from the main body of terminal 100. Specific examples of such storage media include, for example, CD-ROM (Compact Disk-Read Only Memory), DVD-ROM (Digital Versatile Disk-Read Only Memory), USB (Universal Serial Bus) memory, memory card, FD. (Flexible Disk), hard disk, magnetic tape, cassette tape, MO (Magnetic Optical Disk), MD (Mini Disk), IC (Integrated Circuit) card (excluding memory card), optical card, mask ROM, EPROM, EEPROM (Electronically Non-volatile media such as Erasable Programmable Read Only Memory).

The processing unit 101 functions as a content playback unit 101A for playing back content stored in the content storage unit 104A and the like, and for displaying information on the content included in the content list on a display device such as the display unit 102. List display section 101B.

The terminal 100 may not include a display device. In this case, the list display unit 101B causes the display device connected to the terminal 100 to display content information. The display unit 102 is realized by driver software or a driver circuit of the display device. In this case, the content playback unit 101A displays a video (or image) playback screen on the display device.

When the content to be played back includes audio data, the content playback unit 101A causes the internal speaker of the terminal 100 or an external speaker to output audio based on the audio data.

The processing unit 101 further includes a content acquisition unit 101C and a content list acquisition unit 101D as its functions.

The content acquisition unit 101C acquires desired content from the content distribution server 200 via the communication unit 105 and the network 1000. The acquired content is stored in the content storage unit 104A of the storage unit 104. The content list acquisition unit 101D acquires a content list from the content server 300 via the communication unit 105 and the network 1000. The acquired content list is stored in the content DB 104B.

The processing unit 101 further communicates with other devices as an accompanying information generation unit 101E that generates accompanying information, an accompanying information acquisition unit 101F that acquires accompanying information from another device via the communication unit 105, and the like. And an accompanying information transmitting unit 101G that transmits accompanying information via the unit 105.

Each function of the processing unit 101 is realized, for example, when the CPU executes a predetermined program. As an example of the program, an electronic book browsing application program (hereinafter referred to as “electronic book application”) can be cited.

The flash memory 106 is a non-volatile memory that does not lose its stored contents even when the power is turned off, and functions as a cache memory that temporarily records a content list downloaded from the content server 300 as cache data, as will be described later ( It also functions as a data memory that records data other than cache data). In addition, data other than cache data can be recorded in an area of the flash memory 106 where no cache data is recorded.

Here, “cache data” is data stored in the flash memory 106. The “cache memory” is a function for temporarily recording the above-described content list and for reading the data from the flash memory instead of the storage unit 104 when the data is read to the storage unit 104. It is a memory having As the flash memory 106, a NAND flash memory or a NOR flash memory may be used.

<Hardware configuration of content server>
FIG. 3 is a diagram schematically illustrating a hardware configuration of the content server 300.

Referring to FIG. 3, the content server 300 is a communication unit configured by a processing unit 301 that controls the overall operation of the content server 300, a storage unit 302 configured by a storage medium, and a communication device such as a modem. Part 303.

The storage unit 302 includes a book DB 310 and an accompanying information storage unit 311.
The book DB 310 includes at least a user purchase history DB that stores content purchase history for each user, a bibliographic information DB that stores bibliographic information for each content, and a content storage unit that stores data of the content main body. The accompanying information storage unit 311 stores an accompanying information DB described later.

The processing unit 301 includes a processor such as a CPU. The processing unit 301 includes, as its functions, a list generation unit 301A, a list distribution unit 301B, an accompanying information management unit 301C, and a content distribution unit 301X.

The list generation unit 301A generates a content list for each user based on information stored in the user purchase history DB and the bibliographic information DB. The list distribution unit 301B transmits the content list requested to be transmitted to the terminal 100 or the like via the communication unit 303 and the network 1000. The accompanying information management unit 301C includes information attached to the content (bookmark information for designating a specific page in the book, sticky information pasted at a desired location in the book, marker information for marking a predetermined location in the book) , Tag information such as comments attached to the book, etc.), and the like. In response to a request from the terminal 100, the content distribution unit 301X distributes the content main body data. When there is a distribution request for content not stored in the book DB 310, the content distribution unit 301X instructs the server storing the requested content to transmit the content to the terminal 100.

3, the book DB 310 is configured to be included in the content server 300, but the book DB 310 may be configured by a device different from the content server 300. In addition, the user purchase history DB, the bibliographic information DB, and the content storage unit included in the book DB 310 may be included in the same device or may be included in different devices.

<Content DB in terminal>
The content DB 104C of the terminal 100 includes a content DB that stores information on content stored in the content storage unit 104A. Here, the contents stored in the content DB will be described. Table 1 schematically shows the stored contents.

In the content DB, a content ID, a content file name, a content storage destination, a cover image file name, and a cover image storage destination are stored in association with each other.

The content ID is information for specifying each content.
The content file name is the file name of the main file of each content.

The content storage destination is information for specifying the storage location in the content storage unit 104A of the main file of each content.

The cover image file name is a file name of a file displayed as an image showing an outline of each content when content information is displayed in a list (on a bookshelf screen or the like described later) on the terminal 100. For example, when the content is an electronic book, an example of a cover image file name is a file name of a thumbnail image of a cover of an actual book corresponding to the electronic book. When the content is music content, an example of a cover image file name is a thumbnail image of a jacket image of an album in which the content is recorded.

The cover image storage destination is information for specifying the storage location of the cover image in the content storage unit 104A.

The content list distributed from the content server 300 is associated with at least a content ID, a content file name, and a cover image file name. When the content and its cover image are downloaded and stored in the content storage unit 104A, the content storage destination and the cover image storage destination are added to the information such as the content ID and stored in the content DB. .

<User purchase history DB>
Next, the contents stored in the user purchase history DB in the content server 300 will be described. Table 2 schematically shows the stored contents.

In the user purchase history DB, a user ID and a purchased content ID are stored in association with each other.

The user ID is information for identifying each user who uses the system of FIG.
The purchased content ID is a content ID of content purchased by each user on a content purchase site or the like. Note that the content ID of the content for which the user has usage rights may be stored as the purchased content ID.

According to Table 2, it is recorded that the user with the user ID “SC0001” has purchased at least two contents with the content ID “ABCD1234” and the content ID “ABCD1235”.

<Bibliographic information DB>
Next, the contents stored in the bibliographic information DB in the content server 300 will be described. Table 3 schematically shows the stored contents.

The bibliographic information DB includes a content ID, a title, an author, a publisher name, a release date, a price, a product summary, a file name, a download URL (1), a cover image file name, and a download URL. (2) are stored in association with each other.

The content ID is information for specifying each content.
The title and author are the title and author of each content.

The publisher name is information that identifies the company that published the electronic book when the target content is an electronic book, and is a label or the like when the target content is music content.

The release date and price are the release date and price of the target content.
The product overview is information representing an overview of the content of the target content.

The file name is the file name of the main body of the target content.
The download URL (1) is a URL (Uniform Resource Locator) that is accessed to download the main content file of the target content.

The cover image file name is the file name of the cover image described above.
The download URL (2) is a URL that is accessed to download a cover image file of the target content.

<Content list>
As described above, in the system according to the present embodiment, the content server 300 transmits a content list for the user of the terminal 100 to the terminal 100.

The list generation unit 301A acquires a user ID that is a target of the content list from the terminal 100. In response to this, the list generation unit 301A extracts the purchased content ID associated with the acquired user ID in the user purchase history DB of the book DB 310. Then, the list generation unit 301 A extracts information associated with the content ID extracted as the purchased content ID in the bibliographic information DB of the book DB 310 to generate a content list.

For example, when the user ID “SC0001” is acquired as the target of the content list, the list generation unit 301A, in the user purchase history DB of the book DB 310, the content ID “ABCD1234” and the content ID “ABCD1235” associated with the user ID. To get. Then, information corresponding to these content IDs (information associated with these content IDs shown in Table 3) is extracted from the bibliographic information DB of the book DB 310, and the extracted information is used as a content list.

The content list includes data of each item in the bibliographic information DB of Table 3 regarding the content associated with the user ID of the target user in the user purchase history DB of Table 2.

<Meta information file>
The list generation unit 301A generates a meta information file of the content list together with the generation of the content list. An example of the contents of the meta information file is shown in FIG.

Referring to FIG. 4, the meta information file is constituted by a manifest file compliant with, for example, HTML (HyperText Markup Language) 5.

The meta information file shown in FIG. 4 includes information indicating the version of the content list shown below “# Version cid =” and information showing the expiration date of the content list shown below “# Valid until on”. .

The list generation unit 301A can generate information as shown in FIG. 4 as a separate file from the content list, and can also include such information in the content list.

<Reproduction of contents>
Next, content reproduction on the terminal 100 will be described. The terminal 100 according to the present embodiment reproduces an electronic book (content) so that the user can browse the electronic book.

Suppose that terminal 100 according to the present embodiment can operate in two modes, “local mode” and “online mode”, for browsing electronic books. The terminal 100 may be configured such that the operation mode is switched between them based on an operation on the input device 15 or a change in the attitude of the terminal 100 main body, or the terminal 100 may be operable in any mode. There is also.

“Local mode” is a mode for browsing content stored in the content DB of the terminal 100. The “online mode” is a mode for browsing content that the user of the terminal 100 has usage rights and is not stored in the content DB of the terminal 100.

Note that the content that is not stored in the content DB of the terminal 100 for the “online mode” is the content of the terminal 100 that is actually operated by the user even if it is stored in the content DB of another terminal 100 owned by the user. It includes content that is not stored in the DB. More specifically, when the terminal 100A is being operated, even if the content is stored in the content DB of the terminal 100B but is not stored in the content DB of the terminal 100A, the terminal 100A In the online mode operation, the content is not stored in the content DB 140.

The terminal 100 can operate online in either the local mode or the online mode. On the other hand, in offline mode, operation is possible only in the local mode. In this specification, online means a state connected to the network, and offline means a state not connected to the network.

<Bookcase screen (screen for displaying content saved on the terminal)>
FIG. 5 is a diagram illustrating an example of a bookshelf screen displayed on the display unit 102 when the terminal 100 is operating in the local mode.

The bookshelf screen 500 is a screen that displays a list of contents that can be browsed.
The bookshelf screen 500 includes a display field 501 for designating a display format, a display field 502 for designating a mode, and display fields 511 to 517 for displaying a list of information such as titles of electronic books. . Each content whose information is displayed in the display columns 511 to 517 is content in which data of the main body is stored in the content storage unit 104A. In the display column 501, “Title” is selected. As a result, the contents stored in the main body of the content storage unit 104A are displayed and displayed in the display columns 511 to 517 in the order of the titles in the order of 50 sounds.

In addition, software buttons 521 to 525 are displayed on the bookshelf screen 500. The software button 521 is a button for displaying detailed information of each book. The software button 522 is a button that is operated to search for content constituting a series of each content. The software button 523 is a button for registering each content as a favorite. The software button 524 is a button for performing registration (secret registration) for displaying only when a user who designates each content operates. The software button 525 is a button operated for posting shared information such as impressions on a specific site on the network for each content.

In the display field 502 of the bookshelf screen 500, “store in terminal” indicating the local mode is displayed. By visually recognizing the display contents of the display field 502, the user can recognize that the bookshelf screen 500 is a bookshelf screen in the local mode.

<Bookcase screen (screen for displaying server storage contents)>
FIG. 6 is a diagram illustrating an example of a bookshelf screen displayed on the display unit 102 when the terminal 100 is operating in the online mode.

Referring to FIG. 6, the bookshelf screen 600 includes display fields 601 and 602 corresponding to the display fields 501 and 502 in FIG. The bookshelf screen 600 includes software buttons 621 to 625 having the same functions as the software buttons 521 to 525 of FIG.

The bookshelf screen 600 includes display fields 611 to 617. Display columns 611 to 617 indicate contents that are included in the content list received from the content server 300 and are not stored in the content storage unit 104A of the terminal 100.

In the display field 602 of the bookshelf screen 600, “Save to server” indicating the online mode is shown. By visually recognizing the display contents of the display field 602, the user can recognize that the bookshelf screen 600 is a bookshelf screen in the online mode.

Note that an update button 650 is displayed on the bookshelf screen 600. The update button 650 is a button operated to transmit accompanying information in the terminal 100 to the content server 300 as will be described later.

<Bookcase screen display processing>
FIG. 7 is a flowchart of processing executed by the processing unit 101 to display a bookshelf screen as described with reference to FIG. 5 or 6 on the terminal 100.

Referring to FIG. 7, when the electronic book application is activated in terminal 100, processing unit 101 displays the home screen of the electronic book application on display unit 102 in step S 10 and advances the process to step S 20. .

In step S20, the processing unit 101 determines whether or not an operation for requesting the display of the bookshelf screen to the input device 15 has been performed. If it is determined that such an operation has been performed, the processing proceeds to step S30.

In step S30, the processing unit 101 accepts selection of an operation mode in the electronic book application. Then, the processing unit 101 proceeds to step S60 when the online mode is selected, and proceeds to step S40 when the local mode is selected.

In step S40, the processing unit 101 reads content data (in-terminal content DB shown in Table 1) stored in the content DB 104B from the content DB in the terminal 100, and proceeds to step S50. .

In step S50, the processing unit 101 generates data for displaying a bookshelf screen as described with reference to FIG. 5, and advances the process to step S90.

Note that the information in the display column 501 of the bookshelf screen 500 in FIG. 5 is information set by default. The information can be changed by a user operation or the like while the electronic book application is activated.

As information displayed in the display columns 511 to 517, information stored in the terminal content DB as shown in Table 1 is used. Specifically, information (title, author, publisher, etc.) registered for each content in the in-terminal content DB is extracted and displayed in each of the display columns 511 to 517.

Referring back to FIG. 7, in step S60, the processing unit 101 reads the content list distributed from the content server 300, and advances the process to step S70. The reading of the content list in step S60 will be described later with reference to FIG.

In step S70, the processing unit 101 calculates the difference between the content list received from the content server 300 and the content DB data stored in the content DB in the terminal 100, and advances the process to step S80. Through the processing in step S70, the content registered in the content list transmitted from the content server 300 and not stored in the content storage unit 104A of the terminal 100 is extracted.

In step S80, the processing unit 101 generates data for displaying a bookshelf screen as described with reference to FIG. 6 for the content extracted in step S70, and advances the process to step S90.

In step S90, the processing unit 101 causes the display unit 102 to display the bookshelf screen on which the display data is generated in step S50 or step S80, and ends the process.

As described above, according to the processing described with reference to FIG. 7, the bookshelf screen corresponding to the selected operation mode (local mode or online mode) is displayed on the display unit 102.

<Reading content list transmitted from content server>
FIG. 8 is a flowchart of the processing subroutine in step S60 of FIG.

Note that this processing is realized in cooperation with the processing in the content server 300. Therefore, in FIG. 8, in addition to the flowchart of the process on the terminal 100 side, the flowchart of the process in the content server 300 is also shown.

Referring to FIG. 8, in step SA10, processing unit 101 determines whether or not terminal 100 can be connected to content server 300 at that time, and if it determines that connection is possible, processing proceeds to step SA20. If it is determined that the server cannot be connected, the processing unit 101 returns the process to step S40 (see FIG. 7). Thereby, the operation mode of the terminal 100 is switched to the local mode.

In step SA20, the processing unit 101 requests the content server 300 to acquire and transmit the meta information file of the content list. At this time, the processing unit 101 transmits information (for example, a user ID) that identifies the user to the content server 300. The user ID is stored in the storage device 16, for example. The processing unit 101 may request the user to input login information when using the terminal 100. In such a case, in step SA20, the processing unit 101 transmits the user ID input as the login information to the content server 300.

When receiving the request for acquiring the meta information file from the terminal 100, the processing unit 301 of the content server 300 in step SB10, in the user purchase history DB of the book DB 310, the content ID associated with the user ID transmitted from the terminal 100. (Purchase history inquiry).

When the user purchase history DB of the book DB 310 is configured by an apparatus different from the content server 300, the processing unit 301 transmits an inquiry to the apparatus from the user ID received from the terminal 100. With. In response, in step SC10, the device transmits a content ID associated with the received user ID (purchase history transmission).

Further, the processing unit 301 acquires bibliographic information corresponding to the content ID acquired in step SB10 from the bibliographic information DB of the book DB 310. When the bibliographic information DB of the book DB 310 is configured by a device different from the content server 300, the processing unit 301 transmits the content ID acquired in step SB10 to the device, and also includes the bibliographic information. Make an inquiry. In response to this, the apparatus transmits bibliographic information corresponding to the content ID received from the content server 300.

The processing unit 101 generates a content list corresponding to the user ID acquired in step SB10 based on the bibliographic information acquired in step SB20, and generates a meta information file for the generated content list. Then, the process proceeds to step SB40.

In step SB40, the processing unit 301 transmits the meta information file generated in step SB30 to the terminal 100.

In response to this, in step SA30, the processing unit 101 of the terminal 10 determines whether or not the meta information file received from the content server 300 matches the meta information file of the content list already stored in the cache memory. If it matches, the process proceeds to step SA60, and if it does not match, the process proceeds to step SA40.

In step SA40, the processing unit 101 requests the content server 300 to acquire a content list.

In response to the content list acquisition request in step SA40, the processing unit 301 of the content server 300 transmits the content list generated in step SB30 to the terminal 100.

In response to the transmission of the content list from the content server 300, the processing unit 101 of the terminal 100 reads the received content list in step SA50 and returns the process to FIG.

As described above, according to the processing described with reference to FIG. 8, when the bookshelf screen is displayed in the online mode, it is first determined whether or not the terminal 100 can be connected to the content server 300 (step SA10). If not, the operation mode is switched to the local mode.

On the other hand, if connection to the content server 300 is possible, the terminal 100 makes a request to acquire the meta information file of the content list to the content server 300 (step SA20).

In response to this, the content server 300 generates a content list again (step SB30), and a meta information file of the content list is transmitted to the terminal 100 (step SB40).

The terminal 100 that has received the meta information file determines whether or not the meta information file of the content list already stored in the cache memory matches the received meta information file (step SA30). If they match, the content list already stored in the cache memory is read without receiving the content list again from the content server 300 (step SA60). On the other hand, if the meta information files do not match, the terminal 100 requests the content server to acquire a content list (step SA40).

The terminal 100 reads the content list received from the content server 300 (step SA50).

In the content server 300, as shown in steps SB10 to SB30, the content list and the meta information file are generated every time a request for acquisition of the meta information file is made from the terminal 100. This timing is not limited to that described with reference to FIG. For example, it may be when the history information about the target user ID is updated in the user purchase history DB of the book DB 310, when a certain amount of time has elapsed since the last generation of the content list or the like. As described above, when the content list and the meta information file are generated at a timing different from the reception of the meta information file acquisition request from the terminal 100, the processing unit 301 of the content server 300 requests the request in step SA20. Upon reception, the meta information file corresponding to the target user ID already generated and stored in the storage unit 302 or the like is transmitted to the terminal 100 in step SB40. When receiving the content list acquisition request in step SA40, the processing unit 301 transmits the content list already stored in the storage unit 302 or the like to the terminal 100 as the processing in step SB50.

<Content display processing>
In the electronic book application of the terminal 100, as described with reference to FIG. 5 or FIG. 6, the bookshelf screen is displayed. Display columns 511 to 517 and 611 to 617 for selecting each content are displayed on the bookshelf screens 500 and 600, respectively.

When any of the display columns 511 to 517 and 611 to 617 is selected on each of the bookshelf screens 500 and 600, processing for displaying the content corresponding to the display column is executed.

FIG. 9 is a flowchart of the processing executed by the processing unit 101.
Referring to FIG. 9, when an operation for selecting any of display columns 511 to 517 and 611 to 617 is performed on one of

bookshelf screens

500 and 600, processing unit 101 selects the selected one in step SA110. It is determined whether or not the content is stored in the content storage unit 104A of the terminal 100. If the processing unit 101 determines that the selected content is stored in the content storage unit 104A, the processing unit 101 proceeds to step SA150 and determines that the selected content is not stored (the selected content is stored in the content server 300). If determined, the process proceeds to step SA120.

In step SA150, the processing unit 101 displays the selected content, which is the content stored in the content storage unit 104A, on the display unit 102 by the viewer, and ends the processing.

On the other hand, in step SA120, the processing unit 101 transmits a download request for a file of the main body of the selected content to the content server 300.

In response to this, the processing unit 201 of the content server 300 delivers the requested content to the terminal 100 (step SE110).

In response to this, the processing unit 101 of the terminal 100 receives the content in step SA130, stores the content in the content storage unit 104A, updates the information in the content DB according to the information after storage, and then proceeds to step SA140. Proceed with the process. As a result, content information newly stored in the content storage unit 104A is added to the in-terminal content DB (see Table 1).

In step SA140, the processing unit 101 causes the viewer to display the content received in step SA130 on the display unit 102, and ends the process.

FIG. 10 is a diagram illustrating an example of the appearance of the terminal 100. The terminal 100 in FIG. 10 includes operation buttons 103P to 103Q for performing operations such as termination of the electronic book application. The operation buttons 103P to 103Q are included in the operation unit 103. In the display unit 102 of the terminal 100 in FIG. 10, an example of a content display screen (screen 1100) is shown.

The screen 1100 is an electronic book display screen. On the screen 1100, a bookmark icon 701 indicating that bookmark information is associated with the displayed page is displayed. In addition, a marker 702 is attached to a part of the text displayed on the screen 1100. The accompanying information of the content being displayed includes at least bookmark information associated with the displayed page and marker information associated with the portion to which the marker 702 is attached.

<Accompanying information>
As described with reference to FIG. 10, the terminal 100 processes the accompanying information such as the bookmark and the marker together with the electronic book body, and displays the electronic book.

The accompanying information may be set in advance, or may be generated based on a user's operation while browsing the electronic book. An example of the accompanying information is shown in Table 4.

The accompanying information shown in Table 4 is associated with the information ID and the content ID. The information ID is an ID attached to each generated accompanying information. The content ID is information for specifying the content associated with the associated information.

In the accompanying information, the type, the first item, the second item, and the characteristics are associated with each other. The type indicates the type of accompanying information such as “bookmark”, “marker”, “sticky note”, and “tag”. The first item and the second item are information for specifying a value set for each type. A characteristic is information which specifies a characteristic for every said kind. Depending on the type of accompanying information, the second item and / or characteristic value may not be attached.

As for “bookmark”, the first item is information for specifying the page of the electronic book, and the second item and the characteristic are not associated with each other. As for “tag”, the first item is information for specifying the position of text such as a page in the electronic book, the second item is not associated, and the characteristic is information for specifying the color of the tag. Regarding the “marker”, the first item is information for specifying the start position of marking in the electronic book, the second item is information for specifying the end position of marking, and the characteristic is information for specifying the color of the marking. is there. As for “tag”, the first item is information for identifying a comment attached as a tag (for example, “you can read later” in Table 5 to be described later), the second item is not associated, and the characteristic is the tag The information for specifying the color when the information corresponding to is displayed.

When a specific operation (for example, an operation on the operation buttons 103P to 103Q) is performed in the electronic book application, a screen for generating accompanying information is displayed on the display unit 102. FIG. 11 is a diagram illustrating an example of a screen for displaying accompanying information.

In the screen 1101 of FIG. 11, software buttons (buttons 1031 to 1035) are displayed so as to overlap the browsing screen as shown in FIG.

The button 1031 is a button operated to generate marker information. A button 1032 is a button operated to search for a word in the electronic book being browsed in a dictionary installed in the terminal 100. The button 1033 is a button operated to generate bookmark information. A button 1034 is a button operated to generate sticky note information. The button 1035 is a button operated to generate tag information.

In the terminal 100, for example, the accompanying information generated in one browsing of a certain content (from the start of browsing of the electronic book to the end of the electronic book application in the electronic book application) as shown in Table 3 Is assigned one information ID. While the electronic book is being browsed, the accompanying information (“bookmark” and “marker” in Table 3) generated by operating the buttons 1031 to 1035 or the like is accumulated. Then, when browsing of the electronic book is completed, the accompanying information generated during browsing is registered in the accompanying information DB of the accompanying information storage unit 104D.

An example of the contents of the accompanying information DB is shown in Table 5.

In the incidental information DB of Table 5, the type, the information ID, the content ID, the first item, the second item, and the characteristics are associated with each other.

The accompanying information generated as shown in Table 4 is added to the accompanying information DB together with the information ID and content ID associated with the accompanying information. More specifically, every time browsing of the electronic book is completed, the accompanying information DB is updated so that accompanying information generated during the browsing is added.

The incidental information generation unit 101E performs generation of incidental information as shown in Table 4 and storage of the generated incidental information in the incidental information DB. The accompanying information generation unit 101E uniquely generates and associates an information ID with each accompanying information. If the information ID is unique for each accompanying information, a value that combines the date and time when browsing of the electronic book is started, a serial number of the accompanying information generated in the terminal 100, a serial character string, and the like Any form may be used. In the present embodiment, character strings such as “aaa”, “sss”, “ttt”, and “uuu” are exemplified as the information ID.

In the accompanying information DB of Table 5, information is shown for each type “bookmark”, “sticky note”, “marker”, and “tag”.

When registering the generated incidental information in the incidental information DB, the incidental information generation unit 101E determines whether the generated incidental information includes information that conflicts with the incidental information already registered in the incidental information DB. It is preferable to do. “Competing” means that, for example, when the generated accompanying information is directly registered in the accompanying information DB, a plurality of (or more than a predetermined number of) bookmark information is set for the same electronic book. In such a case, there are cases where markers of different colors (or more than a predetermined number) are attached to the same part.

If the accompanying information generation unit 101E determines that the competing information is included, for example, the accompanying information is overwritten with the accompanying information to be newly registered.

When it is determined that the competing information is included, the accompanying information generation unit 101E may perform overwriting while showing the already registered accompanying information and the competing portion in the accompanying information to be registered. You may display the screen which inquires of a user whether it is. Then, the accompanying information generation unit 101E updates the accompanying information DB according to information input by the user on the screen. More specifically, when information permitting overwriting is input, the accompanying information generation unit 101E overwrites the competing portion of the accompanying information DB with the newly generated accompanying information. On the other hand, if information prohibiting overwriting is input, the accompanying information generation unit 101E updates the accompanying information DB without overwriting the competing part. At this time, the accompanying information generation unit 101E deletes the competing part in the newly generated accompanying information and updates the accompanying information DB. In addition, when information for registering both is input, the accompanying information generation unit 101E allows both the already registered information and the conflicting part of the newly generated information to be distinguished from each other. Register in DB. Note that such a registration mode can be realized by applying a well-known technique, and therefore the description of the technique is not repeated in this specification.

<Management of accompanying information in content server>
In the system shown in FIG. 1, accompanying information generated in each terminal 100 (terminals 100A to 100C) is registered in the accompanying information storage unit 311 of the content server 300. Hereinafter, management of accompanying information generated at the terminal in the content server 300 will be described. For ease of explanation, in the following explanation, only the type “marker” of the accompanying information will be described, but in the system according to the present embodiment, other types of information are managed in the same manner. Is made.

Table 6 shows an example of the accompanying information DB registered in the terminal 100A. Table 7 shows an example of the accompanying information DB registered in the terminal 100B. Table 8 shows an example of the contents of the accompanying information DB registered in the content server 300.

Table 6 shows accompanying information DBs corresponding to four information IDs (“aaa”, “sss”, “ttt”, “uuu”). In Table 7, the accompanying information DB corresponding to one information ID (“bbb”) is shown.

When the information in the accompanying information DB as shown in Table 6 is transmitted from the terminal 100A, in the content server 300, the information is stored in the accompanying information storage unit 311 together with information for specifying the transmission source terminal. .

Further, when the information of the accompanying information DB as shown in Table 7 is transmitted from the terminal 100B, the content server 300 determines whether or not it conflicts with each accompanying information already stored in the accompanying information storage unit 311. The The contention determined in the content server 300 is a case where, in addition to the content of the contention in the terminal 100 as described above, there is a content information that has the same information ID in the side information DB transmitted from a different terminal 100. Including. If it is determined that there is no competition, each incidental information in the incidental information DB transmitted from the terminal 100B is stored in the incidental information storage unit 311 together with information specifying the transmission source terminal.

Table 8 shows a state in which the incidental information DB registered in the content server 300 includes the incidental information constituting the incidental information DB of Table 6 and the incidental information constituting the incidental information DB of Table 7. ing.

In addition, in the accompanying information DB of Table 8, in addition to the columns included in the accompanying information DBs of Tables 6 and 7, a “Registered terminal” column is provided. In this field, information for identifying the terminal 100 that is the transmission source of each accompanying information is registered. In Table 8, “A” indicates the terminal 100A, and “B” indicates the terminal 100B.

<Back up accompanying information>
A process (backup process) executed by the processing unit 101 when the accompanying information generated by the terminal 100 is transmitted to the content server 300 will be described. FIG. 12 is a flowchart of the backup process. The process of FIG. 12 is started on the condition that the update button 650 (see FIG. 6) is operated in the terminal 100, for example.

Referring to FIG. 12, processing unit 101 first collects accompanying information in terminal 100 in step SA510 and advances the process to step SA520. At this time, all the accompanying information stored in the accompanying information DB of the accompanying information storage unit 311 may be collected. Further, the processing unit 101 may attach a tag such as transmission completion to the incidental information that has been transmitted to the content server 300 for each backup process in the incidental information DB. In step SA510, the processing unit 101 may collect incidental information that is not attached with the tag from the incidental information stored in the incidental information DB. Further, the accompanying information of the electronic book being browsed as described with reference to Table 4 may be stored in the flash memory 106, for example. In such a case, in step SA510, the processing unit 101 collects accompanying information stored in the flash memory 106 in addition to the accompanying information already registered in the accompanying information DB of the accompanying information storage unit 311.

In step SA520, the processing unit 101 transmits information (command or the like) requesting storage of the accompanying information to the content server 300 together with the accompanying information collected in step SA510, and advances the process to step SA530.

FIG. 13 is a flowchart of processing executed in the content server 300 in response to a request from the terminal 100 in the processing of FIG.

Referring to FIG. 13, upon receiving the request at step SA520, processing unit 301 of content server 300 reads the first record of the accompanying information attached to the request at step SB510, and advances the process to step SB520. . Here, the record refers to a set of accompanying information for one line of information (“type”, “first item”, “second item”, “characteristic”) in the accompanying information in Table 4 and the like. According to this, the incidental information DB of Table 6 includes four records, and the incidental information DB of Table 7 includes one record.

In step SB520, the processing unit 301 reads information on a record to be processed, and advances the process to step SB530. Here, the record to be processed is the record read in step SB510 if it is the first step SB520, and the record designated as the process target in step SB560 if it is the second or subsequent step SB520.

In step SB530, the processing unit 301 determines whether or not the accompanying information read in step SB520 conflicts with the accompanying information constituting the accompanying information DB already registered in the accompanying information storage unit 311. The criteria for determining whether or not to compete are as described above. If it is determined that there is a conflict, the process proceeds to step SB540. If it is determined that there is no conflict, the process proceeds to step SB550.

In step SB540, the processing unit 301 deletes the accompanying information determined to be in conflict from the accompanying information DB in the accompanying information storage unit 311 registered in the content server 300, and advances the process to step SB550.

In step SB550, the processing unit 301 registers (adds) the accompanying information read in step SB520 in the accompanying information DB in the accompanying information storage unit 311 registered in the content server 300, and advances the process to step SB560.

In step SB560, the processing unit 301 changes the processing target to the next record in the accompanying information transmitted by the terminal 100 in step SA520, and advances the processing to step SB570.

In step SB570, the processing unit 301 determines whether or not the processing target in step SB560 could not be changed. More specifically, this determination corresponds to determining whether or not up to the last record has already been processed in the accompanying information already received. If the processing unit 301 determines that all records have already been processed, the processing unit 301 proceeds to step SB580. If the processing unit 301 determines that there is a record that has not yet been processed, the processing unit 301 returns the process to step SB520.

In step SB580, processing unit 301 transmits information (save response) indicating that registration of the transmitted accompanying information has been completed to terminal 100 that has transmitted the request in step SA520, and ends the process. .

Returning to FIG. 12, when the storage response transmitted in step SB580 is received, the processing unit 101 of the terminal 100 receives the storage response in step SA530 and ends the processing.

As described above, according to the processing described with reference to FIG. 12 and FIG. 13, the accompanying information generated in the terminal 100 is transmitted to the content server 300 by the operation on the terminal 100 (operation on the update button 650). In the content server 300, the received accompanying information is registered in the accompanying information DB stored in the content server 300.

For example, when the accompanying information DB as shown in Table 8 is registered in the accompanying information storage unit 311 of the content server 300, the accompanying information as shown in Table 9 is transmitted from the terminal 100 to the content server 300. Consider the case.

In such a case, the incidental information DB of the incidental information storage unit 311 of the content server 300 is updated as shown in Table 10.

The accompanying information DB in Table 10 corresponds to the content shown in Table 8 with the content added as shown in Table 9. The accompanying information in Table 9 is transmitted from the terminal 100B. Therefore, in Table 10, “B” representing the terminal 100B is registered in the “Registered terminal” column of the record corresponding to the accompanying information in Table 9 (record with the information ID “rrr”).

In the process described with reference to FIG. 13, when the accompanying information transmitted from the terminal 100 conflicts with the accompanying information already registered in the accompanying information DB of the content server 300, a new message is sent from the terminal 100. The accompanying information sent is overwritten and updated.

In step SA510 (see FIG. 12), only the information selected by the user among the accompanying information stored (saved) in the terminal 100 may be transmitted to the content server 300.

In this case, when the update button 650 is operated in the terminal 100, among the accompanying information that is registered in the terminal 100 for the user but has not yet been transmitted to the content server 300, the content server 300 receives the information. An inquiry is made to select what to send. FIG. 14 is a diagram showing an example of a screen for such an inquiry.

Referring to FIG. 14, screen 700 includes a message display field 700 A, an OK button 721, a cancel button 722, and buttons corresponding to the contents that are candidates for transmitting accompanying information to content server 300. 711-716.

The processing unit 101 collects incidental information that has been registered in the terminal 100 and has not yet been transmitted to the content server 300, and acquires the content ID of the incidental information, thereby displaying the contents displayed on each of the buttons 711 to 716. (Content title etc.) is determined. The number of buttons displayed here is not limited to “6”. The number of displayed buttons is the number of acquired content IDs. These buttons are arranged so as to be lined up and down. The screen 700 can be associated with more buttons by performing scroll display in the direction in which these buttons are arranged. Because it is possible to associate one screen with a larger number of buttons than the number of buttons displayed on the screen at the same time, and to replace the buttons displayed on the screen by scroll display, by a well-known technique. Here, the description of the technology is not repeated.

The user selects content for transmitting accompanying information to the content server 300 from buttons 711 to 716 on the screen 700 and operates an OK button 721. Accordingly, in step SA510, the processing unit 101 collects accompanying information of the selected content. On the other hand, when the cancel button 722 is operated, the display on the display unit 102 is returned to the screen for browsing the electronic book without performing the backup process. Information for explaining such processing contents is displayed in the column 700A.

When the storage response is received in step SA530, the processing unit 101 may display a screen on the display unit 102 informing that the backup of the accompanying information has been completed. FIG. 15 is a diagram illustrating an example of a screen for informing that backup of accompanying information has been completed.

Referring to FIG. 15, a message indicating that the backup is completed is displayed on screen 750. If there is content for which the accompanying information could not be backed up, this is displayed below the screen 750. When the OK button 751 is operated on the screen 750, the backup process ends.

In step SB540, when there is competing accompanying information, the already registered accompanying information is deleted from the accompanying information DB of the content server 300. Such deletion is applied only between the accompanying information transmitted from the same terminal 100 (for example, when the sources of competing accompanying information are both terminals 100A), and the accompanying information transmitted from different terminals is used. It may not be applied between. Alternatively, it may be applied only between accompanying information transmitted from different terminals, and may not be applied between accompanying information transmitted from the same accompanying information. In this case, the accompanying information transmitted later to the content server 300 is not registered in the accompanying information DB of the content server 300. In this case, the processing unit 301 may return accompanying information that could not be registered in the content server 300 due to contention to the terminal 100 that is the transmission source. In the terminal 100 that has received such a reply, a message to that effect is displayed on the display unit 102. FIG. 16 is a diagram illustrating an example of a screen displayed on the terminal 100 that has received the accompanying information that has not been registered.

Referring to FIG. 16, screen 760 displays a display field 760 A that displays a message indicating that backup could not be performed by content server 300, an OK button 751, and content corresponding to the returned accompanying information.

Buttons

761 and 762. In this case, when the user who has viewed the screen 760 operates the OK button 751, the backup process ends.

<Variation of backup process (1)>
In the system according to the present embodiment, when contention information conflict occurs in the content server 300, the processing unit 301 modifies the additional information newly transmitted to the content server 300 so that the conflict is resolved. You may register into accompanying information DB. In the following description, a case where a conflict occurs due to the same information ID will be described as an example of a conflict of accompanying information.

FIG. 17 is a flowchart of a modification of the backup process of FIG.
Referring to FIG. 17, when processing unit 101 receives a storage response from content server 300 in step SA530, in step SA540, in accordance with the information included in the storage response, processing unit 101 in the accompanying information DB of its own device as necessary. Rewrite information.

FIG. 18 is a flowchart of a modification of the processing of the processing unit 301 in FIG.
Referring to FIG. 18, when it is determined in step SB530 that the accompanying information to be processed conflicts with the accompanying information already registered in the accompanying information DB of content server 300, the process proceeds to step SB541.

In step SB541, the processing unit 301 rewrites the information ID of the incidental information to be processed so as to be different from all the incidental information already registered in the incidental information DB, and advances the process to step SB550.

In step SB550, the processing unit 301 registers the accompanying information to be processed in the accompanying information DB. In this case, when the information ID is rewritten in step SB541, the accompanying information after the information ID is rewritten is registered in the accompanying information DB.

Thereafter, the processing unit 301 executes the processing of step SB560 to step SB570, and if it is determined that there are no unprocessed records in step SB570, the processing proceeds to step SB581.

In step SB581, when the information ID is rewritten in step SB541, the processing unit 301 transmits the accompanying information before and after the rewriting to the transmission source terminal 100 together with the storage response for the accompanying information that is the target of rewriting, The process ends.

Referring back to FIG. 17, the processing unit 101 of the terminal 100 receives the accompanying information before and after the rewriting and the storage response in step SA530, and advances the processing to step SA540.

In step SA540, when the processing unit 101 receives the accompanying information before and after rewriting in step SA530, the processing unit 101 rewrites the information ID of the target accompanying information in the accompanying information DB of its own device to the one after rewriting by the processing unit 301. End the backup process.

Specific examples will be described below.
It is assumed that the accompanying information as shown in Table 11 is transmitted from the terminal 100B when the accompanying information DB shown in Table 10 is registered in the content server 300.

The accompanying information in Table 11 includes information with the information ID “sss”. As shown in Table 10, the accompanying information already registered in the content server 300 also has information ID “sss” (record on the third line from the top of Table 10). Therefore, when the accompanying information as shown in Table 11 is received and the record with the information ID “sss” is a processing target, the processing unit 301 determines that a conflict has occurred (YES in step SB530).

Then, in step SB541, the processing unit 301 rewrites the information ID of the accompanying information so that it does not overlap with any record shown in Table 10. An example of the accompanying information after rewriting is shown in Table 12.

In Table 12, the information ID is rewritten to “vvv”. As understood from Table 10, there is no record having the information ID “vvv” in the incidental information DB already registered in the content server 300.

In step SB550, the processing unit 301 registers the accompanying information after rewriting (the accompanying information shown in Table 12) in the accompanying information DB. Table 13 shows the accompanying information DB after registration.

In Table 13, as compared with Table 10, a record having an information ID “vvv” is added.
Furthermore, the processing unit 301 transmits accompanying information before and after rewriting to the terminal 100B that is the transmission source (step SB581). Thereby, the processing unit 101 of the terminal 100B receives the accompanying information (before rewriting) in Table 11 and the accompanying information (after rewriting) in Table 12 together with the storage response in Step SA530.

Then, in step SA540, the processing unit 101 of the terminal 100B rewrites the accompanying information DB of the own device according to the information after rewriting. An example of the accompanying information DB of the terminal 100B before rewriting is shown in Table 14.

The accompanying information DB in Table 14 includes a record before rewriting (a record with information ID “sss”).
Table 15 shows an example of the accompanying information DB after the information is rewritten by the process of step SA540.

In Table 15, only the information ID of the record with the information ID “sss” in Table 14 is rewritten to “vvv”.

<Variation of backup process (2)>
In this modification, when it is determined that contention information conflict has occurred in the content server 300, the user is inquired about handling of the accompanying information that is the target of the contention.

FIG. 20 shows a flowchart of processing executed by the processing unit 301 of the content server 300 of this modification. FIG. 20 corresponds to a modification of the process of FIG. 18 of the modification (1).

FIG. 21 shows a flowchart of a subroutine of step SA540 (see FIG. 17) executed by the processing unit 101 of the terminal 100 of the present modification. FIG. 21 corresponds to a modification of the process of FIG. 19 in the modification (1).

Referring to FIG. 20, if it is determined in step SB530 that there is a conflict, processing unit 301 advances the process to step SB551. In step SB551, the processing unit 301 registers the record to be processed in step SB520 in the conflict DB together with the accompanying information that is the competing partner in the accompanying information DB of the content server 300, and advances the process to step SB560. . The contention DB is set in a specific storage area in the storage unit 302, for example.

On the other hand, when determining that there is no conflict in step SB530, the processing unit 301 registers the record to be processed in the accompanying information DB in step SB550, and advances the process to step SB560.

In step SB560, the processing target is changed to the next record of the accompanying information received from the terminal 100.

In this modification, when it is determined that the accompanying information received from the terminal conflicts with the accompanying information in the accompanying information DB of the content server 300, the accompanying information is temporarily stored in the conflicting DB.

Then, after processing all the records of the received accompanying information (YES in step SB570), the processing unit 301 sends the accompanying information registered in the contention DB together with the storage response to the terminal 100 that sent the accompanying information in step SB582. List (competitive record list).

Accordingly, in the terminal 100 that is the source of the accompanying information, the processing unit 101 receives the competing record list in step SA530, and advances the process to step SA540. The following processing will be described with reference to the flowchart of the subroutine of step S540. FIG. 21 is a flowchart of the subroutine of step S540.

In step SA541, the processing unit 101 displays a dialog for inquiring about handling of each accompanying information included in the conflicting record list on the display unit 102. FIG. 22 is a diagram illustrating an example of the display screen of the dialog.

Referring to FIG. 22, screen 800 includes a table 810 showing all accompanying information included in the conflict record list. Table 810 shows accompanying information on the terminal 100 side and accompanying information on the content server 300 side competing with the accompanying information for the three records.

Further, the screen 800 includes columns 821 to 823 for designating the respective measures for each record.

The following three types of measures can be specified in this modification.
1. Force backup. 2. Import server information Do nothing. “1. Force backup” is a measure for instructing to replace the accompanying information registered in the accompanying information DB of the content server 300 with the information transmitted from the terminal 100.

“2. Capture server information” is a countermeasure for instructing to replace the accompanying information registered in the terminal 100 with the competing accompanying information registered in the accompanying information DB of the content server 300.

“3. Do nothing” means that the accompanying information in which the conflict has occurred is not changed as it is registered in the content server 300, but is also left as it is registered in the accompanying information DB of the terminal 100. This is the action to be directed. In this case, in the incidental information DB of the content server 300 and the incidental information DB of the terminal 100, different parts are registered with different information.

The screen 800 further includes an execution button 831 and a cancel button 832. When the cancel button 832 is operated, the backup process ends there. Therefore, all the records determined to be in conflict continue to be registered as they are in the terminal 100, and are registered in the conflict DB instead of being registered in the accompanying information DB in the content server 300. If execute button 831 is operated (YES in step SA542), the process proceeds to step SA543.

In step S543, the processing unit 101, as a result of the inquiry as described with reference to FIG. 22, the accompanying information instructed to rewrite the information in the accompanying information DB on the terminal 100 side (accompanying information specified in 2 above). ) Is determined. If it is determined that there is such accompanying information, the process proceeds to step SA544. If it is determined that there is no accompanying information, the process proceeds to step SA545.

In step SA544, the processing unit 101 performs the process described in 2. In the accompanying information DB of the own device, the competing accompanying information is rewritten with the competing information already registered in the content server 300, and the process proceeds to step SA545.

In step SA545, the processing unit 101 is instructed to forcibly rewrite the information registered in the content server 300 with the information on the terminal 100 as a result of the inquiry as described with reference to FIG. It is determined whether there is (accompanying information designated 1 above). If it is determined that there is such accompanying information, the process proceeds to step SA546. If it is determined that there is no accompanying information, the process returns to FIG. Thereby, the processing on the terminal 100 side ends.

In step S546, the above 1. Is transmitted to the content server 300, and the process returns to FIG. Thereby, the processing on the terminal 100 side ends.

Referring back to FIG. 20, after transmitting the save response in step SB582, the processing unit 301 determines whether a forced backup request is received from the terminal 100 in step SB583. If it is determined that it has been received, the process proceeds to step SB584.

In step SB584, the processing unit 301 performs forced backup and ends the process. Forcible backup refers to updating the incidental information DB of the content server 300 by overwriting the incidental information determined to compete in step SB530 with that transmitted from the terminal 100. More specifically, when the accompanying information transmitted from the terminal 100 conflicts with the accompanying information registered in the content server 300, the content server is forced to leave only the accompanying information transmitted from the terminal 100. It means updating 300 accompanying information DB.

Note that, in step SB583, the processing unit 301 may be configured to advance the processing to FIG. 20 if a forced backup request is not received from the terminal 100 for a specific time or longer, for example.

<Retrieving accompanying information>
In the system of FIG. 1, the terminal 100 may request the content server 300 to extract the accompanying information registered in the accompanying information DB of the content server 300.

FIG. 23 is a flowchart of processing executed for extracting accompanying information in the terminal 100. FIG. 24 is a flowchart of processing executed in the content server 300 that has received a retrieval request from the terminal 100.

Referring to FIG. 24, when an operation for requesting extraction of accompanying information is performed during execution of the electronic book application, processing unit 101 causes display unit 102 to indicate that the accompanying information is to be extracted in step SA710. A list of contents to be displayed is displayed, and the process proceeds to step SA720. FIG. 25 is a diagram illustrating an example of a screen that displays a list of contents from which incidental information is to be extracted.

Referring to FIG. 25, screen 900 includes a field 900A for displaying a message, an OK button 921, a cancel button 922, and buttons 911 to 916 corresponding to the contents from which the accompanying information is to be extracted. . The content from which the accompanying information is extracted is the content registered in the content storage unit 104A. The user operates the button corresponding to the content for which the associated information is desired to be extracted from among the buttons 911 to 916, thereby specifying the content for which the associated information is desired to be extracted.

In step SA720, the processing unit 101 transmits a request to retrieve the accompanying information of the designated content to the content server 300.

Referring to FIG. 24, in response to this, in step SB710, processing unit 301 receives a request for extraction of accompanying information from terminal 100, and proceeds to step SB720.

In step SB720, the processing unit 301 collects accompanying information from the accompanying information DB in the content server 300 based on the received information, and advances the process to step SB730. Specifically, in step SB720, processing unit 301 collects accompanying information registered in association with the content ID that has received the retrieval request from terminal 100 in the accompanying information DB in content server 300.

Then, in step SB730, the processing unit 301 transmits the accompanying information collected in step SB720 to the terminal 100 as an extraction response.

Referring back to FIG. 23, in step SA730, the processing unit 101 receives the extraction response and proceeds to step SA740.

In step SA740, the processing unit 101 overwrites and updates the accompanying information DB of the own device with the received accompanying information, and ends the process. FIG. 26 is a diagram illustrating an example of a screen displayed on the display unit 102 by the processing unit 101 in order to notify the fact when the accompanying information extraction processing is completed.

In step SA740, when a conflict occurs between the information registered in the accompanying information DB of the own device and the “accompanying received information”, the processing unit 101 prioritizes the information registered in the own device. Then, information that has a conflict among the “received information” may be discarded. Alternatively, the processing unit 101 gives priority to the information registered in the content server 300 and replaces the information registered in the own device with the “received information” that is the competing partner, so The information DB may be updated.

<Specific examples of terminals>
In the present embodiment described above, the terminal 100 can be realized by various devices as long as it is an information processing apparatus having a content reproduction function.

For example, the terminal 100 may be realized by a tablet terminal as shown in FIG.

27, the tablet terminal (terminal 100) shown in FIG. 27 is provided with an operation button 15A in the casing together with the display device 14. In the terminal 100 shown in FIG. 27, a touch sensor is provided so as to overlap with the display device 14, and the input device 15 is configured by the touch sensor and / or the operation button 15A.

In addition, as shown in FIG. 28, the terminal 100 may be realized by a smartphone terminal (terminal having a call function).

28, the smart phone terminal (terminal 100) shown in FIG. 28 is provided with operation buttons 15B to 15D along with the display device 14 in its casing. In the terminal 100 shown in FIG. 28, a touch sensor is provided so as to overlap the display device 14, and the input device 15 includes the touch sensor and / or operation buttons 15B to 15D.

Further, as shown in FIG. 29, the terminal 100 may be realized by a personal computer installed in an office or the like instead of a terminal having portability.

A monitor 14A, a keyboard 15E, and a mouse 15F are connected to a terminal 100 realized by a personal computer. In this case, the display device 14 controls display on the monitor 14A. More specifically, the display device 14 is realized by driver software or a driver circuit board of the monitor 14A. In this example, the input device 15 is configured by the keyboard 15E and / or the mouse 15F.

As shown in FIG. 30, a terminal 100 realized by a television receiver includes a monitor and a remote controller (hereinafter referred to as “remote controller”). In such an example, the input device 15 is configured by a remote controller, and the display device 14 is configured by a monitor.

<Other variations, etc.>
In the system of FIG. 1, the process for updating the accompanying information DB is executed independently of the process for reproducing (browsing) the electronic book (content). Specifically, for example, even when an electronic book is browsed offline, the processing unit 101 generates accompanying information described with reference to Table 4 and the like, and refers to the accompanying information with reference to Table 5 and the like. Register in the accompanying information DB. Then, the processing unit 101 can perform backup of accompanying information for a plurality of contents in the content server 300 regardless of whether the electronic book is being browsed online. In addition, the processing unit 101 can request the content server 300 to retrieve accompanying information of one or more electronic books (contents) regardless of whether or not the electronic book is being browsed.

Thereby, the processing unit 101 can register the accompanying information generated for the content played off-line in the content server 300 independently of the browsing operation of the content. Further, the processing unit 101 can receive and register accompanying information generated by another terminal 100 owned by the user at the terminal 100.

Note that the accompanying information to be received is not limited to that of the same user as the already registered accompanying information. The system may be configured such that it can be received by the terminal 100 even if the accompanying information is registered in the content server 300 by another user. In this case, in the content server 300, the incidental information may be registered by specifying what is permitted to be received by other users. In this case, when the user who has requested extraction of the accompanying information is different from the user who has registered the accompanying information, the content server 300 has requested only the registered accompanying information with the above designation. It transmits to the terminal 100 of the user.

In the system of FIG. 1, the accompanying information DB may be updated by a backup process in which accompanying information is transmitted from the terminal 100 to the content server 300 by operating the update button 650 (see FIG. 6). For example, as described with reference to FIGS. 23 to 26, the terminal 100 may extract the accompanying information registered in the content server 300. The system shown in FIG. 1 may be configured such that the accompanying information is updated in both of these modes.

Each embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

100, 100A to 100C terminal, 101, 201, 301 processing unit, 101A content playback unit, 101B list display unit, 101C content acquisition unit, 101D content list acquisition unit, 101E associated information generation unit, 101F associated information acquisition unit, 101G associated Information transmission unit, 102 display unit, 103 operation unit, 104, 302 storage unit, 104A content storage unit, 104C user information storage unit, 104D, 311 accompanying information storage unit, 105, 303 communication unit, 106 flash memory, 200 content distribution Server, 300 content server, 301A list generation unit, 301B list distribution unit, 301C accompanying information management unit, 301X content distribution unit.

Claims

A playback unit for playing back content,
A generating unit for generating accompanying information that is information accompanying content that can be played by the playing unit;
A storage unit for storing the accompanying information;
A transmission unit for transmitting accompanying information generated by the generation unit to a server device;
The reproduction unit reproduces content based on the accompanying information stored in the storage unit,
The transmission unit transmits the accompanying information generated by the generating unit to the server device independently of the start or end of browsing of the content corresponding to the accompanying information.
A receiving unit for receiving notification from the server device that the accompanying information transmitted by the transmitting unit conflicts with other accompanying information already stored in the server device;
An input unit for inputting information as to whether or not to permit change of the accompanying information transmitted by the transmission unit based on the notification received by the reception unit;
The receiving unit stores the corrected accompanying information in the storage unit when information permitting the change of the accompanying information transmitted by the transmitting unit is input to the input unit. The terminal device described.
A receiving unit for receiving notification from the server device that the accompanying information transmitted by the transmitting unit conflicts with other accompanying information already stored in the server device;
An input unit for inputting an instruction to register the accompanying information transmitted by the transmission unit in the server device based on the notification received by the reception unit;
When the instruction to register the accompanying information in the server device is input to the input unit, the transmitting unit sends information that instructs the server device to register the accompanying information transmitted by the transmitting unit. The terminal device according to claim 1 which transmits.
A storage medium that non-temporarily records a control program for the terminal device that can be executed by a computer of the terminal device including a storage unit and a playback unit that plays back content.
The control program is stored in the computer.
Generating accompanying information that is information accompanying content that can be played by the playback unit;
Storing the accompanying information in the storage unit;
Transmitting the generated accompanying information to the server device,
The reproduction unit reproduces content based on the accompanying information stored in the storage unit,
The step of transmitting the accompanying information to the server device includes transmitting the generated accompanying information to the server device independently of the start or end of browsing of the content corresponding to the accompanying information.
A control method for a terminal device, executed by a computer of the terminal device including a storage unit and a playback unit for playing back content,
Generating accompanying information that is information accompanying content that can be played by the playback unit;
Storing the accompanying information in the storage unit;
Transmitting the generated accompanying information to the server device,
The reproduction unit reproduces content based on the accompanying information stored in the storage unit,
The step of transmitting the accompanying information to the server device includes transmitting the generated accompanying information to the server device independently from the start or end of browsing the content corresponding to the accompanying information. Method.
A content playback system including a terminal device including a playback unit for playing back content, and a server device capable of communicating with the terminal device,
The terminal device
A generating unit for generating accompanying information that is information accompanying content that can be played by the playing unit;
A first storage unit for storing the accompanying information;
A transmission unit for transmitting the accompanying information generated by the generation unit to the server device,
The server device
A second storage unit for storing accompanying information of the content;
The reproduction unit reproduces content based on the accompanying information stored in the first storage unit,
The content reproduction system, wherein the transmission unit transmits the accompanying information generated by the generating unit to the server device independently of the start or end of browsing of the content corresponding to the accompanying information.
The server device
A management unit for managing the accompanying information transmitted by the transmission unit;
The management unit
Determining whether the accompanying information transmitted by the transmitting unit and the accompanying information stored in the second storage unit compete with each other;
If it is determined that there is a conflict, the accompanying information transmitted by the transmitting unit is corrected so as to avoid the conflict, and the corrected accompanying information is stored in the second storage unit. The content reproduction system described.
The management unit
The corrected incidental information is transmitted to the terminal device when it is determined that the incidental information transmitted by the transmission unit and the incidental information stored in the second storage unit compete with each other. The content reproduction system described.
The management unit
When it is determined that the accompanying information transmitted by the transmitting unit and the accompanying information stored in the second storage unit compete with each other, the terminal device is inquired about whether or not to register the modified accompanying information. 9. The content reproduction system according to claim 7, wherein, on the condition that an answer permitting permission is received, the modified accompanying information is stored in the second storage unit in the second storage unit. .