WO2008059653A1

WO2008059653A1 - Content reproducing system and content reproducing method

Info

Publication number: WO2008059653A1
Application number: PCT/JP2007/067338
Authority: WO
Inventors: Minako Masubuchi
Original assignee: Sharp Kabushiki Kaisha
Priority date: 2006-11-16
Filing date: 2007-09-05
Publication date: 2008-05-22
Also published as: JP4944124B2; JP2012110055A; JPWO2008059653A1

Abstract

[PROBLEMS] For a 'closed' private reproducing system, what is reflected onto a conventional request window in accordance with a view history is only the view history of a user himself or herself in the private reproducing system. That is, as to the contents recorded in a recording/reproducing apparatus in the 'closed' private reproducing system, the view histories of external other users are not reflected, for example, what evaluations the external other users have are not reflected. [MEANS FOR SOLVING PROBLEMS] In order to solve the problem described above, there is provided a content reproducing system that allows a 'closed' private reproducing system of each individual user to be 'opened' for utilizing a request window on which the view history of another user is reflected.

Description

Specification

Content reproduction system and content reproduction method

Technical field

TECHNICAL FIELD [0001] The present invention relates to a technique for playing back content recorded on a recording / playback device in a home or the like using a dedicated portable playback device.

Background art

Conventionally, the following private content playback systems have been provided. In this private playback system, programs received by HDD recorders at home, etc., recorded programs, or content data such as music, text, and web pages acquired and recorded by other recording / playback devices via a network are transmitted. Can be sent to a portable playback device such as a mobile phone for playback. In such a content private playback system, various interfaces for selecting and requesting playback content on a mobile playback device such as a mobile phone are provided.

[0003] For example, in Patent Document 1, in the above-described content private playback system, the content viewing history is stored in a portable playback device such as a mobile phone, and the stored viewing history is transmitted to the recording / playback device. A technology relating to a portable playback device (portable information terminal device) having the above configuration is disclosed. Then, using this viewing history, for example, the content that is currently being viewed is displayed at the top or only the content that is currently being viewed is displayed. When the request screen (interface screen for content playback request) is played back on the mobile phone It can be displayed on a device or a recording / reproducing device.

Patent Document 1: Japanese Patent Laid-Open No. 2005-286855

Disclosure of the invention

Problems to be solved by the invention

[0004] However, the above technique has the following problems. That is, it is a problem that only the viewing history of the individual user in the private playback system is reflected on the return screen corresponding to the viewing history. In other words, regarding the content recorded on the recording / playback device in the “closed” private playback system, Other people outside of the private playback system) have a reputation! /, The power of ru, and! /, The other person's viewing history is not reflected.

Means for solving the problem

[0005] In order to solve the above problems, the present invention uses a request screen reflecting the viewing history of other users "open" even in a private playback system "closed" for each user. Provided is a content reproduction system that enables this.

[0006] Specifically, a management server that includes a plurality of private playback systems including a recording / playback device and a portable playback device having a request function dedicated to content recorded in the recording / playback device, and manages the request Content management system, and the management server makes a request to the portable playback device based on the totaling section that aggregates requests for the same content across the private playback system and the totaling result in the totaling section. And a request screen transmission unit that transmits a request screen that is an interface screen for the content reproduction system.

The invention's effect

[0007] According to the present invention configured as described above, even in the above-mentioned "closed" private playback system, a request screen in which the number of views (request count) of others other than the private user is reflected "open" is displayed. Can be used.

[0008] And, in general, for users' interest in content, especially in entertainment-related content such as broadcast programs and music, the number of times of viewing, etc. It is easily affected by the evaluation of others. Therefore, by presenting a request screen reflecting the number of times other people (other than private users) have viewed to the user of the private playback system, he would like to view the content displayed on the request screen more than before. The appeal effect can be expected.

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the present invention is not limited to these embodiments, and can be implemented in various modes without departing from the scope of the present invention. In Example 1, claims 1, 2, 6, and 7 are mainly described. To do. In the second embodiment, claims 3 and 8 will be mainly described. In the third embodiment, claims 4 and 9 will be mainly described. In the fourth embodiment, claims 5 and 10 will be mainly described.

[0010] << Example 1 >>

FIG. 1 is a diagram illustrating an example of a request screen displayed on a mobile phone which is an example of a portable playback device in the content playback system of the present embodiment. As shown in this figure, the request screen power for sending a playback request to the recording / playback device α constituting the private playback system α Displayed on the display of the mobile phone α belonging to the private playback system α Has been. And on the request screen, “1 Monday Drama: 1035 2 people”, “2 News 10: 8998 people”, “3 Quiz 3 choices: 2494 people”, and other private playback systems β and The content names arranged in order of the number of viewers (number of requests) related to the content aggregated across γ, ··· are displayed!

As described above, in the content reproduction system of the present embodiment, the number of viewers (number of requests) of the content is “opened” across the private reproduction system. The re-list screen reflecting the results of the aggregation can be used in a “closed” private playback system. As a result, the user can know the interest level of others related to the content.For example, referring to such public interest level, the user can execute the playback request of the content he wants to see in his private playback system. it can.

[0012] Functional configuration>

FIG. 2 is a diagram illustrating an example of functional blocks in the content reproduction system of the present embodiment. As shown in this figure, the content playback system of the present embodiment includes a plurality of “private playback systems” (0210 α, 0210/3, 0210 γ), and manages the requests in these private playback systems. It is a system that includes a server (0200).

[0013] It should be noted that the functional blocks of the devices and servers constituting the system described below can be realized as hardware, software, or both hardware and software. Specifically, if you use a computer, you will need a CPU, main memory, bus, or secondary storage device (such as a hard disk, non-volatile memory, CD-ROM, or DVD-ROM). I / O ports for hardware components such as storage media and read drives for such media, printing devices, display devices, other external peripheral devices, and other external peripheral devices

These include driver programs and other application programs for controlling the hardware, and user interfaces used for information input.

[0014] In addition, these hardware and software are such that the program expanded on the main memory is processed by the CPU, the data held on the memory and the hard disk, the data input via the interface, etc. It is used to process, store, output, or control each hardware component. Further, the present invention can be realized not only as an apparatus but also as a method. In addition, a part of such an invention can be configured as software. Furthermore, a software product used for causing a computer to execute such software and a recording medium in which the product is fixed to a recording medium are naturally included in the technical scope of the present invention (the same applies throughout this specification). Is).

Here, first, “private reproduction system α” (0210 α) will be described. Although not shown in the figure, the private playback system (3 and γ have the same configuration as α described below.

The “private playback system α” (0210 α) includes a “recording / playback device” (021 1 α) and a “portable playback device” (021 1 α) having a dedicated function for requesting content recorded in the recording / playback device ( α) and force.

“Recording / playback device” (021 1 α) is a terminal device having a function of recording and playing back content data, such as an HDD / DV D that receives and records broadcast program content. There are various recorders. As an example of content data, video data of a broadcast program recorded on a recording medium or video data of a broadcast program being received by a tuner will be described below as an example. However, content data is of course limited to that. Other video data, music data, text data such as books, Web page data, etc. may be used.

FIG. 3 is a diagram illustrating an example of functional blocks in the recording / reproducing apparatus. As shown in this figure, the “recording / reproducing device” (031 1) is connected to the “content holding unit” (031 1A) and “content”. "Listist transmission unit" (0311B), "request reception unit" (0311C), and "content transmission unit" (0 311D).

[0019] The "content holding unit" (0311A) has a function of holding content such as broadcast program data, other moving image data, music data, text data, web page data, such as HDD, DVD, It can be realized by a recording medium such as a nonvolatile memory. In the private playback system, the content held in the content holding unit is transmitted to the mobile phone or the like in response to a request from a mobile phone or the like that is a mobile playback device.

The “content list transmission unit” (0311B) has a function of transmitting a content list to a management server (0300) described later. The “content list” is data in which the title name and identification information of the content held in the content holding unit is listed, and the management server refers to this content list and each private playback system A request screen suitable for each can be generated. Details of the request screen using this content list will be explained in the section “Request Screen Sending Unit” which is a configuration requirement of the management server.

The “request receiving unit” (0311C) has a function of receiving a content playback request transmitted from a mobile playback device such as a mobile phone. The request received here includes, for example, information for identifying the portable playback device such as a telephone number if the portable playback device is a mobile phone. Content will be transmitted like this. The request receiving unit may receive a force output request such as a mobile phone via a management server as shown in the figure, or may be transmitted from a mobile phone or the like without going through the management server as described later. It may be configured to receive requests.

[0022] The "content transmission unit" (0311D) has a function of transmitting content to a portable playback device dedicated to itself in response to reception of the request. It should be noted that the determination as to whether the portable playback device is dedicated to itself may be performed by, for example, matching processing between a telephone number included in the received request and a telephone number obtained by a registration process as described later. . Also, with regard to content transmission executed by the content transmission unit, for example For example, the management server may be configured to manage the content transmitted and received by transmitting the content via the management server. Of course, content transmission may be executed via the management server! /, Because of traffic.

[0023] Then, a request for reproduction of the content held in the content holding unit of the recording / playback device is transmitted, and the content transmitted from the content transmission unit is acquired as the next “portable playback device” (0312 In Fig. 2, it is 0212 α).

As described above, the “portable playback device” (0212 α) is a terminal device having a request function dedicated to content recorded in the recording / playback device. Note that this portable playback device will be described mainly using a mobile phone as an example in this specification. Of course, the portable playback device may be a PDA, a smartphone, a notebook computer, a portable video player compatible with a network, or a unique portable information terminal designed exclusively for a recording / playback device.

FIG. 4 is a diagram illustrating an example of functional blocks in the portable playback device. As shown in this figure, “portable playback device” (0412) includes “request screen receiving unit” (0412A), “request transmitting unit” (0412B), “content receiving unit” (0412C), “ Content playback display section ”(0412D).

The “request screen receiving unit” (0412A) has a function of receiving a request screen transmitted from the management server. Regarding the request screen, the power described later in the section “Request Screen Sending Unit”, which is a configuration requirement of the management server, is characterized by the fact that the total number of requests in other private playback systems is tabulated. This is a reflected point. The received request screen is displayed on a display or the like, and a content playback request is accepted by a mobile playback device such as a mobile phone by selecting a content name on the request screen.

[0027] The "request transmission unit" (0412B) has a function of transmitting a content reproduction request according to the selection on the request screen received by the request screen reception unit. The request transmission from the request transmission unit may be configured to be transmitted to the recording / reproducing apparatus via the management server as described later, or may be configured to be transmitted without going through the management server.

FIG. 5 shows a request transmitted from the request transmission unit of the portable playback device to the recording / playback device. It is the schematic showing an example of the est. As shown in this figure, the request generated by selecting the program name on the above request screen includes “Title (program name)”, “Channel (broadcast channel)”, “Time (broadcast time)”, “Region”. (Broadcasting area) "and other information for identifying content that requires playback. In the private playback system, content identified with reference to such a request is transmitted to a mobile phone or the like, which is a dedicated mobile playback device, so that the content stored in the recording / playback device can be carried. Perform playback on the phone.

[0029] Also, the content identification information such as "program name" included in this request is, for example, D information such as "A1234" that is attached to the content separately for recording / playback by the recording / playback apparatus! It does not matter. In addition, the D information may be attached using ID information attached to the program in the electronic program guide, for example. In such a case, the same electronic program guide is used in all private playback systems belonging to this content playback system so that the same content is given the same ID information. Also good. By doing so, it becomes possible to identify the identity of the content described later with a simpler process.

[0030] In addition, this request includes a "Tel No. (telephone number)" uniquely assigned to the portable playback device, or a MAC address and a serial number. The recording / playback apparatus that receives the request can use this “Tel No.” to identify the destination of the content and transmit the content. Also, as will be described later, by using this “Tel No.” or the like, it is possible to ensure the privateness of the private playback system by determining whether the portable playback device is dedicated to itself.

The “content receiving unit” (0412C) has a function of receiving content transmitted from the recording / reproducing apparatus in response to a request. The “content reproduction display unit” (0412D) has a function of reproducing and displaying the content received by the content reception unit on, for example, a display. In this way, in this private playback system, the content of the recording / playback device can be played back and displayed on a mobile phone or the like in response to a request from a mobile phone or the like that is a mobile playback device.

[0032] The relationship between the recording / playback apparatus and the portable playback apparatus in the private playback system “Dedicated” indicating that the recording / playback apparatus is configured to accept only a content playback request from an authorized portable playback apparatus. As a method for dedicating a portable playback device to a dedicated recording / playback device, for example, a method of using a dedicated terminal set and prepared in advance for the recording / playback device as the portable playback device can be cited. Or, a method of using a portable information terminal such as a general mobile phone, PDA, laptop computer, or network-compatible portable video player as a dedicated portable playback device by registering various identification information in this recording / playback device. And so on.

[0033] FIG. 6 is a diagram for explaining an example of information registration for dedicating a general portable information terminal to a recording / reproducing apparatus. If the portable playback device is a mobile phone as shown in this figure, the telephone number “080-1111 XXX” is registered in the communication unit of the recording / playback device by the setting registration process. Then, it is determined whether or not the telephone number included in the request matches the registered telephone number “080-1111—X X X X” by CPU logical operation processing. If they match, the recording / playback device performs processing according to the request. If they do not match, the recording / playback device does not support it, so that a general mobile phone terminal can be used exclusively for the recording / playback device. It can be done. In addition to the mobile phone number, for example, identification information of a SIM (Subscriber Identity Module) card that is set unique to the device, an e-mail address, or the like may be used. Alternatively, if the portable playback device is not a mobile phone terminal, a MAC address or a device-specific serial number may be used. Although not shown, the MAC address “00-02-C8-5E-XX-XX” of the communication unit of the recording / reproducing apparatus may be registered in the mobile phone terminal.

[0034] In this way, the private playback system α responds to playback requests from portable playback devices such as other private playback systems 0 and γ mobile phones by referring to registered telephone numbers, for example. It is a “closed” private playback system that processes it so that it does not.

In the content playback system of the present embodiment, as shown in FIG. 7, when a request is transmitted from a mobile playback device such as a mobile phone in the private playback system, the request is sent simultaneously. Is transmitted to a management server having the following configuration ( _a ), or is transmitted via the management server (b). According to it, such "closed" private Also in the playback system, using the management server, it is possible to use a request screen that reflects the number of views that have been opened and counted for other private playback systems. Let it be ί 毁.

[0036] Returning to FIG. 2, next, “Management Sano” included in the content reproduction system will be described. “Management Server” (0200) is “Aggregation Unit” (0201) and “Request Screen Transmission Unit” (020 2) and. This management server has a function for managing requests in the private playback system. This “request management” refers to the cross-tabulation of requests in the “aggregation unit” described below and the “request screen transmission unit”. The process of acquiring, holding, and identifying the request to be executed in connection with the transmission of the request screen.

[0037] "Aggregating unit" (0201) has a function of aggregating requests for the same content across private reproduction systems. Note that the “summary of requests across” in this tabulation section is executed, for example, by sending the request in the private playback system to the management server as described above, or by sending it via the management server. Can

FIG. 8 is a conceptual diagram showing an example of the total number of request requests across the plurality of private playback systems in this totaling unit. As shown in this figure, “request: Monday drama” output from a mobile phone or the like in the private playback system β is transmitted to the recording / playback apparatus belonging to the same private playback system / 3 via the management server. In addition, “Request: Monday Drama” and “Request: Month 8“ Birds and Caricatures ”” _Powered by the Private Playback System _Ί and Private Playback System α Sent to the management server along with the request

[0039] Then, the management server identifies the identity of the content from the titles such as “Monday Drama” and “Month 8“ Birds and Caricatures ””, and requests the same content for each content. The number is counted.

[0040] It should be noted that a plurality of private playback systems included in the content playback system of the present embodiment are not compatible with content identification information or the like unless, for example, the same electronic program guide is used! Is likely to become an independent system! So for example There may be cases where the content title included in the request is different even if the content is the same due to a change in the name. Therefore, with regard to “identity identification of content”, which is necessary for the cross-tabulation of requests on the management server, for broadcast programs such as “broadcast channel”, “broadcast time”, “broadcast region”, etc. included in the request. Using the information, the identity of “Monday Drama” in FIG. 8 and “Month 8“ Birds and Caricatures ”” may be identified and aggregated. In addition, even if the content is the same in a broadcast program, the channel information and broadcast time information may differ from broadcast area to broadcast area. Therefore, electronic program guide information may be used to search for and acquire program information using “regional information” as a key, and to identify identity using the program information.

[0041] Further, as described above, when the recording / playback apparatus such as “A1234” is the identification ID assigned to the content for management as described above, the identification information power of the content included in the acquired request is identified from the recording / playback apparatus. It is recommended that the content identity identification process be performed by obtaining a content list that associates IDs with content titles.

[0042] In addition, by configuring the management server to acquire all or part of the requested content itself, the content content itself, for example, audio frequency, frame data, text sentences, and the like can be matched. It may be configured to identify the identity of the content.

FIG. 9 is a diagram for explaining an example of identification of identity by such content data matching processing. As shown in this figure, for example, in the case of audio frequency matching processing, it is determined by matching processing whether the waveform of the audio frequency within the predetermined range (a) in the figure is included in (b) in the figure. If the matching rate is equal to or higher than the threshold, it is determined that the contents are the same. In addition, in the case of frame matching processing, the matching processing determines whether the frame image power included in the content (a) in the diagram is included in the content (b) in the diagram. When the matching rate is equal to or higher than the threshold, it is determined that the contents are the same.

Thus, in this embodiment, a request transmitted from a portable playback device such as a mobile phone to the recording / playback device in the “closed” private playback system is acquired by the management server. And the content identification information and other identification information included in the request, It is possible to identify the same content by using a process such as a pinching process, and to aggregate requests across multiple private playback systems by content. Then, from the number of requests that have been “opened” in this way, a request screen that reflects the number of views that has been aggregated by the next “request screen transmission unit” is sent to the “closed” private playback system. be able to.

[0045] Note that the requests aggregated here may include requests for the recording / playback apparatus itself to perform playback, in addition to requests from the mobile phone or the like to the recording / playback apparatus. In addition to counting the request when the request is made as described above, it is possible to count when the information indicating whether or not the content reproduction on the mobile phone is actually executed by the request is acquired. Also, it may be configured to count the actual number of content playbacks according to the request.

[0046] The totaling process in the totaling unit may be a totaling result only within a predetermined period, or may be a cumulative total number up to now. In addition, if the content is a series drama, etc., it is acceptable to count for each story, and it is also possible to count for the cumulative total of the series. Alternatively, a configuration may be adopted in which information indicating the end of playback is acquired so that the requests to be counted are only requests for content that is currently not played back and that is currently being played back.

[0047] In addition, by registering user information such as gender, age, and residence in the management server and configuring the request to include the user ID, the number of requests such as gender and age can be aggregated. May be. In addition, a content list is acquired for each private playback system in advance, and private playback systems with similar content lists are grouped so that only requests in private playback systems belonging to the same group are aggregated. May be. As a result, it is possible to provide the user with a request screen that is aggregated based on the number of user requests that are likely to have similar interest in content.

[0048] The "request screen transmission unit" (0202) transmits a request screen, which is an interface screen for requesting, to a portable playback device such as a mobile phone based on the aggregation results in the aggregation unit (0201). It has a function. The “request screen based on the counting result” is, for example, a list of content names and thumbnail images arranged in descending order of the number of request counting by content. Request screen to be displayed. Alternatively, for users who are interested in content that is not generally known to the public, request screens that are displayed in order of decreasing number of requests may be sent. Another example is a request screen that displays only content whose total count is greater than or less than a threshold.

FIG. 10 is a diagram illustrating an example of a request screen transmitted from the request screen transmission unit. As shown in the figure, this request screen is a request screen based on the stored content list of the recording / reproducing apparatus α which is the request transmission destination of the mobile phone α which is the portable reproducing apparatus.

[0050] In other words, the retained content list of the recording / playback device α is separately acquired by the management server using the identification ID of the mobile phone α and the result screen generated by reflecting the counting result in the counting unit It is. In this way, for the mobile phone _α dedicated to the recording / playback device _α , only the content that is held by the recording / playback device α and can be immediately played back by request can be displayed on the request screen. good.

[0051] Alternatively, as shown in FIG. 11, a request screen in which the content names are arranged in order of, for example, the total number of requests managed by the management server may be used.

FIG. 11 is a diagram showing another example of the request screen transmitted from the request screen transmission unit. As shown in this figure, this request screen displays the content names, etc. in order of the total number of requests managed by the management server, regardless of the content held by the recording / playback device α. It is a request screen. In this way, the user can know the general public interest level, such as the number of requests, even for content that is not recorded and cannot be played back by his / her private playback system.

[0053] As shown in Fig. 11, in this request screen, the content that is not held by the recording / playback device α is usually used, such as attachment of white characters or icons, by using the holding content list of the recording / playback device α. It may be configured so that it can be displayed differently and can be notified that it cannot be played immediately.

[0054] For content that is not held by the recording / playback apparatus α, a “0” button or the like for transmitting a recording request for newly recording by the recording / playback apparatus is displayed. You may be made to do. For example, when this button is clicked on the request screen, the electronic program table and the like are referred to search for rebroadcasts of the same content, and if so, a scheduled recording command (recording request) is generated and transmitted to the recording / playback device. It is a state of doing. Alternatively, if it is music content, use a link to a music data sales site on the network and guide the user to that site by pressing the button, or automatically make a purchase request for the music content on that site. And so on.

[0055] In addition, it is preferable that the request for the content selected using this request screen is also transmitted to the management server and used for the totaling process in the totaling unit.

[0056] In this way, the content playback system of this embodiment uses a request screen that reflects the number of return requests by content of other people than private users in the “closed” private playback system for each user. Will be able to.

Note that, as shown in FIGS. 10 and 11, the request screen generation / acquisition processing using the stored content list of the recording / playback apparatus may be executed specifically as follows, for example. . First, the identification power of content such as content titles contained in the retained content list acquired from the recording / playback device, and the power contained in the content identification information of the count list held by the management server itself, Judgment is made by calculation processing, and the ones with matching identification information are extracted. In the generation and acquisition of the request screen in FIG. 10, only the content corresponding to the extracted content identification information is listed. On the other hand, in the generation and acquisition of the request screen shown in FIG. 11, only the extracted content can be requested from the content identification information of the count list held by the management server itself, and the other icons cannot be requested. Or insert a link to a site where the content can be obtained.

[0058] By the way, in order to perform cross-tabulation processing of requests and transmission processing of request screens according to the above-described configuration requirements, of course, configuration requirements for acquiring requests from mobile phones that are portable playback devices and content Configuration requirements for obtaining the list are also required. In the following, the constituent requirements that are secondary to the processing of the above-described “aggregation unit” and “request screen transmission unit” will be briefly described.

FIG. 12 is a diagram illustrating an example of a more detailed functional block in the management server. . As shown in this figure, the “management server” (1200) includes a “totaling unit” (1201) and a “request screen transmission unit” (1202). Since these “aggregation part” and “request screen transmission part” have already been described, detailed description thereof will be omitted.

The management server further includes a “request acquisition unit” (1203), a “content list acquisition unit” (1204), and a “same content identification unit” (1205). May have a “request transfer unit” (1206).

The “request acquisition unit” (1203) has a function of acquiring a request output from a portable playback device such as a mobile phone across the private playback system as described above. Then, the requests acquired here are classified for each identical content by the next identical content identification unit, and aggregated across the same content by the “aggregation unit”. In some cases, the acquired request may be transferred to the recording / reproducing apparatus.

The “content list acquisition unit” has a function of acquiring a content list from the recording / playback apparatus. Then, by using the content list acquired here, it is possible to generate and acquire the request screen as described in FIGS. 10 and 11.

[0063] The "same content identification unit" (1205) has a function of identifying the requested content regarding the acquired request. As a content identification method in the same content identification unit, specifically, as described above, there is a method of identifying the request target content from the “content title” included in the request. Alternatively, a method of identifying a content by acquiring a part of the content by a content acquisition unit (not shown) and executing the above-described matching processing by a logical operation processing of the CPU may be used. Then, by identifying the content here, the totaling unit can classify it for the same content and count the number of requests across the private playback system.

[0064] If the request acquired by the request acquisition unit is configured to be transmitted to the recording / playback device via the management server, the request acquired by the "request transfer unit" (1206) It is good to transfer.

[0065] Hardware Configuration>

Figure 13 shows the contents when the above functional components are realized as hardware. It is the schematic showing an example of the structure in the management server of a reproduction | regeneration system. The operation of each hardware component in the totaling of requests and transmission of request screens on the management server will be described using this figure.

[0066] As shown in this figure, the management server included in the content reproduction system of the present embodiment includes a "CPU (central processing unit)" (1301) that performs various arithmetic processes, a "main memory" (1302), , Is equipped. It also has an “HDD” (1303) that holds the counting results and “ΐ / θ (input / output)” (1304) that sends and receives information to and from the private playback system. They are connected to each other via a data communication path such as a “system bus” to send and receive information and process it.

[0067] Similarly, the mobile playback device α such as a mobile phone included in the content playback system of the present embodiment also has a “CPU” (1311) and a “main memory” (1312) that perform various arithmetic processes. It is equipped with. There is also an “I / O” (1313) for sending and receiving information to and from the management server and recording / playback device, a “frame memory” (1314) for expanding content for display, and a “display” (1315) for playing back and displaying content. I have. They are connected to each other via a data communication path such as a “system bus” to send and receive information and process it.

[0068] Further, the "main memory" provides a work area that is a work area of the program at the same time that the program for performing various processes is read for the CPU to execute. In addition, multiple addresses are assigned to each of the “main memory”, “HDD”, and “flash memory”, and programs executed by the “CPU” specify the addresses and access them to each other. It is possible to perform processing.

[0069] Here, a request operation for content playback is executed by a UI (user interface) not shown in a mobile playback device such as a mobile phone such as a private playback system α, / 3, or γ. Then, in response to the operation, a request including content identification information and its own telephone number is stored in the “main memory” and output from the “I / O” for transmission to the recording / playback device via the management server. The Alternatively, requests are sent separately to the recording / playback apparatus and the management server.

Then, the management server receives the request at “I / O” and stores it at address 1 of “main memory”. For example, “Tight” included in various requests obtained in this way. Content identification information such as “R” is used, and content identity identification processing is executed by “CPU” logical operation processing. Then, for each identified content, the number of requests is added and summed up by CPU counting. And count the results

[0071] On the other hand, when the “UI” of a mobile playback device such as a mobile phone is operated and a request screen is requested to be transmitted from “I / O”, the “count list” is used on the management server. Then, the “request screen” is generated and sent. First, using the identification information of the portable playback device α included in the request for transmission on the request screen, the recording / playback device of the request transmission destination

Get the MAC address. Then, a request for acquiring the content list held by the recording / reproducing apparatus is transmitted to the recording / reproducing apparatus. In response to the request, the stored content list acquired from the recording / reproducing apparatus by “I / O” is stored at address 2 of “main memory”.

[0072] Then, information for the request screen as shown in FIG. 10 or FIG. 11 is generated from the count list that is the total number of requests stored in “HDD” and the content list held by the recording / playback device, Store in address 3 of “Main memory”. The request screen information is transmitted to the “portable playback device α” with the “I / O” power.

[0073] Further, using the request screen, a request that is output from portable playback device α force such as a mobile phone is acquired by “I / O”. Then, the number of requests for the content indicated by the request is added and counted by the “CPU” calculation process, and the count list is updated. When the request is configured to be transmitted to the recording / reproducing device via the management server, the request is transmitted from “I / O” to the recording / reproducing device of the transmission destination included in the request. To do.

[0074] Then, in the recording / reproducing apparatus that has received the request, for example, whether or not the telephone number included in the request matches the telephone number indicating the registered device registered in itself as described above. Is determined by the logical operation processing of its own “CPU”. If the result is a match, the content is transmitted to a portable playback device such as a mobile phone, assuming that the request is from a dedicated portable playback device.

Then, in a portable playback device such as a mobile phone, the content is received by “I / O” and the received data is expanded in a “frame memory”. The expanded content data is It is displayed on the “display”.

FIG. 14 is a flowchart showing an example of the processing flow in the management server included in the content reproduction system of the present embodiment. Note that the steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium. As shown in this figure, first, a plurality of private playback systems including a recording / playback device and a mobile playback device such as a mobile phone having a request function dedicated to content recorded in the recording / playback device are provided. In the content reproduction system including the management server that manages the content, the management server aggregates requests for the same content across the private reproduction system (step S1401).

Then, a request screen is acquired based on the counting result (step S 1402), and the acquired request screen is transmitted to a portable playback device such as a mobile phone (step S1403).

FIG. 15 is a sequence diagram showing an example of a processing flow until requests are totaled across the content reproduction system of the present embodiment. The steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium. As shown in this figure, first, in the recording / reproducing apparatus, a dedicated portable reproducing apparatus registration process or the like is executed, for example, by acquiring or registering a telephone number (step S 1501).

[0079] After that, a content playback request selection operation using a request screen transmitted from the management server, for example, is executed in a mobile playback device such as a mobile phone, and the identification information of the selected content and the phone number of the mobile playback device itself And the like are transmitted to the recording / reproducing apparatus and the management server (step S 1502).

[0080] Then, in order to determine whether or not the request is from a dedicated portable playback device, the recording / playback device, for example, the telephone number included in the received request and the information acquired and registered in step S1501. It is determined whether or not the telephone numbers match (step S 1503). Here, if they match, the recording / playback device transmits the content corresponding to the request to the mobile playback device such as a mobile phone (step S 1504).

[0081] Then, in a portable playback device such as a mobile phone, the container transmitted from the recording / playback device. For example, it is reproduced and displayed on a display or the like (step S1505).

On the other hand, the management server executes the following processing in order to count the number of requests. First, when a request is received from a portable playback device such as a mobile phone, the identity of the content is identified by a decision process using the content identification information included in the request, or a matching process for the content itself acquired separately. (Step S 1 506). Then, the number of requests for each identified identical content is totaled (step S 1507), and the totaled result is updated and stored in a storage medium as a count list (step S1508).

[0083] Then, by executing such processing across a plurality of private playback systems, in the content playback system of the present embodiment, a return from a mobile playback device such as a mobile phone is crossed by the same content. And so on. Next, with reference to FIG. 16, an example of request screen generation / acquisition processing based on the total number of requests as described above, and request processing using the request screen will be described.

FIG. 16 is a sequence diagram illustrating an example of a flow of a return process using a request screen in the content reproduction system of the present embodiment. The steps shown below are

Further, it may be a processing step that constitutes a program recorded on a medium for controlling a computer. Here, each process as described in FIG. 15 is executed. As shown in this figure, first, in the management server, the number of requests aggregated for the same content is updated to a storage medium as a count list, Accumulate (step S1601).

[0085] Thereafter, when a request for transmitting a request screen is performed using a UI or the like in a portable playback device such as a mobile phone, a request for transmitting a request screen is output from the portable playback device to the management server (step S 1602).

Upon receiving this request screen transmission request, the management server performs the following processing in order to identify the recording / reproduction device of the private reproduction system to which the portable reproduction device that has transmitted the transmission request belongs. For example, referring to the telephone number or device ID of a mobile playback device such as a mobile phone included in the transmission request, the recording / playback device is specified from the “portable playback device recording / playback device table” held by itself. Alternatively, if the transmission request itself includes the IP address of the recording / reproducing apparatus, it can be used. So Then, a transmission request for the retained content list is output to the recording / reproducing apparatus thus specified (step S 1603). Then, the recording / reproducing apparatus that has received the transmission request transmits its own content list to the management server (step S 1604).

[0087] In the management server, the content list is acquired, and the acquired content list and the update result are accumulated! A request screen is generated and acquired (step S 1605). Then, the request screen is transmitted to a portable playback device such as a mobile phone that has output the transmission request (step S16 06).

[0088] Then, in a portable playback device such as a mobile phone, the received request screen is displayed on a display or the like, and selection of request content is accepted (step S 1607). When the user selects one of the content names on the request screen on the UI, the request for the selected content is transmitted to the recording / playback apparatus and the management server (step S 1608).

Thereafter, as described with reference to FIG. 15, the content transmission / reproduction process according to the request, the total number of requests for the same content, and the like are executed. In the above processing example, an example in which a request from a portable playback device such as a mobile phone is separately transmitted to the management server and the recording / playback device has been described. May be configured to be transmitted only to the recording / playback apparatus via the management server.

[0090] Other functional configurations>

Further, the content reproduction system of the present embodiment may have the following configuration. FIG. 17 is a diagram showing another example of functional blocks in the content reproduction system of the present embodiment. As shown in this figure, the content playback system includes a “private playback system” (1710) composed of a “recording playback device” (17 11) and a “portable playback device” (1712), and a “management server” (1700 ) And power. Then, the management server includes “communication means” (1700a), “content ID acquisition means” (1700b), “aggregation means” (1700c), “control means” (1700d), and “user management means”. (1700e). Further, the recording / reproducing apparatus includes “communication means” (1711a), “storage means” (1711b), and “content extraction means” (1711c). Further, the portable playback device has “communication means” (1712a) and “display means” (1712b).

Here, when a request is transmitted from the “communication means” of the portable reproduction device such as a mobile phone to the recording / reproduction device, the management server also obtains the request by its own “communication means”. Then, the “content ID acquisition means” acquires the content ID such as “title” included in the request. Then, using the content ID, the “counting means” counts the number of requests for each content. Then, for example, the total number of requests for each content is stored in the “storage means” of the management server, not shown.

Then, the user operates a portable playback device such as a mobile phone, and connects to the management server from “communication means”. The management server refers to the “portable playback device ID—recording / playback device MAC address table” stored in the “user management means” and connects the portable playback device and the recording / playback device of the same private playback system. Connecting.

Subsequently, the recording / playback apparatus outputs the content list stored in the “storage unit” to the management server from the “communication unit”. Then, in the management server, the acquired content list is rearranged in order of the total number of requests stored in the “storage means” (not shown), and a request screen as shown in FIG. 10 is generated by the process of “control means”. get. Or, as shown in Fig. 11, the total number of requests is stored in the storage means! Of all or part of the content, refer to the acquired content list and those in the content list can be played If there is no request, the request screen to be displayed in a non-reproducible state is generated and acquired by the process of “control means”.

Then, the generated and acquired request screen is transmitted from the “communication means” of the management server to a portable playback device such as a cellular phone. Then, the request screen is displayed on the “display means” of the portable playback device such as a mobile phone, and the user selects a desired content from the contents arranged in the order of requests.

Then, the request is transmitted from the “communication means” of the portable playback device such as a mobile phone to the recording / playback device via the management server. In the recording / playback apparatus, the “content extraction unit” extracts the data of the content corresponding to the request and outputs it from the “communication unit”. So Then, it is distributed to the “communication means” of the portable playback device such as a mobile phone that has transmitted the request via the management server, for example, and the content is reproduced and displayed on the “display means”.

In addition, the “aggregation unit” of the management server counts up the number of requests for the content according to the request, and calculates the accumulated number of requests for the content stored in the “storage unit” (not shown). That is, it is updated.

[0098] Brief description of effect>

As described above, with the content playback system of this embodiment, the number of viewers (number of requests) of the content is “opened” across the private playback system, and the request screen reflecting the total results is closed. It can be used in a private playback system. As a result, the user can know the interest level of others related to the content, and execute a playback request for the content that he / she wants to see in his / her private playback system, for example, referring to the public interest level. be able to.

[0099] <Example 2>

The present embodiment is a content reproduction system based on the first embodiment, wherein the recording / reproducing apparatus has an automatic content acquisition function such as automatic recording using a keyword or the like. If the recording / reproducing apparatus has a function such as automatic recording as described above, the following situation is expected to occur frequently. In other words, unless conditions such as keywords are narrowed down, many contents not intended by the user are automatically recorded on the recording / playback apparatus. Then, the user will have many programs that are automatically recorded on the recording / playback device but do not have the time to view them. And you can't watch it! /, The program is deleted from the recording medium one after another! /, And so on.

[0100] The present invention can be an effective means for selecting a content to be viewed by a user from a huge number of contents automatically recorded as described above. This is because, as described above, in the present invention, a user can select a content with reference to another user's opinion (request count) and execute a reproduction request.

[0101] Functional configuration> FIG. 18 is a diagram illustrating an example of functional blocks in the recording / playback apparatus of the content playback system of the present embodiment. As shown in this figure, the content playback system has the power of “Management Sano” (1800) and “Private Playback System” (1810). In addition, the pipeline playback system includes a “recording / playback device” (1811) and a “portable playback device” (1812). Since “management sano and“ portable playback device ”are the same as those already described in the first embodiment, the description thereof is omitted.

A feature of the present embodiment is that the recording / reproducing apparatus includes a “reception unit” (1811A) and a “specific recording unit” (1811B).

[0103] The "accepting unit" (1811A) has a function of accepting a search condition including a content attribute from a user. “Content attribute” refers to information indicating content attributes, such as content names and other keywords, content details, content source addresses, or content data formats. In addition, if the content is a broadcast program, information such as the genre of the program such as sports, dramas, and movies, names of staff such as performers / directors / producers, production / broadcaster names, broadcast times, etc. may be mentioned. For other contents, for example, information such as a content creator is included.

[0104] The "accepting unit" accepts these content attributes input by operating a GUI (graphical 'user' interface) or an input device. The recording / reproducing apparatus according to the present embodiment can search for a corresponding program using an electronic program guide or the like using these content attributes as keywords as in the conventional automatic recording apparatus.

The “specific recording unit” (1811B) has a function of specifying and recording content that matches the accepted search condition from a content table such as an electronic program guide. “Content tape nore” refers to a table in which a plurality of contents can be searched, such as an electronic program table, a music sales site music list, and an RSS table list.

Then, by searching the content table using the content attribute received by the reception unit as a search key, it is possible to specify the content desired by the user and execute automatic recording. FIG. 19 is a diagram illustrating an example of content recorded by the processing of the specific recording unit. As shown in this figure, for example, the reception section accepts search conditions (keywords) such as “movie” and “baseball” as content attributes, and a program including the above keyword by searching the electronic program guide at the specific recording section. Is identified. The recording media in this recording / playback device are automatically recorded based on the specified results. For example, the movie “Spyman”, “Sinking”, “The 'Boxing 4” and the baseball broadcast “September 7 Q vs. “K”, “September 8 vs. Q” and “September 8 vs. Q” have been recorded and accumulated!

[0108] When automatic recording is performed according to the content attributes accepted in this way, the total number of recorded contents becomes enormous. Therefore, in the content reproduction system of the present embodiment, in order to select the request target from such a large number of contents, a request screen that can refer to the opinions of other users as described in the above embodiment is provided. It is to display.

[0109] It should be noted that the configuration for executing the specific recording in the recording / reproducing apparatus may further have a configuration as shown in FIG.

FIG. 20 is a diagram illustrating an example of further detailed functional blocks in the recording / playback apparatus of the content playback system according to the present embodiment. As shown in this figure, the “recording / reproducing apparatus” (2011) of the present embodiment includes a “reception unit” (2011A), a “specific recording unit” (2011B), and an “electronic program guide acquisition unit” (2011C ) And “specific part” (2011D). Since “accepting part” and “specific recording part” have already been described above, description thereof will be omitted.

The “electronic program guide acquisition unit” (2011C) has a function of acquiring an electronic program guide. This electronic program guide acquisition unit is configured to acquire an electronic program guide via, for example, a web server on the Internet or a network, or to acquire an electronic program guide included in a digital broadcast wave from a tuner. It can be realized by configuring. Then, using the electronic program guide acquired in this way, a search process using, for example, a keyword indicating the content attribute received by the reception unit as a search key is executed.

[0112] The "identification unit" (2011D) has a function of identifying content that matches the accepted search condition from a content table such as an electronic program guide. The electronic program guide data includes program titles, performers, genres, internal channels, as well as program broadcast times and channel information. Information such as contents is also described. Therefore, for example, a search condition such as “movie” can be used as a keyword to search the electronic program guide by a logical operation process of “CPU”, and a program matching the search condition can be specified. The specifying unit may have a learning type search specifying function, for example. With this learning function, depending on the user's non-viewing erasure operation on the content, for example, the program whose title includes “movie” is not specified as a search result, but only the program whose genre is “movie” is specified. You may comprise so that a process may be performed.

[0113] Then, the reservation recording process is executed using the broadcast time zone and the broadcast channel information of the program specified in this way, and the automatic recording of the specific program is executed by the specific recording unit. .

[0114] Special hardware configuration>

FIG. 21 is a schematic diagram showing an example of the configuration of the recording / playback apparatus of the content playback system when the above functional components are realized as hardware. Note that the description of the configuration of the management server in the portable playback device has been described in the above embodiment, and will be omitted. The operation of each hardware component in the automatic recording process of a specific program in the recording / playback apparatus will be described using this figure.

As shown in this figure, the recording / reproducing apparatus of the present embodiment includes a “CPU” (2 101) for performing various arithmetic processes and a “main memory” (2102). Also, search conditions such as “HDDJ (2103)” that stores and holds content, “I / O” (2104) that transmits and receives information to and from portable playback devices such as mobile phones and management servers, A “UI (user interface)” (2105) that accepts input, a broadcast program that is an example of content, and a “tuner” (2106) that receives an electronic program guide are also provided. They are connected to each other via a data communication path such as “S” system bus, and send and receive information and process it.

[0116] In addition, the "main memory" provides a work area that is a work area of the program at the same time that the program for performing various processes is read for execution by the CPU. In addition, multiple addresses are assigned to each of the "main memory" and "HDD", and programs executed on the "CPU" exchange data with each other by specifying and accessing these addresses. It is possible to perform processing. Here, a search condition such as “movie” indicating the content attribute is input using an input device such as user power S remote control. Then, the input search condition is accepted by the “UI” and stored in the address 1 of the “main memory” as a search keyword. In addition, the electronic program guide data received at “Tuner” and recorded and held at address 1 of “HDD” is read and stored at address 2 of “main memory”.

[0118] Then, a program including a phrase that matches the central keyword of the program data included in the electronic program guide is specified by the logical operation processing of "CPU". Then, using the broadcast time zone and broadcast channel information included in the specified program data, a reserved recording command for the program is generated and stored in address 3 of the “main memory”. After that, it is determined by the built-in clock that the time indicated by the scheduled recording command has come, and the tuner is matched with the reception of the broadcast channel indicated by the scheduled recording command, and the `` HDD of the broadcast program received thereby When the recording process is executed, it is! /.

[0119] With the hardware configuration described above, it is possible to automatically record a specific program that matches the search condition accepted by the "UI".

[0120] Process Flow>

FIG. 22 is a flowchart showing an example of the flow of processing in the recording / playback apparatus of the content playback system of the present embodiment. Note that the steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium! /. As shown in this figure, first, a plurality of private playback systems including a recording / playback device and a mobile playback device such as a mobile phone having a dedicated function for content recorded in the recording / playback device are provided, and the request is received. In the content playback system including the management server to be managed, the recording / playback apparatus accepts the input of the search condition including the content attribute from the user (step S2201). Also, a content table such as an electronic program guide is acquired (step S2202). Then, the content that matches the accepted search condition is identified from the content table such as an electronic program guide (step S2203), and the identified content is recorded on a recording medium such as an HDD (step S2204).

[0121] Then, regarding the recording / reproducing apparatus for automatically recording the content that matches the search condition as described above, the contents automatically recorded by the processing flow as described in FIG. 14, FIG. 15, and FIG. A request screen for selecting an item is presented on a portable playback device such as a mobile phone.

[0122] Brief explanation of the effect>

As described above, the content playback system of this embodiment can refer to the opinions (number of requests) of other users in a private playback system including a recording / playback device that holds a huge number of contents by automatic recording. To provide a simple request screen.

[0123] Example 3

The present embodiment is a content playback system having the following characteristics in transmission of request screen data from a management server to a mobile playback device such as a mobile phone on the basis of the first and second embodiments. In other words, if the request screen does not fit on a display such as a mobile phone due to the large number of contents to be selected, the request screen data is divided into a size that fits into one display display and the split request screen is displayed. A content playback system configured to transmit sequentially.

[0124] In this way, in a private playback system in which there are many portable playback devices such as mobile phones with a small display size, communication traffic can be distributed according to the display screen size, and efficient data transmission and reception can be achieved. Will be able to do.

[0125] Special Functional Configuration>

FIG. 23 is a diagram illustrating an example of functional blocks in the management server of the content reproduction system according to the present embodiment. As shown in this figure, the content reproduction system has a “management server” (2300) and a plurality of “private reproduction systems” α, β γ. In addition, the “management server” (2300) has, based on the first embodiment, a “aggregation unit” (2301) and a “request screen transmission unit” (2302). The details of the “aggregation unit”, “request screen transmission unit” of the management server, and the private playback system have already been described in the above embodiment, and the description thereof will be omitted.

A feature point of the present embodiment is that the management server further includes a “request screen generation unit” (2303) and a “request screen transmission control unit” (2304). [0127] The "request screen generation unit" (2303) has a function of counting the number of requests for the same content and generating a request screen in which the content can be selected in descending order based on the result of the aggregation. Note that the request screen generation processing has already been described in the above embodiment using, for example, FIG. 10 and FIG. 11, and therefore detailed description thereof is omitted.

In this embodiment, the following processing is performed on the request screen generated by the request screen generation unit according to the display size of the portable playback device as the transmission destination at the next request screen transmission control unit. It is characterized by performing.

[0129] The "request screen transmission control unit" (2304) displays a request from the portable playback device when the request screen that generated the range that can be displayed on one screen is exceeded in the portable playback device that is the destination of the request screen. Each request screen request has a function to divide the request screen by one screen in order from the largest number of requests and send it to the request screen transmitter.

FIG. 24 is a conceptual diagram showing an example of a control process for dividing a request screen in the request screen transmission control unit. As shown in this figure, first, a request screen is generated by the request screen generation unit. Subsequently, for example, “320 pixels × 240 pixels”, information such as the display screen size and displayable size of the display is obtained from the portable playback device. Then, for example, the request screen generated according to the size information is divided into three screens. In addition, when the screen data is split, a button for requesting the next screen transmission is displayed, so that the next request screen is transmitted in response to the pressing operation of the button on the portable playback device. You may comprise as follows.

[0131] Then, the request screen power divided in this way, "request screen transmission unit" (2302), transmits one screen at a time in order of the number of requests in response to request screen requests from the portable playback device. That's it.

[0132] The request screen splitting process in the request screen transmission control unit has a large number of requests! / And may not be split in order! /. As described above, for example, the request screen divided and arranged in the order according to the rules specified by the user, such as the order of few requests! /, May be transmitted.

FIG. 25 is a more detailed view of the management server of the content reproduction system of the present embodiment. It is a figure showing an example of a functional block. As shown in this figure, the “management server” (2500) of the present embodiment includes the “aggregation unit” (2501), “request screen transmission unit” (2502), and “request screen generation unit” (2503). In addition to “Request screen transmission control unit” (2504), “Screen size information acquisition unit” (2505), “Screen division means” (2506), “Request screen request acquisition unit” (2507) ). Since the “aggregation unit”, “request screen transmission unit”, “request screen generation unit”, and “request screen transmission control unit” have already been described above, description thereof will be omitted.

[0134] "Screen size information acquisition unit" (2505) has a function of acquiring screen size information of a portable playback device such as a mobile phone. “Screen size information” refers to information indicating the screen size such as the resolution of the display screen and the number of inches.

[0135] Note that this screen size information acquisition may be included in a request screen transmission request initially transmitted from the portable playback device to the management server, and acquired every time there is a request for transmission of the request screen. good. Alternatively, the screen size information associated with the identification information of the portable playback device is registered in advance in the management server, so that the screen size information is obtained from the registration information based on the identification information included in the request screen transmission request. You may comprise as follows.

The “screen dividing means” (2506) has a function of dividing the request screen generated by the request screen generating unit (2503). As a method for dividing the request screen by the screen dividing means, for example, the following processing methods can be mentioned. For example, a request screen having a screen configuration in which the content shown in FIG. 24 is arranged vertically from the top to the bottom is generated by the processing of the request screen generation unit. And the display size of the request screen before resizing is vertically long, “640 horizontal by 1400 vertical”!

[0137] Here, as a result of the comparison processing by the logical operation of the CPU, the request screen of "640 X 1400" is displayed on the display of resolution "horizontal 320 x vertical 240" indicated by the screen size information of the portable playback device. It is judged that it cannot be displayed on one screen even after resizing. Therefore, the screen division means performs resizing so that the horizontal size becomes “320 pixels” while maintaining the aspect ratio of the request screen. Then, the resized request screen is divided by the vertical size indicated by the screen size information, for example, “240 pixels”, and the request screen is divided into “320 X 2”. For example, it is divided into three so that it fits on one screen of a 40 ”portable playback device.

[0138] The "request screen request acquisition unit" (2507) has a function of acquiring a request screen transmission request from the portable playback device. The request screen transmission request acquired here is a request for transmission of the request screen transmitted by operating the “UI” of a portable playback device such as a mobile phone as described above. Further, regarding the operation of the screen transmission request in the portable playback device, for example, a button for requesting the next page transmission may be provided on the divided request screen.

[0139] Each time the request screen request acquisition unit acquires a request screen transmission request from the portable playback device, the divided request screens are sequentially transmitted to the portable playback device. is there. In addition, when content request processing using the division request screen is executed in the portable playback device, information to that effect may be acquired. Accordingly, transmission of the subsequent division request screen can be stopped.

[0140] Special hardware configuration>

FIG. 26 is a schematic diagram showing an example of a configuration in the management server of the content reproduction system when the above functional components are realized as hardware. The operation of each hardware component in the request screen split transmission process on the management server will be explained using this figure.

[0141] As shown in this figure, the management server included in the content reproduction system of the present embodiment is similar to the implementation column 1 in that "CPU" (2601), "main memory" (2602), and "HDD" (2603) and “1 / OJ (2604). Then, the processing as described in the first embodiment is executed, and the record holding and updating processing of the power list to“ HDD ”is executed. Is done.

[0142] Then, when the "UI" of a portable playback device such as a mobile phone is operated and a transmission request for a request screen is transmitted from "I / O" to the management server, the same as described in the first embodiment. The “request screen” using the “count list” is generated and sent on the management server. At this time, the present embodiment is characterized in that the request screen is divided as follows.

First, for example, a request screen generated through the processing described in the first embodiment is stored at address 1 of “main memory”. Also included in screen transmission requests from portable playback devices The screen size information “320 X 240” of the display of the portable playback device is stored in address 2 of “main memory”. Then, it is determined whether or not the request screen can be resized to fit on one display screen of the portable playback device by logical operation processing of “CPU”. As a result of the judgment, if the field judgment result is output from the “CPU” if it does not fit on one screen, the request screen split size is determined and split processing is also performed by the four arithmetic operations of “CPU”, etc. Is done. The divided request screens A, B, and C force S are stored in addresses 3, 4, and 5 of the “main memory”, respectively. Then, the management server first transmits the division request screen A to the portable playback device that has transmitted the screen transmission request.

[0144] When this split request screen A is received, the portable playback device displays the split request screen A on the display. Then, in response to the content selection operation displayed on the split request screen A, a content playback request is transmitted to the recording / playback device, and the content playback is performed on the mobile playback device such as a mobile phone. In addition, the management server acquires information indicating that the content playback request has been transmitted and the content playback on the portable playback device has been executed. Then, the management server stops sending the divided request screens from the next page.

[0145] If there is no content that the user desires to reproduce on this division request screen A, the user presses a "next page transmission button" provided on the division request screen A, for example. Then, the transmission request for the next screen is transmitted to the management server and acquired by “I / O”. And then. Then, the transmission request is stored at address 6 of the “main memory”, and in response to this, the next page division request screen B is returned from “I / O” to the portable playback device. In this way, the divided request screens are sequentially transmitted one screen at a time to a portable playback device such as a mobile phone.

[0146] Process Flow>

FIG. 27 is a flowchart showing an example of the flow of processing in the management server included in the content reproduction system of the present embodiment. Note that the steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium. As shown in this figure, first, a ply consisting of a recording / reproducing apparatus and a portable reproducing apparatus such as a mobile phone having a function dedicated to content recorded in the recording / reproducing apparatus. In a content reproduction system including a plurality of pet reproduction systems and including a management server that manages the request, the management server aggregates requests for the same content across the private reproduction system (step S2701).

[0147] The request screen is generated and acquired based on the counting result (step S2702), and the request screen exceeds the range that can be displayed on one screen in the portable playback device that is the transmission destination. ! / Is determined (step S2703). If it is determined that the result is exceeding! /, The request screen is divided and transmitted by one screen in order of the number of requests for each request screen request from the portable playback device (step S2704).

FIG. 28 is a sequence diagram illustrating an example of a flow of processing for dividing and transmitting a request screen in the content reproduction system of the present embodiment. Note that the steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium. In this figure, only the steps in the management server and mobile playback device related to the request screen split processing are described, and the steps related to the above-mentioned cross-sectional request count processing and the generation of the request screen before splitting are described. The description of such processing of the recording / reproducing apparatus is omitted.

As shown in this figure, first, in the management server, the number of requests totaled for the same content is updated and stored in a storage medium as a count list or the like (step S2801).

[0150] After that, when a request for transmitting a request screen is performed using a UI or the like on a portable playback device such as a mobile phone, a request for transmitting a request screen is output from the portable playback device to the management server (step S2802). In this embodiment, the transmission request includes the screen size information of the display of the portable playback device itself.

[0151] When the management server receives the request for transmitting the request screen including the screen size information, the management server identifies the recording / playback device by the process described in the first embodiment, and requests according to the content list of the recording / playback device. A screen is generated and acquired based on the aggregation result (step S2803).

[0152] Then, a process for determining whether or not the generated request screen fits on one screen of the portable playback device indicated by the screen size information is executed (step S2804). Then, when the judgment result that the request screen does not fit on one screen of the portable playback device is output, the request is generated. With respect to the obtained request screen, division processing is executed so as to fit on one screen of the portable playback device based on the screen size information (step S2805). Then, the first page of the divided request screen is transmitted to a portable playback device such as a mobile phone that has output the transmission request.

[0153] Then, in a portable playback device such as a mobile phone, the received division request screen is displayed on the display or the like, and the selection of the request content is accepted (step S2807). When the user selects one of the content names on the split request screen on the UI, the request for the selected content is transmitted to the recording / playback device and the management server, respectively, and the portable playback device The content is reproduced.

[0154] When the button operation of the next page transmission request is accepted by the portable playback device (step S2808), the management server receives the next page transmission request (step S2809), and the portable playback device. Send processing of the next page of the split request screen for

[0155] A brief explanation of the effect>

As described above, with the content playback system of this embodiment, the display size of a display such as a mobile phone is small! / There are many portable playback devices! / In a private playback system! / Accordingly, communication traffic can be distributed and data can be transmitted and received efficiently.

[Example 4]

The present embodiment is a content playback system having the following characteristics with respect to a request screen transmitted from a management server to a mobile playback device such as a mobile phone based on any one of the first to third embodiments. That is, the request screen power S to be transmitted, for example, “Request screen reflecting the number of requests in other private playback systems at prime time (19:00 to 23:00)”, “Same request from September 10 to 17 The screen is a request screen that reflects the aggregated results for each predetermined time zone.

[0157] In this way, the user can know, for example, content that is frequently requested in a predetermined time zone. [0158] Highly functional configuration>

FIG. 29 is a diagram illustrating an example of functional blocks in the management server and portable playback device of the content playback system of the present embodiment. As shown in this figure, the content playback system is based on the first embodiment, and has “management server” (2900) and “private playback system α” (2910). The private playback system includes a “recording / playback device” (2911) and a “portable playback device” (2912). The management server has a “totaling unit” (2901) and a “request screen transmission unit” (2902). Since these “management servos and their constituent elements“ aggregation unit ”and“ request screen transmission unit ”,“ recording / reproducing device ”and“ portable reproducing device ”have already been described in the above embodiment, The explanation is omitted. Of course, on the basis of the second and third embodiments, other configuration requirements described above may be included.

The feature point of the present embodiment is that the management server further includes a “time zone control unit” (2903). The second feature point is that the portable playback device has a “time zone request screen request unit” (2912A).

First, the feature point of the management server will be described. The “Time Zone Control Unit” (2903) has a function to count the number of requests for the same content for each request time zone, and a request screen for each request time zone according to the time zone request screen request from the portable playback device. And a function for controlling the request screen transmission unit to transmit. Specifically, the time zone control unit preferably includes, for example, a “time zone request screen request acquisition unit”, a “time zone tabulation control unit”, and a “time zone request screen transmission control unit”.

[0161] "Time period request screen request acquisition means" has a function of acquiring a time period request screen request from a portable playback device to be described later. “Time zone request screen request” means, for example, “request screen in which the number of requests during the prime time has been aggregated”, “same request screen in September 10-17”, etc. Send a request to send the request screen specified by the band.

[0162] The "time zone counting control means" tabulates so that only requests in the time zone indicated in the time zone request screen request are counted in the cross-sectional request aggregation of multiple private playback systems in the aggregation section (2901). A function of controlling the unit. Specifically, the The number of requests for each request time zone is aggregated using transmission time information of requests included in the request.

[0163] The "time zone request screen transmission control means" generates and acquires a time zone request screen based on the number of requests aggregated by the control of the time zone aggregation control means, and the request screen transmission unit (2902 ) Has a function to control to send the time zone request screen.

Next, feature points of the portable playback device will be described. The “time zone request screen request section” (2912A) is configured to transmit a request screen request based on the result of aggregation for each time zone. Specifically, using the user interface, for example, let the user enter information indicating the time zone, such as “Prime time (19:00 to 23:00)” or “September 10 to September 17”. . Then, a request screen request including the input information as a specified time zone is generated and transmitted to the management server and the recording / reproducing apparatus.

FIG. 30 is a conceptual diagram showing an example of this time zone request screen transmission process. As shown in this figure, first, a request to be aggregated across the private playback system is sent to the request transmission time, such as “October 12 20:31” or “October 15 22:01”. To include.

[0166] Then, when the management server receives the "prime time request screen" and! /, The time zone request screen request from the portable playback device, the transmission time included in the request is used to specify the designated time zone "19:00 The content corresponding to “from 23:00” is extracted by CPU processing, and the number of requests is counted. Then, the request screen reflecting the number of requests in the time zone specified by the time zone request screen request is transmitted to the portable playback device.

[0167] Special hardware configuration>

FIG. 31 is a schematic diagram showing an example of a configuration in the management server of the content reproduction system when the above functional components are realized as hardware. The operation of each hardware component in the time zone request screen generation process on the management server will be described using this figure.

As shown in this figure, the management server included in the content reproduction system of the present embodiment is Similarly to the first embodiment, a “CPU” (3101), a “main memory” (3102), an “HDD” (3103), and a “1 / OJ (3104)” are provided. Through the process described in, a request across the private playback system is acquired, and recorded and retained at “HDD” addresses 1, 2,. The request acquired at this time includes transmission time information of the request.

[0169] After that, in response to a user operation, a time zone request screen request specifying a time zone is transmitted from the portable playback device, such as "request screen in which the number of requests from 19:00 to 23:00 is aggregated".

The time zone request screen request is received by “I / O” of the management server and stored in address 1 of “main memory”. Then, the “specified time zone” included in the request is compared with the “request transmission time” included in the request! Only requests sent at the time included in the band are extracted. The total number of requests for each content based on the extraction result is executed by the process described in the first embodiment, and the total result is stored in the address 2 of the “main memory”. Then, a time zone request screen is generated using the totaled result, and is transmitted from “I / O” to the portable playback device.

[0171] Process flow>

FIG. 32 is a flowchart showing an example of the processing flow in the management server included in the content reproduction system of the present embodiment. Note that the steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium. As shown in this figure, first, a plurality of private playback systems including a recording / playback device and a mobile playback device such as a mobile phone having a request function dedicated to content recorded in the recording / playback device are provided. In the content reproduction system including the management server that manages the request, the management server acquires the request including the transmission time information across the private reproduction system (step S3201).

[0172] Thereafter, when the time zone request screen request transmitted from the portable playback device is acquired (step S3202), the time indicated by the time zone request screen request is based on the transmission time information included in the acquired request. Aggregate the number of requests for the same content for each band (Step S3203). Then, a time zone request screen is generated and acquired based on the counting result (step S3204), and the time zone request screen is transmitted to the portable playback device (step S3205).

FIG. 33 is a sequence diagram showing an example of a flow of processing for transmitting a time zone request screen in the content reproduction system of the present embodiment. Note that the steps shown below may be processing steps that constitute a program for controlling a computer recorded on a medium. In this figure, only the management server related to the transmission processing of the time zone request screen and the steps in the portable playback device are described, and the above-mentioned cross-sectional request aggregation processing and recording playback device processing are described. Omitted.

As shown in this figure, first, the management server acquires a request including its own transmission time information across the private playback system, and records it for storage in a recording medium (step S3301).

[0175] After that, when a request for transmission of the request screen specifying the time zone is made using a UI or the like on a portable playback device such as a mobile phone, the time zone request screen is sent from the portable playback device to the management server. A request is output (step S3302). When the management server receives this time zone request screen request, it counts the number of requests for the same content for each time zone indicated by the time zone request screen request based on the transmission time information included in the acquired request ( Step S3303). Although not shown, the content list of the recording / playback apparatus is acquired by the process described in the first embodiment. Then, a time zone request screen is generated and acquired based on the counting result and the content list (step S3304). Then, the generated time zone request screen is transmitted to a portable playback device such as a cellular phone that has output the transmission request (step S3305).

[0176] Then, in a portable playback device such as a mobile phone, the received time zone request screen is displayed on a display or the like, and the selection of the requested content is accepted (step S3306). When the user selects one of the content names on the request screen on the UI, the request for the selected content is transmitted to the recording / playback device and the management server, respectively, and the portable playback device The content is reproduced.

[0177] A brief explanation of the effect> As described above, the content reproduction system of the present embodiment allows the user to know the content that has been requested many times during a predetermined time period.

Brief Description of Drawings

FIG. 1 is a diagram showing an example of a request screen of a portable playback device in the content playback system of Embodiment 1.

FIG. 2 is a diagram illustrating an example of functional blocks in the content reproduction system according to the first embodiment.

FIG. 3 is a diagram illustrating an example of functional blocks in the recording / playback apparatus of the content playback system according to the first embodiment.

FIG. 4 is a diagram illustrating an example of functional blocks in the portable playback device of the content playback system according to the first embodiment.

FIG. 5 is a schematic diagram showing an example of a request transmitted from the portable playback device to the recording / playback device in the private playback system of the content playback system according to the first embodiment.

FIG. 6 is a diagram for explaining an example of a private playback system included in the content playback system of the first embodiment.

FIG. 7 is a conceptual diagram for explaining an example of request transmission to the management server in the content reproduction system of this embodiment.

FIG. 8 is a conceptual diagram showing an example of cross-sectional request aggregation in a plurality of private reproduction systems in the aggregation unit of the management server included in the content reproduction system of Example 1.

FIG. 9 is a diagram for explaining an example of content identity identification by content data matching processing in the aggregation unit of the management server included in the content reproduction system of the first embodiment.

FIG. 10 is a diagram showing an example of a request screen transmitted from the request screen transmission unit of the management server included in the content reproduction system of the first embodiment.

[FIG. 11] A diagram showing another example of a request screen transmitted from the request screen transmission unit of the management server included in the content reproduction system of the first embodiment.

FIG. 12 is a diagram illustrating an example of a more detailed function block in the management server of the content reproduction system of the first embodiment.

FIG. 13: Harduee in the management server included in the content reproduction system of the first embodiment Schematic diagram showing an example of key configuration

FIG. 14 is a flowchart showing an example of a processing flow in the management server included in the content reproduction system of the first embodiment.

15] Sequence diagram showing an example of the processing flow until requests are aggregated across the content playback system of Example 1

FIG. 16 is a sequence diagram showing an example of a request processing flow using a request screen in the content reproduction system of the first embodiment.

FIG. 17 is a diagram illustrating another example of functional blocks in the content reproduction system according to the first embodiment.

FIG. 18 is a diagram showing an example of functional blocks in the content playback system of Embodiment 2. FIG. 18 is a diagram showing an example of content recorded by processing in the specific recording unit of the recording / playback apparatus of Embodiment 2.

20] A diagram showing an example of a more detailed functional block in the recording / playback apparatus of the content playback system of the second embodiment.

21] Schematic showing an example of the hardware configuration of the recording / playback apparatus of the content playback system of Embodiment 2

FIG. 22 is a flowchart showing an example of a process flow in the recording / playback apparatus of the content playback system in the second embodiment.

FIG. 23 is a diagram illustrating an example of functional blocks in the management server of the content reproduction system according to the third embodiment.

24] Conceptual diagram showing an example of control processing for dividing the request screen in the request screen transmission control unit of the management server of Example 2

25] A diagram showing an example of a more detailed functional block in the management server of the content reproduction system of the third embodiment.

FIG. 26 is a schematic diagram showing an example of a hardware configuration in the management server of the content reproduction system of Example 3.

FIG. 27 is a flowchart showing an example of a process flow in the management server of the content reproduction system of the third embodiment. 28] Sequence diagram showing an example of the flow of processing for dividing and transmitting the request screen in the content reproduction system of the third embodiment

FIG. 29 is a diagram showing an example of functional blocks in the content reproduction system of the fourth embodiment. FIG. 29 is a conceptual diagram showing an example of time zone request screen transmission processing in the management server of the fourth embodiment.

FIG. 31 is a schematic diagram showing an example of a hardware configuration in the management server of the content reproduction system of Example 4.

FIG. 32 is a flowchart showing an example of a process flow in the management server of the content reproduction system of the fourth embodiment.

FIG. 33 is a sequence diagram illustrating an example of a process flow for transmitting a time zone request screen in the content reproduction system of the fourth embodiment.

Explanation of symbols

0200 Management server

0201 Total department

0202 Request screen transmitter

0210 α Private playback system α

021 1 α Recording / playback device

0212 α Portable playback device

0210/3 Private playback system / 3

0210 γ Private playback system γ

Claims

The scope of the claims

[1] A content playback system including a plurality of private playback systems including a recording / playback device and a portable playback device having a function dedicated to content recorded in the recording / playback device, and including a management server for managing the request. And

The management server includes a totaling unit that aggregates requests for the same content across the private playback system,

A request screen transmission unit that transmits a request screen, which is an interface screen for a request, to the portable playback device based on the aggregation result in the aggregation unit;

A content reproduction system comprising:

[2] The content playback system according to claim 1, wherein the mobile playback device is a mobile phone terminal device.

[3] The recording and playback device

A reception unit that accepts the user's ability to search conditions including content attributes;

A specific recording unit that identifies and records content that matches the accepted search conditions from a content table such as an electronic program guide;

The content reproduction system according to claim 1 or 2, further comprising:

[4] The management server

A request screen generation unit that generates a request screen in which the number of requests for the same content is aggregated and the content can be selected in descending order based on the aggregation result,

If the request screen that generated the range that can be displayed on one screen is exceeded in the portable playback device that is the destination of the request screen, the request screen from the portable playback device requests one screen in order of the number of requests for each request. A request screen transmission control unit that divides the screen and transmits it to the request screen transmission unit;

The content reproduction system according to any one of claims 1 to 3, further comprising:

[5] The management server

The number of requests for the same content is aggregated for each request time zone, and a request screen for each request time zone is sent in response to the time zone request screen request from the mobile playback device. Has a time zone control unit that controls the request screen transmission unit to communicate,

Portable playback device

Has a time zone request screen request section for sending requests for request screens based on the results of counting for each time zone

The content reproduction system according to any one of claims 1 to 4.

[6] In a content playback system including a plurality of private playback systems including a recording / playback device and a portable playback device having a function dedicated to content recorded in the recording / playback device, and including a management server for managing the request,

In the management server, a totaling step for totalizing requests for the same content across private playback systems,

A request screen sending step for sending a request screen, which is an interface screen for a request, to the portable playback device based on the counting result in the counting step, and a content playback method for causing a computer to execute.

7. The content playback method according to claim 6, wherein the mobile playback device is a mobile phone terminal device.

[8] In the recording / playback device,

A reception step for accepting a search condition including content attributes by a user, a specific recording step for identifying and recording content that matches the received search condition from a content table such as an electronic program guide,

The content reproduction method according to claim 6 or 7, wherein the computer is executed.

[9] On the management server,

Request screen generation that counts the number of requests for the same content and generates a request screen in which the content can be selected in descending order based on the total number of requests. Can be displayed on one screen on the portable playback device that is the destination of the request screen If the request screen that generated the range exceeds the request screen transmission from the mobile playback device, the request screen is divided by one screen in the order of the number of requests for each request and sent in the request screen transmission step. Control steps;

The content reproduction method according to any one of claims 6 to 8, which causes a computer to execute. On the management server,

Time zone control that counts the number of requests for the same content for each request time zone and controls the request screen transmission step to send the request screen for each request time zone in response to the time zone request screen request from the mobile playback device Let the computer execute the steps,

On a portable playback device,

Causes the computer to execute the time zone request screen request step for sending a request screen request based on the total result for each time zone

The content reproduction method according to any one of claims 6 to 9.